New features in IMS TM Resource Adapter Version 11

In addition to all the features in IMS™ TM Resource Adapter Version 10, Version 11 adds the support to eliminate duplicate client ID errors during high system load when multiple instances of distributed WebSphere® Application Server connect to IMS Connect on the same port.
Begin figure description. IMS TM Resource Adapter Version 11 Connection failure recovery for callout messages
The resource adapter will attempt to reconnect to IMS if the backend IMS data store is not available. A new -1 value is added to the IMSActivationSpec retryLimit property to support indefinite retry for connection. When the retry is successful and the connection is restored, informational messages are provided to indicate the successful re-connection.
Begin figure description. IMS TM Resource Adapter Version 11.2 and later versions only. End figure description. Support for a transaction to expire after the execution times out
The OTMA transaction expiration function enables a client application to instruct IMS Connect to indicate to IMS OTMA that, when the execution times out, the transaction expires and OTMA should discard or dequeue the transaction.
Prior to this OTMA enhancement, when IMS does not have the resources to process a transaction in the allotted time frame as specified in the executionTimeout property, the transaction cannot be cancelled.
To support this OTMA enhancement, a new transExpiration property is added to the IMSInteractionSpec class IMS TM Resource Adapter Version 11.2 and later to instruct OTMA to discard or dequeue the transaction when the execution timeout value is reached.
This support enables an IMS TM resource adapter client application to take advantage of the transaction expiration enhancement in OTMA to relieve OTMA from having to process unnecessary messages from the IMS TM resource adapter.
Elimination of duplicate client ID errors during high system load when multiple instances of distributed WebSphere Application Server connect to IMS Connect on the same port
Previously, if the IMS TM resource adapter ran in multiple instances of distributed WebSphere Application Server, each instance of the server must use a different IMS Connect port to avoid the possibility of duplicate client IDs, which would cause an error. In IMS TM Resource Adapter Version 11, if an incoming connection request from the IMS TM resource adapter uses an ID that is a duplicate of an ID already being used, IMS Connect automatically generates a unique client ID for the incoming IMS TM resource adapter session without sending an error to the client application.

Feedback