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.
To specify component-managed EIS signon for your
application, type
the value application for the <res-auth>
element in the resource reference of the deployment descriptor of
your application.
Your application (the component) provides
the security information
(user ID, password, and optional group name) that is used for EIS
signon:
- If your application uses the J2EE Connector Architecture
Common
Client Interface (CCI), it performs component-managed EIS signon by
using the following methods:
- IMSConnectionSpec.setUserName()
- IMSConnectionSpec.setPassword()
- IMSConnectionSpec.setGroupName()
These methods populate an IMSConnectionSpec object with security
information. After the application establishes a connection to IMS,
it passes the IMSConnectionSpec object as a parameter of the IMSConnectionFactory.getConnection method.
The IMS TM
resource adapter passes
this security information to IMS Connect for use in signing on
(authentication and authorization) to IMS.
- If your application is generated by a Rational® or WebSphere® development environment, the
security information is passed as application input data. To pass
the security information as input data you must expose the userName,
password, and groupName properties of the IMSConnectionSpec class.
If your application does not use one of the methods to
provide
security information, WebSphere Application
Server obtains the
security information from the J2C connection factory custom properties.
Tip: If you specified a component-managed JAAS alias when
you set up your connection factory, the user ID and password in the
alias override the userName and password values in the connection
factory custom properties during the startup of WebSphere Application
Server.