This chapter covers booting the application.
As with most procedures in this guide, we start by setting the environment. The variables particularly needed by which causes the prompt:
When you respond The display continues until all servers in the configuration have been started. It ends with a count of the number started.
There are options that can be used to boot only a portion of the configuration. For example, if the In addition to the report on servers booted, We have referred previously to the For more information about the Chapter 15, "Error Management," contains background information on the user of the userlog. In addition, throughout the guide there are examples of messages being sent to the log.
The following pages in Sections 1 and 3cbl of the BEA TUXEDO Reference Manual are important: Executing tmboot
tmboot are TUXCONFIG, APPDIR, and, of course, TUXDIR. The command to boot the complete application is simply:
tmboot
Boot all admin and server processes? (y/n): y
y to the prompt, you get a running report that starts like this:
Booting all admin and server processes in /usr/me/appdir/tuxconfig
Booting all admin processes ...
exec BBL -A:
process id=24223 ... Started.-A flag is used, only administrative servers are booted, but with no options specified, everything is booted.
tmboot also sends messages to the ULOG.
The Userlog: ULOG
ULOG, but this is the first time it has actually played an important role in the process under discussion. It is called ULOG (short for user log) because that is the default prefix; the actual file name of the log is ULOG followed by the date in the form: .mmddyy. Log messages can be directed to ULOG from user-written modules through a call to USERLOG(3cbl), but it is also used heavily by BEA TUXEDO system processes such as tmboot.
References
tmboot command, see Chapter 4, "Starting and Shutting Down Applications," in Administering the BEA TUXEDO System.
tmboot(1) and USERLOG(3cbl).