The documentation has been updated with information on how to back up the persistence database using file-system snapshots while the correlator is still running. See Backing up the persistence database while the correlator is running.

The -XX:+HeapDumpOnOutOfMemoryError argument has been added to the default JVM flags for the Java process within the correlator. This means that whenever a Java OutOfMemoryError is thrown, a java_pidnumber.hprof file is created containing the Java heap. If you want to disable this new behavior, start the correlator with -J-XX:-HeapDumpOnOutOfMemoryError (with a minus sign instead of a plus sign).

In addition to using the apama_env script to set up your console environment to run Apama commands, you can also use it as a one-shot wrapper to run a single Apama command without changing your environment. For more details, see Setting up the environment using the Apama Command Prompt.

The Apama Docker images provided through Docker Hub and other container registries now include a default HEALTHCHECK instruction to monitor the status of the correlator. This will be monitored by Docker and other tooling automatically.

The documentation has been updated with information on how to provide an Apama license file to the Docker image. See Licensing Apama in Docker.

The correlator now exposes non-numeric metadata status over Prometheus. Labels for the name of the slowest context and for the name of the slowest consumer/receiver of events are now given on the sag_apama_correlator_slowest_input_queue_size_total and sag_apama_correlator_slowest_output_queue_size_total metrics. See also List of correlator status statistics. In addition, the following Prometheus metrics have been added where the labels give information about the status of the current license or about the configuration: sag_apama_correlator_licensedata and sag_apama_correlator_metadata. See also Monitoring with Prometheus.

The correlator now logs the user name of the user which it was started as in the start-up stanza of the correlator log file.

The engine_deploy tool now always generates the connectivity.yaml file for a project which contains connectivity bundles. With previous versions, this file was generated only when a deployment file was provided to the engine_deploy tool. See also Deploying a correlator.

The file client_status_names.hpp has been added to the public includes to contain constants for all standard status values within the correlator. See also List of correlator status statistics.

As of Apama 10.3.1, it is possible to uninstall service packs and fixes. To do so, run the Software AG Update Manager or Command Central, select the service pack or fix to be uninstalled, and then follow the instructions in the user interface. Keep in mind that it is not possible to uninstall service packs and fixes for Apama versions before 10.3.1. For detailed information, see Using Software AG Update Manager and Software AG Command Central Help. The most up-to-date versions of these guides are always available at http://documentation.softwareag.com/ (Empower login required).