How MOM Consolidator Responds When You Click "Commit Configuration Change" (297808)
The information in this article applies to:
- Microsoft Operations Manager 2000
This article was previously published under Q297808 SUMMARY
This article describes what occurs when you right-click the Rules container and then click Commit Configuration Change in the Microsoft Operations Manager (MOM) Administrator console.
MORE INFORMATION
Each Consolidator maintains its own in-memory cache of the entire configuration. When you force an update by clicking Commit Configuration Change, the Consolidator reloads the entire cached configuration.
Each of the tables in the OnePoint database contains information that notes when the table was last modified. The Data Access Server (DAS) periodically makes a call that returns the maximum last-modified time for all configuration-related tables. If the Consolidator determines that anything has changed since the last-modified time of the cache, it reloads the configuration information from all related tables.
Last-modified times do not propagate in the database. Each time the Consolidator reloads its cache, the Consolidator compares the new configuration to the old configuration to detect changes (for example, addition of a rule group or deletion of a computer-group-to-rule-group link), and artificially adjusts the times of the changed groups. The Consolidator stores a local copy of its cache so it can safely detect changes across a service restart.
The Consolidator always loads its entire configuration if it notes a change. If it notes no change, the Consolidator sends nothing. The Consolidator never performs a partial loading or a partial sending of its configuration information. This means that, for example, during the next scheduled heartbeat the Agent receives a complete copy of all applicable rules, not just a copy of modifications to the rules.
| Modification Type: | Minor | Last Reviewed: | 6/13/2005 |
|---|
| Keywords: | kbenv kbinfo kbpolicy KB297808 |
|---|
|