This documentation supports the 18.08 version of BMC Atrium Core.

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

Normalization status

This topic describes the various normalization statuses available for a CI, the description for each status, and how you can view the status. 

Each CI has a NormalizationStatus attribute to track the CI's stages of normalization.

To view the Normalization status

You need to update the BMC_BaseRelationship and BMC_BaseElement classes to view the normalization status.  

To update BMC_BaseRelationshipTo update BMC_BaseElement
  1. From the BMC CMDB Class Manager, open BMC_BaseRelationship.
  2. Edit BMC_BaseRelationship.
  3. From the Attributes tab, select the Normalizationstatus attribute, and click Edit
  4. Select No for the Hidden option.
    The Normalization Status field is displayed in the BMC.Core:BMC_BaseRelationship form.
  5. Perform a query to find the normalization status.
  1. From the BMC CMDB Class Manager, open BMC_BaseElement.
  2. Edit BMC_BaseElement.
  3. From the Attributes tab, select the Normalizationstatus attribute, and click Edit.
  4. Select No for the Hidden option.
    The Normalization Status field is displayed in the BMC.Core:BMC_BaseElement form.
  5. Perform a query to find the normalization status.

Normalization status values

The following table describes the possible values for the NormalizationStatus attribute.


Normalization Status values

Status

Numeric Value

Description

Not Normalized

20

The default status of a CI instance is always Not Normalized.

Not Applicable for Normalization

30

The CI is not normalized but did not fail normalization because for some classes, normalization is not applicable. The Normalization Engine assigns this status to CIs with classes not configured for normalization. If required, you can configure the classes or exclude them for normalization. If a class is excluded from normalization, it will affect all CIs created or updated after exclusion, and not those that were there already.

Normalization Failed

40

The CI is not normalized because no Product Catalog entry is found for the CI.

Normalized but Not Approved

50

The CI is normalized but not approved because the CI matched a Product Catalog entry that is not approved.

Normalized and Approved60

The CI is normalized and approved because the following items are true:

  • The CI matched a unique entry in the Product Catalog.
  • The matching product is approved.
  • The CI did not match a Product Catalog entry and the Normalization Engine created a new entry for it. 

Note

Normalization creates entries in the Product Catalog only if you have enabled Allow New Product Catalog Entry for a data set. By default, this setting is disabled.

Modified After Last Normalization

70

The CI was normalized previously but has changed since it was normalized. This can happen if the CI has been normalized but at least one attribute that can be normalized has been modified.

Notes:

  • If the data set is set to Inline normalization, you might not see this status for a CI, as this status appears only for Continuous and Batch mode normalization.
  • If you face data load or performance issues in Atrium Core, then for more information see, Troubleshooting Data load or Performance Issue in Atrium Core.

Note

The NormalizationStatus attribute has an additional value named Other. This value is for future use.

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

Comments