Samples Overview

There are samples for the different functionalities of the platform. For beginners, we recommend to read the lighting sample.

aapi

Examples for the Annotated API, that show a different approach to using the service bus. The examples are based on the lighting sample.
Ontologies: ont.lighting

activityhub/client

Interaction with devices via activityhub ontology: logging events, query sensors, get sensor info.
Similar to Device Client
Ontologies: ont.activityhub

activityhub/simulator

Publish simulated context events for activityhub devices (configurable).
Ontologies: ont.activityhub

device/client

Interaction with devices via device ontology: logging events, query devices, switch device on/off.
Similar to ActivityHubClient
Ontologies: ont.device

integration.tests

Test GUIs to test common functionalities of the different buses and some context managers.
Ontologies: ont.device, ont.device.extra, ont.unit, ont.che, ont.profile, ont.furniture, ont.lighting, ont.measurement, ont.phWorld

karaf

Examples for writing a karaf feature:

• The mw.karaf.feature.lighting-uAAL.osgi is a feature for lighting client and server.
• The mw.karaf.feature.ping-pong.osgi is a feature for smp.mw.broker.client (see below).
  

Ontologies: -

lddi.bluetooth/continuaManager

A client to access Continua Devices via Bluetooth.
unsupported
see LDDI documentation
Ontologies: ont.personalhealthdevice

lddi.bluetooth/weighingScalePublisher

Publishes context event for data coming from a Continua weighting scale via Bluetooth.
unsupported
see LDDI documentation
Ontologies: ont.personalhealthdevice

lighting

The famous lighting sample that is often used to describe the development with universAAL. Manages some simulated light sources that can be queried, turned on/off, and dimmed (client only).
Consists of Client, Server, UI Client, and some scripts for the orchestrator
Ontologies: ont.lighting

ont.tutorial

A simple ontology with just one ontology class, some properties and an enumeration. It can be used as tutorial to write your own ontology manually.
It is recommended to use the ontology modelling tool for this task.
Ontologies: -

simple.ui

Shows how to use the UI framework. It registers an InitialServiceDialog that can be called from the Main Menu of the UI framework. Upon calling this UI Caller, a sample dialog is shown.
Requires the Dialog Manager and a UI Handler to be started in the space, and the manual entry of the UI Caller in the main menu configuration.
Ontologies: -

smp.configurable.module

Shows how to use the configuration framework.
Ontologies: -

smp.ctxt.situation.reasoner.client

GUI for Situation Reasoner.
Ontologies: ont.che, ont.phWorld, ont.situation.reasoner

smp.mw.broker.client

Shows how to write a new middleware broker, like the context bus or service bus, for distributed communication.
The first node just starts the broker and waits for other borkers. The second node detects the first one and sends a 'ping' message to it, which is answered with a 'pong' message.
Ontologies: -

smp.mw.deploymanager.client

Shows how to use the deploy manager of the middleware to deploy an artifact in the Space.
Ontologies: -

smp.ri.exportComponent

Shows a possible approach to export universAAL components as web services.
Ontologies: ont.lighting

smp.sensor.simulator.gui

Simulates some sensors by sending context events.
Ontologies: ont.device, ont.lighting, ont.phWorld, ont.profile

utils

Examples for the Utility API, a library that simplifies the usage of the buses.
Ontologies: ont.device, ont.phWorld, ont.profile