INTER-FW Configuration and Management Framework Web Application

This section explains how the web application is structured and which desing decision have been made during the development.

Application tabs

The application is composed by a set of different views represented by navigation tabs. Each of these tabs have a specific purpose, where some of them are devoted to the management of a spefic layer and other to cross-layer or global features.

Tabs

The different tabs that can be visited are described in the following points sub sections.

Main view

Not accesed by a tab, it is the first view accessed whenever a user get to the applicaiton for the first time in a session. The view can be accessed by clicking the INTER-IoT icon on the top left corner. It shows a list of currently connected IoT nodes (platforms and gateways) with summary information about their activity including:

  • Platform icon if available in the current INTER-IoT deployment
  • Platform / gateway name
  • Platform / gateway access URL
  • Platform location
  • Platform accessibility status (online / offline)

Detail main view

This view does not have any particular data model. Its content is gathered from API calls to the MW2MW and D2D layers.

Platforms

This tab contains three different views:

  • List of platforms working in the current instance of INTER-IoT. This list contains basic meta-data as it is stored in the MW2MW layer, including the platform ID, the human readable name, the type of platform (this is, the generic implementation), the URL to the location of the platform, the base endpoint for API calls and the client ID who has registered the platform.
  • Platform detail. Accessed when clicking one of the platforms of the list, it provides a detailed information of the platform clicked.
  • Platform devices. The sub-tab devices contains a reference to every IoT device (physical or virtual) that is currently registered in the plaform analysed. Devices can be removed or modified by using the action icons or by clicking the devices, which opens a pop-up to edit the device details.

Devices

This tab manages all the devices connected to INTER-IoT, this is very similar as the platform devices view of the platforms tab, with the difference that in this general tab, all the devices are listed, regardles the platform they are connected.

Gateways

This tab is intented to manage the gateways (virtual and physical deployments) which implement the D2D layer. In this case, the first view shows a list of the devices deployed to the current instance of INTER-IoT. By clicking a row, a new view is accessed, where there are displayed 5 different tabs:

  • Info: detailed information regarding the current gateway. The UUID of the device, software version details, build, extensions implemented in the software deployment and other meta-data such as the vendor are displayed.
  • API: this shows the API interface, represented as the UI of the OpenAPI (formerly Swagger) API description language.
  • Physical: Contains the list of physical devices currently deployed. Represented as a list, it contains basic information about these phsysical devices (ID,type,controller,number of sensors, number of actuators and status). By clicking one of the rows, a popup is opened showing more detailed data about the sensor, including the last measurements received, if any.
  • Virtual: this tab shows actions and information regarding the virtual gateway associated to the physical gateways and sensors. It represents a kind of digital twin of the physical devices.
  • Rules: here simple rules can be configured, modified and removed. The rules link actions between sensors and actuators of the different physical devices.

Network

In this tab are contained all the features related to the N2N Software Defined Network layer. It is composed by three sub-menus related to three different aspects of the network.

  • Topology. The virtual network deployment on INTER-IoT is shown. Sensors, servers and gateways are represented differently, network segments are defined as well as the MAC addresses of the devices involved.
  • Statistics. Gives information about the ports, interfaces and addressed of the involved devices in the virtual network. Clicking one of the rows (switches) links to a more detailed information abou the statistics of ports and flows.
  • Quality of Service (QoS). Shows the QoS rules per switch. Initially it is displayed a list of switches. After clicking in one of them, data relative to the data queues, rules and meters is showed for a particular switch.

Services

This tab represent the AS2AS layer mechanisms. The minimum unit of AS2AS interoperability are the flows. Once accessed the Services tab, a list of currently active nodes is shown. These nodes can be started / stoped from the list. By clicking one of the flows on the list, an editor is opened so that the interoperability application can be modified without leaving the INTER-FW application.

Apart from this, this tab also offers the possibility of uploading new nodes related to IoT Platforms interoperability and the posibility to create / remove /start /stop multiple instances of this interoperability layer.

Semantics

This tab manages in a visual and convenient way the interoperability mechanisms of the DS2DS layer.

In the top left corner of the pane, the URL where the DS2DS software, the IoT Platforms Semantic Mediator is located. This way, by changing and applying changes to this URL, multiple instances of the IPSM can be managed without switching of application. The semantics view is divided into three sub-menus:

  • Alignment
  • Channel
  • Translation

Policies

Here is the user inteface for the repository of authorization policies stored in the identity server. The interface allows to upload new XACML policies, that can be bound to specific users, platforms and roles in the identity server.

API Management

This tab provides links to the different API Management tools of INTER-IoT

  • WSO2 Identity Server
  • WSO2 API Publisher
  • WSO2 API Store

Users Management

In this view, the INTER-IoT users are managed. Initially, it shows a list of the INTER-IoT user that can be managed. These profiles are presisted in the identity server.

Configuration

Used for development purposes

Download

This tab is used to feed the INTER-CASE tool, developed for supporting the INTER-METH.