Gateway Mode with Explicitly-Defined Remote Things Example
Although Remote Things can be set to identify themselves to the EMS, in many cases the remote things that connect to the EMS are well-known. In this case, you can explicitly define them within the configuration of the EMS.
For more information on configuring the auto_bind group of the configuration file, refer to the section, Configuring Automatic Binding for EMS and to the section, AutoBound Gateways.
The example below illustrates how to configure the EMS for this scenario:
 |
In the example below, EdgeThing001 is an explicitly defined Remote Thing that runs at a specified IP Address and listens on port 8001.
|
{
"ws_servers":[{
"host":"",
"port":443
}]
"appKey":"some_encrypted_application_key",
"ws_connection":{
"encryption::"ssl"
}
"auto_bind"[{
"name":"EdgeGateway001",
"gateway":true
}
{
"name":"EdgeThing001",
"host":some_ip_address>",
"port":8001
}]
"ws_servers":[{
"host":"",
"port":443
}]
"appKey":"some_encrypted_application_key",
"ws_connection":{
"encryption::"ssl"
}
"auto_bind"[{
"name":"EdgeGateway001",
"gateway":true
}
{
"name":"EdgeThing001",
"host":some_ip_address>",
"port":8001
}]
To encrypt an application key, refer to Encrypting Application Keys, Passwords, and Passphrases.