212 Sentinel 6.1 User Guidenovdocx (en) 7 January 201010.5.1 Collector Workspace and Collector DirectoryCollectors are simple textual scripts that are run by a Collector Manager. The handling of thesescripts is a bit complex:1 The code for all Collectors is stored in a Plugin Repository on the central Sentinel Server whenthey 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 particularCollector Manager) is stored separately in the Sentinel database.3 When a Collector is actually started on the Collector Manager, in real time the Collector pluginis deployed to the Collector Manager, the runtime configuration is applied, and the code isstarted. Any pre-existing instance of the Collector code on that Collector Manager isoverwritten.Location: ESEC_HOME\data\collector_mgr.cache\collector_instances on each CollectorManager.4 In order to edit a Collector, you need to use the ESM Debuggger “Download” button, whichwill copy the Collector to the local Collector Workspace on the client machine (the machinewhere you are running SCC). Edits are made against that local copy and then uploaded backinto the central Plugin Repository.Location: ESEC_HOME\data\collector_workspace on the client application machine.10.5.2 Debugging Proprietary CollectorsThe Debugging Collector window allows you to debug Collectors written in Novell’s proprietarylanguage. The left column on the debugger displays the commands for the current script state. Thehighlighted command is being executed.The right column on the debugger displays the script’s variables and their current value. Thevariable list expands as all the script’s variables are used. The variables are color coded to show newvariables in blue, changed variables in red, and variables whose value has not changed since the last“Step” as black.
