Service monitors
If your Apama application uses ADBC, you need to inject several required service monitors. In
Software AG Designer, this is done automatically when you add the appropriate data source adapter bundle to the application's project as described in
Configuring the Apama database connector. If you are not using
Software AG Designer to develop your application, you need to manually inject the following required service monitors in the order they are listed:
ADBCAdapterEvents.mon — Provides definitions for all events sent to or from the ADBC Adapter.
ADBCEvents.mon — Provides the public API for ADBC, implemented as actions on the following events:
Discovery — This event types defines the actions for discovering ADBC resources. It is used to find the available data sources (ODBC, JDBC, Sim, etc.) and the default databases and query templates configured for those data sources.
Connection — This event type defines actions for performing all operations on a database except those involving queries
Query — This event type defines actions for performing queries on a database.
ADBCAdapterService.mon — Provides actions for the following:
Forwarding database request events to the adapter.
Forwarding database response events to the ADBC Service API layer.
Provides support for using the ADBC event API from contexts other than the main context (see also
setPrespawnContext in
Setting context).
IAFStatusManager.mon StatusSupport.mon ADBCStatusManager.mon — Manages status subscriptions for the ADBC adapter and the application.
ADBCHelper.mon — Include this monitor for applications that use the ADBCHelper API.
The ADBC monitors and IAFStatusManager.mon are located in the adapters\monitors directory of the Apama installation. The StatusSupport.mon monitor is located in the Apama installation's monitors directory