Event Priority

Prior to FTM Version 3.0.0, all events were treated equally and were processed in a FIFO (first in, first out) manner. Apart from allocating additional threads to separated event processing wrappers, there was no way of prioritizing events. This made messages running through FTM subject to latency variances as the system became busy.

Since FTM is event driven with WebSphere® MQ, workload prioritization leverages the basic IBM® MQ priority mechanism.
  • The event queue is defined to use IBM MQ priority for message event ordering.
  • All 'Render As Msg' events are put onto the event queue with a calculated IBM MQ priority.
  • Channel/Mappers can assign priority values to physical transmissions and transactions as they enter the system.
  • Events can be optionally modeled with a priority.
  • The weighting ratio between object priority (OBJ_BASE.TECH_PRIORITY) and event priority influences the calculated priority.

For more information about how to enable event prioritization, how to set tech priority and event priority, the priority weightings, and how the final event priority is calculated, see Event Prioritization.