If you have two EAServer installations, you can enable hot standby, which allows you to designate one of the servers as a backup server that accepts client connection requests in case the master server fails. The master server processes client requests. The backup server starts in “Admin” mode and does not accept client requests. If the master server fails or is unreachable, the backup server sets itself to “Ready” mode and accepts client requests. Once the master server is up and accepting requests, the backup server enters “Admin” mode, refusing connections from clients.
See Chapter 7, “Load Balancing, Failover, and Component Availability” for information about component failover.
Enabling hot standby in EAServer
You must first enable the two hot standby servers as name servers. Select the Naming Service tab and click Enable as a Name Server to configure EAServer as a name server.
Select the Hot Standby tab and click the Enable Hot Standby check box.
Enter the Master Server URL using the format iiop://hostname:port. For
example, iiop://EAServer_master:9095.
Enter the Backup Server URL using the format iiop://hostname:port. For
example, iiop://EAServer_backup:10000.
The master and backup servers must be valid IIOP or IIOPS URLs. You can have only one master and one backup server defined and one of them, but not both, must be defined on the local server.
Synchronize the servers using the master as the primary server—see “Synchronization”.
You can verify the settings of hot standby by checking these properties on the Advanced tab:
com.sybase.jaguar.server.CosNaming.nameserver must be set to true for both the master and backup servers.
com.sybase.jaguar.server.hotstandby is set to true if hot standby is enabled.
com.sybase.jaguar.server.hotstandby.master is the URL of the hot standby master server.
com.sybase.jaguar.server.hotstandby.backup is the URL of the hot standby backup server.
