Author: Eoin Joy

Lots of functionality in the EMS is achieved with the use of runtime configurable groovy scripts, which are stored in the domain of RemoteDiscoveryScript.
These scripts are run as groovy shells and are passed in various bindings determined by where in concrete code they are executed.

There are many different types of RemoteDiscoveryScript, roughly divided into the following categories:

• Alarm Auditor Scripts
• Alarm Sync Scripts
• Component Discovery Scripts
• Config Sync Scripts
• Discovered Trap Scripts
• HTTP Session Manager Scripts
• Parameter Table Scripts
• Performance Discovery Scripts
• Performance and Configuration Sync Creation
• Remote Discovery Configuration Scripts
• Technology Discovery Scripts
• Topology Discovery Scripts

The RemoteDiscoveryScript domain stores the text of the script, a secondary script used to determine test data, and a tertiary unused script, as well as what the return type of the script should be.
The text of the script is encrypted both in the database and when stored to the filesystem in the directory determined in Configuration.remoteDiscoveryScriptDir.
This file storage is currently solely used as a backup, and cannot be read from by the application to update its scripts.

All RemoteDiscoveryScripts can be tested in the UI on the edit page of the RemoteDiscoveryScriptController, this will use the variable script to determine what data to send in as bindings to the shell.