Difference between revisions of "Cloud Configuration for the M2MBridge"
From AMTech WikiDocs
(→Cloud Configuration) |
(→Cloud Configuration) |
||
| Line 6: | Line 6: | ||
* 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 polices needs by the use case | ** Add the polices needs by the use case | ||
| − | *Register a follower (See [[Access control#Actors| | + | *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]]) | *Activity observation configuration (See [[Activities#Observation production configuration|Observation production configuration]]) | ||
Revision as of 18:30, 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 thing name is assigned to templateId at bridgeConfig.json (See Edge Configuration)
- This configuration ensures centralized management and auto-discovering 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 Actors)
- Assign to the follower actorX access
- Activity observation configuration (See Observation production configuration)
- Add the Things types the bridge will use (See Thing types)
- Add the observations types from selected things type the m2mBridge will produce or consume (See Observations and observation types 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 Observation production configuration Topics)
- Add the Things types the bridge will use (See Thing types)
- 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")
