Apama 10.3 | Apama Documentation | Release Notes | What's New In Apama 9.10 | Miscellaneous enhancements and changes in 9.10
Miscellaneous enhancements and changes in 9.10
*It is now possible to pass the username and password on the JDBC connection URL, rather than having to set it in EPL. To do so, you must set the special value ADBC_NULL on both the username and password parameter on the EPL side, for example, via the Connection.openDatabaseFull() action in ADBCEvents.mon.
*The new IAFStatusDataViewService provides support for publishing the status of an IAF adapter as a DataView item. It can be used to easily monitor the adapter status using Apama's Scenario Browser or to visualize the adapter status using an Apama dashboard. For more information, see DataView support.
*ApamaDoc documentation is now provided for most of Apama's public event APIs.
*By default, the ApamaDoc export wizard does not generate documentation for inner fields of a monitor. If you want to include inner fields of a monitor, run ApamaDoc in headless mode using the --includeMonitorMembers option.
*ApamaDoc now supports <code/> tags inside ApamaDoc comments.
*The correlator now logs INFO log lines if an external sender sending events in to the correlator is blocking, giving a reason as to why the queue is full. For example:
Blocked adding 23 events to context main (id=1)'s queue; context is blocked
waiting on correlator (on port 62156) which is flagged as a slow receiver
Blocked adding 2 events to context main (id=1)'s queue; context is blocked
waiting on ctx1 (id=2) which is running a plug-in
*The Java APIs now implement the AutoCloseable interface for simple cleanup using the Java try-with-resources statement, where applicable. See the API Reference for Java (Javadoc) for more information.
*The Apama work directory (APAMA_WORK) now has a lib directory which is on the PATH/LD_LIBRARY_PATH set up by the Apama Command Prompt (apama_env script). This lib directory can be used for user-supplied C++ correlator and IAF plug-ins.
*Client applications can now add user-defined status values which can be appended to the standard status messages of the correlator:
*get, set and delete actions for the user-defined status values are now available from the EPL Management interface. See the corresponding section in Using the Management interface.
*When the new -a (or --all) option is specified for the engine_watch tool, any user-defined status values are now appended to the standard status messages. See Watching correlator runtime status.
*User-defined status values are now visible over the REST API. See Managing and Monitoring over REST.
*User-defined status values can now be retrieved from the EngineClient API. See EngineClient API.
Note that the correlator status statements that appear in the log files will not have the user-defined status values, and will remain unaffected.
*The getMostBackedUpInput and getMostBackedUpQueueSize methods of the EngineStatus interface have changed meaning. They now give the most backed up, or slowest, context name and queue size across all contexts, not just public contexts, as non-public channels can subscribe to specific channels and thus receive external events.
*The Scenario Browser now hides the irrelevant sections from the main panel.
*For Scenario, the metadata section is hidden.
*For Dataview, the input section is hidden.
*For Query, the output section is hidden.
*On Linux, a Universal Messaging Docker sample is now available in the samples/docker/applications/UniversalMessaging directory of your Apama installation.
*With the previous Apama version, the correlator automatically shut down after 30 minutes when a license file could not be found. As of this version, when a license file cannot not found, Apama can be used without a time limit, but with reduced capabilities. See Running Apama without a license file.

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.