Changes between Version 9 and Version 10 of PlugIns/HTML/htmlmonitor


Ignore:
Timestamp:
12/04/14 10:37:17 (9 years ago)
Author:
pharms
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlugIns/HTML/htmlmonitor

    v9 v10  
    3030To start the monitor, change into the installation directory and type {{{./run.sh}}}. The monitor will run in the background. To check, if the monitor is running, type {{{./isRunning.sh}}}. To stop the monitor, you can type {{{./stop.sh}}}. Per default, the monitor logs the recorded actions into a directory named {{{log}}}. To change this directory, you can start the monitor with a parameter denoting the path to the intended log directory. For example, to log into the directory {{{myLogDir}}}, the monitor must be started with the command {{{./run.sh myLogDir}}}. 
    3131 
    32 When started, the monitor listens on 8090 per default. To check, if the monitor is listening on the port, you can type {{{wget localhost:8090/script/autoquest-htmlmonitor.js}}}. As a result, the monitor should respond with the JavaScript for recording user actions. To change the port, you can provide a different port as the second parameter to the {{{run.sh}}} command. For example, to log into the directory {{{log}}} and to listen on port 8099 the monitor must be started using the command {{{./run.sh log 8099}}}. 
     32When started, the monitor listens on port 8090 per default. To check, if the monitor is listening on the port, you can type {{{wget localhost:8090/script/autoquest-htmlmonitor.js}}}. As a result, the monitor should respond with the JavaScript for recording user actions. To change the port, you can provide a different port as the second parameter to the {{{run.sh}}} command. For example, to log into the directory {{{log}}} and to listen on port 8099 the monitor must be started using the command {{{./run.sh log 8099}}}. 
    3333 
    3434