Sysadmin Guide

System Administrator Guide

For Release 9.0

2 System Administrator Guide

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.0Copyright (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 sub-packages.

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 MERCHANT-ABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

System Administrator Guide 3

Table of Contents

1. Getting Started ................................................................................. 191.1 A Note on Terminology .............................................................. 201.2 Customer Support...................................................................... 211.3 About Installation Recommendations ........................................ 221.4 Example Installation................................................................... 231.5 Multiserver Environments .......................................................... 25

1.5.1 Web Servers..................................................................... 251.5.2 ProjectLink........................................................................ 25

1.6 Delivery Manager Considerations.............................................. 271.7 Included Software ...................................................................... 28

2. Installation Prerequisites................................................................. 312.1 Conventions............................................................................... 322.2 Defining a Network User in Windows......................................... 33

2.2.1 Creating pvuser ................................................................ 332.2.2 pvuser and MS Analysis Services .................................... 34

2.3 Third-party Software .................................................................. 362.3.1 RDBMS Prerequisites ...................................................... 362.3.2 MS Analysis Services....................................................... 382.3.3 BEA WebLogic ................................................................. 382.3.4 Actuate ............................................................................. 40

3. Installing Primavera ......................................................................... 433.1 About These Instructions ........................................................... 453.2 Preparing to Install ..................................................................... 463.3 Setting Up the Core Server Host ............................................... 47

3.3.1 Installing the Application Components ............................. 483.3.2 Running Delivery Manager Stored Procedures................ 513.3.3 Setting up the OLAP Virtual Directory in IIS for Portfolio


Manager.............................................................................. 513.4 Enabling SSL Support................................................................ 54

3.4.1 Installing the Certificate .................................................... 543.4.2 Configuring the Core Application...................................... 553.4.3 Configuring the Primavera Event Handler for SSL........... 563.4.4 Configuring the Analytic Applications for SSL .................. 57

3.5 Configuring the Web Client ........................................................ 603.5.1 Enabling ISAPI Filters....................................................... 603.5.2 Primavera URL................................................................. 613.5.3 Customizing Web Client Appearance............................... 623.5.4 Resume Generation ......................................................... 673.5.5 T&E Printer-Friendly ......................................................... 703.5.6 Adding Images to BIRT Reports....................................... 733.5.7 Changing the Logo in the T&E Expense Report Finder ... 743.5.8 Customizing the Quick Help in the T&E Expense Report. 743.5.9 Configuring the Expense Reports Template..................... 75

3.6 Installing Reports and Data Mart ............................................... 763.6.1 Running Setup.................................................................. 763.6.2 Editing DSNs .................................................................... 793.6.3 Reports Properties............................................................ 80

3.7 Enabling Capacity Planning ....................................................... 813.8 Installation Windows .................................................................. 83

3.8.1 Full Setup ......................................................................... 843.8.2 Server Setup................................................................... 1063.8.3 Reports Setup................................................................. 1083.8.4 Analytic Applications Setup ............................................ 1093.8.5 Data Mart Setup ............................................................. 111

3.9 Installing the Clients................................................................. 1123.9.1 Installing Primavera Desktop Clients.............................. 1123.9.2 Installing ProjectLink....................................................... 1143.9.3 Installing Offline Time and Expenses ............................. 1173.9.4 Importing a Certificate for SSL ....................................... 118

3.10 Post-Installation .................................................................... 1203.10.1 Disable Remembered Time and Expense Values........ 1203.10.2 Final Steps to Enable Portfolio Manager ...................... 120


4. Start up and Shutdown.................................................................. 1254.1 Start Up.................................................................................... 126

4.1.1 Starting the Primavera Server Application ..................... 1264.1.2 Starting the Primavera Client ......................................... 129

4.2 Shutdown................................................................................. 1334.2.1 Stopping the Primavera Client........................................ 1334.2.2 Stopping the Primavera Server Application.................... 1344.2.3 Stopping the WorkSite MP Server.................................. 135

4.3 Windows Log Files................................................................... 136

5. Using the Administration Tool ...................................................... 1395.1 Client Options .......................................................................... 1405.2 Server Options......................................................................... 142

5.2.1 Servers ........................................................................... 1435.2.2 Web Components........................................................... 143

5.3 Core Database Options ........................................................... 1445.3.1 MS SQL Server .............................................................. 1445.3.2 Oracle............................................................................. 146

5.4 DM Database Options ............................................................. 1485.4.1 DM Synchronization ....................................................... 150

5.5 Authentication Options............................................................. 1515.5.1 General Options ............................................................. 1525.5.2 Login............................................................................... 1535.5.3 Distinguished Name Resolution ..................................... 1545.5.4 Authentication and Login IDs ......................................... 154

6. Web Administration ....................................................................... 1576.1 Flush Web Client Caches ........................................................ 1586.2 Monitor Server ......................................................................... 1596.3 Active Web Sessions ............................................................... 1606.4 Login Auditing .......................................................................... 1616.5 ID Formats ............................................................................... 1636.6 Synchronize Users................................................................... 1646.7 Project Integration Options ...................................................... 165


6.7.1 ProjectLink Is Enabled.................................................... 1656.7.2 ProjectServerLink Is Enabled ......................................... 167

6.8 Staffing Request Options ......................................................... 1686.9 Administer Groups and Roles .................................................. 170

6.9.1 Creating and Assigning Groups and Roles .................... 1706.10 Third-party T&E Options ........................................................ 1736.11 Field-level Resource Profile Privileges .................................. 1746.12 Language Authorization ......................................................... 176

7. Primavera Reports ......................................................................... 1777.1 Reports and Rate Tables ......................................................... 178

7.1.1 Populating the Reporting Tables: MS SQL..................... 1797.1.2 Populating the Reporting Tables: Oracle........................ 180

7.2 Provided Reports ..................................................................... 1817.3 Custom Reports ....................................................................... 192

7.3.1 Requirements ................................................................. 1927.4 Report Properties..................................................................... 193

7.4.1 Specifying Delivery Manager Reports Printers............... 197

8. Access Control ............................................................................... 1998.1 Introduction to Access Control ................................................. 200

8.1.1 Pool Access.................................................................... 2008.1.2 Company Access............................................................ 2028.1.3 Analytic Applications Access Control ............................. 2028.1.4 Collaboration Access Control ......................................... 2028.1.5 MS Project Server Integration

through ProjectServerLink ................................................ 2028.1.6 Access Control for Client Downloads ............................. 2038.1.7 Pool Structure................................................................. 2048.1.8 Overview of Pools........................................................... 2068.1.9 Adding Domains and Pools ............................................ 2108.1.10 Customizing Pool Owners ............................................ 2128.1.11 Pools and Calendars .................................................... 2148.1.12 Recommendations for Pool Structure Configuration .... 217


8.1.13 Pool Examples ............................................................. 2188.2 Object Access Policies ............................................................ 221

8.2.1 Overview of OAPs .......................................................... 2228.2.2 Task Access Policies...................................................... 2248.2.3 Customizing an OAP ...................................................... 238

8.3 Time and Expenses Overview ................................................. 2428.3.1 Time and Expense Approval .......................................... 2438.3.2 Time and Expense Second-level Approval .................... 2438.3.3 Second-level Default Approver Setup ............................ 2448.3.4 Resource Pool Approvers .............................................. 2458.3.5 Time and Expenses Administrators................................ 2488.3.6 Third-party Time and Expenses ..................................... 252

8.4 Accounts .................................................................................. 2538.4.1 Types of Accounts.......................................................... 2548.4.2 Accounts and Access ..................................................... 2568.4.3 Adding Non-resource Accounts...................................... 2578.4.4 Updating Accounts ......................................................... 2598.4.5 Resetting Passwords...................................................... 2608.4.6 Removing Non-resource Accounts................................. 2618.4.7 Changing a Password .................................................... 262

8.5 Access Role Catalog ............................................................... 2638.5.1 Access Role Overview ................................................... 2638.5.2 Default Access Roles ..................................................... 2648.5.3 Conflicting Access Roles................................................ 2658.5.4 Configuring the Access Role Catalog............................. 2668.5.5 Assigning Access Roles ................................................. 268

8.6 Company Access..................................................................... 2708.7 Access Control Recommendations.......................................... 272

8.7.1 General Recommendations............................................ 2738.7.2 Access Role Recommendations .................................... 2748.7.3 Pool Structure Recommendations.................................. 2758.7.4 Time and Expenses Administrator Recommendations .. 276

8.8 Access Control Example.......................................................... 2788.8.1 Example Pool Structure.................................................. 2798.8.2 Example Organization Structure .................................... 280


8.8.3 Example of Access Roles............................................... 2818.8.4 Example OAPs ............................................................... 2838.8.5 Example Account Access ............................................... 285

9. RDBMS Recommendations ........................................................... 2879.1 Backup and Restore ................................................................ 2889.2 Upgrading Between Primavera Versions ................................. 2909.3 Microsoft SQL Server............................................................... 291

9.3.1 Database Sizing ............................................................. 2929.3.2 Enable Address Windowing Extensions

for SQL Server 2005 ......................................................... 2939.3.3 MS SQL Server Connectivity.......................................... 2949.3.4 Primavera-Provided Files ............................................... 2959.3.5 Creating the Core Schema Manually.............................. 2989.3.6 Creating the Delivery Manager Schema Manually ......... 2999.3.7 Creating the Data Mart Schemas Manually.................... 300

9.4 Oracle ...................................................................................... 3039.4.1 Build and Configuration Parameters............................... 3049.4.2 User Creation Script ....................................................... 3069.4.3 PVDB Schema................................................................ 3069.4.4 Tablespace Sizing .......................................................... 3079.4.5 Oracle Connectivity ........................................................ 3089.4.6 Connection Management ............................................... 3099.4.7 Primavera-Provided Files ............................................... 3099.4.8 Creating the Database Schemas.................................... 314

A. Actuate on Solaris ......................................................................... 321A.1 Conventions............................................................................. 322A.2 Installing Third-party Software................................................. 323

A.2.1 Actuate........................................................................... 323A.3 Configuring Reports................................................................. 325

A.3.1 Configuring Connectivity ................................................ 325A.3.2 Setting Report Properties............................................... 327A.3.3 Importing the Encyclopedia............................................ 327

B. WorkSite MP Server....................................................................... 329


B.1 Running Setup......................................................................... 330B.2 Configuring WorkSite MP ........................................................ 331B.3 Starting the WorkSite MP Server............................................. 336B.4 Initializing the Library............................................................... 337

C. Delivery Manager Administration................................................. 339C.1 Synchronization....................................................................... 340

C.1.1 Synchronization Basics.................................................. 341C.1.2 Transfer Rules ............................................................... 342C.1.3 Automatic Synchronization ............................................ 344C.1.4 Manual Synchronization ................................................ 347

C.2 Changing Financial Rules for Unrestricted Projects................ 350C.2.1 Overview........................................................................ 350C.2.2 Running update_generic_step....................................... 353C.2.3 Example Commands ..................................................... 354

D. Troubleshooting ............................................................................ 355D.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 ................................. 357D.2 Unable to Start the Desktop Client .......................................... 358

D.2.1 Unable to Start a Single Desktop Client ........................ 358D.2.2 Unable to Start All Desktop Clients................................ 358D.2.3 Desktop Client Trace Option.......................................... 359D.2.4 Configuring Desktop Client Connectivity ....................... 359

D.3 Primavera Client Fails to Connect........................................... 361D.4 Web Server Issues.................................................................. 362D.5 Performance Degradation ....................................................... 363

D.5.1 Project Bulk Update ....................................................... 363D.5.2 Data Mart ....................................................................... 363

D.6 Transfer Failure During Synchronization with DM................... 364D.7 iManage Fails to Connect to Its Database .............................. 365D.8 Web Client Issues ................................................................... 366

D.8.1 General Unexpected Behavior....................................... 366D.8.2 Flash Interface Issues.................................................... 366


D.8.3 Web Address or Link Fails ............................................. 367D.8.4 Prompted to Accept a Certificate ................................... 367D.8.5 Access Denied when Publishing a Portfolio................... 368D.8.6 Web Client Error: Editing Qualifications......................... 368D.8.7 Web Client ToolTip Uses Sound Cue ............................ 368

D.9 ProjectLink............................................................................... 370D.9.1 ProjectLink Fails to Connect .......................................... 370D.9.2 ProjectLink Fails to Download Daily Actual Hours ......... 370

D.10 TroubleShooting Portfolio Manager....................................... 372D.10.1 Message Logging......................................................... 372

D.11 Limiting the Number of Objects Displayed in Finders ........... 376D.12 Unable to Launch Client in Windows Vista............................ 378

E. ProjectLink API .............................................................................. 379E.1 Assumptions ............................................................................ 381E.2 COM Interfaces ....................................................................... 382E.3 Sample VBA Macros ............................................................... 389

F. ProjectServerLink and Microsoft Project Server......................... 391F.1 Installing MS Project Server Extensions for HTTP .................. 392F.2 Enabling MSPS Synchronization for Primavera via an Event

Handler .................................................................................... 394F.2.1 Installing the Event Handler ........................................... 394F.2.2 Viewing the Event Handler Log...................................... 398F.2.3 Configuring Primavera With SSL and

the Event Handler ............................................................. 398F.2.4 Configuring the Reporting Database Server in Case of

Connection Errors ............................................................. 398F.3 Setting up Impersonation for Actuals and ETC........................ 400

F.3.1 Configuring the MSPS Server for Impersonation ........... 400F.3.2 Configuring the Primavera Server for Impersonation ..... 402

F.4 Configuring Primavera and MSPS for SSL.............................. 404F.4.1 If Primavera uses SSL.................................................... 404F.4.2 If Microsoft Project Server uses SSL.............................. 404

F.5 Implementation Considerations ............................................... 406F.6 Configuring SharePoint to Support


Fully-qualified Domain Name in PWA URL ............................. 418

G. Certifications.................................................................................. 419G.1 Certified Software Platforms ................................................... 420G.2 Hardware Requirements ......................................................... 427

Preface


PrefaceWelcome to the Primavera System Administrator Guide. This guide details how to install and maintain Primavera.

Audience AssumptionsThis 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 InformationThe following table lists sources of information about Primavera:

See Documentation Set on page 15.

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.

Preface


Documentation ConventionsThis 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 SetIn addition to the online help, the following documentation is provided with Primavera:

For optimal online image quality in Adobe Acrobat, Primavera recommends setting the magnification to 200-250% when referring to graphics in these files.

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.

System Administrator Guide 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.

Preface


Contacting PrimaveraYou can contact Primavera by mail, telephone, or the World Wide Web:

PrimaveraThree Bala Plaza West, Suite 700Bala Cynwyd, PA 19004

Telephone: (610) 667-8600Fax: (610) 667-7894World Wide Web: http://www.primavera.com/customer/

support.asp

System Administrator Guide17

Section 1Primavera Installation

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 TerminologyThe 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 SupportTo 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 RecommendationsThis 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 InstallationPrimavera 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 process-intensive, 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 EnvironmentsSome 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 ServersEach 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 ProjectLinkIf 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 ConsiderationsPrimavera 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 SoftwareYou 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

Portfolio Management 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


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.

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.

Installation Prerequisites


2. Installation Prerequisites

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 SoftwareFor information about the certified third-party software, refer to Certifications on page 419.



2.1 ConventionsThe 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 WindowsIn 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 ServicesOn 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 window9. 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 GroupsGroupsSQLServer2005MSOLAPUser$[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. On the desktop of the MS Analysis Server host, click StartSettings

Control PanelAdministrative ToolsServices.2. 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 Third-party SoftwareInstall the prerequisite software in the following order: RDBMS Prerequisites MS Analysis Services BEA WebLogic ActuateUnless 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 PrerequisitesPrimavera 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 user-defined information in Portfolio Management and security settings for PM.

Collaboration librarya

a.The Collaboration library database version requirements are differentfrom other databases in the table. For information about certified data-base platforms, refer to Certifications on page 419. Collaboration support is provided only for customers upgrading fromPrimavera 8.9 or earlier. For information, refer to WorkSite MPServer on page 329.

Primavera The database that stores the workspace information used in collaboration.



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 MS Analysis ServicesPrimavera 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 WebLogicA 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.exeAfter 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. Select the Custom option.7. 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 FileWhen 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:

When you add the above line ensure that you replace with the correct path. For example, if you use the default install path, you need to add the following line in the Host tag:

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. Installing Primavera

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 InstructionsBecause 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 InstallBefore 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 HostBefore installing the Primavera software on the core server, the computer must first host the following:

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 ManagerInstalling the OLAP Virtual Directory is required only if implementing Portfolio Manager.

Third-party Software Supported Primavera Component

BEA WebLogic Server application, analytic applications

MS Analysis Services Client Components

Analytic applications (Portfolio Manager)

WorkSite MP Server Collaboration



3.3.1 Installing the Application ComponentsRun 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.

14. Supply the requested data in each field and click Next.The Data Mart Database window appears.

15. Supply the requested data in each field and click Next.The Analytic Applications Database window appears. This database (called StrategicPlanning) is the operational database used by PM and stores security access data for PM.

16. Supply the requested data in each field and click Next.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 ProceduresThis 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 directory1. 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]\tmpIf 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_FOLDERExample: 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.



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.

8. Restart IIS.



3.4 Enabling SSL SupportThe 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 CertificateIf 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 ApplicationYou 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 HostnameTo 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 CertificateAdd 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 SSLBecause 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. Stop the server application. For instructions, refer to Stopping the

Primavera Server Application on page 134.2. 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. Save the file.6. 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\WEB-INF\classes directory.

7. Locate the property that reads:singleSignOnProviderBaseURL=http://[hostname]/primavera/webwhere [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/StrategicPlanningwhere [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 ClientYou 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 ReportsThe 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 FiltersOn 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:

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

Component URL

Core web client http://[hostname]/primavera/web

Portfolio Management http://[hostname]/EA/StrategicPlanning/StrategicPlanning

Analytic Access Control http://[hostname]/EA/Configuration/Configuration



3.5.3 Customizing Web Client AppearanceYou can customize the appearance of the Primavera web client by:

Adding a Logo Changing the Custom Color Scheme Adding Links

Adding a LogoThe 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 SchemeThe 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:

3. 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.

4. 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 MistYou 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.

# Scheme 6: Custom Pattern.sss6.name: lbl.color.schemes.customsss6.bodyBG: #fbfeffsss6.mainHeader: #c2d6e7sss6.mainmenuBG: #c2d6e7sss6.tableBorder: #6c9fc6



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.



Figure 3-1 Web Client Color Property Usage

13

7

5

4

2

9

6

8



Adding LinksAt 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. Scroll to the bottom of the file.3. 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.comDelete 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 GenerationResume 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:

Infra.birt.report.format.resume = [format]3. Set the option to the desired format: html or pdf.4. Restart the application server.



Using a Secure ConnectionBIRT 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].rptdesignwhere

[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. 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. 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:



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. Open the AppServerConfig.properties file.2. 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. Restart the application server.

Using a

Documents

Sysadmin Guide