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

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

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 as datasets are created.

You also have the option of applying these defaults to datasets that are already configured.

These settings include the option of full or incremental normalization. All of the other default settings can also be defined for each dataset.

In the Calbro example, the system configuration is set first 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.

Then, 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.

The following table describes the settings that you can configure for normalization, either for individual datasets or as a system default.


Dataset and system normalization settings

Setting

Value

Description

Normalization Type

CTI Only

(Default) Only the categories (Category, Type, and Item attributes) for a CI are normalized, but the Model and ManufacturerName attributes are not. For more information about using CTI Only, see BMC Remedy ITSM and category normalization.

If this option is selected, 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.

Name & CTI Lookup

The product name, model, manufacturer name, CTI attributes, and categories are normalized.

Disabled

(System Configuration only) Normalization is turned off.

Inline Normalization

Deselected

(Default) Normalize data in the continuous mode (if enabled) or, if defined, as scheduled.

For more information, see Configuring inline normalization.

Selected

Normalize data as it is created or modified.

For more information, see Normalization modes.

Allow Unapproved CI

Selected

(Default) 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.

Deselected

If the product is unapproved, the Normalization Engine does not normalize the CI or, if the Allow New Product Catalog Entry option is enabled, does not create a Product Catalog entry.

Allow New Product Catalog Entry

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. See the BMC Product Catalog and DML Guide and Preparing the Product Catalog and planning classes for normalization.

Deselected

(Default) If no entry for a CI is found in the Product Catalog, no entry is created in the Product Catalog, and NormalizationStatus for the product is set to Normalization Failed.

Enabled (Dataset Configuration only)

Selected

(Default) Normalization is turned on for the dataset to run all Normalization Features enabled for the dataset.

Deselected

Normalization is turned off for the dataset.

Normalize All Instances (System Configuration only)

Selected

All instances in datasets with normalization enabled are normalized, including instances that have been previously normalized.

Deselected

(Default) Only new instances in datasets with normalization enabled are normalized. This is an incremental normalization.

Normalization features (Dataset Configuration only)

Relation Name Normalization Feature

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 Configuring rules for normalizing relationships.

Impact Normalization Feature

Sets the HasImpact, ImpactDirection, ImpactPropagationModel, and ImpactWeight impact attributes on the relationship classes based on the defined rules.

For more information, see Normalization and impact relationships and Configuring impact normalization rules.

Suite Rollup Normalization Feature

Define suites and their products and identify an instance as a suite, a suite component, or a standalone application. This allows more accurate management of suite and individual licenses.

For more information, see Normalization and software license management and Configuring Suite Rollup normalization rules.

Version Normalization Feature

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

For more information, see Normalization and software license management and Configuring Version Rollup normalization rules.

Note

The Version Normalization Feature is enabled by default.

Instance Level Permissions Feature

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

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

Custom Normalization Feature

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 Configuring Custom normalization rules.

Auto Impact Manual Edit

Preserve Manual Edits

(Default) Retains any manual edits that you have made to the HasImpact and ImpactDirection impact 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 impact relationships.

Apply Rule Always

Overwrites any manual edits that you have made to the HasImpact and ImpactDirection impact 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 impact relationships.

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

Comments