Installation and Upgrade › Basic Upgrade Process

Basic Upgrade Process

Complete these steps to upgrade to Release 13.1.

1. Install the prerequisite third-party software.

   Review the "Compatibilities" appendix in the release notes for the supporting operating environment information. Some important changes include the following:

   • 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 or 2008 R2 before upgrading to Release 13.1.
   • Dropped Actuate as a supported reporting solution.
   • Dropped integration support for Microsoft Project 2000, 2002, and 2003.
2. Create a full backup of your database, file systems, and customizations (if applicable).

   Best Practice: Take a cold backup to keep sequences in line.

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

   Due to database schema changes for this release, most custom triggers, indexes, and constraints can cause the upgrade to fail. Customer-added triggers should be removed, not disabled.

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

   Some important changes include the following:

   • 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 and Release 13.1 is installed into an empty folder with the target folder name.
   • If you are installing on a different server, review the Server Database Software topic 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.
   2. Review the Clarity System Administration server admin.log and install.log for errors.
   3. Reapply database and file system customizations.
   4. If you have custom Xcelsius dashboards, see the "Correcting the CA Clarity PPM URL for HTML and Xcelsius Portlets" topic in the Version 13 Change Impact and Upgrade Guide.
7. Install or upgrade CABI Release 3.3 (BusinessObjects) and complete the following steps:
   1. If you are installing CABI for the first time, review the CA Clarity PPM requirements.

      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 need to log in to Infoview and run reports. You can also set up BusinessObjects trusted authentication between BusinessObjects and CA Clarity PPM, which provides LDAP integration with BusinessObjects and CA Clarity PPM.

   3. Import the universes and reports.
   4. Manually restart the scheduled reports.

      Note: 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.

   Notes:

   • Review the How to Install Add-ins topic 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.
   • The install.log is now written to the CA Clarity PPM install directory instead of the directory where you extracted the add-in jar file. For example, <install.dir>/logs/content/install/<addin.id>/install log.
   • 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, apply the new incoming stock CA Clarity PPM content, and then retrofit the modifications to the new content.

   • Read the PMO Accelerator Release Notes for important information about what has changed for PMO Accelerator Version 3.0.
   • Review the System: Clarity Content add-in for upgrade ready content (for example, Role Capacity portlet). Apply the changes to accept the new Release 13.1 upgraded content.
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 view and/or the partition.

   Use the Studio Views list page to determine which views were not automatically upgraded.

   Some tips on reviewing the views:

   • The Last Version column identifies changes to stock views in Release 13.1.
   • If a view was automatically upgraded as part of the upgrade process, a check mark appears in the view's Upgraded column. No further action is required.
   • If a view was changed in Release 13.1 but was not upgraded due to pre-existing configurations, decide if you want to apply the changed view.

     Look for views with the following:

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

10. Verify your NSQL queries.

    During the upgrade, the NSQL validator script automatically checks 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

    There are database schema changes in this release. You must correct invalid NSQL queries for portlets to work.

    Note: For more information about database chema 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 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. Click the Preview button.
    11. Confirm the NSQL query is valid.