Compressing JMS Messages

JMS compression ensures that JMS messages take less memory space in storage and are handled faster by the TIBCO Enterprise Message Service server.

With JMS compression, an EMS client can compress JMS message bodies, before sending the messages to the EMS server. It can save space in storage when JMS message bodies are large. However, it is also need more time to publish or receive compressed messages between EMS clients.

It is good practice to enable the compression when the message bodies are large and the messages are to be stored on a server.

For detailed information about JMS messages, see TIBCO Enterprise Message Service User's Guide.

You can configure the JMS compression by using one of the following ways:

In TIBCO Business Studio, select the isCompressed check box in the EndPoint Configuration panel of the JMS Publisher endpoint or JMS Rpc Client endpoint.
Note: The isCompressed check box is only shown in TIBCO Runtime Agent 5.8.0 or above.
In the adapter TRA file, enable the following properties:
- tibco.sdk.session.jmsCompressed session_name
  session_name specifies a list of JMS session names. All the JMS endpoints under the specified session, including Publisher, Client, and Server, send compressed JMS messages to the EMS server.
- tibco.sdk.endpoint.jmsCompressed endpoint_name
  endpoint_name specifies a list of JMS endpoints. All the specified JMS endpoints, including Publisher, Client, and Server, send compressed JMS messages to the EMS server.
Note: Separate multiple session names or endpoint names with vertical bars.
In the adapter TRA file, add the property, adr3.adapter_service_name.jmsProperties JMS_TIBCO_COMPRESS=ON.
Specify the name of the Publication Service service. The value of ON indicates that the JMS compression for the Publication Service service is enabled.

Note: This property is only available in the adapter TRA file. If the JMS property, JMS_TIBCO_COMPRESS, is added in the TRA file, it takes precedence over the adr3.jmscompress property. The adr3.jmscompress property is set to ON in TRA file by default, which indicates that the JMS compression for the Publication Service service enabled.

It is enough to use only one of these ways to set the JMS compression. For example, when a Publication endpoint is set to be compressed in TIBCO Business Studio, the messages are compressed even if it is not set in the TRA file, and vice versa.

The Request-Response Service server replies to JMS messages depending on whether the request messages are compressed. If the request messages are compressed, the Request-Response Service server replies to the compressed JMS messages. Otherwise, the Request-Response Service server replies to messages according to the configuration in the TRA properties.