Fix for PQ66154

Date:  09/20/2002

Release:  WebSphere Advanced 3.5.6, and 3.5.5, This test E-Fix may work on
          previous PTFs, but it is not tested on PTF's prior to 3.5.5.  
          
Directions to apply fix:

1) Create a directory to store the jar file 
     (e.g. c:\WebSphere\AppServer\efix)
2) Copy the jar file into the directory.
3) Add the directory/jar file to the beginning of the admin server's
   classpath in admin.config:
     com.ibm.ejs.sm.adminserver.classpath=C:/WebSphere/AppServer/efix/PQxxxxx.jar; ...
4) Add any desired admin server data source properties to the admin.config following the instructions below.
5) Stop and restart the Admin Server.  

Description of the fix:

This fix allows a user to specify datasource properties such as idle timeout and orphan timeout
for the datasource used by the WebSphere Administrative Server.  These properties are set by adding
entries to the admin.config file.  The possible datasource properties are:

com.ibm.ejs.sm.adminServer.connectionPoolSize    - The maximum number of connection in the 
						   Administrative Server connection pool. The
						   default value is 15.
com.ibm.ejs.sm.adminServer.connectionPoolSizeMin - The minumum number of connections in the
						   Administrative Server connection pool.  The
						   default value is 1.
com.ibm.ejs.sm.adminServer.dbconnTimeout     	 - Amount of time in milliseconds to wait for a 
						   connection from the connection pool before 
						   issuing a ConnectionWaitTimeoutException.
						   The default value is 180000, or 3 minutes.
com.ibm.ejs.sm.adminServer.dbidleTimeout 	 - Amount of time in milliseconds a connection
						   will remain idle in the pool before being
						   closed.  The default value is 1800000, or 30
						   minutes.  If the pool is already at the
						   connectionPoolSizeMin value, connections will
						   not be idled.
com.ibm.ejs.sm.adminServer.dborphanTimeout 	 - Amount of time in milliseconds before a 
						   connection which has not been properly closed
						   will be returned to the connection pool.  The
						   default value is 1800000, or 30 minutes.
com.ibm.ejs.sm.adminServer.dbstatementCacheSize  - The maximum number of prepared statement to
						   cached for the datasource.  This value will be
						   divided by the connectionPoolSize value, and that
						   number of prepared statements will be cached per
						   database connection in the pool.  The default
						   value is 20 prepared statements per connection.

For more details on the meanings of the above values, or for more details on how connection pooling
works, see http://www-3.ibm.com/software/webservers/appserv/whitepapers/connection_pool.pdf.  While
this comprehensive connection pooling whitepaper was written for WebSphere 4.0, most of the concepts
apply to WebSphere 3.5 as well, and features only available in WebSphere 4.0 are flagged as such.