This documentation supports the 9.1.04 version and its patches of BMC Atrium Core. The documentation for version 9.1 to 9.1 Service Pack 3 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Configuring normalization settings for datasets

A dataset is a collection of CIs and relationships, and each data provider has its own dataset. You can configure the default normalization settings that are applied when datasets are created. You can also apply these default settings to datasets that are already configured. These settings include the option of full or incremental normalization. 

In the Calbro example, the system configuration is first set to the most common values:

  • Both product names and categories are normalized.
  • Products are normalized as the datasets are updated (inline mode).
  • Products with errors are not updated.
  • Discovered products that are not found in the Product Catalog are not created.

Next, the Calbro staff configures the individual datasets that need to be configured differently from the system configuration. For example, for CFS.APPS, any new products found there are created in the Product Catalog.

You can configure normalization for datasets in the following ways:

  • Configure default normalization of CIs across all datasets. 
    These settings are the default normalization settings for all datasets, but these settings do not override the individual dataset configurations unless you select Apply Default Settings to all Datasets
  • Customize normalization for each dataset. 
    The dataset normalization settings override the system defaults.

    Note

    The Version Rollup and Instance normalization features are enabled for all datasets by default and cannot be disabled or configured for individual datasets.
    By default, all datasets also have the Relationship and Impact normalization features enabled. The Normalization Type is set to CTI Only.

Before you begin

  • You must create a job to normalize the datasets.
  • Enable inline or continuous normalization for a dataset to normalize when CIs are created.
  • Create a batch job to normalize CIs that are created when normalization is stopped, such as during upgrades.

To configure normalization settings for datasets

  1. On the BMC CMDB Dashboard, click Configurations.
  2. From the list, select Manage Normalization Rules > Dataset Configurations.
  3. Select an existing Dataset Configuration, and click .

  4. On the All Datasets Configurations page, set the normalization settings for the selected dataset.

    The following table describes the settings you can configure for normalization.


Dataset normalization settings

Field nameSetting

Description



Normalization Type

Name and CTI LookupNormalizes the product name, model, manufacturer name, CTI (Category, Type, and Item) attributes, and categories.

CTI Only

(Default: Selected) Normlizes only the CTI categories for a CI, but the Model and ManufacturerName attributes are not normalized.

If you select this option, you can map the categorization of the provider's data to the Product Catalog categorization. If there is no mapping, the Normalization Engine tries to create an entry with the categories that the data provider supplies.







Normalization Mode 

 

 
Inline

(Default: Cleared) If selected, normalizes data as it is created or modified. For more information about configuring inline normalization, see Configuring inline normalization.

Continuous

Normalizes data after a defined condition is met:

  • When a specified number of events occurs
  • After a specified interval of time

For more information about configuring a continuous normalization job, see Configuring continuous normalization.


Allow Unapproved CIs

If the check box is:

  • (Default) Selected: If the product is unapproved in the Product Catalog, the Normalization Engine normalizes the CI and sets its NormalizationStatus attribute to Normalized and Not Approved.
  • Cleared: If the product is unapproved, the Normalization Engine does not normalize the CI or if the Allow New Product Catalog Entry option is enabled, the system does not create a Product Catalog entry.


Allow New Product Catalog Entry

If the check box is:

  • Selected: If no entry for a CI is found in the Product Catalog, then a new product entry is created in the Product Catalog, using the attributes of the discovered product. The created Product Catalog entry is flagged as Approved. You can review and change the status of these entries in the Product Catalog.
  • (Default)Cleared: If no entry for a CI is found in the Product Catalog, no entry is created in the Product Catalog, and the NormalizationStatus attribute for the product is set to Normalization Failed.
Trusted

If the check box is:

  • Selected: The data model changes are not normalized.
  • Cleared: The data model changes are normalized.



Preserve Auto Impact Edit 

Apply Rule Always

Overwrites the manual edits that you do to the HasImpact and ImpactDirection attributes of the relationship instances with the values that are defined in the best-practice impact normalization rules.

For more information about the best-practice relationship instances, see Normalization and service impact.

Preserve Manual Edits

(Default) Retains any manual edits that you do to the HasImpact and ImpactDirection attributes of the relationship instances, instead of reapplying the values that are defined in the best-practice impact normalization rules.

For more information about the best-practice relationship instances, see Normalization and service impact.







Supported Features     

Version Rollup

Rolls the product versions (the MarketVersion attribute) to the highest version with which the licenses are associated. This feature provides more accurate version information for managing licenses.

For more information, see Managing software licenses in your organization using normalization and Creating a Version Rollup rule.

Note: The Version Normalization Feature is enabled by default.

Instance

Sets the row-level and attribute-level permissions for CIs as you define them.

For more information, see Normalization and instance permissions and Creating normalization rules to set row-level permissions.

Relationship

For relationships, replaces the existing names with the BMC recommended or custom names, based on the CI classes in the relationship.

For more information, see Normalization and best practice relationship rules and Creating a relationship rule.

Auto Impact

Sets the HasImpactImpactDirectionImpactPropagationModel, and ImpactWeight attributes on the relationship classes based on the defined rules. 

For more information, see Normalization and service impact and Creating an impact rule.

Custom

Sets attribute values of CIs and relationships based on the custom rules that you have defined.

For more information, see Normalization and custom rules and Creating a custom rule.

Suite Rollup

Defines suites and their products, and identifies an instance as a suite, a suite component, or a standalone application. This feature enables an accurate management of suite and individual licenses.

For more information, see Managing software licenses in your organization using normalization and Creating a Suite Rollup rule.

5. Click Save.

Was this page helpful? Yes No Submitting... Thank you

Comments