Postinstallation Tasks

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 2 Installing TIBCO API Exchange Gateway : Postinstallation Tasks

Postinstallation Tasks

This section explains some postinstallation steps that you might have to perform in your installation.

Set System Environment Variables

After the product is installed, ensure that the following system variables are set appropriately. If they are not set, define them correctly, as indicated for both Windows and UNIX platforms.

On Windows Platform

After the product is installed, verify that the PATH system variable includes RV_HOME/bin, where RV_HOME specifies the directory into which the TIBCO Rendezvous product is installed.

On UNIX Platform

After the product is installed, ensure that the following environment variables are set correctly. Depending on the type of shell, you might have to use different commands to set these variables.

•

RV_HOME: Verify that this variable is set to the directory into which TIBCO Rendezvous is installed. If not, set it as follows:

   export RV_HOME=directory where the TIBCO Rendezvous product is installed.

•

PATH: Verify that this variable includes $RV_HOME/bin. If not, set it as follows:

   export PATH=$RV_HOME/bin:$PATH

•

LD_LIBRARY_PATH: Verify that this variable includes $RV_HOME/lib. If not, set it as follows:

   export LD_LIBRARY_PATH=$RV_HOME/lib/64:$RV_HOME/lib:$LD_LIBRARY_PATH

If you use the EMS channels with TIBCO API Exchange Gateway, do one of the following:

•

Verify that the property tibco.env.EMS_HOME is set to the TIBCO Enterprise Message Service installation home. This property is defined in the ASG_HOME/bin/asg-engine.tra file.

For example,

tibco.env.EMS_HOME=/home/asg/tibco/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

Install and Configure Apache HTTP Server (Optional)

See Appendix A, Configuring Third Party Software.

Configure TIBCO Enterprise Message Service (Optional)

If you use the EMS channels with TIBCO API Exchange Gateway, perform the following tasks:

Task A 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=c:/tibco/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

Task B Enable the ESB Channels in the CDD file

By default, the ESB channels are disabled. To enable the channels, follow these steps:

1.

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

2.

Search the following 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.

Copy the property be.channel.deactivate 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.

Task C Create Users on JMS Server

Ask your JMS server administrator to create a regular user (not an administrator). The Core Engine uses this user to connect to the JMS server when the JMS transport is used at the facade and target side. The administrator should grant the following privileges to this user:

•

Send

•

Receive

•

Browse

This user is specified by the runtime property in the ASG_CONFIG_HOME/asg.properties file. Refer to Engine Runtime Properties in TIBCO API Exchange Gateway User’s Guide.

Task D Create Queues on EMS Server

1.

Make sure that TIBCO Enterprise Message Service is running.

2.

Create the following queues in the TIBCO EMS server. For example, using tibemsadmin tool:

   create queue asg.out.request

   create queue asg.out.request.reply.0.0

   create queue asg.out.request.reply.0.1

   create queue asg.out.request.reply.0.2

   create queue asg.in.request

   create queue asg.in.request.reply.0

   create queue asg.soap.in.request

   create queue asg.soap.in.request.reply.0

   create queue asg.soap.forward

   create queue asg.soap.forward.reply.0

The default configuration assumes that TIBCO Enterprise Message Service is running on the localhost and port 7222. Depending on the host and port where the EMS server runs, edit the EMS server configuration parameters in the ASG_CONFIG_HOME/asg.properties file.