servIoTicy
Home / Documentation

Virtual appliance

Original local development appliance and release notes.

These examples document the original platform. Use your own deployment; this website does not provide the former hosted API or account service.

The original VM download is no longer available here. The Vagrant configuration and source code remain available on GitHub. The release notes below describe the original appliance.

VM 0.6.1 Download link: http://www.servioticy.com/virtual-appliance#source

Versioning info: issues.servioticy.com

VM format: Virtual Box VDI

Guest properties:

  • OS: Ubuntu 12.04.4 LTS
  • Network configuration:  2 DHCP interfaces (eth0 NAT for external routing, eth1 internal bridge for communication with the host)
  • User: servioticy
  • Password: servioticy
  • Root access: use “sudo su” and provide the pasword of the servioticy user
  • Minimum Recommended amount of RAM for the VM: 3GB

Changes in v0.6.1 (released 17/July/2014):

  • Fixed several problems related to data retrieving, mostly related to the use of a conversion of the VM on KVM
  • Added type enforcement checks on the API to avoid conflicts with the ES index
  • Fixed bug on internal retrieving of group subscriptions
  • Added check for forcing SOs to have streams, and have streams getting channels

Changes in v0.6 (released 04/July/2014):

  • More changes on the indexing of contents in ElasticSearch to avoid data clashes and to find subscriptions without problem

Changes in v0.5 (released 02/July/2014):

  • Corrections on the indexing of contents in ElasticSearch – some queries were limited in the number of items being visible
  • Moved the connection between the API and ElasticSearch to unicast mode to avoid multicast filtering in some environments that prevented normal behaviour
  • Minor fixes and bug corrections
  • Updated MQTT/STOMP bridge to allow for messageId field to match requests and responses

Changes in v0.4 (released 09/May/2014):

  • Added more demos (multiple maps)
  • Added topology generator for functional and performance testing

Changes in v0.3 (released 22/April/2014):

  • Added support for actuations (see actuation section in the API documentation) through MQTT
    • The action requests will be published under the topic “SO id/actions” in real time
    • Actions can be updated and their status can be checked
  • Added demo files for simulating actuations (located in demo/actuation)

Changes in v0.2 (released 15/April/2014):

  • Added MQTT subscriptions (see example in this page)
    • The updates will be published under the topic “API_TOKEN/SO id/streams/streamID/updates” in real time
  • Added demo files for simulating MQTT subscriptions (located in demo/mqtt_subscription) – uses the same SO than the map demo

Features in v0.1 (released 07/April/2014):

  • Pre-created API user:
    • username: servioticy
    • API token:
      M2JhMmRkMDEtZTAwZi00ODM5LThmYTktOGU4NjNjYmJmMjc5N2UzNzYwNWItNTc2ZS00MGVlLTgyNTMtNTgzMmJhZjA0ZmIy
  • Ports:
    • API: 8080
    • MQTT/STOMP over TCP: 1883  (user: compose, password: shines)
    • STOMP over WS: 61623  (user: compose, password: shines)
    • Coucbhase Admin Console: 8091 (user: admin / password: password)
    • ElasticSearch console: 9200 (<vm>:9200/_plugin/head/)
    • Demo application: http://<vm>:8090
  • servIoTicy platform:
    • Couchbase 2.2 Enterprise
    • STORM 0.9.1-incubating (running in jar mode, not distributed)
    • Kestrel 2.9.2-2.4.1
    • Jetty 8.1.11.v20130520
    • ElasticSearch 1.0.1
    • Java(TM) SE Runtime Environment (build 1.7.0_51-b13) – Oracle
    • User management DB: Flask and SQLite
    • Apache Apollo 1.7
    • NodeJS v0.6.12
  • Start/Stop servioticy:
    • startAll.sh – starts all services
    • stopAll.sh – stops all services
  • User management:  (files located in folder `scripts`)
    • Create a new user: create_user.sh <username>
    • Check api token for a user: get_api_token.sh <username>
    • List all existing users and api tokens: get_all_tokens.sh
    • Clear all users from de DB: clear_usersDB.sh
  • Pre-loaded (fake) data:
    • Temperature and location sensor – ID: 1396461657731411aa73c28444ecf9a8c803e62312fd1
    • Fake positions in a map
    • Provided scripts to generate new values, get all existing values, get latest value and clear all SO data (located at /home/servioticy/demo/map/utils)
  • Demos:
    • Demo map with heatmap features (requires Internet access on the client browser)
    • Script to start the demo: /home/servioticy/demo/map/start.sh
    • Script to stop the demo: /home/servioticy/demo/map/stop.sh
    • HTTP server: <VM ip>:8090
← All documentationExplore the source code →