Running a webMethods Messaging Trigger with a Launch Configuration
In Designer, you can run a webMethods messaging trigger to verify that the subscription, filters, and trigger service work as expected. Designer requires launch configurations to run webMethods messaging triggers. However, if a webMethods messaging trigger does not have an associated launch configuration and you bypass the Run Configurations dialog boxes when running the webMethods messaging trigger, Designer creates a launch configuration on the fly and saves it in your workspace. You can use this configuration from one session to the next. In fact, Designer reuses this configuration every time you run the webMethods messaging trigger without creating another launch configuration.
By default, Designer saves launch configurations locally in an unexposed location in your workspace. However, you might want to share launch configurations with other developers. You can specify that Designer save a launch configuration to a shared file within your workspace; this location will be exposed. On the Common tab in the Run Configurations dialog box, select the Shared file option and provide a workspace location in which to save the file.
In a launch configuration for a webMethods messaging trigger, you specify:
The condition that you want
Designer to test. Each launch configuration can specify only one condition in the
webMethods messaging trigger.
The document type whose subscription you want to test. For an Any (OR) or Only one (XOR) join condition, you specify the document type for which you want to supply input.
Input data that
Designer uses to build a document.
Designer evaluates the filter using the data in the document and provides the document as input to the trigger service.
You can create multiple launch configurations for each webMethods messaging trigger.
