We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
FIWARE.UserStory.Data.CEP.InOutEventsConnectivity.SubscribeToPubSubEvents.ContextBrokerCEPScenarioDefinition - FIWARE Forge Wiki

FIWARE.UserStory.Data.CEP.InOutEventsConnectivity.SubscribeToPubSubEvents.ContextBrokerCEPScenarioDefinition

From FIWARE Forge Wiki

Jump to: navigation, search
Name Context Broker CEP integration scenario definition
Goal Define a typical scenario that requires both the Context Broker and the CEP
Description Define a typical scenario that requires both the Context Broker and the CEP. Try to have a scenario based on specific UC input. This scenario should define the Context Broker entities, the context update messages the Context Broker gets from external application, the events defined in the CEP, the messages from the Context Broker to the CEP, the CEP patterns, the derived events the CEP generates, the way the Context Broker entities are updated by the CEP events, the messages the Context Broker sends to the external application.
Version FI-WARE.Release.2.3 Source IBM,
Scope Epic Theme
Status Closed MoSCoW priority Must Relative priority 3
Chapter Data/Context Management, Enabler CEP
Stakeholder FI-WARE, Data Chapter, SafeCity, Finest, Envirofi Owner CEP, Tali Yatzkar Haham
Complexity M Rationale


Personal tools
Create a book