CA Business Intelligence JasperReports Server with CA UIM Release Notes

The CA Business Intelligence (CABI) Dashboards within CA UIM use CA Business Intelligence JasperReports Server (CABI Server). CABI Server provides rich reporting and integrates in-memory analysis capabilities. This article explains the new features in this release.
uim902
cabi_rn
The CA Business Intelligence (CABI) Dashboards within CA UIM use CA Business Intelligence JasperReports Server (CABI Server). CABI Server provides rich reporting and integrates in-memory analysis capabilities. This article explains the new features in this release.
 For a matrix of supported CABI package versions, see CA Business Intelligence with CA UIM.
 
Contents
 
 
 
2
 
2
 
 
CA UIM Environment Requirements
The CA Business Intelligence dashboards require the following components:
April 2019
 
New Features
 
The following updates are in the release:
  • The cabi probe 4.1.0 is updated to deploy CABI Server version 7.1.1. The probe also supports Microsoft SQL Server 2016.
  • Added the Availability Reports which enable you to view availability of devices and groups. For more information, see Availability Reports in Probes Documentation Space.
 
New Packages
 
The following new packages are in the release:
  • uim_cabi_availability_report_pack version 1.00 - Install this package to deploy the Availability reports.
  • cabi probe package version 4.1.0 - Install this package to deploy an instance of CABI Server on a robot. This configuration simplifies the CABI Server installation process if you only need to use CABI Server with CA UIM. This version of the probe is required to support reports.
  • ump_cabi portlet version 4.10 - Install this package to view CABI Dashboards in CA UIM 9.0.2.
  1. The cabi 4.10 probe supports TLS v1.2 when communicating with the UIM database: Microsoft SQL Server - 2012, 2014, 2016, and Oracle - 11.2 and 12.1.
  2. The cabi 3.40 probe, available with UMP 9.0.2 HF2, supports TLS v1.2 when communicating with the UIM database: Microsoft SQL Server- 2012, 2014, and Oracle - 11.2 and 12.1. For more information about how to apply the UMP 9.0.2 HF2 for CABI TLS functionality, see UMP 9.0.2 HF2.
  3. The cabi 3.32 probe does not support TLS v1.2 when communicating with the UIM database: Microsoft SQL Server or Oracle. As a result, you cannot view the Operator Console home page, OOTB CABI dashboards, and OOTB CABI reports.
  4. TLS v1.2 support is not enabled by default when you install CA UIM 9.0.2.
February 2019
  • The CABI TLS v1.2 feature is supported only for UMP 902 HF2 for SQL Server and Oracle databases. The supported SQL Server versions are limited to 2012 and 2014 only. 
December 2018
New Features
The following updates are in the release:
  • The cabi probe is updated to deploy CABI Server version 6.4.3. The cabi probe now supports Transport Layer Security (TLS) v1.2 when communicating with the UIM database: Oracle or Microsoft SQL Server. This support enables the UIM Server to establish secure communication with the UIM database.
  • The cabi_external probe is updated to deploy CABI Server version 6.4.3. The cabi external probe now supports Transport Layer Security (TLS) v1.2 when communicating with the UIM database: Oracle or Microsoft SQL Server. This support enables the UIM Server to establish secure communication with the UIM database.
     CABI is not supported for TLS v1.2 enabled UIM environments which have SQL Server 2016 and 2017 as the database. Currently, Jaspersoft does not provide support for TLS v1.2 on SQL Server 2016 and 2017. Therefore, if TLS v1.2 is enabled in your CA UIM environment, and your database is SQL Server 2016 or 2017, then CABI Dashboards will not be supported. As a result, you cannot view CABI reports in CA UIM.
New Packages
The following new packages are in the release:
  • cabi probe package version 3.40 - Install this package to deploy an instance of CABI Server on a robot. This configuration simplifies the CABI Server installation process if you only need to use CABI Server with CA UIM. This version of the probe is required to support reports.
  • cabi_external probe package version 3.40 - Install this package to deploy a probe that functions as a gateway for a separate CABI Server instance. This configuration allows you to share the CABI Server instance with CA UIM and multiple CA Agile Operations products. This version of the probe is required to support reports.
  • ump_cabi portlet version 3.40 - Install this package to view CABI Dashboards in CA UIM 9.0.2.
October 2018
New Features
The following updates are in the release:
  • When sub-tenancy is enabled for your CA UIM environment, user origin settings are applied and each sub-tenant has access to their dashboards data only.
New Packages
The following new packages are in the release:
  • cabi probe package version 3.32 - Install this package to deploy an instance of CABI Server on a robot. This configuration simplifies the CABI Server installation process if you only need to use CABI Server with CA UIM. This version of the probe is required to support reports.
  • cabi_external probe package version 3.32 - Install this package to deploy a probe that functions as a gateway for a separate CABI Server instance. This configuration allows you to share the CABI Server instance with CA UIM and multiple CA Agile Operations products. This version of the probe is required to support reports.
  • ump_cabi portlet version 3.32 - Install this package to view CABI Dashboards in CA UIM 9.0.2.
  • uim_cabi_health_report_pack version 1.31 - Install this package to deploy the Health reports.
August 2018
New Packages
The following new packages are in the release:
  • cabi_external probe package version 3.30 - Install this package to deploy a probe that functions as a gateway for a separate CABI Server instance. This configuration allows you to share the CABI Server instance with CA UIM and multiple CA Agile Operations products. This version of the probe is required to support reports.
April 2018
New Features
The following updates are in the release:
  • The cabi probe is updated to support the latest wasp 9.0.1 release.
  • The CA Business Intelligence UMP portlet is updated to support the version 3.30 release.
  • Added new dashboards for monitoring VMware.
  • Added new dashboards for monitoring MCS (Monitoring Configuration Service).
New Packages
The following new packages are in the release:
  • cabi probe package version 3.30 - Install this package to deploy an instance of CABI Server on a robot. This configuration simplifies the CABI Server installation process if you only need to use CABI Server with CA UIM. This version of the probe is required to support reports.
  • ump_cabi portlet version 3.30 - Install this package to view CABI Dashboards in CA UIM.
  • uim_vmware_dashboards_pack version 1.00 - Install this package to deploy VMware dashboards. This package requires CA UIM, uim_core_dashboards_pack.zip version 2.40, and vmware probe version 6.87 or later.
  • uim_mcs_dashboards_pack version 1.0.0 - Install this package to deploy MCS dashboards. This package requires CA UIM version, uim_core_dashboards_pack.zip version 2.40, and atleast one MCS profile must exist.
November 2017
New Features
The following updates are in the release:
  •  
     
    Changed the deployment process for bundled CABI Server configuration and external CABI Server configuration. 
     
    The significant changes are as follows:
    • There is now a specific probe to use for each configuration. Use the 
      cabi
       probe for the bundled configuration and the 
      cabi_external
       probe for the external configuration.
    • Removed the requirement for MCS.
  • The cabi probe and cabi_external probe packages automatically deploy any package dependencies that exist in the archive. The dependencies include the uim_core_dashboards_pack and report packages.
  • Added a library of reports that you can access from dashboards.
    An additional requirement exists for the CA Business Intelligence (CABI) Unified Reporter (UR) reports that utilize data from the vmware probe. The vmware probe must be deployed and configured using MCS. For more information, see vmware MCS Profile Type Configuration.
  • Added the ability to view Unified Reporter reports in the CA Business Intelligence dashboards.
  • Added legacy dashboard packages to the Archive.
  • Added new dashboards for monitoring SAP.
  • Added new dashboards for monitoring Citrix.
  • Added the ability to migrate custom Unified Reporter reports to the CA Business Intelligence dashboards.
  • Added UIM Metric Topic to expand reporting capabilities. The UIM Metric Topic allows you to create Ad Hoc views with data from multiple metrics and devices
  • Added the ability to control the frequency of backups for probe and dashboard upgrades. The following keys were added to the cabi and cabi_external probes raw configuration: auto_backup_fequency_in_hours, auto_backup_on_import_enabled, auto_backup_on_import_max_time_in_secs. For more information, see the optional tasks in Install or Upgrade for a Bundled CA Business Intelligence JasperReports Server or Install or Upgrade for an External CA Business Intelligence JasperReports Server.
New Packages
The following new packages are in the release:
  • cabi probe package version 3.20 - Install this package to deploy an instance of CABI Server on a robot. This configuration simplifies the CABI Server installation process if you only need to use CABI Server with CA UIM. This version of the probe is required to support reports.
  • cabi_external probe package version 3.20 - Install this package to deploy a probe that functions as a gateway for a separate CABI Server instance. This configuration allows you to share the CABI Server instance with CA UIM and multiple CA Agile Operations products. This version of the probe is required to support reports.
  • ump_cabi portlet version 3.20 - Install this package to update the cabi portlet to support version 3.20 of the cabi probe.
  • uim_core_dashboards_pack version 2.40 - Install this package to update your dashboards to support version 3.20 of the cabi probe.
  • uim_aws_dashboards_pack.zip version 2.40 - Install this package to update the localization support for the AWS dashboards. This package requires uim_core_dashboards_pack.zip version 2.40 and aws probe version 5.25 or later.
  • uim_azure_dashboards_pack.zip version 2.40 - Install this package to update the localization support for the Azure dashboards. This package requires uim_core_dashboards_pack.zip version 2.40 and azure probe version 3.02 or later.
  • uim_sap_dashboards_pack version 1.00 - Install this package to deploy SAP dashboards. This package requires uim_core_dashboards_pack.zip version 2.40 and sap_basis probe version 2.01 or later.
  • uim_citrix_dashboards_pack version 1.00 - Install this package to deploy Citrix dashboards. This package requires uim_core_dashboards_pack.zip version 2.40 and xendesktop probe version 4.20 or later.
  • uim_unified_reporter_pack version 1.02 - Install this package to deploy the CABI for CA UIM library reports for applications, DBs (database), networks, and servers.
    An additional requirement exists for the CA Business Intelligence (CABI) Unified Reporter (UR) reports that utilize data from the vmware probe. The vmware probe must be deployed and configured using MCS. For more information, see vmware MCS Profile Type Configuration.
  • uim_cabi_health_report_pack version 1.20 - Install this package to deploy the Health reports.
Fixed Defects
The following known issues have been resolved:
  • Version 3.0 dashboards not displaying metric detail data - The metrics details reports now display metric data. (Case 008382, 00847337)
July 2017
New Features
The following updates are in the release:
  • The cabi probe was updated to support deployment in either a Bundled mode or an External mode.
    •  
      Bundled mode
      Bundled mode installs and configures an instance of CA Business Intelligence JasperReports Server (CABI Server) on a robot. This mode simplifies the CABI Server installation process if you only need to use a JasperReports Server (CABI Server) instance with CA UIM.
    •  
      External mode
      External mode allows a pre-existing CA Business Intelligence JasperReports Server (CABI Server) instance to communicate with CA UIM. This is a CABI Server instance that is not deployed through the cabi probe. This mode reduces the number of CABI Server instances that you must deploy and maintain. You can share a single CA Business Intelligence (CABI) server instance with multiple CA Agile Operations products. For more information, see Unified Dashboards and Reporting for Infrastructure Management. 
  • The CA Business Intelligence core dashboards were updated to support the version 3.00 release.
New Packages
The following packages were added to the release:
  • cabi-mcs-template version 3.00 - Install this package to configure version 3.00 of the cabi probe.
  • cabi probe package version 3.00 - Install this package to upgrade to the latest cabi probe version. This version of the probe deploys CABI Server version 6.3 when configured in bundled mode.
  • ump_cabi version 3.00 - Install this package to update the cabi portlet to support version 3.00 of the cabi probe.
  • uim_core_dashboards_pack.zip version 2.20 - Install this package to update your dashboards to support version 3.00 of the cabi probe.
Known Issues
The following known issues exist:
Error 403 (Forbidden) message for CABI dashboards
(Reported version 3.00) To resolve this issue check your cabi probe and ump_cabi package versions. This error occurs when incompatible package versions are installed. For example, your cabi probe is version 3.0 and your ump_cabi version is 2.0. For more information about versions, see CA Business Intelligence with CA UIM. Download and deploy the ump_cabi portlet package to the UMP server and restart wasp on the UMP server.
CABI Server installation fails when CA UIM is upgraded from version 8.31 to version 8.5.1, and the CA UIM database is MSSQL.
(Reported version 2.00) To resolve this issue you must restart data_engine.
  1. Go to the data_engine configuration GUI.
    Data Engine Configure Menu  
  2. Locate the Data Source setting.
    Data Source Setting  
  3. Reapply the configuration. To activate the Apply button, make a minor change and then revert to the original setting.
    Reapply Configuration  
  4. Restart data_engine.
      Data Engine Restart  
  5. Reinstall CABI Server.
The Java version was updated to Java 1.8 starting with CA UIM 8.5.1.
(Reported version 2.00) You must upgrade any self-signed certificates that are 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.
The AM, PM, and Interval labels do not appear when you export the Open Alarms Details report in a non-English language.
(Reported version 2.00) No work-around exists at this time.
The CABI portlet icons fail to load on an intermittent basis.
(Reported version 1.10) Refresh the page to resolve this issue.
The rendering of some dashboards might be slow in large-scale environments collecting a large amount of QoS data.
(Reported version 1.10) No work-around exists at this time.
CA UIM bus user accounts with special characters (#?~  $ % ^ & *,  (- + ? [{ " | \ /? < >) are not automatically added to CABI.
(Reported version 1.00) No work-around exists at this time.
CABI Installation Fails When Using Special Characters in UMP and LDAP Account Names
(Reported version 1.00) When you use special characters (\, |, [ ], `, ", ', ~, !, #, $, %, ^, &, [,], *, +, =, ;, * :, ?, <, >, }, {, ), (, ], [, /, @) in the UMP or LDAP account names, account synchronization with CABI fails which results in a failed installation.
Bus users should not share an ACL with LDAP users, or bus users inherit LDAP accounts.
(Reported version 1.00) To avoid this issue, create an ACL to configure for use with LDAP and leave the default ACLs in place. This ACL allows the CA UIM administrator to create Bus users without association to any LDAP account link. For more information, see the Connecting Access Control Lists to LDAP Users section in Enable Login with LDAP.
Data points are offset when you hover over a dashlet in a maximized view.
(Reported version 1.00) This issue is a known Jaspersoft issue.