JMS Messages Compression
JMS message compression is useful when messages are to be stored on the TIBCO Enterprise Message Service server. The messages include persistent queue messages and topics with durable subscribers.
When compression is enabled, messages take less memory space 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 not compressed. When the message bodies are large and the messages are to be stored on a server, you can compress messages.
When messages are not to be stored, compression is not as useful. Compression 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. You do not have to compress small messages that are not to be stored by the server.
You can enable or disable this feature for message senders with the following adapter property:
adapter property for JMS compressing: the default value of the property is set to OFF, which indicates that messages are not compressed. If you want to enable the feature, set the property to ON.