Starting BEA eLink TCP for Tuxedo

The following topics provide information about starting the BEA eLink for Mainframe TCP for Tuxedo (hereafter referenced as eLink TCP for Tuxedo) product:

Setting Environment Variables

Before you attempt to use eLink TCP for Tuxedo, you must set the TUXDIR and PATH environment variables as the following example illustrates.

Listing 6-1 Setting ROOTDIR and PATH Environment Variables

TUXDIR=/usr/tuxedo; export TUXDIR
PATH=$PATH:$TUXDIR/bin; export PATH
GWICONFIG=$APPDIR/gwiconfig;export GWICONFIG
BDMCONFIG=$APPDIR/bdmconfig;export BDMCONFIG
TUXCONFIG=$APPDIR/tuxconfig;export TUXCONFIG

You should set TUXDIR to the actual path where your BEA Tuxedo and eLink TCP for Tuxedo software is installed. Set APPDIR to the application directory, similar to the UBBCONFIG file. You may also need to set the LANG environment variable if you have generated custom mapping tables or message catalogs. Some platforms may require that LANG always is set. Consult your operating system documentation for the appropriate LANG value.

Invoking eLink TCP for Tuxedo

Listing 6-2 Invoking eLink TCP for Tuxedo Using tmboot

tmboot 

Administering the Gateways

BEA Tuxedo has a set of tmadmin and dmadmin commands for the administration of the eLink TCP for Tuxedo gateways. For detailed information about these commands, refer to the BEA Tuxedo Administrator's Guide and the BEA Tuxedo Domain User Guide.