Release Notes 4.3

Since this version the current dashboard view can be printed. Analysis results can thus also serve as a source of information outside the application. The print layout is implemented as map.apps template. This means that the print preview can be optimized by means of the still functional selectors until the desired result is available. The Questions Dashboards have been optimized for DIN A4 format printing, and we recommend the creation of dedicated print dashboards for specially formatted output.

map.apps 4 is based on the new Esri JavaScript API 4. Since this version, basic support has been provided for activity recording in Analytics, especially for activities oriented to the cards. The next version of map.apps (presumably version 4.2.1) will be able to capture map.apps 4 card events. The differentiation of 3D/2D map views can be queried in the events.

The graphical representation of a large number of events on a dashboard provides a new way of accessing information about the order in which the logged events occur. The EventStream can help to investigate the acceptance of workflows of apps optimized for a specific purpose. This feature is initially available in an experimental state, based on your experiences and wishes, further changes should be realized. Using EventStreams in a specific context may require an extended configuration of the product. Please contact us to discuss possible support services.

The date widget now allows you to specify concrete date values in order to optimize the query day to meet your analysis requirements. In conjunction with the new histogram widget, new insights into the collected data are possible. The histogram widget allows the aggregation of values to a certain time unit (e.g. number of app starts of a year aggregated on a monthly basis). This allows statements to be made about the temporal course of the recorded data.

Expectations define user-defined expectations for the server response of a monitoring job. This means that individual and very specific checks, tailored to your own service landscape, can be configured quickly and easily.

Microsoft Teams has been added as a further notification channel for monitoring.

The monitoring component now dispenses with the packaged delivery of the so-called "embedded" security.manager and instead provides an integrated authentication option for customers who have not licensed security.manager. The integrated authentication is a lightweight alternative and provides a default user ("monitor") for use. Please contact con terra Support for alternatives, if desired.

Integration with security.manager is done manually after installation, similar to the other products.

The current release now supports Apache Tomcat 9.0 in addition to Apache Tomcat 8.5, officially ending support for Apache Tomcat 7.

The current release now supports OpenJDK/OpenJRE 8 in addition to Oracle JDK/JRE 8.

By extending the monitoring by service expectations, two new tables have to be created for existing installations. Please note the SQL update scripts that are located in the folder update of the SQL directory of the installation package for monitoring.

With version 4.3.3 there is by default a more strict validation of HTTP SSL connections in place (sue to security reasons). service.monitor will deny connections to those servers which provide an untrusted, invalid or self-signed certificate. service.monitor will also send a notification once a certificate is not valid. This is also true for those (valid) certificates which are not included in the Java Virtual Machine’s keystore of your Servlet Container. Please see the documentation for importing these.

This behavior can be overridden by configuration options. See chapters Common configuration options and SSL configuration options of the installation guide.

The following list contains issues and notes known at the date of release of version 4.3 of service.monitor Analytics