Super Contributor.. Super Contributor..
Super Contributor..

Invoke on New Triggered CIs Immediately

We have one MZ (full DFP range) with the Inventory and Discovery Activities.

We  have check that in the created job "Inventory Discovery by Scanner" the "Invoke on New Triggered CIs Immediately" is set, so when a new node arrivals in UCMDB through CallHome mechanism,  the job launchs against this node and we received a new scan file.

We have test this with one computer, we have delete from UCMDB a few days ago and the computer sends the callhome event. The Node, UDA and CallhomeEvent CI's have created in UCMDB.

We check into the computer for starting scanner and check the DataFlowProbe status, but nothing starts.

Is not supposed that this jobs starting immediately on new nodes?


We have deleted the CI's in the UCMDb a repeat this process with the same issue.

UCMDB 2019.02

CP 2019.11.102

Any ideas?

2 Replies
Outstanding Contributor.
Outstanding Contributor.

Re: Invoke on New Triggered CIs Immediately

That is not how the jobs will work. You must discover each of the Trigger TQL CIs and when those are discovered the job will run immediately.

If you start with nothing known in the UCMDB except the Discovery Probes:

  1. Run Range IPs by ICMP
  2. With the IP Address of target now known run Host Connection by Shell
  3. With the Shell (UDA, NTCMD, SSH) and Node now known this will trigger the Inventory Discovery by Scanner default trigger query scanner_shell

At this point if the target is still connected to the same IP Address then job Inventory Discovery by Scanner will connect to the shell and start the scannner executable and park the job. If the Inventory Discovery by Scanner job is not able to connect it will park the job and retry later.

This is where Call Home function and CallHome Processing job comes in to play. The UD Agent will send a callhome packet on restart of the UD Agent or if the callhome timeout (default 24 hours) is reached. The callhome packet is sent to URL0, URL1 or URL2 defined in UD Agent configuration with the UD Unique ID and IP Address of the host. This callhome packet is handled by a special Jetty servlet (default port 80) on the defined CallHome Data Flow Probe (DFP) and sent to the UCMDB Server as CIT CallHome Event. The job CallHome Processing will send request to the Data Flow Probe of the associated IP Address to unpark UDA specific jobs. The UDA specific jobs are; Install UD Agent, Uninstall UD Agent, Update UD Agent, and Inventory Discovery by Scanner. If, this is important, if the DFP has a parked UDA specific job for that host it will be unparked and the workflow will continue. If the DFP doesn't have a parked UDA specific job then nothing happens. In either case, the CIT CallHome Event is deleted from the UCMDB.

The feature Invoke on New Triggered CIs Immediately is used to specify whether the job will wait for the next invocation time to dispatch the new CIs or dispatch immediately. For example, if you run the Host Connection by Shell job every 12 hours at 8 AM and 8 PM. You discover a new IP Address, the trigger CI, at 1 PM. Without Invoke on New Triggered CIs the job Host Connection by Shell will run on the discovered IP Address at 8 PM.

If this response answers your question please mark it as the solution. Likes and thumbs up are always appreciated.


Tags (3)
Micro Focus Expert
Micro Focus Expert

Re: Invoke on New Triggered CIs Immediately

I don't see the need to use MZ here if it's defined on the full range of the probe.
And I don't trust how the TQLs are being handled for dispatching in MZs.
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.