How are the Software Signatures files (used by AM Software Signature Scan collect task) generated and sent to Scalability Server and Agent ?
Client Automation - All versions
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.
Here is a SQL query showing the value of flag and version number of files :
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 :
And flag is set to 0
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 :
How to configure Engines to use CAFT - Article ID: 40272
Details about File Transfer Server Throttling parameter - Article ID: 30814
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 :
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
For Unix/Linux : /opt/CA/DSM/Agent/AM/data/work