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
    1. Resource Directory
    2. Semantic Query and Entity Directory
    3. AAA / Privacy & Billing
    4. Code Update
    5. PnP / Mobility


The Sensei GUI is a management tool that lets you discover islands, configure main services and browse nodes. The current version of the Management GUI is v.4.


The software requirements for the GUI are the same for any database enabled webapp.

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 (, but any other system can be used.


With access to the sources

In case you have acces to the sources, there are several versions available depending on the development stage. This document refers to Sensei-gui-v3 of the project.

  • Sensei-gui-v3 - stable version, uses Java Server Faces 2 Mojarra (does not use database)
  • SenseiRepos.tgz - MonAlisa Repository plugins for Sensei (used in WP4 Check)
  • SenseiService.tgz - MonAlisa Service Monitoring plugins for Sensei (used in WP4 Check)

Binary version install

You can get the Web archive (gui.war) from here. To install, you only have to copy it into the webapps directory of tomcat.

[root@batch webapps]# pwd
[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

A java web application usually runs on high numbered ports like port :8080. A reverse proxy lets you run your application on port :80. You can do this using mod_jk or by configuring a reverse proxy on an http server like this:

ProxyRequests On

ProxyPass /
ProxyPassReverse /

Some application servers can run on port :80 directly without using a reverse proxy.

Configuring the GUI

All necesary configuration parameters are defined in the file ConfigurationDummyDAO that can be found in the ro.upb.sensei.gui.dao package.

Running the Test Scenarios

These scenarios demo usages of the sensei central services from both the perspective of an administrator and an operator.

Resource Directory

This interface is a browser for all discovered resource directories. It lets you edit entries and provides the means to group resources together. Due to the fact that there are usually multiple resource directories and lots of entries it lets you define filters and select only resources and columns you need.

An example advanced scenario for the Resource Directory is the resource directory peering. The GUI has several RDs defined, for example RD A and RD B and both are peered. To show RD peering you should execute an RLI query and search an entry from RD B by its identifier on the RD A.

The client is redirected to the resource directory that knows how to resolve the query.

Semantic Query and Entity Directory

This is an interface for accessing the SQR and ED. You can use the GUI editor of the Entity Directory or the EOI tab in the administrator view of the GUI. The SQR uses data from the Entity Directory and from Resource Directories to process queries.

More details on how to query for resources using semantic queries please look up the Scenario Demo available for download on the GUI page (available for download here also) or on the Semantic Query Interface page.

AAA / Privacy & Billing

This is an interface over the AAA Interface and Privacy and Billing applications.

Code Update

The Code Update tab configures an Resource Directory Browser to only select Secure Code Update nodes and perform a Synapse++ wireless reprogramming. You can find more on Secure Code Update here. From a user perspective, you can control the Synapse main node by using URLs published in the RD. Starting and detecting code update is done by using GET and POST on these URLs.

The GUI lets you select the only the resources you need and see only the actions available for these links.

PnP / Mobility

The Plug And Play Scenario demonstrates the capability to add nodes to the Sensei Framework without any configuration, while the Mobility demo demonstrates the ability of a node to roam between gateways with all node subscriptions and notfications attached.

Last modified 13 years ago Last modified on Mar 2, 2011, 8:40:03 AM

Attachments (8)

Download all attachments as: .zip