|
|
|
|
|
|
Starting the tlisten Process on a UNIX System
When used in a distributed environment, the BEA Tuxedo system must be able to start, shut down, and administer processes on remote nodes running BEA Tuxedo system servers. The tlisten(1) process provides this capability. Once tlisten is running, tmboot(1), for example, can start BEA Tuxedo system servers on remote nodes.
Note: For details on starting the Listener process on Windows NT systems, see Configuring tlisten Processes to Start Automatically in Using the BEA Tuxedo System on Windows NT.
tlisten is a generic listener process that operates with either of two network interfaces: Sockets or TLI. It runs as a daemon process. tlisten can be started by the:
In all cases the same basic syntax is used to invoke tlisten.
TUXDIR=tuxdir; export TUXDIR
LD_LIBRARY_PATH=libpath:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
$TUXDIR/bin/tlisten [-d devname] -l nlsaddr [-u appuid]
Note: If your system uses an environment variable other than LD_LIBRARY_PATH for the shared library path, specify that variable, instead.
The -l option is required. The argument to -l should match the value of the NLSADDR parameter in the NETWORK section of the configuration file. For information on determining the value of NLSADDR, refer to the following documentation:
Use the -u appuid option when the command is part of an installation script run by root. The value of appuid is the UID or login name of the BEA Tuxedo system administrator; the numeric version is the same as the value of the UID parameter in the RESOURCES section of the configuration file. This means that even though the tlisten process is started by root, it runs with the effective UID of the owner of the BEA Tuxedo system installation. If tlisten is started by the BEA Tuxedo system administrator, either manually or as a cron job, the -u option is unnecessary, since the job is already owned by the right account.
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|