Release Notes

Summary of enhancements, fixes, and open issues.
uim851
There is no supported upgrade path from CA UIM 8.5.1 beta to CA UIM 8.5.1 GA.
This article explains the new features in this release. It also details the international support, product accessibility, and third-party software agreements for CA UIM.
 
Contents
 
 
 
New Features
See the topic What's New  for a list of the new features in this release.
Updated Probes and Packages List
The following probes and packages are installed as part of this CA UIM release.
Probes
You can locate the version number for individual probes on both the 
Probes
 and
 Installed Packages
 tabs in Admin Console. For documentation on probes, see the CA UIM Probes space.
The correct version number for the trellis probe is located on the
 Installed Packages
 tab. The version number for trellis that appears on the 
Probes
 tab displays the version number of the latest installed service.
 
Component
 
Version Number
ace
8.42
alarm_enrichment
8.42
automated_deployment_engine
8.51
baseline_engine
2.76
cdm
5.80-MC
cm_data_import
8.51
controller
7.80
data_engine
8.50
discovery_agent
8.51
discovery_server
8.51
distsrv
5.40
ems
9.01
fault_correlation_engine
1.67
hdb
7.80
hub
7.80
maintenance_mode
8.40
mon_config_service
8.50
mpse
1.72
nas
8.42
net_connect
3.31
nis_server
8.51
ppm
3.45
prediction_engine
1.34
qos_processor
8.50
relationship_services
1.72
rsp
5.20
sla_engine
3.80
spooler
7.80
telemetry
1.03
topology_agent
1.72
trellis
8.51
udm_manager
8.51
wasp
8.51
webservices_rest
8.51
Packages
See your CA UIM package versions by navigating to the
 Installed Packages
 tab in Admin Console. For documentation on the use of Admin Console, see Using Admin Console.
 
Component
 
Version Number
adminconsoleapp
8.51
app_disco_apache
7.90
app_disco_mysql
7.90
app_disco_oracle
7.90
attr_publisher
7.90
cabi-sysedge-report
1.0
cabi-sysedge-datasource
1.0
java_jre
1.80
mon_config_service_templates
10.31
mps
8.49
nisapi_wasp
8.51
pp_defaults
2.12
robot_aix
7.80
robot_deb
7.80
robot_exe
7.80
robot_hpux
7.80
robot_rpm
7.80
robot_sol
7.80
robot_update
7.80
uimhome
8.51
ump
8.51
ump_accountadmin
8.51
ump_adminconsole
8.51
ump_cabi
2.00
ump_cloudmonitor
8.51
ump_dashboard
8.51
ump_listdesigner
8.51
ump_listviewer
8.51
ump_mobile
8.51
ump_mytickets
8.51
ump_policyeditor
8.51
ump_qoschart
8.51
ump_relationshipviewer
8.51
ump_reports
8.51
ump_reportscheduler
8.51
ump_servicedesk
8.51
ump_slareports
8.51
ump_slm
8.51
ump_unifiedreports
8.51
ump_usm
8.51
vs2010sp1_vcredist_x64
1.01
vs2010sp1_vcredist_x86
1.01
Packages for Monitoring SystemEDGE-enabled Devices
 
cabi-sysedge-report Release Notes
 
The cabi-sysedge-report is a companion package that supports the SystemEDGE OnDemand Report that you can view in the Device Summary Dashboards, part of the CA Business Intelligence with CA UIM. The SystemEDGE OnDemand Report displays data for SystemEDGE-enabled devices that are monitored with the snmpcollector probe.
Package Name
Description
State
Date
 
cabi-sysedge-report
 
Initial Release
GA
March 2017
 
cabi-sysedge-report Installation Concerns
 
For more information about how to install the cabi-sysedge-report package, see Monitor SystemEDGE-enabled Devices with the snmpcollector Probe
 
cabi-sysedge-datasource Release Notes
 
The cabi-sysedge-datasource is a companion package that supports the bean data source that you create for use with the SystemEDGE OnDemand Report.
 Package Name
Description
State
Date
 
cabi-sysedge-datasource
 
Initial Release
GA
March 2017
 
cabi-sysedge-datasource Installation Concerns
 
For more information about to install the cabi-sysedge-datasource package, see Monitor SystemEDGE-enabled Devices with the snmpcollector Probe.
Archive Probes
The following optional probes are downloaded to the archive during CA UIM installation.
For more information about CABI, refer to CA Business Intelligence Server Release Notes. 
Component
Version Number
cabi
2.00
Resolved Issues
The following issues were resolved in this release:
ADE Reliability Improved (Support Case 606608)
The reliability of ADE package synchronization has been improved on secondary hubs.
Admin Console Archive Credentials Are No Longer Pre-Populated in Firefox
Sometimes, Firefox would pre-populate the Admin Console archive credentials with a user’s CA UIM user name and password if the user chose to have Firefox remember their credentials. This no longer occurs in the latest release of CA UIM.
Alarms Generated by the logmon Probe Now Have the Correct Severity (Support Case 642035)
logmon probes configured with the Log Monitoring and Setup logmon configuration profiles were incorrectly generating alarms with the Information severity level. The logmon probe now correctly generates alarms with the configured severity level.
Alarm View 
Assigned to
 Dropdown Now Sorts Alarms Correctly
Using the
 Sort By
 drop-down to sort by the 
Assigned To
 alarm parameter previously resulted in incorrect sorting of the alarm table list. This has now been corrected to function as intended..
The baseline_engine Probe Now Recovers After Concurrent Modification Exceptions (Support Case 375092)
The baseline_engine probe now recovers after concurrent modification exceptions.
The data_engine Probe QoS Status Window Is No Longer Blank for Specific Situations
In previous versions of CA UIM, the data_engine Probe QoS Status window would come up blank if a customer’s environment used declared value types greater than 32-bit INT for specific stored procedures. The data type for those procedures has been reset to BIGINT to address this situation.
The data_engine Probe Now Issues an Error When It Fails to Create S_QOS_DATA Entries When the Target Is Longer Than 255 Characters (Support Case 417491)
Added logging in data_engine at level 0 (fatal) if a target string is longer than 255 characters.
Fault Correlation Engine Issue in Which alarm_close Messages Were Not Acknowledged Has Been Corrected (Support Case 472094)
Sometimes, the fault correlation engine would not acknowledge alarm_close messages, causing errors in relationship viewer.
To fix this issue, add alarm_close_with_dev_id = yes to the setup section of nas.cfg.
Japanese Double-Byte Characters Now Appear Correctly in CA UIM Mobile
Garbled double-byte characters no longer appear in the Japanese-language version of the CA UIM Mobile Application.
Long SQL Statements No Longer Fail Table Insert (Support Case 366455)
An issue in the qos_processor in which long SQL statements failed table insert has been fixed.
nas Alarm Replication No Longer Fails Between Primary and Secondary Hubs (Support Case 465349)
This release fixed an issue preventing nas alarm replication between primary and secondary hubs.
The Origin Is Now Updated in the S_QOS_DATA When 
samplevalue 
Is Null (Support Case 439882)
Fixed an issue where, when the samplevalue on an incoming QOS_MESSAGE was null, the origin was not updated in S_QOS_DATA.
Portal Log Error No Longer Occurs on Single System Installations (Support Case 318889)
The following error no longer appears in the
 portal.log
 file of systems that are running both UIM and UMP:
03 Oct 2016 05:47:07,160 ERROR [PortalInitAction:111] java.io.FileNotFoundException: C:\Program Files (x86)\Nimsoft\probes\service\wasp\webapps\adminconsoleapp\WEB-INF\classes\log4j.xml (The system cannot find the file specified)
03 Oct 2016 05:47:07,172 ERROR [PortalInitAction:111] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
03 Oct 2016 05:47:07,173 ERROR [PortalInitAction:111] at java.lang.Thread.run(Thread.java:745)
Probe SDK Documentation Corrected for Webservices Alarm Calls (Support Case 521798)
The probe SDK documentation has been corrected for webservices alarm creation parameters and alarm updating and acknowledgment command syntax.
Server Exception No Longer Occur When Running the 
list_subscribers
 Callback in a European Local (Support Case 246102)
If you run the 
list_subscribers
 probe callback in the Probe Utility, a server exception error no longer occurs if your hub is in a European Locale.
SLA Reports Now Display Correct Compliance Data for Upgraded Systems (Support Case 498861)
A code change in the upgrade from CA UIM v8.2 to CA UIM v8.4 SP1 accessed sla_id data from an incorrect h_slo_compliance table, resulting in incorrectly reported compliance of 100%. This data access issue has been corrected, and reports now correctly display compliance percentages. 
Source From Field in Log Monitoring Configuration Profiles Set Properly (Support Case 508452)
The Monitoring Configuration Service was configuring the Source From field on target devices to Character Position=8 when the field was set to Column=Yes. The Source From setting is applied correctly from the Log Monitoring configuration profile.
USM Groups Types Can No Longer Be Changed After Creation
Once a group is created in USM, its type cannot be changed from static to dynamic or vice versa. This is not a realistic use scenario and so is no longer supported.
Wildcard Characters Can Now Be Used in Performance Report URLs (Support Case 510119)
When setting the 'rawData' parameter to TRUE in a URL call for data to populate a Performance Report, it is now possible to use a wildcard character in specifying series data.
Known Issues
The following items are the current known issues with this release:
At a Glance Reports Do Not Support SQL Database QoS Metrics 
The At A Glance report returns the CDM QoS for the SQL Server if CDM/RSP is configured for it. Currently, none of the SQL Database QoS metrics are returned for this report.
cdm Probe Setting Might Impact the Performance of Discovery Server When Monitored Devices Are Using a Shared File System
By default, the cdm probe configuration has the Setup/allow_remote_disk_info set to Yes. This allows the cdm probe to generate the Device ID for all shared drives on a monitored device using a shared file system. In this situation, cdm creates duplicate perspectives for the same shared file system. This can impact the performance of the Discovery Server.
To correct this issue, use Raw Configure to change the cdm Setup/allow_remote_disk_info set to No. The administrator should take a look at the UIM database and remove duplicate perspectives. This should return the performance of the Discovery Server to a normal operating level.
Changes to Alarm Filters Are Not Reflected Immediately in USM
If you use Account Admin to modify the alarm filter of an ACL, and then immediately view alarms in USM with that ACL, the alarms that are shown might not reflect the change that is made to the alarm filter. This occurs because the default refresh interval for the alarm cache is set to 5 minutes for performance reasons.
Change Password Portlet Is Not Available After Upgrade
The Change Password portlet is no longer available after upgrading to CA UIM 8.4 or later. Administrators can change a user's password with the Account Admin portlet. 
Custom URL Frame in a Unified Reporter Dashboard Does Not Refresh
If you create a Unified Reporter dashboard and add a custom URL, you have the option of selecting an auto-refresh interval for the custom URL frame or manually refreshing the URL frame. Due to a known limitation with JasperReports, if you select either the auto-refresh interval or the 
Manual Only
 refresh option, the frame will will not successfully refresh.
Therefore, if you use a custom URL in a dashboard, it is recommended that you:
  • Do 
    not
     select an auto-refresh interval
  • Avoid clicking the refresh button
To successfully refresh the custom URL frame, reload the dashboard.
Cannot View Active Sessions on UMP
When users login to the UMP using the Standalone JavaServer Pages (JSP) in the URL (standalone.jsp), then those sessions are not recorded and you cannot view the actual number of active standalone sessions, however other sessions can be viewed.
Dashboard Design Permission Requires Bus User Privileges
In the Account Admin portlet, you can add the Dashboard Design permission to an ACL for an account contact user if the user wishes to create custom dashboards. However, the permission will function only for a bus user. Dashboard Design permission applied to an account contact user is ignored.
Error About Retrieving Details for the 
uimserver_home_redirect
 Package in 
uimserver_ia_install.log
 
After upgrading to CA UIM 8.5.1, you might see the following error in the 
uimserver_ia_install.log
:
ERROR probe.AdePackageDistributionStatus:getPackageDetails:127 [Thread-40] - Unable to retrieve package details for pkgName: uimserver_home_redirect, pkgVersion: 8.51
This error can safely be ignored.
Existing Unified Reporter Schema Name Issues During Upgrade
Using an existing schema or catalog name on the Database Connection panel during Unified Reporter upgrade can generate an error that the entered name is already in use. To fix this error, use a different schema or catalog name.
Exchange Monitor Setup Template Localization Issue
In CA UIM 8.5.1, the default profile name is not localized in the Exchange Monitor Setup MCS template.
Insufficient Virtual Memory in Windows Systems Results in a Load Error
In Windows systems, insufficient virtual memory can result in performance problems. For example, the Alarms view in USM might not load but show no errors.
The Windows event log files will record the following warning:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory
A short-term solution is to power down the UIM server and restart it. The long-term solution is to open the Systems Properties window/Performance Options pane and uncheck the box for 
Automatically manage paging file size for all drives
 and set the paging file size to three times the physical memory of the system.
Interface Groups Not Supported with Mobile App
Currently, the application does not support interface groups with either Android or iOS devices.
Java-Based Probes Might Not Start on Secondary Robot Deployment
CA Unified Infrastructure Manager v8.51 and later are installed with Java 8. When upgrading to CA UIM v8.51 or later, if Java-based probes previously deployed to a robot use an older version of Java (for instance, Java 7), the probes might not start. To resolve this, redeploy java_jre version 1.7 to the robot and then restart the robot.
Java SDK Environment Variable Requirement
If you use the Java SDK to send messages to UIM, set the following environment variable to designate the loopback IP address for contacting the local robot. For example:
NIM_ROBOT_IP=127.0.0.1
Liferay Issue Might Cause Permissions Error in UMP Portlets
Due to a known issue with Liferay Enterprise Edition v6.1.30 (used by UMP v7.5 and later), users might encounter a permissions error in UMP portlets. This issue can occur in UMP instances that were created as follows: an administrator exported pages as a LAR file, created a site template and imported the LAR file, created a site that is based on the template, and then deleted one or more pages from the template.
This issue can be avoided if you export and import a LAR file with the 
Permissions
 checkbox selected. When you export pages as a LAR file, select the 
Permissions
 checkbox under the heading Other. When you create the site template and import the LAR file, ensure that you again select the 
Permissions
 checkbox.
If you encounter this issue, the work-around is to select the gear icon in the upper right-hand corner of each UMP portlet. In the Configuration pane, select the 
Permissions
 tab, and then select the 
View
 checkbox for each user in the Role column.
Localization Can Result in a Mix of Output Languages
Under certain circumstances, non-English QOS characters may appear in output encoding is inconsistent in the configuration of probes (such as wasp, dashboard_engine, or alarm_enrichment) that persist data to the database.
Missing Alarms in USM Due to Device ID Case Mismatch in Oracle Tables (Support Case 415248)
Prior to CA UIM v8.4, the following parameters in the file were recommended for a user to enhance performance in returning alarms to USM from Oracle under high data loads:
  • NLS_SORT=BINARY
  • NLS_COMP=BINARY
However, these settings can now create a mismatch in the cases of dev_id in NAS_ALARMS and CM_DEVICE tables that results in a JOIN failure and alarms missing in USM. Recommended Oracle settings for CA UIM versions prior to 8.4 are given in the Oracle installation instructions. No further change is needed for users upgrading to CA UIM 8.4 or later or for users installing CA UIM version 8.4 or later.
MCS Users Can Run an SQL Script to Determine If Their Database is Ready to Upgrade to 8.5.1
This issue only impacts CA UIM versions 8.4 or later.
MCS users whose databases contain duplicate entries in their database tables should not upgrade to 8.5.1 because the duplicate entries can result in inconsistent data after the upgrade is complete. To determine if your database contains the duplicate entries that can cause this issue, run the SQL script provided for your database type.
If your database vendor is MySQL or MS SQL Server execute the following SQL query using the client application for your database:
select case
when
(select count(*) from (select COUNT(*) as duplicates from SSRV2ConfigValue
group by profile, field)a where a.duplicates > 1) > 0
then
'Contact CA support before upgrading to UIM 8.51.'
else
'It is safe to upgrade to UIM 8.51.'
end;
If your database vendor is Oracle, execute the following SQL query using the client application for your database:
select case when
(select count(*) from (select COUNT(*) as duplicates from SSRV2ConfigValue
group by profile, field)a where a.duplicates > 1) > 0
then
'Contact CA support before upgrading to UIM 8.51.'
else
'It is safe to upgrade to UIM 8.51.'
end
from dual;
If your SQL query results in the message, 'Contact CA support before upgrading to UIM 8.51,' contact Support before you upgrade to 8.5.1. Attach to the case, in csv format, extracts of the following tables:
  • ssrv2template
  • ssrv2devicegroup
  • ssrv2field
  • ssrv2profile
  • ssrv2ConfigValue
If your SQL query results in the message, 'It is safe to upgrade to UIM 8.51,' upgrade to 8.5.1.
MCS Configuration Profiles Might Not Be Applied to All Members of Large Dynamic Groups
Dynamic groups are updated by default every 5 minutes. In large 
CA Unified Infrastructure Management
 environments, dynamic groups could have a thousand members or more. It's unlikely that Monitoring Configuration Service will be able deploy or update configuration profiles to all members of a large dynamic group within the 5-minute interval. To resolve the issue, you can increase the configured interval. The interval is set with the group_maintenance_interval on nis_server. For details about modifying the group_maintenance_interval on nis_server, see the 
Configure the Update Interval for Automatic Groups
 section in the Create and Manage Groups in USM article.
MCS MySQL, Oracle, or SQL Server Device-level Configuration Profile Overrides Might Not Be Marked with an Asterisk
Using Monitoring Configuration Service, you can create group-level MySQL, Oracle, or SQL Server configuration profiles. After MCS applies the group configuration profile to all members of a group, you can make device-level overrides. MCS marks each field with a device-level override on the device configuration profile with an asterisk. Under the following conditions, you might not see an asterisk on some of the device-level 
alarm
 fields that have overrides:
  • The group-level profile for a checkpoint was set to publish 
    None
     or 
    QoS
    , and then
     
  • The device-level override for the same checkpoint is set to 
    Alarm
     or 
    QoS and Alarms
     
mon_config_service.log File Rotation Not Working Properly
Both log4j and NimLog are currently writing to the mon_config_service.log and this prevents the log file entries from rolling properly. To correct this issue, you need to modify the log4j.properties file and add an appropriate file size for the mon_config_service.log file. The workaround to correct this issue is:
  1. In Remote Desktop, open the log4j.properties file located at <uim>\Nimsoft\probes\service\mon_config_service in a text editor.
  2. Remove FILE from the 'log4j.rootCategory=ERROR, FILE, CONSOLE' statement on the first line of the file.
    The statement becomes 'log4j.rootCategory=ERROR, CONSOLE'.
  3. Save the file.
  4. Specify an appropriate file size for the mon_config_service.log file. The default file size is 1024 KB.
    1. Access Access Admin Console.
    2. Select the hub on the 
      Robots
       tab, and then click the 
      Probes
       tab.
    3. Click the inline menu button for the mon_config_service.log file, and select 
      Raw Configure
      .
    4. Click the 
      Setup
       section.
    5. Click '
      +
      ' in the top right corner to create a new key.
    6. Enter 
      logsize
       in the Key field.
    7. In the Value field, enter an appropriate file size in kilobytes for the mon_config_service.log file.
    8. Click 
      Create
       to add the logsize key value.
    9. Click Update to save your changes.
Monitoring Configuration Service Profile Type Field Names
While MCS profile types and the associated probe configuration GUIs (either in Admin Console or Infrastructure Manager) for a particular probe will have the same configuration options, individual field names might not always match between them. For more information about the available fields for each probe GUI, see the documentation for each probe on the CA UIM Probes site.
Name Resolution Conflicts on Debian Systems with the automated_deployment_engine Probe
By default Debian v6 uses the address 127.0.1.1 as the name resolution address. When a robot is deployed to a Debian 7 or 8 system using automated_deployment_engine, after system restart, the robot attempts to bind to 127.0.1.1 as the available address. Use the following work-around to avoid contention for 127.0.1.1 on your Debian system:
  • When installing the robot manually or with automated_deployment_engine, you must go to the target system after installation and must add the following line to the robot.cfg file:
robotip = ip_address
where 
ip_address
 is the desired IP address that the robot should bind to on the target system.
  • When deploying to Debian 6.0.5 using XML, you must define the 
    <robotip>ip_address</robotip>
     option, where 
    ip_address
     is the IP address that the robot should bind to on the target system.
The nas AO (Auto Operator) Command Action Does Not Execute When There Is A Space in the Path (Support Cases 246133, 315782)
A command action cannot be parsed when the path contains spaces. Do not use spaces in the AO command path.
Probe Administration Returns an Unknown Error in a Windows Cluster Environment
When you attempt to configure a probe, probe administration might return an 
unknown error
 message in a Windows Cluster environment. Specifically, this problem has occurred with the ems probe, but can happen with other probes. To work around the issue, follow these steps:
  1.     Log in to Infrastructure Manager as the administrator.
  2.     On the Security tab, select 
    Probe Administration
    .
  3.     Click 
    New Probe
     to add an entry for the ems probe.
    1.         Select ems in the 
      Probe
       drop-down list.
    2.         Select Admin in the 
      Access
       drop-down list.
    3.         Enter an asterisk ( * ) in the 
      IP Mask
       field, and click 
      OK
       to save your changes.
Profile Reconciliation Function Removed From Monitoring Configuration Service
The Reconciliation function was moved from the mon_config_service probe to a new MCS Utilities Tools. The MCS Utilities Tools provides more flexibility to schedule reconciliation, more in-depth reports of detected differences, and increases the performance of the mon_config_service probe. To fix differences in configuration profiles managed by Monitoring Configuration Service, use the MCS Utilities Tool.
Printed Performance Reports Display Legends When No Data (Null) is Graphed
In CA UIM 8.5, when a QoS series on a scheduled PRD report does not have any data (all null values or no data) and the “stacked” option is selected, a legend for the series is still printed in the report footer.
S_QOS_SNAPSHOT Does Not Update (Support Case 439738)
Whenever the hub_bulk_size parameter is set to a value larger than the total QoS objects in the S_QOS_DATA, S_QOS_SNAPSHOT will not update. This is a configuration issue.
To correct this issue, set the hub bulk_size to a value less than the total number of rows in s_qos_data.
Robot Communication Failure on Unix When Using Nimldr
 
 
If you are using Nimldr, robot communication over the network can fail due to an invalid /etc/hosts file. If this occurs, ensure that the /etc/hosts file on any system hosting a UIM robot, hub, server, or UMP instance contains a valid entry for the local system. This must be a hostname (does not need to be fully qualified) and IP address. If only loopback is defined (for example, 127.0.0.1 localhost), then the controller probe on that system will be unaware of its own IP address, resulting in network communication failure.
Other methods of robot or hub deployment do not require /etc/hosts configuration.
Reduced the Number of Probe License Checks (Salesforce Case 436860)
Monitoring Configuration Service was checking for licenses for the probes associated with profile types every 60 seconds. With this release, Monitoring Configuration Service checks for probe licenses less frequently.
Trend Reports Show Deleted Devices
Devices deleted in USM still appear in the Elements to Show list in Group Trend Reports, though they are not included in the charts.
Upgrade Self-signed Certificates
The Java version was updated to Java 8. You must upgrade any self-signed certificates generated by CA UIM from previous CA UIM versions. If you do not upgrade the pre-existing certificates, HTTPS connections to CABI Server will not work due to the change in security encryption levels in Java 1.8. For more information, see Configure HTTPS in Admin Console or UMP.
Unknown Error Occurs During Some Alarm Operations
You might see the following error when using the 
Acknowledge
Set invisible
, or 
Assign
 icons in the USM Alarm View:
An unknown error has occurred.
Refreshing your browser may resolve the issue.
Details:
com.firehunter.ump.exceptions.DataFactoryException : null
Stack Trace:
org.springframework.orm.jpa.JpaSystemException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1; nested exception is javax.persistence.PersistenceException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1
Caused by: javax.persistence.PersistenceException: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1
Caused by: org.hibernate.jdbc.BatchedTooManyRowsAffectedException: Batch update returned unexpected row count from update [0]; actual row count: 2; expected: 1
You can safely ignore this error.
Using Variables for a Profile Name is Supported (Salesforce Case 418533)
The Monitoring Configuration Service now allows users to enter variable (for example {device.ip} or {device.name}) for a Profile Name.
USM Doesn't Create Empty Automatic Groups for User Tags
For Oracle users, if there are no systems with user tags assigned and the user creates an automatic group in USM with User Tag 1 or User Tag 2 selected as the parent, no group will be created.
wasp Contains a Non-functional Key for Service-host Address
Functionality for the service_host probe has been moved to wasp, and the probe is no longer installed as part of CA UIM. An address key for the probe still exists in the ump_common section of wasp but is not functional.
wasp Fails to Start Without mpse
If mpse is not deployed and running on the same robot as wasp, or if wasp does not indicate in its configuration file where mpse is running, then wasp fails to start. This results in UMP and any other webapps failing to load. The work-around for this issue is to stop the wasp probe and edit the wasp configuration to point to the hub address (for example, /domain/hub/robot/mpse) where mpse is deployed. Ensure that mpse is running when you restart wasp.
International Support
Include localization details for your release. 
The user interface is available in the following languages:
  • Brazilian Portuguese
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Spanish
The user documentation is available in the following languages:
  • Brazilian Portuguese
  • German
  • Japanese 
  • Spanish
Third-Party Software Agreements
 CA UIM uses the following third-party software. To read the required license agreement, review the .zip file  TPSRS for UIM 8.5.1 SP1_updated7-14-17.zip.
 
    • adal4j 1.1.2
    • Adaptive Communication Environment (ACE) 5.5.10
    • Adaptive Communication Environment (ACE) 5.7.8
    • Adobe Flex SDK 3.4
    • Aleksey XML Security Library 1.2.9
    • antlr3 3.5
    • apache commons csv 1.4
    • apache commons dbutils 1.2
    • Apache JCS 1.3
    • Apache log4cxx 0.10.0
    • Apache log4j 1.2.15
    • Apache log4net 1.2.10
    • args4j 2.32
    • aspectjrt 1.8.2
    • aspectjrt 1.8.5
    • aspectjweaver 1.8.6
    • aws-java-sdk 1.10.50
    • aws-java-sdk 1.11.18
    • aws-java-sdk 1.11.77
    • Axis 1.1
    • backbone.js 1.2.1
    • bcprov 1.53
    • Bouncy Castle Java FIPS 1.0.0
    • byte-buddy 0.6.5
    • bzip2 1.0.2
    • c3p0 0.9.1.1
    • castor 0.9.5.4
    • Commons Cli 1.2
    • Commons Codec 1.3
    • Commons Codec 1.9
    • Commons Collections 3.2.2
    • commons dbcp 1.4
    • Commons httpclient 3.1
    • Commons IO 2.4
    • Commons Lang 3.3.2
    • Commons Logging 1.1.1
    • Commons Validator 1.4.0
    • commons-beanutils 1.9.2
    • commons-compress 1.10
    • commons-compress 1.12
    • commons-io 2.4
    • commons-lang 2.5
    • commons-lang 2.6
    • commons-lang3 3.4
    • Cordova (formerly PhoneGap) 4.1.1
    • cordova-plugin-inappbrowser 1.1.1
    • DataNucleus Maven Plugin 4.0.2
    • Eclipse ECJ 4.4.2
    • elasticsearch 1.5.2
    • expat 2.0.1
    • fastutil 7.0.12
    • flywaydb 4.0.3
    • Groovy 2.4.5
    • Guava 18.0
    • Guava 19.0
    • guava-io r03
    • guice 3.0
    • H2 1.4.190
    • hamcrest-integration 1.3
    • handlebars.js 1.3.0
    • Hibernate 5.0.1.Final
    • hibernate-jpa-2.1-api 1.0.0.Final
    • HikariCP-java6 2.3.12
    • HSQLDB 2.3.3
    • httpclient 4.0
    • httpclient 4.2
    • httpclient 4.2.1
    • httpclient 4.2.2
    • httpclient 4.3
    • httpclient 4.5.1
    • httpcore 4.4.5
    • hyperic-sigar 1.6.4
    • infinispan commons 7.2.5.final
    • infinispan-core 7.2.5.final
    • infinispan-persistence-soft-index 7.0.0.CR1
    • infinispan-spring4 7.2.5.final
    • jackson 2.8.3
    • jackson-annotations 2.5.4
    • jackson-annotations 2.6.1
    • jackson-annotations 2.6.3
    • jackson-core 2.5.4
    • jackson-core 2.6.3
    • jackson-databind 2.5.4
    • jackson-databind 2.6.3
    • jackson-dataformat-csv 2.5.4
    • jackson-dataformat-csv 2.6.3
    • jackson-datatype-hibernate4 2.6.3
    • jackson-datatype-json-org 2.6.3
    • jackson-module-jaxb-annotations 2.6.3
    • Java Deep-Cloning Library 1.9.2
    • Java Rest Client for jasper report server 6.1.0
    • Java-apns 1.0.0.Beta3
    • JavaPNS 2.2.1
    • javapns-jdk16 2.2.1
    • javax.ws.rs-api 2.0.1
    • javax-inject 1
    • jaxb-api 2.1
    • jaxb-api 2.2.12
    • jaxb-api 2.2.3
    • jaxrs-api 3.0.11
    • JBoss Logging 3.3.0.Final
    • jboss-ejb-api_3.1_spec 1.0.2.Final
    • JDBC 12.1.0.2
    • JDOM 2.0.6
    • Jersey 2.21
    • jersey client 2.22.1
    • Jettison 1.3.7
    • JNA 4.0.0
    • Joda-time  2.1
    • Joda-time  2.3
    • jquery-bonsai 2.1.0
    • jquery-qubit 2.0.5
    • jquery-validate 1.13.1
    • JSch 0.1.52
    • jstimezonedetect 1.0.6
    • js-url v2.0.2
    • junit 4.11
    • junixsocket 2.0.4
    • Kafka 2.11-0.9.0.1
    • kryo 3.0.3
    • kryo-serializers 0.36
    • libcurl 7.15.0
    • libcurl 7.18.2
    • libcurl 7.21.1
    • Libxml2 2.6.27
    • Libxml2 2.6.7
    • Log4cplus 1.0.2
    • Log4j 1.2.16
    • Log4j 1.2.17
    • Log4j 2.2
    • Logback 1.1.7
    • Lucene 4.10.4
    • mapdb 1.0.8
    • MariaDB connector/J 1.2.3
    • MIT Kerberos v5  release1.4
    • mokito 1.9.5
    • myfaces 1.1.4
    • not-yet-commons-ssl 0.3.10
    • NUNIT 2.2.8
    • Objenesis 2.2
    • ojdbc14 10.2.0.4.0
    • ojdbc6 11.2.0.1
    • OpenLDAP 2.1
    • OpenLDAP 2.3.20
    • OpenSAML 1.1b
    • OpenSSL 0.9.8.d
    • OpenSSL 0.9.8.h
    • OpenSSL 1.0.2g
    • OpenSSL 1.0.2i
    • OpenSSL FIPS Object Module 2.0.10
    • openstack4j 2.0.4
    • openstack4j-httpclient 2.0.4
    • Oracle Java Runtime Environment (JRE) 1.4.2_04
    • Oracle Java Runtime Environment (JRE) 1.8.0_112
    • Oracle Java Runtime Environment (JRE) 1.8.0_121
    • Oracle JDK (Java Development Kit) 1.6.0
    • org.eclipse.persistence.moxy 2.6.1
    • OrientDB 2.1.8
    • ow2- asm 4.1
    • OWASP Java Encoder 1.2
    • PCRE 6.3
    • PCRE 8.1
    • Push Plugin 2.5.0
    • Quartz 2.2.2
    • quasar-core 0.7.3
    • reactor-bus 2.0.5.RELEASE
    • SBLIM 2.2.5
    • Simple Logging Facade for Java (SLF4J) 1.7.7
    • sinonjs 1.15.4
    • slf4j-api 1.6.6
    • slf4j-api 1.7.2
    • spring framework 3.2.18.RELEASE
    • spring framework 4.1.3-RELEASE
    • spring framework 4.1.6.RELEASE
    • spring-framework 4.2.2.RELEASE
    • StringTemplate4 4.0.8
    • Struts 1.2.4
    • swagger 2.2.2
    • swagger-annotations 1.5.6
    • swagger-jersey2-jaxrs 1.5.6
    • SwaggerUI 2.1.4
    • tomahawk 1.1.5
    • Tomcat 4.1.31
    • Tomcat 7.0.69
    • Underscore.js 1.8.3
    • undertow-core 1.3.8.Final
    • versioneye 0.4.1
    • Woodstox 4.4.1
    • Xalan-J 2.5.2
    • Xerces-C 2.6.0
    • Xerces-C 2.8
    • Xerces-C 3.1.1
    • Xerces-J 2.9.1
    • XML Security Java 1.3
    • zip4j 1.3.2
    • Zlib 1.2.3
    • Zlib 1.2.5
    • ZThread 2.3.2