Difference between revisions of "Services"

Revision as of 20:17, 27 April 2016

When an activity is published a new resource of type service is created, representing a Software as a Service.

• This service can be public to all tenants (_ALL) or restricted to a subset of tenants, controlled by the property guesttenants. This property is defined on activity publication.
• This is the service that followers can subscribe to if they have access to it (based on the service guest tenants)
• Services can be grouped using tags to simplify the search

Validate

• Check if the requirements specified by the activity configuration have been fulfilled.
  • Types that produce observations must have instances
  • Types in observations production configuration must have Actors.
  • If the same entity type is configured to produce an observation type in more than one activity, then all the instances of that entity typemust have the disambiguation property activityForObsProduction set
  • Validate there is only one bridge instance in the tenant of the user performing the validation. It may have several bridge instances shared with him, but it must own only one
  • No empty topics
  • All configurations for producing observations of type Observationresourcecrud must have the same topic
    • sendCommand topic (because m2mBridge listens to only websocket crud and commands must be send to one topic)