Clarity PPM 15.6.0.1 and Jaspersoft Cumulative Patch README Files

Cumulative patches for cappm 15.6 and Jaspersoft for PPM are periodically available. Before applying a patch, see the README for important information.
ccppmod156
Cumulative patches for 
Clarity PPM
 15.6 and Jaspersoft for PPM are periodically available. Before applying a patch, see the README for important information.
  • SaaS Customers: 
    Contact CA Support to request and schedule patch installation on specific CA PPM instances in the CA On Demand Portal. Any fixes for reports are automatically deployed in your SaaS environment. Notifications for scheduled mandatory Jaspersoft patches are provided by email to the customer support contacts on file. 
  • On-premise Customers:
     To install a patch or update reporting content, download the patch from CA Support and follow the README instructions on this page. 
 
2
 
 
HID_clarity_readme
Clarity PPM 15.6.x Cumulative Patch Summary
Because patches are cumulative, when you install a single patch, it includes all the fixes from all previous patches.
GA Date
Patch
May 8, 2019
15.6.0.1
README: Clarity PPM 15.6.0.1 Patch
 
4
 
3
 
 
Patches are intended to be timely fixes and are not fully regression or integration tested, and are only tested against the issues listed below. CA feels confident that this patch will resolve the addressed problems, but customers should be aware that a patch could have adverse side effects to the function of their CA PPM application. Customers should not apply patches directly to production systems without first verifying in a test environment. If any issues arise in the installation or use of this patch, contact CA Support.
 
This patch contains the following files:
  • README.txt -> This file
  • install.sh -> Unix installer
  • install.bat -> Windows installer
  • install.xml -> Ant install script
Prequisites:
Install only on systems running the version stated above.
Install the Patch
 Patch installation is for on-premise administrators only. These steps do not apply for SaaS customers.
Follow these steps:
1. Back up all files and the database on the target system.
 
2. On the CSA server, copy the installer into a temp directory.
 
3. Navigate to the temp directory and enter the following command to extract the contents:
    jar xvf <patch_jar_file>
4. Stop all local nsa, app and bg services:
 service stop nsa app bg Allow databases and reports to continue running.
5. From the temp directory, enter the following command to execute the installer script: install.bat or install.sh
6. Follow the remaining on-screen instructions to complete the installer script.
7. Start all services: service start all.
8. If you are running multiple servers in a cluster:
    a. Log in to the CSA and go to the All Services page to shut down any remote app and bg services.
    b. Go to the Distribute All page, select remote servers, and click Distribute.
    c. Return to the All Services page to restart services when the distribution is complete. If you currently use or want to use the new Jaspersoft Reports and Data Warehouse, choose Step 9 or Step 10. If you do not use these 
    features, skip Steps 9 and 10. 9. If you are applying this patch and you have already configured Jaspersoft Reports and the Data Warehouse:
    a. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
    admin jaspersoft keystore
    b. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance     directory>/webapps/<jaspersoftContext>/WEB-INF/config
    c. Enter the following command to upgrade the report content:
    admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50
    d. Restart all PPM services.
    e. Run the Load Data Warehouse Access Rights job.
 
10. If you are applying this patch and you want to use the new Jaspersoft Reports and Data Warehouse but have not yet configured them:
    a. From <install_dir>/bin directory command prompt, enter the following command to generate keystore:
        admin jaspersoft keystore
    b. Copy the keystore files generated in <install_dir>/config directory to <Jaspersoft Tomcat Instance:
        Directory>/webapps/<jaspersoftContext>/WEB-INF/config
    c. Enter the following command to install the release content:
        admin content-jaspersoft csk -userName <superuser> -password <password> -retryCount 50
        This command imports jaspersoft_csk.zip followed by the file that has patch content (file name for patch content contains         jaspersoft_csk_upgrade).
 
    d. If you encounter any error during the import of the patch content, enter the following command to re-import the patch content:
    admin content-jaspersoft csk -userName <superuser> -password <password> upgrade -retryCount 50 force
 
    e. Configure the Data Warehouse section in CSA. See CSA: CA PPM System Administration at docops.ca.com/ppmop.
 
    f. Enter the following command from the <install_dir>/bin directory command prompt to apply the data warehouse patch content:
    admin db dwh-upgrade -Dupgrade.phase=maintenance
 
    g. Restart all PPM services.
 
    h. Run the Load Data Warehouse Access Rights job.
Uninstall the Patch
Follow these steps: 
1. Stop all local nsa, app, and bg services: 
    service stop nsa app bg
 
2. Restore the installation files and database from the backups above.
 
3. Start all services:
    service start all
 
4. If running multiple servers in a cluster:
    a. Log in to CSA and go to the All Services page to shut down any remote app and bg services.
    b. Go to the Distribute All page, select remote servers and click Distribute.
    c. Return to the All Services page to restart services when the distribution is complete.
 
ISSUES FIXED IN PATCH 15.6.0.1
DE48121: Security Fix
This security defect was resolved in this patch. The steps to reproduce the defect are omitted for security reasons.
DE48094: Security Fix
This security defect was resolved in this patch. The steps to reproduce the defect are omitted for security reasons.
DE44336: Copy Tasks from Previous Week adding Other Work
Steps to Reproduce:
 
1. Add user to Other Work Team.
 
2. Post time without Other Work item.
 
3. On following week, populate the timesheet with copy from previous time period.
Expected Results: Other work should not be on there.
 
Actual Results: Other work item shows.
DE48120: Security Fix
This security defect was resolved in this patch. The steps to reproduce the defect are omitted for security reasons.
DE46774: Performance of Project Task list page is slow when calculated attribute is included
Steps to Reproduce:
Follow these steps: 
 
1. Log in to Classic PPM.
 
2. Navigate to Object --> Task and create a calculated attribute.
 
Data Type: Aggregated - Number , Expression: AGG_Sum(assignment.prpendactsum)
3. Place the attribute on Project and task list page.
Expected Results: With calculated attribute in the list page the performance should be better than what we are getting now.
 
Actual Results: With the calculated attribute the performance of list page goes from 5 seconds to 1 minute.
DE48534: "Error 401 - Unauthorized" when browsing tasks on the Classic PPM Timesheet page
Steps to Reproduce:
 
Follow these steps:
1. Configure a user that has only the default rights and 
Timesheet - Navigate
.
 
2. Open the user for Time Entry.
 
3. Set the user 
Track Mode
 to 
PPM
.
 
4. Assign the user to one or more tasks.
 
5. Log in to Classic PPM as the user from Step 1, open a timesheet, and click the 
Add Task
 button.
    The task list appears.
5A. If more than one page of tasks has been configured, change to page 2.
Expected Results: Page 2 tasks appear.
 
Actual Results: Error 401 - Unauthorized. You are not authorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.
5B. If less than one page of tasks has been configured, try to sort the tasks by any available column. (This is also true with more than one page of tasks.)
Expected Results: Tasks are sorted by the selected column.
 
Actual Results: Error 401 - Unauthorized. You are not authorized to view the page. If you are sure you have access, try logging in again or contact your system administrator.
 
README: JasperReports Server 6.4.2 for Clarity PPM
JasperReports Server 6.4.2 was a maintenance release that included security updates and improvements requested by customers. CA PPM 14.3 and higher on-premise customers must use the CA PPM Jaspersoft installer to apply it, which is a customized wrapper written on top of the original third-party installer.
JasperReports Server 6.4.2 is no longer supported with CA Clarity 15.6 or newer releases. To receive technical support, and to patch vulnerabilities in 6.4.2, upgrade to Jaspersoft 7.1.
Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting. Do not install software, download patches, or apply hot fixes directly from TIBCO.
After installing or upgrading to CA PPM 15.6, you must install or upgrade your reporting environment using the installer provided by CA. Customers can upgrade the same 6.4.2 database to 7.1 or perform a fresh install with 7.1 (and optionally migrate their reporting content). You cannot remain on JasperReports 6.2.1 or 6.4.2. To benefit from the fixes and improvements in 7.1, we recommend that you upgrade to 7.1 as soon as possible. JasperReports Server 6.2.1 is not supported beyond June 28, 2018, its End-of-Support (EOS) milestone. Clarity PPM 15.6 does not support Jaspersoft 6.4.2.
For Clarity PPM SaaS customers, you can arrange to have these upgrades performed for you.
The 6.4.2 update resolves a number of security vulnerabilities associated with 6.2.1, supports same-database upgrades from the previous 6.2.1 release, and introduces new dashboard improvements. 
Your upgrade to 7.1 might require you to first update to 6.4.2. For example, you have 15.1 with Jaspersoft 6.2.1. When you upgrade to 15.6, your reporting environment remains at 6.2.1. Upgrade to 6.4.2 first and then upgrade to 7.1.
JasperReports Server 7.1 for Clarity PPM README (Recommended Version)
JasperReports Server 7.1 is the newest release that includes new features, enhancements, and security updates. All CA PPM SaaS customers automatically receive this new release. CA PPM on-premise customers must use the CA PPM Jaspersoft installer to apply it. The installer is a customized wrapper written on top of the original third-party installer.
After installing or upgrading to CA PPM 15.6, you must install or upgrade your reporting environment using the installer provided with CA PPM. On-Premise customers can upgrade the same database to 7.1, or perform a fresh install of 7.1, and optionally migrate their reporting content. You cannot remain on JasperReports 6.2.1 (supported ended June 28, 2018) or 6.4.2 (not compatible; the native reporting solution certified for 15.5.1, 15.6, or higher is Jaspersoft 7.1). Due to security fixes, we recommend that customers on all releases of CA PPM upgrade to 7.1 as soon as possible.
 
Highlights of the 7.1 release include
:
  • Resolves a number of security vulnerabilities associated with previous releases including 6.4.2.
  • Supports same-database upgrades from the previous 6.4.2 release.
  • New Visualize.js
  • New Jaspersoft Studio data source support for domains and TIBCO Spotfire® information links
  • Improved JasperMobile App Experience
  • JasperReports engine simple text in field property expressions
  • TIBCO Datasource Visualization JDBC driver
  • Native Java 8 support (no longer supports Java 7, SOAP APIs, and Jaspersoft REST API v1.0)
  • Security Fixes
  • New Ad Hoc Views
HARDWARE AND SOFTWARE REQUIREMENTS
 
  • See the CA PPM Release Notes and TIBCO Documentation.
  • CA PPM SaaS customers enjoy an automatic upgrade to JasperReports 7.1.
  • CA PPM 15.6 on-premise customers must download the CA PPM Jaspersoft 7.1 installer, which is a customized wrapper written on top of the original third-party installer. Only the CA installer can be used to install Jaspersoft and integrate it with CA PPM for reporting.
 
Jaspersoft Upgrade Tips
:
  • For best results, always clear the browser cache on each client workstation after installing, upgrading, or patching Jaspersoft.
  • The Create and Update Jaspersoft Users job Full Sync option deletes all user folders with no content.
  • Create a small amount of custom Jaspersoft folders for each team. For example, only for PPM admins, project managers, and a few business analysts.
  • If this is not convenient, create users in PPM and place a small file inside each folder to avoid it from being deleted.
  • For better performance, do not create more than 500 user folders.