CA PPM 15.2 Change Impact and Upgrade

HID_release_info_change_impact_op
ccppmop152
HID_release_info_change_impact_op
Plan the 
CA PPM
upgrade and determine the upgrade options that fit your business needs. As the administrator and implementer, use this information to plan your training and rollout efforts. Complete information for the current release and summary information for previous releases is provided here. The complete 
Change Impact and Upgrade 
content
 
for a specific 14.x release is available by selecting a release in the Versions drop-down on this page. Content before 14.x is available on the Documentation page of CA Support Online.
This article covers the following topics:
  • The system preparation before upgrading
  • An overview of the upgrade process
  • The post-upgrade tasks
  • Features and enhancements for the current and previous releases and the upgrade actions that they require
To prepare for an upgrade to Release 15.2, review the supported upgrade paths, features, enhancements, and required upgrade actions. If you are upgrading from an earlier release, review the information for the updates in each release. For example, when upgrading from Release 13.3, review the release updates in releases 14.2, 14.3, 14.4, 15.1, and 15.2.
2
Supported Upgrade Paths for Release 15.2
If you have any of the following releases installed on their base level with no patches, you can directly upgrade to 
CA PPM
 Release 15.2:
  • CA PPM
     Release 13.3
  • CA PPM
     Release 14.1
  • CA PPM
     Release 14.2
  • CA PPM
     Release 14.3
  • CA PPM
     Release 14.4
  • CA PPM
     Release 15.1
Follow the upgrade patch levels and exceptions in the following table only if you have installed any patches on the base versions:
Supported Patch Levels for Upgrade
Upgrade Patch Level Exceptions
How to Download and Install the Patch
Patch level 13.3.0.14 installed on the base version 13.3.0
None
Patch level 14.2.0.11 installed on the base version 14.2.0
None
See the
CA PPM
14.2 and Jaspersoft Patches
page in the 14.2 documentation.
Patch level 14.3.0.10 installed on the base version 14.3.0
None
See the
CA PPM
14.3 and Jaspersoft Patches
page in the 14.3 documentation.
Patch level 14.4.0.3 installed on the base version 14.4.0
None
See the
CA PPM
14.4 and Jaspersoft Patches
page in the 14.4 documentation.
Patch level 15.1.0.2 installed on the base version 15.1.0
None
See the
CA PPM
15.1 and Jaspersoft Patches
page in the 15.1 documentation.
For example, you have 
CA PPM
 13.3 or an earlier release. Upgrade to one of the listed releases before you upgrade to 
CA PPM
 Release 15.2.
You might experience issues upgrading from a patch level that is not supported. For best results, wait for a supported upgrade path to a later release or patch. To learn more, contact CA Support or your CA Services representative. You can also visit the CA PPM Community to collaborate with other community members about your specific questions.
The Release 15.2 installer can upgrade your data from certain releases. The installer detects how many incremental upgrade steps are required to upgrade to Release 15.2.
If you are running a version earlier than Release 12.1.1, consider upgrading to 12.1.1, 12.1.2, or 12.1.3 before you upgrade to Release 13.3 (as a prerequisite to upgrading to 15.2). Although the 12.1.x upgrade is not required, it simplifies the troubleshooting and restart process if an upgrade step fails.
Upgrade Considerations for Release 15.2
The following information includes the installation and upgrade changes for 
CA PPM
 Release 15.2.
Add-in Compatibilities
Review this important information about upgrading installed add-ins, accelerators, and connectors.
  • If you are upgrading from Releases 13.3 or 14.x to the current release, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Accelerator for the PMBOK
    • CA Agile Planning
  • If you are upgrading from Release 13.2 or earlier to the current release, upgrade all installed add-ins.
  • Starting with Release 13.3, a new installation process is required for add-ins, accelerators, and connectors. For more information, see 
    Installing and Upgrading
    .
The add-ins, accelerators, and connectors listed in the Release Notes are compatible with new installations or upgrades to 15.2.
User Interface Changes for Release 15.2
The previous release (15.1) marked the official debut of the 
New User Experience
. This release adds enhancements. Project managers, coordinators, resource managers, and team members can take advantage of the following enhancements:
New User Experience Improvements for Project Management and Timesheets
  • Resource Managers and Team Members with the 
    Resource - Enter Time
     access right can create, edit, and submit timesheets for other team members. Resource Managers can filter the timesheets by a Resource Manager on whose resources they have timesheet approval access rights. Resource Managers can view, approve, return, and adjust the timesheets of the resources reporting to the other manager. See New User Experience: Review and Approve Timesheets.
  • Resources can access their timesheets directly from 
    CA Agile Central
    , if they have Timesheet Navigate right. This is supported for non-SSO based login. The CA PPM On-Demand Portal does not support this feature. See 
    Integrate CA PPM with CA Agile Central
     in the English edition of the documentation.
  • Project Managers and Team Members can preview current and previous status reports in PDF format. Project Managers can also publish status reports in PDF format. See New User Experience: Measure Trends and Publish Project Status Reports
Time and Work Transparency
  • Resource Managers and Team Members with the 
    Resource - Enter Time
     access right can create, edit, and submit timesheets for other team members. Resource Managers can filter the timesheets by a Resource Manager on whose resources they have timesheet approval access rights. Resource Managers can view, approve, return, and adjust the timesheets of the resources reporting to the other manager. See New User Experience: Review and Approve Timesheets.
  • The Charge Code, Input Type Code, User Value 1, User Value 2 are copied accurately when a task is copied within a timesheet and when creating a timesheet from a previous time period.
Adaptive Project Management
  • Project Managers and Team Members can view and edit (upload, download, delete, add tags, and search) all documents associated with their Project. Nonteam members with the 
    Project - Edit
     access right can view and edit all documents. Nonteam members with the 
    Project - View
     access rights can view and download documents. See New User Experience: Upload and Tag Project Documents.
New Features to Empower Teams to Connect and Collaborate
Last release, we introduced basic project team collaboration. With this release, several improvements have been made. When connecting and collaborating with your project team, you can now do the following:
  • Join conversations and comment in the context of a project or resource assignment for an investment.
  • Mention team members in a conversation using the @sign. Our solution is similar to how you mention people on Twitter, LinkedIn, Facebook, and other social media sites.
  • Receive notifications in both the 
    New User Experience
     and in Classic 
    CA PPM
     when someone mentions you or your team.
Upgrade Action
: For new installations, the 
New User Experience
 is already active and ready to use. For upgrading customers, the 
New User Experience
 is not active. Administrators can activate the 
New User Experience
 by completing the steps under 
Enable the New User Experience
 in Configure General System Settings. If http(s)://<server> is the URL for your existing 
CA PPM
 environment, the URL for the 
New User Experience
 is http(s)://<server>:/pm.
For upgrading customers, activating this feature also resets all fields in the Default Time Entry Options to the stock default values. If you currently have any of these fields configured differently than the stock values, revisit this configuration page after activating timesheets for the 
New User Experience
.
Administrators can also configure Single Sign-On (SSO) for the 
New User Experience
 by configuring an SSO server. See 
Configure Single Sign-On (SSO) for the New User Experience
 in CSA: Security, Passwords, LDAP, SSL, SSO, XSS, and FIPS.
To manage projects in the 
New User Experience
, verify that the PMO Accelerator add-in is installed on your
CA PPM
instance. Users with the Project – Navigate access right get an error message if the PMO Accelerator is not installed. See Install the PMO Accelerator Add-In and PMO Sample Data for more information.
For users accessing only the new Timesheets (with only the Timesheet – Navigate access right), the PMO Accelerator is not required.
Make sure that you provide the appropriate users with the following new access rights as required:
  • C
    lassic PPM - Navigate
    . The access right allows users to navigate back to Classic 
    CA PPM
     from the 
    New User Experience
     using the icon_classic_ppm.png 
    Classic PPM
    main menu item.
  • Project - Task Management (Instance)
    . The access right allows team members to create, edit, delete, and add assignments to tasks. The right is automatically granted when you add a team member to a project in the 
    New User Experience
    .
New User Experience for Resource Management
The new user experience for resource management includes dynamic new ways to plan, forecast, and staff projects with resources. This release offers the following new capabilities:
  • A single view for resource teams that lets you deal with incoming requests.
  • Navigate through time periods frames to determine allocations, workload, etc. You can make decisions and can remove bottlenecks.
  • Perform load balancing
  • Project managers, resource managers, and project coordinators with the 
    Resource Management - Navigate
     right can access the resource management pages in the New User Experience.
Advanced Reporting Changes for Release 15.2
Advanced Reporting with Jaspersoft is an important focus area this release. We have enhanced the following areas:
  • To simplify administration of the Jaspersoft server, the Jaspersoft superuser and the Jaspersoft tenant administrator can export and import Jaspersoft Advanced Reporting Content. See 
    Upgrade Jaspersoft and Migrate Advanced Reporting Content
    .
  • A new Product or Application Roadmap report is available with the PMO Accelerator Advanced Reporting content.
  • Updated Domain Schema
  • Locale Support
Integration Changes for Release 15.2
Integration with CA Agile Central (Formerly Rally)
CA PPM integrates with CA Agile Central agile development software. In this release, the integration provides the following enhancements:
  • Previously, you could only import 
    CA Agile Central
     portfolio items into 
    CA PPM
     projects as tasks. Now, you can also push 
    CA PPM
     tasks into 
    CA Agile Central
     as portfolio items.
  • You can configure more than one application integration instance between 
    CA PPM
     and 
    CA Agile Central
    .
  • A time tracking project template that you can configure and select during integration setup. The template contains time tracking tasks that are automatically generated for any new features imported from 
    CA Agile Central
     into 
    CA PPM
    . The time tracking project template is only available for use with the Agile Central to PPM integration direction. 
  • A new Product Roadmap dashboard that provides visibility into the agile product roadmaps.
  • A new Agile Project Status dashboard that provides the overall picture and performance summary of a 
    CA PPM
     project integrated with 
    CA Agile Central
    .
  • You can access 
    CA PPM
     Timesheets in the 
    New User Experience
     from 
    CA Agile Central
     in a framed browser window.
See 
Integrate 
CA PPM
 with CA Agile Central
.
REST APIs for Release 15.2
The
CA PPM
REST APIs can only be used by
CA PPM
engineering. At this time, the REST APIs are not supported for customer or partner use.
Our strategy is to focus on developing robust APIs as we design the
New User Experience
. The APIs may change as we make architectural improvements, add capabilities, and optimize performance. We will review our strategy every release and make the APIs publicly available as soon as possible.
Administration Changes for Release 15.2
Default Entities
You can mark an entity as the default entity for the system from the following locations in the UI:
  • Entity Properties
  • Financial Management Defaults
A default entity is required for the telescope calendar capability available with the new Resource Management user experience. See New User Experience: Personalize the Telescope Calendar and Views.
For upgrading customers who have a single entity, that entity is marked as the default during the upgrade. If there are multiple entities in the system, no entity is marked as the default during the upgrade.
New System Health Report
Administrators can view and download a health report to get system status. The new health report lists the setup status and completion percentage for the application, database, and data warehouse. The % Completed value calculates the total number of settings that require a value during a new install or upgrade. The health report summary shows you the portion of those required settings that have a compliant value. For example, 90% Complete indicates that you are still missing valid values for the remaining 10 percent of all settings. When the report shows Setup Complete and a green status icon, the health for that category is good. When setup is not complete, a red icon appears. Where applicable, portions of the health report include recommended values.
New PPM Customization Discovery Analysis Report and Job
Administrators can view a discovery analysis report to detect system customizations. This new report identifies potential non-compliant objects before migrating or upgrading from an on-premise to a SaaS environment. You can download the report or schedule it with a job.
New Jobs for Resource Management
The following new jobs are available:
  • The Convert Mixed Booking Status job converts project team allocations with 
    mixed
     booking status to 
    hard
     or 
    soft
    . After all mixed booking allocations are converted, the Allow Mixed Booking option in the Project Management administration settings is disabled. Use this job if you use the new Resource Management features in the 
    New User Experience
    . The new features do not support mixed booking allocations. By default, the job is inactive. Before you can run this job, activate it.
  • The Populate Resource Management Curves job ensures that the time-scaled value fields on the resource management views in the 
    New User Experience
     are created correctly post-upgrade. The job is inactive by default. Activate and run the job only once after upgrade. If you do not run the job after completing an upgrade, no data appears in the resource management views.
Upgrade Action
: After upgrade, run the Populate Resource Management Curves job only once to populate the resource management views in the 
New User Experience
. See CA PPM Jobs Reference.
Runtime Rate Matrix
The runtime or
on-the-fly
rate matrix is disabled by default after the upgrade.
Upgrade Action
: After the upgrade, decide whether to enable this feature or leave it disabled. To enable the runtime rate matrix, enable the 
On-the-fly RateMatrix
 setting on the 
Application
 tab of the new system health report. See CA PPM System Health Report, Customization Discovery, Statistics, and Log Analysis.
New Parallel Job Processor
This advanced new feature processes tasks in one or more jobs in parallel to speed completion time.
: This feature is exclusively for global delivery teams engaged in active integrations. Contact your administrator to learn more. This feature is currently not available for general consumption and cannot be used by custom jobs. The job will fail with the following error message if you attempt to run it:
Parallelism is not yet supported in jobs. The job cannot be executed at this time.
In previous releases, certain integration activities imported data from external systems and mapped it to PPM objects. The preferred method for importing this data is to run XML Open Gateway (XOG) jobs on a background server. These jobs were sequential. Depending on the volume of data, an integration could take a long time. In this release, the job tasks can run in parallel when integration teams import data using the XOG and run the Parallel Job Processor job.
  • The software calculates the optimum number of threads based on the system configuration, number of jobs running, and maximum limit. The minimum and maximum limits for the number of threads are 3 and 10 respectively.
  • The job also supports ordering of tasks/units of work.
  • Authorized persons can now configure the pre-processor and post-processor.
Data Warehouse Changes for Release 15.2
The Data Warehouse includes the following enhancements:
    • The default status for Load Data Warehouse and Load Data Warehouse Access rights jobs is now set to 
      Active
      .
    • The following fields are now enabled for the Data Warehouse: 
      • Financial Status  
      • Chargeable
    • A new Previous Start Date column appears in the DWH_CFG_SETTINGS table. You can use the DWH_DIM_PREV_START_DATE and DWH_DIM_START_DATE columns to troubleshoot issues with the data warehouse. Records with the Last Updated date falling between the range of the previous start date and the start date are the records processed in the last run of the Data Warehouse job. 
    • Performance improvements were made to the financial plans for incremental loads. The incremental load makes use of a new DWH_TMP_FIN_RECORD_KEYS table that contains only those plans that changed since the last incremental load. The Database view joins to this table in order to reduce the amount of data processed. This can significantly improve performance on large datasets.
    • The facts for MSSQL are now defined as numeric (32,6) to be consistent with the CA PPM database. The numeric change fixes the overflow issue for large numbers.
    • Error handling has been added in the MS SQL for the Load Data Warehouse job. If an error occurs when you run the job, the job status does not show as 
      Completed
      .
    • A new error handling table, DWH_CMN_ERROR_MESSAGE contains the error message and the SQL code that was being processed at the time the Load Data Warehouse job failed.
    • Similar to recent improvements for assignments and teams, the load performance of financial transaction facts data is improved. These tables often contain millions of rows of data. The tables include DWH_FIN_TRANSACTION, DWH_FIN_TRANSACTION_LN, and DWH_INV_TASK_PERIOD_FACTS.
Data Model Changes for Release 15.2
To view a summary of the data model changes for this release including the data warehouse, see 
Schema Changes 
under
 Reference.
Known Issues for Release 15.2
The following section lists the known issues at the time this release is delivered.
Create Project Button Appears for Users Without Create Project Access Right in the 
New User Experience
The +Project button always appears for users that have access to the 
New User Experience
 project tiles page. The button appears even if the user does not have the access right to create projects. To limit who can create projects, we recommend that you limit the view access of the project templates in Classic 
CA PPM
. Without access to project templates, a user is unable to create projects in the 
New User Experience
.
The Resource Management Views Allow Adding Investments and Resources Although Filtering is Applied
On the Resources to Investments view, if you are filtering by a specific investment (for example, eBusiness Mobile Network), you only see that one investment when you expand a resource. Next, if you try adding another investment (for example, 4G Upgrade Readiness) to the resource, the investment gets added and appears on the view even though it does not match the filtering criteria. Try refreshing the page and viewing the data. The newly added investment no longer appears as it does not match the filtering criteria. Similarly, on the Investments to Resources view, if you are filtering the view by a specific resource, you only see that resource when you expand an investment. Next, if you try adding another resource to the investment, the resource gets added and appears on the view even though it does not match the filtering criteria. In this case also, try refreshing the page so the new resource that does not match the filtering criteria does not appear.
Potential Security Issue When Viewing a CA PPM Timesheet from 
CA Agile Central
If you log in to CA PPM, then log in to CA Agile Central, and then access your CA PPM timesheet from CA Agile Central, no authentication is required. However, after you log out of CA Agile Central, another user could log in and might be able to view your timesheet.
To avoid that possibility, we recommend that you log in to CA Agile Central first. Then, log in to CA PPM when prompted from CA Agile Central 
Follow these steps:
  1. Log in to CA Agile Central in your browser using a secure computer. 
  2. In CA Agile Central, navigate to your CA PPM timesheet. (Timesheet integration requires configuration by your administrator.)
    The following message appears at the top of the page:
    Login to PPM through Agile Central is recommended only when using a private computer.
  3. Enter your CA PPM username and password
    The timesheet page appears.
Agile Central Embedded PPM Timesheet
CA PPM now supports the Embedded Timesheet directly. If the Integrations setup in PPM uses the standard Agile Central URL (rally1.rallydev.com), timesheet functionality works fine. If the Integrations setup in PPM uses the CDN avoiding Agile Central URL (us1.rallydev.com), the Embedded PPM Timesheet is blocked by the browser. This prevents the timesheet from appearing in CA Agile Central.
See this Agile Central help page for more information on avoiding the CDN for integration connections.
Workaround:
By default, 
CA PPM
 does not allow itself to be embedded within other applications (X-FRAME-OPTIONS). Use the following workaround to enable the embedded timesheet when the PPM Agile Central Integration setup avoids the CDN and uses the us1.rallydev.com Integration URL instead of the standard rally1.rallydev.com URL. 
Follow these steps:
  1. Log in to 
    CA PPM
    .
  2. In the classic user interface, click 
    Administration
    General Settings
    Integrations
    .
  3. Create a second integration that uses the standard URL (rally1.rallydev.com) for 
    CA Agile Central
CA PPM
 does not use the second integration for projects. The system adds an exception to the X-FRAME-OPTIONS. This exception allows the new timesheet page from 
CA PPM
 to appear embedded inside 
CA Agile Central
.
The following image demonstrates the two integrations.
CA PPM integration with CA Agile Central.
Checkinstall Script for Linux Contains DOS End of File Characters and Does Not Execute
Before planning an upgrade, we recommend that you run the checkinstall script to verify that all the pre-upgrade requirements are met. When you run checkinstall.sh on a Linux system, the script does not execute and produces the syntax error: "unexpected end of file".
Workaround: Convert the Script to Unix Format
  1. Convert the checkinstall.sh script to Unix format by running dos2unix:
    # dos2unix ./checkinstall.sh
  2. Run checkinstall again:
    # sh ./checkinstall.sh
Alternately, you can use the following perl script to run checkinstall successfully:
  perl -i -pe 'y|\r||d' checkinstall.sh
Evaluate Before You Install or Upgrade
The Installation Checker (checkinstall) utility assesses an installation or an upgrade. The utility runs automatically at the start of an installation or upgrade and at the end of an upgrade attempt. You can also run it manually. The utility produces a report results file (precheck-results.html) in the <install-root>/checkinstall/check-logs directory.
Upgrade Action
: For best results, run the Installation Checker before starting the full installation and upgrade process. Carefully evaluate and resolve warnings before proceeding.
Run the Installation Checker Manually
Follow these steps:
  1. Extract the 
    CA PPM
    installer to the 
    CA PPM
    application server.
  2. Open a command prompt and navigate to the checkinstall directory located in the directory to which you extracted the installer.
  3. Invoke the checkinstall command:
    UNIX
    :
    sh checkinstall.sh
    Windows
    :
    checkinstall.bat
    You are asked for the Operator Username and Operator Email. This information refers to the user who is upgrading or installing and the email of the user. This information is stored as a record in the installation log.
  4. Verify the results.
    The results contain any warnings and errors and also indicate any customizations that you have made. Review the customizations and make adjustments for the upgrade as necessary.
Make Third-Party Jar Files Accessible to the Installer
Because of licensing restrictions for some third-party library JAR files (currently the jgroups-all.jar and the xinclude.jar), changes were made in how these files ship. The JAR files are shipped separately from the 
CA PPM
image in the installation media. The install.jar image does not contain the files mentioned. Any install packages for a previous version included in the install.jar also exclude the .jar files. For each release of
CA PPM
, the .jar files are bundled into a folder on the installation media containing third-party libraries .jar file. For Release 15.x, the file is named
thirdparty.libs.15.x.0.jar
.
Upgrade Action
: Retrieve the
thirdparty.libs.15.x.0.jar
file from the installation media. Place the .jar file in a location in your file system so that it is accessible to the installer.
Tip
: To keep the installer from prompting you for the file location, place the JAR file in the installation root directory. If you place the .jar file in another directory, the installer prompts you for the file location.
Upgrading Large Data Sets
If your 
CA PPM
upgrade processes a large volume of data, we recommend that you override the default memory settings that are used by the upgrade.
You can override the default memory settings for Release 14.4. Create a file that is named
memory.properties
and place it in the $cappm/config directory. Set the desired memory values in that file.
Here are the default values that the upgrade uses:
defaultScriptMaxMem=1024m defaultScriptPermGenMem=128m
Here are some sample settings in the
memory.properties
file:
defaultScriptMaxMem=2560m defaultScriptPermGenMem=512m
CA PPM
 Upgrade Overview 
Follow these steps:
  1. Perform the pre-upgrade requirements.
    1. Install the prerequisite third-party software. For the supporting operating environment information, see
      Compatibilities
      in the Release Notes
      The following important changes are included:
      -The Java runtime must be a supported 64-bit version.
      -The supported Oracle databases for Release 15.1 are Oracle 11.2.0.4 and 12.1.0.2.
      -The supported MS SQL Server databases for Release 15.1 are 2012 Enterprise Edition: Service Pack 3 and 2014 Enterprise Edition: Service Pack 1.
    2. Create a full backup of your database, file systems, and customizations (if applicable). To keep sequences in line, take a
      cold
      backup.
    3. Remove customer-added database triggers, stored procedures, indexes, views, and constraints before upgrading.
      As a result of the database schema changes for this release, most custom triggers, indexes, and constraints can cause the upgrade to fail. We recommend
      removing
      , not disabling, customer-added triggers.
  2. Perform the remaining pre-upgrade steps and then start the upgrade as detailed in
    Upgrade CA PPM
  3. Some important changes include:
    • The installation for an upgrade prompts you for the current and a target 
      CA PPM
      folder. You can specify the same folder or different folders. If you specify the same folder for both, the existing folder is renamed. Then, Release 15.1 is installed into an empty folder with the target folder name.
    • If you are installing on a different server, review the information about setting up the application server in
      Installing and Upgrading
      .
    • The HTTP and HTTPS Entry URL fields completed for the 
      CA PPM
      server in
      CA PPM
      System Administration (CSA) cannot be
      localhost
      when Jaspersoft is integrated with
      CA PPM
      . When you use Jaspersoft, the complete URLs must be entered on the Application subtab of the Properties tab for the 
      CA PPM
      server.
  4. Complete the following post-installation steps:
    1. Verify that all installation steps completed successfully by reviewing the post upgrade report that the installer generates.
    2. Review the
      CA PPM
      System Administration server admin.log and install.log for errors.
    3. Reapply any database and file system customizations.
    4. Run the Oracle Table Analyze Job from
      CA PPM
      after the upgrade is done to gather schema statistics. The expected time for this job to complete depends on the size of the database. We recommend that you run this job right after the upgrade and at off peak hours thereafter.
      If you use a custom statistics job, refer to the updated Oracle Table Analyze Job procedure in the
      CA PPM
      schema in Release 15.1 (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
  5. Upgrade your Advanced Reporting content or configure Advanced Reporting for the first time:
    1. Set up the Data Warehouse database and populate it with 
      CA PPM
      data.
    2. Install Jaspersoft and import the domain information for reporting.
  6. Install your current add-ins and connectors if an upgrade is desired.
    • Review
      Installing and Upgrading 
      for information about installing add-ins.
    • Back up your 
      CA PPM
      installation before installing each add-in so that you can restore the application if necessary.
    • Apply the Upgrade Ready content for those items that you are actively using.
      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 PPM
      content, copy the modified content before upgrading. Then, apply the new incoming stock 
      CA 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: PPM Content
      add-in available on the Content Add-ins page for upgrade-ready content. This page is available from the Administration menu. To accept the new Release 15.1 upgraded content, apply the changes.
  7. Review the Studio views and system content and manually upgrade as needed.
    The upgrade preserves all pre-existing 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 or the partition.
    To determine which views were not automatically upgraded, use the Studio Views list page.
    Use these tips to help you review the views:
    • The Last Version column identifies changes to stock views in Release 15.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 15.1 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.2 and the Upgraded column= unchecked.
  8. Verify your NSQL queries.
    During the upgrade, the checkinstall utility automatically verifies NSQL queries. Results are captured in the postcheck-results.html file of the checkinstall-results.zip file. This 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 your custom portlets work, correct any invalid NSQL queries.
    For more information about the database schema changes, see 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. In Studio, go to the NSQL tab for the imported query and click the Preview button.
    11. Confirm that the NSQL query is valid.
  9. Save the Upgrade Check Install Results Package.
    The upgrade process produces a zipped file that contains all of the artifacts that were created during the upgrade. Review the contents and save the zip package for future reference.
    The files are zipped into an archive that has a timestamp-encoded name (for example, checkinstall-results_2014-08-17_16-48-31.zip). This file is located in the checkinstall/check-logs directory, and if possible, the file is copied into the <target runtime dir>/logs/checkinstall directory.
How to Upgrade to CA PPM 15.2 from Niku 6.x, Clarity 7.x, and CA Clarity 8.x
As a best practice, we recommend the following steps for customers who are upgrading from older releases:
  1. Upgrade to 
    CA PPM
    12.1.1, 12.1.2 or 12.1.3.
  2. Verify that the upgrade is successful and run the CSA Health Report that is available from
    CA PPM
    System Administration.
  3. Create a full backup of the database and runtime file system.
  4. Proceed with the upgrade to Release 15.x.
MS SQL Server Database Compatibility Level
Release 15.1 supports database compatibility levels for SQL Server 2012 (119) and SQL Server 2014 (120). A new installation of Release 15.1 on SQL Server 2012 has the correct compatibility level of 110. If you are using SQL Server 2014 for Release 15.1, set the compatibility level to 120 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 120
SQL Server 2005 compatibility level (90) has been removed and is no longer supported.
To identify the compatibility level, use the following query:
SELECT NAME DATABASENAME ,COMPATIBILITY_LEVEL COMPATIBILITYLEVEL FROM SYS.DATABASES
Upgrade Action
: None
Oracle Database Only PRJ_BLB_SLICES Table
The ID, UNIT, LAST_UPDATED_DATE and LAST_UPDATED_BY columns in the PRJ_BLB_SLICES table have been dropped. If you are using Oracle, the table is replicated before the columns are dropped. The replication requires you to verify that the tablespace that PRJ_BLB_SLICES occupies is large enough to accommodate the temporary size increase.
Upgrade Action
:
To determine if the tablespace can deal with this condition, have your database administrator (as sysdba) run the following query. Change the schema owner to the owner of the 
CA PPM
schema:
select SLC.owner, SLC.table_name, SLC.TABLESPACE_NAME, SLC.MB MB_NEEDED,  TBSPC.MB_FREE MB_FREE, SIZING.MAX_MB, SIZING.MB_USED, EXT.AUTOEXTENSIBLE FROM (select owner, table_name, NVL(round((num_rows*avg_row_len)/(1024*1024)),0) MB, TABLESPACE_NAME from all_tables where owner = 'CLARITY' and table_name = 'PRJ_BLB_SLICES') SLC INNER JOIN (select df.tablespace_name, (df.totalspace - tu.totalusedspace) "MB_FREE" from (select tablespace_name, round(sum(bytes) / 1048576) TotalSpace from dba_data_files group by tablespace_name) df, (select round(sum(bytes)/(1024*1024)) totalusedspace, tablespace_name from dba_segments group by tablespace_name) tu where df.tablespace_name = tu.tablespace_name) TBSPC ON (SLC.TABLESPACE_NAME = TBSPC.TABLESPACE_NAME) INNER JOIN (select distinct(autoextensible), tablespace_name from dba_data_files) EXT on (slc.tablespace_name = ext.tablespace_name) INNER JOIN (select tablespace_name , count(*) as no_of_data_files , sum(MAXBYTES)/(1024*1024)*count(*) as MAX_MB , sum(user_bytes)/(1024*1024) MB_USED , round((sum(user_bytes)/(1024*1024))/(sum(MAXBYTES)/(1024*1024))*100,2) PERCENT_USED from dba_data_files group by tablespace_name) SIZING ON (SLC.TABLESPACE_NAME = SIZING.TABLESPACE_NAME)
The following example shows the kind of results that the query returns:
OWNER TABLE_NAME TABLESPACE_NAME MB_NEEDED MB_FREE MAX_MB MB_USED AUTO-EXTENSIBLE CLARITY PRJ_BLB_SLICES USERS_LARGE 1306 5020 90000 15997 YES
If AUTOEXTENSIBLE is YES:
The tablespace for PRJ_BLB_SLICES can grow automatically up to the MAX_MB value. Ensure that the MAX_MB value is higher than the MB_NEEDED + MB_USED.
If AUTOEXTENSIBLE is NO:
Ensure that the MB_NEEDED value is less than MB_FREE. If the MB_NEEDED value is not lower, the database administrator can allocate or extend extra data files to the tablespace under the TABLESPACE_NAME column.
We recommend increasing the tablespace at least 20 percent more than is needed. The increase helps to ensure that the tablespace can accommodate standard data growth and the temporary replication.
Filestore and Search Index Location Changes
Two significant changes to the 13.x, 14.1, and 14.2 upgrade processes directly affect the filestore feature. The changes require you to act during the upgrade process to ensure that the filestore feature operates correctly after the upgrade.
The actions are necessary only if your files are not stored in the database. If files are stored in the database, no action is required.
You can determine if your files are stored in the database using the
CA PPM
 System Administration (CSA) application. Log in to CSA and navigate to the Documents and Search link under the Properties tab, then review the Store Files in Database property.
If the database is not the filestore repository, action is required. Failure to follow the recommended steps can lead to permanent loss of the filestore contents.
The following changes were made to the upgrade process in Version 13:
  • The upgrade process always installs to an empty destination folder. During the upgrade, files and folders that exist in the target installation folder are moved to a new location before the new files are installed. If the filestore folder is located in the runtime folder, it is moved with the other content (
    not recommended
    ). If the filestore is located outside the runtime folder (the
    recommended
    configuration), the filestore location is not moved or copied from the backup location.
  • The filestore and search index folder structures were altered to accommodate architectural changes in Version 13. This change requires action for all Release 13.x and 14.x upgrades, whether the filestore was located in the installation folder or not.
Your action depends on the following factors:
  • Where the filestore was before the upgrade
  • The target installation folder that is selected during the upgrade
The correction must be made immediately after the upgrade completes, before any files are added to the filestore. Any files added to the filestore before the correction is made must be manually preserved using the following steps:
  1. Use 
    CA PPM
    to retrieve the newly checked-in documents and save them to a temporary location on the file system.
  2. Perform the steps for the appropriate use case (A, B, or C) in the following Upgrade Action.
  3. To check the saved documents back into the 
    CA PPM
    filestore, use
    CA PPM
    .
  4. Execute the following commands from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Upgrade Action
: Complete the filestore and search index correction procedure.
Before you start, create a backup of the filestore so that recovery is possible in the event of an unexpected problem. Your document store could be used before this procedure can be completed. If so, the newly included documents must be added back to the filestore after you complete the correction procedure.
The following use cases illustrate the actions to take. To determine the correct course of action, use the filestore location and target installation folder.
Use Case A
  • Filestore location: The filestore was located in the 
    CA PPM
    runtime folder before the upgrade.
  • Target installation folder: The existing (preupgrade) 
    CA PPM
    runtime folder was selected as the target installation folder.
Before the upgrade process ran, the file or index folder was in the <runtime> folder. The upgrade process moved the file or folder to a folder named <runtime>_prev based on the chosen upgrade or installation option. The move resulted in the file or index folder being located in the <runtime>_prev folder. The file or index folder must be moved from the <runtime>_prev folder to another location because any subsequent upgrade attempt deletes this folder.
Perform these steps for this use case:
  1. If before the upgrade the filestore location was <runtime>/filestore, copy or move the folders under <runtime>_prev/filestore to this new path:
    <new directory>/filestore/clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices. Placing the folder outside the 
    CA PPM
    installation directory also ensures that this process is not repeated when 
    CA PPM
    is upgraded.
    Log in to the CSA application, navigate to the Documents and Search link under the Properties tab, and update the Filestore Directory location. For example, if the filestore path is <old clarity install directory>/filestore, modify the path to <new directory>/filestore.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  2. If before the upgrade the search index directory location was <runtime>/searchindex, copy or move the folders under <runtime>_prev/searchindex to this new path:
    <new directory>/ searchindex /clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices.
    Log in to the CSA application and navigate to the Documents and Search link under the Properties tab and update the Index Directory location. For example, if the filestore path is <old clarity install directory>/searchindex, modify the path to <new directory>/searchindex.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Use Case B
  • Filestore location: The filestore was located in the runtime folder before the upgrade.
  • Target installation folder: A new, empty folder was selected as the target install folder.
Before the upgrade process ran, the file or index folder was located in the <runtime> folder. The upgrade process produced a different folder named <new runtime>. This process was based on the upgrade or installation option to select a different folder for the upgrade result than the current one. This choice has resulted in the file or index folder being located in the <runtime> folder.
Perform these steps for this use case:
  1. If before the upgrade the filestore location was <runtime>/filestore, copy or move the folders under <runtime>/filestore to this new path:
    <new directory>/filestore/clarity
    Where <new directory> is located outside of the upgrade resulting <runtime> directory. Having the location outside of the runtime folder follows best practices. Locating the folder outside the installation directory ensures that this process is not repeated in the future when 
    CA PPM
    is upgraded.
    Log in to the CSA application and navigate to the Documents and Search link under the Properties tab and update the Filestore Directory location. For example, if the filestore path is <old clarity install directory>/filestore, modify the path to <new directory>/filestore.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  2. If before the upgrade the search index directory location was <runtime>/searchindex, copy or move the folders under <runtime>/searchindex to this new path:
    <new directory>/ searchindex /clarity
    Where <new directory> is located outside the upgrade resulting <runtime> directory. Having the location outside the runtime folder follows best practices.
    Log in to the CSA application, navigate to the Documents and Search link under the Properties tab, and update the Index Directory location. For example, if the filestore path is <old clarity install directory>/searchindex, modify the path to <new directory>/searchindex.
    Do not append ‘clarity’ to the path in the CSA. The 
    CA PPM
    architecture adds this update internally.
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
Use Case C
  • Filestore location: The filestore was located outside the runtime folder before the upgrade.
  • Target installation folder: The target installation folder is not relevant to this use case. These steps must be performed for all upgrades with an external filestore.
The file or index folder is not located in the <runtime> folder.
Perform these steps for this use case:
  1. If the previous filestore folder path is now located in <some folder>/filestore, copy or move the folders under <some folder>/filestore to this new path:
    <some folder>/filestore/clarity
  2. If the previous search index folder path is now located in <some folder>/searchindex, copy or move the folders under <some folder>/seachindex to this new path:
    <some folder>/seachindex/clarity
  3. Execute the following command from the <runtime>/bin folder:
    admin search recreate-index-files admin search recreate-index-data
No modification to the Filestore Directory or Index Directory properties is needed. You can view these properties from the Properties tab, Documents and Search subtab in the CSA application.
Do not append ‘clarity’ to the path in the CSA. The 
CA PPM
architecture adds this update internally.
Preserve Your File Directory Customizations
During the upgrade, you are prompted for the target installation directory. New preupgrade and postupgrade steps let you copy files to and from the 
CA PPM
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in the 
CA PPM
directories.
Templates are provided in release-specific upgrade folders that are located in the installer root directory (at the same level as the install.bat file). The templates are:
preprocess-upgrade.xml
and
postprocess-upgrade.xml
.
Example of preprocess-upgrade.xml script
<project name="content" default="upgrade" basedir="."> <target name="upgrade"> <echo>Preserving customer specified files prior to upgrade from install.dir = ${install.dir}</echo> <if fileexists="${install.dir}" not="true"> <fail>Install dir not specified = ${install.dir}</fail> </if> <delete dir="upgrade_temp"/> <mkdir dir="upgrade_temp" /> <!-- Uncomment the copy below and list the files to be included for preservation --> <!--<copy todir="upgrade_temp"> <fileset dir="${install.dir}" > <include name="myfiles/my*.*"/> <include name="abb/*01.jar"/> <include name="a*01.jar"/> </fileset> </copy>--> </target> </project>
Example of postprocess-upgrade.xml script
<project name="content" default="upgrade" basedir="."> <target name="upgrade"> <echo>Restoring customer specified files after upgrade to install.dir = ${install.target.dir}</echo> <if fileexists="${install.target.dir}" not="true"> <fail>Install dir not specified = ${install.target.dir}</fail> </if> <!-- Uncomment the copy task below and list the files to be restored that were preserved in the preprocess-upgrade.xml script.--> <!--<copy todir="${install.target.dir}"> <fileset dir="upgrade_temp" > <include name="myfiles/my*.*"/> <include name="abb/*01.jar"/> <include name="a*01.jar"/> </fileset> </copy>--> </target> </project>