HP Man PPM9.30 InstallationAdmin 3rded PDF

HP Project and Portfolio
Management Center
Software Version: 9.30

Installation and Administration Guide
Document Release Date: November 2014

Software Release Date: September 2014
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software,
Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Copyright Notice
© 1997 - 2014 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe® is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Documentation Updates
The title page of this document contains the following identifying information:
l Software Version number, which indicates the software version.

l Document Release Date, which changes each time the document is updated.
l Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using the most recent edition of a document, go to: https://softwaresupport.hp.com/.
This site requires that you register for an HP Passport and to sign in. To register for an HP Passport ID, click Register on the HP Support site or click Create an Account on the
HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
The following table indicates changes made to this document since the last released edition.
Support
Visit the HP Software Support site at: https://softwaresupport.hp.com.
This website provides contact information and details about the products, services, and support that HP Software offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your
business. As a valued support customer, you can benefit by using the support website to:
l Search for knowledge documents of interest

l Submit and track support cases and enhancement requests
l Download software patches
l Manage support contracts
l Look up HP support contacts
l Review information about available services
l Enter into discussions with other software customers
l Research and register for software training
Most of the support areas require that you register as an HP Passport user and to sign in. Many also require a support contract. To register for an HP Passport ID, click
Register on the HP Support site or click Create an Account on the HP Passport login page.
To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.
HP Software Solutions Now accesses the HPSW Solution and Integration Portal website. This site enables you to explore HP Product Solutions to meet your business needs,
includes a full list of Integrations between HP Products, as well as a listing of ITIL Processes. The URL for this website is http://h20230.www2.hp.com/sc/solutions/index.jsp.
HP Project and Portfolio Management Center (9.30) Page 2 of 541

Contents
Chapter 1: Administering Project and Portfolio Management Center 15
Related Documents 16
Accessing PPM Center Documentation 17
Chapter 2: System Overview 19

Overview of PPM Center Architecture 19
Client Tier 20
Application Server Tier 21
Database Tier 22
System Configurations 23
Server Cluster Configurations (Recommended) 24
Server Cluster/External Web Server Configuration 26
Server Cluster Hardware Load Balancer Configuration 28
Services Isolation 30
Single-Server Configurations 31
Single-Server/Single-Machine Configuration 31
Single-Server/Multiple-Machine Configuration 32
Single-Server/External Web Server Configuration 33
Chapter 3: Installing PPM Center 36

Key Considerations 36
Installing for the First Time 36
Installing PPM Center Application Lifecycle Management Bundle 38
Plug-in for PPM 38
Installing Object Migrator or GL Migrator 38
Installing an Deployment Management Extension 39
Obtaining License Key Files 39
Checking System Requirements 39
Key Decisions 39
About PPM Center Best Practices Installation 41

Best Practices Content 41

Requirements for Installing Best Practices 41

Language Support for Best Practices 45
Preparing to Install PPM Center 46

Obtaining PPM Center Software 48
Software Update Manager 49
Collecting Required Information 49
Unzipping the Installation Files 53
Installing the Java Development Kit (JDK) 53
(Optional) Configure JDK to Use the Unlimited Strength Java Cryptography Jars 54
Verifying that the JAVA_HOME Environment Variable Is Set 55
Creating a System Account for PPM Center 57
Installing a UNIX Emulator (Windows) 58
Creating the Database Schemas 58
Default Permissions for PPM Center Schemas 60
Other Permissions Needed or Not Needed for PPM Center Schemas Accounts 61
Creating a Shared Folder for the server.conf File 63
Verifying Port Availability 65
Installing PPM Center 67

Installing PPM Center on a Windows System 67
Installing PPM Center on UNIX Systems 76
Configuring the FTP Server on Windows 77
Contacting Support 78
Downloading and Installing Service Packs 79

Contacting Support 81
Protecting Backed-Up Data 81
Handling Backup Files Related to Service Pack Installation 81
Uninstalling a Service Pack 82
Verifying PPM Center Installation 82
Optional Installations 83
Installing HP Project and Portfolio Management Best Practices 83
Installing Deployment Management Extensions 84
What to Do Next 85
Chapter 4: Configuring the System 86

(UNIX only) Setting the ulimit Value 86
Starting and Stopping the PPM Server 87

Setting the Server Mode 87
Starting and Stopping the PPM Server on Windows 89
Starting and Stopping the PPM Server on UNIX 90
Startup Checks 91
Installing Autopass Licenses for PPM Center Product 93

Overview of the Autopass Licensing Solution 93
Activating and Generating Autopass License 96
Installing Autopass License Key File Using the kLicenseInstall Tool 97
Installing Autopass Licenses and Viewing License Summary in Administration Console 97
Installing An Autopass License in a Clustered Environment 98
Reading Licenses Information Using kLicenseReader 98
Configuring or Reconfiguring the PPM Server 99

Standard Configuration 99
Defining Custom and Special Parameters 100
Enabling Secure RMI (Optional) 102
Configuring Private Key Authentication with Secure Shell 103
Configuring Secure Web Logon (Optional) 107
Importing a SSL Certificate from a Certificate Authority to Tomcat 109
Additional Considerations for Configuring Secure Web Logon 113
Generating Password Security (Optional) 114
Configuring Solaris and Linux Environments to Use Deployment Management 115
Enabling Export to PDF 116

Installing Unicode Fonts for Export to PDF 117
Enabling IPv6 118
Verifying Client Access to the PPM Server 119
Accessing the JMX Console 119
Configuring or Reconfiguring the Database 120

Database Parameters 120
Granting Select Privileges to v_$session 130
Generating Database Links (Oracle Object Migration) 130
Configuring the PPM Workbench to Run as a Java Applet 131

(Optional) Enabling SOCKS Proxy 131

Running the PPM Workbench with Secure RMI (Optional) 132
Using the PPM Workbench: What Users Need to Know 133

Installing and Configuring the Java Plug-In on Client Machines 133
Setting the Default Web Browser 134
Starting the PPM Workbench on a Client Machine 134
Troubleshooting Default JVM Problems on Client Machines 135
What to Do Next 136
Chapter 5: Advanced System Configuration 137

Configuring an External Web Server 137
(Windows) Using an External Web Server for Multiple Stand-Alone Instances of PPM Center137
Overview of External Web Server Configuration 138
Choosing an External Web Port 138
Configuring the Workers Properties File 139
Configuring the workers.properties File for a Single Server 139
Configuring the uriworkermap.properties File on Microsoft IIS and Apache-Based
Servers 142
Configuring PPM Center-Supported External Web Servers 143
Configuring the Sun Java System Web Server 143
Configuring the Microsoft Internet Information Services 7.0 Web Server on a Windows
Server 2008 System 145
Server 2008 System 152
Server 2012 R2 System 157
Configuring an Apache-Based Web Server 164
Compile a Binary JK Module 164
Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_jk (IPv4 Only) 165
Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy 167
Configure IBM HTTP Server Versions 6.1 and 7.0 170
(Optional) Generate Redirect URL Based On Server Configuration Parameter BASE_
URL 171
Enabling Secure Sockets Layer on an External Web Server 172
Enabling Dynamic Compression On an External Web Server 173
Creating an SSH Tunnel for External RMI Server (Optional) 175
Integrating an External Web Server with a PPM Server 176

Configuring a Server Cluster 179

Overview of Server Clustering 179
Synchronizing Clocks on Machines Participating in the Server Cluster 181
Server Parameters Required for Server Clustering 182
Creating a Shared Folder for the server.conf File 186
Preparing a Shared Folder for server.conf on a Windows System 187
Preparing a Shared Folder for server.conf on a UNIX System 187
High-Level Steps for Server Cluster Configuration 188
External Web Server, Single Machine 189
External Web Server, Multiple Machines 190
Hardware Load Balancer, Multiple Machines 193
Sample Port Sets 194
Starting and Stopping Servers in a Cluster 194
Verifying Successful Cluster Configuration 195
Detecting Multicast Routing and Configuration Issues for a Server Cluster 198
Multicast in PPM Center Cluster Environment 199
Switching Between Stand-Alone and Server Cluster Configurations 201

Switching from Server Cluster to Stand-Alone Configuration 202
Switching from Stand-Alone to a Server Cluster Configuration 202
Chapter 6: Implementing User Authentication 203

Overview of Implementing User Authentication 203
Integrating with an LDAP Server 204

Integrating PPM Center with an LDAP Server 204
Support for Multi-Domain LDAP Import 208
Authenticating Against Multiple LDAP Domains 209
Validating LDAP Parameters 210
Implementing Web Remote Single Sign-On with PPM Center 210

Requirements for Implementing Web Remote Single Sign-On 211
Setting Up Web Remote Single Sign-On with PPM Center 211
Implementing Generic Single Sign-On with PPM Center 213

Requirements for Implementing Generic Single Sign-On 213
Setting Up Generic Single Sign-On with PPM Center 213
Troubleshooting Your Single Sign-On Implementation 214
Implementing Lightweight Single Sign-On Authentication (LW-SSO) 216

Configuration Requirements for LW-SSO Support 216

LW-SSO Security Warnings 217
LW-SSO Known Issues 218
LW-SSO Limitations 219
Configuring PPM Center for LW-SSO 221
Integrating PPM Center with CA SiteMinder 222

Mixed Mode 222
Single Sign-on Mode 224
Requirements for Integrating with SiteMinder 226
Overview of Integrating PPM Center with SiteMinder 226
Configuring PPM Center for Integration with SiteMinder 226
Configuring PPM Center Users 229
Configuring SiteMinder for Integration with PPM Center 230
Applying FIPS 140-2 Compliant Encryption Algorithm for PPM Center 232
Chapter 7: Improving System Performance 237

Identifying Performance Problems 237
Isolating Performance Problems 237
Troubleshooting Performance Problems 241
Improving System Performance 242

Minimizing the Performance Impact of Running Background Services 243
Tuning Java Virtual Machine (JVM) Performance 245
Tuning Server Cluster Performance 246
Improving Input/Output Throughput 246
Improving Advanced Searches 247
Adjusting Server Configuration Parameters 248
Cleanup Parameters 249
Debug Parameters 249
High-Level Debug Parameters 249
Low-Level Debug Parameters 250
Timeout Parameters 250
Scheduler/Services/Thread Parameters 251
Database Connection Parameters 252
Logging Parameters 252
Cleanup Services 253

Monitoring Activity in PPM Center 253

Action Monitor 253
Portlet Monitor 255
Server Performance Reports 256
Background Services Monitor 260
Viewing the Services Audit Results Page 261
Accessing Application Exception Details 264
Identifying Database Connection Issues 266
Using the Watchdog Tool 267

Generating the GC Log 269
Running Watchdog 269
Chapter 8: Maintaining the System 272

Administration Tools in the Standard Interface 273
Viewing Server Running Server Reports, Requests, and Packages 273
Viewing Running Executions 273
Viewing Interrupted Server Reports, Requests, and Package Executions 274
PPM Center Background Services 274
Tools in the Administration Console 281

Opening the Administration Console 283
Viewing PPM Server Status from the Administration Console 284
Installing Autopass License Key File and Viewing License Summary in Administration
Console 286
Working with Fiscal Periods from the Administration Console 288
Generating Fiscal Periods from the Administration Console 288
Using the Administration Console to Shift Existing Fiscal Periods 290
Using the Administration Console to Import Fiscal Periods 291
Using the Administration Console to Export Fiscal Periods 292
Using the Administration Console to Generate Translations for Fiscal Periods 294
Viewing and Modifying Server Configuration Parameters from the Administration Console 295
Viewing Parameters from the Administration Console 296
Modifying Parameters from the Administration Console 297
Configuring and Migrating the PPM Center Document Management System from the
Administration Console 300
Browsing and Downloading <PPM_Home> Directory Files from the Administration Console 304
Running SQL Queries from the Administration Console 307

Creating a Dashboard Datasource (and List Portlet) from a SQL SELECT Statement in the
Administration Console SQL Runner 309
Gathering Information for HP Software Support from the Administration Console 312
Changing Data Display in Administration Console Tables 319
Using the Unchecking Showing Total Number Tool from Administration Console 321
Installing Autopass License Key File and Viewing License Summary in Administration
Console 322
Server Tools In the PPM Workbench 325

Access Grants Required to Use Server Tools 325
Accessing the PPM Workbench Server Tools 326
Running Server Reports from the Admin Tools Window 327
Running SQL Statements from the PPM Workbench 331
Running an SQL Script with SQL*Plus on a Windows System 333
Setting Debugging and Tracing Parameters 333
SQL Debugging for All Product Areas 337
System Logging in PPM Center 338

Context Option Logging Parameter 339
Redirecting Log File Output 339
Class Filters Logging Parameter 339
Log Levels for the install.sh Script 340
Enabling Debugging On a Per-User Basis 340
Tracing PPM Center Pages with the SQL Tracer Tool 342
(Optional) Enabling Debugging Console on Customized Logo 346
Logging of Physical Memory and Operating System Swap File Space at Server Startup 347
Maintaining Log Files 347

Mail Notification for Specified Server Logs 349
Periodically Stopping and Restarting the Server 354
Maintaining the Database 354

Changing PPM Center Data 355
Changing the Database Schema Passwords 355
Maintaining Temporary Tables 356
Purging Stale PPM Center Database Data 357
Overview of the PPM Purge Tool 357
Prerequisites for Running the PPM Purge Tool 358
Purge Stale Data Using the PPM Purge Tool 359

Restrict Remote Access to the PPM Purge Tool to Specified IP Addresses 372
Backing Up PPM Center Instances 372

Protecting Backups 373
Checking PPM Center License Status 373
Compiling JSP Files at Runtime 374
Chapter 9: Migrating Instances 375

Overview of Instance Migration 375
Copying an Instance to Create a New Instance 375
Running the Installation Script Twice to Create Two Instances 376
Migrating Document Management (Optional) 376
Preparing to Migrate 376

Obtaining a New License Key 377
Stopping the PPM Server 377
Migrating the PPM Server 378

Migrating to a Windows Machine 378
Migrating to a UNIX Machine 380
Migrating the Database Schemas 382
Troubleshooting Instance Migrations 386

PPM Server Does Not Start 386
Server Starts, but You Cannot Access Applications 387
Chapter 10: Migrating Entities 388

About Entity Migration 388
Migration Order 389
Overview of Entity Migration 390

Example Migration: Extracting a Request Type 391
Defining Entity Migrators 395

Migrator Action List 395
Basic Parameters 396
Import Flags 397
Password Fields 399
Internationalization List 400
Environment Considerations 402

Setting Stream Encoding for an Environment 402

Environment Connection Protocol 402
Environment Transfer Protocol 403
Setting the SERVER_ENV_NAME Parameter 403
Security Considerations 403

Migration and Ownership 403
Migrations and Entity Restrictions 404
Entity Migrators 404

Data Source Migrator 404
Module Migrator 405
Object Type Migrator 406
Portlet Definition Migrator 408
Project Type Migrator 408
Report Type Migrator 410
Request Header Type Migrator 411
Request Type Migrator 412
Special Command Migrator 414
User Data Context Migrator 415
Validation Migrator 416
Workflow Migrator 418
Work Plan Template Migrator 421
Appendix A: PPM Center Configuration Parameters 422

Overview of Configuration Parameters 422
Determining the Correct Parameter Settings 422
Required Parameters 423
Directory Path Names 423
Server Configuration Parameters 423

Using the Server Configuration Utility to Modify Server Configuration Parameters 424
Server Configuration Parameters Related to the PPM Dashboard 498
Logging Parameters 502
LDAP Attribute Parameters 510
Appendix B: Server Directory Structure and Server Tools 513

ppm930/system 513

<PPM_Home>/bin 514
kBuildStats.sh 514
kCalculateHealth.sh 514
kCancelStop.sh 514
kChangeNameDisplay.sh 514
kCharConverter.sh 515
kConfig.sh 516
kConfigCheck.sh 516
kConvertProject.sh 517
kConvertToLog4j.sh 517
kConvertUserPasswords.sh 518
kDeploy.sh 518
Deploying Hotfixes with kDeploy.sh 520
kDevMigratorExtract.sh 522
kDevMigratorImport.sh 523
kEnableTimeMgmtPeriodType.sh 523
kEncrypt.sh 523
kExportAttributes.sh 524
kGenFiscalPeriods.sh 524
kGenTimeMgmtPeriods.sh 525
kHash.sh 525
kImportAttributes.sh 526
kJSPCompiler.sh 526
kKeygen.sh 526
kLdap.sh 526
kLicenseReader.sh 527
kLicenseInstall.sh 527
kMigratorExtract.sh 528
kMigratorImport.sh 529
kPMTMSync.sh 531
kRunCacheManager.sh 531
kRunServerAdminReport.sh 532
kStart.sh 532
kStatus.sh 532
kStop.sh 533
kSupport.sh 533

Running SQL Scripts with kSupport.sh 534

Listing Invalid Database Schema Objects and Database Indexes 534
Bill of Materials Information 535
Running Mode for kSupport.sh 535
kTestSiteMinder.sh 536
kTMDataConversion.sh 536
kUpdateHtml.sh 537
kVariables.sh 537
kWall.sh 537
setServerMode.sh 537
<PPM_Home>/pdf 538
<PPM_Home>/integration 538
<PPM_Home>/logs 539
<PPM_Home>/reports 539
<PPM_Home>/server 539
<PPM_Home>/sql 539
<PPM_Home>/transfers 540
<PPM_Home>/utilities 540
kWatchdog.sh 540
Other Directories 540
Send Documentation Feedback 541

Chapter 1: Administering Project and Portfolio
Management Center
This document provides information about how to install, configure, and maintain the Project and
Portfolio Management Center (PPM Center) system. If you are not installing PPM Center for the first
time, but need instructions on how to upgrade from an earlier version, see the
The chapters in this document provide the following information about PPM Center and how to
administer the system:
l Overview of PPM Center system architecture and of single-server and server cluster system
configuration ("System Overview" on page 19)
l Information about product licensing and optional programs that you can install ("Installing PPM
Center" on page 36)
l Instructions on how to create the required database schemas, verify installation, and install service
packs and Deployment Management Extensions ("Installing PPM Center" on page 36)
l Details on how to configure all components of the PPM Center system and to start and stop the
PPM Server ("Configuring the System" on page 86)
l Information that PPM Center users need to know in order to use the PPM Workbench ("Configuring
the System" on page 86)
l Advanced configuration information, including details on how to configure an external Web server
and PPM Server clusters ("Advanced System Configuration" on page 137)
l Information on how to integrate PPM Center with an LDAP server ("Advanced System Configuration"
on page 137)
l Information about the kinds of performance issues that can arise, and how to identify and resolve
them ("Improving System Performance" on page 237)
l Information on how to migrate entire instances of PPM Center, and on how to migrate just the
database schemas ("Migrating Instances" on page 375)
l Details on how to maintain the PPM Center and the database after installation and configuration
("Maintaining the System" on page 272)

Chapter 1: Administering Project and Portfolio Management Center
l Details on how to use the HP entity migrators to migrate specific kinds of PPM Center entities and
associated objects between instances of PPM Center ("Migrating Entities" on page 388)
l PPM Server configuration parameters ("PPM Center Configuration Parameters" on page 422)
l Details about PPM Center directories and the scripts and tools they contain ("Server Directory
Structure and Server Tools" on page 513)
This document is written for users who are moderately knowledgeable about enterprise application
development and skilled in enterprise system and database administration. It is written for:
l Application developers and configurators
l System and instance administrators
l Database administrators (DBAs)
Related Documents
The following documents provide installation information for system administrators and DBAs:
l
Before you install PPM Center, check this document to make sure that your operating environment
meets of the minimum system requirements.
l
The document provides product information that is not included in the regular
documentation set.
l
Refer to this document for information on how to create and maintain your own PPM Dashboard
pages, modules, and portlets for display in the standard interface.
l
If your organization has offices in different countries, see this guide for information on how to set
up the Multilingual User Interface (MLU) in PPM Center.
l Upgrade Guide

If you plan to upgrade from an earlier version of PPM Center, see this guide for information on
supported upgrade paths, what to do to prepare to upgrade, and how to perform and then verify the
upgrade.
Additional documents that you might find useful as you configure or maintain PPM Center include:
l
l
l Open Interface Guide and Reference
l
l
l
l
l
l (includes descriptions of all portlets, request types, and workflows in PPM

Center)
Accessing PPM Center Documentation

To access the online help system of the PPM Center documentation, from the PPM Center menu bar,
select Help > Help Center.
The PDF version of PPM Center documentation are also included with the product. This enables end
users to access the PDF version of PPM Center documentation easily, especially for users who have no
access to the HP Manuals Site. To access PDF version of PPM Center documentation included with the
product, from the Help menu, click Help Center, then in the Getting started section, click Navigate PPM
Center Documentation. Locate a document of your interest and click the PDF link for the document.
Note: Most of documents in the PPM Center documentation set are available in both online help
and PDF format. Only some less used documents are still available in PDF format only.

Tip: For PPM Center administrators who would like to access all PDF files, go to the
directory.

Chapter 2: System Overview
This chapter provides an overview of PPM Center architecture.
Overview of PPM Center Architecture

PPM Center is based on a three-tier architecture that consists of:
l Client browsers ("Client Tier" on the next page)
l One or more middle-tier J2EE servers ("Application Server Tier" on page 21)
l A single Oracle relational database ("Database Tier" on page 22)
This arrangement is shown in the following figure.

PPM Center architecture
Browser clients use HTTP or HTTPS (HTTPS requires an external Web server) to communicate with the
PPM Center Web and application servers. PPM Workbench clients (Java™ applet) use Remote Method
Invocation (RMI). The following sections provide information about each tier.
Client Tier
The client tier of the system consists of:
l The PPM Center standard interface. The standard interface is rendered using Java Server Pages
(JSP) and is accessed using a web browser.

l The PPM Workbench interface is displayed using a Java applet installed on the client machine, and is
started using the Oracle Java plug-in to a web browser.
l The Administration Console. The Administration Console is embedded in the PPM Center standard
interface.
The client and application server tiers communicate as follows:
l For the standard interface, the client and application server communicate using HTTP or HTTPS, with
no code required on client machines. The client accesses information from the database through
the J2EE application server using a shared database session pool.
Note: To use HTTPS, you must also use an external Web server.
l For the PPM Workbench interface, the client and application server communicate using Remote
Method Invocation (RMI) or Secure Remote Method Invocation (SRMI), which is optimized for use in
PPM Center.
The architecture and communication protocols are created to minimize the number of round trips
between the applet and server, and the volume of data transferred.
For more information about the PPM Center standard and PPM Workbench interfaces, see the
guide.
Application Server Tier

The application server (PPM Server):
l Runs on the Microsoft® Windows®, Oracle Solaris, HP-UX, IBM AIX, Red Hat Linux, and SUSE Linux
platforms
l Uses the Tomcat Application Server
l Houses workflow, scheduling, notification, and execution engines that drive automated tasks such
as running scheduled reports and email notifications
l Can run on multiple machines as a cluster to improve performance and scale hardware as usage
increases

l Can run with external Web servers such as Oracle Java System Web Server, Microsoft IIS, Apache
HTTP Server, Apache-based Web Server (from HP), and IBM HTTP Server
Note: For detailed information on which Web server versions PPM Center supports, and on
which platforms, see the
l Maintains a database connection pool that caches connections to the database
l Eliminates the need to restart the PPM Server if the database shuts down for scheduled
maintenance or because of system failure
The application server and the PPM Web server communicate using Apache JServ Protocol version 1.3,
or AJP13. The AJP13 protocol is similar to HTTP that has been optimized for performance. The
application server and database tiers communicate using Java Database Connectivity (JDBC).
For more information about configuring an external Web server, see "Configuring an External Web
Server" on page 137.
Database Tier
The database tier consists of an Oracle database that contains the tables, procedures, PL/SQL
packages, and other components that the PPM Center products use. All transaction, setup, and auditing
data are stored in the database. PPM Center can run on a single database instance, or it can leverage
Oracle RAC (Real Application Cluster) configuration for load balancing and redundancy.
Note: The database consists of the following two database schemas:
l The central schema contains the core PPM Center data model and PL/SQL package code. The
core data model contains all PPM Center configuration and transaction data.
l The Reporting Meta Layer (RML) schema contains a set of database views to facilitate reporting
on PPM Center data.
Note: Running PPM Center on Oracle RAC is supported. However, the Oracle RAC failover feature is
not available due to that PPM Center uses Oracle Thin JDBC Driver.
PPM Center supports the following Oracle database features:

l A relational data model
l Use of Oracle stored procedures to implement business logic (for example, workflow processing)
l Use of a database connection pool to eliminate the need to create a separate database session for
each user or transaction
l Database caching of frequently-used data, programs, and procedures to improve performance
l A database schema (separate from the PPM Center database schema) for implementing operation
reporting in PPM Center
System Configurations
The three-tier architecture of PPM Center supports a variety of system configurations. You can deploy
PPM Servers in a single-server, stand-alone configuration or a server cluster configuration.
In a production environment, you must deploy a server cluster. A stand-alone configuration is adequate
only in a development or testing environment. The following sections provide information about the
possible ways you can configure your PPM Center instance.

Server cluster/external Web server configuration
The Web server (internal or external) listens for HTTP or HTTPS requests from standard interface
clients. Nodes run in the background and are transparent to users. Users access only the URL to the
Web server.
The Web server forwards HTTP or HTTPS requests to one of the nodes. The PPM Web server and the
nodes communicate using Apache JServ Protocol version 1.3 (AJP13).
The nodes also accept RMI or SRMI connections from PPM Workbench users who run applets in browsers
to directly connect to the PPM Server using this protocol. The PPM Server uses JDBC to communicate
with the Oracle database.
Server Cluster Configurations (Recommended)

PPM Servers are deployed in a server cluster configuration. Clustering enables you to run PPM Center on
several parallel servers, or Server cluster configurations improve performance on systems that
handle high transaction volumes or large numbers of concurrent users. In addition to handling higher

user loads and providing greater scalability, the server cluster configuration supports load balancing
and server failover features.
Because clustering distributes work load across different nodes, if any node fails, PPM Center is still
accessible through other nodes in the cluster. You can continue to improve system performance by
simply adding nodes to the cluster.
To leverage the clustering capabilities within PPM Center to support either background service isolation
or the load-balanced user traffic across multiple nodes, you must configure the instance (collection of
nodes) as a formal cluster.
Caution: To avoid problems with memory and performance, HP strongly recommends that you
isolate background services from user traffic. For more information, see "Services Isolation" on
page 30.
In a server cluster configuration, you can enable multiple nodes to run background services.
In a clustered environment with Java Message Service (JMS) and Quartz clustered scheduling, you can
configure the following:
l Clustered nodes run across multiple machines
l JMS monitoring
l Number of consumers (listeners) per node for each queue
l Service failure rules per queue (that is, number of retries, log failures, server shut-downs)
l Notification messages to be sent to each queue
l Specific number of threads per node and cluster information for the scheduler
l Scheduler time zone. (This may be required if the database and PPM Servers are located in different
geographies.)
To handle large numbers of concurrent users, server cluster configurations use either an external Web
server or a hardware-based load balancer to distribute user connections evenly across multiple nodes.
If more than one node in a cluster is dedicated to running services, and one of these services nodes
shuts down, activities such as email notifications and executions scheduled to run on that node are
automatically transferred to another available services node. This server failover feature helps ensure
that PPM Center system services remain operational.

Note: Any unsaved changes on a node that shuts down are lost and are not transferred to an
available node. Users who log on to PPM Center after a node shuts down see only changes that
were saved on that node.
A PPM Center server cluster contains one or more nodes and an Oracle database. The first node
installed and configured is the . The other server (assuming a two-server setup) is the
. The two servers can act as peers in a load-balancing situation, or one can act as a
backup machine for the other.
Note: A server cluster configuration can include Oracle RAC. If a database in a setup such as this
goes down, the Oracle JDBC driver manages database connectivity.
You can implement server cluster configurations on a single machine or on multiple machines. To run
multiple PPM Servers on a single machine, the machine's memory capacity and CPU usage must meet
the same memory and CPU requirements for multiple servers. To run multiple servers on multiple
machines, the servers must share a common file system for reports, execution logs, attachment files,
and server configuration files. Although each machine can contain its own instance of the PPM Center
application code, only a single copy is required for each machine, regardless of the number of servers
running on that machine.
You can set up server clusters with an external Web server, or with a hardware load balancer. The
following sections describe these two setups.
Server Cluster/External Web Server Configuration

The server cluster/external Web server configuration distributes client connections evenly among any
number of nodes, based on Web traffic and server load. This configuration is typically used for
organizations that need to load-balance Web traffic across multiple nodes (as an alternative to
hardware-based load balancing). It can also be useful to an organization that already uses a standard
Web server within its network infrastructure.
You can usually improve user load, transaction capacity, and system performance with this
configuration. The extent of improvement depends on the number of nodes in the cluster and their
available resources. This configuration supports load balancing and server failover features.

Server cluster/external Web server configuration
The Web server (internal or external) listens for HTTP or HTTPS requests from standard interface
clients. Nodes run in the background and are transparent to users. Users access only the URL to the
Web server.
The Web server forwards HTTP or HTTPS requests to one of the nodes. The PPM Web server and the
nodes communicate using Apache JServ Protocol version 1.3 (AJP13).
The nodes also accept RMI or SRMI connections from PPM Workbench users who run applets in browsers
to directly connect to the PPM Server using this protocol. The PPM Server uses JDBC to communicate
with the Oracle database.
The nodes also accept TCP/UDP connections from other nodes for cache synchronization and cluster
moniter.
Software Load Balancing
You can use the PPM Center Web server module as the software load balancer for a PPM Server cluster
configuration. For this configuration, HP recommends that PPM Center nodes in the cluster accept

HTTP requests that are not routed through the Web server.
The request sequence is as follows:
1. A user submits an HTTP request to the Web server.
2. The Web server forwards the request to the HP PPM Web server module.
3. The HP PPM Web server module sends the request to a PPM Server.
Integrating with a Single Sign-On Product
For instructions on how to implement single sign-on with PPM Center, see "Implementing User
Authentication" on page 203.
Using SSL Accelerators
For PPM Server cluster configurations running HTTPS, you must integrate an external Web server that
supports the appropriate accelerator to leverage a hardware-based SSL accelerator.
The external Web server and PPM Servers communicate using AJP13, a proprietary protocol that can be
more efficient than HTTP for communicating with PPM Servers using an external Web server. For
information about how to set up a server cluster with an external Web server, see "Advanced System
Configuration" on page 137.
Server Cluster Hardware Load Balancer Configuration

The server cluster/hardware load balancer configuration is similar to the server cluster/external Web
server configuration. However, in place of an external Web server, a hardware load balancer is used to
balance client HTTP sessions across nodes. This configuration ensures the even distribution of client
connections among nodes based on server load and availability.
Note: HP strongly advises to use cookie-based session persistence for load balancers. IP-based
session persistence is known to result in issues when proxies or VPN are used by end users, and
should be discouraged.
Figure. Server cluster/hardware load balancer configuration

In the server cluster/hardware load balancer configuration:
l Standard interface clients communicate with nodes using HTTP (or, for secure communication,
HTTPS) through the use of a hardware load balancer. The hardware load balancer listens for the
HTTP or HTTPS requests that it distributes.
Many hardware load balancers support handling HTTPS and forwarding plain HTTP. If you use
hardware load balancer to forward HTTPS to PPM Server, you must also have an external Web
server. In this case, the hardware load balancer handles the encryption and decryption of requests,
and the nodes perform other tasks. Setting up your system this way can improve its performance.
l PPM Workbench interface clients communicate directly with the PPM Server using RMI or, for secure
communication, SRMI.
l The PPM Server and Oracle database reside on separate machines and communicate with each
other using JDBC.

Note: Although the above figure shows multiple nodes and just a single database, the system
can support Oracle RAC or a single database mirrored for redundancy across multiple machines.
Using this configuration improves user load distribution, transaction capacity, and system performance.
The degree of improvement depends on the number of nodes in the cluster and the resources available
to each. Load balancing and server failover features are supported in this configuration.
For information about how to set up a server cluster/hardware load balancer configuration, see
"Advanced System Configuration" on page 137.
Services Isolation
PPM Center has many asynchronous background services that process data "behind the scenes" while
the application is running. Depending on data characteristics of your PPM Center deployment, the
overhead of these services in terms of CPU and memory demand are difficult to estimate. To reduce
the impact of services on user response times, HP strongly recommends that you isolate the services on
a separate JVM within the PPM Center server cluster.
Services isolation does not require isolation of services onto separate physical servers. A node that you
dedicate to services can reside on the same machine that hosts nodes handling user traffic. Even in a
shared host model, there is benefit if higher performance-risk services, which tend to be CPU-bound on
the application tier, have a separate node.
PPM Center server clustering does not differentiate between primary or backup nodes in terms of
configuration. The first node to start up attempts to be the "service primary". If a node that is
considered to be a "backup" starts first, then it is the primary. The objective is to earmark a subset of
nodes in the server cluster as services-capable. All of the nodes are peers, and "ownership" of services
is based simply on startup order.
Note: If a node that is running services fails, one of the other nodes enabled to run services
assumes the role of primary. If the node that failed is restarted, services will not automatically
"failback" to that node. To return services ownership to the node that failed and is restarted, you
must stop, and then restart the node that took over services execution from the original services
node.
HP recommends that you devote at least one PPM Center node to process PPM Center background
services.
Dedicating one PPM Center node to your services enables you to:

l Minimize the effect that running PPM Center services has on users
l Better monitor the performance of the services
The more you monitor and understand how your services affect performance, the better you can tune
them.
Single-Server Configurations
PPM Center test and development instances are typically single-server configurations that consist of
one PPM Server and one Oracle database. The single PPM Server handles the entire user load and
functions as the Web server. It also houses the file system for the program code, reports, execution
logs, and attachments files. The Oracle database stores all other data.
You can set up the following types of single-server configurations:
l "Single-Server/Single-Machine Configuration" below
l "Single-Server/Multiple-Machine Configuration" on the next page
l "Single-Server/External Web Server Configuration" on page 33
When you install PPM Center; (see "Installing PPM Center" on page 36), you specify whether you want a
server cluster configuration (required for a production instance) or a configuration. A
stand-alone PPM Center deployment always includes just one PPM Server installation with a single-node
configuration.
You can configure a server cluster that has just one node. The difference is that you can add nodes to
the "server cluster" while you cannot add nodes to a stand-alone instance.
Note: In a production environment, you must deploy a server cluster. A stand-alone configuration is
adequate only in a development or testing environment.
Single-Server/Single-Machine Configuration
The single-server/single-machine configuration shown in the following figure consists of one machine
that hosts both the PPM Server and the Oracle database.
Note: HP strongly recommends that you use the single-server/single-machine configuration only
for a stand-alone PPM Center deployment in either a testing or development environment, and

never for a production instance.
Single-server/single-machine configuration
Standard interface clients communicate with the PPM Server using HTTP, or, for secure communication,
HTTPS (requires that you use an external Web server). PPM Workbench interface clients communicate
with the PPM Server using RMI, or, for secure communication, SRMI.
The machine that houses the PPM Server also contains the Oracle database. The PPM Server uses JDBC
to communicate with the Oracle database.
An organization typically uses this configuration if it requires a dedicated machine for all PPM Center
services and database operations. User load, transaction capacity, and system performance depend on
the available resources on a machine. This configuration does not support load balancing or server
failover features.
For information about how to set up a single-server/single-machine configuration, see "Installing PPM
Center" on page 36.
Single-Server/Multiple-Machine Configuration
In the single-server/multiple-machine configuration shown in the following figure, the PPM Server and
the Oracle database reside on separate machines. This configuration offers additional performance
capacity and modularizes the maintenance of the application server and database tiers. The separate
machines can run on different operating systems, thereby enabling greater flexibility.

Configuration with a single server and multiple machines
Standard interface clients communicate with the PPM Server using HTTP, or HTTPS for secure
communication. (To use HTTPS, you must use an external Web server.) PPM Workbench interface clients
communicate with the PPM Server using RMI, or SRMI for secure communication. The PPM Server and
Oracle database use JDBC to communicate.
An organization typically uses the single-server/multiple-machine configuration if it requires a separate

machine for database operations. User load, transaction capacity, and system performance depend on
the resources available on the PPM Server machine. This configuration does not support load balancing
or server failover features.
For information about how to set up a single-server/multiple-machine configuration, see "Installing PPM
Center" on page 36.
Single-Server/External Web Server Configuration

In the single-server/external Web server configuration shown in the following figure, Web traffic comes
into the Web server and is then passed to PPM Center. The external Web server and the PPM Server
communicate using AJP13, a proprietary protocol that is more efficient for this configuration type than
HTTP or HTTPS.

Single-server/external Web server configuration
l Standard interface clients communicate with an external Web server using HTTP, or, for secure
communication, HTTPS. The external Web server and PPM Servers use AJP13 to communicate.
l PPM Workbench interface clients communicate directly with the PPM Server using RMI, or, for secure
communication, SRMI.
l The PPM Server and Oracle database server reside on separate machines. The PPM Server
communicates with the Oracle database using JDBC.
This configuration is suitable if your organization:
l Already uses a standard Web server within the network infrastructure.
l Must prevent clients from having direct access to the PPM Server.
IT departments often have standards for the Web server used for HTTP traffic. Running the HTTP
listener allows for PPM Center integration with enterprise-specific architecture.
System administrators typically prefer HTTP traffic configured on port 80. On UNIX® systems, processes
must run as root to listen on a port number lower than 1024. However, HP recommends that you not run
the PPM Server as root. If you want to configure HTTP traffic on a port number less than 1024, consider
integrating with an external Web server.
As with other single-server configurations, user load, transaction capacity, and system performance
depend on available resources on the PPM Server machine. This configuration does not support load
balancing and server failover features.
Note: HP recommends that you use the internal Web server built into the PPM Server unless you

have the kind of special Web server requirements described in this section.
For information about how to set up a single-server/external Web server configuration, see "Installing
PPM Center" on page 36 and "Advanced System Configuration" on page 137.
For a list of supported external Web servers, see the . For

information on how to access this and other PPM Center documents, see "Accessing PPM Center
Documentation" on page 17 .

Chapter 3: Installing PPM Center
This chapter contains the following topics:
l "Key Considerations" below
l "Key Decisions" on page 39
l "About PPM Center Best Practices Installation" on page 41
l "Preparing to Install PPM Center " on page 46
l "Installing PPM Center" on page 67
l "Configuring the FTP Server on Windows" on page 77
l "Contacting Support" on page 78
l "Downloading and Installing Service Packs" on page 79
l "Verifying PPM Center Installation" on page 82
l "Optional Installations" on page 83
l "What to Do Next" on page 85
Key Considerations
To prepare to install PPM Center, review the following topics:
Note: For information about how to upgrade to PPM Center version 9.30 from an earlier version,
see the
Installing for the First Time

To prepare to install PPM Center version 9.30:

1. Make sure that your organization has obtained the installation software.
2. Read the rest of this chapter.
3. Read the which is described in "Related

Documents" on page 16.
4. Read the which are described in "Related Documents" on page 16.
5. If you plan to install the PPM Center multilingual user interface, see the
6. To make sure that you have performed all required preinstallation tasks.
7. If you plan to install one of the Deployment Management Extensions, see the documentation for
the product.
Note: For information on how to access documentation for HP Migrators and Deployment
Management Extensions, see "Accessing PPM Center Documentation" on page 17.
8. Make sure that you have generated Autopass license files for all of the products you already
purchased and plan to install. For instructions, see "Activating and Generating Autopass License" on
page 96.
9. Install PPM Center. For instructions on how to install PPM Center, see "Installing PPM Center" on
page 67.
10. Configure the PPM Server and system environment.
For information about how to configure PPM Center, see "Configuring the System" on page 86 and
"Advanced System Configuration" on page 137.
11. Install and configure optional products you have purchased to work with PPM Center.
Note: After you install PPM Center, you can install Extensions, or the GL Migrator in any order
you choose. For information about how to install and configure optional products, see
"Optional Installations" on page 83.

Installing PPM Center Application Lifecycle Management

Bundle
The Application Lifecycle Management (ALM) bundle is included in PPM Center to facilitate integration of
PPM Center with other HP Software products. PPM Center ALM bundle provides entities such as request
types, workflows, portlets, reports, and special commands that you can install in PPM Center to support
Information Technology Infrastructure Library (ITIL) processes for change management and release
management.
ALM entities enhance PPM Center functionality, and facilitate PPM Center integration with HPService
Manager, HP Universal Configuration Management Database (Universal CMDB), HP Quality Center and HP
Application Lifecycle Management, and HP Release Control. For detailed information about ALM bundle
and how to install it, see the
Plug-in for PPM

If you plan to integrate Microsoft Project with Project Management by installing the Plug-in for PPM, be
aware of the following:
l The Plug-in for PPM is a Visual Studio Tool for Office (VSTO). Net Office add-in that adds a menu to
Microsoft Project. You can use the menu to synchronize Microsoft Project and Project Management
data. All communication with the PPM Server is done using HTTP requests to the PPM Server, and the
data is exchanged in XML format.
l Microsoft Project functionality is affected only while the currently opened project is integrated with
PPM Center (for example, while loading tasks, filling in actual effort, and so on).
For information about the requirements and instructions for installing the Plug-in for PPM, see the
Installing Object Migrator or GL Migrator

If you are running PPM Center in the Oracle environment, and plan to use Object Migrator or GL Migrator
software, you must consult not only the installation instructions in this document, but also the
instructions in the Object Migrator or GL Migrator documentation.
For information about the Object Migrator and the GL Migrator, see the and the
respectively.

Installing an Deployment Management Extension

If you purchased an Deployment Management Extension, be sure to consult not only the installation
instructions in this document, but also the instructions in the Deployment Management Extensions
documentation.
To complete an Extension installation successfully, you must make sure that you have the required
system privileges. For information about these privileges, and how to grant them, see "Key Decisions"
below.
Obtaining License Key Files

Make sure that you have purchased the HP products you intend to install (you can purchase and install
additional products later) and that you have Autopass license key file(s) for the purchased version.
Customers with valid entitlement order number can go to HP Licensing for Software portal at
http://www.hp.com/software/licensing by entering your Entitlement Order Number (EON) to activate
your license. For instructions, see "Activating and Generating Autopass License" on page 96.
Contact an HP regional licensing support center or your HP sales representative for assistance if
needed.
Checking System Requirements

Before you start to install PPM Center, make sure that your system environment meets all the
requirements. For information about the system requirements, see the
For information on how to access this and other PPM Center documents, see
"Accessing PPM Center Documentation" on page 17.
Key Decisions
This section addresses several decisions you must make before you begin to install your PPM Center
products.

Table 3-1. Decisions to make before you install
Decision What to Consider
When do I configure Before you can start the PPM Server, you must configure it. The installer
the PPM Server? prompts you for several server parameter values.
If you do configure during installation, the installer saves the values you
provide to the server configuration file, and you can complete server
configuration after installation, without having to reenter the values.
If the server information you provide (for example, valid port numbers) is
unavailable during installation, you must configure the PPM Server after you
install it. For instructions, see "Configuring or Reconfiguring the PPM Server"
on page 99.
When do I create the The PPM Server requires two database schemas to store application data.
database schemas? You can create these schemas before you install PPM Center, or you can
create them automatically during installation.
To create the schemas before installation, follow the instructions provided in

"Creating the Database Schemas" on page 58. If you set up the schemas
before installation, the installer populates them with the entities and data
required to run the PPM Server
When do I set up To improve PPM Center performance, the installer rebuilds statistics for the
grants to the Oracle optimizer during installation.
database schema?
You cannot successfully complete the installation until you grant privileges
and rebuild the statistics.
What privileges do I To rebuild the statistics, the PPM Center database schema user must be
grant the database granted the following privileges (as SYS DBA on Oracle):
schema user?
l
l
l
l
l
If you have access to SQL*Plus, you can run the script

(located in the
directory), which grants all required privileges for you. You can run the script
before installation (as SYS DBA) or during installation.
If you are logged on as SYS DBA, you can run the script after installation. In

Table 3-1. Decisions to make before you install, continued

Decision What to Consider
this case, the installer does not gather statistics or install Best Practices
content. For information about installing Best Practices content, see "About
PPM Center Best Practices Installation" below.
Do I run the install You can either install the PPM Server in graphic mode or in console mode.
program in graphic
mode or in console
mode?
About PPM Center Best Practices Installation

In addition to installing the foundation product, the database, and the application server (PPM Server),
you can install Best Practices on your system. Best Practices provides you with experience-derived
information and advice on how to configure and use Portfolio Management and Program Management.
Best Practices Content

Project Management and Portfolio Management access the request type content installed as part of
Best Practices. This includes HP-supplied menu items that access these request types. "Table 3-2. Best
Practices request types " on the next page lists the Best Practices request types and their associated
workflows, and provides descriptions of the product functionality they provide. "Table 3-3. Best
Practices workflows" on page 45 lists the functionality that Best Practices workflows content enabled in
this version of PPM Center.
Demand Management and Portfolio Management Best Practices content also includes scripts that
populate the Default Demand Set and Default Scoring criteria information.
Requirements for Installing Best Practices

You can install Best Practices if of the following conditions are met:
l PPM Center database schema name
l PPM Center database username and password

l PPM Center administrator username and password
l You have licenses for both the Portfolio Management and Program Management.
For detailed instructions on how to install Best Practices separately, see "Installing HP Project and
Portfolio Management Best Practices" on page 83.
The Best Practices content supplied with this version of PPM Center includes the request types and
workflows listed in "Table 3-2. Best Practices request types " below and "Table 3-3. Best Practices
workflows" on page 45.
Caution: In order for PPM Center software to function correctly, Best Practices request types must
be installed on your system and correctly associated with the menu items and project types.
Table 3-2. Best Practices request types
Request Type and Description Menu Selections Field Groups
PFM - Proposal l Create > Proposal PFM Proposal
Represents a project proposal l Open > Portfolio Management >

within the Portfolio Management Create Proposal
module.
PFM - Asset l Create > Asset PFM Asset
Represents the ongoing costs and l Open > Portfolio Management >
maintenance of the result of a Create Asset
project in the Portfolio
Management system.
PFM - Project l Create > Project PFM Project
Represents data and process l Open > Portfolio Management >

associated with project. This Create Project
request type is connected to a
project type.
Project Issue l Create > Project Issue l Project Reference
Represents issues associated with l Open > Project Management > l Project Issue
a project. Project Controls > Submit Project
Issue
l Search > Project Issues

Table 3-2. Best Practices request types , continued

l Open > Project Management >

Project Controls > Search Project
Issues
Also associated with a project type to

enable creating from within the
Project Overview page.
Project Risk l Create > Project Risk l Project Reference
Represents risks associated with a l Open > Project Management > l Project Risk
project. Project Controls > Submit Risk
l Search > Project Risks

Project Controls > Search Project
Risks

Project Scope Change Request l Create > Project Scope Change l Project Reference
Represents scope changes l Open > Project Management > l Project Scope
associated with a project. Project Controls > Submit Scope Change
Change
l Search > Project Scope Changes

Project Controls > Search Scope
Changes

Program Issue l Create > Program Issue l Program Issue
Represents issues associated with l Open > Program Management > l Program
a program. Issues > Submit Program Issues Reference

Table 3-2. Best Practices request types , continued

l Search > Program Issues
l Open > Program Management >

Issues > Search Program Issues
Program Risk l Search > Program Risks l Program

Reference
Represents risks associated with a l Create > Program Risk
program l Program Risk
Risks > Search Program Risks

Risks > Submit Program Risk
DEM - Application Enhancement l Create > Request l Demand

Management SLA
Used to request new functionality l Open > Demand Management > Fields
in IT current applications. Create Request
l Demand
l Search > Requests Scheduling Fields
l Open > Demand Management >

Search Requests
DEM - Database Refresh l Create > Request l Demand

Management SLA
Database refresh requests can be l Open > Demand Management > Fields
made for all IT Ops applications in Create Request
the testing phase. l Demand
Scheduling Fields
DEM - Application Bug l Create > Request l Demand

Management SLA
Used to report problems in IT l Open > Demand Management > Fields
applications. Create Request
l Demand
Scheduling Fields
DEM - Initiative l Create > Request l Demand

Management SLA
Used to request key projects for l Open > Demand Management > Fields
future quarters. Create Request
l Demand
Scheduling Fields

You can create your own versions of the Best Practices request types by adding the appropriate field
group, and then either editing the menu XML files or associating the request type with the project type
(for Project Issue, Project Risk, and Project Scope Change).
The following table lists the functionality that Best Practices workflows content enabled in this version
of PPM Center.
Table 3-3. Best Practices workflows
Best Practices Workflow Description
PFM - Proposal Portfolio Management process for requesting a new project.
PFM - Asset Portfolio Management process for an asset life cycle.
PFM - Project Portfolio Management process for a project life cycle.
DEM - Enhancement Demand Management process for enhancement requests for new
Request Process functionality in applications.
DEM - Database Refresh Demand Management process for database refresh requests.
DEM - Bug Request Demand Management process for application bug requests.
Workflow
DEM - Project Initiative Demand Management process for initiative requests for key projects.
Process
Program Risk Management Automated process for program risk management.

Process
Risk Management Process Automated process for project risk management.
Scope Change Request Automated scope change request process with three levels of severity.
Process
Issue Management Process Automated process for issue management.
Language Support for Best Practices

PPM Center Best Practices content is available for all supported language packs. HP recommends that
you deploy language packs soon after you install Best Practices so that the its content matches in all
languages.
Note: For detailed information about the language packs and how to install them, see the

Preparing to Install PPM Center

Before you start to install PPM Center, complete the following tasks:
1. Check the to make sure that your system meets

of the minimum requirements.
2. Make sure that you have at least 300 MB temporary space and 0.5 to 1 GB swap space on your
operating system.
Caution: Limits on physical memory for 32-bit Windows operating systems depend in part on
whether the Physical Address Extension (PAE) is enabled. The PAE allows some 32-bit Windows
systems (Windows Server 2008 Datacenter and Windows Server 2008 Enterprise) to use more
than 4 GB of physical memory. (To enable PAE, use the /PAE switch in the file.)
The total available physical RAM on this system is limited to 4 GB. For detailed information
about memory support and memory limitations on Windows operating systems, see Microsoft
Support online.
Note: Total and free physical memory and operating system swap file space are logged during
PPM Server startup. The exception to this is AIX systems, where this information is not
available.
3. Set several Oracle database parameters to the values recommended for the system environment
and optimum system performance. For details, see "Configuring or Reconfiguring the PPM Server"
on page 99.
4. Enable the Oracle Java Virtual Machine (OracleJVM).
PPM Center uses Java Stored Procedures in Oracle. Java Stored Procedures enable you to call Java
code from PL/SQL. To use this feature, you must enable the Oracle Java virtual machine
(OracleJVM). For information about how to install and configure the Oracle Java virtual machine
(JVM), see the for your Oracle software version.
Note: HP strongly recommends that you automate memory so that the size of the JAVA pool
(Oracle parameter setting) is allocated automatically.To automate memory

allocation for Oracle 11g databases, use Automatic Memory Management (AMM).
5. Collect the information required for installation.
For information about what information is required, see "Collecting Required Information" on
page 49.
6. Obtain the installation files, and save them to a temporary directory
The placeholder represents the root directory to which you save the installation
files. The name and location of this directory are up to you.
7. Install the JDK.
For information on which version of the JDK to install, see the

For information on how to install the JDK, see "Installing the Java
Development Kit (JDK)" on page 53.
8. Verify that the environment variable is set.
9. (Windows systems only) On each Windows server with which PPM Center is to interact, download
and install Cygwin. (For information about this UNIX emulator and how to install it, go to
cygwin.com.)
10. (Windows systems only) Make sure that the and environment variables are set
and that the directory paths contain no spaces.
11. Install Oracle client on the PPM Server.
12. Verify that the environment variable is set.
13. Create a system account for PPM Center.
To install PPM Center and maintain the system after installation, you must create a system
account. After you do, always log on to the server machine as this user to perform any PPM Server
maintenance—for example, stopping and restarting the PPM Server. This helps to avoid file system
permission issues, which can be difficult to track.
For instructions on how to create a system account, see "Creating a System Account for PPM
Center " on page 57.

14. Set up the Oracle tablespaces required to create the schemas and
database objects.
To create schemas and database objects, you must first create the data, index, and character
large object data type (CLOB) tablespaces.
15. Set Oracle database parameters:
o Set Oracle database parameter value to
o Set Oracle database parameter value to
Note: For new PPM Center installations, make sure you ALWAYS use .
For information about setting Oracle database parameters, see "Configuring or Reconfiguring the
PPM Server" on page 99.
16. Verify that the required ports are open through the firewall and that other applications are not
using them. (See "Verifying Port Availability" on page 65.)
The following sections provide detailed information about each of these tasks.
Note: The placeholder , which is used throughout this document, refers to the root
directory where PPM Center is installed. The name and location of this directory are up to you.
Do not unzip the installation files in your directory—instead, choose a temporary

directory in another location. The directory to which you extract the installation files is referred to
in this document as .
Obtaining PPM Center Software

After your organization's PPM Center software purchase order is processed, you receive a welcome
letter email from HP, which lists the language-specific download links and provides instructions on how
to activate your software license, access support, and how to log an incident. This section describes how
to download the PPM Center software after you receive the HP welcome letter.
To download the PPM Center software:

1. Go to the Electronic download page on the HP order fulfillment Web site
(https://h20348.www2.hp.com/ecommerce/efulfillment/downloadpage.do).
2. If you do not yet have an HP Passport, click Register, and then complete the registration process
to obtain an HP Passport.
3. Once you have an HP Passport, click Login.
4. In the UserID box, type your HP Passport user ID.
5. In the Password box, type your HP Passport password.
6. Review, and then accept, the terms and conditions of the download.
7. Click Sign-in.
The purchased software bundle download links become accessible for download (or redownload)
for up to 90 days after the purchase date.
8. Click the link for the PPM Center software version you plan to install, and follow the instructions to
complete the download.
Software Update Manager

If you have the required service agreement ID (SAID), you can get PPM Center software updates through
the Software Update Manager (SUM) site (http://www1.itrc.hp.com/service/sum/home.do).
Collecting Required Information

The PPM Center installer prompts you to enter information that it uses to create and configure the
PPM Server. The installer validates each value you enter before it continues the installation. The
following table lists the information required for installing PPM Center on either a single PPM Server or
the primary node for a server cluster.
Note: For additional information that you must provide if you are installing the primary PPM Server
for a server cluster, see "Configuring a Server Cluster" on page 179.
Table 3-4. Required installation information

Prompt Description

Table 3-4. Required installation information, continued

CLASSPATH Environment variable that specifies the directory in which Java class files
reside.
Note: The directory path must not contain spaces.
Software Directory in which the PPM Server is to be installed and configured. If the

installation location directory does not exist, the installer creates it. The directory path cannot
contain spaces.
Note: Do not map the directory so that it is accessible from

an external Web server. This introduces a potential security risk. HP
recommends that you not share this directory.
Path to the The Autopass license key file contains valid PPM Center license keys that you
Autopass license generated from the HP Licensing for Software portal.
key file
If you do not have a valid Autopass license key file, see "Activating and
Generating Autopass License" on page 96.
Path to JAVA_HOME The directory in which Java is installed. On UNIX systems, this environment
variable is set in the profile file (a or file) of the user who
is installing PPM Center.
Windows example
Note: Make sure that the value specified for contains no

spaces.
Database Access page
(Displayed if you chose to have the installer create the database schemas)
System access System database user name to give the installer access to the database.
username
System password System database password to give the installer access to the database.
Note: Do not use a string like “hpswDemo$09$” as a password during the

installation, because the InstallAnywhere treats “$09$” as a parameter
and consequently turns “hpswDemo$09$” into “hpswDemo”.

Table 3-4. Required installation information, continued

JDBC URL JDBC URL the PPM Server uses to connect the Oracle database.
Short format (non-RAC):
where
l is the host name or IP address of the computer running the

database
l is the port number that SQL*Net uses to connect to the database.

To get the actual value, look at the corresponding entry in
l is the security identifier of the database. This is usually identical to

the database connect string. If it is different, an extra parameter is
required.
RAC format:
Example of database access information used to enable the PPM Server to

communicate with databases on two servers named Jaguar1 and Jaguar2:
Table 3-4. Required installation information
Prompt Description
ORACLE_HOME Home directory for the Oracle client tools on the PPM Server machine. The
directory path cannot contain spaces.
PATH Environment variable that specifies the directories to be searched to find a

command.
SQL*PLUS Location of the SQL*Plus utility.
SQL*Plus is not required for installation, but is required for the PPM Server.
Example

Table 3-4. Required installation information , continued

Prompt Description
If the environment variable is set, then this parameter is

detected automatically.
PPM Center Schema page
(Displayed if you created the database schemas before installation)
Username PPM Center database schema user name.
Password PPM Center database schema password.
RML Schema page
Username Username for the PPM Center Reporting Meta Layer (RML) schema.
Password Password for the PPM Center Reporting Meta Layer (RML) schema.
Tablespaces page
Table Data type tablespace in the Oracle database
Index Index type tablespace in the Oracle database
CLOB data Character large object data type (CLOB) tablespace in the Oracle database
NT Service
Service name Name of the Windows service for the PPM Server.
Regional Settings
Holiday schedule Holiday schedule on which to base the PPM Center regional calendar. If your
holiday schedule is not listed, you can select None. In that case, a new
calendar with no holidays is set as the system default regional calendar.
Currency code Three-letter code for the default currency. The system default is in US
dollars (USD). For information on currency codes for other countries, see the
Caution: Once you choose your default currency during installation, you
cannot change it.
Region name Name of the region for the installation, which is defined by a combination of
calendar and currency.
If your organization operates in only one region, use "Enterprise" or your

company name.

Unzipping the Installation Files

Before you run the installation driver script, extract your installation files for the PPM Center software
to the directory. The extraction procedure creates a new subdirectory named
Run the extraction command in a directory other than the directory.
Note: Do not change the directory name.
Installing the Java Development Kit (JDK)

Because the PPM Server is based on Java, the machine that hosts it must also host a Java Virtual
Machine (JVM), which is part of the Java Development Kit (JDK). JDKs native to the operating systems
supported by PPM Center are available from either Oracle or from the operating system vendor.
Note: You must install the complete JDK. The Java Runtime Environment (JRE) alone is not
supported.
For a list of required JDKs, see the
To install the JDK:
1. Download the JDK for your operating system from Oracle or from your operating system vendor's
Web site.
2. Install the JDK according to the instructions provided by the vendor.
Many operating systems require that you apply operating system-specific patches before you
install the JDK. Make sure that you follow all instructions that the vendor provides.
Some vendors provide custom installation packages that you can install automatically using a
command such as . Other vendors provide a TAR file that you must extract.
Note: The directory path name must not contain spaces.
3. Verify that your user name has the Java executable in its path by logging on and running the
following the command:

This returns the Java version. If an error message is displayed, modify the path environment
variable, as required.
Note: For information on supported JDK software, see the
4. Verify that the environment variable is set correctly. If the path set for is
not correct, set it to the correct value.
Note: For information about how to check for and set the environment variable,
see "Verifying that the JAVA_HOME Environment Variable Is Set" on the next page.
(Optional) Configure JDK to Use the Unlimited Strength Java

Cryptography Jars
PPM Center supports control over the encryption suites used by its SSL (TLS) sockets. This can be
specified by the server configuration parameter .
The value for this parameter should contain a comma-separated list of the encryption suites to be
made available to PPM Centre. These should be specified using the standard SSL/TLS cipher suite
names.
For example, to specify that PPM Center should only establish connections using the TLS_DHE_RSA_
WITH_AES_256_CBC_SHA cipher suite:
If using AES256 or similarly strong encryption, the JDK used by both PPM Center and the client must be
configured to use the unlimited strength Java cryptography jars, if this is permissible in your jurisdiction
and under US export laws.
Note: The parameter only impacts the encryption algorithm used for
RMIS traffic. There is no impact on HTTPS (SSL) encryption, nor on how the passwords and sensitive
data are encrypted in PPM Center.
To configure your JDK to use the unlimited strength Java cryptography jars,

1. Go to http://www.oracle.com/technetwork/java/javase/downloads/index.html.
2. Scroll down to the end of the page and download the unlimited strength Java cryptography jars
that match your JDK version.
For JDK 1.7.0, download Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
Files 7 ( ).
3. Extract the downloaded zip package.
4. Copy the and files to the

directory on both your server side and client side to replace the
existing files.
Note: If you enabled secure RMI and are using a high strength encryption suite, such as
AES256, make sure to follow the steps above to install the unlimited jars on machines which
will run workbench.
Verifying that the JAVA_HOME Environment Variable Is Set

PPM Center requires that you set JAVA_HOME in the system environment of the user account to be used
to start the PPM Server. It is important that the JAVA_HOME environment variable be set for the same
shell and user who runs the installation.
Caution: Make sure that the value specified for JAVA_HOME contains no spaces.
Determining the JAVA_HOME Value in DOS
To determine the JAVA_HOME value in DOS, at the command line, type echo %JAVA_HOME%
Determining the JAVA_HOME Value in UNIX
To determine the JAVA_HOME value in a UNIX shell (SH, BASH, or KSH), at the UNIX prompt, type echo
$JAVA_HOME
Setting the JAVA_HOME Value in Windows
The steps described in the following procedure are for Windows 7. The exact steps may differ,
depending on your Windows operating system.

To set the value of JAVA_HOME in Windows:
1. Open the Control Panel.
2. Open the System window.
3. Click Advanced system settingsin the navigation pane.
The System Properties dialog box opens.
4. Click Environment Variables on the Advanced tab.
5. Under System Variables, click New.
The New System Variable dialog box opens.
6. In the Variable name box, type JAVA_HOME
7. In the Variable Value box, type the full Java install directory path, and click OK.
8. Locate the Path variable under System Variables, click Edit.
The Edit System Variable dialog box opens.
9. In the Variable Value box, add to the existing value and click OK.
Setting the JAVA_HOME value in Cygwin
To set the JAVA_HOME value in Cygwin,
1. Add the the JAVA_HOME parameter to System Variables.
For detailed instruction, see Setting the JAVA_HOME Value in Windows section above.
2. (Optional, but recommended) Set the file.
a. Open the file in a text editor.
b. Add the following to the end of the file:
c. Save the file and quit.

Setting the JAVA_HOME Value in DOS
To set the value of JAVA_HOME in DOS, run the following:
Setting the JAVA_HOME Value in UNIX
To set the value of in UNIX using the Bourne shell (SH, BASH, or KSH), run the following:
Creating a System Account for PPM Center

To install PPM Center and maintain the system after installation, you must create a system account.
After you do, always log on to this account on the server machine to perform any PPM Server
maintenance—for example, stopping and restarting the PPM Server. This helps to avoid file system
permission issues, which can be difficult to track.
Configuring a System Account for PPM Center in Windows
In Windows, configure the user to be a member of the Administrators and Domain Users groups, at a
minimum. Provide the user with full access to the installation directory for PPM Center and all of its
subdirectories. Provide the Administrators screen group with at least read access to these directories.
Configuring a PPM Center User for PPM Center in UNIX
In UNIX, PPM Center does not require root access for installation. Do not install the server as the root
user.
Configure your PPM Center user with the following:
l In the file,
o Set the environment variable.
o Set the environment variable.
l Set the term to dumb option.

Installing a UNIX Emulator (Windows)

To run PPM Center on Microsoft Windows, you must have a UNIX emulator such as Cygwin installed. For a
list of supported UNIX emulators , see the .
Note: To configure private key authentication with secure shell (see "Configuring Private Key
Authentication with Secure Shell" on page 103), you use the ssh-keygen utility, which is part of the
Cygwin installation. To get this utility, you must enable the Open SSH components during Cygwin
installation.
Creating the Database Schemas

To create the empty database schemas (with tables to be populated during installation):
1. Set up the required data, index, and CLOB tablespaces for the PPM Center database schema.
Tip: Even though a fresh installation of PPM Center typically requires less than 1 GB of
database space, its size could sharply increase with time, especially if you choose to store
attachments in the database. For an accurate estimation of your DB space requirement on the
long term, contact HP Software Support.
Use locally-managed SYSTEM tablespaces with automatic segment-space management.
Note: Locally-managed tablespaces eliminate extent fragmentation and provide better

performance than dictionary-managed tablespaces.
2. Create each tablespace as shown in the following example for a data tablespace.

Note: Oracle has the default TEMP tablespace, which you can resize to improve performance.
The PPM Server requires two separate database schemas to store application data. A DBA can create
these schemas before installation. Creating database schemas requires privileges that a DBA might not
want to grant to a PPM Center administrator. Either create the database schemas before installation or
make sure that a DBA is available during installation.
To create the database schemas and grant the permissions between them:
1. Unpack the PPM Center installation bundle as outlined in "Installing PPM Center" on page 67.
The directory is created. The and

directories contain the scripts required to create the database
schemas.
2. Run the script (located in ) against the

database into which you plan to install PPM Center. The script prompts for a user name and
password, and the tablespaces that the PPM Center database schema are to use.
sqlplus system/<Password>@<SID> \
@CreateKintanaUser.sql \
<PPM_Username> \
<Password> \
<Data_Tablespace> \
<Index_Tablespace> \
<CLOB_Tablespace>
3. To enable the PPM Center database user to create views and synonyms in the RML schema,
connect to the database that contains the RML schema, and then issue the following SQL
statements:

4. Run the script, which is located in the directory.
The script prompts for a user name and password for the Reporting Meta Layer (RML) schema,
tablespace information, and the PPM Center database schema user name. The script creates the
RML schema and establishes the permissions between the RML and the PPM Center database
schema.
Note: Because the RML schema contains only views (and no physical objects), it does not
require a separate tablespace.
sqlplus system/<Password>@<SID> \
@CreateRMLUser.sql \
<RML_Username> \
<>RML_Password> \
<Data_Tablespace> \
5. As the SYS DBA user, run the script, which is located in the
directory.
This script grants the privileges that the PPM Server requires.
If you created the schemas before installation, select Please use existing schemas when prompted
during installation. Supply the same values as those used in this procedure (that is, the values
and ).
Default Permissions for PPM Center Schemas

By default, the PPM Center database schema and RML database schema accounts (PPM_USER and
RML_USER) are granted Oracle database privileges from an overall PPM Center perspective, which
works for all customer scenarios and environments. Some of these privileges are required, but some
are not, and can be revoked without affecting the PPM Center system.
The PPM Center database schema account is granted Oracle CONNECT role privileges. If this presents a
problem for your organization, you can have your DBA revoke the CONNECT role privilege for the PPM
Center database schema account.
Although revoking the CONNECT role privilege does not affect the PPM Center system, the PPM Center
schema does require the following grants:

l grant create session
l grant create database link
l grant create procedure
l grant create sequence
l grant create synonym
l grant create table
l grant create view
l grant create trigger
l grant create job
l grant execute on ctxsys.ctx_ddl
The RML database schema account is granted Oracle RESOURCE role privileges. Because the RML
schema requires the RESOURCE role privilege, it cannot be revoked. You can, however, revoke the
following privileges, which are also granted to the RML database schema account:
l CREATE CLUSTER
l CREATE INDEXTYPE
l CREATE OPERATOR
Other Permissions Needed or Not Needed for PPM Center Schemas

Accounts
This section provides more information about other permissions needed or not needed for PPM Center
database schema and RML database schema accounts. You can decide whether you want to have them
revoked after reading this section.
HP has not tested every access grant and its impact, because every access grant has a different impact
on each customer, as every customer is using PPM differently and for different scenarios. If you are
looking for specific access grant impact, you may need to test that out.

l SELECT_CATALOG_ROLE and SELECT ANY DICTIONARY
If only SELECT_CATALOG_ROLE is enabled then it provides access to all SYS views only.
If only SELECT ANY DICTIONARY privilege is enabled then it provides access to SYS schema objects
only.
If both SELECT ANY TABLE privilege and SELECT ANY DICTIONARY privilege are enabled then it allow
access to all SYS and non-SYS objects.
PPM Center needs to access many SYS/DBA views and objects, thus needs SELECT_CATALOG_ROLE
role and SELECT ANY DICTIONARY privilege.
To generate AWR/ADDM/ASH reports, PPM Center needs SELECT_CATALOG_ROLE role too.
l PPM Center need access to the following packages:
– DBMS_JAVA
– DBMS_JAVA_TEST
– DBMS_LOB
– DBMS_SCHEDULER
– DBMS_SQL
PPM Center does not need access to the following packages:
– UTL_FILE
– UTL_HTTP
– UTL_TCP
For other packages, read the information below to decide whether your PPM Center still needs
access to them:
o DBMS_JAVA — PPM Center uses a stored procedure written in Java, to generate a hash that is
used as REFERENCE_CODEs for various PPM Center entities. Generating this hash using pure
PL/SQL is cumbersome and unreliable, if not impossible. So, PPM Center used Java for it and the
application code needs access to this package.
o DBMS_JAVA_TEST — Allows you to test Java Stored Procedures. PPM Center might not need to
access this package. So far there seems no harm or implications of revoking the access.
o DBMS_LOB — PPM Center stores a lot of data in BLOB and CLOB columns and the application code
might need to parse or modify the contents.

o DBMS_SCHEDULER — Not needed for core PPM Center. This is required for Operational Reporting.
If your organization does not use Operational Reporting, you may revoke access to this package.
o DBMS_SQL — PPM Center generates dynamic SQL and executes it during installation and
upgrade. This package is also used to create triggers as part of the application functionality.
l EXECUTE ANY PROCEDURE and EXECUTE ANY PROGRAM
PPM Center does not need the EXECUTE ANY PROCEDURE privilege.
PPM Center needs the EXECUTE ANY PROGRAM privilege. The definition of EXECUTE ANY PROGRAM is
as follows:
Use any program in a job in the grantee's schema.
l CREATE ANY VIEW, CREATE ANY TABLE, SELECT ANY TABLE
RML_USER needs these three privileges:
o CREATE ANY TABLE — Create tables in any schema. The owner of the schema containing the table
must have space quota on the tablespace to contain the table.
o SELECT ANY TABLE — Query tables, views, or materialized views in any schema.
o CREATE ANY VIEW — Create views in any schema.
l Privileges required for RML database schema
For information about other Oracle database privileges, see Oracle documentation.
Creating a Shared Folder for the server.conf File

In order to implement a server cluster (recommended) you must have a shared folder for the server
configuration file ( ). In addition to giving all nodes in a cluster access to the same
file, the shared folder simplifies maintenance of the file.

This section provides instructions on how to prepare the shared folder on both Windows and UNIX
systems.
Note: The shared folder described in this section is also required to give users access to the
Administration Console interface after you deploy your PPM Center instance. For information about
the Administration Console, see "Tools in the Administration Console" on page 281.
Preparing a Shared Folder for server.conf on a Windows System
To prepare a shared folder for the file on Windows:
1. Create a shared folder on a file server.
Note: If you plan to configure the server cluster configurations on multiple machines, keep in
mind that the nodes in the cluster must all run on the same operating system. Shared access
to the file does not support mixed operating systems.
2. Attach the shared folder to each machine that is to host PPM Center.
3. If you plan to host multiple PPM Server clusters (instances) under the same account on a single
machine, do the following. Otherwise, proceed to step 4.
a. Using a text editor, create a file named , and add to it the following
text:
b. Save the file in the directory and close the file.
4. Open the Control Panel and define an environment variable named for an
account that is to run PPM Center nodes on Windows. The value of the environment variable is the
location of the shared folder.
Caution: Make sure that you use Universal Naming Convention (UNC) notation
( or
) to specify the location of your shared folder.
Preparing a Shared Folder for server.conf on a UNIX System
To prepare a shared folder for the file on UNIX:

Note: If you plan to configure the server cluster configurations on multiple machines, keep in
mind that the nodes in the cluster must all run on the same operating system. Shared access
to the file does not support mixed operating systems.
2. Mount the shared folder to each machine that is to host PPM Center.
3. If you plan to host multiple PPM Server clusters under the same account on a single machine, do
the following. Otherwise, proceed to step 4.
a. Using a text editor, create a file named "ppm_server_conf.env", and add to it the following
text:
b. Save the file to the directory and close the file.
4. In the file of the account that is to run PPM Center, add the following line:
Verifying Port Availability

To successfully install and configure PPM Center, specific ports must be available through the firewall.
To expedite installation, make sure that the ports are available before you start to install the product.
The following table contains summary information about the ports and protocols that PPM Center
system components use to communicate.
Note: If you are using an external Web server, you must assign it a port number other than the one
assigned to the internal Web server.

Table 3-6. PPM Center ports and protocols
Communication Channel Protocols Ports
Web Browser and Web Server HTTP/HTTPS 80/443 (configurable)
If you do not use the default port, you must specify the
port number in the URL.
Example:
You may also be required to open the firewall for ports

other than the defaults.
On UNIX systems, only processes started by the root user

can be assigned a port number that is less than 1024.
PPM Workbench and App Server RMI / SRMI 1099 (configurable)
External Web Server and App Server AJP13 8009 (configurable)
App Server and Database JDBC 1521 (configurable)
App Server and Mail Server SMTP 25
App Server and LDAP Server LDAP 389
App Server and LDAP Server LDAP over SSL 636
App Server and External System SSH 22
App Server and External System FTP (control) 21
App Server and External System FTP Data Dynamic
App Server and External System SCP (Secure Copy) 22
App Server nodes TCP/UDP Customized in

, ,
and
. It
depends on your requirement.
Assigning Ports Outside of the Ephemeral Port Range
PPM Center uses many client sockets for its internal communications. These are allocated randomly
from the operating system's ephemeral port range.

To prevent conflicts between internal client socket use and your PPM Server port settings, you must
check to make sure that the ephemeral port range set for your operating system does not conflict with
any of the ports assigned in your file. For information about the default ephemeral port
range on your operating system and how to adjust it, see the documentation for your specific operating
system.
Installing PPM Center

This section provides the detailed steps used to install the database objects and data that the
PPM Server uses. You can perform these steps on any computer (running UNIX or Windows) that has
SQL*Net connected to the database on which the PPM Center database objects are to be installed.
Caution: Make sure that you have at least 300 MB temporary space and 0.5 to 1 GB swap space
available on your operating system.
l "Installing PPM Center on a Windows System" below
l "Installing PPM Center on UNIX Systems" on page 76
Installing PPM Center on a Windows System

The installation utility for a Windows server is an executable file that performs the steps required for a
basic server installation. The executable and supporting files are contained in a Zip file. The typical
installation automatically installs the following components on the server:
l PPM Center program files
l PPM Center database objects
l Start menu item
l Windows service
Caution: You cannot install PPM Center unless you have SYS DBA privileges or a DBA has already
created the required schemas. For more information, see "Key Decisions" on page 39.
To install the PPM Server on Windows:

1. Make sure that you have a UNIX emulator (such as Cygwin) installed.
Note: For a list of supported UNIX emulators, see the

.
To configure private key authentication with secure shell (see "Configuring Private Key
Authentication with Secure Shell" on page 103), you use the ssh-keygen utility, which is part of
the Cygwin installation. To get this utility, you must enable the Open SSH components during
Cygwin installation.
2. Extract all files from to the file system.
The extraction creates the directory, which includes the file.
3. From the directory, use Windows Command or Cygwin to run the script.
The PPM Center installer starts.
Note: (Windows 2012 R2 platform only) If you encounter an error and fail to launch the PPM
Center installer, you need to modify the properties of the file for the
installer to run properly. To do so,

a. Locate and right click the file in the

directory.
b. Select Properties from the popup menu.
c. In the ppm_install Properties window, go to the Compatibility tab.
d. In the Compatibility mode section, select the Run this program in compatibility mode
for: checkbox and select a desired option from the drop-down list.
e. Then in the Privilege level section, select the Run this program as an administrator
checkbox.
f. Click Apply.
g. Click OK.
h. Double click the file to launch the PPM Center installer.
4. From the Select the language for this installation list, select the language that you want the
installer to use to display the installation steps.
Depending on the operating system language of the host machine, the languages available for
displaying the installation wizard steps are limited, as shown in the following table.
Languages Available for Displaying Installation

Operating System Language Wizard Steps
English English
Spanish Spanish
Italian Italian
French French
Dutch Dutch
German German
Portuguese (Brazilian) Portuguese (Brazilian)
Swedish Swedish
Russian Russian
English
Chinese Chinese

Languages Available for Displaying Installation

Operating System Language Wizard Steps
English
Korean Korean
English
Japanese Japanese
English
Turkish Turkish
English
Arabic Arabic
English
So, for example, if your operating system is Chinese, you can view the installer steps in either
Chinese or English. This option in no way affects the language packs that you can install.
Note: The language you select here is not the same as the system language, which you select
at a later step.
5. On the License Agreement page, read the agreement carefully, and then select I accept the terms
of the License Agreement.
6. On the Choose License page, select Yes, I have a license and want to install it now to install an
Autopass license file that is sent to you by HP. Or, select No, thanks. I will install the license
later. to generate and activate a 60-day trial license.

7. On the next several pages, provide the information you collected to prepare for the installation
(see "Collecting Required Information" on page 49 in "Collecting Required Information" on page 49).
The MLU (Multilingual User Interface) page is used to select a and additional
languages to deploy on this PPM Center instance.

8. From the Select the system language list, select the PPM Center system language to use.
The system language is the language used to generate system-level information such as server
start-up and shut-down messages. The system language is also used to display attributes of
system data that does not support multiple translations. For more information, see the
.
9. Select the check boxes for any languages you want to deploy in addition to the system language on
your instance.
Note: You can always install languages later, as needed, by running the script. For
information on how to deploy languages after you install PPM Center, see the

10. On the server mode step, do one of the following.
Note: In this context, the term "server mode" refers to a stand-alone or a clustered type of
installation, and is different than the server mode addressed in "Setting the Server Mode" on
page 87.
o If you are installing a primary PPM Server for a production instance, select Cluster.
o If you are installing a PPM Center testing instance or development instance that will consist of a
single PPM Server, leave Stand-alone selected.

The Configuration Option page opens next.
11. On the Configuration Option page, indicate whether you want to configure the PPM Server during
installation, or later, after installation.
Note: For instructions on configuring the server later, see "Configuring the System" on
page 86.
12. If you choose to configure the server, the installer displays several pages of server configuration
parameters. Provide values for all of the required parameters, which are displayed in red text, and
for any optional parameters you want to set.

For descriptions of and valid values for all listed parameters, see "PPM Center Configuration
Parameters" on page 422.
After you provide all required information, the PreInstall Summary page displays summary
information about the installation to be performed.
13. To proceed with the installation, click Install.
Note: The installer displays a progress bar that enables you to monitor installation.
To optimize system performance, the installation script rebuilds statistics for the Oracle optimizer.
For the installation procedure to perform this step, you must have the following grants to the
schema in place:
o
o
o
o
o
The script (located in the directory) performs

these required grants.
If you did not run the script before you started installation, do it now (with
SYS DBA access).
14. After successful installation, PPM Center is installed as a Windows service. You can view the
properties for this service through the Services Control Panel item. To complete the service setup,
start the PPM Center service from the Control Panel (Start > Administrative Tools > Services.)
HP recommends that you set the startup type to Automatic so that the PPM Server restarts
automatically after the computer is restarted. If you have generated a custom PPM Center user, specify
this user name for the "Log On As" value.
Note: PPM Center comes with an Administrator user with the default username/password
combination admin/admin. HP recommends that you change the password for the administrator
user after you install PPM Center.

An item that corresponds to the Windows service name that you specified during installation is added to
the Start menu. The menu provides links to PPM Center documentation and an uninstall program.
If you did not configure the PPM Server during installation, see "Configuring or Reconfiguring the
Installing PPM Center on UNIX Systems

To install the PPM Center on UNIX:
1. Download the bundle and copy it to a directory, referred to as in the following
steps.
2. To extract the files into the directory from the download bundle, at a command
prompt, type one of the following:
unzip ppm-930-install.zip
Alternatively,
jar xvf ppm-930-install.zip
All the files and scripts required for PPM Center installation are extracted (to ). The
installer prompts for the software install directory. You can specify any directory for installation.
The directory that results from the extraction contains the

shell script.
3. To start the installation, run the installation script (as the system account for PPM Center) and
specify the installation mode.
Example
where
Swing mode is an interactive, GUI-based installation mode that requires an X

Window session. A wizard guides you through the installation steps.
Console mode is the interactive command-line mode. The installation script

runs within the terminal session and you respond to the prompts.

To optimize system performance, the installation script rebuilds statistics for the Oracle optimizer.
For the installation procedure to perform this step, you must have the following grants to the
schema in place:
o
o
o
o
o
The script (located in the directory) performs

these required grants.
4. If you did not run the script before you started installation, do it now (with
SYS DBA access).
Note: PPM Center comes with an Administrator user with the default username/password
combination admin/admin. HP recommends that you change the password for the administrator
user after you install PPM Center.
Configuring the FTP Server on Windows

PPM Center 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 Center.
Before you configure the FTP server on a machine, make sure that the Windows user account (which
PPM Center uses to open a connection) has access to the directories to which files are to be moved.
Some FTP servers require that you map these directories to FTP aliases, and a configuration utility is
usually provided for this (for example, for Microsoft IIS, the utility is Internet Services Manager).
Note: On Windows, most FTP servers, including Microsoft IIS, do not support drive letters. If you use
FTP in PPM Center, the drive letter is removed from the base path. If your base path is
then FTP tries to start from the ftp root directory and FTP fails.

To work around this, you must create an FTP alias. (For example, map to )
Configure the FTP server according to directions that the vendor has provided. For the File and Directory
Chooser components to work, you must set the FTP server directory listing style to UNIX, and not to MS-
DOS.
To set the directory listing style to UNIX:
1. In Windows, open the Internet Services Manager.
2. In the left pane, under Console Root, open the Internet Information Server.
3. Select the machine name.
4. Right-click the Default FTP site displayed in the right pane, and then click Properties on the
shortcut menu.
The Default FTP Site window opens.
5. Click the Home Directory tab.
6. Under Directory Listing Style, click UNIX.
7. Test the connection by trying to open a session manually. If you can open an FTP session and
navigate from one directory to another, then PPM Center can do this too.
Contacting Support
If you encounter problems with your installation or if have questions, contact HP Software Support Web
site (hp.com/go/hpsoftwaresupport). Before you contact HP Software Support, have the following
information ready:
1. Open the file (located in the directory) in a

text editor.
This file provides information about what part of the installation failed.
2. Search the file for an error message that is specific to installation failure.
3. Place all of the files in the directory in a compressed file.

The installation utility creates a separate log directory for each installation attempt. In the most
recent directory, examine each file to determine exactly where the PPM Server has failed. The log
file contains information about which failed action it attempted.
Downloading and Installing Service Packs

HP occasionally delivers product service packs to licensed PPM Center customers. You can use the
script (a command-line tool) to install service packs.
Note: To install a service pack, you must make sure that you have the required system privileges.
For information about these privileges, and when to grant them, see "Key Decisions" on page 39.
PPM Center service packs are distributed as deployments (software bundles that contain files and
data). You can get service packs from the HP support Web site.
To locate and download a service pack to install on your PPM Center instance:
1. Go to the Patches search page (support.openview.hp.com/selfsolve/patches) on the HP Software

Support Web site.
2. In the Select your search criteria section, provide the information listed in the following table:
Field Information
Product Select Project and Portfolio Management.
Product version Select the version of the PPM Center software you have installed.
Operating system Select the operating system on which PPM Center is installed.
3. Provide any optional search criteria you want to specify, and then
click Search.
The Title section of the Patches search page lists the service packs that match your search
criteria.
4. Click the link for the service pack to download.
The download page for the selected service pack lists detailed information.
5. In the Should I download? section, click DOWNLOAD PATCH.

6. In the File Download message window, click Open.
7. Copy the deployment JAR file to the directory.
Deployments are in the following format:
where
represents the PPM Center version for which the service pack was created
represents the unique identifier for service pack
represents an optional revision number for the deployment, and may not be
included in the deployment name.
Note: If multiple languages are deployed on your PPM Center instance, after you install a service
pack, you must redeploy the language packs to restore the MLU. For more information, see the
Example
To install Service Pack 1:
1. Back up your database.
2. Stop the PPM Server.
Note: You cannot install the service pack on an active server. For information about how to
start and stop the server, see "Starting and Stopping the PPM Server" on page 87.
3. Run the following command:
4. As the script runs, respond to the prompts.
5. Start the PPM Server.
Tip: To obtain a list of all service packs applied to your PPM Center instance, run the command

For more information about the script, see "kDeploy.sh" on page 518
Contacting Support
If problems occur during service pack installation, go to the HP Software Support Web site
(hp.com/go/hpsoftwaresupport).
Protecting Backed-Up Data

Because the backups (both server host and database backup) you create may contain sensitive
information such as cryptographic keys and payload data, HP strongly advises that you protect the
backups themselves. Oracle Advanced Security provides transparent data encryption of data stored in
the database, the encryption of disk-based backups of the database, and network encryption for data
traveling across the network between the database and client or mid-tier applications. In addition, it
provides a complete suite of strong authentication services to Oracle Database.
If you want to use Enterprise User Security in Oracle Database Enterprise Edition, you must license
Oracle Internet Directory (OID). If you want to use stronger authentication alternatives (such as
Kerberos or PKI) for enterprise user security, you must license Oracle Advanced Security and the Oracle
Internet Directory (OID). For more information, see the release notes for your Oracle software.
Handling Backup Files Related to Service Pack Installation

During a service pack installation, the installer backs up all of the existing files that are to be replaced.
After multiple service pack installations, the backup files can take up significant space.
Eventually, the backed up files can consume so much space that service pack installation fails. To
prevent this from occurring, do one of the following:
l Use the script to install service packs without creating backup files.
For example, to install "Service Pack 3" without creating a backup, run the script as follows:
sh ./kDeploy.sh -i SP3 -B
l Specify that backed up files are deleted after service pack installation. To do this, run the
script, as follows:
sh ./kDeploy.sh -tidy

Uninstalling a Service Pack

When you deploy a service pack bundle, a basic full backup of your PPM Center system is performed,
including the following system folders: , , , , , , , , ,
, , , .
The Patch Uninstaller included in this version allows you to uninstall the service pack files and roll back
your PPM Center file system to the status before the service pack was deployed, using the full backup
files. Note that only the File System changes are rolled back. After rollback of the service pack, make
sure you manually restore PPM Center database to the status before the service pack was deployed,
otherwise the system will NOT work properly.
To uninstall a service pack and roll back the file system to its previous status,
1. Stop PPM Server.
2. Navigate to the directory.
3. Run the following command:
sh ./kDeploy.sh -rollback
4. Follow the on-screen instructions when prompted.
5. Restart PPM Server.
Note: The rollback operation does not roll back the script itself.
Verifying PPM Center Installation

To verify the installation:
1. Check the logs produced during installation. (Located in the

directory)
2. Complete the PPM Center configuration and perform all post-installation tasks (covered in later
chapters).

4. Log on to PPM Center.
Note: All PPM Center clients use the same base URL, which is the Web location (top directory
name) of the PPM Server. To obtain the URL, open the file, which is located in
the directory. The URL is the value specified for the parameter.
5. Start the PPM Workbench.
6. Run a report. (For instructions, see "Running Server Reports from the Admin Tools Window" on
page 327.)
7. Create a request and test the graphical view of the request. (For instructions, see the
)
8. Add a portlet to a PPM Dashboard page and export the page in PDF format. (For instructions, see
the guide.)
Note: Before you can export a page in PDF format, you must enable that functionality. For
information, see "Enabling Export to PDF" on page 116.)
9. Create a project and a work plan. (For instructions, see the )
10. Create a staffing profile. (For instructions, see the )
11. Create a time sheet. (For instructions, see the )
Optional Installations
This section provides descriptions of additional products that you can install and set up to work with
PPM Center.
Installing HP Project and Portfolio Management Best

Practices
HP PPM Best Practices provides customers with experience-derived information and advice about
configuring and using Portfolio Management and Program Management. Best Practices installation

places various workflows and request types on your system to help optimize your use of Program
Management and Portfolio Management.
For more information, see "About PPM Center Best Practices Installation" on page 41. Before you start
to install Best Practices, make sure that of the conditions described in "Requirements for Installing
Best Practices" on page 41 have been met.
To install Best Practices:
1. Start the PPM Server from the command line.
2. Set your server to RESTRICTED mode.
Note: Although setting your server to RESTRICTED mode is optional, HP recommends that you
do so. In RESTRICTED mode, the PPM Server enables only users with Administrator access
granted to log on.
You can use the script to set the server to RESTRICTED mode. (See
"Setting the Server Mode" on page 87.)
3. Run the script, as follows.
Note: For more information about the script, see "kDeploy.sh" on page 518.
Verifying HP Project and Portfolio Management Best Practices Installation
To verify that Best Practices is successfully installed, run the script, as follows.
sh ./kDeploy.sh -l
This returns a list of the deployed bundles in an instance.
Installing Deployment Management Extensions

If you plan to install an Deployment Management Extension, you must do so after you install and
configure PPM Center, and before you use PPM Center for processing.
You are not required to stop the PPM Server(s) before you install an Extension. However, HP
recommends that you install the Extension when no users are logged on to the system. Consider placing
the server in RESTRICTED mode before you install.

Note: Although setting your server to RESTRICTED mode is optional, HP recommends that you do
so. In RESTRICTED mode, the PPM Server enables only users with Administrator access granted to
log on.
You can use the script to set the server to RESTRICTED mode. (See "Setting the
Server Mode" on page 87.)
For specific information on how to install an Deployment Management Extension, see the
documentation for the Extension you purchased.
Note: To install an Extension successfully, you must make sure that you have the required system
privileges. For information about these privileges, and how to grant them, see "Key Decisions" on
page 39.
What to Do Next
After you have successfully installed PPM Center, delete all subdirectories of the
directory, except for the subdirectory.
Proceed to "Configuring the System" on page 86.

Chapter 4: Configuring the System
This chapter provides detailed information about how to configure the basic components of the PPM
Center system and to start and stop the PPM Server. It also includes information that PPM Center users
need to know in order to use the PPM Workbench.
Note: For advanced PPM Center system configuration information, including how to configure an
external Web server and PPM Server clusters, see "Advanced System Configuration" on page 137.
l "(UNIX only) Setting the ulimit Value" below
l "Starting and Stopping the PPM Server" on the next page
l Installing Autopass Licenses for PPM Center Product
l "Configuring or Reconfiguring the PPM Server" on page 99
l "Enabling Export to PDF" on page 116
l "Verifying Client Access to the PPM Server" on page 119
l "Accessing the JMX Console" on page 119
l "Configuring or Reconfiguring the Database" on page 120
l "Configuring the PPM Workbench to Run as a Java Applet" on page 131
l "Using the PPM Workbench: What Users Need to Know" on page 133
l "What to Do Next" on page 136
(UNIX only) Setting the ulimit Value

On UNIX systems, PPM Center (through the script) uses the ulimit utility to set the maximum
number of open file descriptors to 1000. In a server cluster configuration, this setting may be too low,
causing nodes to come down.
If the default ulimit setting does not meet your requirements, reset it as follows:

1. Navigate to the directory and open the file in a text editor.
2. Locate the following text:
3. Change the ulimit value as follows:
4. Repeat step 1 through step 3 for each additional node in the cluster.
For example, if your server cluster consists of five nodes, then specifying the ulimit value of 1100
for each allocates 5500 open file descriptors for the PPM Server cluster deployment.
Tip: You can simply remove the setting mentioned in step 2 from the file to allow the
UNIX operating system to control the number of open file descriptors.
Starting and Stopping the PPM Server

To help ensure that your PPM Center system operates smoothly, HP recommends that you stop and
restart the PPM Server once a month. This section provides information about how to start the
PPM Server on a single-server system.
Note: Unless otherwise indicated, "the server" refers to the PPM Server, and not the server
machine.
For information about configuring and running a clustered configuration, see "System Configurations"
on page 23 and "Configuring a Server Cluster" on page 179.
Setting the Server Mode

PPM Center supports the following server modes:

l NORMAL. In NORMAL mode, all enabled users can log on, and all services are available, subject to
restrictions set in parameters.
l RESTRICTED. In RESTRICTED mode, the server enables only users with Administrator access granted
to log on. The server cannot run scheduled executions, notifications, or the concurrent request
manager while in this mode.
Before you can install an Deployment Management Extension, you must set the server to
RESTRICTED mode.
l DISDABLED. DISABLED mode prevents server startup. A server enters disabled mode only after a
PPM Center upgrade exits before the upgrade is completed.
Setting the Server Mode with setServerMode.sh
The script, located in the directory, sets the server mode in

situations where you want to obtain exclusive access to a running server.
To set the server mode using the script:
1. From the command line, change to the directory, and run the
script.
The Run dialog box opens.
2. In the Open field, type the following:
where represents the or server mode.
For example, to set the server to restricted mode, in the Open field, type:
For more information about the script, see "Setting the Server Mode" on the
previous page. For more information about the script, see "kConfig.sh" on page 516.
Setting the Server Mode Using kConfig

1. Run (located in the directory).
2. Select Set Server Mode.
3. In the list, select Restricted Mode.
4. Click Finish.
5. Run the script.
Starting and Stopping the PPM Server on Windows

This section covers starting and stopping the server on a Windows system.
Caution: If your PPM Center instance includes multiple nodes in a cluster configuration, you must
start these nodes one at a time. Make sure that you wait until each node is fully started before you
start the next node.
If your instance is configured as a server cluster the environment variable

is set, then before you start the PPM Server, you must configure user account logon options for the HP
PPM service. If you do not, the service will not start. (It is only necessary to do this once.)
To configure user account logon options for the HP PPM service:
1. From the Control Panel, select Administrative Tools > Services.
2. Right-click the HP PPM service, and then select Properties from the shortcut menu.
3. In the properties dialog box, click the Log On tab.
4. Select the This account option, and then type .\Administrator in the text box.
5. Type your administrator password in the Password and Confirm password boxes.
To start the PPM Server on Windows:
2. Right-click the HP PPM service, and then click Start on the shortcut menu.
Note: If you prefer to use the Windows shell command line to start servers, you can use the

kStart.sh script. For information about the kStart.sh script, see "Server Directory Structure and
Server Tools" on page 513.
To stop the server on a Windows system:
2. In the Services window, right-click the HP PPM service, and then click Stop on the shortcut menu.
Using the Windows Shell Command Line to Stop PPM Servers
If you prefer to use the Windows shell command line to stop servers instead of using Windows Services,
you can use the kStop.sh script. For information about the kStop.sh script, see "Server Directory
Structure and Server Tools" on page 513.
If the parameter is set to users running to shut down

the PPM Server must supply a valid PPM Center user name and password. If the parameter is set to
any user with access to the script can shut down the server. For information about
the parameter, see "REMOTE_ADMIN_REQUIRE_AUTH" on page 474.
Starting and Stopping the PPM Server on UNIX

To start the server on UNIX.
1. Change to the directory.
2. Run the script, as follows:
For more information about , see "kStart.sh" on page 532. For information about how to
start servers in a cluster, see "Starting and Stopping the PPM Server" on page 87.
To stop the server on UNIX.
Note: If the REMOTE_ADMIN_REQUIRE_AUTH parameter is set to users running to

shut down the PPM Server must supply a valid PPM Center user name and password. If the
parameter is set to any user with access to the script can shut down the server.

For information about the REMOTE_ADMIN_REQUIRE_AUTH parameter, see "REMOTE_ADMIN_

REQUIRE_AUTH" on page 474.
1. Navigate to the directory.
2. Run the script as follows.
Make sure that you type a valid user name that has Administrator privileges.
For more information about , see "kStop.sh" on page 533. For information about how to
stop servers in a cluster, see "Starting and Stopping Servers in a Cluster" on page 194.
Startup Checks
To help catch common configuration and deployment issues, PPM Center performs basic startup checks
before starting. These checks include:
l Making sure that essential parameters are present.
l Making sure that none of the ports required by PPM Center are already bound by other processes.
l Making sure that all ports used by the nodes on a given physical server have unique values.
Note: Because of these startup checks, you may encounter more configuration errors in 9.30 (and
beyond) that prevent a PPM Server from starting (whereas a successful start was allowed on a
previous version).
A summary of all issues found during the startup checks is traced out into the server log of the node
being started. If PPM Center is running as a Windows service, an error is added to the Windows event log
asking you to refer to the server log when errors are found. In some rare cases that the server logs
could not provide useful details, we recommend that you start PPM Center in the console mode by using
the script, and then troubleshoot the configuration and deployment issues. After you fix
these issues, you can start PPM Center as a Windows service again.
Errors fall into two categories:
l Critical errors (Error messages): These errors relate to the node being started. PPM Center will
refuse to start if there are any critical errors.

l Non-critical errors (Warning messages): These errors relate to other nodes in server.conf than the
one being started. It is highly recommended to fix such errors, however they will not prevent the
startup. All nodes in the file are checked when any one node is started.
Bypassing the Startup Checks
By default, the parameter in the

file is set to .
You can bypass the startup checks by setting this parameter to :
Caution: This parameter should only be used under advisement from PPM customer support
engineers, and if there is a clear and well-understood reason for doing so.
Comprehensive Logging During PPM Server Startup
PPM Center includes a significant number of improvements to the application startup process, from
both a logging and configuration validation standpoint. One of the goals of the improvements is to
provide customers with as much information as possible about the validity of the configuration of their
clustered environments.
Displaying Failed Executions at Startup
To enable the display of failed server executions at startup, make sure that the
server configuration parameter is set to in the file. All executions that
were interrupted during the last PPM Center shut-down are marked as failed.
Displaying Configuration Parameters at Startup
You can enable the display (and logging) of all PPM Center server configuration parameters used during
startup. To enable this feature, set the server configuration parameter
to
Adjusting the Server Log Level
Server startup logs indicate what the server is doing at each step of the startup process (including the
successful start of each web context). By default, when the startup check catches a configuration or
deployment issue, only a error or warning message will be generated in the server logs. You can modify
the logging level to get more details by adding the following entries in the logging.conf file:

Caution: These parameters are designed for advanced troubleshooting. We do not suggest
modifying these parameters without advisement from PPM customer support engineers.
Installing Autopass Licenses for PPM Center Product

This section contains the following topics:
l Overview of the Autopass Licensing Solution
l Generating an Autopass License Key File
l "Installing Autopass Licenses and Viewing License Summary in Administration Console" on page 97
l Installing Autopass License Key File Using the kLicenseInstall Tool
l Install An Autopass License in a Clustered Environment
l "Reading Licenses Information Using kLicenseReader" on page 98
l "Reading Licenses Information Using kLicenseReader" on page 98
Overview of the Autopass Licensing Solution

PPM Center version 9.30 implemented Autopass integration to replace PPM Center's original licensing
mechanism with HP's Autopass licensing mechanism. The new Autopass licensing solution simplifies the
license generation and validation process, supports more product license types, offers flexible license
installation options, and simplifies product license management.
l Simplified license activation and validation process. To activate and generate an Autopass
license, simply go to the HP Licensing for Software portal (http://www.hp.com/software/licensing).
See "Activating and Generating Autopass License" on page 96.
When installing an Autopass license key file, PPM Center validates the IP address of the PPM Server
against that assigned in the license file. For a clustered environment, IP address assigned in the

license file shall match that of the primary node in the cluster, otherwise you may receive a "0
license key(s) installed successfully" message.
Invalid licenses (expired license, or a license with IP address not matching that of the machine where
you plan to install the license) will not be installed.
l More product license types available. Starting from PPM Center version 9.30, in addition to the
perpetual product license (or term license), trial license and evaluation license are also available
with PPM Center 9.30. This allows new customers to try and evaluate PPM Center features and
functionalities.
o Trial license. For fresh install of PPM Center, a trial license is always automatically generated
and activated for you right away, which allows you to try and use PPM Center modules for 60 days
with limited number of users for different modules. Trial license has the lowest priority.
Tip: To view the features and capacity available with a trial license, you can check the PPM
Workbench License Administration window (PPM Workbench > System Admin > License).
o Evaluation license. An Autopass license key file that you generate from the HP Licensing for
Software portal with a specified start date and end date. The evaluation license allows you to use
an authorized set of PPM Center modules for an authorized period of time. When you install an
evaluation license, it overrides the system-default trial license.
o Perpetual license (or term license). An Autopass license key file that you generate from the HP
Licensing for Software portal. The perpetual or term license allows you to use an authorized set
of PPM Center modules for an authorized period of time. When you install a perpetual or term
license, it overrides the trial license and evaluation license (if available), regardless of how long
the valid period for the perpetual or term license is. For example, if your evaluation license
expires in three months, but your term license expires in two months, when you install the term
license, it overrides the evaluation license and the end date is displayed as that of the term
license.
If your evaluation license or term license expires within 60 days of the product installation, or you
remove the evaluation license or term license within 60 days of the product installation, the system-
default trial license will become effective, until it expires.
The evaluation licenses and term licenses are additive. For example, if different term licenses are
installed with different dates, the capacity of different licenses are added together, and the

expiration dates for all current licenses are displayed the same in the License Administration window
of PPM Workbench, that is, the expiration date for the license that will expire the earliest.
l More flexible license installation options available.
For new PPM Center customers, when installing PPM Center for the first time, you have the following
options:
o If you do not have an evaluation license or a perpetual product license, you can select the No
thanks. I will install the license later. option in the Choose License page of the installation
wizard. A trial license will be generated automatically and activated for you right away, which
allows you to use limited features of PPM Center for 60 days.
Before the trial license expires, if you wish to experience the full features of PPM Center, you can
obtain an Autopass license file from the HP Licensing for Software portal and install the license
file by using either the Administration Console the newly introduced tool.
o If you have an evaluation license or perpetual product license , you can install the Autopass
license key file using one of the following ways:
l In the Choose License window during PPM Center 9.30 installation process, or
l After the installation of PPM Center 9.30, before the trial license expires, install the license
key file by using either the Administration Console the tool.
For existing PPM Center customers with active support contract, you can go to the My Updates
portal (http://support.openview.hp.com/software_updates.jsp), select My Updates, and enter your
SAID (Service Agreement ID) number to get PPM Center version 9.30 Software Updates and new
license key required for the updates. After successful upgrade, to start PPM Server properly, you
must use the tool to install the Autopass license you received from HP.
For more information, see "Installing Autopass License Key File and Viewing License Summary in
Administration Console" on page 322 and "Installing Autopass License Key File Using the
kLicenseInstall Tool" on page 97.
l Simplified product license management. A new Administration Console tool (Administration

Console > Administration Task > License) is added to allow you manage product license easily.
Using the Administration Console tool, you can,

o Install an Autopass license file without having to stop and restart the PPM Server
o View a summary of licenses installed on the PPM Server, including license capacity and expiration
dates
o Remove an Autopass license file easily
Administration Console" on page 322.
l Licenses installed are stored in the PPM Center database, instead of the file system. This makes it
possible for the installed licenses to become effective right away after installation. There is no need
to stop and restart the PPM Server.
l In a clustered environment, you can install an Autopass license on any node of the cluster. The
installed license becomes effective for the entire cluster right away, no need to stop and restart the
node. See "Installing An Autopass License in a Clustered Environment" on page 98.
l After starting PPM Server, the system checks whether either of the following foundation licenses is
enabled:
o Foundation License Up To 25 Users
o Foundation License Over 25 Users
Activating and Generating Autopass License

To activate and generate your Autopass license for the version of PPM Center you purchased,
1. Go to the HP Licensing for Software portal at http://www.hp.com/software/licensing.
2. Click Sign In.
3. Provide your HP Passport credentials and click Sign in.
Note: If you do not have an HP Passport, click Create an account.
4. On the Enter Entitlement Order Number page, enter the Order number found on your Entitlement
Certificate and click Go.

5. Complete the activation process to generate an Autopass license.
The generated Autopass license (a .dat file or several .dat files) will be sent to you by HP.
Installing Autopass License Key File Using the

kLicenseInstall Tool
After you have successfully installed PPM Center, you can install an Autopass license key file by using
the kLicenseInstall tool, with PPM Server started or not started.
To install an Autopass license key file,
1. Obtain and save the license file somewhere on your computer.
For information about obtaining the license key file, see "Key Considerations" on page 36.
2. Open a command prompt.
3. Navigate to the directory and run the following command:
sh ./kLicenseInstall.sh <Autopass_License_File_Path>
where is the location of the Autopass license key file that you
saved.
The license file is installed and becomes effective right away, with a message popping up showing
how many licenses are installed.
Note: You can also install the Autopass license key file using the Administration Console tool. For
more information, see "Installing Autopass License Key File and Viewing License Summary in
Administration Console" on page 322
Installing Autopass Licenses and Viewing License Summary

in Administration Console
The Install License page in the Administration Console allows you to,

l Install an Autopass license key file without having to stop and restart the PPM Server
l View a summary of licenses installed on the PPM Center instance
l Remove a license key
Installing An Autopass License in a Clustered Environment

Starting from 9.30, you can install an Autopass license file on any node of a cluster without having to
copy the license file to each of the remaining nodes. The licenses you installed are stored in the
database instead of the file, which means that licenses are centralized.
However, always make sure that the IP address assigned in the license file matches that of the primary
node in the cluster, otherwise you will receive a “ ”
message.
To install licenses in a clustered environment,
1. Obtain and save the Autopass license key file somewhere on your computer.
2. Install the license key file using the tool or the Administration Console on
any of the nodes in the cluster.
Note: For instructions about installing licenses using the Administration Console, see "Installing
Autopass License Key File and Viewing License Summary in Administration Console" on page 322
Reading Licenses Information Using kLicenseReader

You can use the license reader tool to obtain the information of licenses that are installed on your
machine.
To use the license reader, you should run the following command:

For more information about this command, see "kLicenseReader.sh" on page 527.
Configuring or Reconfiguring the PPM Server

If you configured the PPM Server during installation, it is probably not necessary to reconfigure it unless
your environment or requirements have changed. If you did not configure the server during installation,
configure it now.
You can perform most of the configuration using the procedure described in the next section, "Standard
Configuration" below. In some cases, however, configuration requires custom parameters. For
information about when and how to configure the server using custom parameters, see "Defining
Custom and Special Parameters" on the next page.
The server configuration tool runs in both console and graphical modes. To run in graphical mode in a
UNIX environment, the tool requires an X Window session.
Standard Configuration
This section provides the steps for standard PPM Server configuration and all of the settings required
for a typical PPM Center installation.
To configure the PPM Server:
1. From a DOS or UNIX command line, run the script (located in the
directory) as follows.
o To run the script in graphical mode, type:
sh ./kConfig.sh -i swing
Note: (UNIX only) Run this utility in an X Window session.
o To run the script in console mode, type:
2. Follow the configuration wizard prompts to complete the configuration.

Specify a value for every parameter required for your system environment. To determine the
correct value to provide for a parameter, move your cursor over the parameter name and display
the tooltip text. For more information, see "PPM Center Configuration Parameters" on page 422.
All confidential information (such as passwords) is hidden and encrypted before it is stored.
Do not change default values unless you are sure that the default value does not meet the
requirements of your organization.
Note: Always use forward slashes (/) as a path separator, regardless of your operating system
environment. PPM Center automatically uses the correct path separators when
communicating with Windows, but expects to read only forward slashes on the configuration
file.
Specify any required parameters on the Custom Parameters page.
3. If you have no custom parameters to add, leave Custom Parameters empty. If you require custom
parameters, see "Defining Custom and Special Parameters" below for instructions on how to
specify them.
The configuration wizard writes the configuration parameters to the file and
generates other files that the PPM Server requires.
4. Stop, and then restart the server.
For information about how to stop and start the server, see "Starting and Stopping the
Note: You can also modify parameters directly in the server configuration file, which is
described in "PPM Center Configuration Parameters" on page 422.
If you modify parameters directly, be sure to run the script after you make
your changes.
Defining Custom and Special Parameters

In addition to the standard parameters that HP supplies, PPM Center supports two additional kinds of
server parameters:

l Custom parameters. You can define your own custom parameters.
Custom parameter names must have the prefix .
Example
To add a custom parameter named , in the Key field, type the following:
Parameters that you add to the custom parameters list are accessible as tokens from within the
application. These tokens are in the format .
l Special Parameters.HP has created configuration parameters that you can use in special situations
after you add them to the custom parameters folder. The following table lists these special
parameters.
If you edit the file directly, you must then run the script (located in the
directory) to rebuild the startup files. To implement your changes, you must stop, and
then restart, the PPM Server. After you restart the server, you can run the Server Configuration Report
to view the new or modified parameter values in the file.
For information about the script, see "kConfig.sh" on page 516.
For information about the script, see "kUpdateHtml.sh" on page 537.
Table 4-1. Special configuration parameters
Parameter
Namea Description Sample Value
DB_ If the parameter is specified, then the security PROD

CONNECTION_ identifier (SID) of the database on which the PPM Center
STRING schema resides is requested. It is assumed that the connect
string for this database is the same as the SID. However, this
is not always the case.
If the connect string (for connecting to the database using

SQL*Plus from the server machine) is different than the
database SID, add this parameter and supply the correct
connect string.
NON_DOMAIN_ Windows environment only: To open an FTP session, FTP WAR-FTPD

FTP_ SERVICES servers on Windows typically require the Windows domain
name and user name (in the form ). By

Table 4-1. Special configuration parameters , continued

Parameter
Namea Description Sample Value
default, PPM Center includes the domain name and user name
in an FTP session to a Windows computer.
If you use an FTP server that does not require the domain
name, you can use this parameter to override the default
functionality.
For more information, contact HP Software Support Web site

(hp.com/go/hpsoftwaresupport).
TEMP_DIR This parameter defines a PPM Center temporary directory.

This defaults to a subdirectory of the directory.
If you use this parameter, make sure that you provide the full
directory path.
a. The parameter names listed in the table are shortened versions of the actual names, all of which start with the string
For example, the full name of the parameter is
Enabling Secure RMI (Optional)

To enable SRMI (RMI over SSL):
1. Create a keystore for SSL to use.
You can use the Java keytool application to create a keystore. For information about the keytool
application, see the Oracle documentation online.
Use the keystore password that you use to run keytool to define the (see
"Enabling Secure RMI (Optional)" above).
2. In the file, specify values for the following three parameters:
o
o Set the parameter to point to the keystore file.
o Set the to the keystore password you created in "Enabling Secure RMI
(Optional)" above. This password can be encrypted.
Example

If you ran keytool to create the file relative to the directory, and you
used the password "welcome", ran on host "caboose", and listened on port 1099, your
parameters would look as follows:
Tip: You can create a self-signed certificate.
Configuring Private Key Authentication with Secure Shell

This section provides information on how to configure private key authentication with secure shell
(SSH). The procedure is based on the following assumptions:
l SSH is installed.
l The SSH server is configured for private key authorization.
l The ssh-keygen utility is part of the Cygwin installation. (To get this utility, you must enable the Open
SSH components during Cygwin installation.)
Before you configure private key authentication, do the following:
l Verify that the PPM Center user account can be used to log on to the remote host through the SSH
session.
l Add the RSA certificate information of the remote host to the ssh file, which is located
in the directory.
To add the RSA certificate of the remote SSH host to the PPM Server SSH file:
1. Log on to the PPM Server as the PPM Center user.
2. From the command line, run the following:
The first time you run this command, you are prompted to indicate whether you want to continue.
3. Type
4. Terminate the SSH connection with the remote host.

To set up private key authentication with SSH:
1. Generate the private/public key pair on the PPM Server.
2. Add the generated public key to the remote file.
3. Configure the PPM Server.
The following sections provide the steps required to perform each of these tasks.
Generating the Private and Public Keys
To generate the private/public key pair on the PPM Server:
1. Log on to the PPM Server machine as the PPM Center user.
2. Change directory to the home directory defined for the PPM Center user on the operating system.
3. Run the following SSH utility.
Note: PPM Center only supports the RSA key type, and not the DSA key type.
Do not provide the "passphrase".
4. Press twice.
5. Verify that the directory now contains the (the private
key) and (the public key) files.
Adding the Public Key to the SSH authorized_keys File on the Remote Host
To append the public key to the remote SSH file (remote hosts):
1. Transfer the file to the remote SSH host machine, in the
directory as
Note: On the remote UNIX host, the directory is in the directory. On

Windows, the location depends on the user home directory defined during Cygwin installation.
2. Log on to the remote host with the user ID that the PPM Server is to use to connect.

3. Change directory to the directory and locate the

file.
Note: If the file does not exist, create it.
4. Append the contents of the file to the file, by running the
command:
5. Repeat these steps on the PPM Server to enable public key authentication from the PPM Server
back to itself.
Reconfiguring the PPM Server
To configure the PPM Server:
1. Open the file in a text editor.
2. Add the following server directive to the file.
3. Change to the directory.
4. To update the required startup files, run the script.
5. Restart the PPM Server.
Verify Server Configuration
To verify the configuration:
1. Open a command-line window outside of the PPM Server.
2. Log on to the PPM Server machine as the PPM Center user, as follows.
Note: You should not be prompted for the password. It should log on to the remote host using
the RSA key file.

3. On the PPM Server, log on to PPM Center.
4. From the menu bar, select Administration > Open Workbench.
The PPM Workbench opens.
5. From the shortcut bar, select Environments > Environments.
The Environment Workbench page opens.
6. Click New Environment.
The Environment: Untitled window opens.
7. In the Environment Name field, type the name of the remote host.
8. In the Server section, do the following:
a. In the Name field, type the remote server name.
b. In the Type list, select the operating system type on the remote server.
c. In the Username field, type the user ID you provided in step 2.
d. In the Password field, click the Password ( ) button.
The Enter or Change Password dialog box opens.
Note: The PPM Workbench requires that you provide a password, regardless of whether
the authentication uses RSA.
If authentication with RSA fails, the password you provide here will be used instead to
connect to the remote host.
e. In the Enter New Password and Confirm New Password fields, type the password for the user
ID you provided in step 2.
f. Click OK.
g. In the Base Path field, type the base path.

h. In the Connection Protocol list, select SSH2.
i. In the Transfer Protocol list, select Secure Copy 2.
9. Clear the Enable Client and Enable Database checkboxes.
Note: The user name specifies the user ID to be used to log on to the destination SSH server.
The Environment Checker requires the password. Package line uses the public key file for
authentication.
10. Click Save.
11. At the bottom left of the window, click Check.
The Check Environment window opens.
12. In the left pane, expand the Server folder, and then click SSH2 Server.
13. Click Check.
In the left pane, an icon to the left of the selected server indicates whether the check succeeded or
failed. The right pane displays the details.
Configuring Secure Web Logon (Optional)

This section provides instructions on how to use the built-in Tomcat server and HTTPS to configure
secure logon on the PPM Center logon page, the Administration Console, and the Change Password
page.
To configure your instance to use HTTPS using the Tomcat server:
1. Import your SSL certificate or, to create a simple self-signed certificate for testing, run the
following command:

Note: Your and should be the same. If they differ, you

will get an error along the lines of . For more
information, see Tomcat documentation.
For information about importing a third-party certificate, see "Importing a SSL Certificate from a
Certificate Authority to Tomcat " on the next page.
2. Open the file (located in the directory) and set the
server configuration parameter to
3. Add the following server configuration parameters to the file and set values for each
of them:
Note: The value must be the number plus 363.
(see "HTTPS_WEB_THREAD_MIN" on page 452)
(see "HTTPS_WEB_THREAD_MAX" on page 452)
(see "HTTPS_KEYSTORE_LOCATION" on page 451)
(see "HTTPS_KEYPASSWORD" on page 451)
Note: To get the encrypted password to copy and paste into the file, run the
following command:
For information about setting server configuration parameters, see "PPM Center Configuration
4. Run the script (located in the directory), and then restart the
servers.
Note: For information about how to stop and start PPM Servers, see "Starting and Stopping
the PPM Server" on page 87.
5. (AIX systems only) If you have PPM Servers running on AIX, stop PPM Server, open the

file (located in the directory) and add to it, as

follows:
algorithm="IbmX509"
Importing a SSL Certificate from a Certificate Authority to Tomcat

To import a SSL certificate from a certificate authority to Tomcat for the PPM Center secure web logon
feature, do the following:
1. Create a local Certificate Signing Request (CSR).
a. On the PPM Server machine, generate a private key with an alias name and a specified
keystore file name locally.
The private key is used to decrypt contents that are encrypted by public key sent by CA
authority.
The alias and specify keystore file name will be used for importing certificate later.
keytool -genkey -alias <your_alias> -keyalg RSA -keystore <the path and
your_keystore_filename, such as c:\myKeystore>
Note: When prompted for first and last name, enter the domain of the PPM Server host
machine which is used by the parameter in the file in order to
create a working certificate.
b. On the PPM Server machine, create a certificate signing request.
keytool -certreq -keyalg RSA -alias <your_alias that is the same one used in
step a> -file <the path and your CSR file name such as c:\certreq.csr> -
keystore <full path and your_keystore_filename used in step a>
The CSR file is used to send to CA authority to request certificate.
c. Open your CSR file, copy and paste the contents (usually it starts with begin line and ends with
end line), and then submit to CA.
When CA receives the CSR file containing your public key, they will sign it with their private key
and return the public key and certificate to you in a certificate file.

2. Import the Certificate.
a. Download a Chain Certificate from the Certificate Authority you obtained the Certificate from.
l For Verisign.com commercial certificates, go to

http://www.verisign.com/support/install/intermediate.html
l For Verisign.com trial certificates, go to http://www.verisign.com/support/verisign-

intermediate-ca/Trial_Secure_Server_Root/index.html
l For Trustcenter.de, go to
http://www.trustcenter.de/certservices/cacerts/en/en.htm#server
l For Thawte.com, go to http://www.thawte.com/certs/trustmap.html
Note: Usually the chain certificate has root and intermediate levels. You always import
root level first, then intermediate level. If the chain certificate file is not in DER format,
then you must convert to DER format before you can import.
b. Convert the root CA to DER format.
i. Double click your chain certificate file stored on the PPM Server machine.
The Certificate dialog opens.
ii. Click on the Certification Path tab.
iii. Highlight the root certificate (the certificate issued by the signing authority. Example:
Entrust, Verisign.)
iv. Click View Certificate.
A new Certificate dialog for the root certificate opens.
v. Click the Details tab.
vi. Click Copy to File.
The Export Certificate Wizard opens.
vii. Click Next.

viii. Select DER encoded binary for X.509 (.CER), and click Next.
ix. Create a new filename to store the newly formatted root certificate and store it on the
PPM Server machine.
x. Click Finish.
c. Convert the intermediate CA to DER format.
i. Double click your chain certificate file stored on the PPM Server machine.
The Certificate dialog opens.
ii. Click on the Certification Path tab.
iii. Highlight the Intermediate certificate.
iv. Click View Certificate.
A new Certificate dialog for the root certificate opens.
v. Click the Details tab.
vi. Click Copy to File.
The Export Certificate Wizard opens.
vii. Click Next.
viii. Select DER encoded binary for X.509 (.CER), and click Next.
ix. Create a new filename to store the newly formatted root certificate and store it on the
PPM Server machine.
x. Click Finish
d. Import root CA by running the following command:
keytool -import -alias root -keystore <the path of your_keystore_filename

that used in step a) -trustcacerts -file <path and filename_of_the_root_
certificate file>
Note: HP recommends you use alias (such as ) here.

e. Import the Intermediate CA.
keytool -import -alias intermediate -keystore <the path of your_keystore_

filename that used in step a) -trustcacerts -file <path and filename_of_the_
intermediate_certificate file>
i. Import the signed certificate.
Note: If the signed certificate file is not in DER format, follow the steps in "Importing a
SSL Certificate from a Certificate Authority to Tomcat " on page 109 to convert the
certificate file to DER format before import.
keytool -import -alias <your_alias that is the same one used in step a> -
keystore <full path and your_keystore_filename used in step a> -trustcacerts
-file <path and your_certificate_filename>
Now the pair of the private key and public key is ready for use in your keystore file
permanently.
f. To verify the signed certificate is imported correctly, run the following command:
keytool -list -v -keystore <full path of your_keystore_filename>
You should see three entries, root certificate, intermediate certificate as well as the private
key, public key and signed certificate listed in the output.
3. Configure PPM Center.
a. In the file, add the following parameters:

b. Modify the following parameters:
c. Save the file.
d. Stop PPM Server and run kUpdateHtml.
e. Start PPM Server and test the login using such as

.
Additional Considerations for Configuring Secure Web Logon

This section describes additional steps required to set up secure Web logon if your users access PPM
Center using Internet Explorer (IE) 7.0, or if you have PPM Servers running on AIX.
Enable Transport Layer Security on Internet Explorer 7.0, 8.0, or 9.0
Make sure that users who access PPM Center using Internet Explorer (IE) 7.0, 8.0, or 9.0 enable
Transport Layer Security (TLS) on their browsers. (On the Advanced tab of the Internet Options dialog
box, select the Use TLS 1.0 checkbox.)
Note: TLS is enabled by default in IE 7.0, 8.0, or 9.0.
TSL option enabled by default in IE 8.0

Edit the server.xsl File (AIX Only)
If you have PPM Servers running on AIX, open the file, and add to it,
as follows:
algorithm="IbmX509"
Generating Password Security (Optional)

For password security, PPM Center uses a client/server encryption model based on the ElGamal
algorithm, which generates a public/private key pair. Passwords are encrypted using the server's public
key. Only the server can decrypt the data using the private key. The client application does not have
access to decrypted data.
The public and private keys, which are generated during PPM Center installation, reside in
. Generate the key pair only once, unless you think that server security has been
breached. In that case, regenerate the key pair and reencrypt all passwords.
To regenerate the private and public key pair:

1. From a DOS or UNIX prompt, run the script, which is located in the
directory.
2. If information is not available in , you are prompted for the following information:
o (the server uses this to communicate with the database)
Example
o (username for the PPM Center database schema)
o (password for the PPM Center database schema)
Caution: If you generate new public or private keys, users cannot log on. The old passwords
stored in the database are encrypted using the old key. All of the passwords encrypted
using the new keys do not match those stored in the database.
As the script run completes, the following two key files are placed in the
directory:
l
l
On a Windows system, anyone can read these files. As the system administrator, make sure that non-
trusted users do not have read privilege to the files. On UNIX, the files are read-only for the user running
the script. If the user running the script is not the user who started the server, the server cannot read
the keys and cannot start.
For more information about the script, see "kKeygen.sh" on page 526.
Configuring Solaris and Linux Environments to Use

Deployment Management
PPM Center can connect to a machine on which the environment variable TERM is set to dumb. To
enable Deployment Management to work in Solaris and Linux environments, you must set this
environment variable.

To set the TERM value on Solaris, run:
To set the TERM value on Linux, run:
To set the TERM value on Linux 2.1, run:
Enabling Export to PDF

The PPM Dashboard supports exporting PPM Center portlet content in PDF format in supported
languages. To enable this capability you must do the following:
l (Required) Provide the PPM Dashboard with access to Unicode fonts.
l If your PPM Center instance is to be integrated with an external Web server, you must set the
parameter for the PPM Dashboard as follows:
l If your PPM Center instance is to be integrated with an external Web server the client and
application server are to communicate using HTTPS, you must set the parameter for
the PPM Dashboard as follows:

Note: For information about the PDF-URL and Non-SSL-Port parameters for the PPM Dashboard,
see "Server Configuration Parameters Related to the PPM Dashboard" on page 498.
l If your PPM Center instance is not to be integrated with an external Web server, then set the
parameter for the PPM Dashboard to the same value set for the parameter.
Instructions on how to give the PPM Dashboard access to Unicode fonts are provided the following
section.
Installing Unicode Fonts for Export to PDF

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 Center 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
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
dashboard server configuration
parameter in the file.
The PPM Dashboard looks for a Unicode font in the standard font locations for the operating system.
The following table lists the operating system-specific fonts directories.
Note: Unicode is the default mode that the PPM Dashboard uses. However, if it cannot locate a
Unicode font, it switches to regular mode.
Operating System Fonts Location
UNIX l /usr/openwin/lib/X11/fonts/TrueType
l /usr/X11/lib/X11/fonts/TrueType
l /usr/X11/lib/X11/fonts/Type1

Operating System Fonts Location
HPUX l /usr/contrib/xf86/xterm/fonts
l /usr/lib/X11/fonts/ms.st/typefaces
Linux l /usr/share/fonts/truetype
l /usr/share/fonts/local
Windows l C:\\WINDOWS\\\Fonts
l C:\\WINNT\\\Fonts
AIX /usr/lpp/Acrobat3/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 "PPM Center Configuration
Parameters" on page 422
Enabling IPv6
To enable support for Internet Protocol version 6 (IPv6), add the parameter to the
file and set it to .
Note: If the parameter is not present in the file, the system uses IPv4
by default.
In addition, if you want to specify a literal IPv6 address, make sure you enclose the literal address with "
" and " " characters for the following parameter values:
l
l
l
l
Caution: If you want to specify a literal IPv6 address for the parameter, do not
enclose the literal address with " " and " " characters.

To specify a valid IPv6 multicast IP address, see http://www.iana.org/assignments/ipv6-multicast-

addresses/ipv6-multicast-addresses.xhtml.
Verifying Client Access to the PPM Server

To verify client access to the PPM Server after installation, log on to a client machine as administrator.
To log on to PPM Center as administrator:
1. On a client machine, start a supported browser, and then specify the URL for your PPM Center site.
Note: All PPM Center clients use the same base URL, which is the Web location (top directory
name) of the PPM Server. To obtain the URL, open the file, which is located in
the directory. The URL is the value specified for the parameter.
The PPM Center logon screen opens.
2. In the Username field, type the user name. (Unless you have changed the default username, as
recommended, type admin.)
3. In the Password field, type the password. (Unless you have changed the default password, as
recommended, type admin.)
PPM Center provides this default account for logging on the first time. HP recommends that you
disable the admin account or change the password after you generate accounts for all of your
users.
4. Click Submit.
The PPM Center standard interface opens.
For more information about how to configure licenses and user access, see the
Accessing the JMX Console

You can use the JMX console to view all registered services that are active in the application server and
that can be accessed either through the JMX console or programmatically from Java code.
To access the JMX console, go to the following URL:

No user name or password is required. As long as you have the privilege to access the Administration
Console, you can access the JMX console.
Configuring or Reconfiguring the Database

The settings described in this section are intended to serve as starting values only. Monitor the
database and analyze performance data to fine-tune the settings for your system environment. Tuning
an Oracle database involves an Oracle SYS DBA.
The recommendations provided in this section are based on the assumption that PPM Center is the only
application that uses the database instance. If other applications share the database, adjust the
recommended parameter values accordingly.
Note: If Oracle Database is running over Oracle VM (OVM), HP recommends to enable the Hard
Partitioning feature, also known as CPU pinning.
For more information, see Oracle VM documentation: http://docs.oracle.com/cd/E26996_

01/E18549/html/vm_hardpart.html
Note: For more recommendations on improving PPM Center performance, see the
Database Parameters
This section describes the key Oracle database parameters that can affect PPM Center system
performance. It also provides parameter settings recommended for the PPM Center environment.
For detailed information about the Oracle parameters described in the following sections, see your
Oracle database documentation.
ARCHIVE_LAG_TARGET
limits the amount of data that can be lost and effectively increases the
availability of the standby database by forcing a log switch after the specified amount of time elapses.
A value disables the time-based thread advance feature; otherwise, the value represents the number
of seconds. Values larger than 7200 seconds are not of much use in maintaining a reasonable lag in the
standby database. The typical, or recommended value is 1800 (30 minutes). Extremely low values can

result in frequent log switches, which could degrade performance; such values can also make the
archiver process too busy to archive the continuously generated logs.
Recommended Setting
Set the parameter to to help lower "log file sync" waits.
_B_TREE_BITMAP_PLANS
The parameter enables creation of interim bitmap representation for tables in

a query with only binary index(es).
Recommended Setting
Set the parameter value to . HP recommends that you set this

parameter at the level instead of at the system level. You can use the trigger so that
the setting does not interfere with other application schemas that use the database.
To set the parameter to , run:
This prevents Oracle from unnecessary conversions between ROWID and BITMAPS when running queries.
CURSOR_SHARING
The parameter determines what kind of SQL statements can share the same cursors.
Although this optional parameter accepts the following three values, PPM Center supports only the
values and is not supported.
l This value forces statements that may differ in some literals, but are otherwise identical, to
share a cursor, unless the literals affect the meaning of the statement.
Caution: Setting results in errors during PPM Center project creation.
l This setting causes statements that may differ in some literals, but are otherwise
identical, to share a cursor, unless the literals affect either the meaning of the statement or the
degree to which the plan is optimized.
l This value only enables statements that have identical text to share a cursor. HP
recommends that you set the parameter to . If any other value is used,
PPM Server will try to force the value of this parameter to for all PPM-related databases
transactions.

DB_BLOCK_SIZE
The parameter is used to specify the size (in bytes) of Oracle database blocks. After
the database is created, you cannot change this parameter.
Recommended Setting
Set the parameter value to 8192 (8 KB).
DB_CACHE_SIZE
The parameter value specifies the size (in or ) of the default buffer pool for
buffers with the primary block size (the block size defined by the parameter).
Recommended Setting
Specify a parameter value of at least 500 (expressed in MB).
Note: HP recommends that you set a value for this parameter, even if is set.
FILESYSTEMIO_OPTIONS
specifies I/O operations for file system files.
Available values include , , , and .
Recommended Setting
Set the parameter to to enable both direct I/O and asynchronous I/O
where possible.
_GC_POLICY_TIME
The parameter allows you to control whether or not to disable Dynamic Resource
Manager.
Recommended Setting
Set the parameter to to disable Dynamic Resource Manager, eliminating cluster

related waits.
Note: Consult your Oracle support when you want to use this hidden parameter.

_GC_UNDO_AFFINITY
The parameter allows you to control whether or not to disable Dynamic Resource
Manager.
Recommended Setting
Set the parameter to to disable Dynamic Resource Manager, eliminating

cluster related waits.
Note: Consult your Oracle support when you want to use this hidden parameter.
GLOBAL_NAMES
The parameter value determines whether a database link must have the same name as
the database to which it connects.
Recommended Setting
Set to If you set the value to loopback database link creation fails.
Note: If multiple PPM Center test instances use the same database instance, you must set
to .
To create a loopback database link with this parameter set to
Example 1
To use the database link you created:
Example 2
_LIKE_WITH_BIND_AS_EQUALITY
In situations in which the pattern is expected to match very few rows, you can set the hidden
parameter to The optimizer treats the predicate as though it
were and uses column density as the selectivity instead of a fixed five percent

selectivity factor. The optimizer treats expressions in the format

in the same way it treats expressions in the format
Oracle uses some defaults to estimate column selectivity for the operator, but most of the time
this estimate is not precise and can cause an index path access to be rejected.
Note: Default selectivity varies between releases. For Oracle releases earlier than 9.2.x, the default
selectivity is 25 percent, whereas in 9.2.x and later releases, default selectivity is five percent.
As of Oracle 9i, the parameter also enables equality costing for

expressions in the following format.
Recommended Setting
Set the parameter value to
LOG_BUFFER
The parameter value determines the size (in bytes) of the memory area used to save
transaction change information. When data is committed, the log buffer is flushed to disk. Small log
buffers cause more frequent flushes to disk.
Recommended Setting
For systems with 50 or more concurrent users, set the parameter value to 25 (expressed in MB).
NLS_LENGTH_SEMANTICS
The initialization parameter lets you create and columns using

either byte- or character-length semantics.
Recommended Setting
You must set the parameter to After you do, the columns in
tables use character-length semantics. This means that if, for example, you declare a column as
the column stores 30 characters, and not 30 bytes. In a multibyte character set, this
ensures that adequate space is available.
If you are using a single-byte character set, setting to makes it easier to

transition to a multibyte character set later.

OPEN_CURSORS
Oracle uses cursors to handle updates, inserts, deletes, and result sets that queries return. The
parameter value determines the number of cursors one session can hold open at a given time.
Recommended Setting
Set the parameter value to 1000 or higher.
OPEN_LINKS
The parameter setting affects only Deployment Management. It determines the number of
open database link connections to other databases that can be active at a given time.
Recommended Setting
Set the parameter value to 20.
OPEN_LINKS_PER_INSTANCE
The parameter determines the maximum number of migrateable open

connections globally for each database instance.
Recommended Setting
Set the parameter value to 4.
OPTIMIZER_INDEX_CACHING
The parameter gives the optimizer an estimate of the percentage of

indexes cached in the buffer cache. The default value is 0. At this setting, Oracle does not "expect" any
index to be cached while deciding the best access plan for a query. If you set this parameter to a higher
value, Oracle favors using an index in the `IN-list iterator' and nested loop joins.
Recommended Setting
The range of values of is: 0 to 100. The default value is 0.
For most OLTP system, can be set to 90.
For most PPM Center deployments, set the parameter value to 90.
OPTIMIZER_INDEX_COST_ADJ
The parameter is used to tune optimizer behavior for access path

selection by making the optimizer more or less prone to selecting an index access path over a full table

scan. The lower this parameter value, the likelier it is that the optimizer chooses index scan over table
scan.
The range of values of is 1 to 10000. The default value is 100. With this
default value, the optimizer evaluates index access paths at regular cost. With any other value, the
optimizer evaluates the access path at that percentage of the regular cost. For example, a setting of 50
makes the index access path look half as expensive as with the default value.
For most OLTP system, can be set from 10 to 50.
For PPM Center deployment, = Full Scan Cost / Index Scan Cost (=20/80 *
100 =25).
Recommended Setting
Although there is no perfect OPTIMIZER_INDEX_COST_ADJ value for every PPM Center deployment, HP
recommends that you set this parameter to 25.
OPTIMIZER_MODE
The parameter establishes the default behavior for choosing an optimization

approach for the instance.
Values:
l
The optimizer uses a cost-based approach and optimizes with a goal of best response time to return
the first rows (where = 1, 10, 100, 1000).
l
The optimizer uses a mix of costs and heuristics to find a best plan for fast delivery of the first few
rows.
l
The optimizer uses a cost-based approach for all SQL statements in the session and optimizes with
a goal of best throughput (minimum resource use to complete the entire statement).
Recommended Setting
Set this parameter to .
PGA_AGGREGATE_TARGET
Automatic Program Global Area (PGA) memory management is enabled by default (unless
is explicitly set to 0 or is explicitly set to ).

defaults to 20 percent of the size of the SGA, unless explicitly set.
The parameter value determines the aggregate Program Global Area (PGA)
memory available to all PPM Server processes attached to the instance. This parameter enables the
automatic sizing of SQL working areas used by memory-intensive SQL operators such as sort, group-by,
hash-join, bitmap merge, and bitmap create.
replaces the traditional parameter. Use it with the

parameter set to AUTO.
Recommended Setting
Set the parameter value to a minimum of 450 MB. For very large databases,
you can set the parameter to 1 GB.
PARALLEL_FORCE_LOCAL
controls parallel execution in an Oracle RAC environment. By default, the

parallel server processes selected to execute a SQL statement can operate on any or all Oracle RAC
nodes in the cluster. By setting PARALLEL_FORCE_LOCAL to true, the parallel server processes are
restricted so that they can only operate on the same Oracle RAC node where the query coordinator
resides (the node on which the SQL statement was executed on).
Recommended Setting
Set the parameter value to to avoid parallel operations across the cluster.
PROCESSES
The parameter value determines the maximum number of operating system user processes
that can simultaneously connect to the Oracle database. PPM Center uses a pool of database
connections. When database activity is required, connections are picked from the pool and the
database activity is performed on this existing connection. This process saves the overhead of creating
and cleaning up database connections.
Recommended Setting
Set the parameter value to plus the number of total connections that might be used
( ), times the number of nodes in your server cluster.
Although concurrent usage and usage nature are factors used to determine the connections. If a
PPM Server cluster configuration is used, each PPM Server might use 60 database connections.
For single-server configurations, set the parameter value to (the default). For a PPM Server cluster
configuration with three nodes, set the parameter value to (3 x 60) + (3 x 20) = .

RESOURCE_MANAGER_PLAN
specifies the top-level resource plan to use for an instance. The resource
manager will load this top-level plan along with all its descendants (subplans, directives, and consumer
groups). If you do not specify this parameter, the resource manager is off by default.
You can change the setting of this parameter using the statement to turn on the
resource manager (if it was previously off) or to turn off the resource manager or change the current
plan (if it was previously on). If you specify a plan that does not exist in the data dictionary, Oracle
returns an error message.
Recommended Setting
Set the parameter to (the default value) to disable the resource

manager.
SESSION_CACHED_CURSORS
The parameter specifies the number of session cursors to cache. Repeated

parse calls of the same SQL (including recursive SQL) or PL/SQL statement causes the session cursor for
that statement to be moved into the session cursor cache.
Subsequent parse calls will find the cursor in the cache and do not need to reopen the cursor.
Oracle uses a least recently used algorithm to remove entries in the session cursor cache to make room
for new entries when needed.
The parameter is used to reduce the amount of parsing with SQL

statements that use host variables and with PL/SQL cursors.
If is not set, it defaults to and no cursors will be cached for your session.
(Your cursors will still be cached in the shared pool, but your session will have to find them there.) If it is
set, then when a parse request is issued, Oracle checks the library cache to see whether more than 3
parse requests have been issued for that statement.
If so, Oracle moves the session cursor associated with that statement into the session cursor cache.
Subsequent parse requests for that statement by the same session are then filled from the session
cursor cache, thus avoiding even a soft parse. (Technically, a parse cannot be completely avoided; a
"softer" soft parse is done that is faster and requires less CPU.)
Recommended Setting
Set the parameter value to or a greater value.
The value of must be less than the value of .
After is modified, Oracle needs to be restarted.

SGA_TARGET
The parameter value determines the maximum size of all System Global Area (SGA)
components combined in the instance. If you specify it is not necessary to specify
individual values for SGA components such as
and
Recommended Setting
Set the parameter value to 1.66 GB. If you also set the parameter, its value
must be higher than the value set for .
SHARED_POOL_RESERVED_SIZE
The parameter helps to ensure that a portion of the shared pool

(determined by the parameter) is set aside for large objects. Reserving an area for
large objects helps to ensure that requests for a large number of bytes do not fail as a result of shared
pool fragmentation.
If you want to place an object in the reserved area, make sure that the object is larger than the
value. HP recommends that you use the default value for the
parameter.
Recommended Setting
Set the parameter value to 10 percent of the shared pool (as

determined by the "SHARED_POOL_SIZE" parameter).
SHARED_POOL_SIZE
The shared pool contains shared cursors and stored procedures. The parameter
value determines the size (in bytes) of the shared pool. Larger values can improve performance in
multiuser systems, but they use more memory. Smaller values use less memory, but they can degrade
the performance of multiuser systems.
Recommended Setting
Set the parameter value to at least 350 MB.
_SORT_ELIMINATION_COST_RATIO
For certain restrictive (with good filters specified) and limited (returns few records) searches, PPM
Center uses the FIRST_ROWS_N optimization mode.

If a search such as this also uses SORT on one or more fields returned by the search, Oracle uses the
INDEX on the sorted columns under the FIRST_ROW_N optimization, even if other indexes on supplied
filters may yield to a better execution plan for a SQL statement. This often leads to a less desirable
INDEX FULL SCAN on the index on sorted column.
Recommended Setting
Set the parameter value to 5. This directs Oracle to consider an execution plan with sort
elimination, as long as the plan is no more expensive than five times the cost of the best-known plan
(that uses sort).
WORKAREA_SIZE_POLICY
The parameter value determines whether work areas operate in automatic or

manual mode. If the value is set to AUTO, work areas used by memory-intense operators are sized
automatically based on the PGA memory that the system uses and the target PGA memory set for the
parameter. If the value is set to work areas are set manually and
based on the value of the parameter.
Recommended Setting
Set the parameter value to AUTO.
Granting Select Privileges to v_$session

If you want PPM Center to keep track of the open database sessions it uses, make sure that a public
grant exists on the v_$session dynamic performance table. To do this, connect as SYS to the database
that contains the PPM Center database schema, and then issue the following SQL statement.
grant select on v_$session to public
Note: You typically assign this grant during PPM Center installation or upgrade.
Generating Database Links (Oracle Object Migration)

PPM Center can use database links to communicate with other databases. Usually a database link
created and associated with a particular environment in PPM Center can be used in situations such as
AutoCompleteSQL.
The following are examples of situations in which database links are used:

l Custom object types designed to provide parameter value lists directly from a source or destination
database during Deployment Management activities
l Some Deployment Management Extensions, such as the Extension for Oracle E-Business Suite, to
facilitate Deployment Management activities
You can define database links on an as-needed basis. For each database link you require (this probably
includes a link to the PPM Center database), issue an SQL statement similar to the following in the PPM
Center database schema.
For more information about database links, see:
l
l
l
l Oracle's reference document on the SQL language
Configuring the PPM Workbench to Run as a Java

Applet
This section provides the steps to follow to perform the following tasks:
l Enable the SOCKS proxy feature in PPM Center
l Run the PPM Workbench with secure RMI in place
l Provide users on client machines with the required version of the Java plug-in
(Optional) Enabling SOCKS Proxy

Using the SOCKS proxy feature in PPM Center improves security. With SOCKS proxy enabled, all RMI
connections are routed through a central server so that each and every PPM Workbench is not required

to contact the application server directly. The SOCKS proxy feature also makes it easier to monitor RMI
traffic.
To enable the SOCKS proxy feature in PPM Center:
2. Set the following two parameters:
o
o
For the value, provide the hostname of the

SOCKS proxy server.
For the value, specify the port on the SOCKS

proxy host that accepts proxy connections.
The PPM Server passes the SOCKS proxy configuration forward to the client applet launcher. Users are
not required to configure anything.
To specify a different JRE version in the file, reset the

parameter.
For example:
Running the PPM Workbench with Secure RMI (Optional)

To run the PPM Workbench as a Java applet with secure RMI:
l Specify the complete RMI URL, in the following format, when you start the PPM Workbench:
You can type the RMI URL at the command line or, on Windows, specify it in a shortcut.
Providing Users with the Java Plug-In
The Java plug-in is required to access the PPM Workbench interface. When a user starts the PPM
Workbench, the system checks the client browser for the Java plug-in, and then determines whether
the correct version is installed.

The supported Java plug-in version is specified by the parameter in the

file. If the system cannot find the required version, it directs the user to the Oracle site
where the user can download the plug-in and follow the installer wizard prompts to install it.
Note: HP recommends that you leave the parameter default value.
If users who access the PPM Workbench from client machines cannot access the Oracle Web site to
download and install the Java plug-in, you must download the plug-in and make it available to users
from within the firewall. You can obtain the plug-in directly from the Oracle Software Download site.
Note: Consider restricting PPM Workbench access to users who must perform the kind of
configuration and administration tasks performed through the PPM Workbench.
Using the PPM Workbench: What Users Need to Know

This section provides the information that users require to start the PPM Workbench on client
machines. It also includes information on how to address JVM-related problems that can arise on client
machines. For information on how to set up your Web browser to access the PPM Workbench, see the
guide.
For more information about the PPM Workbench, see the guide.
Installing and Configuring the Java Plug-In on Client

Machines
The contains one parameter that is associated with the Java plug-in. The
parameter specifies the Web location for downloading the cross-platform Java plug-in
installer for Firefox browsers. The default setting for this parameter is
Note: Normally it is not recommended to set this parameter. The XPI is installed if you install JRE.
To download and install JRE, go to
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
However, if needed, you can go to the following address to find the specific web location for
downloading the file for your Firefox browser:

http://www.oracle.com/technetwork/java/javase/autodownload-140472.html
For information about the Java plug-in supported for the current PPM Center version, see the
For information about server configuration parameters, see
"PPM Center Configuration Parameters" on page 422.
Setting the Default Web Browser

To run the PPM Workbench interface as an application, users must specify the default browser setting
in their user profiles.
To set the default browser setting:
1. From the shortcut bar in the PPM Workbench, select Edit>User Profiles.
2. On the General tab, in the Default Browser field, type the full path of the default Web browser.
If access to a URL is required, the PPM Workbench uses the default Web browser.
Starting the PPM Workbench on a Client Machine

To start the PPM Workbench from the PPM Center standard (HTML) interface:
l On the menu bar, select Open > Administration > Open Workbench.
Troubleshooting Tips
l If a pop-up blocker is installed and enabled on the Web browser, the PPM Workbench cannot open.
The user can configure the blocker to enable pop-ups from PPM Center.
l If the user is stuck on Verifying Installation screen or sees the message "Unable to launch the
application", the user probably needs to configure the Java plug-in add-on in your Windows Internet
Explorer browser to allow access to PPM Workbench.
To configure Java plug-in add-on,
a. In the Internet Explorer, click Tools > Manage Add-ons.
The Manage Add-ons window displays.

b. Locate the Java Plug-in 1.7.0 add-on.
The details for the add-on display. If the add-on is disabled, click Enable.
c. Click More Information link in the details section.
d. In the You have approved this add-on to run on the following websites box, type *.
e. Click Close twice.
l When open PPM Workbench in 64-bit Internet Explorer by clicking

Open > Administration > Open Workbench, you are prompted to install Java plug-in 1.7.0. After
installing the Java Plug-in by following the screen instructions, you still receive prompt asking you to
install Java plug-in 1.7.0.
This is because Oracle provides automatic installation kit for 32-bit Java Plug-in 1.7.0 only. To install
the 64-bit Java plug-in 1.7.0, go to Oracle website, manually download and install the 64-bit Java
plug-in 1.7.0.
Troubleshooting Default JVM Problems on Client Machines

If the Java plug-in sets itself as the default JVM for the browser, users can encounter the following
problems in the PPM Workbench:
l The PPM Workbench displays a "class not found" exception error.
l Problems occur because other applications you are using require different versions of the Java plug-
in.
To resolve these issues, make sure that an installed Java plug-in is not specified as the default.
To remove the default browser association to the Java plug-in:
1. Open the Windows control panel.
2. Double-click the Java Plug-in icon.
The Java Plug-in Control Panel window opens.
3. Click the About tab.
This tab lists the Java plug-in that PPM Center uses, as well as any other Java plug-ins installed.

4. Click the Browser tab.
5. Under Settings, deselect the checkbox (or checkboxes) for the installed browser (or browsers).
6. Click Apply.
The Java Control Panel displays a message to indicate that you must restart the browser(s) to
apply your changes.
After you make this change, other applications can use the Java plug-in version they require, and the
PPM Workbench functions correctly.
Tip: If you encounter issues while downloading the PPM Workbench, try refreshing the Applet cache
and deleting the temporary internet files.
What to Do Next
If you plan to perform any of the optional installations described in "Optional Installations" on page 83
(for example, if you plan to install an Deployment Management Extension), perform them now. If you
have completed your installation tasks, test your system. As you do, be sure you understand the system
maintenance tasks you must perform periodically. Those tasks are described in "Maintaining the
System" on page 272.

Chapter 5: Advanced System Configuration
This chapter provides information about installations, integrations, and configurations in addition to the
standard PPM Center setup. The following sections also include information about how to install
optional products such as Deployment Management Extensions and the service packs that are delivered
after the main PPM Center version.
Note: For information on how to integrate the HPPPM Center product Web service component with
external single sign-on systems, see "Implementing User Authentication" on page 203.
l Configuring an External Web Server
l Integrating an External Web Server with a PPM Server
l Configuring a Server Cluster
l Switching Between Stand-Alone and Server Cluster Configurations
Configuring an External Web Server

The following sections provide information about how to configure an external Web server to work with
a PPM Center Server cluster.
PPM Server can run with external Web servers such as Sun Java System Web Server, Microsoft IIS,
Apache HTTP Server, HP-UX Apache-based Web Server, and IBM HTTP Server (IHS). For detailed
information about which Web server versions PPM Center supports, and on which platforms, see the
(Windows) Using an External Web Server for Multiple

Stand-Alone Instances of PPM Center
Because of Windows registry limitations, you cannot use just one Web server for multiple stand-alone
PPM Center instances on a machine running Windows. Integration with an external Web server involves
specifying the worker_file registry directive that points to the file. The

file tells the redirector ( ) where to forward the request.

Redirecting to two different instances does not work because each instance requires different workers
properties. However, a single Windows registry points to only one file.
If you must use an external Web server for multiple stand-alone PPM Server instances, HP recommends
that you either use a UNIX machine to host the Web server, or use a hardware load balancer.
Overview of External Web Server Configuration

PPM Server can run with any of several external Web servers, including Sun Java System Web Server,
Microsoft IIS, Apache HTTP Server, HP-UX Apache-based Web Server, and IBM HTTP Server (IHS).
Note: For detailed information about which Web server PPM Centerversions supports, and on which
platforms, see the
To configure an external Web server, perform the following tasks:
1. Choose an external Web server.
2. Choose an external Web port.
3. Configure a file.
4. (Microsoft IIS and Apache-based servers only) Configure a file.
5. Configure the external Web server.
6. Integrate the external Web server with the PPM Server.
7. (Optional) Enable cookie logging on the external Web server.
The following sections provide details about these tasks.
Choosing an External Web Port

Choose the port through which the external Web server and the PPM Server(s) are to communicate.
Select a port that is not in use on the machine running PPM Center. Later, you identify this port in the
PPM Center file and your file.
Note: If you are integrating with an external Web server, you must set the

parameter on the PPM Server. This port number is then specified in the file
that is used by the jakarta 1 redirector.
Configuring the Workers Properties File

The file stores information about the PPM Server(s), including the machine name,
ports, and load balance setting. The external Web server uses this information to direct traffic to PPM
Center applications, as required.
The following sections describe how to configure the file for:
l Sun Java System Web Server
l Microsoft IIS
l Apache-based servers (Apache HTTP Server, HP-UX Apache-based Web Server, and IBM HTTP Server).
Note: For information on the Web server versions supported, see the
Proceed to the following topics:
l "Configuring the workers.properties File for a Single Server" below
l "Configuring the uriworkermap.properties File on Microsoft IIS and Apache-Based Servers" on

page 142
Configuring the workers.properties File for a Single Server

The "Sample File" on the next page shows the contents of a sample file for a
single-server configuration. Information that pertains to a clustered configuration is commented out.
As you edit the file, keep the following two requirements in mind:
l The worker name must match the name of PPM Center instance defined for the
l For Web servers such as Sun Java System Web Server, you must specify
and (see comments in the following
sample file).

Sample File

For more information about how to configure a server cluster, see "Configuring a Server Cluster" on
page 179.
Configure the workers.properties File
To configure a file:
1. Navigate to the directory and

open the file in a text editor.
2. Set the parameter to
3. For the single server (or for each node in a cluster), configure the following values:
a. Set to the name of PPM Center instance to which this worker connects. This is
the name defined by the server configuration parameter in the
file.
Note: In a clustered setup, each server has its own parameter.
b. Set the parameter to the network address of the machine on which
PPM Center is installed.
Note: If the PPM Center instance runs on the same machine as the Web server, you can
use .
c. Set the parameter to the external Web port (

parameter) to use.
d. Set the parameter to , which is the protocol used to connect to

the remote server.

e. Set the parameter to the load balancing factor used to distribute
load to the PPM Servers.
If all servers can handle approximately the same load, assign "1" to each server. If a server can
handle twice as much load as another server, assign "2" to that more robust server and "1" to
the other server.
4. Set the parameter to .
5. Set the parameter to a comma-delimited list of all

servers in the cluster (as configured in step 3).
Example:
6. (Optional) To enable the JK status page, add a worker of special type “status”
( ), and then add this worker to the list of workers ( ).
Configuring the uriworkermap.properties File on Microsoft IIS and

Apache-Based Servers
The file is used to specify mappings between a given URL (or URL pattern)
and worker name. The following shows the contents of a sample file.

Each line of file represent a single mapping in the format

If the Web server processes a URL that matches then
is used to serve this request. must be defined in the file.
Configuring PPM Center-Supported External Web Servers

This section provides information about how to set up the following external PPM Center-supported
Web servers:
l Sun Java System Web Server
l Microsoft IIS
l Apache HTTP Server
l HP-UX Apache-based Web Server
l IBM HTTP Server
For a list of supported versions, see the document.
Configuring the Sun Java System Web Server

To configure the Sun Java System Web Server to run as the external Web server for the PPM Server:
1. Connect to the Sun Java System administration server and create a new server named "PPM".
This creates the directory. The directory contains two files:

and
2. Stop the PPM Server. (For instructions, see "Starting and Stopping the PPM Server" on page 87.)
3. Place the configured file (see "Configuring the Workers Properties File" on
page 139) in the directory.
4. Copy the plug-in to any directory on the machine that runs the Sun Java
System Web Server.
The Web server must have permissions to read and execute this file.
5. Add the following two lines to the file (the text can wrap, but each " " must

be a continuous line with no spaces):
6. If you are using the 64-bit version of Sun Java System Web Server, do the following:
a. Set the LD_LIBRARY_PATH_64 environment variable to

.
b. Navigate to the directory, open the file, and then add the
following lines to the file:
7. In the file, do the following:
a. Add the following line at the beginning of the "Object" section (that is, after
).
b. Place the following text after the section:
The strings must match.
Note: The attribute specifies the name of the JK worker used to serve requests with
URLs that match the attribute, which is in this case.

Caution: Check the start and end of each line in the and files to make
sure that there are no extra spaces in either of these files.
8. Enable content compression.
For information on how to enable dynamic content compression, see "Enabling Dynamic
Compression On an External Web Server" on page 173.
(Optional) Enable Cookie Logging on the Sun Java System Web Server
To enable cookie logging:
1. Stop the Sun Java System Web Server.
2. In the file, find the line that initializes flex. The line begins with the following text.
3. Append the following string to the end of this line:
The resulting modified line is:
4. Restart the Web server.
Configuring the Microsoft Internet Information Services 7.0 Web

Server on a Windows Server 2008 System
Note: To enable Microsoft Internet Information Services with PPM Center version 9.30, make sure
to select Allowing double escaping as described in step 12 of the configuration process.

The Tomcat redirector plug-in DLL, does not work under 64-bit mode on
Windows 2008 with IIS 7.0. To successfully configure IIS 7.0 on a Windows 2008 system, you must
configure the plug-in to work in 32-bit mode.
Note: The 64-bit . file is for Windows 2003 64-bit.
To configure the Tomcat redirector plug-in DLL to run in 32-bit mode on a Windows Server 2008 system
(64-bit machine):
1. Stop the IIS 7.0 Web Server.
2. Open Server Manager on the Microsoft IIS Web server host and make sure that the ISAPI Filters and
ISAPI Extensions role services are installed.
Note: If you must install the ISAPI Filters and ISAPI Extensions, make sure that you restart
after you install these services.
3. Start the IIS Manager.
4. In the Advanced Settings section for the Default Application Pools, set Enable 32 bit Application
to True.
5. Make sure that you configure the Windows registry for the Tomcat connector (isapi_redirect) as
follows:
For a 32-bit systems:
For 64-bit systems:
6. Create a virtual directory named that points to the IIS scripts directory, as follows:
a. Select Start > Control Panel > Administrative Tools > Internet Information Services (IIS)
Manager.
b. Under your IIS Web server, create a new (or identify an existing) Web site to integrate with the
PPM Server.

c. In your file system, create a new (or select an existing) directory in which to store integration-
related files. In this procedure, this directory is referred to as
Caution: The directory must have run permission.

If you choose to use the Windows Registry instead of using
then you use the branch Wow6432Node for running IIS 7.0
on Windows 2008.
d. Copy the file, file and

file
to the directory you created (or selected) in step c.
e. Right-click the Web site you created (or identified) in step b, and then select Add Virtual
Directory from the shortcut menu.
f. In the first Add Virtual Directory window, do the following:
i. In the Alias box, type the alias name (for example, ).
ii. Use the Physical path multiselect to navigate to and select the
directory path.
Note: An example of this directory is The drive and directory

depend on the IIS root directory configuration. This directory must have run
permission.
7. If you are using NTLM for user authentication, then do the following:
a. Start the Internet Information Services (IIS) Manager and access the Error Pages feature.
b. Right-click error 500, and then select Edit Feature Settings from the shortcut menu.
c. Set Error Responses to Detailed errors.
8. Configure both a file and a file.
9. Configure IIS to load as a filter, as follows:

a. To define registry values for IIS with Apache Jakarta Tomcat Connector (JK):
i. Add the following registry key:
Add a string named and set its value to
ii. Add a string named and set its value to the full directory path for the
file. That is, \
Example:
iii. Add a string with the name and set its value to (For more verbose
logging, options include and )
iv. Add a string with the name and set its value to the directory in which you want
to save your log file. Include the log file name in the directory path (for example,
).
v. Add a string named and set its value to the full directory path for
the file. That is,
\
Example:
vi. Create a file named in the directory
vii. Add a string named to the file and set its

value to the full directory path for the new file. That is,
Example:
b. Open Internet Information Services (IIS) Manager, and then do the following:

i. Select the name of the Web site you created (or identified) in "Configuring the Microsoft
Internet Information Services 7.5 Web Server on a Windows Server 2008 System" on
page 152, and then, in the center panel, double-click ISAPI Filters.
ii. In the Actions pane, click Add.
The Add ISAPI Filter dialog box opens.
iii. In the Filter name box, type a name for the ISAPI filter.
iv. In the Executable box, click the ellipsis button (...), and then navigate to and select the
folder that contains the file.
The ISAPI Filters list displays the filter name.
10. Enable the Tomcat redirector DLL in Web service extensions, as follows:
a. From the Connections panel of Internet Information Services (IIS) Manager, select the Web
server name.
b. In Features View, double-click ISAPI and CGI Restrictions.
The ISAPI and CGI Restrictions window opens.
c. In the Actions pane, click Add.
The Add ISAPI or CGI Restriction dialog box opens.
d. Do the following:
i. In the ISAPI or CGI path text box, provide the full directory path for the
file.
ii. In the Description text box, type a short description of the restriction.
iii. Select the Allow extension path to execute check box.
e. In the ISAPI and CGI Restrictions list, select the restriction you added.
f. In the Actions pane, click Allow.
11. Enable execution of ISAPI filter, as follows:

a. From the Connections panel of Internet Information Services (IIS) Manager, select the Web site
(see "Configuring the Microsoft Internet Information Services 7.5 Web Server on a Windows
Server 2008 System" on page 152).
b. In Features View, double-click Handler Mappings.
The Handler Mappings window opens.
c. Right-click the ISAPI DLL item, and then select Edit Feature Permissions from the shortcut
menu.
The Edit Feature Permissions window opens.
d. Select the Read,Script, and Execute check boxes.
12. Check the Allow double escaping setting is correct by following these steps:
a. Open Internet Information Services (IIS) Manager.
b. Select the name of the Web site you created (or identified) in step b pf step 6 . And then, in the
center panel, double-click Request filtering.
c. Right-click in the center panel and select Edit Feature Settings from the menu displayed.
The Edit Request Filtering Settings window is displayed.
d. Under General, select the Allow double escaping checkbox, as shown in the following figure.

e. Click OK.
13. Restart the IIS service. (Restarting the Web site is not enough. You must restart World Wide Web
Publishing Service from the Services management console.)
Note: After you restart the IIS service, the ISAPI filter does not load immediately. The IIS
service may require a few minutes to establish a connection with PPM Center. Before the
connection is established, your browser may display the error message "HTTP Error 404 - File
or directory not found. Internet Information Services (IIS)".
14. Start the PPM Server(s).
Caution: If your PPM Center instance includes multiple nodes in a cluster configuration, you
must start these nodes one at a time. Make sure that you wait until each node is fully started
before you start the next node.


Server on a Windows Server 2008 System
to select Allowing double escaping as described in step 8 of the configuration process.
To configure the IIS 7.5 Web server on a Windows Server 2008 system:
1. Open Server Manager on the Microsoft IIS Web server host and make sure that the ISAPI Filters and
Manager.
PPM Server.
d. Copy the file, file and

file
to the directory you created (or selected) in step c of step 2.
e. Right-click the Web site you created (or identified) in step b of step 2, and then select Add
Virtual Directory from the shortcut menu.

directory path.

permission.
d. Click OK to close the window.
ii. Add a string named and set its value to
iii. Add a string named and set its value to the full directory path for the
file. That is,
Example:
iv. Add a string with the name and set its value to (For more verbose

v. Add a string with the name and set its value to the directory in which you want
).
vi. Add a string named and set its value to the full directory path for
the file. That is,
Example:
vii. Create a file named in the directory
viii. Add a string named to the file and set its

Example:
i. Select the name of the Web site you created (or identified) in step b of step 2, and then,
in the center panel, double-click ISAPI Filters.
server name.

file.
(see step b of step 2).
menu.
b. Select the name of the Web site you created (or identified) in step b of step 2. And then, in the

e. Click OK.


Server on a Windows Server 2012 R2 System
to select Allowing double escaping as described in Step 7 of the configuration process.
The Tomcat redirector plug-in DLL, does not work under 64-bit mode on
Windows 2012 R2 with IIS 8.5. To successfully configure IIS 8.5 on a Windows 2012 R2 system, you must
configure the plug-in to work in 32-bit mode.
To configure the Tomcat redirector plug-in DLL to run in 32-bit mode on a Windows Server 2012 R2
system (64-bit machine):
1. Stop the IIS 8.5 Web Server.
2. Open Server Manager on the Microsoft IIS Web Server host and make sure that the ISAPI Filters and
3. Start the IIS Manager.
4. Enable 32-bit applications by doing either of the following:
o Change the default value of the application pool :
i. Select Application Pools under your server.
The Appliaction Pools pane is displayed in the center panel.
ii. Right-click in the center panel and select Set Application Pool Defaults from the menu
displayed.
iii. Under General, set Enable 32-Bit Applications to True.
o Change the application pool that your Web site runs under:

i. Select Application Pools under your server.
ii. Right-click the application pool that your Web site runs under and select Advanced
Aettings from the menu displayed.
iii. Under General, set Enable 32-Bit Applications to True.
5. Make sure that you configure the Windows registry for the Tomcat connector (isapi_redirect) as
follows:
For 32-bit systems:
For 64-bit systems:
To configure the IIS 8.5 Web server on a Windows Server 2012 R2 system cluster:
Manager.
PPM Server.
d. Copy the following files to the directory you created (or selected)
in step c of step 2:
l The and files (located in the

directory

l The file under the

directory
e. Right-click the Web site you created (or identified) in step b of step 2, and then select Add
Virtual Directory from the shortcut menu.
directory path.

permission.
d. Click OK to close the window.
In 32-bit systems:
In 64-bit systems:

ii. Add a string named and set its value to
iii. Add a string named and set its value to the full directory path for the
file. That is,
Example:
iv. Add a string with the name and set its value to (For more verbose
v. Add a string with the name and set its value to the directory in which you want
).
vi. Add a string named and set its value to the full directory path for
the file. That is,
Example:
vii. Create a file named in the directory
viii. Add a string named to the file and set its

Example:
i. Select the name of the Web site you created (or identified) in step b of step 2, and then,
in the center panel, double-click ISAPI Filters.

server name.
file.
(see step b of step 2).

menu.
b. Select the name of the Web site you created (or identified) in Step b of Step 2. And then, in the
e. Click OK.


Configuring an Apache-Based Web Server

This section provides the steps you use to:
l "Compile a Binary JK Module" below (Do this if, and only if, a precompiled binary does not work on
your system.)
l "Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_jk (IPv4 Only)" on the next page
l "Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy" on page 167
l "Configure IBM HTTP Server Versions 6.1 and 7.0" on page 170
l "(Optional) Generate Redirect URL Based On Server Configuration Parameter BASE_URL" on

page 171
This information applies to Apache HTTP Server, HP-UX Apache-based Web Server, and IBM HTTP Server.
Compile a Binary JK Module
Configuring an Apache-based Web server on UNIX requires a dynamically linkable JK module binary
named In most cases, the
directory contains precompiled binaries of JK for several operating systems.
Before you try to compile the JK module, check this directory to determine whether it contains the
binaries required for your system. Select the mod_jk plug-in based on your operating system, Web
server and CPU type (32 or 64-bit).
If a precompiled binary is unavailable, perform the following steps.
To compile a binary JK module:
1. Download and unpack a source code bundle from the following Web site:
tomcat.apache.org/connectors-doc/index.html
2. Change to the following directory:
3. Run the configuration script, as follows:

The configuration script generates the files for the current machine environment. The
files are required to run the command, as described in the next step.
4. Run the command to build the Apache module that forwards requests from the Apache HTTP
Server to the PPM Server using the AJP13 protocol.
Note: For more details on how to recompile the connector, go to the following Web site:
tomcat.apache.org/connectors-doc/index.html
Enabling Content Compression
Configuring an Apache-based Web server also involves enabling dynamic content compression. For
information on how to enable content compression, see "Enabling Dynamic Compression On an External
Web Server" on page 173.
Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_jk (IPv4 Only)
Note: This section applies to IPv4 only.
Note: The configuration steps provided here for Apache HTTP Server version 2.4 were tested on
Linux, but it should work on Windows as well.
This section provides the procedure for configuring Apache HTTP Server Version 2.2 or 2.4 using mod_jk
to work with PPM Center.
To configure Apache 2.2 or 2.4 using mod_jk for PPM Center:
1. Navigate to or
, and then copy
the file to the Apache module directory (usually ).
Note: The Jakarta Tomcat Connector ( ) is used to connect Apache Web Server and PPM
Center. The Ajp13 protocol keeps an open socket and controls the communications between
PPM Center (its built-in Tomcat component) and Apache.
2. Instruct Apache to load the Jakarta Tomcat Connector ( ). You can use the Apache
LoadModule configuration directives in the file, which is located in

(where is the Apache installation directory).
3. Add the following lines of text to the file:
Caution: If you plan to enable SSL on Apache, then you must also do the following:
o
Add the JkMountCopy On to the virtual host directive in the file.
o
Add the JkMountCopy All to the virtual host directive in the file.
4. Check to make sure that is commented out in the

file.
5. Navigate to the directory, and

then copy the and to the Apache configuration
directory (usually ).
6. Configure the file. (For detailed information and instructions, see
"Configuring the Workers Properties File" on page 139.)
7. Configure the file to specify mappings between a given URL (or URL
pattern) and worker name. (For detailed information and instructions, see "Configuring the
uriworkermap.properties File on Microsoft IIS and Apache-Based Servers" on page 142.
Note: Make sure that the name of the worker mapped to pattern in the
file matches the name of the worker defined in the
file. This worker must also be listed in the directive of the
file.
8. Restart your Apache HTTP Server 2.2 or 2.4 and check to see whether your configuration works.

Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy
This section provides instructions on how to configure an external Web server on both Windows and
Linux systems.
l "Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy on a Windows System" below
l "Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy on a Linux System" on the next
page
Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy on a Windows System
To configure Apache HTTP Server version 2.2 or 2.4 using mod_proxy on a Windows system:
1. Download and install the Apache HTTP Server version 2.2 or 2.4 from the Apache HTTP Server
Project web site (http://httpd.apache.org/download.cgi).
Note: Make sure that you use the MSI installer that includes OpenSSL.
2. Navigate to and open the Apache server

configuration file in a text editor.
3. In the file, uncomment the following lines:
4. Add the following line to the file:
5. Save and close the file.
6. Configure SSL for your Apache web server. (For information, see "Configure Apache HTTP Server
Version 2.2 or 2.4 Using mod_jk (IPv4 Only)" on page 165.)
7. Use the following template to create a file named .

Note: Make sure that your correctly conforms to this format. In each
directive section, list each node with IP, PORT, and the respective KINTANA_SERVER_NAME.
For example, for a two-node cluster:
8. Restart the Apache web server.
9. Check your PPM Center file to make sure that all of your base URLs are of the
following type:
Configure Apache HTTP Server Version 2.2 or 2.4 Using mod_proxy on a Linux System
To configure Apache HTTP Server Version 2.2 or 2.4 using mod_proxy on a Linux system:
1. Download and install the Apache HTTP Server Version 2.2 or 2.4 from the Apache HTTP Server
Project web site (http://httpd.apache.org/download.cgi).
2. Download the UNIX source file or .

3. Run the following commands:
4. Configure SSL for your Apache web server. (For information, see "Configure Apache HTTP Server
Version 2.2 or 2.4 Using mod_jk (IPv4 Only)" on page 165.)
To find the Apache installation directory and print the file location, run .
6. Add the following line to the file:
7. Use the following template to create a file named .
Note: Make sure that your correctly conforms to this format. In each
directive section, list each node with IP, PORT, and the respective KINTANA_SERVER_NAME.
For example, for a two-node cluster:

8. Restart the Apache web server.
9. Check your PPM Center file to make sure that all of your base URLs are of the
following type:
Configure IBM HTTP Server Versions 6.1 and 7.0
This section provides the procedure for configuring IBM HTTP Server (IHS) to work with PPM Center.
To configure IHS for PPM Center:
1. Navigate to
and then copy to the IHS module directory (usually ).
Note: The Jakarta Tomcat Connector ( ) is used to connect IHS and PPM Center. The
Ajp13 protocol keeps an open socket and controls the communications between PPM Center
(its built-in Tomcat component) and IHS.
2. Instruct IHS to load the Jakarta Tomcat Connector ( ). You can use the IHS LoadModule
configuration directives in the file, which is located in (where
is the IHS installation directory).
3. Add the following lines of text to the file:

Caution: If you plan to enable SSL on IHS, then you must also add the "JkMountCopy On" virtual
host directive.
4. Navigate to the directory, and

then copy the and to the IHS configuration
directory (usually ).
5. Configure the file. (For detailed information and instructions, see
"Configuring the Workers Properties File" on page 139.)
6. Configuring the file to specify mappings between a given URL (or URL
pattern) and worker name. (For detailed information and instructions, see "Configuring the
uriworkermap.properties File on Microsoft IIS and Apache-Based Servers" on page 142
Note: Make sure that the name of the worker mapped to pattern in the
file matches the name of the worker defined in the
file. This worker must also be listed in the directive of the
file.
7. Restart your IBM HTTP Server to see whether your configuration works.
(Optional) Generate Redirect URL Based On Server Configuration Parameter

BASE_URL
If you enable reverse proxy, you would also need to enable generating correct redirect URL to avoid
potential http redirection issues.
To enable generating redirect URL, set the server configuration parameter

in to (default).
Setting the parameter to enables the

SchemeBasedRedirectFilter. The SchemeBasedRedirectFilter generates a correct redirect URL by
adding the BASE_URL value as prefix to the redirect URL, such that every redirect URL starts with
scheme
( ) and the same base URL, and then sends to the correct target.
If the parameter is not present in , the system would treat it as a condition by

default.

If you do not use https or reverse proxy, you can disable the SchemeBasedRedirectFilter by setting the
parameter to .
Enabling Secure Sockets Layer on an External Web Server

To enable Secure Sockets Layer (SSL) on the Web server:
1. Generate a certificate signing request (CSR) for the server on which you plan to install the SSL
certificate.
To do this, use the software that your external Web server provides. If you do not know what
software your server uses, contact the Web server vendor for that information.
2. Submit the CSR to a certificate authority (such as VeriSign).
Note: It may take several days for the certificate authority to validate the company.
3. After you obtain the SSL certificate, install it on your Web server.
4. Contact your Web server administrator or Web server vendor to help you enable SSL on the Web
server.
5. If your external Web server or hardware load balancer uses SSL, open the file and
change the server configuration parameter to
Note: By default, the HTTPS typically runs on port 443 on the Web server. If you use a port
other than 443, you must specify the port number in the
6. Restart the Web server.
Note: If you enable SSL on IBM HTTP Web Server, the "JKMountCopy On" virtual host directive must
be included in the file. For more information, see "Configure IBM HTTP Server Versions
6.1 and 7.0" on page 170.

Enabling Dynamic Compression On an External Web Server

Wide area networks (WANs) often have both low bandwidth and high latency (delays in network data
processing), which significantly degrade network performance. Users who access applications over a
WAN experience poorer response times than users who access the same applications through a local
area network (LAN).
PPM Center leverages application content compression to minimize the performance overhead imposed
by operating in a WAN environment. Rather than compress content within the application code, PPM
Center uses the compression capabilities of both the Tomcat Web container and the compression
capabilities in third-party Web servers (Microsoft Internet Information Services, Apache-based Web
server, or Sun Java System Web Server).
If you deploy PPM Center without an external Web server, the application content is compressed by
default, and no additional configuration is required. If, however, you deploy an external Web server as
the Web tier, then you must enable compression for that Web server. Otherwise, application content is
delivered uncompressed, which results in poor response times for users over the WAN.
Enabling Dynamic Content Compression on Microsoft Internet Information Services 7.0

and 7.5
To enable HTTP compression of dynamic content through the Microsoft Internet Information Services
(IIS) 7.0 (or 7.5) Manager console:
1. Open the IIS Manager window and navigate to the level you want to manage.
2. In Features View, double-click Compression.
3. On the Compression page, select the box next to Enable dynamic content compression.
4. Click Apply in the Actions pane.
For more information, see Enable HTTP Compression of Dynamic Content (IIS 7), which is available on the
Microsoft TechNet Web site.
Enabling Dynamic Content Compression on Apache-Based Web Servers
This section provides information on how to enable dynamic compression on an Apache-based Web
server that either has been compiled with the module enabled or that can load the
dynamic module. Apache Web server installation documentation provides instructions on how to enable

modules within the application server. If is not loaded in Apache, the following steps
cannot enable content compression.
To enable compression of dynamic assets on an Apache-based Web server:
2. Add the following to the file.
Enabling Dynamic Content Compression on Sun Java System Web Server
To enable compression of dynamic assets on Sun Java System Web Server:
1. On the machine running the Sun Java System Web Server, navigate to the
directory, and open the file.
During the initial Sun Java System Web Server configuration, installation of jk_service required
that the following text be added to the file (after ).
2. Modify that text, as follows.

Creating an SSH Tunnel for External RMI Server (Optional)

You can make an external RMI server outside the firewall available through RMI port forwarding. This
applies to both normal RMI ( ) and secure RMI ( ).
To port forward RMI,
1. Create an SSH tunnel from the public server to the PPM Server.
a. Run the following command on the public server:
where,
is the available port on the public server;
is the IP address of your PPM Server;
is the available port on your PPM Server;
is the user account that you want to use to access your PPM Server.
For example,
b. Enter the password for when prompted.
c. Wait until the tunnel is successfully established.
2. With the tunnel open, add the new parameter to the file if it is not
present:
3. Save the server.conf file and run the kUpdateHtml.sh script (located in the
directory).
5. You can now access PPM Workbench from PPM Center.
6. On the public server, press Ctrl+C to close the tunnel when you no longer need it.

Note: This does not change the RMI URL used when opening the PPM Workbench via Java webstart.
Integrating an External Web Server with a PPM Server

To integrate an external Web server with the PPM Server, perform the following tasks:
For information about how to do this, see "Starting and Stopping the PPM Server" on page 87.
2. Set the server configuration parameter values.
3. Validate the integration.
The following sections provide the steps you use to set the parameters and verify the
integration.
Setting the External Web Port
To set the external Web port:
1. Back up the file.
Caution:
Because the backups you create contain sensitive information such as cryptographic keys and
payload data, HP strongly advises that you protect the backups themselves. Oracle Advanced
Security provides transparent data encryption of data stored in the database, the encryption
of disk-based backups of the database, and network encryption for data traveling across the
network between the database and client or mid-tier applications. It also provides a suite of
strong authentication services to Oracle Database.
To use Enterprise User Security in Oracle Database Enterprise Edition, you must license Oracle
Internet Directory (OID). If you need to use stronger authentication alternatives for enterprise
user security, you must license Oracle Advanced Security and the Oracle Internet Directory
(OID). For more information, see the release notes for your Oracle software

3. Add and set it to the port number in the

file.
4. Change to the base URL of the external Web server.
Note: If your external Web server or hardware load balancer uses Secure Sockets Layer (SSL),
you must change the BASE_URL parameter value to
By default, the HTTPS runs on port 443 on the Web server. If you use a port other than 443,
you must specify that port number in the BASE_URL (
).
6. Run the script.
For more information about the parameter, see "PPM Center Configuration Parameters" on
page 422. For more information about the script, see "kUpdateHtml.sh" on page 537.
Verifying the Integration
To verify the integration between the external Web server and the PPM Server:
1. Start the external Web server and check for errors.
2. Start the PPM Server and check for errors.
3. In a supported browser, open the page

(You must use the complete path.
Specifying only does not work.)
Note: For information about how to start the PPM Server, see "Starting and Stopping the
PPM Server" on page 87. For information about supported browsers, see the
Troubleshooting External Web Server Configuration
If HTTP errors occur when you try to log on to PPM Center, do the following:

1. Gather level logging information for the Web server.
2. Gather level mod_jk logs.
3. Check to make sure that Tomcat connector the plug-in is being loaded:
o Review the plug-in log file.
o Review the operating system logs (for example, Event Viewer on Windows systems).
o Enable debug level logging for the plug-in.
4. If plug-in logs are not generated, check to make sure that the HTTP listener (SSL) port is
configured correctly. (You can check this configuration from the Administration Console.)
5. Review PPM Center logs to see if the PPM Server is receiving requests.
6. (Sun Java System Web Server only) Check to make sure that Java is disabled in the Sun Java
System Web Server console.
Note: By default, Sun Java System Web Server is configured to process JSP files. Because of
this, HTTP requests are not redirected to PPM Center.
7. If PPM Center does not receive requests from the Web server, try to access PPM Center directly
using the HTTP port to isolate the issue. (The HTTP port number is the value assigned to the
parameter in the file.)
Troubleshooting: Exporting PPM Dashboard Pages in PDF Format
If, after you integrate an external Web server with your PPM Center instance, you find that you cannot
export PPM Dashboard pages in PDF format, do the following:
1. From the PPM Center standard interface, open the Administration Console.
2. Specify values for the following PPM Dashboard-related parameters:
o
o

The parameter specifies non-SSL port number for the PPM

Dashboard to use. The parameter specifies the PPM Dashboard URL for PDF
files. (You can configure this as localhost.)
Note: For information about how to open the Administration Console, see "Opening the
For information about how to set parameter values in the Administration Console, see
"Modifying Parameters from the Administration Console" on page 297.
For information about dashboard configuration parameters, see "Server Configuration

Parameters Related to the PPM Dashboard" on page 498.
For information about how to add a server configuration parameter to your PPM Center
instance, see "Modify Server Configuration Parameters Not Listed in the server.conf File" on
the next page.
Configuring a Server Cluster

This section provides the following information about server clustering in the PPM Center environment:
l Server clustering overview
l Creating a shared folder
l Required configuration parameter settings
l Server clustering configuration on a single machine and multiple machines
l Starting and stopping servers in a cluster
l Validating the cluster configuration
Overview of Server Clustering

Before you begin to set up a PPM Server cluster, review the information provided in "System Overview"
on page 19, particularly "Server Cluster Configurations (Recommended)" on page 24. The concepts
described in that section are key to understanding configuring server clusters.

KINTANA_SERVER_NAME and the <PPM_Home >/server directory
A PPM Server consists of the common code located in the directory, as well as the directory
of files that make up the actual PPM Server. These are separate directories in the
directory.
are the individual PPM Servers that comprise a server cluster. Each node in a cluster requires a
separate directory in the directory. The directory names are the server names,
and you configure these in the file with the parameter. Each
server directory in must have a corresponding defined in
, all with the same assigned value.
Note: Server directories cannot contain spaces, commas, or other non-alphanumeric characters,
except for hyphens (-) or underscores (_). For example, is a valid name, but
is not.
@node Directive in the server.conf File
The directive in the file (that is, alone on a line) tells the PPM Server that the
server configuration parameters listed after an are specific to one node in the cluster. You must
specify one directive for each server in your cluster. Parameters displayed before the first
are common to all servers in the cluster.
Caution: If you plan to deploy multiple nodes as a cluster on a single host machine, make sure that
each node has its own dedicated ports (HTTP, RMI, SRMI, and so on) that do not conflict.
Modify Server Configuration Parameters Not Listed in the server.conf File
The KNTA_SERVER_PARAM_DEF_NLS table contains all of the server configuration parameters and their
default values. "Using the Server Configuration Utility to Modify Server Configuration Parameters" on
page 424 provides descriptions of all of the parameters in the KNTA_SERVER_PARAM_DEF_NLS table.
The file contains a subset of the server configuration parameters in the KNTA_SERVER_
PARAM_DEF_NLS table. If a configuration parameter exists in the file, the value specified
for it there supersedes the default value for the parameter in the KNTA_SERVER_PARAM_DEF_NLS
table.
If a server configuration parameter exists in the KNTA_SERVER_PARAM_DEF_NLS table but not in the
file, and you want to change the value of that parameter, you must add it to the
file.

To change the value of a server configuration parameter that exists in the KNTA_SERVER_PARAM_DEF_
NLS table, but is not in the file:
1. Stop all the nodes in the cluster.
2. Navigate to the shared folder that contains the file, and open the file in a text editor.
3. Do one of the following:
o To add a parameter that is to be common to all nodes in the server cluster, type the parameter
name and value before the first directive.
o To add a parameter that is to be specific to one node, type the parameter name and value
under the directive for that node.
Use the parameter name as it is listed in "Using the Server Configuration Utility to Modify Server
Configuration Parameters" on page 424. Make sure that you include the prefix
" " in the parameter name. For example,
5. Run the script on each machine.
Note: If the servers in a cluster are running on multiple machines, then each section requires
the directive.
Synchronizing Clocks on Machines Participating in the

Server Cluster
Check to make sure that the clocks on all machines that host the nodes included in your server cluster
are synchronized to within one second. If the clocks on different machines are not synchronized, use a
time-synch service to synchronize them. For instructions on how to do this, go to the NIST Internet Time
Service (ITS) page of the National Institute of Standards and Technology (NIST) web site
(http://www.nist.gov/index.html).

Server Parameters Required for Server Clustering

The table below lists some of the server configuration parameters that you must define in
a server cluster, based on the type of clustering used. For more information about these parameters,
see "PPM Center Configuration Parameters" on page 422.
Table 1. Server configuration parameters affected by clustering
Hardware Load
External Web Balancer,
Server, Single External Web Server, Multiple
Parameter Namea Machine Multiple Machines Machines
KINTANA_SERVER_NAME X X
ATTACHMENT_DIRNAME X X
BASE_PATH X X
The specified for

the core server is inherited
by all of the sections.
Specify this in an individual
only if the value is
different for that specific
instance.
ORACLE_HOME X X
BASE_URL X X X
BASE_LOG_DIR X
HTTP_PORT X X X
EXTERNAL_WEB_PORT X X
RMI_URL X X X
TRANSFER_PATH X X
PACKAGE_LOG_DIR X X
REPORT_DIR X X
REQUEST_LOG_DIR X X

Table 1. Server configuration parameters affected by clustering, continued

Hardware Load
External Web Balancer,
Server, Single External Web Server, Multiple
Parameter Namea Machine Multiple Machines Machines
a. The parameter names listed in the table are shortened versions of the actual names, all of which start with the string
com.kintana.core.server. For example, the full name of the parameter is
PPM Center uses Tomcat clustering technology, which enables you to set up a PPM Server cluster in
various configurations. For example, you can have multiple nodes on the same host (server machine)
and cluster them together. Or, you can have one or more nodes on one host and other nodes on a
different host, all participating in the same server cluster.
In addition to the server configuration parameters listed in Table 1, successful server cluster setup
requires that you define additional node-specific parameters to specify ports (Table 3) and cluster-
specific (Table 2) server configuration parameters.
For the cluster-specific server configuration parameters listed in Table 2, you must set the same values
for all nodes in the cluster.
Table 2. Required cluster-specific parameters
Parameter Description
MULTICAST_ IP address used for exchange of heartbeat messages, cache synchronization, and
IP cluster communication. This must be between 224.0.0.0 and 239.255.255.255.
The IP address you specify for MULTICAST_IP must include the text string "http://".
MULTICAST_ Multicast port used by PPM Center's cluster monitor. You can specify any unused port
PORT number that does not conflict with other multicast ports.
MULTICAST_ Used by JBoss to uniquely identify a cluster of nodes. Also used by the PPM Server to
CLUSTER_ monitor the status of all nodes in a cluster.
NAME
Example
Note: Do not configure two clusters with the same name running on the same
subnet.
Caution: The value you specify for

MULTICAST_CLUSTER_NAME must include the text string

Table 2. Required cluster-specific parameters, continued

mcast_port Port used by PPM Center through the JGroups channel to synchronize cache messages
across nodes in a cluster. This parameter is in the file and is hardcoded to
46545.
Clustering requires that you define a specific set of ports for each node in the cluster. If the cluster
consists of multiple nodes on same host, you must specify unique port values for each node to prevent
port collisions. Table 3 lists the server configuration parameters you use to specify these ports.
Table 3. Required node-specific parameter for multiple nodes on a single host
Port Parameter Description
APP_SERVER_ Protocol listening port for the JBoss Application Server UIL2 service. For a
UIL2_BINDING_ PPM Server in a server cluster, specify a port that is unique for the node in the
PORT cluster.
Note that if that two nodes in the same server cluster are on separate machines, and they have the
same port settings, no port conflicts occur.
Server Cluster Example
The figure below shows an example of a server cluster that includes two host machines, Server1 and
Server2. Server1 hosts NodeA and NodeB. Server2 hosts NodeC and NodeD. You want to create a server
cluster between Server1 and Server2 and include all the nodes (NodeA, NodeB, NodeC, and NodeD) on
both servers. As long as the ports assigned to each PPM Server do not overlap with any port set
assigned to another PPM Server on the same host, no port conflicts occur.

Example server cluster configuration
The file used for this server cluster might look as follows:

Creating a Shared Folder for the server.conf File

To implement a server cluster that includes nodes hosted on different machines you must have a
shared folder for the server configuration file ( ). In addition to giving all nodes in a cluster
access to the same file, the shared folder simplifies maintenance of the
file.
The shared folder described in this section is also required to give users access to the Administration
Console interface after your PPM Center instance is deployed. For information about the Administration
Console, see "Tools in the Administration Console" on page 281.
Caution: If you plan to configure the server cluster on multiple machines, keep in mind that the
nodes in the cluster must all run on the same operating system. Shared access to the
file does not support mixed operating systems.
The following sections provide instructions on how to prepare the shared folder on both Windows and
UNIX systems.
l "Preparing a Shared Folder for server.conf on a Windows System" on the next page
l "Preparing a Shared Folder for server.conf on a UNIX System" on the next page
l "High-Level Steps for Server Cluster Configuration" on page 188
l "External Web Server, Single Machine" on page 189

l "External Web Server, Multiple Machines" on page 190
l "Hardware Load Balancer, Multiple Machines" on page 193
Preparing a Shared Folder for server.conf on a Windows System

To prepare a shared folder for the file on Windows:
2. Attach the shared folder to each machine that is to host PPM Center.
3. If you plan to host multiple PPM Server clusters (instances) under the same account on a single
machine, do the following. Otherwise, proceed to step 4.
a. Using a text editor, create a file named " ", and add to it the following
text:
b. Save the file in the directory and close the file.
4. Open the Control Panel and define an environment variable named for an
account that is to run PPM Center nodes on Windows. The value of the environment variable is the
location of the shared folder.
Caution: Make sure that you use Universal Naming Convention (UNC) notation (
or ) to specify the
location of your shared folder.
Preparing a Shared Folder for server.conf on a UNIX System

To prepare a shared folder for the file on UNIX:
2. Mount the shared folder to each machine that is to host PPM Center.
3. If you plan to host multiple PPM Server clusters under the same account on a single machine, do
the following. Otherwise, proceed to step 4.

a. Using a text editor, create a file named " ", and add to it the following
text:
b. Save the file to the and close the file.
4. In the file of the account that is to run PPM Center, add the following line:
High-Level Steps for Server Cluster Configuration

Server clusters are configured using the file. You can define all of the nodes in a cluster
(cluster-specific and node-specific configuration) in one file, regardless of whether the
nodes are running on a single machine, or distributed on different machines. Using a single
file ensures that each node reflects the correct setting. It also enables scripts such as
to gather information from all the nodes in the server cluster, and not just the nodes that
reside on the machine from which you run the script.
You can use the same file on different machines that host nodes that participate in the
same cluster. If you do, keep in mind that you must change the machine-specific parameters settings in
the file.
To configure a server cluster:
1. Stop the PPM Server. (See "Starting and Stopping the PPM Server" on page 87.
2. If your cluster is to include nodes hosted on different machines, make sure that you have set up a
shared folder. (See "Creating a Shared Folder for the server.conf File" on page 186
3. If you are using an external Web server, do the following:
a. Stop the external Web server.
b. Configure the file to include information for the multiple cluster nodes.
Each node requires an external Web port defined (using the
configuration parameter).
For information about how to configure the file, see "Configuring the
Workers Properties File" on page 139.

4. Configure the server nodes on the file system.
5. Manually configure the server nodes in the file.
The next sections provide the steps you use to configure the following server cluster setups ("Table 1.
Server configuration parameters affected by clustering" on page 182):
l External Web server, single machine
l External Web server, multiple machines
l Hardware load balancer, multiple machines
External Web Server, Single Machine

To set up a cluster with an external Web server on a single machine:
1. Stop the PPM Server. (See "Starting and Stopping the PPM Server" on page 87).
2. Stop the external Web server.
3. Modify the file to include relevant information about the nodes in the
cluster. (See "Configuring the Workers Properties File" on page 139.)
4. Create the directory.
Make a copy of the first server directory (the entire directory) at the same level as the first.
Example:
Note: Use the value specified for the parameter in the

file that corresponds to the subdirectory node for that system.
5. Open the file in a text editor and add an directive for each node.
6. Before the first directive, add the cluster-specific parameters listed in "Table 2. Required
cluster-specific parameters" on page 183.

7. After each directive, do the following:
a. Set values for the parameters listed in "Table 1. Server configuration parameters affected by
clustering" on page 182 (External Web Server, Single Machine column). The values should be
the same for all nodes in the cluster.
b. Add and specify unique values for the parameters described in "Table 3. Required node-
specific parameter for multiple nodes on a single host" on page 184.
For your convenience, the table in "Sample Port Sets" on page 194 lists port set values that you
can use for up to five separate nodes in a cluster. (These are simply here only for your
convenience. You can use any available port numbers you want.)
8. To apply the changes to all the servers in the cluster, from , run
9. If the PPM Server is running in a Windows environment, start it using the Windows service called
"PPM Server " where is the value of the parameter
for the node in the cluster.
10. Generate a new service for the new node, as follows:
a. From run
The configuration wizard starts up.
b. Select Configure Windows Services.
c. Follow the wizard prompts to create the service.
11. To validate the cluster, use the procedure provided in "Verifying Successful Cluster Configuration"
on page 195.
External Web Server, Multiple Machines

In a server cluster, a directory must reside on each machine, each with a server running
against the same database.
To set up a cluster with an external Web server on multiple machines:

1. Install the PPM Server on the first machine in the cluster and configure it so that it is integrated
with an external Web server.
Note: For information about how to configure a machine for integration with an external Web
server, see "Configuring an External Web Server" on page 137. For information on how to
integrate the PPM Server with an external Web server, see."Integrating an External Web
Server with a PPM Server" on page 176.
2. Stop the PPM Server. (See "Starting and Stopping the PPM Server" on page 87.)
3. Stop the external Web server.
4. Make sure that the common directories that the servers use (
and ) are shared.
Note: Set the permissions for the shared directories so that users of each machine in the
cluster can read from and write to them.
5. Modify the file to include relevant information about the nodes in the
cluster. (See "Configuring the Workers Properties File" on page 139.)
6. Modify the file to include an directive for each node in the cluster, including
those hosted on different machines.
7. If the nodes in the cluster are running on different machines, specify the
server configuration directive for each section.
Note: You must specify the and

The rest of the log directories are derived from these four directories.
Consider specifying these before the first so that you do not have to specify them in
each and every section.
On a Windows system, you must use the UNC format. You cannot use the local shared drive
letter. Use forward slashes.
Example

To enable a node to share these directories, you must start the PPM Windows services using
the PPM Center user account that has read and write permission on the shared host.
On a UNIX system, you must NFS-mount the shared directories locally with the same directory
structure.
8. In the file, before the first directive, add the cluster-specific parameters
listed in "Table 2. Required cluster-specific parameters" on page 183.
9. After each directive, do the following:
a. Set values for the parameters listed in "Table 1. Server configuration parameters affected by
clustering" on page 182 (External Web Server, Multiple Machines column). The values should be
the same for all nodes in the cluster.
b. Add and specify unique values for the parameters described in "Table 3. Required node-
specific parameter for multiple nodes on a single host" on page 184. (For your convenience, HP
provides port set values that you can use for up to five separate nodes in a cluster. These port
sets are listed in "Table 5-4. HP-supplied port sets" on page 194.)
10. To apply the changes to all nodes on the machine that are part of the cluster, from
, run
11. After you configure the first server to include all additional nodes, copy the entire
directory from machine1 to machine2, to the defined in the
directive.
12. Zip the file, send it using FTP, and then unzip it at the destination.
13. After you copy the file, change the directory to on the new machine, and then
rename the directory to
The server name must match the value set for the parameter.
Example
The directories on machine1 could be:

The directories on machine2 could be:
8. Put a new license on machine2, as required by the new IP address.
9. Run on both host machines to apply the changes.
10. Start the PPM Server using the Windows service.
In a multiple-machine configuration, you must generate the services on all machines running
Windows.
11. Generate a new service for the new node, as follows:
a. From , run
The configuration wizard starts up.
b. Select Configure Windows Services.
c. Follow the prompts to create the service.
Note: The keys in the security directory are required to read encrypted values in and
the database. The same keys must be present on all nodes in the cluster.
Hardware Load Balancer, Multiple Machines

You can use a hardware load balancer as the front end of a PPM Server cluster configuration. A
hardware load balancer is similar to an HTTP reverse-proxy server and forwards HTTP requests.
All PPM Servers in a server cluster must listen for HTTP requests on a unique port. Each server in the
cluster must have its parameter set to a unique value that does not conflict with other
external applications. You specify this parameter value for all servers in a cluster in the section
of the file.
Note: Sticky sessions are required for hardware load balancing in the PPM Center environment.

Sample Port Sets

The table below lists five port sets that you can assign to the nodes in the file. These are
listed here only for your convenience. You can use any available port numbers.
Table 5-4. HP-supplied port sets
Port Namea Node A Node B Node C Node D Node E
APP_SERVER_UIL2_BINDING_PORT 8093 8193 8293 8393 8493
a. A PPM Server in a single-server configuration is assigned the Node A port configuration by default.
Note: For a PPM Server in a single-server configuration, only a subset of these port definitions is
required.
Starting and Stopping Servers in a Cluster

The procedures used to start and stop the primary node in a cluster are identical to the procedures
used to start and stop the PPM Server in a single-server configuration. (For detailed information, see
"Starting and Stopping the PPM Server" on page 87.)
To start a secondary node, use the argument in the script, as follows.
To stop a secondary node, run the script, as follows:
On Windows, there is one service (called "HP ") per node. If you prefer to use the
Windows shell command line to start nodes instead of using Windows Services, you can use the
script.
If you do not have a script to stop all nodes in a cluster, you can write a script for this purpose. The
following example script for the UNIX environment stops all three nodes in a cluster configuration (all
nodes are on the same machine).

A PPM Server cluster continues to operate as long as at least one node in the cluster is running. If a
node stops, the HP PPM Web server module detects that the node is unavailable and stops sending it
HTTP requests. When the node becomes available again, the HP PPM Web server module detects the
node and sends the requests again.
Note: If you make a change to the file that affects more than one node in a cluster,
you must:
l Stop and restart (one at a time) all the nodes in the cluster.
l Run the script on all machines.
Verifying Successful Cluster Configuration

To verify successful server cluster configuration:
1. If you are using an external Web server, start it and check for errors.
If the server does not start, make sure that the values in the file are
correct. If you have already validated the external Web server configuration, the problem is likely in
this file.
2. Start one of the nodes, and then try to connect to it.
If you cannot connect to the node, check the file and correct any errors you find.
3. Start the remaining nodes in the cluster, one at a time.
4. Use the script to confirm that all server nodes are running.
If a node is not running, check the server log files in for

errors.

In addition, make sure that:
l Multiple users logging on are automatically distributed to all nodes. Use server reports to verify
which users are logged on to which nodes.
l If you shut down a node, users logged on to the other nodes can continue to work. Users logged on
to the shut down node can log on again and continue to work.
l If more than one node in your cluster is dedicated to running services (recommended), and you shut
down a services node, the services that were running on the node start on another services node.
(For more information, see "Services Isolation" on page 30.)
Note: If you have only one services node in a cluster, and it is shut down, the services will not
run because only nodes that handle user traffic are up and running.
Multicast Settings for Server Cluster Configurations
Multicast must be enabled on network components such as network cards, switches, and routers. To
avoid conflicts between cluster environments, consider the following points.
IP Address and Port Usage within a Server Cluster
The following apply to IP address and port usage in a server cluster:
l Each cluster deployment must have values specified for the ,

, and parameters in the file. These values are shared
by all of the nodes in a cluster.
Caution: The IP address you specify for must include the text string
"http://".
To ensure that the multicast port for the server cluster does not conflict with the multicast port
used by JGroups, make sure that the parameter in the file is
sent to port 46545.
l Each cluster must have unique setting. All nodes within this cluster share
the same value for this parameter.
l Each cluster environment must have the parameter value specified in the
file. This value is shared by all of the nodes in a cluster.

Note: The cache multicast port is hard-coded in the file to 46545. Although there is
no need to modify this value, be aware of it, and check to make sure that other multicast ports
do not conflict with it.
IP Address and Port Usage Across Multiple Clusters within a Subnet
The following apply to IP address and port usage across multiple clusters within the same subnet:
l The parameter value must be unique across clusters within a subnet.
l The combination of with any one of the following ports must be unique across
clusters within a network.
o
o
l If the value is shared by multiple clusters within a network, then values for the
and parameters must be unique for multiple clusters within a subnet.
l If the value is unique across clusters within a network, then values for the
and parameters can be duplicated across clusters within a subnet.
l All nodes in a cluster, such as a production cluster, must use the same , and
settings.
l If clusters other than those related to PPM Center are set up, and these use the same multicast
IP/port, the environment may also conflict.
Disabling Nodes from Running Background Services
HP recommends that, if you have a server cluster configured, and there are nodes in the cluster that do
not handle incoming user requests, you disable the nodes from running the PPM Center background
service.
To disable nodes that receive no user traffic from running background services:
1. Stop the nodes.
Note: For instructions on how to start and stop PPM Servers, see "Starting and Stopping the

2. Navigate to the directory, and then open the file in a text editor.
3. Under do the following:
a. To the nodes that are to receive user requests, add the following:
b. To the nodes that are not to receive user requests, add the following:
Note: For information about adding parameters to nodes in a server cluster, see "@node
Directive in the server.conf File" on page 180.
4. Navigate to the directory, and then run the script.
5. Start the nodes.
Tip: Wait for a few seconds between each node startup.
Tip: To restrict services to nodes that receive no user traffic, remove the service node from the
file during external web server integration configuration or remove it from
hard load balancer redirection list.
Detecting Multicast Routing and Configuration Issues for a

Server Cluster
In PPM Center version 9.11 or earlier, if multicast traffic could not pass between two nodes in a server
cluster, the nodes ran in isolation and no warning was issued. The only way to determine whether the
nodes were communicating was to use the JGroups send and receive test utilities.
Starting from version 9.12, PPM Center logs clear warnings in the server logs if multicast traffic has not
been detected from a node after a specified time interval has elapsed, even though the node can be
reached on its JMS connection factory and the PPM_SERVER_INSTANCE table indicates that the node is

running. You can configure the amount of time that must pass before PPM Center logs warnings by
setting the server configuration parameter.
Node behavior is monitored somewhat differently on the

and ports. To provide system administrators with better visibility into
multicast behavior, server logging was improved as follows:
l The (used to monitor the cluster) tracks incoming messages from each node
individually. After a given node (X) is first heard from on the port, PPM Center logs the following
message to the server log just once:
If a node is not heard from on the port, PPM Center logs the following message:
You can disable the multicast monitoring feature by setting the server
configuration parameter to zero or less. HP strongly recommends that you not disable the feature
unless HP Software Support specifically requests that you do so.
Multicast in PPM Center Cluster Environment

There are two multicast channels:
Multicast
Channel Description
Cache port Cache invalidation channel. Hardcoded to port 46545 in . Uses JGroups
46545 protocol.
MULTICAST_ ClusterMonitor channel. Controls background services scheduler. Uses JGroups

PORT protocol.
All channels are on the same .
View Group Memberships
To view group memberships,

l Run the following command on the machine you want to show group membership:
To check total group membership in a cluster, run the command on all physical servers in the
cluster.
You should find that total group membership = node_count x 3.
l Set to and use JMX console.
You should find a new section near the bottom called . Group memberships are in the
attribute in .
View Multicast Routes
To view multicast routes, run the following command:
route print | grep 224
/sbin/route | grep 224
If you see no multicast route on Windows platform, run the following:
route add 224.0.0.0 mask 240.0.0.0 0.0.0.0 METRIC mmm IF nnnn
Which NIC do Channels Bind to on a Multi Network Card (NIC) Machine
l JGroups: Controlled by Java property.
For example, in :
Since PPM Center version 9.12, the NIC that JGroups has bound to is logged at level on
startup.

Since PPM Center version 9.14, JGroups automatically binds to the NIC which has IP address
.
l MULTICAST_PORT channel: Binds to NIC that has multicast route with most preferred (that is, the
lowest) metric.
Set JGroups channels in TCP mode
You can set the two JGroups channels in TCP mode. To switch to TCP mode,
1. Add the following to the server.conf file:
2. Set two ports in for each PPM node:
o First channel:
o Second channel:
To test the multicast setup, you can use the McastSenderTest and McastReceiverTest utilities. For more
details, visit this URL:
http://www.jgroups.org/manual/html/ch02.html. You may also use ssmping utility from
http://www.venaas.no/multicast/ssmping/.
Switching Between Stand-Alone and Server Cluster

Configurations
If you upgrade a stand-alone instance of PPM Center, and you later determine that a server cluster
configuration better meets the needs of your organization, you can switch to a clustered server setup.
Conversely, if you have configured a server cluster for a test or development instance and you
determine that a stand-alone setup would be adequate for your immediate needs, you can transition to
a stand-alone deployment. This section provides instructions for performing both of these transitions.
Note: For information about server clustering, see "Server Cluster Configurations (Recommended)"
on page 24.

Switching from Server Cluster to Stand-Alone Configuration

If you plan to migrate data from a Production instance to a Development, Test, or Sandbox instance,
and you do not want to migrate all the cluster configurations, you can switch from a server cluster to a
stand-alone deployment.
To switch from a server cluster configuration to a stand-alone configuration:
1. Stop all PPM Servers. (For instructions, see "Starting and Stopping the PPM Server" on page 87.)
2. Run the script.
3. After the script run is completed, run the script to start the PPM Server.
Switching from Stand-Alone to a Server Cluster

Configuration
Note: For information about server clustering, see "Server Cluster Configurations (Recommended)"
on page 24.
To switch from a stand-alone to a server cluster deployment:
1. Stop the PPM Server. (See "Starting and Stopping the PPM Server" on page 87.)
2. Make sure that the following server cluster-related parameter is in the file (located
in the directory), and that it is uncommented:
o
4. Complete the PPM Server cluster environment setup as described in "Configuring a Server Cluster"
on page 179.
5. Run the script.
6. After you complete the server cluster setup, follow the steps described in "Verifying Successful
Cluster Configuration" on page 195.

Chapter 6: Implementing User Authentication
l "Overview of Implementing User Authentication" below
l "Integrating with an LDAP Server " on the next page
l "Implementing Web Remote Single Sign-On with PPM Center" on page 210
l "Implementing Generic Single Sign-On with PPM Center" on page 213
l "Implementing Lightweight Single Sign-On Authentication (LW-SSO)" on page 216
l "Integrating PPM Center with CA SiteMinder" on page 222
Overview of Implementing User Authentication

PPM Center uses a framework similar to Java Authentication and Authorization Service (JAAS) to
integrate with pluggable authentication schemes. Integration of PPM Center with CA SiteMinder and
LDAP is supported. This chapter provides information on how to integrate PPM Center with SiteMinder
and LDAP, as well as instructions on how to implement either Web remote single sign-on or generic
single sign-on (SSO) with PPM Center.
The sections in this chapter cover the different types of user authentication methods supported for use
with PPM Center. They provide instructions on how to:
l Integrate PPM Center with an LDAP directory server
l Implement Web remote single sign-on with PPM Center
l Implement generic single sign-on with PPM Center
l Implement lightweight single sign-on authentication (LW-SSO)
l Integrate PPM Center with SiteMinder
Note: The user experience logging off of a PPM Center instance depends on the SSO plug-in
implemented. If a user logs off (clicks Sign Out) of a PPM Center instance that is integrated with

SiteMinder, he is logged out of both PPM Center and SiteMinder, and does not need to close the
browser tab. If a user logs off (clicks Sign Out) of a PPM Center instance that is integrated with a
plug-in that does not support log-off, users signing out from PPM Center are directed to close the
browser window in order to log off.
Integrating with an LDAP Server

You can integrate PPM Center with any LDAP v3-compliant server such as Microsoft Windows Active
Directory. Integrating with an LDAP server helps minimize the setup and maintenance costs associated
with user account management. With an LDAP server, the PPM Server authenticates users directly to
the LDAP directory server, and does not store passwords in the PPM Center database.
Note: This section addresses LDAP directory server integration with a PPM Center. For information
on how to import users from LDAP and on LDAP authentication, see the
In an LDAP environment, the PPM Server authenticates users in the following way:
l The PPM Server binds to the LDAP server using the credentials supplied in the and
server configuration parameters. If passwords are not supplied in the
file, the PPM Server performs anonymous authentication.
l The PPM Server tries to obtain the user name by supplying a search filter to the LDAP server in the
format . The attribute can vary from one LDAP server to another, depending on
the information supplied in the file.
l If the PPM Server obtains a name, it tries to rebind to the LDAP server using the name and the
password supplied by the user.
l If more than one LDAP server has been specified in the parameter, the
PPM Server tries to authenticate against all LDAP servers until it succeeds. If the referral option is
enabled, and the user is not logged on to the primary server, the PPM Server also checks the referral
server for authentication.
Integrating PPM Center with an LDAP Server

To integrate PPM Center with an LDAP server:

1. Collect the following LDAP server information:
o LDAP server URL (the default port is 389), in the following format.
o LDAP base distinguished name (DN) for PPM Center users, in the following format:
o LDAP user account and password. (The PPM Server uses this information to look up users.)
o If you are integrating with SSL-enabled LDAP, collect the following additional information.
l Entire certificate chain. That is,

in the BASE-64 encoded X509 ( ) file format.
l LDAP SSL port number (the default is typically ).
2. From on the PPM Server, run the script.
3. Provide the information that you collected in step 1 for the following server configuration
parameters in the file:
o
o . Specify the comma-delimited list of LDAP URLs that the PPM Server queries (in the
order queried). If you do not specify a port number, the server uses port number 389.
Example
o The parameter in the file is

an encrypted string enclosed with character delimiters.
Example
You may set the parameter in two ways:

l Run the script and provide the plaintext LDAP password when prompted. The
script will write out the file with the entry
encrypted as above. Or,
l If the LDAP password change is the only change you want to make to the file,
then do the following:
A. Run , and provide the plaintext LDAP password when prompted.
B. Paste the encrypted string output into the file

entry enclosed with the character delimiters as in the example above.
o Specify the PPM Center account on the LDAP server. The PPM Server uses
this to bind to the LDAP server.
Examples
l
l
o Specify the base in the LDAP server from which the search is to start. If you do
not specify a value, the server queries the LDAP server to determine the base.
Example
For an SSL-enabled LDAP server, provide the following additional information:
o
o
o
4. On the PPM Server, back up the existing file, which is located in the
directory.
The file is required for user importation and authentication. The

directory contains LDAP attribute configuration files for different types
of LDAP servers.

5. Copy the appropriate file and overwrite the

file in the same directory.
If you are using Microsoft Active Directory, replace the file with the
file.
If you are using a Sun Java System Active Server Pages LDAP server, replace the
file with the
file.
6. If you are integrating with an SSL-enabled LDAP server, do the following:
a. Get the entire trusted certificate chain of the LDAP server (
exported as Base-64 encoded format) from
your LDAP server administrator.
Note: If the certificate chain is not in the correct format, you can import it to
Internet Explorer, and then export it in the correct format.
b. Use the JDK Keytool utility (from jdk 1.4.2 or later) to import the certificate into the
file.
Note: Your system administrator can help you use the JRE Keytool utility to import the
LDAP server certificate chain into the JDK cacerts file.
c. Change to the directory, and run the command:
Note: The default cacerts keystore password is " ". For tighter security, you may
want to change this password.
7. To enable entity ownership and security, do the following:
a. Make sure that the PPM Server is running.
b. Use the Import Users report to import the LDAP users into the KNTA_USERS table on the
PPM Server.

For instructions on how to run the Import Users report, see the
If you are running the Import Users report for the first time, edit the file
and comment out the and
parameters. If you do not make these changes, the import fails and an error message such as
" ", " ", or " " is displayed. The error
occurs because the import tries to validate the data before the data is imported.
Note that you can import users from Org Units that do not have unique names but are of
different hierarchical levels. A Hierarchy column is added to pages or pop-up windows that are
related to Org Units to help differentiate the hierarchical levels of the Org Units you import.
After running the report, check for duplicated user information and accuracy of each of the
users' information in the PPM Workbench.
c. For the LDAP Import? option, click Yes.
Support for Multi-Domain LDAP Import

PPM Center provides support for multi-domain LDAP import through the following two attributes of the
parameter:
l DISTINGUISHED_NAME: Maps to a unique and fixed field of the LDAP server. For example,
.
Note: By default, the attribute maps to of the LDAP

server. If of the LDAP server is changeable, make sure you map
to another field that is unique and fixed on the LDAP server.
Required if using SSO, LDAP, or NTLM as the user authentication mode.
l LDAP_USERNAME: Maps to a user's Logon ID, which is used by the user to log on to the NTLM or SSO
server. For example, = .
Required if using SSO, LDAP, or NTLM as the user authentication mode.
The parameter exists in the following four configuration files under the
directory:

If you do not find the and columns, make sure to add them and
their mapping values into each of the four configuration files manually.
After you run the Import Users report, the Distinguished Name and Logon ID in LDAP fields are added
to the User Information tab of the User window in the User Workbench.
Running the Import Users report populates these two fields with appropriate values.
These two fields are not editable. If the fields are empty or display incorrect values, contact HP
Software Support.
Authenticating Against Multiple LDAP Domains

PPM Center can handle multiple domains during LDAP authentication. To configure this feature, you add
the server configuration parameter to the file.
The values for the parameter include a space-delimited (not comma-delimited) list of
full LDAP URLs. Each LDAP URL must specify a base distinguished name (DN), which is used in place of
the server configuration parameter.
Example of how to set the parameter:
Disabling the LDAP_URL parameter
If you add the parameter to the file, make sure that you comment out
the parameter. The parameter supersedes the parameter so that,
if both are specified in the file, PPM Center uses the value set for
If the URLs provided for do not have a DN value, PPM Center uses the value set for

Note: To specify a space character inside of a URL, use the URL-encoding scheme, and replace the
space with . For example, if you have an organizational unit called My Org Unit, then specify
in the LDAP URL.
For more information about server parameters related to LDAP integration, see "LDAP Attribute
Validating LDAP Parameters

You can use any of several available tools to validate and troubleshoot the LDAP configuration
parameters. For example, Softerra provides Softerra LDAP Browser freeware, which you can download
and install. You can then use the LDAP server information you collected in step 1 to create a new LDAP
server profile. This confirms that the information is correct. On the LDAP browser windows at the top,
blue line, you can view the DN for a specific resource. Use this to determine the base DN as well as the
search filter for the Import Users report. (To download the Softerra LDAP Browser software, go to the
Softerra LDAP Administrator site.)
Implementing Web Remote Single Sign-On with PPM

Center
This section provides information on how to implement Web remote single sign-on with PPM Center.
This implementation is based on NTLM authentication and requires that the PPM Server(s) be integrated
with an external Web server running Microsoft IIS.
Web remote single sign-on works with PPM Center as follows:
1. A user logs in to a Windows desktop.
2. The user accesses PPM Center through the external (IIS) Web server.
3. The user is authenticated through the Windows user account to IIS and the user name is passed to
the PPM Server by way of the HTTP header field.
4. If the user is a valid PPM Center user, the standard interface and PPM Dashboard open.

Requirements for Implementing Web Remote Single Sign-

On
To implement Web remote single sign-on, your system must meet the following requirements:
l PPM Center must be set up with an external Microsoft IIS Web server. For information on how to do
this, see "Integrating an External Web Server with a PPM Server" on page 176.
l To ensure that you have the required access rights, make sure that the system username you use to
log on to PPM Center is same as the account username for the active directory.
l Clients must use Microsoft Internet Explorer to log on to PPM Center. Logon credentials are not
automatically passed from Web browsers other than Internet Explorer (for example, Firefox) when
connecting to IIS.
Setting Up Web Remote Single Sign-On with PPM Center

To configure Web remote single sign-on with PPM Center:
1. Integrate the external IIS Web server with the PPM Server(s).
For information about how to integrate the external Web server with a PPM Server, see
"Integrating an External Web Server with a PPM Server" on page 176.
2. On the PPM Server, do the following:
a. Stop the PPM Server.
b. Open the file in a text editor, and then add to it the following:
Note: For information on how to edit the file, see "PPM Center Configuration
c. Save and then close the file.

d. Run the script.
Note: For information about the script, see "kUpdateHtml.sh" on

page 537
e. Disable Tomcat from authenticating the user. Otherwise, you will get the " " error
message when trying to access PPM Center.
i. Open the following file in an editor (for example, notepad, or VI editor):
ii. Append tomcatAuthentication="false" to the end of the Connector protocol line.
For example,
tomcatAuthentication="false"
iii. In PPM Workbench, create the same Window user account in PPM Workbench and select
NTLM as its authentication mode. Give proper access grants.
iv. In the file, for , add .
v. Restart the PPM Server.
3. On the IIS external Web server, do the following:
a. From IIS Microsoft Management Console, select the default Web site.
b. In the Home pane for the default Web site, scroll to the Security section, and then double-click
Authentication.
c. In the Authentication pane, right-click Anonymous Authentication and select Disable from the
context menu.
d. Stop, and then restart the IIS Windows service.
4. Stop and restart the PPM Server.
For information on troubleshooting issues you may encounter with Web remote single sign-on, see
"Troubleshooting Your Single Sign-On Implementation" on page 214.

Implementing Generic Single Sign-On with PPM Center

This section provides information on how to configure PPM Center to use the generic single sign-on
module to integrate with third-party authentication servers.
Single sign-on works as follows:
1. A user logs on to a portal that has been configured to use a third-party authentication application.
2. The user accesses the PPM Center standard interface through an external Web Server integration
that is part of the logged-in domain.
3. The PPM Server receives the user information through the HTTP header specified in the
file.
4. If the user is a valid PPM Center user, he is granted access to the PPM Center standard interface
and PPM Dashboard.
Requirements for Implementing Generic Single Sign-On

To implement generic single sign-on with PPM Center, your PPM Center system be integrated with an
external Web server (Sun Java System Web Server, an Apache-based server, or IIS).
Setting Up Generic Single Sign-On with PPM Center

To implement generic single sign-on:
1. Regarding the third-party authentication application you plan to use:
a. To configure the third-party application, follow the instructions provided with the application.
b. Verify that the PPM Center user is also a valid single sign-on user and can be authenticated.
2. External Web server:
a. Integrate PPM Center with the external Web server.
For information on how to integrate an external Web server, see "Integrating an External Web
Server with a PPM Server" on page 176.

b. Configure the external Web server to integrate with the third-party authentication application.
For information on how to do this, see the documentation provided with the with third-party
authentication application.
c. Make sure that the authenticated user's HTTP request is forwarded to the PPM Server with the
user ID inserted into the HTTP header specified in the file.
Note: You can find the file in the directory.
3. PPM Server configuration
a. Verify that the file has the following setting.
where is the header your single sign-on system uses to store

the user ID of the authenticated user. For example, CA SiteMinder uses
b. Add the following line to the file.
c. Run the script, which is located in the directory.
4. Stop, and then restart the PPM Server
For information on troubleshooting issues you may encounter with single sign-on, see "Troubleshooting
Your Single Sign-On Implementation" below.
Troubleshooting Your Single Sign-On Implementation

Determine the header information that the single sign-on server is sending.
1. Check the timestamp as follows:
a. Open the file in a text editor, and set the value of the
parameter to
Note: For information on how to edit the file, see "PPM Center Configuration

b. Run the script.
c. Restart the PPM Server.
Note: For details on how to stop and start the PPM Server, see "Starting and Stopping the
d. Log on to PPM Center.
e. Check the timestamp on the PPM Server.
f. Navigate to the directory.
g. Open the file and check the timestamp.
2. Open the file (located in the directory) in a text editor, and add
the following text.
3. Restart the PPM Server by running the following:
The information is written to the file.
4. Enable logging on the single sign-on agent side, and then check the information passed back and
forth. Check for any error messages reported.
Tip: After you check for problems and error messages, you can remove the debugging code
you added to the file in step 2.

Implementing Lightweight Single Sign-On

Authentication (LW-SSO)
You can configure PPM Center to use lightweight single sign-on. Lightweight single sign-on, or LW-SSO,
is an access control method that enables users to log on just once to gain access to the resources of
multiple HP software systems. The applications inside the configured group of HP software systems
trust the authentication, and there is no need for further authentication when switching from one
application to another.
Note: For Information about the system requirements for LW-SSO, see the
document.
Configuration Requirements for LW-SSO Support

Applications that are part of the software group configured for LW-SSO must meet the following
requirements:
l Each application must have a token expiration configured (see "LW_SSO_EXPIRATION_PERIOD" on

page 221). The expiration value must be at least as high as that of the application session expiration
value.
Note: HP recommends that you set the value to 60 (minutes). For an application that does not
require a high level of security, you can configure a value of 300 minutes.
l All applications that participate in the LW-SSO integration use the same GMT time.
l If applications that participate in the LW-SSO integration are required to integrate with applications
in different DNS domains, then multi-domain functionality requires that trusted hosts settings (or
the protectedDomains settings) are configured for each. In addition, you must add the correct
domain in the element of the configuration for each participating application.
l To receive information sent as SecurityToken for URL from other applications, the host application
must have the correct domain specified in the element of the configuration.

LW-SSO Security Warnings

The following security warnings apply to the LW-SSO configuration:
l Confidential initString parameter in LW-SSO. LW-SSO uses Symmetric Encryption to validate and
create a LW-SSO token. The parameter within the configuration is used to initialize the
secret key. An application creates a token, and each application that uses the same
parameter validates the token.
o You cannot use LW-SSO without setting the parameter.
o The parameter is confidential information and must be treated as such in terms of

publishing, transporting, and persistency.
o The is to be shared only between applications that are integrated with each other
using LW-SSO.
o The parameter value must be at least12 characters long.
l Enable LW-SSO only if it is specifically required. Otherwise, leave it disabled.
l Level of authentication security. The application that uses the weakest authentication framework
and issues a LW-SSO token that is trusted by other integrated applications determines the level of
authentication security for all the applications. HP recommends that only applications using strong
and secure authentication frameworks issue an LW-SSO token.
l Symmetric encryption implications. LW-SSO uses symmetric cryptography to issue and validate
LW-SSO tokens. Therefore, any application that uses LW-SSO can issue a token to be trusted by all
other applications that share the same parameter value. This potential risk is relevant
if an application that shares the value either resides in, or is accessible from, an
untrusted location.
l User mapping (Synchronization). The LW-SSO framework does not ensure user mapping between
the integrated applications. Therefore, the integrated application must monitor user mapping. HP
recommends that the same user registry (as LDAP/AD) be shared among all integrated applications.
Failure to map users may cause security breaches and negative application behavior. For example,
the same user name may be assigned to different real users in different applications.

In addition, in cases where a user logs onto an application (AppA), and then accesses a second
application (AppB) that uses container or application authentication, the failure to map the user
forces the user to manually log on to AppB and enter a user name. If the user enters a different user
name than was used to log on to AppA, the following can occur: If the user subsequently accesses a
third application (AppC) from AppA or AppB, then they will access it using the user names that were
used to log on to AppA or AppB, respectively.
l Identity Manager. Used for authentication purposes, all unprotected resources in the Identity
Manager must be configured as nonsecureURLs settings in the LW-SSO configuration file.
l LW-SSO Demo mode. LW-SSO Demo mode restrictions are as follows:
o Use only for demonstration purposes
o Use only in unsecured networks
o Must be used in production. Any combination on the Demo mode with the production mode
must not be used.
LW-SSO Known Issues

The following issues apply to LW-SSO:
l Security context. The LW-SSO security context supports only one attribute value per attribute
name. Therefore, if the SAML2 token sends more than one value for the same attribute name, the
LW-SSO framework accepts only one value. Similarly, if the IdM token is configured to send more
than one value for the same attribute name, the LW-SSO framework accepts only one value.
l Multi domain logout functionality when using Internet Explorer 7. Multi domain logout
functionality may fail when using Internet Explorer 7 and the application is invoking more than three
consecutive HTTP 302 redirect verbs in the logout procedure.
In this case, Internet Explorer 7 may mishandle the HTTP 302 redirect response and display an
"Internet Explorer cannot display the webpage" error instead.
As a workaround, HP recommends that, if possible, you reduce the number of application redirect
commands in the logout sequence.

LW-SSO Limitations
The following limitations apply to LW-SSO authentication:
l Client access to the application. If a domain is defined in the LW-SSO configuration:
o The application's clients must access the application with a fully qualified domain name (FQDN) in
the login URL. For example,
o LW-SSO cannot support URLs with an IP address. For example,
o LW-SSO cannot support URLs without a domain. For example,
If a domain is not defined in the LW-SSO configuration. If a domain is not defined in the LW-
SSO configuration, the client can access the application without a FQDN in the logon URL. Note
that, in this case, a LW-SSO session cookie is created specifically for a single machine without any
domain information, and, therefore, is not delegated by the browser to another, and does not
pass to other computers located in the same DNS domain. This means that SSO will not work in
the same domain.
l LW-SSO framework integration. Applications can leverage and use LW-SSO capabilities only if you
integrate them within the LW-SSO framework in advance.
l Multi domain support
o Multi domain functionality is based on the HTTP referer. Therefore, LW-SSO supports links from
one application to another and does not support typing a URL into a browser window, except
when both applications are in the same domain.
o The first cross-domain link that uses HTTP POST is not supported. Multi domain functionality
does not support the first HTTP POST request to a second application (only the HTTP GET request
is supported). For example, if your application has an HTTP link to a second application, an HTTP
GET request is supported, but an HTTP FORM request is not supported. All requests after the first
can be either HTTP POST or HTTP GET.
o LW-SSO Token size. The amount of information that LW-SSO can transfer from one application
in one domain to another application in another domain is limited to 15 Groups/Roles/Attributes.
(Each item may be an average of 15 characters long.)

o Linking from protected (HTTPS) to unprotected (HTTP) pages in a multi domain scenario. Multi
domain functionality does not work when linking from a protected (HTTPS) to an unprotected
(HTTP) page. This is a browser limitation where the referer header is not sent when linking from a
protected to a non-protected resource.
o Third-party cookie behavior in Internet Explorer
Microsoft Internet Explorer 6 contains a module that supports the "Platform for Privacy
Preferences (P3P) Project", which means that cookies coming from a third party domain are
blocked by default in the Internet security zone. Internet Explorer also treats session cookies as
third-party cookies. These are therefore blocked, which causes LW-SSO to stop working.
To solve this issue and make sure that cookies are accepted, add the launched application (or a
DNS domain subset as ) to the Intranet/Trusted zone on your computer. (In
Microsoft Internet Explorer, select Menu > Tools > Internet Options > Security > Local Intranet
> Sites > Advanced.)
Note: The LW-SSO session cookie is only one of the cookies used by third-party applications
that are blocked.
l SAML2 token
o Logout functionality is not supported if the SAML2 token is used. Therefore, if the SAML2 token is
used to access a second application, then a user who logs out of the first application is not
logged out of the second application.
o The SAML2 token's expiration is not reflected in the application's session management.
Therefore, if the SAML2 token is used to access a second application, then each application's
session management is handled independently.
l JAAS Realm. The JAAS Realm in Tomcat is not supported.
l Using spaces in Tomcat directories. Using spaces in Tomcat directories is not supported. You
cannot use LW-SSO if the Tomcat installation path includes spaces (for example, )
and the LW-SSO configuration file resides in the Tomcat folder.
l Load balancer configuration. A load balancer deployed with LW-SSO must be configured to use
sticky sessions.
l Demo mode. In Demo mode, LW-SSO supports links from one application to another but, because
there is no HTTP referer header, does not support typing a URL into a browser window.

Configuring PPM Center for LW-SSO

Caution: Before you start to configure PPM Center for LW-SSO, make sure that you first read "LW-
SSO Security Warnings" on page 217.
To configure PPM Center support for LW-SSO:
1. Add the parameters described in the following table to the file and assign values to
each.
ENABLE_LW_SSO_UI Use to enable the LW-SSO user interface. Set this parameter to
LW_SSO_DOMAIN Use to specify the LW-SSO domain.
Example:
LW_SSO_INIT_STRING Use to specify the value of the parameter
For information about the parameter, see "LW-SSO

Security Warnings" on page 217.
LW_SSO_EXPIRATION_ The token for validating user logon has an expiration value that
PERIOD determines an application's session validity. Use this parameter to
specify the LW-SSO token expiration period in minutes.
Configure a token expiration for each application that uses LW-

SSO. HP recommends that you set the value to 60 (minutes).
Note: The expiration value must be at least as high as that of

the application session expiration value.
LW_SSO_TRUSTED_DOMAIN Use to specify one or more LW-SSO trusted domains. To separate

multiple domains, use semicolons (;).
Example:
LW_SSO_CLEAR_COOKIE Use to specify that PPM Center must clear the LW-SSO token when
a user logs out of PPM Center.

Note: For security purposes, HP recommends that you always

keep this parameter set to
ENABLE_LW_SSO_WEB_ For integration of PPM Center Tasks with Service Manager RFCs
SERVICE only.
To specify that PPM Center always uses the current user to call
Service Manager Web service, set to
Default:
2. Run
3. Stop, and then restart the PPM Servers.
Integrating PPM Center with CA SiteMinder

You can configure PPM Center to delegate user authentication to CA SiteMinder for both the standard
(Web) and PPM Workbench interfaces. The configuration supports two authentication modes: mixed and
Single Sign-On (SSO).
l "Mixed Mode" below
l "Single Sign-on Mode" on page 224
l "Requirements for Integrating with SiteMinder" on page 226
l "Overview of Integrating PPM Center with SiteMinder" on page 226
l "Configuring PPM Center for Integration with SiteMinder" on page 226
l "Configuring PPM Center Users" on page 229
l "Configuring SiteMinder for Integration with PPM Center" on page 230
Mixed Mode
In the mixed mode configuration, PPM Center users can continue to log on using the PPM Center logon
page. Within the PPM Server, the integrated SiteMinder Authentication Module routes the logon request

to an existing SiteMinder Policy Server for authentication. This mode is referred to as mixed because
you can configure PPM Center to use both SiteMinder and its own authentication simultaneously. In this
case, the authentication mode to be used must be specified in each PPM Center user account.
Integration Architecture for Mixed Mode
In a mixed mode configuration, users log on to PPM Center, and the integrated SiteMinder
Authentication Module passes logon information to the SiteMinder Policy Server for authentication.
To use mixed mode, you must configure the integrated SiteMinder Authentication Module correctly. An
external Web server can be used, but is not required. For information about external Web servers
supported, see the
For PPM Workbench clients, once the user provides a username and password in the logon page, the
user authentication information is passed to the SiteMinder Policy Server for verification. Once verified,
the information is passed to the PPM Workbench applet for automatic logon. After it starts, the applet
communicates directly with the PPM Server.
Figure 1 shows a system diagram of the SiteMinder integration in mixed mode. Figure 2 shows the
integration architecture for mixed mode with the optional external Web server.
Figure 1. SiteMinder integration architecture for mixed mode
Figure 2. SiteMinder integration architecture for mixed mode with optional external Web server

Single Sign-on Mode

In the SSO mode configuration, Web requests are authenticated before being passed to PPM Center,
bypassing the PPM Center logon page. To enable SSO mode, the SiteMinder Web Agent must be plugged
into any third-party Web server software that PPM Center supports, and be configured to communicate
with a SiteMinder Policy Server. The SiteMinder Web Agent intercepts Web requests and checks with the
Policy Server to ensure they are authenticated before passing them to PPM Center.
Note that you cannot use SiteMinder to manage PPM Center application-level authorization for
controlling access to various screens and functions. Application-level authorization is controlled by the
PPM Center security model using security groups, access grants, product licensing, and so on. Therefore,
user accounts must exist in both PPM Center and the SiteMinder Policy Server, but PPM Center does not
have to maintain the associated passwords.
Integration Architecture for Single Sign-On Mode
Single sign-on configuration requires that PPM Center be integrated with an external Web server that
has both the SiteMinder Web Agent and PPM Center Web Server Module installed. (The PPM Center
internal Web server does not support SiteMinder SSO because there is no compatible Web agent or a
suitable API to create one.)
The SiteMinder Web Agent is the single access point for all Web clients. The SiteMinder Web Agent
intercepts all incoming requests and ensures that they are authenticated before passing them to the
PPM Center Web Server module. The requests then proceed to the PPM Server.

For PPM Workbench clients, the SiteMinder Web Agent protects access to the PPM Workbench logon
page. After the user provides a username and password, the authentication information is passed to
the PPM Workbench applet for automatic logon. Once started, the applet communicates directly with
the PPM Server.
Caution: PPM Workbench does not support SSO mode if you start it from the menu bar (select
Administration > Open Workbench on Desktop). However, if PPM Center is launched as an
application, it uses SiteMinder to authenticate. See "Configuring the PPM Workbench to Run as a
Java Applet" on page 131.
The figure below shows a system diagram of SiteMinder integration in SSO mode.
SiteMinder integration architecture for SSO mode

Requirements for Integrating with SiteMinder

The requirements for integrating PPM Center with SiteMinder are as follows:
l An External Web server (required for SSO mode, optional for mixed mode)
l PPM Center Web Server Module
l CA SiteMinder version 6.0 (for both SSO and mixed modes) is installed and functioning correctly
Note:
o For information on how to install SiteMinder, see the product documentation.
o Support for CA SiteMinder version 12.0 is available since PPM Center version 9.22.
l SiteMinder Java Agent API is installed (for mixed mode only)
Overview of Integrating PPM Center with SiteMinder

PPM Center integration with SiteMinder involves the following tasks:
1. "Configuring PPM Center for Integration with SiteMinder" below
2. "Configuring SiteMinder for Integration with PPM Center" on page 230.
Note: The configuration of SiteMinder for integration with PPM Center must be performed by
a SiteMinder administrator.
Configuring PPM Center for Integration with SiteMinder

To configure PPM Center to integrate with SiteMinder:
1. Verify that your PPM Center installation is functioning correctly.
2. If you plan to use mixed authentication mode, do the following:

a. Install the SiteMinder Java Agent API on the PPM Server:
l On a Windows system, copy the file to the

directory.
l On a UNIX system, copy the file to the

directory.
Note: These JAR and DLL files are available on the SiteMinder Developer SDK CD. You
can also find these files in the SDK home directory. The PPM Server automatically
includes the JAR file in its CLASSPATH upon server startup.
b. (Mixed mode only) Install the SiteMinder Agent native code, as follows:
l On a Windows system navigate to the folder, and

then copy the following files to the directory:
Note: Regardless of which directory you place the DLL files in, check to make sure that
you include the directory path in the PATH system environment variable.
l On a UNIX system, set the CA SiteMinder SDK-related variables (such as

and ) so that the system can find the JNI
support library. Next, navigate to the directory,
and then copy the file to the
directory.
Note:
l For information about which variables to set for which platforms, and what values to
set for them, see the guidelines provided in the CA SiteMinder SDK documentation.
l SiteMinder native dll files are available in both 32-bit and 64-bit versions. PPM
Center requires that the version of SiteMinder native dll files be consistent with the
version of JDK software installed on PPM Center, otherwise PPM Center may fail

loading these local native code.
For example, if you use 32-bit JDK software, make sure you use 32-bit version of
SiteMinder native dll files as well.
3. (Mixed mode only) Open the file (located in the

directory), and make sure that the settings for the following
SiteMinder parameters match the corresponding settings in the SiteMinder setup:
o
o
o
o
o
o
o
o
o
o
o
Caution: Pay particular attention to the value set for
If any SiteMinder settings are modified later, you must update the file
to reflect these changes.
4. (Optional, but recommended) Create a backup copy of the PPM Server file.
5. For mixed mode authentication only:

a. To enable selection of either SiteMinder or PPM authentication for PPM Center users, in the
file, modify the authentication mode as follows:
b. Comment out the following parameter setting in the file.
c. Stop, and then restart the PPM Server.
d. From the User Workbench, (from the PPM Workbench shortcut bar, select Sys Admin > Users),
change the users' authentication mode to SiteMinder.
Tip: You may want to set a few user accounts to use the PPM authentication mode to
enable access to PPM Center in the event that the SiteMinder Policy Server is unavailable.
6. For SSO mode only:
a. To enable only SiteMinder authentication for PPM Center users, in the file,
change the authentication mode as follows.
b. In the file, specify the use of SSO as follows.
Note: When both the SiteMinder Web Agent and PPM Center Web server module are
installed on the external Web server, the SiteMinder Web Agent always takes precedence
for requests in the form of
7. Stop, and then restart the PPM Server.
Configuring PPM Center Users

To configure PPM Center users to authenticate using SiteMinder, complete the following steps:

1. Make sure that the usernames for PPM Center users match those used by SiteMinder.
2. Make sure that PPM Center users are set up to use SiteMinder authentication.
Caution: In SSO mode, users whose authentication mode is set to anything other than
SiteMinder are forced to log on to SiteMinder. Users not set up correctly in SiteMinder are
locked out of PPM Center. If this occurs, revert to the file you created in step 4,
and then make the necessary changes to the user accounts before resetting the
authentication mode in the file.
Configuring SiteMinder for Integration with PPM Center

Before you configure SiteMinder for use with PPM Center, make sure that the Policy Server is working
correctly and that the User Directory to be used for PPM Center authentication is correctly configured.
The SiteMinder Test Tool is useful for verifying that the installation is functioning correctly.
Configuring SiteMinder for PPM Center is the same as configuring any other type of protected resource
in SiteMinder. Use the SiteMinder Policy Server User Interface to update the SiteMinder configuration
entities as necessary. For both mixed and SSO modes, four standard SiteMinder configurations should
exist: Host Configuration Object, User Directory, Policy Domain, and Policy.
To configure SiteMinder for integration with PPM Center, perform the following steps.
Caution: These steps must be performed by a SiteMinder administrator.
1. Create a new Web agent.
2. (Mixed mode only) If you plan to use mixed-mode authentication, then after you create a new Web
agent, do the following:
a. Make sure that the 4.x compatibility flag is set.
b. Specify the name of the PPM Server, and a secret password.
c. In the file, set the following parameters:
l Set the parameter value to the PPM Server name.
l Set the parameter value to the secret password you specified.

3. Create a new Web Agent Conf object.
4. Double-click the new Agent Conf Object to open the Properties window.
5. Add the new property value LogOffUri to
Note: PPM Center uses the property to log off users correctly when they log off of
the PPM Center standard interface.
6. Create a realm for PPM Center to protect resource and specify the name of the agent you
created in step 3 for this realm.
7. Configure and enable two rules for the realm (one to enable HTTP on GET, POST, and PUT actions,
and another to enable OnAuthAccept action as the authentication event) with the following
settings:
o Rule 1. Set the Name field to AllowHTTP, the Resource field to /itg/*, and the Action field to
GET,POST,PUT.
o Rule 2. Set the Name field to OnAuthAccept, the Resource field to /itg/*, and the Action field to
OnAuthAccept.
8. Specify URLs for the CookieDomain and CookieProvider parameters in the agent configuration
object for the SiteMinder Web Agent that is to authenticate PPM Center Web requests.
Note: Cookies are used to track session and idle timeouts.
The format used to specify the value for CookieProvider depends upon the external Web server
you use:
o For Microsoft IIS, Sun ONE, and Sun Java System Web servers, use the following format.
represents the host name or IP address where your PPM Center instance is accessed.
o For Apache, use the following format.
It is important to understand that PPM Center reads the information that SiteMinder automatically
injects into the HTTP Request header.

PPM Center relies on the following user attributes:
l For an authenticated user, this parameter specifies the user distinguished name (DN). For
an unauthenticated user, this is the user ID as specified by the user at logon.
l This parameter specifies the session ID of a user who has already

authenticated, or the session ID that is to be assigned to the user upon successful authentication.
l This parameter specifies the user's session ticket.
Note: For configuration details for these and other SiteMinder parameters, see the SiteMinder
documentation.
Applying FIPS 140-2 Compliant Encryption Algorithm

for PPM Center
PPM Center applied the enhanced encryption algorithm to comply with FIPS 140-2 (Federal Information
Progressing Standards 140-2) in the following cases:
l Logging on to PPM Center with Oracle database authentication
l Creating user
l Editing user profile
l Configuring PPM Center database
l Logging on to PPM Center with LDAP authentication
l Importing LDAP users
To apply the FIPS 140-2 compliant encryption algorithm,
2. Unzip the file located in the directory.
3. Copy the following three files from the directory to the
directory:

o
o
o
4. Edit the file located in the directory:
a. Add the following before the existing security providers:
b. Change the sequence numbers of the providers to make sure that the numbers start with 1,
followed by 2, 3, 4, and so on.
c. Add the following two lines after the security provider list:
l
l
d. Comment out the line by adding a number sign

before it.
5. Run the script located in the directory.
Note: Back up the following DB tables before running this script:
o KNTA_USERS
o KNTA_PASSWORD_CHANGES
o KNTA_USERS_INT
6. Run the script located in the directory.
Note:

o As an administrator, you should have the execution privilege to run this script.
o When running this script, you are required to enter the start user id and the end user id to
decide how much data would be processed in a batch. You can get the user ids from the
KNTA_USERS table.
7. Run the script located in the directory to get the

encrypted values for the passwords you set for DB and LDAP.
Note:
o As an administrator, you should have the execution privilege to run this script.
o If your system is not integrated with LDAP, you do not need to run the script for the
encrypted value of the LDAP password.
8. Configure the following three parameters in the file from the directory.
o Set the parameter to to enable the new

encryption algorithm
o Set the parameter to the encrypted value you get

in Step 7 to reset the DB password
o Set the parameter to the encrypted value you

get in Step 7 to reset the LDAP password
Note:
o You may have to modify these parameter values directly in the file. HP
recommends that you do not run (on Windows) or (on Unix)
to modify these parameters.
o If your system is not integrated with LDAP, you do not need to reset the LDAP password.
9. Run script located in the directory to apply your changes on

the three parameters.

11. (Optional) If your system is integrated with LDAP, and you want to import data from LDAP and set
default password for the Import Users report or the Run PPM Organization Unit Interface report,
you need to add an additional command for either of the reports.
To do so,
a. Log on to PPM Center.
b. From the menu bar, select Open > Administration > Open Workbench.
c. From the shortcut bar, select Configuration > Report Types.
The Report Type Workbench opens.
d. Click List, and then select the desired report type.
e. Open the report type either by double-clicking it or clicking Open.
The Report Type: window opens.
f. Click New Cmd under the Commands tab.
The New Command window opens.

g. Name the new command as you want.
h. Type the following in the Steps field:
Note: TEMP_GROUP_ID is the name for the temp token by default. If you have changed
the token name, replace TEMP_GROUP_ID with the name you used for the token.
i. Click Add.
You are back to the Report Type: window.
j. Adjust the sequence of the added command by using the up or down button, making sure that
the added command is under the Encrypt Password command.
k. Click OK.

Chapter 7: Improving System Performance
This chapter provides information about how to identify and correct performance problems on your
PPM Center system, as well as what you can do to improve system performance. For more information
on improving performance, see the
l "Identifying Performance Problems" below
l "Improving System Performance" on page 242
l "Monitoring Activity in PPM Center" on page 253
l "Using the Watchdog Tool" on page 267
Identifying Performance Problems

This section provides information about how to isolate performance problems, collect statistics about
the database schema, and troubleshoot performance problems. For detailed information on how to
tune your PPM Center instance to maximize performance, see the
Isolating Performance Problems

The section titled "Configuring or Reconfiguring the Database" on page 120 and "PPM Center
Configuration Parameters" on page 422 contain information on the initial settings that HP recommends
for the Oracle database and PPM Server. If performance slows after these settings are in place, use the
methods outlined in the flowcharts shown in Figure 7-1, Figure 7-2, and Figure 7-3 to isolate
performance problems and determine how to fix them.

Figure 7-1. Identifying and addressing system performance problems

Figure 7-2. Identifying and addressing database performance problems (A)

Figure 7-3. Identifying and addressing Java process performance problems (B)

Figure 7-4. Identifying and addressing I/O performance problems (C)
Troubleshooting Performance Problems

This section provides information about common performance problems and how to correct them. If
you are not using the default or recommended settings, reset your parameters to those values before
you try other solutions.
Tip: Consider upgrading to the latest PPM Center service pack. HP has a regular and well-
established service pack release cycle. Much of the development effort that goes into these
service packs is focused on resolving known performance issues. Review the for the
latest service pack to determine whether it addresses the performance problem you are
experiencing.
Scheduled Reports Do Not Run on Schedule
Problem: Although the PPM Server has capacity available, the next scheduled tasks do not start.

Possible source: All listeners on the light-weight service queue are busy running other services.
Solution: Do one of the following:
l Add another node to the PPM Server cluster with services enabled.
l Increase the value for the parameter in the

file for one of the nodes in the cluster.
Packages Do Not Execute
Problem: Packages do not execute.
Possible source: There are not enough execution managers available to service the packages that the
system processed.
Solution: Increase the server configuration parameter value. For

information about this parameter, see "PPM Center Configuration Parameters" on page 422.
Nightly Reports on Sunday Do Not Finish On Time, System Slows on Monday
Problem: By default, database server statistics are collected at 1:00 a.m. on Sundays. For large
installations, collection take so long that it is not completed on time and system performance is slower
on Monday.
Solution: Reschedule the statistics collection to a time that works better for your organization.
Determine the most active system time by running the Server Logon report, which checks the number
of active users. For details on how to run the report, see "Running Server Reports from the Admin Tools
Window" on page 327 and "Running Server Reports from the Command Line" on page 331.
Consider using the estimate method instead of the compute method to gather statistics.
Monitor CPU use. If the system slows because of high peak load, you might require more hardware or
faster hardware.
For more information about gathering statistics, refer to the Oracle documentation.
Improving System Performance

This section provides information about how you can improve system performance. For additional
information about improving performance on your PPM Center instance, see the

Minimizing the Performance Impact of Running

Background Services
As a system administrator, you can schedule, monitor, and distribute background services across all
nodes in a PPM Server cluster. You can proactively monitor application performance to identify threats
and eliminate them before system-wide performance problems or instability occur.
The following subset of PPM Center background services can be run in parallel to optimize performance
and minimize bottlenecks:
l Request Status Export Service
l FX Rate Update Service
l Evaluate TM Approvers Service
l Task Actual Rollup Service.
l Financial Metrics Update Service
l Staffing Profile Period Sum Update Service
l Project Planned Value Update Service
l Resource Pool Rollup Service
These services can be run on the same or on separate server cluster nodes on two different entities,
such as projects, work plans, time sheets, and so on.
Note: For information about how you can monitor background service activity, see"Background
Services Monitor" on page 260.
Recommendations for Running Background Services
Keep in mind that the flexible service framework that you get with a clustered server environment
comes with some risk. Use the following guidelines in enabling and scheduling the background services
on your instance:

l Run the system with background services in an isolated environment. For medium to large PPM
Center deployments, HP recommends that you dedicate one PPM Server on a single JVM to
processing PPM Center background services. This minimizes the impact that running services has on
users, and enables you to better monitor background service performance. For optimal
performance, set the server configuration parameter to false to turn off
services on nodes devoted to user traffic.
By default, nodes that run background services in a server cluster environment have one heavy-
service consumer and two light-service consumers. This configuration reduces both memory
consumption and CPU usage.
l Schedule PPM Center services to run when they are least likely to affect system performance.
Try to schedule background services to run during periods of low activity, such as weekends and
non-working hours.
Note: For Information about PPM Center background services and instructions on how to
schedule them, see "PPM Center Background Services" on page 274.
l Assess and adjust the frequency with which background services are run. Some of the services
may run more often than necessary, while other services may need to be run more frequently. For
PPM Servers devoted to services, schedule services to run only as often as necessary.
l Disable unnecessary background services. Your instance may be running more background
services than you need.
Note: For Information about PPM Center background services and instructions on how to enable
or disable them, see "PPM Center Background Services" on page 274.
l Start by running services on a single node, and then add services nodes as required. Although
you can easily run services across multiple nodes, HP recommends that you start by running services
on a single node. Later, when the workload calls for it, and after you determine that services are
running correctly, you can add PPM Servers as dedicated services nodes (JVMs) that have the same
configuration as the initial services node (one heavy service and two light services). It is always
better to run with fewer services nodes and retain most processing capacity for end-user activity.
l Test your solution. As always, test your solution to determine what is optimal for your environment.

Tuning Java Virtual Machine (JVM) Performance

Because the PPM Server uses JSP, a Java compiler must be available in the environment path where the
server is started.
Running in Interpreted Mode
To improve performance, the Java virtual machine (JVM) uses a just-in-time (JIT) compiler. For
debugging purposes, you can disable the JIT compiler and run the JVM in interpreted mode. Exceptions
that you encounter while running in interpreted mode contain line numbers that are helpful in
debugging.
To run the JVM in interpreted mode, set a variable in the server environment, as follows (use the Bourne
or K shell):
To avoid performance degradation, do not run the JVM in interpreted mode for extended periods in a
production environment.
Debugging
The PPM Server startup script ( ) contains two JVM parameters that you can use for
debugging. The JVM debugging parameters are and . These specify that
the JVM starts up with a heap size of 1280 MB (1.2 GB), and is limited to a maximum heap size of 1280
MB.
These settings are usually sufficient. For sites with heavy usage, however, consider overriding the
default maximum heap size using the parameter in the file. The
amount of memory required depends on factors such as cache sizes and number of Oracle connections.
Note: After you first start the PPM Server following an installation or upgrade, the server occupies
approximately 750 MB in memory. As you use the product, the cache fills up and the JSPs are loaded
into memory. Over time, the system gradually uses more memory. This is normal, and memory
usage levels out over time. In most cases, memory usage can increase to a maximum of 1 GB.
Setting Heap Size
If your Java program requires a large amount of memory, you may find that, at some point, the virtual
machine starts to throw OutOfMemoryError instances as it attempts to instantiate objects. This can

result from your program using more memory than is available. In this case, you can use command-line
options to increase the heap size allocated by the Java Virtual Machine (JVM). If not specified, the heap
size defaults to 1 MB, and can increase to as much as 16 MB if your program requires more memory. (To
set the initial amount of memory allocated for your program, use the -Xms option.)
Tuning Server Cluster Performance

High transaction volumes and a large number of concurrent users on a PPM Server can degrade server
response time. If the PPM Server is running on a multiprocessor system, spare CPU may be available, but
JVM limitations can prevent the system from using the spare CPU.
In this case, consider using a PPM Server cluster. In this system configuration, multiple PPM Servers
point to the same database instance and can be started on one or more systems. In addition to added
capacity, running on multiple systems increases availability.
To use your multiple-CPU system effectively, this may be necessary on a two-CPU system, and it is
required on systems with more than two CPUs.
For information about how to set up a server cluster, see "Configuring a Server Cluster" on page 179.
Improving Input/Output Throughput

The distribution of input and output across multiple disks is an important factor in database
performance. If consistently high input/output (I/O) occurs on one or more disks housing the database,
service time on that disk degrades. To address this problem, replan the database layout to improve
application performance.
You can split the PPM Center database into the following segments:
l PPM Center tables
l PPM Center indexes
l Redo logs
l Rollback tablespaces
l Temporary tablespaces
l System tablespace
l Tablespace for management and related utilities

HP recommends that PPM Center database instances with moderate transaction volume (instances with
more than 5,000 requests per month) have at least four discrete disks, divided as shown in the following
table.
Table 7-1. Database disk recommendations
Disk Recommendations for Data Placement
1 PPM Center tables
2 PPM Center indexes
3 Redo logs
4 l Rollback tablespaces
l Temporary tablespaces
l System tablespace
l Tablespace for management and related utilities
For PPM Center database instances that have higher transaction volumes (more than 10,000 requests
per month), HP recommends you do the following:
l Place each piece of the database on its own separate disk.
l Stripe the data and index tablespaces across multiple disks to provide adequate disk throughput.
For PPM Center database instances with an extremely high transaction volume (over 25,000 requests
per month), move specific tables and indexes to separate tablespaces on separate disks. This provides
better control and further increases available I/O throughput.
Improving Advanced Searches

PPM Center users can search for requests based on custom fields defined in request types, request
header types, and user data. Users can perform advanced searches to locate requests based on
information that is defined as critical to business processes.
As the number of requests logged increases, users performing advanced searches can experience
slower performance. To improve performance during advanced searches, use the following guidelines:
l Specify additional request header fields in the advanced searches. Header fields are automatically
indexed by PPM Center, and therefore yield faster returns.

l Add indexes to a limited number of detail fields, preferably fields that are commonly used in
advanced searches. Take care not to add too many indexes, since this can affect the performance
of inserts and updates to the database.
l Set the server configuration parameter value to to

remove the sort order column on a request search. Record sorting slows performance.
l Change the value set for the server configuration parameter

to restrict the maximum number of records returned by a search. The default is 1000. You can
increase or lower the value based on your environment to achieve a better performance. The value
you set for the server configuration parameter is displayed
as the default in the Limit Rows Returned To field.
If you want to restrict the maximum number of records returned for the current search only, you
can change the value in the Limit Rows Returned To field directly.
l For portlet search queries, lower the value set for the server
configuration parameter. For most portlets, 20 to 50 records is adequate. The default is 200.
Adjusting Server Configuration Parameters

This section provides information about PPM Server parameters related to system performance and
usage considerations for these parameters.
Server configuration parameter fall into the following categories:
l Cleanup parameters
l Debug parameters
l Timeout parameters
l Scheduler/services/thread parameters
l Database connection parameters
l Cache parameters
Most of the parameters are defined in the file. For a list of PPM Server parameters, see
"PPM Center Configuration Parameters" on page 422. The following sections provide descriptions of the
parameters in each system performance parameter category.

Cleanup Parameters
The following parameters, which are defined in the file, determine when the PPM Server
invokes services to clean up database tables:
l determines how many days to keep applet keys in the KNTA_APPLET_

KEYS table.
l determines how many days to keep records in the prepared

commands tables.
l determines how many days to keep records of all interfaces.
l determines how many days to keep records of all logon

attempts.
l determines how long (in hours) to keep rows in the

table.
Note: For descriptions of and valid settings for these parameters, see "PPM Center Configuration
Parameters" on page 422
Debug Parameters
Debug parameters control the debug and log output from the PPM Server. Debug parameters are either
high-level or low-level.
High-Level Debug Parameters
You can change high-level debug parameters without causing system downtime on the PPM Server.
Users who have the required privileges can configure these parameters by selecting Edit > Debug
Settings from the PPM Workbench.
The high-level debug parameters are:
l (defined in the file) control the debugging level.
l (defined in the file) determines whether the server maintains

a JDBC log file. If it is enabled, JDBC logging records SQL runs against the database, the amount of

time required to run the SQL, and the amount of time required to retrieve the results.
l (defined in the file) determines whether performance statistics

for all SQL statements run are placed into a trace file.
l (defined in the file) controls the verbosity of logs generated

by independent server processes such as EmailNotificationAgent.
For more information about the high-level debug parameters, see "PPM Center Configuration
Parameters" on page 422 and "Logging Parameters" on page 502.
Low-Level Debug Parameters
Enable the low-level debug parameters only if you require debugging information for a specific area.
Enabling these parameters can degrade system performance because they consume additional CPU
and generate large log files.
Note: HP strongly recommends thatHP Software Support you consult before you enable low-level
debug parameters.
The low-level debug parameters, which are all defined in the file are:
l
l
l
l
l
l
For more information about low-level debug parameters, see "Logging Parameters" on page 502.
Timeout Parameters
Timeout parameters determine how long the PPM Server waits before it times out. You can set timeout
values for logon sessions, command runs, and workflows.
The timeout parameters, which are all defined in the file, are:

l determines the interval (in minutes) at which PPM Workbench sessions send a
message to inform the PPM Server that the client is active.
l determines the duration (in seconds) for the PPM Server to keep trying to log on
to the database before reporting that the database is unavailable.
l determines the duration (in seconds) for the PPM Server to keep trying
to run commands before timing out.
l determines the duration (in seconds) after which portlets time out.
l determines the duration (in seconds) after which searches time out.
Scheduler/Services/Thread Parameters
Scheduler/services/thread parameters, which are all defined in the file, control
scheduling, services, and thread-related server activities.
The scheduler/services/thread parameters are:
l determines the frequency (in seconds) with which the

command status is refreshed to provide a list of values in an auto-complete field.
l determines the interval (in seconds) that elapses

before a task is verified for exceptions
l determines the number of command executions that can run

simultaneously. Organizations processing a high volume of packages may require a larger number of
execution managers.
l determines the number of command executions that can run

in a release distribution simultaneously. Organizations that process a high package volume may
require more release execution managers.
l determines the frequency (in seconds) with which the report

status is refreshed and displayed to the user.
l determines the maximum number of packages to run simultaneously

within a release distribution. If a large number of packages in a distribution are processing, increase
this value to improve performance.
l determines the minimum number of packages to be run

simultaneously within a release distribution.
l establishes the frequency (in seconds) with which the PPM Server

checks for pending scheduled tasks, and starts the tasks if worker threads are available.
l determines the priority of scheduled tasks. Because scheduled

tasks run in the background, it may be useful to run these tasks at a lower priority than the threads
servicing user-oriented interactive tasks.
Database Connection Parameters

Database connection parameters relate to the management of the database connection pool that the
PPM Server maintains. After the PPM Server starts, one database connection is established. Increased
usage spawns additional database connections.
The database connection parameters, which are all defined in the file, are as follows:
l determines the amount of time that the PPM Server is to continue to try to log
on to the database (acquire the JDBC connections that make up the connection pool) before
reporting that the database is unavailable.
l determines the amount of time (in minutes) that an unused

database connection is held open before it is closed and removed from the pool.
l determines the duration (in minutes) that a database session is

held open before it is closed and removed from the pool. Some Oracle cleanup operations that
should be run periodically occur only at the end of database sessions. Do not keep database
sessions open for the life of the PPM Server.
l determines the maximum size of the database connection pool that the
PPM Server creates.
Logging Parameters
The logging parameters are in the file. For information on the logging parameters that
affect system performance, see "System Logging in PPM Center" on page 338. For descriptions of all
logging parameters, see "Logging Parameters" on page 502.

Cleanup Services
Cleanup services determine which services the PPM Server invokes to clean up database tables. You
enable (or disable) and schedule cleanup services from the Schedule Services page in the PPM Center
standard interface. For instructions on how to enable and schedule services, see "Enabling and
Scheduling PPM Center Services" on page 279.
Monitoring Activity in PPM Center

This section contains information about configurable monitors that capture information on user
interface activity, portlets, and background services in PPM Center. These monitors capture UI activities
(mainly URL requests), background service runs, and portlet activity on the PPM Server.
Starting from PPM Center version 9.30, the parameter is available

to generally control PPM Center monitors. You can configure this parameter in the Administration
Console.
If you set this parameter to , you enable the UI monitor, the portlet monitor, and the Background
Services monitor, regardless of whether these three monitors are enabled or not. If you set this
parameter to , the UI monitor, the portlet monitor, and the Background Services monitor are
enabled or disabled according to their own parameters. By default, the parameter is set to .
Action Monitor
The PPM Center action monitor tracks activity in the standard interface. To control the monitor, you use
the and server configuration parameters. The
parameter turns the monitor on (the default), and the parameter
controls the threshold value of the action monitor, which is set in milliseconds.
Change the Action Monitor Parameters Using the Administration Console
You can change the values of the and parameters using

the script or, you can change them through the JMX console without having to stop, and
then start the PPM Server. Keep in mind that if you change these parameter settings through the JMX
console, your changes do not persist. The next time you start the PPM Server, the parameter settings
revert to the values specified for them in the file.
To enable or disable the UI monitor through the Administration Console,

1. Log on to PPM Center. From the menu bar, select Open > Administration > Open Administration
Console.
2. Under the Administration Console node, select Administration Task > Application configuration.
3. On the Application Configuration page, select the desired PPM Server node from the Scope drop-
down list, and search for parameter
.
4. Set parameter to or to enable or disable the UI monitor.
To change the parameter value,
Console.
2. Navigate to the Application Configuration page, select the desired PPM Server node from the Scope
drop-down list, and search for parameter
.
3. Specify a value for the parameter.
Viewing the Action Monitor Information in Real Time
To see the information captured by the action monitor in real time, go to the JMX console and access
the ActionMonitor MBean in the ppm.monitor section. The ten UI activities (URL requests) that most
affect performance are listed, as well as their average, minimum, and maximum execution times.
Action Monitor Information Log
If the latency for serving the URL request exceeds the threshold value, the captured information is
saved to the file, which resides in the PPM Server>/logs
directory.
The information is formatted as follows:
The information resembles the following:

Note: You can also use the ' ' parameter in the Administration Console
page to enable or disable persisting the captured information to the database table PPM_
PERFORMANCE_LOG.
Note: For information on how to create a report on action monitor activity, see Deployment Best
Practices for PPM Operational Reporting.
SQLs in PPM_PERFORMANCE_LOG for Action Monitor
When the parameter is set to , and if the latency of

serving a URL request exceeds the threshold value specified in the
parameter, then the SQLs that have been executed when serving the URL request are recorded in
the table PPM_PERFORMANCE_LOG.
Note: Only the top five SQLs that take the longest time when serving the URL request are
recorded.
Portlet Monitor
The PPM Center portlet monitor tracks the load time of portlets. You can use the information it
generates to determine the impact of portlet activity on system performance. To control the portlet
monitor, you use the and server
configuration parameters. The parameter turns the monitor on (the
default), and the parameter controls the monitor threshold value, which
is set in milliseconds.
Changing the Portlet Monitor Parameters from the JMX Console
You can change the values of the and

parameters using the script, or you can change them from the Administration Console
without having to stop and then restart the PPM Server. You can also change these parameters settings
through the file.
To enable or disable the portlet monitor through the Administration Console,

Console.
drop-down list, and search for parameter .
3. Set parameter to or to enable or disable the portlet

monitor.
To change the parameter value,
Console.
drop-down list, and search for parameter .
3. Specify a value for the parameter.
Note: You can also use the parameter in the

Administration Console page to enable or disable persisting the captured information to the
log file.
Portlet Monitor Information Log
If the amount of time required to load the portlet exceeds the threshold value, the captured
information is saved to the file, which resides in the
directory.
Note: For information about how to improve portlet performance, see the Deployment Best
Practices for PPM Operational Reporting.
Server Performance Reports

You can create server performance reports that are based on action monitoring and portlet monitoring
results. To do this, you first create a report type, and then create reports of that type from the PPM
Center standard interface. The following sections provide instructions for performing these tasks.

Creating a Portlet Performance Report Type
To create a portlet performance report type:
2. From the menu bar, select Open > Administration > Open Workbench.
3. From the shortcut bar, select Configuration > Report Types.
The Report Type Workbench opens.
4. Click List.
5. On the Results tab, scroll down to and select (REFERENCE)Portlet Performance Report.
6. Click Copy.
7. In the Copy Report Type window, do the following:
a. In the Report Type Name field, type a name such as Server Performance Report.
Note: The report type you create here includes both the action performance report
subtype and the portlet performance report subtype.
b. Click the Reference Code field.
c. A reference code is automatically created for the report type based on the name you typed in.
You can leave this default value, or type a different reference code.
d. If you are working in a multilingual UI (MLU), select the Copy existing translations checkbox.
e. Click Copy.
8. In the dialog box that opens, click Yes, to open the new report type for editing.
9. Select the new report name, and then click Open.
The Report Type window opens.
10. In the Description field, type a new report type description.

11. For Enabled, select Yes.
The Results tab in the Report Type Workbench lists the new report.
Creating Server Performance Reports
To create a portlet performance report or action performance report:
1. After you have created the report type from the PPM Workbench, return to the PPM Center
standard interface.
2. From the menu bar, select Create > Report.
The Submit New Report page opens.
3. From the Report Category list, select Administrative.
4. From the list of Administrative reports, select the report type you created from the PPM
Workbench (see "Creating a Portlet Performance Report Type" on the previous page).
The Submit Report: < > window opens.
5. Provide information in the fields listed in the following table.
Field
(* Required) Description
From Use the Date Time Chooser to specify the start date and time for data to
include in the report.
To Use the Date Time Chooser to specify the end date and time for data to include
in the report.
*Report Name From this list, select one of the following:
o Portlet Performance Report
o Page Performance Report
Report Type From this list, select the level of detail to include in the report. The options are:
o Summary. Presents aggregated results on average execution time, and the

maximum, minimum, and total time taken to invoke the page or portlet
(portlets).

Field
(* Required) Description
o Detail. Presents information on the poorest performing page or portlet

based on execution time.
o Summary and Detail. Presents information on the poorest performing

page or portlet, aggregated results on average execution time, and the
maximum, minimum, and total time taken to invoke the page or portlets.
Top N Use this field to specify how many of the portlet or page invocations with the
worst response times to include in the report. The default is 10.
Portlet Name If you are creating a portlet performance report, use this multiselect to limit
the report to one specific portlet. If you do not specify a portlet, the report
(Enabled for
includes information on all portlets in PPM Center.
portlet
performance If you are creating a page performance report, this field in disabled.
reports only)
Report Period From this list, select the value that indicates the frequency with which to run
the report. The choices are Daily (default), Weekly, Hourly, and All.
Run Report Select this option to run the report now (the default).
Immediately
Run Report On Select this option to run the report on a specific calendar date. If you select
this option, then you must use the multiselect to specify the date and time to
run the report the first time.
Repeat Every If you select the Run Report On option, you can then have the report run at
regular intervals by selecting this checkbox. Use the adjacent number field and
list to specify the report run intervals.
Until Use the multiselect to specify a date and time at which to stop running the
report at the set interval.
Send email to To send an notification email after the report is completed, select this
checkbox. To have the notice sent to a user other than you, use the now-
enabled multiselect to select the user.
Add a Click this button to open the Edit Advanced Notifications window and configure
Notification a custom notification.
6. Click Submit.

Background Services Monitor

The PPM Center Background Service monitor is controlled using the
and server configuration parameters. The
parameter turns the monitor on (the default). The
parameter controls the threshold value (in milliseconds)
for the monitor. If the runtime of a background service exceeds the threshold value, this is recorded in
the file. The following is an example of the file contents:
Note: For information on all of the background services in PPM Center, see "PPM Center
Background Services" on page 274.
Changing the Background Services Parameters Using the JMX Console
You can change the values of the and

parameters using the script, or you can change them through the
JMX console without having to stop and start the PPM Server. However, keep in mind that if you change
them through the JMX console, your changes do not persist. The next time you start the PPM Server, the
values for these parameters revert to the values specified for them in the file.
To enable or disable the Background Services Monitor through the JMX console:
1. Go to the JMX MBean agent view in the JMX console.
2. In the ppm.monitor section, access the BackgroundServiceMonitorAspect MBean.
3. Use the parameter to enable or disable the UI monitor.
To change the UI_MONITOR_THRESHOLD value:
1. Go to the JMX MBean view in the JMX console.
2. In the ppm.monitor section, access the Action Monitor Trigger MBean.
3. Change the value of the parameter.
Note: You can also use the parameter in the JMX console to enable or disable
persisting the captured information to the log file.

Viewing the Background Services Monitor Information in Real Time
Administrators can view the Background Services Monitors in real time through the JMX console, and
use the information to isolate performance issues in the field. To see the information captured by the
Background Services Monitor in real time, go to JMX console and access the BackgroundServiceMonitor
MBean in the ppm.monitor section. Here, all of the background services that have been executed on the
system are listed. Information about the background service runs that most affect performance are
listed, as are the minimum, maximum, and average execution times for these services.
Background Services Monitor Information Log
If background services activity exceeds the configured threshold value, the captured information is
saved to the file, which resides in the
directory.
The logged information has the following format:
The information resembles the following:
SQLs in PPM_PERFORMANCE_LOG for Background Services Monitor
When the parameter is set to , and if a background

services activity exceeds the threshold value specified in the
parameter, the SQLs that have been executed when running the activity are recorded
in the table PPM_PERFORMANCE_LOG.
Note: Only the top five SQLs that take the longest time when running an activity are
recorded.
Viewing the Services Audit Results Page

You can open the Services Audit Results page to quickly view information about PPM Center background
services.

To view the Services Audit Results page:
2. On the Open menu, click Administration > View Services Audit Page.
Note: The Services Audit Results page is read-only. You cannot disable or enable, or reschedule a
service from this page. For instruction on how to enable and schedule services, see "Enabling and
Scheduling PPM Center Services" on page 279.
The following table lists the columns displayed on the page.
Column Heading Description
Service Name Name of the background service
Status Status (enabled or disabled) of the background service
Is Running? Shows whether the service is running ( ), not running ( ), or

disabled ( )
Run Interval Run interval set for the service
Last Run Node Node on which the service was last run

Column Heading Description
Note: A dash (-) character in this column indicates that the

service was triggered, but did not run because there are no data
to process.
Last Completed Run Time and date the service last ran
Next Scheduled Run Time and date the service is scheduled to run next
Accessing Services Exceptions Details
On the Services Audit Results page, you can see whether any services have thrown exceptions.
If a service has encountered one or more exceptions or errors during its last 50 runs, a red icon ( ! ) is
displayed to the left of the service name on the Services Audit Results page. You can change the
threshold for displaying the icon by changing the value for the server
configuration parameter in the file.
To view details about exceptions a service has encountered, click the service name. The Search
Exceptions page opens and displays a list of the exceptions.
The Search Exceptions page provides the following information:
l Presence or absence of exceptions during a particular service run.
l Name of the node on which the service was run
l Time the service run started

l Time the service run finished
l Duration of the run, in seconds
l Any additional information provided by the service. All services by default provide the memory
footprint during the start and end of the service. This information is useful to troubleshoot any
issues related to memory consumption by a service run.
To enable this functionality, add the server configuration parameter to the

file and set its value to
Purging Exceptions Thrown by Services
Whenever a service run is deleted from the system, the exceptions related to that service run are also
removed. By default, the system retains the 50 most recent service run records. You can change this by
setting a new value for the server configuration parameter in the
file.
Accessing Application Exception Details

If an exception occurs, the user sees an error message that displays a GUID number and advises the
user to contact the PPM Center administrator. The PPM Center administrator can then get detailed
information about the exception from the new Search Exceptions page.
Note: To access the Search Exceptions page, you must have an Administrator license and the
following access grants:
l Server Tools: Execute admin tools
l Sys Admin: Edit Services Schedules
To enable this functionality, set the server configuration parameter value to
To access and use the Search Exceptions page:
2. From the menu bar, select Search > Administrative > Exceptions.

The Search Exceptions page opens.
3. In the View Details for Exception GUID field, enter the GUID provided in the error message.
4. Click Go.
The Exception details page opens.
The Exception details page displays the following information:

Field Description
User Full name of the logged-in user who encountered this exception.
This field is empty if the exception was thrown by a background
service.
GUID GUID identifier for this exception. Most web exceptions are tagged
with a GUID. Background service exceptions usually do not have a
GUID.
Name Name of the exception.
URL URL of the page that encountered this exception.
Reason Reason the exception occurred. For background service exceptions,

this can be an error message.
Node name Name of the node on which the exception occurred.
Generated Time Time at which the exception occurred.
Exception Stack trace Stack trace for the exception.
Purging Exceptions (Other than Services Exceptions)
Exceptions (except for services-related exceptions) older than 14 days are automatically purged by
default. You can control the frequency with which exceptions are purged by setting a new value for the
server configuration parameter in the file.
Identifying Database Connection Issues

The Connection details page enables you to identify suspect connections that are leaking. To access the
Connection details page, you must have an administrator license and the "Server Tools: Execute admin
tools" access grant.
To enable this feature, set the server configuration parameter to
To access the Connection details page:
2. From the menu bar, select Open > Administration > View connection correlation.

The table on the left portion of the page displays the stack trace for each connection recorded when
the connection was acquired from the pool.
To display the stack trace associated with the connection at the time it was acquired, click the
corresponding connection entry.
Note: Because this feature involves some database overhead, HP recommends that you use it only
to troubleshoot connection leak issues.
Using the Watchdog Tool

Watchdog is a stand-alone tool that issues a command to generate a thread dump whenever memory
exceeds the configured threshold after a full garbage collection (GC). This tool requires that the Java
garbage collection log be turned on at startup.
Watchdog monitors the memory space through the GC log that the PPM Server generates. If the
memory used after garbage collection is greater than a set threshold value, the Watchdog issues a
command to generate a thread dump, and the thread dump is captured in the server log. You can
configure the Watchdog tool to send out email notifications about this event.
The Watchdog tool does not affect the PPM Center functionality. It is platform-dependent because it
uses different mechanisms to generate thread dumps on Windows than on other, UNIX-like platforms.
Note: Watchdog is not currently supported on AIX systems.

The memory used after a full GC is compared with the threshold. The Watchdog tool is interested in the
following record in the GC log:
l With the JVM option:
l Without the option:
In the second example (without the option), the Watchdog reads the record and parses out the
memory used before GC as 50507K, and memory used after GC as 34733K. The Watchdog then
compares the memory used after GC, 34733K in this case, with the set threshold. If the threshold is set
to 30, then the record triggers a thread dump. If the threshold is set to 35, it does not.
When the memory first exceeds threshold, PPM Center is considered to be entering a critical condition.
A thread dump is triggered and a notification is sent.
After the next full GC, if the memory still exceeds the threshold (PPM Center remains in critical
condition). No dump is generated as long as the memory is still higher after entering critical condition.
When the memory used falls below the threshold in subsequent GCs, PPM Center is considered to be
exiting a critical condition. In this case, no thread dump is generated. You can configure the Watchdog
tool to send out email notifications about this event.
If, after exiting a critical state, the memory used again exceeds the set threshold, a new critical
condition starts. A thread dump is triggered and a notification is sent (if set up) every time PPM Center
enters the critical condition.
Tip:
To collect thread dumps when a threshold value is not desired, you can,
l Use the Watchdog Tool and set to Or,
l (Recommended) Use Stack Trace tool jstack to create all thread dumps on all operating
systems.
For example, jstack pid >a.log
The jstack tool is present in the directory.

Generating the GC Log

The Watchdog utility requires that a Java GC log file be present.
To enable verbose GC logging when starting PPM Center:
2. Locate the following lines in the script:
3. Add the following line to generate the GC metric output file:
4. Stop, and then start the PPM Server in debug mode by running:
The directory now contains a file with garbage collection metrics, and the
directory contains the PPM Server log.
Note: On Windows systems, you may need to start the PPM Server using If you start
the PPM Server in service mode, the Watchdog utility may not work.
Running Watchdog
To use the Watchdog tool:
1. Make sure that the directory contains the GC log file.
2. Navigate to directory, and open the

file.
3. Enter the values for the parameters listed in the following table.

Name Description Required Default
gclog_ Name of the GC log file. The file name is based on the Yes N/A
filename name provided during the run after the
flag.
memory_ Memory threshold set in MB Yes 300

threshold
enable_ Enable email notification No true

email_
notification
enable_ Enable thread dump No true

thread_dump
smtp_host Host name of the SMTP server Yes, if email N/A

notification
is enabled
sender_addr Sender email address Yes, if email N/A

notification
is enabled
recipients_ Specifies email recipients addresses. Use commas to Yes, if email N/A
addr separate multiple addresses. notification
is enabled
node_name PPM Server name Kintana
debug Enables debugging false
use_jmx Specifies the use of JMX to retrieve the thread dump. No false
To use this option, start the PPM Server with the
following system properties:
o
o
o
jmx_output_ If you do not want the JMX thread dump saved in the No
filename server log, use this parameter to specify a different
file name (full directory path).

Name Description Required Default
jmx_url Specifies the URL used to access the PPM Server No

through JMX. Use the following format:
mem_used_ Indicates the number to select as the memory used No 9

after_gc_ after a full garbage collection in a Full GC record.
position_
index
monitored_ Indicates the text string to use to identify the full GC No Full GC
gc_record_ record in the GC log.
indicator
4. Find out the Java process ID of the PPM Server you want to monitor, and then run the following:

Chapter 8: Maintaining the System
This chapter provides information on how to maintain your PPM Center instance. The initial sections
include descriptions of tools available in the PPM Center standard interface, the Administration Console,
and the PPM Workbench. Later sections address the maintenance tasks required to keep your PPM
Center instance running smoothly.
This chapter includes the following sections:
l "Administration Tools in the Standard Interface" on the next page
l "Tools in the Administration Console" on page 281
l "Server Tools In the PPM Workbench" on page 325
l "System Logging in PPM Center" on page 338
l "Maintaining Log Files" on page 347
l "Periodically Stopping and Restarting the Server" on page 354
l "Maintaining the Database" on page 354
l "Backing Up PPM Center Instances" on page 372
l "Checking PPM Center License Status" on page 373

Administration Tools in the Standard Interface
The following sections provide information about the administration tools you can access through the
PPM Center standard interface:
l "Viewing Server Running Server Reports, Requests, and Packages" below
l "Viewing Running Executions" below
l "Viewing Interrupted Server Reports, Requests, and Package Executions" on the next page
l "PPM Center Background Services" on the next page
Viewing Server Running Server Reports, Requests, and

Packages
To view running reports, requests, and packages:
2. On the Open menu, click Administration > Report Execution > View Running Reports.
The View Running Reports page opens and lists any reports, requests, and packages currently running.
Return to "Administration Tools in the Standard Interface" above.
Viewing Running Executions

To view running executions:
2. On the Open menu, click Administration > Report Execution > View Running Executions.
The View Running Executions page opens, and the Summary section lists any distributions, server
reports, requests, or packages that are running.
3. If any reports are listed as running, click View Running Reports.
Return to "Administration Tools in the Standard Interface" above.

Viewing Interrupted Server Reports, Requests, and Package

Executions
To view interrupted server reports, requests, and package executions:
2. On the Open menu, click Administration > Report Execution > View Interrupted Executions.
The View Interrupted Executions page opens and lists interrupted executions (if any exist).
3. In the list below View Interrupted Executions for a Server Startup, select the date of the
interrupted execution to view.
4. To view the details of the selected interrupted execution listed in the Failed Executions section,
click View.
Return to "Administration Tools in the Standard Interface" on the previous page.
PPM Center Background Services

This section provides information about the background services available in PPM Center, and
instructions on how to enable and schedule them. It also provides guidelines for scheduling background
services to optimize resource use and system performance.
The following table lists the PPM Center background services.
Note: For information on background services monitoring in PPM Center, see "Monitoring Activity in
PPM Center" on page 253.
Table 9-1. Background services in PPM Center
Service Name Description
ALM Startup Ensures that the quartz scheduler that synchronizes PPM Center and Service
Manager is running.
Applet Key Periodically removes old records from the database table KNTA_APPLET_KEYS.
Cleanup (These are temporary, system-generated keys used for one-time access to the
system—for example, if a user wants to open the PPM Workbench.)

Table 9-1. Background services in PPM Center, continued

Commands Periodically removes old records from the prepared commands tables.
Cleanup
Concurrent When Deployment Management submits a concurrent request (job) to Oracle Apps,
Request Watch this service polls Oracle to determine what state the job is in, and when it has
Dog completed.
Cost Rate Rule After it checks for changes to cost rules and cost factors, this service:
Update
l Updates time sheet costs stored on the time sheet
l Updates financial summaries that are synchronized to staffing profiles
l Adds projects to the queue for Cost Rollup Service, which updates project cost
in the workplan and in the financial summary.
Cost Rollup Cost rollup service asynchronously rolls up planned and actual costs (entered
manually or pulled from time sheets) from leaf tasks to root tasks in workplans,
and then pushes the data to the financial summary.
In addition, the cost rollup service rolls up actual costs from time sheets to
financial summaries for proposals and assets.
Debug Periodically removes old records from the KNTA_DEBUG_MESSAGES database

Messages table, which can collect a lot of temporary data.
Cleanup
Directory Cleans up files in the dynamic content directory. The PPM Server generates these
Cleanup files and writes temporarily to the dynamic content directory so that they can be
accessed over the Web. After the scheduled number of days, the files are deleted
because they are no longer necessary.
Document Periodically checks for documents that are no longer attached to a PPM Center
Cleanup entity, and removes those it finds from the PPM Center file system.
Evaluate TM An HP Time Management service that periodically checks to determine whether

Approvers the resource assigned to approve a timesheet has changed.
Exception Rule Periodically checks to determine whether active projects are running on time.
Determines if and when task exceptions are recalculated. For more information
about this service, see the
Field Security Because managing field-level security is computationally expensive, whenever the
Pending security settings at the field level are updated, this service performs calculations
Denormalization that ensure live security checks in performance.


Financial Calculates net present value (NPV) and nominal return for Financial Management.
Metrics Update
Financial Calculates rollups of financial information, including forecast and actual costs and
Summary Rollup benefits (monthly data) and approved budgets (annual data), for the following:
l Rollups from proposals, projects, and assets to a program
l Rollups from proposals, projects, assets, programs, and subportfolios to a

portfolio, along with immediate rollups to all the successively higher levels in
the portfolio hierarchy
The following events, performed by manual entry or by another background

service such as Cost Rollup or Web services, trigger this rollup service:
l Addition or removal of items in the program or portfolio
l A change to the financial summary of any item in the program
l A change to the financial information of any item in the portfolio
FX Rate Update Recalculates cost after financial exchange (FX) rates change.
Integration SDK Periodically synchronizes user stories in all sprints from agile management
Sync Service systems to PPM Center tasks.
Interface Tables Periodically removes old records from the database open interface tables.
Cleanup
Logon Attempts Periodically removes old records from the KNTA_LOGON_ATTEMPTS database
Cleanup table, which contains records of all logon attempts.
Mobility Access Enables PPM Center users to process approval workflow steps from desktop email
or a PDA device. Resources working outside of an office or without VPN access can
act on approval workflow steps without having to first log on to PPM Center.
For information about PPM Center Mobility Access, see the
Notification Deletes rows (older than the current date minus the number of days set for the
Cleanup notification cleanup service) from the KNTA_NOTIF_TXN_PARENTS table in the
database. The service then deletes all child rows from the KNTA_NOTIF_TXN_
DETAILS, KNTA_NOTIF_TXN_COLUMNS, and KNTA_NOTIF_TXN_RECIPIENTS tables.
Notification Enables the notification service. You can use this parameter to turn off
notifications for copies of production instances being used for testing, and turn


them on again when the system goes to production.
Pending Periodically checks for duplicate rows in the

Assignments KNTA_PENDING_ASSIGNMENTS table. This parameter is related to the Work Item
Table Cleanup Pending Assignment service. If a work item is updated more than once between
runs of the work item breakdown service, the KNTA_PENDING_ASSIGNMENTS table
contains duplicate rows. This service removes the duplicates.
Pending Cost EV Asynchronously applies external updates to the Pending Cost EV Updates service
Update when updates cannot be made immediately.
Pending EV Removes duplicate rows in the Pending EV Updates table.

Updates Table
Cleanup
Performance Deletes data from the Performance Log table

Log Cleanup (PPM_PERFORMANCE_LOG) in the database. The PERF_LOG_DAYS_TO_KEEP
parameter determines how long records remain in the table. All records older than
the number of days specified by this parameter are deleted from the table.
Project Health Automatically updates project health indicators.
Project Planned This service handles synchronization between requests (as cases of blocking
Value Update predecessors) and between requests and tasks if a request is updated and the
target entity is locked.
Reference Automatically updates references between entities.

Update
Request Status Determines whether any request status values were changed since the service
Export last ran. If status values have changed, and if the updated requests reference
remote entities, then the status values for the referenced remote entities are
updated.
Resource Pool Performs resource pool rollup (between child and parent resource pools.)
Rollup
RM Notification Resource pool and staffing profile notification service. This service must be
enabled in order to send notifications to staffing profile managers, resource pool
managers and resources. For more information, see the
Service to Periodically updated the projected totals for budgets and staffing profiles.
update the
Projected Total


values for
Budgets and
Staffing Profiles
Shared Lock Cleans up any entries left in the shared lock table after a PPM Server crash.
Cleanup
Staffing Profile Synchronizes staffing profile data with financial summary data at a configurable
Financial interval. You can schedule the service so that synchronization does not happen
Summary Sync automatically whenever changes are made to a staffing profile or a budget. If
updates are frequent, delaying synchronization can help preserve system
performance.
Staffing Profile Synchronizes the budgets linked with the staffing profiles that are updated
Linked Budget through the Web service. The Web service update creates an entry in the ITG_
Sync Service PENDING_ROLLUPS table for a staffing profile when its positions are updated from
the Web service.
Staffing Profile Rolls up actuals from time sheets and projects/tasks to staffing profiles.
Period Sum Whenever a time sheet or project/task is updated, the actuals are displayed on
Update the linked staffing profile only after this service runs.
Synchronize The HP Document Management module uses PPM Center entity names (project
Documentum names or request type names) to name the folders and security groups in the EMC
Folder/Security Documentum repository. As those entity names change in PPM Center, this
Group Name background service picks them up and applies the changes to associated items in
the Documentum repository.
For more information, see the .
Task Actual Determines if and how frequently periodic task actual roll-ups are calculated.
Rollup
Asynchronously rolls up actuals provided through HP Time Management or the My
Tasks portlet. For more information about this service, see the
Task Scheduler Determines if the work plan schedule health is recalculated and the frequency
with which work plan schedule health is recalculated. For more information about
this service, see the
Time Sheet Enables notifications to be sent on time sheets.

Notifications
TM-PM Sync Synchronizes time sheet updates from HP Time Management to project work plan
tasks in Project Management, at a configurable interval. Each time the service


runs, it sends a message to the queue for each work plan that must be
synchronized with time sheets. The service ensures that roll-ups for each work
plan can be accumulated and updated once, if necessary, per work plan.
Work Item Periodically populates the KRSC_ WORK_ITEM_ASSIGNMENTS table, which is used
Pending for resource work load information. The service retrieves the actuals information
Assignment from the request.
Work Item On the PPM Server, periodically calls KRSC_PROCESS_PENDING_UPDATES.Patrol to

Pending Update process updates to work items.
Workflow Scans all active workflow steps to verify that they have timed out according to the
Timeout Reaper settings for the step.
Return to "Administration Tools in the Standard Interface" on page 273.
Running Services on Multiple Nodes
You can run multiple instances of the same type of service concurrently to process different entity IDs
on the same or different nodes in a server cluster. For recommendations on how to schedule and run
background services, see "Minimizing the Performance Impact of Running Background Services" on
page 243.
Enabling and Scheduling PPM Center Services
You can enable and schedule the PPM Center background services through the standard interface.
To enable and schedule PPM Center services:
2. On the Open menu, click Administration > Schedule Services.
The Schedule Services page lists all of the available services, and shows the typical load each
service manages, whether the service is enabled, the type of expression used to schedule the
service, and the current run schedule.
3. Click the table row that displays the service you want to enable, disable, or schedule.
The editable fields for that service are enabled.

Note: The typical load values assigned to services are based extensive testing and feedback
from the field. Light services are short-lived with low resource consumption. Heavy services
take longer to run and are more resource-intensive than light services. You cannot modify
these values.
4. To enable or disable the service, from the Status list, select Enabled or Disabled.
5. To select the type of expression to use to schedule the service, from the Schedule Type list, select
either Simple or Cron.
Note: If you use a cron expression to schedule a service, keep in mind that cron expressions
take into account the parameter setting for the PPM Server on which the service
runs. In a server cluster environment, servers can be running on machines located in different
time zones.
6. In the Schedule column, do one of the following:
o To schedule the service using a simple expression, type a number in the first field and, from the
list on the right, select the time unit (seconds,minutes, or hours.)
o To schedule the service using a cron expression, type the expression in the text field. For
detailed help on how to compose a cron expression, under the Schedule Type column heading,

select the Help icon ( ).
Note: If you use a cron expression to schedule a service, keep in mind that the value you
type in the Schedule field cannot exceed 40 characters.
7. For each additional service you want configure, repeat step 3 through step 6.
8. After you have finished configuring services, click Save.
Your changes take effect immediately after you save them. There is no need to restart the PPM Server.
Note: If a service misses one or more of its scheduled runs because, for example, the PPM Server is
shut down, the service is run as soon as the server is restarted.
HP recommends that, if you have a server cluster configured, and there are nodes in the cluster that do
not handle incoming user requests, you disable the nodes from running the PPM Center background
service. For information about disabling nodes or restricting services from running on non-services
nodes, see "Disabling Nodes from Running Background Services" in "Verifying Successful Cluster
Configuration" on page 195.
For information about how to view the current status of background services, see "Viewing the Services
Audit Results Page" on page 261.
Return to "Administration Tools in the Standard Interface" on page 273.
Tools in the Administration Console

The following sections provide information about how to access the Administration Console and about
the tasks you can use it to perform:
l "Opening the Administration Console" on page 283
l "Viewing PPM Server Status from the Administration Console" on page 284
l "Installing Autopass License Key File and Viewing License Summary in Administration Console" on
page 322
l "Working with Fiscal Periods from the Administration Console" on page 288

l "Viewing and Modifying Server Configuration Parameters from the Administration Console" on
page 295
l "Configuring and Migrating the PPM Center Document Management System from the Administration
Console" on page 300
l "Browsing and Downloading <PPM_Home> Directory Files from the Administration Console" on
page 304
l "Running SQL Queries from the Administration Console" on page 307
l "Gathering Information for HP Software Support from the Administration Console" on page 312
l "Changing Data Display in Administration Console Tables" on page 319
l Using the Unchecking Showing Total Number Tool from Administration Console
l "Installing Autopass License Key File and Viewing License Summary in Administration Console" on
page 322
In order to access and use the Administration Console, you must:
l Have the User Administration license
l Have one or more of the following access grants:
Access Grant Permissions
Sys Admin: Server Tools: Lets the user access the Administration Console and the server tools.
Execute Admin Tools
Sys Admin: Server Tools: Enables the SQL Runner menu in the Administration Console and lets
Execute SQL Runner the user run SQL queries from the Administration Console. Without
this access grant, the SQL Runner menu is invisible.
Sys Admin: Server Tools: Enables the File Browser menu Browse PPM Server files in the
Execute File Browser Administration Console and lets the user browse and download PPM
Server files. Without this access grant, the File Browser menu is
invisible.
For more information about security groups and access grants, see the

Opening the Administration Console

You can open the Administration Console from either the PPM Center standard interface or from a Web
browser window.
Opening the Administration Console from the PPM Center Standard Interface
To open the Administration Console from the standard interface:
2. From the menu bar, select Open > Administration > Open Administration Console.
The left panel of the Administration Console window displays the System Health,Administration Task,
and Support Task sections. The right panel displays details about the item selected in the left panel.
The Nodes item under System Health is selected by default. If your PPM Center instance includes
multiple nodes, the Node Name column lists all of the nodes.
Note: If you configure secure Web logon for PPM Center, you can launch Administration Console on
HTTPS. For details, see "Configuring Secure Web Logon (Optional)" on page 107.

Opening the Administration Console from a Web Browser Window
To open the Administration Console from a Web browser window:
1. In the address field of a Web browser window, type the following:
<PPM_URL>/itg/admin/AdminConsole.do
where is the Web location (top directory name) of the

PPM Server.
Example:
The PPM Center logon page opens.
The Administration Console window opens. The left panel of the window displays the System
Health,Administration Task, and Support Task sections. The right panel displays details about the
item selected in the left panel.
The Nodes item under System Health is selected by default. If your PPM Center instance includes
multiple nodes, the Node Name column lists all of the nodes.
Note: If you configure secure Web logon for PPM Center, you can launch Administration Console on
HTTPS. For details, see "Configuring Secure Web Logon (Optional)" on page 107.
Viewing PPM Server Status from the Administration

Console
You can use the Administration Console in PPM Center to quickly assess the status of the nodes in your
instance.
Note: For information about how to run the Server Status Report from the Admin Tools window in
the PPM Workbench, see "Running Server Reports from the Admin Tools Window" on page 327.
To view the status of nodes from the Administration Console:

1. Open the Administration Console. (See "Opening the Administration Console" on page 283.)
In the System Health section in the left panel, Nodes is selected.
The Nodes table in the right panel lists all nodes in the cluster. Icons in the Node Status column
indicate whether a node is up ( ) or down ( ).
2. To view detailed information about a specific node in a cluster, in the Nodes table, click the node
name.
The following table shows the information that the Node Details table displays for the selected
node:
Field Description
Node Status Node status (either Up or Down).
Node Name Node name.
Start Time Day of the week, calendar date, and time the node was last started.
End Time If the node is down, this field shows when this node was stopped
(weekday, calendar date, and time).
RMI URL URL for Java RMI.
Format:

Field Description
Available Light Queue Number of listeners available on the node to run light background
Listeners services.
Available Heavy Queue Number of listeners available on the node to execute heavy background
Listeners services.
The Start Time and End Time columns in the Node Details table display the complete history of
start and stop times (calendar date and times) for the selected node.
Installing Autopass License Key File and Viewing License

Summary in Administration Console
Install an Autopass License Key File
To do so,
For information about obtaining an Autopass license, see "Key Considerations" on page 36.
2. Log in to PPM Center.
4. In the navigation pane, select Administration Task > License.
5. On the License Install page, click Browse to locate the license file you saved, and then click Install.
There is no need to stop and restart the PPM Server for the license to become effective..

View A Summary of Autopass Licenses Purchased and Installed on the PPM Server
You can view a summary of Autopass licenses that you purchased and installed on the PPM Server from
the Administration Console window.
The View History section displays a summary of all Autopass licenses installed on the PPM Server
that are valid for use. Only activated licenses are shown in the View History section.
4. Expand the plus sign in front a license entry to view details.
For example,
The following table describes columns in the View History table:
Column Description
License Full title of the Autopass license key you generated from the HP
Licensing for Software portal
Product Feature A list of product features that are available with the Autopass
license
Capacity Number of users available with the Autopass license
Start Date Start date of an Autopass license key
End Date End date of an Autopass license key
Delete Click the Delete button to remove a corresponding Autopass

license key

Note: To view consumption status of implicit features available with each Autopass license, you can
still go to the License Administration window in the PPM Workbench.
Remove a License Key
To remove a license key,
1. In the Administration Console navigation pane, select Administration Task > License.
2. In the View History section, click Delete for the license key that you want to remove.
Working with Fiscal Periods from the Administration

Console
You can use the Administration Console to generate fiscal periods that reflect your organization's fiscal
calendar. You can also use Administration Console to add translations of fiscal period names, shift
existing fiscal periods, and import and export fiscal periods.
Note: For information about how to use the script to generate fiscal
periods, see the guide.
l "Generating Fiscal Periods from the Administration Console" below
l "Using the Administration Console to Shift Existing Fiscal Periods" on page 290
l "Using the Administration Console to Import Fiscal Periods" on page 291
l "Using the Administration Console to Export Fiscal Periods" on page 292
l "Using the Administration Console to Generate Translations for Fiscal Periods" on page 294
Generating Fiscal Periods from the Administration Console

To generate fiscal periods from the Administration Console:
2. In the left panel of the Administration Console, expand the Administration Task section, and then

select Generate fiscal periods.
3. In the Generate fiscal periods panel on the right, leave the Generate option selected.
4. In the Start Year and End year boxes, type the starting and ending years for the fiscal periods you
want to generate.
The Administration Console generates the fiscal periods, and then lists all existing fiscal periods
(for all period types) in the Administration Console.
Note: If a gap exists between the latest existing fiscal period year and the starting year you
specify, the Administration Console generates fiscal periods for all of the intervening years.
5. To persist the generated fiscal periods, click Commit.
6. To implement your changes, stop, and then restart, the PPM Servers.

Using the Administration Console to Shift Existing Fiscal Periods

So that all fiscal periods match the fiscal year, you can use the Administration Console to do one or
more of the following:
l Change the starting day of the week ( ) of your organization's fiscal year
l Change the starting month ( and ) of your

organization's fiscal year.
The changes you make apply to existing fiscal periods as well as to fiscal periods to be generated later,
so that all fiscal periods match the fiscal year.
Note: Shifting fiscal periods changes period data in the database. HP strongly recommends that
you back up the configuration file before you perform this procedure. For information about how
shifting fiscal periods affect functionality in PPM Center, see the guide.
To shift existing fiscal periods from the Administration Console:
1. Open the file in a text editor. The file is located in the
directory.
2. To change the starting month, change the parameter value to the number that
represents the month the fiscal year starts. For example, you would use 11 to represent
November.
Note: For detailed information about how to set values for the parameters in the
file, see the guide.
3. To change the starting month of your organization's fiscal year, set the
parameter value to or depending on the relationship between
fiscal years and calendar years.
Note: The default value of indicates that the start month does belong to the next
fiscal year.

4. To change the starting day of the week, set the parameter to a number
between 1 and 7, with 1 representing Sunday, and 7 representing Saturday.
5. Save and close the configuration file.
7. In the left panel of the Administration Console, expand the Administration Task section, and then
select Generate fiscal periods.
8. In the right panel, select the Shift option.
9. Click Submit.
The Administration Console shifts the existing fiscal periods, and then lists all fiscal periods (for all
period types) in the Administration Console.
10. To persist the shifted fiscal periods, click Commit.
11. To implement your changes, restart the nodes. For instructions, see "Starting and Stopping the
Note: The adjusted fiscal periods apply to the display of financial data in all languages.
Using the Administration Console to Import Fiscal Periods

To import the modified period definitions into PPM Center:

2. In the left panel, expand the Administration Task section, and then select Generate fiscal
periods.
3. In the right panel, select the Import option.
4. Click Browse, and then navigate to and select the period
definition file from which you want to copy fiscal period definitions.
5. Click Submit.
The imported fiscal periods are listed in the right panel.
6. To persist the imported fiscal periods, click Commit.
7. To implement your changes, stop, and then restart, your PPM Servers.
Using the Administration Console to Export Fiscal Periods

To export current fiscal period definitions from PPM Center to a specific file:
2. In the left panel, expand the Administration Task section, and then select Generate fiscal
periods.
3. In the right panel, select the Export option.

4. In the File box, type the name of the file to which you
want to copy fiscal period definitions.
5. Click Submit.
The Exported Periods tab lists the fiscal periods to be exported.
6. Click Export to File.
7. In the File Download dialog box, click Save.
8. Navigate to the PPM Server directory in which you want to store the file, and the save the file.

Note: On the PPM Server, the default directory for the fiscal periods definition file is
9. Check the directory you specified and verify that it now contains the file you exported.
Note: For information about how to use the script to export fiscal
period definitions, see the guide.
Using the Administration Console to Generate Translations for Fiscal

Periods
You can use the Administration Console to generate translations for fiscal periods in any of the
languages installed on PPM Center. Month names and period formats are as specified in the language
configuration files. After you generate the translations, a user can view the fiscal periods in the session
language he selected at logon. The translated periods cover the same time span as the periods covered
for existing languages.
To generate translations of fiscal periods in any languages installed on PPM Center:
2. In the left panel, under the Administration Task section, select Generate fiscal periods.
3. In the right panel, select the Generate translations option.
4. In the Languages list, select one or more of the languages. (Use the key or the key to
select multiple languages.)

5. Click Submit.
In the right panel, a tab that lists the translated periods is displayed for each of the added
languages.
6. To persist the added translations, click Commit.
7. To implement your changes, stop, and then restart, the PPM Servers.
Note: For information about how to use the script to create periods for
languages installed on a PPM Center instance, see the guide. For
information about using multiple languages on a single instance of PPM Center, see the
Viewing and Modifying Server Configuration Parameters

from the Administration Console
The Administration Console lists two types of server configuration parameters: and
After you change the value of a static parameter, you must restart the PPM Server(s) to implement the
change. If you change the value of a non-static parameter, there is no need to restart your PPM Server
(s).

The Administration Console displays read-only parameters in gray text. Read-only parameters are
either sensitive parameters such as passwords or parameters that you cannot change without
compromising the PPM Center system.
If you start Administration Console using HTTPS, then sensitive parameters that were formerly
displayed in grey text become editable and are displayed normally. If, for some reason, you must modify
values for other read-only parameters, you must either run the script, or edit the
file directly.
Note: The Administration Console displays only the parameters that are defined in the KNTA_
SERVER_PARAM_DEF_NLS table. If a parameter is not listed in the Administration Console, then it is
probably missing from the KNTA_SERVER_PARAM_DEF_NLS table.
Although you can modify server configuration parameter values directly in the file or
using the configuration tool ( script), HP recommends that you modify the values from the
Administration Console. (See "Modifying Parameters from the Administration Console" on the next
page.)
Note: You cannot use the Administration Console to either add parameters to or remove
parameters from the file.
For information about how to run the script, see "Standard Configuration" on page 99.
For information about how to change parameter values in the file, see "PPM Center
Configuration Parameters" on page 422.
Viewing Parameters from the Administration Console

To view parameters from the Administration Console interface, do the following:
2. In the left panel of the Administration Console window, expand the Administration Task section,
and then click Application Configuration.
The Edit PPM Application Parameters table in the right panel lists all the server configuration
parameters, along with their descriptions and current values for the selected scope. (The Scope
value defaults to Cluster or, if the instance consist of just one node, the name of the single
PPM Server.)
3. To specify the scope of the parameters listed, do one of the following:

o To view the parameters that are common to all of the nodes in the cluster, from the Scope list,
select Cluster.
o To view parameters for a specific node, from the Scope list, select the node name.
Note: If you select the name of the primary node from the Scope list, no parameters are
listed in the Edit PPM Application Parameters table. Instead, parameters and values for
the primary node are listed after you select Cluster from the Scope list.
4. To view the setting for a specific parameter, in the box above the Parameter Name heading, type
the first few letters of the parameter name to jump to the parameter names that match in the
list.
Modifying Parameters from the Administration Console

To modify parameters from the Administration Console interface:
2. In the left panel of the Administration Console window, expand Administration Task, and then click
Application Configuration.
The Scope list displays the names of all nodes in the cluster.

3. Click the Value field for the parameter to modify, and then type a new value to replace the existing
value.
4. Repeat step 3 for each parameter you want to change, and then click Save.
Note: Make sure that you save your changes before you close the Administration Console.
Otherwise, any changes you made are lost.

5. (Cluster only) If Cluster is the selected scope, and you change the value of a parameter, and then
click Save, a dialog box opens and gives you the option of applying the changed parameter value
across all nodes.
To apply the new value to all nodes in the cluster, click Yes. To retain node-specific overrides for the
parameter, click No.
6.
Note: The Yes option works only when you have created a shared folder for the
file to give all nodes in the cluster access to the same file.
7. If you change the value of a static parameter, the following warning is displayed to advise you that
you must restart the PPM Server to implement the change.
8. To implement your changes, stop the nodes, run / and then
restart the nodes, one at a time.
the PPM Server" on page 87. For information about the script, see
"kUpdateHtml.sh" on page 537).
The parameter values that you modify from the Administration Console take effect the next time the
parameter values are used.

Configuring and Migrating the PPM Center Document

Management System from the Administration Console
As the PPM Center administrator, you can use the DMS Configuration tool in the Administration Console
to perform the following tasks directly:
l Specify a different directory as the document repository for your Document Management System
(DMS).
l Migrate your current DMS to a different supported DMS.
The configuration is centralized. That is to say, changing the configuration from the Administrator
Console impacts all PPM Server nodes when using clustered configuration. Moreover, no PPM Server
restart is required for changes to take effect—the DMS Driver will be reloaded on all PPM Server nodes
with the new configuration when you save the updated parameters.
Specify a Different Directory for Your DMS
To specify a different directory as the DMS repository for attachments:
1. In the Administration Console Actions panel, select Administration Task > DMS Configuration.
2. In the right panel, click Edit.

The Administration Console displays the current DMS solution and the current directory specified
as the document repository.
Note: The Edit button is available only when your current DMS is PPM Center File System.
3. In the dms.filesys.attachmentDir box, type the path to the directory you prefer to use as the new
repository.
Note that specifying a different directory path does not migrate the documents stored in the
current directory to the new directory.
If you specify the current DMS parameter to point to an empty DMS, the existing documents in your
PPM Center will be lost.
4. Click Save.
Migrate Current DMS to a Different Supported DMS
To migrate your existing document management system to a different supported DMS:

1. In the Administration Console Actions panel, select Administration Task > DMS Configuration.
2. In the right panel, click Migrate.
3. From the Target DMS list, select the document management system to which you want to migrate
your existing DMS data.
4. To test the connection to the selected target DMS, click Next.

5. To start the DMS migration, click Start Migration.
The Administration Console displays the progress of the document migration from the PPM Center
File System to the target DMS you selected. The progress data displayed includes the number of
attachment files that successfully migrated as well as the number that failed to migrate.
6. To see the logs for files that could not be moved to the new DMS, click View failed files logs.
7. To try again to migrate unsuccessfully migrated files, click

Retry failed files.
8. To switch to the PPM Center DMS, click Start Transition.
9. To retire the old DMS and launch the new DMS, click Commit.

For more information about migrating PPM Center DMS, see the Document Management Guide and
Reference.
Browsing and Downloading <PPM_Home> Directory Files

from the Administration Console
You can browse and download directory files from the Administration Console with the File
Browser tool.
The Administration Console File Browser tool is available to any PPM Administrator with the following
access grants:
l Sys Admin: Server Tools: Execute Admin Tools
l Sys Admin: Server Tools: Execute File Browser
Caution: Users can view contents of all the files in in read-only mode once they have
access to the File Browser, HP recommends that you provide the Server Tools: Execute File Browser
access grant only to selected PPM Center administrators.
Note: The directory is not accessible through the File Browser and is not
listed in the contents of as it contains the sensitive private key used for SSL
encryption. You must connect directly to the PPM Server machine to access this folder.
When initially accessed, the File Browser displays all files and folders located in the
directory:
l Click any file to download it, or click any folder to view its contents.
l When a folder's contents is displayed, you can select one or more files or folders and download them
as a Zip file by clicking Download selected file(s) as .Zip available at the bottom of the pane.
The folder hierarchy in the zip file will be rebuilt relatively to the
directory. Empty folders in the Zip file will contain an empty file so that empty folders are
not removed automatically from the Zip file. These empty files are created dynamically when the Zip
file is generated and are not present in the PPM Application Server file system.

File information displayed includes name, size, permissions (R for read, W for write, X for execute), and
last modification date.
l You can sort the files and folders displayed by clicking a column header. Click twice on the same
column header to reverse the sorting order. A small vertical arrow will be displayed in the column
header currently used as the sorting criterion.
Note that when sorting files and folders, the folders are always displayed before the files,
independent of the sorting criterion.
Also, unless you are viewing the folder, a folder is displayed at the beginning of the
list to let the user access the parent folder.
l To navigate to other folders, click a desired bookmark on top of the File Browser, or click any
element of the breadcrumbs representing the current folder (path is relative to ).

Note:
l When PPM Center is configured in cluster mode, the File Browser only displays the files of the
directory that contain the PPM Center instance to which you are currently
connected to.
l If you want to access another of the cluster, you must manually connect to a PPM
Center instance hosted in this > folder.
l When zipping files and folders, you can only select files and folders located in the same folder. If
you switch to another folder while some items are selected, the selected items are not included
in the generated zip file.
Cluster Configuration Considerations
l When PPM Center is configured as a server cluster and there are multiple PPM Center instances in
the same , you can access all the files of all the PPM Center instances located under the
same folder as the instance you are connected to.
l When selecting Logs or HotFix links in the bookmarks, you must manually choose the PPM instance
you want to access. The folder is automatically displayed when the instance is selected.
Performance Concerns
The files listing can take many seconds if there are many thousands of files to list in the folder which
contents are displayed, for example, the
folder, where images of PPM Charts are saved and only deleted after 7 days by
default.
Note that there is no significant performance or memory impact on the PPM Server if you decide to
download the entire contents of as a zipped file. This is a safe (though time-consuming)
operation, but some temporary files might not be included in the resulting zip file if, for example, they
are locked when you try to include them in the Zip file.

Running SQL Queries from the Administration Console

You can run database queries directly against the PPM Center database schema from the
Administration Console.
Note: For information about how to run SQL queries from the PPM Workbench, see "Running SQL
Statements from the PPM Workbench" on page 331.
Running SQL statements from the Administration Console is essentially the same as running them from
the PPM Workbench. However, from the Administration Console you can run a statement that ends with
a semicolon (;).
To run a SQL statement (select statement only) from the Administration Console:
1. In the Administration Console Actions panel, select Administration Task > SQL Runner.
2. In the SQL Statement box, type the select statement to run against the PPM Center database.

3. Click Run SQL.
The Results table displays the query results in numbered rows.
4. To test the connection speed between the PPM Server and the PPM Center database, click the Ping
DB button.
Note: Because the Administration Console uses a Web Interface, it ignores the connection
time between the web client and the PPM Server.
SQL Statement Execution Details
The Execution Details section of the SQL runner page displays the following:
l The Server Roundtrip value represents the time spent (in milliseconds) between the PPM Server and
the PPM Center database.
Note: In Workbench, the Server Roundtrip value represents the time spent between the PPM
Workbench client and the PPM Server). In either context, the measure is a good indication of
measure network latency.
l The SQL Execution value represents the duration of the SQL run in milliseconds.

l The ResultSet Extraction value represents the amount of time (in milliseconds) required to extract
results from the results set.
l The Total Time value represents the amount of time (in milliseconds).
Exporting SQL Run Results
You can export the SQL run results in either comma-separated or text format. If you do export the
results, any sorting and grouping you perform from the Administration Console is discarded. Only the
raw results are exported.
To export the data to a file in comma-separated format:
1. Click Open as CSV.
The Administration Console displays the message "Do you want to open or save
(< > KB) from ?"
2. Click Open, Save, Save as, or Save and open.
To export the data to a text file:
1. Click Open as CSV.
The Administration Console displays the message "Do you want to open or save
from < >?"
2. Click Open, Save, Save as, or Save and open.
Creating a Dashboard Datasource (and List Portlet) from a

SQL SELECT Statement in the Administration Console SQL
Runner
You can create a dashboard datasource and a list portlet from any SQL statement that runs in the
Administration Console SQL Runner.
You can choose whether the dashboard and/or the list portlet is enabled or disabled upon creation.
Default choice is enabled, however you might want to disable it if it is created on a production
environment and that some specific access grants should be added to it to restrict its access before it
can be used by PPM Users.

Once created from the Administration Console, the datasource can be edited from PPM Workbench (to
add filters and access grants) and the list portlet can be edited from the PPM Center portlet definition
page, like any datasource or custom list portlet.
To create a dashboard datasource and a list portlet from the Administration Console,
3. Under the Administration Console node, select Administration Task > SQL Runner.
4. In the SQL Statement text box, run the SQL statement that you want to create a Dashboard
Datasource with.
5. Click the Create Dashboard Datasource button.
The Create Dashboard Datasource dialog opens.
6. Specify names of the datasource and the list portlet that you want to create as described in the
table below.

Field/Option Description
Datasource Specify a name for the datasource that you want to create.
Name
List Portlet Specify a name for the list portlet that you want to create.
Name
The List portlet creation is optional. If you keep this field empty, no list portlet will
be created, and button name changes accordingly.
Enable Select to enable the datasource upon its creation.

Datasource
Enable List Optional. Select to enable the list portlet upon its creation.
Portlet
If you choose to enable the List Portlet, any PPM User can add it directly to their
dashboard after the portlet creation.
Note:
o You CANNOT enable the list portlet but disable the datasource.
o If you enter a name for the list portlet or datasource that already exists, you get an error
message.
For example,
7. Click Create Dashboard Datasource and List Portlet.
The Creation Successful confirmation pops up.

8. Click OK.
9. If you chose to enable the List portlet, any PPM User can now add it directly to their dashboard.
SQL Syntax Accepted and Limitation
Most of the SQL syntax is accepted as long as it is a statement.
You can use the operator for columns, such as:
All columns and their types will be discovered automatically.
However, you cannot use bind variables in the SQL. If you need to use bind variables, first create the
datasource with constants values set in place of variables, and then edit the datasource definition in
the PPM Workbench to add the bind variables.
Gathering Information for HP Software Support from the

Administration Console
You can run the tool from the Administration Console to gather information about the
PPM Server node you currently access with your web browser, and then send that information to HP
Software Support to help diagnosing system problems. This helps to ensure that your issues can be
resolved quickly, with minimal requests for information.

The kSupport tool is designed to serve as a troubleshooting knowledge system for PPM Center.
Embedding into the tool the knowledge gathered from supporting PPM Center customers around the
world, HP expects the tool to make PPM Center self-diagnosable and self-healable. The flexible
interface of the tool makes it easy to absorb new knowledge as PPM Center develops and HP Software
Support’s knowledge grows.
To collect support data for your PPM Server:
1. In the Administration Console Actions panel, select Support Task > Generate Support
Information.

2. Provide the information described in the following table.
Note: Although none of the fields listed are required, to generate information for HP Software
Support, you must select at least one of the check boxes.
Field Description
Company Name of your organization

Name
Incident Number HP has assigned to the incident you reported

Number
System Select this check box to generate log and report information.
Information
o Standard. Select this option to collect information about the PPM Server
level) log and PPM Server reports.
o Full. Select this option to collect information about the following logs:
l Upgrade
l Install

Field Description
l Deploy ( level)
l Server ( level)
l JDBC log
Note: To see a list of the reports covered, move your cursor over the text
"Collect Server (PPM_Home/server level) log and reports."
Super Selecting this check box enables you to search logs by specifying time range and
support keywords.
information
o Start time. Click the Show Date Chooser icon to specify a start time.
o End time. Click the Show Date Chooser icon to specify an end time.
o Logs search key. Enter keywords for logs search.
If specifying both the time range and the keywords, you can retrieve logs
containing the keywords within the time range. This helps quickly locate the
desired information from the massive logs and avoid getting outdated logs.
Note: If the time zone of PPM Server has been changed, the logs cannot be
extracted correctly by the specified time range.
Supper Selecting this check box enables you to gather information based on modules.
support
modules Then, select specific modules that you want to gather information for. For
example, if you want to gather information for the Demand Management module
only, you can just select the DM checkbox. The retrieved information for the
Demand Management module is stored in the
directory.
Note that the check boxes for the Core, DBChangeCheck, FilesystemCheck, and
SeedDataCheck modules are always selected by default, no matter which modules
you select. This means the script is always run for these four modules. Running
the script on the Core module gathers common information not related to any
specific modules. Running the script on the other three mandatorily selected
modules collects data that users have modified. For more details, see Collect
Modified Data below.

Field Description
The DBChangeCheck module is enhanced in 9.30,
Running the script on the Performance module gathers information about PPM
Center performance.
For more details and usage of the ErrorPageCollector check box, see Collect HTML
Source Codes for Error Pages below.
In order to proactively detect some common configuration errors, data missing

issues, potential data corruption issues, and so on, the kSupport tool can perform
some sanity checks for several modules, especially for integration modules. The
sanity check is designed based on best practices of PPM Center Support, so it may
help find out the causes for some system issues in less time.
Note:
o If an integration module is not enabled, you cannot retrieve support

information for that module by selecting the check box for the
corresponding module here.
o Specifying the time range in the Super support information check box
section also helps retrieve database queries within the time range. For
example, if you specify the time range and select the DMS check box, only
the integration events within the time range will be retrieved.
Run SQLs Select this check box to include SQL SELECT statement results in the support
information you generate.
Run SQLs Select this check box to specify either a single SQL file, or a Zip file that contains
from Zip multiple SQL files (or subdirectories). Then, click Browse to navigate to and select
file or the file(s).
single SQL
file
Note: Notes:
o Only statements are retrieved and run.
o Make sure that the SQL statements you type in the text box do not exceed
1 MB in size.
Enter your Select this check box if you want to simply type one or more SQL

Field Description
SQL script statements to run. Then, type the statement(s) in the text box provided.
in the text
box below
Note: If you type multiple statements, make sure that you start each
statement on a new line and end each statement with a semicolon ( ).
3. Click Generate.
Note: Normally a copy of the file is included in the generated kSupport zip file (in the
folder).
If your instance is in clustered environment and the file is located in the shared
folder for the cluster, after generating the kSupport zip file, you can find a copy of the
file in the folder.
Collect Modified Data
Data that users have modified are collected everytime you run on the following three
mandatorily selected modules.
l DBChangeCheck. The script compares user’s database objects against the baseline data, such as
constraints, packages, triggers, and indexes. The retrieved comparison report is stored in the
directory.
The constraint comparison report can be found in the

file. The report lists the following:
o Missing primary keys, foreign keys, and unique constraints
o Custom primary keys, foreign keys, and unique constraints
l FileSystemCheck. The script compares the baseline data with user’s file system, such as , ,
and class files in the directory and
directory. The retrieved comparison report is
stored in the directory, and the modified files are
stored in the directory.

l SeedDataCheck. The script compares the baseline seed data with user’s seed data, such as request
status, workflows, and portlet definitions. The retrieved comparison report is stored in the
directory.
Collect HTML Source Codes for Error Pages
Collecting HTML source codes for JS errors on PPM Center standard user interface can help address
these errors more quickly.
To collect HTML source codes,
2. Navigate to the page you want to trace.
3. From the menu bar, select My Links > Trace Html and Upload.
A dialog pops up.
4. Click OK.
5. Navigate to the Generate Support Information page in the Administration Console.
6. Select ErrorPageCollector in the Super support modules section.
7. Click Generate.
HTML source codes for error pages are stored in the

directory.
Note:

l After you generate support information in the Administration Console, the recently traced error
pages will be cleaned.
l Not only error pages but also normal pages can be traced.
l If you are using Internet Explorer 9.0, and open the Developer Tools, you may not be able to
trace HTML. To address this issue, do one of the following:
o Do not use the Developer Tools when tracing HTML.
o Refresh the page when Developer Tools is opened.
Changing Data Display in Administration Console Tables

This section addresses the various ways you can arrange the data displayed in the right panel of the
Administration Console.
Changing Sort Order
To change the sort order of the values in a column in the Administration Console:
l Right-click the column heading, and then select Sort Ascending or Sort Descending.
Toggling Column Display
To toggle the display of the columns in the right panel:
l Right-click any column heading, select Columns, and then select (or clear) a column heading in the
shortcut menu.

Grouping Displayed Data
To group displayed data based on the dimension in the heading:
l Right-click the column heading, and then select Group by <Heading_Name> from the list.
Filtering Displayed Data
To filter displayed data based on a character string in parameter names, assigned values, or in
descriptions:
l Place your cursor in the filter field above a column heading, and then type the text for the filter.

The table displays all data that include the string you specified (specific to the column).
Freezing Column Width
To freeze a column so that its width does not change if you resize the window:
l Right-click the column heading, and then select Freeze Column "<Column_Name>" from the
shortcut menu.
Return to "Tools in the Administration Console" on page 281.
Using the Unchecking Showing Total Number Tool from

Administration Console
The Unchecking Showing Total Number tool is added to the Administration Console. It allows you to clear
the total number of records displayed on the concerning pages, and thus improve PPM Center system
performance.
To use the tool,
1. Log on to PPM Center and launch the Administration Console.
2. In the left navigation pane of the Administration Console, expand the Administration Task section,
and then select Unchecking Showing Total Number.

3. In the right panel, click Apply for Request Search or Java Portlets of Requests Category.
Caution: Be careful when clearing the Show Total Number of Records checkbox. This batch
operation is irreversible.
For more information about showing total number, see the .
Installing Autopass License Key File and Viewing License

Summary in Administration Console
Install an Autopass License Key File
To do so,
For information about obtaining an Autopass license, see "Key Considerations" on page 36.

5. On the License Install page, click Browse to locate the license file you saved, and then click Install.
There is no need to stop and restart the PPM Server for the license to become effective..
View A Summary of Autopass Licenses Purchased and Installed on the PPM Server
You can view a summary of Autopass licenses that you purchased and installed on the PPM Server from
the Administration Console window.
The View History section displays a summary of all Autopass licenses installed on the PPM Server
that are valid for use. Only activated licenses are shown in the View History section.
4. Expand the plus sign in front a license entry to view details.
For example,
The following table describes columns in the View History table:
Column Description
License Full title of the Autopass license key you generated from the HP
Licensing for Software portal
Product Feature A list of product features that are available with the Autopass
license

Column Description
Capacity Number of users available with the Autopass license
Start Date Start date of an Autopass license key
End Date End date of an Autopass license key
Delete Click the Delete button to remove a corresponding Autopass

license key
Note: To view consumption status of implicit features available with each Autopass license, you can
still go to the License Administration window in the PPM Workbench.
Remove a License Key
To remove a license key,
1. In the Administration Console navigation pane, select Administration Task > License.
2. In the View History section, click Delete for the license key that you want to remove.

Server Tools In the PPM Workbench

The following sections provide information about the administration tools you can access through the
PPM Workbench:
l "Access Grants Required to Use Server Tools" below
l "Accessing the PPM Workbench Server Tools" on the next page
l "Running Server Reports from the Admin Tools Window" on page 327
l "Running SQL Statements from the PPM Workbench" on page 331
l "Running an SQL Script with SQL*Plus on a Windows System" on page 333
l "Setting Debugging and Tracing Parameters" on page 333
l "SQL Debugging for All Product Areas" on page 337
l "Tracing PPM Center Pages with the SQL Tracer Tool" on page 342
Access Grants Required to Use Server Tools

The following table lists the names and descriptions of the three access grants that give users various
levels of access to the Server Tools window.
Table 9-2. Server tools access grants
Access Grant Permissions
Sys Admin: View Server Lets the user view the Admin Tools and SQL Runner windows in read-
Tools only mode.
Sys Admin: Server Tools: Stop the PPM Server by using when you enable
Execute Admin Tools authentication with the
REMOTE_ADMIN_REQUIRE_AUTH parameter set to ,
send messages through , execute administration reports in
the Admin Tools window, and view the SQL Runner window in the Server
Tools Workbench.
Sys Admin: Server Tools: Lets the user run SQL queries in the SQL Runner window and view the
Execute SQL Runner Admin Tools window in read-only mode.

For more information about security groups and access grants, see the
Accessing the PPM Workbench Server Tools

To access the server tools in the PPM Workbench:
2. On the Open menu, click Administration > Open Workbench.
3. On the shortcut bar, click Sys Admin > Server Tools.
The Admin Tools and the SQL Runner windows open.
Return to "Server Tools In the PPM Workbench" on the previous page.

Running Server Reports from the Admin Tools Window

Use the Admin Tools window to run server reports such as Server Status Report and Cache Manager
Statistics. The following table lists the server reports that you can generate from the Admin Tools
window.
Table 9-3. Server reports
Report Name Description
Broker Information about open database pool connections, organized by connection ID.
Connection
Broker In Use Information about database pool connections in use, organized by user. If the server
Sessions parameter is set to , this report also shows stack
traces of where the connection is allocated.
Broker Statistics on database connection usage in the connection pool, to help assess
Performance system performance.
For performance reasons, the PPM Server holds a connection pool to the database
and reuses these connections for accessing the database. Prepared statements
created within a connection are also held open in a cache.
If the PPM Server cannot allocate more connections, threads that need to access
the database might need to wait for a connection.
This report also shows:
l Number of threads waiting for connections
l Average duration threads had to wait for connections
l Percentage of threads that had to wait for connections
l Total number of connection requests, and if JDBC logging is enabled
l Statement cache hit rate percentage (over the last 100 statements)
CacheManager Displays the number of objects in the cache of each entity, the total cache size (in
Sizes KB), and the average size of each cached object type.
CacheManager Displays useful statistics on the caching behavior of each cacheable entity in PPM
Statistics Center, including:
l Hits, misses, and hit rate

Table 9-3. Server reports, continued

l Number of cache flushes (broken down by the categories "old", "idle",

"reclaimed", and "max cache size reached")
l Average load time
l Cached object count and maximum idle time
Client Font All supported fonts for the PPM Center installation.
Client Property Details about the environment of the client computer currently running the PPM
Workbench.
Client Time All time zones recognized by the client.

Zone
Execution Batch executions in progress.

Dispatcher
Manager
Execution Batches pending execution due to the lack of available execution manager threads.
Dispatcher
Pending Batch
Execution Batches pending group execution (batches that are grouped together) due to the
Dispatcher lack of available Execution Manager threads.
Pending Group
Installed Displays the names and versions of HP Deployment Management Extensions

Extensions installed (if any).
JVM Memory Free and total memory in the PPM Server JVM.
Kintana RMI All RMI connection threads.
Server Cache Shows the following cache information:

Status
l Cached entities
l Number of units that can be cached
l Number of free units
l The number of hits and misses, and the miss rate
l Number of entities swapped

Table 9-3. Server reports, continued

l Amount of memory taken up by the cache
Note: Although this report displays information that is similar to the that
displayed in the CacheManagerStatistics report, the data is for a different set
of cached objects.
Server All server parameters in effect for each of the active servers. Includes parameters
Configuration not specifically set in the file.
Server Event Event messages that the PPM Server can send to the client.
Listener
Server Logon Information about all users logged on to the PPM Server(s) and logon information
such as IP address and idle time.
This information is used to determine PPM Server load. If server clustering is used,

this report provides a picture of load distribution.
Server Status Status information about PPM Server(s):
l Whether the server is available and its start time
l Length of time the server has been available
l Number of users logged on to the server
l Number of users active during the last minute
You can also use the Administration Management Console to view the status of
PPM Servers. For information about the Administration Management Console, see
"Viewing PPM Server Status from the Administration Console" on page 284.
Server Thread Information about running threads within a PPM Server(s).
This information is used to determine which services are running. If a server cluster
is used, this report also provides information about which server is running these
services.
To select and run a server report:

3. On the shortcut bar, click Sys Admin > Server Tools.
The Admin Tools and the SQL Runner windows open.
4. Expand the report list in the Admin Tools window and select a report.
5. Click Submit.
The Admin Tools window displays the output of the selected report.

Note: If you run a report on a PPM Center instance that supports multiple languages, then the
resulting report is generated in the language you selected at logon (your language).
Because the report is only generated once, the language used to display the contents does not
change, and any user who later views the report sees it in its original language. For information
about multilingual support in PPM Center, see the
Running Server Reports from the Command Line
You can also run server reports directly from a command line on the PPM Server using the
script, which is located in the directory. For more
information about the script, see "kRunServerAdminReport.sh" on
page 532.
Return to "Server Tools In the PPM Workbench" on page 325.
Running SQL Statements from the PPM Workbench

You can use the SQL Runner window to run database queries directly against the PPM Center database
schema using the PPM Workbench instead of using an external program such as SQL*Plus. One benefit
of using SQL Runner is that you can gain access to the database directly, without having to submit the
database password. Developers and administrators can also use the SQL Runner window to test custom
validations and request rule SQL, among other things.
Note: You can also run SQL queries from the PPM Center Administration Console.For details, see
"Running SQL Queries from the Administration Console" on page 307.
To run an SQL statement from the SQL Runner window:
1. If the Admin Tools window hides the SQL Runner window, minimize it.
2. In the SQL Statement box, type the SQL statement to run.
Caution: Make sure that your SQL statement does not end with a semicolon (;).
3. To run the SQL statement, click Run SQL.

The SQL Runner window displays the list of results in the table below the SQL statement. It also
displays timing information such as how long the statement took to run, and how much of that
time was spent in the database.
4. To view the results as text, click Open As Text.
The following table lists the controls in the SQL Runner window.
Table 9-4. Controls in the SQL Runner window
Control
Name Control Type Description
SQL Text box Use this box to type an SQL query for running and testing purposes.
Statement
Note: Make sure that you do not include a semicolon (;) at the
end of your SQL statement.
Server Read-only text Amount of time (in milliseconds) spent sending the SQL statement
Roundtrip box out to the network and back.
Used to show network latency and performance.
SQL Read-only text Amount of time (in milliseconds) the database spent actually
execution box executing the SQL statement.
Use the displayed information to tune validations or write complex

statements to address performance concerns.
ResultSet Read-only text Amount of time (in milliseconds) that the server spent processing
Extraction box the SQL statement results.
Total time Read-only text Total amount of time (in milliseconds) spent running the SQL
box statement.
Run SQL Button Runs the SQL statement displayed in the SQL Statement box.
Clear Button Clears the window.
Ping Server Button Tests the connection speed between the client and the PPM Server.
Ping DB Button Tests the connection speed between the client and the database
(through the PPM Server).
Open As Text Button Opens results in a text window.
You can cut and paste information from this window.

Running an SQL Script with SQL*Plus on a Windows System

If your PPM Center instance is running on a Windows system, and you are using the SQL*Plus utility to
run an SQL script, the utility "expects" to get the exact number of parameters defined in the script.
Some versions of SQL*Plus ignore null command-line parameters and get hung up waiting for missing
parameter values.
Example
In the following line, the second parameter is null. But, because SQL*Plus is a command-line utility, it
waits for the user to input the second parameter value.
To work around this problem, add the following to the file:
A valid version number is
Setting Debugging and Tracing Parameters

Use the Debugging and Tracing Settings dialog box to set debugging and tracing parameters at both the
user and server levels.
To open the Debugging and Tracing Settings dialog box:
3. On the Edit menu, click Debug Settings.

4. To override the default debug level set for your PPM Center sessions, from the Debug Level list in
the User section, select a different value.
The Debug Level list values map to values in the file as

follows:
l No debugging information is equivalent to the parameter value . Only errors are logged.
l Normal debugging information is equivalent to the parameter value . Errors and information
that describes the normal tasks that the running server is performing are logged.
l Maximum debugging information is equivalent to the parameter value . This setting provides
the most logging information. In addition to the normal debugging information, information is also
logged for various server functions.
This additional debugging information can be useful for troubleshooting any problems you
encounter in PPM Center. If a problem arises, you can set the debug level to Maximum debugging
information, perform the problematic action again, and then check the server logs for information
that can help resolve the issue.
Caution: Make sure that you do not to leave the server running in debug mode for too long. A
large volume of extra information is written to the logs, taking up disk space much more quickly
than during normal operation. The extra logging overhead can affect system performance.

Log User Name Setting
If you want your user name written into the log for each line of debugging text that corresponds to
actions you have performed, select this checkbox. This can be helpful if you need to sift through the
server logs to find information relevant to your user session. (The Log User Name checkbox
corresponds to the configuration parameter.)
Log TimeStamp Setting

If you want a timestamp written into the log for each line of debugging text that corresponds to actions
you have performed, select this checkbox. The timestamp can help you locate information in the server
log files about events that occurred at a specific time, or to determine how much time elapsed between
specific logged statements.
Bear in mind that including the timestamp adds text to each logged statement. This bloats the log file
and can make it more difficult to read. (The Log TimeStamp checkbox corresponds to the
parameter in the file.)
Enable DB Trace Mode Setting
To enable the SQL trace facility during your PPM Center session, select the Enable DB Trace Mode
checkbox. This facility ensures that performance statistics for all SQL statements that you run are
placed into a trace file. (The Enable DB Trace Mode checkbox corresponds to the
server configuration parameter.)
PL/SQL Settings
The PLSQL field provides the following Procedural Language/Structured Query Language (PL/SQL)
options:
l Select the Enable Profiler checkbox to profile the run-time behavior of the PL/SQL code that PPM
Center applications use by calling the Oracle-supplied PL/SQL package
Note: You must set up the PL/SQL package. For an example of how to do this, see "Example of
how to set up the Oracle profiler:" on the next page.
The profiling information is logged in a JDBC log file in the PPM Center directory. Enabling the
profiler can help you to identify performance bottlenecks.

Note: Because running the package might slow system performance and
reduce storage space, HP recommends that you use it only for debugging.
Example of how to set up the Oracle profiler:
l Select the Trace Call Stack, Trace SQL, and Trace Exception checkboxes to enable the Oracle
package functionality that the PL/SQL programs (used by PPM Center applications) use.
The output of the profiling information is saved to a JDBC log file in the
PPM Server directory.
Note: Because running the package can have a negative effect on system
performance and storage space, use it only for debugging.
Server Settings
To override the default logging level for the entire PPM Server, and not just your user session:
1. Under Server, in the Debug Level list, select one of the following.
Note: The following settings correspond to the settings for the

server configuration parameter. The value names, however, are different.

o No debugging information is equivalent to the parameter

value . Only errors are logged.
o Normaldebugging information is equivalent to the parameter value Errors and

information that describes the normal tasks that the running server is performing are logged.
o Maximumdebugging information is equivalent to the parameter value . This setting

provides the most logging information. In addition to the normal debugging information,
information is also logged for various server functions.
This additional debugging information can be useful when troubleshooting any problems you
encounter in PPM Center. If a problem arises, you can set the debug level to Maximum
debugging information, perform the problematic action again, and check the server logs for
information that can help resolve the issue.
For more information about the parameter, see "PPM Center

2. To have the PPM Server(s) maintain a Java Database Connectivity (JDBC) log file, select the Enable
JDBC Logging checkbox.
SQL Debugging for All Product Areas

If you turn on SQL debugging, PPM Center now collects statistics for the following legacy product areas:

l Demand Management web pages
l Deployment Management web pages
To turn on SQL debugging, set the server parameter to .
The debugging console display includes information about the SQL statements executed by the legacy
code. The web pages of the legacy areas now display the debugging console.
System Logging in PPM Center

Every error message logged in PPM Center includes a unique identifier that you can use to locate the
corresponding error in the log file.
Note: Error messages are displayed in users' session languages, but log file content is not. For
information about session and system languages, see the
The following six types of exceptions occur in PPM Center:
l User errors
l Internal errors
l Warnings
l Informational
l Status advisories
l Questions

Note: Only messages for internal errors display the correlation information.
Service and context information are placed in the log messages based on the values of two logging
parameters in the file, which are described in the following sections.
Context Option Logging Parameter

You can use the context option parameter to
specify extra information to include in server exception logs. The possible values are listed in the
following table.
Value
(bitwise combination value in
binary) Additional Information Logged
0 (default) None
001 Context information, if provided
010 All of the stack trace for log messages, including those without
exception
3 All
If bit 1 is set to 1 (001), then the server logs include any exception context information available. If bit 2
is set to 1 (010), then the server logs include stack trace for log messages, including messages without
an exception. The combination of these bits determines the overall setting. If all bits are set (value 3),
then all details are logged.
Redirecting Log File Output

If you need to direct log output to a specific log file, and not to server log and console, you can do so
using the logging configuration parameters. For example, the activity monitor and Background Services
monitor log content to the file. The content is not shown on the server log or in the
console.
Class Filters Logging Parameter

You can use the parameter ( ) to
specify the class names to include in the stack trace (substring of stack trace classname, including

packages). To reduce the log file size, PPM Center uses this parameter value to filter out the classes
that are of no interest in stack traces.
If you specify multiple classes or packages, use commas to separate them. If the full class name in a
stack trace contains one of the specified classes or package names, then that line is preserved. For
example, if the value is set to then any class names that contain the
or strings are kept.
The number of traces filtered out is added to server logs after the stack trace. The
parameter has no default value. If you do not set a
value, no classes are filtered out of the stack trace.
Note: For descriptions of the parameters in the file (located in the

directory), see "Logging Parameters" on page 502.
Log Levels for the install.sh Script

The log for the script ( ) uses the default INFO log level.
The possible log levels are as follows:
l ERROR. Print only error log (not recommended)
l INFO. Print error and information log (default)
l DEBUG. Print error, information and debug log (used in debugging)
Enabling Debugging On a Per-User Basis

You can turn on the debugging console and set a server logging threshold on a per-user basis. After you
do, a specific user logged on to PPM Center can toggle the debugging console by pressing and holding
the key and clicking the HP logo, which is located above the menu bar.
To enable debug logging to the file for a specific user:

1. Add the following server configuration parameters to the file and set the values for
both to true (case-sensitive):
o
o
2. (For "Tracing PPM Center Pages with the SQL Tracer Tool" on the next page only) Run the
script from SQL*PLUS as the SYS DBA user to provide the
necessary grants and permissions to the PPM Center users:
3. Open the file in a text editor, and then set the
parameter as follows:
USER_THRESHOLD = <PPM_Username>, <Log_Level>
The following table lists supported log levels.
Log Level Description
DEBUG Print fatal, status, error, warning information and debug log (used in
debugging)
INFO Print fatal, status, error, warning and information log
WARN Print fatal, status, error and warning
ERROR Print fatal, status, and error log (default)
STATUS Print fatal and status messages (Not recommended)
FATAL Print only fatal messages (Not recommended)
4. To configure finer-grained logging than that specified by the parameter, add
the following to the file:
The file is read periodically, so there is no need to restart the PPM Server(s) to enable
debug logging specific to the user. Logging occurs only for that particular user.
To enable the debug console for multiple users, add values (on separate lines).
Example:

USER_THRESHOLD = gchu, DEBUG
USER_THRESHOLD = pchapin, DEBUG
USER_THRESHOLD = bkordon, DEBUG
If the log level value meets the threshold criteria of the (set for that user) or
the then the message is logged.
Example 1
In Example 1, for a user logged in as ddalton, the system logs all DEBUG and higher (INFO, WARN, ERROR,
STATUS and FATAL) messages. For any other user, the system logs only ERROR, STATUS and FATAL
messages.
Example 2
In Example 2, the system logs all messages for all users. In this case, the
value ( ) set for ddalton has no effect.
Tracing PPM Center Pages with the SQL Tracer Tool

You can trace PPM Center pages with the SQL tracer tool to help diagnose performance issues caused
by poor SQL executions. For example, if you find a slow PPM Center page, you can turn on this tool to
collect information from Oracle side about the SQLs executed on this page and generate support files.
With these files, HP Software Support can better identify the performance bottlenecks and provide
suggestions on how to tune the performance.
Note: The SQL tracer tool works by identifying and tracking threads that handle HTTP requests. If
there are database actions happening outside the main threads that the Web server uses to
handle HTTP requests, those actions are not captured. For example, in the Demand Management
module, special commands are handled by threads spawned by request-handling threads, thus they
would not be captured by the tool.
To trace SQLs executed on a PPM Center page,
1. Log on to PPM Center, and open a page.
For example, the Search Request page.

2. Press and hold the key and click the HP logo located above the menu bar to enable the
Debugging Console.
The Debugging Console opens.
3. Set trace ID.
a. From the right end of the Debugging Console, click the show link.
The DB Stats list displays.
b. Click the latest record from the DB Stats list.

In this example, click /itg/web/knta/crt/RequestSearchResults.jsp.
The DB Statistics page opens in a new window.
c. Provide a value in the TraceID field, and select the Trace This Page checkbox.
Trace ID is the identification you define for collecting information. You can define any words or
string as a trace ID, just make sure you include the following characters: alphabetic characters,
numbers, and " ".
d. Close the DB Statistics details page.
4. Go back to the page you opened in step 1.
In this example, go back to the Search Requests page, and run the search again.
5. Get information from the traced page.
a. Repeat step a and step b of step 3 to reopen the DB Statistics page.
Now the page displays on-screen instructions for DBAs.

b. Follow the on-screen instructions to generate support files.
c. Send the following files that contain the execution plans of SQLs to HP Software Support.
l
l
l [traceid].xplan
Before sending the files to HP Software Support, check and make sure that there are no
warnings in the file.
The and files are generated by Oracle commands. For more

details, see Oracle documentation (http://docs.oracle.com/cd/B10500_
01/server.920/a96533/sqltrace.htm).
The script of the tracer tool generates the and the

files. The script gets SQL plans from the Oracle shared
pools. The file contains the information on whether the execution plans of
SQLs are fully generated. If you have not run the script timely, the SQL plans might get aged
out of the Oracle shared pools. As a result, you might see warnings when you open the
file.

(Optional) Enabling Debugging Console on Customized

Logo
If you have replaced the HP logo located above the menu bar with a customized one, to enable the
Debugging Console, do the following:
1. Make sure the following two files exist:
o
o
2. Open your customized file (located in the

directory), and add the following Java script to it:
3. Add Java script event to your logo, as follows:
onmousedown="return toggleDebugConsole(event);"
4. Include the Debugging Console section in your customized .

Locate the following lines:
Add the following script after them:
Logging of Physical Memory and Operating System Swap

File Space at Server Startup
Total and free physical memory and operating system swap file space are logged during PPM Server
startup.
The exception to this is AIX systems, on which this information is not available.
Maintaining Log Files

The PPM Server generates log files in the file system. Depending on the type of log file, certain
maintenance practices should be employed to maintain the file system. The following sections provide
maintenance recommendations for each type of log file.
Server Log Files

Server log files are stored in the directory. Server log files
are named and . The log timestamp setting (see "Log
TimeStamp Setting" on page 335) uses the format for the date and time the log was
rotated.
Active PPM Servers log their output to the file. The files are
archived versions of the file. The size of these old log files are determined by the

server parameter in the file. This parameter may be set to any value
(in kilobytes) to control the rotation. A high value results in fewer but larger log files.
Generally, server log files are required only when contacting HP Software Support to resolve server
issues. In most cases, it is safe to delete these log files on a regular basis.
The following parameters determine the data volume to be written to the logs by the server:
l
l
l
In the file, set these parameters to their default values:
By setting these parameters to their default settings, only critical error events are written to the server
logs. This decreases the number of server logs generated in the file system, thereby improving system
performance.
If the server experiences technical difficulties or server logs are required by HP Software Support,
increase the debug level.
Unless instructed otherwise by HP Software Support, always set the parameter to

.
To change the parameter dynamically at runtime, change the

parameter in the Edit > Debug Settings screen group in the PPM Workbench interface.
You can also retrieve current server settings by accessing the Server Tools window and running the
Server Configuration report.
Note: Unless instructed by HP Software Support, do not run a production server with the debug
levels set to . This can generate very large log files in the file system that could degrade
system performance.
Enable HTTP Logging
Caution: Do not enable HTTP logging if you use an external Web server.
To enable HTTP logging:

2. Set the server configuration parameter to .
3. Run the script.
4. Start the server.
The internal Web log is saved in NCSA Common format.
Example
Mail Notification for Specified Server Logs

Mail notification is available for specified server logs. As an administrator, you can decide the server
logs information to be notified by email through specifying regular expression or the combination of log
levels and regular expression.
To use the mail notification feature, you should first configure the SMTP related parameter in the
file and then configure the logging parameters as described in the following table. These
logging parameters are added in the file located in the directory.
Parameter Name Default and Valid

(*Required, **Required If) Description, Usage Values
ENABLE_SMTP_LOGGING If set to , mail notification Default:

for critical exceptions is enabled.
Valid values:
**SMTP.To The recipient of the notification. Default: N/A
Required if ENABLE_SMTP_ Valid values: Email address

LOGGING is set to
SMTP.From The sender of the notification. Default: N/A
If not specified, the email address Valid values: Email address

of the sender is derived from
EMAIL_NOTIFICATION_SENDER in
the file.

SMTP.Subject The subject of the notification Default: N/A

mail.
**SMTP.Filter. The keyword or regular Default: N/A

RegexToMatch expression to be monitored.
Valid values: Regular expression
Required if ENABLE_SMTP_
For example,
LOGGING is set to
SMTP.Filter.LevelMin The lowest log level to be Default: N/A

monitored.
Valid values:
SMTP.Filter.LevelMax The highest log level to be Default: N/A

monitored.
Valid values:
SMTP.delayBetwee The time interval (in seconds) to Default:

nChecksInSeconds check message queues.
Valid values:
SMTP.SMTPDebug If set to , enables displaying Default:

debug information when mail
Valid values:
notification is sent out.
SMTP.BufferSize The buffer queue length. Default:
Valid values:
Note:
l The same server log information generated several times within an hour is sent out only once
per hour.
l If the information in the file conflicts with this document, refer to this
document for instructions.
Example
If you want to monitor the InfrastructureException issue only and receive emails about the issue, you
can set the parameters as follows:

Parameter Name Parameter Value
ENABLE_SMTP_LOGGING true
SMTP.To admin@yourdomain.com
SMTP.From sender@youdomain.com or null
SMTP.Subject Notification Report
SMTP.Filter.RegexToMatch InfrastructureException
SMTP.Filter.LevelMin debug
SMTP.Filter.LevelMax fatal
You will receive emails with the content similar to the following:

Report Log Files

Report execution log files are stored in the directory. Report execution log
files are named . The report log ID setting corresponds to the report submission ID.

Use report execution log files to determine why a report executions failed or took too much time to
complete.
These log files are not purged automatically. Generally, report log files are required only to debug timely
report requests. In most cases, it is safe to delete these log files on a regular basis.
Execution Log Files

During normal package and request processing, execution log files are generated:
l For workflow steps running as or
l When resolving a validation defined using command execution logic
Execution log files from these executions are stored in the following directories:
l
l
l
If disk space becomes limited over time, you might need to purge or archive these log files. If the log
files are deleted, the detailed execution logs are no longer available for a package or request.
Execution Debug Log Files

If the or parameter is set to , additional execution
debugging data is written to the execution debug log file. This file is named and is
located in the directory.
If the server is running with full debugging enabled, this file grows over time. Generally, execution debug
log files are required only by HP Software Support to debug the execution engine. In most cases, it is
safe to delete these log files on a regular basis.
Temporary Log Files

Various other files generated in the directory are stored for temporary
purposes. Unless requested otherwise by HP Software Support, you can delete these log files on a
regular basis.

Periodically Stopping and Restarting the Server

The PPM Server generally requires very little maintenance. To help ensure your system operates
smoothly, HP recommends that you stop and restart the PPM Server(s) once a month.
To stop and restart a PPM Server cluster,
1. While the PPM Server cluster is running, from the command line, change to the
directory, and run the following command:
sh ./kRunCacheManager.sh A
where parameter means .
2. Stop all nodes in the cluster.
3. Clear all your browser's cache.
4. Delete all the content of the following folders on each node:
o
o
5. From the directory, run the following command:
6. Restart all nodes in your PPM Server cluster.
Tip: Wait for a few seconds between each node startup.
For information about starting and stopping the PPM Server on a single-server system, see "Starting
and Stopping the PPM Server" on page 87.
Maintaining the Database

Many IT departments have a policy of periodically changing the passwords of their database schemas.
This section covers common topics related to maintaining the Oracle database that is part of PPM
Center.

l "Changing PPM Center Data" below
l "Changing the Database Schema Passwords" below
l "Maintaining Temporary Tables" on the next page
Changing PPM Center Data

Updating PPM Center master data directly in the database can cause various errors to occur. HP highly
recommends that you not make changes directly to the PPM Center database, and instead use the PPM
Center user interface to make changes.
If you absolutely must update the database directly, it is important that you understand the underlying
data model design before you update the tables and views associated with the Multilingual User
Interface (MLU). Before you update MLU views or tables, make sure that your Oracle
parameter is set to the same language as your PPM Center instance. As always, make it a point to check
the data in the views and tables before you commit changes to the database. (For information about
the PPM Center data model, see the )
Changing the Database Schema Passwords

If you must change the PPM Center database schema passwords, be sure to change them both in the
database and in the file. Before you change all the database schema passwords, consider
the following:
l Check your environment definitions to determine whether any contain a password that is to be
changed. You can use the tool to automatically change
all occurrences of a specific password for a particular host and user name.
Note: This functionality is also available from the Environments section of the PPM Workbench.
(Open an environment on the Environment page, and then, on the Environment menu, click
Update Password.)
o Check both server and client passwords, as well as database passwords.
o Check passwords associated with application codes.
l Although it is not a recommended practice, you can hard-code passwords into commands in

workflow steps, requests, and object types.
l There is no need to change commands that use tokens for passwords (that is,
), as long as the password is changed in the respective environment definitions.
To change the PPM Center database schema passwords:
1. Make sure that all users are logged off the system.
2. Stop the PPM Server. (For information about how to stop PPM Servers, see "Starting and Stopping
the PPM Server" on page 87.)
3. Change passwords, as necessary in the database.
4. To change the passwords in the file, run the script to set the
and server parameters.
Note: When changing the passwords, do not edit the file directly. To encrypt
password values correctly, use the script.
Maintaining Temporary Tables

The PPM Server uses several tables for temporary storage during processing (for example, during
package migration) for:
l Logon attempts
l Debug messages
l Commands and parameters
PPM Server uses a set of services to monitor and clean up these temporary tables. Make sure the
cleanup parameters (described in "Cleanup Parameters" on page 249 and in "PPM Center Configuration
Parameters" on page 422) are set so that the temporary tables do not use too much database space.
KNTA_LOGON_ATTEMPTS Table
The table contains information about attempts to log on to the PPM Server

during the previous 14 days. This information includes:

l of users who attempted to log on
l Status (success or failure) of each logon attempt
l Messages generated during the logon attempt
The table is only for auditing purposes. The PPM Server does not require the
data to function.
If logon attempts succeed, the records for those most of those attempts are purged. However, the last
successful logon based on a combination of and IP address is retained.
If a logon attempt fails, the corresponding record remains in the table for future reference. You must
delete the failed logon attempt records manually. the record of the last successful logon attempt also
remains in the table.
The data is automatically purged after the time interval specified by the
server parameter setting.
KNTA_DEBUG_MESSAGES Table
The table contains any debugging text that HP PL/SQL database packages
generate. After you analyze this data, you can safely purge it. The PPM Server purges this data
automatically at the frequency determined by the server configuration
parameter setting.
Purging Stale PPM Center Database Data

The increasing PPM Center database size is starting to impact database operations and affect the
overall performance of PPM Center. This is especially true for organizations that have been using PPM
Center for years.
This section provides complete information about the PPM Purge Tool, including an introduction of the
tool, installation instructions, and usage information.
Overview of the PPM Purge Tool

The standalone PPM Purge Tool is designed only for the users who have both the SYS DBA and PPM
Center application administrator access grants to permanently delete (purge) stale database data by
specifying purging criteria.

For security reasons, it is highly recommended that this tool should be installed on a dedicated server
that only the tool users with both the SYS DBA and administrator access grant can have access to,
rather than on an end-user's machine.
The PPM Purge Tool offers the following:
l Dynamic statistics overview of all entities with statuses in the PPM Center Oracle database
l Enables administrators to define purging criteria based on their organizations business needs and
to purge stale data to decrease database load
l Downloadable XML files for purging criteria that administrators defined and downloadable purge
history reports
The PPM Purge Tool is located here: .
The package contains the following:
l Execute this script to launch the PPM Purge Tool web server on a
Windows system.
l Execute this script to launch the PPM Purge Tool web server on a
Unix system.
l folder, contains all necessary scripts and files for the tool, including the
file.
Note: The PPM Purge Tool can be accessed from an IPv4 address only. It does not support a JDBC
connection using IPv6 URL.
Prerequisites for Running the PPM Purge Tool

Review the following prerequisites:
l The purge operation is irreversible. Make sure you back up the database before you run the
purge tool.
l Before you run the PPM Purge Tool, stop the PPM Server. If in clustered configuration, stop all
PPM Server nodes.
l Collect business needs from your organization's stakeholders in order to clearly define your purge
criteria.

Purge Stale Data Using the PPM Purge Tool

This section provides detailed instructions on how to use the PPM Purge Tool to purge stale database
data.
To purge stale data,
1. Copy and extract the package to a different server than

the DB server.
For security reasons, it is highly recommended that this tool should be installed on a dedicated
server that only the tool users with both the SYS DBA and administrator access grants can have
access to, rather than on an end-user's machine.
2. Stop the PPM Server. If in clustered configuration, stop all nodes in the cluster.
3. Set the JAVA_HOME value.
o To set the JAVA_HOME value in Windows,
Note: The steps described in the following procedure are for Windows 7. The exact steps
may differ, depending on your Windows operating system.
i. Open the Control Panel.
ii. Open the System window.
iii. Click Advanced system settings in the navigation pane.
The System Properties dialog box opens.
iv. Click Environment Variables on the Advanced tab.
v. Under System Variables, click New.
The New System Variable dialog box opens.
vi. In the Variable name box, type JAVA_HOME
vii. In the Variable Value box, type the full Java install directory path, and click OK.

o To set the value of JAVA_HOME in DOS, run the following:
o To set the value of in UNIX using the Bourne shell (SH, BASH, or KSH), run the
following:
For more information about setting JAVA_HOME value, see the

section in the .
4. Navigate to the directory that you extracted in step 1, and run the following file to
start the purge tool server:
o On Windows system, run the file
o On Unix system, run the file
5. Open a web browser, type http://localhost:8080 or a specified IP address with access control
in the Address bar, and press Enter.
Note:
o HP recommends you use domain name to access the Purge Tool web server, instead of
using IP address.
o The default port is . To use a different port, you can configure the port value in the
file.
o By default, the Purge Tool allows access from the localhost only. However, you can control
whether you allow remote access to the Purge Tool or not. For more information, see
"Restrict Remote Access to the PPM Purge Tool to Specified IP Addresses" on page 372.
The PPM Purge Tool login page opens in your browser.

6. As the message on the Login page instructs, go to the the

directory and configure PPM Server and Oracle database related parameters in the
file as described in the table below:
Note: Only the DB account configured in the file has access to the PPM Purge
Tool.
Parameter name Description Sample Value
DB_USERNAME Username of the PPM database schema DB_USERNAME=

for connecting the Oracle database.
It is usually the same as the value of the

DB_USERNAME parameter in the
file.
RMI_URL_LIST RMI URL of the PPM Server. When there RMI_URL=

are multiple PPM Server nodes, the RMI
URLs are separated by commas.

Parameter name Description Sample Value
See the RMI_URL parameter value in

the file.
JDBC_URL JDBC URL for the Oracle database. JDBC_URL=
See the JDBC_URL parameter value in

the file.
7. Provide the DB account information you just configured in the DB User Name and DB Password
fields.
8. Click Login.
The PPM Purge Tool opens to its Database Statistics Overview tab.
The Database Statistics Overview tab dynamically displays the current statistics of all entities
found in the Oracle database.
There are two date types available for all the entities: Creation date (default) and Update date.
You can choose to display the database statistics overview by Creation Date or Update date.

The entities found in the Oracle database are categorized into two statuses for simplification
purpose: Open and Closed. The following table describes specific statuses categorized as Closed or
Open for each entity type:
Entity Type Closed Open
Request (status) o Cancelled All the other Request

o Closed statuses
o Closed (Approved)
o Closed (Not Approved)
o Closed - Failed
o Closed - Rejected
o Closed – Successful
Project (status) o Cancelled All the other Project

o Closed statuses
o Closed (Approved)
o Closed (Not Approved)
o Closed - Failed
o Closed - Rejected
o Closed – Successful
Staffing Profile (status) o Completed All the other Staffing

o Cancelled Profile statuses
Program (status) o Completed All the other Program

o Cancelled statuses
Scenario Comparison n All the other Scenario

(active_flag) Comparison statuses
Timesheet (status) o CANCELLED All the other Timesheet

o CLOSED statuses
Package (status) o Cancelled All the other Package

o Closed [Failure] statuses
o Closed [Mixed]
o Closed [Success]
Release (status) Closed All the other Release

statuses
Portfolio N/A N/A
9. Go to the Run PPM Purge Tool tab.

You can define and add your purge criteria by specifying desired values for the fields on this page.
You can add as many criteria as you like.
Note: In case there are any specific data that you want to retain, go to the White List tab to
specify your retention criteria. Otherwise leave the White List tab empty.
10. On the Purge Criteria tab, define system level or entity level purging criteria as described in the
following table.
Field Description
Date type Specify date type for all entities in the Oracle database by selecting Creation
Date or Update date from the Date type drop-down list.
Criteria Allows you to define a system level or an entity level purging criteria:
To define a system level purging criterion, select All.
To define an entity level purging criteria, select an entity from the list of
supported entities:
o Request

Field Description
o Project
o Timesheet
o StaffingProfile
o Program
o ScenarioComparison
o Package
o Protfolio
o Release
To specify purging criteria for multiple entities, you need to add them one at a
time.
Entity Type Allows you to select All or a specific entity type (if available) for the entities you
specify in the Criteria field: Request, Project, or Package.
Note that the available entity type options vary with the entity you select.
Note: This field is not applicable for the following entities: Timesheet,
StaffingProfile, Program, ScenarioComparison, Protfolio, and Release.
To specify multiple entity types for an entity, you need to add them one at a
time.
Status Allows you to multi-select statuses for the entity type you want to purge.
The available statuses vary with entities you specify in the Criteria field. You can
click Check all or Uncheck all to select or deselect all options.
Note: The Status field is not applicable to the Portfolio entity.
The Status field is not applicable when you select All in the Entity Type
field.
Date Before Click the calendar icon to select a date. This defines that you want to purge data

Field Description
with their creation date or update date earlier than the specified date (not
including data created or updated on the selected date).
You can also manually enter a valid date value.
11. After you have specified a criterion, click Add.
To add multiple entities and/or entity types, you need to add them one at a time. The screenshot
below illustrates an example of multiple purging criteria being added.
Note: If you add a criteria that was already added, the new one will override the existing one.
12. If there are any specific data that you want retain from the purging criteria you already specified,
go to the White List tab and specify the retention criteria.
Otherwise, leave the White List tab empty.
13. Review the purging criteria and click Next.
The purge tool starts to identify and add tags to purgeable data.

14. When the purge tool finished identifying and tagging purgeable data, cilck Next.
The summary page displays an overview of purgeable entities and non-purgeable entities.
Click View Details to view entities that have dependencies.
15. (Optional) Detailed lists of purgeable entities are not displayed here due to potential large amount
of the purgeable entities. However, you can run some SQL scripts in the database to view detailed
lists of purgeable entities.
Note: Skip this step if you do not need to view the detailed lists of purgeable entities.
To view detailed lists of purgeable entities in the database,
a. Log on to the database.
b. Run SQL scripts as described in the table below to view the detailed list of purgeable entities
for a concerning entity type.

Entity Type Run the following script
Request
Project
Timesheet
Staffing Profile
Financial
Summary
Portfolio
Program
Release
Package
16. Go back to the pre-processing summary page of the PPM Purge Tool, click Next.
The purge tool moves to Step 3. Start Purge page.

17. Follow the screen instructions to create the PPM_PURGE_DIR directory and grant read/write
privileges to it.
The PPM_PURGE_DIR directory will hold the external tables that the purge tool created on each run
to store the purged data. For example, you can run the following to replace the
directory with your own
directory on the Oracle database server:
CREATE DIRECTORY PPM_PURGE_DIR AS

'//home/oracle/oracle11g/product/11.2.0/dbhome_1/backup';
GRANT READ, WRITE ON DIRECTORY PPM_PURGE_DIR TO;
18. Check that PPM server or all nodes in the PPM cluster are stopped, and provide comments for the
current purge operation in the Messages text box.
19. Click Start Purging.
Wait for the current purging operation to finish.
Caution: HP strongly recommends you not to click Logout or move to other tab pages while
the purging is in progress.
20. Click Next when purging finishes.

The Purge results < > page displays.
21. To view or download historical purge criteria and summary reports, go to the Purge History tab.
By clicking Download XML, you can download an XML file that contains all purge criteria that you or
another DB administrator specified for that purge operation. You can find the XML file as follows:
. Below is the content of the
XML file for purge ID 30020:

By clicking Summary Report, you can view a snapshot of the database statistics for a purge
operation, like the following.

Restrict Remote Access to the PPM Purge Tool to Specified IP

Addresses
If you need to access the PPM Purge Tool remotely, you may want to restrict remote access to the PPM
Purge Tool to specified IP addresses .
To do so,
1. Go to the directory.
2. Open the file.
3. Add IP addresses you would allow remote access to the purge tool to the line. The
IP addresses shall be separated by commas.
For example, if you want to allow remote access from the IP address of , add it behind
the default value for the line as follows:
,126\.1\.1\.1
4. Save the file.
Note: The default value of 127\.0\.0\.1,0\:0\:0\:0\:0\:0\:0\:1 for means support

for IPv4 and IPv6 localhosts.
Backing Up PPM Center Instances

Backing up a PPM Center instance involves backing up both the file system and the database schema.
HP stores all PPM Center configuration and transaction data in its associated database schema.
Because this information is so important, HP also recommends that you back up the database schema
daily. You can use the Oracle export command to perform the backup, or use the hot backup procedure,

which does not require that you shut down the PPM Server. For information about how to export a
database schema, see your Oracle database documentation.
HP recommends that you back up the directory daily. This directory contains
transactional history files for each migrated package or request.
Note: Before you make critical changes to PPM Center, perform a full backup of the database
schema and complete directory.
It is not necessary to back up registry settings.
Protecting Backups
Because the backups you create may contain sensitive information such as cryptographic keys and
payload data, HP strongly advises that you protect the backups themselves. Oracle Advanced Security
provides transparent data encryption of data stored in the database, the encryption of disk-based
backups of the database, and network encryption for data traveling across the network between the
database and client or mid-tier applications. It also provides a suite of strong authentication services to
Oracle Database.
To use Enterprise User Security in Oracle Database Enterprise Edition, you must license Oracle Internet
Directory (OID). If you want to use stronger authentication alternatives (such as Kerberos or PKI) for
enterprise user security, you must license Oracle Advanced Security and the Oracle Internet Directory
(OID). For more information, see the release notes for your Oracle software.
Checking PPM Center License Status

You can view information related to licenses on your organization's PPM Center instance in the
Administration Console. The License tool provides the following licensing information:
l Which PPM Center products are licensed for use on your instance
l Expiration dates for licenses
l Number of licenses available for different PPM Center modules.
For more information, see "View A Summary of Autopass Licenses Purchased and Installed on the PPM
Server" on page 323.

Compiling JSP Files at Runtime

If you have made changes to JSP files and want to make modified JSP files reloadable at runtime, do the
following:
1. Back up your file, which is located in the directory.
2. Run the script to stop the PPM Server:
3. Open the file in a text editor, and set

to .
4. Specify folders to exclude when compiling the modified JSP files.
For example,
5. Save the file.
6. To regenerate the file and propagate the changes, run the script
from the directory.
7. Run the script to restart the PPM Server.

Chapter 9: Migrating Instances
This chapter covers the following topics:
l "Overview of Instance Migration" below
l "Preparing to Migrate" on the next page
l "Migrating the PPM Server" on page 378
l "Migrating the Database Schemas" on page 382
l "Troubleshooting Instance Migrations" on page 386
Overview of Instance Migration

Each PPM Center instance consists of a file system and an Oracle database, which can exist on Windows
or UNIX machines. You can migrate PPM Center using one of the following methods:
l Copy an entire PPM Center instance (server file system and database schemas) and move it to
another location. If you are moving the copied instance to a different machine, you must have a new
license key for it.
l Migrate the PPM Server to a different machine, but maintain the existing database schemas.
Migrating the server requires a new license key.
l Migrate the database schemas, but maintain the existing PPM Server. Migrating only the database
schema does not require a new license key.
Enterprise environments typically have multiple PPM Center instances (for example, development, test,
and production). The following sections address the simplest multiple-instance configuration, which
consists of a development instance (DEV) and a production instance (PROD). Each is set up on a
different machine. You can extend the migration steps to support all of the instances used at your site.
Copying an Instance to Create a New Instance

To create additional PPM Center instances from an existing production (PROD) instance, clone the PROD
instance.

To move from a single active instance to multiple instances:
1. Copy the PROD instance to DEV.
This includes the file system, database, and license information.
2. Configure any changes to HP products in the DEV instance.
This includes creating or modifying entities such as workflows, object types, request types,
validations, security groups, and environments.
3. From the PROD instance, configure a package workflow to import the configuration data from the
DEV instance.
4. Migrate data from the DEV instance into the PROD instance.
Running the Installation Script Twice to Create Two

Instances
You can set up multiple instances as you first install and set up PPM Center. Configure one instance as
the DEV instance, and the other as the PROD instance. This saves you from having to copy data from
one instance into another later.
Migrating Document Management (Optional)

If your source machine has document management installed and integrated with PPM Center, see the
for information about how to migrate document
management.
Preparing to Migrate
Before you can begin to migrate an entire instance to a different machine, you must obtain a new
license key and stop the PPM Server, as described in the following sections.

Obtaining a New License Key

PPM Center is licensed based on the computer that hosts the PPM Server. If you plan to migrate the
PPM Server to a different machine, you must obtain a new Autopass license key for the target machine.
If you plan to migrate only the database schema, you do not need a new license key.
To obtain a new license key:
1. Gather the following information:
o PPM Center version number
o Machine IP address
o Operating system (Windows or UNIX)
o Server purpose (development, test, or production)
2. Go to the HP Licensing for Software portal: http://www.hp.com/software/licensing.
3. Click Sign In.
4. Provide your HP Passport credentials and click Sign in.
Note: If you do not have an HP Passport, click Create an account.
5. On the Enter Entitlement Order Number page, enter the Order number found on the Entitlement
Certificate and click Go.
6. Complete the activation process to generate an Autopass license key file.
Stopping the PPM Server

To make sure that you do not lose transactions, reports, or logs, stop the PPM Server before you
migrate any part of a PPM Center instance. For information about how to stop the server, see "Starting
and Stopping the PPM Server" on page 87.

Migrating the PPM Server

Before you migrate the PPM Server, make sure that the target machine meets the requirements
described in the document
l "Migrating to a Windows Machine" below
l "Migrating to a UNIX Machine" on page 380
Migrating to a Windows Machine

To migrate the PPM Server to a Windows machine:
1. Obtain a new license key for the target server, as described in "Obtaining a New License Key" on
the previous page.
For information on how to stop the server, see "Starting and Stopping the PPM Server" on page 87.
3. Migrate the PPM Center file system:
a. Make a compressed file of the entire directory.
b. Copy the compressed file to the target machine, and then extract the file contents.
4. Migrate the PPM Center database schema.
For information about how to migrate the database schema, see "Migrating the Database
Schemas" on page 382.
5. Reconfigure the PPM Server in the target location, as follows:
a. Run the script, which is located in the directory.
The script starts the server configuration utility, which then displays the values
for each server parameter from the previous server configuration.
b. Browse through all server configuration parameters, and make the following updates:

l Update all parameters that refer to the DNS name or IP address of the old server to instead
refer to the DNS name or IP address of the new server.
l specifies the Web location (top directory name) of the PPM Server.
l specifies the port on which the PPM Server listens to initiate RMI client/server
communication. (This must be a unique port, distinct from the Web server, SQL*Net, and the
HTTP or HTTPS ports.)
l Update all parameters that reference a specific directory on the old server to instead
reference the corresponding directory on the new server. These parameters include:
l specifies the home directory for the Oracle client tools on the PPM Server
machine.
l specifies the full path to the directory where the PPM Server is installed.
l specifies the absolute pathname of the directory where attached

documents are to be stored. This directory must give read/write access to Web browsers
and, if the system includes an external Web server, exist outside the directory tree.
l specifies the operating system on which the PPM Server is installed.

Because you are placing the server on a computer running Windows, make sure you update
the value to .
l specifies the name of the PPM Server instance. If multiple PPM Servers are

running on the same machine, this name must be unique for each server. If the server is
running Windows, this name must match the name of the Windows service name.
c. To implement your changes, run the script from the

directory.
6. Install Oracle client on the PPM Server.
7. Set the environment variable to the directory path where the Oracle client software
is installed.
8. Set the environment variable.
9. Set the to include and and make sure that the directory
paths contain no spaces.

10. Make sure that the environment variable is set and that the directory path contains no
spaces.
11. To create a Windows service to use to start the new PPM Center instance, do the following:
a. Open a command prompt, and the change to the directory.
b. Run as follows:
Note: The value of is the same as the value set for the
To create a Windows service for the nodes in a cluster, run for each node in the
cluster.
Examples:
12. Start the new nodes, one node at a time.
For information about how to start the server, see "Starting and Stopping the PPM Server" on page 87.
Migrating to a UNIX Machine

To migrate the PPM Server to a UNIX machine:
1. Obtain a new license key, as described in "Obtaining a New License Key" on page 377.
For information about how to stop the PPM Server, see "Starting and Stopping the PPM Server" on
page 87.
3. Migrate the PPM Center file system as follows:

a. On the PPM Server host machine, navigate to the parent of the directory.
b. Using an archiving utility (such as Tar or Zip), create an archive file of the entire
directory.
Example:
If the directory is named " ", run the command:
tar cf ppm930.tar PPM
c. Using FTP in binary mode, copy the archive file to the target machine. Put the archive file in the
parent of the new directory.
d. To extract the archive file, run the command:
tar xf ppm930.tar
This creates the new PPM Server directory structure. A directory named PPM is created
automatically.
4. Migrate the PPM Center database schema.
For information about how to migrate the database schema, see "Migrating the Database
Schemas" on the next page.
5. Reconfigure the PPM Server in the target location:
a. Run the script, which is located in the directory.
The script starts the server configuration utility, which then displays the values
for each server parameter from the previous server configuration.
b. Browse through all server configuration parameters, and make the following updates:
l Update all parameters that refer to the DNS name or IP address of the old server to
instead refer to the DNS name or IP address of the new server.
l specifies the Web location (top directory name) of the PPM Server.
l specifies the port on which the PPM Server listens to initiate RMI client/server
communication. (This must be a unique port, distinct from the Web server, SQL*Net, and
the HTTP or HTTPS ports.)

l Update all parameters that reference a specific directory on the old server to instead
reference the corresponding directory on the new server. These parameters include:
l specifies the home directory for the Oracle client tools on the PPM Server
machine.
l specifies the full path to the directory where the PPM Server is installed.
l specifies the absolute pathname of the directory where attached

documents are to be stored. This directory must give read/write access to Web browsers
and, if the system includes an external Web server, exist outside the directory tree.
l specifies the operating system on which the PPM Server is installed.

Because you are placing the server on a computer running UNIX, make sure you update the
value to .
l specifies the name of the PPM Server instance. If multiple PPM Servers are

running on the same machine, this name must be unique for each server.
c. To implement your changes, run the script from the

directory.
6. Install the new Autopass license key file using the tool.
7. Start the new PPM Server.
For information about how to start the server, see "Starting and Stopping the PPM Server" on page 87.
Migrating the Database Schemas

This section provides the procedures used to migrate the PPM Center database schemas from one
database to another.
Export and Import Tools
Using incompatible versions of export and import tools causes errors in instance migration. Make sure
that the export and import tools you use are either the same version, or the export tool version is
earlier than the import tool version.
If You Use the Extension for Oracle E-Business Suite

If you have Deployment Management Extension for Oracle E-Business Suite, you must consider the
location of your Primary Object Migrator Host when migrating the PPM Center database schema,
because Object Migrator might reside in the same database, or even the same schema, as PPM Center.
Migrating the schema does not require migrating the Object Migrator instance because the integration
method in PPM Center can be refreshed to use the existing Object Migrator installation. If Object
Migrator shares a database with PPM Center, and you intend to migrate it as well as PPM Center, the
destination database must support Object Migrator. (For more information, see the
)
Unless PPM Center and Object Migrator share the same schema, the migration of Object Migrator is
completely separate from the migration of PPM Center, and should be completed before you migrate
the PPM Center database. Contact HP Software Support Web site (hp.com/go/hpsoftwaresupport) for
instructions on how to perform this migration.
If PPM Center and Object Migrator share the same schema and you want to migrate both, you must
coordinate the migration activities. Contact HP Software Support Web site
(hp.com/go/hpsoftwaresupport) for instructions.
Regardless of the configuration, refresh the integration definition after you migrate the PPM Center
schemas.
To migrate the database schemas:
For information about how to stop the PPM Server, see "Starting and Stopping the PPM Server" on
page 87.
2. Export the PPM Center database schema to a file by running the command as shown in the
following example.
where
represents the password for the system user on the Oracle database
represents the database connect string
represents the name of the file that is to contain the export. The
filename must have the extension (for example, ).
represents database dump directory. To create the directory, run the

following:
create directory DUMP_DIR as `c:/dump_dir';
represents the name of the PPM Center database schema to export.
3. Export the RML schema.
4. Create the new PPM Center database schema:
a. Run the script (located in the

directory) from SQL*Plus as the SYSTEM user.
Example:
b. Run the script (located in the directory) from SQL*PLUS as

the SYS DBA user.
5. Create the new PPM Center RML database schema.
To create a new, empty RML database schema in the target database, run the
script (located in the directory) from SQL*PLUS as the SYSTEM
user.
Example
@CreateRMLUser.sql Rml_User Rml_Password Rml_data_tablespace Rml_temp_

tablespace
6. To import data from the export file that you created earlier into the new empty PPM Center
database schema, run the command, as shown in the following example.
ORACLE_HOME/bin/impdp USERID= <Password>@<DB> DIRECTORY=<Dump_Dir>

REMAP_SCHEMA=<Source_Schema>:<Target_Schema> DUMPFILE=<Export_Filename>
LOG=import_knta_920.log
where
represents the password for the system user on the Oracle database

represents the database connect string
represents database dump directory.
represents the name of the PPM Center database schema previously

exported.
represents the name of the new PPM Center database schema
represents the name of the file that contains the export. The filename
must have the extension (for example, ).
7. Import the RML export file.
8. Create the RML-related packages in the RML schema:
a.
b.
9. Grant privileges to the PPM Center RML database schema:
Note: You can find the following scripts in the
o To set up the permissions between the two.
o To create synonyms to PPM Center objects in the RML schema.
10. Configure the database schema to ensure appropriate access to rebuild optimizer statistics.
Note: If PPM Center and Object Migrator share the same database schema, the PPM Center
database schema is referred to as the PPM Center account, and the Object Migrator schema is
referred to as the Object Migrator account.
To provide the necessary grants and permissions to the PPM Center user, run the
script as SYS DBA.

@GrantSysPrivs.sql <PPM_Username>
11. If the Extension for Oracle E-Business Suite is in use and Object Migrator resides in the same
schema as PPM Center, complete the Object Migrator migration.
For assistance, contact HP Software Support Web site (hp.com/go/hpsoftwaresupport).
12. If you are using the Extension for Oracle E-Business Suite, refresh the Primary Object Migrator Host
definition.
Note: To validate any invalid PPM Center database objects generated during link regeneration,
run the script, which is located in the
directory. Run this script from SQL*Plus connected as the new PPM Center database schema
account.
13. Reconfigure the PPM Server to connect to the new database schema:
a. Start the configuration utility by running the script, which is located in the
directory.
b. Update the server configuration parameters, which are described in "PPM Center
Note: If you edit the files manually, be sure to run the

script after you complete the edit.
14. Start the PPM Server (see "Starting and Stopping the PPM Server" on page 87).
Troubleshooting Instance Migrations

This section describes common problems that you might encounter as you migrate PPM Center
instances.
PPM Server Does Not Start

If you cannot start the PPM Server, check the file (located in the
directory) for error messages. If the file contains

no error messages, increase the server debug level to determine whether any additional helpful
information is written to the log.
To increase the server debug level:
1. Open the file (located in the directory) in a text editor.
2. Set the value of the parameter to and then save and close the
file.
3. Run the script.
4. Rerun the script, and then recheck the file to determine whether it
contains any additional information.
5. Open the file.
6. Restore the default value of the parameter.
Note: Restoring the default value ensures that the file system does fill up with unnecessary
information recorded in the file(s).
7. Run the script.
Server Starts, but You Cannot Access Applications

If the Web browser accessing the PPM Center URL generates a "Not Found" or an "Access Denied" error,
check the file and the external Web server (if one exists) to ensure that the PPM Server
installation directory is specified correctly.
If the PPM Server has recently been upgraded and the URL has changed, make sure that any saved links
to the previous PPM Center URL (for example, existing requests) are updated to point to the new URL.

Chapter 10: Migrating Entities
l "About Entity Migration" below
l "Overview of Entity Migration " on page 390
l "Defining Entity Migrators" on page 395
l "Environment Considerations" on page 402
l "Security Considerations" on page 403
l "Entity Migrators" on page 404
About Entity Migration

Entity migrators are Deployment Management object types. Each migrator is designed to migrate a
specific kind of PPM Center entity and all of its dependent objects from one PPM Center instance to
another.
You can use Deployment Management to manage configuration changes to PPM Center. Deployment
Management comes with an out-of-the-box set of object types, or that you can use to
move PPM Center configuration entities (workflows, request types, and so on) between PPM Center
instances. If you maintain scratch instances for developing and testing PPM Center configurations
before you deploy them into your production instance, you must use these entity migrators, and
develop a workflow that drives configuration changes through your source configuration management
deployment process.
Migrating configurations using entity migrators and workflows lets you automate and standardize a
change-control process for your PPM Center implementation. You can build a workflow for every
migrator object type, or create a single generic workflow for all migrator object types.
Note: You can only migrate entities between PPM Center instances of the same version.
You can migrate the following PPM Center entities:

l Special commands
l Object types
l Portlet definitions
l PPM Dashboard modules
l PPM Dashboard data sources
l Project types
l Work plan templates
l Report types
l Request header types
l Request types
l User data contexts
l Validations
l Workflows
Migration Order
If you plan to migrate request type, workflow, project type, and work plan template configurations that
are related to each other, you must perform the migration in the following order:
1. Request type
2. Workflow
3. Request type again (if circular references exist between request type and workflow)
4. Work plan template
5. Project type

Overview of Entity Migration

Consider a scenario in which you want to migrate configuration entities between your "QA" and
"Production" instances of PPM Center. You can automate and track the migration using either the
source instance (QA) or the destination instance (Production). In the example that follows, you are using
the destination instance to control the migration.
You migrate PPM Center entities in the same way that you perform any other deployment management
process. To prepare for the entity migration you do the following:
l Set up the environment definitions for your "QA" and "Production" instances.
l Configure a workflow that directs the migration process (necessary approvals, and an automated
execution step that specifies your "QA" and "Production" environments as source and destination,
respectively).
After you perform these tasks, you can use Deployment Management packages to specify the entities
to migrate. Create a package, specify your migration workflow, and add package lines using the entity
migratory object types for each PPM Center configuration entity that you want to migrate.
When the automated migration execution workflow step is run, the following events occur (remember
that, in this example, you are running the migration in the destination, or Production, environment):
1. The Production server connects to the QA server using SSH, and then submits a request for the
specified configuration data.
2. The QA server extracts the requested configuration data from its database and generates an XML
representation of the data.
3. The QA server writes the extracted XML data into a set of temporary XML files, and packages that
set of files together in a Zip file.
4. The Production server copies the Zip file that contains the bundled XML data from QA to
Production.
Note: If you want to perform version control on changes to PPM Center configuration entities
as they are migrated, you can version the compressed file that is extracted from the source
instance.

HP recommends that you not extract this file manually, except for debugging purposes.
5. The Production server unpacks the migrated compressed file into temporary storage, and reads
the associated XML files.
6. The Production server imports the configuration data to its database, and then generates an
execution log.
Example Migration: Extracting a Request Type

The following example shows a procedure that you can use to migrate a request type from a QA
instance of PPM Center to a production instance.
Note: To create, submit, and process migrations, you must have the required licenses and access
grants. For more information, see the .
Before you perform the following steps, make sure that you have a valid user account in both the
source and destination instances, and that these accounts have the same user name. When the
migrator extracts an entity from the source instance, and then imports it into the destination instance,
it provides your security information.
To migrate a request type:
1. If the environment definition for the PPM Server is not configured, then you must first create the
environment, as follows.
Note: Because you control this migration from the production instance, the environment you
define represents the destination for entity migrations.

a. In the Environment Workbench, open the environment.
b. To the right of the Server section, select the Enable Server checkbox.
c. Provide the server information.
Note: Because this environment definition represents the PPM Server that you are using
to run the migration, there is no need to specify connection information for it. The
migrator performs the required actions locally, without opening a separate SSH session.
d. Define and enable the source environment.
Note: You must specify connection information for the source environment, including the
user name and password, base path, and connection and transfer protocols.
2. Create a deployment management workflow.

For information about how to create a workflow, see the
Specify the QA environment as the source, and the production environment ( ) as

the destination of the execution step.
3. Create a package.
For information about packages and how to create a package, see the
4. In the Package: < > window, in the Workflow field, specify the workflow you created.
5. Click New Line.
The Add Line dialog box opens.

6. In the Object Type field, type
7. On the Parameters tab, provide the following information:
Field Name Description
Migrator action To control how extensive a migration to perform, in this list, select
Extract only.
PPM source password In this field, type the password for your PPM Center account on the
source instance.
PPM dest password In this field, type the password for your PPM Center account on the
destination instance.
Request type In this field, type the name of the request type that you want to
migrate.
Note: For information on Migrator action list dependencies, see "Migrator Action List" on the
next page.
8. Submit the workflow.

9. Process the workflow.
10. Check the execution log to verify that the migration completed successfully.
Defining Entity Migrators

Each object type for the PPM Center entity migrators has a set of parameters similar to those described
in this section (and as shown in the previous example). The RCS File Migration shown in the following
figure is an example.
Figure 10-1. Add Line dialog box for the RCS File Migration
Migrator Action List

To control how extensive a migration to perform, use the Migrator action list on the Parameters tab of
the Add Line dialog box. "Migrator Action List" above shows the Migrator action list.
Figure 10-2. Migrator action list

In the Migrator action list, you can select one of the following actions:
l Migrate (extract and import)
l Extract only
l Import only
The following table lists the controls in the Add Line dialog box that are affected by the migrator action
you select, and provides information about how each control is affected.
Table Column
Control Outside Set
and Control Table:
Names Extract and Import Extract Only Import Only
Table Column Outside Table:
Preview Import Enabled Disabled Enabled
Target entity field Required Required Disabled
Content bundle fields Disabled Enabled Required
Import behavior fields Enabled Disabled Enabled
Source password Required Required Disabled
Destination password Required Disabled Required
Basic Parameters
Whether the basic parameters are required or simply available depends on the migrator action you
select. In the following figure, the parameters are the entity name (in this case, the request type),
content bundle directory, and content bundle filename.
Figure 10-3. Basic parameters

Content Bundle Controls
The behavior of controls related to the content bundle depends on the migrator action you select, as
follows:
l If you select Migrate (extract and import), the migrator maintains its own internal scheme for
naming and locating the temporary bundled XML data. This content bundle is extracted from the
source, migrated to the destination, imported, and then cleaned up, all as part of the same
execution step. The user cannot edit the content bundle information.
l If you select Extract only, you can specify the content bundle location and filename, or accept the
default values. This lets you specify a location and naming convention that is easier to remember so
that you can locate the extracted content bundle and use it as necessary (for example, check it into
your version control system). By default, the migrator creates the bundle in the file system of the
source PPM Server under the directory. The filename is based on the type
of entity migrated, its package number, and its package line number.
l If you select Import only, you must specify the name and location of an existing content bundle file
to import. You can select the file by browsing the file system of the destination PPM Server.
Import Flags
Use the import flags listed in the lower portion of the Parameters tab (shown in the following figure) to
control migrator behavior.

Figure 10-4. Import flags
The available import flags vary with object type.
Preview Import Option
If you set Preview Import? to Yes, the migrator does not actually import the migrated entity into the
destination instance, but instead, simulates the migration and generates an execution log.
Import Behavior Controls
The following settings modify the specific import behavior for the entity to migrate.
l Replace existing request type? If the entity to migrate already exists in the target PPM Center
instance, you can decide whether or not to replace it. The default selection is Yes.
If the entity does not exist in the destination instance, it is created.
l Replace existing req hdr type? If the request type to be migrated references a request header
type that already exists in the target PPM Center instance, you can decide whether or not to replace
it. The default value is No.
l Replace existing validations? If the target entity references validations that already exist in the
target PPM Center instance, you can decide whether or not to overwrite them. The default value is
No.

Regardless of the value, any validations that are missing from the destination instance are
automatically created.
l Replace existing special cmds? If the validation to be migrated references PPM Center special
commands (including parent and child special commands) that exist in the target PPM Center
instance, you can decide whether or not to replace them. The default value is No.
l Add missing request statuses? If the request type to be migrated references request statuses that
do not exist in the target PPM Center instance, you can decide whether or not to create them. The
default value is No.
l Add missing security groups? If the entity to be migrated references security groups that are not
included in the target instance, you can add those security groups. The default value is No.
Only the list of associated access grants, but not associated users, is transferred.
Password Fields
If the Migrator action list displays Migrate (extract and import), then the PPM source password and
PPM dest password fields ("Password Fields" above) are enabled.
Figure 10-5. Password fields
Source Password Field
When the migrator contacts the source server, it uses the credentials of the current PPM Center user to
authorize the entity extraction. This user must be part of a security group that contains the access
grant "System Admin: Migrate HP PPM Objects". Confirm the user password for the source server in the
PPM source password field.
Destination Password Field
When the migrator contacts the destination server, it uses the credentials of the current PPM Center
user to authorize the entity import. This user must be part of a security group that has the "Sys Admin:
Migrate HP PPM Objects" access grant. Confirm the user password for the destination server in the PPM
dest password field.

Internationalization List
Typically, in an environment in which you are managing configuration across multiple PPM Servers, all of
the PPM Center databases involved have the same localization settings. However, if you must migrate
configuration entities between PPM Center databases that have different localization settings, you can
change the localization-checking behavior of the migrator by changing the value of the
Internationalization list.
By default, the Internationalization list is invisible to users on migrator object types. But the control is
enabled and set to Same language and character set. To change this setting:
2. From the menu bar, select Administration > Open Workbench.
3. From the shortcut bar, select Deployment Mgmt > Object Types.
The Object Type Workbench window opens.
4. Click List.
5. In the Object Name column on the Results tab, double-click PPM Request Type Migrator.
The Object Type: PPM Request Type Migrator window opens.
6. In the Prompt column on the Fields tab, double-click Internationalization.
The Field: Internationalization window opens.
7. Click the Default tab.

8. From the Visible Value list, select one of the following:
o Same language and character set. This is the default option for migrating entities between
PPM Center instances running under the same language and character set configuration. It is
the most conservative option; any difference in locale, language, or character set between the
source and destination servers is flagged as an error and the migration fails.
o Different language or character set. This option lets you override character set or language
incompatibilities within the same localization. Use this option if you know that the language or
character set settings are different across the source and destination servers, but you want to
run the migration anyway and you do not anticipate the differences to cause problems with the
entity data you want to migrate. For example, if the destination character set is a superset of
the source character set, then you know that data extracted from the source is valid in the
destination.
o Different localization. This option lets you migrate content between instances belonging to
different localizations (for example, English to German, or German to English). This is the least
restrictive option for migrating configuration data across PPM Servers that have different
locale settings. Selecting this value could potentially result in invalid data (unsupported
characters, and so on) in the destination instance. Be sure to examine (and possibly update) the
migrated entity data to make sure that it is valid in the destination.

Environment Considerations
When migrating entities, Deployment Management logs on to remote machines in the same way
another user would (that is, using FTP, SCP, SSH). Deployment Management can log on to a remote
server using any existing operating system user name and password.
HP recommends that you generate a new user (for example, PPM Center) on every machine to which
Deployment Management has access. A user you create for this purpose must have full access to the
directory on the PPM Server, and read and write permissions on other required directories.
Setting Stream Encoding for an Environment

In a Deployment Management scenario, the stream encoding specifies which character encoding
scheme PPM Center's command execution engine is to use to send and receive commands to a remote
computer (via SSH or FTP/SCP). This setting is important if your PPM Center instance supports multiple
languages, especially in supporting remote executions in IT environments where non-English operating
systems are more common.
When configuring an Environment in PPM, the stream encoding for the client (token: CLIENT_STREAM_
ENCODING) specifies which encoding the client machine uses and therefore, the encoding that PPM uses
in communicating with the client machine.
The stream encoding for the PPM Server (token: SERVER_STREAM_ENCODING) specifies the encoding
the server machine uses and, therefore, the encoding that PPM Center uses to communicate with that
server machine.
This is important if PPM Center is installed on a machine whose default encoding is set to, say, UTF-8,
but must communicate with remote computers that have, for example, Shift-JIS (a Japanese encoding)
or CP-1251 (a Latin encoding) as the default encoding. Having this information known and configured in
advance helps PPM Center send messages and commands that those machines can correctly interpret
and to decode messages that the remote machines return.
Environment Connection Protocol

The environment definition must include information about the communication protocol to be used to
connect to the server or client. For information about connection protocols that PPM Center supports,
see the and the
.

Environment Transfer Protocol

The environment definition must include information about the transfer protocol to be used to transfer
files to or from machines specified in the environment definition. Choose the transfer protocol that
best suits your business and technology needs. Consider factors related to security and performance
when selecting the transfer protocol. Work with the application administrator to determine which
connection protocols are supported for the machines housing the deployment environments.
For information about transfer protocols, see the
Setting the SERVER_ENV_NAME Parameter

The PPM Center migrators depend on the server configuration parameter. This
parameter specifies the name of an environment definition in the PPM Center system that describes
the host server running that PPM Center instance.
When you installed PPM Center, the installer automatically defined the environment.
This name is set as the default value of the server configuration parameter. PPM
Center often refers to this parameter to find the environment definition that contains information
about the computer(s) that hosts the PPM Server and database. For this reason, it is important that you
keep this server configuration parameter synchronized with the name of the corresponding
environment definition, as follows:
Security Considerations
This section provides information about security considerations related to ownership and entity
restrictions.
Migration and Ownership

Different groups of PPM Center users have ownership and control over different PPM Center entities.
These groups are called ownership groups. Unless a global permission has been designated to all users
for an entity, members of ownership groups are the only users who have the right to edit, delete, or
copy that entity. The ownership groups must also have the proper access grant for the entity in order to
complete those tasks.

Application administrators can assign multiple ownership groups to entities. The ownership groups have
sole control over the entity, providing greater security. Ownership groups are defined in the Security
Groups window. Security groups become ownership groups when used in the ownership configuration.
Ownership applies to PPM Center entities during migrations in the following ways:
l If no ownership security is configured for the entity, any user who has permission to perform
migrations can migrate it.
l If entity ownership is configured and the user migrating is not in the ownership group, the migration
fails.
l If entity ownership is configured and the user migrating is in the ownership group, the migration
succeeds.
l If entity ownership is configured and the user migrating is not in the ownership group but has the
Ownership Override access grant, the migration succeeds.
Note: These conditions apply to entity import, but not to entity export.
Migrations and Entity Restrictions

A report type might refer to security groups through entity restrictions. The Report Type migrator
transfers references to security groups, but does not create any new security groups in the destination
instance of PPM Center. If the referenced security group does not exist in the destination instance, the
reference is discarded in transit. A message to that effect is displayed in the migration execution log.
If the source instance contains security groups that do not exist in the destination instance during
migration, the entity restrictions for the migrated report type might be inaccurate. Therefore, after
migration, manually verify report types that contain entity restrictions in the destination instance.
Entity Migrators
This section provides descriptions of PPM Center entity migrators.
Data Source Migrator

You can use the Data Source Migrator to move a data source that you created in the Data Source
Workbench between the PPM Center instances. (Data sources provide data displayed in PPM Dashboard

portlets.)
The following figure shows the parameters for the Data Source migrator as they are displayed during
package line creation.
Figure 10-6. Data Source Migrator
For information about the fields in this migrator, see "Defining Entity Migrators" on page 395. For
information about how to create a portlet data source, see the guide.
Module Migrator
In the PPM Center standard interface, a module is the set of pages that an administrator sets up for
users to view and navigate in the PPM Dashboard. You can use the Module Migrator to move PPM Center
modules from one PPM Center environment to another.
Figure 10-7. Module Migrator

For information about the fields in this migrator, see "Defining Entity Migrators" on page 395. For
information about how to create modules, see the guide.
Object Type Migrator

The Object Type Migrator contains the additional option Replace existing special cmds? If the
validation to be migrated references PPM Center special commands (including parent and child special
commands) that exist in the target PPM Center instance, you can decide whether or not to replace
them. The default value is No.
Regardless of the migrator settings, special commands missing from the destination instance are
created automatically.
Figure 10-8. Object Type Migrator

For information about most of the controls in this migrator window, see "Defining Entity Migrators" on
page 395.
Configuration Considerations
The PPM Object Type Migrator also transfers the following information:
l Special commands referenced by command steps
l Validations referenced by fields
l Environments referenced by validations
l Special commands referenced by validations
l Special commands referenced by other special commands
l Ownership group information for the entity
Note: The migrator transfers references to environments from validations, but does not create
any new environments. If the referenced environment does not exist in the destination
instance, the migration fails. If this happens, create the missing environment manually in the

Portlet Definition Migrator

The Portlet Definition Migrator contains all standard entity migrator object type fields. If you migrate a
portlet definition to replace an existing enabled portlet definition the destination instance of PPM
Center, the migrated changes are applied to all users who have added the same portlet to their PPM
Dashboard pages.
Figure 10-9. Portlet Definition Migrator
For information about the fields in this migrator, see "Defining Entity Migrators" on page 395.
Project Type Migrator

You can define project types in a development or testing instance of PPM Center, and then use the
Project Type Migrator to migrate them to production after testing.
Figure 10-10. Project Type Migrator

The Project Type Migrator migrates the following:
l Header information such as name and enabled flag
l All policies (including all attributes)
l References to request types for project, issue, and so on
If the migrator cannot locate these objects in the destination instance, then it drops the references and
writes a warning message into the migrator log file. The migrator report contains information about the
resolution (or loss) of each entity association.
Project types are connected to work plan templates, resource pools, project requests, and issue
requests. None of these entities are migrated with project types. However, if these entities exist in the
destination instance, the connection to them is maintained (the migrators identify entities by name).
Because project types are useless without an associated project request, you must either migrate the
associated request type first, so that the link to the project type is resolved when you migrate the
project type is migrated, or edit the project type after you migrate it.
Note: The Project Type Migrator does not transport secondary objects as dependencies.

Report Type Migrator

The Report Type Migrator contains the additional option Replace Existing special cmds? If the
validation to be migrated references PPM Center special commands (including parent and child special
commands) that already exist in the target PPM Center instance, you can choose to replace them (or
not). (The default value is No.) Regardless of their values, PPM Center automatically re-creates special
commands that are missing from the destination instance.
Figure 10-11. Report Type Migrator
For information about most of the fields in this migrator, see "Defining Entity Migrators" on page 395.
The Report Type Migrator also transfers the following information:

l Ownership group information for the report type
Note: The Report Type Migrator transfers references to environments from validations, but
does not create an environment. If the referenced environment does not exist in the
destination instance, the migration fails. If this occurs, you must create the missing
environment manually in the destination instance.
Request Header Type Migrator

The Request Header Type Migrator contains the additional option Replace Existing special cmds? If the
validation to be migrated references PPM Center special commands that already exist in the target PPM
Center instance, you can decide whether or not to replace them. This includes both parent and children
special commands. (The default value is No.) Regardless of their values, PPM Center automatically re-
creates special commands that are missing from the destination instance.
Figure 10-12. Request Header Type Migrator
For information about most of the fields in this migrator, see "Defining Entity Migrators" on page 395.
The Request Header Type Migrator also transfers the following information:

l Ownership group information for the request header type
The Request Header Type Migrator transfers references to environments from validations, but does not
create an environment. If the referenced environment does not exist in the destination instance, the
migration fails. In this case, you must create the missing environment manually in the destination
instance.
Request Type Migrator

The Request Type Migrator has additional import behavior options from which to choose.
Figure 10-13. Request Type Migrator
The additional import behavior options are as follows:

l Replace existing req hdr type? If the request type to be migrated references a request header
type that already exists in the target PPM Center instance, you can decide whether or not to replace
it. The default value is No.
l Replace Existing special cmds? If the validation to be migrated references PPM Center special
commands that already exist in the target PPM Center instance, you can decide whether or not to
replace them. This includes both parent and children special commands. The default value is No.
Regardless of their values, PPM Center automatically re-creates special commands that are missing
from the destination instance.
l Add missing request statuses? If the request type to be migrated references request statuses that
do not exist in the target PPM Center instance, you can decide whether or not to create them. The
default value is No.
In the execution log, a message is displayed for each referenced request status that is not created.
Note: If this option is set to No, and one of the missing request statuses is the initial status of the
request type, the migration fails. In this case, you must create the request status for the initial
status manually.
The Request Type Migrator also transfers the following information:
l Request header types referenced by the request type
l Validations referenced by fields of the request type or request header type
l Special commands referenced by other special commands already referenced elsewhere
l Request statuses referenced by the request type
l Security groups referenced by the request type (on the Access tab)
l Workflows referenced by the request type

l Notifications referenced by the request type
l Ownership group information for the request type
The Request Type Migrator transfers references to environments from validations, but does not create
an environment. If the referenced environment does not exist in the destination instance, the migration
fails. In this case, you must create the missing environment manually in the destination instance.
Simple default rules, defined in the request type Rules tab, might reference users, workflows, or other
objects. The Request Type Migrator transfers these references, but does not create a missing user or
workflow. If the referenced user or workflow does not exist in the destination instance, the reference is
discarded in transit, and a message to that effect appears in the migration's execution log. You must
manually reconfirm advanced default rules after migration.
Circular references between request types and workflows could make it necessary to migrate either a
request type or workflow twice:
l A new request type referring to a new workflow is migrated. Because the new workflow does not
exist in the destination instance, not all references to that workflow are included in the new
instance destination.
l The new workflow is migrated.
l The new request type is migrated again. This time, since the workflow it refers to exists, the
references are included in the destination instance.
Special Command Migrator

If you migrate a workflow step, request type, or object type that contains special commands, the special
commands are not migrated along with the entities. You must use the Special Command Migrator to
move the special commands between instances of PPM Center separately.

Figure 10-14. Special Command Migrator
For information about the fields in this migrator, see "Defining Entity Migrators" on page 395.
User Data Context Migrator

The User Data Context Migrator contains the additional option Replace Existing special cmds? If the
validation to be migrated references PPM Center special commands that already exist in the target PPM
Center instance, you can decide whether or not to replace them. This includes both parent and child
special commands. (The default value is No.) Regardless of their values, PPM Center automatically re-
creates special commands that are missing from the destination instance.

Figure 10-15. User Data Context Migrator
For information about most of the fields in the User Data Context Migrator, see "Defining Entity
Migrators" on page 395.
Validation Migrator
The Validation Migrator is shown in the following figure.
Figure 10-16. Validation Migrator

This migrator contains the following two additional import behavior options:
l Replace existing special cmds? If the validation to be migrated references PPM Center special
commands that already exist in the target PPM Center instance, you can decide whether or not to
replace them. This includes both special commands directly referenced by the validation, and also
special commands referenced by these special commands. (The default value is No.) Regardless of
their values, PPM Center automatically re-creates special commands that are missing from the
l Add missing environments? If the validation to be migrated references environments or

environment groups that do not exist in the target PPM Center instance, you can decide whether or
not to create them (assuming that the option has been marked Yes). However, only the environment
header information and user data are transferred. Application codes and extension-specific
environment tabs are not transferred. The default value is No.
Similarly, environment group application code information is not transferred. If an environment

group already exists in the destination instance, it is not updated with environments that were
added in the source instance. After migration is complete, if the migrator has created any
environments, confirm and complete environment data manually.
For information about the controls in this migrator, see "Defining Entity Migrators" on page 395.

Validation values can also carry context-sensitive user data. When migrating validation values that have
such fields, you should manually set up the user data configuration in the destination instance before
migration begins.
Workflow Migrator
The Workflow Migrator is shown in the following figure.
Figure 10-17. Workflow Migrator
This migrator provides the following additional import behavior options:
l Replace existing special cmds? If the workflow to be migrated references PPM Center special
commands that already exist in the target PPM Center instance, you can replace them. This includes
special commands that the workflow references directly, as well as special commands that these
special commands reference. Special commands in validations that the workflow references are
also migrated.
The default value is No. Regardless of the value, any special commands missing from the
destination instance are created automatically.

l Replace existing step sources? If the workflow to be migrated references workflow decision and
execution step sources that exist in the target PPM Center instance, you can choose to replace them
or leave them in place. However, if workflows in the destination instance are using the existing step
sources, you cannot change certain options (such as Workflow Scope, Validation, and Decision
Type), even if you set Replace Existing Step Sources? to Yes.
l Replace existing sub workflow? To overwrite an existing subworkflow in the target environment
when subworkflows are migrated (with or without the main workflow), set this option to Yes.
l Add missing environments? If the workflow to be migrated references environments or

environment groups that do not exist in the target PPM Center instance, you can create the
environments or environment groups. However, only the environment header information and user
data are transferred. Application codes and extension-specific Environment tabs are not
transferred. The default value is No.
Similarly, environment group application code information is not transferred. If an environment

group exists in the destination instance, it is not updated with environments added to the source
instance. If the migrator has created environments, then after migration, make sure that you
confirm and complete the environment data manually.
l Add missing request statuses? If the workflow to be migrated references request status values
that do not exist in the target PPM Center instance, you can create the status values. The default
value is No.
For information about controls in this migrator, see "Defining Entity Migrators" on page 395.
The Workflow Migrator also transfers the following information:
l Subworkflows that the workflow steps reference
l Special commands that the command steps reference
l Workflow step sources that the workflow steps reference
l Validations that the parameters or workflow step sources reference
l Environments and environment groups that the workflow steps reference
l Environments that the environment groups referenced by workflow steps reference
l Environments that validations reference

l Special commands that validations reference
l Special commands that the workflow step sources reference
l Special commands referenced by other special commands referenced elsewhere
l Security groups that the workflow steps reference
l Request statuses that the workflow steps reference
l Notifications that the workflow steps reference
l Notification intervals that notifications reference
l Security groups that notifications reference
l Ownership group information for the workflow and workflow steps
If a notification in a workflow uses a notification interval that does not exist in the destination instance,
the migrator creates this notification interval. The workflow migrator does not replace existing
notification intervals in the destination instance.
The Workflow Migrator transfers entity restriction references to object types, but does not create an
object type. If the referenced object type does not exist in the destination instance, the migrator
discards the reference and records the event in its execution log.
The Workflow Migrator transfers references to request types, but does not create request types. If the
referenced request type does not exist in the destination instance, the migrator discards the reference
and records the event in its execution log.
If there are circular references between workflows and request types, you may have to migrate either a
workflow or request type twice:
l A new request type referring to a new workflow is migrated. Because the new workflow does not
exist in the destination instance, all references to that workflow are dropped in transit.
l The new workflow is migrated.
l The new request type is migrated again. This time, because the referenced workflow exists, the
references are preserved.

Work Plan Template Migrator

You can define work plan templates in a development or testing instance of Project Management, and
then use the Work plan Template Migrator to migrate them to production after testing is completed.
Figure 10-18. Work Plan Template Migrator
The Work Plan Template Migrator migrates the following:
l Header information such as work plan template name and list of owners (users)
l Work plan (hierarchy of tasks and task information)
l References to assigned resource groups or users (by reference only—security groups are not
treated as dependent objects)
The Work Plan Template Migrator does not transport secondary objects (for example, validations) as
dependencies.

Appendix A: PPM Center Configuration
Parameters
This appendix contains the following topics:
l "Overview of Configuration Parameters" below
l "Server Configuration Parameters" on the next page
l "Logging Parameters" on page 502
l "LDAP Attribute Parameters" on page 510
Overview of Configuration Parameters

This appendix lists and describes the PPM Center configuration parameters, which are located in three
files in the directory:
l
l
l
For more information about the PPM Server directory structure and contents, see "Server Directory
Structure and Server Tools" on page 513.
Determining the Correct Parameter Settings

For most PPM Center installations, the default parameter values are optimal. Considerations detailed in
the parameter descriptions can help you determine under what circumstances you might want to
change the parameter settings.

Appendix A: PPM Center Configuration Parameters
Required Parameters
In the tables in this appendix, a single asterisk in the Parameter column indicates that the parameter is
required to set up a PPM Server. Two asterisks in this column indicates that the parameter is required
based on the condition of another parameter. For example, the parameter is
required only if the parameter is set to .
In a server cluster configuration, required parameters must be set for the primary server. Secondary
servers inherit the parameter values from the primary server. To override the inherited value, set the
parameter to the value you want in the appropriate secondary server section of the file.
For more information about setting up PPM Servers in a server cluster configuration, see "Configuring a
Server Cluster" on page 179.
For information about how to specify your own parameters, see "Defining Custom and Special
Directory Path Names

Use forward slashes (/) to separate directory paths that you specify in the file, regardless
of the operating system used. PPM Center automatically uses the appropriate path separators to
communicate with Microsoft Windows. HP recommends that you not use backslashes (\) to separate
directory paths in the file.
Server Configuration Parameters

The server configuration parameter information on a PPM Center instance comes from the following
three different sources:
l KNTA_SERVER_PARAM_DEF_NLS table
l file
l KNTA_APPSERVER_PROPERTIES table
The KNTA_SERVER_PARAM_DEF_NLS table (definitions table) contains all of the server configuration
parameters and their default values. The file contains a subset of the server
configuration parameters in the KNTA_SERVER_PARAM_DEF_NLS table. If you specify the value for a

parameter directly in the file, either manually or from the Administration Console, then
that value supersedes the default value for the parameter in the KNTA_SERVER_PARAM_DEF_NLS table.
The KNTA_APPSERVER_PROPERTIES table contains the server configuration parameters and values that
the PPM Server ultimately uses. Parameter values in the file are compared with those in
the KNTA_SERVER_PARAM_DEF_NLS table. If a non-default value is specified for a parameter in the
file, then the parameter is assigned that value in the KNTA_APPSERVER_PROPERTIES
table. If a parameter exists only in the KNTA_SERVER_PARAM_DEF_NLS table, then the parameter is
assigned the default value in the
KNTA_APPSERVER_PROPERTIES table.
Using the Server Configuration Utility to Modify Server

Configuration Parameters
The file contains the values of all of the server parameters applied during the last server
configuration utility ( script) run.
Note: HP recommends that you modify the file directly. Instead, modify
parameter values from the Administration Console interface, or use the server configuration utility
( ), both of which provide a graphical interface that you can use to change the server
configuration parameter values.
For information about how use Administration Console to modify parameter values, see "Modifying
Parameters from the Administration Console" on page 297.
To edit the file using the server configuration utility:
2. Run the script.
After you finish specifying configuration parameter values, the script automatically
runs the script to regenerate the file and apply your changes. For
information about the script, see "kUpdateHtml.sh" on page 537.
Caution: If you make a change to the file that affects more than one node in a
cluster, you must:

o Stop all the nodes in the cluster.
o Run the script on each machine.
o Start all the nodes in the cluster, one at a time.
Note: To view a list of the server configuration parameter values on an active PPM Server, run
the Server Configuration report. (See "Running Server Reports from the Admin Tools Window"
on page 327 and "Running Server Reports from the Command Line" on page 331.)
The following table provides descriptions of the configuration parameters in the file. The
parameter names listed in the table are shortened versions of the actual names, all of which start with
the string . For example, the full name of the parameter
is .
Table A-1. Server configuration parameters

Parameter
Name
(*Required, Default and Valid
**Required If) Description, Usage Values
AAL_DATA_ Determines the maximum number of resources that can be Default:

EXTRACT_ extracted from the database and returned in the Analyze
Valid values:
MAX_ Assignment Load portlet in Resource Management. This acts as
Positive integer
RESOURCES a safety valve to prevent PPM Center from hanging if a user
defines portlet criteria that would return a very large volume of
data.
AAL_ Maximum number of resources pools to be represented in the Default:

PORTLET_ Analyze Assignment Load portlet in Resource Management.
Valid values:
MAX_
If the resource count exceeds the set value, the PPM Server Any positive integer
RESOURCES
stops calculating and displays no result in the portlet.
Note: Setting a very high value for this parameter could

affect system performance.
ALLOW_ If set to enables the Save Draft button on the Create Default:
SAVE_ New Request page, which allows Demand Management users to
Valid values:
REQUEST_ save requests without automatically submitting them in the

Table A-1. Server configuration parameters, continued

Parameter
Name
DRAFT standard interface.
APP_ Alert text that displays on the application server logon page
SERVER_ and headers.
ALERT_TEXT
**APP_ JBoss UIL2 Binding port. You must set a value for this Default:
SERVER_ parameter if the PPM Server is part of a server cluster.
Valid values:
UIL2_
If the PPM Server is
BINDING_
part of a cluster,
PORT
specify a value that
is unique for the
node.
ARP_MAX_ Maximum number of resource pools that can be represented in Default:

RESOURCE_ the Analyze Resource Pool portlet in Resource Management.
Valid values:
POOLS
If the resource pool count exceeds the set value, the Positive integer
PPM Server stops calculating and no result is displayed in the
portlet.

ARP_MAX_ Maximum number of resources that can be represented in the Default:

RESOURCES Analyze Resource Pool portlet in Resource Management.
Valid values:
If the resource count exceeds the set value, the PPM Server Positive integer
stops calculating and no result is displayed in the portlet.

ARP_ Maximum number of resources to be represented in the Default:

PORTLET_ Analyze Resource Pool portlet in Resource Management.
Valid values:
MAX_
If the resource pool count exceeds the set value, the Any positive integer
RESOURCE_
PPM Server stops calculating and displays no result in the
POOLS
portlet.


Parameter
Name

degrade system performance.
ASSET_ Specifies the batch size of time sheet lines for asset cost Default:
ROLLUP_ calculation.
Valid: Any positive
TIMESHEETLI
integer
NE_BATCH_
SIZE
*ATTACHMEN Absolute pathname of the directory where attached documents Example

T_DIRNAME are to be stored. This directory must:
l Give read/write access to Web browsers
l Be outside the directory tree if the system includes an

external Web server
In a server cluster, all servers must be able to access and share

the specified directory.
AUTHENTICA If set to access to all reports requires user Default:

TE_REPORTS authentication. (A user must provide a PPM Center user login
Valid values:
ID).
*AUTHENTICA Method(s) used to authenticate users. Default:

TION_MODE
To specify multiple modes, use a comma-delimited list of valid Valid values:
values.
AUTO_ Determines whether the user must enter a filter in the auto- Default:
COMPLETE_ complete dialog box in order to retrieve the initial results for
Valid values:
LONG_TYPE_ validations of type long. If set to and no user filter is
CULLTEXT_ specified, the validation returns an empty result set. The user
REQUIRED must then either click Find or select the Show All link.
AUTO_ Maximum number of rows in long auto-complete lists. Default:

COMPLETE_
LONG_TYPE_
MAX_ROWS


Parameter
Name
AUTO_ Sets query timeouts on auto-complete lists to prevent Default:

COMPLETE_ excessive database CPU use. (seconds)
QUERY_
TIMEOUT
AUTO_ Maximum number of rows to retrieve from the database for Default:
COMPLETE_ short type auto-completion lists.
SHORT_
TYPE_MAX_
ROWS
AUTOCOMPLE Interval at which the command status is refreshed to provide a Default:

TE_STATUS_ list of values in an auto-complete list. (seconds)
REFRESH_
RATE
BASE_ Dre: BASE_CURRENCY_ID: This is odd, default is not found in Default: 97

CURRENCY_ usual location even though parameter is used. Should this be
ID configurable?
BACKGROUN If ENABLE_BACKGROUND_SERVICE_MONITOR is enabled, this Default:

D_SERVICE_ parameter determines the threshold value of the Background (milliseconds)
MONITOR_ Services monitor.
THRESHOLD
BASE_ ID for the currency in which your organization maintains its Default:
CURRENCY_ accounting system.
ID
BASE_LOG_ Points to the "logs" directory directly under the directory Example
DIR specified for *BASE_PATH.

*BASE_PATH Full path to the directory where the PPM Server is installed. Default: Based on
the operating
system platform.
Example:


Parameter
Name
*BASE_URL Web location (top directory name) of the PPM Server. Example:
If you want to specify a literal IPv6 address, make sure you

enclose the literal address with " " and " " characters. For
example,
Note: HP strongly recommends you specify DNS name

instead of literal IPv6 address.
BASE_URL_ Used in the process of enabling the integration of PPM Center Default:
QC_INTEG with Quality Center when PPM Center is set up with an external
Valid values:
Web server with HTTPS enabled.
For detailed information on how to use this parameter, see the

.
BLOCK_ Specifies whether or not the system continues executing the Default:
PENDING_ subsequent package lines when a package line fails.
Valid: ,
PKGL_FOR_
If you set this parameter to , when a package line fails,
ERROR
the system continues executing the subsequent package lines.
If you set this parameter to , the execution is blocked
when a package line fails.
When a package line fails and its subsequent package lines

pass, the status of this execution is still successful in PPM
Workbench. However, you should note that even when the
status is successful, it does not mean all the package lines are
executed successfully in logical relationship to meet your
business needs. HP suggests that you exercise caution when
setting this parameter to false, unless you are absolutely sure
about the consequences.
BUDGET_IN_ Used with the parameter as Default:

THOUSAND_ follows:
Valid values:
SHOW_
l If is set to the


Parameter
Name
DECIMAL parameter is ignored and

values are displayed as whole numbers.
l If is set to and
is set to
values are displayed as 1000s without decimals. For
example, the value 1234567 is displayed as 1235.
l If is set to
values are displayed as 1000s with decimals. For example,
the value 1234567 is displayed as 1234.567.
BUDGET_IN_ Determines whether forecast, approved funding, and financial Default:

WHOLE_ summary values are expressed in whole dollars.
Valid values:
DOLLARS
BYPASS_ If set to true, prevents server checks at PPM Center startup. Default:
STARTUP_
Valid values:
CHECKS Caution:HP strongly recommends that you leave this
parameter set to unless HP Software Support has
advised that you set it to
CCM_ URL of the Change Control Management server and port Valid value format:
MACHINE_ number used for integration with PPM Center.
URL a
CHANGE_ License key for Demand Management. Default: N/A

MANAGEMEN
T_LICENSE_
KEY
CLIENT_RMI_ Port on which the PPM Server listens to initiate RMI Valid values:
URL client/server communication via port forwarding. Port numbers
higher than 1024
Must be a unique port, distinct from the Web server, SQL*Net,
and the HTTP or HTTPS ports. Example
Format:


Parameter
Name
CLIENT_ Frequency (in minutes) with which the PPM Workbench Default:
TIMEOUT interface session sends a message to the PPM Server that
indicates the client is still active.
Under normal operation, do not change this value.
CLOSE_ Determines whether the client browser closes after the user Default:
BROWSER_ quits the PPM Workbench.
Valid values:
ON_APPLET_
EXIT
CMQC_QC_ Specifies ALM/Quality Center version for CMQC solution. Valid values:
VERSION
CMQC_INIT_ The value for parameter for CMQC solution, for Valid value: string
STRING example,
You can get the value from Quality Center/ALM server.
The value is stored in a properties file

(ALM\jboss\server\default\deploy\20qcbin.war\WEB-
INF\siteadmin.xml) or an XML configuration file
(ALM\conf\qcConfigFile.properties) on the server where Quality
Center/ALM is installed.
COLOR_ Used to extend the number of colors available in the cached

CACHE_SIZE copy of the file.
**CONC_LOG_ Transfer protocol used to transfer concurrent request logs and Default:
TRANSFER_ patching README files. If you use Object Migrator with PPM
Valid values:
PROTOCOL Center, you must specify value.
FTP, SCP
Required if
ORACLE_
APPS_
ENABLED


Parameter
Name
**CONC_ Encrypted password of the concurrent request user. If you use Default: N/A
REQUEST_ Object Migrator with PPM Center, you must specify a value.
Valid values:
PASSWORD
Encrypted
Note: You must use to encrypt the password.
Required if password in the
For information on how to run the script, see
ORACLE_ format
"kEncrypt.sh" on page 523.
APPS_
ENABLED =
true
**CONC_ Valid user on the Oracle system that can be used to retrieve Example
REQUEST_ concurrent request output files. If you use Object Migrator with
USER PPM Center, you must specify value.
Required if Set the retrieval method (FTP or SCP).

ORACLE_
See CONC_LOG_TRANSFER_PROTOCOL.
APPS_
ENABLED =
true
COST_ Flag to enable cost capitalization globally. You can enable this Default:
CAPITALIZATI parameter only in the file.
Valid values:
ON_ENABLED
Note:HP strongly recommends that you disable this
parameter after you have enabled it.
COST_ Batch size of rows for the Cost Rollup Service to process. Default:
ROWS_
BATCH_SIZE
CUSTOM_ Enables customization of the text Default: N/A

SERVER_INFO displayed in the PPM Workbench title bar. For example,
Valid value:
Text string
DATE_ Interval at which the PPM Server is to check to determine Default:

NOTIFICATIO whether date-based notifications are pending, and to send (minutes)
N_INTERVAL them.
DAYS_TO_ Number of days applet keys are retained in the Default:


Parameter
Name
KEEP_ table.
APPLET_KEYS
DAYS_TO_ Number of days records are kept in the prepared commands Default:
KEEP_ tables before they are cleaned up.
COMMANDS_
ROWS
DAYS_TO_ Number of days to keep records of all interfaces. Default:

KEEP_
INTERFACE_
ROWS
DAYS_TO_ Number of days to keep records of all logon attempts. Default:

KEEP_
LOGON_ Note:PPM Center keeps a record of the most recent logon
ATTEMPT_ attempt, regardless of when it occurred. So, for example, if
ROWS the sole user only logs on once a month, PPM Center
retains the record of the last logon, even if
is set to 14 days.
**DB_ Oracle RAC (Real Application Clusters) service name. Example

CONNECTIO
N_STRING
(Required if
RAC is used)
DB_LOGIN_ Amount of time that the PPM Server is to continue to try to log Default:
TIMEOUT on to the database (acquire the JDBC connections that make up (milliseconds)
the connection pool) before reporting that the database is
unavailable.
*DB_ Password for the database schema that contains the PPM Example
PASSWORD Center tables.



Parameter
Name
DB_POOL_ Specifies database pool deadlock check interval. Default: 10

DEADLOCK_
CHECK_
INTERVAL
DB_ Specifies database reconnection check interval. Default: 240

RECONNECTI
ON_CHECK_
INTERVAL
DB_SESSION_ May have been replaced by ENABLE_DB_SESSION_TRACKING Valid values:

TRACKING
*DB_ Name of the database schema that contains the PPM Center Example
USERNAME tables.
DEFAULT_ Number of seconds the PPM Server can try to run commands Default:
COMMAND_ before it times out.
TIMEOUT
*DEFAULT_ Number of work plan lines that can be loaded into the Work Default:
PAGE_SIZE Plan page for all new users. This setting indicates whether to
use the fast setting or the slow setting (rather than indicating a
specific size).
In new installations, this defaults to the slow connection

setting. HP recommends that the system administrator review
this setting after installation.
If your system has mostly LAN users (fast connections), set this
to use the fast setting. If your system has mostly WAN/VPN
users (slow connections) or mixed usage, set this to use the
slower setting.
DEFAULT_
USER_
DEBUG_
LEVEL
*DEFAULT_ Initial type of page size (low, high, or custom) selected for the Default:
PAGE_SIZE_ Edit My Profile page.


Parameter
Name
OPTION Valid values:
and
DEFAULT_ Affects the Sort By field on the Search Requests page. The Default:
REQUEST_ default value is , which sorts the search results based on
Valid values:
SEARCH_ Request ID. If set to search results are returned
ORDER_BY_ unsorted.
ID
*DEFAULT_ Determines whether the time sheet items in HP Time Default:

TIME_ Management are grouped under appropriate headings, or
Valid values:
SHEET_ displayed in a flat list without headings. For detailed
LINES_VIEW_ information about grouped and ungrouped display of time
MODE sheet items, see the .
DEMAND_ Specifies the size of the demand set fields cache in number of Default:
FIELDS_ demand set.
CACHE_SIZE
DEMAND_ Timeout for the demand set fields cache, expressed in seconds. Default:
FIELDS_ (seconds)
CACHE_
TIMEOUT
DEPLOY_ Deployment destination. Default:

BASE_PATH
Note:HP recommends that you leave the default value
unless the PPM Server directory is renamed.
DIST_ Used in release distribution. Number of milliseconds the Default:

ENGINE_ monitor waits between checking existing result listener. Use (milliseconds)
MONITOR_ this parameter to adjust the amount of time the monitor
SLEEP_TIME sleeps between checks.
Note:HP recommends that you not change this value. It


Parameter
Name
does not affect performance.
DMS_DB_ To enable the database fulltext search feature in document Default:

ENABLE_ management for PPM Center, set this parameter to
Valid values:
FULLTEXT_
SEARCH Note: You must create and build database indexes in
advance. For details, see the
DMS_ Determines the number of characters shown in the References Default:

FILENAME_ section for the names of files attached to PPM Center entities.
Valid values:
DISPLAY_
Positive integer
LENGTH
DMS_ Specifies maximum number of matching items before applying Default:

FILENAME_ filters from other search criteria, such as creation date or
Valid values:
SEARCH_ "Closed" status. You may need to increase this value if too
integer
MAX_ many filename matching items are filtered out by very
RESULTS selective search criteria.
DMS_ Defines the file extensions that cannot be uploaded to PPM Valid values: ,
INSECURE_ Center. , , , ,
FILE_ , and
EXTENDSION
S
DMS_ Flags whether or not to prevent uploading files of the Default:

INSECURE_ extensions defined in the DMS_INSECURE_FILE_EXTENDSIONS
Valid values: ,
FILE_ parameter.
and
EXTENSION_
If you set this parameter to , files of all extensions are
CHECK
allowed to be uploaded. If you set this parameter to , files
of the extensions defined in DMS_INSECURE_FILE_
EXTENDSIONS cannot be uploaded.
DMS_XSS_ Flags whether or not to display the document download links. Default:
CHECK
If you set this parameter to , the document download links Valid values: ,
on PPM Center pages are hidden. and


Parameter
Name
DMS_ Determines the duration (in seconds) that a thread will wait Default:
MIGRATION_ between two documents to migrate. To lighten the load of the (seconds)
DELAY_ migration process on the PPM Server, increase the value of this
Valid values:
BETWEEN_ parameter.
Positive integer
DOCUMENT
DMS_ Determines the number of documents to be queued for Default:

MIGRATION_ migration on a given PPM Service node. Every time the DMS
Valid values:
DOCUMENT Migration Engine Service runs on a Service node, the queue of
Positive integer
S_BATCH_ documents to be migrated is filled up.
SIZE
DMS_ Specifies number of threads that will be migrating documents Default:

MIGRATION_ on a given PPM Service node.
Valid values:
THREAD_
integer
COUNT
EMAIL_ Email address of the default sender of email notifications. Example

NOTIFICATIO
This sender receives any error messages associated with email
N_SENDER
notifications.
ENABLE_ALL_ If you set this parameter to , you enable the UI monitor, Default:
PERFORMAN the portlet monitor, and the Background Services monitor,
CE_MONITOR regardless of whether these three monitors are enabled or not.
If you set this parameter to , the UI monitor, the portlet
monitor, and the Background Services monitor are enabled or
disabled according to their own parameters.
ENABLE_ If you set this parameter to , you enable the AntiSamy Default:
ANTISAMY feature to protect PPM from potential security issues. End Valid values:
users cannot open hyperlinks on request details page or project
details page.
If you set this parameter to , you disable the AntiSamy

feature. End users can open the hyperlinks on the request
details page or project details pages.
If you enable the AntiSamy feature and still want your end
users to access to specific hyperlinks, you can configure the the
file located in to add


Parameter
Name
those hyperlinks.
ENABLE_ If set to enables the background services monitor. Default:

BACKGROUN
Valid values:
D_SERVICE_
MONITOR
ENABLE_ Flags whether PPM server retrieves log/output files from Oracle Default:
CONC_FILES_ E-Business Suite server or not. The default value is .
Valid values:
RETRIEVAL
With the Oracle Apps (the extension for Oracle E-Business
Suite) and the extension for Oracle Technology deployed on
PPM Server, you may encounter performance issue with PPM
server retrieving log/output files from Oracle EBS server. For
better performance, you can add this parameter into the
file manually and set the parameter value to
to switch off the log/output files retrieval. Make sure
you restart the PPM Server for the server configuration
parameter to become effective.
ENABLE_ Related to requests in Demand Management. If set to , Default:

CONCURREN multiple users can change the same request simultaneously.
Valid values:
T_REQUEST_ Request data such as notes, new references and new table
UPDATES entries are always saved. Conflicting changes that cannot be
saved are displayed to the user as differences.
ENABLE_ Default: 3600

COST_
UPDATE_
SERVICE
ENABLE_ The Connection Correlation page is intended for use by HP Default:

CONNECTIO Software Support for troubleshooting and is disabled by default
Valid values:
N_ in a production environment. If the page is enabled, you access
CORRELATIO it by selecting Open > Administration > View connection
N correlation from the PPM Dashboard.
To enable the Open > Administration > View connection

correlation menu item and the Connection Correlation page,
add the parameter to the
file, and set its value to


Parameter
Name
ENABLE_DB_ If set to enables a stack trace to be reported in the PPM Default:

SESSION_ Center DB Server Reports, which you can use to track the exact
Valid values:
TRACKING line of code used to request a database connection.
ENABLE_ Add this parameter to the file and set it to Default:

DEBUGGING_ to enable debug logging to the file for a
Valid values:
PER_USER specific user. For more information, see "Enabling Debugging
On a Per-User Basis" on page 340.
(case-sensitive)
Note: The value is case-sensitive.
ENABLE_IPV6 Add this parameter to the file and set it to Default:

to enable support for IPv6.
Valid values:
Note: If this parameter is not present in the

file, the system uses IPv4 by default.
ENABLE_ Enables JDBC logging, which records SQL runs against the Default:
JDBC_ database, the time required to run the SQL, and the time to
Valid values:
LOGGING retrieve the results. This information is recorded in
in the server log directory.
This parameter is useful in debugging system performance

problems.
You can set this parameter in the PPM Workbench interface

without stopping the system (Edit > Settings).
ENABLE_ If set to the Remember my logon option is displayed on Default:

LOGIN_ the logon page, and a cookie is placed on the client browser to
Valid values:
COOKIE maintain a record of the user logon information.
Remember my logon sets a cookie on the local machine that

lets a user log on to PPM Center later, without providing logon
information. You can also view reports through notification
links, and so on, without logging on. This cookie is removed only
if the user clicks Sign Out (or clears cookies, or the cookie
expires). If a user closes the browser window without signing
off, the cookie is not cleared.


Parameter
Name
To disable this function, change the parameter value to .
Note: If PPM Center is integrated with an SSO provider such

as SiteMinder, then set this parameter to false. If PPM
Center is integrated with an SSO provider, HP
recommends that you keep the parameter set to true.
ENABLE_LW_ If added to the file and set to enables the Default: N/A
SSO_UI lightweight single sign-on (LW-SSO) user interface
Valid values:
ENABLE_LW_ (For integration of PPM Center Tasks with Service Manager Default: N/A
SSO_WEB_ RFCs only)
Valid values:
SERVICE
If LW-SSO authentication is enabled, add this parameter to the
file and set it to to specify that PPM Center
is to always use the current user to call the Service Manager
Web service.
ENABLE_ If set to enables the Mobility Access Service. Default:

MOBILITY_
Valid values:
ACCESS_
SERVICE
ENABLE_ Provided for backward compatibility if you have customized Default:

OVERVIEW_ "overview pages". If you do not have customized "overview
Valid values:
PAGE_ pages", leave the default value ( ).
BUILDER
ENABLE_ If set to enables sorting of portlet results. Default:

PORTLET_
Valid values:
FULL_
RESULTS_
SORTING
ENABLE_ If set to enables the portlet monitor, which gathers Default:

PORTLET_ statistics on portlet performance. If activity exceeds the
Valid values:
MONITOR threshold value (determined by the parameter), the captured
information is output to the log file, which
resides in same directory as the server log.


Parameter
Name
ENABLE_ If set to enables users with the required permission to Default:

PROJECT_ open the PPM Workbench as a stand-alone application using
Valid values:
LAUNCH_ Active X.
FROM_
ACTION_
MENU
ENABLE_ If set to a user who has the Resource Management: Default:

PROMISE_ Promise Unspecified Resources access grant can promise
Valid values:
RESOURCE_ allocations and modify or remove previously promised
ALLOCATION allocations. A user who does not have the access grant cannot
promise allocations or modify or remove previously promised
allocations. In this case, the promise allocations for the
resource pool (if any) are displayed (view-only) on the Staffing
Profile and the Resource Allocation Management pages. The
values are used in computing totals, regardless of whether the
user has the Resource Management: Promise Unspecified
Resources access grant.
ENABLE_ (For integrating with Quality Center version 10.00 only) If no Default:
QUALITY_ XML mapping file has been generated and deployed to both
Valid values:
CENTER_ PPM Center and Quality Center, set this value to If a
INTEGRATION mapping has been deployed, to enable the integration, set the
a value to
ENABLE_ If set to enables the advanced "query builder" capability Default:

QUERY_ for searching Demand Management requests.
Valid values:
BUILDER
ENABLE_ Controls the visibility of the Update button on the Quick List. Default:
QUICKLIST_
Valid values:
UPDATE
ENABLE_ To enable a restriction on the number of projects returned on Default:

RESTRICTION project searches, set this parameter to
Valid values:
S_ON_PROJ_
To specify the maximum number of projects returned on
SEARCH
project searches, set the
parameter.


Parameter
Name
ENABLE_ If set to , enables the Site Map link in the header of each Default:
SITE_MAP page.
Valid values:
ENABLE_ If set to enables the Skip Navigation link in the header Default:
SKIP_ of each page.
Valid values:
NAVIGATION
ENABLE_ Determines whether performance statistics for all SQL Default

SQL_TRACE statements run are placed into a trace file.
Valid values:
The SQL trace facility generates the following statistics for
each SQL statement:
l Parse, run, and fetch counts
l CPU and elapsed times
l Physical reads and logical reads
l Number of rows processed
l Misses on the library cache
l User name under which each parse occurred
l Each commit and rollback
This parameter corresponds to the Enable DB Trace Mode

checkbox in the Server Settings dialog box.
ENABLE_SSL_ Enables flag for the SSL Login page. If set to (default), Default:
LOGIN then the following parameters must also be set:
Valid values:
l HTTPS_PORT
l HTTPS_WEB_THREAD_MIN
l HTTPS_WEB_THREAD_MAX
l HTTPS_KEYSTORE_LOCATION


Parameter
Name
l HTTPS_KEYPASSWORD
ENABLE_ If set to specifies that a timestamp is written into the Default:

TIMESTAMP_ log for each line of debugging text that corresponds to actions
Valid values:
LOGGING you have performed. The timestamp can help you locate
information in the server log files about events that occurred
at a specific time, or to determine how much time elapsed
between specific logged statements.
Note: Including the timestamp adds text to each logged

statement, which bloats the log file and can make it more
difficult to read.
ENABLE_TM_ Default setting used by time sheet policies to specify what Default:
ALLOW_ occurs when users try to submit time sheets that contain
l when
EMPTY_ITEM empty lines (lines in which all values are 0). Time sheet policies
used by new
have options that correspond to these settings. For the users
time sheets or
assigned to a time sheet policy, the policy can override the
new time sheet
default value set for this parameter. Following are the
policies on an
parameter settings and descriptions of their effects if the
upgraded
user's time sheet policy does not override the selected setting:
instance or a
l The user can submit time sheets that contain new
empty lines. installation.
l PPM Center displays a warning that advises the l for

user to consider entering data in the empty lines before existing time
submitting the time sheet. The user can, however, still sheets on an
submit the time sheet. upgraded
instance.
l PPM Center requires the user to enter data in
the empty lines or delete those lines before submitting the Valid values:
time sheet.
Note: To improve PPM Center performance and to make

it easier for approvers to review submitted time sheets,
HP strongly recommends using the setting.


Parameter
Name
For more information about time sheet policies, see the
ENABLE_TM_ If set to the Allowed work item types list on the Work Default:
WORK_ITEM_ Items tab of a time sheet policy includes the Packages
Valid values:
PACKAGES checkbox. If set to the Packages checkbox is not
displayed.
For information about the Work Items tab, see the
ENABLE_TM_ If set to , the External Data option is available in the Default:

WORK_ITEM_ following PPM Workbench windows:
Valid values:
EXTERNAL_
l On the Work Items an Activities tabs of the Tim Sheet Policy
DATA
window
l In the Work Item Type drop-down list (under the

Dependencies section) of the Override Rule window
WORK_ITEM_ Items tab of a time sheet policy includes the Projects checkbox.
Valid values:
PROJECTS If set to the Projects checkbox is not displayed.
WORK_ITEM_ Items tab of a time sheet policy includes the Requests
Valid values:
REQUESTS checkbox. If set to the Requests checkbox is not
displayed.
WORK_ITEM_ Items tab of a time sheet policy includes the Tasks checkbox. If
Valid values:
TASKS set to the Tasks checkbox is not displayed.
ENABLE_ If set to enables the TM-PM Sync Service, which Default:


Parameter
Name
TMPM_ synchronizes time sheet updates from HP Time Management to Valid values:
SYNC_ project work plan tasks in Project Management, at the interval
SERVICE specified by the TMPM_SYNC_SERVICE_INTERVAL parameter.
ENABLE_UI_ If set to enables the activity monitor, which captures UI Default:

MONITOR activities (mainly URL requests). If activity exceeds the
Valid values:
threshold value (determined by the UI_MONITOR_THRESHOLD
parameter), the captured information is output to the
log file. This file resides in same directory
as the server log.
ENABLE_ If set to tells Tomcat to log all http requests received. Default:
WEB_
Valid values:
ACCESS_ Note: If this is enabled on a busy system, Web access
LOGGING logging can generate many log files.
ENABLE_ Enables the PPM Center Web services interface. Default:

WEB_
Valid values:
SERVICES
ENABLE_ If set to the Allowed work item types list on the Work Default:
WORK_ITEM_ Items tab of a time sheet policy includes the Miscellaneous
Valid values:
MISC Items checkbox. If set to the Miscellaneous Items
checkbox is not displayed.
ENABLE_ If set to the PPM Server receives notifications of Default:

WORKBENC completed concurrent requests from the Concurrent Request
Valid values:
H_ Watch background service and updates the status on PPM
NOTIFICATION Workbench clients connected to that server. If set to
S PPM Workbench clients connected to the server do not
receive automatic updates unless the Concurrent Request
Watch background service is running on this node.
ETL_END_ If PPM Center's Operational Reporting solution is implemented, Default: N/A

DATE this determines the end date for the PPM Center data to
Valid values:
extract, transform, and load into the Operational Reporting
database schema.


Parameter
Name
Calendar date in
the format
ETL_START_ If PPM Center's Operational Reporting solution is implemented, Default: N/A

DATE this determines the start date for the PPM Center data to
Valid values:
extract, transform, and load into the Operational Reporting
database schema. Calendar date in
the format
EV_ALLOW_ If set to , indicates that if a task or project is less than Default:

PRORATING 100 percent complete, the earned value is calculated to be 0.
Valid values:
The EV calculation is 100 only if the task or project is 100%
complete.
EXCEL_ Specifies the maximum number of positions that can be Default:

EXPORT_ exported to Excel on the Forecast Planning page.
POSITIONS_
LIMIT
EXCEL_ Specifies the maximum number of resources that can be Default:

EXPORT_ exported to Excel on the Search Resources page.
RESOURCES_
LIMIT
EXCEPTION_ Determines the level of detail to include in internal error Default:

DETAIL_ exceptions displayed in PPM Center. The exception message is
Valid Values:
LEVEL included in server logs.
Integer using
This parameter uses a bitwise value combination, as follows: bitwise value
combination
l If bit 1 is set to 1 (001), the message includes exception
(includes
correlation information.
correlation
l If bit 2 is set to 1 (010), the message includes the information and
application server node name. server node name)
l If bit 3 is set to 1 (100), the message includes the filtered

stack trace.
A value of 7 includes all levels of detail. for the error.


Parameter
Name
EXCEPTION_ Determines the time at which the daily exception engine full Default: (1:00
ENGINE_ calculation runs. A full calculation is needed for exceptions that AM)
WAKE_UP_ occur as time elapses. The default value of 1 (1:00 AM) specifies
Valid Values:
TIME that the daily exception calculation is performed once every
day at 1:00 AM. Integer between 1
and 24
EXCEPTIONS_ Number of days non-service PPM Center exceptions are to be Default:

RETAIN_ retained. Valid Values:
PERIOD Zero or higher
Also see LOG_EXCEPTIONS_TO_DB.
integer
EXTERNAL_ If you are using an external Web server to serve PPM Center Valid value:
WEB_PORT clients, you must configure this parameter as an available port Any available port
that can communicate with the PPM Server. This port receives number
AJP (Apache JServ Protocol) requests from the external Web
server. AJP is the standard protocol used for communication
between a Web server and an application server.
Note: If you are using an external Web server, you must

still configure the standard PPM Center"Using the Server
Configuration Utility to Modify Server Configuration
Parameters" on page 424. This port is used internally by
PPM Center reports. There is no need to make it accessible
to the network.
FAIL_ If the PPM Server stops while command executions are running, Default:
EXECUTIONS_ those executions are interrupted and the parent entities
Valid values:
ON_STARTUP (package lines, releases, requests, and so on) are assigned the
status "in progress". This parameter tells the server that, after
it starts, it must check for any entities that have "in progress"
status and that have no executions running (that is, executions
that were interrupted). The server sets the internal status of
those entities to FAILED, with a visible status of "Failed
(Interrupted)".
FONT_SIZE_ Specifies a font size for displaying larger or smaller characters Default:
OF_GRAPHIC_ in workflow layout images.
WORKFLOW


Parameter
Name
FORECAST_ Number of staffing profile positions displayed on a Forecast Default:

PLANNING_ Planning page in Resource Management.
PAGE_SIZE
FS_QUEUE_ Initial number of concurrent instances of the Financial Default:

CONCURREN Summary background service.
Valid values:
T_
Non-negative
CONSUMERS
integer
FS_QUEUE_ Maximum number of concurrent instances of the Financial Default:

MAX_ Summary background service.
Valid values:
CONCURREN
Non-negative
T_
integer
CONSUMERS
FULL_NAME_ Format in which the full names are displayed for resources, Default:
FORMAT contacts, and so on.
Valid values: 0, 1
0 denotes First
Last. Example: John
Smith.
1 denotes Last,
First. Example:
Smith, John
GRAPHICAL_ If set to makes links to view graphical workflow available Default:

WF_ENABLED on submitted requests.
Valid values:
GROUP.PRIVA If set to after a user selects Dashboard > Personalize Default:

TE. Dashboard, the PPM Dashboard displays two sections: Private
Valid values:
PUBLIC.PAGE and Shared. The Private section contains single pages and
S groups, the Shared section contains modules. If set to false,
dashboard pages will appear as a flat list.
GZIP_ Determines whether HTTP responses are compressed before Default:

ENCODING_ they are sent to PPM Center HTML clients. If set to then
Valid values:
ENABLED textual HTTP responses are compressed using GZIP
compression (if the requesting browser supports GZIP).


Parameter
Name
By default, this is set to to improve the responsiveness of

the PPM Center standard (HTML) interface, because less overall
data is carried across the Internet between the client and the
PPM Server.
If all PPM Center clients have fast network access to the

PPM Server, then consider setting this parameter to to
reduce the overhead of compressing and decompressing
responses.
Caution: There is a known issue related to GZIP

compression in the Oracle Java Virtual Machine (for details,
see http://bugs.java.com/bugdatabase/view_bug.do?bug_
id=8028216). If you see GZIP exceptions in the server log,
you should set this parameter to until Oracle fixes
this issue.
*HEAVY_ Number of listeners per node to execute heavy background Default: 1

QUEUE_ services.
Valid values:
CONCURREN
Positive integer
T_
CONSUMERS
*HEAVY_ Maximum number of listeners per node to execute heavy Default: 1

QUEUE_MAX_ background services.
Valid values:
CONCURREN
Positive integer
T_
CONSUMERS
*HEAVY_ Maximum depth of the heavy services queue. Default:

QUEUE_MAX_
Valid values:
DEPTH
Positive integer
*HEAVY_ Delay between redeliveries of messages to the heavy service Default:

QUEUE_ queue. (milliseconds)
REDELIVERY_
Valid values:
DELAY
Positive integer


Parameter
Name
*HEAVY_ Number of times messages are to be redelivered to the heavy Default:

QUEUE_ service queue.
Valid values:
REDELIVERY_
Positive integer
LIMIT
*HIGH_PAGE_ Recommended number of work plan lines to load into the Work Default:
SIZE Plan page if the user is connected through a fast connection
Valid values:
such as a LAN.
Positive integer
HIGHLIGHT_ If set to for time sheets on which time is logged on a daily Default:
NONWORKIN basis, the columns for non-working days are highlighted in
Valid values:
G_DAYS_IN_ color.
TIMESHEET
*HISTORY_ Number of links to display in the History menu in the PPM Default:
MENU_SIZE Center standard interface.
Valid values:
Positive integer
*HOURS_TO_ Number of hours to keep rows in the Default:

KEEP_ table.
Valid values:
DEBUG_
For high-volume PPM Center installations, a large number of Positive integer
MESSAGE_
rows may be generated in this table. For such installations,
ROWS
decrease this value accordingly.
*HTTP_PORT Port to use to communicate with the built-in HTTP server. Default:
If PPM Center is in stand-alone mode (that is, it is not Valid values: Unique
integrated with an external Web server), then PPM Center port greater than
clients must have access to the HTTP_PORT. 1024 and distinct
from the Web
If PPM Center is integrated with an external Web server, then
server, SQL*Net,
client HTTP traffic is routed through the EXTERNAL_WEB_
and RMI ports.
PORT However, even in that case, the PPM Server still uses the
*HTTP_PORT internally to run reports. In this case, it is not
necessary to make the *HTTP_PORT externally accessible to
PPM Center clients (and thus, the port need not be exposed
outside of the PPM Server).


Parameter
Name
Note: If you are integrating PPM Center with Application

Lifecycle Management, then you must set the parameter
to a number less than 32767.
HTTP_ URL of the HTTP proxy server used for PPM Center to connect
PROXY_URL to the Internet. It can be used by integration solutions or other
PPM Center functionality.
HTTPS_ Specifies the ciphers for the SSL/ TLS protocol with which the Default: N/A
CIPHERS PPM Server negotiates. This parameter accepts a comma-
Valid values:
separated list of ciphers that the server is to allow for SSL/TLS
comma-separated
connections. You can use the parameter to limit the cipher
list of ciphers
suite to a set of specific strong ciphers.
HTTPS_ Keystore password (encrypted). This setting is required if the Default: N/A
KEYPASSWO ENABLE_SSL_LOGIN parameter is set to
Valid values:
RD
Encrypted
password in the
format
HTTPS_ Full path location of the keystore. This parameter setting is Default: N/A
KEYSTORE_ required if the ENABLE_SSL_LOGIN parameter is set to
Valid values: N/A
LOCATION
HTTPS_PORT HTTPS port to use for SSL Login. This parameter setting is Default:
required if the ENABLE_SSL_LOGIN parameter is set to
Valid values:
Must be the HTTP_
PORT number + 363
HTTPS_ Specifies the HTTPS protocol (TLS) the PPM Server uses. Default:
PROTOCOL
Valid values:
Note: Starting from version 9.31, SSLv3 as the HTTPS
protocol is disabled in order to enhance security.
HTTPS_ Specifies the HTTPS protocols in details. Default: ,

ENABLED_ ,


Parameter
Name
PROTOCOLS
HTTPS_WEB_ Maximum number of HTTPS threads. This parameter setting is Default:

THREAD_MAX required if the ENABLE_SSL_LOGIN parameter is set to
Valid values:
Positive integer
HTTPS_WEB_ Minimum number of HTTPS threads. This parameter setting is Default:

THREAD_MIN required if the ENABLE_SSL_LOGIN parameter is set to
Valid values:
Positive integer
I18N_CARET_ Caret position on input fields (for example, text fields). Default:
DIRECTION
If unspecified, the system uses the value specified for I18N_ Valid values:
SECTION_DIRECTION
(left to right,
right to left)
I18N_ Character encoding to be used on all HTML pages in the PPM Default:
ENCODING Center standard interface.
I18N_ Default layout direction of HTML pages in the PPM Center Default: ltr
LAYOUT_ standard interface.
Valid values:
DIRECTION
(left to right,
right to left)
I18N_ HTML character set used to generate PL/SQL reports. Default:

REPORT_
Must map to the character set specified for I18N_REPORTS_
HTML_
ENCODING Valid values:
CHARSET
Any character set
names that Oracle
recognizes
I18N_ Character encoding to use to generate reports in PPM Center. Default:

REPORTS_
HP recommends for Windows systems. Valid values:
ENCODING
Any encoding
algorithm that
Oracle can
interpret.


Parameter
Name
I18N_ Layout direction of custom sections (for example, request Default:

SECTION_ detail sections).
Valid values:
DIRECTION
If unspecified, the system uses the value specified for I18N_
LAYOUT_DIRECTION.
IMPACT_ If you have enabled the attachment of Universal CMDB Impact Default: N/A
ANALYSIS_ Analysis Reports for CIs in PDF format to requests in PPM
Valid values:
REPORT_ Center, use this parameter to specify the default category
CATEGORY value for impact analysis reports, for example, change or
operation.
For details, see the
ANALYSIS_ Analysis Reports for CIs in PDF format to requests in PPM Valid values:
REPORT_ Center, use this parameter to set the default language code.
LANGUAGE
IMPACT_ Specifies a name for the UCMDB impact analysis report. Default:
ANALYSIS_
REPORT_
NAME
ANALYSIS_ Analysis Reports for CIs in PDF format to requests in PPM Valid values:
REPORT_ Center, use this parameter to set the default severity value for
SEVERITY the impact analysis report. For details, see the


Parameter
Name
*INSTALLATIO Language and country code of the PPM Center installation. The Default:
N_LOCALE language code must match the PPM Center installation Valid values: PPM
language. Center installation
language code
JAVA_ JRE classes location. Example:

CLASSES_LOC
JAVA_ Class ID for the Java plugin used for the PPM Workbench. Default:
PLUGIN_
CLASSID
JAVA_ Web location for downloading the cross-platform Java plug-in Default:
PLUGIN_ bundle for Internet Explorer browsers.
PATH_IE
Caution: Internet Explorer versions 7 and 8 display a
warning if the value contains the
protocol identifier " ".
If you override the default setting for this parameter,

make sure that you remove the protocol identifier
" ".
JAVA_ Web location for downloading the cross-platform Java plug-in Example:
PLUGIN_ installer for Netscape browsers.
PATH_NS


Parameter
Name
JAVA_ Earliest version of the Sun Java plug-in used to start the PPM Default:
PLUGIN_ Workbench.
VERSION
JAVA_ Web location for downloading the cross-platform Java plug-in Example:
PLUGIN_XPI_ installer for Firefox browsers.
PATH
JDBC_ Enables debugging of the Java database calls. Default:

DEBUGGING Valid values:
*JDBC_URL Locator for the database that contains the PPM Center Default:
database schema. Example:
Note:
Must be specified correctly for PPM Server to communicate
For
with the database.
Oracle
Format:
RAC
where
(Real
Applicati l is the DNS name or IP address of the system
on running the database
Cluster
s), this l is the port used by SQL*Net to connect to the
paramet database. Refer to the database entry in the
er must file
contain
l is the database system ID.
the host
and port
informa Note: If you want to specify a literal IPv6 address, make
tion for sure you enclose the literal address with " " and " "
all characters. For example,
databas


Parameter
Name
es to Note: HP strongly recommends you specify DNS name

which instead of literal IPv6 address.
the
PPM Ser
ver
connect
s.
*JOB_ Timeout (in minutes) for cleaning the table. Default:

STATUS_ (minutes)
CLEANUP_ Valid values:
INTERVAL
JSP_ Determines whether changes to JSP files are picked up on a Default:

RECOMPILE_ running server, thereby quickly making them visible. on
ENABLED production
If set to JSP files are checked for changes only the first
systems, on
time they are accessed, with the result that changes are visible
development
only after the server is restarted.
systems
Valid values:
*JSP_ If JSP_RECOMPILE_ENABLED is set to , changes made to Default:

COMPILE_ the JSP files inside the folders specified by the JSP_COMPILE_
EXCLUDE_ EXCLUDE_FOLDERS parameter are picked up on a running
FOLDERS server, therefore making them visible quickly.
JVM_ For HP internal use only. Do not alter its value unless directed to Default: N/A
OPTIONS do so by HP Software Support for PPM Center.
KEEP_ALIVE_ Frequency with which the client sends keep-alive messages to Default:
INTERVAL the PPM Server.
KEY_STORE_ Specifies the keystore file for Secure RMI. (See "Enabling Default: N/A
FILE Secure RMI (Optional)" on page 102.)
KEY_STORE_ Password for the keystore created for Secure RMI. (See Default: N/A
PASSWORD "Enabling Secure RMI (Optional)" on page 102.) Valid values:
Encrypted


Parameter
Name
password in the
format
**KINTANA_ PPM Center account on the LDAP server. Default: N/A

LDAP_ID Used by the PPM Server to bind to the LDAP server. Examples:
Required if
AUTHENTICA
TION_MODE =
LDAP
**KINTANA_ PPM Center password on the LDAP server. Default:

LDAP_ The PPM Server configuration utility automatically encrypts this Format:
PASSWORD password. To manually edit this value, surround the encrypted
Required if password with delimiters.
AUTHENTICA
TION_MODE =
LDAP
KINTANA_ Used in non-HTML notification, this parameter value is specified Example:

LOGON_ with the filename (to be appended to the URL), which points to
FILENAME the logon page.
Note:HP recommends that you not reset this parameter.
KINTANA_ Server directory location. Set this value if you have a clustered Default:
SERVER_ server setup.
DIRECTORY
KINTANA_ The server sets the (read-only) value of this parameter at Example:
SERVER_LIST runtime.
*KINTANA_ Name of the PPM Server instance. Default:

SERVER_ If multiple PPM Servers are running on the same machine, this
NAME name must be unique for each server.
If the server is running Windows, this name must match the
name of the Windows service name.


Parameter
Name
*KINTANA_ Time set to elapse before the PPM Server terminates a user Default:
SESSION_ session (in the PPM Workbench or standard interface) because (minutes)
TIMEOUT of inactivity. A value of 0 denotes no timeout. Valid values:
through
LDAP_BASE_ Base distinguished name on the LDAP server. Each LDAP URL Default: N/A
DN must specify a base distinguished name (DN), which is used in Examples:
place of the LDAP_BASE_DN server configuration parameter. If
the URLs provided for LDAP_URL_FULL do not have a DN value,
PPM Center uses the value set for LDAP_BASE_DN.
LDAP_BASE_ Base distinguished name on the LDAP server. Each LDAP URL Default: N/A
DN must specify a base distinguished name (DN), which is used in Examples:
place of the LDAP_BASE_DN server configuration parameter. If
the URLs provided for LDAP_URL_FULL do not have a DN value,
PPM Center uses the value set for LDAP_BASE_DN.
LDAP_ If set to enables LDAP dereferencing. Default:

ENABLE_ For more details about LDAP dereferencing, see "Dereferencing Valid values:
DEREFERENC Aliases" on Oracle's Sun Developer Web site
ING (java.sun.com/products/jndi/tutorial/ldap/misc/aliases.html).
**LDAP_ Number of levels of subgroups to traverse when importing Default:

GROUP_ users from groups.
RECURSION_
LIMIT
(Required if
AUTHENTICA
TION_MODE =
LDAP)
LDAP_ LDAP keystore. Default: N/A

KEYSTORE
LDAP_ LDAP keystore password. Default: N/A

KEYSTORE_ Valid values:
PASSWORD Encrypted
password in the
format


Parameter
Name
LDAP_LAST_ Last time the LDAP import was run. Default: N/A
SYNCH_
TIMESTAMP
LDAP_ If set to enables the LDAP server to follow referrals. Default:

REFERRAL_ Valid values:
CHASE
LDAP_ Maximum number of referral hops that the LDAP libraries can Default: 10
REFERRAL_ follow.
HOP_LIMIT
LDAP_ Type of LDAP server used. Default: N/A

SERVER_
TYPE
**LDAP_SSL_ SSL port number on the LDAP server. If not specified, all Default:
PORT transactions are carried over the port specified for **LDAP_
Required if URL.
AUTHENTICA
TION_MODE =
LDAP
**LDAP_URL Comma-delimited list of LDAP URLs, which the PPM Server Format:

(Required if queries in the order specified.
AUTHENTICA
TION_MODE = Note: Example:
LDAP)
l In version 9.30, make sure you specify a port number
even when you use the default port number 389 for
LDAP server or when you use SSL-enabled LDAP server.
Otherwise, an error occurs.
l The parameter supersedes the

parameter. That is, if a value is set for both in the
file, is used. If the URLs
specified for do not have a DN value,
the value set for is used.


Parameter
Name
LDAP_URL_ PPM Center uses this parameter to handle multiple domains Example:
FULL during LDAP authentication. The values for the parameter
include a space-separated (not comma-separated) list of full
LDAP URLs. Each LDAP URL must specify a base DN.
Notes:
l To specify a space character inside a URL, use the URL
encoding scheme, and replace the space with " ". For
example, if you have an organizational unit called "My
Org Unit", then specify " " in the LDAP
URL.
l The parameter supersedes the

parameter. That is, if a value is set for both in the
file, is used. If URLs
specified for do not have a DN value,
the value set for is used.
LICENSE_KEY License key required to use PPM Center core functionality. Example
*LIGHT_ Number of listeners per node to execute light-weight Default:

QUEUE_ background services. Valid values:
CONCURREN Positive integer
T_
CONSUMERS
*LIGHT_ Maximum number of listeners per node to execute light Default:

QUEUE_MAX_ background services. Valid values: |
CONCURREN Positive integer
T_
CONSUMERS
*LIGHT_ Maximum depth of the light services queue. Default:

QUEUE_MAX_ Valid values:
DEPTH Positive integer
*LIGHT_ Delay between redeliveries of a message to the light service Default:


Parameter
Name
QUEUE_ queue. (milliseconds)

REDELIVERY_ Valid values:
DELAY Positive integer
*LIGHT_ Number of times a message can be redelivered to the light Default:

QUEUE_ service queue. Valid values:
REDELIVERY_ Positive integer
LIMIT
LOAD_ Determines how much load to place on a node in the server Default:
FACTOR cluster. Valid values:
LOCAL_IP Used to construct the servlet URL for use by PPM Server when Defaults to the IP
the PPM Server internally invokes one of its own servlets. An address extracted
example of this is when a report is executed. Ordinarily, this from the server
parameter should not need to be specified. configuration
parameter *RMI_
URL
Example:
LOG_ The menu item Search > Administrative > Exceptions, which Default:
EXCEPTIONS_ opens the Search Exceptions page, is hidden by default. To Valid values:
TO_DB enable it, set the parameter to
You must have the administration license and the "server tools:
Execute admin tools" access grant to access the Search
Exceptions page.
Except for service exceptions, all exceptions more than 14 days
old are purged automatically. To reduce the load on the
PPM Server, the purge is triggered for every 100th exception
created. The value of 14 days can be configured using the
EXCEPTIONS_RETAIN_PERIOD parameter.
LOGIN_ Maximum age (and thus the expiration) of cookies used to start Default: (days)
COOKIE_ a PPM Center session. Valid values:
MAX_AGE
LOGON_ Method used to log on to PPM Center. Default:

METHOD
LOGON_PAGE URL for the PPM Center logon page. Default:


Parameter
Name
*LOGON_ Interval (in minutes) during which logon attempts are Default:
TRIES_ monitored. (minutes)
INTERVAL Valid values:
Positive integer
*LOW_PAGE_ Number of work plan lines to load into the Work Plan page if Default:
SIZE the user is connected through a slow connection such as a WAN. Valid values:
Positive integer
LW_SSO_ If LW-SSO authentication is enabled, add this parameter to the Default: N/A
CLEAR_ file to specify that PPM Center must clear the Valid values:
COOKIE LW-SSO token when a user logs out of PPM Center.
Note: For security purposes, HP recommends that you

always keep this parameter set to
DOMAIN file to specify the LW-SSO domain. Valid values:
LW-SSO domain
Example:
LW_SSO_ The token for validating user logon has an expiration value that Default: N/A
EXPIRATION_ determines an application's session validity. If LW-SSO Valid value: Integer
PERIOD authentication is enabled, add this parameter to the (minutes)
file to specify the LW-SSO token expiration Recommended
period in minutes. value:
Configure a token expiration for each HP application that uses
LW-SSO. HP recommends that you set the value to 60
(minutes).
Note: The expiration value must be at least as high as that

of the application session expiration value. For more
information, see "Configuring PPM Center for LW-SSO" on
page 221.


Parameter
Name
INIT_STRING file to specify the value of the Valid value:

parameter. For information about the parameter, String value at
see "LW-SSO Security Warnings" on page 217. least 12 characters
long
TRUSTED_ file to specify one or more LW-SSO trusted Valid value:
DOMAIN domains. To separate multiple domains, use semicolons (;). Example:
;
MAC_LOG_ Logging level to use. If set to 0, only integration exceptions and Default:
SEVERITY a a summary are logged. If set to 1, events other than errors Valid values:
related to processing changes are also logged. and
MAX_BATCH_ Maximum number of time sheets that can be frozen or closed Default: None
TIMESHEET_ at one time is the of: Valid values:
FREEZE_ l Value of this parameter, which has no default value, and a Integer
CLOSE recommended value of 50.
l Value of the Results Displayed Per Page field on the Search

for a Time Sheet to Freeze/Close page (which has a default
value of 50).
MAX_BATCH_ Maximum number of time sheets that can be approved at one Default: None
TIMESHEET_ time is the of: Valid values:
LINE_ l Value of this parameter, which has no default value, and a Integer
APPROVE recommended value of 50.
l Value of the Results Displayed Per Page field if using the

Approve Time Sheets page (which has a default value of 50),
or Rows Displayed field if using the Approve Time Sheets
portlet (which has a default value of 5).
MAX_ Maximum number of results to display in bubble charts. Default:

BUBBLE_
CHART_
RESULT
MAX_ Maximum number of bubbles (entities) that can be displayed in Default:

BUBBLE_ a bubble chart. Valid values:


Parameter
Name
CHART_SIZE Integer
MAX_ Specifies the maximum number of concurrent users to import Default:

CONCURREN time information from HP Agile Manager.
Valid values:
T_AGM_
REST_CALL_
FOR_ Recommended
TIMESHEET range:
MAX_DB_ Amount of time (in minutes) that an unused database Default:

CONNECTIO connection stays open before it is closed and removed from the (minutes)
N_IDLE_TIME pool.
MAX_DB_ Amount of time that a database session is held open before it Default:
CONNECTIO is closed and removed from the pool. (minutes)
N_LIFE_TIME Some Oracle cleanup operations that should be run periodically
occur only at the end of database sessions. Therefore, do not
keep database sessions open for the life of the PPM Server.
MAX_DB_ Amount of time that the system waits before it times out a Default:
CONNECTIO request for a database connection. (seconds)
N_WAIT_
TIME
MAX_DB_ Maximum size of each of the two database connection pools Default:
CONNECTION that the PPM Server creates. Each user does not get a
S dedicated connection. The server uses connection pooling, so it
opens a new database connection only if no connections are
available in the pool.
After this number is reached, user sessions queue for the next
available database connection.
*MAX_ Maximum number of concurrent executions allowed to run on Default:

EXECUTION_ the server. If your system is heavily loaded, decreasing this may
MANAGERS help reduce load, but may also delay execution of tasks.
If your organization processes a high volume of packages, you
may require more execution managers.
MAX_QC_ Specifies the maximum number of releases from ALM to be Default:

ALM_ displayed on the Project Details page in PPM Center
RELEASES_


Parameter
Name
NUMBER
*MAX_ Maximum number of logon attempts in the time interval Default:

LOGON_ specified for *LOGON_TRIES_INTERVAL.
TRIES
*MAX_PAGE_ Absolute maximum number of work plan lines that can be Default:
SIZE loaded into the Work Plan page. Use this parameter to prevent
excessive load on the server from excessive queries, and to
prevent users from getting themselves into low performance
situations.
*MAX_ Number of command executions that can run in a release Default:

RELEASE_ distribution simultaneously. Valid values:
EXECUTION_ Organizations that process a high volume of packages may Integer greater
MANAGERS require a larger number of release execution managers. than 1
MAX_ Specifies the maximum number of projects returned on project Default:

RESULTS_ searches. Valid values:
ALLOWED_ To set this restriction, you must also set the ENABLE_ Positive integer
ON_PROJ_ RESTRICTIONS_ON_PROJ_SEARCH parameter.
SEARCH
MAX_ Specifies the maximum number of audit event query results. Default:
RESULT_OF_ Valid values:
AUDIT_ Positive integer
EVENT_
QUERY
MAX_ Number of file backups to be maintained when Default:

SERVER_ application configuration parameters are updated through the Positive integer
CONF_ Administration Console.
BACKUPS
MAX_WEB_ Specifies maximum attachment size (in MB) for files uploaded Default:
ATTACHMEN using PPM Center web interface. Attachments size is capped at Valid values:
T_SIZE_IN_ 2 GB. Integer
MB
MOBILITY_ Number of emails that the Mobility Access service fetches in a Default:
ACCESS_ single batch.


Parameter
Name
BATCH_SIZE
MOBILITY_ Amount of time the PPM Server tries to connect to the email Default:
ACCESS_ account before it times out.
FETCH_
TIMEOUT
MOBILITY_ Controls whether to hide or display the initial text in an Mobility Default:
ACCESS_ Access email notification.
HIDE_
INITIAL_
MESSAGE
MOBILITY_ Number of minutes the Mobility Access service is to wait after Default:
ACCESS_ the start time or the last batch sent, before sending out the
SERVICE_ next batch of email notifications.
INTERVAL
MOBILITY_ Number of threads that the Mobility Access service uses to Default:
ACCESS_ process emails.
THREAD_
COUNT
MSP_NOTES_ Maximum size of Microsoft Project notes in PPM Center. Notes Default:
SIZE_LIMIT larger than the size specified for this parameter are truncated
when MSP data is synchronized with PPM Center.
MSP_ Microsoft Project includes a set of pre-defined text fields Default:

PROJECT_ (Text1, Text2, Text3, and so on) that users can use to store
CUSTOM_ whatever they want. By default, PPM Center uses the Text30
FIELD field at the project level in Microsoft Project to store
information about the PPM Center project with which the
Microsoft Project file is associated.
If you already use the Text30 field in Microsoft Project, you can
use this parameter to specify the Microsoft Project field for
PPM Center to use.
Caution: Do not change this parameter value after the

Microsoft Project integration has been used.


Parameter
Name
MSPS_ Used to specify which enterprise custom resource field name is Default: none
RESOURCE_ to be used by the Plug-in for PPM during enterprise resource
CUSTOM_ mapping.
FIELD Make sure that you specify a value for this parameter for each
resource on all MSP Servers, and that the value uniquely
identifies a resource across all MSP Servers. Use this
parameter when working with multiple MSP servers.
MULTICAST_ Unique name of a PPM Server cluster. This parameter, along Example:

CLUSTER_ with the MULTICAST_IP and MULTICAST_PORT parameters,
NAME determines whether PPM Center starts in server cluster mode,
or stand-alone mode.
Caution: Do not configure two clusters with the same

name running on the same subnet.
Caution: The IP address you specify for MULTICAST_

CLUSTER_NAME must not include the text string
MULTICAST_ Determines whether or not incoming and outgoing multicast Default:

DEBUG messages are logged to the PPM Server log. Valid values:
MULTICAST_ IP address used for exchange of heartbeat messages, cache Default: N/A
IP synchronization, and cluster communication. Valid values:
For information about the IP addresses that you can use for
, see the IPv4 Multicast Address Space Registry through
Web page (http://www.iana.org/assignments/multicast-
addresses/multicast-addresses.xml), which is maintained by
the Internet Assigned Numbers Authority (IANA).
Note: The IP address you specify for must

include the text string " ".
Caution: If you want to specify a literal IPv6 address here,

do not enclose the literal address with " " and " "
characters. To specify a valid IPv6 multicast IP address, see


Parameter
Name
http://www.iana.org/assignments/ipv6-multicast-
addresses/ipv6-multicast-addresses.xhtml.
MULTICAST_ Amount of time that must elapse after the PPM Server Default:
LEASE_MILLIS heartbeat stops, before the PPM Server is considered (milliseconds)
terminated.
MULTICAST_ If the MULTICAST_NIC_IP parameter is specified in the Valid value:

NIC_IP file, the JGroup and MULTICAST Channel A host name or an
multicast sockets will bind to the NIC that you specified by using IP address
the MULTICAST_NIC_IP parameter. The value of the MULTICAST_
NIC_IP parameter can be a host name or an IP address.
MULTICAST_ Multicast port used by PPM Center's Cluster Monitor. You can Default:
PORT specify any unused port number that does not conflict with Valid values:
other multicast ports. Number for any
unused port
MULTICAST_ Specifies TTL value in all multicast channels. Default:

TTL
**MULTICAS PPM Center logs warnings in the server logs if it does not detect Default:
T_WARNING_ multicast traffic from a node after a specified time interval has Valid values:
MINUTES elapsed (even though the node can be reached on its JMS An integer value
connection factory and the PPM_SERVER_INSTANCE table greater than and
shows that the node is running). Use this parameter to less than
configure the amount of time that must pass before PPM
Center determines that a node is down. This parameter is
required if you are configuring a clustered environment.
MY_LINKS_ Maximum number of links a user can add to the My Links menu Default:
MAX_COUNT in the standard interface. Valid values:
Positive integer
**NLS_DATE_ Language used to display dates, by locale, on a multilingual PPM Valid values:
< Center system. You can specify NLS_DATE_< > Any Oracle-
> using all languages installed on a PPM Center instance. supported values
Although values are set during installation when the
administrator selects the languages to install, the


Parameter
Name
administrator can also add these values to the

file manually.
For example, if you install Korean and Brazilian Portuguese
languages after you install PPM Center, you would add the
following to the file:
and
For guidance on what values to set for this parameter, see the
(http://www.oracle.com/technology/software/index.html).
NLS_SORT_ Sort order of search results displayed on a multilingual PPM Valid values:
< Center system. You can specify NLS_SORT_< > Any Oracle-
> values for all of the languages installed on a PPM Center supported values
instance.
Although values are set during installation when the
administrator selects the languages to install, the
administrator can also add these values to the
file manually.
For example, if you install Korean and Brazilian Portuguese
languages after you install PPM Center, you would add the
following to the file:
and
For guidance on what values to set for this parameter, see the
(http://www.oracle.com/technology/software/index.html).
NLS_ Oracle defaults for a territory by Java locale. Valid values:

TERRITORY< Any Oracle-
supported values
>
NOTIFICATION Number of days that notifications remain in the system before Default:
S_CLEANUP_ the Notifications Cleanup Service removes them. Valid values:
PERIOD Integer greater
than 1


Parameter
Name
NUMBER_OF_ Number of future fiscal years that can be viewed in a financial Default:
FUTURE_ summary. Valid values:
YEARS_TO_ HP Time Management uses this value to determine the latest Integer between 0
SHOW_ON_ future fiscal year that users can specify in the Fiscal Year and and 20
FINANCIAL_ Data Range fields on a financial summary.
SUMMARY
Note: This parameter is also applied to snapshots of
financial summaries, but is applied relative to the fiscal
year each snapshot was taken, and not relative to the
current fiscal year.
NUMBER_OF_ Number of past fiscal years that can be viewed in a financial Default:
PAST_ summary.
Valid values:
YEARS_TO_
HP Time Management uses this value to determine the earliest Integer between 0
SHOW_ON_
previous fiscal year that users can specify in the Fiscal Year and 20
FINANCIAL_
and Data Range fields on a financial summary.
SUMMARY
Note: This parameter is also applied to snapshots of

financial summaries, but is applied relative to the fiscal
year each snapshot was taken, and not relative to the
current fiscal year.
ONLINE_ Enable or disable the attachment of Universal CMDB Impact Default:

IMPACT_ Analysis Reports for CIs in PDF format to requests in PPM
Valid values:
ANALYSIS_ Center.
REPORT
OPTIMIZATIO Number of algorithmic iterations that the optimization engine Default:

N_ is to run. The more iterations, the more time is given to finding (iterations)
ITERATION_ an optimal portfolio. Although the default is adequate in most
MULTIPLIER instances, complex cases can benefit from more iterations.
Note: This parameter also affects generation of the

Efficient Frontier curve.
OPTIMIZER_ Maximum number of periods the optimizer can shift start dates Default:
NUMBER_OF_ forward. This does not affect manually-shifted Portfolio (months)


Parameter
Name
TIMESHIFTS Management entities.
If you allow a new start date for a project, the optimizer can
start the project any time between the original start date and
six months beyond that date.
**ORACLE_ Determines whether PPM Center is to be integrated with Oracle Default:

APPS_ Apps.
Valid values:
ENABLED
You must set this parameter to for installations using
Deployment Management to integrate with Oracle Apps
through Object Migrator or GL Migrator. If you use Object
Migrator with PPM Center, you must specify a value.
ORACLE_ Version of Oracle Apps used. Default:

APPS_
For releases R11, R11i, and R12, specify R11. Valid values:
VERSION
for any Oracle
Apps release 11 or
later
ORACLE_DB_ The server sets this read-only parameter value during startup. Example
VERSION
Valid values:
Any supported
Oracle database
software version
*ORACLE_ Full path to the Oracle home directory on the PPM Server. Example
HOME
The directory must contain
the correct TNS names (or a file containing the names such as
) required to connect to the PPM Center
database schema.
PACKAGE_ Directory to which PPM Center writes package output. Default:

LOG_DIR Same default value
In a server cluster, if you have overridden the default value for
as the BASE_LOG_
this parameter to refer to a different directory, then all servers
DIR parameter
in the cluster must be able to access and share the directory.
PACKAGE_ Extension used for package log files. Default:


Parameter
Name
LOG_EXT
PACKAGE_ Prefix used for package log file names. Default:

LOG_HEADER
PAGE_PDF_ To disable the Export to PDF feature, add this parameter to the Default: N/A
EXPORT_ file, and set its value to
Valid values:
DISABLED
PARTITION_ Logical group name assigned to a cluster of Tomcat application Default: N/A
NAME servers. Any node in the server cluster that is started with the
same partition name becomes part of the cluster.
The value for this parameter is set during installation. The

startup script pulls the specified partition name from the
file and uses it to start the PPM Server.
*PASSWORD_ Expiration period of passwords for new users. Default:

EXPIRATION_ (days)
A value of 0 indicates no expiration.
DAYS
Valid values:
0 through 366
*PASSWORD_ Number of days to restrict the reuse of an old password from Default:
REUSE_ the last date the password changed.
Valid values:
RESTRICTIO
A value of 0 indicates no restriction. 0 through 2192
N_DAYS
PDF_FONT_ Absolute file path to the font used in exporting work plans in Default: N/A
FILE PDF file format.
Valid values:
PENDING_ Size of the thread pool for the Request Status Change service. Default:
STATUS_
Valid values:
CHANGE_
SERVICE_
POOL_SIZE
PLUGINS Semicolon-separated list of plugins used by the PPM Server. Default: N/A


Parameter
Name
*PM_CAN_ If set to enables the user to change the mode on Project Default:
ROLLUP_ Management's Enter Actuals page. The resulting options are
Valid values:
ACTUALS_ either rollups calculated during save processing, or rollups are
ON_SAVE deferred (and rolled up using the associated service).
*PM_NUM_ Maximum number of assignments that can be displayed for Default:

EDIT_ editing on the Enter Actuals page in Project Management.
ASGMTS
PORTFOLIO_ License key required to use Portfolio Management. This key is Default: N/A
MANAGEMEN available in the Autopass license key file.
T_LICENSE_
KEY
PORTLET_ Amount of time (in seconds) a portlet's SQL statement is to run Default:
EXEC_ before it is automatically disconnected from the database. (seconds)
TIMEOUT
This parameter is used to limit long-running queries in portlets,
which may be caused by adding portlets without filtering
criteria. Used to avoid excessive database CPU processing when
users end their sessions before processing has completed.
Note: Increase the value of only

as a last resort. This setting has system-wide performance
impact. If you must increase the value, specify a value such
as 30, and not a high value such as 200.
PORTLET_ Maximum number of rows to display in portlets. Default:

MAX_ROWS_
RETURNED
PORTLET_ If the parameter is set to Default: 10000

MONITOR_ then this parameter determines the portlet load time threshold (milliseconds)
THRESHOLD (in milliseconds) above which the portlet monitor logs portlet
load information.
PROJ_COST_ Determines the maximum duration of a project (based on start Default:

ROLL_UP_ and finish dates of root task in the assigned work plan), on (days)
DURATION_ which cost roll-up calculations are performed. The default is
IN_DAYS optimized for performance.


Parameter
Name
PV_USE_ If set to true, enables users to use the Planned Value (PV) Default:
ACTIVE_ calculation algorithm, which uses projects' active baseline
Valid values:
BASELINE_ dates instead of their scheduled dates.
DATES
When the Project Planned Value Update service runs, and the
flag is set to PPM
Center checks for and uses active baseline dates instead of
scheduled dates for planned value calculations on all projects.
The PV calculation formula is:
Where
When the Project Planned Value Update service runs the first
time after this flag is turned on, projects with scheduled dates
and active baseline dates that are past are added to the queue
for PV recalculation.
*QUARTZ_ Number of threads to be invoked per PPM Server node to send Default:

WORKER_ messages.
Valid values:
THREADS
Integer greater
than zero
REMOTE_ Determines whether user authentication is required for remote Default:

ADMIN_ administration of the PPM Center instance.
Valid values:
REQUIRE_
If set to users running to shut down the
AUTH
PPM Server must supply a valid PPM Center user name and
password.
If set to any user with access to can shut

down the server.
REPORT_DIR If you want report output to be written to a location other than Example
the default directory (outside of the PPM Server directory
structure), use this parameter to specify a different directory.
Make sure that the PPM Server has access to the directory so
that the report output HTML files can be written here.


Parameter
Name
REPORT_ Directory in which the PPM Center report logs are stored. Same default value
LOG_DIR as the BASE_LOG_
Note: In a server cluster, if you have overridden the default DIR parameter
value for this parameter to refer to a different directory,
Example
then all nodes in the cluster must be able to access and
share the directory.
REPORTING_ If Operational Reporting is deployed on your system, this is the Example

BASE_URL base URL for your BusinessObjects server.
REPORTING_ If Operational Reporting is deployed on your system, this is the NA

JDBC_URL locator for the database that contains the Operational
Reporting database schema.

DB_ username for the Operational Reporting database schema.
USERNAME

DB_ password for the Operational Reporting database schema.
PASSWORD
REPORTING_ Frequency with which report status is refreshed and displayed Default:
STATUS_ to the user.
(seconds)
REFRESH_
RATE
REQUEST_ Setting the parameter value to false disables the PPM Center Default value:
LINK_ALM_ defect workflow driven synchronization between PPM Center
ENTITY_ request status and ALM entity status. The default value is .
Valid values:
STATUS
,
REQUEST_ Location for Request execution log output. (Logs directory Example
LOG_DIR directly under the directory specified by the BASE_PATH
parameter.)


Parameter
Name
Note: In a server cluster, if you have overridden the default

value for this parameter to refer to a different directory,
then all nodes in the cluster must be able to access and
share the directory.
REQUEST_ Determines the stale check timeout frequency for the cache Default: 3600
TYPE_ that holds mapping between parameter and tokens for (seconds)
CACHE_ Request Type and Request Header Type.
TIMEOUT
Note: Do not change the value of this parameter.
REQUEST_ Maximum number of results returned by a search. The value is Default:

SEARCH_ displayed as the default in the Limit Rows Returned To field.
RESULTS_
You can increase or lower the value to meet your needs.
MAX_ROWS
If you want to restrict the maximum number of records
returned for the current search only, you can change the value
in the Limit Rows Returned To field directly.
REQUEST_ Flags whether or not to show total number of records for the Default value:
SEARCH_ request search results pages. The default value is for
RESULTS_ better system performance.
Valid values:
SHOW_
,
TOTAL_
NUMBER_OF_
RECORDS
REQUEST_ Stale check timeout for the cache that maintains mappings Default:
TYPE_ between parameters and tokens for Request Type and Request (seconds)
CACHE_ Header Type.
TIMEOUT
Note: HP strongly recommends that you not change the
value of this parameter.
RESOURCE_ Value used to calculate the suitability score for items returned Default:
FINDER_ on the Resource Finder results page.
Valid values:
ROLE_
through


Parameter
Name
WEIGHT
RESOURCE_ Maximum number of resources that can be targeted in a user Default:

FINDER_ search. If the targeted number exceeds this value, the
SEARCH_ Resource Finder displays the message that the number of
MAX_USERS resources targeted is too large.
RESOURCE_ Value used to calculate the suitability score for items returned Default:
FINDER_ on the resource finder results page.
Valid values:
SKILL_
through
WEIGHT
RESTRICT_ Determines whether only managers can bypass execution of Default:

BYPASS_ workflow steps in packages.
EXECUTION_
If set to only users with an access grant of Package Valid values:
TO_
Manager or Request Manager access can bypass executions.
MANAGERS
If set to all users eligible to act on executions can
bypass them.
RESTRICT_ Restricts bypass execution to request managers. If set to Default:

BYPASS_ only a user with the Manage Request access grant can
Valid values:
REQ_EXEC_ bypass an execution step on a request.
TO_
MANAGERS
RM_ Determines the effort types allowed for Resource Management Default:
ALLOWED_ staffing profile and other modules. You can specify a
EFFORT_ combination of up to three comma-delimited values.
TYPES Valid values:
Examples
l
l
l
l
The order does not matter.


Parameter
Name
*RM_ Effort type used to display staffing profiles and resource pool Default:
DEFAULT_ information.
Valid values:
EFFORT_
TYPE
*RM_ Default period type used to display staffing profiles and Default:
DEFAULT_ resource pool information.
Valid values:
PERIOD_TYPE
*RM_MAX_ Maximum number of resources in a resource pool. If the Default:

RESOURCE_ number of resources exceeds this value, some features are
IN_POOL unavailable on the Resource Pool overview page.
The View Resource Load button is not available if the number

of resources in that resource pool (or its hierarchy if the
"Include children resource pools when calculating load for this
resource pool" flag is selected) exceeds the value set for this
parameter.
The View Forecasted Demand and Manage Pool Capacity

button are also unavailable if the number of resources in the
resource pool exceeds the default. However, you can still use
the Resource page Manage Participation feature to add or
remove resources.
Values greater than the default (250) may increase response

times and memory footprint when the above operations are
performed.
RM_ If set to , this parameter turns off security during Default:

OVERRIDE_ allocation of a resource to a staffing profile or during
Valid values:
ASSIGNMEN assignment of a resource to a work plan. Any user with
T_CONTROLS “Edit/View Staffing Profiles” or “Edit/View All Staffing Profiles”
access grant can then directly perform the following actions:
l Assign any resource (in a resource pool) to the staffing

profile or the work plan, or to both.


Parameter
Name
l Reject unmet resource demand for one or more staffing

profile lines.
l Forward unmet resource demand for one or more staffing

profile lines to a different resource pool.
The user can also use the resource finder to locate and assign
resources in all resource pools.
*RMI_URL Port on which the PPM Server listens to initiate RMI Default:

client/server communication.
Valid values:
Must be a unique port, distinct from the Web server, SQL*Net, Port numbers
and the HTTP or HTTPS ports. higher than 1024
Format: Example
Note: If you want to specify a literal IPv6 address, make

sure you enclose the literal address with " " and " "
characters. For example,

RMI_ Used if PPM Server is running in secure RMI mode. Default:

VALIDATE_
If set to the client PPM Workbench validates the server Valid values:
SERVER_
certificate against the Certificate Authorizer's to verify server
CERTIFICATE
identity. If set to the certificate is not validated.
*RML_ Password for the Oracle schema name specified for *RML_ Valid values:
PASSWORD USERNAME Encrypted
password in the
Note: You must use to encrypt the format
password. For information on how to run the
script, see "kEncrypt.sh" on page 523.
*RML_ Oracle schema name for the meta layer schema. Valid values:


Parameter
Name
USERNAME Must be the same as the database schema name used during Any user name
installation. format that Oracle
supports
RMO_ The maximum number of concurrent threads for the feature Default:
OPTIMIZE_ Resource Management Optimization supported by the system .
Valid Values:
CONCURREN
For example, if the value of this parameter is set to , it means Positive integer
T_
only one user is allowed to use the feature at a time.
THRESHOLD
RMO_ The maximum amount of data to be handled by the feature Default:

OPTIMIZE_ Resource Management Optimization.
AMOUNT_
The amount of the data for calculation = (number of positions) (100 positions, 100
THRESHOLD
x (number of resources in the specified resource pool) x resources, 3 years)
(number of days)
Valid Values:
Positive integer
RMO_OPT_ The timeout (in milliseconds) of the feature Resource Default:

CONCURREN Management Optimization.
Valid Values:
T_TIMEOUT
Positive integer
SCHEME_ If set to , enables the SchemeBasedRedirectFilter filter. Default:

BASED_
The SchemeBasedRedirectFilter generates a correct redirect Valid values:
REDIRECT_
URL by adding the BASE_URL value as prefix to the redirect URL,
FILTER_
such that every redirect URL starts with scheme
ENABLED
(http/https) and the same base URL, and then sends to the
correct target.
If the parameter is not present in , the system

would treat it as a condition by default.
If you do not use https or reverse proxy, you can disable the
SchemeBasedRedirectFilter by setting the parameter to .
SCPCLIENT_ Amount of time after which SCP clients must provide feedback Default:
TIMEOUT after a file transfer has initiated, else a timeout occurs. (milliseconds)
Set to the maximum expected time for file transfer.


Parameter
Name
SDI_LOG_ Level of detail included in Service Desk Integration (SDI) error Valid values:
SEVERITY logs. To log only errors, specify the value 0. To log both errors and
and information, specify the value 1.
SDI_ Frequency (in seconds) with which the SDI service is run. Default:
SERVICE_ (seconds)
INTERVAL
SEARCH_ Number of seconds after which searches time out. Default:

TIMEOUT
Used to limit long-running queries in searches, which may be (seconds)
caused by submitting a search without specifying selective
data. Avoids taking up database CPU if a user ends a session
before the search is completed.
SEARCH_ Setting this parameter to true, you can find all request types Default:
ALL_ listed in the Request Type auto-complete list on the Search
Valid values:
REQUEST_ Request page. However, you are still not able to see the
TYPE requests that you have no access to.
SECURE_RMI If set to enables encryption of RMI network traffic Default:

between PPM Workbench clients and the PPM Server.
Valid values:
SERVER_ Name of the PPM Center environment that contains Default:

ENV_NAME information about the PPM Server machine (for example, host
name, user name, and password).
Must be set before PPM Center entity migrators or commands

involving secure copy can run.
SERVER_ Country code for the default regional settings. Default:

LOCALE_ Valid values:
Add this parameter to the file manually and set a
COUNTRY_ Two-letter
country code value to specify the default regional settings. The
CODE abbreviation of a
default value is . Valid values are any two-letter
country in
abbreviation of a country in uppercase. For example, if you
uppercase.
want to set the default regional settings to United States, set
Example, .
this parameter value to .
This parameter works together with SERVER_LOCALE_

LANGUAGE_CODE to ensure that PPM Center groups all PPM


Parameter
Name
Center users and non-PPM Center users together when sending

notifications.
SERVER_ Language code for the default display language. Default:

LOCALE_ Valid values:
Add this parameter to the file manually and set a
LANGUAGE_ Two-letter
language code value to specify the default display language.
CODE abbreviation of a
The default value is . Valid values are any two-letter
language in
abbreviation of a language in lowercase. For example, if you
lowercase.
want to set the default display language to English, set the
Example, .
server configuration
parameter to .
This parameter works together with SERVER_LOCALE_

COUNTRY_CODE to ensure that PPM Center groups all PPM
Center users and non-PPM Center users together when sending
notifications.
SERVER_ For HP internal use only. Do not change its value unless directed Default: N/A
MAX_PERM_ to do so by HP Software Support for PPM Center.
SIZE
SERVER_ Server mode to use in case you want exclusive access to a Default:
MODE running server.
Valid values:
*SERVER_ DNS name or IP address of the machine hosting the PPM Server. Default:
NAME
If you want to specify a literal IPv6 address, make sure you Valid values:
enclose the literal address with " " and " " characters. For Any valid machine
example, name

SERVER_ Operating system on which the PPM Server is installed. Valid values:

TYPE_CODE
SERVICE_ Source of the available list of services that users can associate Default:


Parameter
Name
LIST_SOURCE with a request (through Demand Management) or a project

task (through Project Management):
Valid values:
l If set to PPM Center retrieves the list of services for
requests from the integrated Universal CMDB application in
real time.
l If set to PPM Center retrieves the list of services

for requests and tasks from the PPM Server.
SERVICE_ Used for integration with Universal CMDB for service list Default:
LIST_ retrieval.
Valid values:
UCMDB_
Length of time (in seconds) that the service list remains in PPM Integer
CACHE_
Center cache before it is retrieved again.
TIMEOUT
SERVICE_ Used for integration with Universal CMDB for service list Default: N/A
LIST_ retrieval.
Example:
UCMDB_CI_
Service list mappings between PPM Center and Universal CMDB
MAPPINGS
CIs. For more information, see the
LIST_ retrieval.
Valid Values:
UCMDB_CI_
Name of the configuration item (CI) type used to store the
TYPE
service list.
Note: You must create this CI type on the Universal CMDB

server. For more information about creating a CI type, see
the documentation for Universal CMDB.
LIST_ retrieval.
Valid values:
UCMDB_WS_
Maximum number of Universal CMDB configuration items (CIs) Integer
MAX_CI_
allowed in the service list.
NUMBER


Parameter
Name
SERVICE_ A group of PPM Center users that no users in the system Default: N/A
PROVIDER_ outside of this group can modify. This prevents these users
SECURITY_ from being locked out of the system and ensures that they
GROUP always maintain a specific set of access rights.
For HP internal use only. Do not change its value unless directed
to do so by HP Software Support for PPM Center.
SERVICE_ Determines the number of the most recent service runs to be Default:
RECORDS_ retained.
Valid values:
RETAIN_
Integer
COUNT
SERVICES_ Services, if any, run on a node in a server cluster. This Default:

ENABLED parameter is set for every server in a cluster.
Valid values:
Valid values are:
l - This node does not process light or heavy services.
l - This node only processes light services
l - This node only processes heavy services
l - This node processes all (light and heavy) service

types
For a description of PPM Center background services and

instructions on how to configure them, see "PPM Center
Background Services" on page 274.
SHOW_BASE_ Determines whether the URL for the PPM Center logon window Default:
URL_ON_ is displayed at the top of each email notification.
Valid values:
NOTIFICATION
S
SHOW_ If set to , allows user access to the debugging console and Default:
DEBUGGING_ sets the server logging threshold on a per-user basis.
Valid values:
CONSOLE_
Note: The value is case-sensitive.
PER_USER
(case-sensitive)
SHOW_ If set to enables the display (and logging) of all PPM Default:


Parameter
Name
PARAMETER Center server configuration parameters used during startup. Valid values:
S_AT_
STARTUP
SHOW_ If set to Personalize Dashboard is the first PPM Default:

PERSONALIZ Dashboard menu item listed on the menu bar.
Valid values:
E_FIRST
SINGLE_ In single sign-on configuration, this parameter is used to Example

SIGN_ON_ specify the SSO method. You must manually add this parameter
PLUGIN to the file. For more information, see
"Implementing User Authentication" on page 203.
SKIP_CHECK_ If set to the import utility skips the check for required Default:
REQUIRED_ fields during project creation.
Valid values:
FIELD_
WHEN_
IMPORT_
PROJECT
SM_RFC_ Enables the integration of PPM Center tasks and Service Default:
INTEGRATIO Manager requests for change (RFCs).
Valid values:
N_ENABLED
SM_ Password that PPM Center uses to access Service Manager. You Default: N/A
PASSWORD must encrypt this password by using the script,
which is located in the bin directory of the PPM Server. Then
remove #!# from the beginning and the end of the encrypted
password.
Note: For information on how to run the

SM_URL Host name or IP address of Service Manager. Default: N/A
Example:


Parameter
Name
SM_ User name that PPM Center uses to access Service Manager. Default: N/A
USERNAME
This user name must include only single-byte characters. Example:
SM_WEB_ Address of Service Manager Web tier. Example:

URL
SMTP_ADD_ Enables an SMTP client to prepend a dot to each line in the body Default:
PERIOD of an email message.
Valid values:
SMTP_AUTH_ Encrypted password of SMTP authentication. Default: N/A

PASSWORD
Note: You must use to encrypt the password. Valid values:
For information on how to run the script, see Encrypted
"kEncrypt.sh" on page 523.. password in the
format
SMTP_AUTH_ Username of SMTP authentication. Default: N/A

USERNAME
SMTP_PORT Port used to connect to the SMTP server when sending Default:
notifications. if SMTP_USE_
SSL is ;
if SMTP_USE_
SSL is .
Valid values:
Any available port
number.
SMTP_RFC_ If set to formats PPM Center email notifications with Default:

COMPLIANCE line-feed <LF> and carriage-return <CR> characters


Parameter
Name
appropriate for restrictive Global 9 security SMTP servers. Valid values:
**SMTP_ Host name of the SMTP-compliant mail server that acts as the Example
SERVER gateway for email notifications.
Required if
notifications
are used
SMTP_USE_ Specifies whether or not to connect to SMTP server using SSL. Default:
SSL Valid values:
Note: SSL is not used by default.
,
SMTP_USE_ Specifies whether or not to connect to SMTP server using Default:

STARTTLS STARTTLS. Valid values:
,
Note: STARTTLS is not the same as SSL. By default,
STARTTLS is not used.
SMTP_ If set to , and if a Windows SMTP server is detected, PPM Default:

WINDOWS_ Center appends a period ( ) to email notifications.
Valid values:
ADD_PERIOD
SOCKS_ Host name of the SOCKS proxy server. Host name of the
PROXY_HOST SOCKS proxy server
SOCKS_ Port on the SOCKS proxy host that accepts proxy connections. Any available port
PROXY_PORT on the SOCKS proxy
host
*SQLPLUS Name of the command-line SQL*Plus executable, which must be Default:

in the directory.
SQLPLUS_ SQL*Plus version and operating system that use the command Default: N/A
CMDLINE_ line to pass arguments.
Example:
HANDLER
SQLPLUS_ Specifies the SQL*Plus escape character. Default: (none)

ESCAPE_
CHARACTER


Parameter
Name
**SQLPLUS_ Oracle SQL*Plus version installed on the machine that hosts the Example
VERSION PPM Server. You must set this for some PPM Center reports
that run from command-line SQL*Plus calls.
If you encounter problems running PL/SQL-based reports in

PPM Center, set this parameter.
SSH2_JSCH_ If set to , the SSH2 client will connect to the remote host Default:
DISABLE_ even when its key is not in the list of the trusted hosts (
Valid values:
STRICT_ file).
HOST_KEY_
CHECKING Caution: This parameter should not be set to true on a
production environment.
SSH2_JSCH_ When a value is defined in this parameter (valid file path), PPM Default: N/A
KNOWN_ Center will use it as file to validate keys of
HOSTS_FILE_ trusted hosts it connects to.
PATH
The remote servers you will connect to should be included in
the file (using OpenSSH format), otherwise the
client cannot connect to them (unless the
parameter is set to
, in which case PPM Center does not search for a
file).
If this parameter is left empty, PPM Center first checks if there

is a file to use. If no, PPM Center
then checks known standard locations for file:
l and
under UNIX
l and
under Windows
Note: When a Linux user connects to a remote server using

the command on the command line and then accepts
the host key when prompted, this remote machine key will


Parameter
Name
be automatically added to the trusted hosts list in

.
SYNC_EXEC_ Amount of time after which the intermediate Request Working Default:
INIT_WAIT_ page opens. For more information, see the
(seconds)
TIME
SYNC_EXEC_ Maximum number of times to poll for completion of a request Default:

MAX_POLL_ before a final message is sent to the user.
TRIES
For more information, see the
SYNC_EXEC_ Time interval (in minutes) at which to poll for completion of a Default:
POLL_ request after the intermediate Request Working page opens.
INTERVAL
SYNCH_PFM_ Determines how often (in seconds) the Synch PFM Project Default:
PROJECT_ Health service runs. (seconds)
HEALTH_
Valid values: N/A
INTERVAL
THREAD_ Maximum number of packages to run simultaneously within a Default:

POOL_MAX_ release distribution.
THREADS
If a large number of packages in a distribution are processing,
increasing this value can improve performance.
THREAD_ Minimum number of packages to be run simultaneously within Default:

POOL_MIN_ a release distribution.
THREADS
See also THREAD_POOL_MAX_THREADS.
**TIME_ZONE Used to set the time zone of the Oracle database. Leave the Default: Time zone
parameter blank if the PPM Server and the Oracle database in which the
Required if
host are in the same time zone. If they are in different time PPM Server is
the
zones, set this to the time zone of the Oracle database host. running
PPM Server
and the Use a "standard" time zone setting, and not a daylight savings Valid values: Any
Oracle setting (such as EDT or PDT). You can use a fully-qualified time


Parameter
Name
database are zone name (you are not restricted to three digits), such as fully-qualified time
in different "America/Los_Angeles" or "Australia/LHI". For a list of fully- zone designation
time zones qualified names, run the Client Time Zone Report in the Admin such as
Tools window of the PPM Workbench. "America/Los_
Angeles" or
For details on how to run the report, see "Running Server
"Australia/LHI".
Reports from the Admin Tools Window" on page 327.
Do not use daylight
If you do not a specify a value for this parameter, the value
savings-modified
defaults to the time zone in which the PPM Server is running.
time zones such as
"EDT" or "PDT".
TM_DISABLE_ If set to disables the option for users to include (copy) Default:
INCLUDING_ items from a time sheet for the most recent previous period
Valid values:
LAST_TS_ when they create a new time sheet.
ITEMS
If set to enables the option.
HP recommends setting this parameter to
TM_ If set to enables the width allotted to the Item column Default:
DYNAMIC_ on each time sheet to vary as items are added or removed,
Valid values:
DESC_CHARS according to the number of characters in the longest work item
data in all the rows on the time sheet. The maximum width of
the column is determined by the TM_DYNAMIC_DESC_CHARS_
MAX parameter.
TM_ If the parameter is set to this Default: 80

DYNAMIC_ parameter determines the maximum width (in number of
Valid values:
DESC_ characters) of the Item column on time sheets. The allotted
Integer
CHARS_MAX column width is calculated from this number as an
approximation, and the data for particular items might be
truncated. If this is an issue, you can increase the value of this
parameter.
Note: HP recommends that you use the default value of 80

characters.
TM_ENABLE_ If set to enables users to vertically resize Time Default:

GRID_ Breakdown tables on time sheets.
Valid values:


Parameter
Name
RESIZE_
CONTROL
TM_ENABLE_ Enable or disable the HP Time Management Custom Policy Default:

POLICY_ Extension.
Valid values:
EXTENSION
TM_ENABLE_ In time sheet policies, you can require users to specify activities Default:
REQ_ on time sheet lines for requests of particular request types. To
Valid values:
ACTIVITY_ enable this activity restriction based on request types, you
CONTROLS must set this parameter to (You must also select the
Use Time Management to track actuals option from the PPM
Workbench.)
TM_ENABLE_ The first time a user opens any time sheet, PPM Center displays Default:
SHOW_ a message that describes the saving of the time sheet. After
Valid values:
WHATS_NEW this, the message is not displayed to that user again for any
time sheet.
To disable the display of this message, set this parameter value

to
Note: On PPM Center instances that support multiple

languages, the message is displayed only to users who
select English at log-in.
TM_MAX_ Determines the maximum number of time periods that can be Default:
PREVIOUS_ displayed in the Previous Time Periods to Show list on the
Valid values:
TIME_ Approve Time Sheets page.
Integer
PERIODS
The default value (4) supplied is for optimal performance. If you
increase the value, search performance may suffer.
TM_MAX_ Determines the maximum number of result rows retrieved Default:

TIMESHEET_ from the database for queries from the Search Time Sheets,
Valid values:
QUERY_ Search for a Time Sheet to Freeze, Search for a Time Sheet to
Integer
RESULTS Close, and Approve Time Sheet pages.
TM_MAX_ The maximum number of time approvers of time sheet lines Default Value:
TIME_ allowed by the system before it throws warning.


Parameter
Name
APPROVER_ Valid Value: Positive

WARNING_ integer
COUNT
TM_MAX_ The maximum number of billing approvers of time sheets Default Value:
BILLING_ allowed by the system before it throws warning.
APPROVER_
Valid Value: Positive
WARNING_
integer
COUNT
TM_MAX_ The maximum number of time approvers of time sheet lines Default Value:
TIME_ allowed by the system before it throws error.
APPROVER_
ERROR_
integer
COUNT
TM_MAX_ The maximum number of billing approvers of time sheets Default Value:
BILLING_ allowed by the system before it throws error.
APPROVER_
ERROR_
integer
COUNT
TM_ Specifies the amount of the Reevaluate Time Sheet Default

REEVALUAT information handled by the Evaluate TM Approvers service. Value:
E_COUNT
TMG_ Stores the reference code for the HP Time Management Default: N/A
CONFIGURAB request type to use to override the default request type used in
Valid values:
LE_FILTERS_ the Add Work Item to Timesheet window.
Reference code of
REF_CODE
the request type
TMG_ Specifies the number future periods for which users can specify Default:
FUTURE_ time on time sheets.
PERIODS_
TO_ALLOW
TMG_PAST_ Specifies the number of previous periods for which users can Default:
PERIODS_ specify time.
TO_ALLOW


Parameter
Name
TMPM_ Determined the frequency (in milliseconds) with which the TM- Default: 10800000
SYNC_ PM Sync Service runs. (in ms)
SERVICE_
INTERVAL Note: HP strongly recommends that you keep the default
value (equal to three hours).
TRANSFER_ Specifies the default temporary directory that PPM Center Example
PATH uses. The main purpose of this directory is to temporarily hold
files as they are migrated from a source environment to a
destination environment with Deployment Management.

TZ_IS_TIME_ Default:
ZONE_
DEFAULTED
TURN_ON_ If set to enables the Watchdog tool. Default:

CONCURREN
Valid values:
T_REQUEST_
WATCH_DOG
UCMDB_ Used for integration with Universal CMDB for CI selection. Valid values:
GATEWAY_
Web location of the Probe Gateway component of the Discovery
URL
and Dependency Mapping (DDM) Probe. The Probe Gateway
provides communication (HTTP or HTTPS) between the Probe
Manager and the Universal CMDB server for processes such as
downloading tasks and returning task results.
UCMDB_ Used for integration with Universal CMDB for CI selection. Default:
MAX_CI_
Maximum number of configuration items (CIs) to display on the Valid values:
NUMBER
Universal CMDB section of the request details page. For more Integer between 1
information, see the and 100
Note: If you specify

a value greater


Parameter
Name
than 100, the

Universal CMDB
server does not
restart, and
instead displays an
error message.
UCMDB_ Encrypted password for the Universal CMDB user. For more Valid values:
PASSWORD information, see the Encrypted
password in the
Note: You must use to encrypt the format
UCMDB_ URL of the Universal CMDB server. Default: N/A

SERVER_URL
or
where represents the machine on which

Universal CMDB is running.
Note: If the Universal CMDB server is configured to support

HTTPS, make sure that you configure the
parameter.
UCMDB_SSL_ Used for integration with Universal CMDB for CI selection or Default: N/A
KEYSTORE_ service list retrieval.
Example:
PATH
SSL keystore path. Required only if UCMDB_SERVER_URL
parameter uses
UCMDB_ Used for integration with Universal CMDB for CI selection. Default: N/A
USER
Universal CMDB user name for the integration. For more Example:


Parameter
Name
information, see the
UCMDB_WS_ Determines the maximum number of connections to the Default: 10

MAX_ Universal CMDB server through the Web Service API.
CONNECTIO
N_NUMBER
UCMDB_WS_ Universal CMDB user password for logging in through Web Default: N/A
PASSWORD service.
Valid values:
Encrypted
Note: You must use to encrypt the
password in the
format
UCMDB_WS_ Used for integration with Universal CMDB for service list Default: N/A
USER retrieval.
Example:
Universal CMDB user name for logging in through Web service.
UI_ If ENABLE_UI_MONITOR is set to this parameter Default:

MONITOR_ determines the time threshold value of the activity monitor. (milliseconds)
THRESHOLD
Valid values:
Integer greater
than 0
USE_ If set to enables the HTTPOnly flag for selected cookies Default:
HTTPONLY used by the PPM Server.
Valid values:
USE_ Flags whether or not to check notification recipient regional Default:

SERVER_ settings. Setting the value to ignores users' regional
Valid values:
LOCALE_ settings when sending email notifications, and uses the values
FOR_ of server configuration parameters SERVER_LOCALE_
NOTIFICATION COUNTRY_CODE and SERVER_LOCALE_LANGUAGE_CODE
S instead. This ensures that recipients are not split into different
groups according to their regional settings.
USER_ Maximum number of characters in user passwords. Default:

PASSWORD_


Parameter
Name
MAX_LENGTH
USER_ Minimum number of digits in user passwords. Default:

PASSWORD_
MIN_DIGITS
USER_ Minimum number of characters in a user password. Default:

PASSWORD_
MIN_LENGTH
USER_ Determines the minimum number of non-alphanumeric Default:

PASSWORD_ characters that user passwords must contain.
MIN_SPECIAL
VALIDATION_ In a server cluster, if you have overridden the default value for Same default value
LOG_DIR this parameters to refer to a different directory, then all as the BASE_LOG_
servers in the cluster must be able to access and share the DIR parameter
directory.
Example
VISUALIZATIO Length of time (in seconds) that resource management Default:

N_EXEC_ visualizations can run before they time out.
TIMEOUT
**WEB_ Specifies web cache directory. Example:

CACHE_DIR
Add this parameter to the file if it is not there
and make sure to use a shared folder in clustered configuration
so that whenever a chart in portlet is loaded by PPM Dashboard,
it creates charts pictures into this shared folder. Then, the
Directory Cleanup Service can automatically clean up the older
pictures files. or
Required only if all the nodes of the cluster are not located on
the same physical machine AND in the same
folder.
WF_DISABLE_ By adding this parameter to the file and setting it Default:


Parameter
Name
DELEGATE_ to , you can hide the Delegate Decision button for Valid values:
DECISION_ workflow steps where the Decision Required option is set to At ,
STEP Least One or All. If this parameter is not set or set to ,
the Delegate Decision button will be displayed.
WF_ Frequency with which the PPM Server checks for pending Default:
SCHEDULED_ scheduled tasks, and starts the tasks if worker threads are (seconds)
TASK_ available.
INTERVAL
WF_ Determines the priority of scheduled tasks. Default:

SCHEDULED_
Because scheduled tasks run in the background, it may be
TASK_
useful to run them at a lower priority than the threads servicing
PRIORITY
user-oriented interactive tasks.
WORKBENC Earliest Java plug-in version used to access the PPM Workbench Example
H_PLUGIN_ interface.
VERSION
Use this parameter to use a specific version (other than the
default version) of the Java plug-in to open the PPM
Workbench.
WORKBENC Specifies maximum available memory (in MB) for the PPM Default:
H_MAX_ Workbench.
HEAP_SIZE
WORK_PLAN_ Specifies resource availability days limit for a task, including Default:
RESOURCE_ the resource's non-working days.
Valid values: An
AVAILABILIT
A schedule warning appears if the total of the value entered in integer value
Y_DAYS_
the Scheduled Duration field and the resource's non-working greater than and
LIMIT
days is bigger than the limit you specified. less than
WS_UPDATE_ If set to lets Web services update closed and canceled Default:
CLOSED_ requests.
Valid values:
AND_
CANCELED_
REQUESTS
a. For details about this parameter, see the


Parameter
Name
b. For details about this parameter, see
Server Configuration Parameters Related to the PPM

Dashboard
The following table lists and provides descriptions of the PPM Server configuration parameters related
to the PPM Dashboard in the PPM Center standard interface. These parameters, like those listed in
"Using the Server Configuration Utility to Modify Server Configuration Parameters" on page 424, are
located in the file.
The parameter names listed in the table are shortened versions of the actual names, all of which start
with the string For example, the full name of the
parameter is .
Table A-2. PPM Dashboard-related server configuration parameters
Parameter Name Default, Valid Values,

(*Required) Description, Usage Example
Application-Server Specifies the application server for the Default:

PPM Dashboard.
BaseURL PPM Dashboard base URL. Valid values:
Same value as set for the

*BASE_URL parameter
Character-Encoding Specifies the coding to use for text Default:

displayed in the PPM Dashboard.
Chart-Width- Setting this to enables PPM Default:

Restriction-Enabled Dashboard chart portlets to maintain
Valid values:
their size, even with large numbers of
data points. A chart maintains its size as
long as the data in the chart is readable.
For very large numbers of data points,
the chart eventually grows.

Table A-2. PPM Dashboard-related server configuration parameters, continued

DSH - Center Name PPM Dashboard center name. Default: PPM Center
DSH - Org Units Supported If set to enables org units in PPM Default:
Dashboard.
Valid values:
DSH - Version Specifies the PPM Dashboard version.
Dashboard-MLU- Used with Supported-MLU-Languages, Default:

Operational determines whether MLU is enabled in
Valid values:
the PPM Dashboard.
Dashboard-Page- Auto-refresh option for the PPM Default:

Auto-Refresh-Disabled Dashboard.
Valid values:
dashboard.Asynchron Setting the value to enables Default:

ous-Loading-Enabled asynchronous rendering of the
Dashboard page.
dashboard.Pivotdata Determines the maximum number of 120,000

set-Max-Cells cells (number of rows * number columns)
in the List display mode of a pivot table
portlet.

set-Max-Distinct-Cells unique aggregations (product of
numbers of unique values in each
column) in a pivot table.
dashboard.Pivotdata Determines the maximum number of 50

set-Max-Distinct-In- unique values in any column of a pivot
Column table.

set-Max-Rows rows in the List display mode of a pivot
table portlet.
Data-Source Specifies the data source for the PPM Default:

Dashboard.
Database-Type Database used by the PPM Dashboard. Default:


Favorites-Disabled Used to turn off the PPM Dashboard Default:

Favorites option.
Valid values:
Fonts-Directory- Directory path of the fonts used by PPM Example:

Path Dashboard.
Footer Absolute URL path of the PPM Dashboard Default:

footer page.
Header Absolute URL path of the PPM Dashboard Default:

header page.
Layout-Direction PPM Dashboard layout direction in a web

browser. (Because only the
left-to-right (ltr) page layout direction is
supported, you can leave the value
unspecified.)
List-Column-Header- Number of characters displayed in the Default: 20

Size column heading of list portlets. If the
Valid values:
number of characters in a column
Positive integer
heading exceeds this value, the heading
is truncated. The default is 20
characters.
Non-SSL-Port Non-SSL port used by the PPM Default: N/A

Dashboard. In order for the PDF export
feature to work when the PPM Server is
configured to use SSL, the PPM
Dashboard must have an HTTP port that
can be accessed locally by ICE browser.
pdf-render-timeout Specifies the timeout (in seconds) for the Valid values:
export-to-PDF mechanism. This timeout Any integer
is used while calling ICEbrowser. Should
be used only for customers who cannot
export to PDF because of database
queries that return a large volume of
data.
openDataSource Open data source used by the PPM Default:


Dashboard.
PDF-URL PPM Dashboard URL for PDF files. Default: N/A
PDF-Unicode-Font- Unicode font file path used by PPM Default: N/A

File-Path Dashboard.
Page-Auto-Refresh- If set to disables the auto-refresh Default:

Disabled capability in the PPM Dashboard.
Valid values:
Page-PDF-Export-Disabled If set to removes the Export to Default:

PDF icon from the PPM Dashboard.
Valid values:
Portlet-Thread- Batch- Specifies the batch size of threads used Default:

Size to process prefetch portlets
Valid values:
simultaneously.
Any positive integer
Printout-Banner-Text Determines the text to be displayed in Valid values:

the header of printouts (for example, the
Any text string
PDF header banner). If you specify no
value, the center name is used.
SQL-Debug If set to enables SQL debugging in Default:

the PPM Dashboard.
Valid values:
Note: Unless you require detailed

PPM Dashboard debug logs for
support, keep this parameter set to
false.
Smtp-Port Specifies an SMTP port for the PPM Default: N/A

Dashboard.
Note: HP recommends that you

leave the value for this parameter
unspecified.
Smtp-Server Specifies an SMTP server for the PPM Default: N/A


Dashboard.

unspecified.
Supported-MLU- Specifies the languages supported for Default: N/A

Languages the PPM Dashboard. Use commas to
Valid values:
separate multiple values.
All languages supported by
the current PPM Center
version
Time-Zone Specifies the time zone used in the PPM Valid values:
Dashboard.

unspecified.
Use-Full-Screen- Indicates that the PPM Dashboard page Default:

Width view occupies the full width of the
Valid values:
screen.
Web-Server If the export-to-PDF functionality does Valid values:

not work and PPM Center is configured
IIS, Apache
with an IIS or Apache Web server, set this
value to try to restore the export-to-PDF
functionality.
Logging Parameters
The following table lists the PPM Server configuration parameters located in the (logging
properties) file, and provides a description of each. The file is located in the
directory.
Note: Changes to the file are picked up dynamically by the application (it takes

about one minute), so there is no need to restart the application.
The logging parameter names listed below are shortened versions of the actual names, all of which
start with the string For example, the full name of the
parameter is
Table A-3. Logging parameters

CATCH_SYSTEM_ Used to determine whether to redirect Default:

ERR to the server log.
Valid values:
CATCH_SYSTEM_ Used to determine whether to redirect Default:

OUT to the server log.
Valid values:
class.filters Specifies the class names to include in the Default:

stack trace (substring of stack trace
classname, including packages). This
parameters is used to filter out the classes in
stack traces that are of no interest to reduce
the log size.
If you specify multiple classes or packages,

use commas to separate them.
If the full class name in a stack trace

contains one of the specified classes or
package names, then that line is preserved.
For example, if the value is set to

then any class
names that contain " " or
" " are kept.
The number of traces filtered out is added to

server logs after the stack trace.The system
default is EMPTY, do not filter out any classes
in stack trace.
CLASS_LOGGING_ Overrides the logging level for a specific Java Default:

LEVEL class to enable logging of a specific piece of
code while leaving the rest of the application
at a lower logging level.

Table A-3. Logging parameters, continued

The format of this parameter is the fully-

qualified class name followed by a "," then
the level.
Caution: Use of class filtering degrades

performance.
CONF_FILE_RECHECK_ Determines the regular interval (in seconds) Default:

INTERVAL at which the file is checked (seconds)
for changes while the server is running.
context.option Number that specifies the levels to include Default:

context in exception logging, as follows:
Valid values:
l 3 includes all ,
and
l 0 include bitwise combination value in
binary (default)
l 001 Include context information, if

provided
l 010 Include stack trace for log messages

without exception
DEFAULT_SERVER_ Determines the default debug logging level Default:

LOGGING_LEVEL of the PPM Server. It controls the verbosity of
Valid values:
logs generated by the PPM Server.
l - No information,
The values, which you can set dynamically at
(including errors) is
runtime in the Workbench Server Settings
logged
window, map as follows:
l maps to None in the Server l - Only errors are

Settings window logged
l maps to Normal l - Errors and

additional information
l maps to Max is logged
For more information about the Server l - Includes

Settings window, see "Setting Debugging and verbose debugging
Tracing Parameters" on page 333. messages


l - Displays all log

messages generated
DEFAULT_USER_ Specifies the default debug level of a user's Default:

DEBUG_ client session.
Valid values:
LEVEL
Controls the verbosity of users' logs on the
l - No information,
client, application server, and database. Can
(including errors) is
be different for different client sessions, and
logged
can be changed in the standard interface as
a user preference. l - Only errors are
The values, which can also be set in the logged
Workbench Server Settings window
l - Errors and
dynamically at runtime, map as follows:
additional information
l ERROR maps to None in the Server is logged
Settings window
l - Includes
l INFO maps to Normal verbose debugging
messages
l DEBUG maps to Max
l - Displays all log
For more information about the Server messages generated
Settings window, see "Setting Debugging and
Tracing Parameters" on page 333.
DEFAULT_USER_ Specifies the default logging level for users Default:

LOGGING_LEVEL client sessions. It controls the verbosity of a
Valid values:
users logs on a client, application server, and
database. No information is
logged (even errors are
excluded)
Only errors are

logged.
Errors and
additional information are
logged.
Verbose logging of
debugging messages.


Display all log

messages being produced
ENABLE_CONSOLE_ If set to true, all logs that are written to the Default:
LOGGING file are also printed to the
Valid values:
console that started the PPM Server.
ENABLE_EXECUTION_ If set to during an execution, all logs Default:

CONSOLE_LOGGING written to the file are also
Valid values:
printed to the console that started the
server.
ENABLE_SMTP_ If set to , mail notification for specified Default:

LOGGING server logs is enabled.
Valid values:
ENABLE_WEB_ Determines whether or not information sent Default:

ACCESS_LOGGING to the internal PPM Center Web server
Valid values:
(Tomcat) is logged.
ENCODING Specifies the default character set for Default:

logged messages. This overrides the default
operating system character set.
FILE_RECHECK_ Time interval (in seconds) at which the Default:

INTERVAL file is checked for changes.
The file keeps being checked as long as the

PPM Server is running.
LOG_LAYOUT Determines the layout format of the log files. Default:
Valid values:
LOG_PATTERN Controls the formatting of the generated Default:

logs. You can use the following variables in
the log output:
l %c - Product function hierarchy of the

logged item Valid values:
See Description, Usage

l %d - Date of logging


l %m - Logging message
l %n - Line separator
l %p - Priority level for the log message
l %r - Number of milliseconds elapsed

since the application started
l %t - Thread name in which the log

message created
l %x - Username for the user who

triggered the log message
Because the following log pattern variables

can significantly slow performance, HP
recommends that you use them only during
debugging.
l %C - Fully-qualified class name of the

class creating the log message
l %F - Name of the file in which the log

message was created
l %l - Class and line number of the log

message source
l %L - Line number where the log message

was created
l %M - Method name producing the log

message
MAX_BACKUP_ Limits the number of backup logs kept in the Default:

INDEX system.
PRODUCT_FUNCTION_ Specifies the logging level for a specific Default:

LOGGING_LEVEL product function while leaving the rest of the
application at a different logging level. The
function areas are hierarchical. Valid values:
Parameter value format:


Caution: This parameter is designed for

advanced troubleshooting.
modify its value unless HP Software
Support engineers advise you to do so.
ROTATE_LOG_ As the PPM Server logs information into the Default:

SIZE file, the file can grow quite
You can specify the size in
large. This parameter determines how large
either kilobytes or
(in KB or MB) it can grow before the server
megabytes by appending
creates a new log file. When the
or to the number
file reaches the size
specified by this parameter, the PPM Server
renames it (to
), and starts a new
serverLog.txt file.
SERVER_ Debug level of the PPM Server. Valid values:

DEBUG_LEVEL
Controls the verbosity of logs generated by
independent server processes (for example,
EmailNotificationAgent).
Corresponds to the Debug Level list in the

Server section of the Server Settings page.
**SMTP.To The recipient of the notification. Default: N/A
Required if ENABLE_ Valid values: Email address

SMTP_LOGGING is set to
.
SMTP.From The sender of the notification. Default: N/A
If not specified, the email address of the Valid values: Email address
sender is derived from EMAIL_NOTIFICATION_
SENDER in the file.
SMTP.Subject The subject of the notification mail. Default: N/A
**SMTP.Filter.Reg The keyword or regular expression to be Default: N/A


exToMatch monitored. Valid values:

Regular expression
Required if ENABLE_
SMTP_LOGGING is set to For example,
.
SMTP.Filter.Level The lowest log level to be monitored. Default: N/A

Min
Valid values:
SMTP.Filter.Level The highest log level to be monitored. Default: N/A

Max
Valid values:
SMTP. The time interval (in seconds) to check Default:

delayBetween message queues.
Valid values:
ChecksInSeconds
SMTP.SMTPDe If set to , enables displaying debug Default:

bug information when mail notification is sent
Valid values:
out.
SMTP.BufferSize The buffer queue length. Default:
Valid values:
SYSTEM_ Determines the system-wide logging Default:

THRESHOLD threshold. IF statements wrapping the log
Valid values:
requests check this setting.
Caution: This parameter is designed for


advanced troubleshooting.
modify its value unless HP Software
Support engineers advise you to do so.
USER_ Used to set logging threshold for individual Default: N/A

THRESHOLD: users, as follows:
To enable the debug console for multiple

users, add on a separate
line of the file for each user.
LDAP Attribute Parameters

The following table lists and provides descriptions of the PPM Server configuration parameters in the
file, which is located in the directory. Use the
file to map the attributes of the LDAP server with the attributes used by the
PPM Server.
The default mapping uses the standard LDAP attributes. All values are case-sensitive. Do not add spaces
between tokens.
Caution: Do not map the and parameters in

. These attributes are specified in the table.
Table A-4. LDAP attribute parameters

Parameter
Name Default, Valid Values,
KNTA_USERS_ Target table for the import. Can be mapped to any LDAP Format:
INT attribute.
Always map both and
To disable default mapping:
1. Either comment out or delete the mapping line.

Table A-4. LDAP attribute parameters, continued

Parameter
Mappings:
l
l
l
l
l
l
l
l
l
l
2. Add a placeholder parameter to the

file that will add a value to the
FIRST_NAME and LAST_NAME fields.
RSC_ Target table for the import. Can be mapped to any LDAP Format:
RESOURCES_INT attribute.
Always map both and
To disable default mapping:
1. Either comment out or delete the mapping line.
Mappings:
l USERNAME = sAMAccountName
l USER_DATA1 = mail
l VISIBLE_USER_DATA1 = mail
2. Add a placeholder parameter to the

file that will add a value to the

Table A-4. LDAP attribute parameters, continued

Parameter
FIRST_NAME and LAST_NAME fields.
LDAP_TIME_ Attribute that keeps track of the time format that the Format for Active
FORMAT LDAP server uses. Directory servers:
Format for Sun Java

System Active Server
Pages LDAP server:
LDAP_USER_ Object class attribute for a user on the LDAP server. Default:
OBJECTCLASS

Appendix B: Server Directory Structure and
Server Tools
This appendix addresses the and directories and the scripts and tools they contain.
The directory (the installation directory) contains two subdirectories that relate to the Oracle
database schemas: and .
The directory (the install directory for PPM Center) holds several subdirectories
( and so on) that contain server and system information, and administrative
tools used to perform tasks such as starting, stopping, and reporting on the PPM Server or system.
ppm930/system
The directory contains the and scripts.
The script variables are:
represents the username of the new database schema.
represents the password of the new database schema
represents the tablespace used to store PPM Center tables
represents the tablespace used to store PPM Center indexes
represents temporary tablespace
represents the tablespace used to store large data (CLOB).
The script variables are:
represents the username for the new RML database schema.
represents the password for the new RML database schema
represents the tablespace used to store PPM Center

database tables
represents temporary tablespace.

Appendix B: Server Directory Structure and Server Tools
<PPM_Home>/bin
The directory contains all of the scripts required to configure and administer the
PPM Server. This section provides descriptions of these scripts.
kBuildStats.sh
In old versions of PPM Center, the script was used to instruct Oracle to gather
statistics about the PPM Center database schema.
Since Oracle offers sufficient tools to gather statistics about the database schema, this script is kept in
code, but not used anymore.
kCalculateHealth.sh
The script computes the classpath for accessing the PPM Center logging
libraries.
kCancelStop.sh
The script is used to cancel a scheduled shutdown of the running PPM Server. If a
command such as is being used to stop the server, you can run to
cancel the stop request. Authentication may be required for this, which works in the same way as for
Use the user name flag.
Example
kChangeNameDisplay.sh
The script is used to change the display format of PPM Center users' names.
Run the script as follows:
where Full_Name_Format is 0, 1, or 2.

During the script run, specify the format to use to display a user's full name, as follows:
l To use the format First Last (for example, John Smith), type 0.
l To use the format Last, First (for example, Smith, John), type 1.
l To use the format LastFirst (for example, SmithJohn), type 2.
The LastFirst format (option 2) is specifically for Korean language users.
l To cancel the operation, type .
Note: Running with no arguments defaults the full name format to 0,

where first name and last name are separated by one space.
kCharConverter.sh
The kCharConverter.sh script is used to convert the character set of a file to a different character set.
If no source encoding has been specified. he script uses the default character set of the system It will
convert it to the character set specified by destEnc.
Examples
where
represents the original character file name
represents the new file name
represents the original character set encoding for the file
represents the new character set encoding you are setting for the file
If you do not specify the source encoding, the script uses the default character set of the system and
converts that to the destination character set you specify.

kConfig.sh
The script launches the server configuration tool. Because you cannot use to
update parameters in a cluster node (that is, anything that comes after an node), HP recommends
that, for a server cluster environment, you use a text editor to edit (or add) parameter values directly in
the file, or use the Administration Console to modify parameter values. Regardless of how
you modify configuration parameters, you must run the script (see "kUpdateHtml.sh"
on page 537) afterward to implement your changes.
l On a Windows system, run the script as follows:
o To run the script in console mode:
o To run the script in graphic mode:
l On a UNIX system, run the script as follows:
o To run the script in console mode:
o To run the script in graphic mode:
Note: Starting from PPM Center version 9.20, you can no longer use this tool to migrate DMS. To
migrate your DMS, use the DMS Configuration tool from the Administration Console instead.
kConfigCheck.sh
The script performs sanity checks on a specified PPM Server instance defined in the
file. The script returns a status of either or

If you run the script without specifying a PPM Server, the script performs a sanity check on the first
node defined in the file.
If the sanity check fails, the PPM Server instance does not start up.
kConvertProject.sh
The script converts project effort data from days to hours.
kConvertToLog4j.sh
The script converts the JDBC log, Web log, or server log to the log4j XML format.
You can view logs in this format with a tool such as Chainsaw (a GUI-based log viewer available at the
Web site logging.apache.org/log4j/docs/chainsaw.html).
Examples
To convert a Web log to the log4j XML format.
To convert a JDBC log to the log4j XML format.
To convert a file in text format to the log4j XML format.
To convert a server log, JDBC log, and Web log, and then concatenate them in a result log.
For information about usage type.
where
represents the server log to be converted
represents the jdbc log to be converted
represents the Web log to be converted
represents the name of the result log
represents the format of date for the Web log

Example
represents a regular expression to match the date in the Web log
represents the date format for the server log
Example
represents a regular expression to match the date in the server log
Determines whether the existing merged log is appended. The default is
represents a message to display
kConvertUserPasswords.sh
The script is used to convert the user password storage algorithm
between a one-way hash and a reversible encryption scheme. Converting to the hashing algorithm
ensures the security of your saved user passwords, but disables the [USR.PASSWORD] token in any
commands, notifications, and so on where it is used. The standard encryption option (the default) saves
passwords securely encrypted with the El Gamal public/private key algorithm, which enables the server
to decrypt the passwords for uses such as the [USR.PASSWORD] token.
kDeploy.sh
The script is used to install Deployment Management Extensions, PPM Center Best
Practices, language packs, hot fixes, and PPM Center product service packs. This software is distributed
as a deployment (a software bundle that contains files) in the following format:
where
represents the PPM Center version for which you can install the Extension, Best
Practices, or service pack
represents the unique identifier for service pack
(Optional) represents the revision number for the deployment.
Example

To install a product service pack SP1:
1. Make sure that the deployment JAR file is in the directory.
Note: There is no need to extract anything. The script does that for you.
2. To apply the SP1 service pack, run the command:
The following table displays the key command-line options for To generate a list of
options, run the command
Table B-1. Key command-line options for kDeploy.sh
Option Description
-i Installs deployments.
Example
To install a PPM Center service pack (SP) 14, run the command:
-l Lists the deployments installed on an instance.
-D Searches for bundles in a given directory.
Example
To search for a file in the directory, run the command:
-h Provides help for Lists all the command-line options.
-hotfix Deploys hotfixes.
-f Reinstalls an existing deployment.
-lang Installs a language pack after PPM Center installation or upgrade. For information about
how to install a language pack, see the
-k Includes the PPM Center database schema password in the command. Automates
command execution but may be a security risk.
-u Includes the PPM Center user name in the command.
-p Includes the password for the PPM Center user name in the command. Automates

Table B-1. Key command-line options for kDeploy.sh, continued

Option Description
command execution but may be a security risk.
-tidy Cleans up unnecessary deployment files.
-skip - Specifies that database changes are not to be applied if they already exist.
database
-update- Extracts the new file, if a new version exists.

deploy
The script performs conflict check before installing a hotfix:
l If the hotfix files do not exist on the current instance, running the deployment command
successfully installs the hotfix.
l If the hotfix is checked to be conflicting with some files on the current instance, the installation
would fail.
To address the conflict issue and to continue the installation, you can contact HP Software Support
who would provide a file that contains the latest MD5 code. You can then run the following
command:
If you encounter further conflict issues when running this deployment command, contact HP
Software Support for solutions.
After the hotfix is deployed successfully, the tool continues to verify whether or not the
hotfix is deployed correctly.
Deploying Hotfixes with kDeploy.sh

To deploy a hotfix, run the following command:
where is the hotfix bundle name.
For example, if the bundle name is then the corresponding deployment

command is as follows:
Viewing hotfix deployment information

To view the hotfix deployment information after you run
1. Navigate to and open the file.
2. Click the Patches Information link.
The file opens and displays the following information:
o Version of PPM Center instance
o Service packs applied in current PPM Center version
o All files in the PPM Center file system
o Additional files applied in the current PPM Center instance, including SQL files and imported
entities (packages, request types, requests, and so on)
o Service packs deployed in your current PPM Center version
3. Check the details in the section(s) of interest.
Undeploying Hotfixes
Running the command undeploys a hotfix, and
this command would perform files dependency check before undeploying the hotfix:
l If the hotfix files are not included in any other hotfix, running the command undeploys it directly.
l If some files in the hotfix are also included in the hotfixes that are installed later than it, you should
undeploy those hotfixes first by running the above command.
Note: In undeploying a hotfix, running the undeploy command rolls back only DB changes and
file changes. It does not roll back DML (Data Modification Language) changes.
Redeploying Hotfixes
If you have successfully deployed a hotfix, and you want to redeploy it, you can run the deployment
command again.
When running this command for redeploying purpose, it would:

1. Perform conflict check.
2. Perform files dependency check.
3. Undeploy the hotfix.
4. Deploy the hotfix again.
Limitations
The script contains the following limitations:
l Only DDLs which are used to update a view or a package are fully supported. Other SQLs, like DML or
DDL used for altering a table can be deploy successfully but cannot be rolled back by this tool.
l The files contained in the directory are not fully supported by this tool. You can deploy
those files using the script, but cannot roll back them.
l This script does not support a patch that is completely composed of SQLs. You cannot use this tool
to deploy, undeploy, or redeploy such patches.
kDevMigratorExtract.sh
The script uses the content migrator to extract a content bundle from the
PPM Center instance.
Note: You must run the script from the directory.
You can use the following command-line options with the script:
Option Description
-username PPM Center administrator user name
-password PPM Center administrator user password
-dbpassword System database password
-itghome Directory where PPM Center is installed ( )
-action Action to perform. Specify either or

Option Description
-entityId Entity ID
-keyword Search keywords
-filename Content bundle filename
-delimiter Delimiter string
-help Help text
-quiet Suppresses output from the script.
In the following example, the script searches for validations on the

PPM Server.
kDevMigratorImport.sh
The script uses the content migrator to import a content bundle into the PPM
Center instance.
kEnableTimeMgmtPeriodType.sh
Use the script to enable or disable period types in the KTMG_
PERIOD_TYPES table. During the script run, you are presented with a list of all of the available period
types. To disable an enabled period type, select it from the list. To enable a disabled period type, select
it from the list.
kEncrypt.sh
In some cases you may need to generate encrypted strings in accordance with the encryption scheme
of your PPM Server installation. To do this, you use the script.
Run the command:
The script run generates an encrypted string that starts and ends with the characters
which the system uses to mark encrypted data. Copy only the text string between these markers.

kExportAttributes.sh
You can use the script to export the translatable attributes of entities for a
PPM Center system that supports multiple languages. If you export a specific entity, the attributes of
child entities defined in the same language are included.
To export the all attribute definitions, run the command:
To export the translations for all entities, run the command:
To export the translations for a single entity, run the command:
For detailed information about how to use the script (and the
script), see the
kGenFiscalPeriods.sh
You can use the script to:
l Generate sets of periods to be used by Portfolio Management, Financial Management, and Resource
Management, for a range of years you specify
l Customize the formats of periods (years, quarters, and months) as they appear in financial
summaries and elsewhere
l Customize the format of weeks as they appear in the project cumulative cost page in Financial
Management
l Customize the names of months as they appear in financial summaries and elsewhere
l Change the month in which fiscal years start, to match your fiscal calendar
l Support fiscal years with more than twelve periods (not twelve months) to represent standard and
non-standard retail calendars in financial summaries, scenario comparisons, some portlets, and

some reports (but not in time sheets)
l Change the start day of the week, used in Financial Management
For more detailed information and instructions on how to set up these functions, see the
document.
kGenTimeMgmtPeriods.sh
The script is used in HP Time Management to populate the
table with data. The script takes the number of periods to be populated and the start date from which
the periods are to be populated.
Run the command:
where
represents the number of time periods to create for a specific period type.
Valid value: integer
represents the date from which the periods are to be populated. Date format:
For a new installation, running is optional. If you run the script with no
arguments, the number of time periods defaults to .
kHash.sh
The user name and password required to access the JMX console are encrypted to prevent
unauthorized access to the information that the JMX console makes available. They are both stored as
SHA-1 hash output in the file, which is located in the
directory.
You can run the script to output the hashed password required to access the JBoss JMX
console, as follows:

kImportAttributes.sh
Use the script to import the translatable attributes of PPM Center entities
that were exported using the script.
To import all of the files in the directory, run the command:
For detailed information about how to use the script, see the
kJSPCompiler.sh
The first time user requests a page in the PPM Center standard interface, the server must compile the
page. To eliminate this initial performance drag, run the script to precompile all of
the JSP pages before users request them. This gives first-time users faster access to the standard PPM
Center interface.
If any JSP is modified, you need to stop PPM Center, run the script, and then restart
PPM Center.
kKeygen.sh
The script generates new security keys.
kLdap.sh
This script is used to add the attribute to specified entries in the LDAP schema. You can
specify the entries using the standard LDAP search filter. If you do not specify a filter, the attribute is
added to all the entries, starting from the base DN.
Example
where indicates that the LDAP server parameters are to be read from the file.

kLicenseReader.sh
Use the to run the license reader tool. The license reader reads the encrypted
license file and provides the following information:
l Detailed information for each license installed on your machine, such as
o PPM Center module that is licensed for use, including the ID, version, and description
o IP address of the license Start date and expiration of the license
o Availability capacity of the license
l A summary of all the licenses installed on your machine
o Capacity for different PPM Center modules
o Expiration dates of licenses for different PPM Center modules
o Licensed IP for different PPM Center modules
To use the license reader, run the following command:
If you do not specify the file name, the license reader provides information of all the licenses installed
on your instance. If you do not specify the file patch, the license reader uses the default file path
.
Note: You can only use the script to read the license information. You cannot use it to modify the
license information.
kLicenseInstall.sh
The script is added in PPM Center version 9.30.
After you have activated and generated an Autopass license (a .dat file or several .dat files that HP sent
to you) from the HP Licensing for Software portal (http://www.hp.com/software/licensing), and that you
have successfully installed or upgraded to PPM Center version 9.30, use the

script to install the Autopass license key file(s). The newly installed Autopass license keys override the
trial or evaluation licenses.
To install an Autopass license key file, run the command as follows:
where, is the full path of the Autopass license key file you save on
your machine.
For example,
Note: Before you run the script, make sure you already activated and
generated an Autopass license from the HP Licensing for Software portal:
http://www.hp.com/software/licensing.
For instructions about activating and generating an Autopass .dat license file, see "Activating and
Generating Autopass License" on page 96.
kMigratorExtract.sh
The script is used in PPM Center entity migration.
It requires the following parameters:
-username
-action
-referenceCode
-entityId

The following parameters are optional:
-url
-password
-delimiter < >
-quiet
-keyword
-primaryKey
-primaryKeyName
-filename
-uncompressed
kMigratorImport.sh
Use the script to migrate PPM Center entities. Type only or for the 19 flags
listed.
Example
To import a file, run the command:
Caution: Make sure that the full file path is enclosed in single quotes.
The following parameters are required for this script:

Require same language and character set
Ignore language and character set warnings
Ignore all warnings
Do not change reference data
Install reference data
Replace existing Object Type
Replace existing Request Type
Replace existing Request Header Type
Replace existing Special Command
Replace existing Validation
Replace existing Workflow
Replace existing Report Type
Replace existing Workplan Template
Replace existing Workflow Step Sources
Add missing Environment
Add missing Security Group
Add missing Request Status
Replace existing Overview Page Section
Replace existing User Data Context
Replace existing Portlet Definition
Replace existing Module
Replace existing Data Source

Replace existing Project Type
Replace existing Sub workflow
The following parameters are optional:
l
l
l
kPMTMSync.sh
Use the script to run a synchronization script that copies actuals with matching tasks
and resources from HP Time Management to Project Management. Any actuals not entered into Project
Management using HP Time Management are replaced by actuals from HP Time Management.
To run this script, you must have the Edit All Projects access grant. For complete details about what the
synchronization script does and how to run it, see the
kRunCacheManager.sh
Use the script to manage your cache from the command line and without
having to restart the PPM Server.
Select the number for the corresponding entity cache (request types, validations, and so on) that you
want to flush. Running this script on any one node clears out the cache on all nodes. You can script this
to run after your database changes have been committed.

kRunServerAdminReport.sh
You can use the script to run diagnostic reports on the PPM Server. This
utility provides a summary of current activity on the system and the number of database connections
made.
Note: You can also access this functionality through the PPM Workbench. To access and run these
diagnostic reports from the PPM Workbench, on the shortcut bar, select Sys Admin > Server
Tools.
The reports listed in the Admin Tools window are the same reports you can use the
script to run.
kStart.sh
The script is used only on UNIX systems to start the PPM Server as a background process.
For more details about starting the server, see "Starting and Stopping the PPM Server" on page 87.
Note: For PPM Servers participating in the same cluster, HP recommends the following:
l Start the servers one at a time.
l Start each server with an explicit partition name to avoid inadvertent cluster participation.
For server clustering, the script accepts as a parameter, as follows:
If no value is specified, the default partition name is used.
kStatus.sh
Run the script to check the state of the PPM Server. This script returns the server status
whether the server is running or not. If it is running, the script returns the current load value, which
refers to the number of active user sessions.

kStop.sh
Use the script to stop the PPM Server. This script requires some arguments. You can use the
flag to quickly stop the server, or use the flag to stop it after a delay of a
specified number of minutes.
Note: If you are using the option, you can use the script to cancel the
stop request.
Using the option automatically issues a message to advise all connected PPM Center users that
the server will stop after the specified delay. This script requires authentication if the server parameter
is set to . In this case, you must also specify the flag
.
For more information on available flags, run without any options. For information about how
to stop the server, see "Starting and Stopping the PPM Server" on page 87.
kSupport.sh
Use the script to gather information useful to HP Software Support in diagnosing system
problems, and create a Zip file with a timestamp in the directory.
The script gathers the following information:
l Install and upgrade logs
l Server logs (with the option for a date range)
l JDBC logs
l Deploy logs (for the installation of patches and Deployment Management Extensions)
l Configuration files
l Server reports
l Database information for troubleshooting
l Invalid PPM Center schema objects and database indexes

l File system information
l Invalid PPM Center schema objects and invalid database indexes
l Bill of Materials (BOM) information
You can run the script from the Administration Console. For information, see "Gathering
Information for HP Software Support from the Administration Console" on page 312.
Running SQL Scripts with kSupport.sh

You can use the script to run SQL scripts that the HP Software Support provides for
gathering database information for troubleshooting purposes. You can browse for SQL scripts to run, or
manually paste SQL scripts in a text area to run. The server information collection summary page,
provides information about the number of SQL commands that are prevented from running.
All of the SQL scripts you select to run are copied into the
directory, and the SQL script content you entered in the text area is concatenated into a CSV-formatted
file named in the directory.
Caution: If the resulting SQL file is larger than 100 MB, a java.lang.OutOfMemory error may be
logged in the file. To correct the problem, split
the source SQL script into multiple files, and then run them again in batches.
You can run SQL scripts in silent mode, as follows:
Listing Invalid Database Schema Objects and Database Indexes

The kSupport output file lists invalid PPM Center schema objects and invalid database
indexes. Running kSupport.sh adds the following two sections to the
file:
l Selecting invalid objects in DB section. This lists the types and names of all invalid objects in the
database. The list includes objects of the following types:
o SEQUENCE
o PROCEDURE

o PACKAGE
o PACKAGE BODY
o TRIGGER
o TABLE
o INDEX
o VIEW
o FUNCTION
l Selecting invalid indexes in DB section. This section lists invalid database indexes. For example,
some INDEX objects are of status in but are of status in
.
Bill of Materials Information

The ksupport tool performs a BOM check and places the findings in the Bill of Materials Information
page, which includes the following three sections:
l Files missing. This section lists files that should exist, but do not.
l Files unwanted. This section lists files that are not shipped with
PPM Center and should not exist.
l Files changed. This section lists files that have changed since they were shipped with PPM Center.
To access the Bill of Materials Information page, do one of the following:
l Navigate to and open the file, and then click Bill of

Materials Information link.
l Navigate to and open the file.
Running Mode for kSupport.sh

You can run in GUI, console, or silent mode. Silent mode automatically captures a default
set of information without prompting for user input.
To run in GUI mode:

To run in console mode:
To run in silent mode:
kTestSiteMinder.sh
Use the script to determine whether SiteMinder is correctly configured with your
PPM Center instance and can authenticate your account. If your file is not configured
correctly, then the file is not parsed, and the error "Unable to connect to SiteMinder Agent" is displayed.
If you provide an invalid username or password, the message "User is failed for the authentication: 2" is
displayed.
After a script run, the SiteMinder Agent API displays one of the following values:
-
-
-
kTMDataConversion.sh
Use this time sheet data loader script to import large volumes of time sheet data from an external
application into the PPM Center database. You can run the script either before or after you start to use
HP Time Management. The time sheets that the script creates from data you specify in files have
the functionality as the time sheets created using HP Time Management in PPM Center.
To run this script, you must have the Edit Time Sheets access grant and the Edit All Projects access
grant. For complete details about the script, the requirements for running it, and how to run it, see the

kUpdateHtml.sh
The script is a key script used to update the PPM Server configuration. Always run the
script after you make changes to the file from a text editor or by
running the kConfig script (see "kConfig.sh" on page 516). If you change the configuration through
the Administration Console, run the script afterward if the Administration
Console prompts you to restart the PPM Server.
kVariables.sh
The script automatically generates the JAVA class search path, validates the JAVA_
HOME environment variable, and sets the KNTA_HOME environment variable. Many scripts, including
and call the script to set the JAVA classpath.
kWall.sh
Use the script to send a message to all users logged on to the PPM Workbench. When you run
the script, it prompts you for your PPM Center user name and password, for the message text, and for a
list of recipients.
setServerMode.sh
The script, located in the directory, sets the server mode in case
you want exclusive access to a running server.
The following are valid server mode values:
l Normal. In normal mode, all enabled users can log on, and all services are available, subject to
restrictions set in parameters.
l Restricted. In restricted mode, the server lets users with Administrator access grant log on. The
server cannot run scheduled executions, notifications, or the concurrent request manager while in
this mode.
Before you can install an Deployment Management Extension, you must set the server to restricted
mode.

l Disabled. Disabled mode prevents server startup. A server enters disabled mode only after a PPM
Center upgrade exits before the upgrade is completed.
1. On the desktop, select Start > Run.
The Run dialog box opens.
2. In the Open field, type:
For more information about server modes, see "Setting the Server Mode" on page 87.
<PPM_Home>/pdf
The subdirectory contains all documentation files for PPM Center (to view the documentation in PDF
format in the subdirectory, you need Adobe Reader).
You can also access product documentation:
l From Help > Help Center in either the PPM Center standard interface or the PPM Workbench
interface
l The HP Software Product Manuals Web site (h20230.www2.hp.com/selfsolve/manuals)
Note: PPM Center version 9.20 introduced a new framework for the PPM Documentation Library,
which is contained in the subdirectory. The new default PPM
Documentation Library is not customizable.
However, you can change back to the old "customizable" PPM Documentation Library. For more
details, see the .
<PPM_Home>/integration
The subdirectory contains information or examples for various common integrations
between the PPM Server and external systems. For example, the
directory contains information about each external Web server that
you can integrate with the PPM Server. Files used to perform the integration are located in these

folders. For more information on using the folders and files in the subdirectory, see the
relevant document that pertains to the integration involved.
<PPM_Home>/logs
The server directory structure has two log directories. The directory contains the
subdirectory, which contains a log file for each PPM Server report that is run, and directories
named and . These subdirectories contain execution logs for Deployment
Management packages and Demand Management requests. The placeholder in the directory
name corresponds to the ID of the package or request being run.
The other log directory, PPM Server contains all PPM Server-generated

logs. As the server runs, it generates logging messages and writes them to the file.
When this file reaches the size indicated by the server parameter, it is renamed to
and a new is started.
The Java servlets used to serve the Web pages generate their own log files, named .
The amount of information in the server log files depends on the debugging level set in the server
configuration. The server parameters and control
the debugging level. If a problem arises and you require more information in the logs, log on to the PPM
Workbench as Administrator and reset the server debug level to
(select Edit > Debug Settings).
<PPM_Home>/reports
The subdirectory contains the HTML files for all reports that PPM Center clients have run.
<PPM_Home>/server
The directory contains the deployed PPM Server. Typically, administrators are not
required to make any changes in this directory. Server configurations are handled through the provided
admin scripts in the directory.
<PPM_Home>/sql
The subdirectory contains source code for the built-in PPM Center reports and core PL/SQL
packages. This is provided for convenience and for customization needs.

<PPM_Home>/transfers
The subdirectory serves as temporary storage for files transferred between the server and
remote computers. For more information about how the transfers directory is used in entity migration,
see "Basic Parameters" on page 396.
<PPM_Home>/utilities
The subdirectory contains scripts for granting the SYS-level privileges to the PPM Center
database schema, and for creating the PPM Center users required for installing or upgrading PPM
Center. It also contains diagnostic tools for troubleshooting PPM Center installation, and the Watchdog
tool.
kWatchdog.sh
This script is used to run the Watchdog tool. Watchdog is a stand-alone tool that issues a command to
generate a thread dump whenever memory exceeds the configured threshold after a full garbage
collection (GC). This tool requires that the Java garbage collection log be turned on at startup.
Run the command:
For more detailed information about the watchdog tool and the requirements for using it, see "Using
the Watchdog Tool" on page 267.
Other Directories
Directories other than those described in this appendix contain reference files, as indicated by their
names. You are not likely to require access to these directories.

Send Documentation Feedback
If you have comments about this document, you can contact the documentation team by email. If an
email client is configured on this system, click the link above and an email window opens with the
following information in the subject line:
Feedback on Installation and Administration Guide (Project and Portfolio Management Center 9.30)
Just add your feedback to the email and click send.
If no email client is available, copy the information above to a new message in a web mail client, and
send your feedback to HPSW-BTO-PPM-SHIE@hp.com.
We appreciate your feedback!

HP Man PPM9.30 InstallationAdmin 3rded PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

HP Man PPM9.30 InstallationAdmin 3rded PDF

Hochgeladen von

Copyright:

Verfügbare Formate

HP Project and Portfolio

Installation and Administration Guide

Document Release Date: November 2014

The information contained herein is subject to change without notice.

Restricted Rights Legend

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

l Software Version number, which indicates the software version.

l Search for knowledge documents of interest

To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels.

HP Project and Portfolio Management Center (9.30) Page 2 of 541

Accessing PPM Center Documentation 17

Chapter 2: System Overview 19

Application Server Tier 21

Chapter 3: Installing PPM Center 36

About PPM Center Best Practices Installation 41

HP Project and Portfolio Management Center (9.30) Page 3 of 541

Requirements for Installing Best Practices 41

Preparing to Install PPM Center 46

Installing PPM Center 67

Configuring the FTP Server on Windows 77

Downloading and Installing Service Packs 79

Verifying PPM Center Installation 82

Chapter 4: Configuring the System 86

HP Project and Portfolio Management Center (9.30) Page 4 of 541

(UNIX only) Setting the ulimit Value 86

Starting and Stopping the PPM Server 87

Installing Autopass Licenses for PPM Center Product 93

Configuring or Reconfiguring the PPM Server 99

Enabling Export to PDF 116

Enabling IPv6 118

Verifying Client Access to the PPM Server 119

Accessing the JMX Console 119

Configuring or Reconfiguring the Database 120

Configuring the PPM Workbench to Run as a Java Applet 131

HP Project and Portfolio Management Center (9.30) Page 5 of 541

Running the PPM Workbench with Secure RMI (Optional) 132

Using the PPM Workbench: What Users Need to Know 133

What to Do Next 136

Chapter 5: Advanced System Configuration 137

Integrating an External Web Server with a PPM Server 176

HP Project and Portfolio Management Center (9.30) Page 6 of 541

Configuring a Server Cluster 179

Switching Between Stand-Alone and Server Cluster Configurations 201

Chapter 6: Implementing User Authentication 203

Integrating with an LDAP Server 204

Implementing Web Remote Single Sign-On with PPM Center 210

Implementing Generic Single Sign-On with PPM Center 213

Implementing Lightweight Single Sign-On Authentication (LW-SSO) 216

HP Project and Portfolio Management Center (9.30) Page 7 of 541

Configuration Requirements for LW-SSO Support 216

Integrating PPM Center with CA SiteMinder 222

Chapter 7: Improving System Performance 237

Improving System Performance 242

HP Project and Portfolio Management Center (9.30) Page 8 of 541

Monitoring Activity in PPM Center 253

Using the Watchdog Tool 267

Chapter 8: Maintaining the System 272

Tools in the Administration Console 281

HP Project and Portfolio Management Center (9.30) Page 9 of 541

Server Tools In the PPM Workbench 325

System Logging in PPM Center 338

Maintaining Log Files 347