(forCrossWorlds
Infrastructure versions 4.1.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.6.1 |
CR36128,36438,CR33728,CR37094/JR20054 CR59006/JR20347 |
CR36128: Fixed a
problem in the WebSphere MQ adapter which caused the adpater to fail during
initialization when the connector-specific property ‘InputQueue’
is not configured. CR36438: Fixed a
problem in the WebSphere MQ adapter which enforced case-sensitivity of
meta-object ASI and attribute names. CR33728: Fixed a
problem in the WebSphere MQ adapter which allowed incorrect caching of
conversion properties when non-unique InputFormat/InputQueue values are
configured in the static meta-object attributes. CR37094: Fixed a
problem in the WebSphere MQ adapter which caused the adpater to incorrectly
map the conversion properties to event messages when in-doubts events are
being processed, with multiple input queues configured for the adapter. CR59006:Added support for custom security exits. |
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.6.1 |
WIN;UNIX |
Replace |
/connectors/WebSphereMQ/CWWebSphereMQ.jar |
|
2.6.1 |
WIN;UNIX |
Replace |
/bin/data/App/WebSphereMQConnectorTemplate |
Add or remove the following connector properties:
|
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
Property (Case-Sensitive) |
|
2.6.1 |
WIN;UNIX |
None |
|
CR36128:
To use the feature fixed with this update, configure the adpater without no ‘InputQueue’. Adapter will now initialize successfully with the polling feature disabled.
CR36438:
To use the feature fixed with this update, configure the application-specific information of the configuration meta-object (or the attribute names of the dynamic meta-object) in different cases, and the adpater will now recognize the conversion properties in a case-insensitive fashion.
CR33728:
To use the feature fixed with this update, users can configure non-unique InputFormat/InputQueue values in the static meta-object and the adpater will now be able to correctly identify the conversion properties for each of the business objects during request and event processing.
CR37094:
To use the feature fixed with this update, users can configure multiple input queues and the adapter will now be able to properly map conversion properties to in-doubt events.
CR59006:
To enable the adpater to invoke a custom security exit, configure the new connector-specific property 'SecurityExitClassName' with the fully classified class name of the custom security exit and the connector-specific propety 'SecurityExitInitParam' with the initialization parameters that need to be passed to the security exit constructor.
To make your custom security exit visible to the MQ JMS libraries at runtime, modify the adapter start script to include the custom security exit directory to the jre extension directories. For example, if you are using the adapter with 2.5.0 release of the ADK, you would set the extension directories like,
set JRE_EXT_DIRS=%JRE_EXT_DIRS%;C:\SecExitDir
where <C:\SecExitDir> is the directory where you placed the custom security exit implementation.
© 2003 IBM
Proprietary and Confidential. All Rights Reserved.