Difference between revisions of "Cloud Configuration for the M2MBridge"

From AMTech WikiDocs
Jump to: navigation, search
(Cloud Configuration)
(Cloud Configuration)
Line 1: Line 1:
 
== Cloud Configuration ==
 
== Cloud Configuration ==
 
*Create an amtechM2mBridge instance (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
 
*Create an amtechM2mBridge instance (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
**This instance name would be set to the templateId at bridgeConfig.json (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
+
**This instance name would be set to the '''templateId''' at bridgeConfig.json (See [[M2M Bridge#Edge Configuration|Edge Configuration]])
 
***When the bridge starts this thing instance and the instances link to '''bridgeInstances''' will be cloned ensuring centralized management of the m2mBridge and others linked things  
 
***When the bridge starts this thing instance and the instances link to '''bridgeInstances''' will be cloned ensuring centralized management of the m2mBridge and others linked things  
 
* 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]])
Line 13: Line 13:
 
*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 instances 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 bridge that requested it.
 
***cloned instance will be giving the access control owner to the follower user id of the bridge that requested it.
 
*Monitoring M2MBridge status
 
*Monitoring M2MBridge status

Revision as of 22:12, 26 April 2016

Cloud Configuration

  • Create an amtechM2mBridge instance (See "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
    • This instance name would be set to the templateId at bridgeConfig.json (See Edge Configuration)
      • When the bridge starts this thing instance and the instances link to bridgeInstances will be cloned ensuring centralized management of the m2mBridge and others linked things
  • Create an actor actorX with the polices required by the activity(s) (See Actors)
    • Add the things type polices the bridge needs to the actor actorX
  • Register a follower (See Roles)
    • Assign to follower actor 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 bridge that requested it.
  • Monitoring M2MBridge status
    • Create an SNMPDevice instance and give access to your M2MBridge actor (See "/amtech/linkeddata/types/composite/entity/SNMPDevice")
      • Send observations 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.
        • This get done by setting at the observation production configuration /observationproductionconfig/SNMPDevice/observationsproducedconfig/snmpRead topic to value /m2mBridge/snmp/ (See Observation production configuration)