Cloud Configuration for the M2MBridge

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 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)
• 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)

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