%----%>
<%--<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>--%>
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/functions" prefix="fn" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>
<%@ taglib uri="http://displaytag.sf.net" prefix="dt" %>
JABAWS comes with a web application for visualizing usage statistics.
The screenshot below shows the main page of this application.
The individual month is linked to detailed usage statistics (described later).
Please note, that the links to the detailed monthly statistics are only
available for authenticated users in the role
If you are using JABAWS VA (Virtual Appliance) then the username is
If you have deployed a JABAWS WAR file, then please see the configuring privileged access for Tomcat web application server section for further details.
The table contains the number of jobs processed by JABAWS per month, for the whole period when the statistics was collected.
For each month the table contains the following information.
The summary for each column is displayed in the last row of the table.
Authentication lets you see the detailed usage statistics.
If you are using JABAWS VA (Virtual Appliance) then the
username is
Detailed execution statistics for each month is available for authenticated users only.
Each table contains the number of jobs processed by JABAWS during the period of time specified in the title:
Please note that if you deployed JABAWS WAR, in order to be able to navigate to the job directory from this view, the application server may need to be configured. Please see Configuring JABAWS execution statistics section for further details.
Columns:
STARTED and FINISHED files contain Unix timestamp - when the job was started and completed respectively. STARTED is replaced by SUBMITTED if the job has been submitted to the cluster, as opposed to executed locally, on the server.
COLLECTED file is empty and indicates that the job results were collected by the user. Due to asynchronous nature of the job it is possible that the job was started and finished, but the results has never been requested.
RunnerConfig.xml file contains a complete description of the job and JABAWS can restart the job based on this description.
procError.txt and procOutput.txt files contains the content of the standard out and standard error streams of the process.
result.txt file contains the results.
input.txt file contains input into the process.
There are maybe other files depending on the nature of the job, but the one described above will be present in most cases. In this example, stat.log file stories the execution statistics generated by (clustal executable in this example) process.
If you have deployed JABAWS WAR file or made changes to JABAWS configuration you may need to make a few changes to the Tomcat configuration to be able to see the content of the job directory. Please see Configuring JABAWS execution statistics section for further details.
JABAWS execution statistics is a multi-component system. First is a crawler whose job is to collect and preprocess the statistics from the job temporary directories and record the collected statistics into the database. The second part of the system is a web application whose job is to visualise the statistics from the database.
It is possible to enable/disable the statistics collector by changing the following properties in the conf/Cluster.engine.properties and conf/Local.engine.properties files.
# Enable/disable cluster statistics collector true = enable, false = disable
cluster.stat.collector.enable=false
# Maximum amount of time the job is considered be running in hours. Optional defaults to 7 days (168h)
cluster.stat.maxruntime=24
# Enable/disable cluster statistics collector true = enable, false = disable
local.stat.collector.enable=true
# Maximum amount of time the job is considered to be running in hours. Optional defaults to 24 hours
local.stat.maxruntime=6
If the statistics collector is enabled then the crawler starts automatically soon after (10 minutes for local engine, and 60 minutes for cluster engine) the JABAWS web application and will be collecting the execution statistics every 24 hours after the start.
The details of the job are only available if the job temporary directory
is located within a JABAWS web application. If not, the system
administrator can create a symbolic link pointing to the temporary
job directories outside of a web application and configure the
application server to allow navigation to the links. For the Tomcat
application server the context configuration file should be created and
copied to the <TOMCAT_ROOT>/conf/Catalina/localhost directory. The
name of the file should be the same as the web application context name,
for example "
<?xml version="1.0" encoding="UTF-8"?>
<Context antiResourceLocking="false" privileged="true" allowLinking="true"/>
The key option here is this:
Access to configuration files, detailed job execution statistics and job
directories are allowed only for authenticated users in role
"
If you use Tomcat, then the simplest way to set up privileged
access is to use a plain text configuration file
<tomcat-users>
<role rolename="admin"/>
<user username="peter" password="your password here " roles="admin"/>
</tomcat-users>
For more information on users and roles please consult Apache-Tomcat help pages.