Manual Steps for Failover Configuration on the Secondary Node (Host 2)

Tip: For Release 21.5.2 or higher, skip these instructions and use the instructions in Set up an Essbase Failover Environment Using the Failover Setup Script instead.

Host 2, the secondary node, only runs Essbase.

SSH to the secondary node, Host 2.

Run WebLogic and unpack essbase_ha.jar, which you copied from Host 1.

On Linux:

<Oracle home>/oracle_common/common/bin/unpack.sh -template=essbase_ha.jar -domain=<Domain Home>

Linux Example:

./Oracle/Middleware/Oracle_Home/oracle_common/common/bin/unpack.sh -template=/scratch/essbase_ha.jar -domain=<Domain Home>

On Windows:

<Oracle home>\oracle_common\common\bin\unpack.cmd -template=essbase_ha.jar -domain=<Domain Home>

Windows Example:

.\Oracle\Middleware\Oracle_Home\oracle_common\common\bin\unpack.cmd -template=\scratch\essbase_ha.jar -domain=<Domain Home>

Note:

<Domain
                        Home>

should be exactly the same as defined in Host 1. For example, ./Oracle/Middleware/Oracle_Home/user_projects/domains/essbase_domain

Edit <Domain Home>/bin/setDomainEnv.sh (on Linux) or <Domain Home>\bin\setDomainEnv.cmd (on Windows)
Caution:

The Essbase platform includes scripts in <DOMAIN HOME>/bin that can customize the environment and behaviors of Essbase functionality. However, making changes to these domain environment or startup scripts can have unintended effects, including startup failure. Oracle recommends making changes in a test environment first. Before editing these scripts, always:
1. Stop the Essbase managed servers, using <DOMAIN HOME>/esstools/bin/stop.sh (on Linux), or <DOMAIN HOME>\esstools\bin\stop.cmd(on Windows).
2. In <DOMAIN HOME>/bin, make a backup copy of the file you want to edit. For example,
  
  On Linux
```
cp setStartupEnv.sh setStartupEnv_bak.sh
```
  On Windows
```
copy setStartupEnv.cmd setStartupEnv_bak.cmd
```
3. Edit carefully, using only Oracle’s documented instructions, or working with Oracle Support.
4. Restart Essbase, using <DOMAIN HOME>/esstools/bin/start.sh (on Linux), or <DOMAIN HOME>\esstools\bin\start.cmd(on Windows). Check that startup completed normally.
Similarly to how EXTRA_JAVA_PROPERTIES was added to Host 1, copy the same EXTRA_JAVA_PROPERTIES to setDomainEnv.sh (on Linux), or setDomainEnv.cmd (on Windows) in Host 2.
1. Search for the string EXTRA_JAVA_PROPERTIES.
  
  Important: Search for EXTRA_JAVA_PROPERTIES, not JAVA_PROPERTIES.
2. Add the following -D definition after the existing export EXTRA_JAVA_PROPERTIES line:
  
  On Linux:
```
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES}-Dweblogic.security.SSL.ignoreHostnameVerification=true" export EXTRA_JAVA_PROPERTIES
```
  On Windows:
```
set EXTRA_JAVA_PROPERTIES=-Dweblogic.security.SSL.ignoreHostnameVerification=true %EXTRA_JAVA_PROPERTIES%
```
  Note:
  This step is not required if all the TLS certificates are imported properly. In case of self-signed certificates, or if the managed server later fails to start with SSL errors, this step is required.
Edit <Domain Home>/bin/setStartupEnv.sh (on Linux) or <Domain Home>\bin\setStartupEnv.cmd (on Windows).
Search for "DISCOVERY_URL" for ESSBASE-MAN-SVR startup group and change the hostname and port from the Host 1 values to the Host 2 values.

Note:
Modify this only for ESSBASE-MAN-SVR. If Essbase Administration Services is installed, then DISCOVERY_URL for ESSBASE-EAS-SVR as STARTUP-GROUP should be https://OHS_HOST:OHS_PORT/essbase/agent.
-DDISCOVERY_URL=https://Host 2:port/essbase/agent
Check the listen address in nodemanager.properties by editing <Domain Location/<Domain Name>/nodemanager/nodemanager.properties. Make sure ListAddress points to Host 2.