IBM Enterprise Content Management System Monitor ESM 5.5.5-001

The Agent did not start on HP-UX, because the karaf scripts were missing the -d64 option for the IBM Java 8 JRE.

The fallback mapping is no longer skipped for multi-sample probes (e.g. WMI or CustomDatabaseQuery).

The probes OnDemandPingOkay and OnDemandPingTime are now supported on Windows.

The probes ElogFileExistence and ImageServicesSystemStatus have been converted to Java. The probe ImageServicesServerProcesses has been removed. Use the new ProcessCount (located under the Agent subsystem) probe instead which also replaces the Processes and ProcessInstances probe.

Sharing of evaluations between different situations is now possible. This will minimise the configuration effort if identical evaluation logics are used by more than one situation.

The list of incidents shown in the history (aka details view) of a situation group or a situation can now be filtered by different criteria.

Encrypted connections for the configuration and monitoring databases are supported for IBM DB2 and MS SQL Server by the standard JDBC URL properties of these databases.

Some OnDemand probes did not recognize when the logon to the OnDemand system failed and returned a sample with value 0. This has been fixed.

Some cepest probes did use the password in clear text on the command line. If technically possible this was fixed. But there are some legacy probes that are still using passwords at the command line calling external programs.

Masking of backslashes in JDBC-URLs e.g. for SQL Server, is no longer necessary. The JDBC-URL can be entered with a single backslash alone.

The following Image Services probes have been removed:

The probes DynamicBatchRecord, ImageServicesCacheStatistic, PrintQueueStatistics, PrintQueueStatus and WorkflowQueueEntries have been converted to Java.

The probes CourierStatistic and CeInfoImportAgentStatistic have been converted to Java.

All Ppmoi* probes have been converted to Java. The PpmoiRdbmsLicenseLimitExceeds probe was removed, because it is no longer possible to get this information from by calling "PPMOI show".

The probes DeserializeCalls, FindObjectCalls, LoggedOnUsers, RejectedUsers, ServiceLogonCalls and SoftSluViolations have been converted to Java.

All MkfHits* probes have been converted to Java.

All Mkf*Blocks probes have been converted to Java. All these probes now support a list of MKF DB types to check.

All ImageServicesCachePercentage* and ImageServicesCacheSectors* probes have been converted to Java.

The probes AllMkfDatabasesAvailable, PermanentDatabaseAvailability, SecurityDatabaseAvailability and TransientDatabaseAvailability have been merged into a single Java-based probe MkfDatabaseAvailability.

New portlet for aggregation reports, see also entry for 11443.

The list of agents is now sorted in two steps. First by state and then alphabetically descending by name.

In the debug output of some Cepest-based HTTP probes, the password was visible in cleartext. This has been fixed.

Cumulative security update of the IBM Java 8 JREs that are shipped with IBM ESM 5.5+ Also: The tool to migrate an IBM ESM 5.2.0.5 configuration to IBM ESM 5.5+ is removed from the product with this version.

Only configurations from the same product version can be imported.

The automatic base monitoring deployment on new agents can now be directly set from the UI.

The OnDemandCpuUse probe is no longer supported and was removed from the product. Existing configurations are removed when installing this update.

The limitation that prevent incidents to be created when a duplicate filter is fixed and no longer exists.

The FileDescriptorUsage probe can no longer be used, because it is removed from the product. There were technical limitations, that made the values returned by the probe quite useless. It only showed the file descriptors used by the JVM of the agent itself.

A new type of reports to create delta calculations is now available. The generated reports of this type are intended to be used in a special portlet, see entry for ID 12162.

A new probe to count client connections found in the Apache HTTPd access log was implemented. It is possible to filter these connections by HTTP status codes.

A command line tool to export the monitoring data into CSV files for later import into IBM DB2 or MS SQL Server databases exists.

Caution: This tool will be removed from the product again with one of the next releases (major or modification) or fixpacks after the upcoming one. Its sole purpose is to ease the migration for customers from H2 to IBM DB2 and MS SQL Server, which both are supported since 5.5.5.0.

It is now possible to directly add a graphical portlet for a situation group to the monitoring dashboard.

It is now possible to manually set the shown state of an Agent to "offline". This does not affect the agent itself, especially it does not lead to a shutdown of an agent in any way. This functionality’s sole purpose is to fix wrong status indicators for agents that are no longer accessible but could not send a status change to the server.

The base monitoring is only deployed on new agents if their version matches that of the server. This change prevents configuration deployments on outdated agents.

The CaseManagerCaseStatus and CaseManagerTaskStatus probes are now also capable of handling non-default solutions and are now also actively searching through sub-folders of tasks and cases.

HTTP Strict Transport Security (HSTS) is now enabled in the HTTP header of the web-UI.

The Icc4SapArchiveStatus probe has been switched to a pure Java implementation.

Some OnDemand probes did not recognize when the logon to the OnDemand system failed and returned a sample with value 0. This has been fixed.

Some cepest probes did use the password in clear text on the command line. If technically possible this was fixed. But there are some legacy probes that are still using passwords at the command line calling external programs.

New portlet for aggregation reports, see also entry for 11443.

The list of agents is now sorted in two steps. First by state and then alphabetically descending by name.

In the debug output of some Cepest-based HTTP probes, the password was visible in cleartext. This has been fixed.

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

Only configurations from the same product version can be imported.

The automatic base monitoring deployment on new agents can now be directly set from the UI.

The limitation that prevent incidents to be created when a duplicate filter is fixed and no longer exists.

The FileDescriptorUsage probe can no longer be used, because it is removed from the product. There were technical limitations, that made the values returned by the probe quite useless. It only showed the file descriptors used by the JVM of the agent itself.

A new type of reports to create delta calculations is now available. The generated reports of this type are intended to be used in a special portlet, see entry for ID 12162.

A new probe to count client connections found in the Apache HTTPd access log was implemented. It is possible to filter these connections by HTTP status codes.

A command line tool to export the monitoring data into CSV files for later import into IBM DB2 or MS SQL Server databases exists.

Caution: This tool will be removed from the product again with one of the next releases (major or modification) or fixpacks after the upcoming one. Its sole purpose is to ease the migration for customers from H2 to IBM DB2 and MS SQL Server, which both are supported since 5.5.5.0.

It is now possible to directly add a graphical portlet for a situation group to the monitoring dashboard.

It is now possible to manually set the shown state of an Agent to "offline". This does not affect the agent itself, especially it does not lead to a shutdown of an agent in any way. This functionality’s sole purpose is to fix wrong status indicators for agents that are no longer accessible but could not send a status change to the server.

The base monitoring is only deployed on new agents if their version matches that of the server. This change prevents configuration deployments on outdated agents.

HTTP Strict Transport Security (HSTS) is now enabled in the HTTP header of the web-UI.

The Icc4SapArchiveStatus probe has been switched to a pure Java implementation.

The probes ObjectsNotStoredFinally, SubscriptionRetryError, ContentSearchServicesIndexingErrors and ContentSearchServicesIndexRequests did not work for case-sensitive MSSQL databases. This has been fixed.

Closing and deleting incidents from a filtered portlet works now as expected.

Custom probes: It is now possible to set specific sample fields. With this the limitation of the returned value to be identical to the return code of the custom probe is also obsolete.

The logic for selecting the correct Objectstore (OS) in the ObjectstorePerformance probe has been reviewed. The probe now monitors only the OS configured and does not allow a wildcard to monitor more than one OS at a time.

New probe named "ObjectstoreRecoveryBinProbe". It counts the number of objects in the recovery bins in the configured object stores.

The IS domain name must now be explicitly set in a new field in the IS subsystem configuration.

New probe named "ObjectstoreNewObjectsProbe". It counts new objects of a specific type per day in the configured object stores.

New probe named "ObjectstoreCustomQueryProbe". It executes a custom query against IBM FileNet P8 object stores and counts the returned objects.

On some MS Windows installations instead of the integrated JRE the OS’s JRE was sometimes falsely referenced in the service start-up configuration. Now this is no longer the case.

Cumulative security update for IBM Java 8 JRE included in the product.

It is now possible to activate or deactivate all probes in all situations of a situation group.

The DLL used by the WMI probes is now thread-safe, so multiple WMI probes can be executed at the same time without causing any issues.

In the configuration there is now a simple context sensitive help per subsystem, probe, and task where applicable.

The OnDemand probes that are based on the ODWEK API have been re-implemented as pure Java probes.

It is now possible per portlet to define a fixed scaling factor for numeric values. The default is 1 (one), no scaling. Decimal values are possible to allow up and down scaling.

MS SQL Server is now supported for storing configuration data.

IBM DB2 is now supported for storing configuration data. Prior to this, only the monitoring data could be stored into IBM DB2.

Microsoft SQL Server is now supported for storing monitoring data.

When updating or deinstalling the product, the complete "karaf/agent" subdirectory is now saved to the "backup" directory and in case of an update restored again.

Configuring more than one Windows Event Log probe for one host (agent) no longer breaks the complete monitoring of that host.

It is still not supported to have more than one Windows Event Log probe per host, because of the bookkeeping process for this type of probe. Use the filter settings in the configuration to achieve the same goal with one probe only. For details read the documentation.

It is now possible to manually set the shown state of an Agent to "offline". This does not affect the agent itself, especially it does not lead to a shutdown of an agent in any way. This functionality’s sole purpose is to fix wrong status indicators for agents that are no longer accessible but could not send a status change to the server.

The global sample filter editor now stays open after changes have been saved aka applied.

The standard situations group named "All Situations" is no longer deletable. It cannot be renamed either.

A new wizard allows to edit task triggers per task in one place. This complements the existing task trigger configuration in the automation of a situation.

The P8 Audittrail probe no longer fails with a NullPointer-Exception if a log entry contains null values in CLOBs.

It is now possible to disable the default behaviour to automatically deploy a basic monitoring to new agents. This has to be done by creating the text file <server install dir>/karaf/etc/de.cenit.phoenix.server.services.agents.AgentBasicMonitoringInitializer.cfg with the following text in one line as its only content: disable=true

A memory leak in the monitoring view in combination with Firefox was fixed. But please see the related Known Limitation for restrictions, that could not be fixed for now.

The sometimes observed behaviour of agents losing the connection to their server after some time is fixed.

Scheduled Reports are now saved on disk in the directory "<server install dir>/karaf/server/reports/" as PDFs instead of being saved in the database.

A continuously blocking task that should forward incidents no longer leads to block the sample processing.

The dashboard settings are now also included in an export and the probes are no longer deactivated. Instead the user now must explicitly disable the probes while importing.

IBM JRE specific JSSE2 system properties to enable TLSv1.2 are now always set.

The GeneralDiskspace probe now correctly handles continuation lines in df output.

The table of subsystem references in the configuration wizard now has descriptive column headers.

Cumulative security update for IBM Java 8 JRE included in the product.

Narrower title leaves more space for information bar, which also acts as a navigational breadcrumb in views that are showing a hierarchy.

It is no longer possible to define a schedule for callback probes (e.g. logfile probes). These do not need a schedule as they are triggered automatically. So the definition of a schedule has no effect et all.

If HTTPS is enabled accessing the web-UI through the HTTP-URL the user will automatically redirected to the HTTPS URL.

Self-monitoring: It is possible to automatically send emails if one or more agents are in the state of "timed out" and/or if one or more tasks failed to run properly (state "failed" and "canceled").

For ODM logfile monitoring the formatfile for the IBM WebSphere logfile can be used.

The CMOD probes will no longer fail if the CMOD installation is not in the default directory.

Custom v2s format files are now retained between updates of the server and the agent.

All file names and domain user names can now be entered in the correct OS specific format. This means that it is no longer required to replace backslashes in file names and user names by forward slashes.

An exported configuration can now be imported. The import reads a JSON file that was created through an export, see extra release notes for that feature.

Export of the configuration is now possible. In this first version one can now export the configuration, without the situations and probes to a JSON file. That file can later be used for an import, see extra release notes entry for that feature.

The WebResponseTime and WebStatusMonitor probes have been switched to a pure Java implementation. Please note that due to technical changes the FULL_RESPONSE_TIME option for the WebResponseTimer probe is no longer available. Probes that use this option will automatically be changed to the option TOTAL_DURATION instead. Also please note that the both probes currently don’t support NTLM authentication.

The LdapConnection and LdapPerformance probes have been switched to a pure Java implementation. Please note that the login.conf for existing probes must be adjusted. Refer to the Configuration Guide for an example of a login.conf file.

The CaseManagerCaseStatus, CaseManagerSolutionStatus and CaseManagerTaskStatus probes have been switched to a pure Java implementation.

The CustomDatabaseQuery probe no longer ignores its timeout setting. Note that the setting is now in seconds instead of milliseconds.

New agents connecting to the server the first time will get a set of probes for monitoring basic paramesters like CPU, memory, and diskspace. Existing agents will not be affected.

Deep copy of subsystems is now supported. A deep copy is a copy of a subsystem populated with copies of the references of the child subsystems found in the original.

Shallow copy of subsystems is now supported. A shallow copy is a copy of a subsystem populated with references of the child subsystems found in the original.