Container-managed EIS signon

With container-managed EIS signon, the security manager in the application server manages the security information for your application.

When the directive <res-auth>Container</res-auth> is specified in the deployment descriptor of the application, container-managed EIS signon is used. In this case, the application server (the container) provides the security information (user ID and password).

For TCP/IP, the application server passes the security information in the alias to the IMS TM resource adapter. The IMS TM resource adapter passes the security information to IMS Connect for authentication. IMS Connect authenticates the user and passes the security information for signon to IMS. If IMS Connect cannot authenticate the user, a security failure is returned to the IMS TM resource adapter which, in turn, passes an exception back to the application.

With container-managed signon, if your application does pass security information to the IMS TM resource adapter by using the userName, password or groupName properties of the IMSConnectionSpec class, this information is ignored. However, if you pass other information in the IMSConnectionSpec object, such as the client ID with commit mode 0 interactions, this information is used by the IMS TM resource adapter.