Release 13.1 Updates › Upgrade Considerations for Release 13.1

Upgrade Considerations for Release 13.1

This section provides information about installation and upgrade changes since Version 13.0.

New Installer

The new Release 13.1 installer includes the following components:

• Service Pack 12.1.1 installer
• Version 13.0 installer

The Release 13.1 installer runs the upgrade processes shown in the following table.

Installation Checker

A new installation checker is available to assess an installation or upgrade before you start. Although the tool runs automatically at the start of the installation or upgrade, you can run it as a standalone utility. The results are saved in a file named results.htm.

Note: On Solaris 10 systems, you may receive the following message:

Warning: Could not verify 64-bit architecture. Ensure this machine is 64-bit and that it is running 64-bit Java.

If the target system is fully compliant with the Version 13.1 installation prerequisites, you can safely ignore this message.

Upgrade Action: None. For more information about the Installation Checker, see the Installation Guide.

Additional Upgrade Steps (Niku 6.x, Clarity 7.x, CA Clarity 8.x)

Important! If you are upgrading to Release 13.1 and have had an older product version (Niku 6.x, Clarity 7.x, or CA Clarity 8.x) installed, additional steps are required for a successful installation.

Complete these steps if one of the following conditions apply:

• You are currently using one of the listed products.
• You previously had one of the listed products installed.

Upgrade Action: Complete the following steps.

1. Upgrade to CA Clarity PPM Version 13.0.
2. Before you upgrade to either Release 13.1 (or 13.0.1.x), copy the caches.xml file from the following source folder to the appropriate target folder:

   UNIX/Linux

   Source Folder: $NIKU_HOME/.setup/templates/config

   Target Folder: $NIKU_HOME/config

   Windows

   Source Folder: %NIKU_HOME%\.setup\templates\config

   Target Folder: %NIKU_HOME%\config

3. Complete the upgrade to Release 13.1 as documented.

Java Runtime Environment Removed From Download Software Link

The Java Runtime Environment (JRE) is no longer available from the Software Downloads link.

Upgrade Action: Review the supporting documentation and training materials you provide to your users. Wherever these materials direct users to download the JRE from within CA Clarity PPM, update the reference to direct users to download the JRE version 7 from www.java.com.

Users can download the latest update of version 7 that is available. The latest version is what www.java.com offers by default. Eventually, when Java 8 is released, it will become the download default on the website. At that point, remind your users to download version 7, not version 8.

Post Installation Step to Remove the Resource - Edit Financial Right

If your company policy does not allow resource managers access to the Financial Properties subpage for the resources they manage, you can remove that capability.

Run a post installation script to perform the following actions:

• Removes the Resource - Edit Financial access right from all current resource managers.
• Clears the setting for the financial option that automatically grants the access right to new resource managers.

Note: To maintain existing behavior, this right is granted during the upgrade to replace the automatic right that was removed as part of the Financially Enabled Roles feature.

Upgrade Action: (Optional) Run the script to remove the access right.

Follow these steps:

1. At the command line on the CA Clarity PPM server, change to the <clarity_home>/bin directory.

   The directory contains the dbpatch script.

2. Run the following command:

   Windows:

   dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml -apply
   

   UNIX:

   ./dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml -apply
   

New System Log File Default Limits

The default behavior for service system logging has changed. Before this release, the size of the system logs for CA Clarity PPM services (for example, the app-system.log) grew continuously unless manual intervention occurred.

As of this release, the default behavior is to restrict the log file size for all service system log files to 5 MB and to keep five rolling logs (for example, app-system.log, app-system.log.1, and so on).

Upgrade Actions: None. The default settings are automatic.

You can change the default settings, to customize the size and number of log files.

Follow these steps:

1. Log in to Clarity System Administration.
2. Open Home, and click Servers.
3. Click the Properties icon for the server to edit log information.
4. Click the Logs tab.
5. Click the Edit Configuration subtab.
6. In the System Logging section, complete the following fields:

   Maximum number of system logs (per service)

   Indicates the number of files to keep for each service. Changing this value requires restarting the services. The default value is five.

   Maximum size of each system log

   Indicates the size of the system log files for each service in megabytes. Changing this value requires restarting the services. The default value is 5 MB.

7. Save the changes.
8. Restart the affected services.

Commands for GEL Tag Restrictions

Use the following commands to control GEL tag restriction:

admin general restrict-gel-tags

Sets the value of the gelTagRestriction property to on.

admin general allow-gel-tags

Sets the value of the gelTagRestriction property to off.

The property gelTagRestriction is referenced to determine if gel tags are restricted. The property is on the system element. It is an optional element.

Use the values on or off to set GEL tag restrictions for the environment. Specifying any value other than off enables GEL tag restriction. GEL tag restrictions are off by default.

Examples

Properties.xml file with no GEL tag restriction:

<system online="true" multiCurrency="false" licenseTypes="old" singleTenantMode="true"/>

or

<system online="true" multiCurrency="false" licenseTypes="old" singleTenantMode="true" gelTagRestriction="off"/>

Properties.xml file with GEL tags restricted:

<system online="true" multiCurrency="false" licenseTypes="old" singleTenantMode="false" gelTagRestriction="on"/>

Upgrade Action: None

New Languages Supported in the User Interface

The product user interface supports the following new languages:

• Korean
• Simplified Chinese
• Traditional Chinese

Upgrade Action: None

Add-ins Compatibilities

The following list shows the add-ins to upgrade for Release 13.1:

• If you are upgrading from Version 13.0 to Release 13.1, the following add-ins are upgraded:
  • PMO Accelerator
  • Earned Value Manager
  • Connector for CA Unicenter Asset Portfolio Management
  • Connector for CA Unicenter Service Desk and CA Software Change Manager for Distributed

  Note: If you plan to use one of the languages added for Release 13.1 (Korean, Simplified Chinese, or Traditional Chinese), upgrade all installed add-ins.

• If you are upgrading from any version before Version 13.0 to Release 13.1, upgrade all installed add-ins.

The following table shows the accelerator and connector releases that are required for Version 13.0, Service Pack 13.0.1, and Release 13.1.

CA Clarity PPM Solution Pack Compatibility

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.