Skip to content

1 Preparation steps

Jump to bottom
JTPCSS edited this page Sep 27, 2018 · 10 revisions

The symbIoTe Cloud components are explained in the following table.

Infrastructure components

Component Supported Version Exposed ports Purpose
RabbitMQ 3.6+ 15672 - Web based management 5672 - AMQP protocol For communication between all cloud components
MongoDB 3.6+ 27017 - Mongo DB access port All components use this database when they are running on one machine but it can be split to more then one database.
nginx - Inteworking Interface 1.12.+ 443 - HTTPS 8102 - HTTP This is gateway to cloud microservices. Microservices can be accessed only through this Interworking Interface. In the case of having certificate it uses HTTPS and in case of using ngrok tool it will use HTTP
SpringCloudConfig 8888 - HTTP This component is used for serving configuration to other components. It uses CloudConfigServer from SpringCloud.
Eureka 8761 - HTTP This component is used for discovery of other components. All other components are registered in Eureka at startup.
Zipkin 8762 - HTTP This component is used for distributed tracing. It is used for debugging communication between components.
gradle 4.6+ If there is a need to build the components
java 1.8 Oracle Java 8 version 8u131+ or OpenJDK version 8u101+

Microservices

Component Supported Version Exposed ports Purpose
AuthenticationAuthorizationManager (AAM or PAAM) 3.+ 8080 - HTTP This component is responsible for security. This port is used for communication to Core services.
RegistrationHandler (RH) 1.2+ 8001 - HTTP This component is responsible for registration of resources. It exposes HTTP, port where you can send request to register/update/unregister resources. This must be used only in the local network.
ResourceAccessProxy (RAP) 1.2+ 8103 - HTTP This component is responsible for accessing resources. It need to be connected to your platform through RAP plugin.
Monitoring 2.0+ 8201 - HTTP This component is responsible for monitoring the platform resources and notifying the core about their status.

For the example integration process described below, we assume the following addresses of various Core and Cloud components (NOTE: those are supposed to be changed to real addresses of Core and Cloud services during integration):

Parameter URL
Admin GUI https://symbiote-open.man.poznan.pl/administration
AuthenticationAuthorizationManager (AAM, PAAM) https://myplatform.eu/aam
Cloud Core Interface https://symbiote-open.man.poznan.pl/cloudCoreInterface
Core Interface https://symbiote-open.man.poznan.pl/coreInterface
Registration Handler (RH) https://myplatform.eu/rh
Resource Access Proxy (RAP) https://myplatform.eu/rap

In this table the platform.eu is your platform DNS entry. In next sections, we use concrete examples with symbiotedoc.tel.fer.hr DNS entry.

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