Scripts allow you to embed scripts of any kind (command line scripts, visual basic scripts, Perl scripts, etc.) inside the EventSentry configuration, so that the scripts themselves do not have to be maintained on the target machines, making it easier to maintain environments that utilize scripts.
Scripts can be utilized from these components:
Scripts can be written in any language as long as the script interpreter (e.g. Perl) is properly installed on the machine where the script is going to be executed. For example, ActivePerl needs to be installed on a host where Perl scripts are configured to run.
Scripts are stored in the registry and can be configured in the sub nodes under the main Scripts node where the general options are configured.
User-maintained (embedded) scripts can be managed here, and clicking this node will display all existing user scripts.
Downloaded scripts maintained by NETIKUS.NET are shown here, and clicking this node will display all managed scripts. While managed scripts cannot be edited or deleted, they can be disabled and the execution frequency can be adjusted as well. Tags associated with scripts cannot be removed, but additional tags can be added.
Scripts can be tagged (and all managed scripts have at least one tag), which can be utilized in Validation Scripts packages.
To use a script, prefix the file name with the @ symbol in an application schedule or process action. For example, if your script is named LaunchUpload.cmd, then specify @LaunchUpload.cmd. Fields that support embedded scripts feature a pull-down menu that lets you select from any of the configured scripts.