Building Your Event-Driven Architecture : Service Development Help : Working with webMethods Messaging Triggers : Overview of Building a webMethods Messaging Trigger : Trigger Service Requirements
Trigger Service Requirements
The service that processes a document received by a webMethods messaging trigger is called a trigger service. A condition specifies a single trigger service.
A trigger service for a webMethods messaging trigger must meet the following requirements:
*Before you can enable a webMethods messaging trigger, the trigger service must already exist on the same Integration Server.
*The input signature for the trigger service needs to have a document reference to the publishable document type.
*The name for this document reference must be the fully qualified name of the publishable document type. The fully qualified name of a publishable document type conforms to the following format: folder.subfolder:PublishableDocumentTypeName
For example, suppose that you want a webMethods messaging trigger to associate the Customers:customerInfo publishable document type with the Customers:addToCustomerStore service. On the Input/Output tab of the service, the input signature must contain a document reference named Customers:customerInfo.
*If you intend to use the service in a join condition (a condition that associates multiple publishable document types with a service), the service’s input signature must have a document reference for each publishable document type. The names of these document reference fields must be the fully qualified names of the publishable document type they reference.
Note:  
An XSLT service cannot be used as a trigger service.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback