19-2 Performance and Tuning for Oracle WebLogic Server
file JAXP API. Oracle recommends setting the properties on the command line to avoid unnecessary file operations at runtime and improve performance and
resource usage.
■
Follow JWS Programming Best Practices in Getting Started With JAX-WS Web Services for Oracle WebLogic Server.
■
Follow best practice and tuning recommendations for all underlying components, such as
Section 10, Tuning WebLogic Server EJBs ,
Section 18, Tuning Web Applications
, Section 12, Tuning Data Sources
, and Section 14, Tuning
WebLogic JMS .
19.2 Tuning Web Service Reliable Messaging Agents
Web Service Reliable Messaging provides advanced store-and-forward capability for high-performance message forwarding from a local server instance to a remote
destination. See Understanding the Store-and-Forward Service in Configuring and Managing Store-and-Forward for Oracle WebLogic Server. The following section provides
information on how to get the best performance from Store-and-Forward SAF applications:
■
Configure separate SAF Agents for JMS SAF and Web Services Reliable Messaging Agents to simplify administration and tuning.
■
Sharing the same WebLogic Store between subsystems provides increased performance for subsystems requiring persistence. For example, transactions that
include SAF and JMS operations, transactions that include multiple SAF destinations, and transactions that include SAF and EJBs. See
Section 8, Tuning the WebLogic Persistent Store
.
■
Consider increasing the WindowSize parameter on the remote SAF agent. For small messages of less than 1K, tuning WindowSize as high as 300 can improve
throughput.
■
Ensure that retry delay is not set too low. This may cause the system to make unnecessary delivery attempts.
19.3 Tuning Heavily Loaded Systems to Improve Web Service Performance
The asynchronous request-response, reliable messaging, and buffering features are all pre-tuned for minimum system resource usage to support a small number of clients
under 10. If you plan on supporting a larger number of clients or high message volumes, you should adjust the tuning parameters to accommodate the additional
load.
19.3.1 Setting the Buffering Sessions
The reliable messaging and buffering features use JMS queue sessions to send messages to the reliabilitybuffer queues. By default, WebLogic Server allocates 10
sessions for buffering which enables 10 clients to enqueue messages simultaneously onto the reliabilitybuffer queue.
Note:
WindowSize also tunes JMS SAF behavior, so it may not be
appropriate to tune this parameter for SAF agents of type both.
Tuning Web Services 19-3
For asynchronous request-response, the request and response portion of the communication exchange count separately, as two clients. In this case, the default pool
of sessions can support five simultaneous asynchronous request-response clients. To accommodate the number of concurrent clients you expect in your application, set the
following parameter to twice the number of expected client threads:
-Dweblogic.wsee.buffer.QueueSessionPoolSize=size
19.3.2 Releasing Asynchronous Resources
When using the asynchronous request-response feature, WebLogic Server persistently stores information about the request until the asynchronous response is returned to
the client. These resources remain in the persistent store until they are released by a background thread, called the store cleaner.
Often, these resources can be released sooner. Executing the store cleaner more frequently can help to reduce the size of the persistent store and minimize the time
required to clean it.
By default, the store cleaner runs every two minutes 120000 ms. Oracle recommends that you set the store cleaner interval to one minute 60000 ms using the following
Java system property:
-Dweblogic.wsee.StateCleanInterval=60000
19-4 Performance and Tuning for Oracle WebLogic Server
20
Tuning WebLogic Tuxedo Connector 20-1
20
Tuning WebLogic Tuxedo Connector
The WebLogic Tuxedo Connector WTC provides interoperability between WebLogic Server applications and Tuxedo services. WTC allows WebLogic Server clients to
invoke Tuxedo services and Tuxedo clients to invoke WebLogic Server Enterprise Java Beans EJBs in response to a service request. See WebLogic Tuxedo Connector in
Information Roadmap for Oracle WebLogic Server .
The following sections provide information on how to get the best performance from WTC applications:
■
Section 20.1, Configuration Guidelines
