Version 12 adds the support for WebSphere® Application
Server Version 8
and its resource workload routing function, the support for multiple
data stores per IMS™ activation
specification for callout messages, and takes advantage of various
enhancements in IMS.
- Support for WebSphere Application
Server Version
8 and its resource workload routing function
- WebSphere Application
Server Version
8 introduces a new resource workload routing function that offers
data source and connection factory failover and subsequent failback
from a predefined alternate or backup resource. This function enables
applications to easily recover from resource outages, such as database
failures, without having to embed alternate resource and configuration
information.
- You can specify two connection factories for the IMS TM
resource adapter, and
then specify the second connection factory to be the alternate resource
for the first connection factory.
- Support for multiple data stores per IMS activation
specification for callout messages
- This enhancement enables a single message-driven bean (MDB) to
pull callout messages from more than one IMS data
store. For a shared-queues environment, this enhancement removes the
requirement to duplicate the MDB application to connect to each IMS member in the shared queue.
- Data store connection failure recovery for callout messages
- When the backend IMS is not
available, in addition to the attempt to reconnect to IMS Connect, he resource adapter will also attempt
to reconnect to the IMS data
store. A new -1 value is added to the IMSActivationSpec retryLimit
property to support indefinite retry for connection to IMS Connect and the IMS data
store. When the retry is successful and the connection is restored,
informational messages are provided to indicate the successful re-connection.
- Support for IMS V12 OTMA
DFS2082 messages for commit-then-send CM0 transactions
- With this IMS V12 enhancement,
for CM0 transactions, if the IMS application
does not reply to the IOPCB or complete a message switch to another
transaction, OTMA issues a DFS2082 message to the client to indicate
the transaction terminated with no reply.
- This enhancement enables you to convert send-then-commit (CM1)
transactions into CM0 transactions without having to modify your applications.
- Support for IMS Version 12 RACF® return codes
- In IMS V12, if a RACF security failure occurs, IMS Connect includes a 2-byte return
code from the RACF RACROUTE
REQUEST=VERIFY command. This version of the IMS TM
resource adapter is enhanced
to take advantage of the enhancement so the RACF security failure reason code is available
to IMS TM
resource adapter to
assist troubleshooting.