Subscribing to an Event


	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

As the administrator for your BEA Tuxedo application, you can enter subscription requests on behalf of a client or server process through calls to the EVENT_MIB(5). You use tpsubscribe to subscribe to an event using the EventBroker. You may want to subscribe to Events A, B, and C and request to be informed when they occur.

Each subscription specifies one of the following notification methods:

Client notification-The EventBroker keeps track of the client's interest in these events and a client is notified in the form of unsolicited notification. Some events are anonymously posted. A client can join an application, independent of whether anyone else has subscribed, and post events to the EventBroker. The EventBroker matches these events against its database of subscriptions and sends an unsolicited notification to the appropriate clients.
Service calls-If the subscriber wants event notifications to go to service calls, then the ctl parameter must point to a valid TPEVCTL structure.
Message enqueuing to stable-storage queues-For subscriptions to stable-storage queues, the queue space, queue name, and correlation identifier are used, in addition to eventexpr and filter, when determining matches. The correlation identifier can be used to differentiate among several subscriptions for the same event expression and filter rule, destined for the same queue.
Placing messages on the ULOG-Using the T_EVENT_USERLOG class of EVENT_MIB, subscribers can write system USERLOG messages. When events are detected and matched, they are written to the USERLOG.
Command-line utilities-Using the T_EVENT_COMMAND class of EVENT_MIB, the EventBroker tracks and matches events. When a match is found, it is passed to the command used when subscribing to the event.
Note: Notification methods are determined by the subscriber process type and the arguments passed to tpsubscribe.

Subscribing to an Event