Upgrade CA PPM

As a
user, you enjoy seamless automated upgrades in the cloud; however, you need to be aware of all the new features and any required or optional changes post-upgrade. See the following documentation:
The following image shows how a system administrator upgrades a 
 installation for single and clustered servers. As a SaaS customer administrator, your upgrade is performed for you. You can skip the execution steps in the diagram and focus only on pre-upgrade and post-upgrade steps. 
This image shows how to upgrade CA PPM
This image shows how to upgrade CA PPM
Complete the Post-Upgrade Tasks
The following post-upgrade tasks are required:
  • Upgrade any add-ins that you intend to use with this release. See Add-Ins and Integrations.
  • Identify the 
    CA PPM
     views that were upgraded automatically and the views that you must upgrade manually.
  • Configure portlets and portlet pages as appropriate to expose or hide the new functionality after the upgrade.
  • Update rights assignments for users, groups, or OBS instances with new or updated security rights that are introduced in this release.
  • If your users run the Schedule Connect clients, Microsoft Project (MSP) or Open Workbench (OWB), and the XOG client, each user needs to install the newest version of the XOG client that ships with 
    CA PPM
    . Also verify your version of MSP or OWB with the Compatibilities section of the Release Notes. Do not automatically update MSP or OWB. Sometimes the newest version is not compatible. 
    : Review these steps after installing a patch to verify any changes in functionality.
  • After upgrading, run the following jobs in the listed order:
    1. Load Data Warehouse (select the Full Load option)
    2. Load Data Warehouse Access Rights
  • Do not use the following views to build new reports. The views were created to support the existing reports that were based on the deprecated tables. The existing reports will still work, but you may experience slow performance:
  • Use the following views to build new reports:
Verify NSQL Queries
During the upgrade process, the checkinstall utility automatically runs the NSQL validator script to verify the NSQL queries. The validator writes the results to the admin.log file in the check-results.html file inside the checkinstall-results.zip file.
Look for the following information in the log:
  • Query name
  • Query ID
  • Content Source
  • Query ID from CMN_NSQL_QUERIES of the query that failed validation
Database schema changes can impact your custom portlets. See Oracle and MS SQL Database Schema Changes.
Correct any invalid NSQL queries. If a query is associated with a portlet, clear the
Available for User Portlets
check box on the query properties page to edit the query. You cannot edit system queries that are provided by 
Follow these steps:
  1. Open Administration, and from Studio, click Queries.
  2. Open a query.
  3. Clear the Available for User Portlets check box.
  4. Click Save and Continue.
  5. Review the errors and repair the broken query constructs or fields.
  6. Click the Preview button.
  7. Confirm that the NSQL query is valid.
  8. Click the General tab.
  9. Select the Available for User Portlets check box.
  10. Click Save and Return.
Some NSQL queries are delivered with add-ins. Applying an update for an add-in makes fixes for the NSQL queries that pertain to the add-in available for an update on the server.
If the query is in use by active portlets and cannot be edited in Studio, complete these steps:
  1. Use the XML Open Gateway (XOG) to export the failing query.
  2. Correct the broken query constructs or fields.
  3. Use XOG to import the corrected query.
  4. In Studio, go to the NSQL tab for the imported query and click the Preview button.
  5. Confirm that the NSQL query is valid.