Understanding dashboards
A DataView is a representation of application logic, but without any defined user interaction. You add a dashboard to a DataView to enable end-users to:
Send an event to create a new DataView instance. This might include entering the initialization values for the DataView.
Monitor the status of all DataView instances. For example, to see when a pattern has been detected, and some action taken.
Manually intervene in the execution of a DataView instance. For example, to take some action in response to an alert.
Send an event to deactivate a DataView instance.
In an Apama application, a dashboard is a real-time, business cockpit for controlling and receiving real-time updates from running DataViews. Deployed dashboards connect to one or more correlators through a dashboard data server. As the DataViews in a correlator run, and their variables or fields change, the correlator sends update events to all connected dashboards. When a dashboard receives an update event, it updates its display in real time to show the behavior of the DataView. User interactions with the dashboard, such as sending an event to create an instance of a DataView, result in control events that the dashboard data server sends to the correlator.
Alternatively, you can use the MemoryStore EPL plug-in in EPL applications. The MemoryStore creates DataViews for you.