BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT

 

   Tuxedo Documentation   |   Tutorials for Developing BEA Tuxedo ATMI Applications   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents

 


Using Event-based Communication

In event-based communication, events can also be posted to application queues, log files, and system commands. Any BEA Tuxedo ATMI 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. ATMI 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


 

See Also

 

back to top   next page