2 WebLogic Server Domain Optimizations for Exalogic Elastic Cloud Software

This chapter describes WebLogic Server 12.1.3 Domain Optimizations for Exalogic Elastic Cloud Software.

This chapter includes the following sections:

Input/ Output and Work Manager Optimizations for Exalogic Elastic Cloud Software

Exalogic Elastic Cloud Software can be configured with input/output and Work Manager optimizations for WebLogic Server Table 2-1 lists and describes the MBean attributes for configuring WebLogic Server with these options that are restricted to Exalogic Domain-Level Elastic Cloud Software licenses.

Table 2-1

MBean Attribute -D Option Description

KernelMBean.ScatteredReadsEnabled=true

-Dweblogic.ScatteredReadsEnabled

Increases efficiency during I/O in environments with high network throughput.

KernelMBean.GatheredWritesEnabled=true

-Dweblogic.GatheredWritesEnabled

Increases efficiency during I/O in environments with high network throughput.

KernelMBean.AddWorkManagerThreadsByCpuCount=true

-Dweblogic.AddWorkManagerThreadsByCpuCount

Increases efficiency of the self-tuning thread pool by aligning it with the Exalogic processor architecture threading capabilities

ServerMBean.useConcurrentQueueForRequestManager=true

-Dweblogic.useConcurrentQueueForRequestManager

Lockless request manager enables higher concurrency and efficiency in processing on Exalogic systems, especially for JMS use cases.

KernelMBean.MuxerClass=weblogic.socket.NIOSharedWorkSocketMuxer

  

Reduces queue wait time for requests with high impact from muxing, such as JMS messages, replication, RMI.

Tuning I/O Performance for a Server Instance Using the Administration Console

When enabled, these attributes increases efficiency during I/O in environments with high network throughput. The attribute is automatically enabled when Enable Exalogic Optimizations is enabled at the Domain level. See Enabling Exalogic Optimizations.

Note:

AddWorkManagerThreadsByCpuCount is not tunable using the WebLogic Server Administration Console.

To manage this behavior at the server level or using a server template:

  1. If you have not already done so, in the Change Center of the WebLogic Server Administration Console, click Lock & Edit. See "Use the Change Center" in Oracle WebLogic Server Administration Console Online Help.

  2. In the left pane of the WebLogic Server Administration Console, under Domain Structure, select Environment > Servers or Environment > Clusters > Server Templates.

  3. Select a server or server template.

  4. Optionally, select Configuration > Tuning and select the appropriate check box:

    • Enable Gathered Writes

    • Enable Scattered Reads

  5. Select Advanced and optionally:

    • Optionally, select Use Concurrent Queue For Request Manager

    • Optionally, set Muxer Class to weblogic.socket.NIOSharedWorkSocketMuxer for Exalogic Environments. The default Muxer Class is weblogic.socket.NIOSocketMuxer.

  6. Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.

  7. Shut down and restart the server. See "Start and stop servers" in Oracle WebLogic Server Administration Console Online Help.

Enabling JDBC Store Exalogic Optimizations

This release of WebLogic Server provides an Exalogic optimization for JDBC stores to commit a batch of INSERT or DELETE operations with the last operation of the transaction instead of issuing a separate commit call to the database server. This feature saves a server round trip per transaction and benefits applications that have many transactions of a small number of operations or small messages.

To manage this behavior for an individual store:

  1. If you have not already done so, in the Change Center of the WebLogic Server Administration Console, click Lock & Edit. See "Use the Change Center" in Oracle WebLogic Server Administration Console Online Help.

  2. In the left pane of the WebLogic Server Administration Console, under Domain Structure, select Services > Persistent Stores.

  3. Select a JDBC store.

  4. Select Advanced on the Configuration tab, optionally select Oracle Piggyback Commit Enabled.

  5. Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.

  6. Shut down and restart the server. See "Start and stop servers" in Oracle WebLogic Server Administration Console Online Help.

Enabling TopLink Exalogic Optimizations

This release of WebLogic Server provides TopLink Exalogic optimizations that include: batch writing, increasing the default cache size, and enable other optimizations such as weaving eager relationships. A runtime tuning agent optimizes the use of query batch fetching and dynamic query processing.

For additional information on how to enable and configure features that can optimize how persistence applications perform in Oracle Exalogic environments, see "Optimizing Persistence Applications for Oracle Exalogic" in Solutions Guide for Oracle TopLink.

Enabling Exalogic Optimizations

Optimizations include improved thread management, request processing, and reduced lock contention. To enable all servers in a domain to use Exalogic optimizations:

  1. If you have not already done so, in the Change Center of the WebLogic Server Administration Console, click Lock & Edit. See "Use the Change Center" in Oracle WebLogic Server Administration Console Online Help.

  2. In the left pane of the WebLogic Server Administration Console, under Domain Structure, select the domain name.

  3. Select Configuration > General and select the Enable Exalogic Optimizations check box.

  4. Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.

  5. Shut down and restart all servers that are currently running in the domain. See "Start and stop servers" in Oracle WebLogic Server Administration Console Online Help.