Using Event-based Communication


	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

Tutorials for Developing a BEA Tuxedo Application

In event-based communication, events can also be posted to application queues, log files, and system commands. Any BEA Tuxedo client can subscribe to a user-defined event using the tpsubscribe() function and receive an unsolicited message whenever a BEA Tuxedo service or client issues a tppost() function. Clients can also subscribe to system-defined events that are triggered whenever the BEA Tuxedo system detects the event. When a server dies, for example, the .SysServerDied event is posted. No application server is needed to post this event, because it is performed by the BEA Tuxedo system.

Using Event-based Communication