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 Job

Agent Driven Inventory Discovery Job

Introduction

This job runs hardware and installed software inventory discovery by UD Agent driven scanners.

Discovery Flow

This job is the last step in a chain of inventory discovery activities that parses the scan file result updated by each process. Currently, the job does not reach the destination by any means, it is isolated to the level of the Probe File System in order to get the proper file from the file system, parse it, and produce the vector of CIs that are populated to the UCMDB.

Note Each instance of this job can handle only one schedule result using the parameter scheduleName. That is, if you have three schedules defined in the agentDrivenInventoryConfiguration.xml file, you should create three job instances to handle these schedules. To do so,

Create a new job instance by right-clicking this job, selecting Save as, and typing the name that you want.
Set the parameter scheduleName value of each job instance to the schedule-instance id defined in the agentDrivenInventoryConfiguration.xml file. (For the default schedule, default is used)

Trigger TQL

CI	Attribute Value
UDA	NOT Discovery Probe Name Is null

Adapter Information

This job uses the Agent Driven Inventory Discovery Adapter.

Triggered CI Data

Name	Value
ProtocolList	${SOURCE.root_class}
codepage	${SOURCE.codepage:NA}
credentialsId	${SOURCE.credentials_id:NA}
hostId	${Node.root_id}
hostName	${Node.name:NA}
ip_address	${SOURCEapplication_ip}
macList	${SOURCE.arp_mac:NA}
nodeGUID	${Node.ud_unique_id:NA}
primaryDNSName	${Node.primary_dns_name:NA}
primary_ip	${Node.primary_ip_address:}

Workflow Steps

Step Name	Module	Failure-policy
Remove Local Scan Log File	RemoveLocalScanLog.py	optional
Wait XML Enricher Process	WaitEnricherProcess.py	mandatory
Parse Enriched Scan File	ParseEnrichedScanFile.py	mandatory

Final Step Module
ReleaseResources.py

Adapter Parameters

Parameter	Default Value	Description
collectIPv6Connectivity	false	Specifies whether to collect the IPv6 related connectivity.
discoverRunningSW	Microsoft Hyper-V Hypervisor, VMware VirtualCenter, Virtualization Layer Software	Determines which running software should be reported.
filterP2PProcessesByName	system, svchost.exe, lsass.exe, System Idle Process	A comma-delimited list of the names of the processes that are not reported. Note This parameter affects only P2P discovery. To prevent P2P running, enter an asterisk (*) as the value.
ignoreP2PLocalConnections	false	If the value of this parameter is set to false, P2P discovery does not ignore local connections. That is, when a client and server are installed on the same host and the client-server relationship connects between them, P2P discovery should report this relationship.
MappingConfiguration		Specifies scan file model mapping configurations.
P2PServerPorts	*	A comma-delimited list of server ports. Only processes connected to these ports (as client or server) are discovered, together with this port. This parameter can include a number or a known name. An asterisk (*) signifies all ports.
PrePostScriptExecTimeout	5	The pre-scan or post-scan script maximum runtime (in minutes).
scheduleName	default	The name of the scheduled run whose results are processed by the job.

Send Help Center feedback