IBM Enterprise Content Management System Monitor Interim Fix ESM_5.5.2-000-002

Incident of the Port Reachable probe showed a timeout of zero milliseconds as January 1st, 1970 00:00:00 UTC. This is now fixed and zero is shown as the correct value.

Setting the languages in the browser setting to a language code alone, e.g. "en" or "de", but not setting the country code, e.g. "English (United States Of America)" or "Deutschland" prevented the web-UI from loading. Now the web-UI will be loaded correctly.

Security fix: It is now possible to turn the H2’s web server off by not setting its port in the installer. This works also while updating the product not only new installations.

A memory leak in the web ui was fixed. This memory leak could be triggered by repeatedly switching between the Situations and the Task Portlets icon on the outer most left side of the Monitoring view.

Filtering of samples on the Agent side works now reliable and can be configured through the Web-UI.

Selecting a task type and clicking on the add (plus) button now correctly opens the task editor for the selected type.

Exporting of incidents to slack works now.

Cumulative security fixes for (IBM Java 8) JREs included in the ESM 5.5 product line.

Some cepest based probes unnecessarily used an internal locking mechanism to prevent parallel runs of the same probe. This could led to errors if the probe’s execution time took too long compared to the schedule. These probes are no longer utilizing the internal locking mechanism.

Monitoring of rotating logfiles no longer unexpectedly stops. The monitoring of so called rotating or rolling logfiles stopped unexpectedly in cases where the logfile to monitor has got a new reference handle (aka I-node) in the file system when "rolling" occurred.

Fixed context root prevented access to webconsole e.g. via Ingres in AWS.

Security scans of the MQTT port of the server via OpenVAS no longer leads to high CPU loads.

Continuous update of all portlets works now reliable even after switching between "Monitoring" and "Configuration" back and forth.

All details of an agent shown in the sidebar below the list of agents are updated if the status of the corresponding agent changes.

New installations no longer use non-standard ports for HTTP and HTTPS for the web-ui.

The problems with the automatic start after the installation no longer exists. The issue was removed from the list of knonw limitations.

The probes Icc4SapArchiveStatus and Icc4SapServerStatus failed on UNIX and Linux systems due to an incorrect directory name. This has been fixed.

Icc4SapArchiveStatus probe no longer fails when authentication type is selected or more than one archive is defined in the INI file.

Icc4SapProcess situation no longer fails with the error message The following processes do not have the specified number of instances […​].

The WMI probe no longer triggers core dumps on agents.

The ICN plug-in now filterts the incidents by the selected situation group.

The limitation of columns in the monitoring dashboad does no longer exist.

The return value of the MSSQL Processes Probe was always 0. The correct return value was only shown in the message field. This is now fixed. The probe returns 0 (zero) and 1 (one) accordingly to measured state’s of the MS SQL processes.

All server’s and the agent’s TLS based communication now uses only Diffie-Hellman (DH) keys sizes bigger or equal to 2048. Shorter key lengths are no longer supported. So e.g. agents prior to this fix will not be able to connect to the server after it was updated. All agents must be updated, too, to allow them to reconnect to the server. This fix can also have effects on HTTPS based communications. It can also have an effect on the overall performance while starting the server. If you want to downgrade to a key length of 1024 after the update, you can edit the JVM property " jdk.tls.ephemeralDHKeySize" in karaf/etc/system.properties. After a change of this property, the server has to be restarted to apply the change to the JVM.

Microsoft Internet Explorer 11 only: Sometimes a tag element in the search dialog of the situation group list dispeared. Only manual refresh of the GUI showed the tag again. This behaviour is now fixed. The shown tags are stable now.

The incident list for a situation can now correctly be sorted by timestamp.

Listing or saving reports could lead to rest errors like "Server could not perform requested action". This could only be fixed by upgrading a third-party library.

The Listener probes have now access to all counters reported by the Listener API, especially the raw counters and accumulators and their statistics data.

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

All probes for subsystems of type eDiscovery received a wrong number of arguments. This has been fixed.

The probes ContentNavigatorPingPageStatus and SyncServerPingPageStatus failed for ICN subsystems that contained a URL without port. This has been fixed.

The DB2Statistics probe now works for DB2 installations that use other languages than English.

The DB2Statistics probe failed because the GSK Kit was missing from the search path.

To streamline the LDAP configuration and to prevent confusion, the configuration settings were split of in two sections. A standard fields section, which is shown immediately after the LDAP configuration editor is opened and an experts settings section, which is hidden beneath an expert settings button in the configuration editor.

Security fix to prevent Cross-Site Request Forgery (CSRF) attacks to succeed.

Creating line charts could lead to a NoSuchMethodError and would prevent generating such reports at all. This could only be fixed by upgrading to a newer charting library version.

Sorting the history view of incidents by clicking on the "value" column is no longer broken.

The format file for the P8 server error logfiles did not parse entries correctly if they ended with a Java exception. This has been fixed.

Some existing Knowledgebase entries did not show up in the details view of an incident although they should. Now this is corrected and these entries are also shown. Mostly the descriptions for P8 server error log entires were affected by this issue.

Lists in the sidebar and portlets scrolled spontaneously to the top if there are automatic refreshes or updates in the UI. This is no longer the case if one has scrolled down.

Datacap Pages Queued Probe can now create more than one sample if needed. So the probe will return samples in such a case instead of returning none and failing silently.

Invalid hostnames in the SNMP configuration no longer generate very technical exceptions, but understandable and helpful error messages.

The probes Icc4SapArchiveStatus and Icc4SapServerStatus failed on UNIX and Linux systems due to an incorrect directory name. This has been fixed.

Datacap probes are now working properly with Oracle.

Icc4SapArchiveStatus probe no longer fails when authentication type is selected or more than one archive is defined in the INI file.

Icc4SapProcess situation no longer fails with the error message The following processes do not have the specified number of instances […​].

The OracleProcesses probe had erroneously returned zero for a successful case instead of one. This is now fixed.

Microsoft Internet Explorer 11 only: Filtering a situation group by a tag resulted in an empty situation list. This is now fixed. The filter works as expected and shows all situations that match the tag used for filtering.

The communication between server and agent is now TLSv1.2 encrypted. Lower encryption protocols are no longer supported. So all agents prior to this fix will not be able to connect to the server after it was updated. All agents must be updated, too, to allow them to reconnect to the server.

It is now possible to have more than one dashboard in the GUI. Dashboards can be created, named, and deleted. Each dashboard can have a different set of portlets.

The welcome page of the product now shows a "Getting Started" section to help a new user to configure a good monitoring of his/her environment.

First probes for monitoring IBM ODM were added to the product. These probes are using the REST API of the RES server.

For MS Windows Event Log monitoring a so called flow limiting or throttling of incidents can now be defined. This is equal to the throttling of incidents for text based logfiles.

The probes Icc4SapArchiveStatus and Icc4SapServerStatus failed on UNIX and Linux systems due to an incorrect directory name. This has been fixed.

Directory traversal vulnerability in ESM 5.5. IF4 does no longer exist.

A pre-installed Java under MS Windows defining JAVA_HOME no longer interferes with the embedded Java used by ESM.

No more connection failures (ERRORCODE=-4228 SQLSTATE=null) with the newest JDBC driver for DB2 11.1.4.4. So using the older driver is no longer needed to connect to a DB2 11.1.4.4.

Optional automatic compression of the embedded database was added to the start-up procedure. For details ask your support personnel.

First probes for monitoring IBM BPM were added to the product. These probes are using the REST API.

The sidebars are now preserving their horizontal size between view changes and sessions.

After deleting an entry in the sidebar the details of the deleted item are also removed from the UI.

Closing of the details aka context view area for incidents is now possible without closing the complete view.

Situation Groups that are defined by more than one tag are now showing all relevant situations again.

New wizard to configure subsystems. The new wizard guides through the process of defining a complete set of related subsystems. For details the updated Configuration Guide.

Cumulative security update of Apache Karaf and bundles Jetty server.

Problems of Datacap probes on Oracle based system fixed.

Icc4SapArchiveStatus probe no longer fails when authentication type is selected or more than one archive is defined in the INI file.

Only relevant KnowledgeBase entries are now shown for cepest based probes with numeric values. Before this fix, all KnowledgeBase entries associated with the subsystem used by the probe were listed in the details view.

Icc4SapProcess situation no longer fails with the error message The following processes do not have the specified number of instances […​].