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.This group of interrelated components is known as the Queuing network. The queuing network helps the system achieve maximum throughput while maintaining the overall stability of the system.
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.
An Object Request Broker (ORB) manages the interaction between clients and servers, using the Internet InterORB Protocol (IIOP). It supports client requests and responses received from servers in a network-distributed environment. You can tune the ORB with the following parameters:
The Object Request Broker tuning guidelines offer tips on using these parameters to tune the ORB.
javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl javax.xml.parsers.DocumentBuildFactory=org.apache.xerces.jaxp. DocumentBuilderFactoryImpl org.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers. StandardParserConfiguration
Using the dynamic cache service can improve performance. See Configuring the dynamic cache service to improve performance for information about using the dynamic cache service and how it can affect your application server performance.
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.