Best practices for specific implementation scenarios
For specific scenarios, BMC recommends particular settings for Atrium Integrator, Product Catalog, Normalization Engine, and Reconciliation Engine.
Recommendation for scheduling
Importing your data into BMC CMDB, normalizing it, and reconciling it must happen separately, so do not schedule any overlap in these processes. For example, reconciliation will result in errors for a group of related configuration items (CIs) such as a computer system and its components if not all of the CIs and relationships in the group have yet been imported.
Best practices for bulk loads
When you are loading a large amount of data, such as an initial load, into BMC CMDB, use the following guidelines. The objective is to provide a starting point with normalized and reconciled data, using batch jobs. After a bulk load, you can decide how to normalize changes to the data (batch, inline, or continuous normalization).
Best practices for bulk load
Best practices for incremental loads
After you have loaded initial data, use the following guidelines to normalize and reconcile changes to the data.
Best practices for incremental loads
Best practices for CMDB Explorer edits
When modifying configuration items (CIs) in the CMDB Explorer, use the following guidelines. When you promote a CI, it is reconciled using a standard Identify and Merge job.
Best practices for CMDB Explorer edits
Best practices for Remedy ITSM suite manual edits
When modifying configuration items (CIs) from the Remedy IT Service Management suite, use the following guidelines.
Best practices for Remedy ITSM suite manual edits