Updating JMS triggers

When API Gateway creates a JMS trigger as part of creating a provider web service endpoint alias, API Gateway uses default values for some of the trigger properties and placeholders for other properties. You can modify the default and placeholder values in the SOAP JMS trigger controls

To update a JMS trigger

1. Expand the menu options icon

, in the title bar, and select Administration.

2. Select General > Messaging.

The SOAP JMS trigger controls section displays a list of all the currently defined JMS triggers and the corresponding details.

3. Click a JMS trigger.

The Update JMS trigger screen appears.

4. In the JMS destinations and message selectors section you can modify the following information as required:

a. Destination name. Type the name of the queue from which the JMS trigger receives messages.

5. In the Settings section you can modify the following information as required:

a. JMS connection alias. Specify the JMS connection alias used by the trigger.

6. In the Properties section you can select one of the following Processing modes:

Concurrent. Specifies that API Gateway processes multiple messages for this trigger at one time. You can modify the following information for this processing mode:

Max execution threads. Specify the maximum number of messages that API Gateway can process concurrently.

Connection count. Specify the number of connections you want the JMS trigger to make to the webMethods Broker.

Note: The Connection count value must be less than or equal to the Max Execution Threads value.

Serial. Specifies that API Gateway processes messages received by the trigger one after the other.

7. Click Update.

The trigger is saved with the modified values.