Creating a Launch Configuration to Publish a Document as a JMS Message
Keep the following information in mind when creating a re-usable launch configuration that publishes an instance of an IS document type as a JMS message:
You can publish any IS document type as a JMS message including publishable document types.
Before you create the launch configuration, a JMS connection alias that you want the launch configuration to use to send the message must already exist.
Use the following procedure to create a re-usable launch configuration that you can run to publish a document as a JMS message to a JMS provider.
To create a launch configuration to publish a document as a JMS message
1. In Package Navigator view in the Service Development perspective, open the IS document type that you want to publish as a JMS message.
2. Select Run > Run Configurations to open the Run Configurations dialog box.
3. On the Configurations tree, select IS Document (Publish as JMS Message), and then click 
. A new configuration entry appears below IS Document (Publish as JMS Message) and the launch configuration options appear on the right-hand side of the dialog box.
4. In the Name field, enter a new name for your launch configuration. The Document tab displays the name of the Integration Server where the document resides as well as the name of the document that you want to publish.
You can change the document specified in the Document Type field by clicking Browse.
5. Click the JMS Settings tab and specify the JMS message details:
a. In the JMS connection alias name field, click 
. In the Select a JMS connection alias for documentName dialog box, select the JMS connection alias that you want this launch configuration to use to receive messages from the JMS provider. Click OK. If a JMS connection alias has not yet been configured on Integration Server, Designer displays a message stating the JMS subsystem has not been configured. For information about creating a JMS connection alias, see webMethods Integration Server Administrator’s Guide.
b. In the Destination name field, do one of the following to specify the destination:
If the JMS connection alias uses JNDI to retrieve administered objects, specify the lookup name of the Destination object.
If the JMS connection alias uses the native
webMethods API to connect directly to
Broker, specify the provider-specific name of the destination.
If the JMS connection alias creates a connection on
Broker or
Universal Messaging, click
to select from a list of existing destinations. After you select the destination, click
OK.
c. From the Destination type list, do the following:
Select
Queue to send the message to a particular queue.
Select
Topic to send the message to a topic.
You need to specify a destination type only if you specified a JMS connection alias name that uses the native webMethods API.
Note: Designer populates Destination type automatically if you selected a destination from the list of existing destinations on the JMS provider.
d. Select Prepare message for BPM to add information to the JMS message that enables Process Engine to start a process instance when it receives the message. When this check box is selected, the published JMS message includes the documentType property which specifies the fully qualified name of the IS document type used to create the JMS message. Process Engine uses the document type name to map the JMS message to the correct process model and start a process instance.
e. Under JMS Message Header and Properties, specify the values for the pre-defined and custom properties that you want to add to the JMS message header. Click 
to add a row to specify custom properties. Click 
to insert a row and 
to delete a row. 6. Click the Input tab and specify input values for the document, which will form the contents of the JMS message body.
a. Enter valid values for the fields defined in the document or click Load to retrieve the values from a file. For information about loading input values from a file, see Loading Input Values. b. 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 runs. For information about saving input values, see Saving Input Values. c. 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. Optionally, click the Common tab to define general information about the launch configuration and to save the launch configuration to a file.
8. Click Apply.
9. Click Run to run the launch configuration to publish the IS document as a JMS message now. Otherwise, click Close.