This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

Normalization process

Normalization Engine works in the following ways:

  • Normalizes the CIs that have a status of Not Normalized or Normalization Failed or Modified After Last Normalization.
  • Normalizes all the CIs, if you set the configuration value to Normalize all the instances. This is useful when you make changes to product aliases or change the categories of the products in the Product Catalog.

The Normalization Engine normalizes non-normalized and modified CIs by evaluating CIs using the Product Catalog:

  • Product attributes — The Model, ManufacturerName, MarketVersion, and (if available in the CI) the MarketVersion, VersionNumber and PatchNumber attributes of the CI. Normalization Engine currently uses only the product attributes for normalization.
  • Signature ID — Stored in the Product Catalog and created by discovery tools for identifying products. For more information about generating the Signature ID, see Using signatures to identify products in the Product Catalog
  • File name and size — The name and size of the file.

    Note

    Signature ID and File name and size are used only with the Normalization Engine Java API. For more information, see BMC Atrium CDMB Javadoc, which is available from PDFs.

At every creation/update of the CI the Normalization Engine checks that the CI class is configured for normalization.

  • If the class is configured, the Normalization Engine continues the process based on the dataset configuration for mode of normalization (Inline or Continuous)
  • If the class is not configured, the Normalization Engine updates the NormalizationStatus attribute to Normalization Not Applicable and ends the normalization process for the CI.

The Normalization process is as follows:

  1. The Normalization Engine checks the Normalization Alias form for aliases for the ManufacturerName and Modelattributes.
  2. The Normalization Engine applies Version Rollup rules and sets MarketVersion using the Version Rollup rules. For information on Version Rollup, see Normalization and software license management and Configuring Version Rollup normalization rules.
  3. The Normalization Engine searches the Product Catalog for a product and its versions based on Model andManufacturerName.

    Note

     

    For versions 8.1.01 or later, if Model or ManufacturerName are NULL, you must manually set the values of Model to BMC_UNKNOWN and ManufacturerName to BMC_UNKNOWN in the Product Catalog. Set the values of CategoryType and Item appropriately.

    If the product is not found, it checks if the Allow New Product Catalog Entry option is enabled.
    • If it is enabled, the Normalization Engine creates a new product entry, sets the NormalizationStatus and ends the normalization process for the CI.
    • Else, the Normalization Engine updates the CI's NormalizationStatus attribute as Normalization Failed and ends the normalization process for the CI.
  4. Normalization Engine checks the product association with the Company populated in the CI.
    If it is not associated, the Normalization Engine updates the CI's NormalizationStatus attribute as Normalization Failed and ends the normalization process for the CI.
  5. If version in the Product Catalog is 'Unknown' and version of the CI is NULL, the Normalization Engine sets theNormalizationStatus and ends the normalization process for the CI.
  6. If MarketVersion is populated for a CI, the Normalization Engine searches the Product Catalog for a product that matches the CI using ManufacturerNameModel, and MarketVersion.
    • If it finds ManufacturerNameModel, and MarketVersion, the Normalization Engine substitutesCategoryType, and Item attribute values from the Product Catalog entry in to the corresponding CI attributes.
    • The Normalization Engine updates the NormalizationStatus attribute to Normalized and Approved or Normalized and Unapproved, and then ends the normalization process for the CI. Normalization of unapproved products depends on whether the Allow Unapproved CI option is disabled. By default, it is enabled.
    • Normalization checks the IsApproved flag for the entry.
    • Normalization Engine applies all the normalization features enabled for the dataset.
  7. If Normalization Engine does not find a match in the Product Catalog with ManufacturerNameModel, andMarketVersion, and if VersionNumber is populated for a CI, it searches the Product Catalog for a product that matches the CI using ManufacturerNameModel, and VersionNumber.
    • If it finds a ManufacturerNameModel, and VersionNumber, the Normalization Engine substitutesCategoryType, and Item attribute values from the Product Catalog entry in to the corresponding CI attributes.
    • The Normalization Engine updates the NormalizationStatus attribute to Normalized and Approved or Normalized and Unapproved, and then ends the normalization process for the CI. Normalization of unapproved products depends on whether the Allow Unapproved CI option is disabled. By default, it is enabled.
    • Normalization checks the IsApproved flag for the entry.
    • Normalization Engine applies all the normalization features enabled for the dataset.
  8. If both, MarketVersion and VersionNumber are not populated for a CI, Normalization Engine checks for match with ManufacturerName and Model. If it finds a match, the Normalization Engine substitutes CategoryType, andItem attribute values from the Product Catalog entry in to the corresponding CI attributes.The Normalization Engine updates the NormalizationStatus attribute to Normalized and Approved. 
  9. If the Normalization Engine does not find a Product Catalog entry with matching version, it checks if the Allow New Product Catalog Entry option is enabled.
    • If it is enabled, the Normalization Engine creates a new product entry, sets the NormalizationStatus and ends the normalization process for the CI.
    • Else, the Normalization Engine updates the CI's NormalizationStatus attribute as Normalization Failed and ends the normalization process for the CI.

After data is normalized, it can be reconciled to the BMC Atrium CMDB production dataset.

You can use the Product Catalog Mapping Alias with datasets configured for normalization to control automatic expansion of the Product Catalog. For example, a Product Catalog Mapping Alias might map all of the data provider's default Tier 1, Tier 2, and Tier 3 categorization to preferred categorization in the Product Catalog. The Allow New Product Catalog Entry option is selected for the data provider's dataset in the Normalization console. So, every time a new product name and manufacturer combination is discovered, a new Product Catalog entry is created, using the preferred three categorization tiers and the discovered product name and manufacturer.

 

Related Topic

Normalization status

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Marek Meres

    Re point 5: "Else, the Normalization Engine updates the CI's NormalizationStatus attribute as Normalization Failed and ends the normalization process for the CI." "Else" means NOT ("version in the Product Catalog is 'Unknown' and version of the CI is NULL") which means (NOT "version in the Product Catalog is 'Unknown'") OR (NOT "version of the CI is NULL"). If this was true Normalization would fail for every CI that has version != NULL which is obviously not true.

    Jul 25, 2016 02:16
    1. Anagha Deshpande

      Hello Marek

      Thanks for the feedback. I have updated the topic.

       

      Regards,

      Anagha 

      Jul 26, 2016 11:16
      1. Marek Meres

        Sorry, it does not seem so. Point 5 still claims that if 'version of the CI' is not NULL the NormalizationStatus is "Normalization Failed". Which is obviously not true - see point 7.

        Imho (based on 8.1.02 testing assisted by BMC engineer) this point should state:

        If VersionNumber on the CI is blank (NULL) the Normalization checks if there is a special Version "UNKNOWN" in the Product Catalog or there are no Versions at all. If so the CI is successfully normalized and the NormalizationStatus (whether "approved" or "not approved") is determined based on Product-Company association "Approved Product" flag (see point 4).

        If VersionNumber on the CI is blank (NULL) and there are any Versions but no special Version "UNKNOWN" in the Product Catalog  the NormalizationStatus is set to "Normalization Failed".

        Aug 03, 2016 06:30
  2. Marek Meres

    If points 8 & 9 are both true and CI has blank Version ('VersionNumber' is the attribute name in CMDB forms and 'Model/Version' in asset mgmt forms) and Allow New Product Catalog Entry option is NOT enabled the Normalization substitutes Categorization Tiers based on ManufacturerName & Model search results (point 8) but sets NormalizationStatus to "Normalization Failed" (point 9). Is it really so?

    Jul 25, 2016 02:20
    1. Anagha Deshpande

      Hello Marek,

      Thanks for your feedback. I will confirm this with SME and will write back to you.

       

      Regards,

      Anagha

       

      Jul 25, 2016 05:05
      1. Anagha Deshpande

        Hello Marek,

        If point 8 mentioned above is true, then the Normalization Engine updates the NormalizationStatus attribute to Normalized and Approved. I have updated the topic accordingly.

        Regards,

        Anagha 

        Jul 26, 2016 11:19
        1. Marek Meres

          Is it really so? So what about point 5 above and the "UNKNOWN" Version in the Product Catalog? Btw: I cannot see the update you mentioned in the documentation above.

          Btw (2): what is the difference between "Normalized but Not Approved" and "Normalized and Approved" statuses? Tests (8.1.02) shows that the latter is only set when both "Approved Product" on the Product-Company association and "Approved Version" on the Version-Company association are set to "Yes". In other cases it is set to "Normalized but Not Approved" (of course if there is a match in Product Catalog).

           

          Aug 03, 2016 06:39
          1. Anagha Deshpande

            Hello Marek,

            I have made the following change in point number 5 of Normalization process:

            5. If version in the Product Catalog is 'Unknown' and version of the CI is NULL, the Normalization Engine sets theNormalizationStatus and ends the normalization process for the CI.

            Regarding your second query — I will discuss this with SME and will write back to you.

            Regards,

            Anagha

             





             

            Aug 03, 2016 10:40
            1. Anagha Deshpande

              Hello Marek,

              Your understanding is correct. Normalized and Approved" status is set only when both "Approved Product" on the Product-Company association and "Approved Version" on the Version-Company association are set to "Yes".  

              Regards,

              Anagha

               

              Aug 10, 2016 03:47