Difference between revisions of "Cloud Configuration for the M2MBridge"

From AMTech WikiDocs
Jump to: navigation, search
Line 7: Line 7:
 
** Configure the topic that m2mBridge will listen for CRUD and command observations, CRUD and command topic must be unique to an user configuration.(See [[Activities#Observation production configuration|Observation production configuration]] [[Sensor's network#Topics|Topics]])
 
** Configure the topic that m2mBridge will listen for CRUD and command observations, CRUD and command topic must be unique to an user configuration.(See [[Activities#Observation production configuration|Observation production configuration]] [[Sensor's network#Topics|Topics]])
 
***When the bridge starts the m2mBridgw and the things linked to it by property '''bridgeInstances''' will be cloned and own by the user id assigned to the M2MBridge. (See [[Access control#Actors|Actors]])
 
***When the bridge starts the m2mBridgw and the things linked to it by property '''bridgeInstances''' will be cloned and own by the user id assigned to the M2MBridge. (See [[Access control#Actors|Actors]])
;This configuration ensures centralized management and auto-discovering.   
+
;This way of managing configuration ensures centralized management and auto-discovering.   
 
* Create an actor actorX with [[Access_control#Policies|polices]] required by the bridge instances (See [[Access control#Actors|Actors]])
 
* Create an actor actorX with [[Access_control#Policies|polices]] required by the bridge instances (See [[Access control#Actors|Actors]])
 
** Add the polices needs by the bridge configuration
 
** Add the polices needs by the bridge configuration
*Register a follower (See [[Access control#Actors|Actors]])
+
*Register a follower (See [[Access control#Roles|Roles]])
 
** Assign to the follower actorX access  
 
** Assign to the follower actorX access  
 
*Things instance creation
 
*Things instance creation
 
**Configuring autoDiscover (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
 
**Configuring autoDiscover (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
 
***The bridge will request the DAP to clone '''templateId''' instance with the name convention '''bridgeIdPrefix''':(device mac address) from bridgeConfig.json
 
***The bridge will request the DAP to clone '''templateId''' instance with the name convention '''bridgeIdPrefix''':(device mac address) from bridgeConfig.json
***the things linked to the templateId property '''bridgeInstances''' will be cloned with the name convention bridgeIdPrefix:(device mac address):thing._name from bridgeConfig.json  
+
***The things linked to the templateId property '''bridgeInstances''' will be cloned with the name convention bridgeIdPrefix:(device mac address):thing._name from bridgeConfig.json  
***cloned instance will be giving the access control owner to the follower user id of the M2MBridge.
+
***The cloned instance will be giving the access control owner to the follower user id of the M2MBridge.
 
*Monitoring M2MBridge status
 
*Monitoring M2MBridge status
 
**Create an SNMPDevice and link it to M2MBridge thing property '''bridgeInstances''' (See "/amtech/linkeddata/types/composite/entity/SNMPDevice")
 
**Create an SNMPDevice and link it to M2MBridge thing property '''bridgeInstances''' (See "/amtech/linkeddata/types/composite/entity/SNMPDevice")
 
***Configure [[Observations_production_and_consumption|m2mBridge production configuration]]
 
***Configure [[Observations_production_and_consumption|m2mBridge production configuration]]

Revision as of 19:06, 11 October 2016

  • Create an amtechM2mBridge thing (Go to "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
This way of managing configuration ensures centralized management and auto-discovering.
  • Create an actor actorX with polices required by the bridge instances (See Actors)
    • Add the polices needs by the bridge configuration
  • Register a follower (See Roles)
    • Assign to the follower actorX access
  • Things instance creation
    • Configuring autoDiscover (See Edge Configuration)
      • The bridge will request the DAP to clone templateId instance with the name convention bridgeIdPrefix:(device mac address) from bridgeConfig.json
      • The things linked to the templateId property bridgeInstances will be cloned with the name convention bridgeIdPrefix:(device mac address):thing._name from bridgeConfig.json
      • The cloned instance will be giving the access control owner to the follower user id of the M2MBridge.
  • Monitoring M2MBridge status
    • Create an SNMPDevice and link it to M2MBridge thing property bridgeInstances (See "/amtech/linkeddata/types/composite/entity/SNMPDevice")