Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Getting Started   |   Topic List   |   Previous   |   Next   |   Contents

   Introducing the BEA Tuxedo System

The user log (ULOG) is a file to which all messages generated by the BEA Tuxedo system-error messages, warning messages, information messages, and debugging messages-are written. Application clients and servers can also write to the user log. A new log is created every day and there can be a different log on each machine. However, a ULOG can be shared by multiple machines when a remote file system is being used.

The ULOG provides an administrator with a record of system events from which the causes of most BEA Tuxedo system and application failures can be determined. You can view the ULOG, a text file, with any text editor. The ULOG also contains messages generated by the tlisten process. The tlisten process provides remote service connections for other machines. Each machine, including the master machine, should have a tlisten process running on it.

A ULOG is created by the BEA Tuxedo system whenever one of the following activities occurs:

• A new configuration file is loaded.

• An application is booted.

Example of a ULOG Message

The following is an example of a ULOG message.

121449.gumby!simpserv.27190.1.0: LIBTUX_CAT:262: std main starting

A ULOG message consists of two parts: a tag and text.

The tag consists of the following:

• A 6-digit string (hhmmss) representing the time of day (in terms of hour, minute, and second)

• The name of the machine (as returned, on UNIX systems, by the uname -n command)

• The name and process identifier of the process that is logging the message. (This process ID can optionally include a transaction ID.) Also included is a thread ID (1) and a context ID (0).

  Note: Placeholders are printed in the thread_ID and context_ID field of entries for single-threaded applications. (Whether an application is multithreaded is not apparent until more than one thread is used.)

The text consists of the following:

• The name of the message catalog

• The message number

• The BEA Tuxedo system message

  The Tag Indicates	The Text Indicates
  The message was written into the log at approximately 12:15 P.M. The machine on which the error occurred was gumby. The message was logged by the simpserv process, which has a process ID of 27190. The thread ID is 1. The context ID is 0.	The message came from the LIBTUX catalog. The number of the message is 262. The message itself reads as follows: std main starting.

  Note: For more information about a message, note its catalog name and number. With this information, you can look up the message in the appropriate catalog.

Where the ULOG Resides

By default, the user log is called ULOG.mmddyy (where mmddyy represents the date in terms of month, day, and year) and it is created in the $APPDIR directory. You can place this file in any location, however, by setting the ULOGPFX parameter in the MACHINES section of the UBBCONFIG file.