Adjusting the JDBC Data Source Connection Pool size
When accessing any database, the initial database connection is an expensive operation. Connection pooling and connection reuse reduces the number of these operations significantly.
Only two parameters should be changed here: Min connections and Max connections. All other parameters should be left untouched. The minimum connections should be set to 15. The maximum connections should be set to equal the number of the Web Container Thread Pool size.
To view or change these parameters, use the following procedure (the following changes should be made to all LMS data sources):
1.In the WebSphere Administrative Console, go to JDBC Providers
2.Adjust Min Connections and Max Connections only; let the other parameters remain unchanged.
Note: Whenever increases are made on the JDBC connection pool, equivalent changes need to be made by the database administrator on the database server.
Adjusting WAS JDBC Data Sources properties to correct content deployment issues
In cases where LMS has trouble deploying course content after a course has been imported and registered, you can try the following suggestions with WAS JDBC Data Sources properties to correct this problem.
•Make sure that the Learning Server, Delivery Server, and Audit data sources have the JDBC Data Source statement cache size set to 0 instead of 10 (the default). This should eliminate the exceptions that were apparent in the log, and will probably allow course tracking to work if it was not working before.
•Change the custom property select method to cursor for all the JDBC data sources. The default value for this property is direct. For additional information about this setting, refer to http://edocs.bea.com/wls/docs81/jdbc_drivers/mssqlserver.html.
You must restart all servers after making any of these changes.
Tuning the LMS applications
Adjusting certain features of the Learning Server and Delivery Server applications can help to increase performance in the Learning Management System.
Adjusting LMS logging
Adjusting logging in LMS to specific levels can produce system performance benefits. To increase performance levels, set the various log Logging levels to “Warn.” Use the following procedures to do this.
Application Log
•Click Settings - LMM Server - System Logging - Application Log
•Set the Logging level to warn
Database Log
•Click Settings - LMM Server - System Logging - Database Log
•Set the Logging level to warn
E-mail Log:
•Click Settings - LMM Server - System Logging -
118 IBM Lotus LMS Release 1 Installation Guide
