Table of Contents
Advertisement
10.5.1 Collector Workspace and Collector Directory
Collectors are simple textual scripts that are run by a Collector Manager. The handling of these
scripts is a bit complex:
1 The code for all Collectors is stored in a Plugin Repository on the central Sentinel Server when
they are imported.
Location: ESEC_HOME data\plugin_repository on Sentinel Server.
2 The runtime configuration for the Collector (when it is configured to run on a particular
Collector Manager) is stored separately in the Sentinel database.
3 When a Collector is actually started on the Collector Manager, in real time the Collector plugin
is deployed to the Collector Manager, the runtime configuration is applied, and the code is
started. Any pre-existing instance of the Collector code on that Collector Manager is
overwritten.
Location: ESEC_HOME\data\collector_mgr.cache\collector_instances on each Collector
Manager.
4 In order to edit a Collector, you need to use the ESM Debuggger "Download" button, which
will copy the Collector to the local Collector Workspace on the client machine (the machine
where you are running SCC). Edits are made against that local copy and then uploaded back
into the central Plugin Repository.
Location: ESEC_HOME\data\collector_workspace on the client application machine.
10.5.2 Debugging Proprietary Collectors
The Debugging Collector window allows you to debug Collectors written in Novell's proprietary
language. The left column on the debugger displays the commands for the current script state. The
highlighted command is being executed.
The right column on the debugger displays the script's variables and their current value. The
variable list expands as all the script's variables are used. The variables are color coded to show new
variables in blue, changed variables in red, and variables whose value has not changed since the last
"Step" as black.
212 Sentinel 6.1 User Guide
Advertisement
Table of Contents
