Option 1: Reconfigure the Applications


	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

Using the BEA Tuxedo Domains Component

One solution is to combine two BEA Tuxedo applications into one, as shown in the following figure.

Combining Two BEA Tuxedo System Applications

In the process of combining the two applications into a single configuration, the following changes are made:

OPTION=LAN is specified and a NETWORK section is included.
Server migration is enabled by specifying OPTION=MIGRATE; at the same time a backup master site is defined.
The gateway server is redefined as three other servers: TLRA, ACCTA, and CRDT.
Credit Authorization services are added.

Configuration File for Combining the Sample Applications

The following code shows a possible configuration file for the combined applications.

Sample Configuration File for the Combined Application

*RESOURCES
IPCKEY 76666
UID 0000
GID 000
PERM 0660
MAXACCESSERS 40
MAXSERVERS 35
MAXSERVICES 75
MAXCONV 10
MASTER SITE1,SITE2
SCANUNIT 10
MODEL MP
LDBAL Y
OPTIONS LAN,MIGRATE
MAXGTT 100
MAXBUFTYPE 16
SCANUNIT 10
SANITYSCAN 5
DBBLWAIT 6
BBLQUERY 50
BLOCKTIME 2
#
#
*MACHINES
#
mach1 LMID=SITE1
TUXDIR="/home/mylogin/tuxroot"
APPDIR="/home/mylogin/bankapp"
ENVFILE="/home/mylogin/bankapp/ENVFILE"
TLOGDEVICE="/home/mylogin/bankapp/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home/mylogin/bankapp/tuxconfig"
ULOGPFX="/home/mylogin/bankapp/ULOG"
TYPE="type1"
#
mach2 LMID=SITE2
TUXDIR="/home/mylogin/tuxroot"
APPDIR="/home/mylogin/bankapp"
ENVFILE="/home/mylogin/bankapp/ENVFILE"
TLOGDEVICE="/home/mylogin/bankapp/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home/mylogin/bankapp/tuxconfig"
ULOGPFX="/home/mylogin/bankapp/ULOG"
TYPE="type2"
#
mach3 LMID=SITE3
TUXDIR="/home/mylogin/tuxroot"
APPDIR="/home/mylogin/bankapp"
ENVFILE="/home/mylogin/bankapp/ENVFILE"
TLOGDEVICE="/home/mylogin/bankapp/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home/mylogin/bankapp/tuxconfig"
ULOGPFX="/home/mylogin/bankapp/ULOG"
TYPE="type2"
#
mach4 LMID=SITE4
TUXDIR="/home/mylogin/tuxroot"
APPDIR="/home/mylogin/bankapp"
ENVFILE="/home/mylogin/bankapp/ENVFILE"
TLOGDEVICE="/home/mylogin/bankapp/TLOG"
TLOGNAME=TLOG
TUXCONFIG="/home/mylogin/bankapp/tuxconfig"
ULOGPFX="/home/mylogin/bankapp/ULOG"
TYPE="type1"
#
*GROUPS
#
DEFAULT: TMSNAME=TMS_SQL TMSCOUNT=2
BANKB1 LMID=SITE1 GRPNO=1
OPENINFO="TUXEDO/SQL:/home/mylogin/bankapp/bankdl1:bankdb:readwrite"
BANKB2 LMID=SITE2 GRPNO=2
OPENINFO="TUXEDO/SQL:/home/mylogin/bankapp/bankdl2:bankdb:readwrite"
BANKB3 LMID=SITE3 GRPNO=3
OPENINFO="TUXEDO/SQL:/home/mylogin/bankapp/bankdl3:bankdb:readwrite"
BANKB4 LMID=SITE4 GRPNO=4
OPENINFO="TUXEDO/SQL:/home/mylogin/bankapp/bankdl4:bankdb:readwrite"
#
#
*NETWORK
#
SITE1 NADDR="<network address of SITE1>"
BRIDGE="<device of provider1>"
NLSADDR="<network listener address of SITE1>"
SITE2 NADDR="<network address of SITE2>"
BRIDGE="<device of provider2>"
NLSADDR="<network listener address of SITE2>"
SITE3 NADDR="<network address of SITE3>"
BRIDGE="<device of provider3>"
NLSADDR="<network listener address of SITE3>"
SITE4 NADDR="<network address of SITE4>"
BRIDGE="<device of provider4>"
NLSADDR="<network listener address of SITE4>"
#
*SERVERS
#
DEFAULT: RESTA

Limitations of Option 1

Administering a single large application can be more cumbersome than administering two smaller ones; each smaller one has its own administrative interface.
Booting a networked application can be more costly because of the time required to boot each server and because of the need to propagate bulletin boards across the network. Smaller, separate applications can be booted simultaneously.