KBI 310210 How Non-Stop Motors Synchronize Registry Settings

Version

Argent XT — All Versions

Date

24 Aug 2010

Summary

This KBI discusses how Motors in a Non-Stop Motor architecture synchronize all registry settings.

Technical Background

Ideally, each Non-Stop Motor needs to be a clone of each other.

This includes hardware specs, Operating System,and most importantly, network connectivity to the central database backend.

This ensures that events, performance data, and database read/write is the same, no matter which Motor a Daughter connects to.

Additionally, all settings made in the GUI must be synchronized across all Motors.

When the GUI is opened on a Motor, any changes made that affect the Motor’s registry is first saved to the Motor’s local registry, then an immediate request occurs to pull all the registry information and store it into the XX_CONFIGURATION table, where XX defines the motor product — e.g. AG_CONFIGURATION for Argent Guardian.

So these XX_CONFIGURATION tables are essentially a dump of the registry from the latest Motor that made changes to the registry via the GUI.

Periodically, each motor will read the XX_CONFIGURATION table, and use this table to overwrite its own local registry.

This is important to note — because some registry settings may contain information that works on the local machine, but not when synchronized with other motors.

Example

An example of this is specifying a System DSN for Automatic Event Archiving into the AAC_CONSOLEARCHIVE table.

The ODBC string used for Automatic Event Archiving is saved into the registry (HKLM\SOFTWARE\Argent\ArgentManagementConsole\ArgentAlertConsole\ARC_ODBC_SOURCE).

On the Motor where you configure this, the System DSN may be working fine, and tests fine.

However, after the registry setting is synchronized across the other motors, if the other motors don’t have this System DSN locally, and will fail if the GUI is opened on these other motors.

This is a classic example where a customer needs to be careful, and ensure the Motors, as mentioned, are essentially clones of each other.

Resolution

N/A