[Top] [Previous] [Next] [End of Book]

# Chapter 5 . Starting BEA Connect TPS

## Setting Environment Variables

Before you attempt to use Connect TPS, you must set the ROOTDIR and PATH environment variables as the following example illustrates:

>     ROOTDIR=/usr/tuxedo; export ROOTDIR
>     PATH=$PATH:$ROOTDIR/bin; export PATH

Of course, you should set ROOTDIR to the actual path where your BEA TUXEDO and Connect TPS software is installed. You may also need to set the LANG environment variable if you have generated custom mapping tables and/or message catalogs. Some platforms may require that LANG always is set. Consult your operating system documentation for the appropriate LANG value.

## Invoking Connect TPS

Connect TPS is invoked when you boot the BEA TUXEDO system (by using the tmboot command). For example:

>     tmboot -y

Prior to using the tmboot command to invoke Connect TPS, you must configure the feature. See Chapter 3, "Installing and Getting Ready to Configure BEA Connect TPS," and Chapter 4, "Configuring BEA Connect TPS," for details.

## Testing Connectivity with Remote Regions

To test connectivity with remote BEA TUXEDO regions, you can invoke the following commands and subcommands in the following order:

1. The tmadmin command

2. The mode subcommand

3. The Connect TPS ping subcommand

See Chapter 6, "Administering BEA Connect TPS," for details.

Note: You cannot use the ping subcommand to test connectivity with systems which use gateways other than Connect TPS.

[Top] [Previous] [Next] [End of Book]