Apama 10.3.1 | Apama Documentation | Using Apama with Software AG Designer | Overview of Developing Apama Applications | About Apama projects
 
About Apama projects
 
Managing project hierarchies
Editors
Outline view
Scenario Browser view
Engine Receive view
Engine Status view
Engine Information view
Console view
Problems view
Data Player Control view
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 Software AG Designer, 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.
*Query files — These files define Apama queries. Queries process only the event types that you specify. Query files have a .qry extension.
*JMon Monitor files — These Java source files define monitors for Apama applications written in Java.
*JMon Event files — These Java source files define event types for Apama applications written in Java.
*Dashboard definition files — If your application uses dashboards, you specify the new dashboard in Software AG Designer. 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.
Software AG Designer provides a variety of ways to manage and interact with the resources in your application's project.
This section briefly describes these Apama features. For more information on how to use them, see Working with Projects and Launching Projects.

Copyright © 2013-2019 | 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.