COSMOS – VE registry

Cosmos VE registry is a semantic tool which supports the annotation as well as the retrieval of Cosmos related entities such as the VEs (Virtual Entities), VE serivces, IoT Services, etc. The tool is backed by the Cosmos Semantic Model developed as part of the project and it provides an web based UI as well as a REST API for all annotation and retrieval operations. A instance of the tool has been deployed at http://www.bamct.siemens.ro:9000/VERegistry/ and artifacts and instructions for custom deployments are also provided.    
  • Latest version ID: v.1.2
  • Tags: , ,
  • Latest update: October 7, 2016
  • Developed by: SIEMENS Corporate Technology Romania
  • Contact name: Bogdan Târnaucă
  • Contact email: [email protected]

Operating Guide

The entry point of the COSMOS VE Registry is the operations selector. The user can choose one of the supported operations.

veregistry1

Typically, the annotation starts with the IoT and VE Services since these are those exposing the VE functionality.

veregistry2

After the identification information has been filled, the user can choose how the location of the VE is defined. Geonames Records, Custom Location Indicators and Mobile Location Indicator services can be used.

veregistry3

veregistry5

After these fields have been filled the user has to proceed to the Iterface Endpoint Definition. This is is used to describe how the IoT Resources or the VE services are accessed.

veregistry9

Once the endpoints have been described, the user can annotate the VEs which are using these services. VE annotation follows the same pattern with regards to the identification and location description. After these attributes have been set,  the user can add VE Properties which expose the IoT and VE services. A VE Property is bind to an endpoint of these services.

veregistry12

 

veregistry14

COSMOS VE Registry tool also includes a search function facilitating the retrieval of any COSMOS entity which has been annotated and published. It includes a multi-criteria, aproximation and location enabled retrieval.

search9

search10

It also includes a graph based entity visualization and exploring functionality.

search11

search12

 

Installation guide

1. Requirements:
JBoss 7.1
openrdf-sesame.war 2.8.8
openrdf-workbench.war 2.8.8
VERegistry.war
veregistry-api.war
cosmosontology file

2. Walk through:
2.1. Deploy openrdf-sesame.war and openrdf-workbench.war on JBoss.

2.2. Check if sesame is working by accessing in a browser the following URI pattern:
http://domainname:jbossrunningport/openrdf-sesame/
and it will take you to
http://domainname:jbossrunningport/openrdf-sesame/home/overview.view
where you can see the sesame server version and some other related information.

2.3. Check if the workbench is working by accessing in a browser the following URI pattern:
http://domainname:jbossrunningport/openrdf-workbench/
and it will take you to
http://domainname:jbossrunningport/openrdf-workbench/repositories/NONE/repositories

2.4. Create a repository.
In the workbench interface click on ‘New repository’ on the left side menu bar.
It will take you to a page where you have to select the repository type (We used In Memory Store).
Also you have to give the repository an ID and a name (please remember the ID, or write it down somewhere).
Click ‘Next’. Check the ‘Persist’ radio button to yes and click ‘Create’.

2.5. Upload the cosmos ontology file.
In the workbench click on ‘Add’ in the left menu bar.
After that hit the ‘Choose File’ button and select the cosmos ontology file.
The ‘Base URI’ will auto complete. Modify it to this value ‘http://siemens.com/ct/ontologies/CosmosOntology.owl#’.
Click upload.

2.6. Open the veregistry-api.war with 7.zip or an alternative tool.
Go to WEB-INFclasses and open the repoconnect.properties file.
Change the ‘serverURL=http://192.168.200.3:9000/openrdf-sesame/’ to your sesame URI( http://domainname:jbossrunningport/openrdf-sesame/).
Change the ‘repositoryName=cosmos’ with the repository ID that you created earlier.
Save the file and close it.

2.7. Open the VERegistry.war with 7.zip or an alternative tool.
Go to WEB-INFclasses and open the apiConnector.properties file.
Change the ‘api-url=http://www.bamct.siemens.ro:9000/veregistry-api/’ the URI pointing to veregestry-api.war deployment.
Ex pattern: api-url=http://domainname:jsbossrunningport/veregistry-api/

2.8. Deploy the VERegistry.war and veregistry-api.war.
Go to http://domainname:jbossrunningport/VERegistry and everything soud work fine.

NOTE: If you use a downloaded version of sesame, the circle search feature will not work. We modified the openrdf-sesame.war to support custom
functions called in sparql queries.

Service level

Technology Readiness Level

5 - technology validated in relevant environment

Reuse Readiness Levels

5 - Reuse is practical; the software could be reused by most users with reasonable cost and risk

A instance of the tool has been deployed at http://www.bamct.siemens.ro:9000/VERegistry and artifacts and instructions for custom deployments are also provided.