Compressing JMS Messages JMS message compression is a service-level option. It is especially useful when messages are to be stored on the TIBCO Enterprise Message Service server, including persistent queue messages, or topics with durable subscribers. Enabling compression ensures that messages occupy less memory in storage and are handled faster by the TIBCO Enterprise Message Service server. When JMS messages are compressed and stored, they are handled by the server in the compressed form. The compression option only compresses the body of a message. Headers and properties are never compressed. It is best to enable compression when the message bodies are large and the messages are to be stored on a server. When messages are not to be stored, compression is not as useful. Compression normally takes time, and therefore the time to send or publish and receive compressed messages is generally longer than the time to send the same messages uncompressed. There is little purpose to message compression for small messages that are not to be stored by the server. JMS message compression is only available for CI Publication Service, Message Publication Service, and Request-Response Invocation Service. You can enable or disable this feature for message senders by using the JMS Compress drop-down list in the Configuration tab of a service. See Configuration Tab in the Configuration Options section of each of the three services in Chapter 5, Configuring Adapter Services.