API Gateway 10.5 | Using API Gateway | API Gateway Administration | General Configuration | JMS Triggers
 
JMS Triggers
 
Updating JMS triggers
JMS Triggers are meant only for SOAP APIS. These triggers are created automatically when you create a Web Service Provider endpoint and act as Listener for that Web Service Provider endpoint.
API Gateway provides ways for managing JMS triggers and the resources used by JMS triggers. You can only update a trigger and cannot create a trigger. Specifically, you can use the controls provided by API Gateway to:
*Increase or decrease the maximum number of server threads used for JMS triggers
*Change the maximum execution threads for concurrent JMS triggers
*Change the destinations to which the trigger subscribes
*Change the JMS connection alias used by the trigger
*Delay the frequency with which a JMS trigger polls for more messages
The Individual SOAP JMS trigger controls section displays all the JMS triggers that exist on the API Gateway along with a summary of each trigger. The summary includes the current status, state, and thread usage of the trigger as well as configuration information such as the JMS connection alias used by the trigger, the destination to which the trigger subscribes, and the processing mode of the trigger.
JMS trigger status and state
The state of a JMS trigger indicates whether the trigger is enabled, disabled, or suspended. The status indicates whether trigger is running.
A JMS trigger can have one of the following states:
*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.
A JMS trigger can have a status of “Running” or “Not Running (reason )” where reason identifies why the rigger is not running, such as “Not Running (trigger disabled)”.
You can enable a trigger by clicking the toggle button . The toggle button changes to to depict that the trigger is enabled.
You can disable the trigger by clicking the toggle button . The toggle button changes to to depict that the trigger is disabled.