Apama 10.3 | Apama Documentation | Developing Apama Applications | Developing Apama Applications in EPL | Making Application Data Available to Clients
Making Application Data Available to Clients
Adding the DataView Service bundle to your project
Creating DataView definitions
Deleting DataView definitions
Creating DataView items
Deleting DataView items
Updating DataView items
Looking up field positions
Using multiple correlators
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:
*DataView definition
*DataView item
A DataView definition specifies a unique DataView name, a set of field names and field types (each type is one of string, decimal, 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: The topics below briefly describe the event types that are used for managing the DataView definitions and items. For detailed information on the fields that are available for these events, see the com.apama.dataview package in the API Reference for EPL (ApamaDoc) .
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.
Metadata properties can be specified for a DataView by adding keys with the prefix DataViewDefinition.EXTRA_PARAMS_METADATA_PREFIX to the extraParams dictionary of DataViewAddDefinition when adding the new DataView definition.
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.

Copyright © 2013-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.