Creating a Launch Configuration for a webMethods Messaging Trigger
Use the following procedure to create a launch configuration for running a webMethods messaging trigger.
To create a launch configuration for running a
webMethods messaging trigger1. In the Service Development perspective, select Run > Run Configurations
2. In the Run Configuration dialog box, select webMethods Messaging Trigger and click 
to add a new launch configuration. 3. In the Name field, specify a name for the launch configuration.
4. On the webMethods Messaging Trigger tab, in the Integration Server list, select the Integration Server on which the webMethods messaging trigger for which you are creating a launch configuration resides.
5. In the webMethods Messaging Trigger field click Browse to navigate to and select the trigger.
6. On the Input tab, in the Condition list, select the condition that you want to test using the launch configuration.
7. If the condition is a join condition with an Any (OR) or Only one (XOR) join, do the following:
a. Next to Document Type, click Select.
b. In the Select a Document Type dialog box, select the document type for which you want to provide input data in this launch configuration.
For an Any (OR) join, select one document type.
For an Only one (XOR) join, select the document or document types that you want to use to test the join condition.
c. Click OK.
8. On the Input tab, select the tab with the name of the IS document type for which you want to provide input data.
If the selected condition uses an All (AND) join, Designer displays one tab for each document type in the join condition. If the condition is an Only one (XOR) join and you selected multiple document types for which to supply input data, Designer displays one tab for each selected document type.
a. 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.
b. Specify the values to save with the launch configuration for the webMethods messaging trigger by doing one of the following:
Type the input value for each field in the document type.
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.
Designer validates the provided input values. If provided values do not match the input parameter data type, Designer displays a message to that effect. You cannot use the launch configuration for the webMethods messaging trigger if the provided input does not match the defined data type.
c. If you want Designer to give the user executing the launch configuration the option of providing different input values than those saved with the launch configuration, select the Prompt for data at launch check box. If you clear this check box, Designer passes the webMethods messaging trigger the same set of data every time the launch configuration executes.
9. Repeat the preceding step for each IS document type displayed on the Input tab.
10. If you want to save the input values that you have entered, click Save.
11. Click Apply.
12. If you want to execute the launch configuration, click Run. Otherwise, click Close.