Table of Contents
Advertisement
9.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:
The code for all Collectors is stored in a Plugin Repository on the central Sentinel server when
they are imported.
Location:
<Install Directory>\data\plugin_repository
The runtime configuration for the Collector (when it is configured to run on a particular
Collector Manager) is stored separately in the Sentinel database.
When a Collector is actually started on the Collector Manager, the Collector plug-in is
deployed to the Collector Manager in real time, the runtime configuration is applied, and the
code is started. Any preexisting instance of the Collector code on that Collector Manager is
overwritten.
Location:
<Install Directory>\data\collector_mgr.cache\collector_instances
on each Collector Manager.
In order to edit a Collector, you need to use the ESM Debuggger Download button, which
copies 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:
<Install Directory>\data\collector_workspace
machine.
9.5.2 Debugging Proprietary Collectors
The Debugging Collector window allows you to debug Collectors written in the Novell 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.
on the Sentinel server.
on the client application
Event Source Management 203
Advertisement
Table of Contents
