Change Impact and Upgrade (On Premise)

HID_release_info_change_impact_op
ccppmop142
HID_release_info_change_impact_op
This information provides insight on planning the 
Clarity Project and Portfolio Management (PPM)
upgrade and helps you determine the upgrade options that best suit your business needs. As the 
Clarity Project and Portfolio Management (PPM)
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
If you are upgrading from an earlier release, review the information for the updates in Release 14.2, 14.1, and the 13.x releases.
Contents
2
Supported Upgrade Paths for Release 14.2
The following unpatched releases can directly upgrade to 
Clarity Project and Portfolio Management (PPM)
 Release 14.2:
  • Clarity Project and Portfolio Management (PPM)
     Release 8.1 or Service Pack or Fix Pack 8.1.x
  • Clarity Project and Portfolio Management (PPM)
     Version 12.0 or Service Pack 12.0.x
  • Clarity Project and Portfolio Management (PPM)
     Release 12.1 or Service Packs
  • Clarity Project and Portfolio Management (PPM)
     Version 13.0 or Service Packs
  • Clarity Project and Portfolio Management (PPM)
     Release 13.1
  • Clarity Project and Portfolio Management (PPM)
     Release 13.2
  • Clarity Project and Portfolio Management (PPM)
     Release 13.3
  • Clarity Project and Portfolio Management (PPM)
     Release 14.1
Follow the upgrade path in the following table, only if you have installed any patches on the base versions:
Patch Levels
Installation Path Before Upgrading to Release 14.2
If any patch level is installed on the base version 12.1.0 (12.1.0.1 - 12.1.0.8)
Installation of 12.1.0.8 is required.
If any patch level is installed on the base version 12.1.1
(12.1.1.1 - 12.1.1.10)
Installation of 12.1.1.10 is recommended.
If any patch level is installed on the base version 12.1.2
(12.1.2.1 - 12.1.2.3)
Installation of 12.1.2.3 is recommended.
If any patch level is installed on the base version 12.1.3
(12.1.3.1 - 12.1.3.6)
Installation of 12.1.3.6 is recommended.
If any patch level is installed on the base version 13.0.1
(13.0.1.1 - 13.0.1.7)
Installation of 13.0.1.7 is required.
If any patch level is installed on the base version 13.1.0
(13.1.0.1 - 13.1.0.9)
Installation of 13.1.0.9 is recommended.
If any patch level is installed on the base version 13.2.0
(13.2.0.1 - 13.2.0.9)
Installation of 13.2.0.9 is recommended.
If any patch level is installed on the base version 13.3.0
(13.3.0.1 - 13.3.0.11)
Installation of 13.3.0.11 is recommended.
For example:
  • If you have 
    Clarity Project and Portfolio Management (PPM)
     SP 12.1.3, you can directly upgrade to Release 14.2.
  • If you have 
    Clarity Project and Portfolio Management (PPM)
     12.1.0.2, apply 
    Clarity Project and Portfolio Management (PPM)
     12.1.0.8 first to upgrade to Release 14.2.
  • If you have 
    Clarity Project and Portfolio Management (PPM)
     12.1.3.4, we recommend that you apply 
    Clarity Project and Portfolio Management (PPM)
     12.1.3.6 first to upgrade to Release 14.2.
  • If you have 
    Clarity Project and Portfolio Management (PPM)
     12.1.3.6, you can directly upgrade to Release 14.2.
If you are on a 
Clarity Project and Portfolio Management (PPM)
 patch level that is not included in the preceding list, take care when attempting an upgrade to Release 14.2. Issues can result if you try to upgrade to Release 14.2 from a patch level that is not supported. For best results, wait for a supported upgrade path to a later release or patch. To find out more, contact CA Support or your CA Services representative. Also, visit the
Clarity Project and Portfolio Management (PPM)
Community to collaborate with your community members.
The Release 14.2 installer can upgrade your data set from various older releases. The installer detects how many incremental upgrade paths are required to update your installation to Release 14.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 14.2. Although the interim upgrade is not required, it simplifies the troubleshooting and restart process if an upgrade step fails.
The Release 14.2 installer runs the upgrade processes that are included in the following table.
Version, Release, or Service Pack Currently Installed
Upgrade Processes
Earlier than Service Pack 12.1.1
Service Pack 12.1.1
Version 13.0
Release 13.1
Release 13.2
Release 13.3
Release 14.1
Release 14.2
Service Pack 12.1.1, 12.1.2, or 12.1.3
Version 13.0
Release 13.1
Release 13.2
Release 13.3
Release 14.1
Release 14.2
Version 13.0 or Service Pack 13.0.x
Release 13.1
Release 13.2
Release 13.3
Release 14.1
Release 14.2
Release 13.1
Release 13.2
Release 13.3
Release 14.1
Release 14.2
Release 13.2
Release 13.3
Release 14.1
Release 14.2
Release 13.3
Release 14.1
Release 14.2
Release 14.1
Release 14.2
Add-in Compatibilities for CA PPM 14.2
Review this important information about upgrading installed add-ins, accelerators, and connectors for Release 14.2.
  • If you are upgrading from Releases 13.x or 14.1 to Release 14.2, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Clarity Project and Portfolio Management (PPM)
       Solution Pack (CSP)
      The CSP add-in is supported only for existing customers. This add-in is not supported for new 
      Clarity Project and Portfolio Management (PPM)
      installations.
    • CA Agile Planning
  • If you are upgrading from any version before Version 13.0 to Release 14.2, upgrade all installed add-ins.
  • Starting with Version 13.3, a new installation process is required for add-ins, accelerators, and connectors.
    For more information, see
    Installing and Upgrading
    .
The accelerator and connector releases that are included in the following table are compatible with Release 14.2.
Accelerator or Connector
14.2 New Install
Upgrade from 12.
x
to 14.2
Upgrade from 13.
x
or 14.1 to 14.2
PMO Accelerator
14.2.0
14.2.0
14.2.0
Clarity Project and Portfolio Management (PPM)
Solution Pack (CSP)
14.2.0
14.2.0
14.2.0
Earned Value Manager
2.0.2
2.0.2
2.0.2
Accelerator for PRINCE2
2.0.2
2.0.2
2.0.2
Accelerator for the PMBOK
2.0.2
2.0.2
2.0.2
Accelerator for New Product Development
2.0.3
2.0.3
2.0.3
PPM Essentials Accelerator
2.0.2
2.0.2
2.0.2
BRM Accelerator
3.0.2
3.0.2
3.0.2
Connector for CA Unicenter Service Desk 12.7
and CA Software Change Manager™ 12.1.0.3
2.0.1
2.0.1
2.0.1
Connector for CA Unicenter
Asset Portfolio Management 11.3.4
2.0.2
2.0.2
2.0.2
Connector for Microsoft SharePoint 2013
3.0.0
3.0.0
3.0.0
Service Connect
2.0.0
2.0.0
2.0.0
Catalyst Connector
2.5.0
2.5.0
2.5.0
CA Agile Planning
14.1.0
14.1.0
14.1.0
VersionOne Connector
14.1.0
14.1.0
14.1.0
Add-in Installation
Add-ins, accelerators, and connectors are now included with the 
Clarity Project and Portfolio Management (PPM)
 installation. You do not have to download the add-in separately and extract the .jar file.
For more information about the new add-in installation process, see
Installing and Upgrading
.
Upgrade Action
: See 
Add-in Compatibilities
 in this article if you are required to install a new version of your existing add-ins, accelerators, or connectors.
Clarity Project and Portfolio Management (PPM)
 Solution Pack Compatibility
The 
Clarity Project and Portfolio Management (PPM)
 Solution Pack (CSP) is supported only for existing customers. This add-in is not supported for new 
Clarity Project and Portfolio Management (PPM)
 installations.
Before you install the CSP add-in, verify that the compatible versions of 
Clarity Project and Portfolio Management (PPM)
 and the PMO Accelerator are installed. The CSP installation fails if you do not install the compatible version of the PMO Accelerator add-in before installing the CSP.
Review the certified and supported versions chart in the CSP Release Notes to determine if an upgrade of 
Clarity Project and Portfolio Management (PPM)
and the PMO Accelerator is required or optional. For complete information, see the CA PPM Solution Pack Index page on CA Support Online.
Java 7
This release uses Java 7. In addition to the 
Clarity Project and Portfolio Management (PPM)
 server, the following software clients also require Java 7:
  • XML Open Gateway (XOG) client
  • Service Connect
Clarity Project and Portfolio Management (PPM)
 provides a specific Java Runtime Environment (JRE) for the following clients.
  • Open Workbench
  • Connector for Microsoft SharePoint
The JRE is copied to the hard drive in the installation directory on the end-user workstation. The JRE is used specifically for the clients and is independent of the JRE used for the Windows workstation.
For an upgrade from a 13.x version, the server installer prompts for the path of JDK 1.7.
The Java Runtime Environment (JRE) is updated frequently with fixes for security issues, including issues that are unknown at the time 
Clarity Project and Portfolio Management (PPM)
is released. To ensure that you have the latest fixes, we recommend that you download the most recent version 7 JDK from the Oracle website.
Upgrade Action
: Install Java 7 on workstations that have the software clients for which 
Clarity Project and Portfolio Management (PPM)
 does not provide the JRE.
See also End of Service Announcement for 
Clarity Project and Portfolio Management (PPM)
 and Oracle Java 7.
Clarity Project and Portfolio Management (PPM)
 is not affected by the January 2013 Java vulnerability (CVE-2013-0422: Oracle Java 7 Security Manager Bypass Vulnerability). For more information please contact your administrator.
 
Microsoft Project Interface and Schedule Connect
Versions of the 
Clarity Project and Portfolio Management (PPM)
 Microsoft Project Interface that were created before Release 14.2 are compatible with this release. However, a new version of 
Clarity Project and Portfolio Management (PPM)
 Microsoft Project Interface is available with Release 14.2. To take advantage of the latest enhancements and fixes, we recommend using the new version when working with Release 14.2. The MSP Interface installer prompts for the installation of the 14.2-compatible 
Clarity Project and Portfolio Management (PPM)
 Schedule Connect, which is required to use the Microsoft Project Interface with 
Clarity Project and Portfolio Management (PPM)
.
You can download the latest version from 
Clarity Project and Portfolio Management (PPM)
 by opening the Home menu and selecting Account Settings, then clicking Software Downloads. Two options for the Microsoft Project Interface are available during the installation: a legacy option and a new option that contains a new driver.
For information about installing these applications, see
Project Management
.
Recommended Upgrade Action
: Upgrade your version of the Microsoft Project Interface and Schedule Connect.
Automatic Updates to Special Characters in OBS Unit Names during Upgrade
While you are upgrading, the preinstallation log can show a warning message about the special characters that are not allowed in the OBS Unit Names. This warning message is displayed in the precheck-results.xml file. The following characters are the special characters for which the warning is shown:
  • Slash (/)
  • Colon (:)
  • Double quote (")
  • Less than (<)
  • Greater than (>)
If the administrator does not replace the special characters with the valid character (hyphen "-") before upgrading, the upgrade automatically replaces the characters with the hyphen.
If you do not want hyphens placed in names with special characters, update the names during the preinstallation check before you begin the upgrade process. 
If you have an existing installation, you have two options for how to proceed before upgrading to 
Clarity Project and Portfolio Management (PPM)
 Release 14.2.
CA Productivity Accelerator (CA PA) Version 11.1
If you have CA PA Version 11.1, install a patch to make the player package compatible with 
Clarity Project and Portfolio Management (PPM)
 Release 14.2. A different file is now used to launch the player package. After you install the patch, republish and upload the content. For more information, see the CA PA Support website.
CA Productivity Accelerator (CA PA) Version 12.1
You can upgrade to the latest version CA PA 12.1. Open a Support ticket, obtain a new license key, and download the software from the Download Center. The content from CA PA 11.1 can be exported and is fully compatible with CA PA 12.1. An additional patch is required for the player package to function properly with 
Clarity Project and Portfolio Management (PPM)
. For more information, see the CA PA Support website.
J2EE Installations
For an upgrade on an installation that uses 
generic 
as the vendor type, update the DataDirect JDBC driver .jar files in your third-party application server environment. The version for these files has changed in this release.
Upgrade Action
: Update your DataDirect JDBC driver .jar files. For more information, see 
Installing and Upgrading
.
Internet Explorer 11
If you are using Internet Explorer 11 with 
Clarity Project and Portfolio Management (PPM)
, the browser is automatically set to run in the Internet Explorer 10 compatibility mode for the 
Clarity Project and Portfolio Management (PPM)
 session. The setting is for the 
Clarity Project and Portfolio Management (PPM)
 session only and does not affect any other Internet Explorer 11 browser activity.
Support Ended for Microsoft Excel 2007 and Microsoft PowerPoint 2007
Clarity Project and Portfolio Management (PPM)
 support for Microsoft Excel 2007 and Microsoft PowerPoint 2007 stopped at Release 14.1.
Upgrade Action
: To use these Microsoft products with this release, you must upgrade them to a newer supported version.
Discontinued Internet Explorer Browser Version Support
Microsoft recently made a significant change in its Internet Explorer support policy. Effective January 12, 2016, only the most current version of Internet Explorer available for a supported operating system will receive technical support and security updates. Support for Internet Explorer versions 8, 9, and 10 is being retired. This change results in potential impacts to customers who are running 
Clarity Project and Portfolio Management (PPM)
 Releases 13.3 or 14.2 and to customers who plan to upgrade to 
Clarity Project and Portfolio Management (PPM)
 Release 14.3.
See the Discontinued Browser Support announcement.
Known Issues for Release 14.2
The following section lists the Known Issues at the time this release was delivered.
Fiscal Time Slices Are Reset after Saving the System Options Page
Fiscal Time slices are reset if you save the System Options page (Administration, General Settings, System Options). This resetting occurs even if you do not change any of the fields on the page.
Advanced Reporting Repository Items Are not Localized
The Advanced Reporting repository folder structure and its items (such as domains, reports, input controls, and templates) are not localized. The Public, Shared, Temp, Themes, and Users folders are also not localized. The out-of-the-box items that are available in these folders are not localized. The item names and their descriptions display in English for all languages. Input Controls (that are used as filters in reports) display the $R expression that is used by Jaspersoft for localization. This expression is only converted when running the reports. However, the report output is fully localized.
Advanced Reporting Custom Subobjects Are not Localized
The names of custom subobjects that are dynamically updated in Advanced Reporting domains are not localized. As a result, the names are not localized in ad hoc views either. The names appear in the language selected when the subobjects were created. However, the custom master object names are localized.
Advanced Reporting Requires Logout to Change Language
If you change languages while you are in your current product session (you do not log out), the data in Advanced Reporting is not completely localized. To resolve this issue, log out of 
Clarity Project and Portfolio Management (PPM)
 after changing the language setting and log in again. The data then appears in the new language.
Advanced Reporting Notifications Do Not Work with Incorrect Email Format
If you set up multiple email addresses for Advanced Reporting Notifications and one of the email addresses uses an incorrect format, none of the email addresses receives the notification. Also, if you have addresses in both the "To" and the "CC" fields and one of the addresses has an incorrect format, no email is sent to any address in the two fields. This issue applies to the "Send report when scheduler runs" and the "Send job status notifications" sections of the Advanced Reporting report schedule Notifications tab.
Advanced Reporting Charts and Widgets Do not Appear in Browser PDF
If you export a report to PDF and then view the report in your browser, the report output data does not display charts, maps, and other widgets. However, if you download the exported PDF and open it in Adobe Reader, the charts and other widgets are shown.
To see the charts and widgets in the browser PDF, enable the Adobe Reader plug-in for your browser. Also, make sure you disable any other PDF reader plug-in.
Advanced Reporting Schedule Date Does not Work for Some Languages
When you schedule an Advanced Reporting report using Create Schedule and you select a date using the date selection calendar for On Specific Date, you can receive an error when you save the schedule. However, you are able to select a specific date for your schedule for the following languages: English, Japanese, Italian, Polish, Brazilian Portuguese, Swedish, Traditional Chinese, and Simplified Chinese. For all other supported languages, you cannot set a specific schedule date.
Advanced Reporting Scheduled PDF Appears in Collapsed Format
Advanced Reporting allows you to schedule a report PDF, save the output to the repository, and send notifications about the report. If you select "Include reports as repository links in email body" when you set up the Notifications, the PDF appears collapsed (in small size) on the browser after the user clicks the email link. This issue occurs with Internet Explorer and Mozilla Firefox.
Advanced Reporting Ad Hoc View Filters Do not Auto-Populate
When you are creating or editing an Advanced Reporting ad hoc view, you can use the filter fields to limit the selection options. However, the filter lists are not auto-populated with selection results based on your search criteria. No results appear. This issue occurs in Oracle database environments.
Advanced Reporting Report Output with Email Notifications
The following output options, which are available for selection when you create or edit a report schedule, have issues regarding their format or content:
  • PDF – Contains one blank page.
  • ODT – Contains one page only.
  • PPTX – Contains one slide only, with extra content on that slide.
  • RTF – Requires a long time for a large report.
Advanced Reporting Report Options Do not Display Data
When you run a report using Advanced Reporting, you can select report options, which display as drop-down lists on the left of the report page. These options let you filter the data in your report. At times, these options do not display all of the selections available in the database. This issue occurs when the data displayed by the report options has been updated after you logged in to your current session. To resolve this issue, log out of 
Clarity Project and Portfolio Management (PPM)
 and log back in again. The data displays correctly then.
Jaspersoft Sender Email Address
The sender email address is the address that appears when JasperSoft sends an email notification for a scheduled report. JasperSoft lets you set the sender email address at the JasperSoft Reporting Server (JRS) level, but not at the tenant (organization) level.
The following address is the default sender email address value for the JasperSoft reporting server for On Premise implementations:
mailto:[email protected]_domain.comFor information about changing this default value during installation, see 
Installing
.
To change the default value after installation, perform the following steps:
  1. Locate and open the js.quartz.properties file in a text editor.
  2. Edit the report.scheduler.mail.sender.from property to include your sender email address and save the file.
  3. Restart the JRS.
Empty Organization Field Results in Blank Key Store
After Jaspersoft installation, the administrator configures Jaspersoft using CA Clarity System Administration (CSA). During this configuration, generate a key store using the following command:
admin jasper keystore
However, if the Organization Name field (in the CSA, Reporting tab, Jaspersoft section) is blank, the resulting key store is also blank.
You can resolve this issue by updating the Organization Name field in CSA and running the command again.
Reports for Earned Value Management (EVMS) and PMBOK Add-Ins
The reports for the EVMS and the PMBOK add-in are not available as Jaspersoft reports.
Microsoft Project Interface: Baseline Costs Ignored
When you baseline your project in Microsoft Project and then import it back to 
Clarity Project and Portfolio Management (PPM)
 again, the baseline costs are ignored when saved to 
Clarity Project and Portfolio Management (PPM)
. The baseline costs include project, assignment task, and team. This situation occurs with the Microsoft Project Interface (newer version). To resolve this issue and as a best practice, update your baseline in 
Clarity Project and Portfolio Management (PPM)
 only.
Duplicate Cost Plan Code Error
This issue applies 
only 
to upgrades from a 12.x release to the current release.
The duplication of a plan code within a financial plan can cause the upgrade process to fail. The plan code for each plan type within the investment must be unique. For example, you can have a cost plan with the code 
MasterPlan2011 
and a budget plan with the same code. However, you cannot have two cost plans with code MasterPlan2011 for the same investment. The unique database constraint for this rule was added in Version 13.0.
Due to concurrency issues, there can be a data issue in previous versions. When a duplicate plan type code exists within a single financial plan, the upgrade process fails with an appropriate error message. You are required to correct the data issue before resuming the upgrade process. An upgrade check script runs and alerts you that this problem exists.
To identify possible data issues before you start the upgrade, run the following query:
SELECT p1.id, p1.code, p1.name FROM fin_plans p1, fin_plans p2 WHERE p1.id != p2.id AND p1.object_id = p2.object_id AND p1.code = p2.code AND p1.plan_type_code = p2.plan_type_code
If this query returns any rows, it indicates issues with fin_plans table data.
We recommend that you rename the codes for duplicate records. Do not change the other data. A sample query is available to fix the data issues. Because this known issue deals with financial information, review the query carefully before deciding to use it. The following query appends 
_<internalId>
 to the duplicate plan code.
<!-- Oracle --> UPDATE fin_plans SET code = code || '_' || to_Char(id) WHERE id IN ( SELECT p1.id FROM fin_plans p1, fin_plans p2 WHERE p1.id != p2.id AND p1.object_id = p2.object_id AND p1.code = p2.code AND p1.plan_type_code = p2.plan_type_code ) <!-- Mssql --> UPDATE fin_plans SET code = code + '_' + CAST(id AS VARCHAR) WHERE id IN ( SELECT p1.id FROM fin_plans p1, fin_plans p2 WHERE p1.id != p2.id AND p1.object_id = p2.object_id AND p1.code = p2.code AND p1.plan_type_code = p2.plan_type_code )
Missing Data for Resource Financials
This issue applies 
only 
to upgrades from a 12.x release to the current release.
If the Resource Class or Transaction Class fields are null for Resource financials, the upgrade process fails. The data must be corrected before you resume the upgrade process. An upgrade check script runs and alerts you that this problem exists.
The 
not null 
database constraint for the RESOURCE_CLASS and TRANSCLASS columns in the PAC_MNT_RESOURCES table was added in Version 13.0. If you are upgrading from a previous version of 
Clarity Project and Portfolio Management (PPM)
, it is possible that the information is missing.
We recommend running the following query to identify records with this data issue before starting the upgrade.
Select * from pac_mnt_resources where RESOURCE_CLASS is null OR transclass is null
If this query returns any rows, it indicates that there are issues with the PAC_MNT_RESOURCES table data. We recommend reviewing all returned records and updating the records with valid transaction class and resource class values.
Upgrade Fails if the Default Language for the Admin User Is Not English
A portion of the upgrade relies on the English locale when it is importing content using the XML Open Gateway (XOG). This import fails if the default language of the admin user is not set to English. The workaround is to set the admin user language to English.
Resume Capability During the Upgrade
Clarity Project and Portfolio Management (PPM)
 does not support the ability to resume during an upgrade. We recommend that you run the Checkinstall utility and review the reports that it generates before starting. To reduce the possibility of a failure, correct any errors that the Checkinstall reports indicate.
If your upgrade fails, review the logs and the Checkinstall post-installation reports to determine the reason for the failure. Then, restore the working preupgrade version and database, correct the failure, and restart the upgrade.
Export Icons in Resource Planning Tabs Not Functioning
Export to Excel and Export to PowerPoint icons on a Resource Planning tab give an error when you click them.
This issue applies only to WebSphere application servers.
As a workaround, use the Export to Excel and Export to PowerPoint links available from the Options icon in the individual portlets on the tabs.
Missing General Action Menu After Upgrade
In some cases, the General Action menu does not appear after an upgrade. This issue occurs on the Project object when the following conditions exist:
  • In the edit properties view (Layout:Edit), a display condition is defined on the General subpage.
  • The General object actions menu for the view is not customized.
You can correct the issue before the upgrade, or you can upgrade and then correct the issue in the new upgraded product.
To correct the issue before the upgrade:
Remove the display conditions on the General subpage before the upgrade and redefine the display conditions after the upgrade.
If the preupgrade server is on Version 13.0 or a later service pack, you can handle the issue in a different manner. Before you start the upgrade, edit the General Action menu. Move any action that is listed there from the Available Actions list to the Selected Actions list and save. After the upgrade is complete, you can remove any unwanted actions.
To correct this issue after the upgrade:
  1. Create an action menu with the following details:
    • Menu Name: General
    • Menu Code: general
    • Description: General
  2. Move the following out-of-the-box actions from the Available Actions to the Selected Actions list:
    • Add to My Projects
    • Copy Project from Template
    • Remove from My Projects
    • Go to Links Page
    • Go to Notes Page
For more information about creating an action menu, see
Studio Development
.
Automatic Update to Curly Brackets in OBS Names During Upgrade
If an OBS name contains a left curly bracket ({) or a right curly bracket (}), left or right parentheses replace the characters during the upgrade.
Example: The OBS name External{Department} becomes External(Department) after the upgrade.
Report Instance Export from the Report Library
You cannot export report instances from the report library when the BusinessObjects server is configured with 
Clarity Project and Portfolio Management (PPM)
 installed on a Windows 2012 server. BusinessObjects Enterprise 3.1 SP5 is not supported for Windows 2012.
 
Installing the BusinessObjects server on a supported configuration does not avoid this issue. The .jar files that are used for the 
Clarity Project and Portfolio Management (PPM)
integration are not compatible with Windows 2012.
Orphan Records in Table CMN_SEC_ASSGND_OBJ_PERM for MSSQL Users
A recent change prevents the creation of orphan records in the table CMN_SEC_ASSGND_OBJ_PERM. However, for MSSQL users, pre-existing orphan records can sometimes remain. You can search for orphan records and can remove them from the table after the upgrade is complete.
To verify that orphan records exist in the table, run the following query:
select COUNT(*) from (select object_instance_id from cmn_sec_assgnd_obj_perm p where p.object_ID = 50680 and object_instance_id not in (select ID from BPM_RUN_PROCESSES)) q
The number value that the query returns indicates the number of orphan records.
To clean up orphan records, invoke the following upgrade script from <clarity_install_dir>/bin using dbpatch:
POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml
Use the following command:
dbpatch -install -file <CLARITY_INSTALL_DIR>\upgrade\13.3.0\component\postupgrade\POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml -apply
The length of time the query runs is dependent on the number of orphan records to be deleted.
Clarity Project and Portfolio Management (PPM)
 Upgrade and Oracle Enterprise Table Compression
If you are using the Oracle Enterprise Edition compression feature, disable the compression feature before starting the 
Clarity Project and Portfolio Management (PPM)
 upgrade. If the compression feature is enabled, the upgrade fails with the following Oracle database error:
[CA Clarity][Oracle JDBC Driver][Oracle]ORA-39726: unsupported add/drop column operation on compressed tables
The following procedure explains how to prepare for the upgrade by disabling compression. Once the procedure is complete, you can proceed with the upgrade. When the upgrade has successfully completed, you can compress the tables again.
To prepare for the upgrade, complete the following steps:
  1. Identify compressed tables by executing the following query:
    SELECT TABLE_NAME, COMPRESSION FROM USER_TABLES WHERE COMPRESSION='ENABLED';
  2. Disable compression. Run the output of this query. Keep this list handy, so that these tables can be compressed again after the upgrade.
    SELECT 'ALTER TABLE ' || TABLE_NAME || ' MOVE NOCOMPRESS;' FROM USER_TABLES WHERE COMPRESSION='ENABLED';
  3. Rebuild the unusable indexes. Run the output of this query:
    SELECT 'ALTER INDEX ' || INDEX_NAME || ' REBUILD;' FROM USER_INDEXES WHERE STATUS='UNUSABLE';
Update Operation For Some Project Object Attributes Does Not Appear in the Audit Trail
In some instances, when auditing is enabled for specific attributes on the Project object, only the insert operation is reported in the audit trail. The update operation does not show for the attributes. The affected attributes include:
  • Budgeted Capital Cost
  • Planned Capital Cost
  • Budgeted Operating Cost
  • Planned Operating Cost
WebSphere Deployment Does Not Show Database Information in CA Clarity System Administration
During a generic J2EE installation, the nsa.ear file installs CA Clarity System Administration. Once you start CA Clarity System Administration, you can see the database information after you specify your database credentials. However, if you are installing on WebSphere, the database information is not available. Neither the Install History page nor the Installation Overview page in CA Clarity System Administration shows the database as installed, even though it is.
This behavior does not affect your ability to complete the installation and use the application.
Upgrade Action
: To get details of the database, run the query CMN_INSTALL_HISTORY.
Generic J2EE Upgrade Produces an Error If the J2EE.home Property Is Not Set
An error is received during an upgrade for a generic J2EE application server (IBM WebSphere). Because the vendor is generic, the prompt for the J2EE home directory does not appear and the j2ee.home property is not set. Without a j2ee.home setting, an error occurs in the installation process.
Upgrade Action
:
Set the following values in the <installer>/install.properties file:
  • j2ee.home=<any value>
  • j2ee.vendor=generic
An Upgrade With a Non-RAC Database Results in a Disconnect Between the Application Server and the Database
If you are upgrading to Release 13.2, 13.3, or 14.1 with a non-RAC database, the network between the application server and the database disconnects during the upgrade. You see the following error:
FATAL 2013-07-17 13:14:46,376 [main] union.persistence Failed to initialize Context properties 7/17/13 1:14 PM (admin) java.sql.SQLNonTransientConnectionException: [CA Clarity][Oracle JDBC Driver]Connection reset 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcg.b(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcg.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.b(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oraclebase.ddcf.a(Unknown Source) 7/17/13 1:14 PM (admin) at com.ca.clarity.jdbc.oracle.net8.dd g.b(Unknown Source)
Upgrade Action
:
Before you start the upgrade, complete the following steps:
  1. Open CA Clarity System Administration, and click Servers in the left pane.
  2. Click the name of the application server.
  3. Click the Database subtab.
  4. In the Internal Connection: Niku section, select the Specify URL check box.
    The JDBC text box appears.
  5. Add the following tags to the JDBC URL:
    ConnectionRetryCount=400;ConnectionRetryDelay=3
  6. Click Save.
Google Chrome Version 30.0.1599.66 m Issues
The following 
Clarity Project and Portfolio Management (PPM)
 issues occur for users who are using this particular version of Chrome (Version 30.0.1599.66 m):
  • The Recent Pages (History) drop-down that lets you navigate back to previously viewed pages does not work.
  • Export to Excel and Export to PowerPoint do not work at the portlet level.
  • Export to Excel does not work on a list page.
These issues do not appear in other browsers and have been found only in this version of Chrome.
Gantt Printing Issue with Chrome
If you use Chrome, the following issues can occur when you print a Gantt chart:
  • Some rows have extra space after the row.
  • Some lines break across pages, presenting part of the line on two pages.
  • The Gantt schedule lines do not appear correctly.
This issue does not occur in Internet Explorer or Firefox.
Rate Matrix Extraction Job's Scheduled Instances and Job Logs Deleted
During an upgrade from a 12.x release to a 13.0 or higher release, the Rate Matrix Extraction job’s scheduled instances and job logs are deleted.
Upgrade action
: Reschedule the Rate Matrix Extraction job.
Microsoft Project 2013 Service Pack 1 Issue with the Legacy MSP Interface
The 
Clarity Project and Portfolio Management (PPM)
 Legacy MSP Interface option does not support the Microsoft Project Service Pack 1.
Service Pack 1 for Microsoft Project 2013 has a known issue that affects how it works with 
Clarity Project and Portfolio Management (PPM)
. The following behavior results when the service pack is installed:
  • Baselined projects cannot be opened with Microsoft Project 2013. The Visual Basics run-time error '91' is received.
  • All the actuals are zeroed out when you launch a project from 
    Clarity Project and Portfolio Management (PPM)
     to Microsoft Project 2013.
For more information, see the following Knowledge Base articles on CA Support Online: TEC610737, TEC615024.
Microsoft Project 2013 Service Pack 1 is supported for integration with the new 
Clarity Project and Portfolio Management (PPM)
Release 14.2 MSP Interface option.
Upgrade Action
: Do not apply Service Pack 1 to Microsoft Project 2013 if you are using the 
Clarity Project and Portfolio Management (PPM)
 Legacy MSP Interface.
Add-In Enhancements for Release 14.2
Here are the add-in enhancements for Release 14.2.
Change to Plugin ID
The plugin ID for VersionOne has changed from remote_v1 to pl_remote_v1. The change means the command to deploy the plugin changes.
admin plugin pl_remote_v1
Upgrading to the Release 14.2 VersionOne plugin automatically updates the install history to reflect the new ID name.
Upgrade Action:
 None
Administration Changes for Release 14.2
Here are the Administration changes for Release 14.2.
Change in Link Actions for the Project Object
The following obsolete actions were removed as options from the Action drop-down list that is available when a new link is created for the Project object:
  • Project Budget - Latest Revision
  • Project Budget - Specific Revision
  • Project Forecast - Latest Revision
  • Project Forecast - Specific Revision
Upgrade Action
: None
Resource Lookups for Action Items
Clarity Project and Portfolio Management (PPM)
 provides the following stock lookups for use with the Action Item Assignees functionality:
  • Resource Browse (SCH_BROWSE_RESOURCE)
  • All Resources Browse (LOOKUP_RESOURCES_ALL)
The lookup definitions contain the following general properties:
  • Object = Resource and the Parent Window
  • Hidden Key = ID value from SRM_RESOURCES table
The 
Clarity Project and Portfolio Management (PPM)
 process Action Item Assignees functionality expects the internal record ID for a Resource record, which is stored on the SRM_RESOURCES table. The functionality does not expect a user record ID. You can create a custom attribute that uses a stock 
Resource Browse
 lookup type, or you can create your own dynamic query lookup definition.
The most commonly used system-supplied lookup that meets this criteria is the Lookup ID = "SCH_BROWSE_RESOURCE". Using this lookup, you can create your own dynamic lookup that returns the SRM_RESOURCE.ID value as the hidden key value in the lookup.
Do not confuse the Resource Browse lookups with similarly named resource or user lookups.
Upgrade Action
: None
Advanced Reporting
The Advanced Reporting feature lets you build views and reports against project and other investment data to drive organizational intelligence. Advance Reporting has the following benefits for your users:
  • Easy to use, interactive reports that run within 
    Clarity Project and Portfolio Management (PPM)
     are available.
  • Filter options and report results appear in the same window, with support for cascading filters.
  • More scheduling options are available.
  • You can email reports, export reports, and save the report in the Jaspersoft repository.
    • Specify email addresses, using up to a maximum of 200 characters. Separate email addresses with commas. You can also enter email aliases, which we recommend if you are sending the report to a large number of users.
    • Export reports to a maximum of two formats (for example, Powerpoint and Word or PDF and Excel).
  • You can create report and style templates.
  • You can develop reports in 
    Clarity Project and Portfolio Management (PPM)
     against the Data Warehouse or the 
    Clarity Project and Portfolio Management (PPM)
     transactional database.
Data Warehouse
The Data Warehouse provides a schema that is optimized specifically for analytics. A set of 
Clarity Project and Portfolio Management (PPM)
 jobs extract, transform, and load the data from 
Clarity Project and Portfolio Management (PPM)
 to the Data Warehouse. The advantages of the Data Warehouse include:
  • Simplification of the data model that makes end user reporting easier. This feature reduces the demand for custom report development.
  • Reducing the stress and traffic on the 
    Clarity Project and Portfolio Management (PPM)
     transactional database. This reduction is possible because the Data Warehouse resides on a separate database server.
  • Any reporting solution can access the information in the Data Warehouse.
The following diagram shows the flow of data from the 
Clarity Project and Portfolio Management (PPM)
 database to the Data Warehouse.
image2018-3-6 12:3:56.png
 
 
The Data Warehouse addresses several data and reporting challenges, described in the following table, that users experienced when working directly with the 
Clarity Project and Portfolio Management (PPM)
 transactional database.
Challenge
Response
Reports run against transactional data
The Data Warehouse has its own database which takes stress off the transactional 
Clarity Project and Portfolio Management (PPM)
database.
Complex relational database queries
The data warehouse carries keys and descriptive values in the dimension tables so that fewer joins are required. Facts are combined into summary and period tables.
Finding data with 1000+ tables
Data Warehouse tables are user friendly for reporting (with the exception of configuration and meta tables).
Table name inconsistencies
Similar tables are grouped together by the table prefix, and the names are descriptive.
Difficult time slice setup
Specific time slices are set up to populate the data warehouse. Defaults are set but can be adjusted.
Inconsistent column naming
Columns are named consistently across tables.
Resource ID versus
User ID confusion
Resource columns (manager_key, resource_key, and so on) are always the resource_key. In
Clarity Project and Portfolio Management (PPM)
, manager points to the user ID and the resource points to the resource ID or code, which is inconsistent.
Date and time storage correctness
The finish/end dates seen in the product are dates in the data warehouse database. In
Clarity Project and Portfolio Management (PPM)
, a user must use a function to determine the date. For example: 12/31/2012 on the page could be stored as 1/1/2013 00:00:00 in the 
Clarity Project and Portfolio Management (PPM)
table.
Use of Code versus ID
The 
Clarity Project and Portfolio Management (PPM)
financial tables use codes instead of IDs. The Data Warehouse always uses the numeric key of the dynamic lookups.
Database tuning
Because the Data Warehouse database is separate from the 
Clarity Project and Portfolio Management (PPM)
database, it can be tuned differently for optimal performance.
Studio attributes not available in a Universe without customization
The data warehouse is extendable without customization. A flag was added to Studio objects and attributes that tells the load job to add new objects and attributes automatically.
The following steps provide a basic overview of how to install the Data Warehouse.
For full details about the preparation and installation for this database, see
Installing and Upgrading
.
  1. Install the database software.
    See the documentation from Oracle or Microsoft for the appropriate instructions.
  2. Configure the database and import the Data Warehouse database backup image.
  3. Set up a database link for the Data Warehouse.
  4. Set the language and fiscal periods for the Data Warehouse.
  5. Configure the Data Warehouse server credentials.
  6. Populate the Data Warehouse with Data.
Upgrade Action
: None
Jaspersoft Reports
Advanced Reporting uses the Jaspersoft Studio application to manage views, reports, and dashboards. This third-party reporting option is integrated with 
Clarity Project and Portfolio Management (PPM)
 to provide easy reporting for users. Each report can be customized by selecting the domains and fields needed.
The Jaspersoft domains are a business representation of the Data Warehouse that lets you interact with data without having to understand database complexities. The Jaspersoft domains parallel and serve the same general purpose as the Business Objects Universes. The Jaspersoft domains can be used to create reports in 
Clarity Project and Portfolio Management (PPM)
.
 
The following steps provide a basic overview of how to install and configure Jaspersoft.
For full details about the preparation and installation of Jaspersoft, see
Installing and Upgrading
.
  1. Download and install Jaspersoft.
    The software is available from the 
    Clarity Project and Portfolio Management (PPM)
     Download Center on CA Support Online.
  2. Configure the Jaspersoft server properties in Clarity System Administration.
  3. Install the Advanced Reporting content by installing or upgrading the PMO Accelerator add-in.
  4. Configure your users for Advanced Reporting by assigning the appropriate access rights and running a job that syncs users between 
    Clarity Project and Portfolio Management (PPM)
     and Jaspersoft.
Upgrade Action
: None
User Interface Adjustments for Advanced Reporting
New or upgrading customers who are moving to Advanced Reporting (Jaspersoft) must adjust the 
Clarity Project and Portfolio Management (PPM)
 user interface and user access rights. Because the Business Objects reporting solution is still available for existing customers, the user interface reflects that option.
Upgrade Actions
: Adjust the user interface and access rights to reflect that Jaspersoft and not Business Objects is the reporting option.
Actions for new and upgrading customers:
  1. Rename the 
    Reports and Jobs
     link that appears in the Home menu to 
    Jobs.
     This menu link appears for basic users.
    1. Open the Administration menu and from Studio, click Menu Manager.
    2. In the menu list, click Application Menu.
    3. Click Reports and Jobs in the list that appears.
    4. Change the link name to Jobs.
    5. Change the link description to Jobs.
    6. Click Save and Return.
    7. To see the updated menu option, refresh the menu.
  2. Rename the 
    Reports and Jobs
     link that appears in the Administration menu to 
    Jobs. 
    This menu link appears for administrators.
    1. Open the Administration menu and from Studio, click Menu Manager.
    2. In the menu list, click Administration Tool Menu.
    3. Click Reports and Jobs in the list that appears.
    4. Change the link name to Jobs.
    5. Change the link description to Jobs.
    6. Click Save and Return.
    7. To see the updated menu option, refresh the menu.
  3. Ensure that no users have the 
    Reports - Access
     right assigned.
    This access right makes the Reports tab under the Reports and Jobs link accessible to users. Because the reports listed there are Business Objects reports, the tab should not be visible to Jaspersoft users.
    If you are a new customer, do not assign this access right to users. 
    If you are an upgrading customer, remove the access right from assigned resources or groups. An out-of-the-box Jaspersoft report that is named 
    User Access Rights
     can provide the resources and groups with the right granted.
  4. Remove the My Reports portlet from the Overview page.
    1. Open the Administration menu and from Studio, click Portlet Pages.
    2. In the Pages list, click Overview, and then click Tabs.
    3. In the list of tabs, click General, and then click Content.
    4. Select the check box next to My Reports and click Remove.
    5. Save your changes.
General 
Clarity Project and Portfolio Management (PPM)
 Differences between Jaspersoft and Business Objects Implementations
The following cases describe the way that 
Clarity Project and Portfolio Management (PPM)
 report-related fields set for Business Objects can affect a Jaspersoft user:
  • If 
    Report 
    is selected for the Executable Type field in the Job Definitions filter, no result is given. Previously, this selection resulted in the list of Business Objects out-of-the-box reports.
  • All Jaspersoft reports are created and executed directly from the Jaspersoft user interface available in 
    Clarity Project and Portfolio Management (PPM)
    . Do not create a job with an Executable Type of 
    Report 
    if you are a Jaspersoft user.
  • Report-based object actions do not allow you to select a report from a drop-down list. No out-of-the-box reports appear in the Report drop-down list.
  • Query (NSQL) link creation does not provide out-of-the-box reports in the list of actions that can be selected.
  • Customers who are using Advanced Reporting cannot currently add an Action Link in Favorites for a report.
  • If you email repository links in the email body, the user must have repository access within Advanced Reporting, which requires at least a restricted user license. If the user needs to view the report output and does not have a minimum of a restricted user license, schedule a report to email the report output to the user. Save the report output to a network file directory or on an FTP site.
Time Slices for the Data Warehouse
The following points apply to time slice requests that support the Data Warehouse:
  • A total of 40 time slice requests (25 new and 15 existing) support the Data Warehouse.
    To view the list of Data Warehouse time slice requests, navigate to the Time Slices list page and sort on the Data Warehouse column.
  • 25 new time slice requests were created.
  • 15 existing time slices can be affected during the Release 14.2 upgrade.
  • Because of new time slice requests and changes to existing requests, the first run of the 
    Time Slicing
     job can take substantially longer than usual.
  • Data Warehouse time slice requests are system requests and cannot be deleted.
  • The Data Warehouse time slice requests default to the following time periods, based on the database server system date:
    • For daily: 1 year back, 1 year forward. The From Date of the slice request is one year prior to the system date.
    • For weekly: 1 year back, 1 year forward. The From Date is one year prior to the system date and is the same day as the 
      First Day of Work Week
      . To locate the 
      First Day of Work Week 
      field, open the Administration menu and from Project Management, click Settings.
    • For monthly: 3 years back, 3 years forward. The From Date is three years prior to the system date and is always the first day of the month.
    • For fiscal: 3 years back, 3 years forward. The From Date is three years prior to the system date and corresponds to the start date of a Monthly (or 13 Period) fiscal period type that is based on the 
      Entity for Fiscal Periods
       value in Data Warehouse Options. To locate the 
      Entity for Fiscal Periods 
      field, open the Administration menu and from General Settings, click System Options.
      The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the
      Time Slicing
      job is run.
      If the From Date and Number of Periods for the 15 existing time slice requests are set to cover a time range greater than the default time ranges, the upgrade does not update the time slices. The time slices are left as they were before the upgrade.
  • The Data Warehouse time slice requests can be edited on the Time Slices page available from the Administration menu.
  • By default, the Data Warehouse time slice requests are set consistently for each slice period (Daily, Weekly, Monthly, Fiscal).
    If you edit these slice requests, set the From Date and Number of Periods to be the same for each slice period type. If these values are not set correctly, the data in the Data Warehouse will be inconsistent.
    Specifically, follow these rules when setting the From Date and Number of Periods for the Data Warehouse time slice requests:
    • All daily time slice requests, must have the same From Date and Number of Periods.
      This release contains only one daily time slice request.
    • All weekly time slice requests must have the same From Date and Number of Periods. The From Date must also be the same day of the week as the 
      First Day of the Work Week
      . For example: If the 
      First Day of the Work Week
       is a Monday, all weekly time slice requests must be set with a From Date that is the same, and the date must be a Monday.
    • All monthly time slice requests must have the same From Date and Number of Periods. The From Date must be the first of a month; it cannot be a day within the month.
    • All fiscal time slice requests must have the same From Date and Number of Periods. The From Date must correspond to the start date of a Monthly (or 13 Period) fiscal period type that is based on the 
      Entity for Fiscal Periods
       value in Data Warehouse Options. To locate the 
      Entity for Fiscal Periods 
      field, open the Administration menu and from General Settings, click System Options. The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the 
      Time Slicing
       job is run.
  • If you change the slice request default time periods, we recommend setting the time slice range to cover the start/finish dates of the investments on which you regularly report. For example, for two-year investments on which you regularly report, set the time slices to cover two years back and two years forward so that all relevant data is included in the Data Warehouse.
  • Fiscal time slice requests and a new table (PRJ_FISCAL_BLB_SLICES) were added to the 
    Clarity Project and Portfolio Management (PPM)
     schema to support fiscal period data in the Data Warehouse. These slice requests are not populated and do not have supporting data in the PRJ_FISCAL_BLB_SLICES table until a series of steps are completed.
    Although we ship fiscal time slice requests, this release contains no option to create new time slice requests with a slice period of fiscal. The only available fiscal time slice request functionality resides in the new slice requests shipped for the Data Warehouse.
    To use the new fiscal slices and populate the PRJ_FISCAL_BLB_SLICES table after the upgrade or installation, follow these steps:
    1. Log in as an Administrator user.
    2. Open the Administration menu and from General Settings, click System Options.
    3. Select the 
      Entity for Fiscal Periods 
      value and verify the Languages setting, and save your changes.
      Specifies the entity that is used to determine fiscal periods. The fiscal periods that are associated with the selected entity are used for all Data Warehouse fiscal period data calculations. Setting the entity for the first time creates new Data Warehouse time slice requests. Therefore, the initial run of the Time Slicing job takes significantly longer than normal. 
      Initially setting an entity or updating it also updates the fiscal entity and fiscal period type for the Data Warehouse fiscal time slice requests. Do not set or change the entity when a time slice rollover is in progress. If you do, an error message appears. Wait until the rollover completes and then set the entity. To determine which slice requests are in the rollover, check the expiration date on the time slices. A slice request with an expiration date that is blank, earlier than the current date, or the same as the current date is in the rollover. Allow the slice request to complete processing before setting the entity.
      The entity must have Monthly (or 13 Period) fiscal time periods set up to cover the range of the time slice requests. Otherwise, the time slice requests are ignored when the
      Time Slicing
      job is run.
    4. Run the 
      Time Slicing
       job.
    5. To populate the Data Warehouse schema, run the Load Data Warehouse job.
    6. To populate the security tables in the Data Warehouse schema, run the Load Data Warehouse Access Rights job.
    For complete information about setting up and populating the Data Warehouse, see
    Installing and Upgrading
    .
  • The following table contains the Data Warehouse time slice requests. Note that the new time slices have 
    dwh 
    in the name, and the fiscal time slices have 
    fiscal 
    in the name.
    Time Slice ID
    Time Slice Name
    55555
    DAILYRESOURCETIMECURVE
    55556
    WEEKLYRESOURCEACTCURVE
    55557
    WEEKLYRESOURCEESTCURVE
    300
    WEEKLYRESOURCEBASECURVE
    307
    WEEKLYBASEASSIGNCOSTS
    55559
    WEEKLYRESOURCEAVAILCURVE
    55558
    WEEKLYRESOURCEALLOCCURVE
    306
    WEEKLYRESOURCEHARDALLOC
    4
    MONTHLYRESOURCEACTCURVE
    5
    MONTHLYRESOURCEESTCURVE
    312
    MONTHLYRESOURCEBASECURVE
    305
    MONTHLYBASEASSIGNCOSTS
    7
    MONTHLYRESOURCEAVAILCURVE
    6
    MONTHLYRESOURCEALLOCCURVE
    55566
    MONTHLYRESOURCEHARDALLOC
    55577
    assignment::practcurve::dwh_fiscal
    55578
    assignment::prestcurve::dwh_fiscal
    5004026
    assignment::actcost_curve::dwh_week
    5004027
    assignment::actcost_curve::dwh_month
    55584
    assignment::actcost_curve::dwh_fiscal
    55576
    assignment::etccost_curve::dwh_week
    55567
    assignment::etccost_curve::dwh_month
    55589
    assignment::etccost_curve::dwh_fiscal
    55588
    baseline::current_assignment_usage::dwh_fiscal
    55587
    baseline::current_assignment_cost::dwh_fiscal
    5004016
    baseline::current_team_usage::dwh_week
    5004017
    baseline::current_team_usage::dwh_month
    55582
    baseline::current_team_usage::dwh_fiscal
    5004020
    baseline::current_team_cost::dwh_week
    5004021
    baseline::current_team_cost::dwh_month
    55581
    baseline::current_team_cost::dwh_fiscal
    55579
    resource::pravailcurve::dwh_fiscal
    55580
    team::pralloccurve::dwh_fiscal
    55583
    team::hard_curve::dwh_fiscal
    5004022
    team::alloccost_curve::dwh_week
    5004023
    team::alloccost_curve::dwh_month
    55585
    team::alloccost_curve::dwh_fiscal
    5004024
    team::hardallccost_curve::dwh_week
    5004025
    team::hardallccost_curve::dwh_month
    55586
    team::hardallccost_curve::dwh_fiscal
Issue with Use of Localhost with Jaspersoft
The HTTP and HTTPS Entry URL fields completed for the 
Clarity Project and Portfolio Management (PPM)
 server in Clarity System Administration (CSA) cannot be 
localhost 
when Jaspersoft is integrated with 
Clarity Project and Portfolio Management (PPM)
. When you use Jaspersoft, the URLs must be explicitly entered on the Application subtab of the Properties tab for the 
Clarity Project and Portfolio Management (PPM)
 server.
For example:
HTTP Entry URL: http://<
server name
>:<
port
>
HTTPS Entry URL: https://<
server name
>:<
port
>
Financial Management Changes for Release 14.2
Here are the Financial Management changes for Release 14.2.
Updates to Non Project Investment Objects (NPIOs)
The following updates were made to NPIOs (Programs, Applications, Assets, Products, and Other Work):
  • Enhanced functionality of the 
    Update Earned Value Totals 
    job
    The 
    Earned Value Totals
     job was renamed to 
    Update Earned Value and Cost Totals 
    to reflect new functionality. This job calculates the earned value and costs for projects and costs for NPIOs. The project or the NPIO can be selected using the Investment Browse field on the job properties page. The job contains parameters that let you select the OBS unit, filter mode for the OBS unit, and the investment manager. The functionality of this job can also be invoked using the object action Update Cost Totals on the Team page of an investment.
  • New Object Action on the Investment Staff pages
    The new object action Update Cost Totals is available on all project and NPIO Staff list and detail pages. This object action calculates the allocation and hard allocation costs. Three new fields (Allocation Cost, Hard Allocation Cost, and ETC Cost) were added to represent these values. The fields were added to capture the cost values in the data warehouse and cannot be broken across the time periods.
    These costs can also be selected on custom portlets that are based on the Team data provider. The Staff list and details pages also display the allocation cost and hard allocation cost.
  • Time Slice Changes
    The following time slices were added or renamed to reflect the new functionality:
    • Added:
      Assignment::ETC Cost
      Team::Allocation Cost
      Team::Hard Allocation Cost
    • Renamed:
      Assignment::Actual Cost (previously Assignment::Actual Cost Curve)
Upgrade Action
: None
Resource Average Allocation Percentage
The business logic behind the calculation for the default resource allocation percentage has been improved. When calculating the average allocation percentage and total availability hours, the application uses the start and finish dates for the team member instead of the investment.
This change can affect your own custom metrics and other calculations.
To illustrate the enhancements, create a project with a six-week duration from August 5 to September 13 and staff it with a team of three resources.
  1. On the Team list for the first resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. The allocation is 40/80 or 50 percent as expected.
  2. For a second resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. Add a segment from August 18 to 30 (two weeks, 80 hours) at an allocation of 100 percent.
    • Before this release, the application would calculate an allocation of 120 (40 + 80) and suggest an average allocation percentage for a resource that spans the complete project duration. In other words, the allocation percentage would apply 50 percent to 240, the total hours in the duration of the project (6 weeks x 40 hours = 240).
    • New in this release, the application calculates the allocation of 120 hours but yields a more accurate average allocation of 75 percent. The duration is just four weeks for the resource, not six. Their 120 hours divided by 160 total hours results in an average allocation of 75 percent.
  3. For a third resource, change the finish date to August 17 (two weeks, 80 hours) and the Default Allocation to 50 percent. Adjust this segment by specifying an allocation of 100 percent from August 5 to 17.
    • Before this release, the application would calculate an allocation of 40 hours for the two weeks, but an average allocation of 16.7 percent (40/240).
    • New in this release, the application calculates the same allocation of 40 hours but yields an average allocation of 50 percent (40/80).
Upgrade Action
: None
Portfolio Management Changes for Release 14.2
Here are the Portfolio Management updates for Release 14.2.
Limit on Portfolio Investments Removed
Release 14.2 has no limit on the number of investments that can be included in a portfolio. In previous releases, the limit for investments was 150.
The limits for roles (25) and attributes (700) remain the same.
Upgrade Action
: None
Usability Improvements for the Waterlines View
The following changes were made to the Waterlines view:
  • Pending Edits for Waterlines
    The changes that you make to the Waterlines view are saved as pending edits. The edits are saved temporarily until you save them permanently or discard them. If you navigate away from the view or close the session, the pending edits are saved. When you return to the view, you can still save or discard your pending edits.
  • Discard Changes 
    This button on the Waterlines view lets you discard pending edits. The button is activated when pending edits appear on the view.
  • Improved Waterline View Navigation
    You can scroll in both directions on the Waterlines view to see the complete list of investments. The Waterlines view contains no pagination; the list of investments is refreshed continuously. You can view 150 investments on the view at a time.
    Setting the Aggregate Constraint on the waterline for the first time, running the Portfolio Synchronization job, or changing the ranking rules with a constraint reprocesses the aggregated values in the Waterlines view. Depending on the number of investments in the portfolio, you can experience a slight delay while the calculations are refreshed.
  • Enhanced Waterline Drag and Drop
    A drag-and-drop operation on Waterlines view investments causes a tool tip to appear that shows the drop target and the number of selected rows. The tool tip is a green checkmark. When you reach the top or bottom of the list, the icon changes to a red circle with a line.
Change to the Synchronize Portfolio Investments Job
When the number of portfolio investments added between runs of the 
Synchronize Portfolio Investments
 job is equal to or greater than 1,000, an alert appears. The alert breaks down the number of investments by type and asks if you want to continue with the synchronization.
The alert appears only when the threshold of 1,000 added portfolio investments is reached. The alert can be triggered when the Sync Now button initiates the job.
Upgrade Action
: None
Synchronization Required after Adding Roles
When you add roles to a portfolio on the Targets page, you must click Sync Now to see the latest aggregated and individual role values on the Waterlines view. If you do not synchronize the portfolio after adding roles, an alert appears on the Waterlines view.
Upgrade Action
: None
Project Management Changes for Release 14.2
Here are the Project Management updates for Release 14.2.
Microsoft Project 2013 Service Pack 1
Microsoft Project 2013 Service Pack 1 is supported for integration with the new 
Clarity Project and Portfolio Management (PPM)
 Release 14.2 MSP Interface option. The 
Clarity Project and Portfolio Management (PPM)
 Legacy MSP Interface option does not support the Microsoft Project Service Pack 1.
Upgrade Action
: Alert your project managers to this incompatibility if they plan to use the Legacy Interface option.
Auto-Numbering and Project IDs
If auto-numbering is defined on the project object, the auto-numbering is enforced when you create and save a project to 
Clarity Project and Portfolio Management (PPM)
. The project ID field will be read-only in Microsoft Project.
Upgrade Action
: None
Assignment Max Percent Load is Respected for Fixed Unit Tasks
A flag has been added under Project Management Administration called “MSP Assignment Units Mapping with Clarity Assignment Max % Load" to allow customers to turn on or off the mapping of Max % Load when opening/exporting the project from Microsoft Project.
  • If the flag is checked, the MSP unit is mapped based on the Max % Load value in 
    Clarity Project and Portfolio Management (PPM)
    .
  • If the flag is unchecked, the MSP unit is mapped based on the staff allocation rate base on the date that you opened the project in Microsoft Project.
When saving or importing to 
Clarity Project and Portfolio Management (PPM)
, the MSP assignment units value is always written to Max % Load, regardless of the flag setting under Project Management Administration.
Upgrade Action
: Set this flag based on your requirement for the Max % Load information when opening the project in Microsoft Project.
New UI for Mapping 
Clarity Project and Portfolio Management (PPM)
 Attributes to Microsoft Project Fields
You can create or update the field mapping for 
Clarity Project and Portfolio Management (PPM)
 custom attributes and Microsoft Project fields to synchronize the values when importing and exporting data. Only the custom attributes of the Project, Resource, Task, Assignment, and Team objects can be mapped. The custom attributes must be of following data types:
  • Date
  • Number
  • String
  • Boolean
For more information about mapping fields, see
Project Management
.
Upgrade Action
: None
Data Model Changes for Release 14.2
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.
The following procedure explains how to run the Installation Checker manually.
Follow these steps:
  1. Extract the 
    Clarity Project and Portfolio Management (PPM)
    installer to the 
    Clarity Project and Portfolio Management (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 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 the .jar files ship. The jar files are shipped separately from the 
Clarity Project and Portfolio Management (PPM)
image in the installation media. The Release 14.2 install.jar image does not contain the .jar files mentioned. Any install packages for a previous version included in the install.jar also exclude the .jar files. For each release of
Clarity Project and Portfolio Management (PPM)
, the .jar files are bundled into a folder on the installation media containing third-party libraries .jar file. For Release 14.2, the .jar file is named
thirdparty.libs.14.2.0.jar
.
Upgrade Action
: Retrieve the
thirdparty.libs.14.2.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 .jar 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.
Review the Upgrade Tips
To ensure that your upgrade to this release works as planned, read the following preupgrade and postupgrade tips.
Preupgrade
  • Verify that you have a consistent back-up of the database schema before you upgrade.
  • You must have the standard base calendar available in your 
    Clarity Project and Portfolio Management (PPM)
    application before you upgrade. If you deleted the shipped calendar named
    Standard
    , create it before upgrading. Contact CA Support if your instance is missing the Standard base calendar.
  • Process all
    In progress
    transactions into WIP.
    Verify the following conditions:
    • imp_transactionimport and ppa_transcontrol are clear.
    • WIP adjustments are approved.
    Review and fix all invalid transactions.
  • Review Time Slices.
    Verify that the table is slicing out only the data that is required. If extra data is getting sliced, the database size increases and affects performance.
  • Clear the Datamart and recreate the data post-upgrade to improve the processing time of the upgrade.
    For Release 14.2, the Datamart is automatically cleared for Oracle.Use
    NBI_Clean_Datamart_sp
    to clear the Datamart. The script does not clear the following tables:
    The configuration table (NBI_CFG%)
    Time facts tables that contain historical information (
    NBI_PM_PT_FACTS
    and
    NBI_FM_PT_FACTS
    )
    After the upgrade, run the following jobs to repopulate the Datamart tables:
    • Datamart Extraction job
    • Datamart Rollup job
  • Complete and put all processes on hold.
  • Remove or delete process history, notifications, jobs, or logs. Look for items that you do not need to retain.
  • Pause all scheduled jobs. Take special note of the
    Time Slicing
    job. Pause it before stopping the 
    Clarity Project and Portfolio Management (PPM)
    services before the upgrade.
  • To verify that all components are installed and functioning before and after the upgrade, run the Health Report that is available in Clarity System Administration.
  • Remove all 
    Clarity Project and Portfolio Management (PPM)
    services before running the upgrade using the following command:
    service remove all
    .
  • Verify that no files or folders in the installation folder are in use anywhere.
  • Recommended:
     We recommend that you turn off auditing on all objects before you start the upgrade process.
See the Known Issues for 14.2 for conditions that can affect the success of your upgrade. Take any required corrective actions.
Post Upgrade
  • Review the post upgrade report that the checkinstall utility generates.
    The files are zipped into an archive that has a timestamp-encoded name (for example, checkinstall-results_2014-12-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.
  • Gather the schema statistics by running the Oracle Analyze job at the end of the upgrade.
  • Verify the performance metrics. During the upgrade, performance metrics are collected and the following files are written to the Logs folder:
    • ScriptMetrics.xml
    • Bootstrap.xml
    The files contain the following information:
    • A list of all upgrade scripts executed
    • The row count of every table that is processed by preupgrade and postupgrade processing
    • The execution time and results for each script or object
  • Verify that Beacon is running to manage services and view logs.
Beacon must always run for Release 14.2.
 
  • Ask your functional experts to review your upgraded test system side-by-side with a working preupgrade system.
    Tip
    : Use dual monitors for side-by-side comparison.
  • Review the
    app-ca.log
    after the functional experts have used the test environment and look for new errors.
  • Review any customizations: Customer-added database triggers, custom indexes and constraints, any file system changes, and custom interfaces. Review anything that did not come out-of-the-box. Adjustments may be necessary for customizations to work with this release.
  • Review the system log file sizes. The log file size for all service system log files is set to 5 MB and to keep five rolling logs (for example, app-system.log, app-system.log.1).
    For more information, see Upgrade Considerations for Release 13.1.
  • GEL Tag Restrictions: Release 13.1 gave the ability to restrict certain GEL tags in an environment.
    For more information, see Upgrade Considerations for Release 13.1.
  • The Java Runtime Environment (JRE) is no longer available from the Clarity Software Downloads link. Review the supporting documentation and training materials you provide to your users. Wherever these materials direct users to download the JRE from within
    Clarity Project and Portfolio Management (PPM)
    , update the reference. Direct your users to download the JRE (Version 7) from www.java.com.
  • Register any Portfolio Investment attributes that you want to display in portfolio pages. Although the required attributes display by default, you must register any other attributes (stock or custom) that you want to display.
  • Remove the
    Resource - Edit Financial
    access right.
  • The product supports Microsoft Project 2010 and 2013. If you upgrade and use one of these versions, update your Microsoft Project Desktop to ensure that data populates appropriately in Microsoft Project. Set the scheduling option to Automatic when you want to open the schedule in Microsoft Project.
  • If your company policy does not allow resource managers access to the Financial Properties subpage for the resources they manage, you can remove that capability.
    Run a post installation script to perform the following actions:
    • Remove the
      Resource - Edit Financial
      access right from all current resource managers.
    • Clear the setting for the financial option that automatically grants the access right to new resource managers.
    To maintain existing behavior, this right is granted during the upgrade. This right replaces the automatic right that was removed as part of the Financially Enabled Roles feature.
    Upgrade Action
    : (Optional) Run the script to remove the access right.
    Follow these steps:
    1. At the command line on the 
      Clarity Project and Portfolio Management (PPM)
      server, navigate to the <clarity_home>/bin directory.
      The directory contains the dbpatch script.
    2. Run the following command:
      Windows:
      dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml  - apply
      UNIX:
      ./dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml  - apply
Upgrading Large Data Sets
If your 
Clarity Project and Portfolio Management (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.2. Create a file named
memory.properties
and place it in the $clarity/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
Upgrade to
Clarity Project and Portfolio Management (PPM)
 Release 14.2 
Follow these steps:
  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:
    • Dropped support for Oracle WebLogic.
    • Dropped support for Oracle Solaris.
    • Dropped support for HP-UX.
    • IBM WebSphere is supported only for IBM AIX.
    • Dropped support for 32-bit third-party vendor applications.
    • The Java runtime must be a supported 64-bit version.
    • Dropped support for Oracle 11.2.0.2 in Release 14.1. The supported Oracle databases for Release 14.2 are Oracle 11.2.0.3 and 11.2.0.4.
    • Dropped support for Microsoft SQL Server 2005. If you currently use this version, we recommend upgrading your database to MS SQL server 2008, MS SQL server 2008 R2, or MS SQL Server 2012 before upgrading to this release.
  2. Create a full backup of your database, file systems, and customizations (if applicable).
    Best Practice
    : To keep sequences in line, take a
    cold
    backup.
  3. Remove customer-added database triggers, stored procedures, indexes, views, and constraints before upgrading.
    Due to 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.
  4. Review the steps for installing and upgrading the product in
    Installing and Upgrading
    .
    Some important changes include:
    • The installation for an upgrade prompts you for the current and a target 
      Clarity Project and Portfolio Management (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 14.2 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 
      Clarity Project and Portfolio Management (PPM)
      server in Clarity System Administration (CSA) cannot be
      localhost
      when Jaspersoft is integrated with
      Clarity Project and Portfolio Management (PPM)
      . When you use Jaspersoft, the complete URLs must be entered on the Application subtab of the Properties tab for the 
      Clarity Project and Portfolio Management (PPM)
      server.
  5. Install or upgrade using the steps in
    Installing and Upgrading
    .
  6. 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 Clarity 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
      Clarity Project and Portfolio Management (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
      Clarity Project and Portfolio Management (PPM)
      schema in Release 14.2 (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
      If you have custom Xcelsius dashboards, see Correcting the 
      Clarity Project and Portfolio Management (PPM)
      URL for HTML and Xcelsius Portlets.
  7. Upgrade CABI Release 3.3 SP2 (BusinessObjects) and complete the following steps:
    CABI software is not available for customers installing for the first time. The reporting solution for new customers is Jaspersoft. Only existing customers who have CABI installed already can upgrade. For more information, see
    Installing and Upgrading
    .
    1. If you are upgrading from a version earlier than Release 12.1, reset the passwords of your BusinessObjects report users.
      Resetting is necessary for all preupgrade users who must log in to Infoview and run reports. You can also set up BusinessObjects trusted authentication between BusinessObjects and
      Clarity Project and Portfolio Management (PPM)
      , which provides the LDAP integration with BusinessObjects and
      Clarity Project and Portfolio Management (PPM)
      .
    2. Import the universes.
    3. See Upgrade Reports for information about legacy stock reports and reactivate any necessary existing stock reports.
    4. Manually restart the scheduled reports.
      Any scheduled reports that were configured before the upgrade to this release do not automatically run after the upgrade.
  8. (Optional) Set up Advanced Reporting and complete the following steps:
    1. Set up the Data Warehouse database and populate it with 
      Clarity Project and Portfolio Management (PPM)
      data.
    2. Install Jaspersoft and import the domain information for reporting.
    For more information about setting up the Data Warehouse and Jaspersoft, see
    Installing and Upgrading
    .
  9. 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 
      Clarity Project and Portfolio Management (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 
      Clarity Project and Portfolio Management (PPM)
      content, copy the modified content before upgrading. Then, apply the new incoming stock 
      Clarity Project and Portfolio Management (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: Clarity 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 14.2 upgraded content, apply the changes.
  10. Review the Studio views and system content and manually upgrade as needed.
    The upgrade preserves all preexisting 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 14.2.
    • 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 14.2 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.
  11. 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.
  12. 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 from Niku 6.x, Clarity 7.x, and CA Clarity PPM 8.x
As a best practice, we recommend the following steps for customers on older versions who are upgrading to Release 14.2:
  1. Upgrade to 
    Clarity Project and Portfolio Management (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 Clarity System Administration.
  3. Create a full backup of the database and runtime file system.
  4. Proceed with the upgrade to Release 14.2.
Database Backup Image for New Installations
Clarity Project and Portfolio Management (PPM)
 uses a backup-based database deployment mechanism. The product provides two prebuilt, fully populated database backup
base images
on the installation media. The base images contain everything that a new 
Clarity Project and Portfolio Management (PPM)
installation requires.
Backup images are available for the following databases:
  • The 
    Clarity Project and Portfolio Management (PPM)
    database.
  • The Data Warehouse. If you plan to use Advanced Reporting with Jaspersoft, the Data Warehouse database is required.
The installation media contains the following images:
  • The Microsoft SQL Server base image, compatible with all supported SQL Server versions. Remember to set the database compatibility level to 110 if you are using SQL Server 2012.
  • The Oracle base image, compatible with all supported Oracle versions.
For information about importing a database template image, see
Installing and Upgrading
.
MS SQL Server Database Compatibility Level
Release 14.2 supports database compatibility levels for SQL Server 2008 (100) and SQL Server 2012 (110). A new installation of Release 14.2 on SQL Server 2008 has the correct compatibility level of 100. If you are using SQL Server 2012 for Release 14.2, set the compatibility level to 110 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 110
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 for the 14.2 release. 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 
Clarity Project and Portfolio Management (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 Clarity 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 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (PPM)
    filestore, use
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (PPM)
    runtime folder before the upgrade.
  • Target installation folder: The existing (preupgrade) 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (PPM)
    installation directory also ensures that this process is not repeated when 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (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 
    Clarity Project and Portfolio Management (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 
Clarity Project and Portfolio Management (PPM)
architecture adds this update internally.
Preserve Your File Directory Customizations
During the upgrade to Release 14.2, you are prompted for the target installation directory. New preupgrade and postupgrade steps let you copy files to and from the 
Clarity Project and Portfolio Management (PPM)
directory using ant-based scripting. Use ant scripts to automate preserving and restoring customization in the 
Clarity Project and Portfolio Management (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>