Administering JMS transport optimization

The flow of business information from adapters to the server, as well, as from the server to adapters, is a vital component of the InterChange Server Express functionality. With the marked increase in the use of JMS Transport, enhancements were necessary to ensure the highest quality in performance, throughputs and scalability.

InterChange Server Express stores events in a persistent storage for recovery purposes. In a non-optimized state, this storage could be very costly, especially if the business object is expansive. In an optimized state, the event is left in the message queue and referenced in the database. When all event subscribers have completed their work, the message is deleted from the queue.

By synchronizing information in the critical sections, events can be retrieved sequentially from the queue, ensuring a retainable event sequence as well as a scalable server in a multi-processor environment.

In order to achieve JMS Transport optimization, the InterChange Server Express provides the following enhancements:

This section covers the following topics:

Optimization versus non-optimization

Steps for activating and de-activating optimization

Optimization versus non-optimization

Although message transport is now optimized, there is also a need for transport to run in a non-optimized state, dependant upon business need. Switching from optimized to non-optimized allows users to swap messaging providers, if necessary, to accommodate the needs of their vendors.

You may opt to use a non-optimized state when business object events are small in size, or when database overhead is insignificant. However, prior to switching between an optimized and a non-optimized state you must wait until all queued events are recovered. Events running in an optimized state cannot be redelivered to InterChange Server Express in a non-optimized state.

Note:
Optimization is designed to have minimal impact on in-bound service calls and Long Lived Business Process (LLBP) events, which will both continue to process as non-optimized events. This is possible since the optimized state can process both optimized and non-optimized events.

Steps for activating and de-activating optimization

Perform the following steps to activate and de-activate JMS transport optimization:

  1. During the connector configuration, select the check box for JMS Optimization.
  2. Set the value of the following connector properties. Once set, the connector configuration will upgrade the configuration files.
    Note:
    If JMS is set as the transport, the default value for the jms.TransportOptimized property is False. When jms.TransportOptimized is set to True, the JMS provider (jms.FactoryClassName) must be IBM MQ.
  3. To switch back to the non-optimized state, first ensure that the server is not currently processing any events and the delivery queue is clean. If you attempt to switch from an optimized state to a non-optimized state there are remaining events in the delivery queue, an error will display when the connector deploys to InterChange Server Express.
  4. Clear the check box for JMS Optimization.
  5. Set the value of the following connector properties. Once set, the connector configuration will upgrade the configuration files.

Copyright IBM Corp. 2004, 2005