Stage 1 | Create a new JMS trigger on Integration Server. During this stage, you use Designer to create the new JMS trigger on the Integration Server where you will do your development and testing. |
Stage 2 | Specify a JMS connection alias. During this stage, you specify the JMS connection alias that Integration Server uses to create connections to the JMS provider. The transaction type of the JMS connection alias determines whether or not the JMS trigger receives and processes messages as part of transaction. |
Stage 3 | Specify JMS destinations and message selectors. During this stage, you specify the destinations (queues or topics) on the JMS provider to which the JMS trigger subscribes. That is, the destination is the source of the messages that the JMS trigger consumes. You also specify any message selectors that you want the JMS provider to use to filter the messages it enqueues for the JMS trigger. |
Stage 4 | Create routing rules (for standard JMS triggers only). During this stage, you specify the service that Integration Server invokes when the standard JMS trigger receives messages. You can also specify a local filter that Integration Server applies to messages. |
Stage 5 | Set JMS trigger properties. During this stage, you determine the type of message processing, the acknowledgement mode, fatal and transient error handling, and exactly-once processing. |
Stage 6 | Test and debug the JMS trigger. During this stage, you test and debug the trigger using the tools provided by Integration Server. For more information, see
Debugging a JMS Trigger. |