Software Release Notice
for
CA Infrastructure Management
Release 2.3.3
Last revised 7/1/14

CA Performance Center Installation Guide

Data Aggregator Installation Guide.

Resolved Issues

(Back to OVERVIEW for Release_2.3.3_July_Update)

Symptom: There were some database changes to synchronize table sizes in the netqosportal and event managment database not related to any defect. Due to a incorrect file specification, these were not applied in the 2.3 upgrade.
Resolution: Added a new Event Managment schema version script with the same changes.
(Release_2.3.3_July_Update, 252142)

Symptom: LDAP Login fails with user name that includes both lower and upper case letters.
Resolution: LDAP authentication will convert the user name to lower case before checking it against the LDAP server.
(Release_2.3.3_July_Update, 262211, 21563728-01)

Symptom: There are two Y axis for the same values in the Trend chart.
Resolution: The ribdocs now contain the correct units for the baseline metrics instead of float.
(Release_2.3.3_July_Update, 289491, 21693399-01;21743166-01)

Symptom: When customizing eHealth in a CA Performance Center view, if the context value is changed on the view setting form an error 500 exception is generated.
Resolution: Fixed context modifications error when attempting to configuration eHealth views with CA Performance Center.
(Release_2.3.3_July_Update, 298179, 21729429-01)

Symptom: Single Sign-On authentication using SAML2 fails if the IDP signs the response but not the assertion.
Resolution: SAML2 authentication modified to validate the response's signature (if signed), and then validate the assertion's signature (if signed).
(Release_2.3.3_July_Update, 300130, 21731200-01 )

Symptom: Running SsoConfig can generate a NullPointerException when using the Reset Value functionality.
Resolution: Fixed the Reset Value functionality so it will not result in NullPointerExceptions.
(Release_2.3.3_July_Update, 300298, 21737234-01)

Symptom: Synchronization Failure of Data Aggregator with Performance Center after a discovery of new items.
Resolution: Enforced a length limit of 255 characters for item description fields.
(Release_2.3.3_July_Update, 302927, 21771721-01)

Symptom: Authentication using SAML2 fails with NullPointerException due to missing RelayState.
Resolution: SAML2 authentication modified to print an error message in the Single Sign-On log when missing or malformed RelayState is encountered. Documentation updated on how to add RelayState to IDP, if needed. Enhanced debug of SAML2 authentication to try and diagnose future problems easier.
(Release_2.3.3_July_Update, 304409, 21765068-01)

Symptom: Server names are truncated in PDF reports.
Resolution: Modified the code so that long server names will now wrap instead of being truncated.
(Release_2.3.3_July_Update, 307133, 21795891-01)

Symptom: After rebooting the server your Data Aggregator runs on, the Data Aggregator is unable to start up successfully.
Resolution: The ActiveMQ service is now setup properly for both fresh install and upgrade cases.
(Release_2.3.3_July_Update, 308733, 21810484-01)

Symptom: On a pre-2.3.3 Performance Center installation where Anomaly Detector data source was added, upgrading to 2.3.3 could result in a MigrateDb error during upgrade.
Resolution: Updated the Performance Center installer to not error if the Anomaly Detector data source type is already in the database during MigrateDb.
(Release_2.3.3_July_Update, 309949, 21818714-01)

Symptom: On-Demand report limits the list of components rendered based on the number of metrics picked.
Resolution: Fixed On-Demand Report View Type "Chart Per Metric with Multiple Items" with Metric Calculate Level "by Component" to properly report limit of 15 components on a single chart.
(Release_2.3.3_July_Update, 310035, 21817370-01)

Symptom: Stored events in the Event Manager database are not pruned according to the specified retention time (which defaults to 30 days). You may also see errors similar to the following in the MySQL error log:2014-06-09 00:00:00 19583 [Note] Event Scheduler: [root@localhost].[em.e_rotate_event_partitions] event execution failed.2014-06-10 00:00:00 19583 [ERROR] Event Scheduler: [root@localhost][em.e_rotate_event_partitions] Data too long for column 'l_old_partitions' at row 217.
Resolution: Modified the stored procedure to make some arrays used to build dynamic queries larger. Added some extra code to ensure clean up of very old records (older than the retention time).
(Release_2.3.3_July_Update, 312977, 21798990)