Securing interactions with the IMS Transaction Manager

You can secure the interactions with IMS Connect and IMS by using the different security features in IMS TM resource adapter.

IMS TM resource adapter security
The Java EE Connector Architecture (JCA) specifies that the application server and the Enterprise Information System (EIS) must collaborate to ensure that only authenticated users are able to access the EIS.
Container-managed EIS signon
With container-managed EIS signon, the security manager in the application server manages the security information for your application.
Component-managed EIS signon
With component-managed EIS signon, your application manages the security information provided to IMS Connect and IMS. In general, your application supplies the security information to be used for EIS signon.
Secure Sockets Layer (SSL) support
SSL provides security for your interactions by securing the TCP/IP connection between the IMS TM resource adapter and IMS Connect.
Changing RACF passwords
When IMS Connect is configured to perform RACF® authentication, you can change RACF password by issuing a password change request to IMS Connect from your Java application.
Securing message retrieval from IMS hold queues
You can specify the user ID and password information to ensure that only authorized users are allowed to retrieve asynchronous output or callout request messages from the IMS hold queue.
Enabling support for distributed network security credentials
IMS TM resource adapter can pass the original, distributed network security credentials, including the network session ID and the network user ID, between Java EE applications and IMS. The network security credentials that are passed by IMS TM resource adapter are written to IMS log records.

Parent topic: Developing an application for use with the IMS TM resource adapter