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 thing (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 thing name is assigned to '''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 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]])
 +
;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]])
** Add the things type polices the bridge needs to the actor actorX
+
** Add the polices needs by the use case
 
*Register a follower (See [[Access control#Actors|Roles]])
 
*Register a follower (See [[Access control#Actors|Roles]])
** Assign to follower actor actorX access  
+
** Assign to the follower actorX access  
 
*Activity observation configuration (See [[Activities#Observation production configuration|Observation production configuration]])
 
*Activity observation configuration (See [[Activities#Observation production configuration|Observation production configuration]])
 
** Add the Things types the bridge will use (See [[Activities#Thing types|Thing types]])
 
** Add the Things types the bridge will use (See [[Activities#Thing types|Thing types]])
*** Add the observations types from selected thing type the bridge will produce or consume (See [[Sensor's network#Observations and observation types|Observations and observation types]] [[Sensor's network#Crud observation|CRUD observations]])
+
*** Add the observations types from selected things type the m2mBridge will produce or consume (See [[Sensor's network#Observations and observation types|Observations and observation types]] [[Sensor's network#Crud observation|CRUD observations]])
** Configure the topic that m2mBridge will listen for crud and command observations has to matched with others things' observation production configuration linked to this m2mBridge 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]])
 
*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 bridge that requested it.
+
***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 instance and give access to your M2MBridge actor (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")
***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.
+
***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 [[Activities#Observation production configuration|Observation production configuration]])
****This get done by setting at the observation production configuration /observationproductionconfig/SNMPDevice/observationsproducedconfig/snmpRead topic to value /m2mBridge/snmp/ (See [[Activities#Observation production configuration|Observation production configuration]])
+

Revision as of 17:12, 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, through 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)