Apama provides the DataViewService, which enables EPL (or Java) application writers to expose a view onto some of their data for easy consumption by remote client applications, such as Dashboard Builder dashboards.

The service uses two central concepts:

A DataView definition specifies a unique DataView name, a set of field names and field types (each type is one of string, float, integer, and boolean), and optionally a set of key fields.

Each DataView item is associated with a DataView definition, and specifies values for the defined fields.

Note that a DataView definition is not intended to serve as a central data structure for your application, but rather is intended merely to expose your application’s data to remote client applications.

The programming interface is defined by DataViewService_Interface.mon in the monitors directory of your Apama installation directory. It defines the API for working with DataView definitions and DataView items.

You can create DataViews in only the main context. You cannot create them in any contexts you create.

You can also use the MemoryStore to create DataViews and you can do this in any context. See Exposing in-memory or persistent data to dashboards.