TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes Software Release 8.5.0 August 2016 Two-Second Advantage
2 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 ActiveMatrix BusinessWorks, TIBCO ActiveMatrix BusinessWorks Plug-in for Data Conversion, TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ, TIBCO Business Studio, and TIBCO Enterprise Administrator 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-2016 TIBCO Software Inc. All rights reserved. TIBCO Software Inc. Confidential Information
3 Contents TIBCO Documentation and Support Services...4 New Features...5 Changes in Functionality... 7 Deprecated and Removed Features...8 Migration and Compatibility...9 Closed Issues...10 Known Issues...12
4 TIBCO Documentation and Support Services Documentation for this and other TIBCO products is available on the TIBCO Documentation site. This 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: https://docs.tibco.com Product-Specific Documentation Documentation for TIBCO products is not bundled with the software. Instead, it is available on the TIBCO Documentation site. To directly access documentation for this product, double-click the following file: TIBCO_HOME/release_notes/TIB_bwmq_version_docinfo.html where TIBCO_HOME is the top-level directory in which TIBCO products are installed. On Windows, the default TIBCO_HOME is C:\Program Files\tibco. On UNIX systems, the default TIBCO_HOME is /opt/tibco. The following documents for this product can be found on the TIBCO Documentation site: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Installation TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User's Guide TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes The following documents provide additional information and can be found on the TIBCO Documentation site: TIBCO ActiveMatrix BusinessWorks Documentation TIBCO Enterprise Administrator User's Guide How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, contact TIBCO Support: 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. How to Join TIBCO Community TIBCO Community 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. TIBCO Community offers forums, blogs, and access to a variety of resources. To register, go to the following web address: https://community.tibco.com
5 New Features The following new features have been added since the version 8.3.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. Release 8.5 The new features in this release are as follows: WebSphere MQ Support for CICS and IMS Headers The CICS and IMS headers are now available on the input and output schemas for appropriately configured ReqReply activities. See the advanced tab of the ReqReply activity. Release 8.4 The new features in this release are as follows: WebSphere MQ Inquire Activity In this release, the WebSphere MQ Inquire activity is added in the product. The WebSphere MQ Inquire activity inquires about the current state of a queue and is primarily intended to obtain the depth of the queue. WebSphere MQ Browse Activity In this release, the WebSphere MQ Browse activity is added in the product. A process with the Browse activity can browse the contents of a queue nondestructively. The contents of messages can be used directly, or can be used as a filter by the Get activity to remove the message from the queue. To access all the messages on a queue, the activity might be used in a loop. Listener Changes The Listener activity can filter messages on the usual three fields (message/correlation/group identifier) using a filter composed of a text, hexbin or base64 filter string. Pooling Changes In previous versions of the plug-in, the activities pool connections were using the pooling manager provided by the WebSphere MQ Client API. However, this pool manager incurred a small disconnect or reconnect penalty for pooled connections as well as some awkwardness when CCDT connections were used. Version 8.4.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. Version Information in the Log In this release, two INFO messages with the version numbers of the plug-in and WebSphere MQ client API are printed to the log at run time. Release 8.3 The new features in this release are as follows: Support for TIBCO Eclipse Plug-in This release adds support for TIBCO Eclipse Plug-in, an installation package for the Eclipse provisioning platform. The TIBCO Eclipse Plug-in supports the installation of the TIBCO ActiveMatrix BusinessWorks Plug-in within the Eclipse environment. Support for Load Balance This release adds the Load Balance check box in the Advance tab of the Put activity. You can use it to enable load balancing when putting messages into suitably configured cluster queues.
6 Support for CustomSegmented This release adds the CustomSegmented radio button in the Multi-Message tab of the Get and Put activities. You can use it to create segmented messages in a loop when the message is too large to fit into memory all at once. Support for Dynamic Properties This release adds support for dynamic properties, which are located in the input and output schemas of all activities. Dynamic properties provide access to message properties in a completely dynamic way. JMS messages support the use of properties in a dynamic way, and messages can be more easily mapped from JMS activities to MQ activities and back without necessarily knowing the schema in advance. Support for Poison Message Detection This release adds support for poison message detection in the Listener activity. A poison message is a message whose backout count exceeds the poison message threshold as defined in the activity. Poison messages are moved to the designated poison message queue. When a process with a Listener activity does not confirm a message, the message is returned to the queue and is reprocessed by the Listener activity. Each time the message is returned to the queue, its backout count is increased. Because the message is at the front of the queue, it is processed over and over again by the Listener activity, and make it impossible to process other messages on the queue. This feature is meant to prevent this situation from happening. To detect poison messages, you must select the Require Client Confirmation check box in the General tab of the Listener activity and click None from the Multi -Message Support area in the Multi-Message tab.
7 Changes in Functionality The following are changes in functionality since the version 8.3.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. Release 8.5 As of version 8.5 of the plug-in pooled, connections are checked for validity when they are removed from the pool. This check involves a small amount of latency, but prevents a connection that has failed while in the pool from being used in an activity and causing an application failure. If the small amount of latency is not acceptable in the application, this check can be turned off. Release 8.4 The change in functionality in this release is as follows: Pool Manager The internal WebSphere MQ client API connection manager, which used the MQSimpleConnectionManager object, is replaced with a dedicated pool of hot standby connections. There are no configuration changes related to this change and the only observable effect is the improved performance for normally low latency activities, such as the Get activity and Publish activity. Release 8.3 The changes in functionality in this release are as follows: Recover Process in Looping Activities In previous versions, you could not use the Get, Put, and Publish activities in a loop with error recovery to run completely reliable processes, which could run despite of network or queue manager outage. This is because the error terminated the loop and the processes failed. As of this release, the processes can recover from related failures of a network and queue manager, and run correctly when those conditions abate. Dynamic Destinations for Looping Activities In previous versions, when the Get, Put, and Publish activities were used in a loop, the destination and destination queue manager remained unchanged. This is because the activities in a loop were designed to facilitate the processing of logical message groups. As of this release, the destination can be changed for each iteration through a loop. When using the Put activity, if you click Batch in the Multi-Message Support area from the Multi-Message tab, the destination can also be changed between messages.
8 Deprecated and Removed Features No features are deprecated or removed in version 8.5.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ.
9 Migration and Compatibility The following are instructions on how to migrate from a previous release to version 8.5.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. You can migrate projects created in a previous release of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ to this release with some caveats. Known Issues with Regards to Migration: Migration of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ projects is only supported when the target platform is TIBCO ActiveMatrix BusinessWorks 6.3.3 or above. Migration of TLS panel for connections is not supported. TLS configurations must be migrated by hand. Migration of message body schemas works but the field may need to be erased and remapped to resolve an error message. For more details about migration, see TIBCO ActiveMatrix BusinessWorks Migration in the TIBCO ActiveMatrix BusinessWorks documentation.
10 Closed Issues The table lists closed issues since the version 8.3.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. Closed in Release Key Summary 8.5.0 BWMQ-530 Connections can go bad in the pool and the application cannot be sure of getting a good one. Added verify connection option to the pool config. Added a new warning message to be issued if an MQ Listener configured with client confirmation does not encounter a confirm before the end of the process. The message id is BWMQ-100503. 8.5.0 BWMQ-529 Put with 'Gen Correlation Id' option set on logical message would create a logical message with different correlation ids. 8.5.0 BWMQ-528 Inquire activity fails on cluster type queues. 8.3.1 BWMQ-411 TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ 8.3.0 was incompatible with TIBCO ActiveMatrix BusinessWorks 6.2.2 and later. 8.3.0 BWMQ-395 The Listener activity did not correctly stop and start in response to engine throttling, and the Listener activity failed to re-establish its connection when the connection was lost. 8.3.0 BWMQ-394 If the MQ activities could not correctly connect to a queue manager, the user name and password you typed in the User Name and Password field of Queue Manager Connection Configuration panel in the WebSphere MQ Connection shared resource were displayed in the console log. 8.3.0 BWMQ-392 If this product was configured with WebSphere MQ Client or Server version 7.1, after you clicked Test Connection in the Queue Manager Connection Configuration panel in the WebSphere MQ Connection shared resource, the result for testing the connection to a queue manager was not correct. 8.3.0 BWMQ-365 When running a process with IBM Server 8.0, the password you typed in the Queue Manager Connection Configuration panel could not be decrypted. 8.3.0 BWMQ-341 When using the Get or Put activity in a loop, if a network or queue manager outage occurred, the activities could not be recovered after the outage was resolved.
11 Closed in Release Key Summary 8.3.0 BWMQ-340 When using the WMQ Connection share resource, 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. You cannot create multiple simultaneous CCDT connection pools, but you can use a CCDT connection pool with restrictions. 8.3.0 BWMQ-339 Errors occurred when the Get activity was in a loop and fetched on different queues. 8.3.0 BWMQ-330 The Get and Put activities could not be made to reconnect to a queue manager after a server or network failed. 8.3.0 BWMQ-294 When using activities in a loop, if a large file could not completely fit into the available memory, you could not create the segmented messages in a loop.
12 Known Issues The table lists known issues in version 8.5.0 of TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. Key BWMQ-513 BWMQ-382 Summary/Workaround Summary: When running a process which involves the MQ activities in the Cloud Foundry environment, if the application properties are used for the MQ activities, the MQ Get and Listener activities might hang and the process does not end. This occurs when using a version 7.x WebSphere MQ client API to access a version 8.x server. Workaround: Select FORCE_MQRFH2 from the Property Control area for the MQ activities. Summary: Some ciphers, which could be used in TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ 8.x running on versions of TIBCO ActiveMatrix BusinessWorks prior to release 6.2.1, are no longer available. This is because the SSLv3 protocol is disabled in the java.security file for TIBCO ActiveMatrix BusinessWorks version 6.2.1. Workaround: You can do the following steps: 1. Navigate to TIBCO_HOME\tibcojre64\version\lib\security. 2. Open the java.security file. 3. Comment out jdk.tls.disabledalgorithms=sslv3, which is located in the last line. Alternatively you can take the steps outlined in IBM WebSphere MQ APAR IV66840. Adding the -Dcom.ibm.mq.cfg.useIBMCipherMappings=false parameter might significantly improve the list of available ciphers if the WebSphere MQ client software is at the correct (recent) level. BWMQ-378 BWMQ-360 BWMQ-157 Summary: This release does not support IBM MQ Server 7.0.x or IBM MQ Client 7.0.x because there is no related OSGi jar file in these products. Workaround: Use IBM MQ Server or IBM MQ Client version 7.5.x or 8.x. Summary: When using remote connection with MQ Server on a Windows platform, the IBM commonservices tracing feature for the activities of the plug-in does not work properly. Workaround: Avoid using the IBM commonservices tracing feature when you use remote connection with MQ Server on a Windows platform. Summary: An error occurs when using the Subscriber activity to receive messages. This is caused by an IBM known issue, and refers to IBM APAR IC92911. Workaround: The IBM WebSphere MQ needs to apply the IBM Select fixes: Fix Pack 7.5.0.5 for WebSphere MQ on Windows Fix Pack 7.5.0.5 for WebSphere MQ on Linux X86-64 For more details about the fix pack, see the IBM site.
13 Key BWMQ-156 Summary/Workaround Summary: An error message, com.ibm.mq.mqexception: MQJE001: Completion Code '2', Reason '2142' is displayed in the Console view, when the MQ activities use the Application Properties field in the General tab to process messages. This is caused by an IBM known issue, and refers to IBM APAR IC92911. Workaround: The IBM WebSphere MQ needs to apply the IBM Select fixes: Fix Pack 7.5.0.5 for WebSphere MQ on Windows Fix Pack 7.5.0.5 for WebSphere MQ on Linux X86-64 For more details about the fix pack, see the IBM site. BWMQ-154 Summary: An inconsequential red body message, MQJE001: Completion Code '2', Reason '2195' is displayed in the Console view, when receiving messages using the Get, Listener, or Subscriber activity. This is caused by an IBM known issue, and refers to IBM APAR IC92911. Workaround: The IBM WebSphere MQ needs to apply the IBM Select fixes: Fix Pack 7.5.0.5 for WebSphere MQ on Windows Fix Pack 7.5.0.5 for WebSphere MQ on Linux X86-64 For more details about the fix pack, see the IBM site.