Could please follow the below steps -
1. Set the NE type as Name & CTI lookup for respective dataset
2. Create entries in NE:ProductNameAlias form like
Manufacture Name Product Name
Discovered CI MS Office 2007 Micro
PC Entry Microsoft Office 2007 Microsoft
3. Restart the AR Service
4. Discovered CI should get replaced with PC entry
NOTE: This would be replacing only Manufacture Name and Product Name
B. Product Catalog Alias
1. From the NE configuration set the NE Type as CTI
2. Create the Entries in ProductNameAlias form like
Discovery Product Categorization – Production categorization
Discovered Cat Tier 1 – Hardware Prod Cat Tier 1 - HARDWARE
Discovered Cat Tier 2 - Processing Unit Prod Cat Tier 2 - SERVER
Discovered Cat Tier 3 – Server Prod Cat Tier 3 - PROCESSING UNIT
3. Restart AR Service
4. Discovered Product Categorization should get replaced with Product Categorization
NOTE : This would be replacing only CTI values.
Thanks and Regards,
JD, we are trying to come up with a clean and uniform list of products before pushing them to the product catalog.
We are pulling in data from several different sources, ADDM, SCCM, and csv's.
Neither the Model, or Manufacturer are getting substituted even though values are listed in the NE:ProductNameAlias table. The logs indicate the substitution, but it does not actually substitute the value on the CI.
We are also having the same issue with the Product Catalog Alias Mapping records. Log indicates substitution, but CI's never actully get updated.
Is there workflow somewhere that is supposed to be making the substitution?
Thanks you for the reply. These scenarios do not work, we have been trying this all along.
I notice that you are restarting AR System service everytime you make a change. I would imagine this is to restet the NE cache, but this does not work either.
Wondering if there is workflow that is supposed to be making the substitution. If so, do you know what it is called?
The Aliases defined for Product Name & Manufacturer Name in NE:ProductNameAlias/Product Catalog Alias mappings form is used by NE to substitute the CI values of model/nafucturer name with the alias mapping to do a lookup in Product Catalog, to rephrase is again the aliases are used in NE workflow to actually lookup data in Product Catalog by substituting the CI model/manufacturer name with the aliased Product/Manufacturer to find a match in Product Catalog, if it finds a match only then is the Model/Manufacturer Name in CI is replaced by what is defined in Product Catalog depending upon the Normalization Type being set, If there is no match found in Product Catalog but you have the setting "Allow New Product Catalog" checked for the dataset, then NE will create a entry in Product Catalog as well as update the CI with the aliases (which correspond to data in Product Catalog).
I think you need to remove the existing entry from the "product catalog advanced search" form, provide proper model + manufacturer names in NE:ProductNameAlias form, create "catalog mappings" from the Atrium:Console itself for the desired product,check "Allow new entry in Product Catalog" and then run the normalization job.
This will result in new product catalog entry in the product catalog with the target values (catalog mappings) which mapped CTIs and Model + Manufacturer Name instead of the source (discovered) CTI + Model Name + Manf Name.
1. Let us assume the Product Catalog is completely empty.
2. According to the NE Normalization Process documentation, my issue is failing at step 2.. It should at this point substitute using the Alias value unless of course the documentation is wrong. It is at Step 3 that is searches the Product Catalog.
3. My particular issue also fails at Step 5. Two different scenarios.
It is at Step 7 that it will check the Dataset to see if "Allow new Product Catalog entry" is checked.
The whole Idea is to clean up the data before pushing into the product catalog.
I just responed to Josie another reply.
Step 2 of the Flowchart may need to be reworded in the documentation. It says, "Replace Product and Manufacturer Names from Product Name Alias Form"
Step 2 Detail says;
Step 2: NE Checks NE:ProductNameAlias form for aliases. Either they are assuming there is already an entry in the Product Catalog, in which case there would be no need to normalize.
No, problem is still there.
Product Catalog is empty.
One record in NE:ProductName Alias and a different record in Product Catalog Alias Mapping.
CI's set up with names that would come from discovery. Normalization does not replace Product name attribute on first CI. And Normalization does not replace CTI from the Producat Catalog Alias Mapping record. The logs indicate that they would be used, but the actual substitution does not take place.
In Documentation Step 2 of Normalization Process says
"Replace product and manufacturer names from the NE:ProductNameAlias form".
This replacement does not mean updating the alias values in the CI, since this step is before the step 3 which does a lookup in Product Catalog, all that step2 indicates is that it will substitute the Model/Manufacturer Name with the aliases defined, so that it will help NE to locate the record in Product Catalog.
Data in Product Catalog will have the following values for Product/Manufacturer Name.
Microsoft Office Word 2007 / Microsoft Incorporated.
CI can contain the following values for Model/Manufacturer Name
Word 2007/Microsoft Inc.
User defined aliases as follows.
Word 2007 maps to Microsoft Office Word 2007
Microsoft Inc maps to Microsoft Incorporated.
What Step 2 will do is that normalization engine internally will replace Word 2007/Microsoft Inc to Microsoft Office Word 2007/Microsoft Incorporated and do a lookup in Product Catalog if it finds a match it will update the CI's CTI values and Product/Manufacturer Name with the data in Product Catalog which will be same as the Aliases defined.
Now in your case since the Product Catalog is empty, if as per Step 7 you have enabled "Allow new Product Catalog entry" for a dataset, then NE will create a entry in Product Catalog with values
Microsoft Office Word 2007 / Microsoft Incorporated for Product/Manufacturer Name which it has replaced in step2 and update the CI with the same.
Use of Aliases is as follows different Discovery Sources can bring in data in different ways for example,
Some may discover Product/Manufacturer Name as Office Word 2007 / Microsoft Corp others May discover it as Microsoft Word 2007/Microsoft Inc, to normalizae both these data to the golden data in Product Catalog which has Microsoft Office Word 2007 / Microsoft Incorporated we define aliases as
Office Word 2007 maps to Microsoft Office Word 2007
Microsoft Word 2007 maps to Microsoft Office Word 2007
Microsoft Corp maps to Microsoft Incorporated
Microsoft Inc maps to Microsoft Incorporated
Hope this explanation helps, let me know if you need more clarification.
We can update the documentation with concrete example to make it more understandable.
Thank you Josie.
I made an entry in the Product Catalog and re-ran the Normalization Job it now replaces the Product Name with the expected value.
Documentation may need some clarification, i.e., MUST HAVE a value in the Product Catalog to use as the ACTUAL NAME on the NE:ProductName Alias entry. ALIAS NAME will be the name of the Discovered Product Name. Perhaps show some examples as well.
I have set your response as the Correct Answer.
Thank you for the clarification.