Copyright © Cloud Software Group, Inc. All Rights Reserved

Configuring JMS Northbound Transport for XML

This section describes the steps to configure the JMS transport on the northbound side for XML message.

TIBCO Designer Configuration

In this scenario, TIBCO BusinessWorks is used as a client to send the XML payload to theAPI Exchange Gateway engine using the JMS transport.

1.	Open the TIBCO Designer and create a new project.

2.	Create a new JMS Application Properties activity resource. Type a name for this resource (for example, JMSProperty1) Add a new property for this resource as follows:

−	PropertyName: Operation

−	Type: string

−	Cardinality: required

3.	Create a new Process Definition. Type a name for this process (for example, SendJMSMessage).

4.	Create a new activity JMS Queue Requestor resource in the process. Type a name for this resource (for example, SendJMSRequest). Configure the JMS Queue Requestor resource as follows:

−	Configure the JMS Connection parameter. Select a pre-configured JMS connection resource.

−	Click the Advanced tab. For the JMS Application Properties field, select the configured JMS Application Properties resource (for example, JMSProperty1). Click Apply.

−	Click the Input tab. Verify that the Operation field appears under OtherProperties. Specify a value for the Operation. This value of the operation field matches the SOAP Action parameter of the operation configuration in the facade Operations tab of the gateway configuration UI.

−	Click Apply and Save the project.

Operations Configuration

1.	Start the Config UI.

2.	Click Facade Operations tab. Configure a new operation as follows:

•	Operation Name: Any logical name. For example, getLocationBW.

•	SOAP Action: Specify the value of this parameter to prepend /ESB followed by the value of Operation, a JMS application property.

For example, if the value of Operation (JMS application property) is specified as getLocation, type the value of SOAP Action parameter as /ESB/getLocation. Operation is identified by Operation/SOAP Action.

3.	Click Save to save the configuration.

Enable the ESB Channels in CDD File

By default, the ESB channels are disabled. To enable the channels, see Enable ESB Channels.

Update TIBCO Enterprise Message Service Libraries

To include the TIBCO Enterprise Message Service libraries, perform only one of the following steps:

•	Open the ASG_HOME/bin/asg-engine.tra file for editing. Set the tibco.env.EMS_HOME property to the TIBCO Enterprise Message Service installation home.

For example,

tibco.env.EMS_HOME=/home/asg/tibcoasg/ems/5.1

•	Copy the jms.jar and tibjms.jar files from TIBCO Enterprise Message Service installation (EMS_HOME/lib) to ASG_HOME/lib/ext/tpcl

Copyright © Cloud Software Group, Inc. All Rights Reserved