Known-as associations let you associate the software resources that are similar but have variations in their company names or software names. When you set up the known-as associations, you define a wildcard for a specific known-as name. When a new software resource is added to the Software Catalog, it is compared to the known-as wildcards. If a wildcard match is found, the company name or the software resource name is changed to the known-as name for that wildcard.
Create any necessary known-as associations before you begin to populate the Software Catalog or as soon as you find duplications. New known-as associations do not affect existing software resources.
When software resources originate from multiple sources, their company names and software names can be inconsistent. Normally, if two software resources are identical but their identifying information is different, they are considered to represent different software. You can create known-as associations and wildcards to associate two software resources so that they are identified as being the same software. The known-as associations help you to identify software resources accurately.
You can create known-as associations for a company or a software resource as follows:
During the import of a package, its company name is compared to the company wildcards. If a wildcard match is found, the company name in the new software resource is changed to the known-as company name for that wildcard.
For example, you associate the wildcard expression Symantec* with Symantec Corporation. When you import any software resource whose company name is Symantec, Symantec Corp., or any other variation, its company name is changed to Symantec Corporation.
During the import of a package, its name is compared to the software known-as wildcards. If a wildcard match is found, the name of the new software resource is changed to the software resource name for that wildcard.
For example, you might create a wildcard to replace MS Office with Microsoft Office.
Be sure to make the wildcard restrictive enough. Otherwise, you might associate multiple software resources that have the same name but do not represent the same software. For example, the wildcard MS Office* changes MS Office Standard, MS Office Professional, and Microsoft Office Enterprise to the same name. Such associations can cause problems with the software identification.
The unique identifiers of the associated software resources are not changed even when their company names or software names change.
The wildcard checks and associations occur when software resources are added to the Software Catalog from the Import wizard or from the Software Discovery scan. When you create a new known-as wildcard, existing software resources are not affected even if they match the wildcard.
When you resolve duplicate software resources, the association that is created appears in the Known As Mappings list.