How To Be Sure At Run Time What Is The Master Machine In A MASTER/BACKUP Configuration?

(Doc ID 1386943.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version: 10.3.0 and later   [Release: and later ]
Information in this document applies to any platform.

Goal

In case of a Tuxedo application span over several machines, one machine must be defined as MASTER machine and a second one can be (this is not mandatory) the BACKUP machine.
   
A master/backup configuration allows to bring down the MASTER machine without shutting down the application.  This is realized by migration of MASTER machine.  After migration the backup machine becomes the MASTER machine and the initial master machine becomes the BACKUP machine.

After several migrations master becoming backup, backup becoming master and so on, the following question can be raised :

    How can you be sure at run time which is the master machine in a MASTER/BACKUP configuration?

The Tuxedo configuration file defines the MASTER machine and the BACKUP machine in *RESOURCES configuration. The first machine listed by MASTER machine is the current MASTER machine, the second one listed (separated from the first one by a comma) is the current BACKUP machine.

Given the following master/backup configuration:

*RESOURCES
<...>
MASTER simple1,simple2
MODEL MP
OPTIONS LAN
<...>

*MACHINES
test1 LMID=simple1
<...>

test2 LMID=simple2
<...>

*NETWORK
<...>


"simple1" is defined as the primary MASTER
and
"simple2" as the backup MASTER.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms