Editing WS Endpoint Triggers

When Integration Server creates a WS endpoint trigger as part of creating a provider web service endpoint alias, Integration Server uses default values for some of the trigger properties and placeholders for other properties. You can use Integration Server Administrator to change the default and placeholder values.

Keep the following guidelines in mind when editing a WS endpoint trigger:

The JMS connection alias you want Integration Server to use to obtain connections to and receive messages from the JMS provider must already exist. Although a JMS connection alias does not need to be enabled at the time you assign it to the WS endpoint trigger, the JMS connection alias must be enabled for the WS endpoint trigger to execute at run time.

The transaction type of the JMS connection alias determines whether or not the WS endpoint trigger is transacted (that is, it receives and processes messages as part of a transaction)

The destination to which the WS endpoint trigger subscribes must be a queue.

Only concurrent triggers can have a Max Execution Threads value greater than one.

To specify a Connection Count value greater than one, the following must be true:

The specified JMS connection alias must be configured to create a new connection for each JMS trigger that uses that connection alias. For more information, see Allowing Multiple Connections for a JMS Connection Alias.

1. Open the Integration Server Administrator if it is not already open.

4. Under Individual SOAP JMS Trigger Controls, select the WS endpoint trigger that you want to edit.

5. On the Settings > Messaging > JMS Trigger Management > Detail > triggerName screen, click Edit Trigger.

6. In the JMS Connection Alias list, select the JMS connection alias that you want the WS endpoint trigger to use to receive messages from the JMS provider.

7. In the Destination Name field, type the name of the queue from which the WS endpoint trigger will receive messages.

Select...	To...
Serial	Specify that Integration Server processes messages received by the trigger one after the other.
Concurrent	Specify that Integration Server processes multiple messages for this trigger at one time.

9. If you selected concurrent processing, in the Max execution threads field, specify the maximum number of messages that Integration Server can process concurrently.

10. If you selected concurrent processing, in the Connection Count field, specify the number of connections you want the WS endpoint trigger to make to the webMethods Broker.

Note:

The Connection Count value must be less than or equal to the Max Execution Threads value.