The Sensei Virtual Machine

The Sensei Virtual Machine is a host that provides all basic functionalities of the Sensei Framework. The VM comes in two flavors: Xen VM and VMWare VM.

Table of Contents

  1. The Sensei Virtual Machine
    1. Where to get it
    2. Environment Setup
    3. Networking Setup
  2. Third party components
    1. Sun Java 6.0 JDK and Apache Ant
    2. Apache Tomcat & Mysql
    3. IPv6 Connectivity
    4. SSL Certificates
  3. Compiling Sensei Services using a CLI (Command Line Interface)
  4. Running Sensei Services in the CLI

Where to get it

  • You can download the Sensei Virtual Machine from (very large, provided as chunked RARs)
  • This Virtual Machine is in VMWare format. You can use VM Player to run this virtual machine.
  • The hostname configured for this VM is, all services configured on this machine assume this hostname. Because SSL certificates depend on the servers hostname, changing the hostname of the VM will impact all SSL applications like AAA and Billing. You must generate and install new a host certificate because all SSL use trusted links. Use this link to find out how.
  • In case you do not wish to change the hostname, please configure its new ip in /etc/hosts on both the VM and you client. If you are using Windows, this file is located in C:\Windows\System32\drivers\etc\hosts.


# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
  • after you boot up, all services should run automatically.

Environment Setup

This is the list of the main components and their configuration

Resource Directory

Install Directory: /opt/sensei/RDv2
Requires: mysql daemon started, database sensei_rd2
Database configuration file: /opt/sensei/RDv2/build/database/
HowTo Run:

  • you can use the service startup script like this:
    [root@sensei-dev1 RDv2]# pwd
    [root@sensei-dev1 RDv2]# ./ start
    [root@sensei-dev1 RDv2]#
  • or you can startup manually like
    nohup java -Xms32m -Xmx384m -classpath .:build:lib/commons-cli-1.2.jar:lib/ restlet_server.RESTLET_Server -host &
  • Check the service:
    [root@sensei-dev1 RDv2]# netstat -anp | grep :8184
    tcp        0      0 :::8184                     :::*                        LISTEN      29572/java

Advanced Resource Description Repository

Install Directory: /opt/sensei/RESTArdRepov2
Requires: sedna database arddb started
Database configuration file: -
HowTo Run:

[root@sensei-dev1 RESTArdRepov2]# cd /opt/sedna/bin/
[root@sensei-dev1 bin]# ./se_gov
GOVERNOR has been started in the background mode
[root@sensei-dev1 bin]# ./se_sm arddb
Starting database recovery or hot-backup restoration...
Database recovery in progress...
SM has been started in the background mode
[root@sensei-dev1 bin]# cd /opt/sensei/RESTArdRepov2
[root@sensei-dev1 RESTArdRepov2]# nohup ant runARDRepoServer &
  • Check the service:
    [root@sensei-dev1 RESTArdRepov2]# netstat -anp | grep :8185
    tcp        0      0 :::8185                     :::*                        LISTEN      29971/java

Entity Directory

Install Directory: /opt/sensei/RESTEoiRepov3
Requires: sedna database eoidb started
Configuration file:
HowTo Run:

[root@sensei-dev1 RESTArdRepov2]# cd /opt/sedna/bin/
[root@sensei-dev1 bin]# ./se_gov
GOVERNOR has been started in the background mode
[root@sensei-dev1 bin]# ./se_sm eoidb
Starting database recovery or hot-backup restoration...
Database recovery in progress...
SM has been started in the background mode
[root@sensei-dev1 bin]# cd /opt/sensei/RESTEoiRepov3
[root@sensei-dev1 RESTEoiRepov3]# nohup java -jar RestEoiv3.jar  
  • Check the service:
    [root@sensei-dev1 RESTEoiRepov3]# netstat -anp | grep :8182
    tcp        0      0 :::8182                     :::*                        LISTEN      30133/java

SQR Directory

Install Directory: /opt/sensei/SQRv2
Requires: -
Configuration file:
HowTo Run:

[root@sensei-dev1 SQRv2]# nohup ant runSQRv2Server &
  • Check the service:
    [root@sensei-dev1 SQRv2]# netstat -anp | grep :8186
    tcp        0      0 :::8186                     :::*                        LISTEN      30404/java

Others (AAA & Billing+Privacy)

They are web-applications. You must only start the application server. All databases are in-memory.

Install Directory: /opt/apache-tomcat-6.0.20/webapps
HowTo Run:

[root@sensei-dev1 webapps]# cd /opt/apache-tomcat-6.0.20/bin/
[root@sensei-dev1 bin]# ./
Using CATALINA_BASE:   /opt/apache-tomcat-6.0.20
Using CATALINA_HOME:   /opt/apache-tomcat-6.0.20
Using CATALINA_TMPDIR: /opt/apache-tomcat-6.0.20/temp
Using JRE_HOME:       /usr
[root@sensei-dev1 bin]#
  • Check the service:
    [root@sensei-dev1 bin]# netstat -anp | grep :8080
    tcp        0      0 :::8080                     :::*                        LISTEN      2238/java
    [root@sensei-dev1 bin]# netstat -anp | grep :8443
    tcp        0      0 :::8443                     :::*                        LISTEN      2238/java
    [root@sensei-dev1 bin]#

Networking Setup

This information is needed usually for debugging and tracking purposes.

  • Dns nameserver:
  • IPv4 gateway: (for the range)
    , (for the range)
  • IPv6 gateway: (2001:5c0:1502:5300::1/64)
[root@star bin]# ping6
PING 56 data bytes
64 bytes from 2a00:1450:8007::68: icmp_seq=0 ttl=55 time=59.5 ms
64 bytes from 2a00:1450:8007::68: icmp_seq=2 ttl=55 time=59.9 ms
64 bytes from 2a00:1450:8007::68: icmp_seq=3 ttl=55 time=58.5 ms

Third party components

This section is "good to know" for debugging services and configurations on the Sensei VM.

The usual requirements for hosting our services are:

  • a linux machine (we use RHEL-flavored operating systems, but any system should do)
  • Sun Java JDK 6.0
  • Apache Tomcat v.6.0.20
  • Mysql 5
  • IPv6
  • SSL Certificates for AAA and Privacy & Billing

IPv6 is needed for communicating with the nodes. For this, you can use a native IPv6 network or IPv6-over-IPv4 tunnels. The current Sensei network uses !GoGo6 ( for Ipv6 tunneling.

Sun Java 6.0 JDK and Apache Ant

You can download the sdk from (direct link: Due to the fact that we'll be using java from the command line you should also set the necesarry environment variables JAVA_HOME and JDK_HOME. It is advisable to use the bin version of the archive and install it in /opt/java for example.

Download java to /opt/java, make the file executable (chmod +x filename) and run it. In our example, java will be installed in /opt/java/jdk1.6.0_20. Other locations possible to find the java instalation would be /usr/java, /usr/lib/jvm (depending of the OS flavor).

Put Java in the Environment Path by adding the following file to /etc/profile.d: (filename ex:

export JAVA_HOME=/opt/java/jdk1.6.0_20
export JDK_HOME=/opt/java/jdk1.6.0_20
export ANT_HOME=/opt/apache-ant-1.8.1
export PATH=/opt/java/jdk1.6.0_20/bin:/opt/apache-ant-1.8.1/bin:$PATH

Several components might use compiling. If you do not have access to a GUI, then you can use Apache Ant ( Just download it and install it in /opt/apache-ant-1.8.1.

Apache Tomcat & Mysql

You can use any application server you like. The one we used was Apache Tomcat 6.0.20. Just download it and unpack it in /opt/apache-tomcat-6.0.20. For ease of development, we recommend using the tar.bz2 version for apache tomcat and the operating system provided mysql.

To install mysql on a RHEL-flavored machine and configure it to run at startup:

   yum -y install mysql mysql-server
   chkconfig mysqld on

IPv6 Connectivity

You may get IPv6 addresses from your ISP or you can tunnel IPv6 over an IPv4 network.

If you want to use the setup for local development (nodes included) and do not need internet access through Ipv6, you can use radvd, a linux IPv6 Router Daemon advertiser. For the address space, just go to and get your own random private ipv6 address space. Theese networks will not get routed in the internet and you can use them locally.

For Gogo6 you must go to and create yourself an account. (there is a the posbility of anonymous use also). You must download the FreeNet? 6 client and run it. The client is named gw6c and we install it in /opt/gw6c. The is a sample configuration file you must edit, gw6c.conf. The most important settings are:

#   host_type=<host|router>

To run it, run gw6c and it will daemonize by itself. To test your ipv6 setup just


If you need a static address, just configure it from /etc/sysconfig/network


and /etc/sysconfig/network-scripts/ifcfg-eth0

# Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express

SSL Certificates

This is the most important step for security services. Not only you got to have an ssl certificate, it must be trusted by all partners. You can get free SSL certificates at StartSSL for free, but for development you might consider to generate on youself. We will not cover this section here, you can use for example the perl script in the openssl-perl package to create yourself a Cerificate Authority that will sign you cert, or you can use openssl directly.

The important step is to tell tomcat an java about the certificates.

To configure Tomcat you must follow these steps: The tricky bit is getting Java JRE to trust this certificate. The easyest way is to use this Java program.

[to add link and howto]

Compiling Sensei Services using a CLI (Command Line Interface)

In case you need to compile the services you can use ant. Each project has a *.properties file for customizations.

To build a service:

   ant build

To run a service. Just check the build target and run it:

[root@sensei-dev1 SQRv2]# ant -p
Buildfile: build.xml

        Sensei SQRv2

Main targets:

 TestSQRLookup   Run ARD Server
 all             Clean build and dist, then compile
 build           Build everything
 clean           Delete old build and dist directories
 dist            Dependency jar
 runSQRv2Server  Run ARD Server
Default target: build
[root@sensei-dev1 SQRv2]# ant runSQRv2Server

In case you need as a daemon (close the terminal session and still have the service running, just use nohup.

[root@sensei-dev1 SQRv2]# nohup ant runSQRv2Server &

This will create a nohup.out file with all the output.

Running Sensei Services in the CLI

For running a service, you can use ant and nohup (in case you have source code access), or java directly

nohup java -jar RestEoiv3.jar &

To check the service is running, look at the output file and/or check that the serivice is running on the specified port.

[root@sensei-dev1 RESTEoiRepov3]# netstat -anp | grep java | grep LISTEN
tcp        0      0 :::9000                     :::*                        LISTEN      2669/java
tcp        0      0 :::42896                    :::*                        LISTEN      2669/java

We have two services running on ports 9000 and 42896.

Last modified 12 years ago Last modified on Nov 4, 2010, 4:05:11 PM