To configure HA for RTViewCentral you setup the Primary and Backup Hosts, verify your setup, test the failover process to the Backup Host and verify the Primary Host is restored to the primary server for the pair.
On both the primary and backup hosts, define PRIMARYSERVER and BACKUPSERVER environment variables:
PRIMARYHOST - the IP address or hostname of the host running the primary servers (ex set PRIMARYHOST=MyHost).
BACKUPHOST - the IP address or hostname of the host running the backup servers (ex. set BACKUPHOST=OtherHost).
Install RTViewCentral on the primary and backup host.
Configure the RTViewCentral servlets to be HA and deploy them to your application server:
cd to projects\rtview-server
In a text editor, open update_wars (.bat or .sh) and fill in the values for HOST, HA_HOST, HA_DISPLAYHOST and HA_FAILBACK as described in the script.
Run the update_wars (.sh or .bat) script.
Copy the generated war files to the webapps directory of your application server.
If you are using the RTView Manager, repeat step 3 in the projects\rtview-manager directory.
On the primary host, open a Windows command line (or a terminal window for UNIX) and execute the following script, located in the RTViewCentral/bin directory, to start the servers: start_servers -haprimary (or start_servers.sh -haprimary for UNIX).
On the backup host, open a Windows command line (or a terminal window for UNIX) and execute the following script, located in the RTViewCentral/bin directory, to start the servers: start_servers -habackup (or start_servers.sh -habackup for UNIX).
Configure RTViewCentral using the RTView Configuration Application. Note that the RTView Configuration Application must be able to connect to both the primary and backup servers in order to enable editing. The same properties are saved to both servers. The RESTART SERVERS button restarts both the primary and backup servers at the same time. If you want to stagger the restarts, use the script under bin to stop, then start your servers after making changes in the Configuration Application.
configure all server options
configure databases
enable and configure alert persistence
Note: Jetty does not have to be disabled, but data clients will not be able to make high availability connections to these servers using the Jetty URL - they can still use the Jetty URL to configure their application.
Verify failover and failback of RTViewCentral.
Open a browser to http://host:port/rtview-central-classic, login as admin/admin and verify that you see services, solution package data and alerts as expected.
On the primary host, stop the servers by executing the following script, located in the RTViewCentral/bin directory: stop_servers (or stop_servers.sh for UNIX).
It might take a few seconds to fail over.
Return to the browser and verify the monitor is still available and you still see services, solution package data and alerts as expected.
On the primary host, restart the servers by executing the following script, located in the RTViewCentral/bin directory: start_servers -haprimary (or start_servers.sh -haprimary for UNIX).
If you encounter issues, look at the following in the log files.
This error indicates that you didn’t set the PRIMARYHOST or BACKUPHOST environment variable:
ERROR: Disabling HA because the PRIMARYHOST and/or BACKUPHOST environment variable is not set.
You have finished configuring High Availability.