Installation and Upgrade › Complete the Upgrade Process

Complete the Upgrade Process

The following process shows what to do when the upgrade is complete.

1. Apply your current add-ins and connectors.

   Notes:

   • 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. A database restore is required to restore any applied items.

     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.

     Note: For more information about applying add-ins and connectors, see the Studio Developer's Guide.

   • Read the PMO Accelerator Release Notes for important information about what has changed for PMO Accelerator Release 3.1.
   • 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.
2. 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 product does not automatically upgrade the view or the partition.

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

   Here are 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 checkmark appears in the view 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 values:

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

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