Difference between revisions of "Activities"
From AMTech WikiDocs
(→Observation production configuration) |
(→Observation production configuration) |
||
Line 30: | Line 30: | ||
*Objective | *Objective | ||
**Identify which thing types and observation types are required by observation type. | **Identify which thing types and observation types are required by observation type. | ||
− | [[File:ObservationConfigProd1. | + | [[File:ObservationConfigProd1.png]] |
**Configure observations' properties required to produce selected observations and enforce security including topic, targetthings, producer, guestusers, and guesttenants | **Configure observations' properties required to produce selected observations and enforce security including topic, targetthings, producer, guestusers, and guesttenants |
Revision as of 11:10, 11 April 2016
Contents
Activity
Observers
Link to observer's help
Actors
- Actors are resources that define access control policies to thing and notification types
- Actors are defined for a tenant and they are not shared with other tenants (although their names must be unique accross tenants)
- Actors are associated to activities, meaning that the follower admin that subscribes to the service will adquire all those access control policies. The follower admin can then selectively give actors to the other followers he invites.
Thing types
Notification types
- Notifications are defined as types in the same way that things and observations are.
- A notification type contains well-known supported properties, such as subject and body.
- Notifications types can be used in actor's policies to define access to the instances of the notifications types
- Instances of a notification type can be generated using an action notify in a reasoner
Reasoners
example
Types of reasoners
Actions
See Actions
Observation production configuration
- Objective
- Identify which thing types and observation types are required by observation type.
- Configure observations' properties required to produce selected observations and enforce security including topic, targetthings, producer, guestusers, and guesttenants
- Placeholders
- Relation with entities observation production configuration
Validation for publication
In order to be published, an activity must be a valid json resource according to its metadata. All resources contained in the activity must also be valid for their metadata. The follower specific validations are also performed on the activity (some generate warning, others generate errors that will not allow publication)
- Types involved in reasoners, observers and actors must be published
- If there is an unpublished type that is used, and it is owned by the activity owner, a warning is generated
- If the unpublished type is owned by another user, an error is generated
- Types used in actors are involved in reasoners or observers (if not, a warning is generated)
- Actors must not contain policies for notifications of a different activity