The Upgrade Process › Post Upgrade Steps

Post Upgrade Steps

Complete the following post upgrade steps:

1. If you have custom Xcelsius dashboards, see "Correcting the CA Clarity PPM URL for HTML and Xcelsius Portlets" in the chapter "Release 13.0 Updates."
2. For CABI Release 3.3 SP1 (BusinessObjects), 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.

3. Apply your upgraded add-ins and connectors.

   Notes:

   • Request a backup of your CA Clarity PPM installation before installing each add-in so that you can restore the application if necessary. You can also use the previous night's regular backup as a restore point.
   • 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 for upgrade ready content (for example, the Role Capacity portlet). To accept the new Release 14.1 upgraded content, apply the changes.
4. 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.

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

   Here are some tips on reviewing the views:

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

5. Verify your custom NSQL queries if any exist.

   During the upgrade, the NSQL validator script automatically verifies NSQL queries. Results are written to the admin.log.

   Put in a ticket to CA Support to get access to the admin.log. The 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 portlets work, correct any invalid NSQL queries.

   Note: For information about the database schema changes, see the section "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. Click the Preview button.
   11. Confirm that the NSQL query is valid.