Workflow Developer Tools

By
Joerg Lew
– March 15, 2011Posted in: Tools
For convenient viewing of the log files, you can use mtail:
http://ophilipp.free.fr/op_tail.htm
Like the linux tail-command it refreshes the open files and is so a very useful tool to watch the logs while running your workflows.

mtail

If you want an alternative for the built-in script editor
ftp://ftp.mozilla.org/pub/mozilla.org/js/rhino1_6R3.zip
mtail
For convenient viewing of the log files, you can use mtail:
http://ophilipp.free.fr/op_tail.htm
Like the linux tail-command it refreshes the open files and is so a very useful tool to watch the logs while running your workflows.

mtail

Rhino shell
If you want an alternative for the built-in script editor you can use the Rhino-debugger.
Rhino shell
Download the Rhino-package from:
ftp://ftp.mozilla.org/pub/mozilla.org/js/rhino1_6R3.zip
(The links point not to the current version, but to the older 1.6R3-version of Rhino which is used in Orchestrator.)
Unzip, open a command prompt, change to the base-directory and start the debugger with
java -cp js.jar org.mozilla.javascript.tools.debugger.Main
For more information, see the docs at
http://www.mozilla.org/rhino/debugger.html
Unfortunately, there is no integration of this debugger to vCO, so it’s difficult to use it for scripts which uses other Orchestrator objects (which is the fact for most of your scripts, I guess). And you have to copy&paste your code to the vCO-Client. Not very convenient, but maybe helpful to debug some plain JavaScript-elements.