Difference between revisions of "Cloud Configuration for the M2MBridge"

From AMTech WikiDocs
Jump to: navigation, search
(Cloud Configuration)
(Cloud Configuration)
Line 2: Line 2:
 
*Create an amtechM2mBridge thing (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
 
*Create an amtechM2mBridge thing (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
 
**This thing name is assigned to '''templateId''' at bridgeConfig.json (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
 
**This thing name is assigned to '''templateId''' at bridgeConfig.json (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
***When the bridge starts this thing and the things linked to it, through property '''bridgeInstances''' will be cloned and own by the user id assigned to the M2MBridge. (See [[Access control#Actors|Actors]])
+
***When the bridge starts this thing 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 configuratio ensures centralized management and clone configuration to others m2mBridge instances/deployments.   
 
;This configuratio ensures centralized management and clone configuration to others m2mBridge instances/deployments.   
 
* Create an actor actorX with the polices required by the activity(s) (See [[Access control#Actors|Actors]])
 
* Create an actor actorX with the polices required by the activity(s) (See [[Access control#Actors|Actors]])

Revision as of 18:13, 27 April 2016

Cloud Configuration

  • Create an amtechM2mBridge thing (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
    • This thing name is assigned to templateId at bridgeConfig.json (See Edge Configuration)
      • When the bridge starts this thing and the things linked to it by property bridgeInstances will be cloned and own by the user id assigned to the M2MBridge. (See Actors)
This configuratio ensures centralized management and clone configuration to others m2mBridge instances/deployments.
  • Create an actor actorX with the polices required by the activity(s) (See Actors)
    • Add the polices needs by the use case
  • Register a follower (See Roles)
    • Assign to the follower actorX access
  • Activity observation configuration (See Observation production configuration)
  • 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
      • 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")
      • Configure topic to /m2mBridge/snmp/read a core activity /amtech/activities/monitorM2MBridgeStatus will analyze the data and notify to the user and guestusers of the M2MBridge instance.(See Observation production configuration)