Sysadmin Guide

System Administrator Guide
For Release 9.0
Copyright 1998-2008 Primavera. All Rights Reserved.

Certain components bundled with the software require the following notice:
The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this
file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/
Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the License for the specific language governing rights and limitations under
the License.
The Original Code is available at http://www.lowagie.com/iText/.
iText Library - Copyright (C) 1999-2005 by Bruno Lowagie and Paulo Soares. All Rights Reserved.
Portions copyright Actuate Corporation 2006.
This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).
The JavaSWF Software License, Version 1.0
Copyright (c) 2000 David Nick Main. All rights reserved.
"JavaSWF" refers to the Java source and binary code in the Java package "com.anotherbigidea" and all its subpackages.
Redistribution and use of the JavaSWF source and binary code, with or without modification, are permitted
provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by David Nick Main." Alternately, this acknowledgment may appear in
the software itself, if and wherever such third-party acknowledgments normally appear.
4. The code may not be used in any software that is available for public distribution or sale in order to provide to a
purchaser or end-user of the software direct programmatic access to the Flash SWF format via Java or JavaScript
(ECMA Script).
5. If the code is included in software that is provided for public distribution or sale then that software must provide
significant extra functionality on top of the Flash SWF access provided by JavaSWF.
Disclaimer:
THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1. Getting Started ................................................................................. 19
1.1 A Note on Terminology .............................................................. 20
1.2 Customer Support...................................................................... 21
1.3 About Installation Recommendations ........................................ 22
1.4 Example Installation................................................................... 23
1.5 Multiserver Environments .......................................................... 25
1.5.1 Web Servers..................................................................... 25
1.5.2 ProjectLink........................................................................ 25
1.6 Delivery Manager Considerations.............................................. 27
1.7 Included Software ...................................................................... 28
2. Installation Prerequisites................................................................. 31
2.1 Conventions ............................................................................... 32
2.2 Defining a Network User in Windows......................................... 33
2.2.1 Creating pvuser ................................................................ 33
2.2.2 pvuser and MS Analysis Services .................................... 34
2.3 Third-party Software .................................................................. 36
2.3.1 RDBMS Prerequisites ...................................................... 36
2.3.2 MS Analysis Services....................................................... 38
2.3.3 BEA WebLogic ................................................................. 38
2.3.4 Actuate ............................................................................. 40
3. Installing Primavera ......................................................................... 43
3.1 About These Instructions ........................................................... 45
3.2 Preparing to Install ..................................................................... 46
3.3 Setting Up the Core Server Host ............................................... 47
3.3.1 Installing the Application Components ............................. 48
3.3.2 Running Delivery Manager Stored Procedures................ 51
3.3.3 Setting up the OLAP Virtual Directory in IIS for Portfolio
Manager.............................................................................. 51
3.4 Enabling SSL Support................................................................ 54
3.4.1 Installing the Certificate .................................................... 54
3.4.2 Configuring the Core Application...................................... 55
3.4.3 Configuring the Primavera Event Handler for SSL ........... 56
3.4.4 Configuring the Analytic Applications for SSL .................. 57
3.5 Configuring the Web Client ........................................................ 60
3.5.1 Enabling ISAPI Filters....................................................... 60
3.5.2 Primavera URL ................................................................. 61
3.5.3 Customizing Web Client Appearance............................... 62
3.5.4 Resume Generation ......................................................... 67
3.5.5 T&E Printer-Friendly ......................................................... 70
3.5.6 Adding Images to BIRT Reports....................................... 73
3.5.7 Changing the Logo in the T&E Expense Report Finder ... 74
3.5.8 Customizing the Quick Help in the T&E Expense Report. 74
3.5.9 Configuring the Expense Reports Template..................... 75
3.6 Installing Reports and Data Mart ............................................... 76
3.6.1 Running Setup.................................................................. 76
3.6.2 Editing DSNs .................................................................... 79
3.6.3 Reports Properties............................................................ 80
3.7 Enabling Capacity Planning ....................................................... 81
3.8 Installation Windows .................................................................. 83
3.8.1 Full Setup ......................................................................... 84
3.8.2 Server Setup................................................................... 106
3.8.3 Reports Setup................................................................. 108
3.8.4 Analytic Applications Setup ............................................ 109
3.8.5 Data Mart Setup ............................................................. 111
3.9 Installing the Clients................................................................. 112
3.9.1 Installing Primavera Desktop Clients.............................. 112
3.9.2 Installing ProjectLink....................................................... 114
3.9.3 Installing Offline Time and Expenses ............................. 117
3.9.4 Importing a Certificate for SSL ....................................... 118
3.10 Post-Installation .................................................................... 120
3.10.1 Disable Remembered Time and Expense Values........ 120
3.10.2 Final Steps to Enable Portfolio Manager ...................... 120
4
4. Start up and Shutdown .................................................................. 125

4.1 Start Up.................................................................................... 126
4.1.1 Starting the Primavera Server Application ..................... 126
4.1.2 Starting the Primavera Client ......................................... 129
4.2 Shutdown ................................................................................. 133
4.2.1 Stopping the Primavera Client........................................ 133
4.2.2 Stopping the Primavera Server Application.................... 134
4.2.3 Stopping the WorkSite MP Server.................................. 135
4.3 Windows Log Files................................................................... 136
5. Using the Administration Tool ...................................................... 139
5.1 Client Options .......................................................................... 140
5.2 Server Options ......................................................................... 142
5.2.1 Servers ........................................................................... 143
5.2.2 Web Components........................................................... 143
5.3 Core Database Options ........................................................... 144
5.3.1 MS SQL Server .............................................................. 144
5.3.2 Oracle............................................................................. 146
5.4 DM Database Options ............................................................. 148
5.4.1 DM Synchronization ....................................................... 150
5.5 Authentication Options............................................................. 151
5.5.1 General Options ............................................................. 152
5.5.2 Login............................................................................... 153
5.5.3 Distinguished Name Resolution ..................................... 154
5.5.4 Authentication and Login IDs ......................................... 154
6. Web Administration ....................................................................... 157
6.1 Flush Web Client Caches ........................................................ 158
6.2 Monitor Server ......................................................................... 159
6.3 Active Web Sessions ............................................................... 160
6.4 Login Auditing .......................................................................... 161
6.5 ID Formats ............................................................................... 163
6.6 Synchronize Users................................................................... 164
6.7 Project Integration Options ...................................................... 165
6.7.1 ProjectLink Is Enabled.................................................... 165

6.7.2 ProjectServerLink Is Enabled ......................................... 167
6.8 Staffing Request Options ......................................................... 168
6.9 Administer Groups and Roles .................................................. 170
6.9.1 Creating and Assigning Groups and Roles .................... 170
6.10 Third-party T&E Options ........................................................ 173
6.11 Field-level Resource Profile Privileges .................................. 174
6.12 Language Authorization ......................................................... 176
7. Primavera Reports ......................................................................... 177
7.1 Reports and Rate Tables ......................................................... 178
7.1.1 Populating the Reporting Tables: MS SQL..................... 179
7.1.2 Populating the Reporting Tables: Oracle........................ 180
7.2 Provided Reports ..................................................................... 181
7.3 Custom Reports ....................................................................... 192
7.3.1 Requirements ................................................................. 192
7.4 Report Properties..................................................................... 193
7.4.1 Specifying Delivery Manager Reports Printers............... 197
8. Access Control ............................................................................... 199
8.1 Introduction to Access Control ................................................. 200
8.1.1 Pool Access.................................................................... 200
8.1.2 Company Access............................................................ 202
8.1.3 Analytic Applications Access Control ............................. 202
8.1.4 Collaboration Access Control ......................................... 202
8.1.5 MS Project Server Integration
through ProjectServerLink ................................................ 202
8.1.6 Access Control for Client Downloads ............................. 203
8.1.7 Pool Structure................................................................. 204
8.1.8 Overview of Pools........................................................... 206
8.1.9 Adding Domains and Pools ............................................ 210
8.1.10 Customizing Pool Owners ............................................ 212
8.1.11 Pools and Calendars .................................................... 214
8.1.12 Recommendations for Pool Structure Configuration .... 217
8.1.13 Pool Examples ............................................................. 218

8.2 Object Access Policies ............................................................ 221
8.2.1 Overview of OAPs .......................................................... 222
8.2.2 Task Access Policies...................................................... 224
8.2.3 Customizing an OAP ...................................................... 238
8.3 Time and Expenses Overview ................................................. 242
8.3.1 Time and Expense Approval .......................................... 243
8.3.2 Time and Expense Second-level Approval .................... 243
8.3.3 Second-level Default Approver Setup ............................ 244
8.3.4 Resource Pool Approvers .............................................. 245
8.3.5 Time and Expenses Administrators................................ 248
8.3.6 Third-party Time and Expenses ..................................... 252
8.4 Accounts .................................................................................. 253
8.4.1 Types of Accounts.......................................................... 254
8.4.2 Accounts and Access ..................................................... 256
8.4.3 Adding Non-resource Accounts...................................... 257
8.4.4 Updating Accounts ......................................................... 259
8.4.5 Resetting Passwords...................................................... 260
8.4.6 Removing Non-resource Accounts................................. 261
8.4.7 Changing a Password .................................................... 262
8.5 Access Role Catalog ............................................................... 263
8.5.1 Access Role Overview ................................................... 263
8.5.2 Default Access Roles ..................................................... 264
8.5.3 Conflicting Access Roles................................................ 265
8.5.4 Configuring the Access Role Catalog............................. 266
8.5.5 Assigning Access Roles ................................................. 268
8.6 Company Access ..................................................................... 270
8.7 Access Control Recommendations.......................................... 272
8.7.1 General Recommendations............................................ 273
8.7.2 Access Role Recommendations .................................... 274
8.7.3 Pool Structure Recommendations.................................. 275
8.7.4 Time and Expenses Administrator Recommendations .. 276
8.8 Access Control Example.......................................................... 278
8.8.1 Example Pool Structure.................................................. 279
8.8.2 Example Organization Structure .................................... 280
8.8.3 Example of Access Roles............................................... 281

8.8.4 Example OAPs ............................................................... 283
8.8.5 Example Account Access ............................................... 285
9. RDBMS Recommendations ........................................................... 287
9.1 Backup and Restore ................................................................ 288
9.2 Upgrading Between Primavera Versions ................................. 290
9.3 Microsoft SQL Server............................................................... 291
9.3.1 Database Sizing ............................................................. 292
9.3.2 Enable Address Windowing Extensions
for SQL Server 2005 ......................................................... 293
9.3.3 MS SQL Server Connectivity.......................................... 294
9.3.4 Primavera-Provided Files ............................................... 295
9.3.5 Creating the Core Schema Manually.............................. 298
9.3.6 Creating the Delivery Manager Schema Manually ......... 299
9.3.7 Creating the Data Mart Schemas Manually.................... 300
9.4 Oracle ...................................................................................... 303
9.4.1 Build and Configuration Parameters............................... 304
9.4.2 User Creation Script ....................................................... 306
9.4.3 PVDB Schema................................................................ 306
9.4.4 Tablespace Sizing .......................................................... 307
9.4.5 Oracle Connectivity ........................................................ 308
9.4.6 Connection Management ............................................... 309
9.4.7 Primavera-Provided Files ............................................... 309
9.4.8 Creating the Database Schemas.................................... 314
A. Actuate on Solaris ......................................................................... 321
A.1 Conventions............................................................................. 322
A.2 Installing Third-party Software................................................. 323
A.2.1 Actuate ........................................................................... 323
A.3 Configuring Reports................................................................. 325
A.3.1 Configuring Connectivity ................................................ 325
A.3.2 Setting Report Properties............................................... 327
A.3.3 Importing the Encyclopedia............................................ 327
B. WorkSite MP Server....................................................................... 329
8
B.1 Running Setup......................................................................... 330

B.2 Configuring WorkSite MP ........................................................ 331
B.3 Starting the WorkSite MP Server............................................. 336
B.4 Initializing the Library............................................................... 337
C. Delivery Manager Administration................................................. 339
C.1 Synchronization....................................................................... 340
C.1.1 Synchronization Basics.................................................. 341
C.1.2 Transfer Rules ............................................................... 342
C.1.3 Automatic Synchronization ............................................ 344
C.1.4 Manual Synchronization ................................................ 347
C.2 Changing Financial Rules for Unrestricted Projects................ 350
C.2.1 Overview........................................................................ 350
C.2.2 Running update_generic_step....................................... 353
C.2.3 Example Commands ..................................................... 354
D. Troubleshooting ............................................................................ 355
D.1 Unable to Start the Server Application .................................... 356
D.1.1 Server Application Unable to Connect
to MS SQL Server............................................................. 356
D.1.2 Previously Started, But Now Fails ................................. 357
D.2 Unable to Start the Desktop Client .......................................... 358
D.2.1 Unable to Start a Single Desktop Client ........................ 358
D.2.2 Unable to Start All Desktop Clients................................ 358
D.2.3 Desktop Client Trace Option.......................................... 359
D.2.4 Configuring Desktop Client Connectivity ....................... 359
D.3 Primavera Client Fails to Connect........................................... 361
D.4 Web Server Issues .................................................................. 362
D.5 Performance Degradation ....................................................... 363
D.5.1 Project Bulk Update ....................................................... 363
D.5.2 Data Mart ....................................................................... 363
D.6 Transfer Failure During Synchronization with DM................... 364
D.7 iManage Fails to Connect to Its Database .............................. 365
D.8 Web Client Issues ................................................................... 366
D.8.1 General Unexpected Behavior....................................... 366
D.8.2 Flash Interface Issues.................................................... 366
D.8.3 Web Address or Link Fails ............................................. 367

D.8.4 Prompted to Accept a Certificate ................................... 367
D.8.5 Access Denied when Publishing a Portfolio................... 368
D.8.6 Web Client Error: Editing Qualifications......................... 368
D.8.7 Web Client ToolTip Uses Sound Cue ............................ 368
D.9 ProjectLink............................................................................... 370
D.9.1 ProjectLink Fails to Connect .......................................... 370
D.9.2 ProjectLink Fails to Download Daily Actual Hours ......... 370
D.10 TroubleShooting Portfolio Manager....................................... 372
D.10.1 Message Logging......................................................... 372
D.11 Limiting the Number of Objects Displayed in Finders ........... 376
D.12 Unable to Launch Client in Windows Vista............................ 378
E. ProjectLink API .............................................................................. 379
E.1 Assumptions ............................................................................ 381
E.2 COM Interfaces ....................................................................... 382
E.3 Sample VBA Macros ............................................................... 389
F. ProjectServerLink and Microsoft Project Server......................... 391
F.1 Installing MS Project Server Extensions for HTTP .................. 392
F.2 Enabling MSPS Synchronization for Primavera via an Event
Handler .................................................................................... 394
F.2.1 Installing the Event Handler ........................................... 394
F.2.2 Viewing the Event Handler Log ...................................... 398
F.2.3 Configuring Primavera With SSL and
the Event Handler ............................................................. 398
F.2.4 Configuring the Reporting Database Server in Case of
Connection Errors ............................................................. 398
F.3 Setting up Impersonation for Actuals and ETC........................ 400
F.3.1 Configuring the MSPS Server for Impersonation ........... 400
F.3.2 Configuring the Primavera Server for Impersonation ..... 402
F.4 Configuring Primavera and MSPS for SSL.............................. 404
F.4.1 If Primavera uses SSL.................................................... 404
F.4.2 If Microsoft Project Server uses SSL.............................. 404
F.5 Implementation Considerations ............................................... 406
F.6 Configuring SharePoint to Support
10 System Administrator Guide
Fully-qualified Domain Name in PWA URL ............................. 418

G. Certifications.................................................................................. 419
G.1 Certified Software Platforms ................................................... 420
G.2 Hardware Requirements ......................................................... 427
System Administrator Guide 11
Preface
Preface
Welcome to the Primavera System Administrator Guide. This guide details
how to install and maintain Primavera.
Audience Assumptions
This guide assumes the reader is a qualified system administrator, familiar with
the supported operating systems, third-party software, and databases.
A Primavera system administrator is responsible for:
Installing Primavera.
Administering and maintaining Primavera, including access control.
Sources of Information
The following table lists sources of information about Primavera:
Source
Location
Online Help
Help is available in Primavera. In the web client,

click Help in the upper left corner.
Online Documentation
The Adobe Acrobat files (.PDF) provided with

Primavera can be viewed and printed with Adobe
Acrobat Reader, which is available at no cost from
Adobe Systems at www.adobe.com.
Primaveras Website
Please visit us at www.primavera.com/

customer/support.asp.
See Documentation Set on page 15.
Preface
Documentation Conventions
This document uses the following conventions:
Convention
Meaning
Plain Text
This is the default font of the manual.
Green Text
Indicates a cross-reference to a section containing

related information. Online, click the text to
navigate to the section.
Blue Text
Indicates text that appears in the graphical user

interface, including menu items and field names.
Code
Indicates code as it appears on the screen or as you

enter it.
FileSave
Indicates clicking a menu (File) then clicking a

command in the menu (Save).
Indicates information about the product that is key
to the topic at hand.
Indicates information that, if ignored, could cause
significant errors to develop.
Indicates a useful tip about using the product.
Preface
Documentation Set
In addition to the online help, the following documentation is provided with
Primavera:
Manual
Contents
Primavera Delivery
High level description of material

resources, transaction processing, billing,
and project accounting in Primavera.
ProjectLink Guide
Conceptual and procedural information

regarding Microsoft Project integration.
Data Mart Administration and

Analysis Services Guide
Provides information on Data Mart

administration. Also includes an overview
of the analytics based on Analysis
Services.
Portfolio Management
Provides conceptual and procedural

information about using Portfolio
Management and analytic application
access control.
Describes administration procedures,

including installation and maintenance.
Configuration Guide
Describes Primavera configuration.
Release Notes
Detailed information regarding the

resolved defects, known issues, and
installation of this release of Primavera.
For optimal online image quality in Adobe Acrobat, Primavera recommends

setting the magnification to 200-250% when referring to graphics in these files.
Preface
Contacting Primavera
You can contact Primavera by mail, telephone, or the World Wide Web:
Primavera
Three Bala Plaza West, Suite 700
Bala Cynwyd, PA 19004
Telephone:
Fax:
World Wide Web:
(610) 667-8600
(610) 667-7894
http://www.primavera.com/customer/
support.asp
Section 1
Primavera Installation
System Administrator Guide17
Getting Started
1.
Getting Started
This chapter provides installation information about Primavera. It includes:

A Note on Terminology
Customer Support
About Installation Recommendations
Example Installation
Multiserver Environments
Delivery Manager Considerations
Included Software
Getting Started
1.1
A Note on Terminology
The term server is casually used to refer both to a computer executing a piece of
software and to the piece of software itself. For example, the database server
might refer to either a computer or to an RDBMS application.
These differing uses of the term can be confusing. Therefore, this guide uses the
terms server and client to refer to software. The term host refers to hardware.
Getting Started
1.2
Customer Support
To access Primaveras extensive repository of product, implementation, and

training resources, visit http://www.primavera.com/customer/support.asp.
This secure site provides access to Primavera Online INTeraction (POINT),
support policies, and maintenance releases of Primavera software. All Primavera
customers, partners, and employees have access to this valuable resource.
Getting Started
1.3
About Installation Recommendations
This document describes the configuration of a possible implementation of

Primavera. The scenario includes the application server running in Windows; MS
SQL Server stores the schemas. For more information, refer to Installing
Primavera on page 43.
This is a medium-sized implementation. However, these recommendations are
merely guidelines that can help you implement Primavera as best suits your
needs. Depending on usage model, number of users, and hardware preferences,
your implementation of Primavera may vary from these recommendations. For
information about other recommended configurations, please contact Primavera
Customer Support. For information about supported third-party software, refer to
Certifications on page 419.
In all cases, the database server host and the application server host should be
situated as geographically close as possible, and be connected to each other by
high-bandwidth, low-latency network connections.
Getting Started
1.4
Example Installation
Primavera is designed to take full advantage of a networked computing

environment. Computing responsibilities can be divided among computers to
maximize performance.
A typical, small installation includes the following server software:
One RDBMS.
One instance of Microsoft Analysis Server (if using the analytic

applications).
One application server running BEA WebLogic. Note that an application

server is required for all implementations of Primavera.
One or more Primavera server applications.
One instance each of Data Mart (Windows only) and Portfolio Management.
Two or more web servers (one for reports, the other for web clients and the
analytic applications). The web servers should be dedicated to Primavera
usage.
One or more WorkSite MP servers.
One Actuate implementation for reports.
For a small enterprise, an installation of all components on minimal hardware

requires two or more server hosts:
One for the RDBMS and MS Analysis Server (if using the analytic
applications).
One for application server (BEA WebLogic in Windows), the server

application, the analytic applications, and the web server.
One for WorkSite MP.
One for Actuate (plus a web server) and Data Mart (Windows only).
Getting Started
Because heavy usage and large data volume can make reporting processintensive, Primavera recommends that larger enterprises run the Actuate reports
against offline copies of the Primavera databases. In this configuration, reporting
demands do not impact the On-line Transaction Processing (OLTP) databases,
and do not effect the performance of the core application. For more information
about replication, consult your RDBMS documentation.
A typical installation includes the following client software:
A web browser for each user.
A desktop client for each user requiring administrative access to Primavera.
If implemented, an installation of ProjectLink for each user who needs to

integrate Primavera data with Microsoft Project. If you use the ProjectLink
extended functionality, you must also distribute the macros written by your
enterprise. For more information, refer to Project Integration Options
on page 165.
If implemented, an installation of Offline Time and Expenses for each user

that reports time or expenses. Note that Offline Time and Expenses is used
by disconnected users who only connect to Primavera during
synchronization.
If implemented, an installation of the API client components for any

developer who must write custom applications using the Primavera API.
For information about required software, refer to Certifications on page 419.
Getting Started
1.5
Multiserver Environments
Some enterprises install multiple Primavera server applications to improve

performance. This section discusses some issues involved in this configuration.
Primavera recommends that the server application hosts be as close to each other
geographically as possible, and be connected to each other by high-bandwidth,
low-latency network connections. Use similar connections between the server
application hosts and the RDBMS host.
Server application hosts and the RDBMS host should not be separated by a
firewall.
1.5.1
Web Servers
Each server application requires a dedicated web server.

To ensure that your servers are sharing the Primavera load equally, implement a
load balancing solution. Note that the load balancing solution must be session
based: all HTTP requests from a single session must be directed to the same web
server.
For information on installing, configuring, and using a load balancing solution,
refer to the associated documentation.
1.5.2
ProjectLink
If you implement ProjectLink in a multiserver environment and your users

download daily actual hours from Primavera to Microsoft Project using the
ProjectLink Application Programming Interface (API), you must implement a
clock synchronization solution. Otherwise, ProjectLink may never download
certain daily actual hours. A clock synchronization solution ensures that the
clocks of a group of computers are set to the same time. In the case of Primavera,
the clock synchronization solution must synchronize all application server hosts.
Primavera has no specific requirements for the solution beyond requiring the
computers to agree on the time.
Getting Started
For more information about the ProjectLink API, refer to ProjectLink API on
page 379. For information about making Primavera more resilient to
synchronization problems, refer to ProjectLink Fails to Download Daily
Actual Hours on page 370.
Though it is only critical for multiserver environments that include ProjectLink, a
clock synchronization solution can be helpful for any multiserver environment.
Getting Started
1.6
Delivery Manager Considerations
Primavera can be implemented with or without the Delivery Manager (DM)

functionality, depending on an enterprises needs. If you implement the DM
solution, the core database (PVDB) shares configuration data with the DM
database (DMDB) and enforces data integrity across databases.
DMs constraints are controlled by the enforceDmRestrictions property in
the AppServerConfig.properties file. By default, the property is set to
TRUE, which causes DM-sensitive constraints to be applied to your data, such as
limits on the length of certain fields, even if you do not implement DM itself.
If you want to make DM-related changes in a new or existing installation, contact
Primavera Customer Support.
Getting Started
1.7
Included Software
You must install an appropriate application server before installing Primavera. For
Windows, Primavera supports BEA WebLogic Server and BEA WebLogic Server
Express.
The following tables list the components provided by Primavera.

Table 1-1
Server Application Components
Product
Description
Primavera Server
Application
Performs the business processing for Primavera.
Web Service Interfaces
Primavera web services interface. Required for

ProjectLink and ProjectServerLink.
Connectors
Standard import and export utilities.
Primavera Administration
Tool
Defines execution parameters for Primavera.
Primavera API
The server side web service component that

fields requests sent by custom applications
developed using .NET or Java.
Getting Started
Table 1-2
Analytic Application Components
Product
Description
Primavera application to assess project risk,

value, and performance, and to track resource
productivity across the enterprise.
Table 1-3
Report Components
Product
Description
Actuate
Found in a separate distribution image,

generates reports from data stored in the
RDBMS.
Report Files
Various files (such as the encyclopedia) used

by Actuate to generate reports.
Table 1-4
Database Utilities Components
Product
Description
Database Management
Scripts
SQL scripts that create, maintain, and

upgrade tables and views used by Primavera.
Table 1-5
Upgrade Archive
Product
Description
Upgrade Archive
Instructions and files necessary to

upgrade from previous versions.
Getting Started
Table 1-6
Desktop Client Components
Product
Description
Primavera Configuration Tool
Defines system-wide data used in

Primavera.
Security and Account Manager
Defines the pool structure, access

policies, access roles, and accounts.
Primavera Administration Tool
Defines execution parameters;

automatically installed with the
Configuration and Security and
Account Manager.
ProjectLink
Integrates Primavera with Microsoft

Project. A module of VBA macros
providing extended functionality is also
provided
Offline Time and Expenses
Allows disconnected resources to

record time and expenses that are later
synchronized with Primavera.
Microsoft .NET Framework
Required for ProjectLink installations;

provides connectivity.
Primavera API Client

Components
The client side web service component

required to develop custom applications
using .NET or Java.
Note that the Microsoft .NET Framework is found in the [PRIMAVERA]\

docroot\setups directory of the server application host.
To install the Primavera client components, download them from the
Primavera server application by visiting the Options page of the web
client once the Primavera server is installed. See Installing the Clients on
page 112.
Installation Prerequisites
2.
Before installing Primavera, you must create a network user for administration
and also install and configure the prerequisite software. This chapter provides
guidance, including:
Conventions
Defining a Network User in Windows
Third-party Software
For information about the certified third-party software, refer to Certifications

on page 419.
2.1
Conventions
The instructions in the following sections and in subsequent chapters use the
following conventions:
[PRIMAVERA] is the directory where Primavera will be installed.
[BEA_HOME] is the directory where the BEA WebLogic application server

will be installed.
[ACTUATE] is the directory where Actuate iServer will be installed.
[ANALYTICS] is the directory where the analytic applications will be
installed.
2.2
Defining a Network User in Windows
In Microsoft Windows, Primavera relies on a network user to run Data Mart, to

start MS Analysis Services, and to provide connectivity for Portfolio Manager.
Primavera recommends and assumes that a single user (pvuser) is responsible
for all these tasks.
Create the user before installing Primavera.
2.2.1
Creating pvuser
To define pvuser:
1.
On the network domain where the analytic applications reside, create a

network user for Primavera. This guide assumes that you name this account
pvuser.
For general information on network users, refer to the documentation
provided by Microsoft.
2.
Configure the password for pvuser to never expire.

If the password expires, MS Analysis Services, Data Mart, and the analytic
applications will fail.
3.
Grant the pvuser account Administrator access on the computers that will
host the application server, Data Mart, the analytic applications, the MS
Analysis Services server, and on any computer that will host the MS
Analysis Services client components.
4.
On every computer that will host the MS Analysis client or server (for
instance, on the application server host, the Data Mart host, and the MS
Analysis Services server host), designate pvuser as an OLAP
Administrator. For instructions, refer to pvuser and MS Analysis
Services on page 34.
When you run setupolapdb, Data Mart, or your application server, be sure to log
into Windows as pvuser.
2.2.2
pvuser and MS Analysis Services
On any computer hosting MS Analysis Services, pvuser requires the ability to

act as part of the operating system. In addition, pvuser must be defined as an
OLAP administrator and should be specified as the account to start the Microsoft
Analysis Services service. Instructions for each of these steps are described in
this section.
To grant pvuser permission to act as part of the operating system:
1.
On the desktop of the computer that will host MS Analysis Services, click
StartSettings Control PanelAdministrative ToolsLocal
Security Policy.
2.
Click Local PoliciesUser Rights Assignments.
3.
In the right-hand list, double-click Act as Part of the Operating System.
4.
In the Local Security policy window, click Add.
5.
In the Select Users, Groups, or Computers window, select the name of the
domain where pvuser was created.
6.
From the scrolling region, select pvuser and click Add.
7.
Click OK in the Select Users, Groups, or Computers window.
8.
Click OK in the Local Security policy window
9.
Reboot the computer.
10. On the desktop of each computer hosting MS Analysis Services, repeat steps
1 through 9
pvuser now has permission to act as part of the operating system of each host
you updated.
You must have MS Analysis Services installed before designating OLAP
administrators. See MS Analysis Services on page 38.
To designate an OLAP Administrator:
1.
On the desktop of the MS Analysis Services host, click

StartProgramsControl PanelAdministrative ToolsComputer
Management.
2.
In the Computer Management window, select Local Users and

GroupsGroups
SQLServer2005MSOLAPUser$[HOSTNAME]$[SQLINSTANCE].
The precise name of the OLAP group will depend on your hostname and
Analysis Server configuration.
3.
Double-click
SQLServer2005MSOLAPUser$[HOSTNAME]$[SQLINSTANCE].
The SQLServer2005MSOLAPUser Properties window appears.
4.
Click Add.
The Select Users and Groups window appears.
5.
Locate and select pvuser.
6.
Click OK in the Add Users window.
7.
Click OK in the SQLServer2005MSOLAPUser Properties window.
8.
Close the Computer Management window.
pvuser is now an OLAP Administrator on this computer.

To have pvuser start MS Analysis Server as a service:
1.
2.
On the desktop of the MS Analysis Server host, click StartSettings

Control PanelAdministrative ToolsServices.
Edit the startup properties of the SQL Server Analysis Services
(MSSQLSERVER) service.
3.
In the Log On As group box, enter pvuser and the associated password.
You must stop and restart the service for this change to take effect.
If you do not run Microsoft Analysis Services as a service, be sure to log in to

Windows as pvuser when starting the Microsoft Analysis Services.
2.3
Install the prerequisite software in the following order:

RDBMS Prerequisites
MS Analysis Services
BEA WebLogic
Actuate
Unless you are otherwise instructed, Primavera recommends using the default
settings when installing third-party software.
For information about the certified third-party software, refer to Certifications
on page 419.
The following hosts cannot be separated by a firewall: the RDBMS host that stores
the related databases, the Data Mart host, and the application server host that
serves the Primavera web client or analytic applications.
Existing Primavera customers can refer to WorkSite MP Server on page 329
for instructions on installing WorkSite MP Server.
2.3.1
RDBMS Prerequisites
Primavera relies on an RDBMS to store and retrieve your business data.

Primavera supports both Microsoft SQL Server (MS SQL) and Oracle, with these
exceptions:
The DM database only supports MS SQL Server.
The OLAP database only supports MS SQL Analysis Services.
Note that you must create a database alias that points to the Oracle instance that
will store your Primavera schemas. Create the alias on the application server host
where the Primavera server application resides. The alias is required by the
database scripts.
Refer to the documentation provided with your RDBMS for installation
instructions. For Primavera-specific configuration recommendations, refer to
RDBMS Recommendations on page 287.
For Oracle, the character set should be AL32UTF8 and the national character set
should be AL16UTF16. For MS SQL, use the default.
Once the RDBMS is installed and configured, create either an empty database (in
MSSQL) or a user (in Oracle) for each of the following that correspond to
functionality you implement:
Table 2-1
Required Databases
Database or
User
Default Name
Description
Primavera
core database
PVDB
The main transactional database of the

Primavera core server application.
Delivery
Manager
database
DMDB
The Delivery Manager transactional

database used for billing, budgeting,
and financial transactions.
Data Mart
database
Target
The database populated by the Data

Mart process. In Oracle, create a
TNSNAMES entry (if it does not exist)
to enable Data Mart to connect to this
database.
Analytic
Applications
database
strategicPlanning
The database that stores the userdefined information in Portfolio

Management and security settings for
PM.
Collaboration
librarya
Primavera
The database that stores the workspace

information used in collaboration.
a.The Collaboration library database version requirements are different

from other databases in the table. For information about certified database platforms, refer to Certifications on page 419.
Collaboration support is provided only for customers upgrading from
Primavera 8.9 or earlier. For information, refer to WorkSite MP
Server on page 329.
In addition, OLAP cubes (PV_OLAP) are created when Data Mart is installed.
In Oracle, use the user script provided with Primavera to create the users to own
these schemas. Refer to User Creation Script on page 306
2.3.2
Primavera relies on MS Analysis Services to store the OLAP cubes used by the
analytic applications. You must install MS Analysis Services before installing
Primavera.
During installation, Primavera recommends that you accept the default values.
Refer to the Analysis Server documentation for installation instructions.
If the application server is installed on a dedicated host, that computer must also
host the MS Analysis client components. Primavera recommends that you install
the same version of all MS Analysis Services components.
The Remote Registry Service must run on every computer hosting the Microsoft
Analysis Services components. For more information, refer to the documentation
provided by Microsoft.
2.3.3
BEA WebLogic
A third-party application server is required for every implementation of

Primavera. It must be installed and configured before installing Primavera.
Primavera supports both WebLogic Server and WebLogic Server Express.
Note that the same WebLogic installation cannot serve both your test and
production environments.
To install and configure a BEA WebLogic application server:
1.
Copy the WebLogic 10.0 MP1 installer (server100_win32.exe and

server1001_upgrade_win32.exe) from the distribution image to the
machine where you want to install WebLogic.
Do not run the installation from a file located remotely. If there is an old version of
WebLogic on your host machine, you must first uninstall it, delete the BEA root
folder, and then restart the host machine.
2.
Install WebLogic by running the following file:

server100_win32.exe
After BEA prepares the installation, the welcome window appears.

3.
Click Next.
The Choose BEA Home Directory window appears.
4.
Select the Create a new BEA Home option and specify the location where
you want to install BEA WebLogic products.
5.
Click Next.
The Choose Install Type window appears.
6.
7.
Select the Custom option.

Click Next.
The Choose Products and Components window appears.
8.
Deselect the Workshop for WebLogic Platform option.
9.
Click Next.
The Optional Tools window appears.
10. Deselect the Mercury Profiling Tools option.

11. Click Next.
Note the directory for WebLogic server for Primavera installation.
12. Click Next.
The Install Windows Service window appears.
13. Select No for the Node Manager Service option.
14. Click Next.
The Choose Shortcut Location window appears.
15. Select the All Users Start Menu folder option (recommended).
This option is used for selecting the Start Menu folder in which you want to
create the BEA shortcuts.
16. Click Done to exit the installer, after the installation is complete.
Install the WebLogic upgrade by running the following file:
server1001_upgrade_win32.exe
1.
The WebLogic installation wizard appears.
2.
Follow the on-screen instructions to upgrade WebLogic.

It will recognize the existing installation and prompt you to upgrade to the
new version.
3.
Click Done to exit the installer, after the installation is complete.
Copying Necessary BEA File

When the installation wizard completes the process, copy the license.bea file
from the Primavera 9.0 media to [bea_root].
2.3.4
Actuate
Primavera relies on Actuate for reporting. You must install Actuate before you
can configure the Primavera reports.
The Actuate install includes two distribution images (downloadable files)
provided by Primavera. You need to copy the following files from the
distribution image to the machine where you want to install Actuate:
Actuate_90SP2.exe
Actuate_90SP2_Doc_L10n.exe (documentation)
Before configuring reports, you must install the following Actuate components in
the order they appear:
To install Actuate 9 iServer:
1.
Run ActuateiServer.exe from the distribution image.
2.
Specify the location where you want to install Actuate iServer.
3.
Select the Typical installation.
4.
When prompted for a license, locate and select the

Actuate_iServer_key_31151.xml key file in the Actuate distribution
image.
5.
Complete the installation accepting the defaults.
To install Actuate 9 iPortal:
1.
Run ActuateiPortal.exe from the distribution image.
2.
Specify the location where you want to install Actuate iPortal.
3.
Select the Typical installation.
4.
Complete the installation accepting the defaults.
5.
After the installation is complete, open the server.xml file located in the
iPortalconf directory and add the following line inside the Host tag:
<Context path="/primavera/reports" docBase="<location of
your iPortal install>\iPortal\webapps\iportal" debug="0"/
>
When you add the above line ensure that you replace <location of your
iPortal install> with the correct path. For example, if you use the default
install path, you need to add the following line in the Host tag:
<Context path="/primavera/reports" docBase="C:\Program
Files\Actuate9\iPortal\webapps\iportal" debug="0"/>
To configure Actuate 9 iPortal:
1.
Open the Start menu and select ProgramsActuate 9 iPortal

Administration Tool.
2.
Enter Administrator in the User Name field and click Log in.
3.
Select iPortalPreferences and click Repository.
4.
Select the Enterprise option for the default repository type for iPortal.
Now, iPortal will use the Actuate iServer Encyclopedia to store and
manage content.
5.
Save the changes.
6.
Select iPortalEnterprise and click iServer Configuration.
7.
Specify the default iServer URL and default volume information to access
the iServer. Primavera recommends entering default values (You may
change the values only if necessary).
8.
Save the changes.
9.
Select Control PanelAdministrative ToolsServices and restart the

Apache Tomcat for Actuate iPortal 9 service.
To install Actuate iServer Integration Technology:
1.
You must install Actuate iServer Integration Technology to integrate reports

with the Primavera applications.
2.
Run ActuateiServerIntegrationTechnology.exe from the

distribution image.
3.
Specify the location where you want to install Actuate iServer Integration
Technology.
4.
Select the default settings for all the options.
The Install wizard will complete the installation. A reboot is not necessary.
For more information, refer to the documentation provided with Actuate.
Install the documentation by running the setup.exe file found in Online
Documentation and Localization Resource
Files\l10nandonlinedocumentation\windows on the Actuate
distribution image.
Primavera recommends changing the user associated with the Actuate service in
Windows. Change the Log on as setting from the user name that installed
Actuate to the Local System account. Change this setting on the Log On tab of the
Services window accessed from StartSettings Control
PanelAdministrative ToolsServices.
Installing Primavera
3.
Once all prerequisites are met, you must install the Primavera software by
running setupwin32.exe, which is in the Primavera distribution image. It
installs each included component. You must run setupwin32.exe on each
server host, selecting the appropriate components for that server:
Ensure beforehand that you have sufficient disk space for the Primavera
software, as well as your databases and third-party software. A full
installation of the Primavera software alone requires at least 1 GB.
To install the software, log in to Windows as a user with system

administrator privileges. You can use the pvuser network account
described in Defining a Network User in Windows on page 33.
This chapter includes the following:
About These Instructions
Preparing to Install
Setting Up the Core Server Host
Enabling SSL Support
Configuring the Web Client
Installing Reports and Data Mart
Enabling Capacity Planning
Installation Windows
Installing the Clients
Post-Installation
Third-Party Post-Installation Requirements
Primavera recommends installing the components in the order they appear in this
chapter.
3.1
About These Instructions
Because Primavera can be configured to run across multiple servers, and because
each enterprises unique needs dictate the most suitable configuration, a
procedural description of the setup process cannot present the exact windows or
fields that you may encounter. Instead, this chapter describes a single
implementation that may be representative of most users experiences. For more
information about the documented implementation, refer to Example
Installation on page 23.
This chapter also provides reference information regarding the fields on each
window that setupwin32.exe displays. For more information, refer to
Installation Windows on page 83.
Hardware sizing varies with many factors, including the modules used, expected
usage scenarios, and the level of redundancy and fault tolerance you require.
While general guidelines can be found in Hardware Requirements on page
427. please contact Primavera for more specific recommendations.
3.2
Preparing to Install
Before running setupwin32.exe, use this checklist to ensure that you have
fulfilled all prerequisites.
Refer to the release notes to determine whether to uninstall previous

releases. For information on upgrading, refer to Upgrading Between
Primavera Versions on page 290.
Determine the names of all hosts to which you will install components
(including server application hosts, RDBMS host, reporting hosts,
analytic applications host, and Data Mart host).
Ensure that the required third-party software has been installed. Refer
to Certifications on page 419.
Ensure that all prerequisite software is installed and configured as

described in Installation Prerequisites on page 31.
Ensure that a network user called pvuser has been created and
configured on each host. See Defining a Network User in Windows
on page 33.
Ensure that the RDBMS that will store the Primavera core database has
been installed.
In MS SQL, create empty databases, as described in RDBMS

Prerequisites on page 36.
In Oracle, create users to own the schemas. Refer to User Creation

Script on page 306.
If you use Oracle, create a database alias on the server application host.
The database alias must point to the database instance (only used by the
batch files provided by Primavera).
If you use Microsoft Project Server 2007 (MSPS), install the

following Microsoft documentation.
3.3
Setting Up the Core Server Host
Before installing the Primavera software on the core server, the computer must
first host the following:
Supported Primavera Component
BEA WebLogic
Server application, analytic applications
MS Analysis Services Client

Components
Analytic applications (Portfolio

Manager)
WorkSite MP Server
Collaboration
If you do not implement the corresponding Primavera component, the software is

not required. Installation of this software is described in Third-party
Software on page 36.
Setting up the core server includes:
Installing the Application Components
Running Delivery Manager Stored Procedures

The stored procedures are only necessary if you implement Primaveras
Delivery Manager. Run them directly after installing the Primavera
software.
Setting up the OLAP Virtual Directory in IIS for Portfolio Manager

Installing the OLAP Virtual Directory is required only if implementing
Portfolio Manager.
3.3.1
Installing the Application Components
Run setupwin32.exe to install the Primavera components that will reside on

the server application host. This example installs everything except reports and
Data Mart.
Each window mentioned in this section is described in further detail in
Installation Windows on page 83. Click the name of a window in this section
to navigate to its description.
If the application server is running, stop it before installing Primavera.
To install the Primavera software on the core server host:
1.
Browse to distribution image (a downloadable file) using Windows

Explorer, and double-click the setupwin32.exe icon.
After InstallShield prepares the installation, the Welcome window appears.
2.
Click Next.
The License Agreement window appears.
3.
Accept the license agreement and click Next.

The Install Directory window appears.
4.
Choose the installation location for Primavera and click Next.

The Setup Type window appears.
5.
Select the Full radio button.
6.
Click Next.
The Component Selection window appears.
7.
Disable the Reports and Data Mart check boxes and click Next.
The BEA WebLogic window appears.
8.
Accept the location that InstallShield determined or click Browse, choose a

directory, and click Open.
The Program Folder window appears.
9.
Accept the default program folder or enter a name to create a new folder, and
click Next.
The RDBMS Type window appears.
10. Select MSSQL (Microsoft SQL Server) and click Next.

The Access Protocol window appears.
11. Select the type of access protocol your enterprise will (HTTP or HTTPS) use
and click Next.
The Server Application Service window appears.
12. Indicate whether Primavera should be installed as a service and click Next.
The Primavera Core Database: MS SQL window appears.
13. Supply the requested data in each field and click Next.
The Delivery Manager Database window appears.
The Data Mart Database window appears.
The Analytic Applications Database window appears. This database
(called StrategicPlanning) is the operational database used by PM and stores
security access data for PM.
The Enterprise Identification window appears.
17. Enter the requested value and click Next.
The Mail Server window appears.
18. Enter the name of your mail server host and click Next.
The Web Server Host window appears.
19. Enter the fully qualified domain and host name of the computer that will host
the web server. Typically, this is the host computer. For example, enter
host1.primavera.com.
The Portfolio Management Host window appears.
20. Enter the fully qualified domain and host name of the computer that will host
PM (in this scenario, the local computer). For example, enter
host1.primavera.com.
21. Click Next.
The MS Analysis Services window appears.
22. For the Analysis Server Host field, enter the fully qualified domain name.
23. For the Analysis Server Name, enter the SQL Server name, and if
applicable, the SQL Server instance name (if not using the default SQL
Server). Use the format:
SQL_SERVER_NAME\[SQL_INSTANCE_NAME]
For example, enter a SQL Server name, such as EVPROD or, if using an
instance, enter EVPROD\SQLSERVER2005.
24. Supply the remaining requested data and click Next.
The Actuate window appears.
25. In the Report Server Volume field, enter the name of the encyclopedia that
will be created in Actuate iServer.
26. Enter the fully-qualified domain and host name of the computer hosting the
reports web server host.
27. If the Actuate HTTP Service uses a non-default port number, enter it.
Otherwise, accept the default value, and click Next.
Two Collaboration Server windows appear.
For details of the Collaboration Server, refer to WorkSite MP Server on
page 329.
28. Generally, you can accept the default values in these windows. If you have
customized your WorkSite MP server user names or passwords, enter the
correct user names and passwords.
29. Click Next.
InstallShield asks you to wait while it validates your selections. When
InstallShield is ready to continue installation, the Summary window
appears.
30. Review your selections and use the Back button to correct any entries. Click
Next when you are satisfied. InstallShield begins copying files.
The installation process can be time consuming, depending on the
components you selected. While it updates your databases, InstallShield
provides real-time information about its activity. When InstallShield is done,
the Results window appears, indicating the components that have just been
installed.
31. Click Finish to exit the setup executable.
The software is installed to the server application host.
3.3.2
Running Delivery Manager Stored Procedures
This section applies only if Delivery Manager is installed.

The stored procedures must be run against the Delivery Manager (DM) database.
Run the dm_storedproc.sql file before you start the server application for the
first time.
The dm_storedproc.sql file is found in the exporter_DM\sql folder within the
folder where you installed the server application. Use Query Analyzer to run this
file. If you encounter errors, contact Primavera Customer Support.
You must install the connectors in order to install this SQL file.
3.3.3
Setting up the OLAP Virtual Directory in IIS for

Portfolio Manager
This section applies only if Portfolio Manager is installed.

After you install Portfolio Manager, you need to set up the OLAP IIS virtual
directory on the Microsoft Analysis Server host. The setupIISOLAP.bat file
allows you to automatically configure HTTP access to SQLServer 2005 Analysis
Server.
To create the OLAP virtual directory
1.
If the Microsoft Analysis Server host resides on a computer that is different

from the one where the Portfolio Manager host resides, create a temporary
folder on the Analysis Server host:
[MICROSOFT ANALYSIS SERVER HOST]\tmp
If the Microsoft Analysis Server resides on the same host as Portfolio

Manager, skip to Step 5.
2.
Create a subdirectory in the tmp folder named docroot:

[MICROSOFT ANALYSIS SERVER HOST]\tmp\docroot
3.
Copy the [PORTFOLIO MANAGER HOST]\bin\setupIISOLAP.bat file to

[MICROSOFT ANALYSIS SERVER HOST]\tmp.
4.
Copy the individual files from [PORTFOLIO MANAGER HOST]\docroot

directory to [MICROSOFT ANALYSIS SERVER HOST]\tmp\docroot.
You do not need to copy any of the subfolders that reside in [PORTFOLIO
MANAGER HOST]\docroot.
5.
Run the [MICROSOFT ANALYSIS SERVER

HOST]\tmp\setupIISOLAP.bat file with the following parameters:
setupIISOLAP HOSTNAME SCRIPT_DIRECTORY WWW_ROOT
MS_ANALYSIS_SERVICES_ISAPI_FOLDER
Example: setupIISOLAP localhost c:\tmp\docroot

C:\InetPub\wwwroot "C:\Program Files\Microsoft SQL
Server\MSSQL.2\OLAP\bin\isapi"
Note that the quotes around the final parameter are required if there are
spaces in your directory names.
6.
Verify the console output and confirm the batch file completed successfully.
7.
Set the Security Authentication for the OLAP Virtual Directory:

a.
Select Start Programs Administrative Tools IIS Manager.
b.
Expand your server name, Web Site, and Default Web Site.
c.
Select Default Web Site from the drop-down menu.
d.
Select the OLAP virtual directory and right-click on Properties.
8.
e.
Select the Directory Security tab.
f.
Click Edit... within Authentication and access control.
g.
Check Enable anonymous access.
h.
Define an appropriate network username and password, such as pvuser.
i.
Select the Integrated Windows authentication check box.
j.
Click OK to save and close.
Restart IIS.
3.4
Enabling SSL Support
The installation wizard prompts you to name the protocol to use when connecting
to Primavera (HTTP or HTTPS). If you enter HTTP during installation but want
to configure SSL (Secure Socket Layer) security and use the HTTPS protocol,
you must take additional steps.
To use SSL security, you must obtain a server security certificate and install it on
the web server. Note that the certificate cannot be a trial version.
These steps are only necessary if you want to enable SSL in a Primavera
installation that was originally configured without SSL.
For information on using SSL with the Primavera clients, refer to Importing a
Certificate for SSL on page 118.
This section includes:
Installing the Certificate
Configuring the Core Application
Configuring the Analytic Applications for SSL
3.4.1
Installing the Certificate
If you use your own trusted authority to issue certificates, the root certificate for
that authority must be imported into the keystore of every server application
using the manageCert batch file, which is found in the [PRIMAVERA]\bin
directory. You must also install the certificate on the analytic applications host, if
they do not share a host with the server application. This step is not necessary if
the certificate was issued by a well-known trusted certificate authority.
To add a certification to the keystore:
1.
Copy the certificate into the bin directory of the server application
installation. For example, c:\Primavera\bin.
2.
On the desktop of the server application host, click StartPrograms

AccessoriesSystem ToolsCommand Prompt.
3.
Change directories until you are in the bin directory under the Primavera
root directory. For example, enter:
cd primvera\bin
4.
At the prompt, enter:

manageCert -import [certification]
Where [certification] is the file name of the certificate.

5.
Repeat Step 1 through Step 4 on the analytic applications host, if they are
installed on a dedicated host.
The new certificate is installed.

The Primavera clients also require this certificate when SSL is enabled. For
instructions, refer to Importing a Certificate for SSL on page 118.
3.4.2
Configuring the Core Application
You must indicate that you want to use SSL.

To configure the core application to support SSL:
1.
Select StartProgramsPrimaveraPrimavera Administration from

the desktop of the server application host.
The Administration window appears.
2.
If necessary, select the Server tab.
3.
In the Web Components group box, check the Use SSL Security check box
if you are using SSL Security.
4.
Click OK.
This configuration is necessary when the web server associated with Primavera is
configured for SSL security.
For more information, refer to the documentation provided with your web server
and to Server Options on page 142.
3.4.3
Configuring the Primavera Event Handler for

SSL
If you are using Primavera with Microsoft Project Server, and Primavera uses
SSL (https), you need to perform these two tasks:
Add a Parameter with the Primavera Server Hostname
Add the Primavera Evolve SSL Certificate as Trusted Root Certificate
Add a Parameter with the Primavera Server Hostname

To configure the Event Handler to work with Primavera if Primavera uses SSL,
add the following parameter to:
[PRIMAVERA]\cfg\appserverconfig.properties:
ServiceSphere.url = https://serverName
where serverName is the Primavera server hostname where this file resides.
This parameter is not required if using non-SSL (http) protocol.
Add the Primavera Evolve SSL Certificate as Trusted Root
Certificate
Add the Primavera Evolve server certificate as trusted root certificate at the
machine level rather than at the logged-in user level.
To add the Primavera Evolve server certificate at the local machine" level:
1.
Copy the Primavera Evolve SSL certificate to a directory in the MSPS

system.
2.
Launch Microsoft Management Console (mmc) by typing mmc at the

prompt when you select Start Run in Windows.
3.
Select File > Add/Remove Snap-in... to launch the Add/Remove Snap-in

dialog box.
4.
Click Add... to bring up the Add Standalone Snap-in dialog box.
5.
Select Certificates and click Add.. to bring up the Certificates Snap-in

dialog box.
6.
Select the Computer Account radio button and click Next.
7.
Select Local Computer and click Finish.
8.
Click Close to close the Add Standalone Snap-in dialog box.
9.
Click OK to close the Add/Remove Snap-in dialog box.
10. Expand the Certificates Trusted Root Certificates nodes.

11. Right-click on the Certificates folder under Trusted Root Certificates.
12. Select All Tasks Import to bring up the Certificate Import Wizard dialog
box.
13. Choose the Primavera Evolve SSL certificate to import and follow the steps
with default options to finish the import process.
14. Close Microsoft Management Console. You can save or ignore the Console
session.
3.4.4
Configuring the Analytic Applications for SSL
Because you indicate whether the applications will use SSL during installation,
most enterprises do not need to take the following steps. These steps are only
necessary if you want to enable SSL in an analytic applications installation that
was originally configured without SSL.
Use caution when editing properties files. Inadvertent or incorrect changes may
cause unexpected errors throughout Primavera that may be difficult to
troubleshoot.
To enable SSL for the analytic applications:
1.
2.
Stop the server application. For instructions, refer to Stopping the

Primavera Server Application on page 134.
On the server application host, locate and open the
AppServerConfig.properties file using a text editor such as Notepad.
In Windows, this file is found in the [PRIMAVERA]\cfg directory.
3.
Locate the properties that read:

Infra.portfolioManager.protocol=http
4.
Change the protocol by specifying HTTPS:

Infra.portfolioManager.protocol=https
5.
6.
Save the file.

On the analytic applications host, locate and open the
Configuration.properties file using a text editor such as Notepad. In
Windows, this file is found in the

[ANALYTICS]\AnalyticalApplications\Configuration\WEBINF\classes directory.
7.
Locate the property that reads:

singleSignOnProviderBaseURL=http://[hostname]/primavera/
web
where [hostname] is the name of the computer hosting the server

application.
8.
Change the protocol of the URL for this property by specifying HTTPS:
singleSignOnProviderBaseURL=https://[hostname]/
primavera/web
9.
Save the file.
10. Still on the analytic applications host, locate and open the
StrategicPlanning.properties file using a text editor such as
Notepad. In Windows, this file is found in the
[ANALYTICS]\AnalyticalApplications\
StrategicPlanning\WEB-INF\classes directory.
11. Locate the property that reads:
strategicPlanningBaseURL=http://[hostname]/EA/
StrategicPlanning/StrategicPlanning
where [hostname] is the name of the computer hosting the server

application.
12. Change the protocol of the URL for this property by specifying HTTPS:
strategicPlanningBaseURL=https://[hostname]/EA/
StrategicPlanning/StrategicPlanning
13. Repeat Step 7 through Step 9.

14. On the computer hosting the Internet Information Services installation that
serves the analytic applications, start IIS and import the certificate for the
Default Web Site. For instructions, refer to the documentation provided by
Microsoft.
15. Start the server application. For instructions, refer to Starting the
Primavera Server Application on page 126.
3.5
Configuring the Web Client
You can customize the Primavera web client for enhanced security or to modify
its appearance, as described in the following sections:
Enabling ISAPI Filters
Primavera URL
Customizing Web Client Appearance
Resume Generation
T&E Printer-Friendly
Adding Images to BIRT Reports
The Primavera web client does not necessarily support web browsers that are not
among those listed in Certified Software Platforms on page 420.
3.5.1
Enabling ISAPI Filters
On Windows 2003, you must take additional steps to configure IIS to allow the
use of ISAPI filters. Primavera uses an ISAPI filter to serve the web client. If you
do not make this change in Windows 2003, the web client will not function.
To enable ISAPI filters for IIS in Windows 2003:
1.
On the desktop of the IIS host, click StartControl Panel

Administrative ToolsInternet Information Service (IIS) Manager.
IIS Manager appears.
2.
Double-click the name of the local computer to expand the tree, and select
the Web Service Extensions folder.
3.
The right-hand pane displays details about the available extensions.
4.
From the list of web server extensions, select All Unknown ISAPI
Extensions, and click the Allow button.
5.
Exit IIS Manager.
3.5.2
Primavera URL
Most of your end-users access Primavera over the Internet or your corporate
intranet by pointing their browsers to the Primavera URL. The Primavera URL
consists of the name of the web servers host and the servlet alias. If you
implemented a load-balancing solution, supply the name of the load-balancing
host rather than that of a web server.
By default the URLs are:
Component
URL
Core web client
http://[hostname]/primavera/web
http://[hostname]/EA/StrategicPlanning/
StrategicPlanning
Analytic Access Control
http://[hostname]/EA/Configuration/Configuration
For [hostname], use the fully qualified domain and host name. Note that these
URLs are case-sensitive.
If you use SSL encryption, the protocol, or first part of the URL, is https. For
example:
https://[hostname]/primavera/web
3.5.3
Customizing Web Client Appearance
You can customize the appearance of the Primavera web client by:
Adding a Logo
Changing the Custom Color Scheme
Adding Links
Adding a Logo
The Primavera logo can be replaced with a graphic specific to your enterprise.
To add a logo (such as your company logo):
1.
Create a GIF file for the logo. This file should have a transparent background
and must be 183 pixels wide and 48 pixels high.
2.
Save this file with the name logo.gif in the docroot\images\sss

directory beneath the directory where you installed the Primavera web
components.
The existing logo.gif file is overwritten with your new image.
3.
Restart the application server.
Changing the Custom Color Scheme

The custom color scheme allows you to implement a web client color scheme
specific to your enterprise. Change the custom color scheme by editing the
ColorSchemes.properties file.
To change the color scheme:
1.
Using a text editor, such as Notepad or vi, locate and open the
ColorSchemes.properties file found in the \cfg directory under the
directory where you installed the server application.
2.
In the ColorSchemes.properties file, locate the section that begins:

# Scheme 6: Custom Pattern.
sss6.name: lbl.color.schemes.custom
sss6.bodyBG:
#fbfeff
sss6.mainHeader:
#c2d6e7
sss6.mainmenuBG:
#c2d6e7
sss6.tableBorder:
#6c9fc6
3.
4.
Change colors, as appropriate. To change a color, change the hexadecimal

color code (that is, the SRGB code) after the colon of each property. Refer to
Table 3-1 on page 64 and Figure 3-1: Web Client Color Property Usage
(next) for usage of each property.
To change the name of the color scheme, locate the
lbl.color.schemes.custom value in the
lib\evolve\generated\language\i18nlabels_en.properties
file, and replace the word custom with the name you want to use. For
example:
lbl.color.schemes.custom= Pistachio Mist
You can change this value for each language you authorize. To do so,
change the lbl.color.schemes.custom value in each of the i18nLabel
files. There is one per language (that is, the i18nLabels_de.properties
file contains German, i18nLabels_es.properties file contains Spanish,
and so forth). These changes are not preserved between versions.
5.
Stop and restart the server application. For instructions, refer to Start up
and Shutdown on page 125.
For information regarding color codes, visit http://www.w3.org.
The number in each row in 3-1 maps to a call-out in Figure 3-1: Web Client
Color Property Usage.
Table 3-1
Custom Color Properties
Value
Usage
1.
sss6.bodyBG
The overall body color of all pages. Use a

lighter color for this property, because the
application text is black.
2.
sss6.mainHeader
The background color of the top of the page.
3.
sss6.mainmenuBG
The background color of the Main Menu.
4.
sss6.tableBorder
The color that outlines all panes (one pixel

wide).
5.
sss6.menurule
The horizontal rule on the Main Menu.
6.
sss6.breadcrumbBG
The background color of the breadcrumb.
7.
sss6.tableBG
The background color of all panes. Also serves

as one of the alternating colors in table rows.
8.
sss6.subHeader
The background color of the title bar on each

pane. Also serves as the title row in tables and
the color of tabs that are not selected. Also
controls the color of column separators.
9.
sss6.altTableBG
The alternate color used in table rows.
2
6
7
8
4
9
5
Figure 3-1
Web Client Color Property Usage
Adding Links
At the bottom of the Main Menu, Primavera includes an area where you can
create external links. If you want your users to have access to certain URLs
through Primavera, edit the CustomizedLink.properties file.
To add a link to the Main Menu:
1.
Using a text editor, such as Notepad or vi, locate and open the
CustomizedLink.properties file found in the \cfg directory under the
directory where you installed the server application.

2.
3.
Scroll to the bottom of the file.

On a new line, enter
[Link_name]=[Address]
where [Link_name] is the name you want displayed as the link, and
[Address] is the URL.
For example:
Primavera=http://www.primavera.com
Delete any entries for web sites you do not want to display.
4.
Save the file and exit the editor.
5.
Stop and restart the server application. For instructions, refer to Start up
and Shutdown on page 125.
When editing this file, you must type a backward slant (\ ) before every space. The
slant is the escape character that allows spaces to be displayed properly in URLs.
3.5.4
Resume Generation
Resume Generation enables a user to generate and print a resume for any
resource. The resumes are generated by BIRT, a Java tool for building and
publishing reports. They can be customized to fit the needs of your organization.
Downloading BIRT
To download the BIRT Reporting Framework:
1.
In your web browser, go to http://download.eclipse.org/birt/downloads/.

The BIRT release build page appears.
2.
Click the All-In-One button.

The download sites page appears.
3.
Select the download site that appears by default (such as [United States]
Georgia Tech. Software Library) or select a site from the list of mirror
sites.
You see the File Download dialog box after the download starts.
Setting the Default View Format

The default view in the Resume Generation application can be configured to
display files in either PDF or HTML format (HTML is the default).
To set the default view:
1.
Open the AppServerConfig.properties file.
2.
In the text file, locate the following option:
3.
Set the option to the desired format: html or pdf.
4.
Infra.birt.report.format.resume = [format]
Using a Secure Connection

BIRT reports cannot render images that are accessed over a secure connection. If
you use a secure connection in your installation of Primavera, you need to
generate the reports with different files.
To use the default reports over an SSL connection:
1.
Locate the Primavera install directory (this folder will be whatever you
named it upon installation) and choose the following path:
[Primavera Install Directory]/lib/BIRTRuntime/reports
2.
In the reports folder, make a copy of the default file

ResourceResume_[RDBMS].rptdesign
where
[RDBMS] is mssql or oracle.
For example, name the copy

ResourceResume_[RDBMS].rptdesign_default
3.
Open the file ResourceResume_[RDBMS].rptdesign_ssl and save it as

the default file ResourceResume_[RDBMS].rptdesign.
Making Changes to a Report File

To make changes to BIRT report files in MSSQL or Oracle format:
1.
2.
Using a text editor such as Notepad, open the report file according to the
database you are using:
ResourceResume_mssql.rptdesign or
ResourceResume_oracle.rptdesign.
3.
In the file, find the following line of code:

<oda-data-source
extensionID="org.eclipse.birt.report.data.oda.subjdbc"
name="PVDB" id="4">
In the code line, change subjdbc to jdbc. This enables BIRT to utilize
the appserver connection to the database.
4.
In the BIRT Report Designer, open the report and click the Layout View
tab.
5.
In the BIRT Data Explorer, expand the Data Sources node and double-click
PVDB.
6.
Update the Database URL, User Name and Password fields.
7.
Click Test Connection.

The message Test Connection Successful appears.
8.
Click OK.
9.
Make the configuration changes you wish to make.
10. Once your changes have been made, change jdbc to subjdbc and
restart the server.
3.5.5
T&E Printer-Friendly
Time and Expense reports can be viewed and printed in a printer-friendly format.
The reports are generated by BIRT, a Java tool for building and publishing
reports. You can customize T&E printer-friendly options in the following ways.
For BIRT download information, refer to Downloading BIRT on page 67.
Setting the Default View Format
The default view in the T&E Printer-friendly application can be configured to
display files in either PDF or HTML format (HTML is the default).
To set the default view:
1.
2.
Open the AppServerConfig.properties file.

In the text file, locate the following option:
Infra.birt.report.format.te.pf = [format]
3.
Set the option to the desired format: html or pdf.
4.
Using a Secure Connection

BIRT reports cannot render images that are accessed over a secure connection. If
you use a secure connection in your installation of Primavera, you need to
generate the reports with different files.
To use the default reports over an SSL connection:
1.
2.
In the reports folder, make copies of the default files

ResourceResume_[RDBMS].rptdesign and
TimesheetPF_[RDBMS].rptdesign
where
[RDBMS] is mssql or oracle.
For example, rename the files [original name]_default.

3.
Open the file ResourceResume_[RDBMS].rptdesign_ssl and save it as

the default file ResourceResume_[RDBMS].rptdesign.
4.
Open the file TimesheetPF_[RDBMS].rptdesign_ssl and save it as the

default file TimesheetPF_[RDBMS].rptdesign.
Making Changes to a Report File

To make changes to BIRT report files in MSSQL or Oracle format:
1.
2.
Using a text editor such as Notepad, open the report file according to the
database you are using:
ResourceResume_mssql.rptdesign or
ResourceResume_oracle.rptdesign.
3.
In the file, find the following line of code:

<oda-data-source
extensionID="org.eclipse.birt.report.data.oda.subjdbc"
name="PVDB" id="4">
In the code line, change subjdbc to jdbc. This enables BIRT to utilize
the appserver connection to the database.
4.
In the BIRT Report Designer, open the report and click the Layout View
tab.
5.
In the BIRT Data Explorer, expand the Data Sources node and double-click
PVDB.
6.
Update the Database URL, User Name and Password fields.
7.
Click Test Connection.
The message Test Connection Successful appears.

8.
Click OK.
9.
Make the configuration changes you wish to make.
10. Once your changes have been made, change jdbc to subjdbc and
check in the file.
3.5.6
Adding Images to BIRT Reports
You can add images to the BIRT reports by linking to them or embedding them.
Using Linked Images
Using linked images, a report can be configured to get the image from a website.
This will work for both HTML and PDF formats, however, due to a current
limitation in BIRT, you cannot get images from any website that uses secure
connections (https).
To add images to a BIRT report:
1.
In the viewer, drag and drop the image icon from the palate onto the report.
The Edit Image Item window appears.
2.
Enter the URL, enclosed in quotation marks, in the Enter URI field.
3.
Click OK.
Using Embedded Images

An image can also be embedded in a report. This can only be done to documents
in PDF format and will not work on HTML reports.
To embed images in a BIRT report:
1.
In the viewer, drag and drop the image icon from the palate onto the report.
The Edit Image Item window appears.
2.
Click Add Image.
3.
Select an image from your local file system.
4.
Click OK in the Edit Image Item window.
3.5.7
Changing the Logo in the T&E Expense Report

Finder
To change the logo in the Time and Expense Report Finder page:
1.
Navigate to the [PRIMAVERA]\docroot\images directory.
2.
Replace the logo_small.gif file with the one you want to use.
3.

When you open the Time and Expense Report Finder, the new logo appears.
3.5.8
Customizing the Quick Help in the T&E Expense

Report
The Time and Expense Report pages contain a Quick Help page that describes
the information about the T&E status legend, as well as hot keys/shortcuts. The
top portion of this page can be used to describe additional help or details that you
want to mention about the Time or Expense Report entry and approval for your
company.
To customize the Quick Help in the Time Report page:
1.
Navigate to the [PRIMAVERA]\docroot\docs\flex\help directory.
2.
Edit the TimeReportHelp.html.template file.

There are no size limitations on the file.
3.
Remove the .template suffix from the file name.

This enables all users of the system to view this content through the Time
Report Quick Help.
To customize the Quick Help in the Expense Report page:
1.
Navigate to the [PRIMAVERA]\docroot\docs\flex\help directory.
2.
Edit the ExpenseReportHelp.html.template file.

There are no size limitations on the file.
3.
Remove the .template suffix from the file name.
This enables all users of the system to view this content through the Expense
Report Quick Help.
Users may need to clear their browser cache to see immediate updates.
3.5.9
Configuring the Expense Reports Template
The columns that appear in the expense reports can be configured by the system
administrator. In order to configure these columns, you must have the Expense
Template Configure access control bit, located under the Expense Configure tab
in the Admin Client.
To configure the Expense Report template:
1.
Access the Time and Expense Report Finder; then click Configure.
2.
Click the Expense Entry Format tab.
3.
If a Resource must specify a task code when entering expenses, check the
checkbox next to Are Resources required to specify task codes when
reporting expenses?
4.
Select additional columns that youd like Resources to see from the
Available Optional Columns list, and move them to the left pane or right
pane lists.
5.
Move the column names up or down the list in the left pane or right pane
lists in order to change the order of columns Resources will see in their
expense reports.
6.
Click the Expense Approval tab to configure the list and order of columns
Approvers will see.
3.6
Installing Reports and Data Mart
Installing reports and Data Mart includes:
Running Setup
Editing DSNs
Reports Properties
3.6.1
Running Setup
Run setupwin32.exe to install the Primavera components that will reside on

the report and Data Mart host.
Before installing the Primavera software, the computer must first host the
following:
Supported Primavera Component
Actuate
Reports
IIS
Reports
MS Analysis Services Client Components
Data Mart
Installation of this software is described in Third-party Software on page 36.

Each window mentioned in the setup instructions is described in further detail in
Installation Windows on page 83.
To install reports and Data Mart:
1.
Browse to the distribution image (a downloadable file) using Windows

Explorer, and double-click the setupwin32.exe icon.
2.
Click Next.
3.

The Install Directory window appears.
4.
Choose the installation location for Primavera and click Next.

The Setup Type window appears.
5.
Select Reports and click Next.

The Component Selection window appears.
6.
Enable the Data Mart check box.

Ensure that only the Reports and Data Mart components are selected.
7.
Click Next.
The RDBMS Type window appears.
8.
Select MSSQL (Microsoft SQL Server) and click Next.

The Access Protocol window appears.
9.
Select the type of access protocol your enterprise will use and click Next.
The Primavera Core Database: MS SQL window appears.
The Delivery Manager Database window appears.
11. Supply the requested data in each field, or enable the Skip DM check box if
you do not implement Delivery Manager.
12. Click Next.
The Data Mart Database window appears. The Data Mart database, which
is called target by default, stores the star schema.
An informational window about database links appears.

14. Click Next.
The MS Analysis Services window appears, displaying the default values.
15. For the Analysis Server Host field, enter the fully qualified domain name.
16. For the Analysis Server Name, enter the SQL Server name, and if
applicable, the SQL Server instance name (if not using the default SQL
Server). Use the format:
SQL_SERVER_NAME\[SQL_INSTANCE_NAME]
For example: EVPROD or, if using an instance, EVPROD\SQLSERVER2005.

17. Supply the remaining requested data and click Next.
The Data Mart Error Email window appears.
18. Enter the port number that the mail server uses.
19. Enter an email address that you want Primavera to send messages in the case
of Data Mart failure. If you want to specify more than one, separate the
addresses with commas.
20. Click Next.
The Currency Conversion window appears.
21. Identify an exchange rate table and currency by entering:
The name of a company in your organization unit structure.
The name of an exchange rate in that company.
The preferred currency to use in the analytic applications.
These values are case-sensitive. If you do not know these values, you can
leave the fields blank, but you will not be able to run Data Mart until you
supply them. To supply them manually, edit the Datamart.properties
file, as described in the Data Mart appendix in Analytic Applications.
22. Click Next.
The Actuate window appears.
23. In the Report Server Volume field, enter the name of the encyclopedia that
will be created in Actuate iServer.
24. Enter the fully-qualified domain and host name of the computer hosting the
reports web server host.
25. If the Actuate HTTP Service uses a non-default port number, enter it.
Otherwise, accept the default value, and click Next.
InstallShield is ready to continue, the Summary window appears.
26. Review your selections and use the Back button to correct any entries. Click
The installation can take several minutes. While it updates your databases,
InstallShield provides real-time information about its activity. When
InstallShield is done installing the selected components, the Results window
appears, indicating the components that have just been installed.
The software is installed to the report and Data Mart host.
3.6.2
Editing DSNs
If you use reports and MSSQL server, InstallShield automatically creates the
required Data Source Names (DSNs) that point to the databases accessed by
Actuate: PVDB, DMDB (if you use Delivery Manager), and target (if you use
Data Mart).
However, InstallShield cannot automatically provide the database user password
required by the DSN. You must edit each DSN you use by adding a password.
To add a DSN password:
1.
On the desktop of the Actuate host, click StartSettingsControl

PanelAdministrative Tools.
The Administrative Tools window appears.
2.
Double-click Data Source (ODBC).

The ODBC Data Source Administration window appears.
3.
Select the System DSN tab.
4.
Select the PVODBCSRC data source, and click Configure.

The Microsoft SQL Server DSN Configuration window appears.
5.
Follow the on-screen instructions and verify the entries that InstallShield
made automatically when you installed the reports.
6.
On the second window to appear, enter the password of the MS SQL Server
user name displayed in the Login In field.
7.
Complete the wizard, and click Test to ensure that the connection succeeds.
8.
If it does not, repeat Step 4 through Step 6.
9.
Click OK.
10. Repeat Step 4 through Step 9 for the DMODBCSRC and

TARGETODBCSRC data sources, as necessary.
11. Click OK.
The DSNs now point to the databases properly.
3.6.3
Reports Properties
Primavera uses parameters in the AppServerConfig.properties file to

connect to Actuate. Several of these have default values. If you use non-default
values, you must edit this file to specify them. If you implement DM, you can
specify printers for those reports.
It is typically not necessary to edit this file for reporting values unless you have
modified the report encyclopedia. Before changing this files contents, make a
copy of the file.
For more information, refer to Report Properties on page 193.
3.7
Enabling Capacity Planning
Capacity Planning models resource supply and project demand. It helps you
assess current capacity requirements and predict future trends through an Actuate
report and PM KPIs. Capacity Planning must be enabled by editing the
AppServerConfig.properties and Datamart.properties files.
Use caution when editing the AppServerConfig.properties and
Datamart.properties files. Inadvertent changes to any properties may cause
unexpected errors throughout Primavera that may be difficult to troubleshoot.
Before changing these files contents, make a copy of each file.
The capacity planning Data Mart process creates suitability scores for each
resource and for each position based on the specified model definitions. Even if
you only use the Capacity Planning report, you must enable it in Data Mart.
Note that you can change the matching model by editing the
primavera.datamart.capacityplanning property in the
Datamart.properties file found in the [PRIMAVERA]\datamart\cfg
directory. For more information, refer to Analytic Applications.
To enable Capacity Planning:
1.
2.
On the Data Mart host, locate and open the Datamart.properties file
using a text editor such as Notepad or vi. For example, in Windows, this file
is found in the [PRIMAVERA]\datamart\cfg directory.
Add the string CapacityPlanning to the end of the
primavera.datamart.startup.ExpediteJobs property, delimited by
a comma:
primavera.datamart.startup.ExpediteJobs = FullTransfer,
CapacityPlanning
3.
Save the file and close the editor.
4.

AppServerConfig.properties file using a text editor such as Notepad
or vi. For example, in Windows, this file is found in the [PRIMAVERA]\cfg
directory.
5.
Near the end of the file, locate the line that reads:
PtsServer.datamart.enabled = false
This line controls the Capacity Planning analytic.

6.
Change the word false to true:

PtsServer.datamart.enabled = true
7.
8.
Stop and start Primavera. For instructions, refer to Start Up on page 126.
3.8
Installation Windows
This section provides detailed information about the fields and windows that
InstallShield may display in preparation for installing the Primavera software.
Note that you may not see the windows in this particular order, because the order
in which windows are displayed is determined by the components that you
install. For example, if you do not implement Actuate reports, you will not see
the Actuate window.
Full Setup
Server Setup
Reports Setup
Analytic Applications Setup
You can use InstallShields Custom option to select the components to install.
3.8.1
Full Setup
A Full Setup installs all components to the local computer. It includes the
following:
Welcome
License Agreement
Install Directory
Setup Type
Component Selection
BEA WebLogic
Program Folder
RDBMS Type
Access Protocol
Server Application Service
Primavera Core Database: MS SQL
Primavera Core Database: Oracle
Delivery Manager Database
Data Mart Database
Data Mart RDBMS-to-RDBMS Transfers
Analytic Applications Database
Enterprise Identification
Mail Server
Web Server Host
Portfolio Management Host
Data Mart Error Email
Currency Conversion
Actuate
Collaboration Service (only if installing connectors separately)
Collaboration Server
Collaboration System Users
Summary
Database Progress
Results
Welcome
This is the first window that InstallShield displays. No data is required.
License Agreement
This window asks you to agree to the Primavera license agreement. You cannot
continue until you click I accept the terms of the license agreement.
Install Directory
Specify the directory where you want to install Primavera. You can accept the
default location (for example, if you are installing the server application the
default is c:\Primavera) or click Browse to select a different directory.
Setup Type
Figure 3-2
Setup Types
Your selection in this window determines the other windows that appear. Select
the type of setup you want to install on this computer:
Full. Installs all components to the local computer and configures the
RDBMS. Refer to Full Setup on page 84.
Server. Installs the core server application and Delivery Manager, and
configures collaboration. Refer to Server Setup on page 106.
Reports. Installs Primaveras Actuate reports to the local computer. Refer to

Reports Setup on page 108.
Analytic Applications. Installs Data Mart and Portfolio Management to the

local computer. Refer to Analytic Applications Setup on page 109.
Data Mart. Installs Data Mart to the local computer. Refer to Data Mart
Setup on page 111.
Custom. Allows you to select the combination of components to install.
Component Selection
Figure 3-3
Component Selection
This window allows you to select many combinations of individual components

to install. It is displayed for every setup type, providing greater flexibility. Note
that some components depend on others. For example, if you select the Server
component, the Security and Account Manager and Configuration
component is also selected.
The components that are selected when this window appears depend on your
selection in the Setup Type window.
Select from the following components:
Server:
Core Server. Installs and deploys the server application, which is the
core element of Primavera. This also installs the web services for
integration, the ProjectLink web service, and required files for
implementing ProjectServerLink.
Configure Collaboration. Configures Primavera to work with a

WorkSite MP installation. If you are installing an application server that
will access the collaboration server (either locally or on a dedicated
host), select this component.
In multiserver environments, every server application must be
configured with the same collaboration settings.
Collaboration support is provided only for customers upgrading from
Primavera 8.9 or earlier. For information, refer to WorkSite MP
Server on page 329.
Delivery Manager. Identifies the MS SQL Server and database to use

for Delivery Manager, and can optionally create the schema. This
component also installs files specific to Delivery Manager.
In multiserver environments, every server application must be
configured with the same DM settings.
Primavera API. Installs and deploys the web server that can field
requests from custom applications built using .NET or Java. Such
applications must utilize the Primavera Application Programming
Interface (API).
Import/Export Connectors. Installs the files necessary to use the import

and export connectors. Select this component if you are installing DM.
Reports. Identifies the Actuate iServer host and installs Primaveras reports.
Security and Account Manager and Configuration. Installs the Security

and Account Manager and Configuration desktop clients. These clients are
used by system administrators and business analysts to administer
Primavera.
Portfolio Management. Installs and deploys the PM application.
Data Mart. Installs and configures Data Mart, which extracts data from the
core database and loads them into the Data Mart and OLAP (Online
Analytical Processing) databases.
BEA WebLogic
You are prompted for the Product Installation Directory (that is, the root
directory of the BEA WebLogic application server). InstallShield detects the
location automatically. If necessary, select a different location.
Program Folder
This window prompts you to indicate the program folder that InstallShield
should create in the Start menu. Accept the default folder name or enter the
name of a folder InstallShield should create.
RDBMS Type
Primavera supports either Microsoft SQL Server or Oracle. Indicate which type
Primavera will access.
Server Application Host Name
When you are installing the Analytic Applications separately, you are prompted
for the location of the Primavera core application host.
Note that you must enter the computers fully qualified domain and host name.
For example, enter host1.primavera.com, where host1 is the computer name, and
primavera.com is the domain name.
Carefully review the default name displayed in this field. While InstallShield
attempts to supply the correct host and domain name, the default value may not
be correct.
Access Protocol
The access protocol used by Primavera is either HTTP or HTTPS, depending on
whether you plan to secure access to the Primavera web server using Secure
Socket-Layer (SSL) encryption. Select the appropriate protocol. Note that, if you
select HTTPS, you must also obtain and install an appropriate SSL certificate on
the web server. Refer to Enabling SSL Support on page 54 for more
information on SSL.
This window prompts you to indicate whether you want to install the Primavera
server application as a service. When installed as a Windows service, Primavera
can run without a user being logged into its host.
Figure 3-4
Database Identification for MS SQL Server
This window identifies the MS SQL Server and database that store the Primavera
core database. All MS SQL Server database windows include these fields:
Fully Qualified Database Host Name. Enter the name of the computer
hosting the MS SQL Server.
User ID. Enter the name of a MS SQL Server user that Primavera will use to
connect to this database. Primavera recommends using an account with
permissions in this database that are comparable to the database owners
(DBOs) permissions.
Password and Confirm Password. Enter the password to the specified user
account in the Password and Confirm Password fields.
Database Host. Enter the name of the computer hosting the MS SQL
Server.
Port. Enter the port number that the MS SQL Server uses. If the database
server uses the default port number (1433), accept the default value.
Database Name. Enter the name of the database. By default, the core
database name is PVDB. Either accept the default or enter a different name,
depending on the name of the database created before installing the
Primavera software.
Do you want to run scripts to create the database schema? Select No if

the database already has a schema or if you want to define the schema later.
Select Yes to run the scripts that create the core database schema.
Do not run the scripts against a database that already has the schema.
Note that, in some configurations, you are prompted to skip database setup for
Data Mart or Delivery Manager.
For more information about the required databases, refer to RDBMS
Figure 3-5
Database Identification for Oracle
This window prompts you to identify the Oracle instance that will store the
Primavera core database. All Oracle database windows include these fields:
Fully Qualified Database Host Name. Enter the name of the computer
hosting Oracle.
User ID. Enter the name of an Oracle user that will own the Primavera
schema.
Password and Confirm Password. Enter the password to the specified user
account in the Password and Confirm Password fields.
Port. Enter the port number Oracle uses. If this instance uses the default port
number (1521), accept the default value.
Database Instance. Enter the name, or system ID, of your Oracle instance.
This value is sometimes referred to as the SID.
Database Alias. Enter the name of a database alias pointing to the Oracle
instance you specified in the Database Instance field. For information about
creating a database alias, refer to the Oracle documentation.
Do you want to run scripts to create the database schema? Select Yes to
indicate that you want to run the scripts that create the core database schema.
For more information about the required schemas, refer to RDBMS

This window prompts you to identify the Microsoft SQL Server and database
that will store the Delivery Manager database. All MS SQL Server database
identification windows include the fields described in Primavera Core
Database: MS SQL on page 91.
Depending on the components you are installing locally, this window may also
include either:
A Skip DM check box or a radio button set that indicates whether you
implement DM. Select Skip DM when installing reports or the analytic
applications if you do not implement DM.
A radio button set indicating whether the schema scripts should be run
against this database.
If you use DM, you should also install the Import/Export Connectors component.

Data Mart Database
This window prompts you to identify the RDBMS that will store the Data Mart
schema. By default, the name of this database is target.
This window varies, depending on the RDBMS type you specified in the
RDBMS Type window. For general information about the meaning of each field,
refer to:
Primavera Core Database: MS SQL on page 91
Primavera Core Database: Oracle on page 93
Depending on the components you are installing locally, this window may
include either:
A Skip Data Mart check box or a radio button set that indicates whether
you implement Data Mart. Select Skip Data Mart when installing reports if
you do not implement Data Mart.
A radio button set indicating whether the scripts should be run against this
database.

Management of transfers between databases depends on the database type:
MSSQL-to-MSSQL. Managed by Microsoft Linked Server.
Oracle-to-Oracle. Managed by Oracle Database Link.
MSSQL-to-Oracle. Managed by JDBC connections. This transfer type is

used only by Financial Manager users with an Oracle core database.
Primavera creates the Oracle Database Link and JDBC connections as needed
with no further user input. However, in order for Primavera to create the MSSQL
Linked Server, the data mart user must have either of these privileges:
System administrator privileges.
Setupadmin and securityadmin privileges.
If you prefer, you can provide the Linked Server yourself instead of relying on
Primavera to create it when needed. For information on providing the Linked
Server, refer to the Data Mart appendix in Analytic Applications.
This window prompts you to identify the RDBMS that will store the Analytic
Applications operational database. By default, the name of this database is
strategicPlanning.
This window varies, depending on the RDBMS type you specified in the
RDBMS Type window. For general information about the meaning of each field,
refer to:
Primavera Core Database: MS SQL on page 91
Primavera Core Database: Oracle on page 93
In MSSQL, the user you specify in this window must have the db_owner role.
include a radio button set indicating whether the scripts should be run against this
database. Select Yes to indicate that you want to run the scripts that create the
core database schema.
Do not run the scripts against a database that already has this schema.
For more information about the required databases, refer to RDBMS

This window prompts you for a one-word identifier for your enterprise (that is,
your company). The string cannot contain spaces or special characters. If
upgrading, use the same value as used in any previous release.
Mail Server
This window prompts you to identify the mail server host that Primavera can use
to send email messages and notifications. It must utilize SMTP (Simple Mail
Transfer Protocol). The server is used for outgoing mail only. Incoming mail sent
to a project workspaces discussions is handled by the James server.
For information, refer to When the installation wizard completes the process,
copy the license.bea file from the Primavera 9.0 media to
[bea_root]..
Web Server Host
This window prompts you to identify the computer hosting the web server that
serves the Primavera web client. Note that you must enter the computers fully
qualified domain and host name. For example, enter host1.primavera.com,
where host1 is the computer name, and primavera.com is the domain name.
be correct.
This window prompts you to identify the computer hosting the Portfolio
Management application. Note that you must enter the computers fully qualified
domain and host name. For example, enter host1.primavera.com, where
host1 is the computer name, and primavera.com is the domain name.
be correct.
include a Skip Portfolio Management check box. Select Skip Portfolio
Management when installing the server or the analytic applications if you do not
implement Portfolio Management.
Figure 3-6
MS Analysis Server
This window prompts you for information about the MS Analysis Services that
will store the OLAP cubes used by the analytic applications:
Analysis Server Host. Verify the name of the server that will store the
OLAP cubes. InstallShield automatically detects this value. Often, the server
name is the same as the computer hosting MS Analysis Services.
Analysis Server Name. Verify the name of the SQL Analysis Server that
will store the OLAP cubes. Often, the server name is the same as the
computer hosting MS Analysis Services.
If this is a SQL Server instance, then use the following format:

[SQL Server name]\[Instance name]
For example, instead of EVPROD the screenshot above would show

something similar to: EVPROD\SQLSERVER2005.
OLAP Database Name. Enter the name of the OLAP database. By default,
the name is PV_OLAP. Either accept the default or enter a different name,
depending on the name of the OLAP database you created before installing
the Primavera software. For more information on required databases, refer to
RDBMS Prerequisites on page 36.
If you are installing Data Mart, the following window appears after you enter the
OLAP Database Name and click Next.
Figure 3-7
MS Analysis Server
Select the Yes option for Do you want to run scripts to create the OLAP
schema.
The above window is not displayed if you are installing Portfolio Manager.

This window prompts you to identify the mail server host that Primavera can use
to send email messages in the event of Data Mart failure. Enter the fully qualified
host and domain name, as well as the port number, of a computer hosting a mail
server Primavera can use. In a comma-separated list, enter the email addresses to
which Primavera should send email if the Data Mart process fails.
The mail server must utilize SMTP (Simple Mail Transfer Protocol).
Currency Conversion
Figure 3-8
Currency Conversion
The conversion window prompts you to identify an exchange rate table for use
by Data Mart. When it transfers data to the target and OLAP databases, Data
Mart converts all monetary values into a single reporting currency. This requires
a companys exchange rate table that can convert each referenced currency into
the reporting currency.
Reporting Company. Enter the name of the company in your organization

structure where the preferred exchange rate table resides.
Exchange Rate Table. Enter the name of the preferred exchange rate table
that can convert all currencies in use into the reporting currency.
Reporting Currency. Enter the code of the currency in which you want
monetary values in the analytic applications to be displayed. By default, the
reporting currency is USD (United States Dollars).
If you do not know these values, you can leave the fields blank, but you will not
be able to run Data Mart until you supply them. To supply them manually, edit
the Datamart.properties file, described in the Data Mart appendix in
Analytic Applications.
Actuate
This window prompts you to identify the computer that is hosting Actuate
iServer and the computer hosting the web server that will be used to access
reports:
Report Server Volume. Enter the Actuate Server Volume. This is the name
of the encyclopedia that was created when Actuate was installed.
Fully Qualified Web Server Host. Enter the fully-qualified domain and
host name of the computer hosting the web server that will be used to access
reports. For example, enter host3.primavera.com.
Sometimes, both the reports and the web client are accessed using the same
web server, which is installed on the server application host.
HTTP Service Port. If the Actuate HTTP Service uses the default port
number, accept the default value (8700). Otherwise, enter the port number
the HTTP Service uses.
Collaboration Service
Figure 3-9
Collaboration Service window
When you are installing the connectors on a computer that does not also host the
collaboration software, you are prompted whether you plan to use collaboration.
If you plan to use the collaboration functionality, click Yes. If you have not
installed WorkSite MP and do not plan to use collaboration, accept the default,
which is No.
For more information about collaboration, refer to WorkSite MP Server on
page 329.
Collaboration Server
Figure 3-10 Collaboration Server

When you configure collaboration, InstallShield prompts you to identify your
WorkSite MP server:
Fully Qualified Host Name. This is the fully qualified domain and host
name of the computer hosting WorkSite MP. For example, enter
host4.primavera.com, where host4 is the computer name, and
primavera.com is the domain name. Carefully review the default name
displayed in this field. While InstallShield attempts to supply the correct host
and domain name, the default value may not be correct.
Server Name. This is the name of the server you created for use with
Primavera. For information, refer to WorkSite MP Server on page 329.
Cluster Name. This is the top-level object displayed in the WorkSite MP

Configuration Manager. By default, it has the same name its host.
Library Name. This is the name of the library you created. Generally, you
can accept the default. For information, refer to WorkSite MP Server on
page 329.
Facility Name. Accept the default value.
Collaboration System Users
Figure 3-11 Collaboration Users

When you configure collaboration, InstallShield prompts you for the user names
and passwords used by several WorkSite MP system users. These users are
created with the default passwords when you install WorkSite MP. If you have
not changed these user names or passwords in WorkSite MP Server, you can
accept the default values in this window.
If you have changed the user names or passwords of the proxy user, admin login,
or cache manager, you must supply the new values in this window.
Summary
The Summary window displays the selected components and the necessary disk
space. Click Next in this window to start copying files and configuring software.
Database Progress
While it updates your databases, InstallShield provides real-time information
about its activity. The Database Progress window is read-only. When the
databases are updated, the window is automatically replaced by the Summary
window.
Results
The Results window displays the components that were successfully installed
and the disk space they required or it displays an error. Review the information
displayed, and click Finish in this window to exit InstallShield.
3.8.2
Server Setup
The Server setup type installs the core server in the local computer. This setup
type includes the following:
Welcome
License Agreement
Install Directory
Setup Type
Component Selection
BEA WebLogic
Program Folder
RDBMS Type
Access Protocol
Mail Server
Web Server Host
Actuate
Summary
Results
Each of these screens is described in Full Setup on page 84.
3.8.3
Reports Setup
The Reports setup type installs Primaveras Actuate reports in the local
computer. This setup type includes the following:
Welcome
License Agreement
Install Directory
Setup Type
Component Selection
RDBMS Type
Access Protocol
Data Mart Database
Actuate
Summary
Database Progress
Results
3.8.4
Analytic Applications Setup
The Analytic Applications setup type installs the Data Mart and Portfolio
Management in the local computer. This setup type includes the following
windows:
Welcome
License Agreement
Install Directory
Setup Type
Component Selection
BEA WebLogic
Program Folder
RDBMS Type
Access Protocol
Data Mart Database
Server Application Host Name
Currency Conversion
Summary
Database Progress
Results
3.8.5
Data Mart Setup
The Data Mart setup type installs Data Mart to the local computer. This setup
type includes the following windows:
Welcome
License Agreement
Install Directory
Setup Type
Component Selection
Program Folder
RDBMS Type
Data Mart Database
Currency Conversion
Summary
Database Progress
Results
3.9
Installing the Clients
The following sections describe installation of client software for your end-users.
Users can install the clients they need through the Primavera core application
interface.
Most of your end-users do not need to install anything on their computers, other
than a supported browser. However, users who require administrative access to
Primavera, users of ProjectLink, and resources who report time and expenses
offline must install Primavera clients.
Users need the appropriate permissions to install clients. You can define these
permissions for the enterprise through the Security and Accounts Manager
application. Refer to Access Control for Client Downloads on page 203.
This section describes:
Installing Primavera Desktop Clients, including the Configuration

Application and the Security and Account Manager.
Installing ProjectLink, including the client and the extended functionality

macros.
Installing Offline Time and Expenses
Importing a Certificate for SSL
For information about the Primavera API client components, refer to the
documentation in the archive downloaded from the web client Options page.
3.9.1
Installing Primavera Desktop Clients
The server application and web clients must be functioning before you can install
the desktop clients.
To install the desktop clients:
1.
After logging into the web client, click Options in the top left corner.
The Options page appears.
2.
In the Install Client Components pane, click Install next to Primavera

Clients.
3.
You are prompted to open the installation or save it to your computer.
4.
Click Open.
5.
In the Welcome window, click Next.

The Software License window appears.
6.

The Choose Destination Location window appears.
7.
Choose the installation location for Primavera. The default location is

C:\PrimaveraClients. To install Primavera in a different location, click
the Browse button, choose a folder, and click OK.

8.
Click Next.
The Select Program Folder window appears.
9.
By default, a Primavera program folder is created. Choose this default or

enter a name to create a new folder.
10. Click Next.

The Connectivity window appears.
11. If your enterprise uses SSL, enable the SSL check box.
If you enable the SSL check box, you may need to import a certificate, as
described in Importing a Certificate for SSL on page 118.
12. Enter the name of the computer hosting the web server.
13. Enter the port number of the computer hosting the web server.
Depending on whether you use SSL, InstallShield supplies the default port
number for your configuration. Change it if the application server uses a
non-default port number.
14. Click Next.
The Start Copying Files window appears. The installation settings you
selected are displayed in a read-only window.
15. Review the settings. If you prefer different settings, click Back.
16. When you are satisfied with the installation settings, click Next.
The file-copy process begins. To quit the installation, click Cancel.
When InstallShield has finished copying the files, a Summary window
provides details regarding each of the components you have installed.
17. Click OK to exit InstallShield.
The clients are installed.
3.9.2
Installing ProjectLink
ProjectLink is an add-on to Microsoft Project. It relies on the Microsoft .NET

Framework, which must be installed on every computer on which ProjectLink
will run.
To install the .NET Framework, the user runs dotnetfx.exe, a copy of which
is in [PRIMAVERA]\docroot\setups. For more information about the .NET
Framework, refer to Included Software on page 28.
.NET Framework must be installed on a users computer before ProjectLink.
Primavera recommends that Windows Vista users turn off User Account Control
(UAC). This allows ProjectLink to install properly.
Installing the ProjectLink Software
Installing the Extended Functionality
Installing the ProjectLink Software

The ProjectLink installation option is only available if the core application server
resides in a Windows environment.
To install ProjectLink:
1.
After logging into the web client, click Options in the top, left corner of the
window.
The Options page appears.
2.
In the Install Client Components pane at the bottom of the page, click Install
next to ProjectLink.
You are prompted to either save the self-extracting archive to your computer
or open it without saving.
3.
Click Open.
The Welcome window appears:
4.
If a previous version of ProjectLink is installed, the window indicates

that you must uninstall it. Close the installation and uninstall
ProjectLink before continuing.
If the current version of ProjectLink is installed, the window prompts

you to repair or remove the application. Either repair the installation or
click Cancel.
If the Microsoft .NET Framework is not installed, you are prompted to

install the .NET Framework. Exit the setup and run the dotnetfx.exe
file, which is found in the docroot\setups directory under the
directory where you installed the Primavera server application.
Click Next.
5.
Click I Agree if you accept the license agreements terms.
6.
Click Next.
The Select Installation Folder window appears, displaying the default
installation directory.
7.
To install ProjectLink to a different location, click the Browse button,

choose a folder, and click OK.
8.
Indicate whether you want to install ProjectLink for all users of this
computer or only for your profile.
9.
Click Next.
The Primavera Server Settings window appears.

10. In the Server Host field, enter the name of the computer hosting your
application server.
If your enterprise uses SSL, this must be the fully-qualified domain and host
name. Additionally, if the certificate was issued by an internal authority, the
certificate must also use the same fully-qualified domain and host name.
11. In the Server Port field, accept the default, unless your enterprise uses SSL.
For SSL, use port 443.
12. Click Next.
The Confirm Installation window appears.
13. Click Next.
14. When the Installation Complete window appears, click Close.
ProjectLink is installed on your computer.
Installing the Extended Functionality
ProjectLink includes an API for Visual Basic for Applications (VBA) macros
running in Microsoft Project. A programmer familiar with VBA, Microsoft
Project, and Primavera can use the API to write macros that enhance
functionality. A Microsoft Project module of sample macros is also installed, to
be used as a guide for developing your own macros. Note that the sample macros
have the locale set to US. For details of the API and sample macros, refer to
ProjectLink API on page 379.
To make the extended functionality available to your users:
Distribute and install your macros to your end-users computers. The macros
must be installed on the end-users computers before you enable them in
Primavera.
Install your macros in the Primavera installation folder and enable them. See
Project Integration Options on page 165.
Extended functionality must be deployed to all your ProjectLink users and enabled
nearly simultaneously. Users cannot run the macros until they are installed on all
of the ProjectLink hosts in the production environment. Further, ProjectLink
cannot run if the macros are enabled before they are installed on all ProjectLink
hosts.
To install the ProjectLink macros:
1.
Save the macros in the file

[PRIMAVERA]\docroot\setups\PvEPMModule.mpp.
2.
Distribute the file PvEPMModule.mpp to all ProjectLink users.

If you do not use a push solution, distribute and install the macros manually
for each user of Projectlink:
In Microsoft Project, set the security level to Medium or Low,

depending on your enterprises security policy. To set the security level,
follow the instructions in your version of Microsoft Project. Project may
display a window asking if you want to enable macros. Enable them.
In Windows Explorer, double-click the macro file to open it.
In Microsoft Project, save the PvEPMModule project and exit from

Project.
You must save and exit in order to complete the installation.
Depending on how you distribute the macros, you might advise your users that the
macros cannot be used until they are installed on all computers properly. Advise
your users when the macros can be used.
You must also enable the macros, as described in Project Integration Options
on page 165.
3.9.3
Installing Offline Time and Expenses
The Offline Time and Expenses installation option is only available if the core
application server resides in a Windows environment.
To install Offline Time and Expenses, download the setup executable from the
web clients Options page, run the executable without saving it to your hard
drive, and follow the on-screen instructions.
3.9.4
Importing a Certificate for SSL
If you implement SSL (Secure Socket Layer) encryption, and you use your own
trusted authority to issue certificates, the root certificate for that authority must
be imported on any computer hosting ProjectLink, Offline T&E, the web client,
the Security and Account Manager, and the Configuration application. These
instructions assume you are using IE.
The process varies depending on the client software:
Desktop Clients and Offline T&E
ProjectLink and Web Client
If you use the API client components and need to access Primavera using
HTTPS, the steps you take depend on the custom application you create.
Desktop Clients and Offline T&E

To add a certification to the keystore:
1.
Copy the certificate into the bin directory under the root of the desktop client
or Offline Time and Expense installation. For example,
C:\PrimaveraClients\bin.
2.
On the desktop of the client host, click StartProgramsAccessories

System ToolsCommand Prompt.
3.
In the window, change directories until you are in the bin directory under the
root directory. For example, enter:
cd primaveraclients\bin
4.

manageCert -import [certification]
where [certification] is the file name of the certificate.

The new certificate is installed.
ProjectLink and Web Client

To install a trusted authority certificate:
1.
With SSL enabled for the server application, visit the Primavera web client
by entering its URL into your browser.
A security alert prompts you to continue, stop, or view the certificate.
2.
Click View Certificate.

The Certificate window displays details about the leaf-level certificate.
3.
4.
Select the Certificate Path tab.

Select the root of the certificate.
The Certificate Status text box displays a message indicating that the
certificate is valid.
5.
Select the General tab.
6.
Click View Certificate.

The Certificate window displays information about the root-level certificate.
7.
Click Install Certificate.

The Certificate Import Wizard appears.
8.
Follow the wizard and accept the defaults.
9.
You are prompted whether you want to install the certificate, despite the fact
that the browser cannot validate the certificate.
10. Click Yes.

11. Click OK to acknowledge the successful importation of the certificate.
3.10
Post-Installation
This section describes tasks that you may need to perform after a successful full
installation.
3.10.1
Disable Remembered Time and Expense Values
This task is optional. The default behavior for remembered rows in Time &
Expense carries forward time hours and expense costs to the next report. You can
disable this feature.
To disable the functionality so hours and costs are not brought forward in
remembered rows:
1.
Make a backup of
[Primavera Root]\cfg\appserverconfig.properties.
2.
Edit appserverconfig.properties with Notepad or another editor.
3.
To disable the functionality with time remembered rows, add the following
parameter to the end of the file and set it to false:
app.TERememberTimeHours=false
4.
To disable the functionality with expense remembered rows, add the

following parameter to the end of the file and set it to false:
app.TERememberExpenseValues=false
5.
Restart the core server for the changes to take effect.
To re-enable the functionality, repeat these steps and set either parameter value
above to true, or remove the parameter. Removing the parameter automatically
re-enables the functionality.
3.10.2
Final Steps to Enable Portfolio Manager
After you install Weblogic 10.0 MP1, you must follow the procedure given
below to allow the application to access Primavera JDBC data sources in
Portfolio Manager. The steps require Primavera to be running. For instructions,
refer to Start Up.
To setup access to JDBC.
1.
Open a browser and go to the Weblogic Console (http://[BEA_host]:7001/

console).
2.
Go to Services and click Work Contexts.
3.
Click New.
4.
Enter weblogic.app.internal.AdminMode in the Path field and read

in the Action field.
5.
Save the work context.
6.
Click the work context that you created in the above steps.
7.
Click Add Conditions in the Policies tab.
8.
From the Predicate list select Group and click Next.
9.
Enter everyone in the Group Argument Name field and click Add.
10. Click Finish.

Ignore any group not existing error message.
11. Click Add Conditions again.
12. From the Predicate list select User and click Next.
13. Enter pmbiuser in the User Argument Name field and click Add.
14. Click Finish.
15. Click Save to save the work context.
After configuring the work context for JDBC access, restart the Primavera server.
3.11
Third-Party Post-Installation
Requirements
This section describes the third-party installation procedures that you may need
to perform after a successful full installation.
3.11.1
WSDL4J Installation
This procedure is required for all Primavera servers and any instance of the
Primavera API client.
After you install Primavera, install version 1.6.2 of WSDL4J.

To install WSDL4J.
1.
Open a browser and go to http://sourceforge.net/projects/wsdl4j (location at

the time of publication of this document).
2.
Download version wsdl4j-bin-1.6.2 of WSDL4J.

You need to extract the wsdl4j zip file to a temporary location.
3.
Copy the wsdl4j.jar file from the temporary location to the following path:
[Primavera Install Directory]/lib/ or
In case of Primavera API client, copy the wsdl4j.jar file to the following
path:
pvapi/common/axis/lib
After copying WSDL4J, restart the Primavera server.
3.11.2
Hibernate2 Installation
This procedure is required if you are using Portfolio Manager. It must be installed
on the Portfolio Manager host only.
After you install Primavera and before you start the server, install version 2.1.4 of
Hibernate2.
To install Hibernate2.
1.
Open a browser and go to http://sourceforge.net/project/

showfiles.php?group_id=40712&package_id=72467
(location at the time of publication of this document).
2.
Download version 2.1.4 of hibernate2.

You need to extract the hibernate-2.1.4 zip file to a temporary location.
3.
Copy the hibernate2.jar file from the temporary location to the following
path:
[Primavera Install Directory]/lib/
After copying Hibernate2, start the Primavera server.
Section 2
Primavera Administration
Start up and Shutdown
4.
This chapter describes procedures for correct start up and shutdown of

Primavera.
These instructions assume that the RDBMS is already running. For instructions
on starting and shutting down MS SQL Server or Oracle, refer to the associated
documentation.
Each component is discussed in the following sections:
Start Up
Shutdown
Windows Log Files
For instructions on starting and stopping Actuate, refer to the associated

documentation.
4.1
Start Up
Start the Primavera components in this order:

1.
Starting the WorkSite MP Server

For instructions on WorkSite MP Server, refer to WorkSite MP Server
on page 329.
2.
Starting the Primavera Server Application
3.
Starting the Primavera Client
Ensure that the Actuate server and Web server are running. For instructions on
starting Actuate and Web Server, refer to the associated documentation.
Any services configured to start automatically at boot can be ignored.
4.1.1
Starting the Primavera Server Application
These instructions vary, depending on whether the server application was

installed as a service. Starting Primavera automatically starts the application
server and the analytic applications (if they are installed locally).
To manually start the Primavera server application:
1.
On the desktop of the server application host, select

StartProgramsPrimavera Primavera Server.
2.
If you are unsure whether the server application is running, select the
Primavera Server option on the Windows taskbar.
The Primavera Server command prompt window appears.
Figure 4-1
Primavera Start Up in BEA WebLogic
Text scrolls down the window. When the message 1127.0.0.1 maps to
multiple IP addresses appears, the server application is running.
To start the server application as a service:
1.
Select StartSettingsControl PanelAdministrative ToolsServices

from the desktop of the server application host.
The Services window appears.
2.
From the Services scrolling region, select beasvcprimavera_myserver.

If the word Started appears in the Status column, the server application is
already running, and you do not have to continue.
3.
Click the Start button.

The Services Control window appears. After a few moments, the Services
Control window disappears, and the word Started appears in the Status
column next to Primavera Server.
To determine whether the server has started successfully, open the

primavera.log file and locate this message: Server started in RUNNING
mode. For more information, refer to Windows Log Files on page 136.
Refer to Unable to Start the Server Application on page 356 if you
encounter problems.
If the analytic applications are installed on a dedicated host, start them after the
application server. Start them in the same manner as you started the core
application server (for example, StartProgramsPrimavera Primavera
Server).
4.1.2
Starting the Primavera Client
Before starting the Primavera client, ensure that the web server and server
application are running. Users connect to Primavera either through the web client
or through a desktop client, depending on the nature of their work:
Users who must configure foundation data or access control connect to

Primavera through a desktop client, either the Security and Account
Manager or the Configuration application.
Users who must view and update business objects, review analytic
information from PM, and interactively report time and expenses connect to
Primavera through a browser.
Users of ProjectLink and the Offline Time and Expenses application connect
to Primavera during synchronization. For more information about starting
these applications, refer to the ProjectLink Guide or the Offline Time and
Expenses help.
Anyone logging into a new implementation of Primavera must use the desktop
client.
The following sections describe the process of starting these Primavera clients:
Starting a Desktop Client
Starting the Web Client
Starting a Desktop Client

To start a Primavera desktop client:
1.
On the desktop, select StartProgramsPrimaveraConfiguration

Application.
You can also start the Security and Account Manager (StartPrograms
PrimaveraSecurity and Account Manager).
The Primavera login window appears.
Figure 4-2
Primavera Desktop Client Login Window
If this window does not appear, refer to Unable to Start the Desktop
Client on page 358.
2.
In the login window, enter the login name admin and the password admin.
This account has global access to Primavera.
If you entered a valid account ID and password, a Primavera window
appears. If this is the first time a desktop client has been started against the
server application, the Administrator Configuration window also appears.
Figure 4-3
Administrator Configuration Window
This window only appears the first time a desktop client connects to the
server application. This is the only opportunity to specify the autogeneration setting. You must specify whether resource IDs are automatically
created.
3.
4.
In the Administrator Configuration window, enable the Auto Generated

check box.
Specify a starting number and increment number.
If you do not specify automatic generation, the Resource Identification
Number field is required in order to save resource profiles.
This setting determines whether and how Resource IDs are generated; it has
no effect on the generation of Login IDs for resources.
The application you are starting (either Security and Account Manager or
Configuration) appears.
5.
Either make updates in the selected desktop client, or exit it as described in

Stopping the Primavera Client on page 133.
Starting the Web Client

To log into Primavera through the web:
1.
In a supported browser (refer to Certifications on page 419), enter the

Primavera URL (refer to Primavera URL on page 61).
The Primavera Login page appears.
Figure 4-4
2.
Primavera Login Page
On the login page, enter the login name admin and the password admin.
This account has global access to Primavera.
The Start page appears.
Immediately upon logging in the first time, Primavera recommends that you
change the admin accounts password. Refer to Changing a Password on
page 262
If you receive an error or cannot log in, refer to Troubleshooting on page
355.
4.2
Shutdown
When shutting down the Primavera application, shut down the components in
this order:
1.
Stopping the Primavera Client
2.
Stopping the Primavera Server Application
3.
Stopping the WorkSite MP Server
Ensure that Actuate is not running. For instructions on stopping Actuate, refer to
the associated documentation. Stop the web server, if necessary. For instructions,
refer to the documentation provided with your web server.
Any services configured to start automatically at boot can be stopped from the
Services window. However, they will shut down properly before the host powers
down.
4.2.1
Stopping the Primavera Client
To stop the Primavera clients:
Click FileExit in the Configuration or Security and Account Manger

applications.
Click Logout on the top left corner of any page to stop the Primavera web
client or Offline Time and Expenses.
Exit Microsoft Project to exit ProjectLink.
4.2.2
Stopping the Primavera Server Application
Before you stop the server application, ensure that all clients are shut down.
When you shut down the server application, connected clients are disconnected
and any open database transactions are rolled back. Shutting down Primavera
also stops the application server that hosts it.
To shut down the server application:
1.
2.
On the desktop of the server application host, select

StartProgramsPrimavera Shutdown Primavera Server.
If you are unsure whether the server application has shut down, verify it:
If you started the server manually, refer to your Windows taskbar. If the
Primavera Server Application option appears, the server has not yet shut
down. The Primavera Server Application option should disappear
promptly.
If you started the server as a service, Select StartSettingsControl

PanelAdministrative ToolsServices from the desktop of the
server application host and locate the Primavera Server in the Services
scrolling region. If nothing appears in the Status column, the server
application has shut down properly.
If the analytic applications are installed to a dedicated host, stop them before the
application server. Stop them in the same manner as you stopped the core
application server (for example, StartProgramsPrimavera Shutdown
Primavera Server).
4.2.3
Stopping the WorkSite MP Server
Do not stop the WorkSite MP server while the Primavera server application is
still running. If users are added while WorkSite MP is not running, you must add
the new users to WorkSite MP, as described in Synchronize Users on page
164.
To stop the WorkSite MP server:
1.
On the desktop of the WorkSite MP server host, select StartPrograms

Interwoven WorkSite MP Server Stop IMPM.
2.
If you are unsure whether WorkSite MP has stopped, open the Windows
Task Manager by right-clicking an empty space on the Windows taskbar, and
clicking Task Manager.
3.
On the Processes tab, locate the following services to ensure that they do not
appear:
4.
imcms.exe
imindexer.exe
imjames.exe
impm.exe
Exit the Task Manager.
WorkSite MP is successfully stopped.
4.3
Windows Log Files
Because Primavera relies on third-party software, a number of log files are

written when Primavera is run.
In Windows, you can view the logs created by WorkSite MP by clicking
StartProgramsInterwoven WorkSite MP ServerLog Viewer.
Table 4-1
Logs When Run in BEA WebLogic
Component
File Name
Location
Primavera Core
serverlog.txt
Defaults to the root of the

Primavera installation. Location
and name are set using the
Administration application.
BEA WebLogic
primavera_myserv
er_serviceoutput
.log
[PRIMAVERA]\j2ee\
weblogic\primavera\
servers\myserver
primavera.log
access.log
myserver.log
[PRIMAVERA]\j2ee\
weblogic\primavera\
servers\myserver\logs
Data Mart
DataMart.log
[PRIMAVERA]\datamart\logs
OLAP
PVOLAP.log
[PRIMAVERA]\datamart\logs
WorkSite MP
cms.[xxx].log, where
[xxx] is a unique
identifier.
[WorkSiteMP]\worksite
server\logs\[primavera]
Desktop
Clients
clientlog.txt
Found in the root of the

installation.
When a server implemented in WebLogic is started manually, all output is written

to the console. In all cases, the data are also written to one of these files:
Primavera server messages are written to the console output file.
WebLogic server messages (including the message, Server started in

RUNNING mode, which indicates a successful start) are written to the
primavera.log file.
Messages from internal applications, such as PM, are written to

myserver.log.
Using the Administration Tool
5.
The Administration Tool stores values you entered during Primavera installation.
You can edit values for server and client information, such as the names and
locations of the database server, server application, web server, and the mail
server.
To start the Administration Tool, select StartPrimaveraPrimavera
Administration from the desktop of the client or server application host. The
Primavera Administration window appears. The tabs in this window include the
following:
Client Options
Server Options
Core Database Options
DM Database Options
Authentication Options
These tabs are only displayed if the corresponding component was installed on
this host. For example, the Server tab is available from the server application
host.
5.1
Client Options
Access the Client tab from a computer hosting the Security and Account
Manager or Configuration application.
Figure 5-1
Client Administration Options
You can configure the following values:
SSL. Enable this check box if your enterprise uses Secure Socket Layer
(SSL) encryption.
Typically, the Server Port field defaults to the correct value, depending on
whether you enable the SSL check box: 80 if it is disabled and 443 if it is
enabled. If you use a non-default port number, specify it. For more
information, refer to Importing a Certificate for SSL on page 118
Web Server Host Name. This is the name of the computer hosting the web
server that serves the Primavera web client.
Web Server Port. This is the port number of the computer hosting the web
server that serves the Primavera web client.
Web Browser. This is the path and filename of the web browser that this
client uses to display web content and help.
Console Output File. Informational and error messages regarding the client
are written to this file.
If a firewall separates clients from the application server or web server, you must
open the correct ports in the firewall.
5.2
Server Options
Access the Server tab from the server application host.
Figure 5-2
Server Administration Options
You can configure values in these panes:
Console Output File. Informational and error messages regarding the server
application are written to this file.
Servers
Web Components
5.2.1
Servers
Mail Server. This is the mail server that Primavera uses to send messages to
users who specify Email as their message delivery method. The server must
use SMTP.
RDBMS Connection Pool Size. This is the number of connections to the

RDBMS that the server application opens. Most enterprises should use the
default value.
5.2.2
Web Components
Use SSL Security. Check this box to enable Primavera to utilize Secure
Socket Layer (SSL) encryption for the web client. In addition to checking
this box you must configure your web server to use SSL encryption, and in
some cases, import your root certificate into the client web browser. For
more information, refer to Enabling SSL Support on page 54 and
Installing the Certificate on page 54.
Web Server Host. This is the external name of the computer hosting the
web server used by Primavera web clients. It is also used by the desktop
clients, Offline Time and Expenses, and ProjectLink. Note that this name
may be different from the local Domain Name Server (DNS) name. Use the
fully qualified host name when specifying the web server host.
Qualifications Warning Threshold. This threshold represents a number of

qualifications selected for edit in the Primavera web client. A user receives a
warning for attempting to edit more than the number of qualifications
specified here. Regardless of this warning, the user can continue.
5.3
Core Database Options
Access the Core Database tab from the server application host. The fields on this
tab vary, depending on whether you indicate MS SQL Server or Oracle as your
RDBMS type.
5.3.1
MS SQL Server
Figure 5-3
Core Database Options, MS SQL Server
You can configure these values:
Database Type. This is the type of RDBMS that contains the Primavera
database. Primavera supports both MS SQL Server and Oracle.
Database Name. This is the name of the database that contains the
Primavera schema (PVDB by default).
ID. This is the account that Primavera uses to connect to the database server.
This accounts permissions in the PVDB database should be comparable to
the database owners (DBOs) permissions.
Password. This is the password associated with the account listed above.
Confirm Password. Reenter the password to confirm that it is entered

correctly.
Instance Name. This is the name of the MS SQL Server instance. Typically,
this is the name of the computer hosting the RDBMS.
Port. This is the port number your MS SQL Server uses. Change this value
if you do not use the default port (1433).
5.3.2
Oracle
Figure 5-4
Core Database Options, Oracle
Database Type. This is the type of RDBMS that contains the Primavera
database. Primavera supports both MS SQL Server and Oracle.
ID. This is the account that Primavera uses to connect to the Oracle instance.
It must be the user that owns the Primavera schema (PVDB by default). For
information about creating this user, refer to User Creation Script on
page 306.

correctly.
Host Name. This is the name of the computer hosting your Oracle instance.
Port. This is the port number your Oracle instance uses. Change this value if
you do not use the default port (1521).
Database Instance. This is the name, or system ID, of your Oracle instance.
This value is sometimes referred to as the SID.
5.4
DM Database Options
Access the DM Database tab from the server application host.
Figure 5-5
DM Database Options
Primavera strongly recommends that all server applications in an installation use

identical DM Synchronization settings.
Database Type. This is the type of RDBMS that contains the DM database
(MS SQL Server only).
Database Name. This is the name of the database that contains the DM
schema (DMDB by default).
ID. This is the account that Primavera uses to connect to the database server.
This accounts permissions in the DMDB database should be comparable to
the database owners (DBOs) permissions.

correctly.
Instance Name. This is the name of the MS SQL Server instance. Typically,
this is the name of the computer hosting the RDBMS.
Port. This is the port number that your MS SQL Server uses. Change this
value if you do not use the default port (1433).
Automatic Synchronization. Enable this check box to have data

automatically transferred to the DM database.
Note that, with the exception of time and expenses, all pertinent data is
committed simultaneously to both the PVDB and DMDB databases. To
transfer the entire set of DM data from Primavera, follow the procedure
described in Manual Synchronization on page 347.
T&E Starting Hour. Enter the hour of the day when synchronization should
start. Enter the hour in 24-hour clock format (that is, as a whole number
between 0 and 23).
T&E Starting Minute. Enter the minute of the hour when synchronization
should start.
T&E Interval. Enter the number of minutes between synchronization. The

larger the value you enter, the less frequently the databases are
synchronized. The maximum interval is 10080 (equivalent to one week).
For more information about synchronization options, refer to DM

Synchronization.
5.4.1
DM Synchronization
If you have implemented the Delivery Manager (DM) solution, Primavera

automatically synchronizes the DM database. Synchronization ensures that the
most recent information is available in DM.
Enable the Automatic Synchronization check box to have Primavera
automatically synchronize time and expenses with the DM database at the
interval you specify. For example, if you set the T&E Interval to 60, Primavera
will synchronize the DM database once every hour.
If necessary, you can also specify a starting hour and starting minute. This setting
allows you to indicate when during the day the synchronization happens. These
settings are useful when your interval is longer than a day. For example, if you
set the interval to 1440 (equivalent to one day), and then set the T&E Starting
Hour to 23 and the T&E Starting Minute to 30, synchronization will occur
daily at 11:30 PM.
The frequency with which data should be synchronized depends on the level of
activity in Primavera and any constraints on the Primavera and RDBMS hosts.
Primavera recommends setting the T&E Interval between 5 and 15.
For more information about synchronization, including notifications and transfer
rules, refer to Synchronization on page 340.
Force the asynchronous transfer of data from PVDB to DMDB by navigating to the
web clients Monitor Server page, and clicking parasyncfire.
5.5
Access the Authentication tab from the server application host. Authentication is
the process of verifying the identity of a user during login. You can configure
Primavera to authenticate users login names and passwords through Primavera,
through an LDAP server, or both. Note that all login IDs must exist in the
Primavera application. For information regarding the version of the LDAP
supported by Primavera, refer to Certifications on page 419..
Figure 5-6
General Options
Login
Distinguished Name Resolution
Authentication and Login IDs
5.5.1
General Options
These options determine the authentication method Primavera uses:
Use Primavera Authentication. Checking this box instructs Primavera to

use its own authentication method. Login names and passwords are
authenticated against Primavera user accounts. If you disable this option,
passwords cannot be changed in Primavera and the resource profiles Login
ID field is required. See Authentication and Login IDs on page 154.
The admin account is authenticated through Primavera, even if Use Primavera

Authentication is disabled, ensuring that Primavera is always accessible.
Use LDAP Authentication. Enabling this box instructs Primavera to

authenticate login names and IDs through an external LDAP system.
Regardless of this setting, access control must still be defined in Primavera.
Enable Secure Connection (SSL). Enabling this box instructs Primavera to

use Secure Socket Layer (SSL) encryption when contacting the LDAP
server. Note that this connection is between the server application and the
LDAP server; no connection is made between the client and LDAP.
If you enable this option, Primavera accesses the correct trusted Certificate
Authority (CA) root certificate before connecting to the LDAP server. Your
Primavera server application installation includes a keystore that contains
many widely-used CA root certificates. If your server requires a different
CA root certificate, you must install the correct certificate, as described in
Installing the Certificate on page 54.
Directory Server. Enter the name of the LDAP server to which Primavera
can connect.
If your LDAP server does not use the default port number, append the port
number to the server name, delimited by a colon. For example, Server:500
indicates an LDAP server named Server with a port number of 500.
If you use both Primavera authentication and LDAP, during login:
LDAP is checked first.

If a matching login and password are found in the LDAP database,
authorization succeeds (access is granted).
If the login is found in the LDAP database, but the passwords do not match,
authentication fails (access is denied).
If the login is not found in the LDAP database, Primavera is checked.

If a matching login and password are found in Primavera, authentication
succeeds. Otherwise, it fails (access is denied).
5.5.2
Login
If you enable LDAP authentication, Primavera must connect to the LDAP server
to authenticate logins and passwords. The following options determine how
Primavera contacts the LDAP server:
Use Anonymous Login. Checking this box instructs Primavera to connect to

the LDAP server using the anonymous login facility. If you do not check this
box, you must provide a login name and password that Primavera can use.
Name. If you choose not to use anonymous login, enter the distinguished
name of the LDAP account Primavera can use to connect to the LDAP
server. Specify an account with limited privileges in the LDAP server.
Password. Enter the password associated with the account listed above.
Confirm Password. Reenter the password to ensure that it is correct.
5.5.3
Distinguished Name Resolution
If you use LDAP to authenticate logins and passwords, you must specify a search
base, which indicates how LDAP finds the distinguished name of the user in
order to authenticate the password:
Search Base. This is the directory that LDAP recursively searches during
authentication.
UserID Attribute. This is the LDAP object attribute name that contains the
users login ID. The default is uid.
Objectclass Attribute. This is the LDAP object class of the authenticatable

user object in the LDAP database. The default is person. Only objects of this
class are searched.
Authentication succeeds if the UserID attribute value, Objectclass attribute value,

and password of the specified object class match exactly those found in the
LDAP server.
5.5.4
Authentication and Login IDs
When users create resource profiles, they can enter the login ID that the resource
will use to access Primavera. If LDAP authentication is not enabled, they can
leave the field blank to have Primavera generate a login ID.
Once an accounts Login ID is specified, it can only be changed by accounts with
the Administrator role.
The type of authentication method used by Primavera determines the way that the
Login ID field on resource profiles is populated:
Primavera Authentication
LDAP Authentication
Primavera Authentication
If you are using Primavera authentication, users can leave the field blank to have
Primavera generate a login ID, or they can provide a unique ID. If the field is
blank when the profile is saved, the user is prompted to either provide an ID or
allow Primavera to generate one.
Generally, users should allow Primavera to generate an ID. If you do not want to
use Primavera-generated IDs, consider mandating login IDs or publishing login
ID guidelines to ensure consistency.
Primavera generates login IDs by appending the resources last name to the
resources first initial. For example, the login ID generated for John Smith is
JSmith. If a second resource named John Smith joins your enterprise, his login
ID is generated by combining the first initial, last name, and resource ID
(JSmith_EV_RS_000324). During authentication, login IDs are not casesensitive, but passwords are.
LDAP Authentication
If you are using LDAP, give your users the correct IDs for the new resources they
must add.
If you use LDAP, but some of your users do not have LDAP IDs, you can also
use Primavera authentication. Note that Primavera-authenticated IDs cannot be
identical to LDAP IDs. If a Primavera-authenticated ID matches an LDAPauthenticated ID, only the LDAP password is accepted.
The admin account is always authenticated through Primavera, even if you only
enable LDAP. This ensures that Primavera is always accessible by the admin
account.
If Primavera relies entirely on LDAP, passwords (other than the admin accounts)
cannot be changed in Primavera. If both methods are enabled, password changes
made in Primavera by users with LDAP logins have no effect.
Web Administration
6.
Web Administration
The web clients Admin page provides convenient access to information and
functionality that help maintain Primavera:
Flush Web Client Caches
Monitor Server
Active Web Sessions
Login Auditing
ID Formats
Synchronize Users
Project Integration Options
Staffing Request Options
Administer Groups and Roles
Third-party T&E Options
Field-level Resource Profile Privileges
Language Authorization
The Main Menu Admin link is only available to users with the Administrator
access role.
Web Administration
6.1
Flush Web Client Caches
When you add values in the Configuration application (such as those listed in
6-1), the new values are not immediately available in the web client. Flush the
web client caches to ensure that the new values are made available to end-users.
The operation refreshes the configuration data listed in table 6-1.
Table 6-1
Data Refreshed When Web Client Caches Are Flushed
Account Owner Types
Final Outcomes
Client Contact Influencer

Types
Lead Source Types
Client Contract Status
Market Categories
Client Industry
Off-time (non-project) Commitment Types
Client Priority
Project Priorities
Client Status
Project Types
Currencies
Qualifications (add or remove)
Engagement Types
Schools
Exchange Rates
Services
To flush the web client caches:
1.
Log into the web client using an account with the Administrator access role.
2.
In the Main Menu, click Admin.

The Admin page appears.
3.
In the Administrative Commands pane, click Flush Caches.

After a moment, the Admin page reappears, which indicates that the cache
has been flushed.
Note that you can also flush these caches using the Clear Drop-down Cache on
the Options page.
Web Administration
6.2
Monitor Server
The Monitor Server page provides links to statistics about your Primavera server
applications. Most links display read-only information. However, the global
cache page includes a command that removes all data from the global cache. Use
this option when instructed to do so by Customer Support.
The global cache accumulates data as users request information. Once values are
added to the cache, the values can be displayed more quickly. Clicking global
cache flush all clears out the cache and leaves it empty, but it will be refilled
through normal use of the system.
You can flush the cache while the server is running, but Primavera strongly
recommends that you not do it during business hours. The operation can take
several minutes to execute, and users may experience poor performance
afterwards. This degradation lasts only until the cache is refilled.
To flush the global cache:
1.
Log in to the web client using an account with the Admin access role.
2.

3.
In the Administrative Commands pane, click Monitor Server.

The Monitor Server page appears, displaying links to pages that list various
statistics.
4.
Click global cache.

The global cache page appears.
5.
Click global cache flush all.

A warning appears, indicating that flushing the global cache will degrade
performance briefly.
6.
Click Yes to continue.

The cache global flush all page appears, and the cache is flushed.
See also Login Auditing on page 161.
Web Administration
6.3
Active Web Sessions
The Active Web Sessions page displays a list of all the web client connections to
Primavera. For each connected session, the page displays:
User Login. The login ID supplied when the computer connected to

Primavera.
Username. The name of the person associated with the login ID.
Client Host. The IP address or host name of the computer connecting to

Primavera.
Login Time. The time that the user logged in during this session.
Last Activity Time. The time of the last action taken by the user.
Last Activity URL. The URL of the last page Primavera displayed to the
user.
Visit this page to determine who is currently connected to Primavera.
Web Administration
6.4
Login Auditing
Login auditing is a security feature consistent with Sarbanes-Oxley requirements.

You have to add it to the AppServerConfig.properties file. Thereafter, you
can turn it on and off in the properties file or in the Primavera web client.
When login auditing is turned on, each web client login produces an entry like
the following in the server log file (serverlog.txt):
Oct-29-21:46:47-TRACE-Thread[ExecuteThread: '14' for
queue: 'weblogic.kernel.Default',5,Thread Group for
Queue: 'weblogic.kernel.Default'] - Login Auditing login SUCCESSFUL for: admin from host: 10.11.5.157
The entry has these components:
Timestamp
Login status (failure/success)
User Id
Host IP address
To enable login auditing:
1.
In the AppServerConfig.properties file, set the following two

properties as shown. Add the properties if they are not already in the file:
Infra.TraceFlagMgr.traceOn = TRUE
Infra.TraceFlagMgr.flag.login = 1
2.
Restart the Primavera application.
Setting the Infra.TraceFlagMgr.flag.login property to 1 turns the logging

on; setting it to -1 turns logging off. The property is read at startup only.
To turn login auditing on and off while the server is running:
1.
Log into the web client using an account with the administrator access role.
2.
Web Administration

3.

The Monitor Server page appears.
4.
On the page, click trace.

The trace pane appears.
5.
In the pane, click the appropriate trace command.

In the small pane, you can set flags for the command.
To view the log entries:
A simple script can be created to search through the server log file for lines
containing Login Auditing.
The matching lines can be copied into a separate log file for easy reporting.
Web Administration
6.5
ID Formats
Opportunities, competitors, clients, projects, resources, and agencies all have

unique identifiers (IDs). IDs must be unique within each object type. These IDs
can be imported through Primavera connectors or they can be generated within
Primavera. In the case of resources, IDs can also be entered manually. The
resource ID option is set the first time a desktop client connects to a server
application. For more information, refer to Starting the Primavera Client on
page 129.
If Primavera is integrated with external systems, such as human resources, CRM,
or financial systems, or if your enterprise has specific prefix or ID length
requirements, set them on the ID Formats page.
To specify business object ID formats:
1.
2.
3.
In the Administrative Commands pane, click ID Formats.

The ID Formats page appears.
4.
In the ID Prefix field next to Client, enter the prefix Primavera should
append when generating IDs for client profiles. Note that the prefix cannot
be more than 6 characters in length.
5.
In the Initial Length field, enter the length (that is, the number of digits) of
the generated portion of the ID. For example, if you enter 5, the generated
portion of the first client ID would be 00001.
6.
Repeat steps 4 and 5 for each other type of business object.
7.
When you are satisfied with the prefix and initial length of each type of
business object, click Save and Close.
Business objects created from this point forward have IDs generated using these
prefixes and initial lengths.
IDs are limited to a length of 20 characters (including the prefix).
Web Administration
6.6
Synchronize Users
These instructions only apply if you implement Primaveras collaboration

functionality.
When you add new users to Primavera, they are automatically added to the
WorkSite MP server so that the users can access project workspaces. However, if
users were added to Primavera while the WorkSite MP server was unavailable,
you must synchronize the new users from the Admin page.
Note that this process is triggered once a day; if the new users need immediate
access, synchronize users between the two systems.
To synchronize Primavera and WorkSite MP users:
1.
2.

3.
In the Administrative Commands pane, click Synchronize Users.

A user finder appears.
4.
Locate the users you want to synchronize, click Add Selected, and click
OK.
The Admin page reappears when the users are synchronized.
The users you selected are added to the WorkSite MP Server.
Web Administration
6.7
Project Integration Options
The Project Integration Options page in the web client (Main Menu > Admin
> Project Integration Options) allows you to enable or disable project data
synchronization with either ProjectLink or ProjectServerLink for the core
Primavera application. Both these options are enabled by default.
You define user permissions to integrate project data through the Security and
Account Manager application. Refer to Access Control on page 199.You need
to define permissions for both ProjectLink and ProjectServerLink. Project
Integration Options only allow you to turn the synchronization functionality on
or off for the core application through the web client.
ProjectLink and ProjectServerLink integration options are independent of each
other and are unavailable for user groups or pools that do not have
synchronization permissions at the enterprise level.
6.7.1
ProjectLink Is Enabled
Selecting the ProjectLink Is Enabled option allows users with appropriate

permissions to download and install the ProjectLink client and integrate data with
projects in MS Project Desktop. Disabling this option makes ProjectLink
unavailable for download.
ProjectLink includes an Application Programming Interface (API) that
developers can use to extend the functionality of ProjectLink. The API exposes
Common Object Model (COM) interfaces that can be called by Microsoft
Project macros. A set of sample macros is copied to the Primavera installation
folder with the API, but the macros are intended to be used only as a guide in
your development of macros tailored to your enterprise. They are not installed on
users computers.
The API is discussed in ProjectLink API on page 379. Installation of your
macros on users computers is discussed in Installing the Extended
Functionality on page 116.
Web Administration
Extended functionality must be deployed to all your ProjectLink users and enabled
nearly simultaneously. Users cannot run the macros until they are installed on all
of the ProjectLink hosts in the production environment. Further, ProjectLink
cannot run if the macros are enabled before they are installed on all ProjectLink
hosts.
To enable the extended functionality macros:
1.
Install the macros as described in Installing the Extended Functionality

on page 116.
2.
Log in to Primavera using an account with the Administrator role.
3.
Click Admin in the Main Menu.
4.
In the Administrative Commands pane, click Project Integration Options.
5.
On the Project Integration Options page, click the check box for
ProjectLink Is Enabled if it is not selected already. ProjectLink is enabled
by default.
6.
Click ProjectLink Options next to the ProjectLink Is Enabled link.

Note that ProjectLink Options is unavailable unless ProjectLink Is
Enabled.
7.
On the ProjectLink Options page, click each listed macro to enable it.
You can enable macros for Integration Options, Options During Open,
and Options During Save.
8.
Save and Close.

The macros are enabled.
You can also select Rules & Settings > ProjectLink Options. For more
information about the macros, refer to ProjectLink API on page 379.
Your ProjectLink users may encounter problems if they have not installed the
extended functionality, as described in Installing the Extended Functionality
on page 116.
Web Administration
6.7.2
ProjectServerLink Is Enabled
Selecting the ProjectServerLink Is Enabled option allows users with

appropriate permissions to integrate data with projects in MS Project Server.
Disabling this option makes all ProjectServerLink options in the web client
unavailable. Unlike ProjectLink, there is no client component to be installed on
the users desktop; ProjectServerLink is not a separate application that the user
needs to download and install.
Users need Update rights for projects and all rights for tasks to be able to
manually synchronize data through the web client.
The ProjectServerLink is Enabled option, which is enabled by default, allows
users with appropriate permissions to use the integration functionality:
Synchronize
Configure ProjectServerLink
New Configuration
Edit Configuration
Copy Configuration
Enable ProjectServerLink
As an administrator, you can configure ProjectServerLink either through the

Admin or the Rules & Settings option in the Main Menu in Primavera.
To install an event handler that automatically synchronizes data when an MS
Project user publishes a project, refer to Enabling MSPS Synchronization for
Primavera via an Event Handler on page 394.
Web Administration
6.8
Staffing Request Options
Staffing requests help users negotiate with each other to make assignments.
Primavera provides configuration options that allow you to control how this
feature behaves, including:
Forwarding Options. Specify whether requests can be forwarded. When it is

set to Allow User Selection, initiators determine whether each request can
be forwarded by each recipient.
Confirmation Options. Specify whether initiators must confirm assignments

for the staffing requests they send. When it is set to Allow User Selection,
initiators can choose to skip the last step of a staffing request. Primavera
automatically assigns the resource when a specific request is approved. In
the case of general requests, Primavera automatically assigns the resource if
the first reply includes a single suggestion.
The options you choose should reflect your enterprises business policy.
To edit the staffing request options:
1.
2.
3.
In the Administrative Commands pane, click Staffing Request Options.

The Staffing Request Options page appears.
4.
In the Forwarding Options pane, indicate whether initiators can allow their
staffing messages to be forwarded. Select from:
Always. Users can always forward requests; the forwarding

configuration controls are hidden from the initiator.
Allow User Selection. The initiator of a request specifies users that can
forward the request separately from those who cannot.
Never. The forwarding controls are hidden in the staffing request.
Web Administration
5.
6.
In the Confirmation Options pane, indicate whether initiators can skip the
confirmation step of the request. Select from:
Always. Initiators are never required to confirm assignments made from

specific requests they send. Confirmation messages are never sent and
Primavera automatically makes the assignment when a recipient
approves a specific request. If an initiator requests suggestions,
Primavera automatically makes the assignment if the first reply includes
a single suggestion.
Allow User Selection. The initiator of a request chooses whether to skip

the confirmation step on each request she sends.
Never. The initiator of a request must always confirm an assignment

created from a request. The automatic confirmation controls are hidden
in the web client.
Click Save and Close.
Staffing requests are now configured.
Web Administration
6.9
A user group is a collection of users that typically serve one of three purposes:
To group users for reviewing and approving work requests.
To group users who act as stakeholders on projects, issues, risks, and work
requests.
To group users for publication; when you publish content, you can specify a
user group as a subscriber.
For more information about work requests and stakeholders, refer to the online
help.
6.9.1
Creating and Assigning Groups and Roles
To create a user group:

1.
Log in to the web client using an account with the Administrator access role.
2.

3.
In the Administrative Commands pane, click Administer Groups and

Roles.
The Administer Groups page appears.
4.
Click New Group.

The New Groups page appears.
5.
Enter a Name, and optionally a Description, for the group. Group names are
required and must be unique.
To create a role:
1.
2.
Web Administration

3.

Roles.
The User Groups page appears.
4.
Click the Administer Roles tab.

The Administer Role page appears.
5.
Click New Role.

The New Role pane appears.
6.
Enter a Name, and optionally a Description, for the role. Role names are
required and must be unique.
Typically, work request roles reflect generic business functions (for
example, purchasing manager or senior IT engineer). These roles are used as
placeholders for participants in a request.
7.
Click Save and Activate to save changes and activate the role. A role must
be active to assign users. If desired, you can save your changes but activate
the role later.
To assign users to groups and role:

1.
2.

3.

Roles.
The User Groups page appears.
4.
Click the Administer Users tab.
Web Administration
The Administer Users page appears.

5.
Locate and select the user to whom you want to assign a role.
6.
If another user should respond to work requests routed to this user, click
next to Delegate to select the user that should receive work requests on the
selected users behalf.
7.
Click
next to Primary User Group to specify the users primary group.
The primary designation is only used for request routing.
8.
Click
group.
9.
Click Add in the Roles pane to assign roles to the selected user.
10. Click
next to Assigned User Groups to specify the users primary
under Roles to select a role.
11. Click
under Group to designate the group in which the user will have
this role.
12. Click Save and Close.
Web Administration
6.10
Third-party T&E Options
The third-party time and expense functionality allows users to enter time and
expenses from an external system into Primavera. These options control it:
Allow users to create third-party T&E transactions against complete

projects. When this check box is enabled, users with sufficient privileges
can create business transactions against projects that are marked complete.
Enabling this option also reveals the second option.
Warn users when they save business transactions that reference

complete projects. This option is only available when the first check box is
enabled. It determines whether Primavera displays a warning message when
users try to save a business transaction created against a project that is
marked complete. Enable the check box to warn users.
To edit the Third-party T&E options:

1.
2.

3.
In the Administrative Commands pane, click Third-party T&E Options.

The Third-party T&E Options page appears.
4.
Enable the Allow users to create third-party T&E transactions against

complete projects check box if users can create business transactions
against projects that have a status of Complete.
The second check box appears.
5.
Enable the Warn users when they save business transactions that
reference complete projects check box if Primavera should display a
warning to users when they create business transactions against projects that
are complete.
6.
Business transactions are now configured. These options control both the web
client and the Primavera API.
Web Administration
6.11
Field-level Resource Profile Privileges
The resource profile privileges functionality allows an administrator to configure

the editing privileges on a resource profile.
An administrator can restrict the editing privileges for the following fields:
First Name
Last Name
Pool
Organization
Hire Date
Job Title
Resource Type
Transaction Type
Business Role
Classifications
To set restrictions on the above fields:
1.
2.
3.
4.
In the Administrative Commands pane, click Resource Profile Privileges.
5.
The Resource Profile Privileges page appears.
6.
By default, all the options will be unchecked. Enable the check box next to
those options that will restrict users from editing that particular field.
7.
8.
The resource profile privileges settings are now configured.
Web Administration
For example, if an administrator has checked the check box next to Last Name,
users will not be able to edit the Last Name field in the resources General
Information page. The restricted fields are displayed as read-only options in the
General Information page. However, an administrator can edit any field
irrespective of the configurations.
There is only one configuration field that controls all classifications of a
resource. If an administrator has checked the check box next to Classifications,
the edit icon for classifications will not be displayed in the Resource Summary
Page.
Configuring these options supersedes any privileges provided by a users access
roles. However, you can create a new resource irrespective of the field-level
resource profile configurations.
Web Administration
6.12
Language Authorization
Primavera can be displayed in five languages (French, English, German, Italian,

or Spanish). The default is English. To make additional languages available,
authorize the ones for which your enterprise is licensed. Once authorized, endusers can select their preferred language from the Options page.
For ProjectLink users, the locale settings in Primavera must match the locale
specified on the computer hosting Microsoft Project.
To authorize a language:
1.
2.

3.
In the Language Authorization pane, click Edit.

The Language Authorization page appears.
4.
Click the Authorized check box next to the language you want to make
available to end-users.
5.
The Admin page appears, listing the authorized languages. Users can now
display Primavera and its help system in the languages you specified.
Primavera Reports
7.
Primavera Reports
Primavera and Actuate have partnered to provide an efficient, scalable, highly

searchable reporting solution for Primavera. The Actuate iServer manages report
execution, display, and delivery. Using Actuate, you can efficiently locate
relevant Primavera data to inform your business decisions. Access reports
directly from the Primavera web client or through the Actuate Active Portal JSP.
The following sections describe the steps required to utilize Primavera reports:
Reports and Rate Tables
Report Properties
Provided Reports
Custom Reports
Report Properties
You must regularly run the populateReportingTables.bat file to ensure that rate
information is calculated properly in reports. For more information, refer to
Reports and Rate Tables on page 178.
This chapter assumes that you are an advanced Actuate user. For information on
administering Actuate, refer to the Administering Actuate iServer System
provided with the Actuate iServer. Note that the instructions in this document
vary, depending on your operating system and RDBMS.
Primavera Reports
7.1
Reports and Rate Tables
The rate information for resources, business roles, and positions is stored in
tables throughout the Primavera schema. Querying this information from the
database on the fly can be very time consuming, especially in the context of
reporting.
To improve performance, Primavera reports reference flattened side tables that
store rate information. These tables must be updated periodically to ensure that
they contain the most current information. To update the tables, run the
populateReportingTables.bat file supplied by Primavera. This batch file
reads the rate information throughout the schema and writes it to the reporting
side tables.
The frequency with which you populate the reporting tables is determined by the
nature of your rate data. Primavera recommends automating this process, and
scheduling it to run as often as your rates and reports necessitate. For more
information on database policies, see your DBA.
Portfolio Management relies on these tables as well.
Primavera Reports
7.1.1
Populating the Reporting Tables: MS SQL
To populate the reporting tables:
1.
On the MSSQL Server host, click StartProgramsAccessories

A command prompt window appears.
2.
In the window, change directories until you are in the

utils\database\mssql folder in the folder where you installed the
Database Utilities component. If you used the default directory, change

directories by typing:
cd primavera\utils\database\mssql
3.
At the prompt, type:

populateReportingTables [SQL_Server] [Database_Name]
[User_ID] [Password]
where the arguments have the following meanings:

[SQL_Server] is the name of the database instance. Typically, this is the
name of the computer hosting MS SQL Server.
[Database_Name] is the name of the database. For example, PVDB.
[User_ID] is the ID to use to log into the database server. This accounts
permissions in the PVDB database should be comparable to the database
owners (DBOs) permissions.
[Password] is the password to the [User_ID] account.
4.
Press Enter.
Text begins to scroll down the command window.
When the prompt appears, the reporting tables are updated with current values.
Primavera Reports
7.1.2
Populating the Reporting Tables: Oracle
To populate the reporting tables:
1.
At the prompt, change directories until you are in the utils/database/oracle

folder in the Primavera installation. For example,
cd primavera\utils\database\oracle
2.

populateReportingTables [Database_Alias] [User_ID]
[Password]

[Database_Alias] is the name of the alias that points to the database
instance that stores the Primavera schema (PVDB).

[User_ID] is the ID of the account that owns the Primavera tables. For
example, PVDB.
[Password] is the password to the above account.
3.
Press Enter.
The message Running populateReportingTable.sql appears (and in
Windows, a new command prompt window also appears). Text begins to
scroll down the window.
When the prompt appears, the Primavera reporting tables are populated.
To ensure that the scripts ran properly, refer to the log files generated when the
batch file was executed.
Primavera Reports
7.2
Provided Reports
Primavera is delivered with a report encyclopedia, which is a shared repository of

all information related to the reporting environment. It contains reports that fall
into the following categories:
Work Request Reports
Opportunity Reports
Win and Loss Reports
Project Reports
Client Reports
Resource Reports
Structures and Catalogs Reports
Time and Expenses Reports
Transaction Processing Reports Reports
Billing Reports
Project Accounting Reports
Most Primavera reports allow you to specify the data to include. For example,
you can specify which projects to include in a Staffing by Project report.
Reports also have a default setting that yields the most comprehensive report
possible. For example, if you do not specify a project when you run a Staffing by
Project report, the report includes all projects you can view.
Some reports are organized into groups that summarize and organize data. You
can navigate these groups in the left-hand pane of the report page.
Primavera Reports
Primavera provides two other Actuate reports. Anyone with appropriate

permissions can run these reports.
The Audit report listed in the report tool is used by some system
administrators to process Primavera licenses.
The Capacity Planning report compares required position qualifications

defined against your existing resource qualifications to help users quickly
make staffing, training, outsourcing, and hiring decisions. For more
information, refer to Analytic Applications.
Primavera Reports
Table 7-1
Work Request Reports
Report
Description
Functional Role Report
Lists functional roles, user groups, and assigned

users.
Primary Groups Report
Lists primary groups and requests, and the

creators assigned to them.
Requests Creators List
Lists requests, creators, and their primary groups.
Table 7-2
Opportunity Reports
Report
Description
Sales Pipeline Report
A combined report that can be run by client,

current phase, engagement date, organization unit,
or win confidence to determine the number of
forecasted revenue of opportunities in the sales
pipeline.
Sales Pipeline by Split

Organization
Reports forecasted revenue for each opportunity in

the pipeline, organized by the owning or split
organization unit.
Sales Pipeline by
Service

the pipeline by each service offered by your
enterprise.
Sales Pipeline by
Competitor

the pipeline by competitor.
Sales Pipeline by
Account Owners

the pipeline by all account owners for the
opportunity. Can be limited to primary account
owners.
Primavera Reports
Table 7-3
Win and Loss Reports
Report
Description
Win/Loss by Date Range
Reports information about all closed

opportunities for a given date range, grouped by
final outcome.
Win/Loss by Client

opportunities for a given date range and client,
grouped by final outcome.
Win/Loss by Competitor

opportunities for a given date range and
competitors, grouped by final outcome.
Win/Loss by Reason

opportunities for a given date range, grouped by
final outcome and final outcome reasons.
Table 7-4
Project Reports
Report
Description
Project Profile (detail or

summary)
Lists general information, project dates, teams

and positions, and assigned resources for the
specified project. The report can include a
particular project, all projects in a pool, or all
projects.
Project Staffing
Lists teams and positions, including start and

end dates and any committed resources for
specified projects. The report can include a
particular project or all projects.
Primavera Reports
Table 7-4
Project Reports (Continued)
Report
Description
Project Pipeline
Lists all the prospective projects for a specified

pool. The report can include all projects in a
pool or all projects.
Project Resources
Lists resources committed to all selected

projects.
Project Unfilled Positions
Lists unfilled positions in any projects in the

specified pool. Includes a total number of
positions and details on each open position. The
report can include all projects in a pool or all
projects.
Table 7-5
Client Reports
Report
Description
Client Profile
Lists general information, projects, client

contacts, and client resources. Defaults to all
clients.This report can be organized by client
pool, client status, account owner, or industry.
Client List Detail by Pool,

or Client List Detail by
Account Owner
Lists all clients, including general information

and contacts. This report can be organized by
pool or account owner.
Client List Summary
Lists general information and account owners

for selected clients. Can be filtered by client
pool, client status, account owner, or industry.
Client Relationships
Lists all parent and subsidiary relationships for

a selected client.
Primavera Reports
Table 7-6
Resource Reports
Report
Description
Resource Profile (detail or

summary)
Lists general information about the specified

resource, including professional information,
work experience, preferences, assignment,
business role, and qualifications. Defaults to
all resources.
Resource List
Lists the current assignments and contact

information for all active resources with a
particular job title or belonging to a particular
pool or organization unit.
Resource Core
Competencies
For each of the five most-common

qualifications in your enterprise, lists the
resources who have the qualification. This
report is organized by pool.
Resource Roll Off
Lists the resources whose project assignments

are ending during the specified period. For
each resource, it lists the business role,
current assignment, and any future
commitments. A summary of this report is
also available.
Staffing Request by Status
For each staffing request, lists the initiator of

the request, the current status (requested,
suggested, waiting for confirmation,
complete), the recipients of the request
(including their pools), request date and time,
subject, project, client, and notes.
Timed Out Requests
Displays information for each timed out

request including the sender, project
information, notes, and current status.
Primavera Reports
Table 7-6
Resource Reports (Continued)
Report
Description
Forecast Utilization
For each resource, displays the actual or

committed hours for a given time period
compared to the potential available hours.
Resource Availability
Displays the number of hours resources are

available to work and their business role.
Table 7-7
Structures and Catalogs Reports
Report
Description
Organization Structure
Lists the office location, parent organization

unit, and manager for each organization unit.
Pool List with Owners
Lists the type and owner of each pool.
Pool Structure
Lists the pool structure hierarchically.
Office Locations
Lists the organization unit and parent office

location for each office location.
Job Title
Lists each job title.
Preferences
Lists each preference and associated scale.
Business Role
Lists the qualifications, rates, estimated costs,

and rate range for each business role.
Primavera Reports
Table 7-7
Structures and Catalogs Reports (Continued)
Report
Description
Skills
Lists the scale and scale levels used by each

skill in the Qualification Catalog.
Education
Lists the scale and scale levels for each

education in the Qualification Catalog.
Certifications
Lists each certification in the Qualification

Catalog.
User Access Roles By Pool
Lists the access assignments in each domain.

The report shows the domain/pools that users
belong to and their access role, user name,
user id, and the user email address. Running
this report requires administrator
permissions; this report does not appear in the
list of Structures and Catalogs Reports unless
the logged-in user has the administrator
access role.
Table 7-8
Time and Expenses Reports
Report
Description
Expenses by Resource or Project
Displays resources expenses by

transaction, reimbursement, and
common converted amounts within a
specified expense date range and
status. This report can be organized
by resource or project.
Primavera Reports
Table 7-8
Time and Expenses Reports (Continued)
Report
Description
Missing Time by Resource or

Project
Displays resources who reported

fewer hours than they were scheduled
to work for a particular time reporting
period. This report can be organized
by resource or project.
Missing Time by Period
For a particular period, lists resources

that reported fewer hours than they
were scheduled to work.
Project Hours by Resource or

Project
Displays resources who reported time

against the specified projects during a
particular time reporting period. This
report can be organized by resource
or project.
Resource Hours Utilization
Displays resources whose utilization

fell below the specified percentage
for a particular time reporting period.
Table 7-9
Transaction Processing Reports
Report
Description
Inter-company Expense
Inter-company expense report that shows

expense transactions.
Inter-company Time
Inter-company time report that shows time

transactions.
Primavera Reports
Table 7-10 Billing Reports

Report
Description
Billing Status
Lists billing details (posted invoices and

invoices in progress) per project and task. The
report shows the billing class at the project and
task level. The report can include all projects
or active projects.
Unbilled Revenue
Lists the progress of recognized revenue

amounts versus invoice amounts as of the
specified date. Any period end balance from
the prior period is brought forward and
adjusted against the revenue and invoice
transactions of the current period. The report
can include all projects or active projects.
Unbilled Hours
For each project, list the hours reported by

each resource that have not been billed. The
report only includes Time and Material
transactions
Primavera Reports
Table 7-11 Project Accounting Reports

Report
Description
Project Gross Margin
Provides a summarized or detailed view of

project cost and revenue tasks. Use this report
to review your gross margin variance against a
project.
Summary Gross Margin
Provides a summarized or detailed view of

project cost and revenue tasks. Use this report
to review your gross margin variance across
projects based on project status, organization,
location, or project type.
Project Configuration
This report assists in auditing the entry and

setup of projects based on the work breakdown
structure. The report displays project and task
details with their respective start and end
dates.
Primavera Reports
7.3
Custom Reports
The Primavera Actuate encyclopedia architecture allows users to add custom

reports. In the web client, access these reports by clicking ReportsCustom in
the Main Menu.
Add custom reports under the CustomReports folder of the Primavera
encyclopedia. You can group custom reports in named folders.
Primavera provides a user in the encyclopedia for use with custom reports. Both
the username and password are evolve_custom. Assign the evolve_custom
role to all Actuate users that need access to custom reports, and give appropriate
privileges to the evolve_custom user.
If you do not create custom reports, your users receive a message indicating that
the folder is empty when they click ReportsCustom Reports in the Main
Menu.
7.3.1
Requirements
Actuate reports need either hard-coded data source connection information

(including login ID and password ), or use libraries (either yours or from
Primavera). Primavera provides libraries if requested. You also need ERDPro.
Your custom reports can be filtered to only include the data to which a user has
access by calling methods in Primaveras reporting security API. The API allows
developers to apply the access control defined in the Security and Account
Manager to custom reports. For more information, refer to Developing Custom
Reports for Primavera.
Note that the invoice report can be customized to fit your enterprises billing
needs. To customize the invoice report, first obtain the source files from
Primavera. You can then add or remove information, change the formatting of the
data, or make any other changes supported by Actuate. Once you have updated
the source file, you must update the PtsServer.DM.InvoiceReportFormats
property in AppServerConfig.properties file to point to the new report.
For more information on report properties, refer to Setting Report Properties

on page 327. For assistance in creating custom reports, contact Primavera.
Primavera Reports
7.4
Report Properties
Primavera uses parameters in the AppServerConfig.properties file to

connect to Actuate. Several of these have default values. The relevant
configuration parameters in this file are listed in the following sections.
Generally, the values in these files are correct, though you may want to edit the
properties that define the printers used with the Delivery Manager reports.
Use caution when editing this file. Inadvertent changes to any properties may
troubleshoot. It is typically not necessary to edit this file for reporting values unless
you have modified the report encyclopedia. Before changing this files contents,
make a copy of the file.
Several properties specify the directory names in the Actuate encyclopedia. By

default, these values are commented in the file, and default to the names used in
the encyclopedia. To change a property, remove the comment character (#) and
change the value. Primavera recommends editing these values only if necessary
and with caution. Such changes require corresponding changes to the Primavera
encyclopedia; otherwise Primavera users will not be able to access these reports.
Standard Primavera Report Properties
Delivery Manager Report Properties
Custom Primavera Report Properties
Specifying Delivery Manager Reports Printers
For more information about reports, refer to Primavera Core Database Schema
Documentation and Developing Custom Reports for Primavera in the Primavera
documentation set.
Primavera Reports
Table 7-12 Standard Primavera Report Properties

Property
Description
PtsServer.Reports.Actuate
.reportServerProtocol
Specifies the protocol used to connect to the

Actuate server. Specified during installation.
Always accept the default, which is HTTP.
.StdReportsExplicitLogon
Specifies whether users must explicitly login to

the Actuate server. When this property is set to
TRUE, users must specify an Actuate user ID
when they click Reports in the Main Menu.
Defaults to FALSE.
.encyclopediaUserName
Specifies the Actuate user ID to use to connect

to the Actuate server when
PtsServer.Reports.Actuate.
StdReportsExplicitLogon is set to FALSE.
The user ID must exist in Actuate. Defaults to

evolve_std.
.encyclopediaPassword
Specifies the password to use when

Defaults to evolve_std.
Primavera Reports
Table 7-13 Custom Primavera Report Properties

Property
Description
.CustomReportServerProt
ocol
Specifies the protocol to use when connecting

to Actuate. Always accept the default, which is
HTTP.
.CustomReportsExplicitLo
gon
Specifies whether the user must explicitly login

to the Actuate server when accessing custom
reports. When this is set to TRUE, users must
specify an Actuate user ID and password when
they click ReportsCustom Reports in the
Main Menu. Defaults to FALSE.
.encyclopediaCustomUser
Name
Specifies the Actuate user ID used to connect to

Actuate if PtsServer.Reports.Actuate.
The user ID must exist in Actuate. Defaults to
evolve_custom.
.encyclopediaCustomPass
word
Specifies the password to be used when

StdReportsExplicitLogon = FALSE.
Defaults to evolve_custom.
Primavera Reports
If you rely on financial reports that access the DMDB, the following properties
can be found in the appserverconfig.properties:
Table 7-14 Delivery Manager Report Properties
Property
Description
PtsServer.DM.Invoice
ReportFormats.
Specifies the format of the Standard Invoice report.

Multiple formats can be specified in a commaseparated list. Defaults to Standard,
DefaultFormat1.
PtsServer.DM.Credit
MemoReportFormats.
Specifies the format of the Credit Memo report.

Multiple formats can be specified in a commaseparated list. Defaults to Standard,
DefaultFormat1.
PtsServer.DM.Prepay
mentReportFormats.
Specifies the format of the Advance Payment

report. Multiple formats can be specified in a
comma-separated list. Defaults to Standard,
DefaultFormat1.
PtsServer.Reports.
Actuate.Printers.
Specifies the path to the printer. Multiple paths can

be specified in a comma-separated list. These
printers must also be defined in the Actuate
Management Console. If this property is set to
Default, invoice reports are printed on Actuates
default printer. Defaults to Default.
Primavera Reports
7.4.1
Specifying Delivery Manager Reports Printers
If you rely on financial reports that access the DMDB database, the
appServerConfig.properties file includes the PtsServer.Reports.
Actuate.Printers property. This property specifies the path to a printer that is
used for Delivery Manager reports, including invoices, credit memos, and
advance payments. Multiple paths can be specified in a comma-separated list.
These printers must also be defined in the Actuate Management Console. If this
property is set to Default, invoice reports are printed on Actuates default printer.
The default value is Default.
To specify a non-default printer, use the following format:
PtsServer.Reports.Actuate.Printers=\\\\[Host_Name]\\
[Printer_Name]
where:
[Host_Name] is the name of the computer to which the printer is connected.
[Printer_Name] is the name of the printer.
For more information about printers, refer to Report Properties on page 193.
Primavera Reports
Access Control
8.
Access Control
Primavera access control is defined by the relationships between pools and

accounts. Each pool has a policy that determines which accounts and access roles
can view or modify the pools data. In the case of financial functionality, such as
posting or billing, access is granted at the company level.
This chapter describes the Primavera Security and Accounts Manager application
and associated administration tasks:
Introduction to Access Control
Pool Structure
Object Access Policies
Time and Expenses Overview
Accounts
Access Role Catalog
Company Access
Access Control Recommendations
Access Control Example
Access control is configured and maintained in the Security and Account

Manager application, which is accessed by selecting StartPrograms
PrimaveraSecurity and Account Manager from the desktop of the client
host. In order to log in to this application, an account must be assigned the
Administrator access role.
Access Control
8.1
Introduction to Access Control
This chapter discusses the main features of the pool structure and of access
control, including company access. Primavera recommends reading this chapter
in its entirety before you configure pools or access control.
8.1.1
Pool Access
The pool structure and access control are interdependent and it is important to
understand this interaction before you configure the pool structure, refer to
Figure 8-1. For more information, see the section of this chapter related to each
of the following topics.
Your approach to configuring the pool structure and access control should be:
1.
Determine the pool structure that best fits your business model and practices.
2.
Abstract out the similarities of your users to create access roles that can be
combined to grant proper access.
3.
Determine an Object Access Policy (OAP) for your Enterprise domain that
reflects the usual level of access your users should have, both within their
own scope of operation and in other divisions of the enterprise.
4.
Revisit the pool structure you originally devised and make any adjustments,
based on your findings regarding access control requirements.
5.
Create the access roles you devised in step 2..
6.
Customize the Enterprise domains OAP to reflect your findings in

step 3.
7.
Create the domains and pools you devised in step 2..
8.
Customize the few pools that cannot conform to the Enterprise domains
OAP.
9.
Determine each resource pools time and expenses approvers.
10. Determine each project pools calendar.

11. Test your access control model by logging into Primavera as various users
with different roles. Correct any problems you find.
Access Control
The following figure depicts the parts of the access control system and their
relationships. An understanding of these relationships is key to properly
configuring security in Primavera.
Figure 8-1
Access Control Relationships
Refer to Accounts and Access on page 256 for information on the precedence
of privileges granted through varying methods.
Access Control
8.1.2
Company Access
In order to accommodate the needs of accounting users, Primavera limits and

grants privileges to financial data along the lines of the organization structure.
Company level access integrates the logical structure of the organization
structure with the access roles assigned to users. A user is granted access to
particular companies (one of which is the users default), and can perform any
tasks to which he is granted access by an access role.
For more information, refer to Company Access on page 270.
8.1.3
Analytic Applications Access Control
Rights to access, edit, and publish data from the analytic applications are defined
in the Access Control application associated with PM. For more information,
refer to Analytic Applications.
8.1.4
Collaboration Access Control
Collaboration access control is typically administered by project owners. For

more information on workspace membership and privileges, refer to the online
help.
8.1.5
MS Project Server Integration

through ProjectServerLink
Permissions that enable users to synchronize data between Microsoft Project

Server (MSPS) and Primavera are defined in the Security and Accounts
application as part of an enterprise policy. For more information about the Object
Access Policy (OAP), refer to Overview of OAPs on page 222.
Access Control
In the Security and Accounts application, you can define configuration settings
through the Project Integration tab under Access Roles and Assign Access
Roles. Refer to Access Role Overview on page 263.
Figure 8-2
Project Integration tab
You can define MSPS integration and synchronization permissions at the

following levels:
Enterprise
The enterprise level gives the ability to configure settings for the enterprise.
Configurations that you define at the enterprise level include MSPS
integration settings for multiple projects, and usernames and passwords for
Primavera features such as the Primavera event handler or impersonation to
upload actuals and Estimated Time to Completion (ETC).
Project
At the project level, you can give users permissions to override some
enterprise-level settings to manage the type of data to synchronize, such as
information about resources and calendars.
User
The user level gives Primavera users permissions to synchronize task
information with MSPS. A user needs all permissions (Create, Delete,
Update, View) for tasks to be able to synchronize data with MSPS. Refer to
Task Access Policies on page 224.
8.1.6
Access Control for Client Downloads
You can provide enterprise-level access control to users for clients they
download through the Primavera web client. Refer to Installing the Clients
on page 112.
Access Control
You can grant or revoke access to access roles, depending on your enterprises
policy. For more information about the Object Access Policy (OAP), refer to
Overview of OAPs on page 222.
In the Security and Accounts Manager application, use the Installer Downloads
tab to assign or remove download access to the following clients:
Primavera Clients
Primavera clients include the following applications: Primavera
Administration, Configuration, and Security and Accounts Manager.
Offline T & E
The Offline Time and Expense client allows the Primavera user to record
time and expenses offline and upload them to Primavera later.
ProjectLink
The ProjectLink client enables the Primavera user to integrate Primavera
data with data in MS Project Desktop.
Primavera API Client Component

This client allows developers to write custom applications.
See also Example Installation on page 23.
8.1.7
Pool Structure
Configuring the pool structure consists of creating domains and pools, and
customizing the aspects particular to each pool, including assigning owners,
identifying time and expenses approvers, selecting calendars, and defining
Object Access Policies (OAPs).
Access Control
Understanding the purposes of the pool structure can facilitate its configuration.
The pool structure has several purposes:
Logically group Primavera data in an understandable structure.
Group projects for staffing purposes (that is, the Team Locator).
Group resources for staffing purposes (that is, the Team Builder).
Define account privileges based on Object Access Policies (OAPs).
Allow groups of resources or projects to share customized calendars.
Define the users responsible for reviewing, approving, and disapproving

time and expenses.
Beyond these purposes, the structure can represent nearly any aspect of your
enterprise.
The following sections discuss the pool structure:
Overview of Pools
Adding Domains and Pools
Access Policies and Pools
Customizing Pool Owners
Pools and Calendars
Recommendations for Pool Structure Configuration
Pool Examples
The pool structure has extensive impact on access control in Primavera. These
ramifications are very important, and you should not create your pool structure
without considering them thoroughly. See Access Control Recommendations
on page 272.
Access Control
8.1.8
Overview of Pools
The following sections provide details on each of the main aspects of the pool
structure, including:
Pools
Domains
Object Pools
Owners
Calendars
Time and Expenses Approval and Pools
Pools
The pool structure is a hierarchical representation of your enterprise that consists
of pools. End-users navigate and search this structure to locate business objects.
A pool is a logical grouping of pools or business objects. It is the generic term
used to refer to all such groupings in the pool structure. Each pool should contain
related items. You can organize the pool structure geographically, by function, or
by any other principle.
Every pool has an OAP and one or more owners. OAPs and owners are usually
inherited from the parent pool, but can also be customized for a particular pool.
The OAP determines the access that users have to the pool. Ownership
determines the users who can modify the pools properties, such as its OAP and
owners.
For information on OAPs, refer to Customizing an OAP on page 238.
Access Control
Domains
A domain is a special pool that can contain other pools and accounts. The toplevel pool is the Enterprise domain. Domains demarcate scopes of operation in
the structure, delineating internal accounts from external ones:
Internal indicates that the account belongs to this logical group. An account
is internal to the domain that contains it, and to any sub-domains (that is, an
account in the Enterprise domain is internal to all other domains).
External indicates that the account does not belong to this logical group. An
account is external to a domain if the account is not in that domain or a
super-domain (that is, if the account is not internal, it is external).
A domain reflects a logical barrier in your enterprise. For example, an enterprise

might have an Audit domain and a Services domain to reflect the limited access
that Auditing personnel have to Services data, and vice versa. In this case, an
account has greater access to objects in the domain that contains it: accounts
internal to the Audit domain would have greater access to Audit business objects;
accounts internal to the Services domain would have greater access to Services
business objects.
Each domain represents the scope of operations for the accounts it contains. An
access role only grants privileges within the accounts domain (unless another
pools External Access Policy has been customized to include the role). Create a
domain for each semiindependent organization in your enterprise.
When a resource profile is created, the account associated with it is created in the
domain that contains the resource pool.
Access Control
Object Pools
Object pools are the leaf-level pools in the pool structure, and can only contain
business objects. Each object pool can contain business objects of one type:
opportunity, project, resource, client, competitor, or agency. They are referred to
by the type of object they contain: opportunity pool, project pool, resource pool,
and so forth.
When a user browses the pool structure to select values, a pool is only displayed
if it contains an object pool of the appropriate type. For example, consider a pool
structure with an East domain and a West domain. If the West domain contained
the only client pool in the enterprise, Primavera would not display the East
domain when a user was selecting a projects client.
Owners
A pool owner is an account holder who has special responsibilities and
permissions in a particular pool. Often, a pool owner is responsible for the
business objects that the pool contains. For example, a resource pool might be
owned by a resource coordinator. By default, owners of a pool have unlimited
access to objects in the pool.
It is particularly important to explicitly assign owners to resource pools. When
users send staffing requests, they must select recipients from a list of explicitlydefined resource pool owners. Note that inherited owners do not appear on the
list. If no resource pool owner has been explicitly defined, the initiator cannot
specify the correct recipients of the request.
An owners privileges to the pool are defined in the pools Maintenance Access
Policy. An owners privileges to pool contents are defaulted from the pools
Owners option in the Internal Access Policy. In the case of project pools, the
privileges you grant to the Owners option are also defaulted to users that own
projects in the pool.
While project profiles have explicitly-defined owners, resource profiles are
implicitly owned by the associated resource account.
Access Control

A pools OAP determines the privileges that accounts have in the pool. See
Object Access Policies on page 221.
The following aspects of the pool structure directly impact access control:
OAP
Pool Ownership
Account locations in the structure
Calendars
Primavera provides configurable calendars (workweeks and holiday schedules),
allowing various pools to default different calendars to resources or projects in a
particular pool. When you customize a pools calendar, you select workweeks
and calendar policies from a list that is created and maintained in the
Configuration application. For more information about creating alternate
workweeks and calendar policies, refer to the Configuration Guide.
Time and Expenses Approval and Pools
When time and expenses reports are submitted by resources, another user might
be required to review the report for approval. These reviewers are defined at the
resource pool level. Time and expenses administrators can also be defined. These
users are granted privileges to act on behalf of other users. For more information
on time and expenses approval, refer to Time and Expenses Overview on
page 242.
Note that third -party time and expense business transactions are secured
separately from native time and expenses. Refer to Third-party Time and
Expenses on page 252.
Access Control
8.1.9
Adding Domains and Pools
When you configure the pool structure, you can define domains, pools, and
object pools. This section includes instructions for each type of pool.
To add a domain, pool, or object pool:
1.
Select StartProgramsPrimaveraSecurity and Account Manager

from the desktop of the client host.
After you log in, the Access Control window appears, with the Organization
View pane selected.
2.
3.
Locate and right-click the pool that will contain the new domain, pool, or
object pool.
From the menu that appears, select NewDomain.
To create a pool, click NewPool.
To create an object pool, click New[Object Type], where [Object Type]
is Opportunity, Project, Resource, Client, Competitor, or Agency.
The New window appears.
4.
Enter a name for the pool. This step is required.
5.
Click OK.
6.
To customize the owners, calendar, OAP, or approvers, change the values

defaulted from the parent. For instructions regarding each procedure, refer
to:
7.
Customizing Pool Owners on page 212
Pools and Calendars on page 214
Customizing an OAP on page 238
Resource Pool Approvers on page 245
Click FileSave.
Access Control
Figure 8-3
Security and Account Manager, Pool Configuration
Access Control
8.1.10
Customizing Pool Owners
When you create a new pool, its owners are defaulted from the parent pool. If the
new pool should have different owners than the parent, you can change them.
A pool owner is granted special privileges to the maintenance of the pool and its
properties (such as access and ownership):
An owners privileges on the pool itself are determined by the Maintenance

Access Policy (MAP).
An owners privileges on the pools contents are determined by the Owner

setting in the Internal Access Policy (IAP).
When you add an owner, that user is granted the default privileges defined in the
pools Maintenance Access Policy and Internal Access Policy. To change the new
owners privileges, you must edit the pools access policies. Refer to
Customizing an OAP on page 238 for more information.
It is particularly important to explicitly assign owners to resource pools. When
users send staffing requests, they must select recipients from a list of explicitlydefined resource pool owners. Note that inherited owners do not appear on the
list. If you have not customized the owners of the requested resources pool, the
initiator cannot specify the correct recipients of the request.
To define a pools owners:
1.

After you log in, the Access Control window appears, displaying the
Organization View pane.
2.
Right-click on the pool that you want to update.
3.
From the menu that appears, select PropertiesPool Owners.
Access Control
The Find window appears.

4.
Enter the first few letters of the users last name in the Named field.
5.
Click Find.
6.
In the Users list, select the user that will own this pool.
7.
Click Add.
8.
Click OK.
The Find window disappears.
9.
Click FileSave.
The selected user now owns this pool, and is granted the default privileges
defined by the Maintenance Access Policy and the Internal Access Policys
Owner setting.
Access Control
8.1.11
Pools and Calendars
The default workweek and holiday schedule define your enterprises calendar. By
default, all resources and projects inherit the holiday schedule and workweek
defined for the enterprise. Use the Configuration application to add new
workweeks and holiday schedules, and to define the enterprise-level policies. For
more information, refer to Chapter 2 of the Configuration Guide.
Workweeks and holiday schedules can be customized at the business object
(resource and project) and pool level. This section provides instructions for
customizing pools holiday schedules and workweeks. Refer to the online help
for instructions about setting positions and resource calendars.
Primavera recommends that you carefully analyze your requirements for
alternate calendars, and create the minimum number of workweeks and holiday
schedules. While Primavera performance usually is not affected by the use of
multiple calendars, utilizing large numbers of workweeks and holiday schedules
may impact performance.
To customize a resource pools or project pools workweek:
1.
Select StartPrimaveraSecurity and Account Manager from the

desktop of the client host.
2.
3.
Right-click on the project or resource pool that you want to update.

From the menu that appears, select PropertiesWorkWeek.
The Select Workweek window appears, displaying all the defined
workweeks.
4.
Enable the check box next to the workweek that resources or projects in this
pool should use.
For each work week, the Work Hours column displays a comma-separated
list of the number of hours required on each day.
Access Control
5.
If you want Primavera to apply the workweek to business objects that

already exist, enable the Change the workweek for [Object Types]
currently in this pool check box (where [Object Types] is Project or
Resource).
6.
Click OK.
The pool is now customized with the workweek you selected.
Figure 8-4
Specifying a Pools Workweek
To customize a pools holiday schedule:

1.

2.
Right-click on the project or resource pool that you want to update.
3.
From the menu that appears, select PropertiesHoliday Schedule.

The Select Holiday Schedule window appears, displaying all the defined
schedules.
Access Control
4.
Enable the check box next to the holiday schedule that resources or projects
in this pool should use.
For each schedule, the Holidays column displays a comma-separated list of
the holidays observed.
5.
If you want Primavera to apply the holiday schedule to business objects that
already exist, enable the Change the holiday schedule for [Object Types]
currently in this pool check box (where [Object Types] is Project or
Resource).
6.
Click OK.
The pool is now customized with the holiday schedule you selected.
Figure 8-5
Specifying a Pools Holiday Schedule
Access Control
8.1.12
Recommendations for Pool Structure

Configuration
The following general tips can help you determine an appropriate structure for
your pools:
Choose an organizing principle that makes sense for your enterprise. The
obvious choice is often best, as it is usually the most intuitive for your users.
Consider carefully which pools should be domains. Select pools that

represent semi-ndependent groups in your enterprise. Since access control is
based on domains, it is important to take access control into consideration
before configuration.
Resource pools should have explicitly-defined owners and approvers to

facilitate staffing requests and time and expenses approval.
Create a chart to model the structure before you configure it in Primavera. It

is often helpful to have a visual representation of the structure you are
creating.
For access control tips regarding the pool structure, refer to Pool Structure
Recommendations on page 275.
Access Control
8.1.13
Pool Examples
This section provides simplified examples of pool structures. For an example of

access control (including pools), refer to Access Control Example on page
278. These examples assume a geographical organizing principle of the pool
structure.
By default, the pool structure includes two domains, as depicted in Figure 8-6:
Enterprise domain includes all the user-defined domains and pools. This
domain can be renamed.
Unassigned domain includes any objects that are not associated with other
pools. It contains a single object pool of each type. This domain cannot be
renamed.
Enterprise Domain
Unassigned Domain
Unassigned Opportunities Pool
Unassigned Resource Pool
Unassigned Project Pool
Unassigned Client Pool
Unassigned Competitors Pool
Unassigned Agency Pool
Figure 8-6
Default Pool Structure
Access Control
If modified, the simplest configuration includes a project pool and a resource

pool directly under the Enterprise domain, similar to Figure 8-7.
Enterprise Domain
Project Pool
Resource Pool
Unassigned Domain
Unassigned Opportunities Pool
Unassigned Client Pool
Figure 8-7
Minimally Modified Pool Example
In this configuration, all projects belong to a single pool, all staffable resources
belong to a single pool, and opportunities, agencies, competitors, and clients are
included in the respective unassigned pools.
A slightly more complex structure could include multiple domains that define
logical groupings of pools.
Access Control
Assuming a geographical organizing principle, the simplest multiple domain

configuration includes a sub-domain for each geographical area. In this case, the
pool structure would be similar to Figure 8-8.
Enterprise Domain
California Domain
Project Pool
Resource Pool
New York Domain
Project Pool
Resource Pool
Unassigned Domain
Unassigned Opportunity Pool
Unassigned Clients Pool
Figure 8-8
Moderately Modified Pool Example
Each of these geographical domains would include a project pool and a resource
pool. Opportunities, clients, competitors, and agencies are added to the respective
Unassigned pools.
The Object Access Policy references domains when determining account access.
For more information regarding Object Access Policies, read the following section,
Object Access Policies.
Access Control
8.2
Object Access Policies
An Object Access Policy (OAP) defines the privileges that access roles and
accounts have on a pool and its contents. Every pool has an OAP. If none is
explicitly defined, the pool inherits its parents OAP. To customize an OAP, add
access roles and accounts, and specify the access each is granted in the pool.
For more information about pools, refer to Pool Structure on page 204.
When you add an access role or account to a pool's OAP, you can customize the
Task Access Policy (TAP) of the access role or account. A TAP is a set of
privileges granted to an access role or account.
Overview of OAPs
Task Access Policies
Customizing an OAP
Access Control
8.2.1
Overview of OAPs
An OAP is a set of policies that determine the accounts that have access to a pool.
A pools OAP governs all users in the system, granting or revoking privileges to
the pool and its contents based on the accounts access role, ownership, and
location in the pool structure.
OAPs rely on the concepts of Internal access and External access to determine
account access to pool contents. Internal and External represent the relationships
between domains and accounts:
Internal. Accounts are internal to the domain that contains them and to any
sub-domain. Accounts in the Enterprise domain are internal to all other
domains.
External. Accounts are external to any domain that does not contain them,
including domains above the accounts domain. Accounts in sub-domains
are external to the parent domain.
Every pool has an Internal, External, and Maintenance access policy. Internal and
External access policies can include access roles and accounts; the Maintenance
access policy can only include accounts. An access role or account can belong to
multiple policies simultaneously.
When you add a particular access role or account and customize its TAP, your
options vary depending on the type of pool. For example, a client pools TAP
only includes the General Tasks tab, as none of the other tabs apply to client
profiles. On the General Tasks tab, the options include Client and Pools/
Domains, as these are the only UI components that apply to client profiles.
The following sections describe the three access policies that constitute the OAP.
Access Control
Internal Access Policy

Though access roles generally govern an accounts access within its domain, the
Internal Access Policy can also define access for internal accounts. It defines
access for the accounts that use the domains data most often. Change this policy
to change internal users access to the data in the domain. When you add an
access role to this policy, its TAP is defaulted.
The Internal Access Policy includes an Owners option that grants pool owners
access to the pool's contents. By default, owners are granted all privileges in the
pool. Owners access to the pool itself is defined by the Maintenance Access
Policy. In the case of project pools, the privileges you grant to the Owners option
are also defaulted to users defined as owners of projects in the pool.
When a role that has been added to a pools Internal Access Policy is customized
to revoke a certain privilege, that privilege is revoked from all accounts with the
role in this domain, regardless of other access roles.
External Access Policy

This policy defines access for accounts external to the domain. It defines access
for users that have limited access to the data in this domain. OAP customization
focuses on the External Access Policy, since most internal access is governed by
access roles.
All other pools inherit the Enterprise domains OAP, directly or indirectly.
Therefore, defining a sensible policy for the Enterprise domain simplifies access
control configuration. Create an External Access Policy for your Enterprise
domain that reflects the kind of access users are normally granted outside their
scope of operation (that is, outside their domain).
Access Control
Maintenance Access Policy

This policy defines maintenance access for owners of the pool. The maintenance
access policy governs pool owners access to the pools properties, including
changing membership. Owner access to the pools contents is defined in the
Internal Access Policy.
The privileges defined for the {Default} option are granted to users when they
are identified as the pools owners. This represents the default maintenance
privileges granted to pool owners, including owners inherited from parent pools.
8.2.2
Task Access Policies
A Task Access Policy (TAP) is the list of privileges to various User Interface (UI)
components granted by a particular role or Object Access Policy (OAP). Each
OAP, access role, and account includes a TAP:
The TAP specified for an OAP defines the access to a particular pool or
business object by listing the privileges explicitly granted to various roles
and accounts.
The TAP specified for an access role defines the privileges granted to
accounts with this role. The privileges granted by an access role only apply
to objects in the same domain as the associated account. In the case of
financial access, the access role defines the privileges granted in the
company to which the account has access. For more information refer to
Company Access on page 270.
For more information about access roles, refer to Access Role Catalog on
page 263.
The TAP defines access to each of the UI components separately. One or more UI
components is included in each of the TAPs tabs. For each UI component,
specify the privileges granted. For example, you can grant Create privileges for
projects. Not all tasks apply to all UI components. For example, you cannot grant
privileges to Terminate Resources in a project pool.
Access Control
The following sections list each TAP tab, along with the privileges and UI
components each includes. For information on the business significance of each
UI Component, refer to online help.
When you are customizing a TAP, click the heading to grant or revoke all the
privileges in a row or column. Click the Area/Unit button to toggle all privileges on
a tab.
General Tasks Tab

The General Tasks tab grants privileges to these UI Components:
Resource Profiles (includes Business Role, Actual Qualifications, Needed

Qualifications, and Desired Qualifications.)
Project Profiles
Project Bulk Update
Project Financials
Project Tasks (includes permissions to open and save Microsoft Projectmanaged work breakdown structures in ProjectLink and ProjectServerLink.)
Time Entry Grace Period
Agency Profiles
Client Profiles
Team Builder
Team Locator
Domains/Pools
Opportunity Profiles
Competitor Profiles
Project Transactions (for third-party transactions)
Organization Transactions (for third-party transactions)
Access Control
The General Tasks Tab grants these privileges:
Create (when granted for Resource Profiles, allows reinstatement.)
Delete
Update
View
Terminate
Project Commitment Tab

The Project Commitment tab grants privileges to these UI components:
Resource Profiles
Project Profiles
Team Builder
Team Locator
The Project Commitment tab grants these privileges:
Project Commitment Assign (includes Exclude and Reserve)
Project Commitment Shortlist (includes Staffing Request)
Project Commitment Delete
Project Commitment View
Non-Project Commitment Tab

The Non-Project Commitment tab grants privileges to these UI Components:
Resource Profiles
Team Builder
Team Locator
Access Control
The Non-Project Commitment tab grants these privileges:
Non-Project Commitment Create
Non-Project Commitment Delete
Non-Project Commitment Update
Non-Project Commitment View
Access Control
Billing/Cost Rate Tab

The Billing Rate tab grants privileges to these UI Components:
Resource Profiles
Project Profiles
Team Builder
Team Locator
Opportunity Forecast
The Billing Rate tab grants these privileges:
Billing Rate Update
Billing Rate View
Cost Rate Update
Cost Rate View
Forecasts Tab
The Forecasts tab, available when creating access roles, grants the following
privileges on resource information:
View Resource Utilization
View Project Revenue
View Pipeline Revenue
Workforce Planning
The Forecasts tab is also in the Access Control of the Organization View, in both
pools that contain other pools and domains. On certain pools, only one of the
three rights is available on the Forecasts tab; this means that on resource pools,
only the resource utilization right is available.
Access Control
Evaluations Tab
The Evaluations tab grants privileges to these UI Components:
Resource Profiles
Project Profiles
Agency Profiles
The Evaluations tab grants the following privileges:
Create Evaluations
Delete Evaluations
Update Evaluations
View Evaluations
My Profile Tab
The My Profile tab, which is only available for resource-related TAPs, grants
resources access to their own profiles. By default, the Resource access role grants
View privileges on this tab. The tab grants View and Update access to the
following resource profile UI Components:
Personal
Job
Financial
Work Preferences
Prior Work Experience
Business Role
Non-Project Commitments
Project Commitments
Actual Qualifications
Needed Qualifications
Access Control
Desired Qualifications
Project Evaluations
Non-Project Evaluations
Resource Pool
Agency and Location
Organization (also controls classifications)
Time & Expense Administrator Tab

The T&E Administrator tab grants the following privileges to act on behalf of
other time and expenses users:
Enter Time
Approve Time
Enter Expense
Approve Expense
Billing Tasks
The Billing Tasks tab grants privileges to these UI Components:
Invoice
Credit Memo
Advance Payment
Post
Billing Schedule
Access Control
The Billing Tasks tab grants the following privileges:
Create
Delete
Update
View
Execute
Print
Note that users who need access to update credit memos must be granted the
View Invoice privilege as well as the related credit memo privileges.
Access Control
Time & Expense (T&E) Tab

The T&E tab grants privileges to enter or approve time and expenses. It also
grants the privilege to override the Billable setting on the Time and Expenses
page.
Granting a user the Billable Override privilege allows that user to change an
activity or position to Non-billable during time and expenses entry and approval.
This change applies only to the particular time or expense report row the user is
editing.
To run reports related to time and expenses, you must have the Entry/Approval
privilege (in addition to privileges to run reports).
Report Tab
The Reports tab grants the privilege to run Primavera reports. Enabling this
option for a user allows the Reports link to be displayed in the Main Menu. Note
that, unlike the other privileges, this privileges can only be defined for access
roles. Granting this privilege allows users to see reports relating to any of the
business data to which they otherwise have access. For example, if a user has the
View Projects privilege in the West Coast domain, and the Run Reports privilege
is assigned to his access role, the user can run reports against all the projects in
the West Coast domain.
To run reports related to time and expenses, you must have the Entry/Approval
privilege found on the Time and Expenses tab (in addition to privileges to run
reports).
Termination Details
The termination details tab grants privileges to update and view the reason
entered when a resource is terminated.
Access Control
Unposted Trx Tasks

The Unposted Trx (transaction) Tasks tab grants privileges to these UI
Components:
Time Transactions
Expense Transactions
Material Resource Trx
Adjustments
Expense Reimbursement
Bulk Update
Post
The Unposted Trx Tasks tab grants the following privileges:
Create
Delete
Update
View
Execute
Access Control
Posted Transactions Tasks

The Posted Transactions Tasks tab grants the Execute privilege to these UI
Components:
Cancel
Adjustment
Hold Adjustment
Adjust Adjustment
Prorate Adjustment
Split Transactions
Transfer Cost
Project Accounting
The Project Accounting tab grants privileges to these UI Components:
Normalization
GL Distribution
% Completion
% Complete Post
The Project Accounting tab grants the following privileges:
Create
Delete
Update
Execute
Access Control
Budgeting
The Budgeting tab grants privileges to these UI Components:
Time
Expenses
Material Resources
Delete Budget
Details/BvA (Budget versus Actuals)
The Budgeting tab grants the following privileges:
Create
Delete
Update
View
Material Resource
The Material Resources tab grants the following privileges on material resources:
Create
Delete
Update
View
Project Owners
The Project Owners tab grants the privilege to change the users that own a
project.
Access Control
Templates
The Templates tab, which is only available when editing access roles, grants the
following privileges to team, task, qualification checklist, and pursuit process
templates:
View
Modify (includes create, update, and save object as template)
The View privilege does not determine whether a user can select a template when
creating new objects; any user who can create objects of a particular type can
select templates of the same type. The View privilege controls whether the
Templates option is displayed in the Main Menu of the web client.
Stakeholders
The Stakeholders tab grants the privilege to define stakeholders at these levels:
Project Stakeholders
Issues
Risks
Dashboard
The Dashboard tab grants privileges to the following UI components:
Own (controls access to the dashboard associated with this account)
Others (controls access to other users dashboards)
Dashboard Pages (controls access to modifying public pages)
The Dashboard tab grants the following privileges:
Configure
View
When editing a pools access policy, the Dashboard tab only includes the Others
UI component. The other privileges are only available on access roles.
Access Control
Work Requests
The Work Requests tab, which is only available when editing access roles, grants
privileges to create user groups, manage work request templates, and create work
requests. The Work Requests tab grants the following privileges:
Administer Templates
Request Creation
User groups are used for request routing, stakeholder definition, and dashboard
content publication.
Users with the admin role also have access to the Administer Groups and Roles
page.
Access Control
8.2.3
Customizing an OAP
Generally, you do not need to manually specify a pools OAP, as access is usually
governed by access roles and inherited OAPs. In rare cases, the OAP for a
particular pool must be customized. When you customize an OAP, you can add
either an access role or an account. You must own a pool (either directly or
indirectly) to define its OAP.
Note that only privileges relevant to this type of pool are displayed in the TAP.
To customize an OAP by adding an access role:
1.

View pane selected.
2.
Right-click the pool you are updating.
3.
Select PropertiesAccess Control from the menu that appears.

The Pool Access Policy Editor window appears.
4.
Click the Roles tab.
5.
Click Internal Access Policy or External Access Policy to select the policy
you want to modify.
6.
In the list of Roles on the left, click the role you want to add.
7.
Click Add.
The access role is added to the policy you selected. When you add an access
role to the Internal Access Policy, the roles TAP is defaulted to the Internal
Access Policy.
8.
If this access role must have specialized access to the pool, expand Roles in
the middle tree pane and select the role you just added.
9.
Customize the access role's TAP for this pool by enabling and disabling
various privileges.
10. Click FileSave & Close.
Access Control
To customize an OAP by adding an account:

1.

View pane selected.
2.
3.
Right-click the pool you are updating.

Select PropertiesAccess Control from the menu that appears.
The Pool Access Policy Editor window appears.
4.
Click the Users tab.
5.
Click Internal Access Policy, External Access Policy, or Maintenance

Access Policy to select the policy you want to modify.
6.
In the list of Users on the left, click the account you want to add.
7.
Click Add.
The specified account is added to one of the three policies. When you add an
account to the Internal Access Policy, the accounts TAP is defaulted to this
policy.
8.
9.
If this account needs specialized privileges in this pool, select the account
you just added:
If you are editing the Internal Access Policy or External Access Policy,
select the account by expanding Users in the middle tree pane.
If you are editing the Maintenance Access Policy, locate the account in
the TAP grid.
Customize the account's TAP for this pool or customize the Maintenance
Access Policy by enabling and disabling various privileges.
10. Click FileSave & Close.

Note that only tasks relevant to this type of pool are displayed in the TAP.
To remove an access role or account from one of the three policies, select it and
click Remove.
Access Control
Figure 8-9
Pool Access Policy Editor
Access Control
Table 8-1
Icon
TAP Grid Icons

Meaning
Primavera grants the privilege to perform this task. In a pools
OAP, it indicates that the privilege is inherited.
Primavera grants the privilege to perform this task. The privilege
is overridden here. This icon only appears when editing a pools
IAP or OAP.
Primavera does not grant the privilege to perform this task. In a
pools OAP, it indicates that the privilege is inherited.
Primavera does not grant the privilege to perform this task. The
privilege is overridden here. This icon only appears when editing
a pools IAP or OAP.
This privilege is not applicable. As an example of a privilege that
is not applicable, you cannot grant Create privileges to the Team
Builder.
For more information on customizing the TAP, refer to Task Access Policies
on page 224 and to Conflicting Access Roles on page 265.
Access Control
8.3
Time and Expenses Overview
Primavera provides two means of tracking time and expenses:
Your resources use Primaveras native time and expenses functionality to

report time and expenses they incur during the course of their commitments.
After a resource reports the time or expense, another user(s) may be required
to approve it. These time and expense reports result in transactions that are
stored in the Delivery Manager database and can be manipulated through the
web clients Transaction Processing menu item.
Project managers and administrators use Primaveras third-party time and

expense business transactions to update Primavera with information
recording in external systems. Business transaction can be created through
the web client or by using a custom application that utilizes the Primavera
API.
This section discusses the configuration of time and expense, and includes:
Time and Expense Approval
Time and Expense Second-level Approval
Second-level Default Approver Setup
Resource Pool Approvers
Time and Expenses Administrators
Third-party Time and Expenses
For recommendations regarding time and expenses, refer to Time and

Expenses Administrator Recommendations on page 276.
Access Control
8.3.1
Time and Expense Approval
Various Primavera users must be granted permission to approve native time and
expenses reports. These users, referred to as approvers, are defined through either
a resource pool or a project:
Resource pool approvers. Approve non-project time and expenses for

resources in that pool. If a project has the Resource Approver option
enabled, time and expenses reported against this project are routed to the
resources pool approver.
Project approvers. Approve time and expenses reported against a particular

project. For information on identifying a projects approvers, refer to the
web client online help.
In addition to approvers, Primavera provides the ability to define time and

expenses administrators.
You can also grant permission for a user to be able to mark a charge on a time or
an expense report separately. For example, the user may have permission to
change the billable/non-billable flag for a charge for an item on a time report, but
may not be able to do the same for an expense item.
8.3.2
Time and Expense Second-level Approval
You can send the Time and Expense reports to more than one user for approval.
Primavera supports two levels of approvers, which you can define at the
Resource pool level and the Project level.
The two levels of approval are sequential. After a user submits or resubmits a
time or expense report, that report is available to the first approver for approval.
If the first approver disapproves some cells in a time row or expense item then
the status of those cells changes to disapproved. The status of the remaining cells
remains submitted or resubmitted.
Access Control
After the first approver approves all the hours in a time row or all the splits in an
expense item, the report is forwarded to the second approver (if defined) for the
final approval. If the first approver disapproves the report, it is not available to
the second approver. The approval status is shown as disapproved and the entry
user is sent an email notification.
The approval status remains unchanged, that is, either submitted or resubmitted
until the second approver acts on it. The status changes to approved or
disapproved after the second approver approves or disapproves the report.
Partial approval is allowed only if the approver is the final approver.
8.3.3
Second-level Default Approver Setup
You can set up the second-level approver in the same way as you set up the firstlevel approver.
The following three approver setup options are provided for Time and Expense
separately at the Resource pool level and the Project level:
Auto Approve. Selecting this option implies the specified user must
approve any time or expense reported against a project.
One level Approver. Selecting this option sets one approver to that assigned
to a position or task, resource approver, or user.
Two level Approver. Selecting this option sets the first level and second
level approver to that assigned to a position or task, resource approver, or
user.
The user can change the approver levels from one level to another. For example,
from Auto Approve to One level Approver or Two level Approver.
Access Control
The following rules apply when you are setting approvers at the Resource pool
level or Project level:
The first level and second level approver cannot be the same. For example, if
the first level is set to Resource Approver then second level cannot be
Resource Approver. If it is, Primavera displays an error message.
The Auto Approve option is not available for the second level approver.
Default Project Approver Setup

The default first-level Time and Expense approver is Resource Approver. The
default second-level Time and Expense approver is Resource Approver if the
first-level approver is not Resource Approver. Else, it is Position Approver.
Default Resource Approver Setup
The default first-level Time approver is Auto Approve. The default first-level
Expense approver is Manager. The default second-level Time and Expense
approver is Manager.
8.3.4
Resource Pool Approvers
When resources report time and expenses, many enterprises require another user,
such as a project manager, resource coordinator, or manager, to approve the
reports before the client is billed or the resource is reimbursed.
Access Control
In the case of non-project time and expenses (or project time and expenses that
are routed to the resource approver), Primavera determines who (if anyone) must
approve time and expenses by checking the resources pools Time Approver and
Expense Approver settings:
If they are set to Manager, time and expenses reported by resources in this
pool must be reviewed by the manager of each resources organization unit.
If they are set to Selected User, time and expenses reported by resources in
this pool must be approved by the user you select.
If they are is set to Auto Approve, time and expenses are not reviewed
before billing clients or reimbursing resources; the approval process is
bypassed. This is the default setting.
To define a resource pools approver:

1.

2.
Right-click on the resource pool that you want to update.
3.
From the menu that appears, select PropertiesTime & Expense

Approvers.
The Time & Expense Approvers window appears.
4.
In each group box, select an approval method for this pool.

Primavera recommends caution when allowing the Auto Approve option.
5.
If you enabled Selected User, click

time/expenses.
to select a user that will approve
The Find window appears.

6.
In the Look For field, select either All Users to view all users or This Pools
Owners to view a filtered list.
7.
Enter the first few letters of the users last name in the Named field.
8.
Click Find.
Access Control
9.
In the results list, select the user that will approve time and expenses for
resources in this pool.
10. Click OK.

The Find window disappears.
11. Click OK.
The Time & Expense Approvers window disappears.
The selected user is now granted permission to approve or disapprove time and
expenses reported by resources in this pool. Note that changes to time and
expenses approvers are not retroactive; they only apply to time and expenses
reports submitted or resubmitted after the change.
Figure 8-10 Time & Expense Approvers
Access Control
8.3.5
Time and Expenses Administrators
Time and expenses administrators are granted permission to act on behalf of

other users to ensure that reports are processed in a timely manner. Time and
expenses administrators can enter and/or approve time and/or expenses when the
approver is unavailable. For example, if an approver is on vacation, a time
administrator can act on his behalf, approving time reports. Primavera
recommends that you define the minimum number of T&E administrators, and
that you select them carefully.
Permission to act on behalf of another user is granted through a pools TAP. The
TAPs T&E Administrator tab grants access to approve or enter time or expenses
on behalf of other users. Depending on the type of pool for which the
administrator is defined, access varies:
Resource Pool. When you grant time or expense permissions at the resource
pool level, the administrator is granted permission to act on behalf of any of
the resources with profiles in that pool.
Pool. When you grant time or expense permissions at the pool level, the
administrator is granted permission to act on behalf of all resources in any
subpool.
Though pool/resource pool administrators can act on behalf of the resources
in the pool(s) to report time or expenses, they cannot necessarily approve
reports.
Domain. When you grant time or expense permissions at the domain level,
the administrator is granted permission to act on the behalf of all resources in
any pool in that domain. Additionally, the administrator is granted
permission to act on behalf of all non-resources defined at the domain level.
In other words, while act on behalf of resources is controlled by the pool in
which the profiles reside, act on behalf of non-resources is controlled by
the domain in which the accounts reside.
To act on behalf of another user, the T&E administrator must select the users
account from the Act on Behalf of page.
Access Control
Identifying Time and Expenses Administrators

You can identify T&E Administrators by adding them directly to a pools TAP.
To identify a time and/or expense administrator:
1.
Follow the procedure for customizing a TAP by adding an account

(described on page 239) until step 7.
2.
Click the T&E Administrator tab.
3.
Examine each box in the grid to determine the access you want to grant. You
can grant permission on the following while acting on behalf of others:
Enter Time
Approve Time
Enter Expenses
Approve Expenses
To act on another users behalf, the user must log into the web client.
4.
Click FileSave & Close.
You can also customize a TAP by adding an access role that grants permission to
act on behalf of other users.
Adding a Time and Expenses Administrator Role
If you plan to identify several time and expenses administrators, you can create
an access role instead of assigning the permissions on a user-by-user basis. Then,
assign the access role to the appropriate users.
To create a time and/or expense administrator access role:
1.
Follow the procedure for creating an access role (described on page 266)
until step 5.
2.
Click the T&E Administrator tab.
Access Control
3.
4.
Examine each box in the grid and determine what access you want this role
to grant. You can grant permission on the following actions while acting on
behalf of other users:
Enter Time
Approve Time
Enter Expenses
Approve Expenses
Click FileSave.
The new access role is added to the catalog.

Once the role is created, you can assign it to any user. The user will then have
permission to act on behalf of any user internal to that users domain. For
information, refer to Assigning Access Roles on page 268.
Expense Policy
The expense policy determines whether users must supply a value in the Task
Code field when reporting expenses.
The columns that appear in the expense reports can be configured by the system
administrator. In order to configure these columns, you must have the Expense
Template Configure access control bit, located under the Expense Configure tab
in the Admin Client.
Access Control
To configure the Expense Report template:
1.
Access the Time and Expense Report Finder; then click Configure.
2.
Click the Expense Entry Format tab.
3.
If a Resource must specify a task code when entering expenses, check the
checkbox next to Are Resources required to specify task codes when
reporting expenses?
4.
Select additional columns that youd like Resources to see from the
Available Optional Columns list, and move them to the left pane or right
pane lists.
5.
Move the column names up or down the list in the left pane or right pane
lists in order to change the order of columns Resources will see in their
expense reports.
6.
Click the Expense Approval Format tab to configure the list and order of
columns Approvers will see.
All time reports require users to specify a task.
Access Control
8.3.6
Third-party Time and Expenses
For third-party T&E transactions in the web client, a user needs appropriate
privileges. They are found on the General Tasks tab:
Project Transactions. This privilege allows users to create business

transactions against projects.
Organization Transactions. This privilege allows users to create business

transactions against organization units. Users with this privilege must also
have company access in order to create such transactions.
For more information about company access, refer to Company Access on

page 270. For more information about pool access, refer to Overview of
OAPs on page 222.
Permissions for third-party T&E are granted separately from permissions for
native T&E, enabling you to assign third-party and native administration to
different users.
Access Control
8.4
Accounts
Everyone who uses Primavera needs an account that defines access to data and
application functionality. The default password created for all user-defined
accounts is newuser. Note that these passwords are only used if the account is
authenticated by Primavera (refer to Authentication Options on page 151).
By default, Primavera contains an admin account that has global access. This
account resides in the top-level domain of your pool structure. The default
password for this account is admin. You should exercise the necessary security
precautions, including changing your password regularly. See Changing a
Password on page 262.
The admin account has three exceptional attributes:
By residing in the Enterprise domain, the admin account is internal to all

domains.
By owning the Enterprise domain, the admin account is an inherited owner

of all pools and objects.
By being assigned the Administrator access role, the admin account has
access to the Configuration tool and the Security and Account Manager. This
role grants global access, including access to the web client Admin page.
Accounts created for users who will administer Primavera should share these
attributes.
This section includes the following information:
Types of Accounts
Accounts and Access
Adding Non-resource Accounts
Updating Accounts
Resetting Passwords
Removing Non-resource Accounts
Changing a Password
Access Control
8.4.1
Types of Accounts
Primavera provides two types of accounts, resource and non-resource:
Resource accounts are generated automatically when resource profiles are

created, providing your resources with access to Primavera.
Non-resource accounts are manually created for individuals who need access
to Primavera but do not have resource profiles. For example, you might
create non-resource accounts for system administrators, resource
coordinators, and project managers.
The crucial factors of an account are:
whether the account is created for a resource or non-resource (that is,

whether it is associated with a resource profile) determines the way it is
created, updated, and deleted.
the accounts location in the pool structure determines the domains to which
the account is internal.
the access roles associated with the account determine access to data in the
domain that contains the account (internal access).
any pools or business objects owned by an account also determine access to

data.
Resource Accounts
Primavera generates a resource account when a resource profile is created. The
pool in which the resource profile is created determines the location of the
associated resource account. The account is placed in the domain that contains
the pool holding the resource profile. If the pool above the resource pool is not a
domain, the account is placed in the next domain up the pool structure. The
account is internal to this domain and to any sub-domains, as well.
When the resource account is generated, users must either enter a login ID for the
resource, or allow Primavera to generate an ID, depending on the authentication
method that Primavera employs.
Access Control
When Primavera generates a login ID, it appends the resources last name to the
resources first initial. For example, the login generated for John Smith is JSmith.
If a second resource named John Smith joins your enterprise, his login is
generated by combining the first initial, last name, and Resource ID (for
example, JSmith_EV_RS_000324). During authentication, Login IDs are not
case-sensitive, but passwords are.
For more information regarding login IDs and passwords, refer to
Authentication Options on page 151.
The account that is generated owns the resource profile and can be granted My
Profile privileges to the profile. See Task Access Policies on page 224.
Resource accounts are automatically given the Resource access role. You can
assign other access roles in the Security and Account Managers Assign Access
Roles pane. For information, refer to Assigning Access Roles on page 268.
Non-Resource Accounts
Create non-resource accounts for individuals who need access to Primavera but
who do not have resource profiles. For example, the business analyst who
determines the qualifications your enterprise tracks may not be a staffable
resource. Nevertheless, she needs access to Primavera in order to modify the
Qualification Catalog.
A non-resource account is created explicitly in a particular domain. The account
is internal to this domain, and to any sub-domains.
When you add a non-resource account, you enter information about the account
(such as the domain in which it resides and the access role of the account) and
user (such as the first and last name, email address, and employer). Notifications
and staffing requests are sent to the email address you specify for the account, if
the user selects Email as the delivery method.
Access Control
8.4.2
Accounts and Access
Primavera provides a number of ways to define access to data. When determining

whether an account has access to a particular object, Primavera refers to the
various access control elements and grants combined privileges according to
those roles and policies.
If access to an object is defined in more than one way (that is, through both an
access role and through ownership), Primavera gives precedence as follows:
1.
The access role is the basis of the accounts privileges. It governs all internal
access that is not specified through pool policies.
2.
A pools Internal or External Access Policy can include the access role, thus
overriding the access generally granted by that role.
When a role that has been added to a pools Internal Access Policy is customized
to revoke a certain privilege, that privilege is revoked from all accounts that have
the role in this domain, regardless of other access roles.
3.
A pools Internal or External Access Policy can include the account, thus
overriding the access generally granted by the accounts roles.
4.
If the account owns the pool or object, the Owners entry of the Internal
Access Policy overrides the access granted to the account by the role.
5.
If the account owns the pool or object, access to alter the pool and its
membership is granted by the Maintenance Access Policy. These privileges
cannot override anything, as they do not overlap any other method of
granting access.
6.
Access to billing, posting, percent complete calculations, and most other

back-office accounting functionality is granted to users at the company level.
The privileges granted by the accounts access roles determine the
functionality the user can access. The user has privileges to perform those
functions in any company to which he is assigned company access.
Access Control
8.4.3
Adding Non-resource Accounts
Anyone who must access Primavera needs an account. If the user has a resource
profile, an account is automatically generated. Otherwise, a non-resource account
must be created manually.
To add a non-resource account:
1.

After you log in, the Access Control window appears.
2.
Click the User Accounts button.

The User Accounts pane appears.
3.
Select the Non-Resource tab.
4.
Browse the pool structure and select the domain to which this account will
belong.
5.
Click FileNew Account.

The Edit User Information window appears.
6.
Enter the individuals first and last names. This step is required.
7.
Enter a login name. This step is required.

For security reasons, Primavera recommends login IDs that are between
three and twenty characters in length.
8.
Enter an email address for this account. If you do not enter an email address,
this user cannot forward Primavera messages to email.
9.
Enter the name of the users employer.
10. Click OK.

11. Click FileSave.
Once you have created an account, you may associate it with one or more access
roles. If a user needs to access the Configuration tool or Security and Account
Manager, the account must be associated with the Administrator access role. See
Assigning Access Roles on page 268.
Access Control
Figure 8-11 User Accounts pane
Access Control
8.4.4
Updating Accounts
Update accounts to ensure they are current. For more information about updating
accounts, refer to Resetting Passwords, next, and Assigning Access Roles
on page 268.
To update an account:
1.

2.

3.
Depending on whether the user has a resource profile, click either the
Resources or Non-Resources tab.
The appropriate tab appears.
4.
Locate and double-click the account you want to update.

The Edit User Information window appears.
5.
Change the appropriate values.

If this is a non-resource, you can reset the password or change the users
name, login name, email address, and employer. If this is a resource, you can
reset the password and change the email address and login name. Changing
the email account in this window also updates the resources profile.
If you change the login name or user name, and this user has access to the
analytic applications, you must also reimport the user. For instructions, refer
to Analytic Applications.
If an email address has not been provided for an account, that user will not
be able to set the Also send messages to my email account option accessed
by selecting ToolsOptions in the Command Center.
6.
Click FileSave.
Associate an account to access roles in the Assign Access Roles pane.
Access Control
8.4.5
Resetting Passwords
If a user forgets his password, you can reset the password to the default. The
default password for resource and non-resource accounts is newuser. Users
should change their passwords regularly.
If you are using LDAP authentication only, you cannot reset passwords in
Primavera, with the exception of the admin accounts password. If you are using
both methods, password changes to externally-authenticated accounts have no
effect.
To reset a Primavera-authenticated password:

1.

2.

3.
Depending on whether the account is associated with a resource profile,

select either the Resources or Non-Resources tab.
The appropriate tab appears.
4.
From the list of accounts, select the appropriate account.
5.
Click the Reset Password button.
6.
Click FileSave.
The accounts password is reset to newuser.

When you reset the admin accounts password, the new password is admin.
Access Control
8.4.6
Removing Non-resource Accounts
Resource accounts are deleted automatically when the resource is terminated or a

resource profile is removed. Non-resource accounts must be removed manually.
To remove a non-resource account:
1.

2.

3.
Select the Non-Resource tab.
4.
Select the account to remove.
5.
Click FileRemove Account.
6.
Click FileSave.
Access Control
8.4.7
Changing a Password
Change the admin accounts password regularly.

If you are using LDAP only, you cannot change passwords in Primavera, with the
exception of the admin accounts password. If you are using both methods,
password changes to externally-authenticated accounts have no effect.
To change the admin password:

1.
Log into Primavera using the admin account.
2.
In Command Center, click ToolsOptions...

The Options window appears, displaying the Password tab.
3.
Enter the current password in the Old Password field.
4.
Enter the new password in the New Password field.
5.
Enter the new password in the Confirm New Password field.
6.
Click OK.
Your password is changed. If a user forgets his passwords, you can reset it to the
default. See Resetting Passwords on page 260.
Access Control
8.5
Access Role Catalog
Access roles are the principal element of access control in Primavera. The access
role catalog lists the access roles defined for your enterprise. An access role is a
set of privileges that are consistently granted to a type of user. Access roles only
grant privileges to objects within the associated accounts domain. In the case of
financial functionality, the privileges are granted at the company level.
Access Role Overview
Default Access Roles
Conflicting Access Roles
Configuring the Access Role Catalog
Assigning Access Roles
8.5.1
Access Role Overview
When you configure access roles, start by defining one access role for each
unique type of user in your enterprise. For example, you might have access roles
for administrators, accountants, resources, resource coordinators, and project
managers. Once you determine the various sets of rights you need to define, you
can sometimes abstract out sub-sets of privileges. Then combine access roles to
provide each user type the exact privileges they need. This approach simplifies
the maintenance of the Access Role catalog.
Consider an example in which there are three different user types: users that
create opportunities, users that create projects, and users that create both. You
could define two access roles: Access Role A, that granted project create
privileges, and Access Role B, that granted opportunity create privileges. Users
who only needed to create projects would be assigned Access Role A, users who
needed to create opportunities would be assigned Access Role B, and users who
needed to create both projects and opportunities would be granted Access Role A
and Access Role B.
Access Control
If an account does not have an access role, the user can log in, but only has the
access granted to them through ownership or a customized OAP. In most cases,
the user has no access.
You can also define enterprise-level access rights for roles that can have access to
MS Project administration and configuration screens using both ProjectLink and
ProjectServerLink.
Note that an access role grants and restricts data at the company and pool level:
Pool level access control governs most functionality and data. See Pool
Structure on page 204.
Company level access control governs financial functionality and data. It

only applies to accounting and delivery functionality. Access to a company
combines with the users access roles to grant the user privileges to both data
and tasks. See Company Access on page 270.
8.5.2
Default Access Roles
Primavera contains two access roles that cannot be deleted:
Administrator. The administrator access role grants all privileges. It

automatically grants access to the web clients Administration page,
Configuration tool, and Security and Account Manager. It also grants
privileges to change login IDs (either in the resource profile or the Security
and Account Manager). You cannot edit this role, other than to change its
description. This role is automatically granted to the admin account.
Resource. By default, the Resource access role grants the View privileges
listed on the TAPs My Profile tab, as well as granting View Domains/Pools,
which allow resources to view the pool structure. This modifiable role is
automatically granted to all resource accounts.
You must manually create all other access roles that your enterprise requires.
Access Control
8.5.3
Conflicting Access Roles
If an account is assigned two access roles that conflict, by default the privileges
in question are revoked. For example, consider an account with two access roles:
one access role revokes the Create Project privilege and the other grants the
Create Project privilege. The Create Project privilege is revoked from this
account.
However each pool inherits access role TAP settings from its parent pool, which
complicates the issue. Privileges that override the parent pools setting have
greater weight than (trump) inherited privileges. Consider an account that has
two access roles. By default, both access roles revoke the Create Project privilege
and grant the Create Client privilege. At a particular level of the pool structure:
Access Role A is overridden to grant the Create Project privilege and

Access Role B inherits the value of revoke. The Create Project privilege is
granted in this pool.
Access Role A is overridden to revoke the Create Client privilege and

Access Role B inherits the value of grant. The Create Client privilege is
revoked in this pool.
For each level of the pool structure, Primavera evaluates such conflicting access
roles using the following precedence:
Setting
Precedence
Overriding revoke trumps any other access role setting for the
pool.
Overriding grant trumps any inherited access role setting for the
pool. It is trumped by overriding revoke.
Inherited revoke trumps inherited grant. It is trumped by any
overridden access role setting for the pool.
Inherited grant is trumped by any inherited or overriding access
role setting for the pool.
Access Control
The following table shows how Primavera resolves conflicting privileges:
8.5.4
Revoke
Revoke
Revoke
Grant
Configuring the Access Role Catalog
To add an access role:
1.

2.
Click the Access Roles button.

The Access Role Catalog pane appears.
3.
Click FileNewAccess Role.
4.
Enter a name for the access role. This step is required.
5.
Enter a description of the access role.
6.
Click on a box in the Task Access Policy grid to grant access for that action
in a UI component. For example, click the top left box in the General Tasks
tab to grant the Create privilege on resource profiles. Refer to Customizing
an OAP on page 238 for icon meanings.
7.
Select each tab and enable each type of access this role will grant.
8.
Click FileSave.
The new access role is added to the catalog.

Select an access role and click FileClone to create a new access role based on
an existing role.
Access Control
For more information on the Task Access Policy, see page 224.
Figure 8-12 Access Role Catalog
Access Control
8.5.5
Assigning Access Roles
Once access roles are defined, you can explicitly assign them to the appropriate
accounts.
When an account without an access role logs into Primavera, the user can log in,
but in most cases will not be able to view or modify data.
To assign an access role to an account:

1.

2.
Click the Assign Access Roles button.

The Assign Access Roles pane appears.
3.
Click the Select User Accounts button to find the account you are updating.
4.
In the Find window, search for the account you are updating, select it, and
click OK.
The users name appears in the User Account List.
5.
In the User Account List, select the account.
6.
In the Access Roles For: list, click the check box of the access role you are
assigning to this account.
7.
Click FileSave.
The access role is added to the account.

You can add any number of roles to an account.
Click each tab in the bottom-right pane to review this accounts composite
privileges (based on all roles assigned).
Access Control
Figure 8-13 Assign Access Roles to Accounts
Access Control
8.6
Company Access
Financial data are not organized along the lines of the pool structure; the data
follow the organization structure, instead. Each company can be configured with
differing financial rules that default to the company's organization units and
projects. These financial rules can be overridden at the project and position
levels.
In order to accommodate the needs of accounting users, Primavera limits and
grants privileges to financial data along the lines of the organization structure. A
user who is granted financial privileges by an access role must also be assigned
company access. The user can perform those actions in any company to which he
has access.
For example, consider an access role that grants the Create Percent Complete
privilege. This role is assigned to a user that has access to the Europe company,
but not the North America company. In this case, the user would have privileges
to create percent complete calculations for projects associated with organization
units in the Europe company only.
Note that resources are automatically granted access in the company in which
their organization units reside. Thus, you should use caution when granting
financial access to resources.
Because financial privileges do not pertain to pools, you cannot grant them in a
pools OAP. They can only be granted by creating an access role and assigning it
to a user that has access to one or more companies. Any access you grant is
granted in all companies to which the user has access.
To assign company access:

1.

2.
Click the Assign Company Access button.

The Assign Company Access pane appears.
Access Control
3.
Click the Select User Accounts button to find the account you are updating.
4.
In the Find window, search for the account you are updating, select it, and
click OK.
The user's name appears in the User Account List.
5.
In the User Account List, select the account.

The right side of the pane displays all the companies in your enterprise.
6.
Click the check box in the Access column to grant the account access to this
company.
Any rights this account is granted by an access role are granted within the
companies you specify here.
7.
Click the check box in the Default column to make a company the user's
default. This is the company defaulted to the In Company field of all
financial finders.
8.
Click FileSave.
If the account is assigned an access role that grants financial data privileges, the
user can now be granted access to financial data in the company you specified.
Note that the account must also be assigned an access role that grants financial
data privileges.
Access Control
8.7
Access Control Recommendations
This section provides tips for creating an access control model within Primavera:
General Recommendations
Access Role Recommendations
Pool Structure Recommendations
Time and Expenses Administrator Recommendations
For general tips regarding the pool structure, refer to Recommendations for
Pool Structure Configuration on page 217.
Access Control
8.7.1
General Recommendations
Before you create the access control model, consider these tips:
Model your access roles, pool structure, and Object Access Policies (OAPs)
on paper before you create them in Primavera. It is often helpful to have a
visual representation of the access control model you are creating.
Take a task-oriented approach to access control. This will help you grant the
right privileges to users based on their job functions.
Implement your access control model iteratively. This will help you
understand the ramifications of various changes.
Do not overcomplicate your access roles and OAPs. Because the Task
Access Policy (TAP) is a powerful tool, you can create a very complicated
access model using very simple access roles and OAPs. The simpler your
access roles and OAPs are, the easier it will be to troubleshoot and maintain
access control.
The majority of your access control model should be implemented through

access roles or in the Enterprise domains OAP. Ensure that the access roles
you define will generally grant your users the correct permissions, regardless
of the pool structures OAPs. By creating an Enterprise-level OAP that is
sensible for your entire enterprise, you can minimize the need for
customization, as all sub-domains inherit that OAP.
The relationships between pools and domains, accounts and domains, and
business objects and domains determine the privileges your users have.
When modeling access control, focus on these relationships.
When assigning company access, remember that access is granted to all

financial functionality and data throughout that company. Access to billing,
posting, and project accounting is not restricted by the pool structure, and
any privileges granted in one company are granted in any other company to
which the account has access. Since each resource is granted access to their
organization units company, use caution when granting them financial
privileges.
Access Control
8.7.2
Access Role Recommendations
Before you create access roles, consider these tips:
When you grant an Update privilege, the corresponding View privilege is

also granted. Similarly, when you grant a Create privilege, the corresponding
Update and View privileges are granted. In some cases (such as billing and
cost rates) you can manually override this, and grant Update without View.
In this case, the user does not have access to data.
When you define an access role for users who will staff resources on
projects, you must grant at least two project commitment privileges: grant
privileges in the resource profile and in the project profile. Otherwise,
resources cannot be staffed to project positions. In addition, you can grant
privileges in the Team Builder and Team Locator.
When you define an access role for users who will evaluate resources, note
that the role does not need to grant the Update Resource privilege.
When you define access roles for users who will create new opportunities
and projects, you must grant them View access to clients as well as Create
and Update access to opportunities or projects. Otherwise, users cannot
specify a client and save the profile.
When you define access roles for users who will post transactions, bill
clients, or account for projects, note that the access is granted at the company
level rather than being granted at the pool level. Because of this, financial
privileges appear on the TAP when you define an access role, but not when
you customize a pools OAP.
Abstract out common privileges between user types and create roles that can
be combined to grant the proper access to each account.
Access Control
8.7.3
Pool Structure Recommendations
Before you create the pool structure, consider these access control tips:
When you create resource pools, be sure that you explicitly define owners.
This allows users to select the appropriate recipients of staffing requests,
simplifying requesting for your users.
When you create a resource pool, identify its time and expenses approvers
immediately. If you do not select an approver, Auto-Approve is selected for
the pool, and resources non-project time and expenses can be reimbursed
without being reviewed and approved.
Select the owners of pools carefully. By default, the owner of an object pool
is granted all privileges to the objects in the pool. For example, the owner of
a resource pool has all privileges on the resources in that pool: Create,
Update, View, Delete, Terminate, Project Commitment Assign, Update
Billing Rate, and so forth.
An account is internal to the domain that contains it and to any sub-domains.

Thus, the Enterprise domain is internal to all other domains, and all other
domains are external to Enterprise. Use this to your advantage by defining
the OAP once at the Enterprise level. This policy is inherited by all subdomains. If you create the optimal policy, the inherited OAP is appropriate
for most pools, and few or none require customization.
Access Control
8.7.4
Time and Expenses Administrator

Recommendations
When identifying time and expenses administrators, consider these tips:
Time and expenses administrators should be considered an exception. Most

time and expenses approval should be processed through the usual means
defined for the project or resource pool. To ensure that reports are processed
in a timely manner, define a few time and expenses administrators who can
occasionally fill in for approvers.
If you plan to have a number of time and expenses approvers throughout

your pool structure (rather than defining a small number in high-level
domains), define access roles that grant time and expenses privileges. Then,
assign the roles to appropriate users in each domain. These users will have
permission to approve and enter time and expenses for all resources and nonresources internal to the domain.
Grant these permissions sparingly. Since your enterprise relies on these

reports to reimburse resources and bill clients, it is important that the
approval process remain secure. Minimize the number of people who can
enter and approve time on behalf of other users to ensure the integrity of
these sensitive data.
When selecting users that will have these permissions, be aware that it is
possible to grant a resource the permission to act on behalf of his own
approver, thus allowing him to approve his own reports. For example, you
might create a T&E Administration role, then grant it to a resource. This
resource would have permission to act on behalf of any approver in the
domain, including (potentially) his own approver, and could approve his
own reports. Though mildly unlikely, you should keep this possibility in
mind when modifying internal access policies and assigning administrator
roles.
By default, resource pool owners are granted all permissions in the pool they
own, including time and expenses permissions. If your resource pools are
owned by users who do not have authority to act on behalf of other users (for
example, staffing coordinators), modify the Owners entry for each resource
Access Control
pool to revoke time and expenses permissions.
Access Control
8.8
Access Control Example
The following is a simplified example of access control in Primavera. It is

intended to familiarize you with some access control concepts. Note that
Primavera provides more tasks and UI components than are shown in the
example, and that most enterprises have more access roles.
Example Pool Structure
Example Organization Structure
Example of Access Roles
Example OAPs
Example Account Access
Access Control
8.8.1
Example Pool Structure
This figure depicts a portion of the fictitious pool structure that is referenced in
the access control example.
Your Service Business
East Coast Domain
West Coast Domain
Resource
Pool
Project Pool
Figure 8-14 Example Pool Structure

For more information regarding the pool structure, refer to Pool Structure on
page 204.
Access Control
8.8.2
Example Organization Structure
This figure depicts a the organization structure root and the companies defined in
the fictitious organization structure that is referenced in the access control
example.
Your Service Business
Technical Practice
Healthcare Practice
Figure 8-15 Example Organization Structure
Logistics Practice
Access Control
8.8.3
Example of Access Roles
This example includes three access roles: Resource Coordinator, Project

Manager, and Project Accountant. The following tables depict the privileges that
the access roles grant on resource and project profiles.
Table 8-2
Example Resource Coordinator Access Role

Create
Update
View
Delete
Resource
Profiles
Yes
Yes
Yes
Yes
Project
Profiles
No
Yes
Yes
No
Financial
Rules
No
No
No
No
Table 8-3
Example Project Manager Access Role

Create
Update
View
Delete
Resource
Profiles
No
No
Yes
No
Project
Profiles
Yes
Yes
Yes
Yes
Financial
Rules
No
No
Yes
No
Access Control
Table 8-4
Example Project Accountant Access Role

Create
Update
View
Delete
Resource
Profiles
No
No
No
No
Project
Profiles
No
No
No
No
Adjustments
Yes
Yes
Yes
Yes
This example is simplified: most enterprises define more than three access roles,
and the TAP includes more UI components and privileges than are included here.
Access Control
8.8.4
Example OAPs
At the top level of the pool structure, the OAP is not customized and reflects the
default settings of the access roles.
The West Coast Domains OAP is customized to override the Resource
Coordinator and Project Manager roles. The following tables depict the internal
and external access policies for the West Coast Domain in the Example Pool
Structure. In the example, pool owners have all maintenance privileges. For
information on access policies, refer to Overview of OAPs on page 222.
Resource Coordinator Access Role
Table 8-5
Internal Access Policy for Resource Coordinators

Create
Update
View
Delete
Resource
Profile
Yes
Yes
Yes
No
Project
Profile
No
No
Yes
No
Table 8-6
External Access Policy for Resource Coordinators

Create
Update
View
Delete
Resource
Profile
No
No
Yes
No
Project
Profile
No
No
Yes
No
Access Control
Project Manager Access Role

Table 8-7
Internal Access Policy for Project Manager

Create
Update
View
Delete
Resource
Profile
No
No
Yes
No
Project
Profile
Yes
Yes
Yes
No
Table 8-8
External Access Policy for Project Manager

Create
Update
View
Delete
Resource
Profile
No
No
Yes
No
Project
Profile
No
No
Yes
No
Project Accountant Access Role

Because financial access is granted at the company level, and is not governed by
the pool structure, financial privileges do not appear in pools OAPs.
Access Control
8.8.5
Example Account Access
Given the example pool structure, access roles, and object access policies,
accounts with the Resource Coordinator, Project Manager, and Project
Accountant access roles will have the following privileges. This section gives an
example of how organizations can configure their users permissions in the pool
structure separately from their company permissions.
Pool Structure Access
Users in the West Coast domain would have the following privileges in the West
Coast domain:
Resource Coordinators can create, update, and view resources. They can also
view projects.
Project Managers can view resources. They can also create, update, and view
projects.
Users in the East Coast domain would have the following privileges in the West
Coast domain:
Resource Coordinators can view resources and projects.
Project Managers can view resources and projects.
Access Control
Company Access
Given the example organization structure and access roles, users assigned the
Project Accountant role with company access to the Technical and Logistics
practices (but not the Healthcare Practice) would have these privileges in the
following companies:
Technical Practice. Create, update, view, and delete expense

reimbursements, and view access to all the supporting project and resource
data necessary to perform those actions.
Healthcare Practice. None.
Logistics Practice. Create, update, view, and delete expense reimbursements,

and view access to all the supporting project and resource data necessary to
perform those actions.
RDBMS Recommendations
9.
This chapter recommends tasks and policies for the RDBMS accessed by
Primavera. It includes the following sections:
Backup and Restore
Upgrading Between Primavera Versions
Microsoft SQL Server
Oracle
For supported version numbers, refer to Certified Software Platforms on

page 420. For information on populating the rate table, refer to Reports and
Rate Tables on page 178.
Consider the RDBMS configuration values recommended in this chapter as
general guidelines. These values vary, depending on the size of the database.
9.1
Backup and Restore
As with all databases, it is important to back up the Primavera databases

regularly, and to test restore procedures rigorously. You should also back up the
Primavera databases prior to upgrading to a new Primavera version. If problems
arise during the installation, use the backups to restore a functioning system. For
specific instructions on backing up and restoring the database:
For information about backup and restoration of databases, refer to the
documentation associate with the RDBMS. In the case of Oracle, the core
database must be restored using a batch or shell file provided by Primavera.
For more information, refer to Restoring Databases on page 310.
For information about backup and restoration of collaboration libraries, refer

to the documentation provided with WorkSite MP.
If you implement Delivery Manager, it is very important to make synchronized

backups of PVDB and DMDB. You must also restore a matched set of databases.
If you implement collaboration, the same constraint applies: you must back up and
restore its database and file server when you backup and restore PVDB and
DMDB.
If you restore databases that do not match exactly, your data integrity is
compromised; end-users will be unable to save data, and time and expenses
information will not be synchronized. In extreme cases, you must synchronize
your populated PVDB with an empty DMDB. Refer to Synchronization on
page 340.
Primavera does not support partial or point-in-time recovery.
To maximize the availability of your production system and maintain consistent

backups, Primavera recommends that you follow these common industry
practices:
Consult your Information Technology department to leverage their expertise
and follow internal best-practices.
Use a RAID disk configuration that provides fault-tolerance for all

Primavera databases (except the Data Mart Target database) and for the
WorkSiteMP fileserver.
Schedule hot backups during periods of low system activity. All backups, for
all databases as well as the WorkSiteMP fileserver, should be made in
tandem.
When Primavera server is stopped, take cold backups before performing

system maintenance tasks such as an upgrade. As with the hot backups, all
cold backups for both databases and the WorkSiteMP fileserver should be
made in tandem.
If you use Delivery Manager, schedule your DMDB database backup to occur
before the core database to simplify the process of synchronizing should a
database fail.
When restoring, note the following:

Restoring a Primavera database with a different version of Primavera may
fail and corrupt the database. For more information, refer to Upgrading
Between Primavera Versions on page 290.
Primavera does not necessarily support later versions of the RDBMS than
those listed in Certifications on page 419.
Contact Customer Support for assistance in transferring data between versions

of the RDBMS.
9.2
Upgrading Between Primavera Versions
Before upgrading to this version of Primavera, refer to the release notes and the
upgrade documentation provided by Primavera. The upgrade documentation is
found in the upgradePreparation ZIP archive found on the distribution image (a
downloadable file).
Due to the nature of the changes between previous versions and the new version,
such as changes to the data model, the upgrade process often includes a number
of procedures that must be taken in addition to just installing and configuring the
Primavera software. The upgrade documentation will provide complete step-bystep instructions.
9.3
This section describes some of the major tasks associated with the Primavera
database when it is stored in a Microsoft SQL Server.
Database Sizing
MS SQL Server Connectivity
Primavera-Provided Files
Creating the Core Schema Manually
Creating the Delivery Manager Schema Manually
Creating the Data Mart Schemas Manually
Primavera recommends that the SQL Server use the dictionary sort order, and
that it be configured as case-insensitive.
9.3.1
Database Sizing
When you create the new database, keep these tips in mind:
Create each database and each log on a separate physical device.
The master database should not include user tables of any kind.
The following tables recommend initial sizes for the Primavera databases and
associated objects. The sizes recommended are general guidelines. You will
eventually need significantly more space, particularly if you implement Time &
Expenses. Carefully watch the sizes of the databases and logs to ensure that they
they are adequate and do not fill the disk.
Table 9-1
MS SQL Recommendations for Large Companies
Database Element
Recommended Size
Primavera database (PVDB)
If you implement Time & Expenses, 10

GB
DM database (DMDB)
4 GB
Dedicate a total of 50 GB of hard disk space to storage, backups, and logs for
these databases.
Table 9-2
MS SQL Recommendations for Midsize Companies
Database Element
Recommended Size
Primavera database (PVDB)
1 GB
DM database (DMDB)
1 GB
Dedicate a total of 20 GB of hard disk space to storage, backups, and logs for
these databases.
In addition, the analytic applications rely on the databases listed in 9-3, next.
Table 9-3
Analytic Application Database Recommendations
Database Element
Recommended Size
Data Mart database
Approximately 30 times the size of Primavera

(PVDB) database.
OLAP database
Approximately 2-3 GB. Plan for additional free

hard drive space to accommodate the databases as
they grow.
StrategicPlanning
Approximately 20% of the space required by

PVDB.
This space is typically sufficient for one to two years worth of data, assuming
Data Mart is run once a day. Allow the databases to grow, but limit their
maximum sizes so that they do not fill the entire disk. If a database grows to the
size of the full disk on which it resides, recovery is impossible.
For information on the databases used by third-party software (such as WorkSite
MP), refer to the documentation associated with them.
9.3.2
Enable Address Windowing Extensions

for SQL Server 2005
Enable Address Windowing Extensions (AWE) for the SQL Server 2005
installation to ensure that the SQL Server 2005 database server is tuned for
optimal performance. You need at least 4 GB of physical memory (RAM).
To enable AWE:
1.
Launch the SQL Server Management Studio application.
2.
Connect to the necessary SQL Server 2005 instance as sa.
3.
In the Object Explorer, right-click on the above SQL Server instance and
select Properties.
4.
In the Properties window select Memory from the left pane.
5.
Check the Use AWE to allocate memory box.
For more information about enabling AWE, see http://

msdn2.microsoft.com/en-us/library/ms190673.aspx.
For additional SQL Server 2005 performance tuning tips, refer to http://
www.microsoft.com/technet/prodtechnol/sql/2005/tsprfprb.mspx.
9.3.3
MS SQL Server Connectivity
The Primavera report server requires connectivity to the database server that
stores your Primavera databases.
In order for the report server to connect to the databases (PVDB, DMDB, and
Target), you must complete the configuration of an ODBC Data Source Names
(DSNs) that correctly point to them. For instructions, refer to Editing DSNs
on page 79.
For instructions about DSNs, refer to the documentation provided by Microsoft.
9.3.4
Primavera provides files to help you maintain its MSSQL databases. These files
are used for:
General Maintenance
Deleting Messages
Deleting Terminated Resources Data
Finding Saved Queries
Do not use custom SQL to update, insert, or delete data in any Primavera
database unless authorized by Primavera Customer Support. Unauthorized
changes can cause data corruption.
General Maintenance
Primavera provides the maintainssdb.bat file to help your DBA support the
PVDB database. This batch file, found in primavera\utils\database\mssql, runs
standard maintenance procedures that are recommended by Microsoft. It updates
information in the master database to ensure that queries are executed efficiently.
Your DBA should run the batch file periodically. The frequency with which this
file runs depends on system usage: in periods of greater usage, run the script
more often. Stop the server application before running the maintainssdb.bat
file, and back up the database after it completes.
To run maintainssdb:
1.
Click StartProgramsAccessoriesSystem ToolsCommand

Prompt.
2.
In the window, change directories until you are in the utils\database\mssql

folder within the folder where you installed the server application. If you
used the default directory, change directories by typing:
3.

maintainssdb [SQL_Server_Host] [Database_Name] [User_ID]
[Password]

[SQL_Server] is the name of the MS SQL Server instance. Typically, this
is the name of the computer hosting the RDBMS.
4.
Press Enter.
Text scrolls down the window. When the prompt appears, the script is done.
Deleting Messages
Primavera uses notifications and staffing messages to keep users informed and to
help them collaborate. However, some users may not delete messages they have
read, which can lead to poor performance of messaging and upgrade.
If your enterprise has used Primavera for a year or more, you may want to reduce
the size of the PVDB database by deleting old messages (such as notifications)
that end-users have not deleted.
The following files, which count and optionally delete messages from the core
database, are found in primavera\utils\database\mssql:
File Name
Purpose
countMessages.sql
Counts and deletes messages generated

automatically that are related to staffing
requests (such as time out messages).
countSystemMessages
.sql
Counts and deletes notifications, such as those

sent during an opportunitys evaluation or those
configured in the Messages panel of the
Configuration application.
Each file includes a cut-off date; you can delete messages older than the specified
date.
To delete messages, edit each file to uncomment the delete statements and run
each using Query Analyzer. The following steps provide details.
To delete messages:
1.

countSystemMessages.sql file using a text editor such as Notepad. This
file is found in the primavera\utils\database\mssql.

2.
Locate the code block that reads:

--delete from SystemMessage
--where creationDate < '2005-05-01'
-- and cid = 25186
-- just SystemMessages
--go
3.
Delete the dashes from the beginning of each line, and change the date if
necessary:
delete from SystemMessage
where creationDate < '2005-01-01'
and cid = 25186
go
Messages older than the specified date are deleted.

4.
5.
Run the countSystemMessages.sql file using Query Analyzer.
6.
Open the countMessages.sql file and repeat steps 2 through 5

When users are terminated, their saved queries and workforce planning models
remain in the system. Two scripts remove the data:
deleteSavedQueries.sql
deleteWPModels.sql
The scripts are fully commented. You can use them as-is or modify them to suit
your conditions.
The file FindSavedQueries.sql has sample SQL code for finding saved
queries of a given kind.
Users of the web client can save their search definitions as private queries. When
an object that is a criterion in a private query is deleted from the database, that
part of the query is no longer valid (the rest of the query remains valid). This
SQL file demonstrates how you can search the database to determine whether
users failed queries relied on deleted objects.
9.3.5
Creating the Core Schema Manually
If the core schema cannot be created by InstallShield, you can create it manually.
The install script creates the schema but does not create the database itself; an
empty Primavera database (PVDB by default) must exist before you create the
schema. The RDBMS must also be running.
To create the database schema and views:
1.

Prompt.
2.
In the window, change directories until you are in the utils\database\mssql

folder beneath the folder where you installed the server application. If you
used the default directory, change directories by typing:
3.
setupSSDB [SQL_Server] [Database_Name] [User_ID]
[Password]
[SQL_Server] is the name of the database server instance. Typically, this
is the name of the computer hosting MS SQL Server. Sometimes, this is the
name of the service appended to the name of the host (for example
primaverahost\sqlservice).
4.
Press Enter.
Text scrolls down the window. When the prompt appears, the script is done.
9.3.6
Creating the Delivery Manager Schema Manually
If the Delivery Manager schema is not created by InstallShield, it can be created

by running a batch file that is installed from the Primavera distribution image. If
you installed in the default directory, the DMDB scripts are found at
c:\primavera\utils\database\mssql\DM.
The name of this database cannot start with numbers.
These instructions assume that your MS SQL Server is running and contains an
empty database. You must also provide further information about ODBC DSNs.
For more information, refer to Editing DSNs on page 79. If you are upgrading
from a previous version, you must take alternate steps. For more information,
refer to Upgrading Between Primavera Versions on page 290.
To create the Delivery Manager schema:
1.

Prompt.

2.
In the window, change directories until you are in the exporter_DM\sql

folder beneath the folder where you installed the server application. For
example, change directories by typing:
cd Primavera\utils\database\mssql\DM
3.
At the command prompt, type:

installdmdb7 [SQL_Server_Host] [Database_Name] [User_ID]
[Password]

[SQL_Server_Host] is the name of the database server instance.
[Database_Name] is the name of the database. For example, DMDB.
permissions in the DMDB database should be comparable to the database
4.
Press Enter.
The script executes for several minutes. When the prompt appears, the
schema has been created.
For more information, refer to Delivery Manager Administration on page

339 and DM Database Options on page 148.
You must also run the stored procedures, as described in Running Delivery
Manager Stored Procedures on page 51.
9.3.7
Creating the Data Mart Schemas Manually
You must create the schemas for the two databases that Data Mart populates:
Creating the Data Mart Schema
Creating the OLAP Cubes

If the Data Mart (target) schema cannot be created by InstallShield, you can
create it manually.
Before creating the target database schema, in Microsoft SQL Server, create a
new, empty database to store the schema. For more information, refer to
Note that the target database must be configured as follows:
In databases Properties window, set the Recovery Option Model to
Simple.
In databases Properties window, enable the Auto Update Statistics and

Auto Create Statistics check boxes on the Options tab.
To create the Data Mart target database schema:
1.

Prompt.
2.
In the window, change directories until you are in the db\mssql folder
beneath the folder where you installed Data Mart. If you used the default
directory, change directories by typing:
cd primavera\datamart\db\mssql
3.

setupTargetDb <SQL_Server> <Database_Name> <User_ID>
<Password>

<SQL_Server> is the name of the database server instance. Typically, this is
the name of the computer hosting Microsoft SQL Server.
<Database_Name> is the name of the target database.
<User_ID> is the ID to use to log into the database server. This accounts
privileges in the target database should be comparable to the database
owners (DBOs) privileges.
<Password> is the password to the <User_ID> account.
4.
Press ENTER.
Creating the OLAP Cubes

If the OLAP cubes cannot be created by InstallShield, you can create them
manually.
The OLAP database is only supported in Microsoft SQL Analysis Services. The
default OLAP database name is PV_OLAP. You can change it in
EvDatamart.properties by the editing following property:
primavera.datamart.olap.dbname= PV_OLAP
To setup the OLAP database:
1.
While logged into Windows as pvuser, click

StartProgramsAccessoriesSystem ToolsCommand Prompt.
2.
In the window, change directories to [DATAMART]\db\mssql directory. If

you used the default directory, change directories by typing:
cd primavera\datamart\db\mssql
3.

setupOlapDb
This batch file does not take any arguments.

The setupOlapDB batch file relies on values in the Datamart.properties file. If
you have not properly identified the OLAP database server, setupOlapDB will
fail.
For information about pvuser, refer to Defining a Network User in
Windows on page 33.
9.4
Oracle
This section describes some of the major tasks associated with the Primavera
schema when it is stored in an Oracle instance. It assumes you access the
database instance as the user that owns the schema (that is, as PVDB).
Primavera provides both batch files and SQL files for use with Oracle:
Run shell files (*.sh) at a prompt.
Run SQL (*.sql) scripts in SQL*PLUS.
These batch files and SQL scripts write messages (including any errors) to log
files in the same directory. The log file has the same proper name as the script,
but has an *.LST extension. For example, running the setupssdb.sh file in
Solaris yields the following log files, among others: createSSschema.lst,
makeviews.lst, createReportingViews.lst,
createQueryDisplayListViews.lst, and verifySSDB.lst. Refer to these
files to ensure that the schema was created properly.
Build and Configuration Parameters
User Creation Script
PVDB Schema
Tablespace Sizing
Oracle Connectivity
Connection Management
Creating the Database Schemas
9.4.1
Build and Configuration Parameters
When Primavera is run against an Oracle instance, you must configure several
Oracle parameters that affect database performance; tune them properly to
improve database performance. Primaveras recommendations differ for the core
and Data Mart databases:
PVDB Recommendations
Data Mart Recommendations
Consult your Oracle DBA and the Oracle documentation for assistance.
PVDB Recommendations
At minimum the following parameters needs to be properly set:
DB_CACHE_SIZE (2GB, 3GB)
SHARED_POOL_SIZE (128MB, 700MB)
PGA_AGGREGATE_TARGET (500MB, 3GB)
LARGE_POOL_SIZE (64MB, 64MB)
JAVA_POOL_SIZE (64MB, 64MB)
SESSION_CACHED_CURSORS (100, 150)
HASH_JOIN_ENABLED (true, true)
OPTIMIZER_INDEX_COST_ADJ (10, 10)
OPTIMIZER_INDEX_CACHING (90,9 0)
SESSIONS (250, 250)
LOG_BUFFER (4MB, 4MB)
DB_BLOCK_SIZE (Appropriate for storage device, typically never below
OPEN_CURSORS (500, 500)
The Database Character Set should be set to AL32UTF8
The Database National Character Set should be set to AL16UTF16
16K)
Data Mart Recommendations

At minimum the following parameters needs to be properly set:
DB_CACHE_SIZE (1GB, 3GB)
SHARED_POOL_SIZE (128MB, 128MB)
PGA_AGGREGATE_TARGET (1.5 GB, 4GB)
LARGE_POOL_SIZE (64MB, 64MB)
JAVA_POOL_SIZE (0MB, 0MB)
SESSION_CACHED_CURSORS (leave default)
HASH_JOIN_ENABLED (true, true)
OPTIMIZER_INDEX_COST_ADJ (leave default)
OPTIMIZER_INDEX_CACHING (leave default)
SESSIONS (250, 250)
LOG_BUFFER (4MB, 4MB) (these values can be increased to 16 MB if you

implement fast disk arrays)
DB_BLOCK_SIZE (Appropriate for storage device, typically never below
16K)
OPEN_CURSORS (500, 500)
The Database Character Set should be set to AL32UTF8
The Database National Character Set should be set to AL16UTF16
9.4.2
User Creation Script
This script is an update of the previous version. Existing customers should be

careful to use only the version included with the current release.
Before creating the PVDB, target, strategicPlanning, and collaboration schemas,

you must create users to own them (for names and descriptions, refer to
RDBMS Prerequisites on page 36). Create these users by running the
createOracleUser SQL script. The script (createOracleUser.sql) is
found in the same directory that contains the Primavera installation executable
(setupwin32.exe) in Windows. After installation, it is also found in the
utils/database/oracle directory under the directory where you installed
Primavera.
The script prompts for the ID and password of one user at a time.
To run the script, you must login using the sysdba role.
Primavera recommends that you create the users listed in Table 2-1,
Required Databases, on page 37.
Oracle user IDs must have access to the system tables.
The script creates the user and grants the appropriate permissions; users that own
the Primavera schemas must have the permissions granted by the script.
Afterwards, to ensure that the script ran properly, refer to the *.LST log file
generated when the script was executed.
9.4.3
PVDB Schema
When you create the new core schema, keep these tips in mind:
By default, Primavera assumes that the user that owns the tables is named
PVDB. If you want to use another name, supply it instead, both in the scripts
and during Primavera installation.
Primavera should always connect to Oracle using the user ID that owns the
schema (PVDB).
The SYSTEM tablespace should not include user tables of any kind.
9.4.4
Tablespace Sizing
The createOracleUser.sql script (described in User Creation Script on

page 306) makes the following tablespace assignments:
PVDB is assigned to the USERS tablespace.
The temporary segment is assigned to the TEMP tablespace.
The following table recommends sizes for each of the required tablespaces. The
sizes recommended are general guidelines. You will eventually need
significantly more room, particularly if you implement Time and Expenses.
Carefully watch the sizes of the tablespaces to ensure that they do not fill the
disk.
Table 9-4
Oracle Recommendations
Tablespace
Size
USER_DATA or USERS
10 GB
UNDO
8 GB
SYSTEM
5 GB
DW_INDEX
4 GB
You must manually create the DW_INDEX tablespace, which is initialized when
you create the Data Mart schema. For assistance with this table space and the
indexes it contains, contact Primavera Customer Support.
In addition, the analytic applications rely on the databases listed in 9-5, next.
Table 9-5
Analytic Application Database Recommendations
Database Element
Recommended Size
Data Mart database
Approximately 30 times the size of Primavera

(PVDB) database.
OLAP database
(MS SQL only)
Approximately 2-3 GB. Plan for additional free hard

drive space to accommodate the databases as they
grow.
StrategicPlanning
Approximately 20% of the space required by PVDB.
This space is typically sufficient for one to two years worth of data, assuming
Data Mart is run once a day.
If you use Data Mart, the data tablespace is likely to require more space than is
typical. To avoid an overflow error during Data Mart processing, dedicate plenty of
space to the data tablespace or allow it to auto-grow.
Allow the databases to auto-grow, but limit their maximum sizes so that they do
not fill the entire disk. If a database grows to the size of the full disk on which it
resides, recovery is impossible.
For information on the databases used by third-party software (such as WorkSite
MP), refer to the documentation associated with them.
9.4.5
Oracle Connectivity
The report server relies on an ODBC DSN and the SQL scripts provided with
Primavera rely on a database alias. Both must point to your database instance.
For instructions on creating a database alias, refer to the documentation
associated with Oracle.
Before creating the data source, you must install the Oracle Client. Refer to
Certifications on page 419 for supported versions.
For instructions about creating DSNs and database aliases, refer to the associated
documentation.
Note that you must also configure the evReportsConfig.properties file in

order to use Actuate iServer with Primavera. For more information, refer to
Setting Report Properties on page 327.
9.4.6
Connection Management
When the server application starts, it establishes several connections using the
supported connectivity software. Additional connections may be dynamically
started and stopped based on load.
Unless your Oracle instance uses Oracle Multi-Threaded Server (MTS), these
connections result in Oracle server processes that may be orphaned when the
server application shuts down.
If these unused connections are left open, you will experience performance
degradation. For instructions about closing unused connections, refer to the
documentation associated with Oracle.
9.4.7
Primavera provides files to help you maintain its Oracle databases. These files
are used for:
Restoring Databases
PVDB Maintenance
Deleting Messages
Do not use custom SQL to update, insert, or delete data in any Primavera
database unless authorized by Primavera Customer Support. Unauthorized
changes can cause data corruption.
Restoring Databases
Primavera relies on Oracle functionality that requires specific restoration steps.
When restoring a backup of the PVDB database, use the
restoreCoreOracleDb.sh file to restore the schema. The following procedure
assumes you are running Solaris.
To run restoreCoreOracleDb:
1.

folder beneath the Primavera installation directory. For example, in Solaris,
type:
cd primavera/utils/database/oracle
2.

./restoreCoreOracleDb.sh [Database_Alias] [User_ID]
[Password] [Filename] [Exporting_User]

[Database_Alias] is the name of the an alias that points to the database
instance that will store the Primavera schema (PVDB).
[User_ID] is the ID of the account to use to connect. For example, PVDB.
[Filename] is the name of the file to restore.

[Exporting_User] is the ID of the account that created the file you are
restoring.
3.
Press Enter.
When the prompt appears, the Primavera schema is complete.

To ensure that the scripts ran properly, refer to the *.LST log files generated
when the shell file was executed.
PVDB Maintenance
Primavera provides the maintainssdb.sh shell script to help your DBA
support the PVDB database. This batch file, found in primavera/utils/database/
oracle, runs standard maintenance procedures that are recommended by Oracle. It
updates information in the schema to ensure that queries are executed efficiently.
Your DBA should run the batch file periodically. The frequency with which you
run this file depends on your Primavera usage: in periods of greater usage, run
the script more often. Stop the server application before you run the
maintainssdb.bat file, and backup the database after the batch file completes.
To run maintainssdb:
1.

folder beneath the Primavera installation directory. For example, in Solaris,
type:
cd primavera/utils/database/oracle
2.

./maintainssdb.sh [Database_Alias] [User_ID] [Password]

instance that stores the Primavera schema (PVDB).

[User_ID] is the ID of the account that owns these tables. For example,
PVDB.
3.
Press Enter.
When the prompt appears, the Primavera schema is complete.

when the shell file was executed.
Deleting Messages
Primavera uses notifications and staffing messages to keep users informed and to
help them collaborate. However, some users may not delete messages they have
read, which can lead to poor performance of messaging and upgrade.
If your enterprise has used Primavera for a year or more, you may want to reduce
the size of the PVDB database by deleting old messages (such as notifications)
that end-users have not deleted through the web client.
The following files, which count and optionally delete messages from the core
database, are found in primavera/utils/database/oracle:
File Name
Purpose
countMessages.sql
Counts and deletes messages generated

automatically that are related to staffing
requests (such as time out messages).
countSystemMessages
.sql
Counts and deletes notifications, such as those

sent during an opportunitys evaluation or those
configured in the Messages panel of the
Configuration application.
Each file includes a cut-off date; you can delete messages older than the specified
date.
To delete messages, edit each file to uncomment the delete statements and run
each using SQL*PLUS. The following steps provide details.
To delete messages:
1.

countSystemMessages.sql file using a text editor such as vi. This file is
found in the primavera/utils/database/oracle.

2.
Locate the code block that reads:

--delete from SystemMessage
--where creationDate < '2005-05-01'
-- and cid = 25186
--go
3.
Delete the dashes from the beginning of each line, and change the date if
necessary:
delete from SystemMessage
where creationDate < '2005-01-01'
and cid = 25186
go
Messages older than the specified date are deleted.

4.
5.
Run the countSystemMessages.sql file using SQL*PLUS.
6.
Open the countMessages.sql file and repeat 2 through 5

When users are terminated, their saved queries and workforce planning models
remain in the system. Two scripts remove the data:
deleteSavedQueries.sql
deleteWPModels.sql
The scripts are fully commented. You can use them as-is or modify them to suit
your conditions.

The file FindSavedQueries.sql has sample SQL code for finding saved
queries of a given kind.
9.4.8
Creating the Database Schemas
In Oracle, the Primavera database schemas are created by running the setup shell
files. Depending on the functionality you implement, Primavera requires:
Database or User
Default Name
Primavera core database
PVDB
Data Mart target database
target
Portfolio Management operational

database
strategicPlanning
Collaboration Database
primavera
The OLAP and Delivery Manager databases are not supported in Oracle.These
schemas are created by running a batch file that is installed from the Primavera
distribution image. If you installed to the default directory, the DMDB scripts are
found at c:\primavera\utils\database\mssql\DM. For more information, refer to
Creating the Delivery Manager Schema Manually on page 299 and
Creating the OLAP Cubes on page 302.
Before running the schema creation script against an Oracle instance, you must
take additional steps. The following sections discuss:
Configuring Oracle
Creating the Core Schema
The collaboration schema is created through WorkSite MP.
Before creating the database schemas, refer to Build and Configuration

Parameters on page 304 for specific information on configuring Oracle. For
more information about P)rimaveras databases, refer to RDBMS
Configuring Oracle
Before you can create the schema, you must:
Define the ORACLE_HOME environment variable to point to the directory
where the Oracle 9.2 client is installed.
Include the ORACLE_HOME\bin directory in your PATH environment

variable. If multiple Oracle clients are installed, the Oracle 9.2 clients bin
directory must appear before any other Oracle clients bin directory.
Create a database alias that points to the instance that will store the
Primavera schemas. This database alias is used by the schema creation
scripts. For instructions for creating a database alias, refer the documentation
provided by Oracle.
Create users to own the Primavera schemas. For example, create a user
named PVDB to own the core schema. Refer to User Creation Script on
page 306 for more information.
The Oracle client is necessary to create the schema, run scripts (such as
maintainssdb) against the database, and to run Actuate reports.
Creating the Core Schema

Once you have properly configured your Oracle instance, run the schema
creation script.
To create the database schema and views:
1.
At the command prompt, change directories until you are in the utils/
database/oracle folder beneath the Primavera installation directory. For
example, in Solaris, type:
cd /export/home/user1/primavera/utils/database/oracle
2.

./setupSSDB.sh [Database_Alias] [User_ID] [Password]

instance that will store the Primavera schema (PVDB).

[User_ID] is the ID of the account that will own these tables. For example,
PVDB.
3.
Press Enter.
Running createSSschema.sql appears in the command prompt
window, and a new command prompt window appears. Text begins to scroll
down both windows.
When prompts appear in both windows, the Primavera schema is complete.
when the file was executed.
You must create the schemas for the two databases Data Mart populates:
The Data Mart schema is described in this section.
The OLAP database is only supported in MS Analysis Server. For

instructions about creating this schema manually, refer to Creating the
OLAP Cubes on page 302.
In addition to these two databases, which must exist before you create the
schemas, you must have an operational database for Portfolio Management. Its
schema is created when the analytic applications are installed. For more
information about required databases, refer to RDBMS Prerequisites on page
37.
The Data Mart database must be populated with the correct schema.
Before creating the target database schema:
1.
Create a user to own the schema. This is the target user that will own the
Data Mart schema. For more information, refer to User Creation Script
on page 306.
2.
Your DBA should tune Oracle according to your enterprises standards,

including checking the db_block_buffers, shared_pool_size, and
sort_area_size server parameters.
3.
Create a tablespace named DW_INDEX to hold the Data Mart indexes. For
more information, refer to Tablespace Sizing on page 307.
To create the Data Mart target database schema:
1.
Run the targetDb.sh file found in the db/oracle directory of the

[DATAMART] directory. The usage is:
./setupTargetDb.sh [Oracle_Service_Name] [User_ID]
[Password]

[Oracle_Service_Name] is the name of the instance that will store the
Data Mart database schema.

[User_ID] is the ID of the account that owns these tables.
2.
Press Enter.
Appendices
319
Actuate on Solaris
A.
Actuate on Solaris
In general, this guide assumes that Primavera is running in a Windows

environment, even though Primavera supports Actuate in a Solaris environment.
This appendix describes procedures for Actuate:
Conventions
Installing Third-party Software
Configuring Reports
This appendix assumes that you are an advanced Solaris user. When following
these procedures, log in as a user with permissions comparable to the root
accounts permissions unless instructed otherwise.
For recommendations regarding software for use with Primavera in a Solaris

environment, refer to Certifications on page 419.
Actuate on Solaris
A.1
Conventions
This appendix uses the following conventions:

[PRIMAVERA] is the directory where Primavera will be installed.
[ACTUATE] is the directory where Actuate iServer will be installed.
Actuate on Solaris
A.2
Installing Third-party Software
This section describes installation of the third-party software required by

Primavera for report generation, Actuate. For general installation instructions,
refer to Installing Primavera on page 43.
A.2.1
Actuate
If you use the Primavera reports, you must install Actuate iServer. For
instructions, refer to the Actuate documentation, which can be accessed after
Actuate iServer is installed. Install the documentation by running the
helpinstall.sh shell file found in Online Documentation and Localization
Resource Files\l10nandonlinedocumentation\unix on the Actuate distribution
image. For Primavera-specific instructions about installing Actuate, refer to
Actuate on page 40.
The user that installs Actuate must have several environment variables set in the
resource file (.cshrc, .login, .profile, or the equivalent), including:
AC_SERVER_HOME must point to the AcServer directory that will be the
root of the Actuate installation.
LD_LIBRARY_PATH must include the /lib directory under

AC_SERVER_HOME
ORACLE_HOME must be set.
The PATH variable must include the bin directory in your Oracle
installation.
ORACLE_BASE must point to $ORACLE_HOME
ORACLE_SID must point to the Oracle instance where the PVDB database
resides.
Actuate on Solaris
For example:
AC_SERVER_HOME=/export/home/actuate/AcServer
export AC_SERVER_HOME
AC_SERVER_HOME=/export/home/actuate/AcServer
export AC_SERVER_HOME
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$AC_SERVER_HOME/lib
export LD_LIBRARY_PATH
ORACLE_HOME=/opt/oracle
ORACLE_BASE=$ORACLE_HOME
ORACLE_SID=pvdb
export ORACLE_HOME ORACLE_BASE ORACLE_SID
PATH=$PATH:$ORACLE_HOME/bin
Actuate on Solaris
A.3
Configuring Reports
After installing Primavera on Windows, you must manually configure installing

Actuate on a Solaris machine. You must edit evReportsConfig.properties file.
Configuration includes:
Configuring Connectivity
Setting Report Properties
Importing the Encyclopedia
A.3.1
Configuring Connectivity
To connect to an Oracle database, Actuate reports use the SQL*NET native

database driver. It is not possible to connect to Microsoft SQL Server databases
when running Actuate on Solaris.
For Actuate installations on Solaris, the Oracle client version installed on the
Actuate Solaris server must be Oracle 9.2.0.7.
Actuate on Solaris
To configure connections to the databases:

1.
Copy the evReportsConfig.properties file from [PRIMAVERA]/actreports

in the Primavera core installation to [Actuate]/iServer directory.
2.
Edit the evReportsConfig.properties using a text editor, such as vi.
3.
Specify the names of the core and target databases (depending on your
scenario), as in the examples below:
evolve.db.type= ORACLE
evolve.db.server_dsn= <sol700>
evolve.db.username= PVDB
evolve.db.password= PVDB
evolve.db.dbinterface= acorcl90
evolve.dm.db.type= ORACLE
evolve.dm.db.server_dsn= <sol700>
evolve.dm.username= PVDB
evolve.dm.password= PVDB
evolve.dm.dbinterface= acorcl90
evolve.datamart.db.type= ORACLE
evolve.datamart.db.server_dsn= <sol700>
evolve.datamart.db.username= target_db_user
evolve.datamart.db.password= target_db_user
evolve.datamart.db.dbinterface= acorcl90
evolve.dm.report.username= evolve_std
evolve.dm.report.password= evolve_std
4.
Supply the appropriate values for each of these properties:
evolve.db.type and evolve.datamart.db.type indicate the

types of the databases. These should always be ORACLE.
evolve.db.server_dsn and evolve.datamart.db.server_dsn
are the Oracle alias names that point to the respective databases.
evolve.db.username and evolve.datamart.db.username are
the names of the Oracle users that Primavera should use to connect to
the databases.
Actuate on Solaris
evolve.db.password and evolve.datamart.db.password are
the passwords of the Oracle users that Primavera should use to connect
to the databases.
5.
Other properties in this file should not be modified.
Save and close the file.
A.3.2
Setting Report Properties
Primavera uses parameters in the AppServerConfig.properties file to connect to

Actuate. Several of these have default values. If you use non-default values, you
must edit this file to specify them.
Use caution when editing this file. Inadvertent changes to any properties may
troubleshoot. It is typically not necessary to edit this file for reporting values
unless you have modified the report encyclopedia. Before changing this files
contents, make a copy of the file.
For a list of reports-related properties, refer to Report Properties on page
193.
A.3.3
Importing the Encyclopedia
Before importing the encyclopedia, the user that installs Actuate must have the
LD_LIBRARY_PATH variable set. It should point to the AcServer/lib directory
created during Actuate installation. For example:
LD_LIBRARY_PATH=/export/home/actuate/AcServer/lib
export LD_LIBRARY_PATH
To import the ACF in Solaris:
1.
Upload the following files from [PRIMAVERA]\actreports\ to the

Solaris machine hosting Actuate:
ss_oracle_rpts.acf
Actuate on Solaris
to the root path of the Actuate installation in:

/export/home/actuate/AcServer
2.
Log in to the Actuate host using the Actuate administrators account.
3.
Change directories to the directory that contains the acimport utility

(for example, cd /export/home/actuate/AcServer/bin).
4.
Shut down the server by entering:

./shutdown_srvr.sh
5.
Verify that all Actuate server processes are stopped. If not, stop them.
6.
Import the ACF file by executing the following command from the
/export/home/actuate/AcServer directory:
./bin/acimport -all -acf -replace -force -input
ss_oracle_rpts.acf
7.
Verify that no errors occurred.
8.
After successfully importing, change directories to the bin directory, and

start the server:
./start_srvr.sh
9.
Verify that the Actuate processes are running:

ps -ef |grep [actuate user]
where [actuate user] is the Actuate administrative users account name.
WorkSite MP Server
B.
WorkSite MP Server
Primavera relies on WorkSite MP for collaboration functionality. If you plan to

implement collaboration, you must install WorkSite MP. You must install
WorkSite MP before installing Primavera.
The information given in this appendix is applicable only for existing customers
who have WorkSite MP Server install executable downloaded from a prior
Primavera version.
WorkSite MP installation includes installing the software and configuring the

server and library that store the collaboration data.
Running Setup
Configuring WorkSite MP
Initializing the Library
During installation of Primavera, you must configure collaboration, as well.

If you want to run WorkSiteMP Server as a service in Windows, you must take
additional steps as described in Using the Process Manager as a Service in
Chapter 3 of the WorkSite MP Server Administrators Reference Manual. This
document is located in the docs directory under the directory where you install
WorkSite MP.
WorkSite MP Server
B.1
Running Setup
To install the WorkSite MP software on the collaboration host:
1.
Open the Software folder in the WorkSite MP distribution image (a

downloadable file) provided by Primavera.
2.
Double-click the setupwin32.exe icon

After InstallShield prepares the installation, the welcome window appears.
3.
Click Next.
The install directory window appears.
4.
The default location is c:\WorkSiteMP. Accept this default or click Browse

to select a different location. This path cannot contain spaces.
5.
Click Next.
The Collaboration Server window appears.
6.
Enter the name of the cluster and host Primavera will use when connecting
to the WorkSite MP server. Typically, the cluster has the same name as its
host (that is, the computer to which you are installing software), and the
library is named Primavera.
7.
Click Next.
The program folder window appears.
8.
Accept the default program folder or enter a name to create a new folder, and
click Next.
InstallShield is ready to continue installation, the summary window appears.
9.
Review your selections and use the Back button to correct any entries. Click
When InstallShield is done installing WorkSite MP, the result window
appears, reporting the outcome of installation.
WorkSite MP Server
B.2
Configuring WorkSite MP
To configure WorkSite MP, you must create a server and a library and configure
the server for use with Primavera. Note that the library will be stored in a
database you created before installing WorkSite MP. For information, refer to
To add a WorkSite MP server and library:
1.
On the WorkSite MP host, start WorkSite MP, as described in Starting the

WorkSite MP Server on page 336.
2.
Start the Configuration Manager by clicking

StartProgramsInterwoven WorkSite MP ServerConfiguration
Manager.
3.
Expand the cluster named after this host.
4.
Expand Libraries.
5.
Right-click Local, and select Add.

The Add Local Library window appears.
6.
Enter primavera as the library name. You can use another name if
necessary. Note that this text will be used for the email addresses of
discussions. For example, if you enter primavera, and the discussion is
named hottopic, its address is
hottopics.primavera@host.domain.com. Note that the total length of
an email address is limited to 63 characters; do not enter a long string in this
field.
For more information on email and discussions, see the online help.
7.
From the Driver drop-down, select either Microsoft SQL Server or Oracle
9i, depending on the type of RDBMS that will store the library schema.
WorkSiteMP requires a specific database version that is separate from other
Evolve requirements, as described in Certifications on page 419.
WorkSite MP Server
8.
9.
In the DB/Instance Name field enter either:
The name of the MSSQL database you created before installing

WorkSite MP.
The name of Oracle instance where the library will reside.
In the Owner field, enter the name of a RDBMS user that will own the
schema. In MS SQL, use DBO. Note that this user must have the
db_datareader role.
10. Enter the name of the computer hosting your RDBMS.

11. If you use a non-default port number, enter it in the Port field.
12. Enter a user name and password that WorkSite MP can use to connect to the
database.
13. Click Test.
14. If the connection succeeds, click OK. If the connection fails, correct your
entries until the connection is successful.
15. Click Create.
The Library Creation Wizard appears.
16. Follow the on-screen instructions to create the library. Use these Primaveraspecific values:
When prompted for the library object model, select PV_WOM_70.
When prompted for a file server path, enter the path to the location
where the librarys files will be stored. For example, c:\WorkSiteMP.
Do not enable the National Character set check box.
When you have supplied the necessary information, the Library Creation
window appears. WorkSite MP creates and configures the library. When the
Finished Creating Library window appears, click Close to exit the window.
17. Click OK to acknowledge that the library was created successfully.
18. Click OK to close the New Local Library window.
WorkSite MP Server
To configure the collaboration server:
1.
While still working in the Configuration Manager, right-click on the cluster

named after the local computer, and click AddServer.
2.
Enter the name of the local computer in the window that appears. These
instructions refer to this server as the collaboration server.
3.
Right-click the cluster and select Edit....

The Edit Cluster window appears.
4.
On the General tab, in the Temporary File Path field, enter the path to a
directory WorkSite MP can use to temporarily store data.
Do not enter a value in the Installation Directory field.
5.
Select the CMS Libraries tab.
6.
Click Add.
The Add Library window appears.
7.
Select the library you created for use with Primavera, enter 32 as the number
of connections, and click OK.
8.
Select the CMS Settings tab.
9.
Enable the Allow external authetication for enterprise users check box
and click OK.
10. In the Server Configuration Manager window, right-click the collaboration

server and click AddCMS.
11. Right-click the collaboration server and click AddIndexer.
The Add Indexer window appears.
12. Click the Libraries tab, select primavera from the Available list, and click
the right arrow button to move it to the Configured list.
13. Click OK.
14. If you plan to use discussions:
Right-click the collaboration server and click AddJames.

The Add James window appears.
WorkSite MP Server
On the General tab, enter the fully qualified host and domain name of
the local computer. For example, host2.primavera.com. Enter this
value in both the Server Domain field and the DNS Server field.
Click the Libraries tab, select primavera from the Available list, and
click the right arrow button to move it to the Configured list.
Click OK.
15. Right-click each of the services you just added (CMS, Indexer, and James),
and select Auto-Start.
16. Click FileSave.
17. Stop the James service using the iManage WorksiteMP Configuration
Manager.
18. Using a text editor such as Notepad, locate and open
[COLLAB]\worksiteserver\james\james.template.xml.
19. Find the section that reads:

<mailet match="All" class="RemoteDelivery">
<outgoing> file://../var/mail/outgoing/ </outgoing>

<delayTime> 21600000 </delayTime>
<maxRetries> 10 </maxRetries>
</mailet>
20. Comment this section out. For example:

<!-<mailet match="All" class="RemoteDelivery">
<outgoing> file://../var/mail/outgoing/ </
outgoing>
<delayTime> 21600000 </delayTime>
<maxRetries> 10 </maxRetries>
</mailet>
-->
WorkSite MP Server
21. Start the James service using the iManage WorksiteMP Configuration
Manager.
22. Stop and restart the collaboration service, as described in Starting the
WorkSite MP Server on page 336.
Discussions allow users to post messages about a topic related to a project. To do
so, users send email to the address associated with the discussion. This
functionality relies on the WorkSite MP James service: an SMTP service that
must be connected either to the Internet or to your corporate mail server. Note
that James uses ports 25 and 110; no other processes on this host should use these
ports.
WorkSite MP Server
B.3
Starting the WorkSite MP Server
The WorkSite MP server provides collaboration functionality for Primavera.

To start the WorkSite MP server:
1.
On the desktop of the WorkSite MP server host, select

StartProgramsInterwoven WorkSite MP Server Start IMPM.
2.
If you are unsure whether WorkSite MP is running, open the Windows Task
Manager by right-clicking an empty space on the Windows taskbar, and
clicking Task Manager.
3.
On the Processes tab, locate the following services to ensure that they have
started:
imcms.exe
imindexer.exe
imjames.exe
impm.exe
Note that, if you have not configured the WorkSite MP server, only the
impm.exe service starts. The other services must be configured as described
in the associated documentation.
4.
Exit the Task Manager.
WorkSite MP is successfully started.
WorkSite MP Server
B.4
Initializing the Library
To initialize the library you just created, click StartProgramsInterwoven

WorkSite MP ServerInitialize Library. A command prompt window
appears. Text begins to scroll down the command window. When the window
disappears, the library is initialized.
WorkSite MP Server
Delivery Manager Administration
C.
Delivery Manager
Administration
This appendix provides maintenance instructions for the Delivery Manager (DM)
database (DMDB).
For instructions on installing the Primavera software, refer to Installing
Primavera on page 43. For information on configuring printers for invoices
and other DM reports, refer to Report Properties on page 193.
This appendix describes:
Synchronization
Changing Financial Rules for Unrestricted Projects
C.1
Synchronization
If you implement DM, the Primavera core application references both PVDB and
DMDB:
PVDB stores data regarding all business objects (resources, projects,
agencies, clients, opportunities, and competitors), as well as time and
expense reports. This database serves as the master for most Primavera data.
DMDB stores project accounting and back-office financial data, such as

transactions, invoices, journal entries, and actuals. These data can be
extracted through the Primavera connectors and transferred to external
financial systems, such as Accounts Payable, Accounts Receivable, or
General Ledger systems.
Information is transferred automatically from PVDB to DMDB, either

synchronously (for most updates) or asynchronously (for time and expenses). If
you want to transfer the entire set of data from PVDB into DMDB, or if the two
databases are out of sync, use the Delivery Manager synchronization
functionality to manually synchronize the two databases.
This appendix provides details about the synchronization process, including:
Synchronization Basics
Transfer Rules
Automatic Synchronization
Manual Synchronization
For more information regarding synchronization administration options, refer to

DM Database Options on page 148.
C.1.1
Synchronization Basics
The server application governs several synchronization processes:

Committing data simultaneously to PVDB and DMDB when users update
business objects and configuration data.
Tracking new and updated time and expenses data that should be transferred
to the DMDB database.
Asynchronously transferring time and expenses data to DMDB.
Sending notifications to administrators when time and expenses transfer

fails.
Figure C-1
Synchronization Data Flow
C.1.2
Transfer Rules
Primavera only commits data to DMDB that can be used by Delivery Manager.
In the case of time and expenses data, Primavera marks data for transfer when it
is updated, and then transfers all records that have been created or updated since
the last synchronization. C-1 lists the data that are committed simultaneously to
both databases; C-2 lists the data are transferred asynchronously.
Synchronization maps PVDB data to the DMDB schema, using the same
mapping as the parasync_resync.bat file. For information about
parasync_resync.bat, refer to Manual Synchronization on page 347.
Table C-1
Data Committed Simultaneously
Account Class
Organization Unit Financials
Activity
Payment Type
Business Role
Period Category
Classifications general reference

G/L mapping (per company)
Position
Classification
Project
Client
Project Type
Company
Resource
Contract
Resource Type
Cost Code
Task Code
Currency
Task Group
Exchange Rate
Tax Group
Expense Item
Tax Type
Financial Period
Transaction Type
Location (on organization unit)
Units of Measure
Table C-1
Data Committed Simultaneously (Continued)
Message Type (in Financial Rules)
Vendor
Non-resource Type
Table C-2
Data Transferred Asynchronously
Expense Type
Time Report Cell
Limitations
The data constraints in DMDB prohibit changes to certain kinds of data. These
constraints are also enforced in PVDB:
Name Change. Certain types of configuration objects cannot be renamed
once saved.
Code change. The code of certain types of configuration objects cannot be

changed once saved.
The following objects cannot be renamed after saving:

Business Role
Financial Period
Message Type (in a companys Financial Rules)
Period Category
Project Activity (in a projects Financial Rules)
Project Type (in Look up Data)
Tax Group
Tax Type
The code of the following objects cannot be changed after saving:

Accounting Treatment
Location Code
Organization Unit
Task
Task Group
Transaction Type (in this case, the Type value is the code)
Unit Of Measure
Vendor
For more information on these values, refer to the Configuration Guide. For
more information, refer to Delivery Manager Considerations on page 27.
C.1.3
Automatic Synchronization
When data is saved, Primavera commits the appropriate data to PVDB.

Depending on the nature of the update, it also does one of the following:
If the update regards business objects, financial transactions, or
configuration data, the same update is committed to DMDB.
If the update regards time or expense transactions, the data is marked for
asynchronous transfer next time the DM synchronization pollster fires.
When the pollster identifies time or expense transactions that need to be
transferred, the data is committed to DMDB.
The following sections describe:

Synchronous Processing
Asynchronous Processing
Notifications
Firing the Pollster
Synchronous Processing
Most changes are committed to the two databases simultaneously. This ensures
that the databases are always synchronized, and the data they contain matches
correctly.
If the transaction fails in either database, an error is returned to the user
immediately, and the update is not made in either database. Because the user
receives feedback immediately, no notification is sent.
If the databases get out of sync for any reason, most updates cannot be saved in
Primavera. For information, refer to Manual Synchronization on page 347.
Asynchronous Processing
Time and expenses data that are saved in PVDB are transferred to DMDB
asynchronously. If the data cannot be committed to DMDB, a notification is sent
to the admin account. Before the data is available for subsequent processes (such
as invoicing, reimbursement, or adjustment), the problem must be corrected.
The timing of asynchronous transfer is controlled by the Automatic
Synchronization options in the Administration tool. For more information, refer
to DM Database Options on page 148.
When the server application synchronizes time and expenses data, it checks the
synchronization sequence numbers stored in the two databases. If the values do
not match, Primavera assumes the databases are out of sync, and asynchronous
transfer fails. No transfer will occur until you alleviate the problem and
synchronize manually. For more information, refer to Manual
Synchronization on page 347.
You can force the asynchronous transfer of data from PVDB to DMDB by
navigating to the web clients Monitor Server page, and clicking parasyncfire.
Notifications
When a time and expenses transfer fails during synchronization, Primavera sends
a notification to the appropriate user or to the administrator. Note that Primavera
sends a single message for any number of time and expenses transfer errors
during a single synchronization.
A notification is only sent once for each transfer error. Even if the problem is not
corrected by the next synchronization, another message is not sent.
Review your transfer error notifications by clicking Messages in the web client,
or if you have configured Primavera to forward messages, in email.
Firing the Pollster
The synchronization pollster fires at the interval you specify in the
Administration tool. If necessary, you can manually trigger transfer by firing the
pollster.
To fire the pollster:
1.
2.
Log into the web client using an account with the administrator access role.
3.

The Monitor Server page appears, displaying links to various statistics, as
well as a link that fires the pollster.
4.
Click parasync.
The parasync page appears, displaying a link that fires the pollster.
5.
Click fire.
A message appears, indicating that the synchronization pollster fired. Time
and expenses are transferred to DMDB.
C.1.4
Manual Synchronization
Primavera automatically transfers time and expenses data to the DMDB database
at regular intervals, ensuring that the most recent information is available to
subsequent processes. All other data is committed to the two databases
simultaneously.
However, if for some reason the databases fall out of sync, you can manually
synchronize DMDB with the data stored in PVDB. For example, if asynchronous
transfer of time and expenses data fails because the sequence numbers in the two
databases do not match, you should manually synchronize. Manual
synchronization may also be necessary if you have upgraded from a previous
version of Primavera, or if you are adding Delivery Manager to an existing
Primavera implementation.
To manually synchronize the databases, run the parasync_resync.bat file
that is found in the exporter_DM\bin folder created when you installed the
Import/Export Connectors. The parasync_resync.bat file synchronizes an
existing PVDB database with an existing DMDB database, and resets the
synchronization sequence. Note that parasync_resync.bat does not transfer
time and expenses data.
Just as with automatic synchronization, parasync_resync.bat only transfers from
PVDB to DMDB, not vice versa. Thus, you must backup and restore the PVDB
and DMDB databases simultaneously.
Before running the batch file (parasync_resync.bat ):

Stop every instance of the server application. For instructions, refer the
Stopping the Primavera Server Application on page 134.
Ensure that the variable $SSPHERE_ROOT points to the root directory of

your Primavera installation.
Run the DM_storedprocs.sql file found in the exporter_DM\sql

directory created when you installed DM.
This procedure assumes that the server application host is running Windows.

To run parasync_resync.bat:
1.
On the server application host, click StartProgramsAccessories

2.

[PRIMAVERA]\exporter_DM\bin folder beneath the root of your
Primavera installation. For example:

cd Primavera\exporter_DM\bin
3.

parasync_resync [SQL_Server_Host] [DM_Database_Name]
[Pv_User_ID] [Pv_Password] [RDBMS_User_ID]
[RDMBS_Password]

[SQL_Server_Host] is the name of the database server that hosts the DM
schema.
[DM_Database_Name] is the name of the DM database.
[Pv_User_ID] is the account to use to log into Primavera. Primavera
recommends using the admin account.
[Pv_Password] is the password to the [Pv_User_ID] account.
[RDBMS_User_ID] is the ID to use to log into the [SQL_Server_Host]
above. This account must have the database owner (db_owner) role.
[RDMBS_Password] is the password to the [RDBMS_User_ID] account.
4.
Press Enter.

When the prompt appears, synchronization is complete.
If synchronization was successful, a message is written to the synchronization

log file (standardconn.log). You can now enable automatic synchronization
by clicking the Automatic Synchronization check box on the DM database tab
of the Administration tool. Note that you must restart the server application
before this setting takes effect. For more information, refer to the DM Database
Options on page 148.
If the file fails to synchronize the databases, it returns an error. In this case,
search the serverconn.log file for the word ERROR (matching case), and if
possible, rectify the problem in Primavera. Often, a simple correction to data can
alleviate the problem, and running parasync_resync.bat again succeeds. If
the issue is unclear or you are unable to correct it, contact Customer Support as
described on page 21.
Note that, until you synchronize successfully, you cannot start the server
application after an unsuccessful synchronization.
C.2
Changing Financial Rules for

Unrestricted Projects
Primavera provides the update_generic_step batch file, which allows

administrators to update the financial rules of projects against which time or
expenses were reported directly. This utility is described in the following
sections:
Overview
Running update_generic_step
Example Commands
C.2.1
Overview
In certain circumstances, users can report time and expenses directly against a
project without specifying a position. For example, this is allowed when a user
enters time against a project that has its Time and Expenses Entry Restrictions
option set to No Restriction, or when a user reports expenses directly against a
project.
In these cases, Primavera records the time or expense against one of three generic
positions:
Time is recorded against the Project Level position.
Expenses that can be billed to a client are recorded against the Billable
Expense position.
Expenses that cannot be billed to a client are recorded against the Nonbillable Expense position.
When time a time or expense transaction against a given project is first approved,
Primavera creates these generic positions and applies the projects financial rules
to them. These rules are used for all subsequent time and expenses transactions
against this project that do not specify a staffable position.
If the projects financial rules are changed before the project ends, the generic
positions must be updated by running the update_generic_step batch file.
This utility changes the financial rules of specified existing generic positions.
The utility relies on action codes to determine the update to make. The action
codes are described in the following table.
Table C-3
Action codes used with update_generic_step
Action Code
Updated Value
Generic Expense Type for Project Level position
Generic Expense Type for Billable Expense position
Generic Expense Type for Non-billable Expense position
Expense Type for Project Level position
Expense Type for Billable Expense position
Expense Type for Non-billable Expense position
Accounting Treatment for Project Level position
Accounting Treatment for Billable Expense position
Accounting Treatment for Non-billable Expense position
10
Time Billing Type for Project Level position
11
Time Billing Type for Billable Expense position
12
Expense Billing Type for Project Level position
13
Expense Billing Type for Billable Expense position
Billing actions (codes 10 through 13) require one of the following billing types as
the new value:
Table C-4
Billing type values used with update_generic_step
Value
Meaning
Time and Materials
Milestone
Fixed
Prepayment
C.2.2
Running update_generic_step
When a projects financial rules change, you may need to run this utility.
To update the generic positions on one or more projects:
1.

Prompt.
2.

utils\database\mssql\DM folder beneath the folder where you installed
Delivery Manager. If you used the default directory, change directories by
typing:
3.
cd primavera\utils\database\mssql\dm
update_generic_step [SQL_Server] [Database_Name]
[User_ID] [Password] [Action_Code] [Company_ID]
[Project_ID] [New_Value]

[SQL_Server] is the name of the database server instance. Typically, this
is the name of the computer hosting MS SQL Server. Sometimes, this is the
name of the service appended to the name of the host (for example
primaverahost\sqlservice).
[Database_Name] is the name of the database. For example, DMDB.
permissions in the DMDB database should be comparable to the database
[Action_Code] is one of the codes described in C-3 Action codes used
with update_generic_step (on page page 351).
[Company_ID] is the name of the company in which the project is found.
Substitute the string all to select all companies.

[Project_ID] is the name of the project you want to update. Substitute the
string all to select all projects within the scope of the value you entered as
the [Company_ID].
[New_Value] is the value you want the project to use. If this is a billing
action, use on of the billing types described in C-4 Billing type values
used with update_generic_step on page 352.
4.
Press Enter.
When the prompt appears, generic positions on the specified projects are updated
with the value you specified.
C.2.3
Example Commands
Consider an unrestricted project named Proj1 in a company with the code 201.
Halfway through the projects life-cycle, the expense type for time reported
against the project must be changed to a new expense type called 2005_Time. In
order to ensure that any new time reported against the project uses the correct
expense type, the administrator runs the following command against a DM
database that resides on a MS SQL Server called SQL1:
update_generic_step SQL1 DMDB sa sa 4 201 Proj1 2005_Time
If the administrator wanted to make the same update to all projects in the
company with code 201, she would run the following command, instead:
update_generic_step SQL1 DMDB sa sa 4 201 all 2005_Time
Troubleshooting
D.
Troubleshooting
This appendix describes general troubleshooting tips for Primavera and provides
advice for the following potential problems:
Unable to Start the Server Application
Unable to Start the Desktop Client
Primavera Client Fails to Connect
Web Server Issues
Performance Degradation
Transfer Failure During Synchronization with DM
iManage Fails to Connect to Its Database
Web Client Issues
ProjectLink
TroubleShooting Portfolio Manager
Limiting the Number of Objects Displayed in Finders
Unable to Launch Client in Windows Vista
If your problem is not listed above, read each section to verify that one of them
does not address your problem. If you are unable to identify a solution, contact
Customer Support as described on page 21.
When troubleshooting, refer to the log files that the applications write. The
following sections list the log files that may be of assistance in each case.
Troubleshooting
D.1
Unable to Start the Server Application
The server application writes messages to a console output file that is configured
using the Administration Tool. For more information, refer to Server Options
on page 142.
Diagnosis varies, depending on the applications servers circumstances:
Server Application Unable to Connect to MS SQL Server
Previously Started, But Now Fails
D.1.1
Server Application Unable to Connect

to MS SQL Server
In some circumstances, the Primavera server application may be unable to

connect to the MS SQL Server. This problem is typically characterized by an
SQL exception indicating that the connection was refused. In the Primavera
server application log or console, such an error looks similar to the following:
Nov-25-16:11:20-ERROR-S:-1:1 - Uncaught exception.
Shutting down...
evolve.pts.infra.common.InfraRuntimeException: Could not
find a valid JDBC driver to connect to MSSQL database!
Connection details: Failed to get connection to JDBC
driver: com.inet.tds.TdsDriver with connection
information: JDBC Connection Information:
Driver:
com.inet.tds.TdsDriver
DataSource: jdbc:inetdae7a:EVMSSQL:2222?database=pvdb
UserName:
sa
DbKey:
Infra.dbil.
This error typically occurs if the MS SQL Server uses a port number other than
the default. Your MS SQL Server might use a nondefault port number for a
number of reasons, such as when multiple MS SQL Servers share on a single
host.
Troubleshooting
If the server application fails to connect to the MS SQL Server, open the
Primavera Administration tool (StartPrimaveraPrimavera
Administration) and verify that the correct port number is displayed in the Port
field. Note that, if this field is blank, Primavera assumes that the MS SQL Server
uses the default port number (1433).
D.1.2
Previously Started, But Now Fails
This section describes solutions to possible problems that might cause a server
application that had started properly in the past to fail.
Fails After Upgrade
If you have successfully started the server application in a previous version, but
cannot start it after upgrading to the latest version, the upgrade may be
incomplete. If you upgraded the software without upgrading the database
schema, you may receive such a message. For more information, refer to
Upgrading Between Primavera Versions on page 290.
Log File Marked Read-only
While Primavera strongly recommends that you protect your server hosts against
viruses, some antivirus software marks the log file (by default,
[PRIMAVERA\serverlog.txt) as read-only during scheduled scans. When the
server application is started, but cannot write to the error log, a message is
written to the command prompt window (if the server application was started
manually). However, since the file is not writable, the server application may
appear to fail without any warning or diagnostic messages.
If you cannot start the server application, verify that the log file is not marked
read-only. If it is marked read-only, configure your antivirus software to skip this
file during its scan, and change the file by disabling the Read-only check box in
the files Properties window.
Troubleshooting
D.2
Unable to Start the Desktop Client
The desktop client writes messages to a console output file that is configured
using the Administration Tool.
Diagnosis varies depending on whether you are unable to start a single desktop
client or you are unable to start all desktop clients. The following sections can
help you identify and resolve problems starting the client:
Unable to Start a Single Desktop Client
Unable to Start All Desktop Clients
Desktop Client Trace Option
Configuring Desktop Client Connectivity
D.2.1
Unable to Start a Single Desktop Client
If you cannot start a single client, but other clients configured to connect to the
same web server start successfully, the client may not have the correct
connectivity information. Using the Administration Tool, verify the application
server host name and whether the SSL check box is enabled.
For more information on the Administration Tool, refer to Client Options on
page 140. For more information about Primavera clients and SSL, refer to
Importing a Certificate for SSL on page 118.
D.2.2
Unable to Start All Desktop Clients
If you cannot start any of the desktop clients configured to connect to a particular
web server, try one of the following:
Verify that the server application is running before starting the client. Refer
to Starting the Primavera Server Application on page 126.
Ensure that the clients connectivity is properly configured. For instructions,

refer to Configuring Desktop Client Connectivity on page 359.
If the clients are separated from the server application host by a firewall, you
must configure the firewall with the correct port numbers. For more
information, refer to the documentation associated with your firewall.
Troubleshooting
D.2.3
Desktop Client Trace Option
If you cannot start the desktop client, you can use the tracing option to determine
the nature of the problem. The console option causes the client to return
informational and warning errors in a command prompt window.
To run the Configuration application with the -console option:
1.
On the desktop of the client host, select StartProgramsAccessories

System ToolsCommand Prompt to open a command prompt window.
2.
In the window, change directories to the bin directory under the directory
where Primavera is installed. If you installed to the default location, type:
cd primavera\bin
3.

configclient -console
4.
Press Enter.
Text begins to scroll down the screen.
The client starts, and informational and warning messages are written to the
command prompt window. These messages can assist in troubleshooting the
desktop client. You can also use the console option with the Primavera Security
and Account Manager.
D.2.4
Configuring Desktop Client Connectivity
The desktop client must be configured to locate the server application.

To configure client connectivity:
1.
On the desktop of the client host, select StartProgramsPrimavera

Administration.
The Administration Tool appears.
2.
Click the Client tab.
Troubleshooting
The Client tab appears.

3.
Enable or disable the SSL check box, depending on whether your enterprise
uses Secure Socket Layer encryption.
4.
In the Web Server Host Name, enter the name of the computer hosting the
server application.
5.
In the Web Server Port, enter the port number of the computer hosting the
server application.
6.
Click OK to close the Administration tool.
Troubleshooting
D.3
Primavera Client Fails to Connect
If ProjectLink, Offline T&E, the web client, the Security and Account Manager,
or the Configuration application fail to connect to the application server, and you
have implemented SSL, the client host may not have the required CA certificate.
If you implement SSL (Secure Socket Layer) encryption, and you use your own
trusted authority to issue certificates, the root certificate for that authority must
be imported on any computer hosting ProjectLink, Offline T&E, the web client,
the Security and Account Manager, and the Configuration application.
If their host does not have the correct certificate, the Primavera clients do not
prompt you for a login and password and return an error indicating that the server
was not available. In the case of Offline Time and Expenses, it returns one of
these messages:
Failed loading CA Certificate from the \\Certs directory. This directory
is found under the directory where you installed Offline Time and
Expense.
The certs directory contains an invalid CA Certificate file. The certs
directory is found under the directory where you installed Offline Time
and Expense.
The first error occurs when no certificate can be found. Typically, the second
error is caused by the expiration of an enterprise-specific certificate. To alleviate
the problem you must locate the expired or invalid certificate and replace it by
adding a new certificate to the keystore.
For instructions, refer to Importing a Certificate for SSL on page 118. Note
that the client software must already be installed before following these
instructions.
Troubleshooting
D.4
Web Server Issues
If you suspect that a problem with the web client or reports is caused by the web
server, you can try the following:
Verify that the web server is running.
Verify that you are using the correct URL, including using the correct
protocol (HTTP or HTTPS, if you are using SSL security). Note that
Primavera URLs are case-sensitive.
Use the fully qualified host and domain name of the web server.
Troubleshooting
D.5
Performance Degradation
While degradation can be caused by other problems, the following sections

describe the most common performance issues:
Project Bulk Update
Data Mart
D.5.1
Project Bulk Update
The project bulk update feature allows users to make the same change to several
projects at once. Since such functionality is necessarily process-intensive,
Primavera recommends that you use this feature sparingly.
If usage of this feature causes your performance to degrade, you may need to
limit its use to off-hours. Note that project bulk update is optimized for a single
user updating 200 or fewer projects at a time.
D.5.2
Data Mart
If Data Marts performance is a concern, the following recommendations may

improve it:
Install and run Data Mart on a dedicated host.
For the source database of the datamart process, replicate the Primavera core
databases rather than using the production databases. If you use replicated
databases, the OLTP (On-Line Transaction Processing) databases (PVDB
and DMDB) are not impacted by Data Mart.
The Data Mart and OLAP databases should reside on a host different from
the application server.
Consult your database administrator. Ideally, the database administrator

should monitor and tune the RDBMS for optimal performance.
If you store the database in Oracle, dedicate an Oracle instance to the Data
Mart database, and tune it for bulk insert and read performance.
Troubleshooting
D.6
Transfer Failure During Synchronization

with DM
If you receive an error message or notification that Primavera encountered a

transfer error while synchronizing the DM database, you must either correct the
problem in Primavera or correct it in DM, depending on the nature of the error:
Upon Save, the user is notified if the data could not be saved in DM. The
user must fix that problem in the web client before saving.
If the problem is found in time and expenses transferred asynchronously, the

administrator account is sent notifications. In this case, the administrator
must correct the problem that is causing synchronization to fail.
If the Primavera and DM databases are out of sync, force the DM database into
synchronization with the Primavera database. For more information about
synchronization, refer to DM Database Options on page 148 and
Synchronization on page 340.
Troubleshooting
D.7
iManage Fails to Connect to Its Database
If you implement collaboration, and iManage fails to connect to its database, the
problem may be caused by an expired iManage user. If 180 days pass without the
admin user logging into iManage, the admin account is marked as expired. This
problem can be caused by restoring a backup that is more than 180 days old.
If iManage fails to connect to its database, you can determine if the problem is an
expired admin account by running the following SQL query:
SELECT
RDN, UID_F21024, LAST_LOGON_TIME
FROM DIT_TRUSTEE
WHERE UID_F21024='ADMIN'
If the date this query returns is more than 180 days old, run the following SQL
query against the iManage database:
UPDATE DIT_TRUSTEE
SET LAST_LOGON_TIME = getutcdate(), MODIFIED_TIME =
getutcdate()
WHERE DIT_CLASS = 1
This query updates the record for the admin accounts last login.
Troubleshooting
D.8
Web Client Issues
This section describes solutions to problems with Primaveras end-user web

interfaces, including:
General Unexpected Behavior
Flash Interface Issues
Web Address or Link Fails
Prompted to Accept a Certificate
Access Denied when Publishing a Portfolio
Web Client Error: Editing Qualifications
Web Client ToolTip Uses Sound Cue
D.8.1
General Unexpected Behavior
If a user is experiencing problems with the web client, such as main pages failing
to respond after interacting with a pop-up window or an inability to log in after
installing a new SSL certificate, the problem may be caused by the way the
browser is configured:
If a pop-up blocking utility is installed, or if a third-party toolbar is installed,
Primaveras web pages may not function properly. Disable the third party
software while connected to the Primavera web client.
If your browser is configured with a higher-than-usual security policy, it may

not allow Primavera to execute properly. Reduce your security setting for the
Primavera web client by editing your browsers security options.
D.8.2
Flash Interface Issues
If you do not have the correct version of the Flash Player, you may have
difficulties displaying or interacting with the Master Schedule and Opportunity
Pipeline features. These problems include seeing a blue puzzle piece instead of
the feature and the feature following the cursor when the user mouses over the
Flash component. To alleviate the problem, you must download the latest Flash
Player.
Troubleshooting
To download the Flash Player, visit www.macromedia.com.
Actuate reports provided with Primavera now load properly.
D.8.3
Web Address or Link Fails
Various Primavera profiles (such as resources and opportunities) can include

URLs or links.
When users click an external link or the URL, they might receive an error
message similar to Unable to locate the server: server name or
Could not open file: path/file name.
This problem often occurs when users enter the URL in a format that the web
server cannot resolve. All links and URLs should be entered in the following
format:
http://host.domain/path and file name
For example, http://www.primavera.com/customer/support.asp.

This format creates a link that can be resolved independently of network
locations. If you do not specify a domain (primavera.com), and only specify a
host (www) and path (customer/support.asp), the link can only be resolved from
within your local area network.
D.8.4
Prompted to Accept a Certificate
When connecting Primavera, your users may be prompted to accept a certificate.

This prompt appears when Primavera is secured through SSL encryption, and the
user does not have the corresponding certificate. Usually this is a result of a
certificate issued by an internal authority.
To alleviate the problem, you must import the certificate, as described in
Troubleshooting
D.8.5
Access Denied when Publishing a Portfolio
When a user running Microsoft IE 6.0 or later tries to publish a portfolio as a

snapshot, Primavera returns an error message denying access. This problem
occurs when the URLs for analytic applications are not added to the list of trusted
sites in IE. To gain access to publish the portfolio, you must assign the Primavera
URLs to the Trusted Site security zone. For more information, refer to the help
provided with IE.
D.8.6
Web Client Error: Editing Qualifications
When a Primavera user selects qualifications to edit while in his profile, he might
receive the following message:
You have selected more than <nn> qualifications. Editing
many qualifications at once can cause problems on some
browsers.
In this case, the default threshold (set to 20 by default) for editing qualifications
has been reached.
The user should edit no more than 20 qualifications at a time. Alternately, modify
the Qualifications Warning Threshold field, as described in Configuring the
Web Client on page 60. However, increasing the threshold may degrade
Primavera performance. If performance is degraded, decrease the threshold.
D.8.7
Web Client ToolTip Uses Sound Cue
When Flash displays a ToolTip, Windows plays a sound. You can change or
disable this setting in the Windows Control Panel.
To disable the ToolTip sound cue:
1.
Select StartSettingsControl PanelSounds and Multimedia.
Troubleshooting
The Sounds Properties window appears.

2.
In the Sound event scrolling region, scroll to Windows Explorer.
3.
Select Complete Navigation.
4.
In the Name drop-down, select (None).
5.
Select Start Navigation.
6.
In the Name drop-down, select (None).
7.
Click Apply.
8.
Click OK.
The ToolTip sound cue is disabled.
Troubleshooting
D.9
ProjectLink
This section provides information about these potential issues:

ProjectLink Fails to Connect
ProjectLink Fails to Download Daily Actual Hours
D.9.1
ProjectLink Fails to Connect
When a user attempts to open a project from Primavera, ProjectLink does not
display the list of projects if the server application is secured through SSL
encryption, and the proper certificate has not been installed on the client. Usually
this is a result of a certificate issued by an internal authority.
To alleviate the problem, you must import the certificate, as described in
D.9.2
ProjectLink Fails to Download Daily Actual

Hours
If you implement ProjectLink in a multiserver environment, and you have

enabled the Download Actuals and ETC (onPvOpen_writeTimeInfo Macro)
check box on the Project Integration Options page in the web client, ProjectLink
may fail to download certain daily actual hours, unless you implement a clock
synchronization solution. For more information, refer to Multiserver
Environments on page 25.
If you have implemented a clock synchronization solution, you can make
Primavera more resilient to synchronization problems by editing the
AppServerConfig.properties file.
Use caution when editing the AppServerConfig.properties file. Inadvertent
changes to any properties may cause unexpected errors throughout Primavera
that may be difficult to troubleshoot. Before changing this files contents, make a
copy of the file.
Troubleshooting
To set the clock synchronization property:
1.

AppServerConfig.properties file using a text editor such as Notepad
or vi. For example, in Windows, this file is found in the [PRIMAVERA]\cfg
directory.
2.
At the bottom of the file, enter the following:

PtsServer.msp.integ.te.actuals.delta.time= <seconds>
where <seconds> is the number of seconds Primavera should add as a buffer.

This property controls the length of a buffer (expressed in seconds) that
determines which actuals are new. When determining which actuals are new,
Primavera includes actuals logged within the specified number of seconds
before the last successful download. Larger numbers create longer buffers,
which return actuals reported earlier.
3.
After the equal sign, specify the number of seconds Primavera should add as
a buffer.
4.
Troubleshooting
D.10
TroubleShooting Portfolio Manager
This section describes troubleshooting tools and tips for Portfolio Manager.
D.10.1
Message Logging
Primavera Portfolio Manager uses WebLogic logging mechanisms to control the

level of detail in messages written to the log file. You can find the
myserver.log file in:
<PrimaveraInstall>\j2ee\weblogic\primavera\servers\myserver\
logs\
You can select from three levels of logging detail: Warning, Info, and Debug. Set
log levels either through the WebLogic console or by editing the log4j property
file. Editing the log4j property file allows you to select the highest level of detail,
but requires a server reboot. Note that increasing the detail of output to the
message log will cause the log file to grow faster and could have negative
performance impacts.
Select Warning or Info levels using the WebLogic console. (This does not require
a server reboot.):
Log into the WebLogic console as the system administrator. The WebLogic
console is usually reached by pointing your web browser to the following
URL: http://hostname:7001/console
Using the left side menu, open Primavera > Servers > myserver
Using the tabs at the top of the right hand frame, select Logging and
Server
Change the Severity Threshold setting to Warning or Info to change

the detail of the log messages in MyServer.log
The highest level of detail is the Debug level, which can only be activated by
editing the log4j properties file and requires a server reboot to activate and
deactivate.
Troubleshooting
Shut down the WebLogic server running Portfolio Manager.
Open <Primavera Install>\cfg\server.log4j.properties in a

text editor.
Locate the following line and change ERROR (in this example) to DEBUG to
activate the Debug level of message logging. You can also change the
property to WARN to select the Warning level of logging.
log4j.rootLogger= ERROR, WebLogic
becomes
log4j.rootLogger= DEBUG, WebLogic
Start the WebLogicServer running Portfolio Manager.
The table below describes the message levels you can set through the WebLogic
console or in the log4j property file.
Troubleshooting
Table D-1 Logging Levels for Messages

Message Level Name
Description
Warning
This is the default logging level that the user

cannot turn off.
The Always On level gives you some basic
information in the log file, such as initialization
information and errors encountered. Messages
always include date, timestamp, session ID, and
user name.
Info
The Info logging causes Portfolio Manager to

write more about the MDX queries being
executed to the log file. This is primarily
intended for trouble-shooting and could
negatively impact performance. You must
explicitly set this level to ON in the
configuration file or by editing the log4j
property file.
The Info level of logging level includes:
MDX queries along with the input

arguments passed, execution time taken
Trace of name of the Java class being

called, name of the methods being called
from PM, tracking line numbers, and total
execution time taken to execute that
particular method.
Troubleshooting
Message Level Name
Description
Debug
The Debug logging level allows you to see

additional information such as connection
pooling, memory leaks, and performance-related
messages. It can only be set by editing the log4j
property file. This level setting may cause the
log file to grow quickly and could have negative
performance impacts.
This level includes all the details of Info and
Warning logging levels plus:
DB connection in use
OLAP driver and OLAP server information
Number of used and unused database

connections
Size of the result set/number of rows

returned from OLAP server
Database locks info
Memory usage information
Troubleshooting
D.11
Limiting the Number of Objects Displayed

in Finders
Very large query results, typically into the tens of thousands of records, may
overwhelm the server and cause an out of memory error with the standard
finders, Master Schedule, and Skill Search. Pre-set parameters provide limits to
specific user queries.
The following parameters are now available:
1.
app.displayListLimit: If search results return more records than the
ones specified for this parameter, the user will see the following warning
message:
"This search will return over <Number of Records> <Domain
Objects>. Click Yes to continue or No to reduce your
search criteria."
The default value is 1000.

2.
app.displayListErrorLimit. If search results return more records than

the ones specified for this parameter, the user will see the following error
message:
"This search was canceled because the number of <Domain

Objects> exceeded the configured system maximum of
<Number of Records>. Please reduce your search criteria
and try again."
You will not see any search results. The default value is 20000.
3.
app.sss.showAllRecordsLimit. This parameter is enforced when a user

clicks Show All on a Finder result that is spread across multiple pages. If the
search result returns more records than the value specified for this parameter,
you will see the following message:
"The action was aborted due to large volume of data.

Please refine your search criteria and/or use page
numbers."
Otherwise, all records will be displayed in a single page. The default value is
set to 1000.
Troubleshooting
The parameters are active by default based on the default numbers listed above.
To override the defaults, add the following parameters to the
[Primavera]\cfg\appserverconfig.properties file in the following
format:
app.sss.showAllRecordsLimit=500
app.displayListLimit=10000
app.displayListErrorLimit=10000
A server restart is required.
Troubleshooting
D.12
Unable to Launch Client in Windows

Vista
Primavera recommends the Windows Vista users to turn off User Account
Control (UAC). This allows Offline Time and Expense to install properly.
ProjectLink API
E.
ProjectLink API
This appendix describes the ProjectLink API: a set of Common Object Model
(COM) interfaces that are passed as arguments to Visual Basic for Applications
(VBA) macros. The API is always installed; you can customize the macros.
Using VBA, which is embedded in Microsoft Project and COM, macros running
in Microsoft Project allow users to selectively get or create the following
information for projects opened from or saved to Primavera:
Get calendar information for the project and for employee resources
committed to the projects positions.
Get resource information (such as commitments) for employee resources

committed to the projects positions. Primavera returns information for
commitments that are in assigned, requested, or change requested state.
Get new approved time hours and Estimate to Complete (ETC) hours for all
tasks and for the resources assigned to them. In addition to the approved
native time hours, Primavera returns time business transactions that are
finalized (excluding those created automatically when native time was
approved). The data only include hours approved, ETC hours changed, or
time business transactions finalized since the last time the project plan was
opened from Primavera.
Create positions on the project in Primavera.
Map custom fields associated with each task in the project plan into the MSP
Fields tab in Primavera.
During Open from Primavera and Save to Primavera operations, ProjectLink can
trigger events that call the VBA macros by passing COM interfaces as
arguments. These macros can implement your enterprises business rules. The
macros must be distributed to all ProjectLink users in the enterprise.
For information on installing the macros, refer to Installing the Extended
Functionality on page 116.
ProjectLink API
This appendix discusses the ProjectLink API as follows:

Assumptions
COM Interfaces
Sample VBA Macros
ProjectLink API
E.1
Assumptions
In providing the extended functionality, Primavera assumes that the programmer

developing the VBA macros has sufficient knowledge to program in VBA for
Microsoft Project, knows how to access Microsoft Project objects (such as tasks,
calendars, and resources) through VBA, and has sufficient knowledge of the
Primavera application to understand the relationships among resources, tasks,
positions, projects, and commitments.
ProjectLink API
E.2
COM Interfaces
These interfaces have the methods for manipulating objects in Microsoft Project
and Primavera:
IPvCalendarInfo
This interface provides methods for getting project and resource calendars:
IPvCalendar getPvProjectCalendar(). Returns the Primavera
calendar policy of the project opened from Primavera.

IPvCalendar[] getPvResourceCalendars(). Returns an array of
resource calendar policies for the resources downloaded from Primavera

with the project. These are resources committed to project positions.
IPvCalendar
This interface, which is accessible from IPvCalendarInfo, gets

information for a given calendar:
String getHolidayPolicyName(). Returns the name of the holiday
policy associated with calendar policy in Primavera.

String getWorkWeekPolicyName (). Returns the name of the
workweek policy associated with calendar policy in Primavera.

Date[] getHolidays(). Returns an array of holiday dates.
float[] getWorkWeekHours(). Returns an array of hours for a
given week.
IPvResourceInfo
This interface returns information about a resource with the name passed in
resourceName. The resource can be accessed from the MSP resource sheet.
Note that resource names are ordered FirstName LastName; for example,
Jane Doe. Position names are assumed to begin with an underscore; for
example, _Technical Writer. Do not begin resource names with
underscores.
ProjectLink API
IPvNonProjectCommitment[]
getNonProjectCommitments(String resourceName). Returns
an array of INonProjectCommitment objects (discussed below) for
the specified resource.

IPvCalendarPolicy getResourceCalendar(String
resourceName). Returns the Primavera Calendar policy for the
specified resource.
IPvPosition[] getCommittedPositions(String
resourceName). Returns an array of IPvPosition (discussed below)
objects for the specified resource.

In business terms, the resource information that is returned includes:
The name of the position to which the resource is assigned.
The non-project commitments of the resource from the start date of the
project, including commitments that continue after the project end date.
Non-project commitments contain status (firm or tentative), type (for
example, vacation), start date, end date, and an array of per-day hours
from start date to end date.
The calendar name for the resource. The name is formed by combining
the names of the Primavera holiday and workweek policies.
IPvNonProjectCommitment
This interface is accessible from IPvResourceInfo. It gets information for

a given non-project commitment.
int getStatus(). Returns the status of the non-project commitment
in Primavera. The value is 1 (firm) or 0 (tentative).
String getType(). Returns the transaction type of the non-project
commitment.
Date getStartDate(). Returns the start date of the non-project
commitment.
Date getEndDate(). Returns the end date of the non-project
commitment.
ProjectLink API
Float[] getPerDayHours(). Returns an array of per-day hours
from start date to end date of the non-project commitment.
IPvTimeInfo
This interface gets incremental actual approved hours and ETC hours for
tasks in the project plan. Additionally, time business transactions in the
finalized state are also available. That is, the hours that are new since the last
Open from Primavera process.
int[] getIncrementalTaskUniqueIds(). Returns the list of task
unique IDs for which either incremental actuals or incremental ETC

hours are available from Primavera.
String[] getIncrementalResourceNames(int
taskUniqueId). Returns the list of resource names for which
incremental actuals or incremental ETC hours are available from

Primavera. This may include resources that are not in the project plan.
float getTotalActualHours(int taskUniqueId). Returns the
total approved hours logged against the task.

float getIncrementalActualHoursPerResource(int
taskUniqueId, String resourceName). Returns the new
approved hours logged against the task by the resource with name
resourceName after the last successful opening from Primavera.
IPvSDR getIncrementalActualHoursPerResourcePerDay(int
taskUniqueId, String resourceName). Returns IPvSDR data
structure containing new per day approved hours with the date range,
that was logged against the task by the resource with name
resourceName after the last successful opening from Primavera.
float getIncrementalETCHours(int taskUniqueId). Returns
the new estimate to complete hours requested by all the resources who
logged time against this task after the last successful opening from
Primavera.
ProjectLink API
float getIncrementalETCHoursPerResource(int
taskUniqueId, String resourceName). Returns the new estimate
to complete hours requested by the resource with name resourceName
who logged time against this task after the last successful opening from
Primavera.
void setTimeInfoAcknowledged(bool flag). Call this method
once the data are processed and the project manager applies or rejects all
the actuals and ETC coming from Primavera. If the flag value passed is
TRUE, ProjectLink assumes the project manager has processed the data
and has applied it to the plan.
During the Save to Primavera process, this flag indicates that ETC
values since the last Open from Primavera operation are rolled up. The
next Open from Primavera operation will include only the actuals and
ETC hours after the last opening from Primavera. When the flag value
passed is FALSE, ProjectLink assumes the project manager has not
processed the data and wants to get them again. During the Save to
Primavera process, this flag indicates that the ETC hours and time have
not been processed. The next Open from Primavera operation will
include the actuals and ETC hours prior to the last Open from Primavera
operation, in addition to the actuals and ETC hours after the last opening
from Primavera.
IPvTimeBusinessTransaction[]
getIncrementalTimeBusinessTransactions(). Returns the list
of externally created (through the Primavera API or web client) thirdparty time business transactions in finalized state after the last
successful Open from Primavera call.
IPvSDR
This interface is accessible from IPvTimeInfo. It gets the per day actual
hour information.
DateTime getStartDate(). Returns the start date for the date range.
DateTime getEndDate(). Returns the end date for the date range.
float[] getPerDayHours(). Returns an array of per day hours from the
start date to the end date.

ProjectLink API
float[] getPositivePerDayHours(). Returns an array of positive per
day hours from the start date to the end date. The value -1 indicates a null per
day value.
float[] getNegativePerDayHours(). Returns an array of negative per
day hours from the start date to the end date. The value -1 indicates a null per
day value.
IPvPosition
This interface is accessible from IPvResourceInfo. It gets information

about the positions to which the resource is committed.
String getName(). Returns the name of the position.
String getBusinessRoleName(). Returns the name of the business
role assigned to the position in Primavera, or NULL if no role is

assigned.
IPvPositions
This interface gets the data needed for creating positions in Primavera.
Void addPosition(String positionName). Pass the name of the
position. If the team already exists in Primavera, the position is added to

that team. Otherwise, if there are multiple teams in Primavera, the
position is added to the first team on the list, and if no team exists, a
team with name Team from MS Project is created and the position is
added to it. The start and end dates of the position is set to the start and
end dates of the project.
Void addPosition_2(String positionName, String
teamName). Pass the names of the position and team. The start and end
dates of the position is set to the start and end dates of the project.
teamName, String businessRoleName). Pass the names of the
position, team, and business role. The start and end dates of the position
are set to the start and end dates of the project.
ProjectLink API
teamName, Date startDate, Date endDate). Pass the names of
the position and team, and set the positions start and end dates. If either
date is outside the corresponding project date, the project date are reset
to match it.
teamName, String businessRoleName, Date startDate,
Date endDate). Pass the names of the position, team, and business
role, and pass the position name, team name, business role name, start
data, and set the positions start and end dates. If either date is outside
the corresponding project date, the project date is reset to match it.
IPvCustomFields
This interface gets information to map the custom fields of tasks in MSP into
the MSP Fields tab in the Primavera web client.
void addCustomField(int fieldId, string fieldName,
bool leafTasksOnly). Pass the information for the custom field to
save to Primavera. The fieldId is required and is one of the
MSProject.pjField enumeration values. If leafTasksOnly flag is true
only the field values for leaf tasks are read.

void addCustomField(int fieldId, string fieldName,
int fieldNumber, bool leafTasksOnly). Pass the information
for the custom field to save to Primavera. The fieldId is required and
is one of the MSProject.pjField enumeration values. The fieldNumber
specifies the order in which the fields are displayed in Primavera web
client. If leafTasksOnly flag is true only the field values for leaf
tasks are read.
PvTimeBusinessTransaction
The externally-mastered time business transactions (created through the

Primavera API or web client) are available as a collection on IPvTimeInfo.
The PvTimeBusinessTransaction interface gives more information
about each time business transaction.
String getTransactionID()
String getPositionName()
ProjectLink API
String getComments()
String getKeywords()
String getExternalTxnID()
float getTransactionMinutes()
String getResourceName()
String getTaskCodeName()
DateTime getTransactionDate()
String getTransactionTypeName()
bool isBillable()
String getLocationName()
bool isExportedToDeliveryManager()
bool isVisibleInDatamart()
bool isReferenced(). Returns TRUE if another transaction
references this time business transaction; otherwise returns FALSE.
ProjectLink API
E.3
Sample VBA Macros
A module of sample VBA macros is installed with ProjectLink

(<Primavera_installation_directory>\docroot\setups\PvEPMModu
le.mpp). The macros use the COM interfaces to access and set data in Primavera
and Microsoft Project.
The sample macros are provided for demonstration purposes and to provide a
starting point for developing your own macros. If you use them, you are
responsible for supporting them.
onPvOpen_writeCalendars(IPvCalendarInfo pvCalendarInfo)
This macro can be invoked as part of the Open from Primavera process to
access the calendars defined in Primavera. The macro is invoked after the
project file is opened from Primavera but before the resources (positions and
actuals, if selected) are written to the MS Project resource sheet.
The macro has an argument pvCalendarInfo of type COM interface
IPvCalendarInfo. The argument contains methods to access project
calendars as well as the calendars for all resources committed to positions.
See IPvCalendarInfo on page 382 for details of the interface.
The calendar information that is returned includes workweek hours and
holidays as defined in the Primavera Configuration application.
onPvOpen_writeResourceInfo(IPvResourceInfo
pvResourceInfo)
access various resource information. The macro is invoked after the project
file is opened from Primavera and the resources (positions and actuals, if
selected) are written to the resource sheet. The macro has an argument called
pvResourceInfo of type COM interface IPvResourceInfo, which
contains methods to access non-project commitments, calendar, and
positions (to which the resource is committed) for a resource. See
IPvResourceInfo on page 382 for details of the interface.
ProjectLink API
onPvOpen_writeTimeInfo
access incremental actual time hours and ETC hours information. The macro
is invoked after onPvOpen_writeResourceInfo. The macro has the
argument PvTimeInfo of type COM interface IPvTimeInfo, which
contains methods to access incremental actual and ETC hours for tasks in
MSP. This also has a collection of incremental time business transactions in
finalized state. Refer to IPvTimeInfo on page 384 for details of the
interface.
onPvSave_getPositionsToCreate(IPvPositions pvPositions)
This macro can be invoked as part of the Save to Primavera process to make
a list of the positions to create in Primavera. The macro is called
immediately before ProjectLink starts collecting the data to save. It has an
argument pvPositions of type COM interface IPvPositions, which
contains methods to add positions in Primavera. The position creation is
independent of the Save to Primavera processthe positions are created if
they pass all validations, regardless of whether the Save to Primavera
process succeeds or fails. See IPvPositions on page 386 for details
of the interface.
In Microsoft Project, the names of resources that are positions must begin
with an underscore so that they can be properly identified as positions in
Primavera. Names without an underscore are interpreted as non-position
resources.
onPvSave_getCustomFieldsToMap(IPvCustomFields
pvCustomFields)
This macro can be invoked as part of the Save to Primavera process to map a
custom fields to Primavera. The macro is called immediately before
ProjectLink starts collecting the data to save. It has an argument
pvCustomFields of type COM interface IPvCustomFields, which
contains methods to add custom field information to map to Primavera. The
custom fields are not mapped if the save to Primavera process fails.
SeeIPvCustomFields on page 387 for details of the interface.
ProjectServerLink and Microsoft Project Server
F.
ProjectServerLink and Microsoft

Project Server
This appendix describes the tasks you need to perform if implementing

Primavera Evolve integration with Microsoft Project Server (MSPS) via
ProjectServerLink.
For directions on installing MS Project Server, see Microsoft documentation.
This appendix explains the following MSPS topics:
Installing MS Project Server Extensions for HTTP
Enabling MSPS Synchronization for Primavera via an Event Handler
Setting up Impersonation for Actuals and ETC
Configuring Primavera and MSPS for SSL
Implementation Considerations
Configuring SharePoint to Support Fully-qualified Domain Name in

PWA URL
F.1
Installing MS Project Server Extensions

for HTTP
Each ProjectServerLink connection uses either HTTP or JDBC protocol as a

database connection method.
If using HTTP for the ProjectServerLink connection, you must install MSPS
extensions provided by Primavera. This section is not required if using JDBC as
the database connection method.
The extensions comprise several files that are installed with Primavera but must
be copied and configured on the appropriate MSPS host.
These instructions assume the Windows OS and MSPS are installed on the C:
drive and in their default paths.
The following steps reference the [Primavera]\docroot\setups\psi folder.
To simplify the installation process, consider copying the entire psi folder first to
a temporary location on the MSPS host.
Follow the steps below to install and register the Project Server PSI Extension dll
and related files on the target MS Project Server:
1.
Copy the following files from [Primavera]\docroot\setups\psi to the

MSPS host to the directory C:\Program Files\Common
Files\Microsoft Shared\web server extensions\12\ISAPI\PSI
PrimaveraEvolvePSIExtensionwsdl.aspx
PrimaveraEvolvePSIExtensiondisco.aspx
2.
Copy the file PrimaveraPSIExtension.dll from

[Primavera]\docroot\setups\psi to a tempory directory on the MSPS
host.
3.
Drag the PrimaveraPSIExtension.dll file from this temporary

directory to C:\WINDOWS\assembly.
This automatically registers the PrimaveraPSIExtension.dll assembly
in the global assembly.
4.
Copy the PrimaveraEvolvePSIExtension.asmx file from

[Primavera]\docroot\setups\psi to the MSPS host and place the file
in C:\Program Files\Microsoft Office
Servers\12.0\WebServices\Shared\PSI.
5.
Open the web.config file in the same directory and add the
PrimaveraPSIExtension assembly as a child of the <assemblies> tag.
The PrimaveraPSIExtension assembly text is:
<add assembly="PrimaveraPSIExtension, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=a906b6910deecefa" />
Place the PrimaveraPSIExtension entry beneath the existing assemply

for Microsoft.Office.Project.Server.WebService. The result
should list two assemblies, where each assembly is on a single line.
The <assemblies> tag should look like this:
<assemblies>
<add
assembly="Microsoft.Office.Project.Server.WebService,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" />
<add assembly="PrimaveraPSIExtension,
Version=1.0.0.0, Culture=neutral,
PublicKeyToken=a906b6910deecefa" />
</assemblies>
6.
Restart Internet Information Services (IIS). To do so, type iisreset in any

Command Prompt window.
F.2
Enabling MSPS Synchronization for

Primavera via an Event Handler
This component enables automatic synchronization when an MS Project user

publishes a project linked with a Primavera Evolve project.
This is an optional installation component. However, to automatically update a
project in Primavera Evolve when an MS Project user publishes a project in
MSPS, this component is required.
Every time the MS Project user publishes a Microsoft project that is linked with a
Primavera project, the event handler fires and synchronizes the data in the two
projects.
F.2.1
Installing the Event Handler
To enable this functionality, install the PrimaveraPSIEventHandler.dll to a

Report Publishing event that applies to Microsoft-managed projects.
To install and configure the Event Handler:
1.
Copy the following files from [Primavera]\docroot\setups\psi to

the MSPS host and place them in C:\Program
Files\OfficeServers\12.0\Bin\ProjectServerEventHandlers:
2.
PrimaveraPSIEventHandler.dll
PrimaveraPSIEventHandler.dll.log4net
log4net.dll
PrimaveraPSIConfig.xml
Register the PrimaveraPSIEventHandler.dll in the machines global

assembly cache on the MS Project Server machine:
Open a new file explorer window and navigate to

C:\WINDOWS\assembly.
3.
Drag the PrimaveraPSIEventHandler.dll from the

ProjectServerEventHandlers directory into that window.
Register the event handler in MS Project Server:
Log in to Project Web Access (default is http://hostname/pwa).
In Project Web Access, in the left pane, click Server Settings.
Under the Operational Policies section, click Server-Side Event

Handler Configuration. See Figure 9-1.
Figure 9-1
The Project Server Administration Page
The Events page appears.
On the Events page, scroll in the Events list and click the Reporting
link for the ProjectChanged event. See Figure 9-2.
Figure 9-2
Selecting the Reporting ProjectChanged event
Click New Event Handler in the Event Handlers grid.
Figure 9-3
Adding an Event Handler
On the Event Handler page, type the following values for the fields (see
Figure 9-3.)
Name. Friendly name for the event handler.
Description. Optional description of the event handler.
Assembly Name. Full name of the assembly. Copy the exact string
below:
PrimaveraPSIEventHandler, Version=1.0.0.0,
Culture=Neutral, PublicKeyToken=b77feceef188b51a
Make sure that the Assembly Name does not have extra spaces or a
break in the line.
Class Name. Fully qualified name of the class. Copy the exact string
below:
PrimaveraPSIEventHandler.PrimaveraReportingEventRecei
ver
Make sure that the Class Name does not have extra spaces or a break in
the line.
Order. Enter the number 1.
Click Save.
Check that the event is added.

In the Events list, click the Reporting link for the Project Changed
event again. Scroll to the Event Handlers grid. If registration is
complete, you see the event handler in the list.
The new Event Handler may take several minutes to be registered.
F.2.2
Viewing the Event Handler Log
The Event Handler creates a log file in c:\program

files\OfficeServers\12.0\Bin\ProjectServerEventHandlers.
Primavera recommends reviewing this log periodically to analyze

ProjectServerLink activity.
A sample file name is: PrimaveraPSIEventHandler.log.09_14_2007.
F.2.3
Configuring Primavera With SSL and

the Event Handler
See Configuring the Primavera Event Handler for SSL on page 56.
F.2.4
Configuring the Reporting Database Server in

Case of Connection Errors
If you implement the Primavera Event Handler, data is synchronized between

MSPS and Primavera Evolve when an MS Project user publishes a project to
MSPS.
The connection string used by the Event Handler to connect from MSPS to
Primavera Evolve concatenates two Primavera custom fields specific to the
project. These two custom fields have a total limit of 510 characters.
It is highly unlikely that the fields comprising this connection string will exceed
the character limit (the two combined custom fields include such values as
Primavera hostname, project ID, authentication values, etc.). Consequently, it is
unlikely that this section will be necessary.
However, in the case of connection errors due to truncated connection strings,
this section provides a secondary connection process for the Event Handler.
If data is not propagating from MSPS to Primavera Evolve, check the Event
Handler log in C:\Program
Files\OfficeServers\12.0\Bin\ProjectServerEventHandlers. See
Viewing the Event Handler Log on page 398. If connection string errors
appear, consider implementing this solution.
To configure your reporting database server in case connection strings are too
long:
1.
Edit the PrimaveraPSIConfig.xml that was previously copied to

C:\Program
Files\OfficeServers\12.0\Bin\ProjectServerEventHandlers.
2.
Replace the sample ReportingDatabaseServer and

ReportingDatabaseName strings in the file with your MSPS database
server and reporting database names.
Ignore the other fields (which are commented out).
The two values to look for are:
<DBInstance>ReportingDatabaseServer</DBInstance>
<DBName>ReportingDatabaseName</DBName>
Change these values to your actual Reporting Database Server and the
correct Reporting Database name.
ProjectServerLink configuration information is also available in the online
help in Primavera Evolve.
F.3
Setting up Impersonation for Actuals and

ETC
These instructions describe how to set up the Primavera server for impersonation
in Microsoft Project Server (MSPS).
Impersonation is required for submitting actuals & estimated time to complete
(ETC) on behalf of Primavera resources. To download actuals and ETC, the
resources must already be mapped as Enterprise resources in MSPS.
Two sets of configuration instructions follow. Complete one set of instructions
on the MSPS server to which the Primavera server is connecting, and perform the
other set on the Primavera server.
F.3.1
Configuring the MSPS Server for Impersonation
On the MSPS Server, follow these steps to add a user and configure the Shared
Servces Provider (SSP) for processing user accounts. The following information
is from Microsoft at http://msdn2.microsoft.com/en-us/library/
bb428835.aspx section Procedure 1b.
1.
Add the user or group to the Shared Services Provider (SSP) site.
To enable a user to view and modify web pages in the SSP site, do the
following:
2.
Open the SharePoint 3.0 Central Administration page. Under Shared

Services Administration in the Quick Launch, click the name of the
SSP site that hosts Project Web Access.
On the Shared Services Administration page, click the Site Actions

drop-down menu, and then click Site Settings.
On the Site Settings page, click People and groups in the Users and
Permissions section.
Add a user. On the Add Users page, click Give users permission
directly and then select the Contribute check box.
To enable the SSP to process accounts, run the following commands in a

Command Prompt window.

cd [Program Files]\Common Files\Microsoft Shared\web
server extensions\12\BIN
stsadm -o editssp -title [SSPName] -setaccounts [accounts
to add]
The following example adds the pvuser user account for processing in a
SSP named SharedServices1.
stsadm -o editssp -title SharedServices1 -setaccounts
"primavera\pvuser"
This completes the steps for configuring the MSPS server for impersonation.
F.3.2
Configuring the Primavera Server for

Impersonation
The following information is stored in each ProjectServerLink configuration in

Primavera. Set the following attributes for impersonation on the Advanced tab of
the ProjectServerLink configuration screen. The steps below also elaborate on
how to use attributes from the MSPS server:
Impersonation Port: This is the port for the Shared Services Provider
(SSP), and the default value is 56737.
To locate the value for Project Web Access on your Project Server
computer:
Open Internet Information Services (IIS) Manager.
Expand the Web Sites node. Right-click the Office Server Web
Services node.
On the Web Site tab, use the TCP Port value.
Impersonation Site URL Part: This is the name of the SSP site, and the
default name is SharedServices1.
Impersonation Site GUID: This is the site ID for Project Web Access.
Determine the site ID by performing the following steps:
Open the SharePoint 3.0 Central Administration page.
Click the Application Management tab.
Click Create or Configure the farm's shared services.
Click the SSP site name; for example Shared Services1 (Default).
On the Shared Services Administration page, click Project Web Access

Sites in the Project Server section.
For the Project Web Access instance you want, pause the mouse pointer
over the URL, such as http://ServerName/PWA.
Click the down arrow in the right side of the field.
Click Edit.
The Edit Project Web Access Site page appears. It will have a URL
similar to the following:

http://ServerName:19466/ssp/admin/_layouts/
createpwa.aspx?task=Edit&id=44c4ae03-16c2-4618-bf9a12643006c5be
Copy the GUID from your specific URL. This is the value after
id=[GUID]. In the example above, the GUID would be:
44c4ae03-16c2-4618-bf9a-12643006c5be
Paste the GUID into the Impersonation Site GUID text.
Impersonation Username: This is the user setup for impersonation in Step

1 and Step 2 above as part of MSPS configuration steps. An example is
primavera\pvuser.
Impersonation Password: The password for the impersonation user.
This completes the impersonation configuration.
F.4
Configuring Primavera and MSPS for SSL
If SSL (https) is configured for either MSPS or Primavera, refer to the

appropriate section below.
F.4.1
If Primavera uses SSL
If Primavera is configured to use SSL, the MSPS host must have the client
certificate installed.
To install the Primavera SSL certificate on the MSPS host:
1.
Login from the MSPS host to Primavera at:

https://[primavera_hostname/primavera/web
2.
When prompted, install the SSL certificate onto the MSPS host.
For SSL requirements specific to Event Handler, see Configuring Primavera

With SSL and the Event Handler on page 398.
F.4.2
If Microsoft Project Server uses SSL
If the MSPS host uses SSL, the Primavera server acts as a client and the client
SSL certificate must be installed on the Primavera host.
Depending on the SSL configuration of the MSPS host, there are one or two SSL
certificates from the MSPS host that need to be installed on Primavera.

To configure the certificate for Project Web Access Sites on MSPS into the
Primavera Server certificate repository:
1.
To locate the first certificate on the MS Project Server (MSPS) computer:
Open Internet Information Services (IIS) Manager.
Expand the Web Sites node.
Right-click the Office Server Web Services node.
On the Directory Security tab, click View Certificate...
2.
On the Details tab, click Copy to File
3.
Copy the file as OfficeServerCer.cer.
4.
Keep it in a shared drive accessible from the Primavera server computer.
5.
Use the manageCert batch file on the Primavera server to add this
certificate as a trusted site. See Installing the Certificate on page 54 for
instructions on manageCert.
6.
Login to PWA (https://[PWAhost]\pwa) from the Primavera server.
7.
If prompted to install an SSL certificate, download the certificate to the

Primavera server.
8.
Use the manageCert batch file on the Primavera server to add this
certificate as a trusted site. See Installing the Certificate on page 54 for
instructions on manageCert.
F.5
Implementation Considerations
The following table lists MSPS topics that pertain to the ProjectServerLink
integration.
These topics cover adminstration and functionality considerations.
Table 1-1. Administration Considerations

Area
Points to Consider
Authentication methods:
MSPS supports two ways of authenticating users - Windows

and Forms.
Windows
Forms
Essentially Forms is an open ended authentication mechanism,

by which the function of authenticating a user is delegated to
an arbitrary provider.
Microsoft recommends to always have a windows
authentication support, even if Forms is mainly used. Both
authentication mechanisms can co-exist on the same MSPS
installation.
Impersonation technique (used to update individual status in
MSPS from Primavera's Actuals and ETC) requires connecting
to both MSPS and SSP (SharePoint). Not only
ProjectServerLink must connect to both of those systems, it
must also have certain credentials in SSP (see Setting up
Impersonation for Actuals and ETC on page 400).
Currently Microsoft supports only windows users in this
scenario, so in order to use Actuals and ETC in
ProjectServerLink, MSPS must support windows
authentication (with or without Forms) and a user account with
rights to delegate has to be established in SSP.

Area
Points to Consider
IDs and Pwds - what

usernames and passwords are
needed for what purpose?
MSPS user account to connect during manual

synchronization
MSPS SQL Server account to extract data from

Reporting database
Overall, ProjectServerLink requires the following accounts:
ProjectServerLink also might use the following optional

accounts, depending on the features used:
Primavera User Account for Even Handler

MSPS user account for Event Handler
SharePoint User Account for synching Actuals and ETC
MSPS user account for viewing PWA in Dashboard
MSPS user account for viewing PWA in Project
Summary
Client requirements
An ActiveX control must be installed when accessing the PWA

for the first time.
Reporting Database
ProjectServerLink uses MSPS Reporting database to collect

daily hours for task assignments. Go to SQL Server 2005 ->
Management Studio to find the exact name of reporting
database (by default the name is "PWA_Reporting_GUID")
XML file overrides for Event

Handler
ProjectServerLink stores all configuration information that is

required for event handler to push MSPS project data to
Primavera upon publishing in two custom fields
(PrimaveraConfiguration1 and PrimaveraConfiguration2).
Due to MSPS custom field length limitation, Primavera
requires to store MSPS Reporting Database Name and Server
in config.xml file (see Administration guide for details).
Upon changes to these names (for example, the name of the
Reporting server changes), the config.xml file may need to be
updated to reflect the change if this file has been edited.
For more information see Configuring the Reporting
Database Server in Case of Connection Errors on page
398

Area
Points to Consider
dll setup and configuration
In order to configure the Event Handler (see Enabling MSPS

Synchronization for Primavera via an Event Handler on
page 394), two user accounts must be established - one in
Primavera and one in MSPS.
The MSPS account is simply the system account that the event
service is running under. To view this service, see Control
panel -> Services -> Project Server Event Service. Please
ensure that this account is set as an active user in MSPS as
well.
The Primavera user is specified in the Evolve Enterprise MSPS
Configuration within the Advanced tab. This user must have
permission to run synchronization.
Event Handler - error

messages in the
EventHandler log file
Make sure that the daily log files generated in

ProjectServerEventHandler directory don't have any errors.
A likely cause of error is with an invalid Event Handler Log on
account. If there are errors, first check that the "Event Handler
Log On" account is set as an active User on PWA. (This
information for the "Event Handler Log On" account is
available in Control Panel->Services panel->Services->Project
Server Event Service
Table 1-2. Functionality Considerations

Area
Points to Consider
Local vs. Global resources:

Rules on replacing resources
in MSP
Within Microsoft Project Server there are two types of

resources
1) Local resources
Local to Local
2) Global resources
Local to Global
Global to Global
Local resources are visible only to a particular MSP plan.

Global resources are part of the enterprise catalog of resources.
Global to Local
When a user attempts to change a task assignment from

one resource to another, there are certain considerations
to be aware of:
Microsoft Project Server doesn't allow assigning a local

resource to a task if a global resource with same name
exists. It forces user to use global resource instead of
local.
During ProjectServerLink synchronization, Primavera

attempts to resolve MSPS resources based on their
names.
In case of resolving MSPS global resource, if the name is

not recognized in Primavera, then Primavera will always
ignore that resource.
In case of resolving MSPS local resource, if the name is

not recognized in Primavera, then Primavera determines
whether to ignore or rename this resource based on
resolution policy.
If the Primavera policy set to use local resources in

MSPS or not set to map resources at all,
ProjectServerLink allows resolving MSPS local resource
with unknown names by renaming them.
However if the ProjectServerLink policy is set to use

global resources in MSPS, then ProjectServerLink
always ignores the MSPS resource (both global and local)
with unknown name.

Area
Points to Consider

Need global resources to sync
resource schedules
ProjectServerLink allows synchronizing Primavera workweeks

and schedules into MSPS Enterprise Calendars. MSPS
Enterprise calendars are used by Projects and Enterprise
Resources.
If the ProjectServerLink policy is set to use Global Resources
and Resource Calendars, ProjectServerLink automatically
maps each resource's workweek and holiday policy to the
MSPS Enterprise calendar that is associated with the Global
Resource.
The option to synchronize Resource Calendars is not available
if Global Resources are not used.

Projects and Enterprise
calendars
If the ProjectServerLink policy is set to use Project Calendar,

ProjectServerLink automatically maps project workweek and
holiday policy to MSPS Enterprise calendar.
It also associates this calendar with projects in MSPS, but only
at the time when a new project is created.
If the project in MSPS has been already created, the user must
manually set Enterprise Calendar to be a default project
calendar in MSPS.
If an MSPS template is used to create a new project, the User
must manually set Enterprise Calendar to be a default project
calendar in MSPS.

My Tasks and Actuals and
ETC
If the ProjectServerLink policy is set to use Global Resources

and to synchronize Actuals and ETC, Primavera automatically
maps approved time and ETC to MSPS.
Approved Actuals and ETC are updated from Evolve into the
MSPS area known as "My Tasks". For each resource that has
submitted time against a synchronized project, Primavera
updates the "My Task" with the status based on hours logged in
Primavera Time Entry module.
If ProjectServerLink policy is not set to use Global Resources,
then the option to synchronize Actuals and ETC is not
available.
For additional information, see Setting up Impersonation
for Actuals and ETC on page 400.

Area
Points to Consider

Non-project commitments
Non-project commitments are mapped as calendar exceptions

and not as part of "My Tasks". However they are also available
only if the Global Resource option is set.
MSPS projects Checked-out
During synchronization, ProjectServerLink checks out MSPS

plans every time it needs to update them. If the project is
checked out in MSPS by another user, the synchronization is
aborted and a message is displayed telling the user that the plan
in Microsoft Project Server has been checked out.
After the changes are applied to the plan, Primavera will
attempt to check-in the plan.
However it is possible for the plan to be in the checked out
state without users realizing. For example if the plan is
published to the MSPS, but left open in the Project
Professional, it leaves it in the checked out state.
To avoid a locking issue that will prevent anyone from
updating the project in MSPS as well as prevent the
ProjectServerLink to resolve invalid Task Codes or correct the
spelling of unknown resources, we highly recommend closing
and checking in the project plan every time the User is finished
with updates to the plan and when publishing the plan back to
PWA.
A project plan may also be left in a checked-out state when
Project Professional times out after a period of inactivity.
MSPS administrators can unlock the projects by going into
"System Setting" -> "Forced check in".

Area
Points to Consider
Checked-in vs. checked-out
ProjectServerLink does not require a MSPS project to be

checked-in (unlocked) during synchronization except for two
operations:
1) Clearing Task Codes
2) Correcting the spelling of the resource name
If during synchronization neither task codes nor resource
names are affected, the project can be checked-out (in a locked
state) in MSPS, but synchronization will still complete.
However if either a Task Code has to be cleared/changed or
Resource Name has to be updated, ProjectServerLink will stop,
display an error, and the Administrator will need to perform a
"Forced Check-in" for synchronization to work.
MSPS Templates - problems

creating new project with
templates
ProjectServerLink allows a user to create a new project in

MSPS based on MSPS template.
However, there is a known issue in Microsoft which prevents
templates to be used in this capacity if they were upgraded
from MSPS2003 or from a MSP Plan prior to Project
Professional 2007.
Project creation via templates is currently available ONLY if
the template has been created in MSPS 2007 from scratch. Any
attempt to migrate the template either from Project Server 2003
or prior versions of Project Desktop will lead to exceptions
during synchronization. Microsoft acknowledged this
limitation and currently is working to resolve it.
No invalid task flag
Unlike ProjectLink, where unresolved data is flagged with a

red circle as being "tentative", ProjectServerLink doesn't have
any indicators in MSPS plan for unresolved data. The User
must login into Primavera and navigate to the synchronization
log to see which resources and resource assignments are still
unresolved.

Area
Points to Consider
Macro-equivalent functions
delta
ProjectServerLink is similar to ProjectLink in that it supports

the same basic functionality to allow a WBS and Resource/
Staffing information to be shared between Microsoft and
Primavera Evolve.
ProjectServerLink supports synchronization of Project and
Resource Calendars, Milestone Tasks, Inactivity
Commitments, Actuals and ETC.
However ProjectServerLink does not support the following
items: Position replacement with Assigned Resource, Position
Creation from MSPS to Primavera, Custom Fields.
Single task group per server
ProjectServerLink requires a single Primavera Task Group to

be associated with MSP Server.
This design is due to the Microsoft limitation that the
Enterprise Global Custom Fields, which are leveraged to store
task groups, cannot be partitioned per project(s). If
synchronizing task codes from Primavera Evolve to Microsoft,
a single task group that includes all relevant task codes must be
created.
Resources duplicate name

and name recognition
Similar to ProjectLink, ProjectServerLink depends on resource

names to be spelled in exactly the same way in Primavera and
MSPS.
In MSPS, the resource display name should be "FirstName
LastName" as defined in Primavera.
If Global Resources are used in MSPS then users should avoid
typing the names and use only the dropdown menu to assign
resources to tasks. (Note that during synchronization Primavera
will only offer to "ignore" a misspelled resource and not to
correct it).
If Global Resources are not used in MSPS, then similar to
ProjectLink, MSPS users can either type the name or use the
dropdown menu populated by ProjectServerLink to assign
resources to tasks. (Note that during synchronization
misspelled names can be corrected).

Area
Points to Consider
Global Catalog / Task Codes

- caching of MSProject
desktop
If any global catalog information that is synchronized from

Evolve to MSPS changes, the User must restart Project
Professional 2007 in order to get the latest updates of
Enterprise Custom Fields.
This means that if Task Codes were modified in Primavera and
then the change was pushed to MSPS, the user must restart the
Project Professional 2007 (desktop) in order to synchronize the
global catalog from MSPS to their local computer.
How to save MSPS

Enterprise templates
When a new project is saved in MSPS, the user can make a

choice whether to save it as a Project or Template. If the
project plan is saved as a Template, then this template can be
used to create a new project, by clicking on New and selecting
Enterprise Templates from "On computer" option.
In order to make changes to the template itself, the User must
create a new project based on this template, then make
necessary updates and save it as a Template again. Upon
saving, the user can type the original template name and chose
the override option when prompted.
Timeout of MSProject
desktop
Project Professional 2007, if left inactive for some time,

displays an error 9000 that seems to be a "time out" error. The
only choice the user has is to shutdown the application and
restart it again.
However this leaves the project that was opened in checked-out
state that can only be cleared in PWA > Server Setting
> Forced Check-in.

Area
Points to Consider
Enterprise vs. Project vs.

User policies
There are three levels where the ProjectServerLink

synchronization policy can be defined.
The top level is Enterprise - options like MSPS url and MSPS
alias can be defined only at this level. Other options, like
synchronization option, can be defined at the Enterprise level
or can be allowed to be defined/overridden at the Project level.
The second level is Project and similar to the Enterprise. Some
options can only be defined here (Milestone Tasks, Dashboard
credentials, etc). Other options, like synchronization options,
can be defined at the Project level or can be allowed to be
defined/overridden at the individual user level. If the Enterprise
policy doesn't allow the Project level override, then those
options cannot be modified at the Project as well as User
levels.
The third and last level is User. Individual users can define the
synchronization options, except those that are set with no
overrides at the Enterprise or Project level, for each
synchronization run. Please note that User options remembered
as User preferences, which means that same user will have the
last synchronization option regardless if she synchronizes the
same or a different project.

Area
Points to Consider
Enterprise catalog
synchronizations
There are two Primavera Enterprise catalogs that are

synchronized to MSPS:
1) Task Codes
2) Calendars (workweek and holidays)
In order to synchronize Task Codes, the User should go the
Enterprise level configuration and Save/Activate it. This will
force Task Codes from the Group set at the configuration to be
synchronized with MSPS.
The calendars can be synchronized by two ways:
1.
Explicitly by navigating to Enterprise configuration

advanced tab, and then selecting the workweek and a
holiday policy. The User can optionally update the MSPS
calendar name or leave it as is (Primavera defaults it by
concatenating workweek and holiday policy names).
User have to click on synchronize command to force
synchronization. Note that after this the User doesn't have
to save the configuration and can simply cancel it, since
the changes are applied right after the click. The user can
repeat the steps and synchronize multiple calendars.
2.
Implicitly by synchronizing the project if either the

Project Calendar map or Resource Calendar map is
selected. Then during project synchronization, the
appropriate calendars will be synchronized, that
potentially has effect beyond the single project. If let's
say the same calendar is used in several projects and its
workweek was updated in Primavera, synchronizing a
single project will update the Global Calendar in MSPS,
and this will affect all the MSPS project that are using
this calendar.

Area
Points to Consider
Global data - object life

cycles
Global catalogs (Task Codes and Calendars) are synchronized

in a such a way that erases all the changes made directly in
MSPS and forces the MSPS catalog to be exactly like its
counterpart in Primavera.
To avoid any day loss, please do not update the Task Codes
global custom field or global calendars in MSPS manually.
If a holiday is removed from the holiday policy in Primavera
Evolve, the next time that calendar is synchronized,
ProjectServerLink will remove the holiday from the MSPS
calendar. The same applies to Task Codes.
Resources - object life cycle
If Primavera resources are mapped to MSPS (either as global

or local), resource First Name and Last Name are used as a key
in ProjectServerLink to connect a Primavera resource to a
MSPS resource.
This means changing the name (last or first) in Primavera and
then synchronizing the project will result in the creation of a
new resource in MSPS rather then updating the name.
In order to avoid this, manually update the name in MSPS
before synchronizing the project.
ProjectServerLink will attempt to create resources within
MSPS. However, ProjectServerLink requires names to be
unique. To avoid potential conflicts, you may choose to
implement Active Directory or LDAP to manage user accounts
across Primavera Evolve and Microsoft Project Server.
MSPS character limitations in

Project and Resource names
Microsoft doesn't allow the following characters in Project

Name - .(period) \ " | / ' ? ; : < > * #
For Resource Name only square brackets or commas are not
allowed
F.6
Configuring SharePoint to Support

Fully-qualified Domain Name in PWA URL
To ensure that the ProjectServerLink activation works if the server URL is a fullyqualified domain name, follow the steps given below.
1.
Click StartAll ProgramsMicrosoft Office ServerSharePoint 3.0

Central Administration.
2.
Click the Operations tab.
3.
Go to Global Configuration and click Alternate Access Mapping

Collection.
4.
Select the Add Internal URLs option.
5.
Navigate to the existing PWA site from the Alternate Access Mapping
Collection dropdown list.
6.
Click Add Internal URLs, and enter the fully qualified domain name along
with the same port number as the PWA site in the text field.
7.
Select the Intranet option from the Zone dropdown list.
8.
Click Save.
Now you can activate MSPS from within Primavera.
Certifications
G.
Certifications
This appendix describes the recommended software for use with Primavera, as
well as the minimum requirements for Primavera clients.
Some of the certifications listed in this appendix may not apply to the current
version of Primavera. In this case, refer to the Primavera release notes for a list of
platforms that were not certified.
For more information on recommended implementations and hardware
configurations, contact Primavera.
The appendix includes:
Certified Software Platforms
Hardware Requirements
Certifications
G.1
Certified Software Platforms
Primavera certifies these platforms:

Certified Server Software
Certified RDBMS
Certified Client Platforms
Certified Web Servers
Certified API Client Configurations
Certifications
Table G-1
Certified Server Software

Windows 2003
Enterprise Server SP2
Server Application2
BEA WebLogic Server

10.0 MP1
Solaris1 10
Not supported
BEA WebLogic Express

10.0 MP1
Analytic Applications3
BEA WebLogic Server

10.0 MP1
Not supported
BEA WebLogic Express

10.0 MP1
Integration API Web
Services
Certified
Not supported
Connectors
Certified
Not supported
Actuate 9.0 SP2
Certified
Certified
WorkSite MP 3.1 SP1 Fix 2

(Collaboration)
Certified
Not supported
LDAP
Compatible with LDAP

version 3
Not supported
Virtual Server4
VMWare ESX Server

3.5
Not supported
1 Primavera certifies the 64-bit versions of Solaris.

2 WSDL4J version 1.6.2 is required for each server. See WSDL4J
Installation for download and installation instructions.
3 Hibernate2 version 2.1.4 is required for analytic applications. See
Hibernate2 Installation for download and installation instructions.
4 VMWare is certified for running the Evolve Application Server only.
Certification does not apply to copying and restoring images. Copying Evolve
Application Server image requires complete re-installation.
Certifications
Table G-2
Certified RDBMS
Windows 2003
Solaris 10
RDBMS for the Core Application

Primavera Core
(PVDB)
MS SQL Server 2005

(SE or EE) SP 2
Oracle 10.2.0.4
Oracle 10.2.0.4
Delivery Manager
(DMDB)
MS SQL Server 2005

(SE or EE) SP 2
Not supported
RDBMS for Analytic Applications

Data Mart
(Target)
MS SQL Server 2005

(SE or EE) SP 2
Oracle 10.2.0.4
Oracle 10.2.0.4
Analytic Applications
OLAP DB (cubes)
MS SQL Analysis
Services 2005 SP 2
Not supported
Certifications
Table G-2
Certified RDBMS (Continued)

Windows 2003
Portfolio Manager
(PM) DB
MS SQL Server 2005

(SE or EE) SP 2
Solaris 10
Oracle 10.2.0.4
Oracle 10.2.0.4
Exporter DB
MS SQL Server 2005

(SE or EE) SP 2
Oracle 10.2.0.4
Oracle 10.2.0.4
Collaboration DB
MS SQL Server 2000

(EE) SP 4
Oracle 9.2.0.7.0 (64

bit)
Primavera certifies the 64-bit versions of Solaris and Oracle.

Oracle character set/national character set needs to be AL32UTF8/
AL16UTF16. For MS SQL, use the default.
Primavera server can run as a service on Windows.
Certifications
Table G-3
Certified Client Platforms
Primavera Software
Windows XP SP 3
Windows Vista EE SP1
Core (including
Collaboration)
Actuate Reports
MS IE 7
MS IE 7
Portfolio
Management
MS IE7
Configuration/
Security & Account
Manager
Certify
Certify
Offline Time &

Expenses
MS IE 7
MS IE 7
ProjectLink
MS Project 2002
MS Project 2002
MS Project 2003
MS Project 2003
MS Project 2007
MS Project 2007
MS Project 2007
MS Project 2007
IE 7
IE 7
ProjectServer
Link/PWA
Firefox 3.0
MS IE 7
Firefox 3.0
The RDBMS client software must be installed on all computers that host
Primavera server components, with the exception of the Standard Import
Connector. For the Oracle clients, select the Administrator installation type
during installation.
Certifications
Table G-4
Certified Web Servers

Windows 2003 Enterprise Server
SP2
Core Application, WorkSite MP
Microsoft Internet Information Server

(IIS) 6.0
Actuate Reports
Actuate default http
Analytic Applications (PM)
Microsoft IIS 6.0
Certifications
Table G-5
Certified API Client Configurations

Windows 2003 Enterprise Server
SP2, Windows XP SP3, or Windows
Vista EE SP1
Development Platform
Microsoft .NET 3.0 or

Sun Java Development Kit (JDK)
1.5.0_11 or JRockit 1.5.0_11
Sample Application Build Tool
Apache Ant 1.6.2
Running a client program against API requires either JDK or .NET. Building
API samples requires ant.
WSDL4J version 1.6.2 is required for Primavera API client. See WSDL4J
Installation for download and installation instructions.
Certifications
G.2
Hardware Requirements
Primavera provides the following requirements as a starting point for designing a

hardware architecture in support of the Primavera application. Since each
customer has individual needs, this section does not offer specific
recommendations or certifications for particular customer environments. For
more precise hardware configuration advice, contact Primavera Professional
Services.
Server Hardware Requirements
Client Hardware Requirements
Certifications
Table G-6
Operating
System
Windows
Table G-7
Server Hardware Requirements
Server
Hardware Requirement
Primavera Server
Host
2.3 GHz Pentium Xeon CPUs with

4 GB of RAM; 50 GB disk space
Database Server Host
2.3 GHz Pentium Xeon CPUs with

4 GB of RAM; 50 GB disk space
Client Hardware Requirements
Operating
System
Client Type
Windows
Web client
1024 x 768 screen resolution; 266

MHz with 128 MB of RAM
Desktop client host*
1024 x 768 screen resolution; 266

MHz with 128 MB of RAM; 150
MB of free space
* Used by system administrators
Minimum Hardware
Requirement
Glossary
Glossary
A
Accessible. Able to be viewed or modified, given company access, the Object
Access Policy and a particular account's Access Role, and whether the account
owns any objects.
Access Control. The process of ensuring that the information within
Primavera is safe against unauthorized access. Security in Primavera is based on
access rolesand access policies.
Access Role. A set of access rights (Privileges) granted to an account. Access
roles determine the information a user can view or modify.
Access Role Catalog. Contains the access roles defined for the enterprise.
Account. An established relationship between a person and an application.
Access to data and functionality in Primavera is limited by the Access Role
associated with the account.
Agency. An external organization that supplies resources to the enterprise for
projects.
Agency Resource. A resource employed by an agency, and contracted to the
enterprise to perform project work. Sometimes called a consultant or contractor.
API. Application Program Interface. A set of routines, protocols, and tools
building blocksfor building software applications.
Application Server. Software that runs between thin clients and back-end
databases and applications to provide business processing. The Primavera Server
Application must be deployed to a third-party application server.
Approver. A Primavera user that has been granted privileges to approve Time
and Expense reports for a particular project, project pool, or resource pool.
Assigned. When a resource is Assigned, the period between the start and end
dates of the position is marked assigned in the resource's schedule. This affects
resource Availability. An assignment commits that resource to the position.
Glossary
Audit Report. In Primavera, a report that the system administrator must run
and submit to Primavera. The Audit Report determines your licensing fees.
Authentication. The process of identifying an individual, based on a login
name and password. In Primavera, authentication is distinct from access control.
Authentication ensures that an individual is who she claims to be.
Availability. The time in a resources schedule that is not filled by
commitments.
B
Browser. A software program used to view HTML documents and World Wide
Web pages. Primavera and its accompanying reports can be displayed in a
browser.
Business Object. A phenomenon tracked by the enterprise affecting project
decisions as they are represented in Primavera. Resource, Opportunity,
Project, Client, Competitor, and Agency are business objects.
Business Role. A set of qualifications associated with sets of estimated billing
rates and costs. A business role can also have a rate range. Project position
definitions can be based on business roles.
C
Classification. An enterprise-specific categorization of profiles that is an
alternative to the pool and organization structures. Depending on the enterprise's
needs, classification types might include line of business, product, market region,
or any other alternate way of categorizing business objects. Classification types,
names, and possible values are defined at the enterprise level.
Client. Two meanings of this word pertain to Primavera: a software client that
accesses a server to retrieve information or request processing; and an
organization outside the enterprise for whom a project is undertaken.
Client Resource. A person who is employed by the client and can be assigned
to work on a project. Client resources do not have profiles.
Glossary
COM. Component Object Model, a technology used by applications to make

objects available to development tools, macro languages and other applications.
These external systems can manipulate the applications objects by invoking
methods on the objects or by setting the objects properties.
Company. A predominantly independent division of the enterprises
Organization Structure that contains Organization Units. Financial
information defined for a company is used by its organization units to regulate
billing and Time and Expense reporting, and to default values for opportunities,
projects, and resources.
Competitor. A business rival that competes with your enterprise for
opportunities and projects.
D
DBA. Database Administrator.
Data Source Name. DSN. Specifies how a client should connect to a
particular data provider.
Database Alias. Specifies information about an Oracle database instance that
is used by clients to connect. Also called a Service Name.
Database Server. An application that allows you to modify, update, or create
records in a system of organized information (database).
Domain. A special pool that can contain any number of accounts and pools.
Domains demarcate the scope of operations and define access rights for users
both Internal and External to the domain. An enterprise has two or more
domains: the enterprise domain, and the unassigned domain.
E
Editable. When a configuration pane is editable, you can add or modify values.
When a pane is not editable, the labels on fields and options are gray.
Employee. A resource hired by and working for the enterprise.
Enterprise. The organization served by the application, that is, your company.
The enterprise encompasses all business data in the application.
Glossary
Excluded. When a resource is excluded from a position, the resource cannot fill
this position for some reason. For example, if a resource you reserved for a
project had a disastrous interview with the client, you could exclude that resource
to ensure that he was not staffed to the position.
Expense Types. One of the Financial Rules, an enterprise-specific
categorization of resources expenses.
External. An account is external to all domains that do not contain it. Subdomains are external to the parent domain. This concept is integral to Primavera
access control.
External Access Policy. Defined for pools, the External Access Policy
determines access for accounts that are external to the pools domain.
External Authentication Method. A service that authenticates users login
IDs and passwords. If your enterprise uses such an external authentication
method, such as LDAP, you must enter each resources external authentication
ID in the Login ID field of the resource profile.
F
Firewall. Hardware or software that prevents unauthorized access to a private
network. Firewalls often separate an enterprises intranet from the Internet.
Foundation Information. The configurable data and policies in Primavera,
including Look Up Data, catalogs, structures, and policies. Foundation
information provides values that ensure consistent and efficient data entry.
Functional Organization Structure. The organization structure that
represents the reporting relationships within your enterprise. This organization
structure reflects all or part of your organization chart and provides a framework
for financial configuration. In Primavera, the organization structure consists of
companies and organizations within those companies.
Glossary
G
H
Host. The computer that executes a piece of software; the computer upon which
a particular application runs.
I
Import/Export. The process of bringing external data into the application or
sending internal data out of the application.
Instance. An occurrence of an application in run-time. For example, an instance
of the Primavera Server Application is a single occurrence of the server
application software running on a host computer.
Internal. An account is internal to any domain that contains it, and to any subdomains. Accounts in the Enterprise domain are internal to all domains. This
concept is integral to Primavera access control.
Internal Access Policy. Defined for a pool and some business objects, the
Internal Access Policy determines access for accounts that are internal to the
pools domain. Owner access to pool contents is also determined by the Internal
Access Policy.
J
JDBC. Java Database Connectivity. A database access standard, JDBC allows
Java applications to access data, regardless of which RDBMS stores the data.
Job Title. The label given a collection of duties and responsibilities that
describe the work performed.
K
L
LDAP. A client-server protocol for accessing a directory service. A directory
service provides information about network resources or users. For example, Sun
ONE Directory Server and any Domain Name Server are LDAP servers.
Glossary
Login Policy. In Primavera, the policy that dictates how resource account
logins are generated when resource profiles are added to the system. In
Primavera, logins are generated by appending the first initial to the last name.
Look Up Data. A set of data types configured at the enterprise level. The
values describe resources, opportunities, projects, and clients.
M
MS Project Server. . supported enterprise-level server developed by
Microsoft that runs in Windows environments. Allows you to manage work from
ad-hoc projects to complex programs across the entire project lifecycle. Users
access Office Project Server 2007 through its clients on the desktop, on the
Web, or, through integration with other Microsoft Office systems or applications.
Requires Microsoft SQL Server and Microsoft Windows Server.
MS SQL Server. A supported relational database management system
(RDBMS) developed by Microsoft that runs in Windows environments.
Macro. A subroutine written in the Visual Basic for Applications editor.
Mail Server. An application that receives and disseminates email.
Maintenance Access Policy. The access policy given to pool owners who
are responsible for maintaining pools. This policy governs access to the pool
itself, not to pool contents.
Mandatory. In Primavera, refers to activities in the pursuit process that must be
marked complete before the phase that contains them can be marked complete.
Messages. An in-box within Primavera:
Notifications and staffing requests for positions and resources can be
received here.
Messages in Financial Rules stand for codes that automatically add notations
to an outgoing invoice. Messages on invoices are also known as comments.
N
Non-resource Account. An account manually created for individuals who
must use Primavera but do not have profiles.
Glossary
Non-resource Item. Part of a delivery scenario and pricing model; a material

object or an expense for which the client will be billed.
O
ODBC. (Open Database Connectivity) A database access standard. ODBC
allows applications to access data, regardless of which RDBMS stores the data.
Object Access Policy. A policy defined for a pool, specifies the access roles
and users that are granted privileges in the pool or to the object. The object access
policy includes an Internal Access Policy, an External Authentication
Method, and a Maintenance Access Policy.
Object Pool. A Pool that contains Business Objects (rather than pools or
accounts). Object pools can contain any number of objects of one type:
opportunity, project, resource, client, competitor, or agency.
Off-time. In configuring transaction types, off-time represent the types of
non-project commitments available when editing a resources schedule.
Opportunity. New business pursued by your enterprise. When an opportunity
is won, it generates one or more Projects.
Oracle. A supported relational database management system (RDBMS)
developed by Oracle Corporation that runs in Windows and Unix.
Organization Structure. See Functional Organization Structure.
Organization Unit. A group of resources organized by some similarity, such as
job function. Organization units are arranged hierarchically to form companies.
Together, organization units and companies constitute the Functional
Organization Structure.
Owner. The user responsible for a particular pool. By default, a pools owner
has the authority to determine the Object Access Policy. A resource owns his
resource profile, and can be granted the privileges displayed on the TAPs My
Profile tab.
P
People. See Resource.
Glossary
Pool. A logical grouping of business objects or pools. Pools that contain

accounts are called Domains. Domains can contain any number of pools and
accounts. Pools that contain business objects are called Object Pools.
Pool Structure. The hierarchical structure of pools that represents a navigable
view of your enterprise. The pool structure contains Pools, Data Source Names,
Object Pools, Opportunity, Projects, Resource, Clients, Competitors, and
Agency.
Privilege. Permission to take some action in Primavera. A Task Access Policy
grants and revokes privilege on various UI Components.
Production. Describes an implementation of software in which users process
an enterprises business data. Typically used with environment and contrasted
with test environment.
Project. A temporary endeavor undertaken by the enterprise to create a unique
product or service for a client.
Q
Qualification. An education, skill, or certification that your enterprise tracks
and recognizes. Qualifications are a factor in Suitability.
Qualification Checklist. A feature for qualifying an opportunity in terms of
client commitment and the feasibility of executing the project.
R
RDBMS. Relational Data Base Management System. An application that allows
you to modify, update, or create records in a system of organized information
(database).
Reports. Formatted and organized presentations of Primavera data.
Reserved. When a resource is reserved for a position, the period between the
start and end dates of the position is marked reserved in the resources schedule.
This affects resource Availability. Depending on configuration, an action of
Reserved may prohibit a resource from being reserved or assigned to a different
position during the same time period.
Glossary
Resource. An individual represented in Primavera, such as an employee,

agency resource, or client resource.
Resource Account. An established relationship between a resource and the
Primavera application. A resource account, which is automatically created for a
resource when the resource profile is created, often has limited permissions in
Primavera.
Role. A set of attributes or functions. Primavera includes two types of role:
Access Rolesare assigned to accounts and Business Rolesare assigned to
positions.
S
Scheduled Date Range (SDR). A position schedule or resource commitment
schedule, as it is stored in a Primavera database. In the Primavera core database,
these schedules are stored in a condensed format. When they are transferred to
the Data Mart database, the data are fully denormalized. SDRs account for a large
percent of the Data Mart's database.
Security. See Access Control.
Server. A computer on a network that manages data and processes requests.
Servers are accessed by Client.
Server Application. In Primavera, the server application enforces business
rules and manages the flow of data between clients and the Application Server.
Server Instance. A piece of server software executing on a host.
Service. A process that performs a specific system function and usually
provides an API for other processes to call.
Service Name. See Database Alias.
Shortlisted. When a resource is shortlisted for a position, the resource is
flagged to indicate that they are a potential candidate for the position. This action
indicates that you are considering a resource for a position. When you open the
Team Builder with this position, any resources you have shortlisted are
displayed. Shortlists do not affect Availability.
Glossary
Structure. A hierarchy of one or more groups that represent your enterprise.

Structures are used to bind together similar information. Structures include the
Functional Organization Structure, the Pool Structure, and the office location
structure.
Suitability. The degree of fit between a resource and a project position. Three
criteria determine suitability: Availability, Qualifications, and Job Title. A
score is determined for each of these, then an overall score is determined for
suitability. Team Builder and Team Locator express suitability as a percentage.
System Administrator. An individual who must access configuration and
access control aspects of Primavera. Sometimes called an administrative user.
T
Task Access Policy. A policy (used in OAP and access role definition) that
specifies whether an account or access role can interact with certain portions of
the user interface. For example, a Task Access Policy may indicate that resources
cannot view or edit client profiles. In this case, the accounts that have this Task
Access Policy cannot see the Client option in the Main Menu.
Template. A standard pattern defined by an enterprise to encourage consistency
of data entry. Templates can be defined for pursuit processes, qualification
checklists, teams and tasks.
Time and Expense. A feature that allows users to enter and approve time and
expense reports. Time and expenses can be entered on or offline. Approval is
executed online only.
Time and Expenses Administrator. A user that has been granted
permission to act on behalf of other users when entering or approving time and
expense reports. For example, a time and expenses administrator could approve
reports usually approved by a vacationing project manager.
U
UI Component. A field, pane, or window in the user interface (UI) for which
individual privileges are granted in a Task Access Policy.
Glossary
Unassigned Domain. A domain that always appears in the pool structure. It

can contain the profiles that do not neatly fit into other object pools.
URL. Uniform Resource Locator. The globally unique address of a document or
other resource on the World Wide Web.
User. A person who has access to Primavera. A user has either a Resource
Account or a Non-resource Account.
User Account. See Account.
V
VBA. Visual Basic for Applications. An object-oriented programming
environment for Microsoft Windows products.
W
Web Server. An application that fields requests for web content, including
HTML documents and Java applets.
Wildcard. A symbol used to represent unknown characters in a search. In
Primavera, prefix a search with %. Searches return objects that contain the letters
you specify. For example, %ram returns grammar, tram, and diagram.
X
Y
Z
Glossary
Index
Index
A
access control 192, 278
access denied 368
access role 207
access roles
and accounts 265
and analytic applications 202
and companies 270
and privileges 224
assigning to accounts 268
conflicting 265
default 157, 264
example 281
overview 263
privileges 224
accounts
and access roles 265, 268
and domains 254
example of access 285
non-resource 255
overview 253
removing 261
resource 254
unable to delete 261
updating 259
active web sessions 160
Actuate
about reports 177197
and resource files 323
certified version 421
functionality 29
installation 40, 323
admin account 253, 262
Admin page 157176
administration
authentication options 151
client options 140
database options 144, 148
login auditing 161
server options 142
tool 28, 30, 139
administrative commands 157
administrator access role 157, 264
Administrator Configuration window 131
Adobe Acrobat Reader 13
agency ID 163
AlphabloxDB database 37
analytic applications
access control 202
and currency 78, 101
and MS Analysis Services 23, 38, 98
and pvuser 33
and SSL 57
databases 292, 307, 422, 423
installation 109
unsupported in Solaris 421
anti-virus software 357
Apache Ant 426
API
and building the sample
application 426
functionality 28, 30
installing the client components 112
supported client platforms 426
supported server platforms 421
application
Security and Accounts Manager 199
application server
terminology 20
unable to start 356
appserverconfig.properties 120
audit report 182
auditing logins 161
Index
authentication options 151
authorizing languages 176
automatic synchronization
DM 344
B
backup data 288
billing rate privileges 228, 230
billing reports 190
BIRT
appserver connection 71
BIRT reports 6773
secure connection 68
budgeting privileges 235
Business Intelligence 54, 109
business role report 187
business transactions 242, 252, 387
C
CA certificate 118, 361, 367
caches
global 159
web client 158
calendar 214
Capacity Planning
and Data Mart 81
enabling 81
Capacity Planning report 182
catalog reports 187
CD-ROM 28, 43
certificates 54, 118
certifications
as qualifications 188
of hardware and software 419
certified platforms 420
character set 304, 305
client
administration options 140
connectivity 359
installing separately 112
reports 185
starting 129
stopping 133
terminology 20
unable to start 358
web browser 141
client ID 163
client trace option 359
clients.exe 112
collaboration database 37
ColorSchemes.properties 62
COM 379
command prompt window 314, 359
company 101, 270
competitor ID 163
Configuration application 30, 54, 118,
158
configuration values, refreshing 158
Confirm Password 145, 147, 149
connectivity
and clients 358, 359
and Oracle 308, 309
and reports 294
connectors
and DM 51, 149
and installation 51, 88
and RDBMS clients 424
functionality 28
console option 359
Console Output File 141, 142
core competencies report 186
count SQL files
countMessages.sql 296
countSystemMessages.sql 296
currency 101
Index
custom reports 192
Customer Support Center 21
CustomizedLink.properties 66
D
Dashboard 236
dashboard privileges 236
Data Mart
and Capacity Planning 81
creating the schema 301, 317
currency conversion 101
databases loaded by 300, 316
db-to-db transfers 95
error email configuration 100
PV_OLAP 37
target database 37, 95
Data Mart database schema
create 317
database
administration options 144, 148
backup and restore 288, 310
connectivity 294, 308
createOracleUser script 306
maintainssdb 295, 311
recommendations 287317
required, by component 37
restoreCoreOracleDb 310
restoring 288, 310
schema 29, 299, 314
StrategicPlanning 49
database alias 36
Database Instance 147
Database Name 145, 149
Database Server Software 145, 147
Database Type 149
db_block_buffers 317
delete SQL files

deleteSavedQueries.sql 297, 313
deleteWPModels.sql 297, 313
deleting accounts 261
Delivery Manager
and unrestricted projects 350
considerations 27
pollster 346
schema 299, 314
synchronization 150, 340
desktop client 112
dictionary sort order 291
directory server 151, 154
distribution
CD-ROM 28, 43
image 28, 43
DMDB 27, 340
and backup 288
contents 340
creating the schema manually 299, 314
identifying 149
sizing 292
synchronization 340349
DMDB database 37
domain 207, 210
E
education 188
email server 143
employee reports 186
English 176
evaluation privileges 229
event handler 394
Event Handler Log 398
Event Handler log 399
expense
policy 250
expenses. See time and expenses.
Index
export connectors 28, 88
External Access Policy 207, 221, 283
external links 66
F
file
dm_storedproc.sql 51
financial data 270
Financial Manager 95
firewall 36, 141
forecast privileges 228
Forecasts tab 228
forgotten passwords 260
French 176
G
general privileges 225
German 176
global cache 159
groups 170, 237
initial length of IDs 163

initSID.ora 304, 305
installation
Actuate 40, 323
and Delivery Manager 299, 314
client only 112
example 23
in Windows 43119
MS Analysis Services 38
prerequisites 3142
RDBMS 36
WorkSite MP 329
Instance Name 145, 149
Internal Access Policy 207, 221, 283
invoice report 192
ISAPI filter 60
Italian 176
J
job catalog 187
K
H
hardware requirements 427
holiday schedule 214
host
of RDBMS 147
terminology 20
web server 141
I
ID format 163
IIS 59
impersonation 400
Impersonation Site GUID 403
import connectors 28, 88
knowledgebase 21
L
languages 176
LDAP 151, 152, 154
LDAP-authenticated ID 155
Linked Server 95
linked server 95
links, in Main Menu 66
load-balancing
host 61
locale settings 176
Index
login
IDs 154, 259
login auditing 161
password 145, 147, 149
to MS SQL Server 145, 149
to Oracle 147
logo.gif 62
M
Mail Server 143
maintainssdb 295, 311
manageCert 55, 118, 361
material resource privileges 235
messages 296
Microsoft
Analysis Services 34, 35, 38
.NET Framework 30, 114, 426
Project integration 114, 379
and deleting messages 296
and terminated resources 297
configuration 301
Data Mart database 301
Linked Server 95
recommendations 291
sort order 291
Monitor Server 161
monitor server 159
MSPS
configure reporting database
server 399
extensions 392
MSPS integration 203
my profile privileges 229
N
non-project commitment privileges 226
non-resource accounts
creating 257
overview 255
removing 261
notifications 296
O
Object Access Policy
and pools 205, 206, 209
and privileges 224
defining 238
example 283
overview 221
object pools 208, 210
ODBC data source 294
office location 187
Offline Time and Expenses 30, 54, 118,
361
OLAP
creating the database 302
OLAP cubes 38
online documents 13
OPEN_CURSORS 304, 305
opportunity ID 163
Index
Oracle
and language support 304, 305
and resource files 323
and terminated resources 313
character set 304, 305
configuration 317
createOracleUser script 306
Data Mart database 317
initSID.ora 304, 305
OLAP & Delivery Manager
databases 314
OPEN_CURSORS 304, 305
point-in-time recovery 288
recommendations 303
restoreCoreOracleDb 310
user 147, 306
ORACLE_HOME 315
organization structure 187, 280
organizational view 205, 217
owners 206, 208, 212
P
parasync.resync.bat 347
partial restore 288
passwords
changing 262
default 260
resetting 260
to MS SQL Server 145, 149
to Oracle 147
PATH environment variable 315
.PDF files 13
performance
and Data Mart 363
and project bulk update 363
pipeline report 184
platforms 420
point-in-time recovery 288
policies
expense 250
policy
editing for a pools access 236
External Access 223
Internal Access 208, 212, 213, 223
Maintenance Access 208, 212, 213,
224
Object Access 220, 221, 222
Task Access 221, 224
using Dashboard for 236
Policy Editor 238
pollster
parasync 344
pool structure
access control example 279
in web client 208
overview 205
purpose of 205
recommendations 217
simple example 218
pools
adding 210
and calendars 214
defining Object Access Policy 238
overview of 206
owners 208, 210, 212
properties 212
report 187
pop-up blocker 366
port
MS SQL Server 141, 147, 149
Oracle 145
Portfolio Management 54, 109, 368
posted transactions task privileges 234
Postinstallation 120
preference catalog 187
prefix for IDs 163
Primavera Administration 139
Index
Primavera database 37
Primavera Online INTeraction
(POINT) 21
Primavera web client
adding links 66
and Administration tool 143
and SSL 141
color scheme 62
configuring 60
login auditing 161
qualifications edit threshold 368
Primavera-authenticated ID 155
PrimaveraPSIConfig.xml 399
PrimaveraPSIEventHandler.dll 394
PrimaveraPSIExtension 393
PrimaveraPSIExtension.dll 392
printer-friendly 7073
printing online documents 13
privileges 224
problems 355
program folder 113
project
accounting privileges 234
bulk update performance 363
commitment privileges 226
ID 163
owner privileges 235
reports 184
ProjectLink 165
and Microsoft .NET 30
and Secure Socket Layer 54, 118
API 379
extended functionality 116, 379
functionality 30
installation 114
locale setting 176
ProjectLink API
macros 116
ProjectServerLink 165, 167

database connection method 392
publish privileges 236
publishing content 236, 368
PV_OLAP 37, 302
PVDB 27, 316, 340
creating 314
in MS SQL server 145, 147
upgrading 290
user, in Oracle 306, 314
PVDB database 37
pvuser
act as part of the operating system 34
and Microsoft Analysis Services 34,
35
as OLAP administrator 35
creating 33
Q
qualifications
edit threshold 143, 368
reports 187
R
read-only files 357
recommendations
server hardware 427
software 419
removing accounts 261
report privileges 232
reporting currency 101
Reporting Database name 399
Reporting Database Server 399
Reports
User Access Roles By Pool 188
Index
reports
Actuate 177
and rates 178
configuring 177
custom 192
delivered 181
in Solaris 323
in Windows 76
installed files 29
invoices 192
requirements
components 28
hardware 427
resetting passwords 260
resource
reports 186
resource profile 207
resources
access roles 264
accounts 154, 254
and saved queries 297, 313
and workforce planning models 297,
313
IDs 131, 163
login IDs 154
terminated resources data 297, 313
restoring databases 288, 310
resume generation 67
roles 170
S
sample macros 116
US locale 116
Sarbanes-Oxley 161
saved queries
and terminated resources 297, 313
finding 298, 314
schema, creating 29, 314

Secure Socket Layer (SSL)
and analytic applications 57
and LDAP 152
and Primavera clients 141
and Primavera URL 61
enabling 54, 143
importing certificates 5459, 118, 361
secure web connection (https) 68
secure web connections (https) 70
Security and Account Manager
and custom reports 192
and SSL 54, 118
functionality 30
Security and Accounts Manager 199
security example 278
server
administration options 142
authentication 151
terminology 20
server application
and DM synchronization 150
shutdown 134
starting 126
terminology 20
unable to start 356
server log file 161
serverconn.log 349
serverlog.txt 357
setupIISOLAP.bat 52
setupOlapDb 302
setupssdb.bat 314
setupTargetDb 301, 317
setupwin32.exe 43
Shared Services Provider (SSP) 400
shared_pool_size 317
Index
shutdown
client 133
in Windows 134
overview 125, 133
server application 134
skill 188
software
certified versions 419426
included for Windows 28
third-party 36, 287
Solaris
analytic applications unsupported
in 421
and Actuate 177
and Primavera 321
and third-party software 323
sort_area_size 317
sound cue 368
Spanish 176
SSL security 55
staffing by project report 184
staffing requests 168, 275
stakeholders 170, 237
Standard Import Connector 28, 424
start up
client 129
in Windows 126
overview 125, 126
server application 126
WorkSite MP 135, 336
strategicPlanning database 37
structure reports 187
Sun
JDK 426
support 21
supported platforms 420
synchronization
and notifications 346
automatic 150, 344
DM 344
failure 364
options 149, 150
overview 340
pollster 346
transfer rules 342
system options
expense policy 250
T
target database 37, 95
Task Access Policy 224237
tasks
codes 250
technical support 21
template privileges 236
termination privileges 232
third-party software
installation in Solaris 323
installation in Windows 36
RDBMS recommendations 36, 287
time and expenses
access role 249
administrators 232, 248
approvers 245
offline client 30
overview 243
printer-friendly 7073
reports 7073
third-party 173, 242, 252, 387
time reports
expense policy 250
ToolTip 368
Index
trace
desktop client 359
login 161
transfers between databases 95
troubleshooting 355
trusted root certificate 56
trusted sites 368
Trx 233
U
UI components 224
unposted transaction task privileges 233
update_generic_step 350
upgrade 29, 290
URL
for clients 61
USD 101
user groups and roles 170, 237
V
VBA 379
VeriSign 54
W
web administration 157, 159
web browser 141, 366
web client 54, 118, 366
caches, refreshing 158
web server
and reports 177
configuring 177
host 143
port 141
web services 28
web.config file 393
WebLogic
certified version 421
win/loss reports 184
work request privileges 237
workforce planning
and terminated resources 297, 313
privileges 228
WorkSite MP server
and database 37
configuration 331
installation 329
setupwin32.exe 330
starting 135, 336
workweek 214

Sysadmin Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Sysadmin Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

System Administrator Guide

For Release 9.0

Copyright 1998-2008 Primavera. All Rights Reserved.

System Administrator Guide

System Administrator Guide

4. Start up and Shutdown .................................................................. 125

6.7.1 ProjectLink Is Enabled.................................................... 165

System Administrator Guide

8.1.13 Pool Examples ............................................................. 218

8.8.3 Example of Access Roles............................................... 281

System Administrator Guide

B.1 Running Setup......................................................................... 330

D.8.3 Web Address or Link Fails ............................................. 367

Fully-qualified Domain Name in PWA URL ............................. 418

System Administrator Guide 11

12 System Administrator Guide

Administering and maintaining Primavera, including access control.

Help is available in Primavera. In the web client,

The Adobe Acrobat files (.PDF) provided with

Please visit us at www.primavera.com/

See Documentation Set on page 15.

System Administrator Guide 13

This is the default font of the manual.

Indicates a cross-reference to a section containing

Indicates text that appears in the graphical user

Indicates code as it appears on the screen or as you

Indicates clicking a menu (File) then clicking a

14 System Administrator Guide

High level description of material

Conceptual and procedural information

Data Mart Administration and

Provides information on Data Mart

Provides conceptual and procedural

System Administrator Guide

Describes administration procedures,

Describes Primavera configuration.

Detailed information regarding the

For optimal online image quality in Adobe Acrobat, Primavera recommends

System Administrator Guide 15

16 System Administrator Guide

System Administrator Guide17

18 System Administrator Guide

This chapter provides installation information about Primavera. It includes:

About Installation Recommendations

Delivery Manager Considerations

System Administrator Guide 19

20 System Administrator Guide

To access Primaveras extensive repository of product, implementation, and

System Administrator Guide 21

About Installation Recommendations

This document describes the configuration of a possible implementation of

22 System Administrator Guide

Primavera is designed to take full advantage of a networked computing

One instance of Microsoft Analysis Server (if using the analytic

One application server running BEA WebLogic. Note that an application

One or more Primavera server applications.

One or more WorkSite MP servers.

One Actuate implementation for reports.

For a small enterprise, an installation of all components on minimal hardware

One for application server (BEA WebLogic in Windows), the server

One for WorkSite MP.

System Administrator Guide 23

A desktop client for each user requiring administrative access to Primavera.

If implemented, an installation of ProjectLink for each user who needs to

Click Local PoliciesUser Rights Assignments.