TUXDIR

Set to the directory where Tuxedo is installed.
Example:
setenv TUXDIR/opt/tuxedo/9.1

PATH

Set to the search path for commands. This should include $TUXDIR/bin.
Example:
setenv PATH $TUXDIR/bin;$PATH

INCLUDE

Set to the directory for Tuxedo header files. This should include $TUXDIR/include.
Example:
Setenv INCLUDE $TUXDIR/include;$INCLUDE

SHLIB_PATH

Set to the directory for Tuxedo library files. This should include $TUXDIR/lib.
Example:
setenv SHLIB_PATH $TUXDIR/lib;$SHLIB_PATH

Note: This is a system dependent environment variable used to indicate the location of the shared libraries. Use LD_LIBRARY_PATH on Solaris, LIBPATH on AIX.

TUXCONFIG

Set to the full pathname of the binary configuration file that results from the UBBCONFIG file described in the following sections.
Example:
setenv TUXCONFIG=<model directory>/inqload/tuxconfig

VIEWDIR32

Set to a semi-colon separated list of directories specifying the directory location of the view object files.
Example:
setenv VIEWDIR32=<model directory>/inqload

Note: This is not needed for clients using TCP/IP or CA Gen as the communication type. See the chapter "Tuxedo Proxy Client (ieftuxcl)" for setup information.

VIEWFILES32

Set to a comma-separated list of view object filenames generated for the application.
Example:
VIEWFILES32=<Pstep1>.V, <Pstep2>.V,...

Note: This is not needed for clients using TCP/IP or CA Gen as the communication type. For setup information, see the chapter “Tuxedo Proxy Client (ieftuxcl).”

AEPATH

Search path for executable load modules.

Set to a semicolon-delimited list of directory paths that indicate a search order for the user's application directories.

Example:

AEPATH=[directory_1;directory_2;...directory_n]

Note: It is expected that each directory on the AEPATH contains an inqload directory where the executable load modules should reside.

CLASSPATH

Set of colon separated jolt jar files (jolt.jar, joltadmin.jar, joltjse.jar).

Example:

CLASSPATH=$TUXDIR/udataobj/jolt/jolt.jar:…:$CLASSPATH

Note: This is needed for enabling Java-based clients access to Tuxedo Application Servers, either through the Java Proxy or Web Generation.