Creating a webMethods Messaging Trigger

DevOps Edition for Continuous Integration 10.4 | Service Development Help | Working with webMethods Messaging Triggers | Creating a webMethods Messaging Trigger

Creating Conditions

Using Filters with a Subscription

Creating Filters for Use with Universal Messaging

Creating Filters for Use with webMethods Broker

Using Multiple Conditions in a webMethods Messaging Trigger

When you create a webMethods messaging trigger, keep the following points in mind:

The publishable document types and services that you want to use in conditions must already existwebMethods messaging trigger.

A webMethods messaging trigger can subscribe to publishable document types only. A webMethods messaging trigger cannot subscribe to ordinary IS document types.

A webMethods messaging trigger must meet the requirements specified in webMethods Messaging Trigger Requirements.

Important: When you create webMethods messaging triggers, work on a stand-alone Integration Server instead of an Integration Server in a cluster or non-clustered group. Creating, modifying, disabling, and enabling webMethods messaging triggers on an Integration Server in a cluster or non-clustered group can create inconsistencies in the object that corresponds to the trigger on the messaging provider.

To create a webMethods messaging trigger

1. In the Package Navigator view of Designer, click File > New > webMethods Messaging Trigger.

2. In the Create a New webMethods Messaging Trigger dialog box, select the folder in which you want to save the webMethods messaging trigger.

3. In the Element Name field, type a name for the webMethods messaging trigger using any combination of letters, and/or the underscore character.

4. Click Finish.

Designer generates the new webMethods messaging trigger and displays it in the Designer window.

5. Under Condition detail, build a condition to specify the document types to which the webMethods messaging trigger subscribes and the trigger services that execute when instances of those document types are received. For more information about creating conditions, see Creating Conditions.

6. In the Properties view, set properties for the webMethods messaging trigger.

7. Click File > Save.

Notes:

Integration Server validates the webMethods messaging trigger before saving it. If Integration Server determines that the webMethods messaging trigger is invalid, Designer prompts you to save the webMethods messaging trigger in a disabled state. For more information about valid webMethods messaging trigger, see webMethods Messaging Trigger Requirements.

You can also use the pub.trigger:createTrigger service to create a webMethods messaging trigger. For more information about this service, see the webMethods Integration Server Built-In Services Reference.