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 DiscoveryContent Pack 26.00 (CP26)

Use > Discovery Modules > Hosts and Resources > Agent Driven Inventory Discovery > Agent Driven Inventory Discovery Configuration File

Agent Driven Inventory Discovery Configuration File

The Agent Driven Inventory discovery configuration file is agentDrivenInventoryConfiguration.xml, located in Adapter Management > Resources pane > Packages tree > DDMInfra > Configuration Files. This file controls most of the Agent Driven Inventory flow.

You can use this file to define which settings should be used during the scan, when the scan should happen, how the data should be provided back, and so on.

Note UCMDB UI does not support a full XML schema validation during the XML editing. It is strongly recommended to use third-party tools to perform a full result XML validation for the provided agentDrivenInventoryConfiguration.xsd schema to make sure that your configuration is valid.

This file includes the following sections:

Default schedule

This section must always exist in the schedule with <probe name="all"/>, which affects all the platforms. This is because in case of multiple schedules, it might happen that no other schedule except the default one affects the particular agent, which might be a problem for the overall flow to detect such.

The default scan configuration is organized as a standalone element named <default-settings>...</default-settings>.

Default schedule configuration

<default-settings>

  <probe-list>

    <probe name="all"/> <!-- affects all probes -->

  </probe-list>

  <isPrePostScriptAllowed>true</isPrePostScriptAllowed> <!-- Specifies whether to allow scanners to run pre-scan or post-scan scripts -->

  <PrePostScriptExecTimeout>5</PrePostScriptExecTimeout> <!-- The pre-scan or post-scan script maximum runtime (in minutes) -->

  <platformToScanConfigMapping><!-- Scan configuration - allows you to define different scan configurations based on different platforms and architecture -->

    <allPlatformsConfiguration>_hwonly.cxz</allPlatformsConfiguration>

  </platformToScanConfigMapping>

  <scan-schedule>

    <scan-frequency>7</scan-frequency><!-- Defines how often the scan should run in days -->

    <allow-scan>

      <scan-day name="any"> <!-- Defines scan days of a week (allowed values are from Monday to Sunday, and all, any, or * to mean any day) -->

        <hour>any</hour>  <!-- Defines hours in a day (allowed values are from 0 to 23, and all, any, or * to mean any time) -->

      </scan-day>

    </allow-scan>

  </scan-schedule>

  <!-- followScan - Immediately sends the scan results to Data Flow Probe after the scan is finished -->

  <send-schedule type="followScan">

  </send-schedule>

</default-settings>

Schedule instance
You can create as many independent custom schedules as you want. The following requirements must be met:
- schedule-instance id must be unique across all the defined schedules.
- schedule-instance id can contain only letters (a-z; A-Z), digits (0-9), and underscore(_).
For example, you want to create a schedule to discover software related information:
```
<schedule-instance id = "SoftwareInventory">
```
```
</schedule-instance>
```
Note The schedule-instance id value must match the parameter scheduleName value of the Agent Driven Inventory Discovery job. For details, see Agent Driven Inventory Discovery Job.
Data Flow Probe limits
Each schedule instance must have the Data Flow Probe limits that this schedule affects.

The Data Flow Probe name (appilog.collectors.probe.name) specified in the DataFlowProbe.properties file must be used to restrict the list of the Probes that are valid for the defined schedule.

The value all is used to affect all the available Probes in the environment.

Configuration to affect all the Data Flow Probes
```
<probe-list>
```
```
	<probe name="all"/> 
```
```
</probe-list>
```
Configuration to affect explicit Data Flow Probes
```
<probe-list>
```
```
	<probe name="myTestProbeNode1"/>
```
```
	<probe name="myTestProbeNode2"/>
```
```
</probe-list>
```

Scan level parameters

The following parameters exist in each schedule and affect the scan flow.

Parameters Description

Parameters	Description
`isPrePostScriptAllowed`	Specifies whether to allow scanners to run pre-scan or post-scan scripts. Default: true
`PrePostScriptExecTimeout`	The pre-scan or post-scan script maximum runtime (in minutes). Default: 5

isPrePostScriptAllowed

Specifies whether to allow scanners to run pre-scan or post-scan scripts.

Default: true

PrePostScriptExecTimeout

The pre-scan or post-scan script maximum runtime (in minutes).

Default: 5

Scan priority
If multiple scans are scheduled for the same time frame, you can use this section to set the scan priority. This section precedes the <scan-schedule> section.

You can set the scan priority value to any number, as long as it is an integer. The default vale is 100.

Example of scan priority
```

```
```
<scan-priority>1</scan-priority>
```

Result-sending parameters
This section allows you to configure when the scan results are sent to Data Flow Probe.

followScan. Immediately sends the scan results to Data Flow Probe after the scan is finished.
```
<send-schedule type="followScan">
```
```
</send-schedule>
```

Send Help Center feedback