Ways to Monitor Your Application


	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

As an administrator, you must ensure that once an application is up and running, it continues to meet the performance, availability, and security requirements set by your company. To perform this task, you need to monitor the resources (such as shared memory), activities (such as transactions), and potential problems (such as security breaches) in your configuration, and take any necessary corrective actions.

To help you meet this responsibility, the BEA Tuxedo system provides several methods for monitoring system and application events, and dynamically reconfiguring your system to improve performance. The BEA Administration Console, command-line utilities, log files, the ATMI, the MIB, and a run-time tracing facility offer an excellent view of how a system is working. They help make your application capable of responding quickly and efficiently to changing business needs or failure conditions. You can use these tools to keep your application performing fast, well, and securely.

Monitoring Tools

The BEA Tuxedo system offers the following tools to monitor your application:

BEA Administration Console—a Web-based graphical user interface you can use to observe the behavior of the application, and to dynamically configure its operation. You can display and change configuration information, determine the state of each component of the system, and obtain statistical information about items such as executed requests, and queued requests.
Command-line utilities—a set of commands (for example, tmboot(1), tmadmin(1), and tmshutdown(1)) you can use to activate, deactivate, configure, and manage your application.
EventBroker—a mechanism that informs administrators of system faults and exceptional happenings such as network failures. When an event is posted by clients or servers, the EventBroker matches the name of the posted event to a list of subscribers for that event, and takes appropriate action, determined by each subscription.
Log files—a set of files that make up a repository for error and warning messages, debugging messages, and informational messages helpful in tracking and resolving problems in the system.
MIB—an interface to a set of procedures for accessing and modifying information in the MIBs. Using the MIB, you can write programs that enable you to monitor your run-time application.
Run-time tracing facility—software that tracks the execution of an application, thus providing information that is helpful in resolving system problems.

See Also

System and Application Data That You Can Monitor
Selecting Appropriate Monitoring Tools
Using the BEA Administration Console to Monitor Your Application
Using the BEA Administration Console in Introducing BEA Tuxedo ATMI
Using Command-line Utilities to Monitor Your Application
Using EventBroker to Monitor Your Application
Using Log Files to Monitor Activity
Using the ATMI to Handle System and Application Errors
Using the MIB to Monitor Your Application
Managing Operations Using the MIB in Introducing BEA Tuxedo ATMI
Using the Run-time Tracing Utility
tmshutdown(1) in the BEA Tuxedo Command Reference