The following steps help you manually configure the connection
factory.
Before you begin
Configure the
eim.jar and
jt400.jar files.
About this task
After you configure the
eim.jar and
jt400.jar files,
you can choose to manually or automatically configure the connection
factory. If you choose to automatically configure the connection factory,
see
Automatically configuring the connection factory for
more information. Perform the following steps to manually configure
the Java 2 Connector (J2C) authentication data,
the resource adapter, and the connection factory.
Procedure
- Configure the Java 2
Connector (J2C) authentication data.
- In the WebSphere® Application Server
administrative console, click Security >Global security.
- Under Java Authentication
and Authorization Service, click J2C Authentication data > New
- Specify the values for each of the required fields. The User ID (cn=administrator for example) and Password values
are those that are used by the connection factory to bind to the Lightweight
Directory Access Protocol (LDAP) server that contains your Enterprise
Identity Mapping (EIM) data.
- Click OK.
- Configure the resource adapter.
- In the WebSphere Application Server
administrative console, click Resources > Resource adapters >
Resource adapters.
- Select the node where you want to install the resource
adapter.
- Click Apply.
- Click Install RAR.
- Select Local path if you have a drive that is
mapped to your iSeries server. Otherwise, select Server
path.
- Specify the path name or browse to the path name for
the idTokenRA.JCA15.rar RAR file.
- Click Next.
- Specify the name of your adapter in the Name field. For example, specify identitytoken.
- Click OK.
- Configure the connection factory.
- On the Resource Adapters panel, click the name of your
newly created resource adapter.
- Under Additional Properties, click J2C connection
factories > New.
- Specify the name of your connection factory in the Name
field. For example, specify idtokenconnection.
- Specify eis/IdentityToken in the Java Naming and Directory Interface (JNDI) name
field. This name must match the JNDI name used during the
deployment of the sample application. The name is used for reference
binding.
- In the Component-managed authentication alias and Container-managed
authentication alias fields, select the authentication data alias
that you created earlier.
- In the Mapping-configuration alias field, select DefaultPrincipalMapping.
- Click Apply.
- Under Additional Properties, click Custom properties. The custom properties are used by the connection factory to
communicate with the EIM controller. View the custom property descriptions,
and determine whether the properties are required or optional. For
more information, see Enterprise Identity Mapping identity token connection factory parameters.
To
set a property value, complete the following steps:
- Click the name of the custom property.
- Type the value of the property in the Value field.
- Click OK.
- Save your configuration changes.
- Expand System administration and click Save
Changes to Master Repository.
- Click Save.
Results
You have manually configured the connection factory.
What to do next
After saving your configuration changes, you can deploy the
EIM sample application into the WebSphere Application
Server environment. The source code files that are used in the sample
application can be used as a model for creating your own applications.
See
Deploying the Enterprise Identity Mapping sample application for
more information.