Commissioning and first steps
41/152
Ø
In the
Upstream Protocol
drop-down list, select the protocol that the
netFIELD OS shall use for sending data to the netFIELD Cloud
(“device-to-cloud” communication).
Note:
Note that messaging over WebSocket causes more “overhead” per
telegram. This might limit the performance if you want to stream
large quantities of data.
·
MQTT
– Uses TCP port
8883
·
AMQP
– Default protocol (most commonly used). Uses TCP port
5671
·
MQTTWS
– MQTT over WebSocket. Uses TCP port
443
(same as
HTTPS)
·
AMQPWS
– AMQP over WebSocket. Uses TCP port
443
(same as
HTTPS)
Important:
Make sure that your company’s firewall does not block the TCP port
(outgoing) of the selected upstream protocol.
Note:
If necessary, you can change the upstream protocol in the
netFIELD Portal after onboarding. See section
Device Navigation:
Edit device settings (Update mask)
in the operating instruction
manual
netFIELD Portal
, DOC190701OIxxEN.
Ø
In case your organization has a “Deployment Manifest” that you want to
use for your device, select the
Use Manifest
option.
Note:
The deployment manifest causes certain software containers
defined in the manifest to be automatically installed on your device.
(For further information on deployment manifests, see section
Deployment Manifest
in the
netFIELD Portal
manual,
DOC190701OIxxEN)
Ø
Click
Onboard
button to start the onboarding process.
ð
The device connects to the portal, is registered there and assigned to
your organization or sub-organization.
If the process has been successful, the following message appears:
Success – Device is now onboarded
.
From now on, the device will be listed in the portal’s
Device Manager
and can be managed from there.
netFIELD OnPremise | User manual
DOC200901UM02EN | Revision 2 | English | 2021-06 | Released | Public
© Hilscher 2021
