Ad-hoc Evaluation of a Software Policy, how to track the events in the logs ?

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

A software policy could be configured for an Ad-hoc evaluation :

How ad-hoc evaluation is done ?
Which entry in the log file shows the registration, which registration event should really trigger the evaluation of the SW policy ?
In which log files can the evaluation and job container creation be tracked ?

Environment

Client Automation - All Versions

Resolution

Example :

1- A Software Policy "TEST POLICY" is linked to group "All Computers" and has option ad-hoc evaluation option "Only when new (or re-installed) targets report their inventory" set :

 

2- A new machine COMP1 is created.

This machine executes caf register for the first time

The information is collected by the Engine (collecting its scalability server) and in <enginename.log> we could see a message 
Created computer compname

Example :

2025-05-22 15:18:03 Performing Job:<ssname> Collect
2025-05-22 15:18:05 Created computer COMP1
2025-05-22 15:18:06 Common inventory information updated for COMP1

3- In TRC_<enginename>*.log following lines are written to indicate that engine is sending the notification 1.2.2.1 (COMPUTER_CREATED)

220525-15:18:05.4633191L|001596|00002d10|SystemEngi|cmEngine        |cAmoDomain::SendNoti|000000|DETAIL | SendNotification 1.2.2.1, <notification>
220525-15:18:05.4705591L|001596|00002d10|SystemEngi|amLogAndNotify  |cAmoLog.h           |000391|INFO   | Created computer COMP1

 

4- InstMan receives the 1.2.2.1 notification and a "Target evaluation" task is created for this computer

In TRC_USD_INSTMAN*.log

220525-15:18:08.3914888L|002136|000006b4|NotMan    |NM:00           |imnothndl.cxx       |000548|INFO   | Notification processed: 1.2.2.1, uuid: <UUID_COMP1>
220525-15:18:08.4060812L|002136|000006b4|NotMan    |NM:00           |imnothndl.cxx       |000576|NOTIFY | Notification unit automatically created: COMP1.
...
220525-15:18:13.6766327L|002136|000006b4|NotMan    |NM:00           |cmpevtsk.cxx        |000695|INFO   | ComputerEvaluationTask::addTarget
220525-15:18:13.6850388L|002136|000006b4|NotMan    |NM:00           |cmpevtsk.cxx        |001088|INFO   | ComputerEvaluationTask::find
220525-15:18:13.6952711L|002136|000006b4|NotMan    |NM:00           |cmpevtsk.cxx        |001172|INFO   | ComputerEvaluationTask::create
220525-15:18:13.6953806L|002136|000006b4|NotMan    |NM:00           |task.cxx            |000246|INFO   | Task: 00000000-0000-0000-0000-000000000000: Is created

In GUI under System Delivery Engine a "Target Evaluation" Task is created

 

With following SQL Query it is possible to see the computers which are in a Target evaluation task.

lock 32 means : COMPUTER_LOCKED_BY_EVAL_CREATE 

select a.agent_name, t.locks
from ca_agent a
inner join usd_target t ON a.object_uuid=t.objectid
where a.object_uuid in 
   (SELECT comp FROM usd_link_grp_cmp WHERE grp in (SELECT objectid FROM usd_cmp_grp WHERE objectid in (SELECT referredentity FROM usd_task WHERE tasktype=13)))

 

When the "target evaluation" task is done, the lock 32 is removed.

5- At scheduled time, PolMan, executes the "Target Evaluation" task.

In TRC_USD_POLMAN*.log :

220525-15:33:20.7591284L|003644|00002c84|PolMan    |PM:00           |task.cxx            |000347|INFO   | Task <Task_UUID> (Comp Eval): Is activated
220525-15:33:20.8638663L|003644|00002c84|PolMan    |PM:00           |jobcont.cxx         |001932|NOTIFY | Policy eval begin:TEST POLICY,uuid:[<uuid>].
220525-15:33:20.9769078L|003644|00002c84|PolMan    |PM:00           |jobcont.cxx         |002733|NOTIFY | Policy eval end:TEST POLICY,uuid:[<uuid>],elapsed:0.