Skip to content

Commit

Permalink
Update wis2-architecture.adoc (#90)
Browse files Browse the repository at this point in the history
* Update wis2-architecture.adoc

Add protocol section with HTTP(S).

* Update wis2-architecture.adoc

---------

Co-authored-by: Tom Kralidis <[email protected]>
  • Loading branch information
golfvert and tomkralidis committed Jan 26, 2024
1 parent 1d24dcb commit 0b05b3c
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions guide/sections/part2/wis2-architecture.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,9 @@ Leveraging existing open standards, WIS2 defines the following specifications in
ii) Whether data can be effectively accessed by Data Consumers.
iii) The performance of components in the WIS2 system.

=== Publish-Subscribe protocol configuration (MQTT)
=== Protocols configuration

==== Publish-Subscribe protocol (MQTT)

* The MQTT protocol is to be used for all WIS2 Publish-Subscribe workflow (publication and subscription).
* MQTT v3.1.1 and v5.0 are the chosen protocols for the WIS2 Notification Messages publication and subscription.
Expand All @@ -123,4 +125,10 @@ Leveraging existing open standards, WIS2 defines the following specifications in
** A maximum of 2000 messages to be held in a queue per client
* In order to permit authentication and authorization for users, WIS2 Node, Global Cache, Global Discovery Catalogue and Global Brokers shall use a user and password based mechanism.
* To improve the overall level of security of WIS2, the secure version of the MQTT protocol is preferred. If used, the certificate must be valid.
* The standard TCP ports to be used are 8883 for MQTT and 443 for Secure Web Socket (WSS).
* The standard TCP ports to be used are 8883 for Secure MQTT (MQTTS) and 443 for Secure Web Socket (WSS).

==== Download protocol (HTTP)

* The HTTP protocol is to be used for all WIS2 download workflow.
* To improve the overall level of security of WIS2, the secure version of the HTTP protocol is preferred. If used, the certificate must be valid.
* The standard TCP port to be used is 443 for Secure HTTP (HTTPS).

0 comments on commit 0b05b3c

Please sign in to comment.