Test Case Title	TC9.2 - Managing heterogeneous File Ingestion, protocols, formats via IOT applications, and open standards
Goal	I can Manage heterogeneous files of different kind with Snap4City Application. Manage heterogeneous protocols with Snap4City Application. Manage formats and communication with open standards
Prerequisites	Using a PC or Mobile with a web browser. You need a Snap4City account. The following functionalities are available only for specific Snap4city users with specific privileges.
Expected successful result	Generation of flows of data corresponding to the selected sensors. The sensors is retrieved from the context brokers in which they are registered.
Steps

 

In this case, several Node-RED blocks are available for accessing data in a specific format (XML, CSV, HTML, YALM, JSON) and translate them into the JavaScript Object representation. Once the data are represented in this target format, it can be easily and uniformly processed and transformed for the application needs. The same Node-RED blocks can be exploited for exporting a value in the JavaScript Object representation in the corresponding format. Once the data have been processed, they can be visualized in a dashboard or stored into a Big Data Storage and/or Knowledge Base by using some Block.

1. You can start testing this requirement by following the sequence of actions:
   • Open a Flow in your cloud (TC2.1a) or local (TC2.1b) IotApplication
   • Import for testing the flow  "TC9.2..." with the steps described in TC2.13 (on cloud) or import it from a file (if you have not an IOT Application on cloud)
2. You can click on the button  to deploy the application and then click on the inject button . The result of the translation can be seen in the debug section (right hand side part of the page). The info tab (right hand side part of the page) contains comment on the current experiment (description of the current scenario and expected result).

In this list the correct name of the resource to download (from Resource Manager or clicking on the name or following the step on TC2.13 ) for testing the protocols

• JSON: TC9.2 (JSON) - Managing heterogeneous

• GeoJSON:  TC9.2 (GeoJSON) - Managing heterogeneous
• HTML:  TC9.2 (HTML) - Managing heterogeneous

• XML: TC9.2 (XML) - Managing heterogeneous

• RDF: TC9.2 (RDF) - Managing heterogeneous

• CSV: TC9.2 (CSV) - Managing heterogeneous

• XLS: TC9.2 (XLS) - Managing heterogeneous

• WSDL: TC9.2 (WSDL through SOAP) - Managing heterogeneous

• HTTP: TC9.2 (HTTP) - Managing heterogeneous

• FTP: TC9.2 (FTP) - Managing heterogeneous

• REST: TC9.2 (REST) - Managing heterogeneous

• Web Socket: TC9.2 (WEB-SOCKET) - Managing heterogeneous

• UDP: TC9.2 (UDP) - Managing heterogeneous

• TCP: TC9.2 (TCP) - Managing heterogeneous

• Twitter: TC9.2 (TWITTER) - Managing heterogeneous

• MySQL: TC9.2 (MySQL) - Managing heterogeneous

• CSV via HTTP: TC9.2 (CSV via HTTP) - Managing heterogeneous

• XML via HTTP: TC9.2 (XML via HTTP) - Managing heterogeneous

• HTML via HTTP: TC9.2 (HTML via HTTP) - Managing heterogeneous

• JSON via HTTP: TC9.2 (JSON via HTTP) - Managing heterogeneous

• XLS via HTTP: TC9.2 (XLS via HTTP) - Managing heterogeneous

• OMA LWM2M TC9.2 (OMA LWM2M) - Managing heterogeneous
• MQTT, by means of the Mosquitto Server (https://mosquitto.org/) TC9.2 (MQTT) - Managing heterogeneous
• NGSI, by means of the Orion Context Broker (https://fiware-orion.readthedocs.io/) TC9.2 (NGSI) - Managing heterogeneous
• AMQP, by means of the RabbitMQ Server (https://www.rabbitmq.com/) TC9.2 (AMQP) - Managing heterogeneous
• STOMP, by means of the RabbitMQ Server (https://www.rabbitmq.com/) TC9.2 (STOMP) - Managing heterogeneous