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
How to Configure XML Enricher to Suit the Probe Deployment Mode
When the Data Flow Probe is installed, the XML Enricher is configured, by default, for the Standard Deployment mode.
Note The XML Enricher’s Windows service is configured with the Manual start up and the probe starts the XML Enricher service on demand when necessary. So you should not change the startup mode of the XML Enricher service.
If another Probe deployment is used, the XML Enricher settings must be manually adjusted to fit the deployment mode of the Probe.
Note
-
The XML Enricher configurations described below have been tested against the Data Flow Probe deployment modes.
However, other configurations may potentially be supported, provided that enough resources (memory and CPU) are available for the XML Enricher.
For details about the Data Flow Probe deployment modes, see the Support Matrix section of the UCMDB Help document.
-
This task relevant for Data Flow Probes meant for discovery (on Windows machines) only.
-
Configure the XML Enricher parameters
Configure the XML Enricher parameters to suit the Data Flow Probe deployment mode:
-
Set the XML Enricher mode and maximum amount of memory allocated by the Java Virtual Machine for the XML Enricher service, per the Data Flow Probe's deployment mode:
-
On the Data Flow Probe machine, locate the WrapperEnricher.conf file in the following folder:
c:\UCMDB\DataFlowProbe\bin\xmlenricher
-
Open the file in any text editor.
-
In the Java Additional Parameters section, locate the following parameter, and set the value per the Data Flow Probe deployment mode:
Parameter Description DsaiDataProvider The XML Enricher mode.
Probe Deployment Mode Small Database Standard Memory Enterprise Memory -
In the Maximum Java Heap Size (in MB) section, locate the following parameter, and set the value per the Data Flow Probe deployment mode:
Parameter Description MaxMemory The maximum amount of memory that the Java Virtual Machine allocates for the XML Enricher service.
Probe Deployment Maximum Memory Small 3584 Standard 5120 Enterprise 8192
-
-
Configure the maximum number of processing threads to allocate to processing scan files in the XML Enricher service for all management zones:
-
On the Data Flow Probe machine, locate the enricher.properties file in the following folder:
c:\UCMDB\DataFlowProbe\conf\
-
Locate the following parameter, and set the value per the Data Flow Probe deployment mode:
Parameter Description max_enricher_thread_number Probe Deployment Threads Small 1 Standard 2 Enterprise 4 Note One thread is used initially. For Standard and Enterprise deployment, the actual number of threads used is gradually increased by 1, depending on load conditions and up to the maximum number of threads (configured in this setting).
-
-
-
Restart the Universal Discovery XML Enricher service on the Data Flow Probe machine.
-
Navigate to
c:\UCMDB\DataFlowProbe\runtime\xmlenricher\scans\incoming
and analyze whether the scan file processing is at an acceptable level.
If there is a large build up of the scan files in the incoming directory that does not get cleared after some time and continues to grow, this indicates that the XML Enricher's does not have enough resources to process scan files. In this case, the number of threads needs to be increased.
Verify the number of threads that the XML Enricher service is using. For details, see How to Check XML Enricher Health Using JMX.
When increasing the number of threads, the amount of memory allocated to the JVM needs to be increased as well. If the Standard mode parameters are not sufficient, use the parameters for the Enterprise mode deployment.
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: