CA PPM 14.4 Change Impact and Upgrade

HID_release_info_change_impact_odPlan the  upgrade and determine the upgrade options that fit your business needs. As an administrator, use this information to plan your upgrade and training efforts. 
ccppmod144
HID_release_info_change_impact_od
Plan the 
Clarity Project and Portfolio Management (PPM)
upgrade and determine the upgrade options that fit your business needs. As an administrator, use this information to plan your upgrade and training efforts. 
This article covers the new features and enhancements for the current release and specifies any required upgrade actions.
If you are upgrading from an earlier release, review the information for the updates in each incremental release, for example, Releases 14.3, 14.2, 14.1, and the 13.x releases.
2
Supported Upgrade Paths for Release 14.4
If you have any of the following releases installed on the base level with no patches, you can directly upgrade to 
Clarity Project and Portfolio Management (PPM)
 Release 14.4:
  • Clarity Project and Portfolio Management (PPM)
     Release 13.3
  • Clarity Project and Portfolio Management (PPM)
     Release 14.1
  • Clarity Project and Portfolio Management (PPM)
     Release 14.2
  • Clarity Project and Portfolio Management (PPM)
     Release 14.3
Follow the upgrade patch levels and exceptions in the following table only if you have installed any patches on the base versions:
Supported Patch Levels for Upgrade
Upgrade Patch Level Exceptions
Patch level 13.3.0.14 installed on the base version 13.3.0
None
Patch level 14.2.0.7 installed on the base version 14.2.0
None
Patch level 14.3.0.5 installed on the base version 14.3.0
None
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.4. Issues can result if you try to upgrade to Release 14.4 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 CA PPM Community to collaborate with other members.
For information about how to assess an upgrade, see the description of the Installation Checker in
Installing and Upgrading
.
The Release 14.4 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.4.
Upgrade Considerations for Release 14.4
The following information includes the installation and upgrade changes for 
Clarity Project and Portfolio Management (PPM)
 Release 14.4.
Add-in Compatibilities
Review this important information about upgrading installed add-ins, accelerators, and connectors for Release 14.4.
  • If you are upgrading from Releases 13.x or 14.1, 14.2, or 14.3 to Release 14.4, the following add-ins are upgraded automatically:
    • PMO Accelerator
    • Accelerator for the PMBOK
    • CA Agile Planning
  • If you are upgrading from any version before Version 13.0 to Release 14.4, 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 add-ins, accelerators, and connector releases that are included in the following table are compatible with new installations and supported upgrades to Release 14.4:
Add-in, Accelerator, or Connector
Release
End of Life Date
PMO Accelerator
14.4.0
 
Application Portfolio Management (APM) Add-in
14.4.0
 
Agile Add-in
14.4.0
 
Earned Value Manager
2.0.2
 
Accelerator for PRINCE2
2.0.2
 
Accelerator for the PMBOK
2.0.3
 
Accelerator for New Product Development
2.0.4
 
Connector for Microsoft SharePoint 2013
3.0.0
 
CA Agile Planning
14.1.0
 
VersionOne Connector (no longer supported)
14.1.0
 
CA PPM Integration Adaptor (SaaS-only)
14.1.0
 
Business Relationship Manager (BRM) Accelerator
3.0.2
June 30, 2016
Clarity Project and Portfolio Management (PPM)
Catalyst Connector
2.5.0
June 30, 2016
CA Unicenter Asset Portfolio Management (APM) Connector
2.0.2
June 30, 2016
Connector for CA Unicenter Service Desk and CA Software Change Manager
2.0.1
June 30, 2016
PPM Essentials Accelerator
2.0.2
June 30, 2016
Service Connect
2.0.0
June 30, 2016
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.
Oracle Database 12.1.0.2
Set the following Oracle database parameter values to optimize performance when running 
Clarity Project and Portfolio Management (PPM)
 Release 14.4 with Oracle 12.1.0.2.
  • optimizer_adaptive_features=false 
  • optimizer_inmemory_aware=false 
  • optimizer_adaptive_reporting_only=true
Microsoft SQL Server 2008 Database Alert
Starting with 
Clarity Project and Portfolio Management (PPM)
 Release 14.3, Microsoft SQL Server 2008 Enterprise is no longer a supported database platform. Customers using Microsoft SQL Server 2008 Enterprise must upgrade their database edition as a part of their Release 14.3 or 14.4 upgrade planning process.
Upgrade Action:
 If you are using Microsoft SQL Server 2008 (any version), the recommended action depends on your current 
Clarity Project and Portfolio Management (PPM)
 release:
  • Customers on Release 13.3 or above–First upgrade the database version from SQL Server 2008 to SQL Server 2012 Enterprise. Then upgrade 
    Clarity Project and Portfolio Management (PPM)
     directly to Release 14.4.
    Note:
     We recommend that you first upgrade to 
    Clarity Project and Portfolio Management (PPM)
     Release 13.3 before upgrading your database version. Release 13.3 supports both SQL Server 2008 and 2012. You may select any release between 13.3 and 14.1 for this first upgrade path. Do not upgrade to Release 14.2, 14.3, or 14.4 directly if your current 
    Clarity Project and Portfolio Management (PPM)
     version is before 13.3.
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
.
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.4.
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.4. A different file is now used to launch the player package. After you install the patch, republish and upload the content to the On Demand team. For more information, see the CA Productivity Accelerator site.
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)
 SaaS. For more information, see the CA Productivity Accelerator site.
Internet Explorer
If you are using Internet Explorer 11 with 
Clarity Project and Portfolio Management (PPM)
, the browser runs in native Internet Explorer 11 mode.
End of Life for CA Business Intelligence with Business Objects
CA Technologies works continually to improve its software and service offerings to meet the needs of customers. Over the last couple of years, the trend in the business intelligence marketplace has been to shift away from a focus on specialized report writers to empowering business-driven information consumers who want to perform their own data discovery and self-service analysis. This trend has been validated by many 
Clarity Project and Portfolio Management (PPM)
 customers who no longer want reporting to be a specialized silo with extended report development queues. As your innovation partner, we have conducted extensive research on new reporting platforms to meet the needs of our customers and to better align with our 
Clarity Project and Portfolio Management (PPM)
 roadmap. Based on that research, we have selected Jaspersoft as the new business intelligence platform for 
Clarity Project and Portfolio Management (PPM)
. Jaspersoft provides customers with a significantly more powerful yet simpler reporting experience.
With Release 14.4, the ability to configure CA Business Intelligence with Business Objects to work with 
Clarity Project and Portfolio Management (PPM)
 is no longer available.
You can read the complete End of Life (EOL) Announcement on the Product Release and Support Announcements page of CA Support Online.
End of Life for CA PPM Solution Pack (CSP) for Business Objects Reporting Add-In
CA Technologies works continually to improve its software and service offerings to meet the needs of customers. To focus our development efforts and to help our customer base achieve their strategic business initiatives, we are investing our resources in new technology and software and will be dropping support for the 
Clarity Project and Portfolio Management (PPM)
 Solution Pack (CSP) for Business Objects Reporting Add-in. This decision is related to the End of Life Announcement for CA Business Intelligence for 
Clarity Project and Portfolio Management (PPM)
You can read the complete End of Life (EOL) Announcement for CA PPM CSP on CA Support Online.
Upgrade Action:
 None. The Status value for CSP appears as "Upgrade Pending", but you can safely ignore this status.
End of Life for Some Add-Ins and Connectors
CA Technologies is continually working to improve our software and services to best meet the needs of our customers. In order to focus our development efforts and to help our customer base achieve their strategic business initiatives, we are investing our resources in new technology and software, and will be dropping support for these add-ins and connectors:
  • Business Relationship Manager (BRM) Accelerator
  • CA PPM Catalyst Connector
  • CA Unicenter Asset Portfolio Management (APM) Connector
  • Connector for CA Unicenter Service Desk and CA Software Change Manager
  • PPM Essentials Accelerator
  • Service Connect
See the End of Life Announcement on the support page.
User Interface Changes for Release 14.4
The user interface updates for Release 14.4 include the following items:
  • User interface menus, tabs, buttons, and text are updated to reflect the removal of legacy reporting options. Advanced Reporting has replaced the legacy reporting. The product areas that displayed Reports and Jobs in previous releases display only Jobs in Release 14.4.
    Example:
    The following image displays the Jobs option on the Home menu in Release 14.4. This menu option in previous releases displayed Reports and Jobs.
    This image displays the Jobs option on the Home menu in Release 14.4. This menu option in previous releases displayed Reports and Jobs.
  • Report definitions from add-ins that are related to Business Objects are not accessible in the 
    Clarity Project and Portfolio Management (PPM)
     Release 14.4 user interface.
Upgrade Action:
 Access reports through Advanced Reporting. To retain your existing reports from the legacy Business Objects reporting, archive the reports before you upgrade. You will not have access to these reports after upgrading.
Timesheet Changes for Release 14.4
The timesheet updates for Release 14.4 include the following items:
Timesheet Auto-Populate Options
The time entry options for automatically populating a timesheet have been renamed and modified to make them easier to use. The options also now appear as check boxes instead of radio buttons as in previous releases. The check boxes allow you to select as many options as you need.
The project and resource manager can apply timesheet options for all resources, or individual users can set their own timesheet options that apply to their timesheets. When you first open a timesheet, the timesheet is blank, containing no tasks. You can populate the timesheet with tasks by setting timesheet options. If you do not select any of the options, the Populate button does not display on the timesheet.
The renamed timesheet options perform the following tasks:
  • Populate assigned tasks
    : Copies all your task assignments to your current timesheet.
  • Copy time entries from previous timesheet: 
    Copies the timesheet entries from your most recently submitted timesheet (and optionally includes actuals) to your current timesheet. This option does not also populate the assigned tasks as it did in previous releases. To populate assigned tasks and entries from the previous timesheet, select both check boxes.
Upgrade Action:
 Selections from previous releases are applied to Release 14.4. To change options, select as many check boxes as you need.
Resource Management Changes for Release 14.4
Allocation and Actuals for Inactive Projects
In previous releases, time-scaled resource allocation and actuals did not include inactive projects. The Allocation by period columns now support the inclusion of inactive investments on the Detail tab of the following portlets:
  • Top Down Planning by Investment
  • Weekly Detail
Studio developers can take advantage of this enhancement in the Team Allocations system data provider.
Upgrade Action
: Users do not automatically start seeing new information after an upgrade. To view the data from inactive investments, set the Investment Active field to 
No
 in the portlet filter. To see both active and inactive investments, set the filter to 
All
.
Portfolio Management Changes for Release 14.4
You can now include aggregated calculated attributes (ACAs) that you add to investment objects (project, non-project, or the investment object) and those ACAs will be visible in the attribute registry on the Portfolio Investment object. Adding an ACA to a portfolio lets you display summary information that is rolled up from the child investments. If you add an ACA to the Portfolio Investment object, the ACA also becomes available to the following portfolio data providers:
  • Portfolio Investment Provider
  • Portfolio Investment Financial Performance Provider
Advanced Reporting Changes for Release 14.4
The Advanced Reporting updates for Release 14.4 include the following items:
CA Business Intelligence JasperReports Server Cumulative Patch
This release includes a JasperReports Server cumulative patch. This patch corrects several issues that previously occurred with Jaspersoft. Also, this patch and the CA JDBC Adapter allow you to access Jaspersoft Studio without using a virtual private network (VPN). You can then build reports with Jaspersoft Studio without the need for VPN access to the database servers.
Upgrade Actions:
  • You are required to install the CA Business Intelligence JasperReports Server Cumulative Patch. 
  • If you want to access Jaspersoft Studio without using VPN, you must install the Jaspersoft Studio Professional CA JDBC Adapter, which is included in the Jaspersoft Studio client. For more information, see the English edition of the documentation.
New Data Warehouse Configuration Options
You can now select Data Warehouse configuration options from the System Options page in the Administration menu to eliminate unused time slice periods. The new settings help reduce the number of fact records stored and the processing time for populating the Data Warehouse.
Upgrade Action:
 From the General Settings, System Option page under Administration, select from the following Data Warehouse options for the time increments that you want to include as part of the Load Data Warehouse job:
  • Store Weekly Time Increments?
  • Store Monthly Time Increments?
  • Store Fiscal Time Increments?  
If you do not select the applicable options, the Load Data Warehouse job does not load time increment data into the fact tables.
For more information, see Advanced Reporting with Jaspersoft.
Changes to the Create and Update Jaspersoft Users Job
To improve performance, the Create and Update Jaspersoft Users job no longer creates the user-specific folders automatically under the Users folder in Jaspersoft. For example, the 
Clarity Project and Portfolio Management (PPM)
 administrator creates a resource in 
Clarity Project and Portfolio Management (PPM)
 and provides the resource Advanced Reporting access rights. The new resource does not automatically get a folder under the Users folder with the folder name matching the 
Clarity Project and Portfolio Management (PPM)
 resource ID. However, the Jaspersoft administrator can create user-specific folders under the Users folder in Jaspersoft. The administrator must also provide administrative rights to the resources for their user-specific folders so they can manage these folders. Ideally, only the specific Advanced Reporting user and the Jaspersoft administrator need access to the user-specific folders. After upgrade, the content of the user-specific folders remains intact.
Also, the Full Sync option is modified to delete any empty user-specific folders under the Users folder that are created by earlier versions of 
Clarity Project and Portfolio Management (PPM)
. The empty user-specific folders are deleted 
only
 if the folder names correspond to 
Clarity Project and Portfolio Management (PPM)
 resource IDs. The user-specific folders are not deleted if the Jaspersoft administrator follows any other naming convention.
These updates have been back ported to 14.2.0.8 (and higher) and 14.3.0.6 (and higher) patches. For more details, see the corresponding patch readme files.
Legacy Reporting Changes
  • The My Reports portlet has been discontinued and is superseded by new Advanced Reporting features.
  • In a previous release, you might have had a process definition that included a job linked to reports as one of the step actions. After upgrading to this release, these process steps are no longer valid.
  • You cannot continue using or developing Studio lookups, object action menus, or links to legacy reporting options.
  • Business Objects report definitions no longer appear on the Reports and Jobs page. That page is renamed as the Jobs page.
  • XOG files that were related to Business Objects have been updated.
  • Xcelsius features have been deprecated due to new Advanced Reporting options. However, interactive portlets are still available for existing users with legacy content. After upgrading, you no longer have Xcelsius portlets, dashboards, queries, or lookups. You can enable these legacy features to create custom interactive portlets. To create interactive portlets, you can license Xcelsius independently; we no longer provide this Business Objects client software option.
  • You can still use the XML Open Gateway (XOG) to import or export interactive portlets.
  • Business Objects Web Service URL and Business Objects Session ID are no longer supported. This release does not include those two global parameters for interactive portlets. If portlets include Crystal Reports and either the Business Objects Web Service URL or Session ID parameters, they no longer function. The application does not support any interactive portlet functionality requiring Business Objects.
  • Your existing interactive portlets and custom dashboards are still available.
  • You can still create custom interactive portlets with 
    Clarity Project and Portfolio Management (PPM)
     Web Services. These portlets and their Web Services URL continue to function as they did in previous releases.
Advanced Reporting Access Rights and License Types
The associated license type for the following Advanced Reporting access rights has changed from 
restricted
 to 
view-only
:
  • Advanced Reporting - Navigate
  • Advanced Reporting - Report Create
Upgrade Action
: After an upgrade to this release, the Rights By License Type portlet displays the View-Only or Viewer license type (depending on the License Type selected in CSA) for these two access rights. Administrators might also experience an update of the user count values in the User Count by License Type portlet. To learn more, see Advanced Reporting Access Rights and Configure Functionality by User Type.
Security Model Update
The Load Data Warehouse Access Rights job has been rewritten for faster performance. As a result, the performance of the Load Data Warehouse Access Rights job is significantly improved especially for customers with a large dataset.
The following improvements were made to the Data Warehouse schema for the security model:
  • The following security tables have been removed and recreated as views to support existing reports. The views are not for use when building new reports.
    • DWH_INV_SECURITY
    • DWH_RES_SECURITY
  • The 
    Clarity Project and Portfolio Management (PPM)
     security tables are now copied to the Data Warehouse with minor enhancements and consistent naming conventions.
  • The views are recreated and used for generating ad hoc views and reports. 
Upgrade Actions
:
  1. After upgrading, run the following jobs in the listed order:
    • Load Data Warehouse (select the Full Load option)
    • Load Data Warehouse Access Rights
  2. Do not use the following views to build new reports. The views were created to support the existing reports that were based on the deprecated tables. The existing reports will still work but you may experience slow performance:
    • DWH_INV_SECURITY
    • DWH_RES_SECURITY
  3. Use the following views to build new reports:
    • DWH_RES_SECURITY_v
    • DWH_INV_SECURITY_v
Studio Changes for Release 14.4
The Studio updates for Release 14.4 include the following items.
Interactive Portlets Based on Business Objects
Custom interactive portlets from previous releases that were based on the Business Objects universes are no longer supported when you upgrade.
Upgrade Action
: As a Studio developer or administrator, remove or adjust these portlets so that they no longer reference legacy reporting functionality.
Secure Dynamic Lookups
This release imposes enhanced security constraints on 46 dynamic system lookups. The system filters the data returned from these lookups according to the access rights for the current user. In previous releases, all resources who could access a given lookup field could view all its associated data.
Upgrade Action
: Assign the appropriate instance or global access right for each user or group. Advise users that the available list of items that they can browse in lookups can vary by user.
The following list shows the secure lookups and their required instance rights. The names for the associated global rights do not appear to avoid adding redundant information. The names of the global rights are similar to the instance rights. For example, when the instance right is 
Resource - View
, the corresponding global right is 
Resource - View - All
. For the 
Project - View
 instance right, the global right is 
Project - View Management - All
.
Each entry uses the following format:
Lookup_Name
(browse object or list item) Secure NSQL Tag
  • Required instance rights.
BROWSE_INV
(investments) WHERE:SECURITY:INV:p.ID
  • Project - View
  • Service - View
  • Other Work - View
  • Idea - View
  • Product - View
  • Application - View
  • Asset - View
BROWSE_PRODUCTS_SERVICES
(products and services) WHERE:SECURITY:INV:p.ID
  • Service - View
  • Product - View
BROWSE_PROJECT_TASKS
(tasks for a project) WHERE:SECURITY:INV:task.prprojectid
  • Project - View
BROWSE_PROJECT_TEAM
(team members for a project) WHERE:SECURITY:RESOURCE:resources.ID
  • Resource - View
BROWSE_PROJECT_WBS
(project tasks that have external IDs) WHERE:SECURITY:INV:INV.ID
  • Project - View
BROWSE_ROLE_BY_TYPE
(roles) WHERE:SECURITY:RESOURCE:SRM_RES.ID
  • Resource - View
BROWSE_USER
(users) WHERE:SECURITY:RESOURCE:RESOURCES.ID
  • Resource - View
BROWSE_WBS_PARENT_TASKS
(tasks for a project hierarchy) WHERE:SECURITY:INV:INV.ID
  • Project - View
BROWSE_WBS_RESOURCES
(resources) WHERE:SECURITY:RESOURCE:SRM_RESOURCES.ID
  • Resource - View
BROWSE_WBS_TEAM
(team members for a project hierarchy) WHERE:SECURITY:INV:INV.ID
  • Project - View
DPT_PARENT_DEPT_PARAMETERIZED
(departments) WHERE:SECURITY:DEPARTMENT:D.ID
  • Department - View
IMM_BROWSE_ACTIVE_USER
(active users) WHERE:SECURITY:RESOURCE:r.ID
  • Resource - View
IMM_BROWSE_INVESTMENT
(investments for an incident) WHERE:SECURITY:INV:I.ID
  • Project - View
  • Service - View
  • Other Work - View
  • Idea - View
  • Product - View
  • Application - View
  • Asset - View
LOOKUP_FIN_AFFILIATED_PROJECTS
(projects) WHERE:SECURITY:INV:INV.ID
  • Project - View
LOOKUP_FIN_ROLES
(financial roles) WHERE:SECURITY:RESOURCE:S.ID
  • Resource - View
LOOKUP_FIN_TASKS
(financial tasks) WHERE:SECURITY:INV:INV.ID
  • Project - View
LOOKUP_INVESTMENTS_CAPEX
(investments that are not yet enabled for capitalization) WHERE:SECURITY:INV:INV.INVESTMENT_ID
  • Project - View
  • Service - View
  • Other Work - View
  • Idea - View
  • Product - View
  • Application - View
  • Asset - View
LOOKUP_INVS_COSTPLAN_CAPEX
(investments that are enabled for capitalization; plan of record and budget not using cost type) WHERE:SECURITY:INV:I.ID
  • Pr
    oject - View
  • Service - View
  • Other Work - View
  • Idea - View
  • Product - View
  • Application - View
  • Asset - View
LOOKUP_PARAM_DEPT_CODE
(departments) WHERE:SECURITY:DEPARTMENT:DEPARTMENTS.ID
  • Department - View
LOOKUP_PARAM_LOC_ID
(locations) WHERE:SECURITY:LOCATION:LOCATIONS.ID
  • Location - View
LOOKUP_PARAM_LOC_PKID
(locations) WHERE:SECURITY:LOCATION:LOCATIONS.ID
  • Location - View
LOOKUP_PARAM_RES_DEPT_CODE
(departments for resource financials page) WHERE:SECURITY:DEPARTMENT:DEPARTMENTS.ID
  • Department - View
LOOKUP_PARAM_RES_LOC_CODE
(locations for resource financials page) WHERE:SECURITY:LOCATION:LOCATIONS.ID
  • Location - View
LOOKUP_PLAN_OF_RECORD
(portfolio plan of record) WHERE:SECURITY:PFM_PLAN:PLN.ID
  • Portfolio - View
LOOKUP_RESOURCES
(active and locked resources) WHERE:SECURITY:RESOURCE:r.ID
  • Resource - View
LOOKUP_USERS
(active users) WHERE:SECURITY:RESOURCE:r.ID
  • Resource - View
PFM_PORTFOLIOS
(portfolios) WHERE:SECURITY:pfm_portfolio:P.ID
  • Portfolio - View
PRJ_RES_ASSOC
(resources associated with a project instance) WHERE:SECURITY:RESOURCE:r.id
  • Resource - View
PSP_SUBPROJECTS
(subprojects) WHERE:SECURITY:INV:INV.ID
  • Project - View
  • Service - View
  • Other Work - View
  • Idea - View
  • Product - View
  • Application - View
  • Asset - View
PV_MAPPED_TASKS
(tasks) WHERE:SECURITY:INV:INV.ID
  • Project - View
RIM_BROWSE_ISSUES
(issues) WHERE:SECURITY:RISK:RIM.ID
  • Project - Risk, Issue, Change Request - View
RIM_BROWSE_RISKS
(risks) WHERE:SECURITY:RISK:RIM.ID
  • Project - Risk, Issue, Change Request - View
RPT_CUST_DEPT
(customer departments) WHERE:SECURITY:DEPARTMENT:dept.ID
  • Department - View
RPT_PROV_DEPT
(provider departments) WHERE:SECURITY:DEPARTMENT:dept.ID
  • Department - View
RQP_LOOKUP_RELEASES
(releases) WHERE:SECURITY:release:release.ID
  • Release - View
SCH_BROWSE_DEPT
(departments) WHERE:SECURITY:DEPARTMENT:D.ID
  • Department - View
SCH_BROWSE_DEPT_CODE
(departments) WHERE:SECURITY:DEPARTMENT:D.ID
  • Department - View
SCH_BROWSE_LOC
(locations) WHERE:SECURITY:LOCATION:L.ID
  • Location - View
SCH_BROWSE_LOC_ID
(locations) WHERE:SECURITY:LOCATION:L.ID
  • Location - View
SCH_BROWSE_LOC_ID1
(locations) WHERE:SECURITY:LOCATION:L.ID
  • Location - View
SCH_BROWSE_PARENT_DEPT
(departments) WHERE:SECURITY:DEPARTMENT:D.ID
  • Department - View
SCH_BROWSE_PARENT_LOC
(locations) WHERE:SECURITY:LOCATION:L.ID
  • Location - View
SCH_BROWSE_USER
(resources) WHERE:SECURITY:RESOURCE:RESOURCES.ID
  • Resource - View
SCH_BROWSE_USER_NAME
(resources) WHERE:SECURITY:RESOURCE:RESOURCES.ID
  • Resource - View
SEARCH_BROWSE_USERS
(resources who can be owners of searchable items) WHERE:SECURITY:RESOURCE:r.ID
  • Resource - View
TASK_ASSIGNED_RESOURCES
(resources assigned to a task) WHERE:SECURITY:RESOURCE:res.ID
  • Resource - View
Integration Changes for Release 14.4
The integration updates for Release 14.4 include the following items:
Integration with CA Agile Central (formerly Rally)
  • Clarity Project and Portfolio Management (PPM)
     integrates with CA Agile Central agile development software. The CA Agile Central integration now works with CA Agile Central SaaS and also with CA Agile Central On Premise 2015.2 and it supports WSAPI version 3.0. To learn more, see 
    Rally Integration
     in the Add-ins and Integrations section.
  • Now you can synchronize the 
    Clarity Project and Portfolio Management (PPM)
     project team with the users assigned to CA Agile Central Features and Initiatives. For an integration instance, you can also specify whether or not the synchronized team members are open for time entry in 
    Clarity Project and Portfolio Management (PPM)
    . To get the latest integration functionality, upgrade customers must install the upgrade ready items of the supported version of the Agile add-in. See 
    Add-Ins Compatibilities
     in the CA PPM 14.4 Release Notes.
  • The integration now supports universal unique IDs (UUID). After upgrade, once the Rally Synchronization job executes successfully on existing Rally instances, the following values are automatically converted to UUID:
    • Integration Instance object ID
    • Default Rally Owner ID
    • Default Rally Project ID
Administration Changes for Release 14.4
The Administration updates for Release 14.4 include the following items:
New Password Policy
The new password policy complies with the following rules out-of-the box:
  • Minimum password length is eight characters including a minimum of one uppercase, one lowercase, one numeric, and one special character.
  • You can reuse a password only after 60 days and following the use of four consecutive unique passwords.
  • The password and user name cannot be the same.
  • The new password policy is applied automatically in the system options but upgrading customers can continue to use the existing password. In the future, when the customer chooses to change the password, the new password policy is applied automatically.
You can overwrite the default password policy rules by selecting the Custom Expression option and specifying your own regular expression for a password.
Process Invalidation for Jobs Linked to Removed Reports
In this release, legacy Business Objects reports were removed. If a process step included a job that was linked to reports, that process is invalidated after upgrading.
Upgrade Action
: As an administrator, examine the step and remove the legacy report reference to revalidate the process.
Changes to the Load Data Warehouse Job
Running the Load Data Warehouse job with the Full Load option selected now adds the following financial plans for all applicable investments to the Data Warehouse:
  • The Plan of Record
  • The current budget plan
  • All benefit plans
All cost plans and budget plans are no longer loaded to the Data Warehouse.
Access Rights for Removed Reports
Because their associated reports were removed in this release, the following access rights for reports were also removed:
  • Report - Edit Properties
  • Report - Run
  • Report - View Output
  • Report Label - XOG Access
  • Report Type Creator (Auto)
  • Reports - Access
  • Reports - Run - All
  • Reports - View Output - All
  • Run Report (Auto)
  • Software Download - Xcelsius
The following table lists the access rights that were renamed:
Previous Name
New Name
Reports and Jobs - Administrator Access
Jobs - Administrator Access
Reports and Jobs - Create Definition
Jobs - Create Definition
Reports and Jobs - Edit Definition
Jobs - Edit Definition
Reports and Jobs - Edit Definition - All
Jobs - Edit Definition - All
Governor Settings
The following table lists the recommended default governor settings. 
Governor Setting
Default Value
Units
Maximum file size for a document
Note:
This restriction is applied at the time that documents are uploaded to
Clarity Project and Portfolio Management (PPM)
. Previously existing documents that exceed the setting are not affected.
20
MB
Maximum number of rows that you can export to Excel
25,000
rows
Maximum number of rows that can be fetched in a list view or grid portlet
Note:
Only applicable if you have aggregation configured on the list view or grid portlet.
50,000
rows
Maximum number of rows that you can retrieve using GEL script
Note:
Only applicable to select queries that are run through GEL script.
100,000
rows
Maximum number of tasks that you can add to a timesheet
250
tasks
Maximum number of nodes that you can read or write through XOG
150,000
nodes
Maximum number of attributes that a portfolio can have
700
attributes
Maximum number of roles that a portfolio can have
25
roles
Rollover Interval Change for Time Slices
To improve Data Warehouse performance, the rollover interval for the following time slices is updated from 
weekly
 or 
monthly
 to 
quarterly
:
  • WEEKLYRESOURCEESTCURVE
  • WEEKLYBASEASSIGNCOSTS
  • WEEKLYRESOURCEBASECURVE
  • WEEKLYRESOURCEAVAILCURVE
  • WEEKLYRESOURCEHARDALLOC
  • WEEKLYRESOURCEALLOCCURVE
  • DAILYRESOURCETIMECURVE
  • WEEKLYRESOURCEACTCURVE
  • MONTHLYRESOURCEACTCURVE
  • MONTHLYRESOURCEESTCURVE
  • MONTHLYBASEASSIGNCOSTS
  • MONTHLYRESOURCEAVAILCURVE
  • MONTHLYRESOURCEBASECURVE
  • MONTHLYRESOURCEALLOCCURVE
  • MONTHLYRESOURCEHARDALLOC
Upgrade Action
: None. If the Entity for Fiscal Periods is set up under Administration, General Settings, System Options, the rollover interval automatically changes to 
quarterly
 after an upgrade.
Installation Changes for Release 14.4
The Installation updates for Release 14.4 include the following items:
Migrate from WebSphere to Tomcat before Upgrading to 
Clarity Project and Portfolio Management (PPM)
 Release 14.4
If you are using WebLogic/WebSphere in a previous release, you must migrate to Tomcat before you upgrade to Release 14.4.
We recommend that you consult the CA Services team for help in transitioning your environment to Tomcat.
In your previous 
Clarity Project and Portfolio Management (PPM)
 version on WebSphere/WebLogic, a standard clarity/ppm directory structure was initially created to generate the NSA.EAR file. This directory structure is also used to apply patches and upgrades. The following steps provide a high-level overview of the process of migrating to Tomcat.
  1. After a supported Tomcat and JDK are installed on the server, update the application server "vendor" and "home" directories for Tomcat in the “applicationServer” section of the properties.xml file (if not already updated). The following image shows the new values for "vendor" and "home".
    This image shows the updated values for the application server vendor and home directories.
  2. With these parameters set, add the NSA service from the command line:
    \> service add deploy start nsa
    \> service start beacon
    If the service command does not work, navigate to the PPM_HOME\bin directory to execute the PPM service commands.
  3. With both beacon and NSA running, log in to CSA and finalize the configuration according to the steps in 
    Installing and Upgrading
    . With all appropriate sections completed in CSA, add an APP service from either the CSA web interface or the command line (following the instructions provided in 
    Installing and Upgrading
    ).
  4. Start the 
    Clarity Project and Portfolio Management (PPM)
     app service and navigate to your 
    Clarity Project and Portfolio Management (PPM)
     URL to log in.  Verify that all functionality is working on Tomcat.  Once validated, proceed with upgrading to Release 14.4 (as described in 
    Installing and Upgrading
    ).
Upgrade Action:
 Migrate from WebLogic/WebSphere to Tomcat before you upgrade to Release 14.4.
REST API Changes for Release 14.4
The CA PPM REST APIs now support the Delete HTTP method for accessing the REST APIs. API support is also extended to include the following operations:
  • Create, update, retrieve, or delete teams and assignments
  • Create, update, retrieve, or delete timesheets
  • Create, update, or retrieve project status reports
  • Delete tasks
To learn more, see 
REST APIs
 in the 
Reference
 section of the English edition of this documentation.
Open Workbench Changes for Release 14.4
The Open Workbench updates for Release 14.4 include the following items:
Keep Original Project Baselines when Transferring Assignments
In Open Workbench, you can transfer specific task assignments from one resource to another using the Transfer Assignments dialog. With Release 14.4, the Keep Baselines check box on this dialog is now selected by default. This setting transfers the original assignment baselines to the new resource.
Upgrade Action:
 None
Documentation and Online Help Changes for Release 14.4
New and expanded cloud-based online help documentation is available at docops.ca.com (formerly wiki.ca.com). Users can continue to click the Help link from the product user interface. The resulting documentation takes the following factors into account before showing the best matching help page: 
  • the current release of your product
  • the current environment (SaaS or On-Premise)
  • the current language setting for the software as set by the current user
  • the current page the user is viewing 
When documentation is not available in the language that matches the user interface, the English edition appears. For example, Studio Developer content appears only in English. 
Upgrade Action
: We recommend that you install patch 14.4.0.2 or later. The Help feature requires no upgrade action when you apply this patch. The patch shifts the processing of online help requests from the server to the client browser. To view the online help, users need to allow popups and clear their browser cache files. The 14.4.0.2 or higher patch updates your wikihelp.properties file on each server in your cluster. The patch changes the wiki.ca.com entry to docops.ca.com. It also changes the help.restURL parameter to:
help.restUrl=https\://docops.ca.com/rest/ca/product/latest/topic?hid\=${hid}&space\=${space}&language\=${language}&format\=${format}
The patch eliminates the need for manual changes. You no longer need to set a port because access is through the client browser. You do not need special firewall access for the online help.
For previous 14.4.x versions without the 14.4.0.2 patch, apply one of two methods to activate the new online help on each application server. Method 1 is a redirect and Method 2 enables direct access to the new docops.ca.com content. To view the online help, users need to allow popups and clear their browser cache files.
Method 1: Allow a Redirect to docops.ca.com
Add the required DNS entries and edit the firewall settings to allow connections to docops.ca.com. Contact your network team to configure a new firewall rule or ACL update for every application server in your 
Clarity Project and Portfolio Management (PPM)
 cluster. The following table serves as an example of the type of information that is required:
Source
Destination
TCP/UDP
Direction
Server 1:
ppm_app_server_IP
52.22.142.110  and 52.1.70.157 
docops.ca.com:443
TCP
Uni-directional
Server 2:
ppm_app_server_IP
52.22.142.110  and 52.1.70.157
docops.ca.com:443
TCP
Uni-directional
Server 3:
ppm_app_server_IP
52.22.142.110  and 52.1.70.157
docops.ca.com:443
TCP
Uni-directional
For the redirect to work, allow connections to docops.ca.com on port 80 or 443. The old IP (199.119.123.234) changed in June 2016 to 52.22.142.110 and 52.1.70.157.
Method 2: Configure Direct Access to docops.ca.com
Your firewall and internet access policy might not allow server traffic on port 80. Apply the following change to use port 443 exclusively instead:
  1. Open the following file:
      %CLARITY_HOME%\webroot\help\wikiHelp.properties 
  2. Locate the following line:
      help.restUrl=http\://wiki.ca.com/rest/ca/product/latest/topic?hid\=${hid}&space\=${space}&language\=${language}&format\=${format} 
  3. Change the line to the following entry:
      help.restUrl=https\://docops.ca.com:443/rest/ca/product/latest/topic?hid\=${hid}&space\=${space}&language\=${language}&format\=${format}
    1. Change http to https
    2. Change wiki.ca.com to docops.ca.com
    3. Change the port (not shown) from 80 to 443
  4. Contact your network team to configure a new firewall rule or ACL update for every application server in your cluster. Refer to the table in Method 1. Configure access to docops.ca.com by allowing IP traffic to and from 52.22.142.110 and 52.1.70.157 over port 443.
Database Schema Changes
See the 
Reference
 section of the English edition of this documentation.
Known Issues for Release 14.4
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.
Error Occurs after Changing Locale and Language from English to Japanese when Using Oracle 12.1.0.2
The following error message appears when you change the locale and language settings from English to Japanese on the Account Settings page under Home:
ERROR 2016-04-11 08:35:10,373 [http-nio-8080-exec-35] odf.lookup (clarity:admin:5153013__AA4FD3E5-6816-46A0-9DCA-A4AD78238D10:odata.GetListContextByRow) com.niku.union.persistence.PersistenceException: SQL error code: 12743Error message: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-12743: internal LX error code, arguments: [evacol], [lxrmcl], [20]
To resolve this issue, apply one of the following patches for Oracle 12.1.0.2:
  • Windows: Patch 22310559 Version 12.1.0.2.160119
  • Linux: Patch 21948354  PSU: 12.1.0.2.160119
Error May Occur while Restoring Data Backups during Upgrade
During an upgrade to Release 14.4 using an Oracle database, you may receive an error when you restore your data backups. The following error message can appear:
ORA-01792: maximum number of columns in a table or view is 1000
For example, the creation of the database views ODF_PFM_INVESTMENT_CALCS_P_V and ODF_PFM_INVESTMENT_CALCS_P_V2 fails with this error message. Other database views may also fail to be restored.
To resolve this issue, use one of the following workarounds:
  • Run the following command with system privileges in Oracle:
    ALTER SYSTEM SET "_fix_control"='17376322:OFF'
    Note:
     For more information about the fix_control parameter, see the following Oracle community discussion: https://community.oracle.com/thread/891457
  • Apply the Oracle patch 19509982 to disable the error by default. This patch is available from Oracle online support. An Oracle login is required.
Data is not Loaded in the Data Warehouse
Data is not loaded in the Data Warehouse if English is not added as one of the languages in the Data Warehouse setup. This issue occurs even after the Load Data Warehouse job completes successfully. Add English in the Languages field of the Data Warehouse Options (Administration, General Settings, System Options). For example, if Spanish is the only language you need, you still have to select both Spanish and English for the data to load successfully in the Data Warehouse after the Load Data Warehouse job.
Data Warehouse Configuration Options Visible on the User Interface but not Functional
The following Data Warehouse configuration options are currently visible on the user interface but will not be functional until a future release:
  • Disable Resource Security for Reporting?
  • Disable Investment Security for Reporting?
Investment Hierarchy Does not Support Custom Time-Scaled Value Attributes
In 
Clarity Project and Portfolio Management (PPM)
 Studio, the Investment (project) Hierarchy Financial Rollup page does not display valid values for custom time-scaled value field attributes. The values all display as zero, even when there is actual data available. The out-of-the-box time-varying attributes (for example, Actuals for Labor Resources or ETC for Labor Resources) do display the correct values. 
Project Status Attribute can be Updated through the CA PPM API by End Users
The Project Status attribute can be updated through the 
Clarity Project and Portfolio Management (PPM)
 API by end users who have the Project Financial-Edit access rights. If this issue could cause problems in your 
Clarity Project and Portfolio Management (PPM)
 environment, we recommend that the API application developer does not expose this attribute in the application.
Advanced Reporting Views and Reports Display Blank Values for the Exchange Rate Key field
In a multi-currency system with foreign exchange rates defined, the Advanced Reporting views and reports display blank exchange rate key values if all the following conditions are true:
  • The Exchange Rate Key field has a value with greater than 10 digits.
  • The Exchange Rate Key field is added to any of the existing reporting domains.
  • The Exchange rate key field is used in any of the reports.
To resolve this issue for any new reports that you create using the existing views that include the Exchange Rate Key field, perform the following steps:
  1. Open the domain in question and edit it using the domain designer.
  2. Try saving the domain without making any changes.
    A message appears notifying about the affected ad hoc views.
  3. For all the affected ad hoc views, remove the Exchange Rate Key field from Columns, Rows, Groups, Filters, and Select Fields.
  4. Save changes to the domain.
  5. Edit the ad hoc views and add the Exchange Rate Key field back to the views.
All the new reports that you create from the resolved ad hoc views show the correct values for the Exchange Rate Key field. However, the existing reports show some inconsistent values for this field. To fix the existing reports, recreate these reports using the resolved ad hoc views.
Invalid Data Adapter Causes Jaspersoft Studio Professional to Hang
A data adapter can become invalid at any point because of any of the following reasons:
  • User does not exist
  • Bad password
  • Server down
If you last saved your Studio report using a data adapter that is no longer valid, then the next time you open the query dialog box and try to select a valid adapter, Jaspersoft Studio just hangs. To resolve this issue, complete the following steps:
  1. Change the adapter to a valid adapter and click OK.
    Jaspersoft Studio no longer tries to connect to the invalid adapter and the report has the valid adapter.
  2. Reopen the query dialog box.
    The valid adapter is now available and shows the Database schemas.
 For more information about Jaspersoft Studio Professional and data adapters, see Advanced Reporting with Jaspersoft.
Problems with Advanced Reporting Custom Domains and Ad Hoc Views after Upgrading
Custom domain problems may occur with customers who have performed the following upgrades:
  • Upgraded to Release 14.3 or 14.4 from Release 14.2 without first applying Release 14.2 patch 7.
  • Upgraded to Release 14.4 from Release 14.3 without first applying Release 14.3 patch 3.
Symptom
After upgrading, the custom ad hoc view for a custom domain produces an error message and does not work.
Workaround
Use the following steps to resolve this issue:
  1. Open and edit the custom domain in the 
    Clarity Project and Portfolio Management (PPM)
     Advanced Reporting user interface.
  2. Click Check Design in the upper left of the page, wait for the check to complete, and click OK.
  3. Click Submit and wait for the update to finish processing.
    If you do not receive any error message, the domain is now valid.
  4. Open the custom ad hoc view associated with the custom domain.
    An error message no longer appears and the ad hoc view works.
Public Folder Displays in Advanced Reporting
When you create an ad hoc view in Advanced Reporting, you are asked to select a domain data source for the view. Using the tree view, this data source should be selected from your default tenant folder structure. However, the Public folder displays in addition to your default tenant folder. The Public folder does not contain any data. You can ignore the Public folder and select your data source from your tenant folder.
You may also receive the following error messages when you create a shared folder and set global permissions:
Error in getting permission: Resource /public/adhoc;role:/ROLE_REPORT_DESIGNER not found.
Error in getting permission: Resource /public/templates;role:/ROLE_REPORT_DESIGNER not found.
Error in getting permission: Resource /public;role:/ROLE_REPORT_DESIGNER not found.
You can ignore these error messages, since they do not affect user-defined content.
Advanced Reporting Error When Exporting the Project Status Summary Report Gantt Chart to Excel (Paginated)
In Advanced Reporting, when you export the Project Status Summary Report Gantt Chart to Excel (Paginated), you receive an error. The report is not exported to Excel along with the Gantt charts. This is a known issue due to an Excel limitation of 255 columns.
Uninstall Open Workbench and Microsoft Project Older Versions before Installing New Versions
You cannot upgrade from any previous version of Open Workbench or Microsoft Project to the Release 14.4 version. You must uninstall the previous version first and then install the Release 14.4 version.
Rally Synchronization Job Fails with Long Portfolio Item Names
The Rally Synchronization job creates top-level Rally Portfolio Items and 
Clarity Project and Portfolio Management (PPM)
 tasks from the lowest-level Rally Portfolio Items. In Rally, the Portfolio Item name can be 256 characters long. However, the 
Clarity Project and Portfolio Management (PPM)
 task name cannot exceed 150 characters. If the Rally Portfolio Item names are greater than 150 characters, the Rally Synchronization job fails.
Dates in Rally UI and 
Clarity Project and Portfolio Management (PPM)
 UI May Be Different
Rally returns dates in Coordinated Universal Time (UTC) format. Those dates are offset to express local workspace time in UTC. As a result of this date offset in Rally, there could be situations in which the dates in the Rally UI are different than in the 
Clarity Project and Portfolio Management (PPM)
 UI.
 To access an article with more details about how Rally interprets dates, follow these steps:
  1. Access the Rally Community page using the following link:
    Rally Community
  2. Click ASK THE COMMUNITY.
  3. In the Search field, enter the following text and press Enter:
    How to Interpret Date Field Values Returned by WS API
  4. In the Search results, select the article with the same title.
Ad Hoc Views Do not Support Different Date Formats for the Same Language
When you display an Advanced Reporting ad hoc view in the Ad Hoc Viewer, you cannot use different date formats for the same language. For example, if the selected language for display is English, the date format cannot be both MM/DD/YYYY and DD/MM/YYYY. This issue applies to Releases 14.2 and 14.3.
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 (that is, 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 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:
Default sender email.
For 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 
Clarity Project and Portfolio Management (PPM)
 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.
Error Occurs during PMBOK Add-In Installation
You may see the following error message in the admin.log file after installing the PMBOK add-in:
Undefined statement set: odf-pmd..select-distinct-no-security-context-only.map
This error occurs during the application of the groups/pbk_grp.xml. However, the add-in is installed successfully with no loss of functionality. You can safely ignore this error message.
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.
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.
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.
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 <ca_ppm_install_dir>/bin using dbpatch:
POSTUPGRADE_57954_MSSQL_DEL_PROC_INST_ASSGND_OBJ_PERM.xml
Use the following command:
dbpatch -install -file <CA_PPM_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';
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.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 
    Clarity Project and Portfolio Management (PPM)
     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.
Error Occurs when Installing a Plug-In or Starting 
Clarity Project and Portfolio Management (PPM)
The following error can occur during specific actions with 
Clarity Project and Portfolio Management (PPM)
Could not locate PMD file csp.xml in component content 
The actions that cause the error to appear include the following situations:
  • Starting 
    Clarity Project and Portfolio Management (PPM)
  • Installing a plug-in
  • Running bulkImportCaller.bat after setting the values
This error, which you can find in the log files, does not result in any loss of functionality or does not indicate any issues with 
Clarity Project and Portfolio Management (PPM)
. You can safely ignore this error message.
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 scheduled Rate Matrix Extraction job instances and 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 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 Basic runtime 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.
Pre-Upgrade: Evaluate Before You Install or Upgrade
The Installation Checker (checkinstall) utility assesses an installation or an upgrade. The utility runs automatically at the start of an installation or upgrade and at the end of an upgrade attempt. You can also run it manually. The utility produces a report results file (precheck-results.html) in the <install-root>/checkinstall/check-logs directory.
Upgrade Action
: For best results, run the Installation Checker before starting the full installation and upgrade process. Carefully evaluate and resolve warnings before proceeding.
Run the Installation Checker Manually
Follow these steps:
  1. Extract the 
    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.4 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.4, the .jar file is named
thirdparty.libs.14.4.0.jar
.
Upgrade Action
: Retrieve the
thirdparty.libs.14.4.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.
Pre-Upgrade Steps
  • 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.4, 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 a CA PPM System Health Report.
  • 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.4 for conditions that can affect the success of your upgrade. Take any required corrective actions.
 
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.4. Create a file named
memory.properties
and place it in the $cappm/config directory. Set the desired memory values in that file.
Here are the default values that the upgrade uses:
defaultScriptMaxMem=1024m defaultScriptPermGenMem=128m
Here are some sample settings in the
memory.properties
file:
defaultScriptMaxMem=2560m defaultScriptPermGenMem=512m
Upgrade to
Clarity Project and Portfolio Management (PPM)
 Release 14.4 
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:
    • The Java runtime must be a supported 64-bit version.
    • The supported Oracle databases for Release 14.4 are Oracle 11.2.0.3 and 11.2.0.4.
    • Dropped support for all of the following products:
      • Oracle WebLogic
      • Oracle Solaris
      • HP-UX
      • IBM WebSphere
      • IBM AIX
      • 32-bit third-party vendor applications
      • Microsoft SQL Server 2005
        : We recommend upgrading your database to MS SQL Server 2008, 2008 R2, or 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.
    As a result of the database schema changes for this release, most custom triggers, indexes, and constraints can cause the upgrade to fail. We recommend
    removing
    , not disabling, customer-added triggers.
  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.4 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 Project and Portfolio Management (PPM)
      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 Project and Portfolio Management (PPM)
      System Administration server admin.log and install.log for errors.
    3. Reapply any database and file system customizations.
    4. Run the Oracle Table Analyze Job from
      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.4 (CMN_JOB_ANALYZE_SP) and make necessary corrections in the custom statistics job.
  7. (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
    .
  8. 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: PPM Content
      add-in available on the Content Add-ins page for upgrade-ready content. This page is available from the Administration menu. To accept the new Release 14.4 upgraded content, apply the changes.
  9. Review the Studio views and system content and manually upgrade as needed.
    The upgrade preserves all pre-existing Studio view configurations. If an existing view has configurations or if the object for the view is partitioned, the system does not automatically upgrade the view or the partition.
    To determine which views were not automatically upgraded, use the Studio Views list page.
    Use these tips to help you review the views:
    • The Last Version column identifies changes to stock views in Release 14.4.
    • 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.4 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.
  10. 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.
  11. 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.
Upgrade suggestion for Niku 6.x, Clarity 7.x, and CA Clarity 8.x
As a best practice, we recommend the following steps for customers on older versions who are upgrading to Release 14.4:
  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 Project and Portfolio Management (PPM)
    System Administration.
  3. Create a full backup of the database and runtime file system.
  4. Proceed with the upgrade to Release 14.4.
MS SQL Server Database Compatibility Level
Release 14.4 supports database compatibility levels for SQL Server 2012 (119) and SQL Server 2014 (120). A new installation of Release 14.4 on SQL Server 2012 has the correct compatibility level of 110. If you are using SQL Server 2014 for Release 14.4, set the compatibility level to 120 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 120
SQL Server 2005 compatibility level (90) has been removed and is no longer supported.
To identify the compatibility level, use the following query:
SELECT NAME DATABASENAME ,COMPATIBILITY_LEVEL COMPATIBILITYLEVEL FROM SYS.DATABASES
Upgrade Action
: None
Oracle Database Only PRJ_BLB_SLICES Table
The ID, UNIT, LAST_UPDATED_DATE and LAST_UPDATED_BY columns in the PRJ_BLB_SLICES table have been dropped. If you are using Oracle, the table is replicated before the columns are dropped. The replication requires you to verify that the tablespace that PRJ_BLB_SLICES occupies is large enough to accommodate the temporary size increase.
Upgrade Action
:
To determine if the tablespace can deal with this condition, have your database administrator (as sysdba) run the following query. Change the schema owner to the owner of the 
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 Project and Portfolio Management (PPM)
 System Administration (CSA) application. Log in to CSA and navigate to the Documents and Search link under the Properties tab, then review the Store Files in Database property.
If the database is not the filestore repository, action is required. Failure to follow the recommended steps can lead to permanent loss of the filestore contents.
The following changes were made to the upgrade process in Version 13:
  • The upgrade process always installs to an empty destination folder. During the upgrade, files and folders that exist in the target installation folder are moved to a new location before the new files are installed. If the filestore folder is located in the runtime folder, it is moved with the other content (
    not recommended
    ). If the filestore is located outside the runtime folder (the
    recommended
    configuration), the filestore location is not moved or copied from the backup location.
  • The filestore and search index folder structures were altered to accommodate architectural changes in Version 13. This change requires action for all Release 13.x and 14.x upgrades, whether the filestore was located in the installation folder or not.
Your action depends on the following factors:
  • Where the filestore was before the upgrade
  • The target installation folder that is selected during the upgrade
The correction must be made immediately after the upgrade completes, before any files are added to the filestore. Any files added to the filestore before the correction is made must be manually preserved using the following steps:
  1. Use 
    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.
Upgrade Reports
This release of 
Clarity Project and Portfolio Management (PPM)
uses the Advanced Reporting solution. This solution uses a 
Clarity Project and Portfolio Management (PPM)
Data Warehouse and a third-party reporting tool (Jaspersoft). Both ship with
Clarity Project and Portfolio Management (PPM)
.
Preserving Your File Directory Customizations
During the upgrade to Release 14.4, 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>