|
|
The following section describes how to setup geographically redundant site pairs and the maintenance attributes and operations for the geographic redundancy service once it is set up. It also provides a workflow for the configuration:
The geographic redundancy service is responsible for replicating data, so that applications can switch from one site to another and have the data necessary for SLA enforcement available at the second, remote, site. For more information about geographic redundancy, refer to the “Redundancy, Load Balancing, and High Availability” chapter in Concepts and Architectural Overview.
Each geographic site has a name. This name is used for looking up data relevant to the site pair. All configuration is done locally per site, so the remote site must be defined in the local site.
Below is an outline for configuring the geographically redundant service. This must be done at both sites.
Managed object: Container Services
GeoRedundantService
MBean: com.bea.wlcp.wlng.core.budget.management.configuration.GeoRedundantServiceMBean
Below is a list of attributes and operations for configuration and maintenance:
Specifies the number of attempts made by a site to reach its peer site before raising an alarm.
Whenever the peer sites fail to establish a connection the number of times defined in RemoteSiteReachabilityAlarmThreshold, a connection lost alarm is raised.
Defines the name of this geographic redundant site. This name is used as key for all operations on the site - see Operation: setSiteAddress, Operation: getSiteAddress, Operation: removeSite.
getSiteAddress(Site name: String)
Displays the address of a given site.
listRemoteSites()
Displays a list of registered remote sites.
removeSite(Site name: String)
Specifies the address of a remote site.
setSiteAddress(Site name: String, Address: String)
|