Configuring WebSphere Application Server connection pooling for IBM Content Manager Enterprise Edition

To improve the security and scalability of the IBM® Content Navigator web client, configure WebSphere® Application Server connection pooling on the servers in your IBM Content Navigator environment.

To enable WebSphere Application Server connection pooling:

1. Modify the cmbpool.ini file to use indirect lookup by adding the values:
   • JavaPool=DKPoolWAS
   • JDBCPrefix=jdbc/

   By default, the cmbpool.ini file is in the same directory that the cmbicmsrvs.ini and cmbicmenv.ini files are located.

   The cmbicmsrvs.ini and cmbicmenv.ini files are required files. They must exist in the same directory as the cmbpool.ini file. Do not remove or rename these files.
2. Set the JDBC driver path in your WebSphere Application Server administrative console:
   1. Navigate to Environment > WebSphere variables.
   2. From Scope, select Node=YourSystemNode.
   3. From the list of resources, select the JDBC driver path for your database type.
   4. Set the value for the JDBC driver path to the location of the JDBC JAR files on your system. Then, save your changes to the master configuration.
3. Create a JDBC resource reference for your IBM Content Manager library server in your WebSphere Application Server administrative console:
   1. Navigate to Resources > JDBC > JDBC Provider and click New.
   2. From Scope, select Node=YourSystemNode.
   3. Set the database and provider types.
   4. Set the implementation type to Connection pool data source.
   5. Verify that the class path is correct. Then, save your changes to the master configuration.
4. Create a data source in your WebSphere Application Server administrative console:
   1. Navigate to Resources > JDBC > JDBC Provider and select the reference that you created.
   2. Click Data sources. Then, click New.
   3. In the JNDI name field, enter jdbc/ICMNLSDB where ICMNLSDB is the library server database name, then click OK. This value is case-sensitive.
   4. In the Database name field, enter the library server database name. This value is case-sensitive.
   5. In the Server name field, enter the host name of the database. Click Next. Then, save your changes to the master configuration.
5. Edit the JAAS – J2C authentication data properties in the WebSphere Application Server administrative console:
   1. Select the data source that you created.
   2. Under Related Items, click JAAS – J2C authentication data. Then, click New.
   3. In the Alias field, enter a value, such as nodename/userID.
   4. In the User ID field, enter ICMCONCT.
   5. In the Password field, enter the password of the ICMCONCT user. Then, click OK. This password was specified during the IBM Content Manager installation.
   Tip: You can create a temporary password with your icmconct user ID. Do not manually edit the password to generate the temporary password. You must generate the temporary password by generating the password for the icmconct user ID in the cmbicmenv.ini file in IBM Content Navigator.
6. Select the alias in Component-managed authentication alias and in Container-managed authentication alias. Then, save your changes to the master configuration.