Configure the EIM Identity Token Connection Factory

The EIM Identity Token Connection Factory requires eim.jar to be in the classpath for the connection factory, and jt400.jar must be in the classpath for the sample application.

Note: In the Network Deployment environment, configure the eim.jar and jt400.jar files for the WebSphere node where the connection factory is to be configured.

Configure eim.jar and jt400.jar files

1. The eim.jar file is already configured on your iSeries system.  No additional action is required to configure the eim.jar file.
2. For OS/400 V5R2, either copy the jt400.jar file to the classes directory of the WebSphere Application Server profile where the sample application is to be deployed (i.e. $USER_INSTALL_ROOT/classes), or to some other directory. If you choose the latter, then the following additional configuration tasks are required:
   • Grant read and execute authority for jt400.jar to the user profile that the application server runs under
   • Configure a shared library for the jt400.jar file (described later)

   For OS/400 V5R3, JTOpen Version 4.3 (or later) of the jt400.jar file is already on your iSeries system. However, you still need to configure a shared library for the jt400.jar file (described later).

Configure a shared library for the jt400.jar file

Use the WebSphere Administrative Console to create a shared library for the jt400.jar file.

Note: This step is not required if you copied the jt400.jar file to the classes directory of your WebSphere Application Server profile.

Note: In the Network Deployment environment, create the shared library for the WebSphere node where the connection factory is to be configured.

1. Create a shared library
   1. Navigate to Shared Libraries (Environment -> Shared Libraries).
   2. Click Shared Libraries
   3. Click to open Scope
   4. Select the Node where you wish to create the shared library
   5. Click Apply
   6. Click New
   7. Type the name of the shared library in the Name field
   8. Type the full pathname of the jt400.jar file in the Classpath field. For OS/400 v5r3 this is /QIBM/ProdData/HTTP/public/jt400/lib/jt400.jar.
   9. Click OK
2. Create an application class loader for the shared library. This makes the jt400.jar file available to all applications deployed on the application server.
   1. Navigate to the Application Servers page (Servers > Application Servers)
   2. Click the name of the server to which the class loader is to be added
   3. Click the Configuration tab
   4. Click Classloader
   5. Click New
   6. Click OK (let Classloader Mode default to PARENT_FIRST)
   7. Click the Classloader Id for the classloader just created
   8. Click Libraries
   9. Click Add
   10. Select the name of the shared library you created
   11. Click OK
3. Grant java.security.AllPermission to the jt400.jar file in the server.policy file.

   To grant the required permission to the jt400.jar file, carefully edit the server.policy file for your WebSphere server profile ($USER_INSTALL_ROOT/properties/server.policy) to add the following statement:

   grant codeBase "file:path_name/jt400.jar" {
     permission java.security.AllPermission;
   };
   

   Where path_name is the fully qualified path name of the directory containing the jt400.jar file. For OS/400 v5r3 this is /QIBM/ProdData/HTTP/public/jt400/lib/jt400.jar.
4. Save your configuration changes
   1. Navigate to Save Changes to Master Repository (System administration > Save Changes to Master Repository)
   2. Click Save