Working with webMethods Messaging Triggers

A webMethods messaging trigger subscribes to one or more publishable document types and processes instances of those document types. A webMethods messaging trigger can receive documents published to a webMethods messaging provider (Software AG Universal Messaging or webMethods Broker) or documents published locally by the Integration Server on which the trigger resides.

Each webMethods messaging trigger is composed of two basic pieces:

A subscription to one or more publishable document types

A service that processes instances of those publishable document types.

When a webMethods messaging trigger receives a document to which it subscribes from the messaging provider, Integration Server passes the document to the specified service and then invokes the service.

Note: Prior to Integration Server and Software AG Designer versions 9.5 SP1, a webMethods messaging trigger was called a webMethods Broker/local trigger.

Note: Information about webMethods messaging triggers is located in webMethods Service Development Help and Publish-Subscribe Developer’s Guide. Both documents include the Working with webMethods Messaging Triggers topic. Publish-Subscribe Developer’s Guide contains information such as how webMethods messaging triggers work, how Integration Server receives documents from webMethods messaging triggers, how webMethods messaging triggers with join conditions work, and how Integration Server performs exactly-once processing.