Types of Events


	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

Types of Events

The BEA Tuxedo system supports two event types:

The following table identifies the differences between system and application-specific events.

Differences between System and Application-specific Events

Area	Differences
Events	System events are defined in advance by the BEA Tuxedo system code. For an application, designers decide which application events should be monitored. Application programs are written to: (a) detect when an event of interest has occurred, and (b) post the event to the EventBroker through tppost.
Event List	A list of the application event subscriptions is made available to interested users just as the BEA Tuxedo system provides a list of system events available to users with EVENTS(5). System event names begin with a dot ( . ); application-specific event names may not begin with a dot (.).
Subscriptions	Subscribing to an event in an application-specific event broker is similar to subscribing to the BEA Tuxedo System EventBroker. You subscribe by making calls to tpsubscribe using the published list of events for the application. EVENTS(5) lists the notification message generated by an event as well as the event name (used as an argument when tppost is called). Subscribers can use the wild card capability of regular expressions to make a single call to tpsubscribe that covers a whole category of events.