BEA Logo BEA Tuxedo Release 7.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   Tuxedo Doc Home   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Using the BEA Tuxedo Domains Component

Planning to Build Domains from Multiple BEA Tuxedo Applications

Suppose a bank has developed the two BEA Tuxedo applications shown in the following figure: bankapp and a credit card authorization center.

Two BEA Tuxedo Applications

The bankapp application connects ATMs at various bank branches to the central bank office. The Credit Card Authorization Center processes applications for credit cards. Over time, the bank realizes that their customers would be better served if the bankapp application could communicate directly with the credit card authorization application. In this way, they could offer instant credit cards to anyone opening a new account.

bankapp is distributed as a sample application with the BEA Tuxedo software. The credit card authorization application is a hypothetical extension of bankapp.

Take a look at the configuration file (represented in the following sample code) to see how to implement bankapp as a multiprocessor application: TUXDIR/apps/bankapp/ubbmp.

You have the following options: