Start Here: Common Steps Before All New Installs and Upgrades

You can set up instances of cappm on-premise or SaaS for development and testing, and upgrade those non-production environments, before upgrading and cutting over to production. After reading the documentation and preparing for your upgrade, SaaS customers can file a support ticket to request an upgrade for a particular instance of cappm SaaS.
ccppmod155
You can set up instances of 
Clarity PPM
 on-premise or SaaS for development and testing, and upgrade those non-production environments, before upgrading and cutting over to production. After reading the documentation and preparing for your upgrade, SaaS customers can file a support ticket to request an upgrade for a particular instance of 
Clarity PPM
 SaaS.
 
As an administrator for an on-prem or SaaS environment, follow these steps:
 
 
 
3
 
3
 
 
Activity:
Status:
Plan for All Required Components
The install and upgrade scripts require the installation or upgrade of certain system components.
 
Required Action: 
All new installs and upgrades require that you perform the following steps. Plan ahead to include these steps before you consider your upgrade complete:
  • Install and Configure the Data Warehouse
  • Run the Load Data Warehouse Job
  • Install the PMO Accelerator add-in (required for the 
    New User Experience
     and if using the optional APM add-in). For best performance and value, we recommend installing the PMO Accelerator and the PMO Accelerator Advanced Reporting content for all installations and upgrades, 14.x or 15.x, whether you plan to use Classic PPM, the Modern UX, or both.
__ Planned
__ Started
__ Completed
__ Not applicable
Upgrade Large Data Sets
If your upgrade processes a large volume of data, we recommend that you override the default memory settings that are used by the upgrade.
 
Recommended Action:
 
  1. Create your own 
    memory.properties
     file and place it in the 
    $cappm/config
     directory.
  2. Set the desired memory values in that file.
    Default pre-upgrade values:
    defaultScriptMaxMem=1024m
     defaultScriptPermGenMem=128m 
     
  3. The following settings represent examples that you might add to your memory.properties file:
 
 defaultScriptMaxMem=2560m
 defaultScriptPermGenMem=512m
 
__ Planned
__ Started
__ Completed
__ Not applicable
Legacy Business Objects Reports
If upgrading from Release 14.4 or older to a newer 15.x release, no legacy SAP Business Objects or Xcelsius functionality is supported. All legacy Business Objects content is removed as part of the upgrade process for both on-premise and SaaS environments.
 
Recommended Action: 
Migrate any legacy SAP Business Objects content that you want to keep before you start the upgrade process.
IMPORTANT
: In a SaaS upgrade from 14.x to 15.x, any legacy Business Objects reporting content is permanently destroyed.
As a reminder, new releases of 
Clarity PPM
 include Advanced Reporting dashboards, views, and trending capabilities.
__ Planned
__ Started
__ Completed
__ Not applicable
Avoid Making Configuration Changes During the Upgrade
As a risk mitigation requirement, a stable configuration is mandatory during the upgrade cycle.
 
Required Action:
 
  1. Complete all your configuration changes, finish any processes or jobs, and migrate any data to the production environment prior to starting the upgrade cycle.
  2. Do not make any changes during the upgrade cycle.
  3. If a critical need arises that requires a change during the upgrade, notify your upgrade team. As a SaaS administrator, contact CA support and enter a new ticket to see what can be done. Do not make any changes yourself.
Failure to follow this best practice can cause your production upgrade to fail or deviate from previous test environment results.
__ Planned
__ Started
__ Completed
__ Not applicable
As an administrator for a SaaS instance or environment, in addition to the steps above, follow these additional steps:
Activity:
Status:
Schedule a Production Data Refresh (Backup)
Non-production environments are upgraded using existing data. In order to minimize risk and ensure a successful production upgrade, it is strongly recommended that your organization request a backup of production data by refreshing it into the first non-production environment scheduled for upgrade.
 
Recommended Action:
 At least 2 or 3 business days before the scheduled non-production upgrade, open a CA Support ticket requesting a production data refresh into the first upgraded non-production environment.
A refresh requires that both environments are on the same SaaS release version.
__ Planned
__ Started
__ Completed
__ Not applicable
Schedule a Second Upgrade If Your UAT Window Exceeds 90 Days
If your testing efforts take more than 90 days to complete, we recommend an additional upgrade of production data before your original production environment is upgraded.
 
Recommended Action: 
 
  1. Upgrade an additional non-production environment, if your organization subscribes to one.
  2. Or, upgrade the same non-production environment again. Option 2, called a re-upgrade, purges any data or configuration settings on the environment and replaces it with new production data and configuration settings.
__ Planned
__ Started
__ Completed
__ Not applicabl