Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Inventory Discovery
- Inventory Discovery Overview
- Inventory Discovery Scanners
- Inventory Discovery Deployment Overview
- Scan Files
- Processing Scan Files
- Scan File Processing Power
- XML Enricher
- XML Enricher Log Files
- Application Teaching
- Using Rules to Teach Applications
- Enriched Scan File Structure
- Hardware and Software Recognition
- App Store Applications
- Custom Hardware or Asset Mapping
- Inventory Tools
- BDNA Normalize Integration
- Discovery Options for Client IP Ranges
- How to Run Inventory Discovery
- How to Run Inventory Discovery Manually
- How to View Discovery Status of an Inventory CI in JMX
- How to View Agent Deployment Log for an Inventory CI in JMX
- How to Edit Pre and Post Scan Scripts
- How to Set Up Asset Fields for Data Collection
- How to Set Up Asset Fields for Data Collection - Example
- How to Set up the Scanner to Handle Delta Scan Files in Manual Deployment Mode
- How to Configure XML Enricher to Suit the Probe Deployment Mode
- How to Configure the Maximum Number of Threads to Process Scan Files
- How to Check XML Enricher Health Using JMX
- How to Limit the XML Enricher Port to Allow Local Connection Only
- How to Reprocess Scan Files
- How to Import SAIs to the Data Flow Probe
- How to Import Normalization Rules to the Data Flow Probe
- How to Configure and Optimize Inventory Discovery
- How to Configure Analysis Asset Fields
- How to Map Scan File Attributes to UCMDB
- Mapping Hardware or Asset Fields to UCMDB - Use-Case Scenario
- How to Set Extract Options
- How to Filter Discovery Results to UCMDB
- How to Enable Application Virtualization Discovery
- How to Rename Scanner Executable Files
- How to Integrate BDNA Normalize
- How to Discover Client IP Ranges Without SNMP
- How to Discover Windows Device Drivers using the Inventory Discovery by Scanner Job
- Scanner Command Line Parameters Overview
- Scanner Command Line Parameters
- Scanner Information Type Parameters
- Scanner File Locations
- Web Server Configuration for Saving Scan Files via HTTP
- XML Enricher Directory Structure
- Enriched XSF File Structure
- Inventory Discovery User Interface
Enriched Scan File Structure
The XML Enricher reads scan files and outputs enriched XML scan files containing all of the original data as well as data identified in the application recognition step.
Each file is stored as a <file> element. When a file is identified as belonging to an application, two attributes are added to the element:
-
versionid
-
flag
For example,
<file name=”winword.exe” size=”12345” versionid=”1111” flag=”M”/>
represents a file named winword.exe identified as belonging to the application with a version ID of 1111. The type of the file is “M”, which means Main file. The possible values for the type field are:
flag | “type” tag in enriched XML file |
---|---|
Main | M |
Associated | Y |
3rd Party | 3 |
Device Driver | A |
Unknown | N |
The versionid attribute refers to the unique ID associated with every version in the SAI library. In an enriched XML scan file, the <applicationdata> section contains a list of applications identified on the machine along with the version IDs.
For example:
<applicationdata> <application version="6.0 sp1" release="6.0" name="Internet Explorer" desc="Microsoft Internet Explorer" publisher="Microsoft" language="English" os="Windows 98/NT/2K/ME/XP" type="Internet browser software" typeid="122252" maindir="C:\Program Files\Internet Explorer" lastUsed="2004-05-05 00:00:00" versionid="12790" releaseid="131" /> <application version="6.0 sp1" release="6.0" name="Outlook Express" publisher="Microsoft" language="English" os="Windows 98/NT/2K/ME/XP" type="Desktop communications software" typeid="105020" maindir="C:\Program Files\Outlook Express" lastUsed="2004-05-05 00:00:00" versionid="12792" releaseid="372" licencedby="12790" licencedbyrelease="131" /> </applicationdata>
The example above could be found for a machine with just two applications on it: Microsoft Internet Explorer and Microsoft Outlook Express. The licencedby attribute indicates that Microsoft Outlook Express is licensed by Microsoft Internet Explorer. In other words, while both are licensable applications, this machine requires one license for Microsoft Internet Explorer; with this license, no separate Outlook Express license is required.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: