BEA Logo BEA Tuxedo Release 7.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   Tuxedo Doc Home   |   Getting Started   |   Topic List   |   Previous   |   Next   |   Contents

   Tutorials for Developing a BEA Tuxedo Application

Step 9: How to Create a Remote Service Connection on Each Machine

tlisten is the listener process that provides a remote service connection for processes such as tmboot between machines in a BEA Tuxedo application. It must be installed on all the machines in your network as defined in the NETWORK section of the configuration file.

Instructions for starting tlisten are provided in the Starting the tlisten Process on a UNIX System in Installing the BEA Tuxedo System.

  1. We recommend starting a separate tlisten process for bankapp. To do so, enter the following command.

        tlisten -l nlsaddr

    The nlsaddr value must be the same as that specified for the NLSADDR parameter for this machine in your configuration file. Because this value changes from one machine to another, it is important that your tlisten argument agrees with your configuration file specification.

    Note: Detection of an error in this specification is not easy. tmloadcf does not check for agreement between your configuration file and your tlisten command. If the two addresses do not match, then the application will probably fail to boot on the machine with the mismatched value of nlsaddr or on which the tlisten process has not been started.

The logfile used by tlisten is separate from all other BEA Tuxedo system log files, but one log can be used by more than one tlisten process. The default filename is TUXDIR/udataobj/tlog.

How to Stop the Listener Process (tlisten)

tlisten is designed to run as a daemon process. For suggestions about incorporating it in startup scripts or running it as a cron job, see tlisten(1) in the BEA Tuxedo Reference Manual.

For bankapp, you may prefer simply to start it and bring it down as you need it. To bring it down, send it a SIGTERM signal such as the following.

kill -15 pid

Note: In an NT environment, you can start and stop the listener process in two ways: using the tlisten on the command line or using the Control Panel.

Sample tlisten Error Messages

If no remote tlisten is running, the boot sequence is displayed on your screen as follows.

    Booting admin processes
exec DBBL -A :
on MASTER -> process id=17160Started.
exec BBL -A :
on MASTER -> process id=17161Started.
exec BBL -A :
on NONMAST2 -> CMDTUX_CAT:814: cannot propagate TUXCONFIG file
tmboot: WARNING: No BBL available on site NONMAST2.
Will not attempt to boot server processes on that site.
exec BBL -A :
on NONMAST1 -> CMDTUX_CAT:814: cannot propagate TUXCONFIG file
tmboot: WARNING: No BBL available on site NONMAST1.
Will not attempt to boot server processes on that site.
2 processes started.
and messages such as these will be in the ULOG:
133757.mach1!DBBL.17160: LIBTUX_CAT:262: std main starting
133800.mach1!BBL.17161: LIBTUX_CAT:262: std main starting
133804.mach1!BRIDGE.17162: LIBTUX_CAT:262: std main starting
133805.mach1!tmboot.17159: LIBTUX_CAT:278: Could not contact NLS on NONMAST2
133805.mach1!tmboot.17159: LIBTUX_CAT:276: No NLS available for remote
machine NONMAST2
133806.mach1!tmboot.17159: LIBTUX_CAT:276: No NLS available for remote
machine NONMAST2
133806.mach1!tmboot.17159: CMDTUX_CAT:850: Error sending TUXCONFIG
propagation request to TAGENT on NONMAST2
133806.mach1!tmboot.17159: WARNING: No BBL available on site NONMAST2.
Will not attempt to boot server processes on that site.
133806.mach1!tmboot.17159: LIBTUX_CAT:278: Could not contact NLS on NONMAST1
133806.mach1!tmboot.17159: LIBTUX_CAT:276: No NLS available for
remote machine NONMAST1
133806.mach1!tmboot.17159: LIBTUX_CAT:276: No NLS available for
remote machine NONMAST1
133806.mach1!tmboot.17159: CMDTUX_CAT:850: Error sending TUXCONFIG
propagation request to TAGENT on NONMAST1
133806.mach1!tmboot.17159: WARNING: No BBL available on site NONMAST1.
Will not attempt to boot server processes on that site.
If tlisten is started with the wrong machine address, the following messages
appear in the tlisten log.

    Mon Aug 26 10:51:56 1991; 14240; BEA TUXEDO System Listener Process Started
Mon Aug 26 10:51:56 1991; 14240; Could not establish listening endpoint
Mon Aug 26 10:51:56 1991; 14240; Terminating listener process, SIGTERM

See Also