TC2.27 - Add new Broker managing new protocol, and the corresponding NIFI process for indexing

Primary tabs

Test Case Title

TC2.27 - Add new Broker managing new protocol, and the corresponding NIFI process for indexing

Goal

I, as  toolAdmin rootAdmin, can:

include in the snap4city environment a new Broker that manage a new protocol.

Register new broker into the IoT Directory and for the corresponding NIFI process for indexing.

Prerequisites

Using a PC or Mobile with a web browser. Access to the back office since this process for changing the flow if needed. The implementation is performed into a data driven VM based on NIFI that can be scaled up.

The following functionalities are available only for specific Snap4city users with specific privileges.

Expected successful result

A new context broker has been properly set up and the access (for reading or sending commands and notifications) are properly logged in Sorl.

Steps

 

 

In this test case we first show the registration of a context broker in the IoT Directory and then provide a description of its registration in the context of NIFI.

  1. By logging as toolAdmin (or rootAdmin) and clicking on the “IOT Directory and Device” button and then on “IOT Brokers” you see the list of available brokers and you can create a new broker

  1. Click on the  button, we can create a new one. A modal menu appears in which you can specify the properties of the new context broker



    Context broker properties are organized in three tabs:
  • Info: It contains the unique logical name associated with the context broker, the IP address, port, and protocol according to which events are transmitted.
  • Geo-Position: the longitude and latitude in which the context broker is located
  • Security: login and password required for accessing the context broker (in our experiments are not required). 

The geo-position of the Context Broker can be specified by the user by clicking on the map as follows

 

  1. Please feel out the form as follow (login and password are related to the context broker that at current stage are not specified).

 

Name

orionUNIFI2

IP

192.168.1.10

Protocol

Ngsi

Port

1026

All the fields (with the exception of Login/Password) are mandatory. If you do not insert them or specify a wrong value (e.g. Port number, IP address) a specific error message is reported. When you have concluded click on the “confirm” button.

  1. If the operation is concluded with success, the context broker appears in the list of available context brokers. At this point you can activate the stub for acquiring the devices that are already registered in the Broker (details on this activity are reported in TC6.2)

    Point the browser on NIFI framework and in the IOT region and copy the “Process Group” named “Template Read NGSI” by right clicking as depicted in the following Figure

 

  1. Paste in the desired position  (See Figure below)

 

  1. Choose a convenience name for the new Block right-clicking on the center of the canvas and then selecting “Configure” as in the following figure

  1. Setup the broker host by setting the relative variable by right-clicking on the center of the canvas and then selecting “Variables” as in the following figure

  1. Mouse hover on the center of the process canvas and left-click to drag the resulting arrow to the flow collector (See Figure below)

Right-click on the center of the process canvas and choose play,  the data generated by the block is stored and indexed on the snap4city platform.