(for WebSphere Business
Integration Adapter Framework versions 2.6.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.7.1 |
CR59006/JR20347 CR44680/JR20745 |
CR59006: Added
support for custom security exits. CR44680: WebSphere MQ adapter could not restart while using the
RestartRetry configuration.
|
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.7.1 |
WIN;UNIX |
Replace |
/connectors/WebSphereMQ/CWWebSphereMQ.jar /bin/data/App/WebSphereMQConnectorTemplate |
Add or remove the following connector properties:
|
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
Property (Case-Sensitive) |
|
2.7.1 |
WIN;UNIX |
None |
|
CR44680:
To use the feature fixed with this update, configure the adapter with the restart-retry feature of the ADK.
CR59006:
To enable the adapter 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 property '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, you would use the following setting in the adapter start script:
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.