Post-Upgrade Tasks

This section addresses tasks to perform after you upgrade to PPM version 9.50.

Installing Unicode Fonts for Export to PDF

The PPM Dashboard supports exporting PPM portlet content in PDF format in supported languages. To do this, the PPM Dashboard must have access to Unicode fonts.

The Unicode character encoding standard enables the sharing of messages and other items in a multilingual environment when the languages involved span multiple code pages. This means that translated portlet content is exported to PDF files in multiple languages, in one string, and in different locales.

Some operating systems, such as Windows, provide Unicode fonts. If your PPM instance runs on an operating system that does not provide Unicode, you must install a Unicode font on the machine that hosts the PPM Server, and then specify the font location by setting the com.kintana.core.server.dashboard.PDF-Unicode-Font-File-Path dashboard server configuration parameter. You can use any Unicode font (for example, Arial Unicode MS or Code2000). You can set additional font directory paths by setting the com.kintana.core.server.dashboard.Fonts-Directory-Path dashboard server configuration parameter in the server.conf file.

The PPM Dashboard looks for a Unicode font in the standard font locations for the operating system. The table below lists the fonts directories for supported operating systems.

Note: Unicode is the default mode that the PPM Dashboard uses. However, if it cannot locate a Unicode font, it switches to regular mode.

Table 3-1. Operating system-specific fonts directories

Operating System

Fonts Location


  • /usr/openwin/lib/X11/fonts/TrueType

  • /usr/X11/lib/X11/fonts/TrueType

  • /usr/X11/lib/X11/fonts/Type1


  • /usr/contrib/xf86/xterm/fonts

  • /usr/lib/X11/fonts/


  • /usr/share/fonts/truetype

  • /usr/share/fonts/local


  • C:\\WINDOWS\\\Fonts

  • C:\\WINNT\\\Fonts



For information about how to install fonts, see the documentation for your operating system. For information about how to set server configuration parameters, see the Installation and Administration Guide.

Enabling JDK 64-bit (HP-UX Systems Only)

After you upgrade PPM to version 9.50 on the HP-UX system, you must enable JDK 64-bit by the following instructions:

  1. In <PPM_HOME>/bin/, add SYSTEM_PROPS="$SYSTEM_PROPS -d64" under SYSTEM_PROPS="$SYSTEM_PROPS -Dorg.owasp.esapi.resources=$KNTA_HOME/server/$SERVER_NAME/esapi-props/".
  2. Delete or rename <PPM_HOME>/bin/os/

Assigning the Portfolio Mgmt: Edit All Portfolios Access Grant

The Portfolio Manager access grant has been renamed View All Portfolios, and it no longer allows users to create and manage business objectives. Assign the new Edit All Portfolios access grant to users who need to be able to create and manage business objectives.

(Optional) Adding the Portfolio Field to PFM Request Types

Any request type that uses the PFM Asset, PFM Project, or PFM Proposal field group, including the PFM - Proposal, PFM - Project, and PFM - Asset request types, now includes the new Portfolio field. This field displays the portfolio, if there is one, that includes the proposal, project, or asset. For upgrades, this field is hidden by default so the requests do not appear to have changed. The administrator can make the new Portfolio field visible by editing the applicable request header type.

(Optional) Preventing Submission of Time Sheets with Lines that Have No Data

The ability of users to submit time sheets that contain "empty" lines (lines in which all values are 0) is controlled by the setting of a new server configuration parameter ENABLE_TM_ALLOW_EMPTY_ITEM and by a corresponding setting on each time sheet policy. By default, the time sheet policy setting initially reflects the server configuration parameter setting. You can change the time sheet policy setting, which controls the operation when users submit time sheets with empty lines. By default, after the upgrade, the server configuration parameter is set to WARNING—if a user submits a time sheet that contains any empty lines, a message tells the user which of the lines have no time entered (with options to delete all the empty lines at once or move them all to the user's My Items list), but the user is allowed to submit the time sheet anyway. In the past, a user could submit a time sheet with empty lines without seeing a message.

To prohibit users from submitting time sheets that have empty lines, Micro Focus strongly recommends that you change the value of the server configuration parameter ENABLE_TM_ALLOW_EMPTY_ITEM from WARNING to RESTRICT. Thereafter, new time sheet policies (on the Time Sheet Policy tab) will, by default, prevent users assigned to those policies from submitting time sheets that have empty lines. To prohibit users assigned to existing time sheet policies from submitting time sheets that have empty lines, on the Time Sheet Policy tab of those time sheet policies, change the option for specifying the level of enforcement for empty lines to Prevent the Resource from submitting a Time Sheet containing empty lines. The resource must enter time on all lines in the time sheet (or remove the empty lines) before it can be submitted.

For more information about the server.conf parameter, see the Installation and Administration Guide.

For more information about configuring time sheet policies, see the Time Management Configuration Guide.

(Optional) Allowing Users to Include Items from Previous Period When They Create a New Time Sheet

By default, when users create a new time sheet, they can no longer include (copy) items from a time sheet for the most recent previous period. Instead, they can copy all open items from their personal My Items lists.

If you want to allow users to continue to be able to include items from time sheets for the previous period, change the TM_DISABLE_INCLUDING_LAST_TS_ITEMS parameter in the server.conf file from true to false. For performance reasons, we recommend keeping this parameter set to true.

If you change this parameter, users can still choose to include all open items from their My Items lists, but Time Management prevents users from including items from both their My Items lists and a time sheet for the previous period.

(Optional) Importing Freestanding Budgets and Benefits

If you have upgraded from version 7.5 to version 8.00 and then to version 9.50 without running the drop_75_objects.sql database cleanup script after either upgrade, you can still assign former freestanding budgets and benefits retained in the version 7.5 database to requests you specify, and then import the budgets and benefits as financial summary snapshots for those requests. For more information, see "Task 14: Optionally Evaluate Freestanding Budgets and Benefits for Prior Upgrade from Version 7.5" in Preparing to Upgrade and the Upgrade Guide for version 8.00.

Configuring the FTP Server (Windows Systems Only)

PPM uses FTP to move files between machines. To transfer files between machines on a network, each source and destination machine must be running an FTP server. On UNIX platforms, this is standard functionality, but machines running Windows require additional FTP server configuration to function with PPM.

If you are configuring PPM Server after upgrading, you probably already have an FTP server set up. If you do, ensure that the installed FTP server is supported. For information about how to configure an FTP server, see the Installation and Administration Guide.

Supported communication software is documented in the System Requirements and Compatibility Matrix document.