Change Impact and Upgrade

ccppmop1581
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
15.8.1. Plan your
Clarity
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 compatibility related information see, Hardware and Software Compatibility Specifications
For installation and upgrade related information see Installing and Upgrading
For example, you are upgrading from
Clarity
Release 15.3 to 15.8. Review the changes in releases 15.4, 15.4.1, 15.5, 15.5.1, 15.6, 15.6.1, 15.7 and 15.7.1 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
15.8.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
SaaS Now Supports Jaspersoft 7.1.3 on the Google Cloud Platform
Clarity
SaaS customers on GCP will soon be upgraded to Jaspersoft 7.1.3. Customers can continue to use Jaspersoft Studio 7.1 and their existing studio and SOW solution adapters. See Install Jaspersoft Studio Professional 7.1 and CA JDBC Adapter for more information.
Clarity
GCP SaaS Customers Only
The domains migrated to PostgreSQL will display errors when viewed or edited in the Domain Designer. Please review this KB article to resolve this issue.
You can also review this KB article on connection failures between Jaspersoft Studio and Jaspersoft server.
Clarity
will announce support for Jaspersoft 7.1.3 for on-premise customers in the near future.
Clarity
15.7 Onward - OracleJDK will be replaced with AdoptOpenJDK
Java Image
Clarity
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
that supports AdoptOpenJDK. This change does not impact Jaspersoft, which will continue to support Java 8.
2
Clarity
PPM is now
Clarity
Clarity
PPM has now been rebranded as
Clarity
. You can see the new
Clarity
logo on the login screen and the New User Experience. The documentation has been updated to reflect the new brand.
Clarity
refers to the New User Experience, and
Classic PPM
refers to the
Classic PPM
Studio.
Clarity
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you will see the new
Clarity
logo.
The following video describes the enhancement made to Clarity logo in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Custom Master Objects, Subobjects, and Custom Virtual Attributes are Available in
Clarity
You can now API enable custom master objects and custom sub-objects in
Classic PPM
so that they are available in
Clarity
. Let’s consider a scenario where you use
Clarity
to manage the entire product lifecycle. You now want to capture Net Promoter Score (NPS) for all your products and save this data in
Clarity
. You also want to ask customers specific questions about the support and services processes. However, you want to save this data separately from the NPS scores. You can create a custom object master in
Classic PPM
called NPS, and API enable it so that it is available in
Clarity
. You can then create two sub-objects, namely Services and Support, API-enable them. You can then use
Clarity
to save your NPS data and the associated Services and Support survey details.
API enable custom master objects and custom sub-objects in Clarity
You can also use XOG to API enable stock and custom virtual attributes in
Classic PPM
. Custom Virtual attributes are only defined on sub-objects. A virtual attribute is a read-only attribute on the sub-object that is linked to a specific attribute on the master object.
You cannot use
Classic PPM
to API enable stock and custom virtual attributes.
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you will be able to API enable existing custom master objects and custom sub-objects. You can then work with them in
Clarity
. You can also use XOG to API enable stock and custom virtual attributes.
The following video describes the enhancements that are made to custom objects and subobjects in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Financial Management Enhancements
You can create benefit plans in Projects, Custom Investment, and Ideas by using the Financials module. You can then associate your cost plans with benefit plans to estimate the benefit from your investments or Net Present Value (NPV) on an investment.
Create benefit plans in investment objects using Financials module in Clarity
While a benefit plan can be associated with an unlimited number of cost plans, a cost plan can have only one associated benefit plan. You can use the Financials module to create new benefit plans or update existing plans. Remember, you cannot delete a benefit plan that is associated with a cost plan.
Remember that the saved views are shared across the financial modules of different investment types. For example, if you save a view in the Benefits Plan grid for a custom investment, the same view is available in the Benefits Plan grid for ideas and projects.
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you can associate existing benefit plans that were available in
Classic PPM
within
Clarity
. You can also create new benefit plans directly in
Clarity
.
The following videos describe the enhancements that are made to the financials module in Projects, Custom Investment, and Ideas.


This video will not be available when you download the documentation in PDF format. Click here and here to watch the video on YouTube.
Common Search Component
You can use the Search bar available across the board, gird, and timeline layouts to filter values based on the name or ID. Consider an example where you want to locate a specific task in an investment. You can simply type the first few characters of its name in the Search bar to locate it and edit it.
Common Search Component in  Clarity
The search values are not persisted when you save a view. Also, if you navigate away and return to the workspace, the search bar will be cleared.
You can use the Search bar alongside the traditional filter available in
Clarity
. Consider an example where you use the filter to identity all the tasks that have not started and then use the search bar to look for a specific task.
Clarity
only displays results that meet the criteria of the filter and the Search bar.
The Search bar is not available in Roadmaps, the Staff module, and the Assignments module.
To learn more, see Common Components
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, you will see the new Search bar across the board, grid, and timeline layouts.
Custom Drop-down Enhancement
From
Clarity
15.8.1 onwards, the Static Value Lookup drop-down contains a search option to let you quickly search for the attribute instead of scrolling the entire list. If the name of the attribute is too long,
Clarity
displays the name with ellipses. The search functionality is applicable in all places where Static Value Lookup is applied.
Searchable Dropdown
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, you will see the search bar in static value lookups.
Increased Hyperlink Length When You Export to Excel (
Classic PPM
)
The Export to Excel functionality in
Classic PPM
has been enhanced to support links that have upto 2085 characters. In previous releases, a hyperlink was removed from the Microsoft Excel file, when you used the Export to Excel functionality, whenever the URL was greater than 255 characters. From
Clarity
15.8.1 onwards, the limit of the length of the URL has been increased from 255 to 2085 characters.
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1 and use the Export to Excel functionality, you will see relevant links in the Microsoft Excel file.
The following video describes the various UI enhancements that are made in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Field Level Security is Supported for Custom Investments
Field level security is now available for custom investments. Consider an example where Sid – a portfolio manager is responsible for creating, editing, and managing Custom Investment Items for his organization. Sid creates a custom investment to define the strategy of his organization. He secures the Estimated Budget Plan attribute and provides relevant stakeholders with edit rights. The stakeholders can now review and update the Estimated Budget Plan for relevant strategies.
Field Level Security
After the strategy is finalized, Sid shares the strategy with the teams. All the resources in the team have view access to the Estimated Budget Plan attribute.
To learn more, see Secure Field Level Access
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you can use Field Level Security to secure attributes associated with Custom Investments.
The following video describes the various enhancements that are made to Field Level Security in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Customize the Header and Login Logos
You can now customize the header logo and the login logo for
Clarity
reflects your organization’s branding. You can also use it to differentiate between various environments, such as development, QA, and production. To learn more, see Clarity: System Settings
You need to have administrative privileges to update the logos.
Clarity
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you can use the System Settings in
Clarity
to customize it so that it reflects your organization's branding.
The following video describes the various UI enhancements that are made in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Configuring
Clarity
to Support SAML 2.0 (On-Premise only)
Clarity
15.8.1 and higher releases allow on-premise customers to use the credentials issued by an IDP - that supports SAML 2.0 - and log into
Clarity
. Some key advantages of using SAML-based SSO login are:
  • Seamless integration between networks and environments: All users can move easily between your organization's intranet and
    Clarity
    .
  • Simplified password management: No need to manage user passwords separately from
    Clarity
    , because your existing user management system handles password management.
Add Staff to Investments by Using the Multi-Select Grid
You can use the new Add Staff button to add resources, roles, and teams to an investment in
Clarity
. After you click the Add Staff button, you can choose if you want to add resources, roles, or teams. If you choose resources,
Clarity
loads a list of all the resources available to you in a generic multi-select grid. You can use the search and filter options to quickly identify the relevant resources and add them to the investment.
Add Staff to Investments by Using the Multi-Select Grid in Clarity
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, you can start using the new Add Staff button to add resources, roles, and teams to your investments.
The following video describes the various enhancements that are made to staffing in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
View Work Effort in Days
You can now configure
Clarity
to display work effort in Days. In previous versions of
Clarity
, you could only view work effort in FTE or Hours. You can now use General Settings to configure the work effort to be displayed in days. This is extremely useful in the Staff Module or the Assignment module in projects and custom investments in
Clarity
. This setting does not impact the following areas:
  • Staffing Workspace
  • Timesheets
  • Financials
  • Roadmaps
Display work effort in days in Clarity
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, you can configure
Clarity
to display the work effort in days.
Removed Warning Message from Staffing Workspace (Mixed Bookings Enabled)
In
Clarity
15.8.1 and future releases, you do not see a warning message on the Staffing workspace informing you that the page is available in read-only mode since mixed booking is enabled. The Staffing workspace will continue to be in read-only mode if you have enabled mixed booking.
Clarity
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, will not see a warning message when you access the Staff workspace. This is applicable when you have enabled Mixed Bookings in
Classic PPM
.
Staffing Workspace Now Supports Custom Investments
You can use the Staffing workspace to plan role allocations, request resources, and staffing of Custom Investments. In previous releases of
Clarity
, you could only use the Staffing workspace for Projects and Ideas.
Staffing Workspace Now Supports Custom Investments in Clarity
Upgrade Action
: When you upgrade to
Clarity
15.8.1, you can start using the Staffing workspace to staff Custom Investments. This was not supported in previous releases of
Clarity
.
The following video describes the various enhancements that are made to staffing in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Improved Import Capability in Roadmaps
The Import from
Clarity
option now displays the corresponding grid with selection checkboxes. Until release
Clarity
15.8 the import option lets you search for specific investment objects. From
Clarity
15.8.1 onwards you can select Projects, Ideas, or Custom Investment Items from the respective grid. The selection grid lets you select individual row items. You can also select or deselect all rows.
Staffing Workspace Now Supports Custom Investments in Clarity
Upgrade Action
: No impact. When you upgrade to
Clarity
15.8.1, you can start using the enhanced import capability to import investments into roadmaps.
The following video describes the various enhancements that are made to roadmaps in this release.

This video will not be available when you download the documentation in PDF format. Click here to watch the video on YouTube.
Internet Explorer 11 Not Supported for
Clarity
Features
Classic PPM
still supports IE 11; however,
Clarity
cannot extend backward compatibility with any old browser technology, including IE 11.
This is not a known issue with
Clarity
. 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
Clarity
, 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
, switch to a new browser such as Edge, Firefox, or Chrome.
Dashboards Not Available in Google Cloud Platform
The Project Management Schedule Dashboard and Project Management Cost and Effort Dashboard portlets have been deprecated in the Google Cloud Platform. Please review this KB article for more information.
Users that use Spanish (Peru) locale will now have the period symbol as a decimal separator.
Change
: Users that use the "Spanish (Peru)" locale will now have the period "." symbol as the decimal separator instead of the comma "," symbol.
Impact
: If the user keeps the Peru locale and tries to use the comma as the decimal separator the symbol will be ignored and it will cause entered values to be saved as large integers instead of the expected value with decimal digits. If desired, the user can choose a different locale in account settings that uses the comma as the decimal separator.
More Details
: The Official Institute of Taxation of Peru uses "." as its decimal separator. Therefore Java (JDK 11.0.5) has been fixed to honor the period symbol instead of a comma. For more details on the Java fix reference their KB article.
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.
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
account settings to one of the supported languages listed in the Release Notes.
Clarity
help will be available only in English for a couple of months after release. The Help link in
Classic PPM
will automatically redirect you to the English site. The help link in
Clarity
currently defaults to the localized site and displays a blank page since the content is not localized. Broadcom will fix this issue in future releases.
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
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
Classic PPM
  • Data Warehouse Configured
  • Load Data Warehouse Job Completed
Clarity
  • PMO Accelerator Add-in Installed
Install PMO or APM add-ins
  • Data Warehouse Configured
Supported Upgrade Paths for Release
15.8.1
Please review the table to identify the minimum supported release from which you can upgrade to the latest version of
Clarity
.
Clarity Version
Minimum Supported Version for Direct Upgrade
15.8.1
15.6.1
15.8.0
15.3
15.7.1
15.3
15.7.0
15.2
15.6.1
15.0
15.6.0
15.0
15.5.1
14.3
15.5.0
14.3
15.4.1
14.1
15.4.0
13.2
15.3
13.2
15.2
13.2
15.1
13.2
  • If you have Release 14.3 or older, your release is no longer supported. Upgrade to Release 15.4 first, and then upgrade to
    15.8.1
  • You cannot upgrade to Release
    15.8.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.8 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, from 15.7 to 15.7.1, from 15.7.1 to 15.8, and from 15.8 to 15.8.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.8. After the upgrade, install the latest 15.8 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
Clarity
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
    installer to the
    Clarity
    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
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
, 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
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
Clarity
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 a 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
    Clarity
    .
  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,
Clarity
provided the functionality with no net loss to end-users. We recommend that you perform an analysis comparing the value of
Clarity
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
Clarity
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in
Clarity
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'