Overview

This IF provides various functional fixes for IBM Enterprise Content Management System Monitor (ESM) 5.5.9.1.

Requirements:

Requires at least a working installation of ESM 5.5.9.1.

Supersedes all previous IFs for ESM 5.5.9.1.

Certifications:

None.
Tip

For tips and tricks regarding the configuration and maintenance of IBM Enterprise Content Management System Monitor please check the CENIT Field Guides at IBM ESM Field Guides.

The updated documentation can be downloaded from the IBM download pages.

Installation Steps

New installation

The installer of this FP/IF cannot be used for a fresh installation.

Before

  • Check if there is an installer.properties file in the same directory where the installer binary was copied to.

    • If so, remove this file from the directory before starting the installer.

  • Proceed as described in the Install Guide of the ESM.

Server

  • Proceed as described in the Install Guide of the ESM.

  • Due to a 3rd-party limitation whitespaces in the installation path are currently not supported under Unix/Linux.

  • If you want to import e.g. the configuration from an existing server into the new server, you must upgrade the existing server to the same version as the new one.

Agent

  • Proceed as described in the Install Guide of the ESM.

  • Due to a 3rd-party limitation whitespaces in the installation path are currently not supported under Unix/Linux.

After

  • No further special actions must be taken directly after the installation has ended.

When updating an existing installation

Before updating make sure you have made a backup of your current installation.

Note

If you have a scanner tool that checks the file system, it may be necessary to manually remove older log4j2 JAR files. These are no longer used by the software, but also not removed by the update process at this time. For server and agent the files are below <installation dir>/karaf/system/org/ops4j/pax/logging/pax-logging-log4j2/. You can remove all files and directories with the lowest version number.

It is possible though, your scanner will find an older log4j or log4j2 JAR file after you have deployed older external API JARs. But this is not a fault of ESM. Keep in mind to update these external JARs if necessary.
Note

We strongly advise against changing an agent’s identifier (aka name) with an update. If there is the need to rename an agent, please remove it and reinstall it again later.

If an agent’s identifier is changed with an update, that agent will be handled as a new agent by the server. You must then manually switch the probe assignments to that new agent if you want to use the situations that were deployed to the agent before the update and renaming took place. Also keep in mind, the automatic base monitoring deployment will be executed for that new agent if it was not disabled in the server’s settings.
Note

You can export your configuration and later import it again from a subtopic in the Administration view. But that import is only possible from a file exported from the same product version!

This step is necessary if you are planning to switch the storage type of the H2 database from the default MV mode to the PR mode. You must then export the configuration after the update and before switching the database type.

For details, see the section about database corruptions below.
Note

Debug and logging settings like e.g. plusdebug directories from older versions will be removed by an update.
Note

If you have deployed probes that are no longer available or have been renamed, e.g. for ImageServices, it may be necessary to execute the following steps for the agents these probes were deployed to after the agent has been updated:

  1. Stop the agent.

  2. Remove the configuration database file from the agent.

  3. Restart the agent again.

The list of renamed and removed probes can be found in the readme file and the release notes document.

Before

  • It is not recommended to mix GUI based and console mode based installations. This can lead to configuration settings erroneously enclosed with double quotes, e.g. "1883" instead of plain 1883.

  • Check if there is an installer.properties file in the same directory where the installer binary was copied to.

    • If so, remove this file from the directory before starting the installer. If not, this will damage your installation.

  • When updating from ESM 5.5.7.0-003 or older check if there are NumberOfTempFiles probes (subsystem type ContentCollector) configured.

    • If so, note down the evaluation parameters of the probe(s) as well as the parameter Logfile Path in the corresponding subsystem as these probes as well as the subsystem parameter will be removed during update due to internal changes.

    • After update, create instances of the new FileCount probe (subsystem type Host) with the parameters you noted down before the update.

  • When updating from ESM 5.5.7.0-003 or older check if there are NumberOfFilesPercentage or NumberOfFilesReached probes (subsystem type Host) configured.

    • If so, note down Maximum Number Of Files parameter. The probes will be converted to the new FileCount probe that does not have this parameter due to internal changes.

    • After update, adjust the evaluation of the NumberOfFilesPercentage and NumberOfFilesReached probes that have been migrated to FileCount probes during update, using the parameters you noted down before. This can not be done automatically during update.

  • When updating to ESM 5.5.9.0 check if there are FullTextSearchStatistics (subsystem type OnDemand) or ContentSearchServicesStatistics (subsystem type ObjectsStore) probes configured.

    • If so, check if there are instances that use thresholds in their Statistic Value field. Note down the thresholds as these will be removed during update.

    • After update, adjust the evaluation of the FullTextSearchStatistics and ContentSearchServicesStatistics probes, using the parameters you noted down before. This can not be done automatically during update.

  • When updating to ESM 5.5.9.0 check if there are Db2Statistic probes configured.

    • If so, check if there are instances that use thresholds in their Parameter To Check field. Note down the thresholds as these will be removed during update. The probes will also be converted to the new Db2DatabaseStatistic probe.

    • After update, adjust the evaluation of the Db2DatabaseStatistic probes, using the parameters you noted down before. This can not be done automatically during update.

    • Note that the valid parameters of this probe have been changed and that some old parameters are no longer available in the new implementation or have been moved to the new Db2TransactionLogStatistic probe. If an instance of Db2Statistic cannot be converted fully to the new parameter names, it will be deactivated during update.
      These parameters have been moved to Db2TransactionlogStatistic:

      • Number of indoubt transactions → NUM_INDOUBT_TRANS

      • Log space available to the database → TOTAL_LOG_AVAILABLE

      • Log space used by the database → TOTAL_LOG_USED

      • Maximum secondary log space used → SEC_LOG_USED_TOP

      • Maximum total log space used → TOT_LOG_USED_TOP

      • Secondary logs allocated currently → SEC_LOGS_ALLOCATED

      • Log pages read → LOG_READS

      • Log read time → LOG_READ_TIME

      • Log pages written → LOG_WRITES

      • Log write time → LOG_WRITE_TIME

      • Number write log IOs → NUM_LOG_WRITE_IO

      • Number read log IOs → NUM_LOG_READ_IO

      • Number partial page log IOs → NUM_LOG_PART_PAGE_IO

      • Number log buffer full → NUM_LOG_BUFFER_FULL

      • Log data found in buffer → NUM_LOG_DATA_FOUND_IN_BUFFER

      • Appl id holding the oldest transaction → APPLID_HOLDING_OLDEST_XACT

      • Log to be redone for recovery → LOG_TO_REDO_FOR_RECOVERY

      • Log accounted for by dirty pages → LOG_HELD_BY_DIRTY_PAGES

      • File number of first active log → FIRST_ACTIVE_LOG

      • File number of last active log → LAST_ACTIVE_LOG

      • File number of current active log → CURRENT_ACTIVE_LOG

      • File number of log being archived → CURRENT_ARCHIVE_LOG

      These parameters are no longer available due to technical changes:

      • Maximum agents associated with applications

      • Exclusive lock escalations

      • Total sort time

      • Data pages copied to extended storage

      • Index pages copied to extended storage

      • Data pages copied from extended storage

      • Index pages copied from extended storage

      • Physical page maps

      • Host execution elapsed time

      • Commit statements attempted commit_sql_stmts

      • Rollback statements attempted rollback_sql_stmts

      • Internal rollbacks due to deadlock int_deadlock_rollbacks

      • Package cache high water mark

      • Catalog cache high water mark

      • Shared high water mark

      • Corresponding shared overflows

      • Total shared section inserts

      • Total shared section lookups

      • Private high water mark

      • Corresponding private overflows

      • Total private section inserts

      • Total private section lookups

Server

  • We recommend to stop the ESM server.

  • Proceed with the update guided by the installer.

  • Due to a 3rd-party limitation whitespace in the installation path are currently not supported under Unix/Linux.

Agent

  • We recommend to stop the ESM agent.

  • Proceed with the update guided by the installer.

  • Due to a 3rd-party limitation whitespace in the installation path are currently not supported under Unix/Linux.

After

  • Modern browsers tend to cache data to enhance the responsiveness of web-UIs. We have found this can lead to complications after updates. Sometimes the browser does not recognize or simply ignores updates of the UI and its underlying data stores. That caching will even survive a browser restart. This all depends on the specific settings of each browser. So after an update it is recommended to explicitly clear the web browser’s caches to trigger a fresh update of the UI and its components. Normally pressing Ctrl and F5 when the focus is in the tab of the ESM’s UI should clean the cache. But we have found this is not always sufficient. That is why we recommend to use the browser’s settings to clear stored website data and the browser’s cache.

  • ISP (formerly known as TSM) CustomQuery probes that are using shell commands have to be adopted to the new Java implementation. The new implementation does not allow and though does not execute custom shell commands anymore. Instead it supports direct calculations. Read the probe’s documentation for details.

  • There is now only one ISP (formerly known as TSM) CustomQuery probe regardless if the result is numeric or alphanumeric. Existing configurations are automatically converted. But you should check these after the update.

  • The ObjectStoreNewObjects probe was rewritten to use direct SQL commands instead of the FileNet P8 Java-API, which improves the performance of the probe. This has the following implications when updating to ESM 5.5.7.0-002:

    • Objectstores that are monitored by an ObjectStoreNewObjects probe have to be added to the CPE subsystem referenced in the probe’s configuration. All these objectstores must also reference the correct database/RDBMS subsystem configurations.

    • Now only the objectstores with objectstore subsystem configurations associated to the CPE referenced in the probe’s configuration are monitored by the probe.

    • If a Custom Type is defined in a probe’s configuration, that type and the selected object type is used in the SQL query.

  • When updating from ESM 5.5.7.0-001 or older, a new option Interval In Seconds is added to all Listener subsystems. This will initially set the Listener interval to 15 minutes for all active Listener probes. See documentation for the Listener subsystem for further details.

  • When updating from ESM 5.5.7.0-001 or older, adjust the evaluation for Rmi4IiceStatus probes. The probe now returns the number of reachable connector URLs instead of simply returning 0 (ok) or 1 (not ok).

  • When updating to ESM 5.5.9.0, add instances of the FileCount probe as replacement for the NumberOfTempFiles probe as described in the Before section above.

  • When updating to ESM 5.5.9.0, the Search Pattern in all instances of the FileCount probe that have been converted from BatchItErrors probes must be changed from globbing pattern to regex.

  • When updating to ESM 5.5.9.0, check the Directory field in all instances of the FileCount probe that have been converted from NumberOfFiles, NumberOfFilesPercentage and NumberOfFilesReached probes.

    • If the Directory contains a wildcard, that part of the directory name must be moved to the Search Pattern field and be converted from globbing pattern to regex.

    • In addition, the evaluation for converted NumberOfFilesPercentage and NumberOfFilesReached probes must be adjusted as described in the Before section above.

  • When updating to ESM 5.5.9.0 it is necessary to change all relative paths in logfile subsystems to absolute paths. Relative paths are no longer supported. The entry must always be a valid regexp, see documentation for details.

Virus Scanners

We strongly advise to exclude the karaf folder of the server from virus scans and from access by other external programs that potentially can lead to file locks. This can lead to database corruption.

Microsoft Windows Server Core

ESM does not support an installation on Microsoft Windows Server Core, neither for the server nor for the agent component. You have to use an installation with the so called Desktop Experience. For details see the Microsoft webpages.

Database Corruption with H2

The following is only for the server not the agent.

Important

Keep in mind that H2 is not supported in productive environments. See the chapter about platform support in this document for a list of databases supported in production.
Note

We have reports that under some circumstances the embedded database of the server has gone corrupt beyond repair. It looks that especially the configuration database is affected by this issue.

Follow the instructions below to avoid this risk. Read them carefully and if in doubt ask your support representative for help.
Important

Before switching the database mode of the H2 database you should export the configuration to a file, from which you can later re-import it. Changing the storage mode will wipe-out the complete content of the database. So you will need the export to be able to restore your configuration after the change was applied.

The export is made through a function in the Administration view, see the documentation for details.

Only imports from the same product version are possible!

The migration of the monitoring data is not described here. Changing the storage mode of the monitoring database without a proper migration will wipe-out all monitoring data from the database.

Changing the storage mode is done by changing the JDBC-URL of the datasources defined in the server’s configuration org.ops4j.datasource-phoenix.cfg which can be found below <server install dir>/karaf/etc/.

Procedure

  1. Login as admin user and export the configuration.

  2. Stop the ESM server.

  3. Open the file org.ops4j.datasource-phoenix.cfg with a text editor.

  4. Search for the line defining the JDBC URL. It should start with url=jdbc:h2:.

  5. Add ;MV_STORE=FALSE to the end of the URL.

  6. The result should look like the following for the configuration database: url=jdbc:h2:./configuration;AUTO_SERVER=TRUE;AUTO_RECONNECT=TRUE;MV_STORE=FALSE

  7. Save the changed file.

  8. Restart the server.

  9. Login as admin user and import the exported configuration.

Note

Keep in mind: The database is created anew with standard settings by the first server start after the JDBC-URL has been changed. So you have to use the default password for the admin user before importing your configuration.

How to migrate an H2 to MV_STORE=FALSE

Important

  • Keep in mind that H2 is not supported in productive environments.

  • See the chapter about platform support in the Install Guide for a list of databases supported in production.

  • Also keep in mind that you can always ask your support representative for help.
Note

As always when migrating data or applications: Make a backup before you start.

Preparation

Check if it is necessary to migrate the database at all by looking at the JDBC URL in <install dir>/karaf/etc/org.ops4j.datasource-phoenix.cfg and <install dir>/karaf/etc/org.ops4j.datasource-monitoring.cfg. If MV_STORE=FALSE is missing in the JDBC URL (property named url), then a migration is necessary. If it is not necessary obviously you can stop here. If not sure ask your support representative for help.

If a migration is necessary

  • Stop a running ESM server.

  • Copy the current database from <install dir>/karaf/ to a different directory. The configuration database is named configuration.mv.db and the monitoring database is named monitoring.mv.db.

  • Copy the H2 Jar file from <install dir>/karaf/system/com/h2database/h2/1.4.200/h2-1.4.200.jar to the directory you have copied the database files into.

For the migration execute the following in the directory you have copied the database files into.

Be sure at least a Java 8 executable can be called from the command line.

Note

In the following example the migration is shown for the monitoring database. The schema will work for the configuration database as well.

Dump the original database

A database dump is created by executing the following from the command line:

java -cp h2-1.4.200.jar org.h2.tools.Script -url jdbc:h2:./monitoring -user db -password Database1! -script backup.zip -options compression zip

This should create a file named backup.zip that contains a SQL script with all the statements needed to re-create the database and its content. How large that file will be depends on your database.

Note

User and password shown in this example are the defaults used for an H2 installation. If you have changed these in the installation process you have to use your values here of course.

Prepare the target database

You have to create the initial and empty database and a database user. This is done in an interactive session like the following:

java -cp h2-1.4.200.jar org.h2.tools.Shell

A welcome message should be shown and H2 asks you about the initial settings for the new database. At first the JDBC-URL has to be entered. It is important to use the MV_STORE=FALSE here. In the example session the new database is named newmonitoring.

Welcome to H2 Shell 1.4.200 (2019-10-14)
Exit with Ctrl+C
[Enter]   <suggested jdbc url from shell>
URL       jdbc:h2:./newmonitoring;AUTO_SERVER=TRUE;AUTO_RECONNECT=TRUE;MV_STORE=FALSE
[Enter]   org.h2.Driver
Driver
[Enter]   <default database user>
User      <use the same user name as for the old database>
Password  <use the same password as for the old database>

There is no need to enter the Driver explicitly. Simply press enter in that line. After you have entered the password you can exit the session by pressing Ctrl+C.

Migrate the data

Now you can start to import the dump created before into the new database.

java -cp h2-1.4.200.jar org.h2.tools.RunScript -url jdbc:h2:./newmonitoring -user db -password Database1! -script backup.zip -options compression zip

Like before replace the database user and password with the correct values for your database.

Use the new database in the product

The new database has to copied to <install dir>/karaf/monitoring.h2.db. Beware in this step the new database is not only copied but also renamed.

Now you have to edit the JDBC-URL used in the product at runtime. In the file <install dir>/karaf/etc/org.ops4j.datasource-monitoring.cfg (use org.ops4j.datasource-phoenix.cfg for the configuration database) add MV_STORE\=FALSE to the end of the JDBC-URL parameter url. It should look like this:

url=jdbc\:h2\:./monitoring;AUTO_SERVER\=TRUE;AUTO_RECONNECT\=TRUE;MV_STORE\=FALSE

To persist the change when updating the product you should also change the JDBC-URLs in the file <install dir>/installvariables.properties. Edit that file with a text editor and search for JDBC_URL and MONITORING_JDBC_URL. Also add MV_STORE\=FALSE to the end of the entries. Do not instert line breaks. For the monitoring database it should then look like:

MONITORING_JDBC_URL=jdbc\:h2\:./monitoring;AUTO_SERVER\=TRUE;AUTO_RECONNECT\=TRUE;MV_STORE\=FALSE

After that delete the old database file, e.g. <install dir>/karaf/monitoring.mv.db.

The migration is now completed. You can now start the ESM server again.

Maintenance (if needed)

After the ESM server has started you should check the file size of the database file(s). If the size has doubled compared to the original ones, the database has to be defragmented/compacted as it is called.

Stop the ESM server again and follow these steps:

  • On the command line go to the <install dir>/karaf folder.

  • Execute ../jre/bin/java -cp ./system/com/h2database/h2/1.4.200/h2-1.4.200.jar org.h2.tools.Shell

  • You will be prompted with the welcome message of H2 as seen before.

  • Enter jdbc:h2:./monitoring;AUTO_SERVER=TRUE;AUTO_RECONNECT=TRUE;MV_STORE=FALSE for the JDBC-URL. Again, this example is for the monitoring database.

  • Simply press enter when asked for the JDBC driver.

  • Enter user and password appropriate for you database.

  • At the H2 shell prompt enter SHUTDOWN COMPACT;. That command can take a few seconds to be executed. The command will log you out from the H2 shell at the end. It is possible you will see an error message saying Database is already closed. This can be ignored.

  • The file size of the database file should be smaller than before.

You can start the ESM again.

Known Limitations

Call # IBM APAR # Description

19310

-

Occasional mixup of database connection options when monitoring multiple CM8 systems with the same agent

In the rare case that one agent monitors more than one CM8 system, database connection options can occasionally get mixed up, leading to incidents showing up in the wrong context. This is caused by an issue in older versions of the CM8 API.

Solution

For CM8 8.6: choose different schedules for instances of the CM8 API-based probes to make sure only one probe is triggered at a time.

For CM8 8.7: update to CM8 8.7 FP1 and use the API jar files provided with that FixPack. If updating is not possible, choose different schedules for instances of the CM8 API-based probes to make sure only one probe is triggered at a time.

19281

-

Newly created elements not always immediately shown in the UI

Due to technical limitations it is possible a newly created element, e.g. an SNMP server, will not immediately shown in the UI (in the example in the sidebar).

Solution

Press F5 or Ctrl-R to reload the web-UI. The new element should then be shown as expected.

19025

-

CVE-2022-45146 for BC-FIPS

The BouncyCastle FIPS-140 provider used in the product (version 1.0.2.3) is vulnerable to CVE-2022-45146 when used with a Java version higher than 11. Currently there is no stable version available that included a fix for this CVE and is FIPS 140-2 certified. We will update the FIPS provider as soon as possible after a fix is available.

Solution

There is no workaround available at the moment. We think a workaround is also not necessary. Please read the CVE description and the Bouncy Castle webpage for details. From the information provided there, this CVE does not apply to the product as it is shipped with its own Java 11. Higher Java versions are not supported.

17976

-

HTTP ERROR 404 Not Found for 'Servlet -'

Sometimes we have seen the web UI does not start right after the installation. Instead the error "HTTP ERROR 404 Not Found" for "SERVLET: -" is presented in the browser. We suspect timing problems in the start-up process in some environments.

Solution

In most cases the web UI will start after some time and the message is replaced by the login page, please be patient on slower systems. If this is not the case, first try to refresh the page with a cleared browser cache by pressing Ctrl-F5. If that does also not fix the problem, restart the server.

17953

-

No automatic escalation of metric Incidents

The severity of Incidents with mode 'METRIC', e.g. CPU, cannot automatically be escalated. The escalation configuration will be ignored for these Incidents. The escalation works for Incidents with mode 'EVENT', e.g. logfiles.

Solution

The mode can be changed manually. We do not recommend this. But if necessary, it is possible.

17255

-

Problem when switching to an other configuration if the current configuration was changed

If a situation or subsystem configuration 'A' was opened and changed but not saved and then a different situation or subsystem 'B' is double clicked to open that configuration instead and the changes of the first configuration 'A' are discarded, the configuration of the other situation or subsystem 'B' is not shown.

Solution

Trigger a re-rendering, e.g. by toggling one of the sidebars or resize the window.

16037

-

Column header missing in newly added list portlet

After adding a new list portlet to a dashboard, the column headers are missing.

Solution

Move the portlet. After the redraw, the column headers are visible.

14840

-

Issues in the details / history view of a portlet

The following issues exist in the details aka history view for incidents: * The details section can obscure the selected incident, if the incident is in the lower part of the list. * The details section in the view is not hidden again, when simply selecting the entry for which the details are shown, again. This is not a limitation, but a necessary change, because of the implementation of the multi-select feature.

Solution

The details part can be hidden again by selecting a second entry (multi-select) or by holding down the Ctrl-key when selecting the selected incident. To see the selected incident that was obscured by the details view, one can scroll the incident list section upwards.

14827

-

Some limitations concerning accessibility keyboard short cuts

ALT-S does not work in the editors to save the content; see. workaround below. In Mozilla Firefox SHIFT-F8 does not highlight/select the drop-down list in the probe configuration editor.

Solution

Move the focus to the GUI-element (button, drop-down list, …​) and press enter or cursor down to trigger the desired functionality.

12060

-

Keystore settings are ignored by FileNet P8 probes using the FileNet API

The settings made in keystore subsystems are ignored by the FileNet P8 API. The FileNet P8 API always uses the JRE’s initial truststore that is created when the JVM boots up. That truststore is made up of the certificates stored in the file …​/jre/lib/security/cacerts alone. This affects all probes using the FileNet P8 API JAR file, but not probes accessing FileNet e.g. via HTTPS or JDBC with SSL/TLS.

Solution

Import the certificates into the cacerts file of the agent’s JRE below <agent install dir>/jre/lib/security/ and restart the agent afterwards.

Fixes and Feature list

5.5.9.1-002

Call # IBM APAR # Type Area Description

19985

-

Fix

Monitoring

All database probes now detect reliably if an existing connection has been closed by the RDBMS.

19960

-

Fix

Cross-Cutting-Concerns

If your browser’s language settings for web pages were set to Japanese, the web UI missed some if not all (english) texts and labels. This is no longer the case. But keep in mind, the web UI still is available in english only.

19958

-

Fix

Monitoring

Forwarding monitoring data into Grafana works now again as expected. So, metrics are now updated regularly and charts can be plotted again.

19954

PJ47057

Fix

Installation

Cumulative security update of the IBM Java 11 JRE included in 5.5.9.1.

19950

-

Fix

Administration

Max reports Per Report Configuration parameter in server settings allowed negative values. This is now fixed.

19949

-

Fix

Reporting

Scheduled reports are no longer executed twice after the server has been restarted.

19930

-

Fix

Monitoring

After some time with SQL Server as the main database, the server stopped processing incoming samples with a queue full error (exception in the log). For now a workaround was implemented to mitigate this issue. There will still be canceled tasks reported in the log. But the server will be able to process incoming samples as expected.

19922

-

Fix

Monitoring

A bug was fixed in the new ServiceManagerStatus probe that prevents monitoring of more than one service at a time with a single probe. Now for every service deteced/configured a separate sample/incident is created.

5.5.9.1-001

Call # IBM APAR # Type Area Description

19905

-

Fix

Monitoring

Older but still active Incidents are no longer moving out of sight over time in portlets.

19369

-

Fix

Monitoring

The configuration of the MkfDatabaseAvailability probe and all Mkf*Blocks probes has been changed. Instead of specifying a list of databases, the configuration now specifies which MKF databases to skip.

19360

-

Fix

Security

Automatic logout after a specific time span of inactivity works now. The time span can be defined in minutes in the server settings. The default is no automatic logout. Changes in these settings do not affect existing sessions. You have to logout and login again after the settings have been changed.

19353

-

Fix

Monitoring

In some cases, the probe ContentNavigatorPingPageStatus returned an HTTP code 411 due to a missing Content-Length header. This has been fixed.

19323

-

Fix

Cross-Cutting-Concerns

Cumulative security update: Apache Karaf was updated to 4.4.3.

19322

-

Fix

Installation

Artemis-server was updated to include fixes for GHSA-cv6r-h2fm-pvrp.

19321

-

Fix

Installation

woodstox-core, jsoup, and jackson were updated to include security fixes for GHSA-3f7h-mf4q-vrm4, GHSA-gp7f-rwcx-9369, CVE-2022-36033, CVE-2022-41854, CVE-2022-38752, GHSA-jjjh-jjxp-wpff, and GHSA-rgv9-q543-rqg4.

19308

-

Fix

Monitoring

The Scope dropdown in the WorkpackagesPerProcess probe configuration showed superfluous entries. This has been fixed.

19306

-

Fix

Monitoring

The documentation of the CM8 API integration no longer states that API-based monitoring of CM8 8.6 requires jar files from CM8 8.7. Instead, the jars from CM8 8.6.0.5 are sufficient.

19305

-

Fix

Monitoring

On Windows, the file <KARAF_HOME>/data/log/dklog.log was not created even if logging for the CM8 API was enabled. This has been fixed.

In addition, cmblogconfig.properties is now checked for changes every 5 minutes to enable adjustment of the CM8 logging settings without agent restart.

19302

-

Fix

Monitoring

Cenit ServiceManager can now be monitored. A probe to check the status of the configured services was implemented.

19274

-

Fix

Monitoring

The known limitation concerning deep copies of subsystems that led to no copying deeply nested items no longer exists. For all items a deep copy will create opied items.

12159

-

Fix

Monitoring

Installation: If the service should not be started at system start-up on MS Windows a service will be installed with start-up type "manual". This was requested by customers. On Unix and Linux still no service will be installed at all. Caveat when changing the start-up type of an existing service while updating the product, the service will always be re-installed.

5.5.9.1

Call # IBM APAR # Type Area Description

19284

-

Enh

Monitoring

Netty component updated to fix CVE-2022-41881 and CVE-2022-41915.

19283

-

Fix

Monitoring

The ContentSearchServicesStatus and FullTextSearchServerStatus probe now use the service’s display name instead of its internal for the service discovery.

19280

-

Fix

Administration

Like documented the role 'user' now actually allows saving of existing but edited situations.

19279

-

Fix

Administration

The role 'guest' falsely allowed the creation of sample filters. It also falsely allowed changes of the server configuration and looking into the audit log. All this is now no longer possible.

19273

-

Enh

Monitoring

Automation mode always now fires for Incident updates, too.

19270

-

Enh

Monitoring

ContentNavigatorActiveStatus probe now supports ICN 3.0.12, too.

19032

-

Enh

Monitoring

New CM8 probes for the monitoring of document routing have been added. These probes use the CM8 API. The probes are:

  • WorknodeLoadPercentage - check current load against overload limit

  • WorkpackagesPerWorklist - count work packages based on worklists

  • WorkpackagesPerProcess - count work packages based on processes, work nodes, and item types

  • CustomQueryCount - count matches for custom query

19028

-

Enh

Monitoring

Change in the column width for the incident update counter in the incident history table. The icon was removed and initially there is enough space for at least four to five digits.

18072

PJ46944

Enh

Installation

Cumulative security update of the Java 11 JRE included in 5.5.9.

18071

-

Fix

Monitoring

When a situation or probe was deleted not all related tags where deleted, too. This issue has been fixed.

18066

-

Fix

Monitoring

Deleting a subsystem hierarchy removed elements although they were referenced in other hierarchies as well. This is now fixed.

18052

-

Enh

Monitoring

SyncServerPingPage now works with on-premise and cloud installations.

18045

-

Enh

Cross-Cutting-Concerns

Cumulative security update: Apache Karaf was updated to 4.4.2.

18044

-

Enh

Cross-Cutting-Concerns

Apache Commons Text updated to 1.10.0 to provide a security fix for CVE-2022-42889.

18043

-

Enh

Monitoring

Autodiscovery of ICN deployments in OpenShitft: There is a task for automatically creating an ICN subsystem for Content Navigator deployments in an OpenShift environment.

18031

-

Fix

Monitoring

Objectstore names used in the configuration of the ObjectstoreCustomQueryCount probe are now always used as complete names when searching for objectstores. So only exact machtes will be used. Before this fix, substring matches were also valid. E.g. before this fix BASE would match BASE, BASEOS, BASEFOO and so on. Now only BASE will match.

18028

-

Fix

Monitoring

ContentNavigatorPingPage: Credentials are no longer provided in the URL.

18023

-

Enh

Monitoring

New probe for IBM Datacap: 'BatchCounterProbe' counts the number of specific batch jobs. See the probe’s documentation for details and configurable parameters.

18022

-

Enh

Monitoring

New probe for IBM Datacap: 'ScanClientWebserviceBatchesCounterProbe' counts the number of waiting batches whose upload was initialized by the Scan Client web service. See the probe’s documentation for details an configurable parameters.

18014

-

Enh

Monitoring

New Datacap probe to report the memory consumption of the fingerprint service as provided by SOAP. See documentation of "FpServiceMemoryConsumptionProbe" for details.

18013

-

Fix

Monitoring

The error field is now updated for consecutive incidents with different content in the error sample of the same probe.

18012

-

Fix

Monitoring

The LibraryServer subsystem can now reference Keystore subsystems. This is necessary to monitor https-based Resource Managers with the ResourceManagerWebStatus probe. In the past you had to use an unrelated Keystore subsytem from the same host.

18011

-

Enh

Monitoring

New Datacap probe to report the availability of the fingerprint’s SOAP service. See documentation of "FpServiceAvailableProbe" for details.

18009

-

Enh

Administration

It is now possible to define an Azure mail service to send emails in Azure via the sendMail resource.

18008

-

Fix

Tasks

Automation mode "First" now works again as expected. It was broken in 5.5.9.0.

18001

-

Fix

Monitoring

The CPU- and the MemoryUsagePerProcess probes created two samples if an aggregation was defined and no matching process was found. This was fixed. Only one sample is now created. That sample informs the user about the non-existent process in its message and has a value of zero.

17932

-

Enh

Installation

Agent updates via the UI are now possible again. Keep in mind the standard policy for updating different product versions is valid here, too. So with 5.5.9.1 you can only update 5.5.9.0 agents up to and including 5.5.9.1-000.

17681

-

Enh

Monitoring

On Linux the NetworkRouting probe will first try to execute tracepath. If that fails it will try to execute traceroute. Only if that does also fail an error sample is created. Before 5.5.9.1 only tracepath was used.

7139

-

Enh

Monitoring

A field for a custom URL has been added to allow probes to override the base URL specified in their subsystem. The following probes have been changed:

  • CaseManagerCaseStatus , CaseManagerPingPageStatus, CaseManagerSolutionStatus, CaseManagerTaskStatus

  • ContentNavigatorActiveStatus, ContentNavigatorPingPageStatus, SyncServerPingPageStatus

  • CeEngineStatus, CeHealthPageStatus, CeWebServicesStatus, ContentSearchServicesFTSPerformance, ObjectstoreCustomQueryCount, ObjectstoreCustomQuery, ObjectstoreDocumentIndexingErrors, ObjectstoreLoadDocumentPerformance, ObjectstorePerformance, ObjectstoreRecoveryBin, PeLoadStatus, PeLockedQueueWorkObjects, PeLockedRosterWorkObjects, PePingPageStatus, PeQueueCount, PeQueueStatistic, PeRosterCount, PeRosterStatistic, PeWebServicesStatus,

5.5.9.0

Call # IBM APAR # Type Area Description

17979

-

Fix

Usermanagement

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

17970

-

Enh

Installation

After an update to 5.5.9 the 'customshell' directory will be removed from the installation. The directory will be moved to the 'backup' directory. The 'customshell' is no longer necessary starting with 5.5.9.

17966

-

Enh

Monitoring

Agents no longer require 32-bit libraries. Agents on Windows no longer require win-bash.

17948

-

Fix

Monitoring

The CpuUsagePerProcess probe reported invalid values on Windows systems with multiple CPUs. This has been fixed.

17934

-

Enh

Installation

Updating to 5.5.9 will automatically close all Incidents. This is necessary as the Incidents in 5.5.9 are technically different from the ones of prior releases. There are now two types (modes) of Incidents: Events and Metrics. The latter one will be updated if there is no change in the severity. For that their update counter is increased and the (new) update timestamp set. Also the chart portlets are now based upon Samples not Incidents anymore. This is also true for line chart reports as well.

17681

-

Enh

Monitoring

On Linux the NetworkRouting probe will first try to execute tracepath. If that fails it will try to execute traceroute. Only if that does also fail an error sample is created. Before 5.5.9 only tracepath was used.

17666

-

Enh

Monitoring

A new probe PeWebServicesStatus has been added for the ContentPlatformEngine subsystem. All probes that still used an older mechanism for HTTP requests have been switched to a pure Java implementation. All these probes do not support NTLM authentication anymore:

  • CeEngineStatus (Subsystem ContentPlatformEngine)

  • CeHealthPageStatus (Subsystem ContentPlatformEngine)

  • CeWebServicesStatus (Subsystem ContentPlatformEngine)

  • PePingPageStatus (Subsystem ContentPlatformEngine)

  • ContentNavigatorPingPageStatus (Subsystem ContentNavigator)

  • SyncServerPingPageStatus (Subsystem ContentNavigator)

  • ResourceManagerWebStatus (Subsystem LibraryServer)

17635

-

Enh

Monitoring

The probe Db2Statistic has been replaced by the Java-based probes Db2DatabaseStatistic and Db2TransactionLogStatistic.

17622

-

Fix

Monitoring

With rolling logfiles it was possible the logfile monitoring did not switch over to the new active logfile. This has been fixed.

17604

-

Enh

Monitoring

The probes ContentSearchServicesStatistics and FullTextSearchStatistics have been converted to Java. Please note that the evaluation of existing probes must be adjusted manually if the Statistic Value parameter contained an evaluation. See ReadMe and Installation Guide for details.

17587

-

Enh

Monitoring

The CebiError and ImageImportError probe have been renamed to CebiBatchStatus and ImageImportBatchStatus respectively and are now implemented in Java. Both probes now send one sample per batch with errors. The CebiStatistics and ImageImportStatistics probes have been converted to Java as well.

17586

-

Enh

Cross-Cutting-Concerns

The Eclipse Paho MQTT client used in the product was replaced by HiveMQ for stability and performance reasons.

17577

-

Fix

Monitoring

Shared evaluations can now be used again as expected.

17568

-

Fix

Monitoring

The editors are no longer falsely detecting a change when initially opened.

17567

-

Enh

Tasks

The tasks Cebi Start and Cebi Stop have been converted to Java.

17525

-

Enh

Tasks

The tasks OnDemand Start and OnDemand Stop have been renamed to OnDemand Start Library Server and OnDemand Stop Library Server and have been converted to Java. The new tasks OnDemand Start Object Server and OnDemand Stop Object Server have been added.

17515

-

Enh

Monitoring

The Icc4SapServerStatus probe has been converted to Java.

17463

-

Enh

Monitoring

New timestamp columns in the list portlets: Timestamp created and updates is now shown. Initially the sorting is done by severity (worst at top) then by the created timestamp (oldest first!). Sorting can changed by clicking on the respective column header. The sorting order is persisted.

17460

-

Enh

Monitoring

Aggregation reports and reports showing line charts do now use values from samples as their basis.

17452

-

Enh

Monitoring

In all samples the source field is now set to be unique for each sample of one probe run. It identifies now the source of the data (value, message), e.g. a specific logfile. Exception: All error samples.

17443

-

Enh

Monitoring

New FileNet P8 synthetic check probe ContentSearchServicesFTSPerformance to measure the time used for a CSS full text search in a specific document.

17442

-

Enh

Monitoring

New synthetic check probe CeObjectstoreLoadDocumentPerformance to measure document load time for FileNet P8.

17438

-

Enh

Monitoring

The OnDemandSyslogErrors probe was extended into a general OnDemand syslog probe. The new implementation can check all types of relevant states reported in the OnDemand system log. The result is a count of matching entries.

17437

-

Enh

Monitoring

New probe to check the IBM Content Navigator active status via the API introduced in IBM Content Navigator 3.0.11. The probe checks the state of your IBM Content Navigator without logging in. This probe will only work with IBM Content Navigator 3.0.11 and newer.

17436

-

Enh

Monitoring

The graph portlets are now visualizing sample values and no longer values of incidents. So the graph shows the raw sampling data created by the probes.

17431

-

Enh

Monitoring

The OnDemandPingOkay probe has been renamed to OnDemandPingStatus and is now implemented in Java. The OnDemandPingTime probe has been converted to Java as well.

17418

-

Enh

Monitoring

The CenteraStatus probe has been converted to Java.

17369

-

Enh

Monitoring

The following probes for the Host subsystem have been converted to Java implementations. * NetworkPing (The functionality of the PingPeriod probe has been merged into the NetworkPing probe.) * NetworkResolution * NetworkRouting * PortCheck

17364

-

Enh

Monitoring

The GenericPingPage probe has been removed from the Website subsystem.

17363

-

Enh

Monitoring

The creation and update of Incidents has changed fundamentally.

17305

-

Enh

Monitoring

The following probes have been converted to Java implementations:

  • MssqlProcesses (Database)

  • OracleProcesses (Database)

  • CebiProcesses (Cebi)

  • ImageImportProcesses (ImageImport)

  • NetSearchExtenderProcesses (LibraryServer)

  • ContentSearchServicesServerStatus (ObjectStore)

  • FullTextSearchServerStatus (OnDemand)

  • OnDemandServiceStatus (OnDemand)

17297

-

Enh

Monitoring

CaseAnalyzer monitoring is no longer supported.

17296

-

Enh

Monitoring

ComponentManager monitoring is no longer supported.

17283

-

Enh

Installation

Linux on POWER aka Linux-PPC or Linux-ppc64 is no longer supported. If on POWER we recommend to use IBM AIX (Server and Agent). You can also move to Linux on x86_64 (Server and Agent) or to Linux on s390x (Agent only!).

17281

-

Enh

Monitoring

Globbing patterns in configurations were replaced by regular expressions. Globbing patterns are no longer supported in e.g. file paths for log files. Regular expressions have to be used instead.

17279

-

Enh

Monitoring

Heatmap portlets for situations will now also show the newest value not only the severity icon.

17276

-

Enh

Monitoring

The probes BatchIT_Errors, NumberOfFiles, NumberOfFilesPercentage and NumberOfFilesReached have been consolidated into the Java-based probe FileCount. Existing situations based on these probes will be migrated during update as far as possible. Please note that the evaluation of former NumberOfFilesPercentage and NumberOfFilesReached probes must be adjusted manually. See ReadMe and Installation Guide for details.

The probe NumberOfTempFiles for the ContentCollector subsystem has been removed. It can be replaced by the FileCount probe as well.

15983

-

Enh

Monitoring

eDiscovery monitoring is no longer supported.

7139

-

Enh

Monitoring

A field for a custom URL has been added to allow probes to override the base URL specified in their subsystem. The following probes have been changed: * CaseManagerCaseStatus , CaseManagerPingPageStatus, CaseManagerSolutionStatus, CaseManagerTaskStatus * ContentNavigatorActiveStatus, ContentNavigatorPingPageStatus, SyncServerPingPageStatus * CeEngineStatus, CeHealthPageStatus, CeWebServicesStatus, ContentSearchServicesFTSPerformance, ObjectstoreCustomQueryCount, ObjectstoreCustomQuery, ObjectstoreDocumentIndexingErrors, ObjectstoreLoadDocumentPerformance, ObjectstorePerformance, ObjectstoreRecoveryBin, PeLoadStatus, PeLockedQueueWorkObjects, PeLockedRosterWorkObjects, PePingPageStatus, PeQueueCount, PeQueueStatistic, PeRosterCount, PeRosterStatistic, PeWebServicesStatus,

5690

-

Fix

Monitoring

The PortReachable probe now returns 1 if the port is reachable and 0 if it is not.

5666

-

Fix

Installation

On AIX the service wrapper failed to start with Java 11. This has been fixed internally circumventing a known issue in Apache Karaf https://issues.apache.org/jira/browse/KARAF-6439 originating from an issue in OpenJ9 https://github.com/adoptium/adoptium-support/issues/303.

1726

-

Enh

Monitoring

The maximum number of portlets for each dashboard has been doubled.

Details on features

Introduced in ESM 5.5.9.1-002

ESM 5.5.9.1-002 did not introduce any new features.

Introduced in ESM 5.5.9.1-001

ESM 5.5.9.1-001 did not introduce any new features.

Introduced in ESM 5.5.9.1

  • Netty component updated to fix CVE-2022-41881 and CVE-2022-41915.

  • Automation mode always now fires for Incident updates, too.

  • ContentNavigatorActiveStatus probe now supports ICN 3.0.12, too.

  • New CM8 probes for the monitoring of document routing have been added. These probes use the CM8 API. The probes are:

  • WorknodeLoadPercentage - check current load against overload limit

  • WorkpackagesPerWorklist - count work packages based on worklists

  • WorkpackagesPerProcess - count work packages based on processes, work nodes, and item types

  • CustomQueryCount - count matches for custom query

  • Change in the column width for the incident update counter in the incident history table. The icon was removed and initially there is enough space for at least four to five digits.

  • Cumulative security update of the Java 11 JRE included in 5.5.9.

  • SyncServerPingPage now works with on-premise and cloud installations.

  • Cumulative security update: Apache Karaf was updated to 4.4.2.

  • Apache Commons Text updated to 1.10.0 to provide a security fix for CVE-2022-42889.

  • Autodiscovery of ICN deployments in OpenShitft: There is a task for automatically creating an ICN subsystem for Content Navigator deployments in an OpenShift environment.

  • New probe for IBM Datacap: 'BatchCounterProbe' counts the number of specific batch jobs. See the probe’s documentation for details and configurable parameters.

  • New probe for IBM Datacap: 'ScanClientWebserviceBatchesCounterProbe' counts the number of waiting batches whose upload was initialized by the Scan Client web service. See the probe’s documentation for details an configurable parameters.

  • New Datacap probe to report the memory consumption of the fingerprint service as provided by SOAP. See documentation of "FpServiceMemoryConsumptionProbe" for details.

  • New Datacap probe to report the availability of the fingerprint’s SOAP service. See documentation of "FpServiceAvailableProbe" for details.

  • It is now possible to define an Azure mail service to send emails in Azure via the sendMail resource.

  • Agent updates via the UI are now possible again. Keep in mind the standard policy for updating different product versions is valid here, too. So with 5.5.9.1 you can only update 5.5.9.0 agents up to and including 5.5.9.1-000.

  • On Linux the NetworkRouting probe will first try to execute tracepath. If that fails it will try to execute traceroute. Only if that does also fail an error sample is created. Before 5.5.9.1 only tracepath was used.

  • A field for a custom URL has been added to allow probes to override the base URL specified in their subsystem. The following probes have been changed:

  • CaseManagerCaseStatus , CaseManagerPingPageStatus, CaseManagerSolutionStatus, CaseManagerTaskStatus

  • ContentNavigatorActiveStatus, ContentNavigatorPingPageStatus, SyncServerPingPageStatus

  • CeEngineStatus, CeHealthPageStatus, CeWebServicesStatus, ContentSearchServicesFTSPerformance, ObjectstoreCustomQueryCount, ObjectstoreCustomQuery, ObjectstoreDocumentIndexingErrors, ObjectstoreLoadDocumentPerformance, ObjectstorePerformance, ObjectstoreRecoveryBin, PeLoadStatus, PeLockedQueueWorkObjects, PeLockedRosterWorkObjects, PePingPageStatus, PeQueueCount, PeQueueStatistic, PeRosterCount, PeRosterStatistic, PeWebServicesStatus,

Introduced in ESM 5.5.9.0

  • After an update to 5.5.9 the 'customshell' directory will be removed from the installation. The directory will be moved to the 'backup' directory. The 'customshell' is no longer necessary starting with 5.5.9.

  • Agents no longer require 32-bit libraries. Agents on Windows no longer require win-bash.

  • Updating to 5.5.9 will automatically close all Incidents. This is necessary as the Incidents in 5.5.9 are technically different from the ones of prior releases. There are now two types (modes) of Incidents: Events and Metrics. The latter one will be updated if there is no change in the severity. For that their update counter is increased and the (new) update timestamp set. Also the chart portlets are now based upon Samples not Incidents anymore. This is also true for line chart reports as well.

  • On Linux the NetworkRouting probe will first try to execute tracepath. If that fails it will try to execute traceroute. Only if that does also fail an error sample is created. Before 5.5.9 only tracepath was used.

  • A new probe PeWebServicesStatus has been added for the ContentPlatformEngine subsystem. All probes that still used an older mechanism for HTTP requests have been switched to a pure Java implementation. All these probes do not support NTLM authentication anymore:

  • CeEngineStatus (Subsystem ContentPlatformEngine)

  • CeHealthPageStatus (Subsystem ContentPlatformEngine)

  • CeWebServicesStatus (Subsystem ContentPlatformEngine)

  • PePingPageStatus (Subsystem ContentPlatformEngine)

  • ContentNavigatorPingPageStatus (Subsystem ContentNavigator)

  • SyncServerPingPageStatus (Subsystem ContentNavigator)

  • ResourceManagerWebStatus (Subsystem LibraryServer)

  • The probe Db2Statistic has been replaced by the Java-based probes Db2DatabaseStatistic and Db2TransactionLogStatistic.

  • The probes ContentSearchServicesStatistics and FullTextSearchStatistics have been converted to Java. Please note that the evaluation of existing probes must be adjusted manually if the Statistic Value parameter contained an evaluation. See ReadMe and Installation Guide for details.

  • The CebiError and ImageImportError probe have been renamed to CebiBatchStatus and ImageImportBatchStatus respectively and are now implemented in Java. Both probes now send one sample per batch with errors. The CebiStatistics and ImageImportStatistics probes have been converted to Java as well.

  • The Eclipse Paho MQTT client used in the product was replaced by HiveMQ for stability and performance reasons.

  • The tasks Cebi Start and Cebi Stop have been converted to Java.

  • The tasks OnDemand Start and OnDemand Stop have been renamed to OnDemand Start Library Server and OnDemand Stop Library Server and have been converted to Java. The new tasks OnDemand Start Object Server and OnDemand Stop Object Server have been added.

  • The Icc4SapServerStatus probe has been converted to Java.

  • New timestamp columns in the list portlets: Timestamp created and updates is now shown. Initially the sorting is done by severity (worst at top) then by the created timestamp (oldest first!). Sorting can changed by clicking on the respective column header. The sorting order is persisted.

  • Aggregation reports and reports showing line charts do now use values from samples as their basis.

  • In all samples the source field is now set to be unique for each sample of one probe run. It identifies now the source of the data (value, message), e.g. a specific logfile. Exception: All error samples.

  • New FileNet P8 synthetic check probe ContentSearchServicesFTSPerformance to measure the time used for a CSS full text search in a specific document.

  • New synthetic check probe CeObjectstoreLoadDocumentPerformance to measure document load time for FileNet P8.

  • The OnDemandSyslogErrors probe was extended into a general OnDemand syslog probe. The new implementation can check all types of relevant states reported in the OnDemand system log. The result is a count of matching entries.

  • New probe to check the IBM Content Navigator active status via the API introduced in IBM Content Navigator 3.0.11. The probe checks the state of your IBM Content Navigator without logging in. This probe will only work with IBM Content Navigator 3.0.11 and newer.

  • The graph portlets are now visualizing sample values and no longer values of incidents. So the graph shows the raw sampling data created by the probes.

  • The OnDemandPingOkay probe has been renamed to OnDemandPingStatus and is now implemented in Java. The OnDemandPingTime probe has been converted to Java as well.

  • The CenteraStatus probe has been converted to Java.

  • The following probes for the Host subsystem have been converted to Java implementations.

  • NetworkPing (The functionality of the PingPeriod probe has been merged into the NetworkPing probe.)

  • NetworkResolution

  • NetworkRouting

  • PortCheck

  • The GenericPingPage probe has been removed from the Website subsystem.

  • The creation and update of Incidents has changed fundamentally.

  • The following probes have been converted to Java implementations:

  • MssqlProcesses (Database)

  • OracleProcesses (Database)

  • CebiProcesses (Cebi)

  • ImageImportProcesses (ImageImport)

  • NetSearchExtenderProcesses (LibraryServer)

  • ContentSearchServicesServerStatus (ObjectStore)

  • FullTextSearchServerStatus (OnDemand)

  • OnDemandServiceStatus (OnDemand)

  • CaseAnalyzer monitoring is no longer supported.

  • ComponentManager monitoring is no longer supported.

  • Linux on POWER aka Linux-PPC or Linux-ppc64 is no longer supported. If on POWER we recommend to use IBM AIX (Server and Agent). You can also move to Linux on x86_64 (Server and Agent) or to Linux on s390x (Agent only!).

  • Globbing patterns in configurations were replaced by regular expressions. Globbing patterns are no longer supported in e.g. file paths for log files. Regular expressions have to be used instead.

  • Heatmap portlets for situations will now also show the newest value not only the severity icon.

  • The probes BatchIT_Errors, NumberOfFiles, NumberOfFilesPercentage and NumberOfFilesReached have been consolidated into the Java-based probe FileCount. Existing situations based on these probes will be migrated during update as far as possible. Please note that the evaluation of former NumberOfFilesPercentage and NumberOfFilesReached probes must be adjusted manually. See ReadMe and Installation Guide for details.

The probe NumberOfTempFiles for the ContentCollector subsystem has been removed. It can be replaced by the FileCount probe as well. * eDiscovery monitoring is no longer supported. * A field for a custom URL has been added to allow probes to override the base URL specified in their subsystem. The following probes have been changed: * CaseManagerCaseStatus , CaseManagerPingPageStatus, CaseManagerSolutionStatus, CaseManagerTaskStatus * ContentNavigatorActiveStatus, ContentNavigatorPingPageStatus, SyncServerPingPageStatus * CeEngineStatus, CeHealthPageStatus, CeWebServicesStatus, ContentSearchServicesFTSPerformance, ObjectstoreCustomQueryCount, ObjectstoreCustomQuery, ObjectstoreDocumentIndexingErrors, ObjectstoreLoadDocumentPerformance, ObjectstorePerformance, ObjectstoreRecoveryBin, PeLoadStatus, PeLockedQueueWorkObjects, PeLockedRosterWorkObjects, PePingPageStatus, PeQueueCount, PeQueueStatistic, PeRosterCount, PeRosterStatistic, PeWebServicesStatus,

  • The maximum number of portlets for each dashboard has been doubled.

Created on 2023-06-15 03:54:26 UTC