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.

Preparing the Product Catalog and planning classes for normalization

Before you can normalize CIs, you must configure the Product Catalog:

  1. Create Product Catalog entries for the class instances to be normalized.
    • The Normalization Engine normalizes any BMC.CORE:BMC_BaseElement child class.
    • For classes that do not have Product Catalog entries, you can configure the product categorization aliases to normalize CTI values.

      You can add products for other classes to the Product Catalog in the following ways:
      • Import data from external files — You can import data from an external file or from staging forms. For more information, see Overview of importing custom Product Catalog data.

        You can also import the Product Catalog data provided by BMC. Product Catalog data updates are released on a regular basis. For more information, see the BMC online documentation at
      • Use the Normalization Engine to create entries — You can configure the Normalization Engine to create Product Catalog entries from the dataset. You must configure this option before normalizing the dataset.
      • Create entries manually — From the Product Catalog Console, you can create new products, versions, and patches and define their status options.

        Before you use the Normalization Engine to create Product Catalog entries, consider the following information to avoid creating duplicate entries for a product in the Product Catalog and to avoid adding unwanted Product Catalog entries.
        • You can only set this option to create entries for a dataset, not for specific classes or instances in a dataset.
        • To select only specific classes or CIs to use to create Product Catalog entries, create a dataset containing only those CIs.
        • Verify that the CIs in the dataset contain values that you want to apply to all discovered or imported instances of those classes and products. For example, make sure that all CIs for a specific product have the same ManufacturerName, Model (Product Name), Category, Type, and Item categorization values. For more information about creating Product Catalog entries by using the Normalization Engine, see Normalization settings for datasets.
  2. Approve the Product Catalog entries to define the Definitive Media Library (DML) and Definitive Hardware Library (DHL). For more information about these steps, see Product Catalog status options.
  3. From the Product Catalog Console, use the Normalization Alias form to create product and manufacturer aliases. For more information on aliasing, see Setting up aliases for normalization and the Product name and manufacturer normalization aliases in the Product Catalog.
  4. For software license management or to use Version Rollup rules, set the Market Version field for each product. For more information, see Version Normalization.
  5. Create product categorization aliases. You can create these aliases from the Catalog Mapping in the Normalization console. For more information, see Mapping product categorization aliases.
  6. After setting up normalization, run the Normalization Simulation utility to preview normalization results.
Was this page helpful? Yes No Submitting... Thank you