Overview of normalization
The Normalization Engine is a policy enforcement engine installed with the BMC Atrium Configuration Management Database (BMC Atrium CMDB) product. It enables you to centrally define data policies and automatically enforce them throughout BMC Atrium CMDB.
The following topics provide information about how normalization works in BMC Atrium CMDB:
- Normalization features
- Normalization status
- Normalization and the Product Catalog
- Normalization process
- Normalization and NULL values for Model (Product Name) and ManufacturerName
- Multitenancy support in the Normalization Engine
- Normalization and software license management
- Normalization and impact relationships
- Normalization and best-practice relationship rules
- Normalization and instance permissions
- Normalization and custom rules
- Normalization Failover - Scheduled Batch Jobs
- Normalization use cases
- Calbro scenario for normalization
When multiple sources provide data to BMC Atrium CMDB, data consistency problems such as the following can occur:
- Inconsistent categories and naming
- Duplicate configuration items (CIs)
The Normalization Engine provides a centralized, customizable, and uniform way to overcome data consistency problems. This consistency in BMC Atrium CMDB data enables consuming applications to make good decisions. For example, BMC Asset Management can report on software license usage appropriately.
You can normalize data before or after it is written to a dataset in BMC Atrium CMDB. With the Normalization Engine, you can define what is normalized:
- A specific dataset, such as BMC.ADDM
You can enable or disable normalization for each dataset, as well as configure other normalization features.
- A specific class to normalize, such as
You cannot choose to normalize specific classes in different datasets. Instead, you configure classes across all datasets.