Configuring WebSphere Application Server connection pooling for use with a client

WebSphere Application Server connection pooling enables a data store to scale to an indefinite number of users. Connection pooling also improves client performance by reducing logon time and memory usage.

About this task

You must manually configure connection pooling.

The Content Manager Enterprise Edition Version 8 connectors use the WebSphere Application Server JDBC connection pooling. If the two connectors share the same database, they share the same WebSphere Application Server database connection pool. If you choose a different database when installing the two connectors, the connectors use different WebSphere Application Server database connection pools.

Without connection pooling, each database handles its own database connection, which can limit the scalability of an application. When you implement connection pooling, each database can share a database connection from the WebSphere Application Server JDBC connection pool. This benefits performance by reducing the quantity of resources that are required for a set of databases.

You can use either a direct or indirect Java™ Naming and Directory Interface (JNDI) name to look up the data source. Indirect lookup is recommended for the following reasons:

Indirect lookup enables more control over connection management properties such as authentication and sharing scope that are specified in a resource reference, and allows you to select which J2C connection factory to use.
Direct lookup has been deprecated in WebSphere Application Server.

To configure WebSphere Application Server connection pooling:

Procedure

Modify the cmbpool.ini file to enable WebSphere Application Server connection pooling.
By default, this file is in the /home/ibmcmadm/cmgmt/connectors directory for AIX® or Linux®; or in the IBMCMROOT\cmgmt\connectors directory for Windows™; or in the IBMCMROOT/cmgmt/connectors directory for z/OS®.
- To use indirect lookup, modify the cmbpool.ini file with the following values:
```
JavaPool=DKPoolWAS
JDBCPrefix=java:comp/env/jdbc/
```
If you set JavaPool=DKPoolWAS but do not set a value for JDBCPrefix, direct lookup is used by default.
Add the following statement to the cmbicmsrvs.ini file:
- ICMJNDIREF=CM_LSDatasource_01
Set up a JNDI resource reference for your library server:
1. In the WebSphere Application Server administrative console, click Applications > Enterprise Applications > client_name > Resource references, and select a row in the table of resource references. The row you select would be consistent with the ICMJNDIREF data source specified.
2. In the JNDI Name column, select a JNDI name for the data source that is the mapping target of the resource reference.
Note that step 3 is most of the time already completed by the client deployment.
Edit the properties of your data source:
1. In the WebSphere Application Server administrative console, click Resources > JDBC > Data sources, and select your data source specified.
2. Enter the Scope, Provider, Name, and JNDI name. Activate the radio button Select a data store helper class and then select Db2® Universal data store helper.
3. Under Related Items, click JAAS - J2C authentication data and select the authentication data entry that you selected in step 3.
4. Enter the User ID and Password used to connect to the database.
5. Click OK and Save to save changes to the master configuration.
Return back to the data sources page.
1. For Component-managed authentication alias select the authentication data entry that you selected in step 3.
2. For DB2 universal source properties specify the following data source information for your system:
  
  Database name
  
  Specify the name of the Content Manager Enterprise Edition database.
  
  Driver type
  
  Specify the JDBC connectivity type that is used by the data source. There are four JDBC driver types. Driver type 4 is the most common driver type for applications that access the internet, such as a client.
  
  Server name
  
  Specify the IP address or host name of the computer on which your Content Manager Enterprise Edition library server is installed.
  
  Port number
  
  Specify the TCP/IP port number of the Content Manager Enterprise Edition library server. DATASTORE_NAME is set according to your database name for the library server.
3. Port number: Specify the TCP/IP port number of the Db2 Content Manager library server. DATASTORE_NAME is set according to your database name for the library server.
4. Click OK and Save to save changes to the master configuration.
5. Click Test connection to verify that the data source you configured is working.
Restart server1 to make all of a client configuration take effect.
Configure the WebSphere Application Server connection pool settings, such as connection timeout, maximum connections, minimum connections, reap time, unused timeout, aged timeout, and purge policy.
Configure these parameters according to your performance requirements and system resources.