8. Test Integrated L2 Resources

After a resource has been shared in a federation, we can test if we can find and access it properly.

8.1 Security

Security in L2 does not differ compared to L1, since we use the same ABAC approach. The only restriction here is that in order to access a resource shared in a federation, we need a valid security token from a platform that is a member of the federation.

8.2 Search for resources

The search for resources in L2 differs significantly compared to L1, since the search requests are handled from the Platform Registry instead of the Search Component in the Core. Furthermore, as of Release 2.0.0, the Platform Registry offers two basic functionalities:

• Listing all the available resources
• Filtering all the available resources in a specific federation

8.2.1 Listing all the resources

This is done by sending a HTTP GET request on the Platform Registry list_resources endpoint (i.e. http://127.0.0.1:8203/pr/list_resources). As a result, you will get back a FederationSearchResult.

{
  "resources": [
    {
      "symbioteId": "7513f65108884234@icom-platform",
      "cloudResource": {
        "internalId": "1500",
        "pluginId": "openhab",
        "accessPolicy": null,
        "filteringPolicy": null,
        "resource": {
          "@c": ".StationarySensor",
          "observesProperty": [
            "temperature",
            "humidity",
            "atmosphericPressure",
            "carbonMonoxideConcentration",
            "nitrogenDioxideConcentration"
          ],
          "id": null,
          "name": "DefaultSensor1",
          "description": [
            "Default sensor for testing RAP"
          ],
          "interworkingServiceURL": "https://intracom.symbiote-h2020.eu/",
          "locatedAt": {
            "@c": ".WGS84Location",
            "longitude": 52.513681,
            "latitude": 13.363782,
            "altitude": 15,
            "name": "Berlin",
            "description": [
              "Grosser Tiergarten"
            ]
          },
          "services": null,
          "featureOfInterest": {
            "name": "temperature feature of interest",
            "description": [
              "measures temperature"
            ],
            "hasProperty": [
              "temperature",
              "humidity",
              "atmosphericPressure",
              "carbonMonoxideConcentration",
              "nitrogenDioxideConcentration"
            ]
          }
        },
        "federationInfo": {
          "symbioteId": "7513f65108884234@icom-platform",
          "sharingInformation": {
            "fed1": {
              "sharingDate": 1525272416589,
              "bartering": true
            }
          }
        }
      },
      "oDataUrl": "https://intracom.symbiote-h2020.eu/rap/Sensors('7513f65108884234@icom-platform')",
      "restUrl": "https://intracom.symbiote-h2020.eu/rap/Sensor/7513f65108884234@icom-platform",
      "federations": [
        "fed1"
      ]
    }
  ]
}

, where each array entry in the resources field has the following fields:

• symbIoTeId: the id of the resource in the federations that is shared
• cloudResource: the cloudResource description used to register the resource
• oDataUrl: the oData endpoint for accessing the resource. Here, you need again to add any operators (e.g. /Observations)
• restUrl: the REST endpoint for accessing the resource
• federations: the ids of the federations, where the resource is shared to

8.2.2 Filtering by federation id

Likewise, in order to filter by federation id we have to send a HTTP GET request on the Platform Registry list_federation_resources endpoint containing the federation id (i.e. http://127.0.0.1:8203/pr/list_federation_resources/{fedId}). The response is again a FederationSearchResult.

8.3 Accessing resources

Once, we have obtained a L2 resource URL as described above, accessing a L2 resource is exactly the same as accessing a L1 resource.