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
Processing Scan Files
Processing Normal Scan Files
At the end of the enrichment process, a new enriched scan file is created; the enriched core file is converted to UCMDB CI and relationship data, and reported to UCMDB. If delta scanning was enabled in the parameters for the Scanner used to produce the scan file, the incoming scan file is stored in the Original directory for future use by the delta scan processing. If delta scanning was disabled, the incoming scan file is deleted.
Tip
-
If an error occurs, the original scan file is moved to a failure directory and is not deleted.
- If an enriched scan file for the same computer already exists, the old file is overwritten.
Reprocessing Normal Scan Files
Scan files can be reprocessed after they are enriched. For example, you may want to run this operation when you update the Software Application Index (SAI) file. For example, after you use Express Teaching to teach applications, you may want to reprocess scan files. Scan files for selected nodes are moved from the Processed folder to the Incoming folder. Then, the scan file is processed using the updated SAI file.
To reprocess normal scan files, see How to Reprocess Scan Files.
Processing Delta Scan Files
The delta scan file is used in conjunction with the previous version of the scan file located in the Original directory to reconstruct the new full version of the scan file. This full version is then moved into the Incoming directory, where it gets processed in the same way as other normal scan files.
At the end of the process, the reconstructed scan file is moved to the Original directory, ready for the next time a delta scan is found for this particular scan file instance.
For details handling delta scan files (Manual Deployment mode only), see How to Set up the Scanner to Handle Delta Scan Files in Manual Deployment Mode.
Note If the enriched scan file contains the hwOSUserProfiles attribute that has about 300,000 values, the Data Flow Probe maximum memory size should be increased by one gigabyte (GB). For details on how to increase the Data Flow Probe maximum memory size , see How to Update the Data Flow Probe Memory Size.
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: