IBM Enterprise Content Management System Monitor ESM_5.5.7.0-007

Cumulative security update of the IBM Java 8 JREs that are shipped with IBM ESM 5.5.7. Due to technical reasons this update needs at least IBM ESM 5.5.7.0-003 to be installed.

Cumulative security update of the IBM Java 8 JREs that are shipped with IBM ESM 5.5.7. Due to technical reasons this update needs at least IBM ESM 5.5.7.0-003 to be installed.

Cumulative security update of the IBM Java 8 JREs that are shipped with IBM ESM 5.5.7.

Security update of embedded Jetty webserver to fix CVE-2022-2047.

A deleted standard admin user was unintentionally recreated again after a server restart. This has been fixed. The user remains deleted.

Fixed: Default mapping in the shared evaluations was broken as it referenced the initial probe configuration and not any of the other ones the evaluation is shared with.

Cumulative security update of the IBM Java 8 JRE included in the product. This interims fix can only be installed on the previous interims fix due to technical limitations.

Cumulative security and bug fix update for IBM Java 8 JRE included in the product. The Java 8 version is now 8.0.7.6 aka 8.0 SR 7 FP 6. There is no APAR for this update.

Closing/Deleting all Incidents from a filtered history view will work again and only close/delete all of the entries that are matched by the currently active filter criteria.

The replacement of a deleted SMTP server in report configurations works again.

At the start of an agent, the internal database, which is stored in files on the filesystem, is always removed if it exists. This will lead to an always up-to-date configuration sent from the server right after the first connect of the agent with the server. No stale information can be erroneously used.

The LDAP login module now uses "simple" as default value for authentication as it already was documented.

The update feature for Agents is now again accessible via the UI.

CeObjectstoreIndexingException now uses the correct Listener path ("CBR" and "value"). So there is no longer the need to monitor that path ("/USER/<objectstore>/CBR/Indexing Batch/Batch Exceptions/value") by the generic listener probe.

Minor UI issue in the automation editor fixed. The last entry in a row is now always accessible.

Deleting an item that is opened in an editor no longer triggers server errors (404 or 500). The still opened item can also be saved again. This will create a new entry.

A server that was stopped over a longer period will no longer be flooded by samples from his agents when coming online again. The old samples are discarded on the agent side if the connection to the server gets lost.

Adding or removing an STMP server will be seen in the task editor (MailExportIncident task) even if these changes were made in a different browser tab.

The TERM NEWLINE in v2-format files will now be considered by the logfile parser to detect ending of new entries. This will lead to the detection of new entries immediately when these are completed with a newline. There is no longer the necessity to wait for the next entry to be appended to the logfile to start processing the entry that was terminated by a newline.

The known limitation that the top most subsystem was not deleted when deleting subsystems no longer exists. Now all subsystem, starting with the selected one are deleted if there are no other references to these subsystems.

The probes CpuUsagePerProcess and MemoryUsagePerProcess have been converted to Java. Both probes can now send one sample per process instead of one summary sample for all processes.

Cumulative security updated of the IBM Java 8 JRE shipped with the product.

Forwarding of incidents into a Grafana based dashboard is now possible by the means of the Grafana API.

Non-english language settings in browsers will no longer lead to errors. But English is still the only supported language of the web-UI.

The RMI4IICEStatus probe now returns the number of reachable connector URLs instead of simply returning '0' (ok) or '1' (not ok).

New users will have a default dashboard right after their first login.

The following issue was fixed: Editing the settings of a dashboard as non-administrator will prevent the deletion of that dashboard. The close button (little cross on the tab) will vanish after the changes are saved.

The Javax Mail API JAR was updated for security reasons and also to fix an error concerning TLS based connections to SMTP servers.

On Linux s390x the messaging did not work. So agents could not connect to servers. This has been fixed.

All IBM Spectrum Protect probes, formerly known as IBM TSM probes, were rewritten in Java. This implies also some side effects to be beware of. Especially most of the probes are now multi sample probes, which means they can create more than one sample at each probe run. Please read the readme file and the documentation of these probes for details and further information.

Apache Karaf was updated to 4.2.15. This also includes updates of dependencies, e.g. like log4j2.

The username for logins is case insensitive. The dashboard now also handles this as expected (case insensitive).Before this fix, using a different case for a username resulted in different dashboards for each different spelling.

To enhance the performance of the ObjectStoreNewObjects probe in larger environments, it was rewritten to use direct SQL commands instead of the FileNet P8 Java API. This has some implications for existing configurations; for details please refer to the section titled "When updating existing installations" in the readme file and the Install Guide.

As a complement to the ApacheAccessLogfile probe there is now the new ApacheAccessLogAnalyzer task. The task is convenient for offline analyzation of huge Apache access logfiles or logfiles that can very rapidly grow while a probe is trying to anayze them.

DBExportIncident task: It is now possible to split defined parts of the message and source field of an incident to write these parts into different database columns. For details, see the documentation of the DBExportIncident task.

Raising memory consumption of the browser process while rolling dashboards are enabled were detected. This has been fixed.

Security enhancement: Cross Security Policy (CSP) header now set in responses.

On each start-up the monitoring of log entries (files and databases) looks at the newest entry and does no longer process older entries that occurred between the Agent’s shutdown and re-start.

Technically all bookkeeping information is erased at an Agent’s start.

HTML specific characters in text fields of samples and incidents are now always correctly displayed in the web-UI. Before the changes, there was a difference between the portlets, deatils, and tooltips.

The TSM subsystem was renamed to reflect the change in the product’s name. IBM TSM is known as IBM Spectrum Protect.

The ObjectStoreStorageAreaStatus probe can now also be used to get the amount of storage areas in the desired states not only the ones in undesired states.

It is now possible to set an interval in the Listener subsystem that controls how often the monitored application should send data.

A new task "Collect Listener Paths" has been added that collects cached Listener paths from all agents and stores them in a downloadable ZIP file.

Security fix for Log4jv2. It installs Log4jv2 2.17.1 through an update of pax logging.

Settings for escalation can now be saved again.

Autodiscovery of CPE deployments in OpenShitft: There is a task for automatically creating CPE subsystem hierarchies (CPE, ObjectStore, Database, RDBMS) for CPE deployments in an OpenShift environment.

A new probe to compare a certificate of an https connection against certificates stored in a given truststore. The existing SslCertExpiry probe has been renamed to CertificateExpiration and has been moved to the Website subsystem.

The NumberOfFiles probe showed a misleading error message on Windows. This has been fixed.

The HTTP server version is no longer included in the http response header.

The welcome page now optionally shows information about noteworthy changes and enhancements.

An administrator can pre-define dashboards for other users.

Rolling dashboards: It is now possible to define a schedule to automatically and regularly sequentially iterate through monitoring dashboards.

Opening or removing a report configuration after a situation used in that configuration was removed will no longer create an exception.

Removing report configruations with a huge amount of created reports created by these will no longer create high CPU load and Java heap dumps in the worst case.

Removing references between subsystems will no longer trigger repeated unncessary probe reconfigurations.

The severity shown in monitoring portlets is now correctly updated when incidents are closed or deleted.

Reports for situations without any data is working again. Now a report is created that says there were no incidents for the configured situation.

The standard evaluation of the NumberOfFilesReached probe ignores there are no changes in the number of files. In that case the message contains "no_change …​" and the return value is 0. That should be matched to the severity "harmless". Currently this state is handled like "not_ok", which is mapped to "fatal". The documentation now explicitly mentions this situation.

Deleting a situation that used a shared evaluation will no longer interfere with other situations referencing that same shared evaluation. Especially editing or listing these situations was not possible.

New installer. With 5.5.7 Solaris and HP-UX are no longer supported. Updates are only supported from version 5.5.5.1-001 although possible from older versions. This is due to some technical limitations of the installer.

Closed incidents can now be reopened again.

Deep copies of subsystems no longer create unnecessary copies. This known limitation is now fixed.

A change in the severity will now correctly reset the duplicate counter to zero.

New probe for detecting long running SQL-requests logged in the P8 trace log.

The MBeanWebApp no longer supports Java 6 or 7. At least a Java 8 JRE must be used for the deployed application.

On MS Windows it is now possible to update without uninstalling and reinstalling the accompanied service.

If there is a deactivated probe in a situation, the entry/icon of that situation is now grayed out in the list of situations and situation groups in the configuration view.

As announced previously the monitoring database migration tool is removed from the product.

Now it is again possible to save changes made in the sample filter editor directly from the confirmation dialog.

Starting with 5.5.7 it is now possible to restart an agent directly from the web-UI. Agent and server must be at least on version 5.5.7.

The handling of keystores on the agent has been reviewed.