Apama 10.3 | Apama Documentation | Release Notes | What's New in Apama 5.2 | Apama Studio enhancements in 5.2
Apama Studio enhancements in 5.2
Apama 5.2 adds the following enhancements to Apama Studio.
Apama Studio now uses Eclipse 4.3.
When Apama Studio starts it now collects any files in Apama's new studio\extensions folder and uses those files to add resources to the Apama Studio environment. This is useful when you want to import projects that have dependencies such as environment variables or catalogs of blocks, bundles or functions. In previous releases, when you imported projects that had such dependencies you manually added each resource before you could build the project.
See Setting up the environment before importing projects.
There are several enhancements for creating launch configurations:
*In the Run Configurations dialog, when you select the Common tab, the default selection for Save as is now Shared file with a default path of project_name\config\launch. In previous releases, Local file was selected by default.
When Shared file is selected and you click Apply to create a new launch configuration Apama Studio now creates two files and places them in the directory specified by Shared file. The names of these files have the following format and the launch configuration information is split between them:
In previous releases, creating a launch configuration generated only a .launch file, which contained Apama information but was managed by Eclipse. Now Apama manages the content of the .deploy file.
Any changes you make to the launch configuration will be reflected in the .deploy file.
*When you export an Ant launch configuration and you select Generate initialization list during launch, Apama Studio uses the .launch and .deploy files to create the deployment script. The Ant deployment script then uses .deploy file at runtime to read the injection order details.
*In the Run Configurations dialog, in the Components tab, a new Connections button is available. After you add two or more correlators, click Connections to specify connections between correlators. This has the same effect as using the engine_connect correlator utility to connect correlators.
The Ant export facility uses this connection information to create the required engine_connect tasks in the deployment script. Any engine_connect options that you specify in the Connections tab are saved in the .deploy file.
*In the Correlator Configuration dialog, the Initialization tab has been rearranged into two tabs as follows:
*The Injections tab lists the files to be injected except for event files. The files will be injected in the order in which they appear in the Injections tab. You can accept the default Automatic Ordering calculated by Apama Studio or you can select Manual Ordering to change the default order. If you change the default order then it is up to you to ensure that you specify a correct injection order. You can also de-select a file so that it is not injected in a particular launch configuration. The file remains in the project.
*The Event Files tab lists the .evt files to be injected. You can de-select a file so it is not injected in a particular launch configuration. You can select a .evt file and move it up or down in the list. The order of the files in the list on the Event Files tab is the order in which they will be injected. The default behavior is that Apama Studio lists the files in lexicographical order.
The information in the .deploy file accommodates any injection order changes you make in the Injections tab or Event Files tab of the Correlator Configuration dialog.
In Apama 5.2, EPL files are injected first and then .evt files are injected. In previous releases, EPL files and .evt files were injected in the order in which they appeared in the Initialization tab, which meant that they might be interspersed. This might cause a backward incompatibility for launch configurations created with previous releases.

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.