Management GUI

This document includes instructions how to install and to run the management GUI. The management GUI is a client for all Sensei services that lets you run demo scenarios and show advanced capabilities and component interaction.

Table of Contents

1. Management GUI
2. Introduction
3. Installation
   1. Software Requirements
   2. Installation
   3. Configuring the GUI
4. Running the Test Scenarios

Introduction

The current version of the Management GUI is v.4.

Installation

The software requirements for the GUI are the same for any database enabled webapp. In case you get the binary version, you only need the *.war file, in case you want to compile the sources, there are several version on the SVN all eclipse projects and ant enabled.

Software Requirements

The current version of the gui requires a working

• Apache Tomcat configuration and
• Java v.6.0. The development version also uses a database for persistence information that will initialize itself at startup. The webapplication can be run either on Linux or Windows. Parts of the GUI use data from external applications like the monitoring information and service health checks.

The current monitoring system implemented is the MonAlisa service (​http://monalisa.cern.ch), but any other system can be used.

Installation

With access to the sources

In case you have acces to the sources, there are several versions available depending on the development stage. The project trunk is available at /svn/Sensei-WP5/management/

• SenseiStaticWeb/ - first version, uses static web pages and Yahoo UI (YUI v2)
• Sensei-gui-v2/ - experimental version
• Sensei-gui-v3/ - stable version, uses Java Server Faces 2 Mojarra (does not use database)
• Sensei-gui-v4/ - current development version, uses Java Server Faces 2 with Prime Faces API (YUI) and Mysql Database
• SenseiRepos/ - MonAlisa Repository plugins for Sensei (used in WP4 Check)
• SenseiService/ - MonAlisa Service Monitoring plugins for Sensei (used in WP4 Check)

Binary version install

You get a Web archive (*.war), you only have to copy it into the webapps directory of tomcat.

[root@batch webapps]# pwd
/opt/apache-tomcat-6.0.24/webapps
[root@batch webapps]# ls -l gui.war
-rw-r--r-- 1 root root 15187840 Mar 30  2010 gui.war

(Optional) Configure a reverse proxy for your webapp

Running java web applications usually run on port :8080. Because you usually also do not run the application server as root, there are few cases in witch the application server knows how to run on port :80 and still use an uprivileged account. The fix for this is using mod_jk or configuring a reverse proxy on the http server like this:

ProxyRequests On

ProxyPass / http://monalisa.grid.pub.ro:8080/
ProxyPassReverse / http://monalisa.grid.pub.ro:8080/

Configuring the GUI

Configuring a reverse proxy for Apache

Configuring the services and filters

Other configuration

Running the Test Scenarios