Installation and Upgrade › Basic Upgrade Process

Basic Upgrade Process

To upgrade to Release 13.3, complete these steps.

1. Install the prerequisite third-party software.

   Review the "Compatibilities" appendix in the release notes for the supporting operating environment information. The following important changes are included:

   • Dropped support for 32-bit third-party vendor applications.
   • The Java runtime must be a supported 64-bit version.
   • Dropped support for Microsoft SQL Server 2005. If you use Microsoft SQL Server 2005 currently, we recommend upgrading your database to MS SQL server 2008, MS SQL server 2008 R2, or MS SQL Server 2012 before upgrading to Release 13.3.
   • Dropped Actuate as a supported reporting solution.
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.

   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 in the Installation Guide.

   Some important changes include:

   • The installation for an upgrade prompts you for the current CA Clarity PPM folder and a target CA Clarity PPM folder. You can indicate the same folder or different folders for these prompts. If you specify the same folder for both prompts, the existing folder is renamed. Then, Release 13.3 is installed into an empty folder with the target folder name.
   • If you are installing on a different server, review the chapter "How to Set up the Application Server" in the Installation Guide.
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. If you have custom Xcelsius dashboards, see "Correcting the CA Clarity PPM URL for HTML and Xcelsius Portlets" in the Version 13.0 Change Impact and Upgrade Guide.
7. Install or upgrade CABI Release 3.3 SP1 (BusinessObjects) and complete the following steps:
   1. If you are installing CABI for the first time, review the CA Clarity PPM requirements. If you are an upgrading customer, install CABI 3.3 SP1.

      Note: For more information, see the Installation Guide.

   2. 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.

   3. Import the universes.
   4. Review the section that is named "Reports" for information about legacy stock reports and reactivate any existing stock reports that are desired.
   5. 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. Install your current add-ins and connectors if an upgrade is desired.

   Notes:

   • Review "How to Install Add-ins" in the Installation Guide.
   • 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 PMO Accelerator.
   • Review the System: Clarity Content add-in for upgrade ready content. To accept the new Release 13.3 upgraded content, apply the changes.
9. 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 either view or the partition.

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

   Some tips on reviewing the views:

   • The Last Version column identifies changes to stock views in Release 13.3.
   • 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 13.3 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=13.3 and the Upgraded column= unchecked.

10. Verify your NSQL queries.

    During the upgrade, the NSQL validator script automatically verifies NSQL queries. Results are written to the admin.log. 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 information about the database schema changes, see the chapter "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. User 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.
11. 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_2013-04-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.