test

Sun Java System Portal Server 7 Developer's Guide

Monitoring cmdHook Execution

At the default logging level, a log message is written in robot.log when the cmdHook is run.

For example, if the onCompletion parameter is set to idle, the robot.log output would look like the following:


[12:45:57]  Run cmd: /opt/SUNWps/bin/cmdHook1
[12:45:58]  Complete cmd: /opt/SUNWps/cmdHook1
[12:45:58]  Robot is idle....
. . . if the onCompletion parameter is set to shutdown, the robot.log output would look like:
[12:45:57]  Run cmd: /opt/SUNWps/bin/cmdHook1
[12:45:58]  Complete cmd: /opt/SUNWps/bin/cmdHook1
[12:46:33]  Workload complete.
. . . if the onCompletion parameter is set to loop, the robot.log output would look like:
[12:52:04]  Run cmd: /opt/SUNWps/bin/cmdHook1
[12:52:05] Complete cmd: /opt/SUNWps/bin/cmdHook1
[12:52:05] Restart Robot.
. . . if the onCompletion parameter is set to loop, there will be an additional entry in filter.log like this:
[12:54:41] Filter log started - loop 15