Tuning application servers

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.

About this task

The following steps describe various tuning tasks that may improve your application server performance. You can choose to implement any of these application server settings. These steps can be performed in any order.

Procedure

  1. Tune the object request broker. 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 use the following parameters to tune the ORB:
  2. Tune the XML parser definitions.
    • Description: Facilitates server startup by adding XML parser definitions to the jaxp.properties and xerxes.properties files in the ${app_server_root}/jre/lib directory. The XMLParserConfiguration value might change as new versions of Xerces are provided.
    • How to view or set: Insert the following lines in both files:
      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
    • Default value: None
    • Recommended value: None
  3. Tune the dynamic cache service.

    Using the dynamic cache service can improve performance. See Task overview: Using the dynamic cache service to improve performance for information about using the dynamic cache service and how it can affect your application server performance.

  4. Tune the EJB container. An Enterprise JavaBeans (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.

  5. Tune the session management.

    The installed default settings for session management are optimal for performance.

  6. Tune the data sources and associated connection pools. A data source is used to access data from the database; it is associated with a pool of connections to that database.
    • Review information on Connection pooling to understand how the number of physical connections within a connection pool can change performance.
    • Use Data access tuning parameters as a reference for the data source and connection pool properties that most affect performance.
  7. Tune the URL invocation cache.

    Each JavaServer Page is a unique URL. If you have more than 50 unique URLs that are actively being used, increase the value specified for the invocationCacheSize JVM custom property. This property controls the size of the URL invocation cache.

  8. Change how frequently the recovery log service attempts to compress any logstreams that application components are using.

    The Transaction Service RLS_LOGSTREAM_COMPRESS_INTERVAL custom property can be set to a value larger then the default value if the Transaction Service is the only application component using a logstream. If none of your components are configured to use a logstream, you can set this property to 0 (zero) to disable this function.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tprf_tuneappserv
File name: tprf_tuneappserv.html