Changes between Version 3 and Version 4 of PlugIns/GenericEvents/generic-event-monitor

Timestamp:

10/04/17 13:00:02 (7 years ago)

Author:

pharms

Comment:

--

PlugIns/GenericEvents/generic-event-monitor

@@ -55 +55 @@
 
 Afterwards, the tar-file needs to be extracted to a preferred location. The resulting folder structure will look as follows:
- * autoquest-htmlmonitor-version
-  * data
-   * robots
-    * robotsfilter.txt
+ * autoquest-generic-event-monitor-version
   * lib
     * <some libraries (jar-files)>
-  * autoquest-htmlmonitor-version.jar
+  * autoquest-generic-event-monitor-version.jar
   * run.sh
   * stop.sh
   * isRunning.sh
 
-After the first start of the monitor, a further folder called log will be added. In this folder, the logfiles will be stored. The log directory can be changed using start parameters for the monitor (see next Section).
+After the first start of the monitor, a further folder called log will be added. In this folder, the logfiles will be stored. The log directory can be changed using start parameters for the monitor (see next Section). The sub directories of the log directory will be created depending on the application and client ids provided in the received JSON message (see above).
 
 
@@ -76 +73 @@
 
 
-== Monitoring Web Applications ==
+== Monitoring Applications ==
 
-To monitor web applications, the JavaScript provided by the monitor needs to be 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 include 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 changed 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 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 leaves 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. To check if the monitor correctly records user actions, you can check if a specific log file is created in the log directory. Furthermore, you can check the {{{console.log}}} for respective messages, e.g. the following one: