service-failover="num"

Valid Values: An integer value > 0

A process-type may be configured as a service-failover (if num is not zero), which represents a process that exists num times somewhere in the cluster when it is up. The implementation is limited such that only one process of this type runs on a single instance, and so the maximum number of processes for a specific service-failover in the cluster can never be more than the number of participating instances in the cluster. If the value of num is greater than the number of instances participating in this service-failover in the cluster and the service-failover is active (it has been started), then each participant added to the cluster automatically starts its service-failover process until the total number cluster wide is num.

A service-failover process can run on any instance participating in the service, which means each instance must have the service configured with the same ias-component id, process-type id and process-set id. To target the service itself, a request must specify both the ias-component and the process-type (it can also include the process-set).

A service-failover process-type can have only one process-set. Because the number of processes for a failover service is always 1, this process-set cannot specify numprocs, minprocs, or maxprocs.

A service-failover can be specified as a dependency (like any managed-process) or can specify dependencies. If specified as a dependency, the dependency check for a service-failover evaluates true as soon as one process of this type is active anywhere in the cluster, regardless of the configured value for num.

Example:

<ias-component id="<Essbase-Cluster-Name>">
   <process-type id="EssbaseAgent" module-id="ESS" service-failover="1" service-weight="101">
     <environment>
        <variable id="EPM_ORACLE_HOME" value="<Oracle Home-Location>”>
     </environment>
     ...
   </process-type>
</ias-component>