Oracle Coherence Monitor

User Guide

 

High Availability Configurations

High Availability (HA) mitigates single point of failure within OCM by providing a means of defining redundant system components together with failover capability for users of those components.

When using HA, components are designated PRIMARY and BACKUP. If the PRIMARY component fails, failover occurs to the BACKUP component. If the PRIMARY component is subsequently restarted, the BACKUP component allows the newly restarted component to take the primary role and return to its backup role.

This section includes:

OCM HA Stand-alone Version
OCM is available with a High Availability (HA) Data Server configuration. The project/sample directory provides an example of HA Data Server with OCM. The example assumes the availability of two machines, PRIMARYHOST and BACKUPHOST, defined by environment variables of the same name.

OCM is configured by using the primary and backup configurations in rtvservers.dat, with start_rtv in place of the default configuration.

The primary Data Server is run on PRIMARYHOST; the backup Data Server is run on BACKUPHOST; the other OCM applications failover between the Data Servers as appropriate. Assuming the environment variables PRIMARYHOST and BACKUPHOST are set correctly, OCM components on the primary machine are started as normal using the primary configuration (instead of the default configuration) with the start_rtv command. The backup OCM Data Server on the backup machine is started using the backup configuration with the start_rtv command.

Start the primary OCM components on the primary machine using the primary configuration with the start_rtv command. For example:

Windows
start_rtv primary

UNIX
start_rtv.sh primary

Start the backup OCM Data Server on the backup machine using the backup configuration with the start_rtv command. For example:

Windows
start_rtv backup

UNIX
start_rtv.sh backup

The appropriate property files and propfilters for the primary and backup Data Servers are defined in the rtvservers.dat file under the primary and backup configurations. The property values controlling HA, used by the OCM Data Servers, are defined in the ha.properties file.

OCM HA Solution Package Version
A High Availability (HA) Data Server configuration that is within the RTView EM platform is available for the OCM Solution Package version.

The emsample/servers directory provides an example of HA for RTView EM and the OCM Solution Package version. The example assumes the availability of two machines PRIMARYHOST and BACKUPHOST defined by environment variables of the same name. RTView EM is configured by the rtvservers-ha.dat file in place of the rtvservers.dat file in the emsample/servers directory

Assuming the environment variables PRIMARYHOST and BACKUPHOST are set correctly,
EM components on the primary machine are started as normal using the “central” configuration with the start_rtv command. EM components on the backup machine are started using the “central-backup” configuration with the start_rtv command.

Start the primary OCM Data Server on the primary machine as normal using the ocmon configuration with the start_rtv command. For example:

Windows
start_rtv ocmon dataserver

UNIX
start_rtv.sh ocmon dataserver

Start the backup OCM Data Server on the backup machine using the ocmon-backup configuration with the start_rtv command. For example:

Windows
start_rtv ocmon-backup dataserver

UNIX
start_rtv.sh ocmon-backup dataserver

The appropriate property files and propfilters for the OCM Data Sever are defined in the rtvservers-ha.dat file in the servers directory. The property values controlling HA used by the OCM Data Servers are defined in the ha.properties file in the servers/ocmon directory.












 

 

 

 


 

RTView contains components licensed under the Apache License Version 2.0.

 

Treemap Algorithms v1.0  is used without modifications and licensed by MPL Version 1.1. Copyright © 2001 University of Maryland, College Park, MD

 

Datejs is licensed under MIT. Copyright © Coolite Inc.

 

jQuery is licensed under MIT. Copyright © John Resig,

 

JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

jQuery is licensed under MIT. Copyright (c) 2009 John Resig, http://jquery.com/ JCalendar 1.3.2 is licensed under LGPL. Copyright © Kai Toedter.

 

JMS, JMX and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. They are mentioned in this document for identification purposes only. 

 

SL, SL-GMS, GMS, RTView, SL Corporation, and the SL logo are trademarks or registered trademarks of Sherrill-Lubinski Corporation in the United States and other countries. Copyright © 1998-2013 Sherrill-Lubinski Corporation. All Rights Reserved.