Troubleshooting

If the tests associated with the Tuxedo domain server are in UNKNOWN state, it could indicate any/all of the following:

1. The eG agent has not been started.

   If the eG agent executing the Tuxedo tests has not been started, then, the tests will not get executed. In such a case, proceed to start the eG agent. Refer to the eG Installation Manual for the procedure for starting an eG agent on Windows and Unix environments.

2. The Tuxedo domain server being monitored has not been started

   If the eG agent has already been started, then verify whether the Tuxedo domain server has been started or not. To check this, perform the following steps:

3. In a Windows installation of the Tuxedo server, set the following environment variables for the application being monitored:

   set TUXDIR=pathname_of_BEA_Tuxedo_product_directory

   set APPDIR=pathname_of_BEA_Tuxedo_application_directory

   set TUXCONFIG=pathname_of_TUXCONFIG_file

   set WEBJAVADIR=%TUXDIR%\udataobj\webgui\java

   set PATH=%APPDIR%;%TUXDIR%\bin;\bin;%PATH%

   Examples of TUXDIR, APPDIR, and TUXCONFIG are:

   TUXDIR=C:\bea\tuxedo8.1

   APPDIR=C:\home\me\simpapp

   TUXCONFIG=%APPDIR%\tuxconfig

4. On a Unix server machine, set and export the following environment variables for the application being monitored:

   TUXDIR=pathname_of_BEA_Tuxedo_product_directory

   APPDIR=pathname_of_BEA_Tuxedo_application_directory

   TUXCONFIG=pathname_of_TUXCONFIG_file

   WEBJAVADIR=$TUXDIR/udataobj/webgui/java

   PATH=$APPDIR:$TUXDIR/bin:/bin:$PATH

   LD_LIBRARY_PATH=$APPDIR:$TUXDIR/lib:/lib:/usr/lib:$LD_LIBRARY_PATH

   export TUXDIR APPDIR TUXCONFIG WEBJAVADIR PATH LD_LIBRARY_PATH

   Note:

   For HP-UX systems only, use SHLIB_PATH instead of LD_LIBRARY_PATH.

   Examples of TUXDIR, APPDIR, and TUXCONFIG are:

   TUXDIR=/home/bea/tuxedo8.1

   APPDIR=/home/me/simpapp

   TUXCONFIG=$APPDIR/tuxconfig

   The TUXDIR, APPDIR, and TUXCONFIG environment variables (in both Windows and Unix) must match the values of the TUXDIR, APPDIR, and TUXCONFIG parameters in the MACHINES section of the UBBCONFIG file of the corresponding application. This config file will be present in the APPDIR of the application being monitored.

5. After setting the variables properly, start the Tuxedo server by executing the following command from the command prompt:

   tmboot –y

   If the Tuxedo server has been started for the first time, then the following output will appear:

   Booting all admin and server processes in C:\home\me\atmi\tuxconfig

   INFO: BEA Tuxedo(r) System Release 8.1

   INFO: Serial #: 000102-9125503751, Maxusers 25

   Booting admin processes ...

   exec BBL -A:

   process id=24180 ... Started.

   Booting server processes ...

   exec simpserv -A :

   process id=24181 ... Started.

   2 processes started.

   If the Tuxedo server had already been started, then a message to that effect will appear.

6. If the Tuxedo domain server has already been started, then it could indicate that the Tuxedo tests have not been configured properly.

   While configuring Tuxedo tests, ensure that the TuxConfig and TuxDir parameters contain the same value as the TUXCONFIG and TUXDIR environment variables set earlier. In Unix environments, make sure that the value of the TuxLibPath parameter matches with the value of the environment variable ld_library_path.