IMS Transaction Manager (TM) Resource Adapter Version 15

Last updated: November 2022
  

Contents

• Key features
• Downloads
• Documentation
• List of updates
  • V15.3.8
  • V15.3.7
  • V15.3.6
  • V15.3.5
  • V15.3.4
  • V15.3.3
  • V15.3.2
  • V15.3.1
  • V15.3.0
  • V15.1.10
  • V15.1.9
  • V15.1.8
  • V15.1.7
  • V15.1.6
  • V15.1.5
  • V15.1.4
  • V15.1.3
  • V15.1.2
  • V15.1.1
• Other versions

Key features

IMS TM Resource Adapter Version 15 provides all the features that are available in Version 14 and Version 13 of the resource adapter. Key features include:

• Support for RACF® password phrases from 9 -100 characters
• Support for SSL protocol type specification to be used for socket connections
• Support for IBM® WebSphere® Application Server Version 8 and its resource workload routing function
• Support for network security credential propagation to IBM® IMS
• 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
• Support for both synchronous and asynchronous callout requests from IMS applications to external message-driven beans (MDBs), Enterprise JavaBeans™ (EJB) components, or Web services
• Support for enhanced security when retrieving callout requests or asynchronous output messages from the hold queue (RESUME TPIPE security) through the specification of a user ID that will be authorized by IMS OTMA
• Support for the invocation of IMS applications by using complex data types from distributed platforms
• Business process choreography support of IMS conversations
• Support for integrating IMS MFS services in business processes through IBM Integration Designer and IBM Process Server
• Support for re-establishing any stale connection in a connection pool when the connection encounters a communication failure
• Support for changing RACF passwords from Java™ applications
• Support for returning multiple output messages for commit mode 0 interactions as a single, multi segment message

IMS TM Resource Adapter Version 15 supports IMS Version 15, Version 14, and Version 13, with the integrated IMS Connect function. The IMS Connect function can coexist with earlier or newer versions of IMS. See the Release Planning Guide for the version of IMS that you are using, for IMS Connect coexistence considerations and coexistence APARs.

The runtime environment is the same as the target WebSphere Application Server where the IMS TM resource adapter is deployed.

Downloads

To download the IMS TM resource adapter, go to the IMS TM resource adapter download site.

Documentation

• IMS TM resource adapter information is available in the IBM Knowledge Center.
• IMS TM resource adapter: Supported development environments and runtime environments is available on IBM techdocs

List of updates

The following list details all enhancements that have been delivered through IMS TM resource adapter version 15.

Version 15.3.8 (PH71090)

This version includes the following fixes:

- DFS message DFS555I content was updated, removing input message bytes.

Version 15.3.7 (PH69543)

This version includes the following fixes:

- TMRA now supports the send-only-with-acknowledgment protocol for Java applications implementing the HWSJAVA0 user message exit routine.

- The setPassword IMS Connection Factory method has been enhanced to automatically convert a password exceeding a length of 8 characters to a passphrase using the setPasswordPhrase method.

- Fix for case TS020968898: Upgrade aspectjrt.jar to 1.9.25.1.

Version 15.3.6 (PH68428)

This version includes the following fixes:

- Fixes a bug that prevented secure sockets using SAF keyrings.

- Fix for case TS020587817: Upgraded the icu4j.jar to v77.1.

- Fix for case TS019856955: Enhanced tracing for easier diagnosis of multi-threading issues with ManagedConnections.

Version 15.3.5 (PH68019)

This version includes the following fixes:

- Provides support for Open Telemetry (provider only).

- Added the ability to obtain a program name that made a outbound call.

Version 15.3.4 (PH66649)

This version includes the following fixes:

- Provides support for Jakarta.

- Provides a fix for IIB, now IBM API Connect Enterprise (ACE), to include userId in PING IMS calls.

Version 15.3.3 (PH66059)

This version includes the following fixes:

- TMRA .rar files are now signed.

- Provides the ability to retrieve the userId from the correlator token for Tran Orchestration.

Version 15.3.2

This version includes the following fixes:

- Provides support for Java 21.

Version 15.3.1

This version fixes multiple minor bugs.

Version 15.3.0

This version includes the following fixes:

- Provides support for a new function delivered to OTMA by PH39434: AltPcbOutput support for IMS Connect SENDRECV calls.

- Fix for case TS003362979: We now bundle library javaee-api-8.0.jar along side the .rar file. This .jar file provides JavaEE classes which are needed on the classpath when writing standalone Java applications.

Version 15.1.10 (APAR PH28554)

This version includes the following fixes:

TMRA has been fixed to address the failure of TMRA to reestablish a connection to the datastore after IMS is cycled for Message-Driven Bean applications.

TMRA has been enhanced with a new API method to explicitly ping IMS Connect to verify a connection is valid before attempting a transaction invocation.

TMRA has been fixed to prevent NullPointerExceptions occuring from invocations of the IMSPingService.

• TS003307303 - A NullPointerException occurs in TMRA while invoking the IMSPingService in z/OS Connect EE.

Version 15.1.9 (APAR PH24236)

This version includes the following fixes:

TMRA now correctly handles various connection issues, preventing Null Pointer Exceptions.

• Null Pointer Exceptions occur during error processing for various connection issues from TMRA.

TMRA has been fixed with a performance improvement for clients that create dual authentication TLS sockets using a Keyring.

• TS003288764 - Timeouts occur when many clients invoke services in parallel.

TMRA has been fixed to resolve the following exception.

• TS002525437 - An exception occurs in TMRA when accessing a resource bundle in z/OS Connect EE.

Version 15.1.8 (APAR PH17607)

This version includes the following fixes:

TMRA now correctly reads the bit flag to determine if IRM extensions are supported. This allows a user specified passphrase to be correctly sent down to IMS Connect.

• TMRA did not correctly check a bit flag to see if IRM extensions are supported. This would cause passphrases to not be included in the input OTMA buffer sent down to IMS Connect.

Version 15.1.7 (APAR PH16510)

TMRA now uses the correct single logging call when SSL is enabled, preventing null pointer exceptions.

• When users enable SSL using TMRA, they get a null pointer exception due to TMRA using an incorrect logging method. The incorrect logging method causes a failure to load the logging messages resources, thus causing a null pointer.

Version 15.1.6 (APAR PH08886)

• TMRA throws an error claiming it cannot find the LogMessages bundle due to an incorrect logging method call.

• TMRA unnecessarily ships an additional j2ee.jar in its installation package which, when used, causes a Java class conflict.

Enhancements are added to TMRA to detect the context in which TMRA is running. If TMRA detects it is being used within zCEE, it will prepend "GMP" to the connection id as opposed to "HWS".

• An incorrect connection id prefix is used by TMRA when used in a zCEE context.

• Support for SSL protocol types

• TMRA incorrectly sets the OTMA buffer offset for Transaction Tracking and Network Security bytes when both are enabled.

• TMRA was previously packaged with a .jar file which caused conflicts with JBOSS dependencies.

• The IMSAdapterPoolManager did not terminate the IMSAdapterPool upon catching an InterruptedException, resulting in exceptions being quickly lost without notification to the user.

• Network security credential propagation
  • TMRA now supports network security credential propagation, introduced in IMS 15. A client can specify a distinguished name and realm by using either the IMS interaction spec, or a login-module. The credentials will be propagated  from TMRA, to IMS Connect, and finally to IMS.

Other versions

• IMS TM Resource Adapter V14
• IMS TM Resource Adapter V13
• IMS TM Resource Adapter V12 (out of service)