What's New

This section outlines the new features and enhancements that are available in this release. 
CA UIM 9.2.0 (August 2019)
This section outlines the new features and enhancements that are available in the CA UIM 9.2.0 service pack. 
  • Replacing Oracle JDK with OpenJDK
  • Secure Hub and Robot
  • Removed License Dependency (Hub, Robot, Probes)
  • Enhanced security.cfg
  • Performance Improvements
  • Accessing support.nimsoft.com
  • Alarm Policy Enhancements
  • Telemetry Configuration for the PLA Model
  • RESTMon Enhancements
  • CABI Probe Deploys CABI JasperReports Server 7.1.1
  • Operator Console Enhancements
  • Availability Reports
  • Account Lock
  • Addressed Jackson Vulnerabilities
  • Addressed Update Version Issue in IM
  • Addressed Penetration Test Vulnerabilities
  • Removed MCS Utilities Tool
For more information about the new features, enhancements, resolved issues, and known issues, see the CA UIM 9.2.0 article.
CA UIM 9.0.2 (October 2018)
This section includes the new features and enhancements that are available in CA UIM 9.0.2.
Alarm Management with Centralized Alarm Policies
CA UIM provides centralized management of alarm configurations at device and group levels with 
 best practice monitoring policies. It also provides advanced options for defining static and dynamic thresholds, time over threshold, and alarm message customization along with the conditional disablement. For more information, see Manage Alarms with Centralized Alarm Policies.
Sub-Tenancy REST APIs
As an MSP administrator, you can globally modify the user-origin association of existing or new users by mapping them to specific origins for a Tenant using REST APIs (
). By default, when you add a user to an account, they do not have access to any resources, such as Performance Reports, Alarm Viewer, UMP Dashboards, until you enable the pre-provisioned white list of the origins for them. You can enable multiple origins for multiple UIM contact users and LDAP users. For more information, see Enable Enhanced Multitenancy.
RESTMon - Generic REST API-Based Monitoring
One of the key advantages of REST APIs is that they provide a great deal of flexibility. Data is not tied to resources or methods, so REST can handle multiple types of calls, return different data formats, and even change structurally with the correct implementation of hypermedia. To reduce the release time for supporting any new technology, we experimented internally to come up with monitoring probes using RESTful APIs, and looking at the efficiency of this REST-based monitoring approach, we packaged the REST-based monitoring framework, into a functionality called RESTMon probe.
The RESTMon probe enables you to monitor any technology and device (physical or virtual) that can send monitoring data over a REST API. Using the templates that are provided by CA UIM, you can upload the schema, which details the QoS and the aggregation logic with the http/https REST end points. You can define the metrics, alarms, and can populate CABI dashboards for the monitored devices. For more information about download and update of the default schema, see RESTful API Monitoring. From the Operator Console, you can download the default template and can build your own schema, or you can use one of the following out-of-the-box schemas:
  •  CA Jarvis Monitoring
  •  Elastic Cloud Storage Monitoring
  •  Elasticsearch Monitoring
  •  Paloalto Monitoring
  • Tandberg C Series Monitoring
  •  Tandberg EX90 Monitoring
  •  Tandberg MXP Monitoring
Webhook Integration using messagegtw Probe
This release of CA UIM introduces the messagegtw (Message Gateway) probe. The probe is used to publish CA UIM alarms to an external application using webhooks. A webhook is a simple notification message using an HTTP POST to an external application. In CA UIM, a webhook is triggered based on the occurrence of an alarm. The webhook integration also enables an integration with CA Automic for self remediation. For more information about the UIM-Automic integration, see Integrate CA Automic.
A common application of this would be to invoke a REST API of an external application with a customizable JSON payload. The payload can be customized and configured to use variable substitution from the source alarm, device, metric, and configuration item. For example, you might alert your remote application when an alarm is generated in CA UIM. For instance, the webhook can trigger an issue in issue tracking software, send an SMS message, post a message to a Slack channel, or send the alarms to any other third-party application or web page. For more information see, messagegtw probe documentation.
Operator Console
This release of CA UIM introduces the Operator Console, built using HTML5 with smarter User Experience workflows, richer set of out-of-box dashboards, and ad-hoc reporting capabilities. The Operator Console is available as part of the UMP provides users with an alternative way to manage membership in devices, groups, and device monitoring profiles, and view dashboards and alarms.
The Operator Console provides you with a graphical, clickable means to navigate through system operations and monitoring results. Summary views of monitored technologies, devices and groups, and alarms are linked to in-depth views of system components and metrics. 
For more information, see Operator Console Functions.
TLS v1.2 Support
This release of CA UIM provides enhanced security by supporting Transport Layer Security (TLS) v1.2 while communicating with the UIM database: Oracle or Microsoft SQL Server. This support lets the UIM Server establish secure communication with the UIM database, without compromising on the product performance. To enable the TLS v1.2 support in CA UIM, you perform:
  • configurations on the required database server: Microsoft SQL Server or Oracle.
  • enable the TLS option and provide relevant details during installation of the UIM Server.
For more information, see the support for TLS v1.2 in Oracle and Microsoft SQL Server.
IPv6 Support
CA UIM now supports deployment and monitoring on an Internet Protocol version 6 (IPv6) environment. This support enables UIM components to receive and handle data from IPv6 probes. You can install the following UIM components on an IPv6 environment:
Supported Platforms
Windows – 2008R2, 2016, Linux
Windows – 2008R2, 2016
Nimbus Infrastructure (Secondary Hub)
Windows – 2008R2, 2016
Nimbus Robot (Secondary robot)
Windows, Linux, AIX, HP-UX
Infrastructure Manager
Windows – 2008R2, 2016
For more information to configure IPv6 and to view the list of supported probes, see Configure IPv6 Support.
Enhanced Profiles in MCS
This release of CA UIM includes a new type of Monitoring Configuration Service (MCS) profile, called an enhanced profile. Enhanced profiles provide a consistent way to configure alarms using MCS. Enhanced profiles enable you to configure metrics, baselines, alarm thresholds, Time Over Threshold alarms, and create custom alarm messages, all within a single MCS profile.
Rather than sending an alarm immediately after a threshold violation has occurred, Time Over Threshold, reduces alarm traffic and provides more contextual information around generated alarms by:
  • Monitoring the events that occur during a user-defined sliding time window 
  • Tracking the length of time that the metric is at each alarm severity.
  • Raising an alarm if the cumulative time the metric is in violation during the sliding window reaches the set Time Over Threshold.
For more information about the Time over threshold rule, see Time over Threshold event rule in the Probes Documentation Space.
 If you are using an earlier version of the MCS package for a probe and want to migrate your existing profiles to enhanced profiles, ensure that you upgrade to the latest (non-enhanced) MCS template package before attempting to migrate the existing profiles to enhanced profiles.
For the complete list of probes that support enhanced profiles in MCS, their corresponding MCS template package versions and additional information on migration from existing MCS profiles, see Configuring Alarm Thresholds in MCS in Probes Documentation Space.
New Platform Support
The following table lists new combinations of operating systems and components that are supported in CA UIM 9.0.2. For more information, see Compatibility Matrix and Probes Support Matrix.
UIM Component
SQL Server 2016
SQL Server 2017
Windows Server 2016
All components
Windows Server 2019
Robot, Probes (CDM, RSP, Dirscan, Processes, Logmon, net_connect)
PowerPC 64 Little-endian (ppc64le)
Robot, Probes (CDM, Processes, Logmon, Oracle, and DB2)
18.04 LTS
Robot, Probes (CDM, Logmon, Dirscan, and Processes)
IBM iSeries
i 7.3
iSeries Robot, Probes (Diskstat, Fetchmsg, History, Jobqs, Jobs, Jobsched, Journal, Outqs, and Systat)
CABI is not supported for SQL Server 2017.
Deprecated Platform Support
The following table lists operating systems and components that are no longer supported from CA UIM 9.0.2. For more information, see Compatibility Matrix and Probes Support Matrix.
UIM Component
Windows 2008
MySQL Community Edition
11.2 (IA64)
11.2 (PA-RISC)
IBM iSeries
CentOS 5 (32 bit and 64 bit)
Robot, Hub
Debian 5 & 6
Robot, Hub
RHEL 5 (32, 64 bit)
Health Reports
The CA Business Intelligence (CABI) Health reports enable you to understand the usage, health, and aggregated performance of your Server or Network. For more information, see Health Reports in Probes Documentation Space.
VMware Dashboards
New predefined CA Business Intelligence (CABI) dashboards for VMware probe are now available that provide an overview of your VMware environment. For more information, see VMware Dashboards in Probes Documentation Space.
MCS Dashboards
New predefined CA Business Intelligence (CABI) dashboards for Monitoring Configuration Service (MCS) are now available that provide an overview of your device and device group monitoring profile configurations. For more information, see Monitoring Configuration Service Dashboards in Probes Documentation Space.
Ad hoc Reporting
You can now create custom reports in the CABI Server when the predefined reports do not meet your needs. For more information, see Create a Custom Report. For more information about Ad Hoc Reporting, see Design an Ad hoc View.
UMP CABI Portlet
You can now use the ump_cabi portlet package to view the predefined CABI dashboards in UMP. For more information, see Deploy the ump_cabi Portlet.
Addressing CVE-2018-13820 and CVE-2018-13819 Vulnerabilities
This release of CA UIM addresses CVE-2018-13820 and CVE-2018-13819 vulnerabilities. CVE-2018-13820 is about a hard-coded passphrase, which is now externalized to data_engine. The probes that connect to the database now use the externalized passphrase. CVE-2018-13819 is about a hard-coded secret key in the ppm probe, which is also addressed as a part of this release. For more information, see Addressing CVE-2018-13820 and CVE-2018-13819 Vulnerabilities.
Upgrade to Microsoft Visual C++ Redistributable for Visual Studio 2017
This release of CA UIM uses Microsoft Visual C++ Redistributable for Visual Studio 2017 instead of the end-of-life (EOL) Microsoft Visual C++ Redistributable. For more information, see Upgrade to Microsoft Visual C++ Redistributable for Visual Studio 2017.
uimapi provides improvements over webservices_rest and provides Swagger documentation and endpoints to work with the RESTful web services. Deploy uimapi 9.02 from the archive to get these web services. The uimapi REST API endpoints are provided within a self-documenting framework that lets you try the methods and see the generated responses. All methods are grouped by resource type and can be displayed in a single window. Use the 
List Operations
, and 
Expand Operations
 options to expand and collapse the resources and methods. You can also use the 
Try it out!
 button to send the request and see the generated response in real time. For more information, see uimapi APIs in Probes Documentation Space.
plugin_metric is a dynamic library that is introduced in hub or robot version 7.96 that is loaded into the spooler process. The plugin_metric post-processes QoS messages. The post-processing includes generating alarms according to static and dynamic thresholds, base-lining, or performing Time over Threshold. The plugin_metric is configured by default for the hub/spooler. The plugin_metric configuration file is the central place for all the alarm policies for all the probes of a robot. For more information, see plugin_metric in the Probes Documentation Space.
Compatibility Matrix
The compatibility matrix for CA UIM 9.0.2 is now included in the DocOps space. Review the following topics for the required information:
Multiple enhancements and improvements have been made to the ems probe. The ems probe is now added to the list of probes that are supported by the ha probe for failover scenarios on the secondary hub. For more information about the specific changes to ems probe, see the ems probe documentation.
alarm_enrichment and nas
The nas and alarm_enrichment probe has been enhanced for performance improvements for alarm queue handling and MS SQL database performance. Some additional parameters are added and default values for various settings are changed in their respective probe configuration (.cfg) files. For specific changes made to the alarm_enrichment / nas probe functionality, see the nas probe documentation
The following changes have been made to the wasp probe which improves the memory capacity:
  • Changed the default value of the java_mem_max setting in wasp.cfg to Xmx4096m.
  • Changed the default value of the nimpool_timeout setting in wasp.cfg to 300 seconds.
Changed the default value of various settings in the discovery_server.cfg file.
For more information, see the discovery_server probe documentation.
The following enhancements have been made to the data_engine probe:
  • Changed the default value of various settings in data_engine.cfg.
  • Added the update_metric_id=yes setting to data_engine.cfg. 
  • Improved startup time and performance when using an Oracle database.
  • Added new configuration parameters for optimizing Oracle driver functionality.
  • Added new configuration parameters for supporting Transport Layer Security (TLS) v1.2 for Oracle and Microsoft SQL Server databases.
  • Enhanced data_engine so that it also uses the 
     value to uniquely decide whether the incoming QoS is a new one or an update of an existing QoS. 
For more information, see the data_engine probe documentation.
The following enhancements have been made to the hub probe:
  • Added the ability to monitor, at specific intervals, if robots deployed on a hub are powered on.
  • Changed the default value of various settings in hub.cfg.
  • Updated to ensure that hub works in a CA UIM environment when TLS v1.2 is enabled on the UIM database (Oracle and Microsoft SQL Server).
  • Updated to ensure that hub supports communication with TLS v1.2-enabled OpenLDAP server.
  • Fixed an issue where USM was ignoring the severity of hub alarms.
  • Updated to provide support for Red Hat Directory Server 10 (RHDS 10) as the LDAP Server.
  • Removed support for Windows 2008.
  • Removed support for the following 32-bit platforms:
    • Solaris 10 and 11
    • RHEL 6
    • CentOS 6 and 7
    • SUSE 11
    • OpenSUSE 12 and 13
       The hub no longer supports any 32-bit platforms.
For more information, see the hub probe documentation.
A new version, 7.97, of hub and robot is now available on the Nimsoft web archive. This new version (v7.97) has been released after the CA UIM 9.0.2 release. We recommend that you use this new 7.97 version of hub and robot. The 7.97 version has been updated to support the Microsoft Visual C++ Redistributable for Visual Studio 2017 package version 1.01 (vs2017_vcredist_x86 1.01 and vs2017_vcredist_x64 1.01). This support helps ensure that the minimum version of the VS 2017 package is equal to or greater than 1.01. With this dependency on the version 1.01, the computer is not getting restarted automatically when installing the VS 2017 package. That is, with v1.01, no auto-restart of the computer happens.
The following enhancements have been made to the automated_deployment_engine probe:
  • Configure a custom SSH port and select the version of the robot package to deploy.
  • Server Message Block protocol v1 (SMB1) is no longer supported. Support for SMB2 is now enabled.
  • Added a new raw configuration parameter probeFileTransferBufferSize.
  • Added a configuration option to control deployment rollback behavior when an update fails.
For more information, see the automated_deployment_engine probe documentation.