Difference between revisions of "Cloud Configuration for the M2MBridge"

From AMTech WikiDocs
Jump to: navigation, search
(→‎Cloud Configuration)
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
== Cloud Configuration ==
 
 
*Create an amtechM2mBridge thing (Go to "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
 
*Create an amtechM2mBridge thing (Go to "/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 [[Edge_Configuration|Edge Configuration]])
 +
**Set the bridge production configuration by editing the template instance (See [[Observations_production_and_consumption|m2mBridge production
 +
configuration]])
 +
*** Add the Things types that produced observations (See [[Activities#Thing types|Thing types]])
 +
**** 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%27s_network#CRUD_observation|CRUD observations]])
 +
** 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 to others m2mBridge instances/deployments.   
+
;This way of managing configuration ensures centralized management and auto-discovering.   
−
* Create an actor actorX with the polices required by the activity(s) (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 use case
+
** Add the polices needs by the bridge configuration
−
;if the m2mBRidge access [[Access_control#Policies|police]] has been set to check user id each user id need to be add to the m2mBridge guest user list
+
*Register a follower (See [[Access control#Roles|Roles]])
−
*Register a follower (See [[Access control#Actors|Actors]])
+
 
** Assign to the follower actorX access  
 
** Assign to the follower actorX access  
−
*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 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, 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 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 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]])
+
***Configure [[Observations_production_and_consumption|m2mBridge production configuration]]
−
 
+
−
== Specific Cloud Configuration for beacons  ==
+
−
* Using the thing type BLEbeaconsScanner
+
−
* Create BLEBeaconsScanner instance, set properties related to the specific instance (Ex. scanEddystone)
+
−
* Create M2mBridge instance
+
−
* Add the BLEBeaconsScanner to the list of instances of the bridge
+
−
* Configure actor to give access to the bridge and beacon
+
−
* Define an activity & Configure Observation Production
+
−
* Publish activity
+
−
* Subscribe follower to the generated service. This is the follower to be used from the bridge
+

Latest revision as of 15:06, 12 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")
Retrieved from "http://wiki.amtech.mx/mediawiki/index.php?title=Cloud_Configuration_for_the_M2MBridge&oldid=2621"