Difference between revisions of "M2M Bridge"
From AMTech WikiDocs
(→Configuration) |
(→Configuration) |
||
| Line 39: | Line 39: | ||
}, | }, | ||
"networkFailed" :{ | "networkFailed" :{ | ||
| − | + | "retries" : 5, | |
"failedWait" : 3000, | "failedWait" : 3000, | ||
"reconnectWait" : 60000 //re-connection delay after an instance of plug in failed | "reconnectWait" : 60000 //re-connection delay after an instance of plug in failed | ||
}, | }, | ||
"pluginLoad" :{ //bridge startup configuration | "pluginLoad" :{ //bridge startup configuration | ||
| − | + | "sendM2mBridgeError" : true //send observations error when errors occurred at bridge layer | |
}, | }, | ||
"logger" :{ | "logger" :{ | ||
| − | + | "colorize" : true, //colorize log console messages | |
"level": "debug" //log level | "level": "debug" //log level | ||
}, | }, | ||
"address" :{ //Address use to geo locate m2mBridge instance | "address" :{ //Address use to geo locate m2mBridge instance | ||
| − | + | "country" : "usa", | |
"city": "Las Vegas", | "city": "Las Vegas", | ||
"road": "Las Vegas Boulevard South", | "road": "Las Vegas Boulevard South", | ||
| Line 58: | Line 58: | ||
"bridgeId":"m2mBridgeProgressNext", //Id to uniquely identify m2m Bridge instance, in absence of this property a unique identifier gets created | "bridgeId":"m2mBridgeProgressNext", //Id to uniquely identify m2m Bridge instance, in absence of this property a unique identifier gets created | ||
"autoDiscover":{ | "autoDiscover":{ | ||
| − | + | "execute" : false, //create things type instances at startup time | |
"instances":{"SNMPDevice":[{...}], ...} //Jsonld instances to be created | "instances":{"SNMPDevice":[{...}], ...} //Jsonld instances to be created | ||
} | } | ||
Revision as of 16:15, 3 March 2016
Contents
Functionality
- Configurable edge intelligence
- Bridges standard and proprietary protocols to AMTech IoT DAP.
- Device-to-device or device-to-server communications.
- MQTT, LLRP, CoAP, STOMP, SmartM2M, LWM2M, PLC, Zigbee and others
- Allow remote and centralized control of IoT devices and gateways.
- SNMP/MIB/TRAP, Reader Management and other
- Configurable autodiscover
- Implements common functionality and host the execution of the protocols
- Network failure detection and recovery
- Get centralized configuration information at startup and real time modifications
- Access control policies to manage observation production and consumption
Configuration
- Edge/Device(s) site configuration bridgeConfig.json #1
- located at M2MBridge root directory.
{
//text to label bridge instance
"description": "AMTech M2M Bridge",
"dap":{
//amtech IoT DAP ur
"dapUrl": "https://dap.amtech.mx",
//userid for the m2mBridge instance
"userId": "xxxxxxx@amtech.mx",
// tenant where bridge been configured
"tenant" : "xxxxxxx",
//m2mBridge userId password
"password" :"xxxxxxxx",
//topic to get crud and command observations
"crudCommandUrl" :"/xx/xx/"
},
//access control information add to send observations
"guestSecurity":{
//add guest tenants to observations send from bridge
"guesttenants":["progressnext2016"],
//add guest users to observations send from bridge
"guestusers":[]
},
"networkFailed" :{
"retries" : 5,
"failedWait" : 3000,
"reconnectWait" : 60000 //re-connection delay after an instance of plug in failed
},
"pluginLoad" :{ //bridge startup configuration
"sendM2mBridgeError" : true //send observations error when errors occurred at bridge layer
},
"logger" :{
"colorize" : true, //colorize log console messages
"level": "debug" //log level
},
"address" :{ //Address use to geo locate m2mBridge instance
"country" : "usa",
"city": "Las Vegas",
"road": "Las Vegas Boulevard South",
"number":"3960"
},
"bridgeId":"m2mBridgeProgressNext", //Id to uniquely identify m2m Bridge instance, in absence of this property a unique identifier gets created
"autoDiscover":{
"execute" : false, //create things type instances at startup time
"instances":{"SNMPDevice":[{...}], ...} //Jsonld instances to be created
}
}
