webMethods 10.2 | Service Development Help | Working with Document Types | About Testing Publishable Document Types | Creating a Launch Configuration for a Publishable Document Type
 
Creating a Launch Configuration for a Publishable Document Type
Use the following procedure to create a re-usable launch configuration that you can run to test a publishable document type.
* To create a launch configuration for a publishable document type
1. In the Service Development perspective, select Run > Run Configurations.
2. On the Configurations tree, select IS Document (Publishable), and then click .
A new configuration entry appears below IS Document (Publishable) and the launch configuration options appear on the right-hand side of the dialog box.
3. In the Name field, enter a new name for your launch configuration. The Publishable tab displays the name of the Integration Server where the document type resides as well as the name of the document type.
4. In the Integration Server list, select the Integration Server on which the publishable document type for which you are creating a launch configuration resides.
5. In the Publishable Document Type field, click Browse to navigate to and select the publishable document type for which you want to create a launch configuration.
6. Click the Input tab and specify input values for the publishable document type.
a. Enter valid values for the fields defined in the publishable document type or click Load to retrieve the values from a file. For information about loading input values from a file, see Loading Input Values.
b. Select the Prompt for data at launch check box if you want to view or edit the input data before the launch configuration runs. This option is selected by default.
c. If you want to save the input values that you have entered, click Save. Input values that you save can be recalled and reused in later tests. For information about saving input values, see Saving Input Values.
d. Click Apply. When you enter values for constrained objects in the Input tab, Integration Server automatically validates the values. If the value is not of the type specified by the object constraint, Designer displays a message identifying the variable and the expected type.
7. Click the Action tab and specify publish settings for the document type.
a. Select the type of publishing for the document.
Note: The options available here are enabled or disabled, depending on the messaging provider of the publishable document type or the version of Integration Server to which your Designer is connected.
Select...
To...
Publish locally to this Integration Server
Publish an instance of the publishable document type to the same Integration Server to which you are connected.
Publish to the Provider
Publish an instance of this publishable document type to the messaging provider specified by the messaging connection alias assigned to the document type.
Deliver to a destination
Deliver an instance of the publishable document type to a specific destination on the messaging provider.
Note: This option is disabled if your Designer is connected to a version of Integration Server prior to 9.8 and the messaging provider is Universal Messaging.
Publish locally to this Integration Server and wait for a Reply
Publish an instance of the publishable document type to the same Integration Server to which you are connected and wait for a response document.
Publish to the Provider and wait for a Reply
Publish an instance of this publishable document type to the messaging provider and wait for a response document.
Deliver to a destination and wait for a Reply
Deliver an instance of the publishable document type to a specific destination on the messaging provider and wait for a reply document.
Note: This option is disabled if your Designer is connected to a version of Integration Server prior to 9.8 and the messaging provider is Universal Messaging.
b. If you selected either Deliver to a destination or Deliver to a destination and wait for a Reply, in the Destination ID field, specify the destination to which you want to deliver the document. You can either enter the destination name or click Browse to select the destination. If you click Browse, Designer displays all the available Destination IDs.
Note: If your Designer is connected to Integration Server version 9.8 and the messaging provider is Universal Messaging, the Browse button is disabled. You can, however, enter destination ids in the Destination IDs field.
Note: Integration Server assigns trigger clients names according to the client prefix set for the Broker connection alias.
c. If you selected a publication action in which you wait for a reply, you need to select the document type that you expect as a reply. You can enter the document type name or click Browse to select the document type.
If you click Browse, Designer displays all the publishable document types on the Integration Server to which you are currently connected. In the Elements Name field, type the fully qualified name of the publishable document type that you expect as a reply or select it from the Folder list. If the service does not expect a specific document type as a reply, leave this field blank.
d. Under Set how long Designer waits for a Reply, select one of the following:
Select...
To...
Wait indefinitely
Specify that Designer should wait indefinitely for a reply document. Designer will wait for the response for the length of your session on the Integration Server. When you end your session or close Designer, Designer stops waiting for the reply.
Wait for
Specify the length of time that Designer should wait for the reply document.
Next to the Wait for option, enter how long you want Designer to wait for the reply document.
8. Optionally, click the Common tab to define general information about the launch configuration and to save the launch configuration to a file.
9. Click Apply.
10. Click Run to test the publishable document type now. Otherwise, click Close.

Copyright © 2017-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release