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   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Administering a BEA Tuxedo Application at Run Time

The EventBroker enhances troubleshooting by providing a system-wide summary of events and a mechanism whereby an event triggers notification. The EventBroker provides details about BEA Tuxedo system events, such as servers dying and networks failing, or application events, such as an ATM machine running out of money. A BEA Tuxedo client that receives unsolicited notification of an event, can name a service routine to be invoked, or name an application queue in which data should be stored for later processing. A BEA Tuxedo server that receives unsolicited notification can specify a service request or name an application queue to store data.

1. To send an unsolicited message, enter the following command.

   broadcast (bcst) [-m machine] [-u usrname] [-c cltname] [text] 

   Note: By default, the message is sent to all clients.

2. You can limit distribution to one of the following recipients:

   • One machine (-m machine)

   • One client group (-c client_group)

   • One user (-u user)

The text may not include more than 80 characters. The system sends the message in a STRING type buffer, which means the client's unsolicited message handling function (specified by tpsetunsol(0)) must be able to handle this type of message. The tptypes() function may be useful in this case.

• What Is Unsolicited Communication in Introducing the BEA Tuxedo System

• Managing System Events Using EventBroker in Introducing the BEA Tuxedo System