Selecting Appropriate Monitoring Tools


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Administering a BEA Tuxedo Application at Run Time \| Local Topics \| Previous Topic \| Next Topic \| Contents

To monitor a running application, you need to keep track of the dynamic aspects of your configuration and sometimes check the static data. In other words, you need to be able to watch the bulletin board on an ongoing basis and consult the UBBCONFIG file when necessary. The method you choose depends on the following factors:

Your BEA Tuxedo system administration experience: If you have a lot of experience as an administrator, as well as shell programming expertise, you may prefer to write programs that automate your most frequently run commands.
Your operating system experience: If you are inexperienced, you may be more comfortable using the BEA Administration Console.
Which information you want to view: If you decide to monitor your application by examining the RESOURCES section of the UBBCONFIG file through the tmadmin command, you will have access to only the current values.

The following table describes how to use each monitoring method.

Use This Method...	By...
BEA Administration Console	Using a graphical interface.
Command-line utilities, such as txrpt and tmadmin	Entering commands after a prompt.
EventBroker	Subscribing to BEA Tuxedo system events, such as servers dying, and network failures.
Log files (for example, ULOG, TLOG)	Viewing the ULOG with any text editor; checking the ULOG for tlisten messages; and converting the TLOG (a binary file) to a text file by running tmadmin dumptlog which downloads a TLOG to a text file.
MIB	Writing programs that monitor your run-time application.
Run-time tracing utility	Specifying a tracing expression that contains a category, a filtering expression, and an action, and enabling the TMTRACE environment variable. For more information, see Using the Run-time Tracing Utility.