How To Be Sure At Run Time What Is The Master Machine In A MASTER/BACKUP Configuration? (Doc ID 1386943.1)

Last updated on MAY 19, 2020

Applies to:

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:

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

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.