Just running scripts not related to HQ but run them by HQ agent.
Here is the example of what I want to use it for.
I configured a monitor for a specific process ( using Process Service). It monitors process, log file and properties file . Very nice and useful. The only problem is that log file created by process has date and time stamp in the name so every time it is restarted the name of the log file is changed. I don't know how to make Log tracking to use the right file. So I created hardlink (on Windows 2003 it's " fsutil hardlink create " command, btw) and monitor that instead. I want to have a script that would delete and create new hardlink every time the process is restarted so I can create custom control action in HQ . I can write as DOS batch or VB Script but I like groovy more.
Basically, I want Control Actions to be groovy scripts. Not sure how much of HQ functionality is there involved
Now you've got me thinking into custom plugins idea, I think that custom Groovy Script plugin would be nice or better yet have a dedicated thread in the agent that would be devoted to scripting. If there are no scripts then it's idle, but if there is a script to run it would be fast - JVM is already loaded, groovy.jar is loaded , just feed it with bytecode compiled script.