If all triggers in the trigger group have the same state, then the trigger group header will display that state.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. |
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. |
If all triggers in the trigger group have the same state, then the trigger group header will display that state.If at least one trigger in the trigger group is enabled, then the trigger group header will display "Enabled [x of n]" where x is the number of enabled triggers and n is the total number of triggers in the trigger group.If no triggers are enabled but at least one trigger in the group is Suspended, then the trigger group header will display "Suspended [x of n]" where x is the number of suspended triggers and n is the total number of triggers in the trigger group.If all of the triggers in the group are running, the Status column displays “Running “.If at least one trigger in the group is running, the Status column displays “Running [x of n]”.If none of the triggers in the group are running, the Status column displays “Not Running”.