Configure a failover host (managed by EGO)

Edit online

For enterprise grid orchestrator (EGO) failover to function correctly, Process Manager must have its conf and work directories installed in a shared location. When you install Process Manager as an EGO service, Process Manager benefits from the failover features of EGO. If the server running Process Manager fails, EGO relocates and restarts Process Manager on another host.

Before you begin

Prerequisites:

Process Manager must have been installed as an EGO service.

On Windows, this is done by specifying to install Process Manager as an EGO service during installation.
On UNIX, this is done by specifying EGO_DAEMON_CONTROL=true in install.config at installation.

Procedure

In js.conf, set JS_FAILOVER=true and define JS_FAILOVER_HOST.
The hosts that you define for JS_HOST and JS_FAILOVER_HOST must both belong to the EGO ManagementHosts resource group.
Edit the processmanager.xml file.
- Windows: %LSF_ENVDIR%\ego\cluster_name\eservice\esc\conf\services\processmanager.xml
- UNIX: $LSF_ENVDIR/ego/cluster_name/eservice/esc/conf/services/processmanager.xml
Change the StartType from MANUAL to AUTOMATIC.
Navigate to the following line:
```
<sc:StartType>MANUAL</sc:StartType>
```
Change it to:
```
<sc:StartType>AUTOMATIC</sc:StartType>
```

Add JS_FAILOVER_HOST to the ResourceRequirement select statement.

Navigate to the following line:

<ego:ResourceRequirement>select('JS_HOST')</ego:ResourceRequirement>

Change this line to the following:

<ego:ResourceRequirement>select(’JS_HOST’||’JS_FAILOVER_HOST’) order(’JS_FAILOVER_HOST’)</ego:ResourceRequirement>

Save and close the file.
Open the Services page from the Windows™ Control Panel, and change the Startup Type for the Process Manager service from Automatic to Manual.
Restart EGO to apply your changes.
You will need to log in to EGO first with the command egosh user logon. The default user name is Admin, and the default password is Admin.
```
egosh ego restart all
```