Configuring extra failover capabilities in the ObjectServer
Related events use standard ObjectServer components to provide a high availability solution. These ObjectServer components require extra configuration to ensure high availability where there is an ObjectServer pair and the primary ObjectServer goes down before the cache on the Netcool®/Impact node refreshes.
In this scenario, if you deploy a correlation rule, the rule is picked up if you have replication setup between the ObjectServer tables. Otherwise, the new rule is not picked up and this state continues until you deploy another new rule. Complete the following steps to setup replication between the ObjectServer tables.
- In the
.GATE.mapfile, add the following lines.
CREATE MAPPING RE_CACHEMAP ( 'name' = '@name' ON INSERT ONLY, 'updates' = '@updates' );
- If your configuration does not use the standard
StatusMapfile, add the following line to the
StatusMapfile that you use to control
alerts.status, you can find the
StatusMapfile in the
'ParentIdentifier' = '@ParentIdentifier'
- In the
.tblrep.deffile, add the following lines.
REPLICATE ALL FROM TABLE 'relatedevents.cacheupdates' USING map 'RE_CACHEMAP';
- Setting up the standard multitiered environment
- Configuring the bidirectional aggregation ObjectServer Gateway
- Configuring the unidirectional primary collection ObjectServer Gateway