High availability for BMC Impact Integration Web Services
If a BMC Impact Integration Web Services client requires high availability (HA) for BMC Impact Integration Web Services, then in addition to deploying HA cells, you must also deploy two IIWS servers.
You can use this configuration to configure a HA BMC Impact Integration Web Services for BMC Performance Manager. The client, BMC Performance Manager, has knowledge of the primary and secondary (or backup) BMC Impact Integration Web Services server. In case one of the BMC Impact Integration Web Services servers is down, the client will work with the other BMC Impact Integration Web Services server.
The two Impact Integration Web Services servers are working with both the HA cells.
The same rules for configuring high availability cells for the BMC Impact Integration Web Services server. See Configuring the primary and secondary cells in an HA pair. Also apply to the BMC Performance Manager environment. BMC Performance Manager adds the extra feature of having a backup BMC Impact Integration Web Services server.
In a BMC Performance Manager environment, the recommended HA cell configuration is to have the BMC Performance Manager specify a primary and a backup or secondary web services server. Note that the cell does not have to reside on the same system as the web services server.
In this scenario, both the primary and secondary web services servers connect to the same HA cells.
In case you deploy the receive events function, when the primary IIWS server goes down, the client will not get the events already received by this server, until this primary server comes up again. For this reason, BMC strongly recommends restricting a pair of IIWS servers to the querying and send events functionality. To reduce the result set of event queries, the events in the cells can be extended with a client_ack slot that is set by the IIWS client upon receiving the event.
Following figures and the following figure depict the mcell.dir file entries required in the following scenario:
- The primary BMC Impact Integration Web Services server is installed on System 1.
- The backup or secondary BMC Impact Integration Web Services server is installed on System 2.
- The primary HA cell server is installed on System A.
- The backup or secondary HA cell server is installed on System B.
The following figure depicts the flow of information between the BMC IIWS client, the BMC Impact Integration Web Services servers, and the HA cells.
Communication flow between the BMC IIWS client, the BMC Impact Integration Web Services servers, and the HA cells
System 1: mcell of the primary BMC Impact Integration Web Services server
Type Name EncryptionKey IPAddress:Port
cell Alphonse mc SystemA:1828 SystemB:1828
The preceding figure depicts the mcell.dir file for the primary BMC Impact Integration Web Services server on System 1, which communicates with the primary HA cell Alphonse, on System A, and the secondary HA cell, Alphonse, on System B.
System 2: mcell of the backup or secondary BMC Impact Integration Web Services server
Type Name EncryptionKey IPAddress:Port
cell Alphonse mc SystemA:1828 SystemB:1828
The preceding figure depicts the mcell.dir file for the backup or secondary BMC Impact Integration Web Services server on System 2, which also communicates with the primary HA cell, Alphonse, on System A, and the secondary HA cell, Alphonse, on System B.
System A: mcell of the primary HA cell, Alphonse
Type Name EncryptionKey IPAddress:Port
cell Alphonse mc SystemA:1828 SystemB:1828
The preceding figure depicts the mcell.dir file for the primary HA cell, Alphonse, on System A, which has entries for HA cell, Alphonse, on System A and on System B.
System B: mcell of the secondary HA cell, Alphonse
Type Name EncryptionKey IPAddress:Port
cell Alphonse mc SystemA:1828 SystemB:1828
Comments
Log in or register to comment.