TIBCO ActiveMatrix BusinessWorks Plug

TIBCO ActiveMatrix BusinessWorks Plug
TIBCO ActiveMatrix
BusinessWorks™ Plug-in for
WebSphere MQ
Release Notes
Software Release 7.6.0
November 2015
Two-Second Advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED
OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED
ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED
SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR
ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE
AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER
LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE
SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE
LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED
IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS
AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN
AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and
treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO
Software Inc.
TIBCO, Two-Second Advantage, TIBCO Administrator, TIBCO ActiveMatrix BusinessWorks,
TIBCOActiveMatrix BusinessWorks Plug-in for Data Conversion, TIBCO BusinessWorks XA Transaction
Manager, TIBCO Designer, TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ, TIBCO Enterprise
Message Service, TIBCO Hawk, TIBCO Rendezvous, and TIBCO Runtime Agent are either registered
trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition
(J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation
in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE
INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE
IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN
THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING
BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2012-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
| iii
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Documentation . . . . . . . . . . . . . . . . . . . . .
Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Third-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
vi
vi
vii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xi
xi
xi
xi
Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 7.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Release 7.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Release 7.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Release 7.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Release 7.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Release 7.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Release 7.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Release 7.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
iv
| Contents
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
|v
Preface
TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ is referred to
as the plug-in in this manual. With this plug-in, you can design and implement
ActiveMatrix BusinessWorks applications that exchange messages with other
WebSphere MQ-capable applications across a wide range of hardware and
operating systems.
Topics
•
Related Documentation, page vi
•
Typographical Conventions, page viii
•
Connecting with TIBCO Resources, page xi
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
vi
| Related Documentation
Related Documentation
This section lists documentation resources you might find useful.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Documentation
The following documents form the TIBCO ActiveMatrix BusinessWorks Plug-in
for WebSphere MQ documentation set:
•
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Installation Read
this manual for instructions on site preparation and installation.
•
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s
Guide Read this manual for instructions on using the product on all platforms.
•
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release
Notes Read the release notes for a list of new and changed features. This
document also contains lists of known issues and closed issues for this release.
Other TIBCO Product Documentation
You might find it useful to read the documentation for the following TIBCO
products:
•
TIBCO Administrator™ software: this product provides capabilities for
managing users, monitoring machines, and deploying and managing
applications that use TIBCO products.
•
TIBCO ActiveMatrix BusinessWorks™ software: this product provides an
integration platform for companies to rapidly integrate systems and automate
business processes.
•
TIBCO ActiveMatrix BusinessWorks™ Plug-in for Data Conversion software:
this product is a prerequisite for working with TIBCO ActiveMatrix
BusinessWorks Plug-in for WebSphere MQ.
•
TIBCO BusinessWorks™ XA Transaction Manager software: this product is
required if the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere
MQ activities run in a TIBCO BusinessWorks XA Transaction group.
•
TIBCO Designer™ software: TIBCO Designer is an intuitive graphical user
interface for the design-time configuration of TIBCO applications. Online help
is available for TIBCO Designer palettes.
•
TIBCO Enterprise Message Service™ software: this product sends messages
from your applications in a format that conforms to the Java Messaging
Service (JMS) specification.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Preface vii
|
•
TIBCO Hawk® software: this product is for monitoring and managing
distributed applications and systems throughout the enterprise.
Third-Party Documentation
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ relates to other
products documentation which you might find helpful.
WebSphere MQ description and documentation, which might be found at:
http://www-01.ibm.com/software/integration/wmq/library/library75.html
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
viii
| Typographical Conventions
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 General Typographical Conventions
Convention
Use
ENV_NAME
TIBCO products are installed into an installation environment. A product
installed into an installation environment does not access components in other
installation environments. Incompatible products and multiple instances of the
same product must be installed into different installation environments.
TIBCO_HOME
<ProductAcron
ym>_HOME
An installation environment consists of the following properties:
•
Name Identifies the installation environment. This name is referenced in
documentation as ENV_NAME. On Microsoft Windows, the name is
appended to the name of Windows services created by the installer and is a
component of the path to the product shortcut in the Windows Start > All
Programs menu.
•
Path The folder into which the product is installed. This folder is referenced
in documentation as TIBCO_HOME.
TIBCO <ProductName> installs into a directory within a TIBCO_HOME. This
directory is referenced in documentation as <ProductAcronym>_HOME. The
default value of <ProductAcronym>_HOME depends on the operating system.
For example on Windows systems, the default value is
C:\tibco\<ProductAcronym>\<ReleaseNumber>.
code font
Code font identifies commands, code examples, filenames, pathnames, and
output displayed in a command window. For example:
Use MyCommand to start the foo process.
bold code
font
Bold code font is used in the following ways:
•
In procedures, to indicate what a user types. For example: Type admin.
•
In large code samples, to indicate the parts of the sample that are of
particular interest.
•
In command syntax, to indicate the default parameter for a command. For
example, if no parameter is specified, MyCommand is enabled:
MyCommand [enable | disable]
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Preface ix
|
Table 1 General Typographical Conventions (Cont’d)
Convention
Use
italic font
Italic font is used in the following ways:
Key
combinations
•
To indicate a document title. For example: See TIBCO ActiveMatrix
BusinessWorks Concepts.
•
To introduce new terms For example: A portal page may contain several
portlets. Portlets are mini-applications that run in a portal.
•
To indicate a variable in a command or code syntax that you must replace.
For example: MyCommand PathName
Key name separated by a plus sign indicate keys pressed simultaneously. For
example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed one after the
other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or importance, for
example, an additional action required only in certain circumstances.
The tip icon indicates an idea that could be useful, for example, a way to apply
the information provided in the current section to achieve a specific result.
The warning icon indicates the potential for a damaging situation, for example,
data loss or corruption if certain steps are taken or not taken.
Table 2 Syntax Typographical Conventions
Convention
Use
[ ]
An optional item in a command or code syntax.
For example:
MyCommand [optional_parameter] required_parameter
|
A logical OR that separates multiple items of which only one may be chosen.
For example, you can select only one of the following parameters:
MyCommand param1 | param2 | param3
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
x
| Typographical Conventions
Table 2 Syntax Typographical Conventions (Cont’d)
Convention
Use
{ }
A logical group of items in a command. Other syntax notations may appear
within each logical group.
For example, the following command requires two parameters, which can be
either the pair param1 and param2, or the pair param3 and param4.
MyCommand {param1 param2} | {param3 param4}
In the next example, the command requires two parameters. The first parameter
can be either param1 or param2 and the second can be either param3 or param4:
MyCommand {param1 | param2} {param3 | param4}
In the next example, the command can accept either two or three parameters.
The first parameter must be param1. You can optionally include param2 as the
second parameter. And the last parameter is either param3 or param4.
MyCommand param1 [param2] {param3 | param4}
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Preface xi
|
Connecting with TIBCO Resources
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and
resident experts. It is a place to share and access the collective experience of the
TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety
of resources. To register, go to https://community.tibco.com/.
How to Access TIBCO Documentation
Documentation for this and other TIBCO products is available on the TIBCO
Documentation site:
https://docs.tibco.com
Documentation on the TIBCO Documentation site is updated more frequently
than any documentation that might be included with the product. To ensure that
you are accessing the latest available help topics, please visit us at
https://docs.tibco.com.
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact
TIBCO Support as follows:
•
For an overview of TIBCO Support, and information about getting started
with TIBCO Support, visit this site:
http://www.tibco.com/services/support
•
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user
name, you can request one.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
xii
| Connecting with TIBCO Resources
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
|1
Release Notes
Check the TIBCO Product Support website at https://support.tibco.com for
product information that was not available at release time. Entry to this site
requires a user name and password. If you do not have a user name, you can
request one. You must have a valid maintenance or support contract to use this
site.
Topics
•
New Features, page 2
•
Changes in Functionality, page 5
•
Deprecated and Removed Features, page 6
•
Migration and Compatibility, page 7
•
Closed Issues, page 8
•
Known Issues, page 12
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
2
|
Release Notes
New Features
This section lists features added since the 7.5.0 release of TIBCO ActiveMatrix
BusinessWorks Plug-in for WebSphere MQ.
Release 7.6.0
The new features in this release are:
WebSphere MQ Listener Activity and WebSphere MQ Subscriber Activity
•
The WebSphere MQ Listener activity and WebSphere MQ Subscriber activity
now have the option to release their connections after each message
confirmation. This option is the Disable Connection Reuse check box, which
causes the event starter to release the connection after confirming the
message.
•
The WebSphere MQ Listener activity can filter messages in the usual three
fields (Correlation Id, Message Id, and Group Id) by using a filter composed
of a text, hexbin, or base64 filter string.
•
The WebSphere MQ Listener activity and WebSphere MQ Subscriber activity
can now emit errors with the Error Output check box selected. If the Error
Output option is enabled in the Advanced tab, when the listener or subscriber
encounters an error condition, the listener or subscriber creates new processes
composed of a BwmqException object. Previously, the WebSphere MQ
Listener activity and WebSphere MQ Subscriber activity only logged these
conditions but these conditions are now available for application level
interception.
•
The WebSphere MQ Listener activity can now relocate messages that, for
some reason, cannot be confirmed to a special queue where they can be
processed by error recovery logic, or manually recovered. This is called
Poison Message Detection and is only available when the listener is
processing single messages using message confirmation. See the description
of the MultiMessage tab in the TIBCO ActiveMatrix BusinessWorks Plug-in for
WebSphere MQ User’s Guide.
New Inquire Activity
The WebSphere MQ Inquire activity is added to inquire about the current state of
a queue. It is primarily intended to obtain the depth of the queue.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
New Features 3
|
Dynamic Properties
All activities that work with messages now have a DynamicProperties node in
their input or output schemas. This node works like its JMS equivalent and allows
JMS messages containing dynamic properties to be seamlessly mapped between
MQ and JMS. This node also allows MQ activities to work with application
properties without having a schema defined.
Pooling Changes
In TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ 7.5.0 and
earlier versions, the activities pool connections by using the pooling manager
provided with the WebSphere MQ Client API. However, this pool manager incurs
a small disconnect or reconnect penalty for pooled connections as well as some
awkwardness when CCDT connections are used.
Version 7.6.0 introduces a new custom connection manager that keeps truly hot
standby connections in a pool for use by activities. No configuration changes are
made for this feature.
Error Schema
The BwmqException object has two new fields: mqCompCode and
mqReasonCode. These fields contain the completion and reason codes from the
most recently failed WebSphere MQ API call. The mqCompCode and
mqReasonCode fields are now displayed in the Error Output tab of each
WebSphere MQ activity.
Support for Load Balance
This release adds the Load Balance check box in the Advanced tab of the
WebSphere MQ Put activity. You can use it to enable load balancing when putting
messages in suitably configured cluster queues.
Release 7.5.0
The new features in this release are:
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
4
|
Release Notes
Adding SyncPoint Activity
The SyncPoint Activity has been introduced to give application designers an
alternative to XA transactions. XA transactions involve significant overhead and
have a finite lifespan when used with the WebSphere MQ transaction resource (60
seconds). To use the SyncPoint Activity simply enable the "Commit Via SyncPoint
Activity" option on the multi-message tab of all the get and put operations which
are to be synced together and then call the SyncPoint Activity to commit or back
out the operations on the associated queues.
Adding CustomSegmented Option
Using the previous versions of the plug-in, you were able to create or consume a
Logical Grouped Message by calling a Put or Get operation in a loop. A similar
option has been added to make it possible to do the same thing with a Segmented
Group Message. This mode of operation is expressly intended to allow an
application to put a segmented message in a queue which is too large to fit in the
BW Engine's memory. The message can be parsed externally (for instance by a
Java activity) and iteratively placed on a queue by a loop.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Changes in Functionality 5
|
Changes in Functionality
This section lists changes in functionality since the 7.5.0 release of TIBCO
ActiveMatrix BusinessWorks Plug-in for WebSphere MQ.
Release 7.6.0
The changes in functionality in this release are:
Pool Manager
The internal WebSphere MQ client API connection manager (which used the
MQSimpleConnectionManager object) has been replaced with a dedicated pool of
hot standby connections. No configuration changes are made related to this
change and the only observable effect is improved performance for normally low
latency activities, such as the WebSphere MQ Get activity and the WebSphere MQ
Publish activity.
Tracing
When using the IBM WebSphere internal tracing facilities, the activities no longer
switch the tracing on and off as they run. If tracing is enabled, then it is turned on
by the first activity to run and remains on until the JVM is shut down. This
addresses the potential for missing trace records.
Batch Size
Regarding the WebSphere MQ Get activity and Listener activity, the Batch Size
field in the MultiMessage tab is now limited only by the amount of memory
available and the work unit size of the queue manager.
Note that using an excessively large value might cause the plug-in to run out of
memory.
Release 7.5.0
There are no changes in functionality in this release.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
6
|
Release Notes
Deprecated and Removed Features
This section describes deprecated features (if any), and lists features, if relevant,
that may be useful alternatives to the deprecated features. Any use of a
deprecated feature should be discontinued as it may be removed in a future
release. You should avoid becoming dependent on deprecated features and
become familiar with the suggested alternative features.
This section also lists features that are removed (if any).
Release 7.6.0
No features are deprecated or removed in this release.
Release 7.5.0
No features are deprecated or removed in this release.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Migration and Compatibility 7
|
Migration and Compatibility
This section explains how to migrate from a previous release to this release.
Release 7.6.0
There are no migration procedures or compatibility issues in this release.
Release 7.5.0
There are no migration procedures or compatibility issues in this release.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
8
|
Release Notes
Closed Issues
The table in this section lists issues that were closed in the named releases of
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ.
Closed
in
Release
Key
Summary
7.6.0
BWMQ-433
WebSphere MQ activities did not work in a JDBC transaction group.
Now WebSphere MQ activities (Put and Get) function in a JDBC
transaction group; however, they are not commit coordinated by the
JDBC transaction.
7.6.0
BWMQ-421
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ 7.6.0
meets the need to be able to listen or subscribe by hex encoded filter
fields. A new filter encoding field has been added to the listener
configuration to allow messages to be filtered by binary values encoded
as either base64 or hexbin.
7.6.0
BWMQ-418
The WebSphere MQ SyncPoint activity did not fail in conditions where
it should.
If the connection is invalid or no activity has used the connection to
create a unit of work, the WebSphere MQ SyncPoint activity now fails.
7.6.0
BWMQ-414
The WebSphere MQ Subscriber activity or Listener activity hung on
explicit confirm in certain configurations.
7.6.0
BWMQ-413
After the WebSphere MQ Put activity was configured in a loop, if an
exception related to a non-existent destination, the WebSphere MQ Put
activity threw a different error message on the second and successive
iterations through a loop than the first iteration did.
7.6.0
BWMQ-410
The mqCompCode and mqReasonCode fields are now displayed in
the Error Output tab of each WebSphere MQ activity.
7.6.0
BWMQ-404
The icon with which the plug-in decorated the queue picker was
removed or renamed in TIBCO Runtime Agent of the latest version. As
a result, the Queue Picker button hung TIBCO Designer.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Closed Issues 9
|
Closed
in
Release
Key
Summary
7.6.0
BWMQ-401
When using TIBCO Designer to test a Listener with the confirm activity,
if the Stop button was pressed on the debugger, it was possible to have
a message confirmed, and therefore removed from the queue.
In the Designer context, this confirmation is now backed out.
7.6.0
BWMQ-399
Regarding the WebSphere MQ Get activity and Listener activity, the
Batch Size field in the MultiMessage tab is now limited only by the
amount of memory available and the work unit size of the queue
manager.
Note that using an excessively large value might cause the plug-in to
run out of memory.
7.6.0
BWMQ-393
If the WebSphere MQ Listener activity attempted to reconnect to an
unavailable queue manager, an error message was displayed but the
error message unexpectedly contained the user password in plain text.
7.6.0
BWMQ-372
WebSphere MQ API warning exceptions caused the WebSphere MQ
Listener activity to report an error. Most incidences of warnings are
triggered by using the GMO Convert option on a message with an
invalid charset or encoding properties. As part of this change, the
message has been changed so as not to reference the error role.
The new message follows the format:
2015 Mar 14 10:29:48:607 GMT -0600
BW.TestMQWarnings-Process_Archive Warn [bw.logger]
BW-EXT-LOG-200000 BWMQ-100500 Warning exception returned
from the WebSphere MQ java library: WebSphere MQ Listener
Start: MQJE001: Completion Code '1', Reason '2110'.
If your deployment monitored the previous message, that monitor
must be updated.
7.6.0
BWMQ-369
When you attempted to install TIBCO ActiveMatrix BusinessWorks
Plug-in for WebSphere MQ 7.4.0 without installing TIBCO Designer,
the "DEPENDENCY CHECK FAILED" error occurred.
7.6.0
BWMQ-368
Dynamic Application properties are now supported for the WebSphere
MQ Put activity in version 7.6.0. All activities except the Inquire activity
now have the DynamicProperties node in their input or output
schemas where appropriate.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
10
|
Release Notes
Closed
in
Release
Key
Summary
7.6.0
BWMQ-356
The WebSphere MQ Listener activity did not correctly stop or start in
response to the engine throttling. Additionally, the activity did not
recover correctly from a network or queue manager interruption.
7.5.0
BWMQ-353
If WebSphere MQ connections were involved with XA transactions, the
connections used the close() method instead of using the
disconnect() method. This could potentially cause the orphaned
connections.
7.5.0
BWMQ-334
When using the WMQ Connection, if the connection was the Client
Connection Data Table Binding type with pooling enabled, it was not
pooled. The reason for this situation was that the WebSphere MQ API
did not provide a pooling mechanism for multiple CCDT pools
equivalent to that provided for remote connections.
Note: You cannot create multiple simultaneous CCDT connection pools
but you can use a CCDT connection pool with some restrictions.
For more details about the restrictions, see the Pooling of CCDT
Connections part in Chapter 3 of TIBCO ActiveMatrix BusinessWorks
Plug-in for WebSphere MQ User’s Guide.
7.5.0
BWMQ-331
Errors occurred when the Get activity was in a loop and fetched on
different queues.
7.5.0
BWMQ-329
The Get and Put activities could not be made to reconnect to the queue
manager after a server or network failed.
7.5.0
BWMQ-308
With the WebSphere MQ SyncPoint activity and the Commit Via
SyncPoint Activity check box which have been added to the plug-in ,
the WebSphere MQ unit of work can be committed or rolled back in the
WMQ Commit activity.
This has been fixed.
7.5.0
BWMQ-301
The plug-in did not support to commit coordinate multiple queue
operations outside of XA transactions.
7.5.0
BWMQ-300
When the process was under heavy load, the engine repeatedly started
and stopped the Listener activity. If the Listener activity was
interrupted in the middle of getting messages, it might not correctly
return its connection to the pool. The Listener activity did not close
connections correctly.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Closed Issues 11
|
Closed
in
Release
Key
Summary
7.5.0
BWMQ-296
When using the XA transactions with multiple servers, the XA
transactions failed.
7.5.0
BWMQ-295
When running a process with the logical messages, the logical messages
had the same message ID across the group.
7.5.0
BWMQ-291
When running a process with a Get activity, if the Explicit Syncpoint
check box was selected, the message was not correctly rolled back.
7.5.0
BWMQ-289
Running a process with the Get activity failed if the z/OS queue was
not indexed in the filter. The options MQGMO_ALL_MSGS_AVAILABLE and
MQGMO_LOGICAL_ORDER were turned off in this situation.
7.5.0
BWMQ-288
A validation error: unexpected content applicationIdData
error occurred if you used the plug-in 7.4 version to run a process
which was made from version 7.2 or version 7.3 with the valid value in
the applicationIdData field.
7.5.0
BWMQ-267
When using the Listener activity, if you selected BatchGroup from the
Multi Message Support list, the Correlation Id, Message Id and
Group Id fields were unavailable.
7.5.0
BWMQ-259
The responsetimemillisec field in the Output Tab of WMQ Get palette
was invalid.
7.5.0
BWMQ-251
The group-id field is available as a filter on the Put, Get and Listen
activities.
This has been fixed.
7.5.0
BWMQ-218
The TLS check box is externalized. When using the WMQ Connection
with selecting the TLS check box, the configuration property can be
mapped to a global variable and thus be switchable at run time.
This has been fixed.
7.5.0
BWMQ-213
When using the WMQ Connection, if the Pooling Enabled check box
was selected, the WMQ connections were not marked as available and
returned to the pool after a network outage.
This issue was addressed by IBM in the MQ Client versions 7.5.0.5,
8.0.0.1 and above.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
12
|
Release Notes
Known Issues
The table lists known issues in version 7.6.0 of TIBCO ActiveMatrix
BusinessWorks Plug-in for WebSphere MQ.
Key
Summary/Workaround
BWMQ-467
Summary: On the platforms where TIBCO Designer and TIBCO ActiveMatrix
BusinessWorks run in the IBM JRE, if a PKCS12 file is used as the key repository,
TLS connections cannot connect to the queue manager.
Workaround: On those platforms, use a Java key store to connect to the queue
manager.
BWMQ-465
Summary: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ cannot
be uninstalled completely on the zLinux platform. The
TIB_bwpluginmq_7.6.0_readme file remains in the TIBCO_HOME/release_notes
directory after the uninstallation.
Workaround: Manually delete the TIB_bwpluginmq_7.6.0_readme file after the
uninstallation.
BWMQ-464
Summary: If the destination of a WebSphere MQ Inquire activity is only mapped
into the input schema, the Validate Project For Deployment operation for the
Inquire activity generates an error.
It is safe to ignore this error.
Workaround: None.
BWMQ-332
Summary: If you use the plug-in with the IBM MQ server version 7.0, the plug-in
does not support the TIBCO ActiveMatrix BusinessWorks debug trace properties.
Workaround: Use IBM MQ server version 7.5 or above.
TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising