Using the --outputDeployDir action of the engine_deploy tool, you can now alternatively specify the name of a Zip file that is to contain the contents of the correlator deployment directory. See also Deploying a correlator.

With previous versions, when a directory containing a Software AG Designer project was specified with the engine_deploy tool, the resulting correlator deployment directory would not configure any connectivity plug-ins or any other kind of configuration. This is no longer the case. The resulting correlator deployment directory now accurately reflects the entire launch configuration, unless more than one launch configuration exists in the project in which case you have to choose a launch configuration. See also Deploying a correlator.

The YAML configuration file for the correlator now supports many new elements which correspond to command-line options of the engine_connect tool. For more information, see Setting up connections between correlators in a YAML configuration file.

To mitigate potential injection attacks against the correlator web interface, the address used to access the web interface is now, for certain URLs, validated against a list of permitted host names. By default, this corresponds to the configured IP addresses and host names of the machine on which the correlator is running and the configured correlator port. This means that for most applications this change will be transparent. If your correlator web interface is deployed behind another component or has otherwise non-standard configuration, you may need to set the new configuration option server/permittedRootURIs to include the addresses from which the correlator will be accessed. For more information, see Using the correlator web interface with non-default addresses.

If persistence is enabled, a new Persistence Status: log line is now shown in the main correlator log file when logging at INFO level. See Persistence status for detailed information on the log fields that are shown in this line.