webMethods Messaging Trigger Requirements

Cloud Application Integration (On-Premises) : Service Development : Working with webMethods Messaging Triggers : Overview of Building a webMethods Messaging Trigger : webMethods Messaging Trigger Requirements

AwebMethods messaging trigger must meet the following requirements:

The webMethods messaging trigger contains at least one condition.

Each condition in the webMethods messaging trigger specifies a unique name.

Each condition in the webMethods messaging trigger specifies a service.

Each condition in the webMethods messaging trigger specifies at least one publishable document type.

If more than one condition in the webMethods messaging trigger specifies the same publishable document type and the trigger receives messages from the webMethods Broker, the filters in the conditions must be the same. Specifically, the contents of the Filter column must be identical for each condition that subscribes to the publishable document type. Software AG does not recommend using the same publishable document type in more than one condition in the same trigger when receiving messages from webMethods Broker.

Note:

Provider filters must be identical if multiple conditions in the same trigger specify the same publishable document type.

If more than one condition in the webMethods messaging trigger specifies the same publishable document type and the trigger receives messages from Universal Messaging, the provider filters must be identical in each condition but the local filters can be different. Specifically, the contents of the Provider Filter (UM) column must be identical for each condition that subscribes to the publishable document type. The contents of the Filter column can be different.

The webMethods messaging trigger contains no more than one join condition.

The webMethods messaging trigger subscribes to publishable document types that use the same messaging connection alias. For the publishable document types to which the trigger subscribes, the value of the Connection alias name property can be:

The name of a specific messaging connection alias.

DEFAULT where the default messaging connection alias is the same as the alias specified for the other publishable document types to which the trigger subscribes.

The syntax of a filter applied to a publishable document type is correct. That is, the filter in the Filter column must be valid. Integration Server does not validate the provider filter in the Provider Filter column.

When you save a webMethods messaging trigger, Integration Server evaluates the webMethods messaging trigger to make sure the webMethods messaging trigger is valid. If Integration Server determines that the webMethods messaging trigger or a condition in the webMethods messaging trigger is not valid, Designer displays an error message and prompts you to cancel the save or continue the save with a disabled webMethods messaging trigger.