Running a webMethods Messaging Trigger

When you run a webMethods messaging trigger, you can select the launch configuration that Designer uses to run the webMethods messaging trigger. If a launch configuration does not exist for a webMethods messaging trigger, Designer creates a launch configuration and immediately prompts you for input values and then runs the webMethods messaging trigger. Designer saves the launch configuration in your workspace.

When you run a webMethods messaging trigger, you can only test one condition at a time.

When you run a webMethods messaging trigger with a join condition Designer treats the activation IDs for the documents as identical. Designer ignores the value of the activation field in the document envelope.

When you run a webMethods messaging trigger by running a launch configuration, the webMethods messaging trigger is tested locally. That is, a document is not routed through the messaging provider.

Note:

To test a webMethods messaging trigger by publishing a document to the messaging provider, test a publishable document type. You test a publishable document type by creating and running a launch configuration for the publishable document type.

Designer displays results for running the webMethods messaging trigger in the Results view.

1. In Package Navigator view of the Service Development perspective, select the webMethods messaging trigger you want to run.

3. If multiple launch configurations exist for the service, use the Select Launch Configuration dialog box to select the launch configuration that you want Designer to use to run the webMethods messaging trigger.

4. If the launch configuration is set up to prompt the user for input values or there is no launch configuration, in the Enter Input for triggerName dialog box, in the Condition list, select the condition that you want to test using the launch configuration.

5. If the condition is a join condition with an Any (OR) or Only one (XOR) join, do the following:

b. In the Select a Document Type dialog box, select the document type for which you want to provide input data.

For an Only one (XOR) join, select one or more document types to use to test the join condition. Note that at run time, the trigger service processes only one of the documents. The trigger discards the other document.

6. In the Enter Input for triggerName dialog box, select the tab with the name of the IS document type for which you want to provide input data.

7. Select or clear the Include empty values for String Types check box to indicate how to handle variables that have no value.

If you want to use an empty String (i.e., a String with a zero-length), select the Include empty values for String Types check box. Also note that Document Lists that have defined elements will be part of the input, but they will be empty.

If you want to use a null value for the empty Strings, clear the check box. String-type variables will not included in the input document.

Note:

The setting applies to all String-type variables in the root document of the input signature. The setting does not apply to String-type variables within Document Lists. You define how you want to handle String-type variables within Document Lists separately when you assign values to Document Lists variables. For more information, see webMethods Service Development Help.

8. Specify the values to save with the launch configuration for the webMethods messaging trigger by doing one of the following:

To load the input values from a file, click Load to locate and select the file containing the input values. If Designer cannot parse the input data, it displays an error message indicating why it cannot load the data.

For more information about loading input values from a file, see webMethods Service Development Help.

Note:

If you type in input values, Designer discards the values you specified after the run. If you want to save input values, create a launch configuration. For instructions, see Running a webMethods Messaging Trigger .