UDOO-BETaaS

BETaaS is a collaborative project co-funded by the European Commission that aims at overcoming the limitations of current M2M applications platforms. It provides a runtime that simplifies the deployment and execution of content-centric M2M applications with a horizontal abstraction which relies on a local cloud of gateways, enabling the use of Things as a Service over heterogeneous things.

The platform has been released as open source project on GitHub.

This guide walks through the steps required to use the BETaaS platform installed and configured on the UDOOBETaaS image. In particular, it is shown how to start the environment pre-configured with an emulator of sensors generating data and how to install one of the example applications available (a IntrusionDetection application realized as Tomcat web application).

First download the UDOOBETaaS image from here.

1. After installing the image login into the board

2. First, start the zookeeper server using the following command:

zkServer.sh start

3. Start karaf as a daemon with the following command:

/opt/apache-karaf-2.3.8/bin/start

or with the following command in case the interactive console is required:

karaf

4. Wait for the BETaaS environment to initialize, check the log with the following command:

tail /opt/apache-karaf-2.3.8/data/log/karaf_betaas.log

The environment is ready when the following output is displayed (it shows that the platform is ready and the sensor simulator installed by default is generating data):

2015-02-16 16:14:42 | 235 - betaas-adaptation-simulator - 2.1.0.release | Going to read data from the file...:pir1.csv

2015-02-16 16:14:42 | 235 - betaas-adaptation-simulator - 2.1.0.release | counter : 1

2015-02-16 16:14:42 | 235 - betaas-adaptation-simulator - 2.1.0.release | x : 1

5. Restart tomcat to start the example web application, which is pre-installed in the image:

sudo service tomcat6 restart

6. Check that the application installed successfully:

tail /var/lib/tomcat6/webapps/intrusiondetection-2.1-release/IntrusionDetection.log

The expected output is the following:

2015-02-16 16:16:25 INF: Application successfully installed

2015-02-16 16:16:25 INF: Configuration saved

2015-02-16 16:16:25 INF: App ID: 1::1

2015-02-16 16:16:25 INF: Service ID: 1::1_presence_home

2015-02-16 16:16:25 INF: --- end of list ---

2015-02-16 16:16:25 INF: Starting the processing

7. Open a browser and access the IntrusionDetection web application:

More tutorials and how to on the BETaaS platform can be found here!

Next step: integrate real devices (e.g. CoAP devices) into the system: