# Normal Message Handling Compared to Fast Path Message Handling

The normal message handling processes in Substation ES are made to process numerous variations of RECIPE and TRIGGER definitions. It is extremely efficient but TIBCO has observed that certain message formats and layouts can be processed more efficiently by special (Fast Path) message handlers. These Fast Path handlers are selected at RECIPE or TRIGGER load time when analysis of the Service definition shows them to be “straight forward”.

Input Messages that will use Fast Path message Handlers are:

- In EMS:
  - Recipes that use CICS Container input
  - JMS input message type can be Bytes, or Text

- In RV:
  - Recipes that use CICS Container input
  - RV input message with only one data input field which is either OPA or STR

Output Messages that will use Fast Path message Handlers are:

- In EMS:
  - Recipes that use CICS Container output and Triggers with one output data object
    - JMS output message type can be Bytes, or Text (String)
    - No correlation id
    - No dynamic destination name
    - Only tibss-status property
    - No JMS compress feature

- In RV:
  - Recipes that use CICS Container output and Triggers with one output data object
    - RV input message with only one data input field which is either OPA or STR
    - Dynamic destination name is acceptable
    - Only tibss-status property

Copyright © TIBCO Software Inc. All rights reserved.