Copyright © Cloud Software Group, Inc. All Rights Reserved

ESB Channel

TIBCO API Exchange Gateway supports ESB transport to communicate with JMS servers both at facade and target side. ESB transport allows you to use JMS transport with XML messages and does not contain SOAP messages.

By default, you can define one ESB channel at facade side to process northbound requests. Similarly you can define three ESB channels at target side to process southbound requests. Each ESB channel is configured using the global variables specified in the ASG_CONFIG_HOME/asg.properties file.

You can add more ESB channels, if required using the custom extension mechanism.

Enable ESB Channels

By default, JMS channels are disabled. If they are enabled, the Core Engine tries to connect to JMS server on the startup. If you do not use the JMS transport, keep them disabled so that the Core Engine does not attempt to connect to EMS server. If you use the JMS transport, enable the JMS channels so that the Core Engine can connect to the EMS server when started.

To enable the JMS channels, follow these steps:

1.	Open the ASG_HOME/bin/asg_core.cdd file for editing in a text editor.

2.	Search the be.channel.deactivate property:

---

 

<property-group comment="" name="Channel">

<property name="be.channel.deactivate" value="/DefaultImplementation/Channels/SouthboundEsb0Channel,/DefaultImplementation/Channels/SouthboundEsb1Channel,/DefaultImplementation/Channels/SouthboundEsb2Channel,/DefaultImplementation/Channels/North_ESBChannel,/DefaultImplementation/Channels/North_HTTPChannel,/ASG/Channels/SOAPJMSChannel_North,/ASG/Channels/SOAPJMSChannel_South,/ASG/Channels/modAS_Channel,/Common/Channel/PSMChannel,/Common/Channel/CentralLoggerJMS"/>

---

 

3.	If you have not taken the backup of the be.channel.deactivate property, copy the be.channel.deactivate property to be.channel.deactivate.backup, as follows:

---

 

<property name="be.channel.deactivate.backup" value="/DefaultImplementation/Channels/SouthboundEsb0Channel,/DefaultImplementation/Channels/SouthboundEsb1Channel,/DefaultImplementation/Channels/SouthboundEsb2Channel,/DefaultImplementation/Channels/North_ESBChannel,/DefaultImplementation/Channels/North_HTTPChannel,/ASG/Channels/SOAPJMSChannel_North,/ASG/Channels/SOAPJMSChannel_South,/ASG/Channels/modAS_Channel,/Common/Channel/PSMChannel,/Common/Channel/CentralLoggerJMS"/>

---

 

4.	Enable the ESB channels as follows:

a.	To enable the northbound ESB channel, remove /DefaultImplementation/Channels/North_ESBChannel from the value of the be.channel.deactivate property. The modified value of the property is as follows:

---

 

<property name="be.channel.deactivate" value="/DefaultImplementation/Channels/SouthboundEsb0Channel,/DefaultImplementation/Channels/SouthboundEsb1Channel,/DefaultImplementation/Channels/SouthboundEsb2Channel,/DefaultImplementation/Channels/North_HTTPChannel,/ASG/Channels/SOAPJMSChannel_North,/ASG/Channels/SOAPJMSChannel_South,/ASG/Channels/modAS_Channel,/Common/Channel/PSMChannel,/Common/Channel/CentralLoggerJMS"/>

---

 

b.

To enable the southbound ESB channels, remove the /DefaultImplementation/Channels/SouthboundEsb0Channel,/DefaultImplementation/Channels/SouthboundEsb1Channel, ,/DefaultImplementation/Channels/SouthboundEsb2Channel from the value of the be.channel.deactivate property. The modified value of the property is as follows:

---

 

<property name="be.channel.deactivate" value="/DefaultImplementation/Channels/North_ESBChannel,/DefaultImplementation/Channels/North_HTTPChannel,/ASG/Channels/SOAPJMSChannel_North,/ASG/Channels/SOAPJMSChannel_South,/ASG/Channels/modAS_Channel,/Common/Channel/PSMChannel,/Common/Channel/CentralLoggerJMS"/>

---

 

5.	Save the changes to the file.

Edit asg.properties File

ASG_CONFIG_HOME/asg.properties file defines JMS server connections, queue names and the user details for ESB transport.

JMS Server Connection Parameters For ESB Channel

JMS server connection parameters are defined by the following properties. Edit the property as per your JMS server connection details.

JMS Server Connection Parameters at Facade Side

Following properties define the JMS server connection parameters for ESB channel used at the facade (northbound) side. Edit the properties values as per your JMS server settings.

Table 36: JMS Server Connection Parameters (facade)

Property Name	Default Value
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JMSProviderURL	tcp://localhost:7222
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JNDIContextURL	tibjmsnaming://localhost:7222
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/TopicConnectionFactoryName	TopicConnectionFactory
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/QueueConnectionFactoryName	QueueConnectionFactory
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JNDIUsername	admin
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JNDIPassword
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JMSUsername	admin
tibco.clientVar.Common/Connections/JMS/FacadeEsbConnection0/JMSPassword

JMS Server Connection Parameters At Target Side

Following properties define the JMS server connection parameters for ESB channels used at the target (southbound) side. By default, you can use three ESB channels at southbound side. Edit the properties values as per your JMS server settings.

Table 37: JMS Server Connection Parameters (Target)

Property Name	Default Value
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/JMSProviderURL	tcp://localhost:7222
tibco.clientVar.Common/Connections/JMS/SouthboundEsbConnection0/JNDIContextURL	tibjmsnaming://localhost:7222
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/TopicConnectionFactoryName	TopicConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/QueueConnectionFactoryName	QueueConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/JNDIUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/JNDIPassword
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/JMSUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection0/JMSPassword
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JMSProviderURL	tcp://localhost:7222
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JNDIContextURL	tibjmsnaming://localhost:7222
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/TopicConnectionFactoryName	TopicConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/QueueConnectionFactoryName	QueueConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JNDIUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JNDIPassword
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JMSUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection1/JMSPassword
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JMSProviderURL	tcp://localhost:7222
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JNDIContextURL	tibjmsnaming://localhost:7222
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/TopicConnectionFactoryName	TopicConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/QueueConnectionFactoryName	QueueConnectionFactory
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JNDIUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JNDIPassword
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JMSUsername	admin
tibco.clientVar.Common/Connections/JMS/TargetEsbConnection2/JMSPassword

Facade Queue Names For ESB Transport

The queue names for the ESB channel at facade side are defined by the following properties. Edit the default values, if needed.

Table 38: facade Queue Names (ESB)

Global Variable	Default Value
tibco.clientVar.ASG/facade/ESB0/requestQueue	asg.in.request
tibco.clientVar.ASG/facade/ESB0/replyQueue	asg.in.request.reply.0

Target Queue Names For ESB Transport

The queue names for the ESB channel at target side are defined by the following properties. Edit the default values, if needed:

Table 39: Target Queue Names (ESB)

Global Variable	Default Value
tibco.clientVar.ASG/Endpoint/ESB0/requestQueue	asg.out.request
tibco.clientVar.ASG/Endpoint/ESB0/replyQueue	asg.out.request.reply.0.0
tibco.clientVar.ASG/Endpoint/ESB1/requestQueue	asg.out.request
tibco.clientVar.ASG/Endpoint/ESB1/replyQueue	asg.out.request.reply.0.1
tibco.clientVar.ASG/Endpoint/ESB2/requestQueue	asg.out.request
tibco.clientVar.ASG/Endpoint/ESB2/replyQueue	asg.out.request.reply.0.2

Create queues on EMS Server

By default, TIBCO API Exchange Gateway uses the queue names for ESB transport as defined in the ASG_CONFIG_HOME/asg.properties file.

Create the following queues on the EMS server:

asg.out.request

asg.out.request.reply.0.0

asg.out.request.reply.0.1

asg.out.request.reply.0.2

• The queue names can be overwritten by editing the values of global variables as defined in the ASG_CONFIG_HOME/asg.properties file. If you changed the default values as mentioned in Facade Queue Names For ESB Transport and Target Queue Names For ESB Transport, you should create the queue names defined by the global variables. • You can edit the global variables values as follows: − Using the Config UI. See Set Runtime Properties for details. − Editing the ASG_CONFIG_HOME/asg.properties file using a text editor.

Create Users On EMS Server

Ask the EMS server administrator to create a normal user without administrator privileges. TIBCO API Exchange Gateway uses this user to connect to EMS server when ESB transport channel is used at facade and target side. The administrator should grant the following privileges to this user:

•

Send

•

Receive

•

Browse

This user is specified by the global variable properties in the ASG_CONFIG_HOME/asg.properties file. See JMS Server Connection Parameters For ESB Channel.

Copyright © Cloud Software Group, Inc. All Rights Reserved