Why and when to perform this task
The WebSphere Application Server contains interrelated components that must be harmoniously tuned to support the custom needs of your end-to-end e-business application.The follow steps describe various tuning tasks that may improve your application server performance. You can choose to implement any of these application server settings.
One of the parts of each WebSphere Application Server is a Web container. To route servlet requests from the Web server to the Web containers, the product establishes a transport queue between the Web server plug-in and each Web container. The Web container is initially created with default property values suitable for simple Web applications. However, these values might not be appropriate for more complex Web applications. Using the following parameters, you can tune the Web container to fit the specific needs of your application server.
An EJB container is automatically created when you create an application server. After the EJB container is deployed, you can use the following parameters to make adjustments that improve performance.
See also EJB method Invocation Queuing.
The installed default settings for session management are optimal for performance. See Tuning session management and Tuning parameter settings for more information about tuning session management.
A data source is used to access data from the database. The following parameters reveal how the number of physical connections within a connection pool can change performance.
If more than 50 unique URLs are actively being used (each JSP is a unique URL), increase the value specified for the invocationCacheSize JVM custom property. This property controls the size of the URL invocation cache. See Tuning the URL invocation cache for more information on how to change this property.