(forCrossWorlds
Infrastructure versions 4.x and WBIA versions 2.x)
The patch notes contain the following sections:
This patch contains fixes for the following CRs based
on customer-reported cases
|
Available
as of Version |
CR
Number/APAR # |
Description |
|
2.5.2 |
CR35855/JR20009 |
During event
notification, WebSphereMQ fails to copy the MessageID generated by a
different JMS provider to the CorrelationID field. |
|
2.5.1 |
CR27958/JR19496 |
Added support for multiple connection factories in JMS adapter.
|
To
perform an upgrade to this version of the connector:
Add, replace, or remove the following files and directories
as indicated:
|
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
|
2.5.2 |
WIN;UNIX |
Replace |
/connectors/JMS/CWJMS.jar |
|
2.5.1 |
WIN;UNIX |
Replace |
/connectors/JMS/CWJMS.jar |
Add or remove the following connector properties using CSM:
|
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
Property (Case-Sensitive) |
|
2.5.2 |
WIN;UNIX |
None |
|
|
2.5.1 |
WIN;UNIX |
Add |
ArchivalConnectionFactoryName |
CR27958:
To use the feature added with this update, configure the ‘ArchivalConnectionFactoryName’ adapter property with a connection factory name. JMS adapter looks up for a connection factory with this name in the JNDI context and creates a connection from this factory, which would be used for archiving the messages processed by the adapter at the time of polling.
CR35855:
Configure the adapter for topics and queues with two connection factories from different JMS providers. This fixpack provides a workaround to overcome a WebSphereMQ issue which was causing the adapter to fail while copying the MessageID (generated by a different JMS provider) to the CorrelationID header of the WebSphereMQ message.
© 2003 IBM
Proprietary and Confidential. All Rights Reserved.