Configuring WebSphere Application Server, J2EE, and JDBC for better performance

Configuring IBM® WebSphere® Application Server parameters can improve IBM Records Manager performance. You use the WebSphere Application Server administrative console to do the configuration.

• Setting the transaction lifetime
  The maximum duration for transactions on this application server is measured in seconds. Any transaction that is not requested to complete before the maximum duration expires times out and rolls back to the previous setting.
• Configuring the data source connection pool
  Set the maximum value according to the amount of concurrent users accessing the IBM Records Manager engine.
• Setting Max connections (WebSphere Application Server JMS Provider connection pool)
  The value of Max connections should be based on the number of concurrent batch requests.
• Configuring MaxUserPort (Maximum user ports)
  The MaxUserPort parameter sets the maximum number of user ports that TCP/IP can assign when an application requests an available user port from the system. You can adjust the value of this parameter to optimize network throughput. The MaxUserPort parameter applies only to the Windows® operating system.
• Setting TCP timed wait delay (TcpTimedWaitDelay)
  This parameter applies only to the Windows operating system. It determines the time that must elapse before TCP can release a closed connection and reuse its resources.
• Setting the initial and maximum heap size for the JVM
  Heap size specifies the amount of dynamic memory to be made available to the JVM code. For systems with less than 1 GB of physical memory, use a maximum heap size of 256 MB, and an initial heap size of 0 MB.