Apama 10.3 | Apama Documentation | Developing Apama Applications | Developing Apama Applications in Event Modeler | Overview of Using Event Modeler | Event Modeler layout
Event Modeler layout
To begin learning how to use Event Modeler, it is helpful to examine a demo scenario in Event Modeler.
Note: The Event Modeler is deprecated, and therefore the Statistical Arbitrage demo that is available from the Welcome page has been changed to use EPL streams and data views (instead of scenarios). The description below, which is based on the Statistical Arbitrage demo of a previous version, has been kept for your convenience.
The Event Modeler editor is divided into a number of areas. In the panel on the left (the Event Flow tab) click on the double-bordered oval shape marked start. Your display will now look as follows:
This is the default view. Event Modeler displays the following primary areas:
*Event Flow
*Global Rules and Local Rules
*Tabs for Variables, Blocks, Catalogs, and Functions.
At the bottom of Event Modeler, there are tabs for Event Flow and Block Wiring. When you click the Block Wiring tab, the Event Flow and Rules panels disappear and the Block Wiring tab appears.
During its lifetime, a scenario instance transits through a number of execution states, starting from the start state, and eventually ending at the end state (shown in the Event Flow tab). Event flows are described in About event flow states.
Each state consists of a list of rules that are executed in a particular sequence. Each has a condition that needs to be met for its embedded actions to be executed, and once those actions are complete, it can specify whether the following rules are to be processed next or the scenario should transit directly to another state. These rules appear in the Global Rules and Local Rules panels. Rules are examined in How rules define scenario behavior
The Variables tab lists any variables defined in the scenario. Scenario variables are placeholders for important information that needs to be referred to and modified during the scenario's execution. They also reflect what data can be collected from the user or sent back to be displayed to the user as results or progress updates. Variables will be described in About scenario variables.
The Blocks tab lists any blocks that are being used by this scenario. Blocks are pre-packaged modules that can be imported and used within scenarios. They can accept inputs, execute some logic of their own, and generate output. Like a scenario, blocks can themselves have configuration parameters as well as input and output feeds. Blocks can also carry out specialized operations. See About blocks for details.
The Catalogs tab lists the reusable, ready packaged blocks that are available for use in this scenario. Event Modeler comes with a selection of standard blocks, and these are documented in Using Standard Blocks. Using the Catalogs tab describes usage of the Catalogs tab.
The Functions tab lists the functions that are available for use in this scenario. Event Modeler comes with a selection of standard functions, and these are documented in Using the Functions tab.
Minimize the panels that are not part of Event Modeler and then click the Block Wiring tab that appears below the Event Flow tab. The main view changes to show the Block Wiring tab. The Event Modeler display now looks like this:
This tab shows the blocks that are being used within this scenario, and whether those blocks are wired together; that is, whether the outputs of one block are acting as the inputs of another. This functionality will be described in Switching blocks. The specific functionality of all the tabs will be covered in depth in Using Event Modeler.

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.