CA Business Intelligence Dashboards Release Notes

The CA Business Intelligence Dashboards (CABI) within CA Unified Infrastructure Management (CA UIM) use CABI Server. CABI Server provides rich reporting and integrates in-memory analysis capabilities. This article explains the new features in this release.
uim85
Before installing or upgrading your CABI server, read this topic and the Install or Upgrade CA Business Intelligence with CA UIM topic.
The CA Business Intelligence Dashboards (CABI) within CA Unified Infrastructure Management (CA UIM) use CABI Server. CABI Server provides rich reporting and integrates in-memory analysis capabilities. This article explains the new features in this release.
1
 
Installation and Upgrade Procedures
As of the CA UIM 8.5 release, the processes that you use to install or upgrade your CABI server differs based on several factors in your CA UIM environment. See the topic Install or Upgrade CA Business Intelligence with CA UIM for the full set of installation and upgrade procedures.
CA UIM Environment Requirements
The CABI requires the following components:
  • CABI is supported on all platforms, operating systems, and databases that are supported by UIM server and UMP. For more information about supported platforms, refer to the CA UIM Support Matrix (login required).
  • Deploy a new robot on the primary hub if a robot without UMP does not exist. For more information, see the Deploy Robots article.
User Accounts for Dashboards
Create and modify users through UMP in CA UIM. When a user is created in CA UIM, the same user is automatically created in CABI Server.
Users are not automatically deleted between CA UIM and CABI. When a user is deleted in CA UIM, the user still exists in CABI server to preserve any reports that the user might have created. You must manually delete a user in CA UIM and then in CABI server to completely remove the user. Because user permissions in CABI server are inherited from CA UIM, a deleted CA UIM user would typically not have access to CABI Server. The exception to this rule is if a user is created directly within CABI Server.
Using CABI Superuser
A default superuser account exists in CABI Server. Before you make any changes to the CABI server settings, use the export function in CABI server to back up your default configuration. For more information, see the CABI help.
You can use the superuser account to:
  • Manage CABI server settings
  • Configure custom data sources and domains
  • Delete users and organizations
  • Import and export reports
Permissions for Dashboards
The data a user can view is determined by their CA UIM origin. For more information about the types of users and their permissions, see Types of Users.
To use the dashboards, a CA UIM user must have the following ACL permissions:
  • List Viewer - To view reports
  • Report Designer - To edit and create dashboards and reports
The following accounts are set up in CABI as part of the installation:
  • The CABI_REST_ USER has ROLE_ SUPERUSER and ROLE_ ADMINISTRATOR
  • Any CA UIM bus user (non-account user) has ROLE_ADMINISTRATOR and can manage users and reports within an organization.
Do not modify the CABI_REST_ USER account in CABI Server. This account is required to synchronize users, roles, and organizations in CABI Server.
Hardware Requirements for CABI Server
  Ensure that your robot with CABI server meets the following minimum hardware requirements:
  • 10-GB free disk space
  • 8-GB memory
  • Four 2-GHz CPUs
New Features
Version 1.10
For a video overview of the CABI dashboards, see the topic How To Videos.
Predefined Dashboards
Dashboards exist for monitoring the following applications:
  • Summary and default dashboards - You can use these dashboards to view alarms for devices, probes, and groups in a CA UIM environment. These dashboards work with any probe in your CA UIM environment.
    Example Summary Dashboard
  • Azure - Requires the azure probe version 3.00 or later.
    Example Azure Dashboard
Version 1.00
You access the dashboards through the Unified Dashboards portlet. The ump_cabi package that updates the portlet is automatically installed with UMP. CABI Server and the dashboards are available for use after deploying the cabi probe. The cabi probe package is added to the archive after you install or update CA UIM to version 8.47 or later.  This release supports Ad Hoc reporting and provides predefined dashboards for supported probes.
Predefined Dashboards
Dashboards exist for monitoring the following applications:
  • AWS - Requires aws probe version 5.10 or later
  • Docker - Requires docker_monitor probe version 1.31 or later
  • Nutanix - Requires nutanix_monitor probe version  1.31 or later 
  • OpenStack - Requires openstack probe version 1.20 or later
  • SAP - Requires sap_basis probe version 1.30 or later
New Packages
Version 1.10
The following packages are delivered with the CA UIM version 8.5 release:
  • cabi probe package version 1.10 - Installs CABI version 6.2
  • ump_cabi version 1.10
  • uim_core_dashboards_pack.zip version 1.0
  • uim_azure_dashboards_pack.zip version 1.0
Version 1.00
The following packages are delivered with the CA UIM version 8.47 release:
  • cabi probe package version 1.00 - Installs CABI version 6.2
  • ump_cabi version 1.00
Known Issues
Version 1.10
The following known issues exist in this release:
  • The time zone for all time sequence reports is displayed in the time zone of the CABI server.
  • The alarm severity icons fail to load on an intermittent basis. Refresh the page to resolve this issue.
  • If you use an Oracle database for CABI, the Minimum Alarm Level filter for the Probes by Alarm report (dashlet) does not work. The report shows all alarm levels.
  • If you use an Oracle database for CABI, the Minimum Alarm Level filter for the Top N Devices by Alarm report (dashlet) does not work correctly. The report filter shows the alarm levels in decreasing order of severity. To work around this issue, adjust the filter to display the maximum alarm level for the report.
Version 1.00
The following known issues exist in this release:
  • CA UIM bus user accounts with special characters (# !~  $ % ^ & * ,  (  - + 、 [ { " | \ / ? < > ) are not automatically added to CABI. No work-around exists at this time.
  • Special characters (# !~  $ % ^ & * ,  (  - + 、 [ { " | \ / ? < >. ) in CA UIM accounts are converted to underscores when the accounts are added to CABI. This conversion can lead to accounts with duplicate names. If a collision occurs, only the first account is added to CABI. Do not create accounts with the same name where the only differentiation is a dash or underscore. For example, do not create two accounts with the names test_1 and test-1. This example results in a collision.
  • The CABI Server robot and UMP robot must use the same operating system.
  • Bus users should not share an ACL with LDAP users, or bus users will inherit LDAP accounts. To avoid this issue, create a new 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. This is a known Jaspersoft issue.
  • Wasp generates the following error:
    Sep 19 10:23:51:030 INFO  [http-bio-80-exec-20258, com.ca.cabi4uim.sso.PortletAccessor] ERROR: ensureUserExistsForSSO - Response PDS from cabi probe indicates failure, value for success was true
    This error is harmless and can be ignored.
Resolved Issues
The following known issues have been resolved:
  • (Fixed version 1.10) The CABI Server robot and UMP robot must use the same operating system.
  • (Fixed version 1.10) Wasp generates the following error:
    Sep 19 10:23:51:030 INFO  [http-bio-80-exec-20258, com.ca.cabi4uim.sso.PortletAccessor] ERROR: ensureUserExistsForSSO - Response PDS from cabi probe indicates failure, value for success was true
    This error is harmless and can be ignored.