uSpace Server
This artifact provides an interface to instances of uSpace Profiles stored inside the Context Store. There are methods to query or update information about an uSpace stored in its uSpace Profile.
This module covers the implementation of the following features:
- Get/create an uSpace Profile
- Get the complete profile
- Create an empty uSpace profile
- Manage devices contained inside the uSpace
- Get a list of devices associated with a given uSpace in its uSpace profile
- Attach a given device to the uSpace by adding it to the uSpace profile
- Remove a device from an uSpace by removing it from the uSpace profile
- Manage installed AAL apps / AAL services in a given space
- Get a list of AAL apps / AAL services installed in a given space
- Add an AAL app / AAL service to the uSpace profile of a given uSpace
- Remove an AAL app / AAL service from the uSpace profile of a given uSpace
The following Maven artifact from the Context repository is related to the uSpace Server module.
- org.universAAL.context/ctxt.space.server: The core of the uSpace Server.
To get the Space Server working, just like the Profiling Server, currently you need to include the CHE first, and make sure you included the Profiling ontology (and their dependencies). The Profiling server and the CHE use data serialization so you will have to include it in the middleware. That would be:
...Middleware bundles (with mw.data.serialization)... (Ont) org.universAAL.ontology/ont.profile/x.y.z (Ont) org.universAAL.ontology/ont.che/x.y.z (CHE) org.openrdf.sesame/sesame-runtime-osgi/2.6.0 (CHE) org.universAAL.context/ctxt.che/x.y.z org.universAAL.context/ctxt.prof.server/x.y.z
The version of uAAL bundles is not shown, as this changes with every release. Another way to include the Space Server is to use its composite bundle (scan-composite:mvn:org.universAAL.context/ctxt.space.server/x.y.0/composite) or the Profiling Server Karaf feature (uAAL-ctxt.Space.Server) from the Context features.
The Space server does not require any configuration at the time being. However, for all services to be available and properly working, the preload of ontologies must be activated in the Context History Entrepot, with the parameter STORE.PRELOAD=true.
The uSpace Server provides practically the same services of the Profiling Server, but oriented to uSpace and AAL Service. Therefore its methods are provided and called the same way. I provides methods for getting, changing, adding and removing uSpace profiles and profilable entities, that is: uSpace, uSpaceProfile, AALService and AALServiceProfile, and it also provides generic GET methods for getting the list of all the uSpace and AALService. All these methods are called the same way as their Profiling Server equivalents (changing the URIs and paths of the ontologies where appropriate).
There are other additional helper services provided by the uSpace Server which have no equivalent in Profiling Server. These are:
- GET/ADD/CHANGE/REMOVE of Device and OntologyEntry.
- GET/ADD AALService, Device and OntologyEntry on a specified uSpace.
- GET the HRSubProfile, HWSubProfile and AALAppSubProfile of a specified AALService.
The Space server is not connected to the Context bus.
The Space server does not provide a UI by itself.