The Upgrade Process › Upgrade to CA Clarity PPM Release 14.2

Upgrade to CA Clarity PPM Release 14.2

Follow these steps:

1. Install the prerequisite third-party software.

   Note: For the supporting operating environment information, see the appendix "Compatibilities" in the Release Notes . The following important changes are included:

   • Dropped support for Oracle WebLogic.
   • Dropped support for Oracle Solaris.
   • Dropped support for HP-UX.
   • IBM WebSphere is supported only for IBM AIX.
   • Dropped support for 32-bit third-party vendor applications.
   • The Java runtime must be a supported 64-bit version.
   • Dropped support for Oracle 11.2.0.2 in Release 14.1. The supported Oracle databases for Release 14.2 are Oracle 11.2.0.3 and 11.2.0.4.
   • Dropped support for Microsoft SQL Server 2005. If you currently use this version, we recommend upgrading your database to MS SQL server 2008, MS SQL server 2008 R2, or MS SQL Server 2012 before upgrading to this release.
2. Create a full backup of your database, file systems, and customizations (if applicable).

   Best Practice: To keep sequences in line, take a cold backup.

3. Remove customer-added database triggers, stored procedures, indexes, views, and constraints before upgrading.

   Important! Due to the database schema changes for this release, most custom triggers, indexes, and constraints can cause the upgrade to fail. We recommend removing, not disabling, customer-added triggers.

4. Review the steps for installing and upgrading the product in the Installation Guide.

   Some important changes include:

   • The installation for an upgrade prompts you for the current and a target CA Clarity PPM folder. You can specify the same folder or different folders. If you specify the same folder for both, the existing folder is renamed. Then, Release 14.2 is installed into an empty folder with the target folder name.
   • If you are installing on a different server, review the information about setting up the application server in the Installation Guide.
   • The HTTP and HTTPS Entry URL fields completed for the CA Clarity PPM server in Clarity System Administration (CSA) cannot be localhost when Jaspersoft is integrated with CA Clarity PPM. When you use Jaspersoft, the complete URLs must be entered on the Application subtab of the Properties tab for the CA Clarity PPM server.
5. Install or upgrade using the steps in the Installation Guide.
6. Complete the following post-installation steps:
   1. Verify that all installation steps completed successfully by reviewing the post upgrade report that the installer generates.
   2. Review the Clarity System Administration server admin.log and install.log for errors.
   3. Reapply any database and file system customizations.
   4. Run the Oracle Table Analyze Job from CA Clarity PPM after the upgrade is done to gather schema statistics. The expected time for this job to complete depends on the size of the database. We recommend that you run this job right after the upgrade and at off peak hours thereafter.

      If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the CA Clarity PPM schema in Release 14.2 (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.

      Note: If you have custom Xcelsius dashboards, see Correcting the CA Clarity PPM URL for HTML and Xcelsius Portlets.

7. Upgrade CABI Release 3.3 SP2 (BusinessObjects) and complete the following steps:

   Note: CABI software is not available for customers installing for the first time. The reporting solution for new customers is Jaspersoft. Only existing customers who have CABI installed already can upgrade. For more information, see the Installation Guide.

   1. If you are upgrading from a version earlier than Release 12.1, reset the passwords of your BusinessObjects report users.

      Resetting is necessary for all preupgrade users who must log in to Infoview and run reports. You can also set up BusinessObjects trusted authentication between BusinessObjects and CA Clarity PPM, which provides the LDAP integration with BusinessObjects and CA Clarity PPM.

   2. Import the universes.
   3. See Upgrade Reports for information about legacy stock reports and reactivate any necessary existing stock reports.
   4. Manually restart the scheduled reports.

      Note: Any scheduled reports that were configured before the upgrade to this release do not automatically run after the upgrade.

8. (Optional) Set up Advanced Reporting and complete the following steps:
   1. Set up the Data Warehouse database and populate it with CA Clarity PPM data.
   2. Install Jaspersoft and import the domain information for reporting.

   Note: For more information about setting up the Data Warehouse and Jaspersoft, see the chapters "How to Set Up the Data Warehouse" and "How to Set Up CA Clarity PPM Reports" in the Installation Guide.

9. Install your current add-ins and connectors if an upgrade is desired.
   • Review the Installation Guide for information about installing add-ins.
   • Back up your CA Clarity PPM installation before installing each add-in so that you can restore the application if necessary.
   • Apply the Upgrade Ready content for those items that you are actively using.

     Important! Consider the configurations that you have made to items before applying them. Applying modified items overwrites your configurations.

     Best Practice: If you modified stock CA Clarity PPM content, copy the modified content before upgrading. Then, apply the new incoming stock CA Clarity PPM content, and retrofit the modifications to the new content.

   • Read the PMO Accelerator Release Notes for important information about what has changed for the PMO Accelerator.
   • Review the System: Clarity Content add-in available on the Content Add-ins page for upgrade-ready content. This page is available from the Administration menu. To accept the new Release 14.2 upgraded content, apply the changes.
10. Review the Studio views and system content and manually upgrade as needed.

    The upgrade preserves all preexisting Studio view configurations. If an existing view has configurations or if the object for the view is partitioned, the system does not automatically upgrade the view or the partition.

    To determine which views were not automatically upgraded, use the Studio Views list page.

    Use these tips to help you review the views:

    • The Last Version column identifies changes to stock views in Release 14.2.
    • If a view was automatically upgraded as part of the upgrade process, a checkmark appears in the Upgraded column. No further action is required.
    • If a view that changed in Release 14.2 was not upgraded due to pre-existing configurations, decide whether to apply the changed view.

      Look for views with the following column information:

      Last Version column=14.2 and the Upgraded column= unchecked.

11. Verify your NSQL queries.

    During the upgrade, the checkinstall utility automatically verifies NSQL queries. Results are captured in the postcheck-results.html file of the checkinstall-results.zip file. This log contains the following information:

    • Query name
    • Query ID
    • Content Source
    • Query ID from CMN_NSQL_QUERIES of the query that failed validation

    This release contains database schema changes. To ensure that your custom portlets work, correct any invalid NSQL queries.

    Note: For more information about the database schema changes, see Data Model Changes.

    Upgrade Action:

    If the query can be changed in Studio, complete these steps:

    1. Go to the NSQL tab for each failing query.
    2. Click the Preview button.
    3. Review the errors.
    4. Repair the broken query constructs or fields.
    5. Click the Preview button.
    6. Confirm that the NSQL query is valid.

       If the query is in use by active portlets and cannot be edited in Studio, complete these steps:

    7. Use the XML Open Gateway (XOG) to export the failing query.
    8. Correct the broken query constructs or fields.
    9. Use XOG to import the corrected query.
    10. In Studio, go to the NSQL tab for the imported query and click the Preview button.
    11. Confirm that the NSQL query is valid.
12. Save the Upgrade Check Install Results Package.

    The upgrade process produces a zipped file that contains all of the artifacts that were created during the upgrade. Review the contents and save the zip package for future reference.

    The files are zipped into an archive that has a timestamp-encoded name (for example, checkinstall-results_2014-08-17_16-48-31.zip). This file is located in the checkinstall/check-logs directory, and if possible, the file is copied into the <target runtime dir>/logs/checkinstall directory.

Upgrade suggestion for Niku 6.x, Clarity 7.x, and CA Clarity 8.x

As a best practice, we recommend the following steps for customers on older versions who are upgrading to Release 14.2:

1. Upgrade to CA Clarity PPM 12.1.1, 12.1.2 or 12.1.3.
2. Verify that the upgrade is successful and run the CSA Health Report that is available from Clarity System Administration.
3. Create a full backup of the database and runtime file system.

   Note: For more information, see Basic Upgrade Process.

4. Proceed with the upgrade to Release 14.2.