Change Impact and Upgrade

ccppmop1571
HID_HID_release_info_change_impact_od
This
Change Impact and Upgrade
page highlights significant changes, required actions, known issues, and recommended options for customers upgrading from the previous release to
Clarity PPM
Release 15.7.1. Plan your
Clarity PPM
upgrade and determine the options that fit your business needs. Teams can also use this information to plan your new feature adoption, onboarding, and training efforts.
For example, you are upgrading from Clarity PPM Release 15.3 to 15.7.1. Review the changes in releases 15.4, 15.4.1, 15.5, 15.5.1, 15.6, 15.6.1 and 15.7 before and after you upgrade. To switch to the
Change Impact and Upgrade
page for each release, click the
Versions
menu at the top of this page. Check back often for updated content, especially if you downloaded a PDF file. The English edition of this documentation is periodically updated with new information including new examples, explanations, corrections, and patch information.
To prepare for an upgrade to
Clarity PPM
Release 15.7.1, review the supported upgrade paths, features, enhancements, and required upgrade actions. The following information summarizes how the new changes introduced in this release impact your upgrade experience.
Clarity PPM 15.7 Onward - OracleJDK will be replaced with AdoptOpenJDK
Java Image
Clarity PPM will discontinue product updates related to Oracle Java, beginning
August 19, 2019
. This will allow our development team to focus on adding value to future product releases.CA Technologies, a Broadcom Company (CA), continues to support its products and stand by the terms and conditions set forth in the license agreements between CA Technologies and its customers.
Existing customers may continue to run and use releases that include Oracle Java components in production and non-production environments
. However, to address any future Java security and vulnerability issues that may arise, it may be necessary for customers to install a service pack or upgrade to a newer release of Clarity PPM that supports AdoptOpenJDK.This change does not impact Jaspersoft, which will continue to support Java 8.
2
Clarity PPM New User Experience: Custom Investment Enhancements
STAFF Module
You can use the grid in the STAFF module to identify and add people, roles, teams, and even non-labor resources by name or ID. The STAFF module is built using the same common component that is used in Projects. You can ask your administrator to use blueprints to add the STAFF module to your custom investment item.
image2019-4-26_15-41-9.png
Some key activities you can perform by using the STAFF module are:
  • Add people, roles, teams, and even non-labor resources by name or ID
  • Use PER-PERIOD METRICS field to view a time-scaled series of time-sliced data for allocations
  • Set the hard or soft booking type for roles and resources
  • Replace a role with a different role, a team, or a resource.
  • Replace a resource with a different resource, team, or a role.
  • Replace a team with a different team, a resource, or a role.
Some key points you need to remember while using the STAFF module are:
  • Saved views in the STAFF module, including detail configuration, are shared across different objects.
  • Clarity PPM retains user settings for FTE or Hours regardless of the view.
  • The Start and End period for a saved view in the STAFF module is retained across objects.
  • Saved views created in the STAFF module of the Project object in older releases of Clarity PPM will be available in custom investment STAFF module after upgrading to 15.7.1.
In Clarity PPM 15.7.1, you cannot use the Staffing Workspace to allocate resources to staff custom investment items. You can use the Resources to Investments view to review the current resource allocation and identify potential resources. However, you cannot use the Investment to Resources view or the Requests section to staff custom investment items. You need to use the Staffing grid in the investment item to make any staffing changes.
For more information about Staff Module, see Custom Investments Staff an Investment.
Upgrade Action
: The Standard blueprint associated with your custom investments will include the STAFF module. Clarity PPM will not update any user-defined blueprints. You need to request your administrator to create a copy of the Standard blueprint and assign the STAFF module to your custom investment item.
TASKS Module
You can now add the TASKS module to a custom investment item in Clarity PPM. A task is a unit of work in a project plan that is assigned to one or more resources for a specified period.
Group By.jpg
The TASK module includes the following layouts:
  • Timeline layout
    – View and manage tasks in a hierarchical timeline so that you can see and manage multiple sub-level task and their relationships.
  • Board layout
    – View project tasks as cards, which you can arrange with drag-and-drop precision on a board layout with columnar swim lanes.
  • Grid layout
    – Analyze project tasks quickly by using an excel-inspired grid layout
Some key points you need to remember while using the TASKS module are:
  • Saved views in the TASKS module including detail configuration are shared across different objects.
  • Clarity PPM retains user settings for FTE or Hours regardless of the view.
  • The Start and End period for a saved view in the TASKS module is retained across objects.
  • Saved views created in the TASKS module of the Project object in older releases of Clarity PPM will be available in custom investment TASKS module after upgrading to 15.7.1.
  • Local picklist, when used in saved views, are automatically removed when accessing it from another object instance.
  • Custom attributes created in Clarity PPM Studio can be used between projects and custom investments.
For more information about Tasks Module, see Custom Investments Tasks and To-Do Items.
Upgrade Action
: The Standard blueprint associated with your custom investments will include the TASKS module. Clarity PPM will not update any user-defined blueprints. You need to request your administrator to create a copy of the Standard blueprint and assign the TASKS module to your custom investment item.
ASSIGNMENTS Module
You can now use the ASSIGNMENTS module in custom investment type to manage task assignments, perform resource and role planning, and monitor estimate-to-complete (ETC) values for your team members directly inside an investment item. You can also apply filters, saved views, and specify your choice of assignment attributes that appear as columns in the ASSIGNMENTS grid. The familiar grid features include grouping, sorting, and exporting to CSV.
image2019-5-23_18-20-1.png
Some key points you need to remember while using the ASSIGNMENTS module are:
  • Saved views in the ASSIGNMENTS module including detail configuration are shared across different objects.
  • Clarity PPM retains user settings for FTE or Hours regardless of the view.
  • The Start and End period for a saved view in the ASSIGNMENTS module is retained across objects.
  • Saved views created in the ASSIGNMENTS module of the Project object in older releases of Clarity PPM will be available in custom investment ASSIGNMENTS module after upgrading to 15.7.1.
For more information about Assignments Module, see Custom Investments: Assign Resources, Roles, or Teams to Tasks.
Upgrade Action
: The Standard blueprint associated with your custom investments will include the ASSIGNMENTS module. Clarity PPM will not update any user-defined blueprints. You need to request your administrator to create a copy of the Standard blueprint and assign the ASSIGNMENTS module to your custom investment item.
OBS Support for Custom Investments
You can associate custom investments with organizational breakdown structure (OBS) and associate specific departments and locations with custom investment items. OBS can then be used in filters and security rights.
Upgrade Action
: You can now associate existing custom investment items with the relevant OBS in your organization.
Custom Investment Access Rights
You can now provide access to specific custom investments. If you are provided with the
<custom investment type name> - Navigate
access right, you should be able to see the specific custom investment tile. For example, if you have a custom investment named Business Case, you need the Business Case-Navigate access right to view the custom investment item.  You can then provide the relevant access rights, to allow resources to perform actions such as creating and editing cost and budget plans.
To learn more about Custom Investment Access Rights, see Clarity PPM Access Rights.
Upgrade Action
: If you have existing custom investment items, use blueprints to add the STAFF, TASKS, and ASSIGNMENTS modules. Then, use the new access rights to determine which resource can access what module based on their requirements.
Cost Plan Details: Actuals, Units, and Revenue for Custom Investments
You can now view the actual costs posted during the fiscal period for the custom investment. This will help you to compare Planned to Actuals for the custom investment. You can adjust your view of the Custom Investment grid to show fiscal or calendar per-period metrics (also known as time-scaled values, or TSVs).
Actuals_for_Investment.png
  The following time-scaled values (TSV) fields for cost plan details are available for selection from the PER-PERIOD METRICS field:
  • Cost
  • Actual Cost
  • Actual Revenue
  • Actual Units
  • Cost Variance
  • Revenue
  • Revenue Variance
  • Units
  • Units Variance
For more information, see View Actuals Posted in Custom Investment Items.
Upgrade Action
: No action required. You can use the new Update Financial Plan Actuals job that has been added in Clarity PPM 15.7.1 to post actuals in custom investment items.
Clarity PPM New User Experience: Introducing Hierarchies (BETA)
You can now use Hierarchies in Clarity PPM to create one or more hierarchies and define the relationship between various investments. Each hierarchy includes a tree with multiple cards. You can establish a parent-child relationship between cards to help your stakeholders understand the dynamics of your products. Your stakeholders can use the Hierarchies (beta) page to view all the hierarchies in your organization. In this release, you can add investments (ideas, projects, and custom investments) as cards to a hierarchy.
Hierarchy
Some key points you need to remember while using the Hierarchies are:
  • In Clarity PPM 15.7.1 an Investment Hierarchy is limited to a maximum of 500 cards.
  • Saved views defined at the investment level (e.g., Project, Idea and Custom Investment Type), are available on the multi-select add grid when importing those investment types.
  • If Projects or Ideas are deleted by using the Delete Investment Job, the investment types will automatically be removed from the Hierarchies.
  • The card option metrics displayed on each hierarchy card is associated only with an individual investment associated with the card. Metric aggregation or roll-ups is not available in Clarity PPM 15.7.1.
For more information about Hierarchy, see New User Experience: Create and Edit Hierarchies.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Clarity PPM New User Experience: Timesheet Enhancements
Time Entry for Custom Investments
You can now enter the number of hours for a Custom Investment task. If you log in as an individual user who has access to timesheets, you can see the tasks that are assigned to you, and can now enter time for each Custom Investment task. For more information about submitting a timesheet, see New User Experience: Enter Hours and Submit a Timesheet.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Timesheet Fields from Classic PPM Now Available in Clarity PPM New User Experience
You can now view the Classic PPM Timesheet fields on the Clarity PPM New User Experience. Your administrator must configure the classic PPM Timesheet fields. The following Classic PPM Timesheet fields are available for configuration:
  • (Task) Short Name
  • Parent
  • Parent ID
  • Phase ID
  • (Task) Start
  • (Task) Finish
  • Posted Actuals
  • Baseline
  • Role
Columns
Upgrade Action
: No action required.
Filter Resource and Resource Manager Using Resource ID
You can now filter Resource Manager and Resource using Resource ID in My Timesheet and in Review and Approve tabs.
Search by ResourceID
For more information about filters, see Common Components.
Timesheet Grid with View Component (Read Only)
You can now view Timesheets in grid layout. The timesheet grid provides you the Grid-Filter-View (GFV) capabilities.
Timesheet Grid Layout
For more  information, see View and Manage Timesheets From Grid Layout.
Upgrade Action
: No action required.
Display Effort and Project Time Gauge Configuration
You can display or hide the Effort Gauge and Project Time Gauge in Timesheets from Classic Clarity PPM.
Effort and Project Time Gauge
Upgrade Action
: No action required.
Post Timesheets Job by Location
You can now process timesheets based on the location of the resource, using the
Post Timesheets
job. The batch processing ensures greater control in choosing one or more resource location for which the timesheets must be posted.
Post Timesheets By Location
For more information, see Post Timesheets Job.
Upgrade Action
: No action required.
In this release, the ability to access internal and external applications from the main menu in Clarity New User Experience is enabled. This is very similar to the links provided in the context of a Custom Investment. However, Link channels from the main menu provide you with the ability to access internal and external applications completely outside of a specific project or custom investment. You can view, create, edit, delete Menu Links directly from the Menu Links page, based on your respective permissions. You can configure dynamic links with a placeholder for just user name using supported username variable that takes users to specific pages with personalized username attributes in the URL.
Menu Links
For more information, see Create, Edit, and Delete Menu Links.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Classic PPM: Enhancements
Classic PPM: Financial Enhancements
For a project, you can now update the associated name of the company in the
Company Name
field even after you have posted the actuals.
Upgrade Action
: No action required. You can use this feature to edit the Company after you have posted actuals.
Classic PPM: Enable SAML Authentication
The Enable SAML Authentication option allows Clarity PPM to accept SAML responses from Identity Providers such as OKTA or Auth0.
  • On-Premise Customers
    : This option is currently not applicable to Clarity PPM On-Premise customers. If you select this option, users will experience authentication issues.
  • On-Demand Customers
    : Please do not make any changes to this option. This setting governs the authentication mechanism of your Clarity PPM On-Demand environment. If you update this option, users will face authentication issues.
Upgrade Action
: No action required. Please do not update this option.
Clarity PPM New User Experience: Generic Enhancements
Create Charts in Clarity PPM Grid
You can now utilize the out-of-the-box charting experience in the common grids. The charting experience is very similar to the capabilities you find in spreadsheet applications like Microsoft Excel or Google Sheets but is directly embedded within the Clarity PPM New User Experience.
Charts
For more information see Common Components.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Static MVL component to use the searchable-drop down
You can now search for the required value wherever there is a Multi-Value Lookup. The search capability is introduced and all attributes that are listed in MVL are now available with infinite scrolling.
The limitation in the infinite scroll is that the selected values do not appear in the first half of the drop-down list now.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Infinite Scroll on Special Staff and Assignment Lookups
The ability to scroll beyond 25 items in Staff and Assignment Lookups is introduced in this release. The Resource field in Project Staff and Assignment grids now contain a searchable drop-down list. The drop-down list now accommodates all the values that are available in the lookup.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Saved Views on Sub-Objects of the Investment Abstract Object Are Available Across Objects and Instances
When you use an out-of-the-box or custom sub-object associated with the Investment abstract object (Staff, Tasks, Cost Plan), then saved views on those sub-objects are available across various objects and instances.
Example: Saved Views on the Staff Module: When you save a view in the Staff module, it will be available across all other instances and objects that are using the Staff module in Clarity PPM. In Clarity PPM 15.7.1, the Staff module is available for projects and custom investments.
For more information, Common Components
Upgrade Action:
After upgrading to 15.7.1, you will see multiple instances of the same saved view name created by the same user, including yourself.
When you upgrade to 15.7.1, the saved views the functionality has been upgraded to allow sub-object views to be shared across instances. In the past, especially on the TASKS Module, you were not able to create one view that could be reused across investments. Therefore, you might have created project-specific views with the same name in different investments. However, after the upgrade, you can see all the saved views for the same object across other investment types. Remember that, although the 'name' of the saved views are the same, they may not necessarily have the same configuration. It is up to the individual users to review their saved views and determine which views to keep or rename for better management of the views.
Instance Rights for Custom Sub-Objects
You can now provide instance rights to specific individuals for custom sub-objects in Projects, Ideas, and Custom Investments.
Upgrade Action
: You can provide instance rights for custom sub-objects created in older versions of Clarity PPM.
Clarity PPM New User Experience: Demand Management - Ideas Enhancements
You can now view the actual costs posted during the fiscal period for Ideas. This will help you to compare the Planned to Actuals values for an Idea.
An effort task is created for the idea when a Staff Member is added to the idea.
You can adjust your view of the Idea grid to show fiscal or calendar per-period metrics (also known as time-scaled values, or TSVs).
Actuals_for_Ideas.png
The following time-scaled values (TSV) fields for cost plan details are available for selection from the PER-PERIOD METRICS field:
  • Cost
  • Actual Cost
  • Actual Revenue
  • Actual Units
  • Cost Variance
  • Revenue
  • Revenue Variance
  • Units
  • Units Variance
For more information, see Ideas Effort Task and View Actuals Posted in Ideas.
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Classic Clarity PPM: MSP Integration
The following functionalities are added to MSP integration
  • Lightweight integration of Clarity PPM with MSP (BETA)
  • One way import of project details from MSP to Clarity PPM (BETA)
  • Copy and paste project tasks in MSP
Upgrade Action
: No action required. This is a new feature introduced in Clarity PPM 15.7.1.
Internet Explorer 11 Not Supported for New User Experience Features
Classic PPM still supports IE 11; however, the
New User Experience
cannot extend backward compatibility with any old browser technology, including IE 11.
This is not a known issue with Clarity PPM. Instead, it is a known issue with IE 11. Microsoft has invested in a new browser, Microsoft Edge.
If users ignore the support requirements and attempt to use IE 11 with the
New User Experience
, the following problems could occur:
  • Defective features or memory leaks (with no scheduled fixes from Microsoft)
  • Missing browser framework support for new REST API capabilities
  • Poor appearance or slow performance with HTML 5 and new Angular components
  • Links to other sites stop working or show messages indicating you need to update your browser
For example, using IE 11, you could cause your roadmap timeline to stop working, the staffing pages might not load all resources, and other problems could occur that appear to be
random
until users realize they are using old unsupported browser technology to access a completely new drag-and-drop feature-rich web application interface. For best results when viewing the modern user experience pages in Clarity PPM, switch to a new browser such as Edge, Firefox, or Chrome.
Cannot Upgrade on Oracle Until Security License and MD5 Package Are Enabled
  1. Contact your database administrator or Oracle to obtain the advanced security license (OAS) required only if using DBMS_CRYPTO.
  2. Enable and grant explicit permissions to dbms_obfuscation_toolkit.md5 (also provided with your Oracle installation).
  3. Start the upgrade to 15.7.
Known Issue Due to Dropped Support for Languages
This release no longer supports the following languages:
Catalan
Czech
Danish
Finish
Hungarian
Dutch
Norwegian
Polish
Russian
Swedish
Turkish
Chinese-Simplified
Chinese-Traditional
Korean
As a result, a user might see a raw text label or English text in the user interface instead of the translated text.
Workaround
: Switch your Clarity PPM account settings to one of the supported languages listed in the Release Notes.
Export to CSV Shows No Per-Period Metric Data Unless Totals Column is Present
The project STAFF and ASSIGNMENTS grids use the Totals and Per-Period Metrics columns for ETC, ETC Cost, Actuals, and Actual Cost.
  • If the Totals column and the Per-Period Metrics columns are configured on the grid, the Export to CSV file feature works as expected.
  • If you don't have the Totals column configured in the grid, the export does not work as expected (all per-period metric columns are blank).
Workaround
: In the grid, click Column Panel and add the Totals column to the grid layout before using Export to CSV.
Known Issue with Fresh Installations of Jaspersoft 7.1
In on-premise environments, you might observe the following
Failed to execute: create index
entry in the installation logs during a new installation of Jaspersoft 7.1.0 on Oracle 11g R2 or 12c:
[exec] [exec] init-js-db-pro:
[exec] [exec] [echo] For JDBC driver the artifactId and version properties are set:
[exec] [exec] [echo] maven.jdbc.artifactId=ojdbc8
[exec] [exec] [echo] maven.jdbc.version=12.2.0.1.0
[exec] [exec] [echo] Specified JDBC driver jar exists
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/js-pro-create.ddl
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql]
Failed to execute: create index
idx46_jiresfldr_hidden_idx on JIResourceFolder(hidden)
[exec] [exec] [advanced-sql] java.sql.SQLException: ORA-01408: such column list already indexed
[exec] [exec] [advanced-sql] 0 rows affected
[exec] [exec] [advanced-sql] Executing resource: /fs0/clarity1/install_cd/ca_ppm_jaspersoft_7.1.0/buildomatic/install_resources/sql/oracle/quartz.ddl
You can ignore this entry. The warning appears to be alerting you about a duplicate index creation scenario; however, it is not a valid warning.
  • This warning has no impact on your installation and does not affect any Jaspersoft 7.1 functionality.
  • CA Engineering teams confirmed that all the DDL commands are successfully executed after the reported warning.
  • The warning only appears on new Oracle installations; it does not occur with supported versions of Microsoft SQL Server
Review Cancelled Jobs After Upgrade
Please review any Clarity PPM jobs that are in the Canceled state after your upgrade is complete. Please pay special attention to any canceled jobs that were previously recurring jobs. Sometimes, after an upgrade, job parameters change and the jobs move to a canceled state. If you don't proactively review canceled jobs, you will only notice them after you receive escalations from the business.
Installation and Upgrade Dependencies
The install and upgrade scripts in this release introduce the following dependencies in the listed chronological order:
Install/Upgrade of This Component:
Requires This Component:
Upgrade
Clarity PPM
  • Data Warehouse Configured
  • Load Data Warehouse Job Completed
New User Experience
  • PMO Accelerator Add-in Installed
Install PMO or APM add-ins
  • Data Warehouse Configured
Supported Upgrade Paths for Release 15.7.1
To upgrade
directly
to this release (15.7.1), your current release must be 15.3 or higher. The 15.7.1 installer can backup and upgrade your data from supported older releases.
  • If you have Release 14.3 or older, your release is no longer supported. Upgrade to Release 15.3 first, and then upgrade to 15.7.1
  • You cannot upgrade to Release 15.7.1
    directly
    from Release 14.2 with Jaspersoft 5.6.1 or from Release 14.3 with Jaspersoft 6.1.0. The Jaspersoft 6.4.2 or 7.1 upgrade does not support those configurations. Your
    indirect
    upgrade is still supported. For example, upgrade to 14.3 and Jaspersoft 6.4.2 first. Then upgrade to 15.7 and upgrade to Jaspersoft 7.1.
  • You can upgrade from a previous release even if you have no Jaspersoft reports environment configured. The data warehouse is required; however, reporting is not required. You can elect to upgrade from 14.x and perform a fresh installation of your reports environment.
  • To upgrade from earlier 13.x releases, it often helps to upgrade to 14.3 or 14.4 first and skip the Advanced Reporting component. This approach simplifies the troubleshooting and restart process if an upgrade step fails. Then, from 14.x, you can upgrade to 15.6 and install Jaspersoft 7.1 for Advanced Reporting.
The installer detects how many incremental upgrade steps are required to update your installation to the latest release. If two or more, you are prompted to decide if you would like the installer to save automated backups at each step. For example, from 15.4 to 15.5, from 15.5 to 15.5.1, from 15.5.1 to 15.6, from 15.6 to 15.6.1,  from 15.6.1 to 15.7, and from 15.7 to 15.7.1
If you have installed any patches on the base version, verify that you applied the latest supported cumulative patch before and after you upgrade. Patch maintenance before and after upgrades is important for troubleshooting, security fixes, and general system health.
Follow these steps
:
  1. Select your current release from the
    Versions
    menu at the top right of that help page.
    For example, select 15.1 and verify you installed the 15.1.0.9 patch or select 15.3 and verify that you installed the 15.3.0.5 patch before starting your upgrade to 15.7.1. After the upgrade, install the latest 15.7 patch.
You might experience issues if you attempt to upgrade directly from an unsupported patch level. For best results, follow a supported upgrade path. To learn more, contact CA Support. You can also visit the CA PPM Community to collaborate with other community members about your specific questions.
Pre-Upgrade: Run the Installation Checker (On-Premise Only)
The Installation Checker (checkinstall) utility assesses any installation or 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.
Follow these steps:
  1. Extract the
    Clarity PPM
    installer to the
    Clarity 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  (On-Premise Only)
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
Clarity 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
Clarity 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 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 file in another directory, the installer prompts you for the file location.
Upgrade Large Data Sets  (On-Premise Only)
If your
Clarity 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 this release. Create a
memory.properties
file 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
MS SQL Server Database Compatibility Level
If you are using SQL Server 2016 for this release, set the compatibility level to 130 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 130
Custom Processes, Scripts, and Other Customizations
CA PPM cannot upgrade any unsupported customized content. Customizations must be disabled and may need to be redesigned and re-implemented to work with changing product functionality.
! After an upgrade, unless you disable them, your customizations might result in errors or fail to work as expected.
Follow these steps
:
  1. Identify your custom content. For example, you have one or more custom processes with custom GEL scripts that modified timesheet status attributes in a previous release.
  2. Acknowledge the customizations and recognize that the upgrade scripts might not support the custom content. Even if the custom content is upgraded, it may no longer work as expected. For example, your custom process references an object or attribute that has changed in the new release.
  3. As an on-premise administrator, the checkinstall script provides a warning for customizations that it detects pre-upgrade. You can see these warnings or the referenced logs for insight into the types of customizations that can negatively impact your upgrade experience. For example:
    WARNING: Possible schema customizations have been found. Any customizations to the system are the responsibility of the customer to maintain and are not supported. To upgrade, all customizations must be reviewed, changed, or removed as needed before the upgrade. After a successful upgrade, the customizations may be added back to the system. The possible customizations found are listed in the following log files:
    check‐logs/database_customization_triggers.txt check‐logs/database_customization_indexes.txt check‐logs/database_customization_tables.txt checklogs/database_customization_constraints.txt
  4. As an on-demand (SaaS) administrator, you do not see these warnings or the referenced logs. These example messages provide insight into the types of customizations that can negatively impact your upgrade experience.
  5. In on-premise or SaaS environments, turn off your customizations before the upgrade. After the upgrade, reintroduce the customizations and test them in the Classic PPM interface. Optionally, verify the impact of the customization behavior on the
    New User Experience
    .
  6. In addition to database objects, also evaluate attribute values. Review the Oracle and Microsoft SQL database and data warehouse changes (see the Reference section in the English documentation). Validate if any of your customizations depend on any dropped, changed, or new attributes.
Some customers have experienced errors with legacy custom content. After disabling the custom process, script, or other legacy custom content, the
New User Experience
provided the functionality with no net loss to end-users. We recommend that you perform an analysis comparing the value of CA PPM features in a complete COTS/SaaS solution against the value of developing your own unsupported customizations.
Pre-and-Post-Upgrade: Preserve Your File Directory Customizations  (On-Premise Only)
During the upgrade, you are prompted for the target installation directory. New pre-upgrade and post-upgrade steps let you copy files to and from the
Clarity PPM
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in the
Clarity 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>
Post-Upgrade or Post-Install: Optimize Oracle 12c Performance (On-Premise Only)
On local installations of Oracle 12c R1 or R2, you might detect a regression issue with Oracle 12c when ORDERED hint is used in structured queries. An Oracle bug in 12c R2 can degrade performance if the optimizer is set to 12.2.0.1.
  • For systems using Oracle 12c R1 (12.1.0.2), no further action is required.
  • For systems using Oracle 12c R2 (12.2.0.1), you can optimize performance by setting the optimizer to 12.1.0.2. We recommend applying this optional local fix.
Follow these steps
:
  1. From a command prompt in Oracle, enter the following lines:
    sqlplus / as sysdba ALTER SYSTEM SET "_fix_control" = '17800514:0'; Exit;
  2. Run the following command:
    ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '12.1.0.2' SCOPE=BOTH;
  3. Verify that your Oracle 12c R2 initialization file parameters appear similar to the following example:
    *._fix_control='17800514:0' *._optimizer_multi_table_outerjoin=FALSE *.audit_file_dest='/fs0/oracle/12201/12c/admin/niku/adump' *.audit_trail='DB' *.cluster_database=FALSE *.compatible='12.2.0.1' *.control_files='/fs0/oracle/12201/12c/oradata/niku/CONTROL01.CTL','/fs0/oracle/12201/12c/oradata/niku/CONTROL02.CTL' *.cursor_sharing='FORCE' *.db_block_size=8192 *.db_name='niku' *.diagnostic_dest='/fs0/oracle/12201/12c/admin/niku/udump' *.dispatchers='(PROTOCOL=TCP) (SERVICE=nikuXDB)' *.local_listener='LISTENER_NIKU' *.nls_comp='BINARY' *.nls_date_format='YYYY-MM-DD HH24:MI:SS' *.nls_language='AMERICAN' *.nls_sort='BINARY' *.nls_territory='AMERICA' *.open_cursors=1000 *.optimizer_adaptive_plans=false *.optimizer_adaptive_reporting_only=TRUE *.optimizer_adaptive_statistics=FALSE *.optimizer_features_enable='12.2.0.1' *.optimizer_inmemory_aware=FALSE *.pga_aggregate_target=4G *.processes=1000 *.remote_login_passwordfile='EXCLUSIVE' *.session_cached_cursors=1000 *.sessions=1536 *.sga_target=80G *.streams_pool_size=536870912 *.trace_enabled=TRUE *.undo_tablespace='UNDOTBS1'