Apama projects
An Apama project typically manages a single Apama application. A project provides a means of keeping the application’s resources organized. In the process of developing an application with Apama Studio, you add the various resources that make up the application to the project. For example, you can include:
EPL files — These files define
monitors and associated
event types that are used by your application. EPL files have a
.mon extension.
Apama Java Monitor files — These Java source files define
monitors for Apama applications written in Java.
Apama Java Event files — These Java source files define
event types for Apama applications written in Java.
Scenario definition files — If your application uses scenarios, you specify the new scenario in Apama Studio. This adds a
scenario definition file to your project and opens the new scenario in Apama Studio’s Event Modeler editor where you specify its behavior. Scenario definition files have a
.sdf extension.
Dashboard definition files — If your application uses dashboards, you specify the new dashboard in Apama Studio. This adds a
dashboard definition file to your project and opens the new dashboard in Apama’s Dashboard Builder. Dashboard definition files have an .
rtv extension.
Bundles — These are pre-packaged collections of Apama objects.
Event files — Event files have an
.evt extension.
Block definition files — If your application uses scenarios and, in addition to the standard blocks packaged with Apama, you need to create customized blocks, you create the block in Apama Studio. This adds a
block definition file to your project. Block definition files have a
.bdf extension.
Function definition files — If your application uses scenarios and, in addition to the standard functions packaged with Apama, you need to create customized functions, you create the function in Apama Studio. This adds a
function definition file to your project. Function definition files have a
.fdf extension
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.