SNMP Agent MIB Reference
|
 |
 |
|
|
 |
 |
EventBroker MIB
There are two types of BEA Tuxedo events: application events and system events. Application events are usually controlled or trapped by the application code. System events are generated by the Tuxedo run-time system when important changes in that system are detected. Application programs (clients or services) can subscribe to these system events.
The EventBroker MIB defines the characteristics of an event subscription. You can use the EventBroker MIB to obtain the characteristics of current event subscriptions, define new subscriptions, or invalidate subscriptions. To enable both system event and application event notification, you need to define the system event broker and the application event broker in the Core MIB.
Event subscriptions can be temporary or persistent. Persistent subscriptions survive across application activations and can be removed through the EventBroker MIB. The Tuxedo EventBroker MIB contains five groups of event subscriptions through which the EventBroker can be managed.
The EventBroker MIB consists of the following subscription groups.
Each object in these groups represents a single subscription request. Client Notifications (tuxEventClientTbl group) indicate which events trigger an unsolicited message to a client. Service Notifications (tuxEventSvcTbl group) indicate which events trigger a request to an application service. Application Queue Notifications (tuxEventQueTbl group) indicate which events send a message to an application queue. System Command Notifications (tuxEventCmdTbl group) indicate which events trigger an operating system command. Log File Notifications (tuxEventUlogTbl group) indicate which events generate a record in the central event log (ulog). The EventBroker automatically removes temporary subscriptions when it detects that the corresponding target is no longer active.
Event subscriptions and the ability to change the Tuxedo MIB enables system administrators and application designers to write event-adaptive applications. When a failure is detected through a system event notification, a management framework program can perform the corrective measures. For example, a management framework task can be triggered to activate servers on a backup machine when it receives an event notification about a failure on a primary machine.
tuxEventClientTbl
This group contains objects that represent subscriptions registered with the EventBroker for client-based notification.
When an event is detected, it is compared to each tuxEventClientTbl instance. If the event name matches the value in the event expression and the optional filter rule is true, then the event buffer is sent to the specified client's unsolicited message handling routine. To create a new row in this table, it is necessary to issue a SET request that at least specifies the values for tuxEventClientExpr and tuxEventClientId.
