Configuring high availability in BMC Service Resolution
You can achieve high availability in BMC Service Resolution by performing certain simple configurations.
The following topics are provided:
High-availability architecture in BMC Service Resolution 3.0.00
Refer to the following architecture diagram.
Configurations/Setup required to enable failover
Ensure that two BMC TrueSight instances are installed on separate hosts. See Installing from the BMC TrueSight online documentation.
- Configure the Cells of the two BMC TrueSight instances in HA mode. See To configure cells in HA mode.
Configure the Cells of the two BMC TrueSight instances to propagate events using the One Of policy. See Creating a new propagation policy from the BMC TrueSight online documentation.
- Add the HA cell entry in the Java plug-in to ensure fault tolerance. This is valid only for BMC Service Resolution 3.0 or earlier versions. For information about using and downloading the plug-in JAR file, see the BMC Communities post - https://communities.bmc.com/docs/DOC-38223.
Failover scenarios
The following diagrams depict how failover is achieved using different failure scenarios.
- If the BMC TrueSight Cell goes down, failover is achieved because the Cells are configured to be in HA mode.
- If Service Desk Integration Gateway goes down; failover is achieved because the event policy is configured to use the propagate to One Of policy option.
- If the BMC TrueSight server goes down, failover is achieved because the Cells are configured to be in HA mode.
High-availability architecture in BMC Service Resolution 3.0.01
Refer to the following architecture diagram.
Configurations/Setup required to enable failover
Ensure that two BMC TrueSight instances are installed on separate hosts. See Installing from the BMC TrueSight online documentation.
- Configure the Cells of the two BMC TrueSight instances in HA mode. See To configure cells in HA mode.
Configure the Cells of the two BMC TrueSight instances to propagate events using the One Of policy. See Creating a new propagation policy from the BMC TrueSight online documentation.
Failover scenarios
The following diagrams depict how failover is achieved when any one of the component fails:
- If Service Desk Integration Gateway goes down; failover is achieved because the event policy is configured to use the propagate to One Of option.
- If the Cell goes down on BMC TrueSight server: Failover is achieved because the Cells are configured to be in HA mode.
- If BMC TrueSight server goes down: Failover is achieved because the Cells are configured to be in HA mode.
Partial high-availability architecture
Refer to the following architecture diagram to understand the partial high-availability architecture in BMC Service Resolution.
In the partial high-availability architecture, there is no BMC TrueSight stand by server. Therefore, when the Primary server goes down, failover is not achieved.
However, failover can be achieved in the following scenarios:
- When the Cell 1 goes down, requests are routed through Cell 2. Failover to Cell 2 is achieved because the cells are configured to be in HA mode.
- When the SDiG 1 goes down, requests get routed through SDIG 2. Failover to SDIG 2 is achieved because the event policy is configured to use the Propagate to One of policy option.
To configure cells in HA mode
- Add an entry for a cell and its counterpart in high-availability mode in the installationDirectory\server\etc\mcell.dir file as follows:
cellcellNamemccomputer1NameWithDomain:portOnWhichCellIsInstalled computer2NameWithDomain:portOnWhichHACellIsInstalled - Restart JServer process.