(iseries)

Manually configuring the connection factory

The following steps help you manually configure the connection factory.

Configure the eim.jar and jt400.jar files.

After you configure the eim.jar and jt400.jar files, we can choose to manually or automatically configure the connection factory. If we choose to automatically configure the connection factory, see Automatically configuring the connection factory for more information. To manually configure the Java 2 Connector (J2C) authentication data, the resource adapter, and the connection factory.

1. Configure the Java 2 Connector (J2C) authentication data.

   1. In the WAS administrative console, click Security >Global security.

   2. Under Java Authentication and Authorization Service, click J2C Authentication data > New

   3. Specify the values for each of the required fields. The User ID (cn=administrator for example) and Password values are those used by the connection factory to bind to the LDAP server containing the Enterprise Identity Mapping (EIM) data.

   4. Click OK.

2. Configure the resource adapter.

   1. In the WAS administrative console, click Resources > Resource adapters > Resource adapters.

   2. Select the node where to install the resource adapter.

   3. Click Apply.

   4. Click Install RAR.

   5. Select Local path if we have a drive that is mapped to the iSeries server. Otherwise, select Server path.

   6. Specify the path name or browse to the path name for the idTokenRA.JCA15.rar RAR file.

   7. Click Next.

   8. Specify the name of the adapter in the Name field. For example, specify identitytoken.

   9. Click OK.

3. Configure the connection factory.

   1. On the Resource Adapters panel, click the name of your newly created resource adapter.

   2. Under Additional Properties, click J2C connection factories > New.

   3. Specify the name of the connection factory in the Name field. For example, specify idtokenconnection.

   4. Specify eis/IdentityToken in the 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.

   5. In the Component-managed authentication alias and Container-managed authentication alias fields, select the authentication data alias created earlier.

   6. In the Mapping-configuration alias field, select DefaultPrincipalMapping.

   7. Click Apply.

   8. 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...

      1. Click the name of the custom property.

      2. Type the value of the property in the Value field.

      3. Click OK.

4. Save the configuration changes.

   1. Expand System administration and click Save Changes to Master Repository.

   2. Click Save.

Results

You have manually configured the connection factory.

What to do next

After saving the configuration changes, we can deploy the EIM sample application into the WAS environment. The source code files used in the sample application can be used as a model for creating our own applications. See Deploy the Enterprise Identity Mapping sample application for more information.

Related tasks

Configure single sign-on capability with Enterprise Identity Mapping