Client Automation - How are the Software Signatures files generated and sent to Scalability Server and Agent ?

Products

• CA Automation Suite for Data Centers - Configuration Automation
• CA Client Automation - Asset Management
• CA Client Automation - IT Client Manager
• CA Client Automation
• CA Client Automation - Remote Control
• CA Client Automation - Asset Intelligence
• CA Client Automation - Desktop Migration Manager
• CA Client Automation - Patch Manager

Issue/Introduction

How are the Software Signatures files (used by AM Software Signature Scan collect task) generated and sent to Scalability Server and Agent ?

Environment

Release: UASIT.99000-12.9-Asset Intelligence
Component:

Resolution

1- When a new Software Definition is created or updated (manually or via Engine job moteur « Default Software Contents Download Job »), a flag is set in database to indicate that new versions of Software Signature Files should be generated. Current version numbers for Windows and Linux/Unix are incremented in database.
 

<Please see attached file for image>

Here is a SQL query showing the value of flag and version number of files :
 

SELECT 'Flag = '+LTRIM(STR(set_val_lng)) FROM ca_settings WHERE set_id=5
UNION
SELECT 'Windows Version = '+LTRIM(STR(set_val_lng+1)) FROM ca_settings WHERE set_id=4
UNION
SELECT 'Unix/Linux Version = '+LTRIM(STR(set_val_lng+1)) FROM ca_settings WHERE set_id=6
 

 
Example 1:
 

Flag is not set. Current version number of files is 54

 

<Please see attached file for image>

Example 2:
 

Flag is set. Current version number of files is 55
 

<Please see attached file for image>

2. On Domain ITCM when Engine executes a Scalability Server collect Job, it checks the flag in database.

If it is set, it starts the Software Signature Files generation procedure. Big SQL Queries are executed and this could take time on CPU and Signature files are create on DOMAIN ITC in directory :

C:\ProgramData\CA\eso_fingerprints

And flag is set to 0
 
Example :

Windows file is W0000054.xml
Unix file is U0000054.xml
 

<Please see attached file for image>

3. Next Engine transferts a compressed version of files to the Scalability Server.

By default transfert is made with cfftplugin and port TCP 4728

See these documents for detail about transfert and its configuration :
 

https://comm.support.ca.com/kb/how-to-configure-engines-to-use-caft/kb000040272
https://comm.support.ca.com/kb/details-about-file-transfer-server-throttling-parameter/kb000030814

 
So Scalability Server receives the last Software Signature files when Engine execute its collect job.




4. the file is put on the Scalability server in these directories :
 

For Windows : C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFW
For Unix/Linux : C:\Program Files (x86)\CA\DSM\ServerDB\SECTOR\SSFU

 

<Please see attached file for image>

 

<Please see attached file for image>

The ZML files could be uncompressed using tools like Winzip of 7-Zip to see the XML file.
 
 

5- When AM Agent is executed on the machine and when it executes the Software inventory "Signature Scan" a download of latest signature ZML file is made (if the file is not yet present) and uncompressed in its directory :

For Windows : C:\Program Files (x86)\CA\DSM\Agent\units\00000001\uam
 

<Please see attached file for image>

For Unix/Linux : /opt/CA/DSM/Agent/AM/data/work
 

<Please see attached file for image>