Upgrade Jaspersoft and Migrate Advanced Reporting Content

CA PPM SaaS customers enjoy an automatic upgrade to the latest release of JasperReports (7.1 is now available to replace 6.4.2).
CA PPM SaaS customers enjoy an automatic upgrade to the latest release of JasperReports (7.1 is now available to replace 6.4.2).
CA PPM on-premise customers can decide to upgrade now or defer until a future CA PPM upgrade. For example, you are on 15.2 with JasperReports 6.4.2. You will upgrade to CA PPM 15.6 in 2019. At that time, your reporting solution will also be upgraded to JasperReports 7.1. As an on-premise customer, if you decide to upgrade, you must use the CA PPM Jaspersoft installer, a customized wrapper written on top of the original third-party installer. Only the CA installer (a ZIP archive you can download) can be used to install Jaspersoft and integrate it with CA PPM for reporting.
JasperReports Server 6.4.2 is a maintenance release and 7.1 is a new release. Both include improvements requested by customers. For security and new features, we strongly recommend upgrading to 7.1. For a summary of the changes, see CA PPM and Jaspersoft Cumulative Patch README Files. For information about the status of specific cases, visit TIBCO Jaspersoft Technical Support (http://support.tibco.com). 
In CA PPM SaaS environments, your Jaspersoft server is upgraded for you when you decide to upgrade to a new CA PPM release. However, you can migrate your advanced reporting content. See Export, Import, or Migrate Advanced Reporting Content
Jaspersoft 7.1 Advanced Reporting and Analytics
All supported releases of CA PPM now include support for the performance and security updates in Jaspersoft 7.1 (strongly recommended), with 6.4.2 also available. CA PPM 15.5.1 on-premise and all SaaS environments include Jaspersoft 7.1.
For on-premise customers, the Jaspersoft installer for both versions is similar and prompts you for an installation type: 
fresh installation
. You can install a new report server database or perform an in-place upgrade of your existing report server database. 
Although Jaspersoft 6.4.2 is a maintenance update and 7.1 represents a new release, and neither are labeled
, their upgrade steps are relatively easy, similar to a patch. You can download 7.1 and install or upgrade much like a patch.
If you choose 
, the following choices appear in the installer command lines:
Select Installation Type: 1) Fresh Installation 2) Upgrade Installation Type selected: upgrade
Select Upgrade Method:
1) New DB Upgrade - New Jaspersoft Report Server database will be used for upgrading to 6.4.2 or 7.1 2) Same DB (in-place) Upgrade - Existing Jaspersoft Report Server database will be upgraded to 6.4.2 or 7.1
: A
Same DB
upgrade can fail for one or more of the following reasons:
  • Your are running an unsupported release of Jaspersoft. The minimum Jaspersoft version supported for a
    Same DB
    upgrade is 6.2.1.
  • You are running an unsupported release of Tomcat. The minimum version supported is 7.0.x, and 8.5.x is recommended. Jaspersoft 6.4.2 requires Tomcat 8.5.13 or higher. For Jaspersoft 7.1, we recommend Tomcat 8.5.30.
  • You are attempting to upgrade Jaspersoft on a server with an unsupported release of Oracle or MS-SQL. The minimums for CA PPM 15.4 are MS-SQL Server 2014 or Oracle 12cR2.
: If you are upgrading from an older release and older database, you might also need to upgrade to a temporary intermediate release
you can upgrade your database. See the upgrade scenarios under
Upgrade Enhancements
later on this page for guidance. Same DB upgrades require that you already have Oracle 11g R2, Oracle 12c R2, or Microsoft SQL Server 2014.
Jaspersoft and CA PPM UI Themes 
To support a consistent viewing experience, Jaspersoft theme cascading style sheets (CSS) updates are included in the CA PPM Studio user interface themes. Application and reporting themes are generally consistent.
Upgrade Action
: No action is required unless you applied customizations. New releases of CA PPM attempt to provide backward compatibility; however, any customizations from a previous release may no longer be supported. Review any modified or custom themes after every major release. Update any required images, colors, font sizes, spacing parameters, or other details.
The following points summarize the behavior of UI themes when navigating between Classic CA PPM pages and Jaspersoft Advanced Reporting pages embedded in CA PPM:
  • You select one of the available default CA PPM Studio UI themes. The Advanced Reporting user interface also appears in the same theme.
  • You edit one of the default UI themes. Your changes are not visible in Advanced Reporting until you log out and log back in again.
  • You configure a new custom UI theme in CA PPM Studio. The theme does not exist in the admin repository in Jaspersoft. The Advanced Reporting pages continues to appear in the default UI theme. 
JRE_HOME No Longer Required
Before Jaspersoft 6.4.2, our Jaspersoft 6.2, 6.1, and 5.6 installers required both JAVA_HOME and JRE_HOME. Because JRE_HOME is not required, that parameter no longer appears as a required entry for the new Jaspersoft 6.4.2 or 7.1 installers for CA PPM.
UI Customizations During Upgrade
The JasperReports Server UI is customizable using Cascading Style Sheets (CSS). The themes mechanism exposes the CSS of the UI through the repository. This makes it easy for administrators to change the appearance of the UI. Changes include images, colors, font size, spacing, and even the general layout. New releases of CA PPM attempt to provide backward compatibility. However, to improve the UI and to provide new features, CA PPM cannot ensure that all your customizations from a previous release still apply.
We recommend that you review your customized theme after every major release. If necessary modify and update your customized theme.
Post-Upgrade Folder Level and User Level Security
After the upgrade, the folder-level or user-level security can get reset by the installer.
  1. To check if a user has the required rights, log in to CA PPM Advance Reporting with an account that does not have administrative access. 
  2. In Release 15.3 or higher, test the reports by clicking Home, Reports and Jobs and launching any default report. 
  3. If you encounter the RPT-0023 error, folder-level access permissions have been reset. 
  4. To fix this problem, change the folder-level access for ROLE_USER from
    No Access
    Read Only