Skip to content

6 Preparation for L2 compliance

Jump to bottom
Vasilis Glykantzis edited this page Sep 7, 2018 · 3 revisions

This is a page containing a detailed description of the platform L2 integration process for the Release 2.+. As a result of the following steps you will setup and run symbIoTe Cloud components for your platform. You will also register your platform symbIoTe Core offered by symbIoTe project, which collects the metadata for all symbIoTe-enabled platforms. You will also be able to register and access resources in federations which your platform participates to.

In order to run symbIoTe Cloud components you need to have public IP address with DNS entry. For testing purposes and Hackathons, we provide instructions that use ngrok tool/service but this is not for production.

6.1 Preparation steps

The process for making your platform L2-compliant is actually very similar to making your platform L1-compliant. The main difference is that in L2, there is a need for some extra components (i.e. FederationManager, SubscriptionManager, PlatformRegistry).

Microservices

Component Supported Version Exposed ports Purpose
FederationManager (FM) 3.x 8202 - HTTP This component is responsible for listening to federation events (i.e. federation created/deleted/updated) and informing the other cloud components.
SubscriptionManager (SM 3.x 8128 - HTTP This component is responsible for notifying about resource registration/update/unregistration other interested platforms in federations where our platform participates.
PlatformRegistry (PR) 3.x 8203 - HTTP This component is responsible for storing metadata about resources exposed in the federations our platform participates to. This component also offers an endpoint for searching for such resources.
TrustManager (TM) 3.x 8204 - HTTP This component is responsible for calculating the platform and resource trust.
BarteringAndTrading (BT) 3.x 8205 - HTTP This component is responsible for bartering support in federations.
SLA Manager (SLAM) 3.x 8200 - HTTP This component is responsible for verifying that the agreed SLA is met.

So, the Platform Owner has to complete the steps described in chapters 1 and 2 before going on installing the extra components

Getting Started
Migration to 3.0.0
Migration to Docker

  1. Preparation steps
    1.1. Register user and configure platform in symbIoTe Core
    1.2. Installation of required tools for symbIoTe platform components
    1.3. Downloading jars
    1.4. Downloading sources
  2. Configuring and starting components
    2.1. Configuration of NGINX
    2.2. Starting third party tools that are prerequisite for symbIoTe
    2.3. Starting (generic) symbIoTe Cloud components
    2.4. Configuration of cloud components
    2.4.1. Starting symbIoTe Cloud components
    2.5. Setting up the Platform Authentication and Authorization Manager (PAAM)
    2.6. Starting Registration Handler and resource management
    2.7. Set up of Resource Access Proxy
    2.8. Manage resources
    2.9. Set up of the Monitoring component
    2.10. Other configuration topics
  3. Test integrated resource
    3.1. Security
    3.2. Search for resources
    3.3. Obtaining resource access URL
    3.4. Accessing the resource and actuating and invoking service for default (dummy) resources
  4. Creating RAP plugin
    4.1. Customizing internal RAP plugin
    4.2. Using RAP plugin starter
    4.3. Creating RAP plugin in other languages
  5. Resource Description Examples
    5.1. JSON Description Examples
    5.2. RDF Description Examples
  6. Preparation for L2 compliance
  7. Configuring and starting components for L2
    7.1. Starting Federation Manager
    7.2. Starting Subscription Manager
    7.3. Starting Platform Registry
    7.4. Starting Trust Manager
    7.5. Starting Bartering And Trading
    7.6. Starting SLA Manager
    7.7. Create a federation
    7.8. Manage resources in L2
    7.9. Register Subscription
  8. Test Integrated L2 Resources
  9. Developing symbIoTe enabled apps
Clone this wiki locally