Foreword

INTER-IoT is a complete interoperability framework whose layers are more o less independent implementations solving specific IoT interoperability problems.

These layers provide solutions for problems that can happen simultaneously in integration scenarios, however, the design of the layers have been kept independent during the INTER-IoT technical execution, to let them free of constrains from other layers and allowing to find optimal solutions for each single layer problem. This have encouraged independency and efficiency in the analysis and development phases of the project.

However, this efficiency would disappear if in the integration phase the user of INTER-IoT would be forced to use all five the independent layers following different ways of defining the problem, configuring, deploying monitoring, etc. This would imply for instance that an integrator could be tempted to deploy all layers by default solving twice the same problem with two different layers, having an evident configuration overhead and increasing complexity that in the end could end in abandoning the INTER-IoT solution and coming back to old-fashioned ad-hoc implementations.

To solve this issue, INTER-IoT have a complete configuration and management framework devoted to help developers, system integrators and IT administrators to deploy, configure and control all the interoperability instances that each specific scenario needs.

The INTER-IoT framework is visual based, presented in the form of a cloud application. It has the property of summarize in a single window all the interoperability activities that are running in a specific deployment of INTER-IoT, so that it is easier to launch new layer components, design interoperability strategies or check the correct functioning of a solution.

As INTER-IoT framework is a visual tool, it was included and in-tool specific documentation (an step-by-step overlay) that guides users in each of the menus of the tool. For this reason, in this document there are only recipes related to the deployment of the framework and, in section security, how the security is addressed using the tool.