Enabling, Disabling, and Suspending SOAP-JMS Triggers

You can manage SOAP-JMS triggers and the amount of resources they consume by changing the state of a SOAP-JMS trigger. A SOAP-JMS trigger can have one of the following states:

Trigger State	Description
Enabled	The SOAP-JMS trigger is running and connected to the JMS provider. Integration Server retrieves and processes messages for the SOAP-JMS trigger.
Disabled	The SOAP-JMS trigger is stopped. Integration Server neither retrieves nor processes messages for the SOAP-JMS trigger.
Suspended	The SOAP-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.

You might want to change the state of all SOAP-JMS triggers at once as a quick way of making server resources available. This can be especially helpful in a situation in which Integration Server is functioning under heavy load and additional resources are needed immediately.

When a back-end system needs maintenance or is becoming unresponsive, you might want to suspend SOAP-JMS Triggers that interact with the back-end system. When the back-end system becomes available, you can enable the SOAP-JMS triggers.

After suspending or disabling all SOAP-JMS triggers, you might enable specific SOAP-JMS triggers. For example, if the server is functioning under an unusually heavy load, you might first suspend all SOAP-JMS triggers and then gradually enable SOAP-JMS triggers, starting with the SOAP-JMS triggers involved in key processes.

After Integration Server suspends a serial SOAP-JMS trigger automatically because a fatal error occurred during message processing.

The following procedure explains how to use Integration Server Administrator to change the state of all or individual SOAP-JMS triggers.

b. On the Settings > Messaging > JMS Trigger Management > Edit State screen, in the New State list, select the state that you want to apply to all SOAP-JMS triggers.

a. Under Individual SOAP JMS Trigger Controls, in the row for the SOAP-JMS trigger that you want to enable, disable, or suspend, click the text in the Enabled column

b. On the Settings > Messaging > JMS Trigger Management > Edit State: triggerName screen, in the New State list, select the state that you want to apply to this SOAP-JMS trigger.

If you want to disable a SOAP-JMS trigger, first suspend the SOAP-JMS trigger and wait for all the processing threads complete. Then disable the SOAP-JMS trigger. You can view the number of threads currently used by a SOAP-JMS trigger on the Settings > Messaging > JMS Trigger Management screen.

If the SOAP-JMS trigger is waiting before making a retry attempt, Integration Server interrupts processing for the SOAP-JMS trigger.

If the SOAP-JMS trigger is currently processing messages, Integration Server waits a specified amount of time before forcing the SOAP-JMS trigger to stop processing messages. If it does not complete in the allotted time, Integration Server stops the message consumer used to receive messages for the SOAP-JMS trigger and closes the JMS session. At this point the server thread for the SOAP-JMS trigger continues to run to completion. However, the SOAP-JMS trigger is not able to acknowledge the message when processing completes. If the delivery mode of the message is set to persistent, this can lead to duplicate messages.

The time Integration Server waits between the request to disable the SOAP-JMS trigger and forcing the trigger to stop is specified by the watt.server.jms.trigger.stopRequestTimeout property.

Because administered objects, such as destinations, are configured outside of Integration Server, disabling a SOAP-JMS trigger has no impact on the subscription.

If a SOAP-JMS trigger is processing messages at the time it is suspended, the SOAP-JMS trigger completes processing of those messages. The SOAP-JMS trigger also acknowledges the messages to the JMS provider.

You can use the following built-in services to enable, disable, and suspend one or more triggers: pub.trigger:enableJMSTriggers, pub.trigger:disableJMSTriggers, and pub.trigger:suspendJMSTriggers. For details, see the webMethods Integration Server Built-In Services Reference.