Managing System Events Using EventBroker


	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

Managing System Events Using EventBroker

The BEA Tuxedo EventBroker performs the following tasks:

Monitors events and notifies subscribers when events are posted via tppost(3c).
Keeps an administrator informed of changes in an application by tracking events.
Enhances event monitoring by providing a system-wide summary of events.
Provides a mechanism through which an event can trigger a variety of notification activities.

The EventBroker recognizes over 100 meaningful state transitions in a MIB object as system events. The postings for system events include the current MIB representation of the object on which the event has occurred, and some event-specific fields that identify the event that occurred. For example, if a machine is partitioned, an event is posted with the following information:

The name of a machine class object (T_MACHINE), with all the attributes of that machine
Some event attributes identifying the event as machine partitioned

You can use the EventBroker simply by subscribing to system events. Then, instead of having to query for MIB records, you can be informed automatically when events occur in the MIB by receiving FML data buffers representing MIB objects.

See Also

What Is an Event
Subscribing to an Event
Types of Events
Using Event-based Communication in Tutorials for Developing a BEA Tuxedo Application

Copyright © 2000 BEA Systems, Inc. All rights reserved.
Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.