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 Integrate BDNA Normalize with Universal Discovery
This task describes how to integrate BDNA Normalize. After BDNA is installed, and after the configurations are performed on the Data Flow Probe, the normalized installed software data produced by the scanner-based inventory is normalized using the BDNA Technopedia catalog instead of the Universal Discovery application library (SAI). To enable this integration, perform the following:
-
Configure the Data Flow Probe
-
Edit the dataflowprobe.properties file. To do this, go to <DataFlowProbeInstallDir>\conf directory.
where <DataFlowProbeInstallDir> is the directory where Data Flow Probe is installed.
-
Find the following string and change the value to true:
com.hp.ucmdb.discovery.probe.agents.probemgr.
xmlenricher.external.application.recognition=false (default = false). -
(Optional if you want to enable Debug) Find the following string and change the value to true:
com.hp.ucmdb.discovery.probe.agents.
probemgr.xmlenricher.external.application.recognition.
debug=false (default = false).Note For more information on Debug mode, see BDNA Normalize Integration.
-
-
Install BDNA Normalize
Install BDNA according to the vendor instructions.
-
Configure BDNA
- Double-click the Normalize shortcut that should be created by BDNA Normalize on the Windows desktop.
-
In the Data Source pane, locate HP XSF and then click . The Normalize Settings dialog box opens.
Note If the HP XSF process has not been created, click on New Process and select "HP Universal Discovery (XSF)" as the datasource.
-
Click the Data Source tab.
-
Review the settings in the Input Folder - it should point to the <DataFlowProbeInstallDir>\runtime\xmlenricher\Scans\ProcessedNew directory.
-
In Actions section, the XSF Out field should point to the <DataFlowProbeInstallDir>\runtime\xmlenricher\Scans\ProcessedCore directory.
-
Results
Data enriched by BDNA can be pushed using integration adapters to other systems.
Tip Use the newly-created RecognizedBy (recognized_by) attribute for the Installed Software CI to locate and leverage BDNA-created data. If the value of this attribute is "BDNA" - then installed software is normalized using the BDNA Technopedia catalog. If value is "SAI", the installed software CI is normalized using the Universal Discovery application library (SAI). Attribute values can be seen by using the CI Types pane.
For more information on CI Types and attributes, see CI Type Manager Page.