Resolution:
TIBCO ActiveMatrix (R) Service Performance Manager Installation guide provides steps for setting Service Performance Manager services in fault tolerance using three ActiveMatrix nodes in the 'Making the Rule Service Fault Tolerant' section. In fact, users can achieve fault tolerance with any number of nodes (two or greater).

In the case of two nodes, the services typically hosted by each node are as follows:
- spmsysenv_sysnode can host AlertSA, ActionManagerSA, RuleserviceSA and ActionServicesSA i.e. all service units (SOAP Service Unit and Java Service Unit) of these SAs can be mapped to spmsysenv_sysnode
- spsmsysenv_node2 can host only Java Service Units of AlertSA, ActionManagerSA, RuleserviceSA and ActionServicesSA i.e. all Java Service Units of these Service Assemblies can be mapped to spsmsysenv_node2

In this case, if spmsysenv_sysnode goes down, all the services on that node will stop and only Java Service Units will be functional on spsmsysenv_node2.

Note: -
Prior to release 1.3.0, RuleServiceSOAPSU was used for communication between ActiveMatrix Administrator and Rule Service. Since the communication channel was changed to JMS in release 1.3.0 (and above), if the RuleServiceSOAPSU goes down, it does  not affect any functionality. In other words, RuleServiceSOAPSU has no role in fault tolerance and high availability scenarios. This also applies to SOAP service units for AlertSA and ActionManagerSA.

The steps below explain how you can configure the services fault tolerant, and avoid a single point of failure.

Environment:
TIBCO ActiveMatrix (R) Service Performance Manager version 1.3.x.

Resolution:
To make any service fault tolerant:

1. Login to TIBCO ActiveMatrix Administrator.

2. Select the 'Deploy to an Environment' from the 'Perspective' drop-down.

3. Select the Environment 'spmsysenv'.

4. From the Service Assemblies table, select the SPM Service Assembly that needs to run in the fault tolerant mode.

5. Click 'Undeploy'.
   The details of the selected service assemblies are displayed in the lower panel.

6. Click 'Service Units'.
   From the Service Units table, select JavaSU of the selected service assembly.
   The Mapped Nodes table displays that the JavaSU is mapped on the default system node spmsysenv_sysnode.

7. Click 'Edit' to map the service to an additional node (that is, node in addition to the default node).
    In the Node Mapping tab:
    From 'Available Nodes', select an additional node and add it into the Mapped Nodes table.
    It is recommended that you select this additional node from a different machine.

8. Click 'Save'.

   Note: Follow these extra steps only for RuleServiceSA:
   - Click General Settings > Substitution Variables and set the value of rule_service_in_ft_mode to true.
   - Optionally, you can inject additional properties to RuleServiceSA before redeploying the service assembly.
   For details, refer the section 'Adding Properties to Rule Service' from the Installation guide.

9. Click the 'Deploy' button to deploy the service assembly on the newly mapped node.

10. Click the 'Start' button to start the service assembly.

Attachments:
&ltNone>

References:
- TIBCO ActiveMatrix (R) Service Performance Manager Installation guide -> Chap 1 -> Making the Rule Service Fault Tolerant.
- TIBCO ActiveMatrix (R) Service Performance Manager Installation guide -> Chap 1 -> Adding Properties to Rule Service
- TIBCO ActiveMatrix (R) Service Performance Manager Installation guide -> Chap 1 -> Making the SPM Services Highly Available