![]() |
![]() |
BEA eLink TCP for TUXEDO 3.1 Information Center |
![]() HOME | SEARCH | CONTACT | PDF FILES | WHAT'S NEW |
||
![]() TABLE OF CONTENTS | PREVIOUS TOPIC | NEXT TOPIC | INDEX |
The following topics provide information about starting the BEA eLink for Mainframe TCP for TUXEDO (hereafter referenced as eLink TCP for TUXEDO) product:
Before you attempt to use eLink TCP for TUXEDO, you must set the TUXDIR and PATH environment variables as the following example illustrates.
Setting Environment Variables
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.
Perform a tmloadcf
and dmloadcf
to load the UBBCONFIG and the DMCONFIG files. Invoke eLink TCP for TUXEDO using the tmboot
command to boot the BEA TUXEDO system. Be sure to configure eLink TCP for TUXEDO prior to using the tmboot
command. For details, see "Configuring BEA eLink TCP for TUXEDO."
Listing 6-2 Invoking eLink TCP for TUXEDO Using tmboot
tmboot -y
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.