+ All Categories
Home > Documents > TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ...

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ...

Date post: 14-Jul-2020
Category:
Upload: others
View: 22 times
Download: 0 times
Share this document with a friend
26
TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ Release Notes Software Release 7.3.0 November 2013 Two-Second Advantage ®
Transcript
Page 1: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ

Release NotesSoftware Release 7.3.0November 2013

Two-Second Advantage®

Page 2: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

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, TIBCO ActiveMatrix BusinessWorks Plug-in for Data Conversion, TIBCO ActiveMatrix BusinessWorks XA Transaction Manager, TIBCO Designer, 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-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

Page 3: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Documentation . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viThird-Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 7.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Release 7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 4: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

iv | Contents

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 5: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

| v

Preface

TIBCO ActiveMatrix BusinessWorks™ Plug-in for WebSphere MQ, referred to as the Plug-in in this manual, allows the user to 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

Page 6: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

vi | Related Documentation

Related Documentation

This section lists documentation resources you may find useful.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ DocumentationThe 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 DocumentationYou may 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 that enables 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 ActiveMatrix BusinessWorks™ XA Transaction Manager software: This product is required if the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ activities are run in a TIBCO ActiveMatrix BusinessWorks XA Transaction group.

• TIBCO Designer™ software: TIBCO Designer is an intuitive graphical user interface for design-time configuration of TIBCO applications. Online help is available for TIBCO Designer palettes.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 7: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Preface | vii

• 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 Hawk® software: This product is for monitoring and managing distributed applications and systems throughout the enterprise.

• TIBCO Rendezvous® software: This product uses messages to enable distributed application programs to communicate across a wide variety of hardware platforms and programming languages.

• TIBCO Runtime Agent™: This product is a bundle of TIBCO software and third-party software that is required to run many TIBCO applications such as TIBCO ActiveMatrix BusinessWorks, TIBCO Adapters, and so on.

Third-Party DocumentationTIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ relates to other products documentation which you might find helpful:

• WebSphere MQ description and documentation, which may be found at:

http://www-01.ibm.com/software/integration/wmq/

• WebSphere MQ for z/OS description and documentation, which may be found at:

http://www-01.ibm.com/software/integration/wmq/zos/

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 8: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

viii | Typographical Conventions

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

ENV_NAME

TIBCO_HOME

TIB_BWPLUGINMQ_HOME

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.

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.

The product is installed into a directory within a TIBCO_HOME.

The Plug-in Installation installs into a directory within a TIBCO_HOME. This directory is referenced in documentation as TIB_BWPLUGINMQ_HOME. The default value depends on the operating system. For example on Windows system, the default value is C:\tibco\bw\plugins\mq .

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.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 9: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Preface | ix

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]

italic font Italic font is used in the following ways:

• 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 combinations 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 1 General Typographical Conventions (Cont’d)

Convention Use

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 10: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

x | Typographical Conventions

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 para1 | param2 | param3

{ } 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

Page 11: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Preface | xi

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, 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 http://www.tibcommunity.com.

How to Access All TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, please 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

Page 12: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

xii | Connecting with TIBCO Resources

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 13: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, 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 7

• Deprecated and Removed Features, page 8

• Migration and Compatibility, page 9

• Closed Issues, page 10

• Known Issues, page 13

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 14: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

2 | Release Notes

New Features

This section lists features added since the 7.0.0 release of this product.

Release 7.3The following are new features in this release:

• Improved Password Field The Password field in the Configuration tab of the WebSphere MQ Connection shared resource now can be defined by using Global Variables.

• Added AlternateUserid Item The alternateUserid item has been added to the Put/Get/Publish activity. The specified username overrides the Userid for that operation only.

• The Modified Listener Start Activity When explicit client confirmation is requested, each instance of the Listener activity gets exactly one message and dispatches a process context which starts an activity. After that, the Listener activity waits for confirmation of the message before getting the next one.

Instances is a new item in the configuration tab of the Listener activity. Its number controls the number of threads used to poll the queue.

• Improved Designer Behavior The issues of error messages and Test buttons which were occasionally misleading are fixed when the plug-in works with Clustered Queues. Where ambiguity exists it is now documented in the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s Guide.

• Added Platform Support This release adds new platform support for TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ:

— Red Hat Enterprise Linux 5.x

• Available WaitInterval Item The waitInterval item in the Input tab of the Get activity is now available and can be dynamically mapped during the runtime. This only occurs when the Wait Forever check box in the configuration tab is cleared.

• Added Connection Support for Version 6.x This release supports connections to WebSphere MQ 6.x queue managers in accordance with IBM’s statement of support for such connections. In addition to the items mentioned in this (and any other) IBM statement: http://www-01.ibm.com/support/docview.wss?uid=swg21312967

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 15: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

New Features | 3

the plug-in does not support the following operations when connected to a Queue Manager 6.x:

— Application Properties

— Pub/Sub Operations of any kind

— Locally bound connections to WebSphere MQ Server 6.x

• Batch Mode support for messaging activities This release adds the Batch Mode item to the Get/Put/Listener activity. This allows the process to put as many messages as the input schema has been configured to contain and the Get/Listener activity can be configured to process an arbitrary number of messages from 2 to 100. The input and output schemas have been adjusted to allow multiples of the normal input and output XML nodes. In this way the entire batch of messages is processed as a single unit of work and committed by a single commit action, reducing the impact of network latency on the application.

Release 7.2The following are new features in this release:

• Supporting Multi-instance Queue Managers The connection resource in the Plug-in's Connection Table has been enhanced to support using WebSphere MQ Client Channel Definition Tables (CCDTs) for making connections to a queue manager or multi-instance queue manager. All that is required is a working CCDT that can be accessed using the HTTP, FTP, or FILE protocols. CCDTs are the only supported way to connect to a multi-instance queue manager.

See the IBM documentation for a description of CCDTs and how they are to be used.

Refer to IBM WebSphere MQ documentation regarding High Availability and multi-instance queue managers for configuration and related information.

• New Application Context Fields Many new fields related to the application context are exposed in the Input and Output tab for all activities. The addition of these fields is facilitated by the destination and message option MQOO_SET_ALL_CONTEXT. This is now set for all Put and Publish activities and is not configurable.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 16: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

4 | Release Notes

Release 7.1The following are new features in this release:

• Transport Layer Security Connection Support Transport Layer Security (TLS) is equivalent to SSL V3. The Plug-in now supports TLS connections between MQ clients and the MQ Queue Manager. Queue managers can be configured to support a TLS connection based on the credentials contained in a specially prepared key store. The Plug-in can connect to these queue managers by either using a Java key store, or discrete files composing the identity and trust relationships necessary to make the connection.

For more information, see Creating Secure Connections to the Queue Manager in the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s Guide.

• Pooled Connections Connections are now cached at the job level and reused by processes which share the same connection resource. This minimizes the number of connections created and destroyed by a given job. Additionally, connections can be pooled for rapid access based on parameters supplied in the new Pooling tab of the connection resource. Connections acquired from the pool are maintained in a hot standby mode and are therefore faster to obtain and release.

See the section in the Pooling Tab in the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s Guide for more information.

• Additional Report Formats Report messages have been expanded and enhanced. Reports can now be triggered from exception and expiry events. For more information, see the field description for Report Confirmation in the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s Guide.

• Schema Field Priority The message property priority is now supported using the input schema for all activities which have an input schema. The normal first-in, first-out (fifo) behavior of queues can be modified by biasing messages based on the value of the priority field.

• Important New Fields

— destqmgr This field follows the destination field in the input and output schemas. It is used to specify a remote queue manager for the specified destination. To use remote queue managers, the appropriate send and receive channels must be configured between the queue managers involved.

— replyToQmgrName This field has been added to schemas featuring a relyToQueueName field, and specifies the remote queue manager to which the reply message should be routed. As with the destqmgr field, send and receive channels must be configured between the queue managers involved for this to work.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 17: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

New Features | 5

• Sync-Point Control The Queue Listener process starter can now be configured to explicitly acknowledge the arrival of a message. This allows the message to be conditionally accepted based on conditions detected in the process. See the section on the WebSphere MQ Listener Activity in the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User's Guide for more information.

• Topic Activities Support for Topic Publisher and Subscriber activities has been added. Messages can be published and consumed from either dynamic or administratively defined topics and subscriptions. Subscriptions are expected to be of the "managed" type. Consult the WebSphere MQ documentation for a description of managed vs unmanaged subscriptions.

• Bi-directional Message Crossover The Plug-in activities now facilitate bi-directional message crossover between WebSphere MQ and TIBCO Enterprise Message ServiceTM. This is done by mapping messages between the two transports using explicit confirmation of the received message.

Release 7.0This is the first release of the TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ. The following are the features in Release 7.0.0.

• WebSphere MQ 7.x and upward releases.

• A Connection resource that contains all parameters relevant to establishing a connection, including automatic re-connectivity and re-delivery.

• A WebSphere MQ Get activity that gets a message from a queue and returns the message as a bytes array.

• A WebSphere MQ Put that puts message to a queue. Payloads are binary blobs.

• A WebSphere MQ Listener that gets a message from a queue as a process starter. Each process started may access the message read as a bytes array.

• Handles the following message types:

— Datagram

— Request

— Reply

— Report (COA and COD types only)

• Filters on correlation and message identifiers.

• XA transactions for get and put activities.

• Group messages and segmented message groups.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 18: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

6 | Release Notes

• Dynamic queues.

• WebSphere MQ message properties.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 19: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Changes in Functionality | 7

Changes in Functionality

This section lists changes in functionality since the 7.0.0 release of this product.

Release 7.3The following are changes in functionality in this release:

• Connections The Plug-in supports connections to WebSphere MQ 6.x servers to the same extent that IBM supports connections between the 7.x client and 6.x servers. See the IBM documentation for the version of softwares installed to determine if the features you wish to use are supported. The following Plug-in items are unsupported for Queue Manager 6.x connections:

— Pub/Sub Applications

— Application Properties

— Locally bound connections to WebSphere MQ Server 6.x

Release 7.2The following are changes in functionality in this release:

• The Put Activity The Put operations now use the MQOO_SET_ALL_CONTEXT option to provide access to most of the message application context fields. This change is completely transparent to existing applications.

Release 7.1There are no changes in functionality in this release.

Release 7.0There are no changes in functionality in this release.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 20: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

8 | 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.3No features are deprecated or removed in this release.

Release 7.2No features are deprecated or removed in this release.

Release 7.1No features are deprecated or removed in this release.

Release 7.0

Deprecated Features

The following features are deprecated in this release:

• Removed Schema Fields The reportQueueName field has been removed from the Put activity input schema. This field is functionally equivalent to the Reply To Queue field which is already present in all input schemas.

Removed Features

No features are removed in this release.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 21: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Migration and Compatibility | 9

Migration and Compatibility

This section explains how to migrate from a previous release to this release.

Release 7.3There are no absolute migration procedures or compatibility issues in this release. However, if an application is configured to use a single instance of the Queue Listener Start activity to consume large numbers of messages using the explicit client confirmation, it may now be necessary to increase the number of instances for these activities in order to achieve the same level of throughput as is observed in the Release 7.2.

See TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ User’s Guide for the Listener activity to obtain more information.

Release 7.2There are no migration procedures or compatibility issues in this release.

Release 7.1There are no migration procedures or compatibility issues in this release.

Release 7.0There are no migration procedures or compatibility issues in this release.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 22: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

10 | Release Notes

Closed Issues

The table in this section list issues that were closed in the named releases.

Closed in Release Key Summary

7.3.0 BWMQ-112 The Password field in the configuration tab of the WebSphere MQ Connection shared resource could not be defined by using Global Variables.

7.3.0 BWMQ-115 The Input tab of the activities (Put/Get/Publish) did not include the alternateUserId item.

7.3.0 BWMQ-117 Previously, the results of the EW0M49 project suggested that a large amount of memory was consumed and the throughtput capability was poor for the Listener Start activity.

The Listener Start activity now supports multiple threads and is completely synchronous when explicit client confirmation is required. The memory consumption and the throughtput capability issues have been fixed.

7.3.0 BWMQ-120 When the Listener/Subscriber activity lost its connection to the queue manager, log messages were not displayed. Also, after the MQ channel was restarted, the Listener/Subscriber activity did not reconnect successfully.

7.3.0 BWMQ-125 Fixed an error in the Test button that resulted in the error message MQRC_SELECTOR_NOT_FOR_TYPE , if a queue is defined as a Cluster Queue and existed in the Local or Remote MQ Server.

7.3.0 BWMQ-126 When the Get activity received messages that already existed in a cluster queue of one Queue Manager from a queue of another Queue Manager, the following error messages appeared:

MQRC_UNKNOWN_OBJECT_NAME

7.3.0 BWMQ-127 TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ added the platform support for Red Hat Enterprise Linux 5.x.

7.3.0 BWMQ-128 If the Listener Start activity used explicit confirmation, the activity consumed a large amount of memory and connection resources, and ran for a long time.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 23: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Closed Issues | 11

7.3.0 BWMQ-130 The waitInterval item in the Input tab of the Get activity was not available, making it impossible to dynamically adjust the Wait Timeout field in the Configuration tab.

7.3.0 BWMQ-132 Fixed an error in the Test button that resulted in the error message Administratively defined portion of the topic "XXX" doen

not exist , if a topic was defined as a Cluster Topic and existed in the Local or Remote MQ Server.

Note: This was an update in documentation only.

7.3.0 BWMQ-134 When the Get/Listener activity received messages already existing in a cluster queue of one Queue Manager from a queue of another Queue Manager, the Cluster Queue type was recognized by clicking the Test button and the error message MQRC_UNKNOWN_OBJECT_NAME was generated during the runtime. These issues were fixed.

Note: This was an update in documentation only.

7.3.0 BWMQ-138 Fixed an issue that TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ did not support the connection between the MQ Client 7.x and MQ Server 6.x.

7.2.0 BWMQ-103 Fixed an error in the Test button that resulted in the error MQRC_SELECTOR_NOT_FOR_TYPE when an alias queue was selected for Put/Get/Listener.

7.2.0 BWMQ-98 Previously, Get, Listener, and Subscribe activities on z/OS would fail for queues that were defined without being indexed by group ID. This occurred because the plug-in specified group sequencing on gets to all platforms.

The platform is now dynamically detected, and the group sequencing option is turned off for z/OS queue managers. As a result, if a grouped message is retrieved from a z/OS queue manager which is not correctly indexed, the portions of the group may be concatenated out of order. It is the application designer's responsibility to ensure that the queue is correctly indexed.

Closed in Release Key Summary

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 24: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

12 | Release Notes

7.2.0 BWMQ-89 Previously, the MQ Message descriptor (MQMD) fields were not exposed in the Plug-in. The fields accountingToken , applicationIdData , applicationOriginData , putApplicationType , putApplicationName , and userId are now available on the input schemas for put and publish operations, as well as all output schemas.

7.2.0 BWMQ-88 Fixed a problem that prevented the mqproperties field replyToQmgrName setting for the Put activity from overwriting the Queue Manager name.

7.2.0 BWMQ-86 The replytoqmgrname field was not always correctly provided in the output schema of the topic subscriber. This has been fixed.

7.1.0 BWMQ-38 When connecting to a remote queue manager, put activities that used a loop occasionally failed with an out of memory condition. This behavior was experienced when the put buffers a large number of messages in a loop. This has been fixed.

Closed in Release Key Summary

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 25: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

Known Issues | 13

Known Issues

The table in this section lists known issues in this release.

Key Summary/Workaround

BWMQ-53 Summary When dealing with grouped messages, the get activity is sometimes unable to create a job after putting a large message. This problem is seen when groups contain approximately 5000 (or more) smaller messages.

This issue is currently under investigation.

Workaround Increase the Maximum Segment Size for large messages in order to decrease the number of smaller messages and the overall number of messages in the group.

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes

Page 26: TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ ...€¦ · for WebSphere MQ documentation set: † TIBCO ActiveMatrix Busine ssWorks Plug-in for WebSphere MQ Installation

14 | Release Notes

TIBCO ActiveMatrix BusinessWorks Plug-in for WebSphere MQ Release Notes


Recommended