ActiveVOS Server Console Help
This feature requires a MultiSite license. MultiSite is currently supported only for WebLogic application server and Oracle Database 11g. MultiSite configuration is incompatible with the Eventing Service, and Eventing is disabled in a MultiSite license.
What is MultiSite?
ActiveVOS Server supports a site configuration, which allows a cluster of process servers to replicate its database to other databases serving other sites. Each site has its own cluster of servers with a single persistent database, and the site operates independently of other sites. All process instances are available for execution at each site. In the event of a server failure at one site, a process that started execution on that site can complete on a different site.
In addition, most ActiveVOS server configuration properties are replicated from site to site. This means you can configure server properties in one site’s server console, and they are automatically copied to another site’s administration console.
In the event of a site failure, work on a process instance can be failed over to another site.
The database setup is a master-master replication, as shown in the following illustration.
In a site configuration, ActiveVOS provides a high degree of fault tolerance and load balancing.
Database Replication Setup and MultiSite Configuration
The MultiSite page does not show any site information until you set up and configure databases for replication on each site.
For set up and configuration details, refer to the ActiveVOS Server MultiSite Configuration section of the Install, Configure, and Deploy Guide. To access this guide, open quickstart_server.html in the server-enterprise folder of your ActiveVOS Server installation. Be sure to follow all instructions for successful replication setup and testing.
MultiSite Page Details
The MultiSite page contains the following information.
|
Name |
Name added to the Site Properties page of the ActiveVOS Console associated with the site. You can update site properties for the current site; however, you cannot update one site’s properties on another site’s server console. Connect to a site’s Administration Console via the name. |
|
Status |
Statuses include Available, Unavailable, Failed Over, or Incompatible. Available indicates the site is sending heartbeats. If a site was unavailable or failed over, it changes to available when it begins to communicate. Unavailable indicates that the site is not communicating. It has exceeded the maximum number of missed heartbeats set in the Site Properties page. An alert is automatically triggered, and sent to the Monitor Alert Service, if the service is deployed and running. For details, see Monitoring Thresholds, Properties, and Monitor Alert Service. The site is not immediately failed over. You can manually fail over the site, as described below. Failed Over indicates you have manually failed over an unavailable site, as described below. Incompatible indicates that the site is using a software version that does not match the other site(s). |
|
Id |
A numeric value in the range of 0 to 127 which uniquely identifies the site (There is a limit of 128 sites). ActiveVOS generates an Id after database replication is configured. |
|
Description |
Description of the site as it appears in the Site Properties page. |
Failing Over a Site Manually
There may be times when inter-site communications go down but the sites are still running. In this case, a site is considered unavailable.
When a site becomes unavailable due to a communication error, it is not immediately failed over to another site. Instead, ActiveVOS sets the site status to Unavailable, triggers an alert, and provides a Fail Over action for you to take, if desired.
Once a site has failed over, a new state called Failed Over is displayed, and the Fail Over button is removed.
When the unavailable/failed-over site begins communicating with the other sites (sends a heartbeat), the site automatically becomes available.
Monitor Alert Service
When a site becomes unavailable, an alert is automatically triggered. If ActiveVOS server finds a deployed Monitor Alert Service, the service will run. For details, see Monitoring Thresholds, Properties, and Monitor Alert Service.
See also:
Copyright (c) 2004-2009 Active Endpoints, Inc.