Apama 10.3 | Apama Documentation | Release Notes | What's New in Apama 5.1 | Miscellaneous enhancements in 5.1
Miscellaneous enhancements in 5.1
Apama 5.1 includes the following enhancements:
*Correlator Deployment Packages (CDPs) can now contain .jar files.
*In Apama Studio, you can now export a project's Web Services Client adapter configuration to an archive file. You can then import the archive file into any Apama project.
*The Apama correlator-integrated adapter for JMS now supports Software AG's Universal Messaging 9.5.2.
*In previous releases, when using the Apama correlator-integrated messaging adapter for JMS, you had to explicitly obtain and install the javax.jms.jar file. This file is now provided with Apama and installed as part of Apama installation. Manual steps are no longer required.
*In the Event Mappings tab for the correlator-integrated messaging adapter for JMS and for the Web Services Client adapter, Apama Studio now displays error markers if events that were previously mapped are missing. You must correct the event mappings before you can run the adapter.
*The com.apama.jmon.Unloadable interface has been added to JMon. For any monitor that implements this interface, the Unloadable.onUnload() method will be called when the application is being unloaded, for example, due to an engine_delete request.
*Dashboards now support the following functions. Details for using these functions are in the Dashboard Function Reference.
*Init Local Variable initializes a local variable to a specified value.
*Quick Set Sub sets a substitution string to a specified value.
*For dashboard processes, the filterInstance attribute in the apama-macros.xml file now defaults to true. This ensures that users can see only the instances that are owned by them. To change this behavior, edit the apama-macros.xml file or create the DataView instances with "*" as the owner.
*As of Apama 5.0, Apama applications running in the correlator can make use of Apama out of band notifications. Out of band notifications are events that are automatically sent to all public contexts in a correlator whenever any component (an IAF adapter, dashboard, another correlator, or a client built using the Apama SDKs) connects or disconnects from the correlator. (This was not previously listed in the Release Notes.)

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.