B2B Integration 10.4 | Administering and Monitoring B2B Transactions | Service Development Help | Working with JMS Triggers | Enabling or Disabling a JMS Trigger | JMS Trigger States
 
JMS Trigger States
A JMS trigger can have one of the following states:
Trigger State
Description
Enabled
The JMS trigger is available. A JMS trigger must be enabled for it to receive and process messages.
An enabled trigger can have a status of “Not Running” which means that it would not receive and process messages. Reasons that an enabled JMS trigger can be disabled include: a disabled JMS connection alias, an exception thrown by the trigger, and trigger failure at startup. JMS trigger status can be seen on the Settings > Messaging > JMS Trigger Management page in Integration Server Administrator.
Disabled
The JMS trigger is not available. Integration Server neither retrieves nor processes messages for the JMS trigger. The JMS trigger remains in this state until you enable the trigger.
Suspended
The JMS trigger is running and connected to the JMS provider. Integration Server has stopped message retrieval, but continues processing any messages it has already retrieved. Integration Server enables the JMS trigger automatically upon server restart or when the package containing the JMS trigger reloads.
Note: You can suspend a JMS trigger using Integration Server Administrator or the pub.triggers:suspendJMSTriggers service.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release