Gateway Mode with Self-Identifying Remote Things Example
The EMS can be configured to run as a gateway, acting as the communication conduit and providing message relaying services for one or more Remote Things.
The EMS keeps a registry of the Remote Things for which it acts as a gateway. You can set up the Remote Things to “self-identify” with the EMS. That is, when the Remote Things initialize and connect to the EMS, they send the information that uniquely identifies them to the EMS. This information is stored in the registry 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:
{
"ws_servers": [{
"host" : "acmeServer.mycompany.com",
"port": 443
},
{
"host" : "fallback_server.somewhere.com",
"port": 443
}]
"appKey" : "some_encrypted_application_key",
"ws_connection": {
"encryption" : "ssl"
}
"auto-bind": [{
"name" : "EdgeGateway001",
"gateway": true
},
{
"name" : "EdgeThing001",
"host" : "some_ip_address",
"port": 8443
}]
}