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.
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.
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.
You can make one or more of the following configuration changes to decrease the CPU overhead for a server:
The WebSphere Application Server class loading function uses asynchronous scope alarms instead of Java timers. If you put the alarm manager into quiet mode, class reload only runs when the server completes the processing of a request. If the server is not processing any requests, the class reload function does not run.
Example: Setting Custom JVM Properties describes how to put the alarm manager into quiet mode.
Enterprise application settings describes how to disable class reloading, and how to change the value of the Reload Interval parameter.
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000