"IIM". This data may be matched by installer evidence recognition rules in the Application Recognition Library to recognize installations of associated applications.How the FlexNet Inventory Agent gathers IBM Installation Manager (IIM) evidence
InstallationManager.datconfig.iniinstalled.xml
-
Windows operating systems:
- The registry entry
HKLM\Software\WOW6432Node\IBM\Installation Manager\appDataLocationis read to identify a directory. - Any
installed.xmlfile in that directory is added to the investigation list.
- The registry entry
-
UNIX-like operating systems:
- The file
/etc/.ibm/registry/InstallationManager.dat, which is the standard data location, is searched. - The user home’s
/etc/.ibm/registry/InstallationManager.datsubdirectory is also checked if present. - Any discovered
InstallationManager.datfiles are analyzed to locateconfig.inifiles. config.inifiles are then scanned for references toinstalled.xmlfiles.
- The file
How are software details recorded?
installed.xml files contain details about software packages that are installed on the device. Details are stored in an XML structure similar to the following abbreviated example:<location id='IBM Tivoli Storage Manager' kind='product' path='C:\Program Files\Tivoli\TSM'>
<property name='user.license,com.tivoli.dsm.server' value='tsm'/>
<package kind='offering' name='IBM Tivoli Storage Manager device driver' id='com.tivoli.dsm.devices' [...]>
<property name='cic.info.version' value='7.1.1.20141123_0819'/>
<property name='vendor.name' value='IBM'/>
[...]
Package details extracted by the FlexNet Inventory Agent for inclusion in the gathered inventory data include:
- Name is taken from package/@name
- Version is taken from package/property[@name='cic.info.version']/@value
- Publisher is taken from package/property[@name='vendor.name']/@value
installed.xml file illustrated above result in the following information being recorded in the inventory NDI file:<Package Name="IBM Tivoli Storage Manager device driver" Evidence="IIM" Version="7.1.1.20141123_0819">
<Property Name="InstallLocation" Value="C:\Program Files\Tivoli\TSM"/>
<Property Name="Publisher" Value="IBM"/>
</Package>
Identifying where IIM evidence has come from on a device
When the FlexNet Inventory Agent's inventory gathering process finds an installed.xml file on the filesystem during a filesystem scan, details of the path are noted in the tracker.log log file with messages similar to the following:
[2026-03-07T12:09:32+1100 (G, 0)] {42568} Scanning directory 'C:\' for files
[2026-03-07T12:09:32+1100 (G, 0)] {42568} The file 'C:\Path\installed.xml' has been detected as a possible package registry
[2026-03-07T12:09:32+1100 (G, 0)] {42568} Finished tracking files
Note: No logging of this nature is generated showing details of installed.xml files found based on path details obtained from well-known locations, such as through the ...\Installation Manager\appDataLocation registry entry on Windows, or details found in InstallationManager.dat files.
Review the contents of each installed.xml file listed in the logging to identify which specific file(s) contain evidence of interest.
On devices running Unix-like operating systems, a command like the following can also be used to find installed.xml files and search for particular details in them:
find / -name installed.xml -print0 | xargs -0 grep -H 'IBM Tivioli Storage Manager device driver'
Additional diagnostics
Additional diagnostic tracing information from the inventory gathering process can be obtained by enabling the following agent trace classes in the etcp.trace file:
- +Inventory/FileSystemScanListener
- +Inventory/Tracker/Package
- +Inventory/Tracker/Software/Files
Instructions on how to do this are located here: How to enable FlexNet Manager Suite diagnostic tracing.
This style of diagnostic tracing can help to identify exactly where installed.xml files have been found (including files that were not found through a filesystem scan, and so were not referenced in the tracker.log file), and what package details have been retrieved.
Here are some examples of the style of diagnostic tracing information that may be seen:
2026-03-07T17:45:43, pid 40184, thread 34304 (Inventory/FileSystemScanListener/General): CFileSystemScanListener - listener "IM" listing file "C:\Path\installed.xml" as REG_SYSTEM.
2026-03-07T17:45:43, pid 40184, thread 34304 (Inventory/FileSystemScanListener/General): CFileSystemScanListener - listener "IM" listing file "C:\Path\installed.xml".
2026-03-07T17:45:43, pid 40184, thread 34304 (Inventory/Tracker/Package): Package tracked: IBM Tivoli Storage Manager device drivers
Or:
2026-03-07T17:45:43, pid 40184, thread 34304 (Inventory/Tracker/Software/Files): TrackFile(1) RealFile [C:\Path\installed.xml] MainDirName [C:\] NameInStage [C:\]
What if details are incorrect?
Generally IIM evidence information about installed components contained within installed.xml files is assumed to be trustworthy. However, some IIM evidence may be an unreliable indicator of what is currently installed on computers, especially in environments where software components have been removed simply by deleting files from a filesystem without also taking appropriate action to remove details of the components from installed.xml files.
Some strategies to consider to deal with such situations are:
- Work with appropriate software owners to arrange to remove erroneous information from
installed.xmlfiles. - Exclude directories found to contain unreliable data from inventory scanning. (This will only help with
installed.xmlfiles found through filesystem scanning.) - If a consistent problem is found particular evidence, the relevant installer evidence rule in the ARL can be marked as Ignored. This will prevent the rules from being used to recognize installations on any devices. Note that this may also result in legitimate installations associated with that evidence failing to be recognized, so apply this technique with caution. In general, it is better to implement processes to cleanly uninstall software components in a way that updates details in
installed.xmlfiles appropriately.
Related resources
The following resource published by IBM contains additional information about IBM Installation Manager:
Additional Information
The following article summarizes different types of evidence gathered by the FlexNet Inventory Agent: What file and installer evidence is gathered by the FlexNet Inventory Agent?
Related Articles
IBM Installation Manager (IIM) installer evidence is not gathered if file system scanning is not enabled 7Number of Views What file and installer evidence is gathered by the FlexNet Inventory Agent? 179Number of Views What is InstallShield Multiplatform (ISMP) evidence? 58Number of Views What is InstallAnywhere (IA) Evidence? 94Number of Views What is Oracle Universal Installer (OUI) evidence? 195Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago