Welcome to March’s CMDB Blog. In this blog, we will discuss about Normalization process using new CMDB UI. Normalization is the first activity which takes place after importing data in CMDB source datasets through Atrium Integrator or Discovery Sync.
Below are the topics which we are going to cover:
Normalization Console Overview
Normalization process makes sure that product names and categorization are consistent across different datasets and from different data providers. Normalization Engine provides a centralized, customizable, and uniform way to overcome data consistency problems.
How to access Normalization Console in new UI?
- Once you login to new CMDB Console, CMDB Dashboard is displayed. From this home page, you can open it using ‘Manage Normalization’ option under ‘Jobs’ menu.
Normalization Console Layout
- Normalization Console shows the number of jobs along with the job run details.
- It displays information on the processed CIs and relationships. It also shows whether the CIs/Relationships have any errors after normalization or not.
- You can filter the jobs to be displayed by selecting the dataset above.
Creating Normalization Job
1. In the CMDB UI, select Jobs > Manage Normalization.
2. On the Normalization page, click Create Job. The Create Normalization page opens as shown in the following figure:
3. Enter a unique name for the job.
4. From the Dataset Configuration drop-down list, select the dataset.
5. If you want Product catalog entry to be created if it doesn’t exist, then you can check ‘Allow New Product Catalog Entry’ checkbox.
6. ‘Allow Unapproved CIs’ option will Normalize CI even If the product is unapproved in the Product Catalog.
Normalization Engine will set its NormalizationStatus attribute to Normalized and Not Approved.
7. Select Normalization Features which you want to enable.
8. Schedule will decide the Job type i.e. Continuous / Batch. Continuous job will run continuously & Batch job runs on specific time.
9. Click on “Save” button to create the Normalization Job.
You will find below options under Configuration > Manage Normalization Rules’ from CMDB Dashboard:
- Catalog Mapping
- Dataset Configuration
- Class Configuration
From the Catalog Mapping, you can map incoming CI categorizations for a discovered or imported CI to preferred categorizations for different reasons. The product categorization aliases provide the correct categorizations either when the CI's Category, Type, and Item attributes have no values or when they do not match those in the corresponding Product Catalog entry.
You can create Product catalog alias mapping with below steps:
1. In the BMC CMDB Dashboard, select Configurations > Manage Normalization Rules > Catalog Mapping
2. In the Catalog Mapping screen, click the ( + ) sign to open the page in which you can select a class for which you want to create the product alias mapping.
3. Select the CI class from the drop-down list
4. In the Discovery Product Categorization section, select the categorization values of discovered products for the CI class you selected.
Specify a name for the product in the Product Name field.
In the Mapped Product Categorization section, select the categorization values that are applied to the discovered product when it is normalized.
5. Click on Save button to save the details.
The Normalization Engine is provided with various capabilities that enable you to define rules and actions to normalize CIs. These rules can be applied to individual datasets.
You can view/modify existing rules or create new rules from Configurations > Manage Normalization Rules > Features
There are two attributes related to versions i.e. MarketVersion & VersionNumber in BaseElement. The VersionNumber attribute stores a full version number, such as 18.104.22.168, which can change frequently with maintenance releases. To manage licenses more accurately, the MarkerVersion attribute stores a simpler string version, such as 5.0 or 2007. You can do this version rollup for MarketVersion attribute using Version normalization feature.
The Impact Normalization feature is applied to relationship classes only. This feature sets the impact attributes based on the out-of-the-box or custom impact rules for the relationship class and the source and destination classes it relates to.
Relation Name Normalization
The Relation Name Normalization feature is applicable to relationship classes only. This feature replaces the existing relationship names with the BMC recommended or custom names, based on the CI classes in the relationship.
Instance Level Permissions
This feature enables you to set the row-level permissions on CIs as defined by the CI classes and additional qualifiers of the Instance attributes.
Suite Rollup Normalization
This feature enables you to define suites and their products and to identify an instance as a suite, a suite component, or a standalone application. Allows more accurate management of suite and individual licenses.
This feature enables you to create custom rules when the out-of-the-box Normalization features do not meet your requirements for normalizing data. You can create a custom rule for CI and relationship classes to perform a required action.
1. On the BMC CMDB Dashboard, click Configurations > Manage Normalization Rules > Dataset Configurations.
2. Select an existing Dataset Configuration and click on Edit.
3. On the All Datasets Configurations page, set the normalization settings for the selected dataset.
You can get more information about Dataset configuration in below link:
You can add or remove classes for Normalization. If you remove class from Class configuration then CIs from that class will have NormalizationStatus as “Not Applicable for Normalization”.
To add a class for Normalization:
1. On the BMC CMDB Dashboard, click Configurations > Manage Normalization Rules > Class Configuration
2. Click on ‘Add Class Configuration’
3. Select class name from drop-down list & click on Save
Enable Debug Level Logging
You can enable debug level logging from CMDB Dashboard > Configurations > Core Configurations
Follow the below steps to enable debug level logging:
- Click on Normalization
- Select ‘Plugin Server Configuration’
- From the drop-down list select the server on which you want to enable debug logs.
4. Click on API/Batch/Continuous Job Configuration.
- API Job Configuration – Logs for Inline Normalization Job & detailed NE API calls.
- Batch Job Configuration – Logs for Batch Job
- Continuous Job Configuration – Logs for Continuous Job.
5. Change Log Level from Warn to Debug.
6. Click on Save button.
Thank you for reading this blog.