This section contains the following topics:
Supported Upgrade Paths for Release 13.2
Upgrade Considerations for Release 13.2
Before you start the upgrade, we recommend that you read the Basic Upgrade Process process.
If you have any of the following releases installed, you can upgrade to CA Clarity PPM Release 13.2:
Supported patch levels:
Supported patch levels:
Supported patch levels:
Important! If you are on a CA Clarity PPM patch level that is not included in the preceding list, take care when attempting an upgrade to Release 13.2. Issues could result if you try to upgrade to Release 13.2 from a patch level that is not supported. For best results, wait for a supported upgrade path to a later release or patch. To find out more, contact CA Support or your CA Services representative. You can also find more information by visiting the CA Clarity PPM User Communities.
The Release 13.2 installer can upgrade your data set from a variety of older releases. The installer detects how many incremental upgrade paths are required to bring your current installation up to Release 13.2.
Note: If you are running a version earlier than Release 12.1.1, consider upgrading to 12.1.1, 12.1.2 or 12.1.3 before you upgrade to Release 13.2. Although the interim upgrade is not a requirement, it simplifies the troubleshooting and re-start process if an upgrade step fails.
The Release 13.2 installer runs the upgrade processes shown in the following table.
|
Version, Release, or Service Pack Currently Installed |
Upgrade Processes |
|---|---|
|
Earlier than Service Pack 12.1.1 |
|
|
Service Pack 12.1.1, 12.1.2, or 12.1.3 |
|
|
Version 13.0 or Service Pack 13.0.x |
|
|
Release 13.1 or Service Pack 13.1.x |
|
This section provides information about installation and upgrade changes for Release 13.2.
Release 13.2 supports database compatibility levels for SQL Server 2008 (100) and SQL Server 2012 (110). A new installation of Release 13.2 on SQL Server 2008 will have the correct compatibility level of 100. If you are using SQL Server 2012 for Release 13.2, set the compatibility level to 110 from SQL Server Management Studio or use the following command:
EXEC SP_DBCMPTLEVEL <database>, 110
Note: SQL Server 2005 compatibility level (90) has been removed and is no longer supported.
Upgrade Action: Set the database compatibility level after the upgrade is complete. You can set the compatibility level using SQL Server Management Studio or one of the following commands:
SQL Server 2008:
EXEC SP_DBCMPTLEVEL <database>, 100
SQL Server 2012:
EXEC SP_DBCMPTLEVEL <database>, 110
To identify the compatibility level, use the following query:
SELECT NAME DATABASENAME ,COMPATIBILITY_LEVEL COMPATIBILITYLEVEL FROM SYS.DATABASES
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. Starting with Release 13.2, the jars are shipped on a separate DVD from the CA Clarity PPM image DVD. The Release 13.2 install.jar image does not contain the .jar files mentioned. Any install packages for a previous version included in the install.jar also exclude the .jar files. For each release of CA Clarity PPM, the .jar files are bundled into a folder on the DVD containing third-party libraries .jar file. For Release 13.2, the .jar file is named thirdparty.libs.13.2.0.jar.
Upgrade Action: Retrieve the thirdparty.libs.13.2.0.jar file from its DVD. 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.
If you are upgrading a CA Clarity PPM installation that uses generic as the vendor type, update the DataDirect JDBC driver .jar files in your third-party application server environments. The version for these files has changed in Release 13.2.
Upgrade Action: Update your DataDirect JDBC driver .jar files. For more information, see the Installation Guide.
The following functionality is no longer available in CSA:
A Database link still appears, but clicking the link results in database status information only.
XDM installation and application packaging are still available.
Upgrade Action: None
Release 13.2 supports the Oracle DB national character set AL16UTF16.
CA Clarity PPM supports the following character sets:
Keep in mind the following points when using national DB character sets:
See the Oracle documentation for the pros and cons of using different character sets. CA Clarity PPM works with UTF8 and AL16UTF16 National character sets.
Upgrade Action: None
The Oracle 11g template is no longer available on the CA Clarity PPM DVD image. For information about setting up a database instance for the best performance, see the Installation Guide.
The Oracle database backup that is provided with CA Clarity PPM contains the complete schema for a fresh installation of the product. The schema in the backup is named NIKU. The tablespaces are:
If you want to remap the schema or tablespaces, use the Oracle Datapump options. For information about database import operations and Datapump options, see the Oracle website.
Upgrade Action: None
For Release 13.2, changes were made to the Datamart Extraction job. The result of the changes is improved performance for an Oracle full refresh of the Datamart. The job has been optimized to run faster in Oracle. The job does a full refresh of the Datamart tables every time it runs. We recommend running the Datamart Extraction job after the upgrade is complete and during off-peak hours.
Note: No changes were made for Microsoft SQL.
Upgrade Action for Oracle Customers: None. During the upgrade, the Datamart tables are truncated automatically. You do not need to truncate the tables manually before upgrading.
Upgrade Action for Microsoft SQL Customers: Continue to follow the best practice for clearing the Datamart Extraction tables before you upgrade. See the section that is named "Upgrade Tips" for details.
CA has introduced a new, configurable set of CSRF strategies for Release 13.2. The allowed configurations are:
This configuration does not generate CSRF tokens or validate requests. This configuration is the default setting for on-premise installations. This configuration is recommended if CA Clarity PPM is behind your corporate firewall. Customers that upgrade receive this setting automatically.
This configuration implements the same strategy that is used in Release 13.1. This strategy generates a new token for each request and validates against a limited size cache in the user session. Due to the possibility of cache exhaustion, this strategy can lead to false-positive validation errors. These errors are especially true for users who work with multiple tabs open in CA Clarity PPM.
This configuration generates a single token for the user session and uses the token for validation. This configuration is the recommended strategy for on-demand SaaS and hosted installations. The configuration is also recommended for on-premise customer installations where CA Clarity PPM is outside the corporate firewall.
Upgrade Action: The setting is automatically set to none. No further action is required.
To change the shipped setting, see the following Technical Bulletin: TEC567263
Release 13.2 provides a new logging category (security.violation.csrf) and appender for cross-site request forgery (CSRF) exceptions. The exceptions are written to a log file named <service>-security-violations.log.
The category is set to a level of warn by default. Exceptions that are false-positive due to a session timeout are logged at the info level and do not appear in the log.
Upgrade Action: None
Export to Excel and Export to PowerPoint icons on a Resource Planning tab give an error when you click them.
Note: This issue applies only to WebSphere application servers.
As a workaround, use the Export to Excel and Export to PowerPoint links available from the Options icon in the individual portlets on the tabs.
The following section describes important information about upgrading installed add-ins, accelerators, and connectors for Release 13.2.
Note: For more information, see the Installation Guide.
The following table shows the accelerator and connector releases that are compatible with Release 13.2.
|
Accelerator or Connector |
New Installation |
Upgrade from 12.x to 13.2 |
Upgrade from 13.x to 13.2 |
|---|---|---|---|
|
PMO Accelerator |
3.2.00 |
3.2.0 |
3.2.0 |
|
Clarity Solution Pack (CSP) |
3.2.0 |
3.2.0 |
3.2.0 |
|
Earned Value Manager |
2.0.1 |
2.0.1 |
2.0.1 |
|
Accelerator for PRINCE2 |
2.0.1 |
2.0.1 |
2.0.0 or 2.0.1 |
|
Accelerator for the PMBOK |
2.0.1 |
2.0.1 |
2.0.0 or 2.0.1 |
|
Accelerator for New Product Development |
2.0.2 |
2.0.2 |
2.0.2 |
|
PPM Essentials Accelerator |
2.0.2 |
2.0.2 |
2.0.0, 2.0.1, or 2.0.2 |
|
BRM Accelerator |
3.0.2 |
3.0.2 |
3.0.2 |
|
Connector for CA Unicenter Service Desk 12.7 & CA Software Change Manager™ 12.1.0.3 |
2.0.1 |
2.0.1 |
2.0.1 |
|
Connector for CA Unicenter Asset Portfolio Management 11.3.4 |
2.0.1 |
2.0.1 |
2.0.1 |
|
Connector for Microsoft SharePoint 2010 |
2.0.2 |
2.0.2 |
2.0.0, 2.0.1, or 2.0.2 |
|
Service Connect |
2.0.0 |
2.0.0 |
2.0.0 |
|
Catalyst Connector |
2.5.0 or 3.3.0 |
2.5.0 or 3.3.0 |
2.5.0 or 3.3.0 |
|
CA Clarity Agile |
Spring 2013 |
Spring 2013 |
Spring 2013 |
Add-ins, accelerators, and connectors are now included with CA Clarity PPM. You do not have to download the add-in separately and extract the .jar file.
Note: For more information about the new add-in installation process, see the Installation Guide.
Upgrade Action: See the table in the section named "Add-in Compatibilities" if you are required to install a new version of your existing add-ins, accelerators, or connectors.
The removal of old Portfolio features affected the following add-ins:
All three add-ins had portfolio-related portlets that were removed. For BRM Accelerator and NPD, the pages that displayed the portlets were left in place. The pages were left to accommodate customers who placed custom portlets or other valid portlets on the pages. If no custom or other portlets are present, the pages appear blank.
For the PMO Accelerator, the pages that contained portfolio-related portlets were removed. For the list of portlets and other features that were removed from CA Clarity PPM, see the section named "Removal of the Old Portfolio Feature."
Upgrade Action: If you use BRM Accelerator or NPD, review your Studio portlet pages and delete any that are empty.
Before you install the CA Clarity PPM Solution Pack add-in, verify that the compatible versions of CA Clarity PPM and the PMO Accelerator are installed. The CA Clarity PPM Solution Pack installation fails if you do not install the compatible version of the PMO Accelerator add-in before installing the solution pack.
Important! Review the certified and supported versions chart in the CA Clarity PPM Solution Pack Release Notes to determine if an upgrade of CA Clarity PPM and the PMO Accelerator is required, or optional. For complete information, see the CA Clarity PPM Solution Pack Index page on CA Support Online.
|
Copyright © 2014 CA.
All rights reserved.
|
|