WebLogic Server 12.1.3 provides the ability to configure message compression for JMS Store I/O operations which may provide significant performance improvements in Oracle Exalogic environments.
By selecting an appropriate message body compression option, JMS store I/O performance may improve for:
Persistent messages that are read from or written to disk.
Persistent and non-persistent messages are paged in or paged out when JMS paging is enabled.
The following sections provide information on how to configure message compression:
Message Compression for JMS Servers in Exalogic Environments
Message Compression for Store-and-Forward Sending Agents in Exalogic Environments
For general tuning information on JMS message compression, see "Compressing Messages" in Tuning Performance of Oracle WebLogic Server.
This section provides information on the types of message compression available for use when message body compression is enabled.
Note:
The performance of each compression option is dependent on the operating environment, data type, and data size. Oracle recommends users test their environments to determine the most appropriate compression option.Table 5-1 Message Body Compression Options
| Compression Type | Description |
|---|---|
|
GZIP DEFAULT_COMPRESSION |
Use |
|
GZIP BEST_COMPRESSION |
Use |
|
GZIP BEST_SPEED |
Use |
|
LZF |
Use LZF to enable message compression using Open Source LZF. See |
To configure message body compression for JMS servers:
If you have not done so, create a JMS Server, see "Create JMS servers" in the Oracle WebLogic Server Administration Console Online Help
Use the instructions to "Configure general JMS server properties" in the Oracle WebLogic Server Administration Console Online Help. Update the following Advanced JMS server attributes for your environment:
Optionally, select Store Message Compression Enabled to enable the JMS store to perform message body compression. See "StoreMessageCompressionEnabled" in MBean Reference for Oracle WebLogic Server.
Optionally, select Paging Message Compression Enabled to enable the JMS paging store to perform message body compression on persistent and non-persistent messages. See "PagingMessageCompressionEnabled" in MBean Reference for Oracle WebLogic Server.
In Message Compression Options, specify the type of message compression used. See "MessageCompressionOptions" in MBean Reference for Oracle WebLogic Server.
To configure message body compression for SAF Sending Agents:
If you have not done so, create a SAF Sending Agent, see "Create Store-and-Forward agents" in the Oracle WebLogic Server Administration Console Online Help
Use the instructions to "Configure SAF agent general properties" in the Oracle WebLogic Server Administration Console Online Help. Update the following Advanced Sending Agent attributes for your environment:
Optionally, select Store Message Compression Enabled to enable the JMS store to perform message body compression. See "StoreMessageCompressionEnabled" in MBean Reference for Oracle WebLogic Server.
Optionally, select Paging Message Compression Enabled to enable the JMS paging store to perform message body compression on persistent and non-persistent messages. See "PagingMessageCompressionEnabled" in MBean Reference for Oracle WebLogic Server.
In Message Compression Options, specify the type of message compression used. See "MessageCompressionOptions" in MBean Reference for Oracle WebLogic Server.