# Triggered Message Flow from IMS Transactions

Implementing a triggered message flow is normally intrusive. If you want to use an IMS application to write messages to IMS queues with an alternate IOPCB, you must first add code to the application logic.

However, if output from an application only needs to be redirected to Substation ES, the redirection of the message can be accomplished by means of IMS OTMA exits.

The following is the process for a typical flow of a triggered message:

1. An IMS application inserts a message to the IMS message queue, specifying the trigger Tpipe name.
2. Substation ES IMS Interface is notified of the messages by XCF and consumes the information from the IMS queues through the OTMA protocol.
3. If the message is valid and recognized by Substation ES IMS Interface, the message is placed on a Substation ES inbound queue, making the request eligible for transformation.
4. After transformation, ESB Interface sends a message formatted for TIBCO messaging applications, and the message is sent to Substation ES Delivery Agent.

   If transformation fails, and the message is sent using a guaranteed service, the message is returned to an IMS Tpipe named SXITRNAK.

5. ESB Interface publishes the message to TIBCO messaging applications based on the level of service and destinations configured on the transformation recipe.

Copyright © TIBCO Software Inc. All rights reserved.