Populating the Product Catalog
Each Product Catalog entry must be unique. A Product Catalog entry is considered unique based on the manufacturer name and the product name. These values correspond to the
Model attributes in a CI.
The names of some fields in the Product Catalog do not match their respective CI attribute names. The following table shows how some key CI attributes map to Product Catalog fields.
CI attribute name
Product Catalog field name
Categorization Tier 1
Categorization Tier 2
Categorization Tier 3
The following process diagram illustrates different paths you can use to populate the Product Catalog.
Paths to populate Product Catalog
- Manually add product entries — From the Product Catalog Console, you can create new companies or products, versions, and patches and define their status. For more information, see Creating custom Product Catalog entries.
- Import Product Catalog data provided by BMC — BMC releases Product Catalog data updates on a regular basis. For more information, see the online documentation BMC Atrium Core Product Catalog Data.
The BMC data contains only software products. If you are only tracking software, importing this data might be all that you need. However, if you are tracking hardware, services, or other types of products, you must create custom product entries manually, import data from external files, or use the Normalization Engine to create product entries.
- Import product entries from other sources — You can use BMC Remedy Data Import to load data from supported data sources, such as formatted files and spreadsheets, into staging forms and then the PDL:ESIDImportConsoleCustom form to import the data from the staging forms to the Product Catalog forms. For more information, see Overview of importing custom Product Catalog data. You can import companies and product information.
- Use the Normalization Engine to create product entries — You can configure the Normalization Engine to create Product Catalog entries based on the CIs in the BMC Atrium CMDB datasets. You must configure this option before normalizing the dataset. For guidelines and procedures, see Preparing the Product Catalog and planning classes for normalization.
When using the Normalization Engine to create product entries, verify that the CIs in the BMC Atrium CMDB dataset contain the appropriate values for the
Item attributes. Make sure that all CIs for a specific product have the same values for these attributes; otherwise, the Normalization Engine is likely to create duplicate entries for a product in the Product Catalog. If you have duplicates in the Product Catalog, you must remove them manually.
If you are implementing software license management, evaluate the
MarketVersion values of software CIs. Before normalizing the CIs and creating new Product Catalog entries, create Version Rollup rules to map related
VersionNumber values to a single
MarketVersion value. For more information, see Product Catalog and Software License Management.