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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal CMDB11.0

Use > Data Flow Management > Data Flow Management Setup > Data Flow Probe Setup > How to Deploy Hotfixes and Track Hotfixes Applied on Data Flow Probe

How to Deploy Hotfixes and Track Hotfixes Applied on Data Flow Probe

Starting with version 10.30, packaging of hotfix files is improved to enable easy deployment and management, and a new JMX method showAllBinariesApplied was introduced to enable you to easily view and track all information about the hotfixes you deployed.

Note This hotfix deployment mechanism is applicable to engine hotfixes on probe only, not to content library hotfixes. Therefore the hotfixes for the following paths still follow the old process:

DataFlowProbe\runtime\probeManager\discoveryResources
DataFlowProbe\runtime\probeGateway\discoveryResources
DataFlowProbe\content

Also, invoking the showAllBinariesApplied JMX method will return the result about engine hotfixes only.

When you deploy hotfixes, you are actually deploying each of them separately in a different folder under the classes folder. After deployment, the hotfix path looks like the following:

<DataFlowProbe_install_dir>/classes/HF_QCCR1HXXXXX/com/hp/ucmdb/

The hotfix folder name where the classes are loaded follows the format of HF_QCCR1H<ID>. If the hotfix folder name does not start with the HF_ prefix, the classes for the hotfix will not be loaded.

The hotfix Readme file should be located directly inside the hotfix folder. For example, for HF_QCCR1H101112, the readme file is located in the folder ..\HF_QCCR1H101112/Readme_QCCR1H101112.txt, as shown in the screenshot below. If it has a different name and/or placed in a different location it will not be read.

Note

Hotfixes are loaded at probe startup. If a new hotfix is deployed, it will not be displayed until the probe restarts.
Every hotfix has a unique QCCR ID, which will be added to the hotfix folder name after the HF_ prefix.
When multiple hotfixes are deployed, class files from hotfixes will be loaded in the sequential order of QCCR IDs of the hotfixes. For example, if hotfixes HF_QCCR1H101112 and HF_QCCR1H123122 are deployed, the class files from HF_QCCR1H101112 will be loaded first. This is important to know in the corner case when a class file is deployed on the server side by two hotfixes.
This hotfix deployment mechanism is applicable for engine hotfixes on probe only, not for content library hotfixes. Therefore the hotfixes for the following paths still follow the old process
- DataFlowProbe\runtime\probeManager\discoveryResources
- DataFlowProbe\runtime\probeGateway\discoveryResources
- DataFlowProbe\content
Also, invoking the showAllBinariesApplied JMX method will return the result about engine hotfixes only.

Send Help Center feedback