Changes between Version 7 and Version 8 of PlugIns/HTML/htmlmonitor

Timestamp:

12/04/14 10:36:10 (9 years ago)

Author:

pharms

Comment:

--

PlugIns/HTML/htmlmonitor

@@ -31 +31 @@
 
 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}}}.
+
+
+== Monitoring Web Applications ==
+
+To monitor web applications, the JavaScript provided by the monitor needs to integrated into each page of the web application. For example, if a monitor is running on host {{{host}}} and port {{{1234}}}, then each page of the web application must integrate the following JavaScript
+{{{
+  <script type="text/javascript" src="http://host:1234/script/autoquest-htmlmonitor.js"></script>
+}}}
+
+In this simple setup, recorded user data will be sent unencrypted from the users browser to the server. Hence, the setup should be changes to support encryption. For this, several options exist. A good solution is to have a further Apache webserver which listens on an encrypted port and forwards any request machine internally to the unencrypted port of the monitor. In this case, the integration of the script into the pages of the monitored website must be adapted to match the changed setup.
+
+After the JavaScript is integrated into the web pages, the browser at of the user will execute it on each loading of the pages. The script will ensure to register for any user action. If 10 actions were recorded, if a timeout occurs, or if the user leaved the page, all recorded user actions will be sent to the monitor for storing them into the log files.
+
+Log files are separated in the log directory by the URL of the monitored web application as well as by a unique id of the client. Please note, that a client here is a specific installation of a specific browser on a specific machine. If the installation changes, the client id may change. If several users use the same installed browser, they are considered as one user.