Guide for Extensions

5 Testbed & Resource registration

5.1 Testbed Registration

The Testbed Registration UI can be found at the FIESTA-IoT portal under the Testbed Provider Menu (see 1st Figure below) item named the “Register Testbed”. 

Register Testbed page (see 2nd Figure below) will show the list of registered testbeds and enable user to register a new testbed. The admin user can view all the registered testbeds, whereas the testbed providers only see their own testbeds that they have registered.

In principle, you should see an empty list the first time you enter into the portal and, once you have registered your testbed, you should see it on the list. As far as you are registering only one testbed, there should be only one row listed in the UI.

The user can register a new testbed by clicking the “Register new testbed” button, a register testbed page (see 3rd Figure);  a register testbed page will be shown where the user inputs testbed related information:

  • Input IRI. This has to be unique for each registered testbed. Note that this IRI is the one that you will have to use when creating your annotated resource descriptions for the ssn:Deployment individual. This is important since it is the way of linking your devices to your testbed. For example, if the IRI you provide in the form is: http://testbed.test.com#testTestbed, then your devices’ descriptions will have to include a statement like: http://testbed.test.com#device1 ssn:hasDeployment http://testbed.test.com#testTestbed.
  • Input Annotated Resource Observation. This is a sample observation as it results from your annotator. Although this has been already checked during the certification process, the testbed registration form is created to do on-line validation. You must specify the appropriate data format by selecting a format from combo-box list. Validate it by clicking Validate Observation button in order to enable the Save button at the bottom of the testbed registration form.
  • Input Annotated Resource Description. This is a sample resource description as it results from your annotator. Although this has been already checked during the certification process, the testbed registration form is created to do on-line validation. You must specify the appropriate data format by selecting a format from combo-box list. Validate it by clicking Validate Annotated Resource button in order to enable the Save button at the bottom of the testbed registration form.
  • Input latitude and longitude. These are the GPS coordinates of your testbed. They are mainly used for map representation of your testbed. Typically, core of the testbed if it is distributed among a large area (e.g. city-hall for smart city).
  • Input Name. Just for informational purposes. Human-friendly name to be used for identifying your testbed.

Other remaining textboxes are optional. However, some of them are still important for completing the testbed integration.

  • Input Get Last Observations URL, Get Observations URL, Push Last Observations URL and Push Observations URL. You have to specify the URL for the TPS interface(s) that you have developed for your testbed. Only one out of the four options is necessary. Identify the one that you have implemented and provide the corresponding endpoint. Those that are not provided will not be available for Testbed Provider Interface (TPI) Configuration.
  • Input Get API Key and Push API Key. In case your TPS endpoint is protected using an API Key, you have to provide it. This API key is the one that the Fiesta−IoT Platform will use when calling at your TPS. Depending on which of the four options (i.e. two Get-based or two Push-based) you have implemented you have to provide the corresponding API key(s). If your endpoint(s) is not protected, then leave the field blank.
  • Note that if you support both types of TPS, then you should provide the corresponding API key for each of them (if it is the same one, you have to copy it in both fields)

When the user clicks the Save button, if the registration process is successful the register testbed page will disappear and a success message is displayed along with the identifier of the registered testbed.

You can confirm that the registration has been correctly stored at the Fiesta−IoT Platform semantic repository by taking the following steps:

1. Since Fiesta−IoT Platform hides your testbed details, it gives your testbed a unique ID that you can get by making an HTTP call similar to the one below:

GET /iot-registry/api/utils/identifier/to_fiesta_iot?type=testbed&value=http%3A%2F%2Ftestbed.test.com%23ucExperimenterUser HTTP/1.1

Host: platform.fiesta-iot.eu

iPlanetDirectoryPro: AQIC5wM2LY4SfcwEw_Jg.........

Note that a valid SSO Token has to be previously obtained and added to the request. Also note that the appropriate Host has to be used. The IRI you provided when registering your testbed has to be provided as the query parameter value. As it is shown in the example, special characters like colon, slash, hash, etc., which are prohibited for URLs, have to be transformed into its appropriate URL encoding.

2. Make the following HTTP Request (i.e. accessing your testbed URL as result of step 1):

GET 

/iot-registry/api/testbeds/1B2F37ZYQ5A4I5... HTTP/1.1

Host: platform.fiesta-iot.eu

iPlanetDirectoryPro: AQIC5wM2LY4SfcwEw_Jg.......

....

Note that a valid SSO Token has to be previously obtained and added to the request. Also note that the appropriate Host has to be used. The result should be an annotated document of your testbed as an ssn:Deployment node in RDF format.