Différences

Ci-dessous, les différences entre deux révisions de la page.

--- cours:mit_2018_2019:soa4iotlab [2019/02/04 16:24] – [SOA for IoT and WS-SOAP] tigli
+++ cours:mit_2018_2019:soa4iotlab [2019/02/05 06:57] (Version actuelle) – tigli
@@ Ligne 96: / Ligne 96: @@
 [[cours:mit_2018_2019:node_red_soap_client_correction|correction]]
-** Soap server **
-** Exercice**: Create your own soap server with // npm install node-red-contrib-soapserver// (see [[https://www.npmjs.com/package/node-red-contrib-soapserver| ]]).
-This package provides a node that can be used to start a Node-RED flow. The node is called soap server and listens on a configurable TCP port on the host on which Node-RED run. It is important that the port number be supplied as there is no default assumed. The listener is listening for an incoming SOAP/HTTP request. The WSDL that describes the SOAP server can be retrieved through an HTTP GET request using the <code> /soap?wsdl </code> URL and query parameters. For example:
-<code>
- http://<node-RED-Host>:<port>/soap?wsdl **.
-</code>
-The endpoint for the SOAP request is found at the same address
-<code>
-http://<node-RED-Host>:<port>/soap
-</code>
-The interface supplies one operation called startFlow which takes a single parameter as input of type string. When a client invokes that operation, a new Node-RED flow is initiated. The passed in data appears in the msg.payload property of the Node-RED message.
-A Node-RED flow that starts with a soap server node should also conclude with a corresponding soap server output node. This is used to pass back a value to the original SOAP client. The string found in msg.payload is returned as the response value.
-**Soap client**
-**Exercice:** write your own client programm of a SOAP web service and node-red-contrib-soap package [[https://flows.nodered.org/node/node-red-contrib-soap|SOAP web service]]. Create a WS-Soap Client to test your own WS-Soap server.
-** Advanced Exercice**: write your own soap server that get an MQTT topic and provide it on web service client  request
 ==== SOA for IoT and CoAP ====
@@ Ligne 148: / Ligne 121: @@
 [[https://flows.nodered.org/node/node-red-contrib-coap]]
-== IoT Use Cases with CoAP ==
-==== Advanced SOA - Service Registry ====
-== Get started with UDDI ==
-== UDDI in Node-Red ==
-== IoT Use Cases with UDDI ==
-==== Advanced SOA for IoT - Service Discovery Protocol ====
-== Get started with SSDP ==
-== SSDP in Node-Red ==
-== IoT Use Cases with SSDP ==
-==== SOA for IoT  : Web Service for Device (UPnP and DPWS) ====
-== Get started with UPnP ==
-== UPnP in Node-Red ==
-== IoT Use Cases with UPnP ==
-== Get started with DPWS==
-== DPWS in Node-Red ==
-== IoT Use Cases with DPWs ==
-====== Synthesis =======
-Middleware for IoT are deployed on heterogeneous IoT Plateform to provide a more homogeneous way to develop some distributed software applications. Most of the time, we distinguish four levels : IoT Devices, Edge, Fog, and Cloud.
-**Exercice :** Find in the technical and scientific litterature some definitions and recent surveys on these concepts for IoT. Write a paper (Max 2 pages long) on this 4-levels point of view of distributed system that can then emerged like CyberPhysical Systems.
-For example you can argue :
-  * why differents patterns of communication are used in this 4-levels System,
-  * what are the famoust technologies for each levels
-<note>
-This paper will be sent **To tigli@unice.fr** with ** Subject : <Your Name> IoT Paper 2019 ** as to attached files : one .zip with sources (tex/docx) and one pdf,  no later than 10th of February
-</note>