Multiple BO Configuration
A multiple BO configuration in Primo allows clients to configure one or more failover servers for the Primo BO. In this configuration, only one server is active, while the others are inactive.
If a failure occurs in the active BO server, an inactive server must be started manually to provide BO service.
Guidelines
When configuring a multiple BO configuration, the following guidelines must be followed:
-
Only one BO server can be active at a time; all others must be inactive.
-
To avoid having to change a number of Back Office parameters manually, all BO servers must be directed to a single database using a load balancer. Alternatively, if a load balancer is not used, access the Installation subsystem of the General Configuration Wizard in the Primo Back Office and change the following parameters to use the host name of the new Back Office:pds_url, pds_configuration_url, Reports URL, Help Base URL, reporting_base, primo_admin_base, primo_base, and Search Statistics Report URL.
-
The BE_HOST parameter must be defined as a common host name on all BO servers.
-
The BO servers must share the same ng/primo/home/profile/publish/publish/production directory using NFS.
-
Add an entry to the be_stop script to remove the startup control file from the ng/primo/home/profile/publish/publish/production directory.
-
To ensure that only one BO server is active and running, add the following checks to the be_start script:
-
Check to see that the other BO servers are accessible and run the be_stop script for BO servers.
-
Check to see that there are no connections to the other BO server's BO port.
-
Check that the start up control file does not exist in the shared ng/primo/home/profile/publish/publish/production directory.
-
-
Add an entry to the be_start script to create a startup control file in the
ng/primo/home/profile/publish/publish/production directory for the active BO server.