Some Detect components and utilities can run one of several different batch files when they complete a run. There are different batch files for each component or utility and for each process result: success, success with errors (for some processes), and failed.
Default, empty files are shipped with the product; you must edit these files as needed to perform the appropriate actions for your system when a Detect process finishes. If the batch file for a process result (as specified in the Configuration Utility) is empty, no further processing takes place.
When you run from the command line, the /ftp switch determines whether the the process invokes the batch file when it finishes. To have the process run the batch file, use
/ftp:On in the command you use to run the process. When you run the
Detect engine from the Engine Manager, check the
Batch Notification checkbox to run a batch file when the process completes.
The batch files that Detect processes invoke at the end of runs must be located on the machine where the Enterprise Management Controller (EMC)is installed.
In addition to attempting to run files associated with success, success with errors, and failure, the Detect engine can run an alert file N seconds before the end of the run. This applies only to always-on runs of the
Detect engine,
This feature is configurable. This file is executed if you set the if the Alert Before Processing Completion option in the Configuration Utility's
Advanced Configuration > System Options section to a value greater than
0. The value you set specifies the number of seconds before processing completes when
Detect attempts to run the file.
The following is a list of processes and process states that cause Detect to attempt to execute a batch file specific to a process outcome.
