Last updated on NOVEMBER 04, 2016
Applies to:Oracle Tuxedo - Version: 10.3.0
Information in this document applies to any platform.
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
"simple2" as the backup MASTER.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms