Customizing the software catalog
The software catalog contains signatures that allow for identifying software installed on the computers in your infrastructure. It is updated by IBM on a regular basis. However, due to the number of software products that are available on the market, a product that you are using might not be included in the catalog. In this case, you can create a custom signature to ensure that the software is properly detected and reported. To get a better understanding of the software catalog concepts, check out the Software catalog overview document.
Before you start creating your own signatures, it might be worth checking the bigfix.me site. It’s a place where you can find various resources for IEM, including custom signatures created by other members of the community. You can download such signatures and import them to your Software Use Analysis. The functionality is available from version 188.8.131.52.
If you decide to create custom signatures, follow a process that will allow you to ensure that the signatures are of high-quality. Start your work by identifying products that you expect to discover but are not reported or are missing from the software catalog. Next, organize your work to ensure that the most important products are given the highest priority. Then, determine what files or packages can be used to detect the software and report its usage. Finally, create the signatures. To get more information about the process as well as instructions for creating signatures in Software Use Analysis, read the Customizing the software catalog guide.
Apart from the guide, you can also use the Signature development checklist. You can tick off each point on the list as you go through the process to ensure that your signatures are effective and properly discover the software.
After you create your custom signatures, consider contributing them to the SUA signature community.