(for WebSphere
Business Integration Framework versions 2.6.x)
The patch notes contain the following sections:
This Fix pack contains fixes for the
following CRs based on
customer-reported cases
|
Available as of Version |
CR Number/APAR # |
Description |
| 2.8.1 | CR72202/JR 22448 | Adapter will accept
(optional)id/password to connect to JMS Provider. If id/password is provided, same will be used for authentication, else adapter will assume the system defaults. |
| 2.8.1 | CR72274/JR 22449 | If a connection already has
client ID associated with it and attempt is made to set client ID
again, an exception is thrown. Checks are implemented to avoid this
situation. |
| 2.8.1 | CR71128(linked to CR60707)/JR21381 | Fixed a problem in the WebSphere
MQ adapter so that the adapter does not trim spaces from the
correlationID in the MQMD header as this was causing incorrect
correlation id problem in case of binary. |
| 2.8.1 | CR67384/JR22404 |
As per documentation, adapter
should trace a message at trace level 1 when it detects event in the
Input Destination and not for empty Input Destination. The code is
fixed for the same. |
| 2.8.1 | CR67516//JR22407 |
During adapter processing, it
was observed that it accepts only CRUD, Exists and RetrieveByContent as
verbs. This CR fixes the issue by allowing other custom verbs. |
| 2.8.1 | CR78700/JR22427 | If the JNDI provider becomes
unavailable during adapter run, adapter encountered exceptions but did not terminate and restart (based on retries setting). The fix ensures adapter terminate and restart as appropriate. |
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 %INSTALLEDDIR) |
| 2.8.1 | WIN;UNIX | Replace | /connectors/JMS/CWJMS.jar |
| 2.8.1 | WIN;UNIX | Replace | ./bin/Data/App/JMSConnectorTemplate |
Add or remove the following connector properties:
|
For Adapter Version |
Platform [WIN; UNIX] |
Add / Replace / Remove |
Property (Case-Sensitive) |
| 2.8.1 | WIN;UNIX | Add |
ApplicationUserName, ApplicationPassword |
CR72202:
This TestFix allows the user to supply Id and
Password
to establish JMS connection. If connector configuration supplies values
for
ApplicationUserName and ApplicationPassword, same are used to establish
connection to the JMS provider. If no value is supplied, the connection
is
established with default user identity.The connector configuration
needs two
new optional properties - ApplicationUserName and ApplicationPassword.
CR72274:
This TestFix checks if the clientID is set on the Connection. If it
is already set, it takes no action, else sets clientID on the
connection. This Fix is introduced to eliminate the cause of JMS
IllegalStateException due to attempting setClientID() on the connection
which has existing clientID.
CR71128(Linked to CR60707):
To use the feature fixed with the update, users
can send a message to the adapter with correlation id in the MQMD
header set to n spaces. The adapter will now successfully process this
message.
CR67384:
Check connector trace file messages by setting trace level 1 in
connector configuration. Check with A) some events available in Input
Destination, as well as, with B)
No events available in Input Destination.
CR78700:
This Fix fixes the issue of connector behavior
when the JNDI provider becomes
unavailable during runtime. If the JNDI provider terminates after the
connector
has started, the connector encounters error when trying to connect to a
destination. In this case it errors out and terminates.
CR67516:
This Fix allows the user to use custom verbs (in
addition to CRUD, Exists and RetrieveByContent) in Business Objects
© 2003 IBM Proprietary
and Confidential. All
Rights Reserved.