Difference between revisions of "Cloud Configuration for the M2MBridge"
From AMTech WikiDocs
| Line 1: | Line 1: | ||
*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 [[M2M Bridge#Edge Configuration|Edge Configuration]]) | ||
| − | **Set the bridge production configuration by editing the template instance (See [[Observations_production_and_consumption|m2mBridge production 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'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]]) | ||
***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 configuration ensures centralized management and auto-discovering. |
| − | * Create an actor actorX with | + | * 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 | + | ** Add the polices needs by the bridge configuration |
*Register a follower (See [[Access control#Actors|Actors]]) | *Register a follower (See [[Access control#Actors|Actors]]) | ||
** 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]]) | ||
Revision as of 14:39, 4 October 2016
- Create an amtechM2mBridge thing (Go to "/amtech/linkeddata/types/composite/entity/amtechM2mBridge")
- This thing name is assigned to templateId at bridgeConfig.json (See Edge Configuration)
- Set the bridge production configuration by editing the template instance (See m2mBridge production
configuration)
- Add the Things types that produced observations (See Thing types)
- Add the observations types from selected things type the m2mBridge will produce or consume (See Observations and observation types CRUD observations)
- Add the Things types that produced observations (See Thing types)
- Configure the topic that m2mBridge will listen for CRUD and command observations, CRUD and command topic must be unique to an user configuration.(See Observation production configuration 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 Actors)
- This 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 Actors)
- 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
- cloned instance will be giving the access control owner to the follower user id of the M2MBridge.
- Configuring autoDiscover (See Edge Configuration)
- 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)
- Create an SNMPDevice and link it to M2MBridge thing property bridgeInstances (See "/amtech/linkeddata/types/composite/entity/SNMPDevice")
