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

A client accesses the EventBroker through either of two servers provided by the BEA Tuxedo system: TMUSREVT(5), which handles application events, and TMSYSEVT(5), which handles system events. Both servers process events and trigger the sending of notification to subscribers.

To set up the BEA Tuxedo EventBroker on your system, you must configure either or both of these servers in the SERVERS section of the UBBCONFIG file, as shown in the following example.

  *SERVERS
    TMSYSEVT SRVGRP=ADMIN1 SRVID=100 RESTART=Y GRACE=900 MAXGEN=5 
      CLOPT="-A --" 
    TMSYSEVT SRVGRP=ADMIN2 SRVID=100 RESTART=Y GRACE=900 MAXGEN=5 
      CLOPT="-A -- -S -p 90"

    TMUSREVT SRVGRP=ADMIN1 SRVID=100 RESTART=Y
      MAXGEN=5 GRACE=3600 
      CLOPT="-A --" 
    TMUSREVT SRVGRP=ADMIN2 SRVID=100 RESTART=Y
      MAXGEN=5 GRACE=3600 
      CLOPT="-A -- -S -p 120"

We recommend that you assign the principal server to the MASTER site, even though either server can reside anywhere on your network.

Note: You can reduce the network traffic caused by event postings and notifications by assigning secondary servers to other machines in your network.