A Capture Profile is sent to a target in the form of a file. This happens when a profile is sent for the first time, or updated, or re-sent by System Manager.
-
For a Windows or an OpenVMS target, there is one file called APMconfg.txt.
-
For a UNIX/Linux target, there are two files called APMconfg and APMjob.
-
For Oracle or SQL Server or VMware targets, the file(s) are the same as those for the system here the Acquire is hosted (Windows or UNIX/Linux).
The file(s) are written to a subfolder of the \Work\Out directory:
tgtnnnnnnnn.metron
where nnnnnnnn is the unique 8-digit target number of the target system to which it is being sent.
When the file has been completely written to that folder (which only takes a very short time), the folder is renamed as:
tgtnnnnnnnn.ready
Now, the Control Center can pick the file up and send it to the appropriate target. Once the file has been sent, the tgtnnnnnnnn.ready directory is removed.
It should be noted that third party applications such as virus checkers and back-up software can sometimes hold a lock on the tgtnnnnnnnn directories, which can prevent the necessary folder renames. This will result in profiles not being sent to the required Targets.
This will be apparent as the profile status will not return to “Normal” and the “Profile last sent at” field will not be updated.
If these third party applications cannot be configured to ignore the transient tgtnnnnnnnn folders and do interfere with profile transmissions, then a simple re-send once the folder lock has been removed will ensure that the profile is updated on the Target. There should be no requirement to re-start the Control Center.