Creating a JavaScript Action

JavaScript actions take advantage of the functionality and flexibility of the JavaScript language and can be used to execute actions using Sentinel system methods to do things such as:

The code sample below starts or stops a Collector based on the information in the correlated event.

importPackage(java.lang);
var CollectorName = "TC_5";
var evt = scriptEnv.getCurrentEvent();
var collNm = evt.getPort();
var outfile = new java.io.PrintWriter(new java.io.FileWriter("/opt/jaya/strtcoll.txt", true));
if(collNm && collNm.equals(CollectorName))
{
   var collist = ESM.collectorsForName(collNm);
   if (collist.size() > 0)
   {
      var coll = collist.get(0);
      outfile.println("Stopping " + CollectorName);
      coll.stop();
      Thread.sleep(60000);
      outfile.println("starting " +CollectorName);
      coll.start();
   }
}
else
{
   outfile.println("JSTest collector does not exist");
}
outfile.close();

Debugging JavaScript Actions

You can debug JavaScript files from the Sentinel Control Center with the help of the JavaScript debugger. The JavaScript debugger is a local debugger that executes scripts with respect to the machine on which the Sentinel Control Center is running. The JavaScript debugger instantiates a debug session from the Data Access Service (DAS) machine.

A JavaScript Correlation action can only be debugged after it is associated with a fired correlation rule. Therefore, a prerequisite to debugging is to create a correlation rule that is guaranteed to fire, then associate the JavaScript correlation action with that rule.

The debugger has the following controls:

Table 17-2 Debugger Controls

Icon	Name	Description
	Run	Runs the script until the next breakpoint is encountered.
	Step Into	Steps into a function, one line at a time.
	Pause	Pauses the running script.
	Stop	Stops the script.
	Step Over	Steps over a function to the next line in the script.
	Step Out	Steps out of the function to the next line in the script.