This chapter describes how to prepare to boot You will find that most of the material applies to a networked application, that is, a configuration with more than one machine. If you are bringing As with all the steps since Chapter 2, "bankapp Files," of this guide, you should be in the directory in which your Once the configuration file has been edited to your satisfaction, it must be loaded to a binary file on your There is a If you have specified The
Note:
In a production environment, the device list may be the same as that used for the database. (See Administering the BEA TUXEDO System.)
There is a script in On all other machines, do not specify If you are using a non-XA resource manager, there is no requirement for a transaction log so you may skip this step.
Starting where devname is the device name of your network provider. This is apt to be The The nlsaddr value must be the same as that specified for the
Note:
Detection of an error in this specification is not easy. If no remote and messages such as these will be in the If For more information about For examples of network addresses, see Chapter 6, "Building Networked Applications," in Administering the BEA TUXEDO System.
Installation of The following pages in the BEA TUXEDO Reference Manual are important.
Creating tuxconfig, tlog tlisten
bankapp.
bankapp up in SHM mode, you do not have to be concerned about the tlisten process or about creating a TLOG on another machine.
bankapp files are located and you must set the environment by entering.
. ./bankvar
Loading the Configuration File
MASTER node. The binary configuration file has a file name of tuxconfig; its pathname relative to APPDIR is in the environment variable, TUXCONFIG. The file should be created by a person with the effective user ID and group ID of the BEA TUXEDO system administrator, which should be the same as the UID and GID values in your configuration file. If these conditions are not observed, you may run into permission problems in running bankapp. The command line for creating tuxconfig is:
tmloadcf ubbmp
-y option to suppress prompts that ask if you really want to install TUXCONFIG or to overwrite it if it already exists. There is a -c option that calculates the numbers for IPC resources the configuration requires.
tuxconfig needs to be installed only on the MASTER node; it is propagated to other nodes by tmboot when the application is booted.
SECURITY as an option for the configuration, tmloadcf prompts you to enter an application password. The password you select can be up to 30 characters long. Client processes joining the application will be required to supply the password.
tmloadcf parses the ASCII configuration file for syntax errors before it loads it, so if there are errors in the file, the job fails.
Creating the TLOG
TLOG is the transaction log needed by the BEA TUXEDO system in the management of global transactions. Before an application can be booted an entry for the TLOG must be created on all nodes of the application, and a file for the log itself must be created on the MASTER node.
bankapp called crtlog that creates the device list and the TLOG for you. The device list is created using the TLOGDEVICE variable from bankvar. On the MASTER node, enter the command as follows.
crtlog -m
-m; when the system is booted, the BBL on each non-MASTER node creates the log.
Starting tlisten
tlisten is the ProductName listener process that provides a remote service connection between nodes of an application for ProductName processes such as tmboot. It must be installed on all nodes of your network as defined in the NETWORK page of the configuration file.
tlisten is described in more detail in the BEA TUXEDO Installation Guide, as a step in the installation of the ProductName software. For the purposes of running bankapp you may prefer to start a separate instance. It can be done with a command like this.
tlisten -d /dev/devname -l nlsaddr
/dev/tcp. (If your provider is Sockets, the -d option is not needed.)
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.
NLSADDR parameter for this machine in your configuration file. As noted in the previous chapter, this value changes from one machine to another; it is important that your tlisten arguments agree with your configuration file specification.
tmloadcf does not check for agreement between your configuration file and your tlisten command. The symptom is most likely to be that the application fails to boot on the machine where the mismatch in nlsaddr values occurs or where the tlisten process has not been started.
Stopping tlisten
tlisten is designed to run as a daemon process. The reference page has some suggestions about incorporating it in startup scripts or running it as a cron job. 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 like this.
kill -15 pid
Error Messages from tlisten Problems
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 filetmboot: 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 filetmboot: WARNING: No BBL available on site NONMAST1.
Will not attempt to boot server processes on that site.2 processes started.
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.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 References
tlisten and the TLOG, see Chapter 15, "Monitoring Log Files," in Administering the BEA TUXEDO System.
tlisten is covered, as noted above, in the BEA TUXEDO Installation Guide.