Describes the steps you must complete for all individual Sybase CEP Servers acting as Managers in your cluster when configuring Manager or Container High Availability.
Complete these steps individually for all Sybase CEP Servers acting as Managers in your cluster, whether or not you plan to run multiple Managers. Some of these values have already been set appropriately by the installation program, but other preferences will need to be set manually. Refer to the information from "Preparing to Configure High Availability Features" while you work on this section.
If you plan to configure Sybase CEP Engine High Availability features for Manager failover, set the "SybaseC8/Server/Common/ManagerURI" preference in the c8-server.conf configuration file to the Manager's Uniform Resource Identifier (URI). To use only one Manager with no Manager failover, set this preference to the local address of the Manager.
The Manager URI uses the following format: http:// generic-host-name-alias:port or https:// generic-host-name-alias:port where generic-host-name-alias is the generic host name alias you set up in Step 7d of "Preparing to Configure High Availability Features", and port is the port number set for the Managers in your cluster in Step 3c of "Preparing to Configure High Availability Features". If SSL is enabled on Sybase CEP Servers in the cluster, then all Manager URIs must start with https:// instead of http:// . For more information about configuring SSL features, see "Configuring SSL Support".
If you are using multiple Managers in your cluster, and the "ManagerURI" preference is currently set to the local address of the computer where the Manager is installed, replace the local address with the URI. For example, you might change this preference:
<section name="SybaseC8/Server"> <section name="Common"> ... <!-- the URI of the Manager this server is using --> <preference name="ManagerUri"> http://localhost:6789</preference>
to this:
<section name="SybaseC8/Server"> <section name="Common"> ... <!-- the URI of the Manager this server is using --> <preference name="ManagerUri"> http://C8MgrShared:6790</preference>
As explained in "Configuring Managers for Manager or Container High Availability", the Domain Name Service (DNS) uses this URI to route messages from Containers to the current active Manager. All the Managers in your cluster must refer to the same Manager URI.
Specify how many active Containers you want the Manager to try to maintain at any given time in the "Manager/HighAvailability/MinActiveContainerNative" preference of the c8-server.conf configuration file. For example:
<section name="Manager"> ... <section name="HighAvailability"> <!-- After this number of active native containers is reached, all containers will be made passive --> <preference name="MinActiveContainersNative" value="0"/>
The default setting for this value is 0, which specifies unlimited active Containers. If you set the value to 0, the Manager activates all available Containers. If you set the value to another number, the Manager attempts to limit the number of Containers to the number you specify in "MinActiveContainersNative".
Under normal circumstances, the Manger sets all other available Containers to passive mode until they are needed for failover. However, the "LoadLimit" setting, which specifies the maximum number of CCX modules (that is, adapters or query processors) that a given Container can simultaneously execute, may affect the number of active Containers. If a Container's "LoadLimit" setting does not permit it to take on additional workload, the Manager attempts to activate another available passive Container, even if the number of active Containers specified in the "MinActiveContainersNative" has already been reached.
Complete these steps for every Sybase CEP Server acting as Manager in your cluster only if you are using multiple Managers and setting up Manager failover features. If you plan to use a single Manager with no failover features, skip the rest of this section and go to "Configuring Containers for High Availability" for instructions on configuring Containers for High Availability features.