Compressing & Decompressing JMS messages in IBM Sterling Order Management

Steps to Configure Message Compression in JMS Sender of a Sample Service:

  1. Open Applications Manager.
  2. Click on "Applications" and select "Application Platform".
  3. In the tree structure on the application rules side panel, double-click on "Process Modeling".
  4. Click on the "Service Definitions" tab.
  5. Expand the relevant service group and locate the LoadInventoryMismatch service.
  6. Click on the green connector around JMS Sender component. The JMS Sender properties will be displayed under the graphic area.
    JMS_Sender
  7. Switch to the "Runtime" tab.
  8. Ensure that the "Destination Name" entered matches the name of an existing JMS Queue and matches the "Destination Name" specified in the JMS Receiver properties.
  9. Enable the "Needs Compression" option.

Steps to Configure Message Decompression in JMS Receiver of a Sample Service:

  1. Open Applications Manager.
  2. Click on "Applications" and select "Application Platform".
  3. In the tree structure on the application rules side panel, double-click on "Process Modeling".
  4. Click on the "General" tab. In the "Process Types" swimlane, right-click on the "General" process type and click on "Model Process". The Repository Details window and work area for the General process type will be displayed.
  5. Click on the "Service Definitions" tab.
  6. Locate the connector around JMS Receiver component and the API. The JMS Receiver properties will be displayed under the graphic area.
    JMS_Receiver
  7. Switch to the "Server" tab.
  8. Enable the "Needs Decompression" option in the JMS Receiver properties.

Conclusion:
Proper configuration for compressing and decompressing messages in OMS is essential for efficient message handling and reduced storage requirements. By following the guidelines provided in this technote, you can enable message compression, configure the system for decompression handling, and ensure smooth integration with external applications. Remember that decompression logic needs to be implemented by the client application or integration server consuming the messages.