Primavera P6

Administrators Guide
Version 6.1
Copyright 1999 - 2007 Primavera. All rights reserved. While reasonable efforts have been made to ensure the accuracy of this document, Primavera assumes no liability resulting from any omission or inaccuracies in this document or from use of the information obtained herein. Primavera reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Primavera does not assume any liability arising out of the application or use of any product described herein; neither does it convey license under its patent rights or the rights of others. Please send your comments to: Primavera Systems, Inc. Three Bala Plaza West Bala Cynwyd, PA 19004 Telephone: 1-610-667-8600 FAX: 1-610-667-7894 World Wide Web site: http://www.primavera.com Computer Software Copyrights: The Primavera software products described in this document may not be copied, reproduced, modified, or distributed in any manner without Primavera's express written permission. Use and Disclosure Restrictions: The software described in this document is the property of Primavera Systems. It is furnished under a license agreement and may be used and/or disclosed only in accordance with the terms of the agreement. U.S. Government Restricted Rights: If the Software is acquired for or on behalf of the United States of America, its agencies and/or instrumentalities (U.S. Government), it is provided with RESTRICTED RIGHTS. The Software and accompanying documentation are commercial computer software and commercial computer software documentation, respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and restricted computer software pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, reproduction, release, performance, display or disclosure of the Software and accompanying documentation by the U.S. Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R. 12.212, 52.22714 (Alternate III), 52.227-19, 227.7202, and 1852.227-86, as applicable. Trademarks: Primavera, the Primavera sundial logo, P3, P3e, P3e/c, Primavera Enterprise, Primavera Evolve, Primavera Expedition, Primavera Project Planner, Primavera TeamPlay, Primavision, PrimeContract, and SureTrak are either trademarks, registered trademarks, or service marks of Primavera in the United States and/or in other countries. All other trademarks mentioned herein are the property of their respective owners. Certain products included in the software require the following disclosures: This product includes software developed by the JDOM Project (http://www.jdom.org/). Copyright (c) 2002-2006 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 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.

Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or promote products derived from this

software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. *****

The Apache Software License, Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2Redistributions 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. 3The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ***** Copyright 1994-2006 Sun Microsystems, Inc. All Rights Reserved. Sun, Sun Microsystems, the Sun Logo, Java, Java runtime environment, J2SE, and JavaOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistribution 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. Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived from this software without specific prior written permission. This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. ***** Portions copyright (c) Macromedia, Inc. All rights reserved. ***** Portions (c) Microsoft Corporation. All rights reserved. ***** The contents of iText are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use iText 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. iText Library - Copyright (C) 1999-2008 by Bruno Lowagie and Paulo Soares. All Rights Reserved. Alternatively, the contents of iText may be used under the terms of the GNU Library General Public License (the "LGPL License"), in which case the provisions of LGPL License are applicable instead of those above. If you wish to allow use of your version of iText only under the terms of the LGPL License and not to allow others to use your version of iText under the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the LGPL License. If you do not delete the provisions above, a recipient may use your version of iText under

either the MPL or the LGPL License. Sun, Sun Microsystems, the Sun Logo, Java, Java runtime environment, J2SE, and JavaOS are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. ILOG, the ILOG Logo or the ILOG Mark is a trademark of ILOG S.A. Printed in the United States of America

Preface.................................................................................................xi
Using the Administrators Guide........................................................................xii Primavera Documentation..................................................................................xiv Where to Get Support........................................................................................xvi

Part 1: Before You Begin

Installation Process Overview.............................................................3
What is the Primavera Solution?...........................................................................4 Who Should Help with the Installation?...............................................................8 Installation Process Phases.................................................................................10

Planning Your Implementation........................................................11

Which Components Do I Need?.........................................................................12 Client and Server Requirements.........................................................................16 Project Management Database Server Sizing Guide..........................................21 Methodology Management Database Server Sizing Guide................................22 Practical Product Limits......................................................................................23

Part 2: Database Installation and Configuration

Automatic Database Install...............................................................27
Overview.............................................................................................................28 Running the Database Wizard.............................................................................29 Automatically Installing an Oracle Database and Loading Application Data....30 Automatically Installing a SQL Server Database and Loading Application Data..........................................................................35

Configuring the Server Databases....................................................39

Overview.............................................................................................................40 Creating the Database Structure for Oracle........................................................41 Creating the Database Structures for MS SQL Server........................................46 Installing the Application Data (Oracle and Microsoft SQL Server).................52 Background Processes and Clean Up in P6........................................................58 Configuring the RDBMS Scheduler...................................................................59 Setting Table........................................................................................................61 Reading and Writing Setting Values...................................................................62 Tracking Background Job Execution..................................................................64 SYMON (System Monitor).................................................................................66 DAMON (Data Monitor)....................................................................................68 Improving Oracle Database Performance...........................................................80 Native Database Auditing...................................................................................81

Part 3: Server Installation and Configuration

Configuring the Group Server for Timesheets................................91 Uninstalling a Previous Version of the Group Server.........................................92 Installing the Group Server and Timesheets Web Site........................................93 Configuring Group Server/Timesheets for LDAP Authentication....................104 Configuring Group Server/Timesheets for Single Sign- On Authentication....106 Configuring Group Server Settings...................................................................108 Setting up Java Web Start for Timesheets.........................................................112 Creating Multiple Instances of Group Server...................................................115 Group Server Configuration Settings................................................................118 Installing P6 Web Access.................................................................125 Upgrading to P6 Web Access............................................................................126 Uninstalling Previous Versions.........................................................................127 Installing the Application Server for P6 Web Access.......................................128 Installation Process for P6 Web Access............................................................130 Configuring and Deploying the Application Server for P6 Web Access..........133 Starting the Server for P6 Web Access.............................................................145 Stopping the Server for P6 Web Access............................................................146 Accessing P6 Web Access from Client Browsers.............................................147 Configuration Settings on Client Browsers.......................................................148 Changing Database Configuration Settings......................................................152 Using the Administration Application..............................................................153 Starting the Administration Application...........................................................154 Reviewing and Modifying Configurations for P6 Web Access........................155 Configuration Settings for P6 Web Access.......................................................163 Implementing Application Server Plug-Ins......................................................186 Collaboration Setup.........................................................................187 Migrating WorkSite MP Server 3.1 HFB12 to 5.0 Patch 1...............................188 Migrating WorkSite MP Server 4.1 HFB7 to 5.0 Patch 1.................................202 Installing the Collaboration Server for the First Time......................................210 Creating a Collaboration Configuration for the First Time...............................215 Configuring P6 Web Access for Collaboration.................................................247 Distributed Job Service Overview....................................................................252 Installing the Distributed Job Service...............................................................253 Disabling the Windows Firewall.......................................................................254 Configure Access to the Distributed Job Service..............................................255 Configure DCOM for the Distributed Job Service...........................................256 Configure the Controller and DJS servers........................................................267 Job Service Registry Settings............................................................................270

Part 4:

Primavera Client Installation and Configuration

Installing Client Modules and Additional Components...............279 Installing Database Client Software..................................................................280 Uninstalling Previous Versions.........................................................................281 Running the Setup Wizard................................................................................282 Installing Client Modules..................................................................................285 Installing the Job Service and Distributed Job Service.....................................287 Installing the Software Development Kit..........................................................294 Installing ProjectLink........................................................................................297 Installing and/or Upgrading the Stand-Alone Version......................................299 Automatic Database Upgrade.........................................................301 Upgrade Process Overview...............................................................................302 Upgrading an Oracle Database to P6................................................................304 Upgrading a Microsoft SQL Server Database to P6.........................................306 Creating and Running an Unattended Setup................................309 Creating Unattended Setup Files......................................................................310 Running an Unattended Setup..........................................................................314 Changing Database Configuration Settings..................................317 Changing Database Connection Settings..........................................................318 Performing Administrative Tasks.....................................................................320 Configuring Authentication Modes................................................323 Authentication in Primavera.............................................................................324 Process Overview..............................................................................................326 Choosing an Authentication Scheme................................................................327 Login Procedures and Authentication...............................................................338

Part 5: Primavera Application Administration

Administering Users and Security..................................................341 Understanding Security in Primavera...............................................................342 Process Overview..............................................................................................351 Defining Global Profiles...................................................................................353 Defining Project Profiles...................................................................................361 Adding Users in the Project Management Module...........................................368 Assigning OBS Elements to the EPS................................................................384 Defining User Access to Resources..................................................................387 Defining User Access to P6 Web Access Functionality...................................391 Setting Security in the Methodology Management Module.............................393 Defining Administrative Preferences and Categories in Project Management.......................................401 Defining Default Settings..................................................................................402 Defining Standard Categories and Values.........................................................415

Defining Currencies..........................................................................................421 Defining Administrative Preferences and Categories in Methodology Management.............................425 Defining Default Settings..................................................................................426 Defining Standard Categories and Values.........................................................430 Defining Currencies..........................................................................................435 Implementing Timesheets...............................................................439 Implementation Overview.................................................................................440 Setting Timesheet Preferences..........................................................................442 Configuring Resources to Use Timesheets.......................................................447 Creating Timesheets for Timesheets Users.......................................................450 Setting Project-Specific Timesheets Preferences..............................................452 Using Overhead Codes......................................................................................453 Running Timesheets Web Browser Version and Java Web Start Version.........454 Configure Access to Timesheet Approval.........................................................457 Defining Financial Periods..............................................................461 Defining Financial Periods in the Project Management Module......................462

: Appendices
Appendix A: Running Primavera Databases in One Oracle Instance..................................................................467 Process Overview..............................................................................................468 Running MMDB and PMDB in a Single Oracle Instance................................469 Upgrading a Single Instance Database from Primavera 5.0 or 6.0 to P6 version 6.1...................................................482 Appendix B: Undoing Changes in the Project Management Database...............................................487 Understanding Undo.........................................................................................488 Configuring Safe Deletes..................................................................................489 Index..................................................................................................491 Primavera provides comprehensive, multiproject planning and control software, built on Microsoft SQL Server and Oracle databases for enterprise-wide project management scalability. Smaller multiuser or stand-alone installations can use Microsoft SQL Server 2005 Express. The Primavera solution includes the Project Management module, which can stand alone for project and resource management or be used with companion products. Timesheets enables Web-based team communication and time keeping; the Methodology Management module stores methodologies as templates for new projects; P6 Web Access provides project analysis across the enterprise and allows users to access project management data via the Internet. In this preface:
Using the Administrators Guide Primavera Documentation

Where to Get Support

Preface
Using the Administrators Guide
This book is a step-by-step guide to installing and configuring Primavera software components. Read Part 1 to become familiar with the overall process of installing Primavera software components, then read the chapters in the rest of the book that discuss the components you plan to install and configure. This manual is organized as follows: Part 1: Before You Begin Provides an overview of Primavera software components, discusses how to plan an implementation for your organization, and offers an overview of the process of installing and configuring Primavera software components. Part 2: Database Installation and Configuration Provides steps for using a wizard to automate the process of creating project management and methodology management databases on either Oracle or Microsoft SQL Server/SQL Server Express and loading application data into the databases. This part also details how to manually create a database. Part 3: Server Installation and Configuration Provides steps for manually installing and configuring the server-based components of the Primavera solution, including the following:
Group P6

Server and Timesheets files on a Web server

Web Access (formerly known as Primaveras Web application or myPrimavera) Collaboration Server for P6 Web Access Job Service

The

Distributed

Part 4: Primavera Client Installation and Configuration Describes how to install and configure Primavera client modules. Part 4 explains how to:
Install Install Use

the Project Management and Methodology Management modules, as well as Timesheets additional components such as the (Distributed) Job Service, Software Development Kit, and ProjectLink

a wizard to automatically upgrade from previous versions of Primavera and run an unattended setup

Create

Configure

module connectivity to the project management database, user passwords, database logins, and module licensing using the Database Configuration wizard
Set

up authentication

Part 5: Primavera Application Administration Describes how to customize Primavera modules, once installed. Specifically, Part 5 covers how to:
Set

up users and configure security preferences and categories for the Project Management and Methodology Management modules the Project Management module to allow Timesheets users to record their time in the project management access to the Timesheet Approval application

Modify

Configure

database
Configure Create

financial periods in the financial periods dictionary

Appendices

Provides steps for running your project management and methodology management databases in a single Oracle instance and describes how to undo changes to the project management database.

Primavera Documentation
Primavera documentation consists of printed and online manuals. You can access online documentation by inserting CD 3 in your workstations CD drive. In the \Documentation\<language> folder on the CD-ROM, open the appropriate industryspecific documentation folder, then double-click the applicable PDF file to view the information using Adobe Acrobat Reader (also available on CD 3). The following table describes each manual and lists the recommended readers by role. Primavera roles are described in Installation Process Overview on page 3 of this manual Title Description
Primavera Administrators Guide This guide explains how to set up the Primavera server, database, and components; it also provides an overview of all the components in the Primavera solution. The guide describes the workflow required to administer the Project Management module, including setting up security and configuring global preferences. The Project Management module network administrator/database administrator and project controls coordinator should read this guide. This guide explains how to plan, set up, and manage projects in an enterprise system. If you are new to the Project Management module, start with this guide to learn how to use the software effectively to plan and manage projects. When you need more detail, refer to the Project Management Help. The project controls coordinator, program manager, project manager, resource/cost manager, and team leader should read this guide. This guide explains how to establish methodologies, or project templates, using the Methodology Management module. Methodologies enable your organization to gather its best practices and reuse them to create custom project plans in the Project Management module. If you are new to the Methodology Management module, start with this guide to learn how to use the software to create base, plug-in, and activity library methodologies. When you need more detail, refer to the Methodology Management Help. The project controls coordinator, program manager, project manager, resource/cost manager, and team leader should read this guide. P6 Web Access Help describes how to create and manage projects, group projects into portfolios, review resource allocation and requirements, and evaluate budget, performance and ROI for project portfolios. The operations executive, project controls coordinator, program manager, project manager, resource/cost manager, and team leader should read this Help. Timesheets Web-based Help describes how to use Timesheets to enter and update time spent on assignments. Team members should read this Help. Describes how to use ProjectLink to enable Microsoft Project (MSP) users to work in the MSP environment while being connected to Primavera's enterprise features. MSP users can learn how to open/save projects from/to the Project Management module database from within the MSP application and how to invoke Primavera's resource management within the MSP environment. Team members that use MSP for daily project maintenance in organizations that use Primavera for enterprise-wide project planning and control should read this help. This guide explains how to install and configure the Integration API (Application Programming Interface), which allows direct access to the Project Management module via Java. Those creating client code in Java and needing direct access to the project management database should read this guide. This guide is available on the Integration API CD.

Project Management Reference Manual

Methodology Management Reference Manual

P6 Web Access Help

Timesheets Web-based Help ProjectLink Help

Integration API Administrators Guide

Software Development Kit (SDK) Web-based documentation

This documentation describes how to use the SDK to connect to the project management database. The tables, fields, and stored procedures that you can access through the SDK are described. Examples are also provided to show how you can use the SDK to perform several basic tasks, such as creating a new project or assigning a resource to a project activity. The Project Management network administrator/database administrator and project controls coordinator should read this documentation, which is available in your \Program Files\Common Files\Primavera Common\PMSDK\Doc folder. Double-click the INDEX.HTML file to open the Table of Contents page.

Distributing Information to the Team

The online documentation can be copied to a network drive for access by project participants. Each team member can then print only those portions that specifically relate to his or her role in the enterprise.
The documentation assumes a standard setup of the product, with full access rights to all features and functions.

Where to Get Support

If you have a question about using Primavera products that you or your network administrator cannot resolve with information in the documentation or Help, contact Primavera Customer Support at the times and locations listed below. Please provide your Primavera product serial number when contacting Primavera. Each interaction is logged to help Primavera resolve your questions quickly.

Office Bala Cynwyd, Pennsylvan ia, USA London, England, UK

Time Zone ET

Hours 8:008:00 (MonFri) 9:002:00 (Sat) 8:306:30 (Mon Thur) 8:305:30 (Fri) 8:005:00 (MonFri)

Telephone +1-610-668-3030

FAX +1-610-667-0652

E-mail Address* support@primavera.com

GMT

+44-20-85635555

+44-20-85635543

support@primavera.com

Hong Kong

GMT +8

+852-2111-8299

+852-2111-9477

support@primavera.com

*Primavera's Web site at http://www.primavera.com/customer/index.asp provides support and product information, such as knowledgebases, file downloads, user group and newsgroup information, and a product enhancement request form.

In the United States, Primavera periodically and randomly monitors technical support calls to ensure that you receive the highest quality support.
All Primavera products are backed by comprehensive support and training. To request product literature in the United States, contact your local dealer, call Primavera at 1-610-667-8600, or send your request via e-mail to info@primavera.com. In the United Kingdom, call 44-20-8563-5500 or e-mail your request to intlinfo@primavera.com.

Installation Process Overview

Planning Your Implementation In this part:

Part

Before You Begin

his part discusses how to plan and prepare for installing Primavera components. Begin by reading

Installation Process Overview, which describes the Primavera components, summarizes the skills needed to install these products, and explains each phase in the installation process. Planning Your Implementation demonstrates how to identify the components your organization requires and helps you ensure that you have the hardware and software needed to support that implementation. This chapter describes the components that make up the Primavera solution and reviews the installation and configuration process. In this chapter:
What is the Primavera Solution? Who Should Help with the Installation? Installation Process Phases

Installation Process Overview

What is the Primavera Solution?
Primavera provides a set of integrated components that meet the project management needs of different areas of an organization. It uses standard Windows interfaces, Web-enabled technology, small multiuser or stand-alone (SQL Server Express) databases, or network-based (Oracle and Microsoft SQL Server) databases. This installation guide assumes you are installing Primavera software components on a client/server network, which requires the installation and configuration of both client software and server-based components. It also provides information on stand-alone installations.
Primavera uses DBExpress as the standard interface between its components and the project management and methodology management databases. DBExpress is automatically installed when you install the Project Management

module. Some additional components, such as the Group Server and Job Service, also install DBExpress to connect to the databases.

Client components The Primavera solution consists of the following client modules:
Project

Management Project Management is a module that enables users to plan and control a large number of projects. Project data is stored in a central project management database. Either Oracle or Microsoft SQL Server can be used as the relational database management system in a large networked configuration. For smaller multiuser or standalone implementations, you can use Microsoft SQL Server 2005 Express as the database. Project Management also provides centralized resource management, including resource timesheet approval and the ability to communicate with project resources through the Timesheets module, a Web-based timesheet management application.
Methodology

Management Methodology Management is a module for authoring and storing methodologies, or project plan templates. Methodology Management enables your organization to gather its best practices and store them in a central methodology management database.
Timesheets

Timesheets is a Web-based interproject communication and timekeeping system. Team members use Timesheets to enter up-to-the-minute information about their assignments across projects and record time against their workload. Server components Primavera may require the installation and configuration of the following server-based components:
Relational

Database Management System (RDBMS) Project data and project methodologies are each stored in separate central databases. These two databases should be maintained on a database server running Oracle, Microsoft SQL Server, or SQL Server Express. (You also need to install the client software for the RDBMS on each computer needing network access to the database server. If you are running Microsoft SQL Server or SQL Server Express, the necessary software is installed for you automatically when you install Primaveras Project Management module.)
Group

Server If your implementation of Primavera includes the Timesheets client module, you must install the Group Server. This component is a Windows 2003 service that runs on your Web server and allows clients to download Timesheets from that server using their Web browsers. It further acts as an intermediary between the Timesheets client and the project management database. Additional components Your Primavera implementation may require the installation of one or more optional components. These additional components expand the functionality of the Primavera solution:
P6

Web Access P6 Web Access (formerly known as Primaveras Web application or myPrimavera) provides browser-based access to project, portfolio, and resource data across the enterprise. Every P6 Web Access user can customize dashboards to create an individualized and focused view of the specific projects and categories of project data that are most relevant to their role in managing projects and resources. Project Workspaces and Workgroups extend the model of customizable, focused data views by enabling designated project team members to create a uniform team view of data that relates to one specific project or to a subset of activities within a project. P6 Web Access provides access to a wide range of data views and features that enable users to manage their projects from initial concept review and approval through to completion.
The

P6 Web Access Collaboration Server The collaboration infrastructure of P6 Web Access provides enhanced capabilities to connect all team members, at all levels, to all shared work necessary for the successful completion of a project. Features include full discussion threads, improved issues management, team and project event calendars, comprehensive file management, and comprehensive e-mail integration.
(Distributed)

Job Service The Job Service is a Windows 2003 service that runs defined jobs on project data at preconfigured intervals. Users create jobs in the Project Management module. The job details are stored in the central project management database. The Job Service periodically reads the database and performs jobs as directed. This service must run on a server that has a constant connection to the database server. The Distributed Job Service is an extension of the Job Service that enables a controller machine to manage

multiple servers running job services.

ProjectLink

ProjectLink is a plug-in that enables Microsoft Project (MSP) users to work in the MSP environment while being connected to Primavera's enterprise features. The functionality enables MSP users to open/save projects from/to the Project Management module database from within the MSP application. Moreover, MSP users have the ability to invoke Primavera's resource management within the MSP environment. ProjectLink benefits organizations that use MSP for daily project maintenance but require some users to have the enterprise capabilities available within Primavera applications.
Software

Development Kit (SDK) The SDK enables you to integrate the data in the project management database with external databases and applications. It provides access to the schema and to business logic. The SDK supports the Open Database Connectivity (ODBC) standard and ODBC-compliant interfaces, such as OLE DB, for connecting to the project management database. The SDK may be installed on any computer that needs to integrate with the Primavera database.
The Integration API (Application Programming Interface) can also be used to connect directly to the project management database. This tool requires the ability to write client code in Java. For further information, see the Integration API Administrators Guide.

The following figure illustrates the relationship between Primavera components.

For details on the configuration requirements of each component, see Planning Your Implementation on page 11.

You are not required to install the server-based components as shown here. For example, P6 Web Access and the collaboration server can be installed on the same server (if necessary), and Job Services can run on any computer with a constant connection to the project database.

Who Should Help with the Installation?

The talents of several different types of employees may be required to install and configure Primavera components in your organization. The following section describes the basic roles and the responsibilities typically given to those roles during the installation process. Roles may vary or overlap depending on the structure of your organization. Network administrators Network administrators configure an enterprises network environment (local- and wide-area networks) for optimal performance with Primavera components. They install and maintain the server and client components in the Primavera solution. They manage user access to project data and develop and maintain a comprehensive security policy to ensure that project and methodology data is protected from unauthorized access, theft, or damage. Network administrators ensure that the hardware and software supporting Primavera function reliably by
Setting

up and maintaining the network to ensure reliable connections and the fastest possible data transfer and maintaining accurate lists of network resources and users so that each has a unique network identity

Creating

Database administrators Database administrators (DBAs) are responsible for setting up, managing, and assigning access rights for the Primavera databases. They set and oversee rules governing the use of corporate databases, maintain data integrity, and set interoperability standards. Database administrators ensure reliable access to the Primavera databases by
Installing, Creating

configuring, and upgrading database server software and related products as required

and implementing the databases and maintaining database security, including creating and maintaining users, roles, and privileges for

Implementing

the databases
Monitoring Planning

database performance and tuning as needed

for growth and changes and establishing and maintaining backup and recovery policies and procedures

Project controls coordinator Project control coordinators are responsible for ensuring that the Project Management module is implemented properly and that it operates smoothly. They play a key role during implementation by
Working

with senior management to establish the enterprise project structure, resource hierarchy, and organizational breakdown structure (OBS); set up basic calendars; and define enterprise-wide codes in the Project Management module
Working

with the network administrator to create user accounts and user groups for the Project Management module security rights to Primavera users in the Project Management module

Assigning Working

with the Human Resources (HR) department to keep the resource hierarchy in the Project Management module up-to-date and complete, possibly through integration of an HR module from an enterprise resource planning (ERP) system Program and project managers In some cases, program and project managers may also become involved in the initial configuration of the Primavera solution, though they are not normally involved in the installation. They are responsible for managing one or more projects and use the Project Management module for
Adding

projects to the project management database resources across projects

Prioritizing Planning

and managing projects

Installation Process Phases

The network administrator, database administrator, and project controls coordinator should work together to ensure that the Primavera solution is successfully installed for your organization. These roles may be played by teams of people or by a few people sharing responsibilities. Primavera recommends installing and configuring the Primavera solution in phases. Each phase of the installation process is explained below.
The planning phase is covered in this part of this guide.

Phase 1: Plan your Primavera configuration Before you begin the installation, decide how your organization will implement the Primavera solution. Identify the servers and network hardware you will need to support the implementation. Install and configure the third-party database server software (Oracle or Microsoft SQL Server), if necessary. Perform any upgrade procedures as needed to roll projects from previous versions into the new version. If you simply will be installing a stand-alone version, refer to Installing and/or Upgrading the Stand-Alone Version on page 299.
Automatic and manual configuration of the databases is covered in Part 2 of this guide. Server configuration is covered in Part 3.

Phase 2: Configure your Primavera servers Once you have set up your network and prepared your servers, you can begin to configure the servers. Start by setting up the project management and methodology management databases on the database server. You can choose an automated or a manual method to complete this process. If you are using SQL Server Express, you should follow the automated process.
The client module configuration phase is covered in Part 4 of this guide.

Phase 3: Configure your Primavera client modules Once your servers are configured and the databases are installed, you can begin to install the Primavera client modules on your client workstations according to your implementation plan. You can then install and configure additional components

as needed for your implementation.

Read this chapter when you are ready to plan your Primavera implementation. For more detailed information and assistance, please consult with Primavera Customer Support (if you have questions about installation) or Professional Services (if you want Primavera to assist you with your implementation.) In this chapter:
Which Components Do I Need? Client and Server Requirements Project Management Database Server Sizing Guide Methodology Management Database Server Sizing Guide Practical Product Limits

Planning Your Implementation

Which Components Do I Need?
When planning your Primavera implementation, you will first need to know what client modules and server components you will need to install and configure, and where those modules and components need to be installed. The following is a set of questions that you will want to answer before you begin. Which relational database management system (RDBMS) will we use on our database server? You can use either Oracle or Microsoft SQL Server on your database server for enterprise installations. For smaller implementations, you can use Microsoft SQL Server 2005 Express with Advanced Services. Which workstations will require the Project Management module? Which will require Methodology Management? All Project Management and Methodology Management users will need access to the database server. If using Oracle as the RDBMS, you will need to install the Oracle client software on each computer that runs these client modules. If using SQL Server as the RDBMS, Primavera automatically installs the required SQL Server files when you install the Project Management module. Do we want our administrators to install the Project Management and Methodology Management modules using standardized preconfigured settings? If you want all of your client modules to be configured identically, your administrators can run an unattended setup for each module based on a standard configuration. You can create one or more sets of unattended setup files and share them on a network server. Will our Project Management module users need to automatically run jobs (such as scheduling or summarizing) on project data? If your Project Management users will need to run jobs, you will need to install the Job Service. For non-distributed jobs, install the Job Service on a server that has constant access to the database server. For distributed jobs, install the Distributed Job Service on multiple servers operated by a Controller server. Additionally, the Primavera Web Scheduler is available, but disabled by default. The Web Scheduler can be enabled via the Administrator Application of P6 Web Access. Do we need to integrate our project data with other enterprise systems? If you need to integrate your project data with other enterprise systems, such as Accounting or Human Resources applications, you will need to install either the Integration API (Application Programming Interface) or the Software Development Kit (SDK) on computers that require access to the data. The Integration API makes data accessible through JDBC and requires knowledge of Java programming. The SDK makes project data available to external applications through Open Database Connectivity (ODBC) interfaces, such as OLE DB.

Do some users require the ability to manage their projects in Microsoft Project while utilizing Primavera to manage enterprise data? Your enterprise may currently use Microsoft Project to manage projects. To enable users to continue to use MSP to manage projects while integrating with Primaveras enterprise-level functionality, you will need to install Primavera ProjectLink. Will our team members use Primavera Timesheets to submit timesheets to the project/resource managers? If so, will we require that resource and/or project managers review and approve resource timesheets? If team members will use Timesheets, you will need to install the Group Server and the Timesheets files on your Web server. If you require that resource and/or project managers review and approve resource timesheets, you must install P6 Web Access. The Timesheet Approval application, which is installed on the P6 Web Access application server when you install P6 Web Access, enables timesheet approval managers to review, approve, and reject timesheets, communicate with Timesheets resources, and run timesheet reports. Once installed, you can configure access to Timesheet Approval from P6 Web Access and the Project Management module, or you can make it available to approval managers as a stand-alone application.

If we use Timesheets, which version of Timesheets should we use?

Timesheets is a three-tier client/server module, consisting of the Timesheets client on the front end, the database server that contains your projects on the back end, and the Group Server in the middle, providing a link between Timesheets clients and the database. Primavera facilitates project communication among team members across the enterprise by providing two types of interfaces for Timesheets: a Web Browser version and a Java Web Start version. The Java Web Start version is optional. The differences between the two interfaces are described below. Web Browser version Timesheets Web Browser version enables users to access their timesheet data across the Internet as a Java applet. To run the Web Browser version, users simply visit a specified URL, and the Java applet automatically downloads to their computers; the applet can then be run in their Web browsers. When many users will need to use Timesheets, running it as a Java applet can provide great administration time savingsno client-side installation is required, and software updates are automatically distributed. The primary disadvantage may be the initial download time for the applet, which can take up to 20 minutes over a slow modem connection. Java Web Start version Timesheets Java Web Start version performs the same function as the Web Browser version, but this version runs as a Java application. Java Web Start provides a secure and platform-independent deployment of Timesheets, using the Java Network Launching Protocol (JNLP) technology. Java Web Start also ensures that users always launch the most recent version of Timesheets under the correct JRE version, even if there is more than one JRE version present at the same time. Java Web Start automatically downloads the most recent version of Timesheets to the users computer, so users never have to upgrade manually. Do we want to provide Web access to project data for performance of project management tasks? P6 Web Access provides access to project data via a Web browser. It supports the creation and management of projects within the enterprise, provides resource availability and allocation details, and provides project portfolio reporting features to support strategic decision-making. The following table lists each client component and the corresponding server-based components that it requires.
RDBMS Group Server P6 Web Access Primave ra Job Service Collaborati on

Project Management Methodology Management Timesheets P6 Web Access User

1 1

4 3 5

1If using Oracle as the RDBMS, these modules require the Oracle client software to be installed on the client computer. 2The Job Service is an optional component for the Project Management module. 3The Group Server is an optional component for P6 Web Access; it is required if you are using the Timesheets functionality of P6 Web Access. 4P6 Web Access is an optional component for Timesheets and is only required if resource timesheets must be reviewed and approved. 5Collaboration is an optional component for P6 Web Access. It can serve as an aid in document management, workflows, and discussion threads.

Client and Server Requirements

After determining your Primavera implementation plan, ensure that your hardware and software can support it.
The following tables summarize configurations that have been tested with Primavera. For the full list of system requirements, versions, and tested configurations, refer to the testedcfg.htm file in the \Documentation\<language>\Technical Documentation\Tested Configurations folder on CD 3.

Supported Platforms for Primavera Client modules (Project Management, Methodology Management, P6 Web Access)
Microsoft Microsoft Citrix

Windows XP Professional (SP2) Windows Vista Business Edition

Presentation Server 4

The Integration API (Application Programming Interface) and Software Development Kit (SDK) can be installed on any Windows 2003 (SP2), XP (SP2) or Vista Business Edition computer. System requirements will vary depending on the requirements of the module that uses the API or SDK to integrate with Primavera databases. Minimum Client Configurations For clients running the Project Management and Methodology Management modules
Oracle Oracle SQL 1 1 If

10.2 full XE Client for Vista

Server 2005 sp2 full

x 2.8 GHz or higher Intel processor GB of available RAM or more

installing standalone modules, 575 MB of available hard-disk space for supporting software, including .NET and SQL Server 2005 Express with Advanced Services (SP2). If upgrading from a prior release, an additional 40MB of available hard-disk space per module.
If If

installing the Project Management module, 185 MB of additional hard-disk space installing the Methodology Management module, 45 MB of additional hard-disk space Internet Explorer 6 (SP2) or 7

Microsoft

TCP/IP

network protocol

For clients running Timesheets Web Browser version

Microsoft Microsoft Ubuntu

Windows XP Professional (SP2) Windows Vista Business Edition

Linux 7.04 Internet Explorer 6 (SP2) or 7 or Firefox 2.0

Microsoft Sun

JRE (appropriate version will be installed automatically with Timesheets) network protocol software:

TCP/IP

Optional

Java Access Bridge 2.01 (for 508 accessibility.)

The

Timesheets application has been tested with the following assistive technologies: JAWS for Windows screen reading software, version 7.0 ZoomText Magnifier 9.0

For clients running Timesheets Java Web Start version

Microsoft Sun

Internet Explorer 6 (SP2) or 7 or Firefox 2.0

JRE (appropriate version will be installed automatically with Timesheets) network protocol software:

TCP/IP

Optional

Java Access Bridge 2.01 (for 508 accessibility.)

The

Timesheets application has been tested with the following assistive technologies: JAWS for Windows screen reading software, version 7.0 ZoomText Magnifier 9.0

For clients accessing P6 Web Access

1 1

x 2.8 GHz or higher Intel processor (recommended) GB of available RAM or more (recommended) MB of available hard-disk space network protocol Internet Explorer 6 (SP2) or 7

25

TCP/IP

Microsoft Sun

JRE (the required version is automatically installed with P6 Web Access) Supported Configurations for Servers

For the database server

Oracle

10.2.0.2 or higher on Windows 2003 Server (SP2), HP-UX 11i v2, Solaris 10 (SPARC), or Red Hat Enterprise Linux 4.0
Microsoft Microsoft 4

SQL Server 2005 (SP2) on Windows 2003 Server (SP2) SQL Server 2005 Express with Advanced Services (SP2) on Windows XP (SP2) or Vista Business Edition

x 3.2 GHz or higher Intel processors

15K See

RPM SCIS I/O subsystem across minimum of 6 physical drives

Project Management Database Server Sizing Guide on page 21 and Methodology Management Database Server Sizing Guide on page 22 for memory requirements. Job Service must run on Windows 2003 Server (SP2). For the server running Group Server and providing the Timesheets files
The The

Oracle OLE DB driver compatible with your Oracle version SQL Server client driver compatible with your SQL version server software installed and running

Web 512 200

MB of available RAM or more MB of available hard-disk space network protocol

TCP/IP

For the Job Service or Distributed Job Service

Microsoft 1 4

Windows 2003 Server (SP2)

x 2.8 GHz or higher Intel processor GB of available RAM (recommended)

For the collaboration server

Microsoft Solaris 2 2 1

Windows 2003 Server (SP2)

10 (SPARC)

x 3.2 GHz or higher Intel processors GB of available RAM or more GB minimum available hard-disk space. Size will vary depending volume of documents. server should have a static IP address

The

Application server requirements hosting P6 Web Access

Microsoft Solaris Red

Windows 2003 Server (SP2)

10 (SPARC)

Hat Enterprise Linux AS 4.0 v2

HP-UX11i IBM 2 4 1

AIX 5.3

x 3.2 GHz or higher Intel processors GB of available RAM or more (recommended) GB minimum of available hard-disk space

Java Application server requirements hosting P6 Web Access

JBoss BEA IBM

4.0.5

WebLogic Express or Enterprise Server 9.2 WebSphere Application Server 6.1

For the Web server hosting Project Web Site files

Microsoft

Windows 2003 Server (SP2)

Microsoft Microsoft

Internet Information Server (IIS) 6.0 TCP/IP networking protocol

For P6 Web Access Web server

Microsoft Apache

Internet Information Server (IIS) 6.0

Web Server 2.0.5.9 (or 2.2.6 for Windows 2003 SP2) Supported E-Mail Systems and Network Protocols

Internet

e-mail (SMTP) or MAPI is supported protocols depend only on database vendor

Network Web

site requires TCP/IP

P6 Web Access supports only SMTP.

Project Management Database Server Sizing Guide

The following sizes refer to a single instance of the project management database. Memory sizes do not include overhead required by the operating system, which typically adds 32 MB to the memory requirement and varies depending on the server version.

File
Temp TBS RBS TBS Index TBS Data TBS Lob TBS Total RAM:

Small
300 MB 300 MB 250 MB 250 MB 250 MB 1,350 MB 384 MB

Medium
500 MB 500 MB 500 MB 500 MB 500 MB 2,500 MB 512 MB

Large
1,000 MB 1,000 MB 1,000 MB 1,000 MB 1,000 MB 5,000 MB 1024+MB

Oracle Microsoft SQL Server File

Data Data Log Temp Temp Log Total RAM:

Small
300 MB 150 MB 100 MB 50 MB 600 MB 384 MB

Medium
500 MB 250 MB 200 MB 100 MB 1,050 MB 512 MB

Large
1,000 MB 500 MB 275 MB 125 MB 1,900 MB 1024+MB

Methodology Management Database Server Sizing Guide

The following sizes refer to a single instance of the methodology management database. Memory sizes do not include overhead required by the operating system, which typically adds 32 MB to the memory requirement and varies depending on the server version.

File

Recommende d Size
250 MB 250 MB 250 MB 750 MB

Index TBS Data TBS Lob TBS Total

Oracle Microsoft SQL Server File Recommende d Size

300 MB 150 MB 450 MB

Data Data Log Total

Practical Product Limits

The following table summarizes various practical limits. Exceeding these limits can result in performance issues. Element
Number of activities assigned to a user within the users specified activity timeframe Number of activities per timesheet Number of activities per project Number of relationships per project

Practical Limit
100 100 100,000 100,000

Automatic Database Install Configuring the Server Databases Database Administration In this part

Part

Database Installation and Configuration

hile it is best to have an experienced database administrator install and set up Primavera

applications to run on a network server, your company may not have this type of person available. Primavera provides a quick and easy Setup program for installing the necessary database components on your database server. Read Automatic Database Install and simply follow the steps in the Database wizard to create a new project management and/or methodology management database and load the required data. If you choose not to follow the automated steps, you can also manually set up the database and load the data. See Configuring the Server Databases for detailed instructions. Whether you choose to automatically or manually install your databases, refer to Database Administration for important instructions on modifying database settings that are not part of the installation/setup process. Follow the steps in this chapter to set up and load the Project Management and Methodology Management module databases on a server using the automatic install process. In this chapter:
Overview Running the Database Wizard Automatically Installing an Oracle Database and Loading Application Data Automatically Installing a SQL Server Database and Loading Application Data

Automatic Database Install

Overview
Two databases are used to run Primavera:

The

project management database (PMDB) stores the Project Management data used by Primavera. It is a required database.
The

methodology management database (MMDB) stores the methodologies that can be used as templates when creating new projects. You must install this database if you will be using the Methodology Management module.
If you need detailed steps on installing Oracle for the server and client, or SQL Server for the server, contact Primavera Customer Support.

Primavera supports Oracle, Microsoft SQL Server, and Microsoft SQL Server Express databases. The MS SQL Server or Oracle server software must be installed on the database server(s) before you can create the database. You can run the database wizard to automatically create a database structure and load application data into it; or, you can manually configure the database structures and then run the database wizard to load the application data.
For additional tips and considerations related to database performance along with additional settings, refer to Database Administration on page 57.

Oracle considerations Before installing the Primavera database, consider the following:
If

you intend to run Primavera on an Oracle database server, the Oracle client must be installed on each machine that will be accessing the database server.
When

you install the Oracle client, the TNSPING.EXE utility is automatically installed in the \oracle\<ora_home>\bin folder. This utility must be present for Primavera applications. Do not delete it.
Oracle If

must be run in Dedicated Mode (rather than MTS mode).

you need to use the Euro symbol in any Western European language, you must use codepage WE8MSWIN1252 or UTF8. SQL Server considerations If you intend to run Primavera on a SQL Server or SQL Server Express database server, the required SQL Server client files are automatically installed when you install the Project Management module on a client machine.

Running the Database Wizard

The Database wizard guides you through the steps for creating a new database structure and loading the application data into it. You need not be an experienced DBA to perform these steps; however, Oracle, Microsoft SQL Server or SQL Server Express must already be installed on the database server. You can run the Database wizard to create a new database from a client computer or from the server itself. The Database wizard creates any necessary file structures and users for you. Run the Database wizard twice: first to create the database structure and load data for the project management database, then again for the methodology management database.

Automatically Installing an Oracle Database and Loading Application Data

Complete the following steps to automatically create an Oracle database and load application data:
Primavera Systems recommends that you create a 500 MB temporary tablespace, a 500 MB rollback tablespace, and a 500 MB UNDOTBS tablespace. Refer to your Oracle database documentation if you are unfamiliar with this process. If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key

file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.

1If you are installing from a CD, insert CD 1. An introductory screen should appear that provides installation options. If the screen does not appear, or if you are installing from a network location, double-click autorun.exe in the root folder of CD 1. 2On the main Primavera screen, choose Install Other Tools. 3On the Other Tools screen, choose Server Databases.
Click Next on each wizard dialog box to advance to the next step.

4On the Welcome! dialog box: Choose Create a new Primavera database. In the Key field, enter the product key located on the License CD label. 5On the Select Database Type dialog box, Choose Oracle as the database type. Chose whether to include sample project data in the database. If you want to use a currency other than US Dollars as the base currency for the database, select a different base currency in the To change the base currency field.
YOU MUST CHOOSE THE BASE CURRENCY IN THE FOLLOWING STEP IF YOU DO NOT WANT THE DATABASE TO USE US DOLLARS ($) AS THE BASE CURRENCY. IT IS NOT POSSIBLE TO CHANGE THE BASE CURRENCY ONCE PROJECTS ARE IN PROGRESS.

Setting the Base Currency

For information on adding view currencies, refer to Defining Administrative Preferences and Categories in Project Management on page 401.

The base currency is the monetary unit used to store cost data for all projects in the database and is controlled by a global administrative setting in the Project Management module. The default base currency for Primavera is US dollars ($). The view currency is the monetary unit used to display cost data in Primavera and is controlled by a user preference. The exchange rate for the base currency is always 1.0. When a user selects a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields. For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields. Similarly, if you enter 7.5 Euros in a cost or price field, it is stored in the database as $10. When data is displayed in a view currency that is different than the base currency, some cost and price values may vary slightly (e.g., due to rounding). As long as the correct base currency is selected during database installation, a user can view completely accurate cost and price data by changing the view currency to match the base currency. 6On the Select Application Database dialog box, choose the database for which you are installing data. 7On the Select Installation Method dialog box: Choose Create database and load application data. Decide whether to mark Load license key file. If you choose to load the license key file now, browse to the location of the LICENSE.TXT file. If the LICENSE.TXT file is not available at this time, you can clear this checkbox and load the file later using the Database wizard. Refer to Changing Database Configuration Settings on page 317 for more information.

8On the Oracle Server Details dialog box: In the DBA Username field, type the Oracle system user name to log on to the database; for example, system (which is the default). In the DBA Password field, type the password to log on to the database. If you chose system for the DBA Username, use manager as the password. Otherwise, enter the password associated with the Username you entered. In the Oracle connect string field, enter the Oracle connect string. It can be found in the TNSNAMES.ORA file. The TNSNAMES.ORA file is created when you or your DBA set up the Oracle client. 9On the Configure Oracle Tablespaces dialog box, click Next to accept the name for the Data, Index, and LOB tablespaces and estimated tablespace sizes. The wizard automatically names the tablespaces using the Oracle connect string you previously specified as the prefix (for example, PMDB). You can change the estimated tablespace sizes. Refer to Project Management Database Server Sizing Guide on page 21 for guidelines on sizing. Mark Use existing tablespaces only if the database to which you are connecting already has existing tablespaces. For a new database, do not mark this option. 10On the Configure Oracle Tablespaces dialog box, accept the default location for the Oracle tablespaces, Data, Index, and LOB, or specify different locations. 11On the Configure Oracle Users dialog box, accept the default names for the Oracle administrative user, privileged user, and public user, or specify the appropriate names. If necessary, choose a different default tablespace and temporary tablespace from the dropdown list.
You cannot enter PRIVUSER as the administrative username; doing so will cause conflicts.

You can choose a default tablespace from the dropdown list in the Default Tablespace field. In the Temporary Tablespace field, use the temporary tablespace that you created prior to starting this procedure.
The temporary tablespace must be of temporary type; otherwise, errors can occur to your database.

12On the Ready to Begin Creating Database Structure dialog box, choose Yes, I want to create database tables and structure.
If the database creation fails before completion, a Database Creation Failed dialog box appears with messages stating the errors. Click Copy to Clipboard on this dialog box to record the messages and contact Customer Support for more information.

13On the Load Application Data dialog box, click Next to start the process of loading the database tables with application data. When the process has completed, the message Data Loading Completed appears. Click Finish to exit the wizard. 14If prompted, run the RUN_AS_SYS.SQL and GATHER_STATS.SQL scripts. If you are not prompted, you can access these scripts in the \install\database folder on CD 1.
Running these scripts will improve database performance. The V_$TRANSACTION table stores the earliest login time that data was changed. This improves performance when refreshing data because data before that login time is not accessed. Users must have access to view the V_$TRANSACTION table. Otherwise, the earliest login time cannot be viewed and redundant data is accessed which causes slower performance. To grant access to this table, run the RUN_AS_SYS.SQL script when prompted. Oracle 10g and later supports only cost-based optimization, which relies on accurate statistics to determine the optimal access path for a query. To gather the appropriate statistics for the optimizer, run the GATHER_STATS.SQL script.

15Run the Database wizard again if you will be using the Methodology Management module. Once both sets of application data are installed (Project Management and Methodology Management), you can begin to install client modules and additional components. Refer to Part 3 and Part 4 for more information on configuring the servers and installing client module(s) and additional components.

Automatically Installing a SQL Server Database and Loading Application Data

Complete the following steps to automatically create a SQL Server or SQL Server Express database and load application data:
If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.

1If you are installing from a CD, insert CD 1. An introductory screen should appear that provides installation options. If the screen does not appear, or if you are installing from a network location, double-click autorun.exe in the root folder of CD 1. 2On the main Primavera screen, choose Install Other Tools. 3On the Other Tools screen, choose Server Databases.
Click Next on each wizard dialog box to advance to the next step.

4On the Welcome! dialog box,: Choose Create a new Primavera database. In the Key field, enter the product key located on the License CD label. 5On the Select Database Type dialog box: Choose Microsoft SQL Server/SQL Express as the database type. Choose whether to include sample project data in the database. If you want to use a currency other than US Dollars as the base currency for the database, select a different base currency in the To change the base currency field.
YOU MUST CHOOSE THE BASE CURRENCY IF YOU DO NOT WANT THE DATABASE TO USE US DOLLARS ($) AS THE BASE CURRENCY. IT IS NOT POSSIBLE TO CHANGE THE BASE CURRENCY ONCE PROJECTS ARE IN PROGRESS.

Setting the Base Currency

For information on adding view currencies, refer to Defining Administrative Preferences and Categories in Project Management on page 401.

The base currency is the monetary unit used to store cost data for all projects in the database and is controlled by a global administrative setting in the Project Management module. The default base currency for Primavera is US dollars ($). The view currency is the monetary unit used to display cost data in Primavera and is controlled by a user preference. The exchange rate for the base currency is always 1.0. When a user selects a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields. For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields. Similarly, if you enter 7.5 Euros in a cost or price field, it is stored in the database as $10. When data is displayed in a view currency that is different than the base currency, some cost and price values may vary

slightly (e.g., due to rounding). As long as the correct base currency is selected during database installation, a user can view completely accurate cost and price data by changing the view currency to match the base currency. 6On the Select Application database dialog box, choose the database for which you are installing data. 7On the Select Installation Method dialog box: Choose Create Database and Load Application Data. Mark Load the license key file. Browse to the location of the LICENSE.TXT file. If the LICENSE.TXT file is not available at this time, you can clear this checkbox and load the file later using the Database wizard. Refer to Changing Database Configuration Settings on page 317 for more information. 8On the Microsoft SQL Server Details dialog box: In the System Admin Name field, type the Microsoft SQL Server system administrator name to register to the server. If you chose the defaults during the Microsoft SQL Server installation, accept SA as the system administrator name. In the System Admin Password field, type the password for this system administrator. If you chose the defaults during the Microsoft SQL Server installation, accept a blank password. In the Server Name field, enter the server machine name or IP address where Microsoft SQL Server is installed. You must specify a server name. If you are running the Database wizard from the server machine, the Database wizard automatically enters the server name for you. 9On the Configure SQL Server Database dialog box, click Next to accept the default values, or change them as appropriate to your installation. If you change the name of the database, duplicate database names are not permittedyou will be prompted to enter a unique name if a database with the specified name already exists.
Do not use a dash (-) in the database name; it will cause errors.

The data file contains the database tables and procedures. The log file contains a record of changes. By default, the Database wizard stores these files in the folder on your server where Microsoft SQL Server is installed. The database name that you specify is used to name the files. If you change the location, the destination folder must exist on the server. 10On the Ready to Begin Creating Database Structure dialog box, choose YES, I Want to Create Database Tables and Structure.
If the database creation fails before completion, a Database Creation Failed dialog box appears with messages stating the errors. Click Copy to Clipboard on this dialog box to record the messages and contact Customer Support for more information.

11On the Load Application Data dialog box, click Next to start the process of loading the database tables with application data. When the process has completed, the message Data Loading Completed appears. Click Finish to exit the wizard. 12Run the Database wizard again if you will be using the Methodology Management module. Once both sets of application data are installed (project management and methodology management), you can begin to install client modules and additional components. Refer to Part 3 and Part 4 for more information on configuring the servers and installing client module(s) and additional components. For information on configuring database settings to optimize performance, refer to Database Administration on page 57.

Read this chapter to manually set up the central project management database and the methodology management database on a server running Oracle or Microsoft SQL Server. The steps in this chapter should be performed by your database administrator (DBA). Setup is divided into two steps: creating each databases structure and loading the application data into each database. To use a wizard that automatically creates the database structures and loads the data, refer to Automatic Database Install on page 27. If you are using Microsoft SQL Server Express you should run the Database wizard. In this chapter:
Overview Creating the Database Structure for Oracle Creating the Database Structures for MS SQL Server Installing the Application Data (Oracle and Microsoft SQL Server)

Configuring the Server Databases

Overview
Two databases are used to run Primavera:
The

project management database (PMDB) stores the Project Management data used by Primavera. It is a required database.
The

methodology management database (MMDB) stores the methodologies that can be used as templates when creating new projects. You must install this database if you will be using the Methodology Management module.
If you need detailed steps on installing Oracle for the server and client, or SQL Server for the server, contact Primavera Customer Support.

Primavera supports Oracle, Microsoft SQL Server, and Microsoft SQL Server Express databases. The MS SQL Server or Oracle server software must be installed on the database server(s) before you can create the database.
When you install the Oracle client, the TNSPING.EXE utility is automatically installed in the \oracle\<ora_home>\bin folder. This utility must be present for Primavera applications. Do not delete it.

Creating the Database Structure for Oracle

The Oracle database administrator (DBA) creates the project management and methodology management database, then runs two SQL scripts provided by Primavera, one for each database, that create each databases structure (tables, indexes, relationships, and so on).

The Group Server requires a Unicode project management database when supporting international languages. Oracle must be run in Dedicated Mode (rather than MTS mode). If you need to use the Euro symbol in any Western European language, you must use codepage WE8MSWIN1252 or UTF8. You can also use a wizard that automatically creates the database structures and loads the data for you. Refer to Automatic Database Install on page 27 for more information.

These instructions assume you are an Oracle DBA or are familiar with administering Oracle databases. Create the PMDB Oracle database structures 1Copy the ORPM_INS.SQL and ORPM_SRC.SQL scripts to a local folder. The scripts are located on CD 1 in the \install\database\scripts\install\or folder. You must copy the scripts to a local drive so they can be edited. 2Turn off the files read-only attribute. Since files on a CD are read-only, this attribute is turned on when a file is copied from a CD. In Windows Explorer, right-click the file, choose Properties, and clear the Read-Only checkbox. 3Edit the scripts that you copied in step 1. Follow the instructions in the header of each script for what to modify. 4Create a database with system, temporary, and rollback tablespaces. To keep it simple, create an alias PMDB for that database. Then, make sure that the Oracle client can connect using that alias.
Primavera Systems recommends that you create a database with 500 MB temporary tablespace, a 500 MB rollback tablespace, and a 500 MB UNDOTBS tablespace. Refer to your Oracle database documentation if you are unfamiliar with this process.

5Log on to the PMDB database as a SYSTEM or other DBA privileged user.

Refer to Database Administration on page 57 for more information on database settings you can modify and additional scripts you can run to improve database performance.

6Run the edited ORPM_INS.SQL script. This script creates the data structure for PMDB.
The results of the SQL script are spooled to a text file, ORPM_INS.LST, which is created in the location from which the script is executed. Review this file for error messages to ensure that the process ran as expected.

Once the database structures are created, you can install the application data in the PMDB database as described in Installing the Application Data (Oracle and Microsoft SQL Server) on page 52.

Dropping PMDB Oracle Database Objects

If you make a mistake or want to recreate the database objects, first drop the objects created by the database installation script. Dropping database objects deletes them permanently. For your convenience scripts are provided to drop the database objects. Run the scripts in the \install\database\scripts\install\or\drop\pmdb folder on CD 1. This folder contains the following files:
ORDP_SPS.SQL ORDP_SYN.SQL ORDP_GRN.SQL ORDP_FKC.SQL drops stored procedures drops synonyms revokes privileges drops foreign keys constraints

ORDP_PK.SQL ORDP_NDX.SQL ORDP_TAB.SQL

drops primary keys drops indexes drops tables

If data exists, you must drop the objects in the order they are listed. The results of each script are spooled to a file with an .LST extension. For example, ORDP_TAB.LST contains the results of the SQL script of that name. Create the MMDB Oracle database structures 1Copy the ORMM_INS.SQL and ORMM_SRC.SQL scripts to a local folder. The scripts are located on CD 1 in the \install\database\scripts\install\or folder. You must copy the scripts to a local drive so they can be edited. 2Turn off the files read-only attribute. Since files on a CD are read-only, this attribute is turned on when a file is copied from a CD. In Windows Explorer, right-click the file, choose Properties, and clear the Read-Only checkbox. 3Edit the scripts that you copied in step 1. Follow the instructions in the header of each script for what to modify. 4Create a database with system, temporary, and rollback tablespace. To keep it simple, create an alias MMDB for that database. Then, make sure that the Oracle client can connect using that alias.
Primavera Systems recommends that you create a database with 500 MB temporary tablespace, a 500 MB rollback tablespace, and a 500 MB UNDOTBS tablespace. Refer to your Oracle database documentation if you are unfamiliar with this process.

5Log on to the MMDB database as a SYSTEM or other DBA privileged user. 6Run the edited ORMM_INS.SQL script. This script creates the data structure for MMDB.
The results of the SQL script are spooled to a text file, ORMM_INS.LST, which is created in the location from which the script is executed. Review this file for error messages to ensure that the process ran as expected.

Once the database structures are created, you can install the application data in the MMDB database as described in Installing the Application Data (Oracle and Microsoft SQL Server) on page 52.

Dropping MMDB Oracle Database Objects

If you make a mistake or want to recreate the database objects for the methodology management database, first drop the objects created by the database installation script. Dropping database objects deletes them permanently. For your convenience scripts are provided to drop the database objects. To drop the objects created by the database installation script, run the scripts in the \install\database\scripts\install\or\drop\mmdb folder of CD 1. This folder contains the following files:
ORDP_SPS.SQL ORDP_SYN.SQL ORDP_GRN.SQL ORDP_FKC.SQL ORDP_PK.SQL ORDP_NDX.SQL drops stored procedures drops synonyms revokes privileges drops foreign keys constraints drops primary keys drops indexes

ORDP_TAB.SQL

drops tables

If data exists, you must drop the objects in the order they are listed. The results of each script are spooled to a file with an .LST extension. For example, ORDM_TAB.LST contains the results of the SQL script of that name.

Creating the Database Structures for MS SQL Server

The Microsoft SQL Server DBA creates the project management and methodology management database, then runs two SQL scripts provided by Primavera, one for each database, that create each databases structure (tables, indexes, relationships, and so on).
See Client and Server Requirements on page 16 for more detailed information.

Primavera supports Microsoft SQL Server 2005. These instructions assume you are a DBA or are familiar with how to administer Microsoft SQL Server databases. Before you create the Microsoft SQL Server database structure, you should first register to the server as a system administrator (SA) and review the following server-level configuration changes in the Microsoft SQL Server Enterprise Manager:
Max

Worker Threads Specify the number of threads used to support the users connected to the server. The default setting (255) may be too high for some configurations, depending on the number of concurrent users. Each worker thread is allocated, even if it is not in use, which means that if there are fewer concurrent connections than allocated worker threads, you could be wasting memory resources.
Memory

Keep the setting as Dynamic. Microsoft SQL Server dynamically acquires and frees memory as needed, up to the maximum available memory on your server.
Open

Objects Keep the setting as Dynamic. This setting determines the maximum number of objects that can be opened concurrently on Microsoft SQL Server. The value is set automatically depending on current system needs. You should not need to change this value.
User

Connections Keep the setting as 0, which designates Microsoft SQL Server to adjust the number of simultaneous user connections allowed based on how many are needed, up to the maximum value.
Network

Packet Size Set to 16384.

After configuring the server, stop and start Microsoft SQL Server to ensure that the changes take effect.

Configuring for International Language Support (SQL Server 2005)

For non-Latin language support (Traditional Chinese, Simplified Chinese, Russian, or Japanese), the Group Server requires specific settings when configuring the database. In the database setup, choose the codepage and collation options that coincide with your installation when prompted. Create the PMDB Microsoft SQL Server database structures 1Copy the SSPM_DB.SQL, SSPM_LOGIN.SQL, SSPM_USER,SQL, SSPM_INS.SQL, and SSPM_SRC.SQL scripts to a local folder. These scripts are located on CD 1 in the \install\database\scripts\install\ss folder. You must copy the scripts to a local drive so they can be edited. 2Turn off the files read-only attribute. Since files on a CD are read-only, this attribute is turned on when a file is copied from a CD. In Windows Explorer, right-click the file, choose Properties, and clear the Read-Only checkbox. 3Edit each of the scripts you copied in Step 1.

Follow the instructions in the header of each script for what to replace.
Primavera Systems recommends that you use Microsoft SQL Server Enterprise Manager to perform these steps.

4Register to the server as user SA. 5Create a database named PMDB with a data device of 500 MB or more and a log device of 200 MB or more. You can increase or decrease these amounts depending on how much data you plan to store in the database. You can also mark the Automatically Grow File checkbox to specify that these values automatically increase based on need. 6Create the file groups pmdb_dat1, pmdb_lob1, and pmdb_ndx, and a database file for each group. Make pmdb_dat1 the default file group. Depending on your configuration, consider locating these file groups on separate physical drives. You can change the initial tablespace sizes. Refer to Project Management Database Server Sizing Guide on page 21 for guidelines on sizing. 7At the server level, create logins named PRIVUSER and PUBUSER with secure passwords. Mark the Permit checkbox for the PMDB database for both PRIVUSER and PUBUSER. Also make sure users named PRIVUSER and PUBUSER have been created for the PMDB database in the public group, which should be created automatically when you create logins. 8In Microsoft SQL Server Enterprise Manager, choose Tools, SQL Server Query Analyzer. 9Run the SSPM_INS.SQL script. This script creates the data structure for PMDB. It also creates all of the necessary grants for PRIVUSER and PUBUSER. Once the database structures are created, you can install the application data in the PMDB database as described in Installing the Application Data (Oracle and Microsoft SQL Server) on page 52.

Dropping PMDB Microsoft SQL Server Database Objects

If you make a mistake or want to recreate the database objects for the project management database, first drop the objects created by the database installation script. Dropping database objects deletes them permanently. For your convenience scripts are provided to drop the database objects. To drop the objects created by the database installation script, run the scripts in the \install\database\scripts\install\ss\drop\pmdb folder of CD 1. This folder contains the following files:
SSDP_SPS.SQL SSDP_SYN.SQL SSDP_FKC.SQL SSDP_PK.SQL SSDP_NDX.SQL SSDP_TAB.SQL drops stored procedures drops synonyms drops foreign keys constraints drops primary keys drops indexes drops tables

You must connect to the server as SA to drop objects. Before running each script, copy the scripts to a local drive, turn off the read-only attribute of each file, and edit each script to replace the ??DATABASE_NAME?? parameter in the USE statement with the name of your database (for example, PMDB). If data exists, you must run the scripts in the order listed. Create the MMDB Microsoft SQL Server database structures 1Copy the SSMM_DB.SQL, SSMM_LOGIN.SQL, SSMM_USER,SQL, SSPMM_INS.SQL, and SSMM_SRC.SQL scripts to a local folder.

These scripts are located on CD 1 in the \install\database\scripts\install\ss folder. You must copy the scripts to a local drive so they can be edited. 2Turn off the files read-only attribute. Since files on a CD are read-only, this attribute is turned on when a file is copied from a CD. In Windows Explorer, right-click the file, choose Properties, and clear the Read-Only checkbox. 3Edit each of the scripts you copied in Step 1. Follow the instructions in the header of each script for what to replace.
Primavera Systems recommends that you use Microsoft SQL Server Enterprise Manager to perform these steps.

4Register to the server as user SA. 5Create a database named MMDB with a data device of 500 MB or more and a log device of 200 MB or more. You can increase or decrease these amounts depending on how much data you plan to store in the database. You can also mark the Automatically Grow File checkbox to specify that these values automatically increase based on need. 6At the server level, create logins named PRIVUSER and PUBUSER with secure passwords. Mark the Permit checkbox for the PMDB database for both PRIVUSER and PUBUSER. Also make sure users named PRIVUSER and PUBUSER have been created for the PMDB database in the public group, which should be created automatically when you create logins. 7In Microsoft SQL Server Enterprise Manager, choose Tools, SQL Server Query Analyzer. 8Run the SSMM_INS.SQL script. This script creates the data structure for MMDB. It also creates the necessary grants for PRIVUSER and PUBUSER. Once the database structures are created, you can install the application data in the MMDB database as described in Installing the Application Data (Oracle and Microsoft SQL Server) on page 52.

Dropping MMDB Microsoft SQL Server Database Objects

If you make a mistake or want to recreate the database objects for the methodology management database, first drop the objects created by the database installation script. Dropping database objects deletes them permanently. For your convenience scripts are provided to drop the database objects. To drop the objects created by the database installation script, run the scripts in the \install\database\scripts\install\ss\drop\mmdb folder of CD 1. This folder contains the following files:
SSDP_SPS.SQL SSDP_SYN.SQL SSDP_FKC.SQL SSDP_NDX.SQL SSDP_PK.SQL SSDP_TAB.SQL drops stored procedures drops synonyms drops foreign keys constraints drops indexes drops primary keys drops tables

You must connect to the server as SA to drop objects. Before running each script, copy the scripts to a local drive, turn off the read-only attribute of each file, and edit each script to replace the ??DATABASE_NAME?? parameter in the USE statement with the name of your database (for example, PMDB). If data exists, you must run the scripts in the order listed.

Installing the Application Data (Oracle and Microsoft SQL Server)

When the project management and methodology management database structures are set up, run the Database wizard to load the application data in each of the new databases. You can load the data from a client computer that has access to the databases, or, if your database server is running Windows 2003, you can load the data from the server itself. The client computer used to install the Primavera databases must have the database drivers installed on it. Perform these steps twice: first load the data for the project management database (PMDB), then perform these steps again to load the data for the methodology management database (MMDB).
If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.

Load the application data 1If you are installing from a CD, insert CD 1. An introductory screen should appear that provides installation options. If the screen does not appear, or if you are installing from a network location, double-click autorun.exe in the root folder of CD 1. 2On the main Primavera screen, choose Install Other Tools. 3On the Other Tools screen, choose Server Databases.
Click Next on each wizard dialog box to advance to the next step.

4On the Welcome! dialog box: Choose Create a new Primavera database. In the Key field, enter the product key located on the License CD label. 5On the Select Database Type dialog box: Choose Oracle or Microsoft SQL Server/SQL Express as the database type. Choose whether to include sample project data in the selected database. If you want to use a currency other than US Dollars as the base currency for the database, select a different base currency in the To change the base currency field.
YOU MUST CHOOSE THE BASE CURRENCY IF YOU DO NOT WANT THE DATABASE TO USE US DOLLARS ($) AS THE BASE CURRENCY. IT IS NOT POSSIBLE TO CHANGE THE BASE CURRENCY ONCE PROJECTS ARE IN PROGRESS.

Setting the Base Currency

For information on adding view currencies, refer to Defining Administrative Preferences and Categories in Project Management on page 401.

The base currency is the monetary unit used to store cost data for all projects in the database and is controlled by a global administrative setting in the Project Management module. The default base currency for Primavera is US dollars ($). The view currency is the monetary unit used to display cost data in Primavera and is controlled by a user preference. The exchange rate for the base currency is always 1.0. When a user selects a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields. For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields. Similarly, if you enter 7.5 Euros in a cost or price field, it is stored in the database as $10. When data is displayed in a view currency that is different than the base currency, some cost and price values may vary

slightly (e.g., due to rounding). As long as the correct base currency is selected during database installation, a user can view completely accurate cost and price data by changing the view currency to match the base currency. 6On the Select Application Database dialog box, choose the database for which you are installing data. 7On the Select Installation Method dialog box: Select an installation method. Choose Load Application Data Only if you have already set up the central databases as described earlier in this chapter. Choose whether to load the license key file.
To create database structures and load data automatically, see Automatic Database Install on page 27.

If you choose to load the license key file now, browse to the location of the LICENSE.TXT file. If you do not have the LICENSE.TXT file available to you at this time, you can clear this checkbox and load the file later using the Database Configuration wizard. See Changing Database Configuration Settings on page 317 for more information. 8On the Load Application Data dialog box, click Next to load the database. Before clicking Next, the database structure must already exist, or the application data will not be installed. 9On the Log on as Privileged User dialog box: In the Username and Password fields, type your privileged user name and password. If you are connecting to SQL Server, you must specify the appropriate names in the Server Name field and the Database Name field. If you are running the Database Installation wizard from the server machine, the wizard automatically enters the server name for you. If you are connecting to Oracle, in the Oracle connect string field, type the Oracle connect string, which can be found in the TNSNAMES.ORA file. 10On the Ready to Begin Loading Data dialog box, choose YES, I Want to Overwrite My Database with Default Data.
The data loading process will overwrite any data in the specified database.

After you click Next, the process of clearing the database tables (if they already exist) and loading them with data starts. When the data is loaded, the message Data Loading Completed appears. 11Click Finish to close the Database Configuration wizard. 12Run one of the following scripts: For Oracle and the project management database: ORPM_SRC.SQL For Oracle and the methodology management database: ORMM_SRC.SQL For SQL Server and the project management database: SSPM_SRC.SQL For SQL Server and the methodology management database: SSMM_SRC.SQL

To run these scripts, you must be logged in as admuser for Oracle databases and sa for SQL databases.

Once both sets of application data are installed, you can begin installing other Primavera components and client modules.

Read this chapter to learn how to configure the job scheduler supplied by your RDBMS, how to optimize performance of your Oracle and SQL Primavera databases, and how to configure the native database auditing feature to monitor edits, deletions, and additions to the databases. In this chapter:
Background Processes and Clean Up in P6 Configuring the RDBMS Scheduler Setting Table Reading and Writing Setting Values Tracking Background Job Execution SYMON (System Monitor) DAMON (Data Monitor) Improving Oracle Database Performance Native Database Auditing

Database Administration
Background Processes and Clean Up in P6
Overview Previous Versions Prior to P6, the task of cleaning up the database was initiated by the PM (Project Management) client application. Depending on the clean up task, these tasks were automatically initiated by the PM client when users logged in and out of individual sessions or when the task was manually initiated via an option on the Tools menu. Current Version Because clean up tasks can be resource intensive and time consuming, in P6 these tasks are initiated by two background jobs that run on the database server:
SYMON DAMON

(System Monitor), responsible for running procedures that take less than a few seconds to complete. (Data Monitor), responsible for running procedures that take longer than a few seconds to complete.

Both of these jobs are pre-configured with default settings. Since the default settings are optimal for most environments, you generally do not need to tune them. However, if further optimization is required, you can change the settings to tune the behavior of the background jobs for specific environments. RDBMS Scheduler Since the background jobs are initiated by the job scheduler supplied by the RDBMS, you need to ensure that the scheduler for your specific RDBMS is properly configured. See Configuring the RDBMS Scheduler on page 59 for the configuration parameters for your RDBMS.

Configuring the RDBMS Scheduler

Oracle 10g

Primavera P6 uses DBMS_JOB to schedule jobs in Oracle. If you are using Oracle 10g, verify that the Oracle parameter JOB_QUEUE_PROCESSES is set to a minimum of two. Set JOB_QUEUE_PROCESSES to a greater value than two if other DBMS_JOB processes are present on your system. SQL Server The SQL Server 2005 job uses the SQL Agent to schedule jobs. If you are using SQL Server 2005, verify that the SQL Server Agent service is started on the server and has a startup type of automatic. SQL Server 2005 Express Since Microsoft does not supply a job scheduler with SQL Server 2005 Express, Primavera has created an agent that runs P6 background jobs on SQL Server 2005 Express. This Windows service, Primavera Background Agent (Service Name: PrmBackAgent), is automatically installed when the standalone installation of P6 is used along with SQL Server 2005 Express.
The PrmBackAgent service is installed automatically when you install P6, if it is required, and generally does not need to be manually installed or started unless you have installed SQL Server 2005 Express after installing the standalone version of P6.

Manually Installing PrmBackAgent for SQL Server 2005 Express Although the service is installed automatically by the Primavera installation when it is required, the service can also be installed manually. To install the service manually, you must be a Windows user with admin access to the databases involved. Follow the procedure below to manually install the service. 1Extract the prmbackgroundagent.exe executable from the Data1.cab file on CD 1. 2Place the prmbackgroundagent.exe file in a directory on the local machine (for example, C:\Primavera\PrmBackAgent). 3From the Start menu, click Run. 4Substituting the appropriate path to the prmbackgroundagent.exe file from step 2, execute the following command to install the service:
c:\primavera\PrmBackAgent\prmbackgroundagent.exe /install

Manually Registering and Starting PrmBackAgent Before starting the service, the name of the database instance containing P6 databases must be added to the registry. Follow the procedure below to manually add the database instance name to the registry. 1Add a new registry key to HKEY_LOCAL_MACHINE\Software\Primavera called "BackgroundAgent. 2Add one new string value to the new key called "Server" with the value matching the instance name of the local SQL Server Express (for example, <local computer name>\sqlexpress). 3When this is complete, use the Services control panel to start the agent. The agent will check each database for an instance of the Primavera schema and run the appropriate jobs.

Setting Table
Settings Table Overview The settings table contains name-value pairs that configure the behavior of the background processes. Setting Name The setting name comprises two components: the namespace and the setting name. The namespace component is a dotnotation string representing a formal path to the parameter. The second component identities the name of the setting. Together these two components make up the full setting name.

Value Values in the SETTINGS table are case-sensitive. The value portion of the pair can be one of the following types:
String.

The string data type is a free text value. The most common string sub-type is interval which represents an interval of time by combining a numeric portion with a unit portion as depicted in the table below.

Table 1: Interv al Subty pe

Numeric portion

Unit portion

Example

Meaning

d h + m s

30d 2h 10m 30s

Thirty day interval Two hour interval Ten minute interval Thirty second interval

Numeric. Boolean.

The numeric data type consists of any number.

The boolean data type can have one of two values: true or false, where zero represents false and any non-zero number represents true.
Date.

Setting Example The following is an example of a setting:

Namespace: Setting Value:

database.cleanup.Usession

Name: ExpiredSessionTimeout 2h (two hour interval)

Reading and Writing Setting Values

Settings can be configured through the Settings API Procedures. These procedures are similar to registry or INI file procedure calls. Reading Settings Values Use the following SETTINGS_READ_* procedures to determine the current value of specific settings:
SETTINGS_READ_STRING(ret_val,namespace,settings_name,default) SETTINGS_READ_DATE(ret_val,namespace,settings_name,default) SETTINGS_READ_NUMBER(ret_val,namespace,settings_name,default) SETTINGS_READ_BOOL(ret_val,namespace,settings_name,default)

By way of example, the following code snippets for the Oracle and SQL server databases demonstrate how these procedures are used to read the setting values: Oracle Example: To retrieve the value of the KeepInterval setting in Oracle, use the following code:
SQL> variable vset varchar2(255)

SQL> exec settings_read_string(:vset,'database.cleanup.Usession', 'ExpiredSessionTimeout');

The system responds: PL/SQL procedure successfully completed.

SQL> print vset

SQL Server Example: To retrieve the value of the KeepInterval setting in SQL, use the following code:
declare @vset varchar(255) exec settings_read_string @vset OUTPUT,'database.cleanup.Usession','ExpiredSessionTimeout' print @vset

Writing Setting Values Use the SETTINGS_WRITE_STRING procedure to set the value of a specific setting:
SETTINGS_WRITE_STRING(new value,namespace,settings_name);

The following code snippets for Oracle and SQL server databases demonstrate how this procedure is used to set the value of the ExpiredSessionTimeout setting to twelve hours: Oracle Example: To set the value of the ExpiredSessionTimout setting to twelve hours in an Oracle database, use the following procedure: 1Log into SQL *Plus using PRIVUSER as your user name, 2Run the following statement:
SQL > exec SETTINGS_WRITE_STRING ('12h',' database.cleanup.Usession','ExpiredSessionTimeout');

SQL Server Example: To set the value of the ExpiredSessionTimeout setting to twelve hours in a SQL server database, use the following procedure: 1Open the Query Analyzer/SSMS and connect as PRIVUSER. 2Select the PMDB database, then run the following statement (using 12 hours as an example):
exec SETTINGS_WRITE_STRING '12h','database.cleanup.Usession', 'ExpiredSessionTimeout'

Tracking Background Job Execution

You can track the execution of background jobs by monitoring the high level status settings or by inspecting the BGPLOG table. Monitoring the High Level Status Settings Each time a job is run it will update the SETTINGS table for the setting_name = 'HeartBeatTime.' The job may update this value multiple times during the execution. The maximum difference between this time and the current date can be monitored to assure that the job is running promptly. Refer to the High Level Status Settings table below for information about the HeartBeatTime setting.

Table 2: High Level Status SettingsLast date and time

background job SYMON was executed. Namespace Setting Name Default Setting
database.background.Symon HeartBeatTime N/A

Last date and time background job DAMON was executed. Namespace Setting Name Default Setting
database.background.Damon HeartBeatTime N/A

Inspecting the BGPLOG Table You can also track the execution of background jobs by inspecting BGPLOG table. The BGPLOG table holds detailed entries from the background processes including informational, elapsed time, and error entries. Refer to the BGPLOG Table Descriptions for information about what this table contains. Description Table 3: BGPL OG Table Descri ptionsC olumn
Log_time Time when log entry was made by background process Program generating log entry Type of message Message from the background process Datetime

Value

Source Type Descriptio n

system_monitor, data_monitor INFORMATION, ELAPSED TIME, ERROR A variable message followed by a number in parenthesis which represents the number of rows that were processed. As an example, the message Complete BGPLOG (40) indicates that forty rows were processed.

SYMON (System Monitor)

SYMON is meant to run simple Primavera tasks on a relatively quick schedule. By default the job is scheduled to run every minute and the tasks assigned to this job should not take more than a few seconds to complete on each run. The default interval of one minute should not be changed for this procedure. Procedures performed by SYMON The USESSION_CLEANUP_EXPIRED procedure is currently the only procedure performed by SYMON. This procedure logically deletes USESSION records that have not updated their last_active_time based on the Expired Session settings. Marking expired USESSION records as logically deleted maximizes the number of licenses that are available. Since it is not cleaning up the underlying data (physically deleting rows), the task completes quickly. The clean up of expired sessions is controlled by a value in the SETTINGS table. By default, although the clean up of expired sessions occurs every two hours, the SETTINGS table does not contain a value for this setting. Use the SETTINGS_WRITE_STRING (<value>, <namespace>, <setting>) stored procedure to change the default clean up value. For example, setting the value to "2d" deletes expired sessions older than two days.
Primavera recommends that you set the ExpiredLongSessionTimeout sessions to at least one hour longer than your longest job. For example, if your longest job is a summarizer job that usually takes 12 hours, you should set the value in the SETTINGS table to at least 13.

Refer to the table below for information about the USESSION_CLEANUP_EXPIRED Settings.

Table 4: USESSION_CLEANUP_EXPIRED SettingsSetting Description: Time-out period for normal sessions.

Namespace Setting Name Default Setting Type
database.cleanup.Usession ExpiredSessionTimeout 2h

Interval

Setting Description: Time-out period for long running sessions based

on the function preformed in the application (i.e. Scheduling, Leveling, Summarizing, etc.).

Namespace Setting Name Default Setting Type

database.cleanup.Usession ExpiredLongSessionTimeout 12h

Interval

DAMON (Data Monitor)

The second database job is the DAMON data monitor job. The DAMON job runs the majority of the background processing and is responsible for running background clean up processes required by the application that can potentially take a

relatively long time to run. Procedures performed by DAMON The procedures run by DAMON perform the following tasks:
Cleaning Cleaning

up the BGPLOG table containing the background logs. up the REFRDEL table. the PRMQUEUE entries for Project Security.

Processing Cleaning

up the PRMQUEUE table. cleaning up remaining USESSION records.

Physically Cleaning Cleaning Cleaning Running

up logically deleted records. up the PRMAUDIT table. up the USESSION audit table (USESSAUD). release-specific data clean up.

Additionally the functionality of the DAMON process can be dynamically extended via the user-defined procedure, USER_DEFINED_BACKGROUND. DAMON Procedure Settings BGPLOG_CLEANUP This procedure keeps the BGPLOG table at a reasonable size. The default clean up interval is 5 days which will result in a table size of about 54,000 records. Refer to the following table for information about the settings associated with the BGPLOG_CLEANUP procedure.

Table 5: BGPLOG_CLEANUP SettingsSetting

Description: The oldest records to keep in the BGPLOG table. Namespace Setting Name Default Setting Type
database.cleanup.BackGroundProcessLog KeepInterval 5d Interval

REFRDEL_CLEANUP This procedure physically deletes records from the REFRDEL table based on the value of the KeepInterval setting. The default setting keeps the REFRDEL records from the last five days. To reduce the workload, the number of records processed is capped by the setting MaxRowsToDelete which is set to 10,000 rows by default. During each pass the procedure will attempt to delete percentage of rows defined by the DeletePercentage setting. The default value of the DeletePercentage is setting is ten percent. The DeleteAllThreshold is effectively the minimum number of rows to delete, which is set to 1,000 by default. If desired the clean up can delete all the rows that can be deleted by setting the DeleteAll setting to true (1). Refer to the following table for information about the settings associated with the REFRDEL_CLEANUP procedure:

Table 6: REFRDEL_CLEANUP SettingsSetting

Description: The oldest records to keep in the REFRDEL table.

Namespace Setting Name Default Setting Type

database.cleanup.Refrdel KeepInterval 5d

Interval

Setting Description: Determines whether the procedure will delete all

of the REFRDEL records possible on each pass.

Namespace Setting Name Default Setting Type

database.cleanup.Refrdel DeleteAll 0 (false)

Boolean

Setting Description: Determines whether all of the records are cleaned

up. If the total record count is less than this number then all the records are cleaned up.

Namespace Setting Name Default Setting Type

database.cleanup.Refrdel DeleteAllThreshold 1,000

Numeric

Setting Description: Percentage of records to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Refrdel DeletePercentage 10 (%)

Numeric

Setting Description: Maximum rows to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Refrdel MaxRowsToDelete 10,000

Numeric

OBSPROJ_PROCESS_QUEUE

This procedure is used to defer processing of OBSPROJ updates by queuing the updates to the PRMQUEUE table. Refer to the following table for information about the settings associated with the OBSPROJ_PROCESS_QUEUE procedure.

Table 7: OBSPROJ_PROCESS_QUEUE SettingsSetting Description: Maximum project-level queue records

to process on each run.

Namespace Setting Name Default Setting Type

database.obsproj.queue MaxProjectUpdates 1000

Numeric

Setting Description: Maximum EPS-level queue records to process on each run.

Namespace Setting Name Default Setting Type

database.obsproj.queue MaxEpsUpdate 25

Numeric

Setting Description: Maximum times to re-process a failed entry before

marking it as an error.

Namespace Setting Name Default Setting Type

database.obsproj.queue MaxRetries 50

Numeric

CLEANUP_PRMQUEUE This procedure physically deletes records from the PRMQUEUE table based on the value of the KeepInterval setting. The remaining settings are similar to the REFRDEL_CLEANUP. Refer to the following table for information about the settings associated with the CLEANUP_PRMQUEUE procedure:

Table 8: CLEANUP_PRMQUEUE SettingsSetting

Description: The oldest records to keep in the PRMQUEUE table.
Default is five days.

Namespace

database.cleanup.Prmqueue

Setting Name Default Setting Type

KeepInterval 5d

Interval

Setting Description: Determines whether the procedure will delete all

of the PRMQUEUE records possible on each pass.

Namespace Setting Name Default Setting Type

database.cleanup.Prmqueue DeleteAll 0 (false)

Boolean

Setting Description: Determines whether all of the records are cleaned

up. If the total record count is less than this number then all the records are cleaned up.

Namespace Setting Name Default Setting Type

database.cleanup.Prmqueue DeleteAllThreshold 1,000

Numeric

Setting Description: Percentage of records to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Prmqueue DeletePercentage 10(%)

Numeric

Setting Description: Maximum rows to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Prmqueue MaxRowsToDelete 10,000

Numeric

USESSION_CLEAR_LOGICAL_DELETES This procedure physically deletes all logically deleted USESSION records. There are no settings associated with this procedure: All logically deleted USESSION records are cleared.

CLEANUP_LOGICAL_DELETES This procedure removes logically deleted rows based on the value of the KeepInterval setting. Records in the database can be marked as deleted (logically deleted) by setting the DELETE_SESSION_ID column to a non-null value. By default, records that were deleted more than 5 days ago will be physically deleted by this procedure.
The CLEANUP_LOGICAL_DELETES procedure will not physically delete records whose DELETE_SESSION_ID column is set to a negative value.

Refer to the following table for information about the settings associated with the CLEANUP_LOGICAL_DELETES procedure:

Table 9: CLEANUP_LOGICAL_DELETES SettingsSetting Description: The oldest logically deleted records to

keep in tables.

Namespace Setting Name Default Setting Type

database.cleanup.LogicalDelete KeepInterval 5d Interval

Setting Description: Determines whether the procedure will delete all

of the logically deleted records possible on each pass.

Namespace Setting Name Default Setting Type

database.cleanup.LogicalDelete DeleteAll 0 (false) Boolean

Setting Description: Maximum rows to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.LogicalDelete MaxRowsToDelete 10,000 Numeric

PRMAUDIT_CLEANUP If the auditing feature is enabled, this procedure will physically delete records from the table based on the value of the KeepInterval setting. Refer to the following table for information about the settings associated with the PRMAUDIT_CLEANUP procedure:

Table 10: PRMAUDIT_CLEANUP SettingsSetting

Description: Should the procedure attempt to clean up PRMAUDIT
records.

Namespace Setting Name Default Setting Type

database.cleanup.auditing Enabled 1 (true)

Boolean

Setting Description: The oldest audit records to keep in PRMAUDIT. Namespace Setting Name Default Setting Type
database.cleanup.auditing KeepInterval 30d

Interval

CLEANUP_USESSAUD This procedure physically deletes records from the USESSAUD table based on the KeepInterval. The remaining settings are similar to the REFRDEL_CLEANUP procedure. Refer to the following table for information about the settings associated with the CLEANUP_USESSAUD procedure:

Table 11: CLEANUP_USESSAUD SettingsSetting

Description: The oldest records to keep in the USESSAUD table. Namespace Setting Name Default Setting Type
database.cleanup.Usessaud KeepInterval 5d Interval

Setting Description: Determines whether the procedure delete all the

REFRDEL records possible on each pass.

Namespace Setting Name Default Setting Type

database.cleanup.Usessaud DeleteAll 0 (false) Boolean

Setting Description: Determines whether all of the records are cleaned

up. If the total record count is less than this number then all records are cleaned up.

Namespace Setting Name

database.cleanup.Usessaud DeleteAllThreshold

Default Setting Type

1,000 Numeric

Setting Description: Percentage of records to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Usessaud DeletePercentage 10 (%) Numeric

Setting Description: Maximum rows to delete on each pass. Namespace Setting Name Default Setting Type
database.cleanup.Usessaud MaxRowsToDelete 10,000 Numeric

USER_DEFINED_BACKGROUND This procedure is an optional customer procedure that is run by DAMON. There are no settings associated with this procedure. CLEANUP_OLD_DATA This procedure is empty in P6. It will be used in future releases to perform release related data clean up.

Improving Oracle Database Performance

There are several Oracle database settings you can modify that will improve the performance of your Primavera database.
If you automatically install the database using the database configuration wizard as described in Automatic Database Install on page 27, you are automatically prompted to run the RUN_AS_SYS.SQL and GATHER_STATS.SQL scripts at the end of the installation. If you manually create the database as described in Configuring the Server Databases on page 39, you should run the script as described below after you create the database.

Grant access to the V_$TRANSACTION table: The V_$TRANSACTION table stores the earliest login time that data was changed. This improves performance when refreshing data because data before that login time is not accessed. Users must have access to view the V_$TRANSACTION table; otherwise, the earliest login time cannot be viewed and redundant data is accessed which causes slower performance. To grant access to this table, connect to Oracle as SYS. Run the RUN_AS_SYS.SQL script located in the \install\database folder on CD1, or run the following GRANT statement: grant select on v_$transaction to admuser; Gather statistics for cost-based optimization: Oracle 10g and later supports only cost-based optimization, which relies on accurate statistics to determine the optimal access path for a query. To gather the appropriate statistics for the optimizer, which will improve database performance, run the GATHER_STATS.SQL script located in the \install\database folder on CD1.

Native Database Auditing

Native database auditing permits you to log the edits, additions, and deletions made by users of Primavera applications. Native database auditing takes advantage of the fact that every change made by a user results in a Data Manipulation Language (DML) INSERT, UPDATE, or DELETE statement being executed against tables in the database schema. Since every application table in the schema has its own auditing trigger, you can log changes made to each table regardless of who made the change or when the change was made. The database schema owner owns the auditing trigger: trigger execution cannot be bypassed. Configuring the Auditing Level You can adjust the amount of information that is logged by adjusting the audit level for each table. The granularity of the audit can be refined further by setting the audit level individually for insert, updates and deletes within each table.

Table 12: Auditing LevelsLevel

Level 0 Level 1 Level 2 Level 3

Description

No audit. Row-level audit. Audit only the operation without column details Column-level Audit without blobs. Audit changes to the data at the column level but without blob changes Full Audit. Audit changes to the data at the column level. For Oracle, column level changes to blobs are audited. For SQL server, column level changes to blobs are not included.

Simple Configuration There are two configuration procedures available that provide for the simple control of the auditing feature:
auditing_enable(<table_name>,

<level>)

auditing_disable(<table_name>)

These procedures allow for setting the audit level on an individual table or the same audit level for all of the tables. However, the simple configuration procedures do not allow for setting individual auditing levels for insert, update, or delete operations within a table. Examples for Oracle: Use the following examples as a guide to using the simple audit configuration procedures to control the auditing feature. The following code snippet enables full auditing on all tables:
exec auditing_enable(null,3);

The following code snippet enables level one auditing on the task table:
exec auditing_enable('TASK',1);

The following code snippet disables auditing on PROJWBS:

exec auditing_disable('PROJWBS');

The following code snippet completely disables auditing across the entire database:

exec auditing_disable(null);

Detailed Configuration You can configure auditing trigger behavior by changing values in the settings table that enable or disable the following auditing features:
The The The

auditing feature itself auditing of specific tables auditing of table insert, update, or delete operations within each table

Turning Auditing Off and On You can enable or disable the auditing feature itself by using the database.audit.Enable setting. Use the settings_write_bool procedure to enable/disable the overall auditing feature. Oracle Example: To enable the overall auditing feature in Oracle, use the following code:
exec settings_write_bool(1,'database_audit','Enable');

SQL Server Example: To enable the overall auditing feature in SQL Server, use the following code:
exec settings_write_bool 1,'database_audit','Enable'

Each individual table's auditing settings are controlled by the Options setting in each table's auditing namespace (for example, database.audit.TASK). The Options setting is a three character string with a numeric value in each character position representing the audit level for insert, update, and delete, respectively.

Tabl e 13: Audi ting Level Opti ons Setti ng by Tabl e Oper ation
Insert Level
0 1

Operation

Update
0 1

Delete
0 1

Description
No audit. Row-level audit. Audit only the operation without column details

Column-level audit without blobs. Audit changes to the data at the column level but without blob changes Full Audit. Audit changes to the data at the column level. For Oracle, column level changes to blobs are audited. For SQL server, column level changes to blobs are not included.

The following table provides some example uses of the options setting:

Table 14: Setting the Auditing Level Options Setting by Table Operation ExamplesNamespac
e
database.audit.TASK

Setting

Value

Description

330

Fully audit any insert and update operations. Do not audit any delete operations. Row-level audit on deletes only. Fully audit.

database.audit.PROJWBS database.audit.TASKRSR C

Options

001 333

Individual table audit settings can be changed using the settings_write_string procedure. Oracle Example: To set the table settings to fully audit insert and update operations but ignore any delete operations, use the following code for Oracle:
exec setting_write_string('330','database.audit.TASK','Options');

SQL Server Example: To set the table settings to fully audit insert and update operations but ignore any delete operations, use the following code for SQL Server:
exec setting_write_string '330','database.audit.TASK','Options' Changes to auditing settings will not necessarily be reflected immediately in the application. In general the program will need to close the database connection and then reconnect to the database to get the new settings.

Understanding Auditing Data The Audit Table Audit records are inserted into the PRMAUDIT table. One record is inserted into the audit table for each row changed in the database.

Table 15:

Type

Description

PRMAUDIT TableColumn
audit_date table_name pk1, pk2, pk3, pk4 oper prm_user_name Date String(30) String(255) String(1) String(32)

Date and time of change Table Name

Primary key values for audited record I=Insert, U=Update, D=Delete Primavera user name if the change was made in Primaveras applications Column changes up to 4000 characters (Level 2 and 3 only) Blob changes and overflow from audit_info (Level 2 and 3 only) Flag for deletes that are logical (marked) rather that a physical delete Database user name (usually PRIVUSER) Operating system user name of connected session Name of program connecting to the database

audit_info audit_info_extended

String(4000) BLOB

logical_delete_flag

String(1)

rdbms_user_name* os_user_name* program* host_name*

String(255) String(255) String(255) String(255)

Computer name of connected session

Name of application connected to the database IP or MAC address of connected session

app_name* netaddress*

String(25) String(24)

* Values will differ from SQL Server and Oracle

Select privileges should be granted to the administrative user (ADMUSER) on V_$SESSION to assure correct values for several auditing table values.

Session Auditing Activity for the USESSION table is audited with its own trigger and table. When an application user logs out of the system they logically delete, or mark, their session record in the USESSION table. One record is written to the USESSAUD table for each logout. The format of the USESSAUD table mirrors that of the USESSION table. This audit can be enabled using the usessaud_enable procedure and disabled using the usessaud_disable procedure. Column-level Audit Data The data changes for each audit are stored in the audit_info and audit_info_extended columns. The audit_info column contains all the row changes as long as they do not exceed 4000 characters. Changes over 4000 characters or any edit to a blob will be written to the audit_info_extended BLOB column.

Data in the two audit_info columns has a specific format. Each column audit within the data begins with either ":O" (old data) or ":N" (new data) to distinguish between the audit of the previous (old) or the changed (new) value (for BLOB columns the data starts with :BLOBO or :BLOBN). Directly after this is the name of the column in lowercase. Following the column name is the length of the audited value in a fixed four character field. Finally the actual data is placed in the audit record. Updates will have both an old and new value for each change. Inserts will have only a new value and deletes only an old value. The following is an example of the audit record for a change to the TASK to change the task_code from 'A1010' to 'B102:'
audit_info =>:Otask_code: 5:A1010:Ntask_code: 4:B102

Configuring the Group Server for Timesheets Installing P6 Web Access Collaboration Setup Configuring the Distributed Job Service In this part:

Part

Server Installation and Configuration

ead this part to install and configure the components of Primavera that need to run on a network

server. Configuring the Group Server for Timesheets discusses how to prepare a server for a Timesheets implementation, which requires a Web server. The Installing P6 Web Access chapter provides instructions for setting up P6 Web Access. The Collaboration Setup chapter describes how to set up the collaboration server for use with P6 Web Access. The Configuring the Distributed Job Service chapter provides details on how to configure the job service to distribute jobs to multiple servers simultaneously. To implement Timesheets as part of your Primavera installation, you must install the Group Server on your network. The Group Server acts as an intermediary between the Timesheets client module and your database server. This chapter describes how to install and configure the Group Server. In this chapter:

Uninstalling a Previous Version of the Group Server Installing the Group Server and Timesheets Web Site Configuring Group Server/Timesheets for LDAP Authentication Configuring Group Server/Timesheets for Single Sign- On Authentication Configuring Group Server Settings Setting up Java Web Start for Timesheets Creating Multiple Instances of Group Server Group Server Configuration Settings

Configuring the Group Server for Timesheets

Uninstalling a Previous Version of the Group Server
If you are upgrading from a previous version, we recommend that you first uninstall the existing Group Server. A new Web site is created during Setup. 1From the Windows Control Panel, select Services. 2Select the Primavera Group Server entry and click Stop. 3Close the Services window. 4In the Control Panel window, double-click Add/Remove Programs. 5Select Primavera Group Server, then click the Add/Remove button. Follow the steps in the Uninstall wizard, then click Finish when the wizard completes the uninstall.

Installing the Group Server and Timesheets Web Site

After installing the Group Server and Timesheets website, refer to Implementing Timesheets on page 439 for information on configuring Timesheets.

Timesheets is a Web-based module that project team members can use to update project data. Timesheets connects to the project management database via the Group Server, which is a Windows 2003 service. Timesheets requires a two-part installation: installing and configuring the Group Server and installing the Timesheets Web site. You can install the Group Server on any Windows 2003 server that has constant access to the project management database. The Timesheets Web site must be installed on a Web server. The files installed to the Timesheets Web site include HTML and Java files, applet download files, the Java JRE installer, and the Timesheets Help site. The installation process allows you to enable users to launch Timesheets via Java Web Start as well.
If you will require that timesheets be reviewed and approved, you must install P6 Web Access, as described in Installing P6 Web Access on page 125, to enable user access to the Timesheet Approval application. After you install P6 Web Access and configure Timesheets, you can configure access to the Timesheet Approval application as described in Configure Access to Timesheet Approval on page 457. For more information about Java Web Start, visit the http://java.sun.com Web site.

Java Web Start Java Web Start provides a secure and platform-independent deployment of Timesheets using Java Network Launching Protocol (JNLP) technology. Java Web Start also ensures that users always launch the most recent version of Timesheets under the correct client-side JRE version, even if there is more than one JRE version present.

Supported operating systems for Java Web Start: Windows XP Windows Vista Ubuntu Linux Supported Web servers for Java Web Start: Microsoft IIS Apache Client requirements for Java Web Start: JRE Internet Explorer or Firefox For Oracle connections, the Group Server machine must have the Oracle Provider for OLE DB installed. A full Oracle client installation (Administrator Setup) will install the required Oracle Provider for OLE DB files. If connecting to a unicode Oracle database, you must install the compatible Oracle OLE DB driver on the machine running the Group Server. For Oracle 10g, the minimum supported version of the OLE DB driver is 10.2.0.2. For SQL Server connections, the Group Server machine requires that the SQL Server client is installed. The SQL Server client is automatically installed when you install Primaveras Project Management module. FOR LANGUAGE SUPPORT If the Group Server is connecting to a Unicode Oracle database and international language support is required, confirm the following Registry setting under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME The suffix for the NLS_LANG key must coincide with the current language (e.g., CL8MSWIN1251 to support Russian). See the appropriate Oracle NLS documentation for more information. If the Group Server is connecting to a SQL Server database, the system default locale for the operating system of the Group Server machine must match the codepage setting of the database instance to which it is connecting.

Before performing these steps, you must have already set up the central project management database. Set up the Group Server and Timesheets files 1Insert CD 1. An introductory screen should appear that provides installation options. If the screen does not appear, double-click autorun.exe in the root folder of CD 1. 2On the main Primavera screen, click Install Other Tools. 3On the Other Tools screen, choose Team Member Timesheets.
Click Next on each wizard dialog box to advance to the next step.

4On the Enter Product Key screen, enter the product key located on the License CD label. 5On the Welcome! dialog box, click Next. 6On the Choose Components dialog box, choose the components you want to install. Mark both checkboxes to install the Group Server and Timesheets Web site on the same server. If you choose to install only the Group Server, skip to step 10. 7On the Choose Language dialog box, choose to install Timesheets in any of the languages listed. 8On the Choose Web Destination Location dialog box, click Browse to specify a destination folder for the Web files. The files will be installed in a folder named \GroupServer\en. If you chose not to install the Group Server, skip to step 12.
If installing to Sun ONE Web Server, you must edit the config\mime.types file to support the Primavera Timesheets JRE auto-installation feature. See Support JRE auto-installation on Sun ONE Web Server on page 102.

9On the Help URLs dialog box, specify the location of the Timesheets Help web site.
You can change the web site values later by manually editing the proper files. For the Java Web Start version of Timesheets, edit the timesheet.jnlp file in the \GroupServer\App folder. For the applet version, edit the erps8x6.html in the \GroupServer\en folder.

10On the Choose Database Type dialog box, select the database type. The database must already be installed and configured. 11On the Enter Database Parameters dialog box, specify the database connection parameters. The database user name must be a privileged user (for example, privuser). If connecting to Oracle, an Oracle DSN need not be predefined. Enter the Oracle Service Name (for example, PMDB), which may have been defined using Oracles Net Configuration Assistant, or refer to your TNSNAMES.ORA file located in \Oracle_Home\Network\Admin. If connecting to Microsoft SQL Server, enter the SQL Server Database Machine Name, which is the name of the computer on which the Microsoft SQL Server database is running. In the Database Schema Name field, type the name of the database specified when the Microsoft SQL Server database was created, such as PMDB. 12On the Choose User Authentication Method dialog box, choose the Group Server authentication method.
If you choose LDAP authentication, additional configuration steps are required after you complete this procedure. For details, see Configuring Group Server/Timesheets for LDAP Authentication on page 104.

13If you chose Native or LDAP authentication in step 12, the Choose Communication Protocol dialog box is displayed: choose the protocol to connect to the Group Server. Choose Socket for direct communication between the client and the Group Server. If you choose this option, continue with step 14. Choose HTTP(s) for secure transmission of timesheet data using the HTTP(s) protocol. If you choose this option, stop performing these steps and continue with Installing Group Server to use HTTP(s) on page 99. If you chose Single Sign-On authentication in step 12, the Choose Communication Protocol dialog box is not displayed. Instead, the installation wizard assumes HTTP protocol and modifies the Choose User Authentication Method dialog box (step 12) to allow you to choose a destination folder for the required Group Server servlet. After accepting the default location or specifying a new location for the servlet, continue the installation procedure as documented in Installing Group Server to use HTTP(s) on page 99, beginning with step 3 (page 100). 14If you chose Socket in step 13, the Server Information dialog box is displayed. In the Server Name field, type the name of the computer running the Group Server. In the Port Number field, accept 9002 as the port number, or specify a port number greater than 1024. This number is used with the IP address to create a Windows socket (Winsock) connection between the Timesheets client and the Group Server. If your organization uses a firewall, this port must be opened for Internet use.
If you use a port number other than 9002, you must edit the web.xml file, as described later in this chapter (page 103).

15On the Enter URL to launch Timesheet application dialog box, enter the URL for Java Web Start.
You can change the Java Web Start URL later by manually editing the proper files. See Changing the Java Web Start URL on page 113.

To allow users to launch Timesheets via Java Web Start, you have to enter the URL for the Java Web Start Web server. Enter the server IP address, and change the folders if necessary.
Apache URLs are case-sensitive. In case of a mismatch, instead of being processed by the server, the XML content of the JNLP file is displayed in the browser.

16On the Start Installation dialog box, click Next to begin the installation. 17On the Test Database Connection String dialog box, click Test to test the connection. If errors are reported, you can modify the database connection string and click Test to retry the connection. Use the following format in the Database Connection String field:
If you receive the error Provider not found, install the Oracle Provider for OLE DB, which can be downloaded from Oracles Web site.

If connecting to Oracle: Provider=OraOLEDB.Oracle;Data Source=Oracle Service Name, where the Oracle Service Name can be found in the TNSNAMES.ORA file. If connecting to Microsoft SQL Server: Provider=SQLOLEDB; Data Source=MachineName; Initial Catalog=DatabaseSchemaName 18Click Next to continue. 19On the Start Window service dialog box, mark the checkbox to start the Primavera Group Server service now. If you do not start it now, you can start it at any time with Microsoft Services in the Microsoft Management Console (the Group Server runs as a Windows service.) 20Click Next to continue. 21Click Finish to close the Setup wizard. Setup is now complete. You can run the Group Server Administrator to review or modify additional configuration settings, as described in Configuring Group Server Settings on page 108. Installing Group Server to use HTTP(s) When installing the Group Server, you can use the HTTPS protocol for secure transmission of timesheet data. The GroupServer.war file includes a J2EE-compliant servlet that enables client communications to occur over the HTTP protocol. The .war file must be installed on a Java application server, such as JBoss. You can install JBoss from CD 2. The following figure illustrates the relationship between the components. In this figure, the Group Server and the Java application server can reside on the same or separate machines.

If the Group Server and Java application server do not reside on the same machine, you must edit the web.xml file. The web.xml file is contained within the GroupServer.war file. For more information, see page 103.

To use the HTTP protocol, follow these steps: 1To install the Group Server, follow steps 1 through 12, as described earlier in this chapter (Set up the Group Server and Timesheets files, beginning on page 95). 2On the Choose Communication Protocol dialog box, choose HTTP(s). Click Browse to specify a destination folder for deploying the GroupServer.war file. By default, this file installs to your inetpub\wwwroot folder. However, you should specify the location that your Java application server uses for storing Web applications.
You may need to deploy the GroupServer.war file manually. On JBoss, simply copy the groupserver.war file to the \jboss-4.0.5.GA\server\myprimavera\deploy folder and start the application server. On WebSphere, use the Administrative Console to assign the context root GroupServer to the groupserver.war file. Refer to the application servers documentation for more information.

3On the Server Information dialog box, specify the URL for the Group Server servlet, which depends on the

application server being used and its configuration. For normal transmission using the HTTP protocol, enter http and the port number to which you have configured your Java application server to service http requests. Use the following format
: http://<Java app server>:port number/GroupServer/GroupServer.

For example, the URL for a default JBoss installation is

:http://<jboss_server_name>:8080/GroupServer/GroupServer
You can manually change the URL after Setup by editing the erps8x6.html file in the \GroupServer\Language folder. For more information, see Edit the erps8x6.html File on page 102.

For secure transmission using the HTTPS protocol, enter https and the port number to which you have configured your Java application server to service https requests. The default secure port on JBoss is 8443. In this case, for example, specify the secure URL as,
:https://<jboss_server_name>:8443/groupserver/groupserver. Some Java application servers (e.g., IBM WebSphere) are case-sensitive.

4On the Enter URL to launch Timesheet application dialog box, if you plan to use the Timesheets Java Web Start version, enter the URL that will launch Timesheets. 5Click Next to begin the installation. 6On the Test Database Connection String dialog box click Test to test the connection. If errors are reported, you can modify the database connection string and click Test to retry the connection. Use the following format in the Database Connection String field: If connecting to Oracle through ODBC: Provider=OraOLEDB.Oracle;Data Source=Oracle Service Name, where the Oracle Service Name can be found in the TNSNAMES.ORA file. If connecting to Microsoft SQL Server: Provider=SQLOLEDB; Data Source=MachineName; Initial Catalog=DatabaseSchemaName 7Click Next to continue. 8On the Start Window service dialog box, mark the checkbox to start the Primavera Group Server service now. If you do not start it now, you can start it at any time with Microsoft Services in the Microsoft Management Console (the Group Server runs as a Windows service.) 9Click Next to continue. 10Click Finish to close the Setup wizard. Edit the erps8x6.html File To change the URL specified for the Group Server servlet during installation, edit the erps8x6.html file as follows. The erps8X6.html file is located in the language folder within the Group Server install location. For example, for English, the location is GroupServer/en/erps8X6.html. // *** Configurable variables. // *** May be changed by the system administrator. var ServerName=''; var ServerPortNum=9002; var DebugLevel=0; var Protocol='http'; // This should say 'http' for HTTP OR HTTPS, or, // 'socket' for a traditional socket install.
In the erps8X6.html file, the entire var url entry must appear on a single line.

var url='http://my_server_name:8080/groupserver/groupserver'; // Or, if you want to use HTTPS, "var url='https://my_server_name:8443/groupserver/groupserver';". Support JRE auto-installation on Sun ONE Web Server To support successful operation of the JRE auto-installation feature, edit the config\mime.types file to remove the exe reference as shown below. Before: type=magnus-internal/cgi After: type=magnus-internal/cgi

exts=cgi,exe,bat exts=cgi,bat

Edit the web.xml File If either of the following conditions exists, once the GroupServer.war file has been expanded, you must edit the web.xml file.
the the

Primavera Group Server and Java application server do not reside on the same machine Primavera Group Server is not using port number 9002

The web.xml file is located in the \groupserver\WEB-INF folder. Configure the server and port number to point to the Group Server. This is the location of the TPGS service that is configured during the initial setup. From the web.xml file: <init-param> <param-name>server</param-name> <param-value>TPGS_server_name</param-value> </init-param> <init-param> <param-name>port</param-name> <param-value>9002</param-value> </init-param>

Configuring Group Server/Timesheets for LDAP Authentication

To run Group Server/Timesheets using LDAP authentication:
Select

LDAP mode when you install Group Server the Timesheets web site file erps8X6.html

Modify

You can configure both the HTTP(s) and socket communication protocols by creating two Timesheets web sites, one configured for socket and one for HTTP(s). This might be useful when some Timesheets users run Timesheets inside your corporate network, while others run outside the firewall. Both web sites can be configured to use the same Group Server.

Modify the erps8X6.html File The erps8X6.html file is located in the language folder within the Group Server install location. For example, for English, the location is GroupServer/en/erps8X6.html. If Group Server is installed to communicate with Timesheets using a socket connection, modify erps8X6.html to match

the following settings:

ServerName and Server Port Number are specific to your installation.

var ServerName='yourGroupServer ServerName' (only used if Timesheets is communicating with Group Server via socket) var ServerPortNum=9002 (only used if Timesheets is communicating with Group Server via socket) var DebugLevel=0; var Protocol='socket'; var url= ''; (optional - only used if Timesheets is communicating with Group Server via servlet) var appType='atTeamplay' var authMode='LDAP'; If Group Server is installed to communicate with Timesheets using HTTP(s) protocol, modify erps8X6.html to match the following settings:
URL is specific to your installation.

var ServerName=' ' (unused - this is specified in the web.xml in the Group Server servlet) var ServerPortNum=9002 (unused - this is specified in the web.xml in the Group Server servlet) var DebugLevel=0; var Protocol='http';
In the erps8X6.html file, the entire var url entry must appear on a single line.

var url='http://yourServerName:780/groupserver/groupserver'; var appType='atTeamplay' var authMode='LDAP';

Configuring Group Server/Timesheets for Single Sign- On Authentication

To run Group Server/Timesheets using Single Sign-On authentication:
Select

Single Sign-On mode when you install Group Server the Web server plug-in you are using to proxy requests

Configure Modify

the Timesheets Web site file erps8X6.html

Timesheets Single Sign-On authentication requires that the Group Server be installed using HTTP protocol.

Configure the Web Server Plug-In for Single Sign-On The procedure for configuring a Web server plug-in to proxy Group Server requests depends on your application server/Web server combination. For specific instructions, refer to the documentation provided for your application server/Web server. Modify the erps8X6.html File After installation, modify the Group Server erps8x6.html files so that the URL for the Group Server servlet contains the fully qualified Web server name and the SiteMinder protected port. An erps8X6.html file is located in each language folder within the Group Server install location. For example, for English, the location is GroupServer/en/erps8X6.html. Modify the erps8X6.html file as shown in the following settings:
The format of the Group Server servlet URL depends on the server you are using to host the Group Server servlet. The settings shown here are only an example.

var ServerName=' ' (unused - this is specified in the web.xml in the GroupServer servlet)

var ServerPortNum=9002 (unused - this is specified in the web.xml in the GroupServer servlet) var Protocol='http';
In the erps8X6.html file, the entire var url entry must appear on a single line.

var url='http://<yourfullyqualifieddomainname>:<yourSiteMinder protectedportnumber>/groupserver/groupserver'; var appType='atTeamplay' var authMode='WebSSO'; The URL line in the erps8X6.html file identifies the Web server/port number that is being protected by SiteMinder. It is through this URL that the timesheet applet communicates with the GroupServer servlet. For Single Sign-On, all requests for this URL go through the SiteMinder agent that is running on the Web server. In the Web server, you must configure a virtual directory to redirect requests received on the virtual directory to the Group Server servlet.

Configuring Group Server Settings

As the system administrator, you can view and modify additional administrative information using the Group Server Administrator. Start the Group Server Administrator From the server computers, on the Windows Control Panel, select TPGS Administrator. Administer servers The Administration tab displays the current Group Server to administer. If multiple Group Servers are installed, you can choose which server to administer. Click the Browse button in the Server field and navigate to the server you want to add. For security purposes, Primavera Systems recommends placing all Group Servers in the same domain or at a minimum, establishing trust relationships between them.

If you need to take the server offline to perform system maintenance, click Take Off-Line.
Login requests are denied when the server is offline.

The Take Off-Line Options dialog box displays the number of users currently connected to the server. Choose whether to wait for the last user to exit from Timesheets before taking the server offline automatically, or specify a number of minutes to wait before the server is taken offline. When you choose either option, no new users can start Timesheets.
You can type @TIME in the body of the message, which will automatically report the amount of time remaining before the server goes offline.

Mark the Send Message to Logged in Users checkbox and type a message. You can specify how often to resend the message. Once the Group Server is offline, all client connections are terminated and future connection requests are denied. Review configuration settings for Group Server The Properties tab provides information about how the Group Server is configured. Generally, you do not need to modify these settings. You can click on each property to display a brief description at the bottom of the dialog box. To modify a setting, click the property and type the new value in the Value column.

For an explanation of each property and its location in the system registry, see Group Server Configuration Settings on page 118.

Mark the Show Advanced Properties checkbox to show additional properties that you can change. You should not change these properties casually; incorrect settings may prevent the server or operating system from working properly.
You must first close the TPGS Administrator, then stop and restart the Group Server (TPGS) service for changes to take effect.

The Users tab displays the active user names. Click Refresh to refresh the list of users connected. Click Disconnect User(s) to immediately disconnect the currently selected user. You can also send a message to one or more users, for example, a notification before you disconnect them. Select each user name in the Users area, then type a message in the Message field at the bottom of the screen. Click Send Message.

Setting up Java Web Start for Timesheets

Java Web Start provides a secure and platform-independent deployment of Timesheets, using the Java Network Launching Protocol (JNLP) technology. Java Web Start also ensures that users always launch the most recent version of Timesheets under the correct JRE version, even if there is more than one JRE version present.
To learn how to run Timesheets after Java Web Start has been configured, refer to Running Timesheets Web Browser Version and Java Web Start Version on page 454.

How does Java Web Start work? Java Web Start can launch a Java application stored on a server by presenting a link in an HTML page to the user. When the user clicks the link on the HTML page, Java Web Start detects whether the user has the correct JRE version installed and the most recent version of Timesheets cached. If not, Java Web Start automatically downloads the necessary files, then launches Timesheets from the users machine. This enables the user to run the most recent version of Timesheets with the required version of the JRE without performing a manual upgrade process. By temporarily hiding, but not overwriting other versions of the JRE, Java Web Start ensures that other applications that need those JRE versions will still run.
Java Web Start allows you to launch more than one instance of Timesheets at the same time. Previously, Timesheets did not allow multiple instances running at the same time.

Configure Microsoft IIS Web server to support JNLP files Make sure the correct MIME type is set for JNLP files. From the IIS services, select the Default Web Site. Right-click to choose Properties and click the HTTP Header tab. Click the File Types on the bottom of the window and add the following new type if necessary: .jnlp application/x-java-jnlp-file

Configure Apache Web server to support JNLP files To ensure that the Web server recognizes the JNLP files, add the following two lines to the httpd.conf file if necessary: AddType application/x-java-jnlp-file .jnlp AddType application/x-java-archive-diff .jardiff
Remember that Apache URLs are case-sensitive. In case of a mismatch, instead of being processed by the server, the XML content of the JNLP file is displayed in the browser.

Changing the Java Web Start URL If you change the original Java Web Start URL (for example, to move the Java Web Start Web site), you have to edit the URL manually in the following three files:
Timesheet.jnlp

Tsres.jnlp Download.html

Changing the required JRE version The Timesheet.jnlp file defines the required JRE for Java Web Start when launching Timesheets. When you launch the Java Web Start version of Timesheets, if the required JRE version is not found, it is downloaded and installed. Troubleshooting
Remember For For

that Apache URLs are case sensitive, even if the user has a Windows client that does not differentiate.

non-Windows clients, the server IP address has to be mapped to the server name in the host file.

Windows clients, if the URL with the server name is not recognized (you see the content of the JNLP file), use the server IP address in the URL or add an entry for the server in host file.

Creating Multiple Instances of Group Server

You can create multiple Group Server instances in the TPGS Administrator. This enables you to access several different databases from the same server machine. You must have a unique database for each new instance. Launching the TPGS Administrator starts the primary instance. To start a new instance, select it from the list.

Create a new instance Click the New Instance button and specify its properties. Type an instance name, description, unique port number, and your privileged administrative database user name and password.

Use the following formats to specify the connection string: For Oracle: Provider=OraOLEDB.Oracle;Data Source=Oracle Service Name For Microsoft SQL Server: Provider=SQLOLEDB; Data Source=MachineName; Initial Catalog=DatabaseSchemaName You can define the Oracle Service Name using Oracles Net Configuration Assistant, or you can refer to your TNSNAMES.ORA file located in \Oracle_Home\Network\Admin. Once a new instance is created, it appears in the Services dialog box. You can start or stop the instances from the Services dialog box. A new instance has a Manual startup property (does not start automatically after a reboot).

Set up the Web site for a new instance You must create a new Timesheets Web site for each new instance. Once a new Group Server instance is set up in the TPGS Administrator, you must copy the Timesheets Web site to enable clients to connect to the new instance. For example, copy the GroupServer Web site folder to a new name, GroupServer2. In the GroupServer2 folder, edit the erps8x6.html file to update the port number. For example, by default, the original Group Server instance has a port number equal to 9002. In the erps8x6.html file, change the ServerPortNum variable to match the port number of the newly created instance (9003), as shown. // *** Configurable variables.

// *** May be changed by the system administrator. var ServerName='servername var ServerPortNum=9003 Clients can visit the original instance by visiting the index.html file in the GroupServer folder; clients can visit the newly created instance by visiting the index.html file in the GroupServer2 folder.

Group Server Configuration Settings

Configuration settings can be reviewed or modified using the Properties tab in the TPGS Administrator. Mark the Show Advanced Properties checkbox to display all properties. These settings are stored in the Registry in the HKEY\System\CurrentControlSet\Services\TPGS\Configuration key on the computer running the Group Server.
Only experienced administrators should use the Registry to modify configuration settings. In the tables below, the Value column lists the recommended settings given heavy load conditions (1000 users or more).

[General key values] Value Name

Allow Negative Actuals Cycle Seed

Value
Yes/No Yes/No

Description
Allow negative actuals when calculated. No - Disallow. Yes Allow. Controls whether or not to cycle the seed used for password encryption. A seed is a unique, random numeric value, used to make each encrypted password unique. Set to No when load testing, where login requests need constant encrypted password values. Allow supervisor to modify subordinate resources timesheets. Allow editing of public document path in the Work Product and Document Details dialog box in the timesheet client. Sets Performance Monitor counters based on TPGS server activity. Use the Windows Performance Monitor utility to view TPGS performance counters.

Edit Subordinate Resources Timesheets Edit Work Product and Document Details Enable Performance Counters Enable Primary Resource to Edit Steps UDF Values Counters Greeting LDAP Connect Timeout

Yes/No Yes/No

Yes/No

If Y, overrides OBS access to edit steps UDF values. Gives edit rights to primary resources. If N, steps can be edited if user has OBS access to the project. The default value is N. Sets the message that appears in the client when first connected to the TPGS server.

15

The maximum amount of time Group Server will allow for a connection attempt to an LDAP data store to succeed. This is only used if the Group Server is configured for LDAP authentication. Records transactions for tracing to the event log

Log Transactions Maximum Auto-Fetch Size (bytes) Maximum Request Size 2048

Maximum size of blobs (notes/memos) in bytes that will be sent automatically in low bandwidth mode. Largest client TCPIP request that will be accepted by TPGS server.

Port

9002

Sets the TCP/IP port number used by the Group Server to communicate with the Java client. This port must be opened to the Internet, or you can change this setting to specify another port that is open to the Internet. The default value is 9002. Amount of time the TPGS service delays before starting. Use this setting if dependent services (such as a database server service) need time to start first. Amount of time in seconds a connection can remain idle before being logged off. The default value is 600.

Startup Wait Period (seconds) User Inactivity TimeOut Period

600

[Database key values] Value Name

ADO Connection TimeOut (seconds) ADO Command TimeOut (seconds) ADO RecordSet Cache Size ADO Stalled Check Period (seconds) Apply Session Setting Auto Translate Base Connections Cache Refresh Interval (seconds) Connect Retry Period (milliseconds) Connection String 15

Value

Description

Amount of time to wait while establishing a connection before terminating the attempt and generating an error message. Amount of time to wait while executing a command before terminating the attempt and generating an error message. The number of records stored in memory at any given time. Frequency with which the connection is checked for stalled operations. Determines whether to execute the SQL command specified in the Session Setting property. The default value is No. The Auto translate property of the SQL Server ODBC Driver for a SQL Server Unicode database. Default number of database connections that the TPGS server makes on startup. Frequency of the TPGS server for refreshing cached data from the database. Amount of time to wait before retrying to connect. ADO connection string used to connect to the database. For example, for Oracle, use the connection string provider=OraOLEDB.Oracle; Data Source = pmdb.world. For example, for SQL Server or SQL Server Express, use the connection string provider=SQLOLEDB; Data Source=PMDBSRV\ENGLISH;Initial Catalog=TPPM60, where PMDBSRV is the database machine name. Type of database ("Oracle or Microsoft SQL Server/SQL Express) that the TPGS server uses for data.

30

5 30

Yes/No Yes/No 25 (default=10) 60 30000

Database Type DB Connectivity Check Yes/No

Determines if database connectivity is tested periodically. and if connections are closed and restored upon database shutdown, restart. User name with privileged access used to connect to the database. The default value is PRIVUSER. Period that inactive licensed client connections are considered to be bad.

DB User License Inactivity TimeOut

PRIVUSER 900

(seconds) Log Invalid Login Attempts Log SQL Max Search Result Records Password Session Setting Sync Period (seconds) Synchronize ADO Connection Creation Temporary Connections 60 Yes/No 150 Yes/No 0 100 Logs invalid login attempts to the event log. The default value is No. Sets SQL tracing flags for tracing to the event log. Maximum number of records in search results. Encrypted password of DB user account used to connect to the database. SQL command to be executed against every database connection created by Group Server. Period between updating the sync table in the database. Blocks other requests while connecting to a database. The default value is Yes. Number of database connections that the TPGS server can make as demand warrants. These settings determine how many connections the Group Server has to the database. If you are getting an error where HRESULT = 8004b002, this indicates the Group Server cannot handle the load and needs more database connections to process all requests. A value of 400 is recommended if more than 1000 timesheet users are accessing the Group Server, which will allow more connections so that TPGS can handle a larger load. Consideration is also given to the Oracle Server machine. Determines if verbose logging is enabled when sending error messages to the event log.

Verbose Logging

Yes/No

[Threading key values] Value Name

Caching Threads

Value
1

Description
Number of threads that will handle cached transaction processing. This is the minimum number of caching threads. Cache threads in the Group Server are responsible for processing data where the data can be cached. The Group Server will create up to Maximum Temporary threads per CPU caching threads as needed. Number of coalesced jobs that determine when the coalescing processor is considered busy. Number of threads that will handle coalesced transaction processing. This is the minimum number of coalescing threads. Coalescing threads in the Group Server are responsible for processing jobs which can be coalesced. Coalescing is the act of taking like requests (e.g., open, update timesheet) and coalescing them into a single SQL request to satisfy several clients concurrently with one DB hit, thus greatly improving performance. The Group Server will create up to Maximum Temporary threads per CPU coalescing threads as needed. Frequency that coalesced requests are fulfilled.

Coalescing Jobs Busy Threshold Coalescing Threads

50 1

Coalescing Timeout (milliseconds)

750

Connection Check Period (seconds) Connection TimeOut Period (seconds) License Manager Interval (seconds) Message Threads Per CPU

60

Frequency at which database connections are checked.

300

Period of inactivity for which attached database connections are assumed to be good. Frequency that the license manager is checked for concurrent users. Number of threads that will handle socket connections from the client. This is the minimum number of threads which accept messages from the client via a socket connection and create jobs to be processed in the Group Server. The Group Server will create up to Maximum Temporary threads per CPU message threads as needed. Maximum number of coalesced transactions that can be queued before they are processed. Maximum number of threads that can be started by each processor. MaxTempThreads=CPU>1?MaxTempThreads+ (MaxTempThreads*4/CPU Period of inactivity before a temporary thread is shut down.

120

3 (default=1)

Maximum Coalescing Size Maximum Temporary Threads Per CPU (SMP) Thread Inactivity TimeOut Period (seconds) Transaction Threads

20 15

180

Number of threads that will handle transaction processing. This is the minimum number of threads which create transactions in the Group Server. Transactions created are either Caching, Coalescing, or Update. The Group Server will create up to Maximum Temporary threads per CPU transaction threads as needed. Number of threads that will handle update transaction processing. This is the minimum number of Update threads. Update threads in the Group Server are responsible for updating data. The Group Server will create up to Maximum Temporary threads per CPU update threads as needed. Frequency that the TPGS server checks for connection problems.

Update Threads

Watch Dog Period (seconds)

120

[Security keys] Keys

Accept Filters Reject Filters

Value
Filter #1, *.*.*.* Filter #1, *.*.*.255

Description
TCP/IP client addresses that will be accepted. TCP/IP client addresses that will be rejected.

[Install key values] Value Name

Value

Description

HTML Path

c:\inetpub\wwwroot\GroupServer

Path to the HTML files.

This chapter describes how to install P6 Web Access (formerly known as Primaveras Web application or myPrimavera) on a Windows, Solaris, AIX, Red Hat Enterprise Linux or HPUX server. In addition, this chapter explains how to use the Administration Application of P6 Web Access to review, modify, add, and delete Application Server configurations for P6 Web Access. In this chapter:
Upgrading to P6 Web Access Uninstalling Previous Versions Installing the Application Server for P6 Web Access Installation Process for P6 Web Access Configuring and Deploying the Application Server for P6 Web Access Starting the Server for P6 Web Access Stopping the Server for P6 Web Access Accessing P6 Web Access from Client Browsers Configuration Settings on Client Browsers Changing Database Configuration Settings Using the Administration Application Starting the Administration Application Reviewing and Modifying Configurations for P6 Web Access Configuration Settings for P6 Web Access Implementing Application Server Plug-Ins

Installing P6 Web Access

Upgrading to P6 Web Access
Before upgrading to P6 Web Access, you should upgrade the project management and/or methodology management database for compatibility with P6 and install the Project Management and/or Methodology Management client modules.
For further details, see Automatic Database Upgrade on page 301 and Installing Client Modules and Additional Components on page 279. For the full list of tested configurations for P6 Web Access, refer to the testedcfg.htm file in the \Documentation\ <language>\Technical Documentation\Tested Configurations folder on CD 3.

To upgrade from myPrimavera 5.0 or Primaveras Web Application 6.0 to P6 Web Access version 6.1 1Uninstall the current version of myPrimavera or Primaveras Web Application.

2Install one of the supported application servers. 3JBoss (for Windows and Solaris) is included on CD 2. 4For a list of supported application servers, see Client and Server Requirements on page 16. 5Install P6 Web Access. 6Configure and Deploy the application server. 7Install or upgrade the collaboration server for P6 Web Access (see Collaboration Setup on page 187).

Uninstalling Previous Versions

You must uninstall any previous versions of P6 Web Access before upgrading to P6. To uninstall myPrimavera 5.0 from a Tomcat 5.5 Server
On

Windows, from the Start menu, choose Programs, <app name>, Uninstall <app name>. On Solaris, change to the webapps directory under the Tomcat install directory and run the uninstalltc.sh script.
Tomcat is not a supported application server for P6 Web Access version 6.1.

To uninstall myPrimavera 5.0 or Primaveras Web Application 6.0 from a JBoss 4.0.4 Server Rename or delete the myprimavera folder from the JBoss install location (for example, c:\jboss-4.0.4.GA\server) To uninstall myPrimavera 5.0 or Primaveras Web Application 6.0 from a WebLogic 9.2 Server 1On Windows, from the Start menu, choose Programs, <app name>, Uninstall <app name>. On Solaris, run the uninstall.sh script in the <BEA_HOME>\user_projects\<domain> directory. 2Launch the WebLogic Admin Console and delete the myPrimavera application from the Web Application modules. The myprimavera.war file must be deleted manually. To uninstall myPrimavera 5.0 or Primaveras Web Application 6.0 from a WebSphere 6.1 Server 1On Windows, from the Start menu, choose Programs, <app name>, Uninstall <app name>. On Solaris, change to the installableApps/<app name> directory under the WebSphere install directory and run the uninstallws.sh script. 2Launch the WebSphere Application Console and remove the current myPrimavera deployment.
If you will use the same <myPrimavera_home> directory for the new deployment, the existing myprimavera.war file must be deleted from the <myPrimavera_home> directory.

Installing the Application Server for P6 Web Access

P6 Web Access includes the JBoss server. The files for Windows and Solaris are located in the \jboss-4.0.5 folder on CD 2.
For the full list of tested configurations for P6 Web Access, refer to the testedcfg.htm file in the \Documentation\ <language>\Technical Documentation\Tested Configurations folder on CD 3.

P6 Web Access also supports BEA WebLogic and IBM WebSphere. For a complete list of supported application servers with version numbers, see Client and Server Requirements on page 16.
On Windows, it is recommended that you install the application server to a folder with a short name.

Installing JBoss on Microsoft Windows Install the JDK The version of JBoss included on CD 2 requires JDK 1.5.0_13. The JDK is not provided by Primavera. To download the JDK, go to

http://java.sun.com/products/archive. Install JBOSS 4.0.5 GA 1Copy the jboss-4.0.5.GA.zip to a local drive. 2Unzip the folder to <JBOSS INSTALL LOCATION> (for example, C:\jboss-4.0.5.GA). 3Go to <JBOSS INSTALL LOCATION>\server. 4Select the folder default, press Ctrl-C to copy it, and then press Ctrl-V. This creates a folder named copy of default. 5Rename the folder called 'copy of default' to be 'myprimavera.' 6Go to <JBOSS INSTALL LOCATION>\server\myprimavera\ deploy\jbossweb-tomcat55.sar\META-INF. 7Open jboss-service.xml and find the following entry: <attribute name="UseJBossWebLoader">false</attribute> Change false to true. Installing JBoss on Red Hat Enterprise Linux Install the JDK The version of JBoss included on CD 2 requires JDK 1.5.0_13. The JDK is not provided by Primavera. To download the JDK, go to http://java.sun.com/products/archive. Install JBOSS 4.0.5 GA 1Copy the jboss-4.0.5.GA.zip to a local drive. 2Unzip the folder to <JBOSS INSTALL LOCATION> (for example, /usr/jboss-4.0.5.GA). 3Go to the <JBOSS INSTALL LOCATION>/server. 4Select the folder default, press Ctrl-C to copy it, and then press Ctrl-V. This creates a folder named default(copy). 5Rename the folder called 'default(copy)' to be 'myprimavera.' 6Go to <JBOSS INSTALL LOCATION>/server/myprimavera/deploy/jbossweb-tomcat55.sar/META-INF. 7Open jboss-service.xml and find the following entry: <attribute name="UseJBossWebLoader">false</attribute> Change false to true. Installing WebLogic Install the JDK The 9.2 version of WebLogic requires JDK 1.5.0_13 (or 1.5.0_08 for HP-UX) to run on P6 Web Access. The JDK is not provided by Primavera. To download the JDK, go to http://java.sun.com/products/archive. Install WebLogic 9.2 Consult WebLogics documentation for installation instructions. Installing WebSphere Install the JDK The 6.1 version of WebSphere requires JDK 1.5.0_10 (or 1.5.0_06 for Solaris and IBM AIX) to run on P6 Web Access. The JDK is not provided by Primavera. To download the JDK, go to http://java.sun.com/products/archive.

Install WebSphere 6.1 Consult WebSpheres documentation for installation instructions.

Installation Process for P6 Web Access

For information on installing the project management database, see Database Installation and Configuration on page 25. For information on upgrading a database for compatibility, see Automatic Database Upgrade on page 301.

Before upgrading to P6 Web Access version 6.1, you should install the 6.1 version of the project management and/or methodology management database, or upgrade your current version, and install the 6.1 version of the Project Management and/or Methodology Management client modules.
For instructions on installing the Project Management module, see Installing Client Modules and Additional Components on page 279.

The installer for P6 Web Access provides a wizard to guide you through the installation process, which includes: 1Identifying the application server used for P6 Web Access 2Installing P6 Web Access and Administration Application files 3Setting up and configuring the database for P6 Web Access
If you are using JBoss as your application server, you must install the Sun JDK 1.5.0_13 prior to installing P6 Web Access.

To install P6 Web Access 1Launch the installer from the root folder of CD 2: For the Windows platform, double-click 'SetupMainWin.exe'. For the Solaris and Red Hat Enterprise Linux platforms, double-click 'SetupMainSol.bin'. For the AIX platform, double-click 'setupaix'. For the HP-UX platform, double-click 'setupHP11.bin'.
Click Next on each wizard dialog box to advance to the next step.

2On the Welcome screen, click Next. 3Accept the license agreement. 4On the Please specify a Primavera Home folder. . . dialog box, type or browse to the location for the home folder of P6 Web Access. Click Yes to create the directory, if necessary.
The home folder name cannot contain spaces.

The application EAR file (myprimavera.ear) is copied to the home folder for P6 Web Access. You must then use the application servers deployment tools to deploy the myPrimavera EAR file. Also, make sure that the supported JDK is set as an environment variable in your path to provide access to the java command. For the full list of tested configurations for P6 Web Access, refer to the testedcfg.htm file in the \Documentation\ <language>\Technical Documentation\Tested Configurations folder on CD 3. P6 Web Access supports SSL implementation for JBoss. For information on configuring SSL, refer to the JBoss server documentation.

5On the P6 Web Access will be installed. . . dialog box, click Next to start the installation. 6On the Setup and Configuration of the Primavera Database dialog box, select the database type (Oracle or SQL). 7On the Please enter the following information. . . dialog box, specify the database connection parameters. Type your database user name (for example, pubuser) and password, the database name, host address, and host port. The database name, host address, and host port are specific to your Oracle or MS SQL Server installation. The Database Host Port field displays the default port for the database type you selected. You can edit this port. The Public Group ID must be 1 for a standard configuration.
For more information about configurations, see Using the Administration Application on page 153.

8If there is an existing Primavera configuration, on the The installer has detected. . . dialog box, you can choose whether you want to use it, or create a new configuration.
If you are upgrading from a previous version of myPrimavera against the same database, choose the option to create a new configuration. This is necessary to accommodate newly added configuration settings.

If there is no existing Primavera configuration, the The installer has detected. . . dialog box does not appear and the installation process automatically creates a default configuration named Primavera Configuration. You can edit the settings for this configuration through the Administration Application of P6 Web Access.
For more information, see Changing Database Configuration Settings on page 152.

After installation, you can use the Database Configuration Setup wizard to choose a different configuration, if necessary

9When the message displays to confirm that the database configuration has completed successfully, click OK. Then, click Finish to close the Setup wizard.
For information about installing the Job Service, see Installing the Job Service and Distributed Job Service on page 287.

The schedule, apply actuals, and summarize functions of P6 Web Access require you to install the Job Service.

Configuring and Deploying the Application Server for P6 Web Access

Configuring JBoss 4.0.5 GA on Microsoft Windows 1Use the P6 Web Access Database Configuration Utility (that automatically launched during setup) to connect to your database. 2Copy the myPrimavera.ear file to the following location: <JBOSS INSTALL LOCATION>\server\myprimavera\deploy\ 3For international support: Edit the following file: <JBOSS INSTALL LOCATION>\server\myprimavera\ deploy\jbossweb-tomcat55.sar\server.xml In the Connector setting, add the parameter URIEncoding="UTF-8". For example: <!--A HTTP/1.1 Connector on port 8080--> <Connector port="8080" URIEncoding="UTF-8" address="${jboss.bind.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/>
When you are using the SSL-connector, add this parameter to its settings as well.

4Browse to <JBOSS INSTALL LOCATION>\bin. 5Edit the run.bat command file. Insert the following line before the :RESTART line: set JAVA_OPTS= "-Dprimavera.bootstrap.home=<p6webaccesshome>" %JAVA_OPTS% Change <p6webaccesshome> to the proper location (for example, c:\myPrimavera). 6In the run.bat file, do the following to set the Java options: Find the following line: set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m Replace that line with the following: set JAVA_OPTS=%JAVA_OPTS% -XX:PermSize=64m -XX:MaxPermSize=128m -Xms512m -Xmx512m 7Save the changes to the run.bat file. 8Create a bat file named 'startmyPVinJboss.bat' in <p6webaccesshome> that contains the following: @echo off set JBOSS_HOME=C:\jboss-4.0.5.GA call %JBOSS_HOME%\bin\run.bat -c myprimavera
This bat file is necessary for starting the JBoss application server.

9Run the newly created bat file.

If a Java version error displays, add the JAVA_HOME Environment variable in the <myprimavera>.bat file. For example, in Windows, the line would read as follows: set JAVA_HOME=C:\Program Files\Java\jdk1.5.0_13

10Now that the server is started, follows these steps to display the language drop-down on the login page: Search for the primalang.xml file in the JBoss home directory. Copy this file to <p6webaccesshome>. Restart the server. 11Service Administrators might want to secure the JMX Console. For instructions, visit the following JBoss web page: http://www.jboss.org/wiki/Wiki.jsp?page=SecureTheJmxConsole 12If applicable, proceed to Additional Settings for JBoss and WebLogic on Microsoft SQL 2005 Databases on page 140. Configuring JBoss 4.0.5 GA on Red Hat Enterprise Linux 1Use the P6 Web Access Database Configuration Utility (that automatically launched during setup) to connect to your database. 2Copy the myPrimavera.ear file to the following location: <JBOSS INSTALL LOCATION>/server/myprimavera/deploy/ 3For international support: Edit the <JBOSS INSTALL LOCATION>/server/myprimavera/deploy/jbossweb-tomcat55.sar/server.xml file.

In the Connector setting, add the parameter URIEncoding="UTF-8". For example: <!--A HTTP/1.1 Connector on port 8080--> <Connector port="8080" URIEncoding="UTF-8" address="${jboss.bind.address}" maxThreads="250" strategy="ms" maxHttpHeaderSize="8192" emptySessionPath="true" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true"/>
When you are using the SSL-connector, add this parameter to its settings as well.

4Browse to <JBOSS INSTALL LOCATION>/bin. 5Edit the run.sh command file. Insert the following line in the '# Setup JBoss specific properties' section: JAVA_OPTS="-Dprimavera.bootstrap.home=<p6webaccesshome> $JAVA_OPTS" Change <p6webaccesshome> to the proper location (for example, /usr/webaccess61). 6Save the changes to the run.sh file. 7In the run.conf file, do the following to set the Java options: Find the following line: JAVA_OPTS="-XX:PermSize=64m -XX:MaxPermSize=64m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gsInterval=3600000" Replace "-XX:PermSize=64m -XX:MaxPermSize=64m" with the following: "-XX:PermSize=64m -XX:MaxPermSize=128m -Xms512m -Xmx512m" 8Save the changes to the run.conf file. 9Open a terminal. Type the following commands: cd /<JBOSS INSTALL LOCATION>/bin ./run.sh -c myprimavera
If a Java version error displays, add the JAVA_HOME Environment variable in the <myprimavera>.sh file.

10Now that the server is started, follows these steps to display the language drop-down on the login page: Search for the primalang.xml file in the JBoss home directory. Copy this file to <p6webaccesshome>. Restart the server. 11Service Administrators might want to secure the JMX Console. For instructions, visit the following JBoss web page: http://www.jboss.org/wiki/Wiki.jsp?page=SecureTheJmxConsole 12If applicable, proceed to Additional Settings for JBoss and WebLogic on Microsoft SQL 2005 Databases on page 140. Configuring WebLogic 9.2
For users installing P6 Web Access on HP-UX 11i and wishing to start the P6 Web Access installation from CD: Go to the command prompt, change your directory to point to the root of the CD-ROM, and find the setupmain.jar file. Then, type the following command, making sure to specify the java executable in the system path: <cdrom_mount> java -jar setupmain.jar

1Run the WebLogic Configuration Wizard to create a server domain for P6 Web Access. On the Configure Server Start Mode and JDK window, you must select Development Mode in the WebLogic Domain Startup Mode left hand pane. 2Copy myprimavera.ear from the P6 Web Access home folder created during installation to the following folder: <bea_home>\user_projects\domains\<your_domain>\autodeploy 3Make a backup copy of the startWebLogic file in case you need to undo any changes. 4Edit the line that begins with set JAVA_OPTIONS= in the startWebLogic file. In Unix, the file is named startWebLogic.sh and is located in: <bea_home>/user_projects/domains/<your_domain>/bin/ In Windows, the file is named startWebLogic.cmd and is located in: <bea_home>\user_projects\domains\<your_domain>\bin\ 5At the end of this line in the startWebLogic file, add the Primavera bootstrap variable. In Unix, the line should look similar to the following: set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Dprimavera.bootstrap.home=/usr/local/<p6webaccesshome> 6By default, WebLogic 9.2 does not work with Sun JDK 1.5.0_13. In order for P6 Web Access to work with this configuration, append the following to the end of the line in the startWebLogic file (modified in step 5): -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersion UID=1.0
Be sure to include a space before the -Dcom specification.

7(Red Hat Enterprise Linux) By default, RedHat does not install all the appropriate libraries for P6 Web Access. In order for P6 Web Access to work under Weblogic 9.2 on RedHat, append the following to the end of the line in the startWebLogic file (modified in step 5): -Djava.awt.headless=true
Be sure to include a space before the -Djava specification. Properties after the bootstrap can be in any order.

8Set the Java Virtual Machine by entering a variable for JAVA_VM, immediately below the JAVA_OPTIONS line, in the startWebLogic file. In Unix, the line should look similar to the following: set JAVA_VM=-server 9Include <p6webaccesshome>\license and ojdbc14.jar at the beginning of the WebLogic classpath in the startWebLogic file. In Unix, the line should look similar to the following: CLASSPATH=/usr/local/<p6webaccesshome>/license:/user/local/<p6webaccesshome>/lib/ojdbc14.jar:$ {CLASSPATH} In Windows, the line should look similar to the following: CLASSPATH=C:\<p6webaccesshome>\license\;C:\ <p6webaccesshome>\lib\ojdbc14.jar;%SAVE_CLASSPATH% 10Make a backup copy of the setDomainEnv file in case you need to undo any changes.

11In the setDomainEnv file, add the JAVA_HOME setting. In Windows, the line should look similar to the following: set BEA_JAVA_HOME=C:\bea\jrockit90_150_04 set SUN_JAVA_HOME=C:\Program Files\Java\jdk1.5.0_13 if "%JAVA_VENDOR%"=="BEA" ( set JAVA_HOME=%BEA_JAVA_HOME% ) else ( if "%JAVA_VENDOR%"=="Sun" ( set JAVA_HOME=%SUN_JAVA_HOME% ) else ( set JAVA_VENDOR=Sun set JAVA_HOME=C:\Program Files\Java\jdk1.5.0_13 ) ) 12Increase the JVM MaxPermSize setting in the setDomainEnv file to avoid Out-of-Memory errors. The MaxPermSize setting should be set to at least 256m. In HP-UX, the line should look similar to the following if [ ${JAVA_VENDOR} = HP ] ; then MEM_ARGS=${MEM_ARGS} ${MEM_DEV_ARGS} -XX:MaxPermSize=256m export MEM_ARGS In Windows, the line should look similar to the following: if %JAVA_VENDOR%==Sun ( set MEM_ARGS=%MEM_ARGS% %MEM_DEV_ARGS% -XX:MaxPermSize=256m ) 13Modify memory settings in the setDomainEnv file to maximize performance. To do this, edit the MEM_ARGS line so that values can be set for NewSize, MaxNewSize and SurvivorRatio. For instance, if the total heap size is 1024, NewSize and Max NewSize should be set to 256, which would then require a value of 8 for SurvivorRatio. The complete line would look similar to the following: set MEM_ARGS=-XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m where: -XX:NewSize= is the minimum size of new generation heap (sum of eden & two Survivor spaces) -XX:MaxNewSize= is the maximum size of the new generation heap -XX:SurvivorRatio= is the size of survivor space (ratio of eden to Survivor space) The Young generation area equals the sum of eden and 2 Survivor spaces.
After completion of step 13, the WebLogic domain instance of P6 Web Access can be started.

Precompiling P6 Web Access on WebLogic 1Copy the "precompile_utility" directory from CD 2 to the server where P6 Web Access is installed. 2Open a command prompt and go to the newly created "precompile" directory.

3Run the following command: precompile -u <base URL> -f <input file> -w where: <base URL> is the P6 Web Access base URL <input file> is the P6 Web Access EAR file -w enables windowed mode (optional)
The file path of the P6 Web Access EAR file cannot contain spaces.

Assuming a standard P6 Web Access installation, The command should look similar to the following in HPUX-11i: java -jar JSPPrecompile.jar -u http://localhost:7001/myprimavera -f <p6webaccesshome>/myprimavera.ear The command should look similar to the following in Windows: precompile -u http://localhost:7001/myprimavera -f c:\<p6webaccesshome>\myprimavera.ear Additional Settings for JBoss and WebLogic on Microsoft SQL 2005 Databases The following instructions apply when using Microsoft SQL Server 2005 databases. If the Microsoft SQL Server database is localized or installed on a localized operating system, it is necessary to use the SET DATEFORMAT setting in the P6 Web Access admin.jsp. Otherwise, the user will encounter SQL errors when navigating in Resource Planning and Capacity Analysis. Odd behavior might also occur in the Activities view. 1In the P6 Web Access admin.jsp file (Adminstration Application), locate the Database folder for the Microsoft SQL Server database used by P6 Web Access. 2In that folder, expand the appropriate Instance folder and then the Session Settings folder (choices will be from 1 to 5). 3Use the following syntax to add a Session Setting: set DATEFORMAT ymd 4Save the change. 5Restart the application server, and the change will immediately take effect. Configuring WebSphere 6.1 Changing Java Home for Primavera Administrative BAT files
After installing P6 Web Access, you must change JAVA_HOME in the following files: dbconfigpv.cmd and adminpv.cmd. They are found in the home directory of P6 Web Access.

1Open the dbconfigpv.cmd and adminpv.cmd files with a text editor. Change the following line in each file, from: set JAVA_HOME=C:\DOCUME~1\ADMINI~1\LOCALS~1\ Temp.... to: set JAVA_HOME=<WEBSPHERE INSTALL DIRECTORY>\ AppServer\java\bin 2Execute the dbconfigpv.cmd and create a new database connection as described in Installation Process for P6 Web Access on page 130.

Installation on Windows
These steps should be performed immediately after installing P6 Web Access.

1Start the WebSphere Application Server. 2Launch the WebSphere Application Server Administrative Console. 3In the left-hand navigation pane, expand Servers and click Application Servers. 4On the Application Servers screen, click the server name link. 5On the Configuration tab, under Server Infrastructure, expand Java and Process Management. 6Click Process Definition. 7Under Additional Properties, click Java Virtual Machine. 8Under Generic JVM arguments, type: -Dprimavera.bootstrap.home=c:\<p6webaccesshome> 9Click OK. Click the Save link that appears within the message reporting changes. 10In the left-hand navigation pane, expand Applications and click Install New Application. 11Specify the path to the p6webaccesshome folder for P6 Web Access, which contains the myprimavera.ear file. For example: c:\p6webaccesshome\myprimavera.ear. 12For the Context Root, type myprimavera, then click Next. 13On the Choose to generate default bindings and mappings screen, accept the defaults and click Next.
If the Application Security Warnings screen displays, click Continue.

14On the Specify options for installing enterprise applications and modules screens do the following: For Step 1, mark the checkbox for Pre-compile JSPs, and click Next. In the Step 2 section "Install new application", mark the myprimavera checkbox, and click Next. In the Step 3 section "Install new application", mark the myprimavera checkbox, and click Next. On the Step 4 screen (Summary), click Finish. Note that the application EAR file is now deploying and this process might take several minutes. 15To save the master WebSphere configuration, click Save. This process might also take several minutes. 16On the Administrative Console Main screen, in the left-hand navigation, expand Applications and click Enterprise Applications. 17Locate myprimavera and check its application status. If it is not a green arrow, click the Start button above the Select column. 18If necessary, restart the WebSphere application server. Installation on AIX 5.2
The following instructions (step 1 through step 3) are only required for installing P6 Web Access on AIX 5.2.

1To start the P6 Web Access installation from CD, go to a command prompt and change your directory to point to the root of the CD-ROM. The "setupmain.jar" file should be found. 2Type the following command to start the installation: <cdrom_mount> java -jar setupmain.jar
The java executable must be specified in the system path.

3Follow the steps in the Installation on Windows section. Using Sun JCP Provider in the WebSphere Runtime 1Download Sun JCE: jce-1_2_2.zip. 2Unzip the download file. The default folder is folder like c:\jce1.2.2 with subdirectories doc and lib. 3The lib subdirectory contains the following JCE framework: jce1_2_2.jar local_policy.jar sunjce_provider.jar US_export_policy.jar Copy the files to your WebSphere install folder's %javahome%\jre\lib\ext folder. For example: C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\ext 4Edit the java.security file located in %javahome%\jre\lib\security. For example: C:\Program Files\IBM\WebSphere\AppServer\java\jre\lib\security After the following lines: security.provider.1=com.ibm.crypto.provider.IBMJCE security.provider.2=com.ibm.jsse.IBMJSSEProvider security.provider.3=com.ibm.jsse2.IBMJSSEProvider2 security.provider.4=com.ibm.security.jgss.IBMJGSSProvider security.provider.5=com.ibm.security.cert.IBMCertPath security.provider.6=com.ibm.crypto.pkcs11.provider.IBMPKCS11 security.provider.7=com.ibm.security.cmskeystore.CMSProvider security.provider.8=com.ibm.security.jgss.mech.spnego.IBMSPNEGO append: security.provider.9=com.sun.crypto.provider.SunJCE
You might need adjust the number based on your configuration, or you can simply replace: security.provider.1=com.ibm.crypto.provider.IBMJCE with: security.provider.1=com.sun.crypto.provider.SunJCE

Starting the Server for P6 Web Access

The following procedures assume you have installed P6 Web Access into a supported application server and completed the additional steps outlined in Configuring and Deploying the Application Server for P6 Web Access on page 133. Starting the Server for P6 Web Access on JBoss
On On

Windows, double-click the startmyPVinJoss.bat file that was created in step 8 on page 134. Linux, open a terminal and enter the following commands:

cd /<JBOSS INSTALL LOCATION>/bin ./run.sh -c myprimavera

Starting the Server for P6 Web Access on WebLogic

On

Windows, from the Start menu, navigate to the BEA WebLogic submenu, then choose User Projects, <domain>, Start Server. When prompted for a user name and password in the WebLogic console window, type in the admin user name and password you specified when creating the domain.
On

Solaris and HP-UX, change to the <bea_home>/user_projects/<domain> directory and run the startWebLogic.sh script. When prompted for a user name and password in the WebLogic console window, type in the admin user name and password you specified when creating the domain.
If P6 Web Access is installed as an application, and the WebLogic precompile option has been turned on, the WebLogic console displays Server started in RUNNING mode when precompiling has completed. For information about turning on precompilation, see your WebLogic Server documentation.

Starting the Server for P6 Web Access on WebSphere Advanced Server

On

Windows, Linux, and AIX, from the WebSphere administrative console, start the myPrimavera module. myPrimavera is the default module name assigned during installation.

Stopping the Server for P6 Web Access

Stopping the Server on JBoss From the Windows Command prompt, press Ctrl+c. Stopping the Server on WebLogic On Windows and Solaris, in the WebLogic terminal console, press Ctrl+c. Stopping the Server on WebSphere Advanced Server On Windows, Linux, and AIX, from the WebSphere administrative console, stop the myPrimavera module. myPrimavera is the default module name assigned during installation.

Accessing P6 Web Access from Client Browsers

To select authentication mode for P6 Web Access, use the Authentication Configuration wizard (LDAPCfgWiz.exe, located in the \install\ database\ldap-config folder on CD 1). Also, specify the configuration settings for P6 Web Access that are required for authentication. For details on the Configuration wizard, see Configuring Authentication Modes on page 323. For information about authentication configuration settings, see Configure Authentication on page 161.

Users can access P6 Web Access from client browsers using the following URL structure, depending on the application server platform. On a JBoss application server http://serverIP:listenport/ContextRoot/login_it Example: http://192.168.0.1:8080/myprimavera/login_it The default listenport is 8080. The default context root is myprimavera.

On a WebLogic application server http://serverIP:listenport/ContextRoot/login_it Example: http://192.168.0.1:7001/myprimavera/login_it The default listenport for new WebLogic domains is 7001. The default context root is myprimavera. On a WebSphere application server http://serverIP:listenport/ContextRoot/login_it Example: http://192.168.0.1:9080/myprimavera/login_itcmt The default listenport is 9080. The default context root is myprimavera.
The context root is configurable on all supported application servers. For information about context root configuration, refer to your application server documentation. Also, URLs might be case-sensitive, depending on your application server configuration.

Configuration Settings on Client Browsers

Setting Change to Resolve Export to Excel Issue When clicking on a link to export to Excel, users might experience a lack of response (no Open/Save dialog box launches) from P6 Web Access if Internet Explorer is not configured properly. If this occurs, do the following on each client machine experiencing the issue: 1From the Windows Control Panel, select Internet Options. 2Click on Trusted Sites. 3Click on the Sites button and add your P6 Web Access URL to the zone.

4Close the Sites window. 5Click on the Custom level button.

6Enable the setting, Automatic prompting for file downloads.

Setting Change to Resolve Null Pointer Exceptions Users might receive null pointer exceptions if a large number of activity code values (40,000 or more) are loaded when using P6 Web Access. If so, do the following on every client machine where the P6 Web Access module is being used: 1From the Windows Control Panel, select Java. 2On the Java Control Panel, select the Java tab. 3On the Java tab, under Java Applet Runtime Settings, click View.

4On the Java Runtime Settings screen, in the JRE/1.6.0.03 row, add -Xms<value>m and -Xmx<value>m entries in the Java Runtime Parameters field.

The appropriate values will vary with your configuration; however, we recommend the following values as a starting point: -Xms128m -Xmx128m

5Exit the Java Control Panel.

Changing Database Configuration Settings

The Database Configuration wizard enables you to change the database connection settings you specified when you installed P6 Web Access. The database you select during installation stores one or more Primavera configurations, each one specifying a set of configurable parameters that determine how P6 Web Access operates. During installation, you select an existing Primavera configuration or create a new one. Later, you can use the Database Configuration wizard to select a different Primavera configuration or create a new one.
After selecting a different P6 configuration or creating a new configuration, you must stop and restart the application server for P6 Web Access in order for the changes to take effect.

Starting the Database Configuration wizard on JBoss From the Start menu, choose Programs, myPrimavera, Database Configuration Setup. Starting the Database Configuration wizard on WebLogic
On

Windows, run dbconfigpv.cmd (located in the <P6_Web_Access_home> directory you specified when setting up P6 Web Access), or choose Start, Programs, myPrimavera, Database Configuration Setup.
On

Solaris and HP-UX, change to the <P6_Web_Access_home> directory you specified when setting up P6 Web Access, and run dbconfigpv.sh. Starting the Database Configuration wizard on WebSphere
On

Windows, run dbconfigpv.cmd (located in the <P6_Web_Access_home> directory you specified when setting up P6 Web Access), or choose Start, Programs, myPrimavera, Database Configuration Setup.
On

Linux and IBM AIX, change to the <P6_Web_Access_home> directory under the WebSphere install directory and run dbconfigpv.sh.

Using the Administration Application

As the system administrator, you can use the Administration Application of P6 Web Access to review, modify, add, and delete Primavera configurations. Primavera configurations are stored in the database for P6 Web Access, which you specified during installation. These configurations contain all of the settings used to run the Application Server for P6 Web Access.
Only experienced administrators should use the Administration Application to modify configuration settings.

Starting the Administration Application

You can run the Administration Application of P6 Web Access locally or remotely through a browser. After launching the Administration Application, you will be prompted for a database level user name and password. The default PMDB database-level user name and password are privuser. This is case-sensitive, and is all lowercase letters. Starting the Administration Application on JBoss

Run adminpv.cmd (located in the <P6_Web_Access_home> directory you specified when setting up P6 Web Access, or choose Start, Programs, myPrimavera, Administration Application.
The installation for P6 Web Access sets the default URLs for remote access to the Administration Application. You can use the application servers configuration utility to change the listen port number and context root.

Starting the Administration Application on WebLogic

On

Windows, run adminpv.cmd (located in the <P6_Web_Access_home> directory you specified when setting up P6 Web Access, or choose Start, Programs, myPrimavera, Administration Application.
On

Solaris and HP-UX, to launch the Administration Application locally, change to the <P6_Web_Access_home> directory you specified when setting up P6 Web Access, then run the adminpv.sh script.
To

launch the Administration Application remotely, launch a browser and navigate to http://server IP:listenport/ContextRoot/admin.jsp, where serverIP:listenport is the IP address and listen port for the server of P6 Web Access. The default context root is myprimavera. Starting the Administration Application on WebSphere
On

Windows, run adminpv.cmd (located in the <P6_Web_Access_home> directory you specified when setting up P6 Web Access, or choose Start, Programs, myPrimavera, Administration Application.
On

Linux and IBM AIX, to launch the Administration Application locally, change to the <myPrimavera_home> directory under the WebSphere install directory and run the adminpv.sh script .
To

launch the Administration Application remotely, launch a browser and navigate to http://server IP:listenport/ContextRoot/admin.jsp, where serverIP:listenport is the IP address and listen port for the server of P6 Web Access. The default context root is myprimavera.

Reviewing and Modifying Configurations for P6 Web Access

The Administration Application of P6 Web Access presents configuration settings in a tabbed dialog box. Tree view and Table view display the current configurations and settings. Log displays a history of configuration changes, additions, or deletions.
You cannot edit the Factory Default configuration settings. You can only modify custom configurations.

To display brief setting descriptions in Tree or Table view, mark the Show tool tips checkbox. Then, position the mouse over a setting to read the popup description.
Configurations highlighted in red are out of date. Primavera recommends that you delete these configurations.

Add configurations for P6 Web Access To create a new configuration, you can duplicate an existing configuration.
To

duplicate a configuration, select the configuration name in Tree View, then right-click and choose Duplicate. Enter a name for the configuration, then click OK. Edit the settings as needed.
To

create a new configuration based on factory default settings, right-click on Factory Defaults in Tree View and choose Duplicate. Add database instances to a configuration To add a new database instance to a configuration, you can duplicate an existing instance.
To

duplicate a database instance, select the icon representing the instance, then right-click and choose Duplicate. Enter

a unique name for the new instance and edit other settings as needed. Delete configurations and database instances for P6 Web Access To delete a configuration or database instance, select it, then right-click and choose Delete. You cannot delete the Factory Defaults configuration. You can delete any custom configuration, but not all of them. There must always be at least one custom configuration. You can delete any database instance associated with a configuration, but not all of them. Each configuration must have at least one database instance.
You are not prohibited from deleting the database that was specified during the database configuration. If you do so, you will need to run the Database Configuration wizard again (see Changing Database Configuration Settings on page 152).

Configure P6 Web Access to run the Project Architect job service To run the Project Architect job service in P6 Web Access, you must modify the appropriate P6 Web Access configuration to connect the project management database associated with the job service to the methodology management DB Alias specified on the job service machine. Complete the following steps to configure P6 Web Access to run the Project Architect job service:
If a methodology management DB Alias does not exist on the machine on which you installed the job service, you must use the Database Configuration wizard to create or select one. If a methodology management DB Alias already exists on the job service machine, skip step 1 in the following procedure.
For information on installing and configuring the job service, refer to Installing the Job Service and Distributed Job Service on page 287.

These instructions assume you have already installed the Job Service.

1If necessary, on the job service machine, run the Database Configuration wizard to create or select a methodology management DB Alias that connects the job service machine to the methodology management database you want to associate with P6 Web Access. For instructions on configuring database connections, refer to Changing Database Connection Settings on page 318. 2Launch the Administration Application. For instructions on launching the Administration Application, refer to Starting the Administration Application on page 154. 3In the Tree View, underneath the appropriate Primavera Configuration, navigate to the following location: Database/Instance/MethodologyManagement. 4In the Methodology Management folder, modify the URL so that it points to the same methodology management database you specified in step 1. 5Modify the DBAlias value to match the DB Alias of the methodology management database you specified in step 1.

Manage access to multiple database instances P6 Web Access enables you to access data from different project management databases. When you configure P6 Web Access to support multiple database instances, the Login page displays a Database drop-down list that enables users to choose the database instance they want to connect to. Through the Administration Application, you can configure the server for P6 Web Access to manage user access to specific databases by requiring a database parameter in the URL. The database parameter, which is the name of a database instance, is appended to the P6 Web Access server URL and points to that specific database instance. When users access the URL you

specify, the Database drop-down list does not display in the Login page and they have login access only to the database instance defined by the database parameter. If users attempt to access the login page URL without specifying the required database parameter, a message displays to indicate that the URL is invalid and directs them to the administrator of P6 Web Access. For example, the following URL would log a user into the database instance named Sample. http://serverIP:listenport/login_it?db=Sample As the administrator, you can specify a keyword that bypasses the database parameter requirement, so that you can access all databases through the Login page database drop-down list. To require a database parameter with the URL for P6 Web Access 1Launch the Administration Application. 2Under the configuration you want to modify, specify a value for the setting Application.DBDropdownKeyword. Specifying a value adds the database parameter requirement to the server URL. Use the value you specify as the keyword to bypass the database requirement when logging in to the server for P6 Web Access. For example, http://serverIP:listenport/login_it?db=bypass
For more information, see Database.Instance.Driver and Database.Instance.URL in Configuration Settings for P6 Web Access on page 163.

Database driver configurations The following table lists the database drivers that P6 Web Access supports for each application server/database configuration. Use the Database.Instance.Driver configuration setting to specify the database driver you are using. Application Server
JBoss JBoss WebLogic WebLogic WebSphere WebSphere

Database Type
Oracle SQL Server Oracle SQL Server Oracle SQL Server

Database Driver
Oracle Thin Client SQL Server 2005 JDBC Oracle Thin Client SQL Server 2005 JDBC Oracle Thin Client SQL Server 2005 JDBC

Defau lt
Y Y Y Y Y Y

Configure Authentication P6 Web Access uses up to six configuration settings to support authentication.
Authentication.Mode Authentication.WebSSO.UserNameHeaderKey Authentication.WebSSO.ContextPathOverride Authentication.WebSSO.ServerandPortOverride Authentication.LDAP.SSLCertificateStore Authentication.LDAP.SSLStorePassword

The Authentication.Mode settings must match the mode selected for Group Server.

Because one server instance of P6 Web Access might control more than one database, in addition to specifying an authentication mode through the LDAP Configuration wizard, you use the new Authentication.Mode configuration setting to specify the overall mode you want to use for the server of P6 Web Access. If using Single Sign-On, you will also need to modify three additional configuration settings required for the policy server. For LDAP authentication with secure communication (SSL) between P6 Web Access and the LDAP server, two additional configuration settings are required. For more information about each of these settings, refer to the Authentication Settings subsection in the next section, Configuration Settings for P6 Web Access.
A configuration for P6 Web Access might include database instances that are not set to the same authentication mode as the server of P6 Web Access. If a user connects and requests a database that is set to a different authentication mode than the server of P6 Web Access, an error message displays. The user must select a database that matches the authentication mode set for the server of P6 Web Access.

Configuring custom portlets In the Personal Workspace and Project Workspace of P6 Web Access, you can create custom portlets that pass the password of the currently logged on user to the target application. By default, the password is not encrypted. You can use the new Application.CustomPortletURLUserInfoEncryptionKey configuration setting to encrypt the password. This encryption uses the Bouncy Castle/Blowfish algorithm. For more information about this setting, refer to the Application Settings subsection in the next section, Configuration Settings for P6 Web Access.
You must update your configuration for this setting to appear. To do so, highlight the configuration, right-click, and select Update to latest version.

Configuration Settings for P6 Web Access

You can review and modify configuration settings in the Administration Application Tree View or Table View. Configuration settings are stored in the database for P6 Web Access, which you specified during installation. You can specify durations (time-related values) in several ways:
As

a simple number, which is treated as milliseconds. For example, 240000 would be equivalent to 4 minutes (240000/60000).

In

the form <n>d<n>h<n>m<n>s, where d is days, h is hours, m is minutes, and s is seconds. All parts are optional. For example, you can enter: 1d2h30m20s 4m 1h30s
Only experienced administrators should use the Administration Application of P6 Web Access to modify configuration settings.

[Localization Settings] Setting Name and Description

Localization/System Language Language for server string constants

Default
en

Valid Ranges/Values

Localization/System Country Country for server string constants

US

[Authentication Settings] Setting Name and Description

Authentication/Mode The method used for client authentication. Authentication/Web Single Sign-On/User Name Header Key The name of the http header you specified in SiteMinder. The value you specify must match the property of a SiteMinder response you have created under the policy domain/realm within which the Web server for P6 Web Access resides. The value of this response should be smuser=uid, where smuser is configurable and uid matches the LDAP server attribute that maps to the Primavera database USER_Name field. Authentication/Web Single Sign-On/Context Path Override The path used to pass web requests from the SiteMinder Web server to the server of P6 Web Access. Authentication/Web Single Sign-On/Server and Port Override The fully qualified domain name and port for the Web server that SiteMinder is controlling. Authentication/LDAP/SSL Certificate Store The full path to the keystore that holds the SSL certificate for the LDAP server. Authentication/LDAP/SSL Store Password The password for the keystore that holds the SSL certificate. /Primavera

Default
NATIVE smuser

Valid Ranges/Values
Native, LDAP, WebSSO

http://servername.do main.com:82

[Database Settings] Setting Name and Description

Database/Instance/Name The name of this database instance. Database/Instance/Description A description of this database instance. Database/Instance/Schema The schema that will be defined for the database. Database/Instance/Driver The class name of the JDBC driver.

Default
PMDB

Valid Ranges/Values
up to 32 characters up to 128 characters com.microsoft.sqlserver.jdbc. SQLServerDriver oracle.jdbc.driver.OracleDriver

Database/Instance/URL The database URL used to establish a connection to the database. Oracle example: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST =(ADDRESS=(PROTOCOL=TCP) (HOST=xx.xxx.xxx.xx)(PORT=yyyy))) (CONNECT_DATA=(SID=zzzz))) Oracle short form example: jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz SQL example: jdbc:sqlserver://xxxx:yyyy;database=zzzz x = SQLServer IP address or hostname y = database listen port z = database name Database/Instance/Public Group ID The public group ID used to establish a connection to the database. Database/Instance/User Name The name used to establish a connection to the database. Database/Instance/Password The password used to establish a connection to the database. Database/Instance/Collaboration Domain The collaboration domain name used by P6 Web Access. Database/Instance/Connection Pool [aaa]/Resize Rate The timeout period after which the system will adjust the number of database connections to be equal to the maximum number of database connections concurrently used during the last period. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/ Maintenance Frequency The run frequency of the maintenance that ensures leases have not exceeded the maximum duration. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested.

pubuser pubuser

4m

4m - 12h

1m

10s - 1h

Database/Instance/Connection Pool [aaa]/ Lease Request Wait Timeout The amount of time a request for a database connection will wait. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/ Maximum Connections The maximum number of connections the server will have to the database. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/Fetch Size A hint to the database driver for how many rows to fetch at a time. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/Trace SQL Trace all SQL sent to the database. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested.

30s

5s - 2h

50

5 - 15000

120

false

true/false

Database/Instance/Connection Pool [aaa]/ Renewable Free Limit The minimum number of connections that should be available for leases to be renewed. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/ Renewable Leases If false, each connection can be leased only for the MaxLeaseDuration period. If true, connection leases are renewed if database statements are completed within the MaxLeaseDuration time period. When true, the code can hold onto the connection as long as it needs, provided SQL statements are completed within the MaxLeaseDuration period. When true, the connection is revoked if no SQL statements are issued within the MaxLeaseDuration period or if one statement takes longer to execute than that period. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Connection Pool [aaa]/ Maximum Lease Duration The maximum amount of time a database connection can be leased before it is revoked. [PMR] Used for the standard connection pool, which is the most frequently used connection pool in the Business Rule Engine. [PML] Used for the long running connection pool, which is used in the Business Rule Engine when scheduling long running jobs. [PMT] Used for the transactional connection pool, which is used in the Business Rule Engine when a client transaction is requested. Database/Instance/Group Server/Protocol Protocol for GroupServer Database/Instance/Group Server/Server GroupServer host machine name Database/Instance/Group Server/Port GroupServer host listen port Database/Instance/Group Server/URL GroupServer servlet URL.

3-5

PMR - false PML - false PMT - true

true/false

PMR - 2m PML - 10m PMT - 10m

PMR - 5s - 4h PML - 5s - 6h PMT - 5s - 6h

socket servername 9002 http://serverna me

http, https, socket

Database/Instance/Methodology Management/Name Name of this database instance. Database/Instance/Methodology Management/ Description Description of this database instance. Database/Instance/Methodology Management/Driver Class name of the JDBC driver. Database/Instance/Methodology Management/URL Database URL used to establish a connection to the database. Oracle example: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST =(ADDRESS=(PROTOCOL=TCP) (HOST=xx.xxx.xxx.xx)(PORT=yyyy))) (CONNECT_DATA=(SID=zzzz))) Oracle short form example: jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz SQL example: jdbc:sqlserver://xxxx:yyyy;database=zzzz x = SQLServer IP address or hostname y = database listen port z = database name Database/Instance/Methodology Management/User Name The name used to establish a connection to the database. Database/Instance/Methodology Management/Password The password used to establish a connection to the database. Database/Instance/Methodology Management/ Public Group ID The Group ID used to establish a connection to the database. Database/Instance/Methodology Management/ Database Alias The DB Alias name used by the Project Architect job service to create a project plan from a methodology. Database/Instance/Methodology Management/ Connection Pool [MMR]/Resize Rate The timeout period after which the system will adjust the number of database connections to be equal to the maximum number of database connections concurrently used during the last period. Database/Instance/Methodology Management/ Connection Pool [MMR]/Maintenance Frequency The run frequency of the maintenance that ensures leases have not exceeded the maximum duration.

oracle.jdbc.dri ver.OracleDri ver

com.microsoft.sqlserver.jdbc. SQLServerDriver oracle.jdbc.driver.OracleDriver

MMDB

4m

4m - 12h

1m

10s - 1h

Database/Instance/Methodology Management/ Connection Pool [MMR]/Lease Request Wait Timeout The amount of time a request for a database connection will wait. Database/Instance/Methodology Management/ Connection Pool [MMR]/Maximum Connections The maximum number of connections the server will have to the database. Database/Instance/Methodology Management/ Connection Pool [MMR]/Fetch Size A hint to the database driver for how many rows to fetch at a time. Database/Instance/Methodology Management/ Connection Pool [MMR]/Trace SQL Trace all SQL sent to the database. Database/Instance/Methodology Management/ Connection Pool [MMR]/Renewable Free Limit The minimum number of connections that should be available for leases to be renewed. Database/Instance/Methodology Management/ Connection Pool [MMR]/Renewable Leases If false, each connection can be leased only for the MaxLeaseDuration period. If true, connection leases are renewed if database statements are completed within the MaxLeaseDuration time period. When true, the code can hold onto the connection as long as it needs, provided SQL statements are completed within the MaxLeaseDuration period. When true, the connection is revoked if no SQL statements are issued within the MaxLeaseDuration period or if one statement takes longer to execute than that period. Database/Instance/Methodology Management/ Connection Pool [MMR]/Maximum Lease Duration The maximum amount of time a database connection can be leased before it is revoked. Database/Instance/Session Settings/Setting 1-5 Alter session commands used to establish cursor sharing, rule-based mode, SQL trace, and more. Invalid settings in these fields are ignored. Database/Instance/Cost Based Optimization Settings/ Enable Enable Cost Based Optimization if true. Database/Instance/Cost Based Optimization Settings/ Log File Name The CBO SQL log file name created in Primavera Home. Database/Instance/Cost Based Optimization Settings/ Dump Matching SQL Set to true to dump the SQL where a match is found in the QUERYLIB table for a given SQL statement. Set to false to dump the SQL where a match is not found in the QUERYLIB table for a given SQL statement.

30s

5s - 2h

50

5 - 15000

120

false

true/false

3-5

false

true/false

2m

5s - 4h

alter session set _ = _

false

true/false

false

true/false

[Thread Pool Settings] Setting Name and Description

Thread Pool/Number of Threads The number of server threads. Thread Pool/Maximum Task Duration The maximum duration a thread can be used for one task. Thread Pool/Maximum Long Running Task Duration The maximum duration a thread can be used for a long running task. Thread Pool/Maintenance Frequency The frequency at which threads are checked for excess time durations.

Default
25 3m 5m

Valid Ranges/Values
2-300 10s - 24d 10s - 24d

45s

15s - 24d

[Log Settings] Setting Name and Description

Log/Console Logger/Severity Level Log severity level for the Console Logger. The ranges are inclusive. For example, choose debug to log all messages; choose warning to log both warning and error level messages. Log/Console Logger/Enabled Enable the Console Logger Log/File Logger/Archive Size The minimum size (in bytes) a log file must be before it is archived. Log/File Logger/Severity Level Log severity level for the HTML Logger. The ranges are inclusive. For example, choose debug to log all messages; choose warning to log both warning and error level messages. Log/File Logger/Number of Archive Files Maximum number of log files to be used. The default files are named myprimaveralog0.html through myprimaveralog5.html. Log/File Logger/HTML Log as HTML. 6 2 - 2073600000 false 1048576 true/false 1042 - 2073600000

Default
error

Valid Ranges/Values
debug, info, warning, error

error

debug, info, warning, error

true

true/false

Log/File Logger/Enabled Enable the HTML Logger. Log files are created in a folder named myPrimaveraLogs, located as follows: JBoss on Windows: <pvhome>\myPrimaveraLogs JBoss on Solaris: /mount_point/<pvhome>/myPrimaveraLogs JBoss on Red Hat Enterprise Linux: /mount_point/<pvhome>/AppServer/ WebLogic on Windows: <pvhome>\myPrimaveraLogs WebLogic on Solaris: /mount_point/<pvhome>/myPrimaveraLogs WebSphere on Windows: <pvhome>\myPrimaveraLogs WebSphere on Red Hat Enterprise Linux: /mount_point/WebSphere/AppServer/myPrimaveraLogs Log/Email Logger/SMTP Port SMTP server that will send the email message. Log/Email Logger/From Email Address Set to the email address from which you would like log messages sent. Log/Email Logger/To Email Address Set to the email address to which you would like log messages sent. Log/Email Logger/Email subject The default Email subject. Log/Email Logger/Enabled Enable the Email logger. Log/Asynchronous Log messages asynchronously for better performance.

true

true/false

Joe User <joeuser@ uninitabc123z.com>

P6 Web Access error false true

true/false true/false

[Collaboration Server Settings] Setting Name and Description Default Valid Ranges/Values

Collaboration Server/Server Name Hostname of the collaboration server of P6 Web Access. Collaboration Server/Library Name The name of the database where library data resides. Collaboration Server/Collaboration Workspace Name The default collaboration workspace name. Collaboration Server/Initiation Workspace Name The default initiation workspace name. Collaboration Server/Application Name The default app name used by P6 Web Access.

PrimaveraRootContain er primavera_initiations primaveraApp

Collaboration Server/Pool Size The number of collaboration connections initialized. Collaboration Server/Pool User Name The name used to start the connection pool. Collaboration Server/Pool User Password Password for the user name used to start the connection pool. Collaboration Server/Admin User Name The Admin user with full privileges. Collaboration Server/Admin User Password The password of the admin user. Collaboration Server/Cache User Name The user name that enables P6 Web Access to access the application cache. Collaboration Server/Cache User Password The password that corresponds to the CacheUserName. Collaboration Server/Cache Limit The maximum number of CMS objects that are kept in the application cache. Collaboration Server/Strict Document Versioning If true, document checkout is restricted to the most recent version of a document. If false, any document version can be checked out.

20 PROXYUSER proxyuser

0 - 2147483647

Admin admin CACHEMANAGER

cachemanager 1000

0 - 2147483647

true

true/false

[Application Settings] Setting Name and Description

Application/Prototype User Prototype user login used to create and store default Dashboards and Global Preference settings for new P6 Web Access users. Application/Ignore Daylight Savings Time Set to false to account for daylight savings time. Application/Timesheet URL URL for invoking timesheet program Application/Timesheet Codebase URL for the timesheet application Web site Application/Internet Explorer Java Plugin URL URL for Internet Explorer users to download Java Plug-in (JRE). Application/Internet Explorer Java Plugin Version JRE version used by applets in Internet Explorer Application/Maximum Transactions for Excel Import The maximum number of transactions (activities or resources) that can be imported at once from a .xls or .csv file

Default

Valid Ranges/Values

true / action/launchTimeshee tSeemlessly server/GroupServer Defaults to the plug-in version 1.6.0_03 that is installed during setup. 2000

true/false

100 - 2000

Application/Maximum Excel Import File Size The maximum size of the .xls or .csv file uploaded during an import attempt (KB) Application/Allow Auto-Summarize Option Set to true to allow automatic summarization to be available in resource staffing user preferences. Application/Database Dropdown Key Keyword to use for enabling database selection control in the login page. Pass this as a URL parameter db=keyword. Set this to an empty string if you do not want to require the keyword. Application/Logout URL Directs P6 Web Access to a specific URL when the user exits with the Logout/Close icon in the banner of P6 Web Access. Any valid URL can be used. If no URL is specified, P6 Web Access directs the user to the launch page of P6 Web Access. Application/Compress Applet Communication Set to true to compress communication between applets and the server. Application/Compress HTML Content Set to true to compress HTML-related content generated by P6 Web Access, including .html, .js, and css files, and Ajax content. Application/Maximum Projects in Portfolio The maximum number of projects returned when creating a portfolio with a filter. Application/Maximum Loaded Resource Planning Projects The maximum number of projects that can be open in the Resource Planning spreadsheet. Application/Maximum Portlets per Dashboard The maximum number of portlets that can be displayed in a dashboard on the Dashboards Home page. Application/Maximum Projects per Portfolio View The maximum number of projects that can be displayed in a portfolio view on the Portfolio Analysis tab and in Portfolio View portlets on dashboards. Application/Maximum Activities per Activity View The maximum number of activities that can be displayed in the Activities tab of the Projects section. Application/Maximum MRU List Items The maximum number of items that can be displayed in a Most Recently Used (MRU) list. Application/Maximum Project Activity Codes The maximum number of projects that can be selected and displayed in the Projects tab of the Activity Codes section. Application/Maximum Activity Code Values The maximum number of activity code values that can be created or selected per Activity Code.

1048

64 - 4096

true

true/false

blank

true

true/false

true

true/false

1000

1 - 100000

100

1 - 1000

12

1 - 50

5000

1 - 20000

2000

1 - 5000

1 - 10

350

1-350

100000

1-1m

Application/Custom Portlet URL Encryption Key Encryption key for custom portlet user password. Assigning a key causes the password that is passed as part of the URL for a custom portlet to be encrypted. If you do not assign a value, the password is not encrypted. The value can be any alphanumeric character or string of characters. This encryption uses the Bouncy Castle/Blowfish algorithm. Application/Transaction Monitor Execution Interval The frequency at which the transaction monitor job runs, which ensures transactions have not bee orphaned. Application/Notifications/Enable Issue Notifications Enable or disable automated notifications when Issues are added or modified. Application/Notifications/Enable Event Notifications Enable or disable automated notifications when Events are added or modified. Application/Notifications/Enable Invitation Notifications Enable or disable automated notifications when Invitations are added. Application/Notifications/Enable Initiation Notifications Enable or disable automated notifications when Invitations are pending. Application/Notifications/Override Notification Email from User Set to true to always use the systems From email address. Set to false to use the email address of the user who causes notifications to be sent, if their email address is configured. Application/Notifications/Notification from Email User The email address from which Notifications will be sent when either NotificationsFromEmailOverride is true or the users email address is not configured

10m

1s 24d20h31m23s647 true/false

false

false

true/false

false

true/false

false

true/false

false

true/false

Joe User <joeuser@ uninitabc123z.com>

[Services Settings] Setting Name and Description

Services/License Service/Recalculate Rate The rate at which the database is checked for changes in total license counts. Services/License Service/Update Rate The rate at which a Business Rule Engine synchronizes with the database for license counts. Services/License Service/Expiration Check Rate The rate at which licenses are checked to see if they should expire.

Default
5m

Valid Ranges/Values
10s - 10m

30s

100 - 1m

2m

500 - 15m

Services/Timestamp Service/Refresh Rate The rate at which the database is queried to determine if a table change notification is necessary. Services/Registry Service/Refresh Rate The rate at which the database is updated with the status of the Business Rule Engine. Services/Registry Service/Stale Period The duration of inactivity that indicates an inoperable Business Rule Engine. Services/Registry Service/Port The TCP/IP port on which requests to revive dead Business Rule Engines will be received. Services/Next Key Service/Refresh Rate The rate at which nextkey cache is refreshed. Services/Next Key Service/Maximum Cached Keys Maximum nextkeys to cache per table Services/Performance/Use Enterprise Summary Use enterprise level summary data for resources and roles. This setting specifies whether you want to use EPS level records or Project level records to draw Resource Manager histograms. If true, performance is better because only one record (EPS record) is used for the histogram. If false, a much larger number of records (Project records) is used to draw the histogram chart, so performance is slower. However, it is important to note that histogram data is more accurate when the setting is false, using Project records. Services/Performance/Maximum Summary Node Count The threshold for displaying summarized data in views such as Resource Usage and Resource Analysis. If the number of child elements contained in a node exceeds this number, no data is displayed. Services/Web Scheduler/Enabled If true, scheduling for jobs from P6 Web Access is performed using the Web Scheduler. If false, scheduling is performed using the Job Service Scheduler. Services/Web Scheduler/Scheduling Interval Amount of time the Web Scheduler will wait before scheduling the next available job. Services/Web Scheduler/Concurrent Schedulers The number of processes (active schedulers) used for scheduling on this server. A value of 0 (zero) indicates that scheduling will not be performed on this server. Services/Web Scheduler/Active Scheduler Mode If true, jobs are processed continuously until all jobs are scheduled. If false, each job is processed according to the Scheduling Interval. Services/Web Scheduler/ASAP Cleanup Rate Amount of time at which completed WebASAP scheduler jobs are removed from the database.

1m

15s - 1h

1m30s

15s - 1h

4m

1m - 10m

9192

1024 - 65535

1m 10 false

15s - 1h 1 - 100 true/false

1000

1-50000

true

true/false

5m

1s - 24d20h31m23s647

0-20

true

true/false

1d

1h 24d20h31m23s647

Services/Store Period Performance/Enabled Service for storing period performance. If true, ThisPeriod values are stored in the specified financial period. Services/Store Period Performance/Execution Interval Amount of time the service will wait before checking for any period performance jobs. Services/Store Period Performance/Concurrent Tasks The number of processes used for the PeriodPerformance service on this server. A value of 0 (zero) indicates that the service is not available on this server. Services/Sync Actual This Period/Enabled Service for synchronizing actuals and ActualThisPeriod values. If true, recalculates actual units and costs for ThisPeriod. Services/Sync Actual This Period/Execution Interval Amount of time the service will wait before checking for any SyncActualThisPeriod jobs. Services/Sync Actual This Period/Concurrent Tasks The number of processes used for the SyncActualThisPeriod service on this server. A value of 0 (zero) indicates that the service is not available on this server. Services/Project Hierarchy Cache/Cache Policy The cache policy to use. The cache policy determines how much data is in the cache and which data is removed to reclaim memory. The allowable values are: FIFO (First In First Out-projects are cleared from the cache in the same order they were added to memory) LRU (Least Recently Used projects are cleared from the cache before more recently used ones) JVMM (Java Virtual Machine Managed-uses soft references to cached elements; memory used by soft references is reclaimed by the JVM as required) PRR (Projects are selected at random to be cleared from cache) PRFIFO (Periodic Refresh First In First Out-same as FIFO, except policy is enforced based on MaintenanceFrequency) PRLRU (Periodic Refresh Least Recently Used-same as LRU, except policy is enforced based on MaintenanceFrequency) PRCC (Periodic Refresh Clear Cache-ignores CacheLimit to flush the entire cache, based on MaitenanceFrequency) Services/Project Hierarchy Cache/Cache Limit The maximum number of projects stored in memory. Services/Project Hierarchy Cache/Maintenance Frequency The frequency for applying the specified cache policy. Application of the cache policy might result in memory used by the cache to be reclaimed.

true

true/false

5m

1s - 24d20h31m23s647

0 - 20

true

true/false

5m

1s - 24d20h31m23s647

0 - 20

PRR

FIFO, LRU, JVMM, PRR, PRFIFO, PRLRU, PRCC

5000 5h

1000 - 30000 1m - 24d

Services/Collaboration Synchronization Service/ Synchronization Interval The interval at which the collaboration synchronization service will run. The synchronization moves documents marked for deletion to the collaboration server \trash folder. Additionally, other collaboration items (e.g., discussions or issues) that should be removed (e.g., when a project is deleted) are moved to the \trash folder. Documents can then be manually deleted or backed up from the \trash folder. Services/Collaboration Recycler Service/Automatic If true, enables the collaboration recycler service, which purges deleted documents and other collaboration items from the collaboration file server \trash folder. Once the recycler service runs, deleted items will no longer be retrievable from the collaboration server.

1h

1m 24d20h31m23s647

false

true/false

Services/Collaboration Recycler Service/Recycle Interval The interval at which the collaboration recycler service should run. Services/Asynchronous Jobs/Purge Interval The frequency at which long running job records will be removed from the database. Services/Asynchronous Jobs/Grace Time The minimum age of long running job records removed during purge. Services/Mail Service/Email Notification Server Hostname or IP address of the E-mail notification server for Timesheet Approval. Services/Mail Service/SMTP Port The tcp/ip port of the outgoing SMTP server. Services/Mail Service/Send Interval The frequency at which queued mail messages are sent. Services/Mail Service/Maximum Queue Length The maximum size of the mail message queue Services/Mail Service/Authorized User Name The name of the account to use to send mail from this mail server. Services/Mail Service/Authorized User Password The password of the account used to send mail from this mail server.

24d

10m 24d20h31m23s647

1h

0 - 24d20h31m23s647

1d

0 - 24d20h31m23s647

25 1m 250

1 - 65535 0 - 24d20h31m23s647 0 - 2147483647

[Performance Monitor Settings] Setting Name and Description

Performance Monitor/Enabled Performance monitor packets are sent when true.

Default
false

Valid Ranges/Values
true/false

Performance Monitor/Monitor Host The destination IP or machine name for the performance monitor packets Performance Monitor/Monitor Port The destination port for the performance monitor packets Performance Monitor/Update Interval The rate at which the performance monitor packets are sent.

localhost

6990 1s

1024 - 65535 250 - 1m

[Tracer Settings] Setting Name and Description

Tracer/Enabled If true, debugging messages are sent to Tracer application. Tracer/Server Name Hostname or IP address of destination for sending tracer information. Tracer/Port Port to use for Tracer socket connection Tracer/Use Background Send Thread If true, use background thread for sending TCP messages to tracer.

Default
false localhost

Valid Ranges/Values
true/false

9210 true

1024-65535 true/false

[Integration API Server Settings] Setting Name and Description

Integration API server/RMI/Registry Port The port for the RMI Registry. This value is usually set to at least 1024. Integration API server/RMI/Enable The setting that enables the RMI server. Integration API server/RMI/Enable Compression The setting that enables compression service mode. Integration API server/RMI/Enable SSL The setting that enables SSL service mode. Integration API server/RMI/Enable Standard Service The setting that enables Standard service mode. Integration API server/RMI/HTTP Service Enable The setting that enables HTTP tunneling mode. Integration API server/RMI/Enable HTTPS Service The setting that enables secure HTTP (SSL) tunneling mode.

Default
9099

Valid Ranges/Values
1024 - 65535

true true true true false false

true/false true/false true/false true/false true/false true/false

Integration API server/RMI/Compression Service Port The port to use for Compression service mode. A setting of 0 indicates that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port. Integration API Server/RMI/SSL Service Port The port to use for SSL service mode. A setting of 0 indicates that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port. Integration API Server/RMI/Standard Service Port The port to use for Standard service mode. A setting of 0 indicates that any available port will be used. If the server will be accessed across a firewall, you must set this to a specific port. Integration API Server/RMI/HTTP Service Port The port to use for HTTP tunneling mode. A setting of 0 indicates that any available port will be used. Integration API Server/RMI/HTTPS Service Port The port to use for secure HTTP tunneling mode. A setting of 0 indicates that any available port will be used. Integration API Server/Session Timeout The amount of time after which an idle client connection will be terminated.

0 - 65535

0 - 65535

0 - 65535

0 - 65535

0 - 65535

120

1 - 24d

Implementing Application Server Plug-Ins

For a full list of tested configurations for P6 Web Access, refer to the testedcfg.htm file in the \Documentation\ <language>\Technical Documentation\Tested Configurations folder on CD 3.

The JBoss, WebLogic, and WebSphere application servers offer a variety of plug-ins that enable you to configure a Web server front-end other than the one provided with the application server. For procedures on configuring a Web server plugin, refer to the individual application servers documentation.

This chapter describes how to install and configure the collaboration server of P6 Web Access. If you have not previously installed the collaboration server, start with Installing the Collaboration Server for the First Time on page 210. If you have already installed the collaboration server with the 6.0 release of Primaveras Web Application, you need to upgrade your Interwoven WorkSite MP Server from v4.1 Patch B7 (or later) to v5.0 Patch 1. Go to Migrating WorkSite MP Server 4.1 HFB7 to 5.0 Patch 1 on page 202. If you have already installed the collaboration server with the 5.0 release of myPrimavera, you need to upgrade your Interwoven WorkSite MP Server from v3.1 Patch B12 (or later) to v5.0 Patch 1. Proceed to Migrating WorkSite MP Server 3.1 HFB12 to 5.0 Patch 1 on page 188. In this chapter:
Migrating WorkSite MP Server 3.1 HFB12 to 5.0 Patch 1 Migrating WorkSite MP Server 4.1 HFB7 to 5.0 Patch 1

Installing the Collaboration Server for the First Time Creating a Collaboration Configuration for the First Time Configuring P6 Web Access for Collaboration

Collaboration Setup
Migrating WorkSite MP Server 3.1 HFB12 to 5.0 Patch 1
If you had previously installed v3.1 of the collaboration server (i.e., with the 5.0 release of myPrimavera), you need to migrate it to WorkSite MP Server v5.0 Patch 1. Complete all steps below, in the order specified, to migrate from 3.1 HFB12 to 5.0 Patch 1: 1Installing version 4.1 of the Collaboration Server 2Installing version 5.0 of the Collaboration Server 3Migrating data from 3.1 to 4.1 on Windows and Solaris 4Applying the 4.1 HFB7 Update 5Migrating data from 4.1 HFB7 to 5.0 on Windows and Solaris 6Applying Patch 1 for version 5.0 Before you begin the migration, ensure that your current WorkSite MP Server v3.1 version is 3.1.6.8.2. To verify the version, launch the Configuration Manager, click Help, About..., and scroll to the bottom of the window. Installing version 4.1 of the Collaboration Server You will first need to install the 4.1 version of WorkSite MP server before migrating: 1Insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP41\41\WSMP_Server41\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6Select the install location (to use a different location, type the full path or click Choose... and browse to the location).

7Select the Complete Install option.

8Review the details of the pre-installation summary. Click Install to continue or Previous to go back. 9When the installation is complete, click Done to exit the installer. 10Verify that worksitetemp4 exists in the installation location chosen in step 6. Installing version 5.0 of the Collaboration Server

Next, you will need to install the 5.0 version of WorkSite MP Server before migrating: 1If necessary, insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP50\WSMPServer50\Server\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6Select the install location (to use a different location, type the full path or click Choose... and browse to the location).

7Select the Complete Install option.

8Review the details of the pre-installation summary. Click Install to continue or Previous to go back. 9When the installation is complete, click Done to exit the installer.

10Verify that worksitetemp5 exists in the installation location chosen in step 6. Migrating data from 3.1 to 4.1 on Windows and Solaris Next, data from 3.1 will be migrated to 4.1, with the help of a script provided by Primavera, and HFB7 will be installed for version 4.1.
This procedure assumes that the original name of the 3.1 schema, finalschema.dat, has not been altered.

1Make a backup copy of the database and file servers. The default location for 3.1 file servers is c:\worksitemp. 2Open the WorkSite MP 3.1 Configuration Manager and stop all processes, including CMS and Indexer. Disable auto start for all processes, and save the configuration. 3Make a temporary folder on your local drive and name it migrate. For example, c:\migrate. 4Copy all files and folders in the \Collab\Migrate\ folder on the Collaboration DVD (labeled CD 4) to the new temporary folder. 5Locate setmigratevars.bat (or setmigratevars.sh on Solaris) and remove the read-only attribute. 6Edit setmigratevars.bat (or setmigratevars.sh) and fill in the appropriate variable values. Examples are located in the comments section, indicated by lines beginning with rem (or # for Solaris).
Make sure that no spaces exist in the variable entries. Otherwise, execution will fail. For example, if a value of C:\worksitemp\worksiteserver is entered for im3home= via copy/paste, a space may exist at the end of the line. This space will need to be deleted.

7Save setmigratevars.bat (or setmigratevars.sh) and close it. 8Execute the following batch file (shell script for Solaris): Windows: c:\migrate\migrate3to4<database type>.bat

Solaris: ./migrate/migrate3to4.sh For example, the Oracle file in Windows would be c:\migrate\migrate3to4ORA.bat
A log file will not be created automatically. However, the output can be viewed from the console. In order to do so, it is recommended that the DOS screen buffer size (height) be increased to 9000.

9Carefully follow the instructions that appear during the execution. You will be prompted to complete some manual steps during the process. Otherwise, allow the script to run, making sure not to scroll up and down in the console window until the migration has completed.
Disregard the following error messages: log4j:WARN No appenders could be found for logger (java.sql.ImStatementProxy). log4j:WARN Please initialize the log4j system properly.

Refer to the next two sections, Opening the Configuration Manager and Starting CMS and Applying the 4.1 HFB7 Update, for comprehensive details on two of the manual steps.
You can safely exit the execution of the script at any time by press CTRL-C. To restart from a specific step, follow the instructions in the comment section of the script.

Opening the Configuration Manager and Starting CMS During the execution of the migrate3to4<database>.bat (or migrate3to4.sh), you will be prompted to Open the Configuration Manager and start the CMS. 1Open the Configuration Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 4, Configuration Manager Solaris: /worksitemp4/mpserver/bin/unix/imconfigmgr 2To start the CMS, expand the server node in the Configuration Manager, right-click on CMS and select Start. 3Close the Configuration Manager. Applying the 4.1 HFB7 Update During the execution of the migrate3to4<database>.bat (or migrate3to4.sh), you will also be prompted to apply the HFB7 Hotfix.
For more detailed HFB7 installation instructions and considerations, refer to the WSMPRelNotes41_SP1_B7.pdf file in the \Collab\WSMP41\docs folder on the Collaboration DVD (labeled CD 4).

1If necessary, insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP41\41hfb7\WSMP_Server41SP1HFB7\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6When prompted for the existing installation directory, verify that the path listed is correct. If not, click Choose... and select the base installation directory (this directory contains the "mpserver" directory).

7When prompted for a backup directory, you can leave the default directory, type the path to a new directory, or click

Choose... and select a backup directory.

8When the installer is finished, click Done to quit.

9To verify the upgrade, launch the Configuration Manager for WorkSite MP Server 4, click Help, and select About. After installing HFB7, the current version should be 4.1.1.7.5.

Do not delete the 3.1 Library files (lib folder), as they are used by WorkSite MP even after migrating to 5.0 Patch 1.

Migrating data from 4.1 HFB7 to 5.0 on Windows and Solaris The final process is to upgrade data from version 4.1 HFB7 to 5.0 and to install Patch 1 for version 5.0. 1Make a backup copy of the database and file servers. The default location for 4.1 file servers is c:\worksitemp4. 2Review the entries in setmigratevars.bat (or setmigratevars.sh), which were added in step 6 on page 192.
Make sure that no spaces exist in the variable entries. Otherwise, execution will fail. For example, if a value of C:\worksitemp4\mpserver is entered for im4home= via copy/paste, a space may exist at the end of the line. This space will need to be deleted.

3If any changes are made, make sure to save setmigratevars.bat (or setmigratevars.sh) and close it. 4Execute the following batch file (shell script for Solaris:) Windows: c:\migrate\migrate4to5.bat Solaris: ./migrate/migrate4to5.sh
A log file will not be created automatically. However, the output can be viewed from the console. In order to do so, it is recommended that the DOS screen buffer size (height) be increased to 9000.

5Carefully follow any instructions that appear during the execution. You will be prompted to complete one manual step during the process. Otherwise, allow the script to run, making sure not to scroll up and down in the console window until the migration has completed.
Disregard the following error message: Running ObsoleteLDAPRemoval...failed

Refer to the next section, Applying Patch 1 for version 5.0, for comprehensive details on the manual step.
You can safely exit the execution of the script at any time by press CTRL-C. To restart from a specific step, follow the instructions in the comment section of the script.

Applying Patch 1 for version 5.0 After you run the migrate4to5.bat file, you will be prompted to apply v5.0 Patch 1.
For more detailed SP1 installation instructions and considerations, refer to the WSMP_500P1_Server_rn_V1_EN.pdf file in the \Collab\WSMP50\WSMP_Server50_with_Patch1\ WSMP_Server50P1 folder on the Collaboration DVD (labeled CD 4).

1If necessary, insert/mount the Collaboration DVD (labeled CD 4).

2Launch the installer from the following folder: \Collab\WSMP50\WSMP_Server50_with_Patch1\ WSMP_Server50P1\upgradefrom5.0GA\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6When prompted for the existing installation directory, verify that the path listed is correct. If not, click Choose... and select the base installation directory (this directory contains the "mpserver" directory).

7When prompted for a backup directory, you can leave the default directory, type the path to a new directory, or click Choose... and select a backup directory.

8When the installation is complete, click Done to exit the installer.

9Delete any temporary files (all files) in the \fxfer directory of your Worksite MP installation. The default location of this directory is c:\worksitemp\<library_name>\fxfer\. 10Restart the WorkSite Process Manager (or restart the service on Windows). From the Configuration Manager, reset CMS and Indexer to Auto-Start.
If Windows desktop or start menu shortcuts to the Configuration Manager and Library Manager are not created or do not work, you can create new shortcuts or launch the tools from the directory in which they are installed: Configuration Manager (if installed in the default location): Windows=c:\worksitemp5\mpserver\bin\win\imconfigmgr.exe Solaris=/worksitemp5/mpserver/bin/unix/imconfigmgr Library Manager (if installed in the default location): Windows=c:\worksitemp5\mpserver\bin\win\imlibmgr.exe Solaris=/worksitemp5/mpserver/bin/unix/imlibmgr

11Re-Index all libraries: Windows: In Configuration Manager, expand the library node, right-click on a library and select Re-Index Library.

12Restart the CMS and Indexer services so that the library changes take effect. 13To verify the upgrade, launch the Configuration Manager, click Help, and select About. The current version should display as 5.0.0.1.59.

Do not delete the 3.1 Library files (lib folder), as they are used by WorkSite MP even after migrating to 5.0 Patch 1.

Ensuring Optimal Performance of the Collaboration Server

To ensure optimal performance after you have migrated Worskite MP Server versions and applied the service pack, verify the following setting in the collaboration server file programinit.properties. The file is located at <server install location>\worksitemp5\mpserver\config\programs. jvm.interpreted.windows=false

The migration of WorkSite MP Server to version 5.0 Patch 1 is now complete.

Migrating WorkSite MP Server 4.1 HFB7 to 5.0 Patch 1

If you had previously installed v4.1 HFB7 of the collaboration server (i.e., with the 6.0 release of Primaveras Web Application), you need to migrate it to WorkSite MP Server v5.0 Patch 1. Complete all steps below, in the order specified, to migrate from 4.1 HFB7 to 5.0 Patch 1: 1Installing version 5.0 of the Collaboration Server 2Migrating data from 4.1 HFB7 to 5.0 on Windows and Solaris 3Applying Patch 1 for version 5.0 Before you begin the migration, ensure that your current WorkSite MP Server v4.1 version is 4.1.1.7.5. To verify the version, launch the Configuration Manager, click Help, and select About. The version will be at the top of the window. Installing version 5.0 of the Collaboration Server You will first need to install the 5.0 version of the collaboration server before migrating: 1Insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP50\WSMPServer50\Server\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6Select the install location (to use a different location, type the full path or click Choose... and browse to the location).

7Select the Complete Install option.

8Review the details of the pre-installation summary. Click Install to continue or Previous to go back. 9When the installation is complete, click Done to exit the installer.

10Verify that worksitetemp5 exists in the installation location chosen in step 6.

Migrating data from 4.1 HFB7 to 5.0 on Windows and Solaris Next, the data from version 4.1 will be migrated to 5.0, with the help of a script provided by Primavera, and Patch 1 will be installed for version 5.0.
This procedure assumes that the original name of the 4.1 schema, finalschema41.dat, has not been altered.

1Make a backup copy of the database and file servers. The default location for 4.1 file servers is c:\worksitemp4. 2Open the WorkSite MP 4.1 Configuration Manager and stop all processes, including CMS and Indexer. Disable auto start for all processes, and save the configuration. 3Make a temporary folder on your local drive and name it migrate. For example, c:\migrate. 4Copy all files and folders in the \Collab\migrate\ folder on the Collaboration DVD (labeled CD 4) to the new temporary folder. 5Locate setmigratevars.bat (or setmigratevars.sh on Solaris) and remove the read-only attribute. 6Edit setmigratevars.bat (or setmigratevars.sh) and fill in the appropriate variable values. Examples are located in the comments section, indicated by lines beginning with rem (or # for Solaris).
Make sure that no spaces exist in the variable entries. Otherwise, execution will fail. For example, if a value of C:\worksitemp4\mpserver is entered for im4home= via copy/paste, a space may exist at the end of the line. This space will need to be deleted.

7Save setmigratevars.bat (or setmigratevars.sh) and close it. 8Execute the following batch file (shell script for Solaris:) Windows: c:\migrate\migrate4to5.bat Solaris: ./migrate/migrate4to5.sh
A log file will not be created automatically. However, the output can be viewed from the console. In order to do so, it is recommended that the DOS screen buffer size (height) be increased to 9000.

9Carefully follow any instructions that appear during the execution. You will be prompted to complete one manual step during the process. Otherwise, allow the script to run, making sure not to scroll up and down in the console window until the migration has completed.
Disregard the following error message: Running ObsoleteLDAPRemoval...failed

Refer to the next section, Installing version 5.0 Patch 1 of the Collaboration Server, for comprehensive details on the manual step.
You can safely exit the execution of the script at any time by press CTRL-C. To restart from a specific step, follow the instructions in the comment section of the script.

Applying Patch 1 for version 5.0 After you run the migrate4to5.bat file, you will be prompted to apply v5.0 Patch 1.
For more detailed SP1 installation instructions and considerations, refer to the WSMP_500P1_Server_rn_V1_EN.pdf file in the \Collab\WSMP50\WSMP_Server50_with_Patch1\ WSMP_Server50P1 folder on the Collaboration DVD (labeled CD 4).

1If necessary, insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP50\WSMP_Server50_with_Patch1\

WSMP_Server50P1\upgradefrom5.0GA\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6When prompted for the existing installation directory, verify that the path listed is correct. If not, click Choose... and select the base installation directory (this directory contains the "mpserver" directory).

7When prompted for a backup directory, you can leave the default directory, type the path to a new directory, or click Choose... and select a backup directory.

8When the installation is complete, click Done to exit the installer.

9Delete any temporary files (all files) in the \fxfer directory of your WorkSite MP installation. The default location of this directory is c:\worksitemp4\<library_name>\fxfer\. 10Restart the WorkSite Process Manager (or restart the service on Windows). From the Configuration Manager, reset the CMS and Indexer to Auto-Start.
If Windows desktop or start menu shortcuts to the Configuration Manager and Library Manager are not created or do not work, you can create new shortcuts or launch the tools from the directory in which they are installed: Configuration Manager (if installed in the default location): Windows=c:\worksitemp5\mpserver\bin\win\imconfigmgr.exe Solaris=/worksitemp5/mpserver/bin/unix/imconfigmgr Library Manager (if installed in the default location): Windows=c:\worksitemp5\mpserver\bin\win\imlibmgr.exe Solaris=/worksitemp5/mpserver/bin/unix/imlibmgr

11Re-Index all libraries: Windows: In Configuration Manager, expand the library node, right-click on a library and select Re-Index Library.

12Restart the CMS and Indexer services in order for the library changes to take effect. 13To verify the upgrade, launch the Configuration Manager, click Help, and select About. The current version should display as 5.0.0.1.59.

Do not delete the 4.1 Library files (lib folder), as they are used by WorkSite MP even after migrating to 5.0 Patch 1.

Ensuring Optimal Performance of the Collaboration Server

To ensure optimal performance after you have migrated Worskite MP Server versions and applied the service pack, verify the following setting in the collaboration server file programinit.properties. The file is located at <server install location>\worksitemp5\mpserver\config\programs.

jvm.interpreted.windows=false

The migration of WorkSite MP Server to version 5.0 Patch 1 is now complete.

Installing the Collaboration Server for the First Time

Preparing the Installation This section details only the steps necessary to install the collaboration server for use with P6 Web Access. For complete server setup and configuration information, refer to the pdf files within the \Collab\WSMP50 directory of the Collaboration DVD (labeled CD 4). Prerequisites The only prerequisite to installing the collaboration server is the creation of a database that will be used as the authentication library for the collaboration server. The database should contain a data and log file, each at least 100 MB in size.
For Oracle users, the database owner must be created in Oracle, have a default tablespace assigned, be granted connect and resource roles and QUERY REWRITE system privileges. See step 7 on page 223. On Solaris, Primavera recommends that you use the korn shell (ksh), that you set the unmask value for the installation account to 700, and that the installation, /tmp, and /temp directories enable read/write access. If you are installing from a remote terminal, the terminal session must support a graphical display mode.

Sizing Considerations The following guidelines should be considered when preparing the collaboration server for use in your organization. Collaboration file server disk space requirements are approximately equal (1-to-1 in byte size) to the total source file size + room to grow. For example, if the total source file size is 5 GB, then the collaboration file server space requirement would be 5 GB + room to grow.
Room to grow is a projected calculation based on a company's growth and expected rate of entering new projects and data into Primavera. If the user uploads 5 GB of documents, deletes the same 5 GB of documents, then adds 5 GB of new documents, the total disk space required is at least 10 GB. Documents are not purged from the system, they are placed in the \trash folder on the collaboration file server. Deleted documents can be retrieved from the \trash folder, if necessary, as long as the Collaboration Recycler Service was not previously enabled and run. The Collaboration Recycler Service can be enabled in the Administration Application of P6 Web Access to purge deleted documents at user-defined intervals.

The Indexer service requires approximately 10% to 20% of the total file server disk space consumption. For example, if the disk space usage on the file server is 5 GB, the Indexer disk space requirement would rage between 500 MB (10%) to 1 GB (20%). Installing version 5.0 Patch 1 of the Collaboration Server If you have not previously installed the Collaboration Server, you will need to install version 5.0 Patch 1.
For more detailed installation instructions and considerations, refer to the WSMP_500_Server_install_V1_EN.pdf and WSMP_500P1_Server_rn_V1_EN.pdf files in the \Collab\WSMP50 folder on the Collaboration DVD (labeled CD 4).

1Insert/mount the Collaboration DVD (labeled CD 4). 2Launch the installer from the following folder: \Collab\WSMP50\WSMP_Server50_with_Patch1\ WSMP_Server50P1\new install\Server\install.htm 3On the Update page, click on the download link for the appropriate platform (Windows or Solaris) and run/open the executable (install.exe). 4After the download is complete, select the installation language and review the introduction. 5Accept the license agreement. 6Select the install location (to use a different location, type the full path or click Choose... and browse to the location).

7Select the Complete Install option.

8Review the details of the pre-installation summary. Click Install to continue or Previous to go back. 9When the installation is complete, click Done to exit the installer.

10Copy the license key file (wsmp.lic) from the Collaboration DVD (labeled CD 4) to the mpserver directory on each server in the WorkSite MP Server cluster. The default Windows path is c:\worksitemp5\mpserver\ The default Solaris path is /worksitemp5/mpserver/ 11Start the Process Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Start Process Manager Solaris: /worksitemp5/mpserver/bin/unix/impm
On Windows operating systems, it is recommended to install the Process Manager as a service by executing the following command: c:\worksitemp5\mpserver\bin\win\impmservice install After installing the service, launch the services control panel and set the startup type of the Woksite MP Process Manager service to Automatic, then start the service if it is not already running.

12Launch the Configuration Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Configuration Manager Solaris: /worksitemp5/mpserver/bin/unix/imconfigmgr 13To verify the installation, launch the Configuration Manager, click Help, and select About. The current version should display as 5.0.0.1.59.

Ensuring Optimal Performance of the Collaboration Server

To ensure optimal performance after you have installed the collaboration server for the first time, verify the following setting

in the collaboration server file programinit.properties. The file is located at <server install location>\worksitemp5\mpserver\config\programs. jvm.interpreted.windows=false

This concludes the installation of the Collaboration Server. Proceed to the next section, Creating a Collaboration Configuration for the First Time.

Creating a Collaboration Configuration for the First Time

After the collaboration server has been installed for the first time, it must be configured. The following tasks need to be completed, in the order specified: 1Configuration Tasks Overview 2Adding the Main Components 3Adding the Indexer Service 4Adding Trustees 5Enabling Expired Trustees 6Adding a Facility 7Adding a Domain and Admin User 8Extend the Collaboration Schema 9Adding Updated Document Formats 10Configuring P6 Web Access for Collaboration Configuration Tasks Overview After installing the collaboration server, several configuration tasks are required to prepare the server for use in the Primavera environment. The two main interfaces used to configure the collaboration server are the Configuration Manager and the Library Manager. This section describes the main configuration interfaces and highlights the tasks for which each interface is used. Configuration Manager The Configuration Manager is used to configure one or more server clusters and to control the CMS, Indexer, and other collaboration services. The entire WorkSite MP server cluster can be controlled via this application, which is what makes the Configuration Manager such a powerful tool. When you set up your WorkSite MP Server, you must run the Configuration Manager to create a configuration for all the components that make up a WorkSite MP Server Cluster. The list below denotes the components that are configured for each WorkSite MP Server Cluster using the Configuration Manager:
WorkSite

MP Cluster Configurations

Server Clusters Local and Remote Libraries Servers Services

Library Manager The Library Manager is an administrative tool used to set up and manage data associated with libraries serviced by WorkSite MP Server clusters. Using Library Manager, a WorkSite administrator can manage the following types of library data:
Facilities

WorkGroups
Library

metadata instances

Metadata classes Metadata Relationships

Privileges System Trustee

Configuration information, including the following:

Master Realm Settings Realms, which include the ability to perform the following tasks: Add a Master Realm to the library Add individual users, groups, localities, and organizational units as native trustee nodes under a librarys Master Realm Import and synchronize directories from external LDAP directory services as imported trustee nodes under a librarys Master Realm Add Slave Realms from other libraries
System

Users

When a library is created, it has a predefined directory structure that corresponds to the WorkSite object model. This structure can be implemented as an out-of-the-box solution. It can also be viewed as a model for building an application based on a custom object model. Library Manager Window The Library Manager Window section is divided into five subsections that describe different parts of the Library Manager window and their functions. The five subsections are:
Directory Display Menus Toolbar Look-Up

frame

frame

toolbar

Top-Level Nodes The Top-Level Nodes section covers the functions that can be performed from the following nodes:
Clusters Server

Cluster

Library

The

tasks that can be performed from these nodes are: Add a Server Cluster Delete a Server Cluster Login to a Library

Facilities Node The Facilities Node section contains descriptions of the tasks that can be performed from the Facilities node and descriptions of the dialogs that are used to perform the tasks. The following tasks can be performed from this node:
Adding Editing

Metadata instances Metadata sources and instances Metadata instances

Deleting Adding

Metadata relationships

Privileges Node The Privileges Node section contains descriptions of the tasks that can be performed from the Privileges Node as well as descriptions of the dialogs that are used to perform these tasks. The Privileges node helps administrators to determine security for trustees. Depending upon the privilege, security can be either set automatically or require specific settings. The following tasks can be performed from the subnodes that appear below the Privileges node:
Edit

Privileges

System Configurations Node The System Configurations Node section contains descriptions of the tasks that can be performed from the System Configurations node as well as descriptions of the dialogs that are used to perform these tasks. The System Configurations node helps administrators to keep track of global configurations at the library level. The following tasks can be performed from the subnodes that appear below the System Configurations node:
Edit

System Configurations

Trustees Node The Trustees Node section contains descriptions of the tasks that can be performed from the Trustees node and descriptions of the dialogs that are used to perform the tasks. The Trustees node contains a variety of subnodes that are used to create and maintain native and imported trustees for a library. The following tasks can be performed from the subnodes that appear below the Trustees node:
Add, Edit

Edit, or Delete libraries in the Accessible Libraries list

an existing LDAP Link Edit, or Delete Connections to external LDAP Directory servers Edit, or Delete Maps to external LDAP Directories or Edit a Master Realm Edit, or Delete Trustees Synchronize, or Delete external LDAP Trustee directories to/from the Master Realm

Add, Add, Add Add,

Import, Add Add, Add,

a Unique Identifier to an LDAP Directory Edit, or Delete Slave Realms Edit, or Delete System Users

Add Unique Identifier to LDAP Directory

The WorkSite MP Server uses a unique identifier attribute (or synchronization ID) to enable the import and synchronization of LDAP-compliant directories into the Library Manager tree. The default name for this attribute is iManageSyncId, though any appropriate name can be used. The following section provides a guide for extending the schema of a remote LDAP directory service to include the iManageSyncId and iManageSyncIdClass.
Creating

a User with Restricted Access Rights

The following figure illustrates the Library Manager interface:

Adding the Main Components

The nodes in the Configuration Manager and Library Manager can be expanded by clicking the + next to the node or by double-clicking the node name.

1Start the Process Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Start Process Manager Solaris: /worksitemp5/mpserver/bin/unix/impm
On Windows operating systems, it is recommended to install the Process Manager as a service by executing the following command: c:\worksitemp5\mpserver\bin\win\impmservice install After installing the service, launch the services control panel and set the startup type of the Woksite MP Process Manager service to Automatic, then start the service if it is not already running.

2Launch the Configuration Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Configuration Manager Solaris: /worksitemp5/mpserver/bin/unix/imconfigmgr 3If a default cluster does not appear under the WorkSite Cluster Configurations, right-click and select Add Cluster.

The cluster name must be the same as the hostname (machine name) of the collaboration server.

4Right-click the cluster and select Add > Server.

The server name must the same as the cluster name.

5Right-click the server node and select Add > CMS.

In addition to CMS (Content Management System) the Indexer service must be added after the collaboration library has been configured. See Adding the Indexer Service on page 228 for more information.

6Right-click the Local node under Libraries and select Add.

7Enter the details of the local library database:

The local library database is the database created before starting the installation of the collaboration server.

Field
Library Name DBInstance Name

Definition
The name of the collaboration library. Instance name of the Oracle or SQL Server database to be used as the collaboration library. Supplied database driver for MS SQL Server and Oracle. Database system owner for collaboration tables and libraries. Database server Host, Port, Account, and Password

Value
User-defined -

Driver Owner Connection

WORKSITEM P -

8Click Test to validate the database details. If the test fails, ensure the library/database details are correct. Once the test is successful, click the Create button to create the authentication library.

The Content Library Creation Wizard creates the database tables and indices required to run the collaboration server. Click Next to move to the next step in the wizard. The following information is required: Library Object Model - choose worksitemp50

File Server Path - type or browse to the full path to the location where the library files should be created and stored (this can be any desired location)

Database Character Support - enable or disable the use of national characters for database string attributes
Enabling the National Character Support option is NOT recommended when creating an Oracle database.

Review the Library Configuration Summary and click Next to continue or Back to make changes.

Once the wizard is finished, the new library must be defined as the Authentication Library. Add an Authentication Library 9Right-click the cluster name and select Edit.

10Click the CMS Libraries tab and click Add.

11Ensure the authentication library is selected and click OK.

12Click OK to close the Edit Cluster dialog.

When all database tables and indices are created, three system accounts are added: PROXYUSER, CACHEMANAGER, and TOOLUSER.

13Select File, Save, to save your configuration settings. Start the CMS Service 14To start CMS, right-click the service and select Start.

When CMS has started successfully, the red square on the CMS service icon changes to a green arrow. 15After starting the CMS service, right-click the service name and select Auto-Start from the menu.

Enabling the CMS auto-start ensures that the collaboration services will be available in the case of a server reboot. 16Save the configuration when finished. Adding the Indexer Service 1Launch the Configuration Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Configuration Manager Solaris: /worksitemp5/mpserver/bin/unix/imconfigmgr 2Expand the WorkSite Cluster Configurations tree to show the server node (below the cluster node). 3Right-click the server node and select Add > Indexer.

The Add Indexer window is displayed. 4If you want to enable SSL on the Indexer service, mark the checkbox next to SSL Enabled.

5Click the Libraries tab. 6From the Available list, select the library that you are adding to the Indexer service. To select multiple libraries, use Ctrl or Shift.

7Click the arrow button () to add the selected libraries to the Configured list.

8Click OK when you are finished. 9Select File, Save to save your configuration settings. Start the Indexer Service 10To start the Indexer, right-click the service and select Start.

When the Indexer has started successfully, the red circle on the Indexer service icon changes to a green arrow. 11After starting the Indexer service, right-click the service name and select Auto-Start from the menu.

Enabling the Indexer auto-start ensures that the service will be available in the case of a server reboot. 12Save the configuration when finished, if needed. Adding Trustees 1Launch the Library Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Library Manager Solaris: /worksitemp5/mpserver/bin/unix/imlibmgr
The CMS service must be running before the Library Manager can be launched.

By default, the master local library (created in the Configuration Manager) is displayed in the Library Manager. 2Expand the cluster node to display the library node. 3Expand the library node to display the library sub-nodes. 4Expand the Trustees node. 5Right-click on the Realms node and select Add.

6When prompted for the type of realm to add, select Master.

7Enter a name for the master realm next to RDN (the suggested default name is WorkSiteRealm), then click OK.

8Expand the Realms node, right-click the new master realm, then select Add to add a trustee.

The first trustee is not necessarily used by Primavera, but it is required to initialize the collaboration facility.

9Enter the following details for the new trustee: RDN - the name of the new trustee (can be any desired name) Class - leave the default value, Person Label - defaults to p when Class = Person

UID - the user ID of the new trustee (user-defined) Domain - an LDAP-related value, manually defined (not required) You can set a password for the trustee, but no other changes are needed.

10Click OK when finished. Enabling Expired Trustees Over time, passwords for trustees might expire, based on the Password expiration time n days value in the System Configurations node of the Library Manager tool. When they do, you might receive ExpiredTrusteesException messages. To enable expired trustees, you can reset their last login date to the current date, as follows: 1Log into the collaboration database as the database owner (default owner is WORKSITEMP). 2Run the following MS SQL statement against the database for each expired trustee: SQL Server: update dit_trustee set LAST_LOGON_TIME = getutcdate(), modified_time = getutcdate() where dit_class= 1 and rdn=userid Oracle: update dit_trustee set LAST_LOGON_TIME = sysdate, modified_time = sysdate where dit_class = 1 and rdn=userid; 3You can verify that an expired trustee has been updated by running the following MS SQL statement: SQL Server: select LAST_LOGON_TIME, rdn from dit_trustee where rdn= userid Oracle select LAST_LOGON_TIME, rdn from dit_trustee where rdn= userid; Adding a Facility After adding at least one trustee to the master realm, the next step is to add a default facility. 1Right-click on the Facilities node and select Add.

2Enter a name for the facility. Select the master realm under the Trustee Selection Tree, select the new trustee from the Trustee Selection list, then click Add to move the trustee to the Grants list.

3Click OK to save the changes. 4When prompted for an initializer trustee, select Members under Trustee Selection Tree, select the new trustee under Person Selection, enter the trustee password if one was assigned, then click OK.

You will be notified when the facility has been successfully initialized. By default, the new trustee is also added Grant access to the facilitys three child workgroups: Administrators, Trustee Browsers, and Workspace Creators. Additionally, a default Workspace is created, called WorkSite MP Home.

Adding a Domain and Admin User For integration with P6 Web Access, the primavera.com must be added to the master realm. Within that domain, a user called DomainAdmin must be added. 1Right-click the master realm (WorkSiteRealm) and select Add.

2Enter the following details for the primavera.com domain: RDN - primavera.com Class - Domain Label - d (changed automatically when Class is changed)

3Click on the Libraries tab and uncheck each of the Inherit boxes under Preferences Facility and Homepage Workspace. Click the browse button (...) next to the Preferences Facility.

4Browse to and highlight the facility that was created in the previous section, then click OK.

The value should look like <library>:<facility>.

5Click the browse button (...) next to Homepage Workspace, browse to and highlight WorkSite MP Home workgroup (under the facility node), then click OK.

The value should look like <library>:<facility>:WorkSite MP Home.

6Click OK when finished. 7Right-click the primavera.com domain and select Add.

8Enter the following details for the domain admin user: RDN - DomainAdmin Class - Person Label - p UID - DomainAdmin Domain - primavera.com
The password for the DomainAdmin user should be left blank, and you should select the Password never expires option.

9Click OK when finished. Make DomainAdmin the Manager of primavera.com After the DomainAdmin user has been created, it should be designated as the manager of the primavera.com domain. 10Right-click the primavera.com domain node under the master realm and select Edit.

11Click on the Trustee Managers tab, expand the Trustee Selection Tree, select the DomainAdmin user under Person Selection, then click Add to add the user to the Trustee Managers list.

12Click OK when finished. Add DomainAdmin to the Trustee Browsers and Workspace Creators Workgroups After creating the DomainAdmin user, the user must be added to the Trustee Browsers and Workspace Creators workgroups. 13Right-click the Trustee Browsers workgroup and select Edit.

14Select the primaver.com domain under Trustee Selection Tree, select the DomainAdmin user under Trustee Selection, then click Add to add the user to the Members list.

15Click OK when finished. 16Right-click the Workspace Creators workgroup and select Edit.

17Select the primaver.com domain under Trustee Selection Tree, select the DomainAdmin user under Trustee Selection, then click Add to add the user to the Members list.

18Click OK when finished. Extend the Collaboration Schema After installing the collaboration server and library, the database must be upgraded to the extended schema. Extending the Database Schema 1Copy finalschema50.dat from the \Collab\WSMP50\schema directory on the Collaboration DVD (labeled CD 4) to \worksitemp5\mpserver\config\objectmodels on the collaboration server. 2Stop the CMS service in the Configuration Manager. 3Open a command prompt or shell and go to the following directory: Windows: c:\worksitemp5\mpserver\bin\win\ Solaris: /worksitemp5/mpserver/bin/unix/ 4Run the following command: imlibmigrate -from objectmodels\worksitemp50.dat -to objectmodels\finalschema50.dat -library <library name>

-cluster <cluster name> Replace the values for -library and -cluster with the library name and cluster name for your installation. In the library database, table p_project will have new fields X_PVPKID and X_PVTYPE. 5Restart the WorkSite MP 5.0 Process Manager. Windows: Stop and start the IMPM.EXE, or, if installed as a service, restart the WorkSite PM process. Solaris: Stop and start the IMPM process by typing the following commands: ./imstoppm ./impm & 6Restart CMS (if not set to Auto-Start). Verifying the Upgrade To verify whether the schema upgrade was successful, check the cms.ImLibraryMigrate.<cluster>.log file located in the following directory: \worksitemp5\mpserver\logs\<cluster>\
The path and filename of the log file for your server will use the cluster name (hostname) of the collaboration server instead of <cluster>, as shown above.

The log file should end with the following line in the case of a successful upgrade: <Date/Time>: INFO [main] Library Migrate ended successfully Adding Updated Document Formats Two document formats are supported by P6 Web Access, but not by the collaboration server, by default. These formats should be added to the collaboration library after server setup is complete. The document format values are listed below: NAME
DESCRIPTION EXTENSION NAME

VALUE (Format 1)
MicroStation Design File dgn DGN

VALUE (Format 2)
AutoCAD Drawing File dwg DWG

1Launch the Library Manager according to your operating system: Windows: Start, Programs, WorkSite MP Server 5, Library Manager Solaris: /worksitemp5/mpserver/bin/unix/imlibmgr
The CMS service must be running before the Library Manager can be launched.

2Expand the cluster and library nodes to display the library sub-nodes. 3Expand the Metadata node. 4Right-click on the Application Formats node and select Add.

The Add Metadata dialog is displayed.

5Enter the information (listed in the table before step 1) for either Format 1 or 2. To enter data in a VALUE cell, left-click the desired cell and enter the text required. 6Click OK when finished.
If the file format is used frequently, you may want to mark the IS_INDEXABLE checkbox to enable faster loading of the specified document format.

7Repeat steps 4 through 6 for the other document format. This concludes creating a Collaboration configuration. Proceed to the next section, Configuring P6 Web Access for Collaboration.

Configuring P6 Web Access for Collaboration

After the collaboration server has been successfully installed, you should modify the appropriate settings in the Administration Application of P6 Web Access (see Using the Administration Application on page 153). The settings related to collaboration are listed below. Required Settings The values for certain settings are specific to your installation. Therefore, the following settings must be modified in the Administration Application before your collaboration server will properly function in your environment.
Database/Instance/Collaboration

Domain - The collaboration domain created in Adding a Domain and Admin

User on page 236.

Collaboration Collaboration Collaboration

Server/Server Name - Hostname of the collaboration server for P6 Web Access. Server/Library Name - The collaboration library created in step 7 on page 223.

Server/Cache User Name - The ID of the user having access to the collaboration application cache. This setting (CACHEMANAGER) is created by default and must match the ID of the user created on the collaboration server when adding the authentication library (see Add an Authentication Library on page 226).
Collaboration

Server/Cache User Password - The password that corresponds to the CacheUserName. This setting must be entered in the Administration Application and must match the password used for CACHEMANAGER on the collaboration server. The default password created on the collaboration server is also CACHEMANAGER (see Add an Authentication Library on page 226). Additional Settings The remaining collaboration settings can be modified as needed, but changes are not required to enable collaboration functionality in P6 Web Access.
Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration Collaboration

Server/Collaboration Workspace Name - The default collaboration workspace name. Server/Initiation Workspace Name - The default initiation workspace name. Server/Application Name - The default app name used by P6 Web Access. Server/Pool Size - The number of collaboration connections initialized. Server/Pool User Name - The user name used to start the connection pool. Server/Pool User Password - Password for the user name used to start the connection pool. Server/Admin User Name - The Admin user with full privileges. Server/Admin User Password - The password of the admin user. Server/Cache Limit - The maximum number of CMS objects that are kept in the application cache.

Collaboration

Server/Strict Document Versioning - If true, document checkout is restricted to the most recent version of a document. If false, any document version can be checked out.
Services/Collaboration

Synchronization Service/ Synchronization Interval - The interval at which the collaboration synchronization service will run. The synchronization moves documents marked for deletion to the collaboration server \trash folder. Additionally, other collaboration items (e.g., discussions or issues) that should be removed (e.g., when a project is deleted) are moved to the \trash folder. Documents can then be manually deleted or backed up from the \trash folder.
Services/Collaboration

Recycler Service/Automatic - If true, enables the collaboration recycler service, which purges deleted documents and other collaboration items from the \trash folder.
Once the recycler service runs, deleted items will no longer be retrievable from the collaboration server.
Services/Collaboration

Recycler Service/Recycle Interval - The interval at which the collaboration recycler service

should run.

Use the Distributed Job Service (DJS) to run jobs independently on multiple Job Service servers at the same time. You can configure a controller server that manages the distributed Job Service by distributing jobs to multiple machines. In this chapter:
Distributed Job Service Overview Installing the Distributed Job Service Disabling the Windows Firewall Configure Access to the Distributed Job Service Configure DCOM for the Distributed Job Service Configure the Controller and DJS servers Job Service Registry Settings

Configuring the Distributed Job Service

Distributed Job Service Overview
The Distributed Job Service (DJS) is an extension of the Job Service that enables a controller machine to manage multiple machines (servers) running job services. Non-distributed job services run jobs on a single machine; installing the nondistributed job service on multiple machines results in each service running independently on each machine. With distributed job services, each designated server runs jobs as requested by the controller via DCOM communication, as shown in the following figure. This distributes the job service load across multiple machines. If desired, the controller can also run jobs.

In addition to the preparations described in this section, you must configure the database for P6 Web Access to run the Project Architect job service. Refer to Configure P6 Web Access to run the Project Architect job service on page 158.

Prepare the Controller and DJS servers for installation and configuration Be sure to complete the following tasks before you install and configure DJS on the Controller and servers:
On

the Controller and all DJS servers, define the Temp and TMP variables in Environment variables (both User variables and System variables).

Synchronize

the system clocks of the Controller and all DJS servers to have identical time stamps in the log files.

Installing the Distributed Job Service

Before installing the Distributed Job Service, identify the Controller and servers (maximum 10). Install the Job Service on each machine as described in Installing the Job Service and Distributed Job Service on page 287. On the Controller, be sure to select the Distributed Job Service Configuration option as shown in the following figure. When you finish the installation, return to this section to configure user access.
Primavera recommends that the controller and all related servers be in the same network domain. Also, each machine should have Windows Server 2003 or Windows XP as the operating system, with Firewall turned off.

Disabling the Windows Firewall

The Windows Firewall, which is enabled by default on Windows 2003 and XP, prevents DCOM connections from functioning. You must disable the firewall on the controller and each DJS server. To disable the Windows Firewall, perform the following steps: 1From the Windows Control Panel, click Windows Firewall. 2In the General tab of the Windows Firewall dialog, select Off. then click OK.

Configure Access to the Distributed Job Service

Before configuring DCOM and the DJS, you must create users that have privileges to launch the Job Service, access the registry and path information on the Controller, and access applications across the network. On the server that controls the domain in which the Controller and DJS servers reside, perform the following steps: 1Create a user group (for example, PrmAdmins). 2For the Controller and each DJS server, add a user name to the user group you just created. For example, Name of Controller : ControllerUser Name of Server1 (DCOM Server) : Server1User Name of Server2 (DCOM Server) : Server2User Name of Server3 (DCOM Server) : Server3User 3On the Controller and each DJS server, add the group you created to the Local Administrator Group. 4In the Security tab of the DCOM Configuration dialog, add the group you created to each Custom permission.
The example above illustrates a multi-user scenario. You can also configure single-user access. For example, you could create a single domain user (e.g., ControllerUser) and add that user to the Local Administrator group on the Controller and each DJS server. Then, when configuring DCOM, you could use the ControllerUser instead of the PrmAdmins user group shown above.

Configure DCOM for the Distributed Job Service

To configure DCOM for the Distributed Job Service on servers running Windows Server 2003 or Windows XP Professional, perform the following steps for the Controller and each DJS server.

1From the command line (or Start, Run utility), run dcomcnfg. The Component Services dialog is displayed.

2In the Component Services dialog, expand the tree in the left panel by clicking Component Services, Computers, My Computer, DCOM Config.

3Right click on the {9E521861-5A76-11D5-98F4-00C0F680F1F} entry in the right panel and select Properties. 4In the Properties dialog, General tab, set the Authentication Level to Connect.

Make sure the Controller and all DJS servers are set to the same Authentication Level. If desired, you can set Connect as the Default Authentication Level in the Default Properties tab of the Distributed COM Configuration Properties dialog.

5In the Properties dialog, Location tab, select the Run application on this computer option.

6In the Properties dialog, Security tab, ensure that the Customize options are selected for all permission types, as shown in the following figure.

7In the Properties dialog, Security tab, click the Edit button associated with Launch and Activation Permissions. 8In the Launch Permission dialog, Security tab, click Add.

9In the Select Users, Computers, or Groups dialog, enter the user group name you created previously (for example, PrmAdmins). Click OK.

10In the Launch Permission dialog, Security tab, select the user group you added (for example, PrmAdmins), and select Allow for all permissions, as shown in the following figure. Click OK.

11In the Properties dialog, Security tab, click the Edit button associated with Access Permissions.

12In the Access Permission dialog, Security tab, click Add.

13In the Select Users, Computers, or Groups dialog, enter the user group name you created previously (for example, PrmAdmins). Click OK.

14In the Access Permission dialog, Security tab, select the user group you added (for example, PrmAdmins), and select Allow for all permissions, as shown in the following figure. Then click OK.

15In the Properties dialog, Security tab, click the Edit button associated with Configuration Permissions.

16In the Change Configuration Permission dialog, Security tab, click Add.

17In the Select Users, Computers, or Groups dialog, enter the user group name you created previously (for example, PrmAdmins). Click OK.

18In the Change Configuration Permission dialog, Security tab, select the user group you added (for example, PrmAdmins), and ensure that permissions are set as shown in the following figure. Then click OK.

19In the Properties dialog, Identity tab, select the This User option. Enter the Password for a user who has administrative privileges on the machine you are using.

20Click OK to close the dialog. 21On the Controller, launch the Services Control Panel. 22In the Services dialog, double-click the Primavera Job Service (JSDB) to open the Properties dialog. 23In the Properties dialog, select This Account and enter the password of an administrative user on the Controller.
Steps 21 - 23 enable the DJS to use the name and password of the administrator you specified during DCOM configuration as the launching user for all servers.

24Click OK to close the dialog.

Configure the Controller and DJS servers

Configure the Controller and DJS servers using the Distributed Job Services Configuration tool. Follow the instructions to access the configuration tool and configure the Controller and DJS servers. 1On the Controller, run the DistributedJobsAdmin.exe from the following file location: C:\Program Files\Common Files\Primavera Common\JobService\JSConfig. The Distributed Job Service Configuration dialog opens (shown in the next figure)

2In the Distributed Job Service Configuration dialog, click Browse. Navigate to the C:\Program Files\Common Files\Primavera Common\JobService folder and select PrmJobSvXXXX.exe, where XXXX equals the DB Alias of the database connection (in this example, XXXX equals JSDB as shown in the next figure). 3In the Distributed Job Service Configuration dialog, click Add. For each server listed, select the equivalent PrmJobSvXXXX.exe.

The Distributed Job Service Configuration dialog should appear similar to the next figure.

If you have already used the configuration tool, all servers you previously configured appear in the list of servers (bottom grid of previous figure).

4Set the Status (Enabled/Disabled) for the Controller and each DJS server.
You can disable the DJS on any machine (e.g., if you want to execute jobs only on the servers and not on the Controller). However, a disabled machine may still run jobs if no enabled machine is available (e.g., due to network problems).

5Click Test to verify that the DCOM configuration and PrmJob installation is working correctly on each machine. 6In the Maximum Number of myPrimavera Jobs field, enter a value between 0 (zero) and the number of enabled DJS machines.
The Maximum Number of myPrimavera Jobs value determines the number of P6 Web Access jobs that can be run at one time. Also, this value does not affect recurring jobs set up using the Job Services dialog in the Project Management module.

7Click Save Settings, Close. 8Reboot the Controller and all DJS servers.
When the Controller restarts, its job scheduling actions are listed in the Event Viewer. Log files for all jobs are located in the appropriate folder of the Controller (not on the servers). After you reboot the Controller and DJS servers, if you modify the DCOM settings you specified in Configure DCOM for the Distributed Job Service on page 256, you must reboot the machine(s) on which you made the modifications.

Job Service Registry Settings

You can edit the registry settings that apply to the (Distributed) Job Service and the summarizer service (in both the Job Service and the Project Management module). Edit (Distributed) Job Service registry settings Type 'regedit' in the Start, Run utility to open the Registry Editor. In the Registry Editor, navigate to the following directory: My Computer\HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\PrmJobSvXXXX\Parameters (where XXXX equals the DB Alias of the database connection). The following table summarizes the Job Services registry settings. [Job Service settings] Setting Name and Description EstablishDBConnectionRetryCount
Number of times to try to connect to database on startup.

Defaul t
3

Valid Ranges/Values
1-10

MaxNumRecurringJobs
The maximum number of recurring (Project Management) jobs that can run simultaneously.

1-(no maximum)

MaxNumNonRecurringJobs
The maximum number of non-recurring (P6 Web Access) jobs that can run simultaneously.

1-5

NonRecurringJobCleanupRate
Frequency (in seconds) in which completed P6 Web Access jobs are removed from the database (1 minute to 7 days).

3600

60-604800

NonRecurringJobRefreshRate
Frequency (in seconds) in which P6 Web Access jobs are loaded from the database.

1-3600

RecurringJobRefreshRate
Frequency (in seconds) in which Project Management jobs are loaded from the database.

600

60-1440

DeleteRemoteLog
[test purposes only] If set to false, log file Prm*.tmp will not be deleted.

1 (true)

0 (false) 1 (true)

For more information about summarizer jobs, refer to About summarizer jobs and P6 Web Access on page 291.

Edit registry settings for summarizer jobs Type 'regedit' in the Start, Run utility to open the Registry Editor. In the Registry Editor, navigate to the following directory: My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Primavera. You can add any of the following settings as D Words and modify the defaults to the recommended value.
The following settings apply to the Job Service and the Project Management module. You would typically modify them to improve performance.

[Summarizer settings] Setting Name and Description Defaul t

1

Valid Ranges/Values
1-xx

NumProjectsSummarizedAtATime
Number of projects that can be summarized at the same time by the Job Service or the Project Management module. To achieve the best possible performance, Primavera recommends that the value of this setting = 20.

PreQuerySummarizablePct
The percentage threshold that determines how the summarizer will analyze a projects need for summarization. If the value of the equation shown below is less than the threshold, each project is considered for summarization individually. If the value of the following equation is greater than the threshold, all projects to be considered for summarization are analyzed simultaneously. The equation that determines this behavior is: # of projects to be summarized / # of projects user can access*100.

50

0-100

MaxDurationToSummarize
The maximum remaining duration or the maximum original duration, in hours, that an activity or activity assignment can have in order to be summarized. If an activity or activity assignment has a remaining duration greater than this threshold, it is ignored during summarization. To ensure that all activities are summarized, Primavera recommends that the value of this setting = 100000.

-1

The following settings are also available. However, you would not typically need to modify their values, unless you are performing tests.
[Summarizer settings] Setting Name and Description Default Valid Ranges/Values
0 (false) 1 (true)

EnterpriseSummaries
If true, EPS nodes are summarized. Applies only to the Project Management module. Note: The Job Service always summarizes EPS nodes.

0 (false)

ResourceSummaries
If true, resources are summarized. Applies to the Job Service and the Project Management module.

1 (true)

0 (false) 1 (true)

ForceEnterpriseSummaries
If true, forces an enterprise-level summarization even when no projects are summarized. Applies only to the Job Service.

0 (false)

0 (false) 1 (true)

EnterpriseCommit
Controls how frequently to commit EPS summary records to the database, based on the number of rows of data that have been processed. Useful for improving performance when summarizing large jobs. No value commits the EPS summary records when processing is complete. If you assign a value, this value is applied to both the Job Service and the Project Management module.

1000 for the Job Service No value for the Project Management module

1-(no maximum)

PrmJobLogMemory Usage
If true, logs memory usage of PrmJob in megabytes. Applies only to the Job Service.

0 (false)

0 (false) 1 (true)

RetrySleep
The time, in milliseconds, to wait between retry attempts when there is a connection failure. Applies only to the Job Service.

60000

MaxRetries
The maximum number of retry attempts to make when there is a connection failure. Applies only to the Job Service.

10

DumpSettings
Set to true to log all settings to a Job.txt file for the summarization job. Applies only to the Job Service.

0 (false)

0 (false) 1 (true)

PreLoadTASKSUMFINForEPS
Preloads TASKSUMFIN records for all projects before summarizing the entire EPS. Set to false to use a load on demand approach that will conserve memory but will be much slower due to an increased number of SQL queries for TASKSUMFIN records. Applies to summarizing Financial Periods in the Job Service and the Project Management module. Does not affect the performance of summarization by Weeks or Months.

1 (true)

0 (false) 1 (true)

PreLoadTASKSUMFINForProject
Preloads TASKSUMFIN records for each project before summarizing that project. Set to false to use a load on demand approach that will conserve memory but will be much slower due to an increased number of SQL queries for TASKSUMFIN records. Applies to summarizing Financial Periods in the Job Service and the Project Management module. Does not affect the performance of summarization by Weeks or Months.

1 (true)

0 (false) 1 (true)

PreLoadTRSRCSUMFN
Preloads TRSRCSUMFN records for each project before summarizing any project. Also, during summarization of the entire EPS, it preloads all TRSRCSUMFN records for one resource or role at a time. Set to false to use a load on demand approach that will conserve memory but will be much slower due to an increased number of SQL queries for TRSRCSUMFN records. Applies to summarizing Financial Periods in the Job Service and the Project Management module. Does not affect the performance of summarization by Weeks or Months.

1 (true)

0 (false) 1 (true)

Installing Client Modules and Additional Components

Automatic Database Upgrade Creating and Running an Unattended Setup Changing Database Configuration Settings Configuring Authentication Modes In this part:

Part

Primavera Client Installation and Configuration

ead this part to install and configure the Primavera client modules, additional components, and the

stand-alone version. The first chapter, Installing Client Modules and Additional Components, describes how to set up each module and component on a client workstation. If you are upgrading from a previous version of Primavera, read Automatic Database Upgrade. If you want to set up an automated installation rather than install the software manually, read Creating and Running an Unattended Setup. Once the modules are installed, read Changing Database Configuration Settings to learn how to use the Database Configuration utility to modify database connection information, administer licensing, change user passwords, and configure private database user accounts. Read Configuring Authentication Modes to select a method for validating user access to modules. Read this chapter to install the Primavera modules (Project Management and Methodology Management), additional components (Job Service, Software Development Kit, and ProjectLink), and the stand-alone version. Run the Setup program on the client/desktop computers that will be used by project personnel.

Install the Primavera client modules only after you install and configure the servers. The Setup wizard needs to connect to the database server when installing client modules. In this chapter:
Installing Database Client Software Uninstalling Previous Versions Running the Setup Wizard Installing Client Modules Installing the Job Service and Distributed Job Service Installing the Software Development Kit Installing ProjectLink Installing and/or Upgrading the Stand-Alone Version

Installing Client Modules and Additional Components

Installing Database Client Software
Before you install Primavera client modules, first install the client software for the database you will be using. The database client software enables the client computer to connect over the network to the database on the server computer. Microsoft SQL Server/SQL Server Express When you install the Project Management module on a client computer, the Microsoft SQL Server client files necessary to connect to Primavera modules are also automatically installed for you. You must use this method to install database client software if you are using SQL Server Express. Or, if you are using Microsoft SQL Server, you can also use your Microsoft SQL Server installation CD to install the client network utility. If you are unfamiliar with this process, please contact your database administrator. Oracle Use your Oracle installation CD to set up an application user and configure your Oracle Net Services client files to match your network. If you are unfamiliar with this process, please contact your database administrator.
Ensure that all clients are configured to use TCP/IP as the default network protocol. Make sure to reference the TNSPING.EXE location in your path environment variable. The TNSNAMES.ORA file should be in the oracle home folder on the client (local) machine not in a shared location.

Uninstalling Previous Versions

If you are upgrading from Primavera 5.0, all client modules other than Job Services are automatically upgraded during the install process; if you are upgrading Job Services 5.0, you must first uninstall the 5.0 version of Job Services before installing the P6 version.
Although you are not prompted to do so, its a good practice to restart your computer between uninstalling an application and

installing another application.

Uninstalling 5.0 versions of Job Services 1Click Start, Settings, Control Panel, Add or Remove Programs . 2Select the Primavera entry and click Change/Remove. 3On the Welcome screen of the Installation wizard, select Modify. 4On the Select Features to install screen, unselect Job Services and click Next. 5On the Ready to Install the Program screen, click Install.

Running the Setup Wizard

If you do not want to install the software manually, you can run an unattended setup. Refer to Creating and Running an Unattended Setup on page 309.

Install the client modules (Project Management and Methodology Management) additional components (Job Service, Software Development Kit, and ProjectLink), and the stand-alone version by running the Setup wizard. The first several steps of the installation process are exactly the same for all of these Primavera applications. These preliminary steps are documented in this section. When you complete the steps in this section, proceed to the section that contains the instructions for installing the module or component you want to install. You can install one or more modules. Each module requires approximately 20 MB of disk space. Administrator rights are required to install Primavera client modules on a computer running Windows XP Professional and Windows Vista.
The network protocol TCP/IP must be installed on the client computer. When you install Primavera applications, Primavera automatically installs MDAC 2.8 (English version) if it is not present on your machine. If you are installing Primavera applications on a machine running on a non-English operating system, Primavera recommends that you install the appropriate language version of MDAC 2.8 before installing Primavera. The Primavera installer will not overwrite the existing version of MDAC 2.8. To download the correct MDAC version, go to http://www.microsoft.com/downloads.

Preliminary steps for installing the client modules, additional components, and the stand-alone version 1If you are installing from a CD, insert CD 1. An introductory screen should appear that provides installation options. If the screen does not appear, or if you are installing from a network location, double-click setup.exe in the root folder of CD 1 and skip Step 2. 2On the main Primavera screen, choose Install Client Applications.
Click Next on each wizard dialog box to advance to the next step. Click Cancel at any time to exit the wizard.

3On the Welcome screen, click Next. 4On the Product Code dialog box, enter the product key located on the License CD label. If you are installing from a network location and are not sure what the product key is, ask your system administrator. 5On the License dialog box, accept the license agreement. 6On the Select Type dialog box, choose: Primavera Client Applications if you want to install only the client modules (Project Management and Methodology Management). Primavera Stand-alone if you want to install the stand-alone version.

Custom if you want to specify the client modules and additional components (including the Job Service, Software Development Kit, and ProjectLink).
For detailed instructions on installing an additional component individually, refer to its section in this chapter.

7On the Choose Destination Location dialog box, enter or select the destination folder for the client modules. 8On the Choose Destination Location (Common) dialog box, enter or select the destination folder for Primavera common files. By default, common files are installed in the Primavera Common folder created during installation. You can choose a different folder. 9Proceed to the section that contains installation instructions for the module or component you want to install: For client modules, continue with Installing Client Modules on page 285. For the Job Service, continue with Installing the Job Service and Distributed Job Service on page 287. For the Software Development Kit, continue with Installing the Software Development Kit on page 294. For ProjectLink, continue with Installing ProjectLink on page 297. For the stand-alone version, continue with Installing and/or Upgrading the Stand-Alone Version on page 299.

Installing Client Modules

Complete the following steps to install the Project Management and/or Methodology Management modules.
The following instructions assume you are installing the client modules only and that you have completed the steps detailed in Preliminary steps for installing the client modules, additional components, and the stand-alone version on page 282.

Install one or more modules 1On the Select Features to install dialog box, deselect the modules you do not want to install. By default, each module is selected. 2Enter or select the program folder in which the Primavera client icons will be stored on the Start menu. If you make no changes, these icons are stored under Programs, Primavera. 3Click Install to begin the installation. When the installation is complete, you are prompted to configure the database connection(s). 4On the Select Driver Type dialog box, select the driver type for the Primavera database. If you are installing the Project Management module, you must configure the clients connection to the project management database. If you are installing the Methodology Management module, you must configure a connection to the methodology management database. If both are being installed, you are prompted to configure the project management database connection first. 5On the Configure SQL Server Connection dialog box or the Configure Oracle Connection dialog box, configure the database connection settings. If you are configuring Microsoft SQL Server or SQL Server Express, type the database host name and database name. The database name was specified when the database was created; for example, PMDB. The host name is the name of the computer or IP address where Microsoft SQL Server is installed. If you are configuring Oracle, type the Oracle database name.

6On the Enter Public Login Information dialog box, enter your public login information that was defined by your administrator; for example, a Username of pubuser, and a group ID of 1. 7On the Validate Database Connection dialog box, click Next to test the database connection. 8Click Finish to complete the database connection setup. If the connection was not successful, click Back to revise your settings. If you chose to install both the Project Management and Methodology Management modules, the Database Configuration wizard starts again so you can configure the connection to the methodology management database. 9Click Finish to complete the installation.

Installing the Job Service and Distributed Job Service

The Job Service enables you to automate certain functions in the Project Management module. You can apply actuals, run a batch report, export projects, schedule projects, and summarize projects. These operations run in the background at specified intervals. The Job Service runs as a Windows 2003 service and can support an unlimited number of jobs, each with its own schedule of execution. Jobs are defined in the Project Management module and stored in the enterprises project management database. If you are working with more than one project management database, you can run jobs for all of the databases from one Windows 2003 server machine by installing multiple instances of the Job Service, as described in this section.
For more information on the distributed job service, refer to Configuring the Distributed Job Service on page 251.

If you want to be able to run multiple jobs simultaneously on separate servers, you can install the Distributed Job Service on a controller server that manages the Job Service and distributes jobs to the Job Service servers.
In addition to installing the job service, you must configure the database for P6 Web Access to run the Project Architect job service. Refer to Configure P6 Web Access to run the Project Architect job service on page 158.

Install the Job Service Complete the following steps to install the Job Service and/or Distributed Job Service.
The following instructions assume you are installing the Job Service only and that you have completed the steps detailed in Preliminary steps for installing the client modules, additional components, and the stand-alone version on page 282.

1On the Select Features to install dialog box, expand Other Components, expand Job Service, and choose the type of job service to install. Choose Job Service when: you want to install the non-distributed Job Service (single server only) you want to use the Distributed Job Service but the machine on which you are installing is NOT the controller server. Choose Distributed Job Service configuration only when you want to use the Distributed Job Service and the machine on which you are installing is the controller server.
If you want to run Job Service jobs in a language other than English, you must install the Project Management module on the Job Service machine. You can install it along with the Job Service, or you can install it at another time. After the applications are installed, refer to Specify a different language for the Job Service on page 293 for detailed instructions. Setup will verify that the user has administrator rights on the computer. If the user does not have administrator rights, the Setup wizard will end.

2On the Job Service Alias dialog box, type the database alias in the DB Alias field; for example, JSDB. Do not use dashes as part of the DB alias; otherwise, an error will occur.

Click the More button if you want to add more than one service. You can create multiple instances of the Job Service, which enables you to run multiple job services for all project management databases from one Windows 2003 server machine. Create one job service instance for each database.
For more information on running jobs on multiple databases using the Job Service, see Running Job Services on Multiple Databases on page 290.

When installing multiple instances of the Job Service, you should first stop all existing job services.

The Job Service uses the DB alias to connect to the database server. 3Enter or select the program folder. 4Click Install to begin the installation. 5On the Select Driver Type dialog box, in the Job Services driver type field, choose the database server type: Oracle or Microsoft SQL Server/SQL Express. 6If you are connecting to Oracle, on the Configure ORACLE Connection dialog box, in the type the Oracle connect string (database name), which can be found in the TNSNAMES.ORA file. If you are connecting to Microsoft SQL Server or SQL Server Express, on the Configure SQL Server Connection dialog box, type the database name and specify the server computer name. 7On the Enter Public Login dialog box, enter your public login information that was defined by your administrator; for example, a Username of pubuser, and a group ID of 1. 8On the Validate Database Connection dialog box, click Next to validate the database connection. The DB alias that you specified is created. 9On the Connection Successful dialog box, click Finish. You are prompted to test the Job Service alias.
If you are installing on a SERVER machine in a Distributed Job Services environment, DO NOT click the Test button as described in the following step.

10Click Yes to test the database connection. If the test fails, you can still continue the installation. 11Click Finish. Once the Job Service is installed on your computer and it is able to successfully connect to the database, the service will periodically run any user-defined jobs that are scheduled in the Project Management module.

Running Job Services on Multiple Databases

Once you have installed a separate job service instance for each project management database, you can apply actuals, run a batch report, export projects, schedule, or summarize all of the databases from one Windows 2003 server machine. Log into the Project Management module and select one of the project management databases that you want to summarize.

In the Project Management module, choose Tools, Job Services. Add the job service you want to run for that database. To set up another job service for a second project management database, exit the Project Management module. Log in again and choose a different project management database by selecting its database alias. In the Job Services dialog box, add the job for the currently open database. About summarizer jobs and P6 Web Access

Resource Management functions in P6 Web Access that use summary data rely on the creation of current enterprise resource records. Each record is the sum of all assignments for a resource. To ensure that enterprise records are current, use the methods below when summarizing projects.
Summarize

the project from within P6 Web Access. Summarizer jobs always update the enterprise records for resources in the selected project.
In

the client/server module, login as Admin Superuser and create a summarizer job to generate enterprise resource records for all resources in the specified projects.
For more information on registry settings for summarizer jobs, refer to Edit registry settings for summarizer jobs on page 271. In

the client/server module, if using the menu options to summarize, a registry key must exist for enterprise resource records to be created. To make the key, add EnterpriseSummaries as a D Word under HKEY_LOCAL_MACHINE/SOFTWARE/Primavera and modify the setting value to (1). Configure the Job Service to send jobs directly to a printer To send jobs directly to a printer, you must run the Job Service using an administrator account rather than the general system account. On the machine running the Job Service, complete the following steps to login to the Job Service using your administrator user name and password. 1From the Windows Control Panel, select Administrative Tools, Services. 2Double-click the Primavera Job Service. 3On the Primavera Job Service Properties dialog, select the Log On tab. 4Select the This Account option and enter the account and password of an administrative user. 5Click Apply, OK.

Specify a different language for the Job Service You can specify the output language for Job Service jobs. Complete the following steps to specify a language other than English. 1Complete the steps in the previous section, Configure the Job Service to send jobs directly to a printer, to login to the Job Service using your administrator account rather than the system account. 2If you did not install the Project Management module when you installed the Job Service (as described in step 1 on page 287), install the Project Management module on the Job Service machine. For detailed instructions on installing the Project Management module, refer to Installing Client Modules on page 285. 3After the Project Management module is installed and the database configured, start the module by choosing Programs, Primavera, Project Management from the Start menu. 4Login to the Project Management module using the same administrator account you used to login to the Job Service. 5On the Welcome dialog, choose Open Global Data Only. 6Choose Tools, Set Language, then select the desired language.
The Job Service will run jobs in the selected language assuming that the Job Service continues to run using the administrator account you used to login in Step 1. If, at any time, a different login is specified, you must repeat these steps using the alternate login. You cannot run Job Service jobs in a different language using the local system account.

Installing the Software Development Kit

The Software Development Kit (SDK) makes Primavera data available for use by external applications. In addition to data, the SDK provides application business rules and calculated values, and enforces application security. The SDK supports the Open Database Connectivity (ODBC) standard for connecting to the project management database. ODBC-compliant interfaces, such as OLE DB, are also supported.
The Integration API (Application Programming Interface) can also be used to connect directly to the project management database. This tool requires the ability to write client code in Java. For further information, see the Integration API Administrators Guide.

Install the Software Development Kit Complete the following steps to install the Software Development Kit.
The following instructions assume you are installing the Software Development Kit only and that you have completed the steps detailed in Preliminary steps for installing the client modules, additional components, and the stand-alone version on page 282.

1On the Select Features to install dialog box, expand Other Components and choose Software Development Kit. 2Click Install. 3Click OK after reading the explanation of the remaining process. You will be creating a DB alias named PMSDK for use with the SDK. You will then create an ODBC user data source name (DSN) called PrimaveraSDK. The ODBC DSN will use the DB alias to connect to the project management database. 4On the Select Driver Type dialog box, select the driver type of your database server. You can select Oracle or Microsoft SQL Server/SQL Express. 5Type the connection information as required for your database type. If you are configuring Oracle, on the Configure ORACLE Connection dialog box, type the Oracle connect string. If you are configuring Microsoft SQL Server or SQL Server Express, on the Configure SQL Server Connection dialog box, type the database name and server computer name. 6On the Enter Public Information dialog box, enter your public login information that was defined by your administrator; for example, a Username of pubuser, and a group ID of 1. 7On the Validate Database Connection dialog box, click Next to validate the database connection. 8On the Connection Successful dialog box, if the connection was successful, a DB alias named PMSDK was created. Click Finish. If the connection was not successful, click Back to re-enter the database information. 9On the Primavera Software Development Kit Setup dialog box, verify that the ODBC connection values are correct for your database, and click OK. An ODBC DSN named PrimaveraSDK is created.

Once the SDK is installed on your computer, you can connect to the project management database using the ODBC DSN. The SDK documentation is located in your \Program Files\Common Files\Primavera Common\PMSDK\Doc folder.
To access the SDK, you need to be added as a user with Admin Superuser access rights or be assigned the global privilege View All Global/Project Data via SDK.

On Windows Vista machines, the SDK and all applications using the SDK need to run in Administrator mode. The SDK documentation can be read using a Web browser. Open the INDEX.HTM file to view the table of contents for the documentation.

Installing ProjectLink
ProjectLink is a plug-in that enables Microsoft Project (MSP) users to work in the MSP environment while being connected to Primavera's enterprise features. The functionality enables MSP users to open/save projects from/to the Project Management module database from within the MSP application. With ProjectLink, MSP users have the ability to invoke Primavera's resource management within the MSP environment. ProjectLink enables users to use MSP for daily project maintenance while also having access to the enterprise capabilities available within Primavera applications. Install ProjectLink Complete the following steps to install ProjectLink.
The following instructions assume you are installing ProjectLink only and that you have completed the steps detailed in Preliminary steps for installing the client modules, additional components, and the stand-alone version on page 282.

1On the Select Features to install dialog box, expand Other Components and choose Project Link. 2Enter or select the program folder. 3Click Install. 4Click Finish when the download is complete. After you have successfully completed the installation, Primavera ProjectLink will appear as a toolbar in Microsoft Project. You can also choose Tools, Primavera ProjectLink in Microsoft Project to access any ProjectLink dialog box. ProjectLink Help is automatically installed in the same folder in which you installed the program. You can also access ProjectLink Help by clicking the help icon in any ProjectLink dialog box.

Ensuring Access to ProjectLink

Access to ProjectLink is user-specific, not machine-specific. Only the user that installs ProjectLink on a machine can use ProjectLink on that machine. For example, a typical computer will have multiple defined users (e.g., Administrator, All Users, <User Name>). If ProjectLink is installed by the 'Administrator' user, only the 'Administrator' user can view/access ProjectLink in Microsoft Project; when any other user logs in on that machine, ProjectLink is not visible. To ensure that users can access ProjectLink on their computer, you should allow users to physically install ProjectLink through the Install wizard as previously described in this section. If it is not possible for each user to physically install ProjectLink (e.g., the administrator performs the install for all users), you can enable access to ProjectLink on a users computer by performing the following steps after ProjectLink is installed: 1On the users computer, log in using the same login that was used to install ProjectLink (e.g., 'Administrator'). 2Using the Start, Run utility, type regedit and click OK. 3In the Registry Editor, navigate to the following directory: HKEY_CURRENT_USER\Software\Microsoft\Office\MSProject\ Addins 4Select the PMAddin.PrimaveraAddin folder. 5Choose Registry, Export Registry File. 6Export the registry file to a location on the users computer that the user can access (e.g., c:\<user>\My Documents). 7Login to the users computer with the users login.

8Repeat steps 2 and 3. 9Choose Registry, Import Registry File. 10Import the registry file you exported in step 6. The user should now be able to access ProjectLink on the local machine.

Installing and/or Upgrading the Stand-Alone Version

Before you begin, make sure your computer is running Windows XP Professional (SP2) or Windows Vista. Also, even though you are running Primavera as a stand-alone product, a network interface card or modem must be installed and TCP/IP networking software must be running on the computer.
Primavera recommends that you make a backup copy of your database before you upgrade. Be sure you check in any projects that are checked out before you upgrade the database. When installing Primavera on Windows XP or Vista, you must have administrator rights to your computer. See your network administrator for more information or contact Primavera Customer Support. If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.

Install/upgrade the stand-alone version Complete the following steps to install/upgrade the Primavera stand-alone version.
The following instructions assume you are installing or upgrading the stand-alone version only and that you have completed the steps detailed in Preliminary steps for installing the client modules, additional components, and the standalone version on page 282.

1On the Select Features to install dialog box, mark the checkbox next to Sample Projects if you want to install sample projects. 2Select the program folder name in which the Primavera icons will be stored on the Start menu. If you make no changes, these icons are stored under Programs, Primavera.
If you are upgrading from a previous version, you might be prompted that a Primavera folder already exists. Click Yes to install P6 in this folder.

3If installing the standalone version for the first time on this computer, on the Select License File dialog box, in the Select a license file for the newly created database field, browse to the location of the LICENSE.TXT file. 4Click Install to begin the installation/upgrade. During the installation, the setup program automatically installs and configures Microsoft.NET Framework and Microsoft SQL Server Express. The setup also installs/upgrades the project management and methodology management databases.
If a Primavera MSDE instance is already present on your computer, the setup will upgrade it to a SQL Server Express instance.

5On the InstallShield Wizard Complete dialog box, choose whether to restart your computer now or later, then click Finish. After the installation is complete, you must restart your computer before you can use the software. You can launch a module by clicking Start, Programs, Primavera, then select the module of your choice.

Read this chapter to upgrade your database to P6 version 6.1 when version 5.0 or 6.0 is already installed. You need to upgrade your database if you want to preserve your project data for use with the new version of Primavera. A wizard automatically upgrades your database for you. Primavera recommends that you upgrade your database automatically as described in this chapter; however, if you want to manually upgrade your database, manual upgrade instructions are included on CD 3. The manual upgrade documents are available in the \Documentation\<language>\ Technical Documentation\Manual Upgrades directory. If you are upgrading a standalone installation, see Installing and/or Upgrading the Stand-Alone Version on page 299. In this chapter:
Upgrade Process Overview Upgrading an Oracle Database to P6 Upgrading a Microsoft SQL Server Database to P6

Automatic Database Upgrade

Upgrade Process Overview
You can upgrade your existing Primavera database (v5.0 or 6.0) to P6 version 6.1. You must upgrade both your project management and methodology management databases so they will work with the new version.
To upgrade a stand-alone installation, see Installing and/or Upgrading the Stand-Alone Version on page 299.

You can upgrade your database automatically using the Database wizard. The wizard runs the necessary scripts to upgrade the database structure and an upgrade program to add data required by the new version. To upgrade from version 5.0 or 6.0 The following list summarizes the steps required to upgrade to P6 version 6.1:
Back

up your project management and methodology management databases before beginning the upgrade process to ensure you will not lose any data due to unexpected problems.
Run

the Database wizard to automatically upgrade your existing project management and methodology management databases.
Test

the new databases to ensure the upgrade succeeded. the new Group Server and any additional components as described in this guide.

Install

Privileges The following privileges included in the P6 Project Management module are either new or modified. Assign them to your users as needed if you are currently using a previous version. New Global Privileges New Project Privileges

Edit User Defined Fields (modified) Edit User Interface Views Edit Global Project/WBS Layouts and Portfolio Views Edit Global Scenarios Edit Global Dashboards Import Global Data for XER, MSP, XLS, and P3 Import XML

View Timesheets in Reports Edit Resource Assignments for Resource Planning Edit Role Assignments for Resource Planning Edit Committed Flag for Resource Planning Edit Future Periods Add/Edit Project Level Layouts Edit Projects from Scorecards

If you are currently running Primavera with Oracle, see Upgrading an Oracle Database to P6 on page 304. If you are currently running Primavera with Microsoft SQL Server, see Upgrading a Microsoft SQL Server Database to P6 on page 306.

Upgrading an Oracle Database to P6

If you want to use the databases from Primavera 5.0/6.0 with P6 version 6.1, you need to upgrade them by performing the following sets of steps. Although recommended, it is not required that these steps be performed by an experienced database administrator. The wizard runs the necessary scripts to upgrade the database structure and an upgrade program to add data required by the new version. You must upgrade your project management and methodology management databases. Oracle Requirements The following should be noted if you are upgrading an Oracle database:
The

upgrade will fail if you are using any Oracle version prior to 10.2.

Datafiles

in the LOB tablespace (e.g., PMDB_LOB1) should be made to autoextend. The estimated sizing is not exact, and the database conversion may fail if the datafiles are a fixed size.
If

your existing database uses code page WE8ISO8859P1 and you want to use the Euro symbol, you will need to convert your database to WE8MSWIN1252 using the following statement: ALTER DATABASE CHARACTER SET WE8MSWIN1252; Upgrade an Oracle project management or methodology management database 1Perform a cold backup and a full database export. If you are unsure how to back up your Oracle database, do not proceed with the upgrade. Contact your database administrator, your database vendor, or Primavera Systems for assistance in backing up your database before performing the database upgrade. Also, ensure that you are familiar with the process of restoring the backup copy of the database in case you need to do so. 2Double-click ConfigAsst.exe in the \install\database directory of CD 1 to start the Database wizard. 3On the Welcome dialog box, Choose Upgrade an existing Primavera database. In the Key field, enter the product key located on the License CD label. 4On the Database Upgrade dialog box, click Next to begin the upgrade process. 5On the Select Database Type dialog box, choose Oracle. 6On the Log on as Administrator User dialog box:

In the Username field, log on to the database as an administrative user, such as ADMUSER. The username, such as ADMUSER, must have DBA privileges and must be the owner of the application tables. The database must also have the Oracle compatible parameter set to 10.2 or greater. In the Password field, type the password for the Username. In the Oracle connect string field, specify the Oracle connection string. You must specify the Oracle connection string. It can be found in the TNSNAMES.ORA file. The TNSNAMES.ORA file is created when you or your DBA set up the Oracle client. 7On the Privileged Database Username dialog box, in the Oracle Username field, select your privileged user name for the database; for example, PRIVUSER. 8On the Ready to Begin Upgrading Data dialog box, choose Yes, I want to upgrade my database, then click Next. The current version of your existing database appears. The upgrade process could take several minutes, depending on its size. 9Click Finish when the Database Upgrade Completed message is displayed. 10Run the Database wizard again to upgrade your methodology management database. 11Run the Database Configuration wizard from the client and update your license in the database. Refer to the Changing Database Configuration Settings on page 317 for more information. 12Your database is now ready to use with P6.

Upgrading a Microsoft SQL Server Database to P6

If you want to use the databases from Primavera 5.0/6.0 with P6 version 6.1, you need to upgrade the database(s) by performing the following sets of steps. It is not required that these steps be performed by an experienced database administrator. The wizard runs the necessary scripts to upgrade the database structure and an upgrade program to add data required by the new version. You must upgrade both the project management and the methodology management databases. Upgrade a Microsoft SQL Server database 1Perform a full backup of the current databases. If you are unsure how to back up your SQL Server database, do not proceed with the upgrade. Contact your database administrator, your database vendor, or Primavera Systems for assistance in backing up your database before performing the database upgrade. Also, ensure that you are familiar with the process of restoring the backup copy of the database in case you need to do so. 2Double-click ConfigAsst.exe in the \install\database directory of CD 1 to start the Database wizard. 3On the Welcome dialog box, Choose Upgrade an existing Primavera database. In the Key field, enter the product key located on the License CD label. 4On the Database Upgrade dialog box, click Next to begin the upgrade process. 5On the Select Database Type dialog box, choose Microsoft SQL Server or SQL Express. 6On the Log on as Administrator User dialog box:

In the System Admin Name field, register to the server as user SA or another user with system administrator privileges. In the System Admin Password field, type the password for the user. In the Server Name field, specify the name of the server machine you are connecting to. In the Database Name field, specify the name of the database you are connecting to. 7On the Privileged Database Username dialog box, in the SQL Server Username field, enter your privileged user name for the database; for example, PRIVUSER. Also enter the password for that user. 8On the Ready to Begin Upgrading Data dialog box, choose Yes, I want to upgrade my database, then click Next. The current version of your existing database appears. The upgrade process could take several minutes, depending on its size. 9Click Finish when the Database Upgrade Completed message is displayed. 10Run the Database wizard again to upgrade your methodology management database. 11Run the Database Configuration wizard from the client and update your license in the database. Refer to Changing Database Configuration Settings on page 317 for more information. Your database is now ready to use with P6.

This section provides instructions for creating an unattended setup of Primavera applications and running an unattended setup on client computers. An unattended setup enables administrators to install Primavera applications on client computers without having to run through the setup process each time. It also ensures that each user receives the same Primavera configuration.
You cannot use unattended setup for a stand-alone configuration.

In this chapter:
Creating Unattended Setup Files Running an Unattended Setup

Creating and Running an Unattended Setup

Creating Unattended Setup Files
An unattended setup allows an administrator to install Primavera modules on a client computer without having to answer the configuration prompts of the Setup wizard. All configuration details for the installation are specified when the unattended setup files are first created. You can choose which client modules to install, configure the connection to the project management database, and specify the destination folders where the program files are copied. Unattended installations ensure that all client modules are configured identically at setup. To create an unattended setup, you enter command lines to automatically create a response file and launch the Primavera Setup wizard. The response file records the configuration settings you specify during the setup process. When completed, you can copy the response file to a network location which a user with administrator privileges can access from any networked computer. The unattended setup can be run by an administrator on client computers by entering the appropriate command lines. The unattended setup will silently install Primavera according to the configuration you specify in the response file.
For information on running an attended setup, see Running an Unattended Setup on page 314.

You can also rerun the Setup wizard to recreate a set of unattended setup files or to create multiple sets of files for different configurations.

Create unattended setup files 1Select a computer that does not have Primavera currently installed. 2Copy the contents of CD 1 to a folder on the local machine. Primavera recommends creating a new folder (e.g., Primavera_Install). Do not include spaces in the folder name. 3Open a command line by choosing Start, Run. Type cmd and click OK. 4Enter a command line that will access the directory to which you copied the Primavera installation files. For example,
cd c:\Primavera_install In the next step, you will enter a command that creates a response file, then automatically launches the Primavera setup in record mode. The response file will record your selections while you proceed through the Primavera setup. Users with administrator privileges will then be able to install Primavera from the response file you create. There are no restrictions on the name of the response file; however, Primavera recommends that you name it setup.iss.

5Enter the following command line to create a response file and to launch the Primavera setup in record mode, where pathname = the directory you accessed in Step 4 (e.g., Primavera_install):
setup /r /f1"c:\pathname\setup.iss" Do not include a space between the f1 and the quote ".

The Primavera setup launches automatically. On the Welcome dialog box, read the recommendations and click Next.
Click Next on each wizard dialog box to advance to the next step.

6On the Product Code dialog box, enter the product key located on the License CD label. 7Accept the license agreement. 8On the Setup Type dialog box, choose Custom. 9On the Choose Destination Location dialog box, accept the default installation folder or click Browse to specify a different folder. 10On the Choose Destination Location (common files) dialog box, accept the default location for Primavera common files or click Browse to specify a different folder. 11On the Select Features to install dialog box, mark the checkbox next to each application you want installed when a user with administrator privileges runs this unattended setup on a client machine. If you select only the Software Development Kit, components from the Project Management and Methodology Management modules are also installed.
You should not include the Job Service or Distributed Job Service when configuring an unattended setup unless you are creating an unattended setup that will only be run on server machines that you intend to use as Job Service or Distributed Job Service servers.

12If you chose to include the Job Service or Distributed Job Service in the previous step, enter or select the database alias of the job service database. 13On the Select Program Folder dialog box, accept the default location (Primavera) for Primavera program icons or select/type a different folder name. 14On the Ready to Install the Program dialog box, click Install to begin the installation.

15When the installation is complete, you are prompted to configure the database connection(s). The connections you must configure, and the order in which you are prompted, depend on the applications you chose to install in step 11.
If you chose to include the Job Service or Distributed Job Service in the unattended setup, you are first prompted to configure the job service database. Click Yes. After configuring the job service database, you are prompted to test the database connection. Click Yes to test the connection, or No to continue configuring database connections.

When prompted, click Yes to configure the project management or methodology management database connection. 16On the Select Driver Type dialog box, choose the database type from the list in the Project Management driver type field. 17If users will be connecting using SQL Server, on the Configure SQL Server Connection dialog box, enter the server host name and the database name. The host name is the name of the computer or IP address where Microsoft SQL Server is installed. The database name was specified when the database was created; for example, PMDB. If users will be connecting using Oracle, on the Configure ORACLE Connection dialog box, enter the Oracle connection string; for example, PMDB.
Before you enter the database information, confirm that all users with administrator privileges who will be running the unattended setup have access to the specified database.

18On the Enter Public Login Information dialog box, enter your public login information that was defined by your administrator; for example, a Username of pubuser, and a group ID of 1. 19On the Validate Database Connection dialog box, click Next to test the database connection. If the connection is not valid, you can go back and change your settings. 20On the Connection Successful dialog box, click Finish. 21If you chose to include the Methodology Management module in the unattended installation, repeat steps 15 - 20 to configure the methodology management database. 22Copy and paste the contents of the folder you created in Step 2 to a network location accessible to all computers that need to run the unattended setup. This folder should contain the contents of CD 1 as well as the 'setup.iss' response file. Refer to the next section for instructions on running an unattended setup on a client machine.

Running an Unattended Setup

An unattended setup is a special installation program that uses the configuration file you or another administrator created in the previous section (Creating Unattended Setup Files on page 310) to supply information such as the module to be installed, the database connection settings, and the destination folders for the installation. This configuration file is typically named 'setup.iss;' however, the administrator who created the configuration file may have provided a different name. Running an unattended setup saves you time and effort, and it ensures that every Primavera client module is configured identically at setup. If the 'setup.iss' (or equivalent) file has been stored on a network server, you can run the unattended setup from any client computer with a network connection to that server.
The 'setup.iss' (or equivalent) file and the contents of CD 1 must be stored in the same folder on the network server.

As an administrator, you have several options for installing Primavera on client machines using the unattended setup. For example, you can physically run the unattended setup on each machine, write scripts that will run the unattended setup on the client machines you specify, or provide these instructions to users with administrator privileges, who can run the unattended setup on his/her computer.
The following instructions assume that an administrator or the owner of the client computer is physically running the unattended setup from the client computer. Also, as an example, the folder containing the required files is named "Primavera_install," the setup file is named 'setup.iss,' and the log file is named 'setup.log.' The administrator who

configured the unattended setup may have provided different names.

Run an unattended setup 1On the client computer, open a command line by choosing Start, Run. Type 'cmd' and click OK. 2Enter a command line that will access the directory on the network server that contains the CD 1 files, the 'setup.iss' file, and the 'setup.log' file. For example,
cd e:\Primavera_install

If you are unsure of the location of the unattended setup file, refer to your system administrator. 3Enter a command line to run the unattended setup, where pathname = the directory you accessed in step 2 (e.g., Primavera_install). For example:
setup.exe /s /f1"e:\pathname\setup.iss" /f2"c:\pathname\setup.log" Do not include a space between the f1 and f2 and the parentheses (").

The Primavera installation launches automatically. You will not see a dialog box; however, a Primavera taskbar icon indicates that the installation is in progress. The installation is complete when the taskbar icon closes. 4Confirm that the files were successfully installed by navigating to the appropriate folder on the local drive. By default, Primavera applications are installed in c:\Program Files\ Primavera. The administrator who configured the unattended setup may have supplied a different default installation folder. If the Primavera applications were not installed, or if you cannot run a Primavera application, contact your system administrator. All errors are logged in the 'setup.log' file (or equivalent).

The Database Configuration wizard enables you to alter database connection settings for Primavera client modules. This chapter describes how to change database connection settings, configure licenses, change user passwords, and administer login names and passwords. In this chapter:
Changing Database Connection Settings Performing Administrative Tasks

Changing Database Configuration Settings

Changing Database Connection Settings
Use the Database Configuration wizard to change connection settings for a client module if your database server configuration changes. For example, if the database is moved to a new server, run the Database Configuration wizard to configure the connection to the new server.
To be able to change database connection settings, the Database Configuration wizard must access the modules initialization (INI) file. This file is located in the modules folder; for example, the INI file for the Project Management module is PM.INI. If the wizard cannot locate the modules INI file, you will be prompted to browse for it.

Change database configuration settings 1From the client computers desktop, click Start, then choose Programs, Primavera, Help and Utilities, Database Configuration. 2On the Welcome dialog box, click Next.
Click Next on each wizard dialog box to advance to the next step.

3On the What would you like to do? dialog box, choose Configure my database connections. 4On the Select Database Alias dialog box, choose the appropriate database; for example, PMDB. 5On the Select or Create Alias dialog box, select the alias and driver type of the database. If you are changing the alias or database driver, type the new alias (for example, PMDB) or select the new driver type. 6Type the new connection settings for the database. If the client computer is connecting to an Oracle database, on the Configure ORACLE Connection dialog box, type the connection string, which can be found in the TNSNAMES.ORA file. If the client computer is connecting to Microsoft SQL Server or SQL Server Express, on the Configure SQL Server Connection dialog box, type the server host name and the database name. The database name was specified when the database was created; for example, PMDB. The host name is the name of the computer or IP address where Microsoft SQL Server is installed. 7On the Enter Public Login Information dialog box, enter your public login information that was defined by your administrator; for example, a Username of pubuser, and a group ID of 1. The public login is used by module users to connect to the database. 8On the Validate Database Connection dialog box, click Next to test the database connection. If the test connection fails, you can ignore the error or click Back to correct the settings now. 9On the Connection Successful dialog box, click Finish. If you create a new DB alias for a module, the modules INI file is updated to reflect the change. If multiple modules are installed on one client computer, changing the DB alias for one module does not affect the other modules. If you change the database connection settings for a DB alias and multiple modules share that alias to access the database, your changes affect all the modules that share the alias.

Performing Administrative Tasks

Use the Database Configuration wizard to configure application licensing, change user passwords, and administer private database logins. If you want to configure application licensing, you can use the wizard to connect to the database and store the license in the database. You can store two types of licenses using the Database Configuration wizard: the new license you receive from Primavera when you implement a new or upgraded Primavera installation; or, the incremental license you receive from Primavera when you purchase additional users for your existing license. You can also use the Database Configuration wizard to change the passwords of module user logins. Note that these logins are not database logins but are the Primavera logins that are administered using the Project Management module. Private database logins are used primarily by administrators to gain direct access to a database. For example, the privileged user login that you use to access the database is a private database login. You can modify existing logins or create new ones using the Database Configuration wizard. Run the Database Configuration wizard Whether you are configuring application licensing, changing user passwords, or administering private database logins, most of the steps required to perform these administrative tasks are the same. Complete the following steps to perform all of these tasks:

1From the client computers desktop, click Start, then choose Programs, Primavera, Help and Utilities, Database Configuration. 2On the Welcome dialog box, click Next.
Click Next on each wizard dialog box to advance to the next step.

3On the What would you like to do? dialog box, choose Administration Tasks. 4On the Select Administration Task dialog box, choose the appropriate administrative task. 5On the Select Database Alias dialog box, select the appropriate database. 6On the Database Configuration dialog box, type the name and password of a privileged database user. This login should have administrative rights on the database. 7Complete the following instructions that correspond to the administrative task you are performing: To configure application licensing: You can paste a license or load one from a file. To paste a new license in place of the old license, copy the license, click Paste, and click Yes to overwrite the old license. To add a license from a file, click Open. Click Finish to close the wizard.

After applying any licensing changes that affect P6 Web Access, the application server hosting P6 Web Access must be restarted before the changes will take effect.

To change user passwords: Select the module login and set its new password. Click OK, then click Finish to close the wizard.

To administer private database logins: Review the explanation of private database logins and click Next. To modify the settings for a login, click the appropriate cell and type the new value. To add a new login, click Add. To delete a login, select the login and click Delete. Click Finish to close the wizard.

This chapter describes the Primavera authentication modes, outlines the steps required to implement an authentication scheme, and explains how to use the configuration wizard to specify the mode you want to use for client/server and Web modules. In this chapter:
Authentication in Primavera Process Overview Choosing an Authentication Scheme Login Procedures and Authentication

Configuring Authentication Modes

Authentication in Primavera
Typically, within an enterprise, user access to software applications is managed through authentication and authorization mechanisms. Simply put, authentication is the process of validating user identity and authorization is the mechanism used to control access to specific resources or data. Primavera supports three authentication modes: Native (the original Primavera authentication scheme), Single Sign-On, and LDAP.
Native

Native authentication is the default mode for all Primavera modules. In this mode, when a user attempts to log in to a Primavera module, authentication is handled directly through the module with the Primavera database acting as the authority.
Single

Sign-On Single Sign-On authentication, which provides access control for Web applications, is available for Group Server and P6 Web Access. In this mode, when a user attempts to log in to a Primavera module (protected resource), a Web agent intercepts the request and prompts the user for login credentials. The users credentials are passed to a policy server and authenticated against a user data store. With Single Sign-On, a user logs on only once and is authenticated for all Web applications for the duration of the browser session (provided that all Web applications authenticate against the same policy server).
LDAP

(Lightweight Directory Access Protocol) LDAP is directory-based authentication and is available for client/server and Web applications. In this mode, when a user attempts to log in to a Primavera module, the users identity is confirmed in an LDAP-compliant directory server database.
If the Project Management module is configured for Single Sign-On or LDAP authentication, all Project Management module applications (e.g., Update Baseline, Schedule Comparison) or third-party applications (e.g., Pertmaster) that use the Primavera Integration API must be separately configured for Single Sign-On or LDAP authentication using the API AdminApp java utility. For more information on the API, refer to the Primavera Integration API Administrators Guide on the Integration API CD.

Regardless of the authentication scheme you choose, Primavera controls user authorization though the project management or methodology management database. For details about user authorization, see Administering Users and Security on page 341.

Process Overview
By default, all Primavera modules are installed using Native authentication. After you install Primavera client/server modules and additional components, you can choose a different authentication scheme. To specify an authentication scheme:
The Borland Database Engine and the database client software must be installed on the machine used to run the Authentication Configuration wizard.
Run

the Authentication Configuration wizard to choose an authentication mode for the project management database (PMDB) and, if applicable, methodology management database (MMDB).
Configure

settings in the Timesheets Web site file erps8X6.html. For information, see Configuring the Group Server for Timesheets on page 91.
Configure

administrative settings for P6 Web Access. For information, see Installing P6 Web Access on page 125.

If you are upgrading from a previous version of Primavera software, refer to the procedures in Automatic Database Upgrade on page 301 before running the Authentication Configuration wizard.

Authentication mode is database-driven, so the Authentication Configuration wizard enables you to first specify a database

connection setting, then choose authentication modes for the modules that access that database. Although the wizard prompts you to separately choose an authentication mode for client/server modules and Web modules, you must use a consistent authentication scheme within the Primavera suite when choosing Native authentication; that is, both client/server and Web modules must use Native mode. LDAP authentication can be used for both client/server and Web modules, or LDAP client/server authentication can be combined with Single Sign-On, which is available only for Web modules. For LDAP authentication, the configuration utility also enables you to specify LDAP servers, map LDAP attributes to Primavera database fields, and provision users.

Choosing an Authentication Scheme

After installing Primavera, use the Authentication Configuration wizard to set up an authentication scheme, which includes one or more of the following steps:
Selecting

an authentication mode LDAP servers LDAP user information to a Primavera database

Configuring Provisioning

Depending on the authentication modes you select for client/server and Web modules, the wizard guides you through the applicable steps. When initially configuring Primavera modules to use LDAP mode for either client/server or Web modules, you can provision users. Once you have configured an LDAP authentication mode, you can also run the Authentication Configuration wizard at a later time to reprovision user information as necessary. The Authentication Configuration wizard is provided on CD 1. You can run the wizard directly from the CD. To set up an authentication scheme 1On CD 1, in the Install\Database\ldap_config directory, double click on the file LDAPCfgWiz.exe. 2Select the database alias you want to provision LDAP information for, then type the database user name and password.

3Choose to configure an authentication mode.

The Import option is active only if the database has previously been configured for either LDAP or Single Sign-On mode.

4Choose an authentication mode for the client-server and Web modules.

If you choose Native, the Finish button becomes active so you can exit the wizard. For all other authentication mode selections, continue through the wizard to configure additional information as described in the following steps. 5To add a new LDAP server, click Add. If previously configured LDAP servers are listed, you can modify the information or remove server entries.

6On the General tab, specify the LDAP directory server host name or IP address, listening port, and Base Directory

Node. For Base Directory Node, specify the location in the directory information tree (DIT) that is the location from which to start the search for module users during login. Base Directory Node is also the location where the provisioning function begins the search for directory server users. To use SSL protocol for communication with the LDAP server, mark the Enable SSL checkbox.
For P6 Web Access, if choosing SSL, you will need to configure two settings that identify the location and password for the keystore that holds the SSL certificate. For details about configuration settings for P6 Web Access, see Installing P6 Web Access on page 125.

If the LDAP server does not allow anonymous searches, click the Login tab. Type the user name and password of an LDAP server user who has search access for the Base Directory Node you specified on the General tab.

When you are finished configuring the LDAP server, click OK or, to validate connection with the LDAP server, click Test, then click OK after a successful connection message.
USER_NAME is a required field that must be mapped and can not be deleted. Up to four fields can be mapped between the LDAP store and the project management/methodology management database.

7Select an LDAP server. Then, in the LDAP attribute column, specify the term/field in the LDAP store that corresponds to the Primavera project management/methodology management database USER_NAME field. Optionally, specify the LDAP term/field for e-mail address, actual name, and office phone number. To add fields, click Add. To remove a field, select it and click Remove.
If you are unsure of the correct LDAP terms, check with your LDAP directory server administrator.

8To provision LDAP user information to the Primavera database, click Next. You can search the LDAP directory server or import an LDIF file to provision users. To exit the wizard, click Finish. 9Click Search and Import Users.

When you provision users, changed records are updated in the Primavera database and new users are added. However, users that have been deleted from the LDAP directory or LDIF file are not automatically removed from the Primavera database. You will need to manually delete these users.

10To import from an LDIF file, click Load LDIF, then navigate to the file you want to import and click OK. To import from an LDAP server, you can run an existing search or define a new search. If one or more previously defined searches exist, the name of the most recently run search is displayed next to the Search Name drop-down list. To initiate the current search, click Run Search. Results display in the Available Users section. To specify a new search, click Define Criteria.

When you click Define Criteria, the Select/Define Searches dialog box displays so you can add, modify, and delete

searches. To add a search, click Add. Type a unique name for the search. In the Search criteria field, specify the LDAP search filter you want to use. When finished specifying criteria, click Save, then click Close.
Search filter syntax should adhere to the rules outlined in RFC 2254.

To modify a search name or criteria, edit the existing information, click Save, then click Close. To delete a search, select it. Click Remove, then Close.

After provisioning users, you will need to set up Primavera user accounts for the imported users by assigning security profiles and licenses through the Project Management or Methodology Management modules.

11When finished importing user information, in the Import LDAP Users dialog box, click Close. To exit the Authentication Configuration wizard, click Finish. To provision LDAP user information to the Primavera database
When you provision users, changed records are updated in the Primavera database and new users are added. However, users that have been deleted from the LDAP directory or LDIF file are not automatically removed from the Primavera database. You will need to manually delete these users.

1On CD 1, in the Install\Database\ldap_config directory, double click on the file LDAPCfgWiz.exe. 2Select the database alias you want to provision LDAP information for, then type the database user name and password.

3Choose to import user information.

The Import option is active only if the database has previously been configured for either LDAP or Single Sign-On mode.

4Follow steps 9 - 11 (beginning on page 332) in Choosing an Authentication Scheme which describes how to set up an authentication scheme, including the provisioning of users.

Login Procedures and Authentication

Login procedures for Primavera modules vary according to the authentication mode selected. In Native mode
Primavera

modules present a login dialog that prompts for a user name and password. In Native mode, the use of passwords is optional. In LDAP mode
All

Primavera modules (Project Management, Methodology Management, Timesheets, P6 Web Access, and Software Development Kit) require a login password. Additionally, because passwords are stored and authenticated against an LDAP directory, the capability for users to change passwords within a Primavera module is disabled. In Single Sign-On mode
For

Timesheets, the Primavera login dialog box never appears. Instead, login credentials are requested and validated by SiteMinder. Once a user is authenticated, the Timesheets launch page appears.

For

P6 Web Access, login credentials are requested and validated by SiteMinder. Once a user is authenticated, the launch page for P6 Web Access appears so the user can select a database and language. The capability for users to change passwords within Timesheets and P6 Web Access is disabled because passwords are stored and authenticated against a directory server user store.

Administering Users and Security Defining Administrative Preferences and Categories in Project Management Defining Administrative Preferences and Categories in Methodology Management Implementing Timesheets Defining Financial Periods In this part:

Part

Primavera Application Administration

his part describes how to set up security and preferences after all needed Primavera components are

installed. Read Administering Users and Security to learn how to use the Project Management module to set up user accounts to secure project data. Defining Administrative Preferences and Categories in Project Management explains how to apply a series of parameters and values that apply to all projects in the Project Management module. Read the Defining Administrative Preferences and Categories in Methodology Management chapter to learn how to apply a series of parameters and values that apply to all methodologies in the Methodology Management module.

If you installed Timesheets, refer to Implementing Timesheets to set up users and timesheets, and to configure access to Timesheet Approval. In the Defining Financial Periods chapter, learn how to define Primavera enables multiple users to work simultaneously in the same projects across an enterprise. To ensure that data is protected from unauthorized changes, you can create global and project security profiles that control access. You can then set up users and assign organizational breakdown structure (OBS) elements to users, project profiles, and enterprise project structure (EPS) nodes. You can additionally configure resource security and define access to P6 Web Access functionality. Read this chapter to understand the process for setting up users and implementing security in Primavera. In this chapter:
Understanding Security in Primavera Process Overview Defining Global Profiles Defining Project Profiles Adding Users in the Project Management Module Assigning OBS Elements and Project Profiles Assigning OBS Elements to the EPS Defining User Access to Resources Defining User Access to P6 Web Access Functionality Setting Security in the Methodology Management Module

Administering Users and Security

Understanding Security in Primavera
Each person who will be using any component of the Primavera suite must be registered as a user with the appropriate licensing rights. Additional security privileges determine each users access to data. Use the Project Management module to administer security for the Project Management and Timesheets modules, and P6 Web Access. The Methodology Management module administers its own security.
The Methodology Management module uses its own set of users and security profiles to control access to methodology data. See Setting Security in the Methodology Management Module on page 393

To ensure security at various levels of data, the Project Management module provides two sets of security profiles:
Global

profiles Define a users access to application-wide information and settings, such as the enterprise project structure (EPS), resources, roles, and cost accounts. Each user must be assigned a global profile.
Project

profiles Define a users access to project-specific information. The Project Management module does not require that each user be assigned a project profile; however, users cannot access projects unless they are assigned a project profile or the global profile, Admin Superuser. You can create a set of profiles that limit access to global information and then assign the appropriate global profile to each user. Similarly, to limit privileges for each project, you assign the appropriate project profile to each user via an organizational breakdown structure (OBS) element. When you create the EPS for your company, you must identify an OBS

element, or person responsible, for each node and project within the EPS. This OBS element assignment determines the users rights to the EPS level (and all levels below it). You can further control access to specific project data by assigning a responsible OBS element to each work breakdown structure (WBS) element within a project. You can also control user access to resource data by implementing resource security. The following diagram illustrates the relationships between a user, the OBS, EPS, and WBS. If a user will be accessing Timesheets to update time, he/she will also need to be associated with a resource in the Project Management module.

Useful Primavera Terms

Review the following Primavera terms to help you better understand how to administer users and security: User Any person who needs access to Primavera components, including the Project Management, Methodology Management, Timesheets modules, and P6 Web Access. Resource The people, materials, and/or equipment that perform the work on activities. In the Project Management module, you can build a resource hierarchy that includes the required resources across all projects in the enterprise. Resources are assigned to activities in the Project Management module and can be set up to use Timesheets to report actual workhours. OBS A global hierarchy that represents the managers responsible for the projects in your enterprise The OBS usually reflects the management structure of your organization, from top-level personnel down through the various levels constituting your business. The OBS can be role-based or name-based. EPS A hierarchy that represents the breakdown of projects in the enterprise. Nodes at the highest, or root, level might represent divisions within your company, project phases, site locations, or other major groupings that meet the needs of your organization, while projects always represent the lowest level of the hierarchy. Every project in the enterprise must be included in an EPS node. WBS A hierarchical arrangement of the products and services produced during and by a project. In the Project Management module, the project is the highest level of the WBS, while an individual activity required to create a product or service is the lowest level. Each project in the EPS has its own WBS. An OBS is not the same as a resource pool. While resources are assigned to activities, OBS elements are associated with EPS nodes and projects. The OBS element corresponding to an EPS node is the manager responsible for all work included in that branch of the hierarchy. In this way, an OBS supports larger projects that involve several project managers with different areas of responsibility. A user does not have to be included in the OBS if he/she may need to access the Project Management module but is not part of the responsible management structure. Similarly, a user may or may not be a part of the resource hierarchy. For example, if the user is a resource assigned to activities and needs to update a timesheet in Timesheets, he/she must be included in the resource hierarchy; however, a user who is an executive requiring access to the Web Portfolio Management application is not a part of the resource pool. For more information on resources, OBS, EPS, and WBS, see the Project Management Reference Manual. Review the following portions of a sample EPS for an IT department and its corresponding portion of the OBS.

With these structures defined, you can map users to their corresponding roles in the OBS, which in turn can be assigned to

each level in the EPS. The EPS level to which you assign the OBS determines the nodes/projects the associated user can access. For example, if you assign an OBS element to the root node of the EPS, the users associated with that OBS element can access the projects in the entire EPS. If you assign an OBS element to one branch of the EPS, the associated users can access only projects within that branch. The project profile associated with each OBS element determines which data items in the projects the user can access. Only one OBS element can be assigned to each EPS level. For example, suppose that two project profiles are defined: one that allows edit access to all data, including administration rights (Project Administrator profile), and one that allows viewing and editing of most, but not all, project data (the Project Management module profile). Marie Ross, Vice-President of Technology Services, is assigned the Project Administrator profile. The OBS element, Technology Services, is assigned as the responsible manager at the Tech. Services node of the EPS, indicating that Marie Ross has access to all nodes and projects within Tech. Services. If Gretchen Schantz is the Director of the Information Technology Department, she can be assigned Project Administrator rights to all projects under Internal IT Projects.

You can further control the access to projects by assigning OBS elements at the project and/or WBS level.In the previous example, if Dee Morris is the Project Manager in the IT Department responsible for the Network Upgrade project, you can assign her to that OBS element with a Project Manager profile. She would then have editing access to just that project. As another example, if the Design Team needs access to only the design portion of the Network Upgrade project, you can assign the Design Team to just the WBS branch in the Network Upgrade project that involves the project design. You can assign multiple users to the same OBS element and/or you can assign each user to multiple OBS elements. This flexibility enables you to provide access to the same EPS branch or project to more than one responsible manager (OBS element), and it allows you to control access by the same user across different EPS nodes and projects. For example, suppose Dee Morris, the Project Manager in the IT Department responsible for the Network Upgrade project, also needs access to the Hardware Upgrade project; however, for this project, you want to limit her access to reviewing and editing financial data only. Also suppose that Jim Harkey, another Project Manager in the IT Department, is responsible for the Hardware Upgrade project. He needs Project Manager access to that project, but he also needs to review financial information in Dees Network Upgrade project. You first would create another project profile that specifies viewing/editing rights to just project costs and financial data (Account Manager profile) and then make the following assignments:

To designate that Jim Harkey has Project Manager rights to the Hardware Upgrade project and Dee Morris has Account Manager rights to the Hardware Manager project, you would need to add another element to the OBS.

With these assignments, Jim Harkey and Dee Morris now have Project Manager rights to their primary projects and Account Manager rights to their secondary projects. The following section provides guidelines for setting up users and administering security in Primavera.

Process Overview
Enterprise project management involves a structured approach to managing several ongoing projects and teams across multiple locations at the same time. To ensure good results, up-front planning and coordination by various members of the

enterprise are essential. Before you can use Primavera to manage your projects successfully, you must first administer users and set up structures in the Project Management module, including the organizational breakdown structure (OBS), enterprise project structure (EPS), and resource hierarchy. Once users and structures are in place, you can implement security to restrict and/or provide access to project data.
The Methodology Management module uses its own security model to control access to the methodology management database. See Setting Security in the Methodology Management Module on page 393.

The following steps provide guidelines and a general process for administering users and security in Primavera. Because the structures are global across the company, some steps may require information from many participants. You can vary the order depending on your companys implementation plan. Also, some of these processes, such as defining resource security and user interface views, are optional depending on the needs of your enterprise. 1Create global and project security profiles in the Project Management module. Define a standard set of profiles that determine access rights to global and project-specific data. Most likely, administrators perform this step. See Defining Global Profiles on page 353 and Defining Project Profiles on page 361. 2Add users in the Project Management module. You must add each user who needs access to any Primavera component. At a minimum, each user is assigned a login name, license, and a global profile. See Adding Users in the Project Management Module on page 368 for more information. 3Set up the OBS for your company and assign each element of the OBS to the appropriate users and project profiles.
The Project Management Reference Manual (PMRefMan.pdf) is available online and can be accessed from your industryspecific folder in the \Documentation\ <language>\ folder of CD 3. View the information using Adobe Acrobat Reader (also available on CD 3).

Identify your companys management structure and include the roles or names of those who will be responsible for the projects and work to be completed. See Setting Up the Organizational Breakdown Structure in the Project Management Reference Manual for more information. Also, see Assigning OBS Elements and Project Profiles on page 381. 4Set up the EPS for your company and assign the responsible manager (OBS) to each node. Identify your companys project structure, which is global across the enterprise. See Setting Up the Enterprise Project Structure in the Project Management Reference Manual for more information. 5Define the resources necessary to complete the projects across the enterprise, and link resources to users if they will be using Timesheets. See Defining Resources and Roles in the Project Management Reference Manual for more information. Also, see Adding Users in the Project Management Module on page 368 later in this chapter. 6Define user access to resource data. See Defining User Access to Resources on page 387. 7Define user interface views that restrict and provide access to P6 Web Access functionality according to the requirements of your companys functional roles. See Defining User Access to P6 Web Access Functionality on page 391.
Administrators can also set preferences for data in the Project Management module. See Defining Administrative Preferences and Categories in Project Management on page 401.

8Add projects to the EPS and define the WBS for each project. Project managers perform this step. They can further control security within their own projects by assigning specific OBS elements to WBS levels. Refer to the Project Management Reference Manual for more information.

The remainder of this chapter provides additional information on this process.

Defining Global Profiles

A global profile determines a users access to application-wide information and settings, such as resources, global codes, and the OBS. The Project Management module requires that you assign a global profile to each user. You can define an unlimited number of global profiles in the Project Management module. In addition, the Project Management module provides two predefined global profiles: Admin Superuser and No Global Privileges. The Admin Superuser profile allows complete access to all global information and all projects. This profile is assigned to the user Admin when you install Primavera modules. For security reasons, you should limit the Admin Superuser assignment to only those individuals who require access to all data.
At least one user must be assigned to the Admin Superuser profile. If only one user is assigned to this profile, the Project Management module does not allow that user to be deleted.

The No Global Privileges profile restricts access to global data. Assign this profile to anyone who is strictly a Timesheets user and does not require access to the Project Management module. If a user with licensed access to the Project Management module is assigned this profile, the user can log in to the Project Management module but has no access to project data and read-only access to global data. If a user is assigned this profile and is also assigned to an OBS element, the user will have access to project data as defined for the OBS element, but access to other global data is restricted. When defining each global profile, the Admin Superuser may designate that users have the ability to add/delete, edit, assign, or view secure codes. Secure codes enable privileged users to hide Project, Activity, and Resource codes from users that do not have security privileges to view them. Also, users with privileges to Edit Security Profiles can restrict other users to edit, assign, and view privileges. For example, management could track project approval processes through secure codes that others cannot edit or, in some cases, view. Secure codes are structured hierarchically. In other words, if a user is granted add/delete privileges, that user automatically has edit, assign, and view privileges. If a user is granted edit privileges, that user is automatically granted assign and view privileges. If a user is granted assign privileges, that user is automatically assigned view privileges.
The Project Management module does not limit the group of codes that a user can edit or assign. Once you designate a security privilege, the same security privilege applies to all codes (secure or not). If you designate add/delete, edit, assign, or view privileges to a user, that user has the ability to add/delete, edit, assign, or view all existing codes.

Create global profiles In the Project Management module, choose Admin, Security Profiles. Choose Global Profiles, then click Add. Type the new profiles name. To make the new profile the default global profile, mark the Default checkbox. In the Privilege area, mark the appropriate Has Privilege checkboxes to grant privileges to the profile.

For information on assigning global profiles, see Adding Users in the Project Management Module on page 368.

The following table defines each global privilege Privilege Name

Edit Global Change Definitions Edit Admin Preferences and Categories

Privilege Definition
Create, edit, and delete Global Change specifications available to all users. Change administrative preferences and categories as defined in the Admin Preferences and Admin Categories dialog boxes. Edit currency data in the Currencies dialog box.

Delete Resources

Remove resources from the project management database. This privilege automatically grants the Add Resources and Edit Resources privileges. Create resources. This privilege automatically grants the Edit Resources privilege. Edit resource data. Display resource price/unit (if the View Resource Costs global privilege is also granted), and resource skill level (a resources role proficiency), in reports. View, group/sort, filter, and report on resource and role proficiency. A user must have this privilege to view and search by resource and role proficiency in P6 Web Access. Review, approve, and reject submitted timesheets as a Resource Manager in the Timesheet Approval application. Create, edit, and delete cost accounts. Import projects, resources, and roles from XER, MSP, XLS, and P3 formats. A user must also have the Create Project within EPS project privilege to import and create new projects. A user must also be a super user to update a project from XER, XLS, or P3 formats, or to import MSP formats using Project Link. Import projects from Project Management module XML format. A user must also have the Create Project within EPS project privilege to import and create new projects. Create, edit, and delete global reports; edit report groups and global report batches; and save global reports created or modified by the Report Wizard. Create, edit, and delete global tracking layouts in the Project Management module. Create, edit, and delete global roles. Edit the name of global activity codes in both P6 Web Access and the Project Management module. This privilege automatically enables you to add, edit, and delete global activity code values as well. Add new global activity codes and code values in both P6 Web Access and the Project Management module. This privilege automatically enables you to edit existing global activity codes and code values as well. Delete global activity codes and code values in both P6 Web Access and the Project Management module. This privilege automatically enables you to add and edit global activity codes and code values as well. Add, edit, and delete issue forms and issue form categories in P6 Web Access. Enables access to the Issues menu in P6 Web Access. Create, edit, and delete global calendars and shifts.

Add Resources Edit Resources

View Resource Role Proficiency

Approve Resource Timesheets Edit Cost Accounts Import Global Data for XER, MSP, XLS, and P3*

Import XML*

Edit Global Reports

Edit Global Tracking Layouts Edit Roles Edit Global Activity Codes

Add Global Activity Codes

Delete Global Activity Codes

Edit Issue Forms

Edit Global Calendars

Edit Resource Calendars Edit Security Profiles Edit Users Edit Timesheet Dates Add/Edit Global Activity and Assignment Layouts and Filters Edit OBS Edit Project Codes

Create, edit, and delete resource calendars and shifts. Create, edit, and delete global and project security profiles. Add, edit, and remove Project Management module users. Create and delete timesheet batches. Create, edit, and delete global activity and resource assignment layouts, views, and filters.

Create, edit, and delete global OBS hierarchy. Edit the name of project codes. This privilege automatically enables you to add, edit, and delete project code values as well. Add new project codes and code values. This privilege automatically enables you to edit existing codes and code values as well. Delete project codes and code values. This privilege automatically enables you to add and edit project codes and code values as well. Edit the name of resource codes. This privilege automatically enables you to add, edit, and delete resource code values as well. Add new resource codes and code values. This privilege automatically enables you to edit resource codes and code values as well. Delete global resource codes and code values. This privilege automatically enables you to add and edit resource codes and code values as well. Create, edit, and delete global portfolios in the Project Management module and in P6 Web Access. Administer the list of global external applications.

Add Project Codes

Delete Project Codes Edit Resource Codes Add Resource Codes Delete Resource Codes Edit Global Portfolios Administer Global External Applications Edit Funding Sources Run Project Architect

Create, edit, and delete funding sources in the Funding Sources Dictionary. Run the Project Architect wizard. The wizard enables Project Management module users to create a new project based on methodologies imported from the Methodology Management module and to add methodologies to an existing project.

View Resource and Role Costs

Administer Job Services

Edit Personal Resource Calendar

View all values for labor and nonlabor resource costs and price/unit values for roles. If this privilege is not granted to a user, all areas in the Project Management module that display monetary values for roles and labor, material, and nonlabor resources display dashes and cannot be edited. For resources, such areas include resource price/time, values in resource profiles in the Activities window and monetary values in Tracking layouts. For roles, the area is the price/unit value in the Roles dialog box. Administer the Job Services; set up the Apply Actuals, Batch Reports, Export, Schedule, and Summarize services to run at specific time intervals. Enables users to edit their own resource calendars if they do not have the Edit Global and Resource Calendars global privilege. This privilege or the Edit Global and Resource Calendars privilege is required for access to the Import Appointments feature of P6 Web Access. Initiate predefined workflow processes for reviewing new project requests or new work requests for existing projects. A separate privilege is required to create the templates that define the available workflow processes. Create, edit, and modify templates that define workflow processes for reviewing new project requests or new work requests for existing projects. Create, edit, assign, view, and delete all global and EPS-level secure activity codes and values, as well as all global secure issue codes and values. Edit, assign, and view global and EPS-level secure activity codes and values, as well as all global secure issue codes and values. Assign and view global and EPS-level secure activity codes and values, as well as all global secure issue codes and values. View global and EPS-level secure activity codes and values, as well as all global secure issue codes and values. Create, edit, and delete user interface views in P6 Web Access. This privilege also grants you the right to assign user interface views to users in both P6 Web Access and the Project Management module. Access the SDK in read only mode, without superuser privileges. Create, edit, and delete global Resource Teams and Role Teams. A Resource/Role Team is a collection of resources/roles. Resource/Role Teams are available in P6 Web Access. Create, edit, and delete resource distribution curves.

Create Project Requests and Processes

Edit Project Request and Process Templates Add and Delete Secure Codes Edit Secure Codes

Assign Secure Codes View Secure Codes

Edit User Interface Views*

View All Global/Project Data via SDK Edit Global Resource and Role Teams Edit Resource Curves

Edit User Defined Fields*

Create, edit, and delete user defined fields. Without this privilege, you can only view user defined fields. In P6 Web Access, enables access to the Project User Defined Fields section on the Administration Home page, where you can create, edit, and delete project user defined fields. Create, edit, and delete global project and WBS layouts. In P6 Web Access, create, edit, and delete portfolio views. This privilege is required to save view changes made to the Portfolio Analysis tab in P6 Web Access. Create, edit, and delete Microsoft Project Templates used to import/export data from/to Microsoft Project. Create, edit, and delete Activity Step Templates used to add a set of common steps to multiple activities. Create new issue codes and issue code values in P6 Web Access. Enables access to the Issues menu in P6 Web Access. Edit issue codes and issue code values in P6 Web Access. Enables access to the Issues menu in P6 Web Access. Delete issue codes and issue code values in P6 Web Access. This privilege automatically enables you to add and edit global issue codes and issue code values as well. It also enables access to the Issues menu in P6 Web Access. Create, edit, and delete financial periods in the Financial Period dictionary. A user must also be assigned the Edit Period Performance project privilege to edit period data. Create, edit, and delete global scenarios in the Portfolio Management module of P6 Web Access. Create, edit, and delete global dashboards in P6 Web Access. Add, edit, and delete projects from scorecards in the Portfolio View portlet and the Portfolio Analysis tab in P6 Web Access. This privilege is required to save data changes made to the Portfolio Analysis tab. To edit project data in a scorecard, a user must also be assigned the 'Edit Project Details Except Financials' project privilege. To edit project cost data in a scorecard, a user must also be assigned the 'Edit Project WBS Financials' project privilege. To add a project from a scorecard, a user must also be assigned the 'Create Project Within EPS' project privilege. To delete a project from a scorecard, a user must also be assigned the 'Delete Project Within EPS' project privilege.

Add/Edit Global Project/WBS Layouts and Portfolio Views* Edit Microsoft Project Templates Edit Activity Step Templates Add Global Issue Codes Edit Global Issue Codes Delete Global Issue Codes

Edit Financial Period Dates

Edit Global Scenarios* Edit Global Dashboards* Edit Projects from Scorecards*

:
The following table groups global privileges by functionality. The privileges are listed in the same order as displayed in the Security Profiles dialog box. To view the privileges in alphabetical order in the Security Profiles dialog box, click the Privileges bar as shown in the previous image.

Privileges that are new or modified in P6 are marked with an asterisk (*).

Defining Project Profiles

A project profile is a role-based profile that limits privileges to specific project data, such as baselines, the WBS, and thresholds. The Project Management module does not require that each user be assigned a project profile; however, users cannot access projects unless they are assigned a project profile or the global profile, Admin Superuser. You can define an unlimited number of project profiles in the Project Management module. In addition, the Project Management module provides a predefined project profile called Project Superuser. The Project Superuser profile allows complete access to elements within a project.
For more information on assigning users to OBS elements, see Assigning OBS Elements and Project Profiles on page 381.

Project profiles are applied to users via OBS assignments. The Project Management module requires that all EPS and WBS elements, and projects, are assigned a responsible OBS. The combination of the project profile/user assignment to an OBS assignment, and the OBS assignment to the EPS/WBS, determines which projects and data the user can access. Create project profiles Choose Admin, Security Profiles. Choose Project Profiles, then click Add. Type the new profiles name. To make the new profile the default project profile, mark the Default checkbox. In the Privilege area, mark the appropriate Has Privilege checkboxes to grant privileges to the profile.

To allow read-write privileges for all aspects of a project, you can assign a user to a projects root OBS element and then apply the Project Superuser profile to the OBS assignment.

The following table defines each project privilege:

The following table groups each privilege by functionality. The privileges are listed in the same order as in the Security Profiles dialog box. To view the privileges in alphabetical order in the Security Profiles dialog box, click the Privileges bar as shown in the previous image. Privileges that are new or modified in P6 are marked with an asterisk (*).

Privilege Name
Create Project within EPS Delete Project within EPS Summarize Project Edit Project Details Except Financials Administer Project External Applications Schedule Project Level Resources Apply Actuals

Privilege Definition
Create, copy, and paste projects within the EPS. Delete, cut, and paste projects within the EPS. Summarize data for all projects in the EPS. Edit fields in General, Dates, Defaults, Resources, and Settings tabs in Project Details. A user must be assigned this privilege to select the project baseline. Administer links to external applications.

Schedule a project. Level resources for a project. Apply actuals to activities in a project.

Store Period Performance

Store actual this period values for actual units and costs in a projects financial periods. A user must be assigned the Add/Edit Project Activities Except Relationships project privilege before you can assign this privilege. Edit period performance values for labor and nonlabor units as well as labor, nonlabor, material, and expense costs. A user must be assigned the View Project Cost/Financials project privilege before you can assign this privilege. Add, save, and delete a projects baselines. A user must be assigned this privilege, and the Edit Project Details Except Financials project privilege, to add a project baseline in the Project Management module. Update a projects baselines with new project data using the Update Baseline utility. Select the project baseline for a project. A user must also be assigned the Edit Project Details Except Financials project privilege to select the project baseline. Create, edit, and delete a project's work products and documents. In P6 Web Access, relate items to documents, change a document's access level, add and delete folders, and start project document reviews. Collaboration functionality is additionally required to change a document's access level, add and delete folders, and start project document reviews. In P6 Web Access, create, edit, delete, check out, and start reviews for project template documents. A user needs to have the privilege to 'Edit Project Work Products and Documents' also. Collaboration functionality is additionally required to check out and start reviews for project template documents. View all monetary values for a project. If a user cannot view project costs, all features that display monetary values are replaced by three dashes (---) in the Project Management module and cannot be edited by the user. The ability to view resource price/time is controlled by the View Resource and Role Costs global privilege. Modify a projects activity codes in both P6 Web Access and the Project Management module. Create a projects activity codes in both P6 Web Access and the Project Management module. Remove a projects activity codes from the project database in both P6 Web Access and the Project Management module. Modify EPS-level activity codes in both P6 Web Access and the Project Management module.

Edit Period Performance

Maintain Project Baselines

Run Baseline Update Assign Project Baseline

Edit Project Work Products and Documents

Add/Edit Project Template Documents

View Project Costs/Financials

Edit Project Activity Codes Add Project Activity Codes Delete Project Activity Codes Edit EPS Activity Codes

Add EPS Activity Codes

Create EPS-level activity codes in both P6 Web Access and the Project Management module. This privilege automatically enables you to edit existing EPS-level activity codes as well. Remove EPS-level activity codes in both P6 Web Access and the Project Management module. This privilege automatically enables you to add and edit existing EPS-level activity codes as well. Run the threshold monitor for a project. Publish a projects Web site. Edit a projects reports and edit a projects report batches. Create, edit, and delete a projects calendars. Run Global Change to update activity detail information. Check projects in and out of the Project Management module. In P6 Web Access, assign issue forms to a project. Run reports against timesheets for all resources in a project from the myReports portlet in P6 Web Access. This privilege does not grant access to the Timesheet Approval application. Import and view data from Contract Manager.

Delete EPS Activity Codes

Monitor Project Thresholds Publish Project Website Edit Project Reports Edit Project Calendars Run Global Change Check In/Check Out Project Assign Issue Forms View Timesheets in Reports*

Import/View Contract Manager Data Edit Project WBS Except Financials

Edit Project WBS Financials Edit EPS Except Financials Edit EPS Financials Project Top-Down Estimation Approve Timesheets as Project Manager Edit Project Expenses Edit Project Thresholds, Issues and Risks Edit Project Activity Relationships

Edit WBS hierarchy (add/remove/move WBS nodes), notebook entries, earned value settings, milestones (steps), work products and documents, and dates. Edit WBS budget logs, funding sources, spending plan, and financial data at the project level. Edit cost data at the activity level. Edit EPS hierarchy (add/remove/move EPS nodes), edit EPS notebook, and edit all EPS-related data except financial information. Edit EPS budget logs, funding sources, and spending plan. Run Top-Down Estimation for a project. Review, approve, or reject timesheets for a project.

Create, edit, and delete a projects expenses. Create, edit, and delete a projects thresholds, issues, and risks. Create, edit, and delete a projects activity relationships.

Add/Edit Project Activities Except Relationships Perform Activity Resource Requests Delete Project Activities Delete Project Data with Timesheet Actuals Create Workgroups Delete Workgroups Modify Project Workspace and Workgroup Preferences Edit Resource Assignments for Resource Planning*

Create and edit a projects activity information, except activity relationships. Assign resource requests to activities in P6 Web Access. Delete a projects activities. Delete a projects activities that have timesheet actuals applied to them. A user needs to have the privilege to Delete Project Activities also. Add a new workgroup in P6 Web Access. Delete a workgroup in P6 Web Access. In P6 Web Access, customize the project workspace and workgroup preferences.

Assign, delete, and modify resource assignments on a project or WBS level in the Web Resource Management module. Users can also define search criteria, and conduct a search for resource assignments. For users that do not have this privilege, the resource assignment information on the Plan Resource page is read-only for that particular project or WBS. Since project-level security privileges go down to the WBS level, it is possible to be able to assign a resource to one WBS in a project and not another. Create, edit, and delete a link to a Primavera Contract Manager project. Edit Activity IDs in the Project Management module and P6 Web Access. Assign, delete, and modify role assignments on a project or WBS level in the Web Resource Management module. Users can also define search criteria for role assignments. For users that do not have this privilege, role assignment information on the Plan Resources page is read-only for that particular project or WBS. Since project-level security privileges go down to the WBS level, it is possible to be able to assign a role to one WBS in a project and not another. Identify committed resource and role assignments on a project or WBS level on the Plan Resources page in the Web Resource Management module. This privilege also requires the Edit Resource Assignments for Resource Planning privilege. Enter or edit future period values in the Planned Units and Remaining (Early) Units fields of the Resource Usage Spreadsheet. To assign this privilege to a user, you must first assign the 'Add/Edit Project Activities Except Relationships' project privilege to the user; otherwise, you cannot select this privilege.

Edit Contract Manager Project Link Edit Activity ID Edit Role Assignments for Resource Planning*

Edit Committed Flag for Resource Planning*

Edit Future Periods*

Add/Edit Project Level Layouts*

Create, edit, and delete project level layouts in Activities, Assignments, or WBS views.

Adding Users in the Project Management Module

Depending on your security profile, the Users dialog box enables you to add and remove users and control user access to Primavera components. You must add a user in the Project Management module for each person who needs access to any Primavera component, except for the Methodology Management module, which uses its own security data.
If your companys OBS is established, and you know which OBS elements to associate with each user, you can make the assignments in the Project Access tab in the Users dialog box. See Assigning OBS Elements and Project Profiles on page 381.

At a minimum, each user requires a login name, global profile, and licensing information (component and access level). You can also provide additional information about the user, such as an e-mail address and office phone number.
If your organization centralizes user information in an LDAP directory, you can add Primavera users by provisioning from the LDAP store. For more information, see Configuring Authentication Modes on page 323. After you provision users, you will need to assign each user a security profile and license. If your company uses P6 Web Access, you might want to create a default prototype user before adding new users. The prototype user enables you to define default dashboards and global preference settings that apply to all users of P6 Web Access. See Adding a prototype user and defining default settings for P6 Web Access on page 379 for more information.

Add new users Choose Admin, Users. Click Add. Click the General tab, type the users login name and personal name, then click Password. Type the users password, then retype the password to verify it. Click OK. If the user will be accessing Timesheets, you can associate the user with a resource in the Project Management module at this time, or you can create the link when you add resources. Click the Contact tab and type the users e-mail address and telephone number.
If the Project Management module is running in LDAP authentication mode, when you click Add, a dialog appears for you to enter a user name and verify it against the LDAP store. When you click Test, if the user exists in the LDAP store, the actual name, e-mail address, and telephone number fields are populatedif you previously mapped those fields through the Authentication Configuration tool. To add the user, click Add. When you click Test, if the user is not found in the LDAP store, a message appears to notify you that the user cannot be added.

Associate resources and users Choose Admin, Users. Click the General tab, then click the Browse button in the ResourceID/Resource Name field to select a resource for the selected user. If the resource is already associated with another user, you are prompted to replace the association. The Project Management module allows a resource to be associated with only one user to maintain a single login name for project resources and users of both the Project Management module and Timesheets. You can also set this association from the Timesheets tab of Resource Details.
For more information, see Defining Global Profiles on page 353.

Assign a global profile A global profile determines a users access to application-wide features, such as resources and roles. The Project Management module requires that each user be assigned a global profile. Choose Admin, Users. Select the user to whom you want to assign a global profile. Click the Global Access tab, then select the users global profile. .
Assign the global profile <No Global Privileges> to users who may only access Timesheets. These users must also be granted access to Timesheets via a Team Member or Timesheets license.

Assign product licensing Each user accessing Primavera must be assigned the appropriate licensing. For each component of Primavera, a user identified as a named user is guaranteed access to the designated product. Choose Admin, Users. Select the user for whom you want to set database access for licensed users of Primavera products. Click the Licensing tab. For each component you want the user to have access to, mark the checkbox in the Named column. Clear the checkbox if a user is not a valid licensed user of the corresponding Primavera component.

The total number of named users must not exceed the maximum number of named users stored in your license file. Primavera Systems provides you with a license file based on the number of named users purchased.

Marking a components checkbox gives the user access to the following:

All licenses except Timesheet and Integration API provide access to the Dashboards Home page in P6 Web Access; however, the portlets and Action Bar items available on the Dashboards Home page are dependent on the license and security privileges.
Project

Management Provides access to the Project Management module and the Projects sections of P6 Web Access. When a user has both a Project Management and myPrimavera Projects license, only the myPrimavera Projects license is used when the user logs into P6 Web Access.
Team

Member Provides access to Primavera Timesheets and to limited functionality in P6 Web Access, including Dashboards and the Projects section (Workspace and Activities tabs). Access to P6 Web Access functionality is additionally determined by a users OBS access and relationship to the project, that is, whether the user is assigned as a resource to activities, designated as an activity owner, or invited to join the project. For users who require access to Timesheets, you must grant them either the Team Member license or the Timesheet license; you can not grant a user both licenses. For more detailed information on the Team Member license, see What does the Team Member license enable a user to access? on page 374.
Timesheets

Provides access to Primavera Timesheets and enables users to log into P6 Web Access to import appointments only (if properly configured). For users who require access to Timesheets, you must grant them either the Team Member license or the Timesheet license; you can not grant a user both licenses.
myPrimavera

Portfolios Provides access to the following functionality in P6 Web Access: the Portfolios section, Project Performance portlets, the Portfolio View portlet in the Dashboards section, and collaboration functionality (if installed).
myPrimavera

Projects Provides access to the following functionality in P6 Web Access: the Projects section, Project Performance portlets in the Dashboards section, and collaboration functionality (if installed). When a user has both a Project Management and myPrimavera Projects license, only the myPrimavera Projects license is used when the user logs into P6 Web Access.
myPrimavera

Resources Provides access to the following functionality in P6 Web Access: the Resources section, Resources portlets in the Dashboards section, and collaboration functionality (if installed).
Integration

API Provides access to the API only.

All licenses, except Timesheets and Integration API, provide access to Primavera ProjectLink. Access to project data in Primavera ProjectLink is dependent on security privilege settings and OBS access to projects, regardless of license. Some Primavera products, such as the SDK and the Job Service, do not require a license. Users can view project data in P6 Web Access without a Team Member license as long as they have a myPrimavera Portfolios, myPrimavera Projects, or myPrimavera Resources license. When this is the case, users can view data for a project when they have OBS access to the project, they are assigned as a resource to an activity in the project, they are an invited user to the project, or they are the project owner.

What does the Team Member license enable a user to access?

The Team Member license provides access to Timesheets and to some P6 Web Access functionality. The following sections describe the P6 Web Access functionality a Team Member-licensed user can access. In general, all Team Member-licensed users can: create private and multi-user dashboards create private and multi-user portfolios (from Dashboards only) import appointments create private and multi-user activity views set global and project preferences Depending on OBS access to projects (as described in the following sections), Team Member-licensed users can also: add/edit project issues add/edit resource assignments add activity steps edit activity dates edit activity status add/edit/delete activity relationships add/edit activity expenses add/edit activity notebook topics add/edit user-defined fields add private documents
Invited users to projects can access the same project data as a Team Member-licensed user without OBS access to the project, as described in this section. In P6 Web Access, users with the required license and privilege can invite users to a project on the Invited Users tab in the Projects section or on the Manage Invited Users page of a workgroup. If you assign a user interface view to a user who has only a Team Member license, view settings are ignored; the functionality available to Team Member-licensed users is always controlled by the license. For more information on assigning user interface views, refer to Defining User Access to P6 Web Access Functionality on page 391.

Dashboards In the Dashboards section of P6 Web Access, Team Member-licensed users can create private and multi-user dashboards, create private and multi-user portfolios, import appointments, and approve timesheets (with the required security privilege). Dashboard portlets display data for projects the user is associated with that meet the criteria of the specified Dashboard Filter. Together, a users association with a project, OBS access, and security privileges, determine the level of view and edit access that is granted to project data. A licensed Team Member can be associated with a project via OBS access, by assignment as an activity resource, through invitation to join a project, and by assignment as activity owner in a Reflection project.
The Reflection project and Activity Owner features can be used together to collect and review activity progress information from licensed Team Members who are not assigned as activity resources and who do not use the Timesheets application for status reporting. For more details, refer to Using Reflection projects and Activity Owner features to collect and review activity status in the Project Management Help.

Team Member-licensed users can access the following Dashboards portlets (full functionality is available except where noted): My Projects My Workgroups My Activities My Risks Users can view, but not add, risks. My Issues Users without OBS access to a project can view, but not add, issues. Users with OBS access to a project can add issues with the required security privilege. Communication Center My Documents Users can add private documents only. My Events My Calendar My Reports Action Required Project and Document Workflows Cost Worksheet Custom Portlet All other portlets are not available to Team Member-licensed users.
The Action Required, Communication Center, My Documents, My Workgroups, and Project and Document Workflows portlets are only available if P6 Web Access is installed with collaboration functionality. Additionally, some functionality within available portlets requires collaboration functionality to be installed.

Projects In the Projects section of P6 Web Access, Team Member-licensed users can access the Projects Home page, the Project Workspace, and the Activities tab. The Projects Home page displays all projects to which the user has OBS access, all projects in which the user is assigned as an activity resource, all Reflection projects in which the user is designated as an activity owner, and all projects the user is invited to. From the Projects Home page, a Team Member-licensed user can create and edit private and multi-user activity views. The Activities tab in the Projects section displays all activities the user is associated with either as an assigned resource or as an activity owner. Users who are associated with activities, but who do not have OBS access rights, can view, print, and export data but can not access features and functions that change project data. For example, they can not edit activity data in the table, modify the Gantt chart, or modify activity details. Users associated with activities who have OBS access to the project and the required security privileges can access, add, and edit activities, edit fields in the activity table, modify Gantt Chart bars, establish relationships, print, export, and import information.
Team Member-licensed users cannot delete activities or add/edit WBS elements.

In the Project Workspace, Team Member-licensed users can access the following portlets (full functionality is available except where noted): Project Documents Users can view, download, and check out, but not add, project documents. Project Risks Users can view, but not add or edit, project risks.

Project Issues Users without OBS access to the project can view, but not add or edit, project issues. Users with OBS access to the project can add and edit issues if they are assigned the required project privilege. Project Notebooks Users can view, but not add or edit, project notebooks. Overallocated Resources Critical activities behind schedule Users can view all activities behind schedule for the project. For users without OBS access to the project, all activity details accessed from this portlet are read-only. For users with OBS access to the project, users can edit activity details accessed from this portlet if they have the appropriate security privileges and are a resource on the activity or are the activity owner. Milestone status Users can view all milestone activities for the project. For users without OBS access to the project, all activity details accessed from this portlet are read-only. For users with OBS access to the project, users can edit activity details accessed from this portlet if they have the appropriate security privileges and are a resource on the activity or are the activity owner. Project Reports Project Discussions Project Events News Communication Center Project Calendar Users can view all activities for the project scheduled for the selected week. For users without OBS access to the project, all activity details accessed from this portlet are read-only. For users with OBS access to the project, users can edit activity details accessed from this portlet if they have the appropriate security privileges and are a resource on the activity or are the activity owner. Workgroups Custom Portlet Contract Manager portlets Users can view all Contract Manager portlets if P6 Web Access is configured to access Contract Manager and the P6 Web Access project is linked to a Contract Manager project. All other Project Workspace portlets are not available to Team Member-licensed users.
The Communication Center, News, Project Discussions, Project Documents, and Workgroups portlets are only available if P6 Web Access is installed with collaboration functionality. Additionally, some functionality within available portlets requires collaboration functionality to be installed.

Adding a prototype user and defining default settings for P6 Web Access
For information on creating a default user interface view for new users, refer to Defining User Access to P6 Web Access Functionality on page 391.

As an administrator, you can create a prototype user that enables you to create default global Dashboards and select Global Preferences that apply to all new P6 Web Access users. Defining a prototype user configuration, in combination with defining user interface views, ensures that new users of P6 Web Access will have a consistent interface customized for the business needs of the enterprise. After you complete the steps below, the prototype user configuration you create is automatically copied to each new P6 Web Access user you add.
If you do not create a prototype user configuration, Primavera automatically creates a default Personal Workspace dashboard for each new user based on the users role.

To create a prototype user configuration, do the following: 1In the Project Management module, choose Admin, Users. 2Click Add. A (New User) row is added to the Users table.

3In the Login Name column, or in the Login Name field on the General tab, type a login name for the prototype user (for example, prototype_user). 4In the Global Profile column, select a Global Profile (Admin Superuser, for example) that will enable the prototype user to appropriately configure default Dashboards and Global Preferences for all new users. For more information about assigning a Global Profile, see Assign a global profile on page 370 5Log into P6 Web Access as the new prototype user, using the login name you set for the prototype user.
Click Help on the Manage Dashboards or Dashboard Preferences pages for details on creating a dashboard, choosing the portlets to display in a dashboard, and specifying user access.

6On the Dashboards Home page, click Manage Dashboards to create default global dashboards that will be displayed for each new P6 Web Access user. Be sure to select All Users as the access type on the Access tab of Dashboard Preferences to ensure that each dashboard you create is a global dashboard.
If upgrading from myPrimavera 5.0 to P6 Web Access: After the upgrade and before adding new users, log into P6 Web Access as the prototype user and make sure that all selected dashboards for the prototype user are global. Otherwise, users dependent on the prototype may not have a dashboard displayed after the upgrade. By default, the maximum number of portlets you can display in a dashboard is twelve. You can change this setting in the Primavera Administration Application. For the Primavera Configuration you want to modify, the Maximum Portlets per Dashboard setting is located in the Application folder. Refer to Configuration Settings for P6 Web Access on page 163 for more information. If upgrading from myPrimavera 5.0 to P6 Web Access: After upgrading, only twelve portlets will be selected. The program will automatically select the portlets in this order: wide, narrow, custom.

7At the top right of P6 Web Access, click Preferences. On the Global tab, set the Global Preferences you want to apply to new users. When finished, click Save and Close. 8Log out of P6 Web Access. 9Log into the Primavera Administration Application. 10Expand the configuration for which you want to add the prototype user (for example, Primavera Configuration), then expand the Application folder. For information on changing configuration settings, refer to Reviewing and Modifying Configurations for P6 Web Access on page 155. 11Select the PrototypeUser setting, then press F2 to edit the field. 12Type the prototype user login name you created, click Save Changes, and exit the Administration Application. 13In the Project Management module, choose Admin, Users, then select the Login Name of the prototype user you created. On the Licensing tab, clear all boxes under Named User and Concurrent User to ensure against unauthorized login.

Assigning OBS Elements and Project Profiles

To restrict or grant access to projects and their data, you must assign project profiles to users. A project profile is a rolebased profile that limits privileges to specific project data, such as baselines, the WBS, and thresholds. Project profiles are linked to users through one or more OBS assignments. You assign responsibilities to specific projects and work within projects by assigning OBS elements to various levels of the EPS and each projects WBS. The combination of the project profile/user assignment to an OBS assignment, and the OBS assignment to the EPS/WBS, determines which projects and data the user can access.

For more information on project profiles, see Defining Project Profiles on page 361.

You can assign a user an OBS element and a corresponding project profile in the Users dialog box when you are adding users, or you can make the assignment in the OBS dialog box during or after creating the OBS.
The Project Management module does not require that each user have a project profile; however, a user cannot access a project without a project profile or the global profile, Admin Superuser.

Assign users and project profiles to OBS elements Choose Enterprise, OBS. Click the Users tab. Select the OBS element whose user and project profile you want to specify, then click Assign. Select the user to associate with the specified OBS element, then click the Select button. A default project profile is associated with the user. Double-click the project profile to choose another project profile from the predefined list.

Assign OBS elements and project profiles to users You can also assign OBS elements and project profiles to a user when you first add the user. Choose Admin, Users. Click the Project Access tab. Select the user to whom you want to assign an OBS element and project profile, then click Assign. Select the OBS element associated with the user, then click the Select button. A default project profile is associated with the user. Double-click the project profile to choose another profile from the predefined list.
If an OBS element is the Responsible Manager for several projects in the EPS, any user you associate with that OBS element will have access to all the corresponding projects.

To deny the user access to an OBS elements project information, select the Responsible Managers name, then click Remove.

Assigning OBS Elements to the EPS

For more information on the EPS, see Setting Up the Enterprise Project Structure in the Project Management Reference Manual.

In the Project Management module, your database of projects is arranged in a hierarchy called the enterprise project structure (EPS). The EPS can be subdivided into as many levels or nodes as needed to parallel work in the enterprise. Nodes at the highest, or root, level might represent divisions within your company, project phases, site locations, or other major groupings that meet the needs of your organization, while projects always represent the lowest level of the hierarchy. Every project in the enterprise must be included in an EPS node. User access and privileges to nodes within the EPS hierarchy are implemented through a global OBS that represents the management responsible for the projects in the EPS. Each manager in the OBS is associated with an area of the EPS, either by node or by project, and the WBS of the particular level of the hierarchy. Once you have added users and associated them with OBS elements and project profiles, you can define the EPS and assign a responsible manager (OBS element) to each level. You must specify a responsible manager for each node of the EPS. Assign OBS elements to the EPS You can assign the responsible manager (OBS element) to each level of the EPS when you create the project structure. Choose Enterprise, Enterprise Project Structure. Select the EPS node, then click the Browse button in the Responsible Manager field to select the appropriate OBS element. The users associated with the responsible manager will have access rights to the selected node and all nodes/projects within that branch. The specific data that can be accessed within the projects depend on the project profile that corresponds to the OBS element.
If more than one user is responsible for the same node of the EPS, you must assign each of those users to the corresponding OBS element.

You can also assign/review the responsible manager in the Projects window. Choose Enterprise, Projects, then click the General tab.

Once the EPS and OBS structures are defined and security is implemented at the EPS level, project managers can begin to add their own projects to the hierarchy. To further control security within projects, project managers can assign specific OBS elements to WBS levels. See Setting Up the Enterprise Project Structure and Reviewing Work Breakdown Structures in the Project Management Reference Manual for more information.

Defining User Access to Resources

Resource security enables you to restrict a users access to resources. Each user can have access to all resources, no resources, or a limited number of resources in the resource hierarchy. To restrict access to a limited number of resources, you can designate each users root resource by assigning each user to a resource in the resource hierarchy. The position of the assigned resource in the hierarchy determines the users resource access. When the user logs in, the resource hierarchy displays only the assigned resource node and its children. Resources outside the users root resource are not displayed.
Users with restricted resource access can still view and edit all current project resource assignments if they have the proper project privileges.

You can grant one of the following three types of resource access to each user:
All

Resource Access disables resource security and provides access to all resources. This is the default option for upgrading users. Admin Superusers always have all resource access, no matter what option is selected.
No

Resource Access does not provide access to any resources. This is the default option for new users. With no resource access, the user cannot view any global resource data in the resource dictionary.
Resource

Node provides access to one selected resource (root resource node) and all its children in the resource hierarchy. Users with this restricted access can view global resource data for resources they have access to.
You can assign only one resource node to each user. Multiple resource nodes are not supported.

The following example shows how resource access is determined by the root resource assigned to different users.

Refer to the Defining Resources and Roles chapter in the Project Management Reference Manual for more information on setting up the resource hierarchy.

Implementing resource security Before you implement resource security, you must first set up your resource hierarchy in a manner that enables you to assign users to single resource nodes. For example, you can use resource security to restrict users access to resources who are not in the same department or geographic location. In this case, you would create a resource hierarchy containing separate branches for each department or geographic location. Once the resource hierarchy is in place, you can implement resource security by completing the following steps: 1In the Project Management module, choose Admin, Users. The Users dialog displays a filtered users list based on your resource access.

2Select the Global Access tab.

3Select the user that you want to set resource security for. You can select only one user at a time.
Resource access settings are ignored for Admin Superusers. Admin Superusers always have all resource access.

4Set resource access for the selected user as follows: To provide all resource access to the selected user, mark the All Resource Access checkbox. To restrict resource access to a single resource node for the selected user, unmark the All Resource Access checkbox. Then, click the browse button in the Resource Access field and select a resource. If you do not want the selected user to have any resource access, unmark the All Resource Access checkbox and be sure there is no resource selected in the Resource Access field.

Defining User Access to P6 Web Access Functionality

For more information on user interface views, and for detailed instructions on creating and assigning user interface views in P6 Web Access, refer to the P6 Web Access Help.

In addition to licensing and security privileges, you can further control access to P6 Web Access functionality using user interface views. A user interface view is a defined set of tabs and Action Bar items that a user assigned to that view can access in each section of P6 Web Access (Dashboards, Portfolios, Projects, and Resources). You can create multiple user interface views that correspond to the job functions performed by each role in your organization, or you can create user interface views to meet each individual user's needs. User interface views can only be defined in P6 Web Access and can be assigned to users in both P6 Web Access and the Project Management module.
You must designate one user interface view as the default view for new P6 Web Access users. The default view controls user access to functionality only for new users who are not assigned to a user interface view. Existing P6 Web Access users who do not have an assigned user interface view can continue to access all functionality. When creating user interface views in P6 Web Access, provide a name for each user interface view that enables you to easily identify the user interface views associated functionality.

Creating user interface views is a useful way to enhance security and enable users to more easily access the functionality they use when performing project work and managing projects. For example, executives may require access to some, but not all, project information. In this case, you can create a user interface view named 'Executive' that provides access to some or all Portfolios functionality, along with access to the Projects data executives require.
A users associated license and security privilege settings always override the settings defined in the users assigned user interface view. For example, if a user has a Primavera Web Resources license but not a Primavera Web Portfolios license, the user cannot access any functionality in the Portfolios section of P6 Web Access, even if Portfolios functionality is enabled in the users assigned user interface view. Additionally, if you assign a user interface view to a user who has only a Team Member license, view settings are ignored; the functionality available to Team Memberlicensed users is always controlled by the license. For more information on functionality available to Team Memberlicensed users, refer to What does the Team Member license enable a user to access? on page 374

You can also use user interface views to hide P6 Web Access functionality your organization does not use. For example, if your organization does not use Primavera Timesheets for time reporting, you can hide the Approve Timesheets Action Bar item in the Dashboards section. Assign a user interface view to a user in the Project Management module Choose Admin, Users. Select the user to whom you want to assign a user interface view, then click the Global Access tab. In the User Interface Views section, click the Browse button to select a user interface view. Mark the Enable user to modify view settings checkbox if you want to enable the user to change personal user interface view settings in View Preferences in P6 Web Access.

Setting Security in the Methodology Management Module

The Methodology Management module uses its own set of users, global profiles, and methodology profiles to control access to Methodology Management data. These security data are stored in the methodology management database. No security data are shared between the Project Management and Methodology Management modules. Methodology Management uses its own OBS, users, global and methodology profiles, and license. The security model for Methodology Management differs from the Project Management module. Only one methodology can be open at a time, and there is no EPS. Users and methodology profiles cannot be assigned to OBS elements; methodology profiles must be assigned directly to users to allow the user access to a methodology. This section discusses the process of creating security profiles and users in the Methodology Management module. Create global profiles In the Methodology Management module, choose Admin, Security Profiles. Choose Global Profiles, then click Add. Type the new profiles name. To make the new profile the default global profile, mark the Default checkbox. In the Privilege area, mark the appropriate Has Privilege checkboxes to grant privileges to the profile.

The following table defines each global privilege:

The following table groups each privilege by functionality. The privileges are listed in the same order as in the Security Profiles dialog box. To view the privileges in alphabetical order in the Security Profiles dialog box, click the Privileges bar as shown in the previous image. Privileges that are new or modified in P6 are marked with an asterisk (*).

Privilege Name
Edit Security Profiles Edit Users Edit Admin Preferences and Categories

Privilege Definition
Change security profile information. Create and delete Methodology Management module users, and change user access permissions. Change administrative preferences as defined in the Admin Preferences dialog box. Create, change, and delete administrative categories as defined in the Admin Categories dialog box. Edit currency data in the Currencies dialog box. Create, import, or copy a methodology. Create, delete, and change elements of the resource hierarchy. Create, delete, and change role information. Create, delete, and change work product and document records. Import global and methodology information.

Create New / Copy Methodology Edit Resources Edit Roles Edit Work Products and Documents Import Global / Methodology Information Edit Reports

Create, edit, and delete reports; save reports in the Report Wizard.

Edit Activity Attributes Edit Activity Codes Edit Estimation Factors View Resource Prices Edit Global Activity Layouts and Filters Edit OBS Edit Methodology Codes and Resource Codes Edit User Defined Fields Edit Microsoft Project Templates Edit Activity Step Templates

Create, change, and delete activity attributes. Create, change, and delete global activity codes and values. Create, change, and delete estimation factors. View resource prices. Create, delete, and change global activity layouts and filters. Create, delete, and change organizational breakdown structure information. Create, delete, and change methodology and resource codes. Create, edit, and delete user-defined fields. Users that do not have this privilege can view userdefined fields. Create, edit, and delete Microsoft Project Templates used to import/export data from/to Microsoft Project. Create, edit, and delete Activity Step Templates used to add a set of common steps to multiple activities.

Create methodology profiles Choose Admin, Security Profiles. Choose Methodology Profiles, then click Add. Type the new profiles name. To make the new profile the default methodology profile, mark the Default checkbox. In the Privilege area, mark the appropriate Has Privilege checkboxes to grant privileges to the profile.

The following table defines each methodology privilege:

Privileges that are new or modified in P6 are marked with an asterisk (*).

Privilege Name
Edit Methodology Properties Edit Methodology WBS Edit Methodology Links Edit Methodology Activities Edit Methodology Expenses View Methodology Costs

Privilege Definition
Create, delete, and change a methodologys properties, as defined in the Methodology Properties dialog box. Create, delete, and change a methodologys work breakdown structure (WBS) elements and versions. Create, delete, and change a methodologys links, if the user has this privilege for both linked methodologies. Add, change, and delete activities and activity information. Add, change, and delete expenses. View methodology cost information.

Check In/Check Out Methodology Edit Methodology Risks Edit Activity ID

Check methodologies in and out of the Methodology Management module. Create, delete, and change a methodologys risks. Edit methodology activity IDs.

Add new users Choose Admin, Users. Click Add. Click the General tab, type the users login name and personal name, then click Password. Type the users password, then retype the password to verify it. Click OK.
If the Methodology Management module is running in LDAP authentication mode, when you click Add, a dialog appears for you to enter a user name and verify it against the LDAP store. When you click Test, if the user exists in the LDAP store, the actual name, e-mail address, and telephone number fields are populatedif you previously mapped those fields through the Authentication Configuration tool. To add the user, click Add. When you click Test, if the user is not found in the LDAP store, a message appears to notify you that the user cannot be added. If your organization centralizes user information in an LDAP directory, you can add Primavera users by provisioning from the LDAP store. For more information, see Configuring Authentication Modes on page 323. After you provision users, you will need to assign each user a security profile.

Product licensing You do not need to assign product licensing for the Methodology Management module. For each license of the Project Management module that you have purchased, you automatically are granted one license of the Methodology Management module. Assign a global profile and methodology profiles A global profile determines a users access to global data, such as resources and roles; methodology profiles restrict the users access to methodology data. The Methodology Management module requires that each user be assigned a global profile. To open a methodology, the user must be assigned a methodology profile for that methodology. Choose Admin, Users. Select the user to whom you want to assign a global profile and methodology profiles. Click the Methodology Profiles tab.

.The Methodology Management module includes an Admin Superuser global profile that allows complete access to all global information and methodologies. The Methodology Superuser profile grants read-write privileges to all aspects of a methodology. A user with Admin Superuser global privileges automatically has Methodology Superuser access to all methodologies. If a user creates a new methodology, that user is automatically granted the Methodology Superuser profile for that methodology.

The Project Management module enables your organization to define a series of module-wide parameters and values that apply to all projects in an enterprise project structure (EPS). Use these settings to customize the module to meet specific project management requirements and standards. While all users can view these settings, a user must have special security privileges to edit them. This chapter discusses the types of settings you can specify: Administrative Preferences, which are default settings; Administrative Categories, which are standard values that apply to all projects; and Currencies, which consist of a base currency used to store costs in the database and a view currency

used to display cost data in windows and dialog boxes. In this chapter:
Defining Default Settings Defining Standard Categories and Values Defining Currencies

Defining Administrative Preferences and Categories in Project Management

Defining Default Settings
For detailed information on each field in Admin Preferences, click Help in the Admin Preferences dialog box.

Use the Admin Preferences dialog box to specify default settings established by the project controls coordinator. Choose Admin, Admin Preferences. General information Use the General tab to specify general default options, such as the weekday on which the calendar week begins. You can also change the character used to separate hierarchy levels in resource, project, and activity codes; roles; cost accounts; and WBS elements.

The start day of the week affects how all days in a week are displayed in profiles, spreadsheets, and other layouts in which a weekly timescale can be displayed. For example, if Wednesday is selected as the starting day of the week, the week is displayed as WTFSSMT in an Activity Usage Profile.

Timesheets Use the Timesheets tab to specify default setup options when using the Timesheets module.

If there is a discrepancy between the number of decimal places you enter in the Maximum hours a resource can enter per day and Maximum number of decimal digits for recording hours in timesheets fields, values a user enters in a timesheet field may round up or down. The rounding of values is for display purposes only; the originally entered value is stored in the database. For example, if you specify 10.5 as the maximum hours per day but specify 0 (zero) as the maximum number of decimal places for recording hours in timesheets, if a user enters 10.5 in a timesheet field, the value will round up to 11 in the timesheet. Since the value 10.5 is stored in the database, the resource does not exceed the maximum hours per day setting in this case.

The Timesheet Approval Level section contains the following options:

Auto

Submission Choose to indicate that resource timesheets do not need to be submitted or approved. Timesheet data are automatically updated in the database when you apply actuals.
Auto

Approval Choose to indicate that resource timesheets do not require management approval. Timesheets are approved automatically when they are submitted.
For more information on implementing the Timesheets module, see Configuring the Group Server for Timesheets on page 91 and Implementing Timesheets on page 439. 1

Approval Level Choose to indicate that resource timesheets require approval by the resource/cost manager only. If you select this option, the status of all submitted timesheets remains Submitted until the approving manager changes the timesheets status. If you previously required both project manager and resource/cost manager approval, and you select this option, the status of all current timesheets that have received one level of approval changes to Approved.

Approval Levels Choose to indicate that resource timesheets require approval by project and resource/cost managers. If you select this option, the status of all submitted timesheets remains Submitted until both managers approve the timesheet.
Project

Manager Must Approve Before Resource Manager If you choose 2 Approval Levels, mark to indicate that project managers must approve timesheets before resource/cost managers.
Default

Resource Manager Approving Timesheets The name of the manager who approves resource timesheets, unless you specify otherwise. Click the Browse button to select a new manager. Timesheet Privileges Use the Timesheet Privileges tab to define privileges for reporting hours.

Data limits Use the Data Limits tab to specify the maximum number of levels for hierarchical structures. You can also specify the maximum number of baselines and activity codes that can be included in a project.

If you change maximum hierarchy level settings, the new settings apply only when you add new elements or edit existing elements.

ID lengths Use the ID Lengths tab to specify the maximum number of characters for IDs and codes.

If you change the maximum number of characters in an ID or code, the new number applies only when you add new IDs/codes or edit existing IDs/codes.

Time Periods Use the Time Periods tab to define the default number of hours in a workday, workweek, workmonth, and workyear. These values are used as conversion factors when displaying the time units and duration display formats you select. You can also specify abbreviations for displaying minutes, hours, days, weeks, months, and years.

Allowing Users to Define the Default Hours per Time Period

Primavera calculates and stores time unit values in hourly increments. However, through User Preferences, each user can choose to display time unit values as hours, days, weeks, months, or years. When a user displays data in time unit fields in increments other than hours, the Project Management module converts the data based on the Admin Preference Hours per Time Period settings. Conversely, if a user enters time units in increments other than hours, the Admin Preference Hours per Time Period settings are used to convert these input values to hours for database calculation and storage. As an administrator, you can specify the conversion factors or you can allow users to specify the conversion factors. If you want to specify the conversion factors, enter the number of hours to use as a conversion factor in each Hours per Time Period field. If you want users to specify the conversion factors, mark the 'Allow users to specify the number of work hours for each time period' checkbox. Enabling users to enter their own Hours per Time Period settings in User Preferences prevents time unit data from being displayed incorrectly when they view summary or detailed schedule data for their activities in spreadsheets, reports, etc. (which can occur when the Admin time period settings and the activity calendar time period settings do not match). If you do not allow users to specify the User Preference Hours per Time Period and the user preference for display is set to an increment other than hours, when a user enters hours for an activity that uses different hours/time period calendar values

than the Admin Preference Hours per Time Period settings, the display output may not be as expected. This occurs because the display reflects the conversion factor of the Admin Preference Hours per Time Period settings, not the hours/time period defined by the activitys calendar. For example, User Preferences, Time Units = day Admin Preferences, Hours per Time Period = 8h/d Activity calendar = 10h/d User-entered activity duration = 30h Duration display = 3d6h (30h duration/8h per day, based on the conversion factor) To avoid an unexpected display result, mark the 'Allow users to specify the number of work hours for each time period' checkbox. Then, advise users to set the Hours per Time Period values in User Preferences according to the activity calendar used by their role in the organization. For example, if engineers use an 8-hour activity calendar, engineers should enter 8 for the Hours/Day user preference. Likewise, if construction workers use a 10-hour activity calendar, construction workers should enter 10 as the Hours/Day user preference. Advising users to set the user preference according to their role will provide users with an accurate representation of their activity durations. Earned value Use the Earned Value tab to specify default settings for calculating earned value. You can change the settings for specific WBS elements in the Earned Value tab in Work Breakdown Structure Details.

Reports Use the Reports tab to define up to three sets of headers, footers, and custom labels for reports.

Options Use the Options tab to specify the time intervals in which cost and quantity summaries should be calculated for activities and resources/roles: by calendar intervals, by financial period intervals, or both. Your choices determine the data available for display in charts and spreadsheets that display summarized activity and assignment data in P6 Web Access and the Project Management module. The By calendar option is selected by default. You can choose to not summarize by calendar intervals, however this is not recommended for most companies. To ensure that P6 Web Access users can view activity and assignment data (both actual to date and past period actual) in Financial Period timescale intervals in charts and spreadsheets, choose to summarize by financial period; choosing this option additionally ensures that Financial Period timescale intervals in the Project Management module accurately display summarized actual to date values for closed projects.
If you modify summarization settings after upgrading to P6.1 (for example, you select the By financial period option), some projects are ignored when you summarize all projects. Specifically, projects that were summarized prior to upgrading, and have not been modified since, WILL NOT BE SUMMARIZED when you choose to summarize all projects.

To include summary financial period data for these projects, after upgrading you must delete the existing summary data for these projects, then summarize each project (either individually or through the job service). To delete summary data for a project, in the Projects window in the Project Management module, right-click on the project name and choose Delete Project Summaries. Summarizing by both calendar and financial period intervals will increase the runtime of summarizer jobs. If you experience performance issues, refer to Job Service Registry Settings on page 270 for information on how to improve summarizer performance. Financial periods must be properly defined for P6 Web Access users to display a Financial Period timescale, even if data

is summarized by financial period. See Defining Financial Periods on page 461 for more information on properly configuring financial periods. If you choose to summarize by financial period intervals and you want data for closed projects to be included when users display a Financial Period timescale, you must summarize each closed project once. For more information on summarizing projects, refer to the Project Management Reference Manual.

You can select whether users can access methodologies to add activities or create new projects using Project Architect. To enable users to launch collaboration documents and the Timesheet Approval application from the Project Management module, type the URL to the P6 Web Access server. The Workflow Administrator is the web user responsible for administrative tasks related to P6 Web Access workflow templates, which are used for project and process requests. Click the browse button to select. You can additionally use this tab to set up a link to the Contract Manager module (formerly known as Expedition) and choose the Contract Manager product version you want to connect to.

Once a link to the Contract Manager module is set up, users can create a link to a Contract Manager project to import and view project-level data. Refer to the Project Management Reference Manual for more information.

Rate Types Use the Rate Types tab to provide a title for each of the five available Price/Unit fields. The title should describe what the rate type represents. The rate type titles you define appear wherever the rate types are displayed in a list or column.

Defining Standard Categories and Values

Use the Admin Categories dialog box to define standard categories and values that you can apply to all projects. Choose Admin, Admin Categories.
For more information about baselines, see the Project Management Reference Manual.

Baseline types Use the Baseline Types tab to create, edit, and delete baseline types. Baseline types enable you to categorize and standardize baselines across projects. To change the name of a baseline type, double-click it, then type a new name. The change applies to all projects to which the baseline is assigned.

Click the Shift Up/Shift Down buttons to move the selected category/type to a higher/lower position in the display. This changes the order in which the categories/types are listed when you assign them. These buttons are available only when the list is not sorted alphabetically.
For more information about expenses, see the Project Management Reference Manual.

Expense categories Use the Expense Categories tab to create, edit, and delete expense categories. Expense categories can be used to categorize and standardize project expenses, and to organize and maintain your expense information. To change an expense category, double-click it, then type a new name. The change applies to all projects to which the expense item is assigned.

For more information about the WBS, see the Project Management Reference Manual.

WBS custom category Use the third tab on the Admin Categories dialog box to define a custom WBS category and category values. The tab displays the name you define. To change the category name, click in the field in the top right, then type a new name. Use this category to organize, filter, and report WBS information in all projects. To change a category value, double-click it, then type a new name. The change applies to all projects to which the WBS item is assigned.

If you change the WBS category, the categorys values or value assignments do not change.

Document categories Use the Document Categories tab to set up categories for work products and documents, then assign these categories to documents in the Work Products and Documents window and activities in the WPs & Docs tab of Activities Details. To change a document category, double-click it, then type a new name. The change applies to all projects to which the document is assigned.

For more information about work products and documents, see the Project Management Reference Manual.

Document status Use the Document Status tab to create, edit, and delete document status types. Status types identify the current status of work products and documents within a project. Use them to determine which documents can be assigned to activities or WBS elements. To change a status type, double-click it, then type a new name. The change applies to all projects to which the document is assigned.

For more information about the Timesheets module, see the Project Management Reference Manual.

Overhead codes Use the Overhead Codes tab to create, edit, and delete overhead activity codes for Timesheets module users. Timesheets module users add overhead activities to their timesheets to log timesheet hours that are not associated with project activities. To change a code, double-click it, then type a new name. The change applies to all projects in which the code is assigned.

For more information about risks, see the Project Management Reference Manual.

Risk types Use the Risk Types tab to create, edit, and delete risk types, or categories of possible risks. Risk types allow you to classify and standardize risks across projects. To change a risk type, double-click it, then type a new name. The change applies to all projects in which the risk is assigned.

For more information about activity notes, see the Project Management Reference Manual.

Notebook topics Use the Notebook Topics tab to create, edit, and delete notebook topics. Notebook topics typically consist of instructions or descriptions for performing an activity. However, notebook topics can also be assigned at the EPS, project, and WBS levels. Examples include Purpose, Entry Criteria, Tools and Techniques, and Exit Criteria. To change a notebook topic, doubleclick it, then type a new name. The change applies to all notebook assignments.

Units of Measure Use the Units of Measure tab to set up units of measure labels that you can assign to material resources. To change a unit of measure label, double-click it, then type a new name. The change applies to all unit of measure assignments.

Defining Currencies
You can specify the monetary unit or base currency used to store cost data for all projects in the database, as well as the

monetary unit or view currency used to display cost data in windows and dialog boxes.
Only a user with Admin Superuser privileges can change the base currency and define additional view currency types.

The exchange rate for the base currency is always 1.0. If you select a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields. For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields in windows and dialog boxes. Similarly, if you enter 10 Euros in a cost or price field, it is stored in the database as $13.30.
When you enter values in cost and price fields, they are always displayed in the view currency.

Use the Currencies dialog box to set up the base and view currencies.
If you are upgrading from a previous version of the Project Management module, you should set up the base currency in the new version before you start adding and changing projects.

Define a base currency The base currency, by default, is U.S. dollars. To define a different currency as the base, choose Admin, Currencies. Select the base currency, then, in the General tab, type the currencys ID, name, and symbol. The exchange rate for the base currency is always one. Click the Appearance tab to further define how the currency is displayed.

If you want to view costs in the old base currency, you will need to add it to the list of available currencies.

Add a view currency Choose Admin, Currencies. Click Add. Specify the currencys ID, name, symbol, and exchange rate, and indicate how the currency should be displayed.

The Methodology Management module enables your organization to define a series of module-wide parameters and values that apply to all methodologies. Use these settings to customize the module to meet specific project management requirements and standards. While all users can view these settings, a user must have special security privileges to edit them. This chapter discusses the types of settings you can specify: Administrative Preferences, which are default settings used in the module; Administrative Categories, which are standard values that apply to all methodologies in the module; and Currencies, which consist of a base currency used to store cost data in the database and a view currency used to display cost data in windows and dialog boxes. In this chapter:
Defining Default Settings Defining Standard Categories and Values Defining Currencies

Defining Administrative Preferences and Categories in Methodology Management

Defining Default Settings
Use the Admin Preferences dialog box to specify default settings established by the project controls coordinator. Choose Admin, Admin Preferences. General information Use the General tab to specify general default options for new activities, such as the duration type, percent complete type, and activity type. You can also change the character used to separate hierarchy levels in resource, methodology, and activity codes; roles; and work breakdown structure (WBS) elements.

ID lengths Use the ID Lengths tab to specify the maximum number of characters for IDs and codes.

If you change the maximum number of characters in an ID or code, the new number applies only when you add new IDs/codes or edit existing IDs/codes.

Data limits Use the Data Limits tab to specify the maximum number of levels for hierarchical structures.

If you change maximum hierarchy level settings, the new settings apply only when you add new elements or edit existing elements.

Timeperiods Use the Time Periods tab to define the default number of hours in a workday, workweek, workmonth, and workyear. The module uses these values as conversion factors when displaying the time units and duration display formats you select. You can also specify abbreviations for displaying minutes, hours, days, weeks, months, and years.

Defining Standard Categories and Values

Use the Admin Categories dialog box to define standard categories and values that you can apply to all methodologies. Choose Admin, Admin Categories.
For more information about expenses, see the Methodology Management Reference Manual.

Expense categories Use the Expense Categories tab to create, edit, and delete expense categories. Expense categories can be used to categorize and standardize methodology expenses, and organize and maintain your expense information. To change an expense category, double-click it, then type a new name. The module applies the change to all activities to which the expense item is assigned.

For more information about activity notes, see the Methodology Management Reference Manual.

Notebook topics Use the Notebook Topics tab to create, edit, and delete notebook topics. A notebook typically consists of instructions or descriptions for performing an activity. You can also assign notebooks to categorize notes about methodologies and WBS elements. Mark the appropriate Methodology, WBS, and Activity checkboxes to activate the availability of a selected notebook topic in the Notebook Topics tab. Examples of topics include Purpose, Entry Criteria, Tools and Techniques, and Exit Criteria. To change a notebook topic, double-click it, then type a new name. The module applies your change to all methodologies, WBS elements, and activities to which the notebook topic is assigned.

For more information about the WBS, see the Methodology Management Reference Manual.

WBS custom category Use the third tab on the Admin Categories dialog box to define a custom WBS category and category values. To change the category name, click in the field in the top right, then type a new name. Use this category to organize, filter, and report WBS information in an open methodology. To change a category value, double-click it, then type a new name. The module applies the change to all methodologies to which the WBS item is assigned.
If you change the WBS category, the module does not change any of the categorys values or value assignments.

Report groups Use the Report Groups tab to create, edit, and delete report groups, which help you organize reports.

Document categories Work products typically refer to activity output, such as blueprints or testing plans, and documents refer to items such as standards and guidelines. Use the Document Categories tab to set up categories for work products and documents, then assign these categories to work products and documents in the Work Products and Documents window, and to WBS elements and activities in the WPs & Docs tab of Work Breakdown Structure Details and Activity Details, respectively. To change a document category, double-click it, then type a new name. The module applies the change to all WBS elements and activities to which the document category is assigned.

For more information about establishing estimation data, see the Methodology Management Reference Manual.

Factor categories Use the Factor Categories tab to set up categories for organizing estimation factors in methodologies. These factors are used in Project Architect to calculate a project size and complexity value for performing bottom-up estimating in the Project Management module. Estimation factor categories are beneficial when you want to assign sets of factors to each methodology and categorize them according to a specific area or phase, such as Internet development and product maintenance. To change an estimation factor category, double-click it, then type a new name. The Methodology Management module applies the change to all methodologies to which the estimation factor category is assigned.

Once you establish estimation factor categories, you can assign one or more estimation factors to them in the Estimation Factors dialog box (choose Define, Estimation Factors). Risk types Use the Risk Types tab to identify, categorize, and prioritize potential risks associated with specific WBS elements. To

change a risk type, double-click it, then type a new name. The module applies the change to all WBS elements to which the associated risk type is assigned.

Units of measure Use the Units of Measure tab to set up units of measure labels that you can assign to material resources. To change a unit of measure label, double-click it, then type a new name. The change applies to all unit of measure assignments.

Defining Currencies
You can specify the monetary unit or base currency used to store cost data for all methodologies in the database, as well as the monetary unit or view currency used to display cost data in windows and dialog boxes.
Only a user with Admin Superuser privileges can change the base currency and define additional view currency types.

The exchange rate for the base currency is always 1.0. If you select a different currency than the base currency to view cost data, the base currency value is multiplied times the current exchange rate for the view currency to calculate the values displayed in cost and price fields. For example, if the base currency is U.S. Dollars, the view currency is Euros, and the exchange rate for Euros is .75, a value of $10 stored in the database is displayed as 7.5 Euros in cost and price fields in windows and dialog boxes. Similarly, if you enter 10 Euros in a cost or price field, it is stored in the database as $13.30.
When you enter values in cost and price fields, they are always displayed in the view currency.

Use the Currencies dialog box to set up the base and view currencies.
If you are upgrading from a previous version of the module, you should set up the base currency in the new version before you start adding and changing methodologies.

Define a base currency The base currency, by default, is U.S. dollars. To define a different currency as the base, choose Admin, Currencies. Select the base currency, then, in the General tab, type the currencys ID, name, and symbol. The exchange rate for the base currency is always 1.0. Click the Appearance tab to further define how the currency is displayed.

If you want to view costs in the old base currency, you will need to add it to the list of available currencies.

Add a view currency Choose Admin, Currencies. Click Add. Specify the currencys ID, name, symbol, and exchange rate, and indicate how the currency should be displayed.

Project team members can use Timesheets to submit timesheets that update their activities in the Project Management module. This chapter describes how to configure the Project Management module

for use with Timesheets, how to run Timesheets once it has been configured, and how to configure access to the Timesheet Approval application for timesheet approval managers. In this chapter:
Implementation Overview Setting Timesheet Preferences Configuring Resources to Use Timesheets Creating Timesheets for Timesheets Users Setting Project-Specific Timesheets Preferences Using Overhead Codes Running Timesheets Web Browser Version and Java Web Start Version Configure Access to Timesheet Approval

Implementing Timesheets
Implementation Overview
Timesheets enables project team members to use the web to communicate timesheet and activity status directly to their organizations database, regardless of their location. This ensures that project managers are always working with the most up-to-date project information, making it easier to plan resource use or resolve conflicts. Timesheets consists of the Timesheets client, the database server that contains your organizations projects, and the Group Server, which links the Timesheets client and database server. Additionally, the P6 Web Access application server hosts the Timesheet Approval application, which timesheet approval managers use to review resource timesheets.
Installation and configuration of Timesheets is slightly different for the Web Browser version and the Java Web Start version. Refer to Configuring the Group Server for Timesheets on page 91 for complete details on how to configure either version of Timesheets. Internet Explorer version 6.1 (SP2) or 7.x is required to support the full functionality of Primavera Timesheets.

Before you implement Timesheets, first ensure that the following steps have been completed:
Install Install Install Install

the project management database, as described in Database Installation and Configuration on page 25. a Web server, if one is not already available. the Group Server, as described in Configuring the Group Server for Timesheets on page 91.

the Timesheets Java files on the Web server, as described in Installing the Group Server and Timesheets Web Site on page 93.
If

you are using Timesheets Java Web Start version, configure Java Web Start as described in Setting up Java Web Start for Timesheets on page 112. After the Timesheets files have been installed, use the Project Management module to perform the following steps, which are described in more detail in this chapter:
Set

preferences for how users will use timesheets. resources to use Timesheets.

Configure Create Set

timesheets.

project-specific preferences for Timesheets.

Create

overhead codes for recording nonproject hours.

Finally, if your organization plans to use the Timesheet Approval application, perform the following, which is described as noted:
The Timesheet Approval application, when properly configured, is accessible from P6 Web Access, the Project Management module, and as a stand-alone application. Since P6 Web Access hosts the Timesheet Approval application, you must install P6 Web Access regardless of how users will access the application.
Install

and configure P6 Web Access as described in Installing P6 Web Access on page 125. timesheet approval requirements in Admin Preferences as described in this chapter.

Specify Assign

product licensing and the required security privileges to timesheet approval managers as described in Administering Users and Security on page 341.
Configure

access to Timesheet Approval as described in Configure Access to Timesheet Approval on page 457.

When you have actual units assigned to resource assignments (whether they came from an imported project or whether you decided to start using Timesheets in the middle of your project), all pre-existing actual values are lost the first time you use Timesheets unless you run the Timesheet Actualizer. See the readme in the Support\Utilities\ folder on CD 3 for more information.

Setting Timesheet Preferences

Use the Timesheets and Timesheet Privileges tabs in the Admin Preferences dialog box in the Project Management module to configure how Timesheets users use timesheets to update project data in the Project Management module. You can determine how often users must report their time, which activities and timesheets users can view, how timesheets are approved before project data is updated, and which privileges are assigned to users for logging time. Set preferences for timesheets In the Project Management module, choose Admin, Admin Preferences. Click the Timesheets tab.

The General Settings section contains the following options:

New

resources use timesheets by default Mark to require that all new resources use timesheets, unless you specify otherwise.
Resources

can assign themselves to activities by default Mark when you want every newly created project to grant permission for resources to assign themselves to activities. When you change this setting, it does not affect existing projects; the new setting is applied only when a new project is created. For individual projects, you can override this setting on the Project Details Resources tab.
Enable

Timesheet Auditing Mark if you want to save the history of timesheet submission, approval, rejection, reviewers, and associated dates. If you select this option, you can add the Timesheet History subject area to a timesheet report to view the historical data. The Entering Timesheets section contains the following options:
Timesheets

users enter timesheet hours Daily Choose to require that all resources report their hours on a daily basis for each assigned activity.
Maximum

hours a resource can enter per day If you choose to require that all resources report their hours on a daily basis, you can optionally specify a maximum number of hours resources can enter per day for all of their assigned activities (minimum 0.5, maximum 24). For example, if you set this value to 12, for all of a resource's activities, a resource can not report more than a combined total of 12 hours per day.
Timesheets

users enter timesheet hours By Reporting Period Choose to require that all resources report their hours

as a single time value for each assigned activity in a timesheet reporting period, regardless of the number of days included in the timesheet period.
Number

of decimal digits for recording hours in timesheets The number of decimal places a resource can use when entering hours in timesheets. Type or click the arrows to select a new number.
Number

of future timesheets users are allowed to access The number of future timesheets a resource can view beyond the current timesheet period. Type or click the arrows to select a new number.
Number

of past timesheets users are allowed to access The number of past timesheets a resource can view before the current timesheet period. Type or click the arrows to select a new number.
If there is a discrepancy between the number of decimal places you enter in the Maximum hours a resource can enter per day and Maximum number of decimal digits for recording hours in timesheets fields, values a user enters in a timesheet field may round up or down. The rounding of values is for display purposes only; the originally entered value is stored in the database. For example, if you specify 10.5 as the maximum hours per day but specify 0 (zero) as the maximum number of decimal places for recording hours in timesheets, if a user enters 10.5 in a timesheet field, the value will round up to 11 in the timesheet. Since the value 10.5 is stored in the database, the resource does not exceed the maximum hours per day setting in this case.
For information on approving timesheets, see the Updating, Scheduling, and Leveling chapter in the Project Management Reference Manual.

The Timesheet Approval Level section contains the following options:

Auto

Submission Choose to indicate that resource timesheets do not need to be submitted or approved. Timesheet data are automatically updated in the database when you apply actuals.
Auto

Approval Choose to indicate that resource timesheets do not require management approval. Timesheets are approved automatically when they are submitted.
1

Approval Level Choose to indicate that resource timesheets require approval by the resource/cost manager only. If you select this option, the status of all submitted timesheets remains Submitted until the approving manager changes the timesheets status. If you previously required both project manager and resource/cost manager approval, and you select this option, the status of all current timesheets that have received one level of approval changes to Approved.
2

Approval Levels Choose to indicate that resource timesheets require approval by project and resource/cost managers. If you select this option, the status of all submitted timesheets remains Submitted until both managers approve the timesheet.
Project

Manager Must Approve Before Resource Manager If you choose 2 Approval Levels, mark to indicate that project managers must approve timesheets before resource/cost managers.
Default

Resource Manager Approving Timesheets The name of the manager who approves resource timesheets, unless you specify otherwise. Click the Browse button to select a new manager.
Once Timesheets users have begun submitting timesheets, if you change the approval level to a lower setting, all currently submitted timesheets are altered to reflect the change. For example, if you change your setting from 2 Approval Levels to Auto Submission, all timesheets, including those that are currently approved by only one manager, are changed to no longer require submission or approval, and the project management database is updated with their data when you apply actuals.

Set Timesheets user privileges In the Project Management module, choose Admin, Admin Preferences. Click the Timesheet Privileges tab.

The Privileges for Logging Hours on Timesheets section contains the following options:
Log

hours on future timesheets Mark to indicate that users can report hours on timesheets with dates after the current timesheet period (for example, entering vacation time in advance).
Log

hours on not-started activities Mark to indicate that users can report hours for activities that have not been

marked as started.
Log

hours on completed Activities and Assignments Mark to indicate that users can report hours for activities and assignments after they have been marked as completed.
Log

hours on completed Assignments only Mark to indicate that users can report hours for assignments that have been marked as completed.
Log

hours on activities before the activity start date Mark to indicate that users can report hours for activities on dates before their start dates.
Log

hours on activities after the activity finish date Mark to indicate that users can report hours for activities on dates after their finish dates.

Configuring Resources to Use Timesheets

To enable a project resource to use Timesheets, you must assign a user login account to the resource and set the resource to use timesheets. Create a user login for Timesheets In the Project Management module, choose Admin, Users. Click Add. Type a unique login name, then click the Licensing tab. Mark the Named User checkbox next to Team Member or Timesheet.
For more information on the functionality associated with licenses, refer to Assign product licensing on page 371.

The Timesheet license provides access to the Timesheets application and enables the user to log into P6 Web Access to import appointments only (provided that this functionality is configured for the user). The Team Member license provides access to the Timesheets application and, in P6 Web Access, enables the user to access some dashboard portlets, the project workspace (for projects they have rights to access), the activities to which they are assigned, and more. You can not assign both the Team Member and Timesheets licenses to a user; you must choose which one to assign.

A user must have a resource assigned to it for the user to access Timesheets. To assign a resource to a login name in the Users dialog box, double-click the corresponding cell in the Resource column, select a resource in the Select Resource dialog box, and click the Select button.

Configure resources to use timesheets In the Project Management module, choose Enterprise, Resources. Display resource details, then click the Timesheets tab.

Each resource can be associated with only one user login.

If you marked the New Resources Use Timesheets by Default checkbox on the Timesheets tab of the Admin Preferences dialog box, when you create a new resource, the Use Timesheets checkbox is marked automatically. You still must assign a user login to the resource and grant that user permission to log in to Timesheets.

Set overtime policy You can enable users to enter overtime in their timesheets. In the Project Management module, choose Enterprise, Resources, then click the Details tab. Mark the Overtime Allowed checkbox. Type the overtime factor by which the resources standard price is multiplied to determine the overtime price (standard price * overtime factor = overtime price).
Resources indicate overtime with a slash (/) in the time field. For example, if a resource worked 10 hours in one eighthour day, the user types 8/2 for that day.

Creating Timesheets for Timesheets Users

Use the Timesheet Dates Administration dialog box to create timesheets for Timesheets users. You can also view a list of previous timesheets and determine which timesheets are currently in use by Primavera Timesheets users. Users cannot view any timesheets in Timesheets until you create them in the Project Management module. Create a batch of timesheets In the Project Management module, choose Admin, Timesheet Dates.

To create another set of timesheets, reset the batch start and end dates, select the appropriate timesheet period, then click Batch Create. Create a single timesheet In the Project Management module, choose Admin, Timesheet Dates. Click Add.

You cannot create new timesheets that have start and end dates that overlap existing timesheet dates.

Setting Project-Specific Timesheets Preferences

For each project in an enterprise, you can control how resources report the status of their activities. Set project-specific Timesheets preferences In the Project Management module, choose Enterprise, Projects. Select the project, then click the Resources tab.

Using Overhead Codes

Overhead codes enable users to log hours that are not associated with project activities; for example, users can enter time for vacations, holiday hours, sick time, or general administrative work as overhead activities. Add overhead codes If the existing set of overhead codes is not adequate, you can add new codes. In the Project Management module, choose Admin, Admin Categories, then click the Overhead Codes tab. Click Add. Type a unique code for the overhead type and a short description.

When you specify that two approval levels are required to approve timesheets, timesheets that contain only overhead activities bypass project manager approval and are sent directly to the resource/cost manager for approval. For timesheets containing a mix of regular and overhead activities, project managers can view, but not approve, the overhead activities.

Running Timesheets Web Browser Version and Java Web Start Version
After you install and configure Group Server/Timesheets (as described in Configuring the Group Server for Timesheets on page 91) and implement Timesheets as described in this chapter, users can access either the Web Browser version or the Java Web Start version by following the instructions in this section.
Timesheets Java Web Start version users only have to complete these steps the first time they attempt to access Timesheets. After completing these steps, users can access Timesheets Java Web Start version by choosing Start,

Programs, Primavera Timesheets, Primavera Timesheets. Timesheets Web Browser version users must always access Timesheets using the URL specified in Step 1.

Run Timesheets 1To load the Timesheets version from the server, visit the URL where the Timesheets launch page is located (the server you specified during installation). For Timesheets Web Browser version, enter: <Web server>/GroupServer/en/Index.html, where /en is the language subfolder. For example, http://10.12.14.123/Groupserver/en/index.html. For Timesheets Java Web Start version, enter: <Web server>/GroupServer/App/index.html. For example, http://10.12.14.123/Groupserver/App/index.html.
If the Web Server is not using the default port, you must enter the port number after the IP address separated by a semicolon (:).

2For Timesheets Web Browser version: Click Run Timesheets. If prompted, click Yes to install the Java files from Primavera Systems. The Setup program searches for the required Java Runtime Environment (JRE). If the required version it is not found on your machine, the setup process to install it is automatically launched. Click Yes to install the required JRE and accept the license agreement.
You will only be prompted to download the Java files the first time you click the Run Timesheets link.

For Timesheets Java Web Start version: Click Launch Primavera Timesheets Application. One of the following scenarios will occur depending on your current JRE version: If a JRE is not installed, you are prompted to download the required JRE version. Click the provided link and download the JRE. When the JRE installation completes, Java Web Start launches Timesheets. If the required JRE version is present, Java Web Start uses the existing JRE. If a JRE version earlier than the required version is present, Java Web Start automatically downloads the required JRE, installs it, then launches Timesheets. Java Web Start does not change the default JRE version for the browser on the client machine when the install is complete. You can change the default version by choosing Tools, Internet Options, in your web browser. On the Advanced tab, select the default JRE in the Java (Sun) section.
Downloading the JRE may take some time, depending on your network speed.

3If prompted, click Grant Always to run the applet. 4Type your login name and password.

If Timesheets is running in Single Sign-On authentication mode, the preceding dialog box does not appear. Instead, login credentials are requested and validated by the policy server.

Your activities appear in the Activities window.

Before a user can log on to Timesheets, the project administrator must configure the Project Management module for Timesheets users. See Implementing Timesheets on page 439.

Configure Access to Timesheet Approval

For information on using the Timesheet Approval application, click Help in Timesheet Approval, or refer to the P6 Web Access Help, Project Management Help, or Project Management Reference Manual.

If your organization requires resource timesheets to be approved by resource/cost managers and/or project managers, timesheets can be reviewed in the Timesheet Approval application. When properly configured, any user with the appropriate license and security privilege can access Timesheet Approval from P6 Web Access, the Project Management module, or as a virtual stand-alone application.
Prior to P6.1, Timesheet Approval was available from both the Project Management module and P6 Web Access as separate applications. In P6.1, the web version of Timesheet Approval has been enhanced and made available from within P6 Web Access and the Project Management module, and as a stand-alone application. Due to these enhancements, all new or upgrading organizations that want to use Timesheet Approval MUST INSTALL P6 WEB ACCESS.

Preliminary setup Before configuring access to Timesheet Approval, be sure to complete the following:
Install

and configure P6 Web Access on a supported application server as described in Installing P6 Web Access on page 125.
Configure

user licensing as described in Assign product licensing on page 371.

To access Timesheet Approval from P6 Web Access or as a stand-alone application, users must be assigned at least one of the following licenses: Project Management, Team Member, myPrimavera Portfolios, myPrimavera Projects, or myPrimavera Resources. To access Timesheet Approval from the Project Management module, users must be assigned the Project Management license.
Assign

global and/or project profiles to timesheet approval managers, as described in Administering Users and Security on page 341, that include the required security privilege to enable approval managers to access Timesheet Approval to review timesheets. To enable a user to approve resource timesheets as a resource/cost manager, the user must be assigned the Approve Resource Timesheets global privilege. To enable a user to approve resource timesheets as a project manager, the user must have the Approve Timesheets as Project Manager project privilege.
Specify

the required timesheet approval levels as described in Setting Timesheet Preferences on page 442.

To configure access to Timesheet Approval from P6 Web Access:

For information on creating and assigning user interface views, refer to Defining User Access to P6 Web Access Functionality on page 391.

P6 Web Access users with the appropriate license and security privilege can access Timesheet Approval by clicking the Approve Timesheets link on the Dashboards Home page. To ensure that the link appears, you must include the Approve Timesheets Action Bar item in each approval manager's assigned user interface view. For new user interface views you create, and for organizations that do not utilize user interface views, the Approve Timesheets Action Bar item appears by default; if a user does not have rights to access Timesheet Approval, the link will not appear on the Dashboards Home page, even if you include it in the user's assigned user interface view. For users upgrading to P6.1, the Approve Timesheets Action Bar item appears for users who had rights to approve timesheets in previous releases. To configure access to Timesheet Approval from the Project Management module: Project Management module users with the appropriate license and security privilege can access Timesheet Approval by choosing Tools > Time Approval. To ensure that Timesheet Approval opens when users select it, you must specify the P6 Web Access URL.

1In the Project Management module, choose Admin > Admin Preferences, then select the Options tab. 2In the myPrimavera Server URL field, enter the URL to the P6 Web Access server in the form of: http://P6_Web_Access_Server_Name:port_number/context_root. For example: http://P6WebServer:8080/myprimavera 3Click Close.
Opening Timesheet Approval from the Project Management module does not provide access to other areas of P6 Web Access.

To configure access to Timesheet Approval as a stand-alone application: Any user with the appropriate license and security privilege can access Timesheet Approval as a virtual stand-alone application. To ensure that timesheet approval managers can access Timesheet Approval as a stand-alone application, you must install and configure P6 Web Access, then communicate the location of the Timesheet Approval application on the P6 Web Access server. After installing and configuring P6 Web Access, complete the following steps: 1Send an e-mail to timesheet approval managers containing the URL of Timesheet Approval in the form of: http://P6_Web_Access_Server_Name:port_number/context_root/action/timesheetapproval.jnlp For example: http://P6WebServer:8080/myprimavera/action/timesheetapproval.jnlp 2Instruct users to click on the link. Java Web Start and the required JRE are installed on the user's machine (if necessary), and users are prompted to login to Primavera. 3Instruct users to enter their Primavera username and password, select the appropriate database, and select a language to login to Timesheet Approval. If Timesheet Approval is successfully downloaded, users can subsequently log into Timesheet Approval by selecting Primavera > Primavera Timesheet Approval from the Windows Start menu.

Read this chapter if you want to define customized financial periods in the Financial Periods dictionary of the Project Management module. After creating financial periods, you can plan and record activity and assignment progress per financial period and store these values as past period actuals when you close out a period. Additionally, P6 Web Access users can display and, in some cases, edit activity and assignment data in financial period timescale intervals. In this chapter:
Defining Financial Periods in the Project Management Module

Defining Financial Periods

Defining Financial Periods in the Project Management Module
For more information on financial periods, including storing period performance and editing past period actuals, refer to the Project Management Reference Manual or Help.

The Project Management module enables you to define your enterprises global financial periods in the Financial Periods dialog box. Customized financial periods provide more accurate display and reporting of actual units and costs. Rather than spreading units and costs evenly throughout the length of a project, users can view how actual units and costs were incurred by customized financial period. Users can store period performance for any predefined period in the Financial Period dictionary.

For more information on displaying a financial period timescale in P6 Web Access, refer to the P6 Web Access Help.

In P6 Web Access, for the range of defined financial periods, users can display summary project data in financial period timescale intervals in charts and spreadsheets, as well as edit high-level planning assignments in financial period intervals.
You must have the Edit Financial Period Dates global privilege to add or edit data in the Financial Periods dialog box. To store past period actuals for a projects defined financial periods, you must have the Store Period Performance project privilege. To edit past period actual data after storing period performance, users must have the Edit Period Performance project privilege.

Financial period considerations for P6 Web Access users In P6 Web Access, users can customize many tabs and pages to display a financial period timescale if financial periods are properly defined in the Project Management module. To enable P6 Web Access users to display financial period timescale intervals, you must adhere to the following guidelines when creating financial periods: all defined financial periods must have a minimum duration of one week (seven days) there can not be a time gap between any two financial periods
Following these requirements only ensures that P6 Web Access users can display a financial period timescale. To ensure that data is displayed in financial period timescale intervals in P6 Web Access, you must additionally summarize projects by financial period. To summarize projects by financial period, choose Admin, Preferences, select the Options tab, then select the By financial period option. For more information on this option, see Options on page 412.

Create batches of financial periods In the Project Management module choose Admin, Financial Periods.

The start and end dates of a financial period cannot overlap existing financial periods. Also, you cannot modify the start and end dates of a financial period after you create it. If your organization summarizes project data by financial period (as specified on the Admin Preferences, Options tab), to ensure that all project data in the database will be summarized (including closed projects), you must create financial periods that span the date range of all projects in the database. For example, if the oldest project in your database has a project start date of October 1st, 2001, your financial periods should begin on or before that date.

Create a single financial period In the Project Management module choose Admin, Financial Periods. Click Add.

All periods start at midnight and end at 11:59 PM. The end date must be at least one day later than the start date; therefore, the shortest financial period you can create is two days long. For example, if you create a financial period with a Start Date of July 1, 2007, and an End Date of July 2, 2007, the period begins at midnight on July 1st and ends at 11:59 PM on July 2nd. To enable users to display financial period timescale intervals in P6 Web Access, all financial periods must have a minimum duration of one week (seven days).

Delete a financial period In the Project Management module choose Admin, Financial Periods. Select the financial period(s) you want to delete. Click Delete.
You cannot delete a financial period that stores past period actuals for any project. If you attempt to delete multiple financial periods at the same time, none of the financial periods will be deleted if any period stores past period actuals for any project. In this case, to delete a financial period, you must archive and delete the project containing past period actuals, then delete the financial period. You can delete a financial period that has high-level assignment planning values (as entered on the Plan Resources page of P6 Web Access) as long as the financial period does not contain past period actuals. When you delete a

financial period that has high-level assignment planning values, the values are deleted as well.

Appendix A: Running Primavera Databases in One Oracle Instance Appendix B: Undoing Changes in the Project Management Database

Appendices

hese appendices describe how to run the Project Management and Methodology Management

modules in one Oracle database instance and how to undo changes youve made to the project management database.

Read this appendix if you want to run the project management database (PMDB) and the methodology management database (MMDB) in one Oracle instance. If you already are running PMDB and MMDB in a single Oracle instance, read the section on upgrading. In this appendix:
Process Overview Running MMDB and PMDB in a Single Oracle Instance Upgrading a Single Instance Database from Primavera 5.0 or 6.0 to P6 version 6.1

Appendix A: Running Primavera Databases in One Oracle Instance

Process Overview
The following steps outline the process for running the PMDB and MMDB databases in one Oracle instance.
Create

an Oracle instance and install the PMDB database server as described in Database Installation and Configuration on page 25.

Install

the Primavera client, which can install the Project Management and/or Methodology Management modules, as described in Primavera Client Installation and Configuration on page 277.
Create

the MMDB database and load data as described in this section. the private database login for MMDB. the database alias for PMDB. the database alias for MMDB.

Configure Configure Configure

Be sure you have enough disk space available to run both databases in the same Oracle instance.

At the end of the process, your database should look like the following:

User
admuser privuser pubuser

Default Tablespace
pmdb_dat1 pmdb_dat1 pmdb_dat1

For PMDB For MMDB User

admuser1 privuser1 pubuser1

Default Tablespace
mmdb_dat1 mmdb_dat1 mmdb_dat1

Running MMDB and PMDB in a Single Oracle Instance

The following steps describe how to run MMDB and PMDB in the same Oracle instance. These steps should be performed by your database administrator (DBA).
If you will be loading a license key file as part of this procedure, copy the file to hard disk before you begin. A license key file is required to use the software and should have been provided via e-mail or CD. It contains your company name, serial number, the product components with version number you have purchased, and the number of users allowed.

1Create the database structure and load the PMDB database as described in Automatically Installing an Oracle Database and Loading Application Data on page 30.
If you have an existing project management database and you need to preserve the data, you should NOT set up and install the databases as described in Configuring the Server Databases on page 39; otherwise, your existing data will be deleted and replaced.

2Install the Primavera client modules as described in Installing Client Modules and Additional Components on page 279. 3Create the methodology management database, MMDB, and load data using the Database wizard, as described in Automatically Installing an Oracle Database and Loading Application Data on page 30. When you reach step 6 (page 31), choose MMDB as the database type.

4Choose Create Database and Load Application Data as the installation method. If you choose to load the license key file now, browse to the location of the LICENSE.TXT file. If the LICENSE.TXT file is not available at this time, you can clear this checkbox and load the file later using the Database wizard. Refer to Changing Database Configuration Settings on page 317 for more information. 5Type the Oracle system user name and password to log on to the database. Also, enter the Oracle connect string.

6Click Next to accept the name for the Data, Index, and LOB tablespaces and estimated tablespace sizes.

7Accept the default location for the Oracle tablespaces, Data, Index, and LOB.

8Type ADMUSER1 as the Oracle administrative name, PRIVUSER1 as the Oracle privileged name, and PUBUSER1 as the Oracle public name. If necessary, choose a different default tablespace and temporary tablespace; however, the temporary tablespace must be of temporary type.

9In the Ready to Begin Creating Database dialog box, choose Yes, I Want to Create Database Tables and Structure, then click Next. 10Follow the remaining steps in the Database wizard to create the tables and load the data. Click Finish to exit the wizard when it has completed.
If you need to drop the MMDB objects created by the database installation script, run the scripts in the install\database\scripts\install\or\OneInstance\drop\MMDB folder of CD 1. You must log onto the database as ADMUSER1. To drop PMDB objects, refer to Configuring the Server Databases on page 39.

Configure the private database login for MMDB Private database logins are used primarily by administrators to gain direct access to a database. For example, the privileged user login that you use to access the database is a private database login. 1From Start, choose Programs, Primavera, Help and Utilities, Database Configuration. 2Click Next on the Welcome dialog box.
Click Next on each wizard dialog box to advance to the next step.

3Choose Administration Tasks.

4Choose Administer private database logins.

5Select Methodology Manager database.

6Type the name and password of a privileged database user. This login should have administrative rights on the database.

7Review the explanation of private database logins and click Next. 8Edit the Private DB Username to match the name defined for the Methodology Management database (for example, privuser1), by clicking on the name. Click Finish to close the wizard.

Configure the database alias for PMDB 1You can use the Database Configuration wizard to change/review the connection settings and database alias for PMDB, as shown in the next five figures.

Create a database alias for MMDB Use the Database Configuration wizard to create an alias for MMDB. 1Choose to configure your database connection.

2Choose MMDB as the database type.

3Enter MMDB as the database alias and select Oracle as the driver type.

4Enter the Oracle connect string.

5Enter pubuser1 as the Username and Password.

6Click Next to validate the database connection.

The following dialog indicates if the connection was successful.

Once you complete these steps, you should be able to run the Methodology Management and Project Management modules using the aliases you established, while still connecting to the same database.

Upgrading a Single Instance Database from Primavera 5.0 or 6.0 to P6 version 6.1
If you are configured to run your PMDB and MMDB database in a single Oracle instance and you are using version 5.0 or 6.0, follow these steps to upgrade the database for use with P6 version 6.1. Upgrade an Oracle project management database when running with MMDB in a single instance 1Perform a cold backup and a full database export. If you are unsure how to back up your Oracle database, do not proceed with the upgrade. Contact your database administrator, your database vendor, or Primavera Systems for assistance in backing up your database before performing the database upgrade. Also, ensure that you are familiar with the process of restoring the backup copy of the database in case you need to do so.
You should NOT set up and install the databases as described in Configuring the Server Databases on page 39; otherwise, your existing data will be deleted and replaced with default application data.

2Double-click ConfigAsst.exe in the \install\database directory of CD 1 to start the Database wizard. 3Choose Upgrade an Existing Primavera Database, enter the product key located on the License CD label, then click Next.

4Click Next to begin the upgrade process.

5Choose Oracle as the database type.

6Log on to the database as an administrative user, such as ADMUSER. Type your password. Specify the Oracle connect string. ADMUSER must have DBA privileges and must be the owner of the application tables. The database must also have the Oracle compatible parameter set to 10.2.0 or greater. The Oracle connect string must be specified. It can be found in the TNSNAMES.ORA file. The TNSNAMES.ORA file is created when you or your DBA set up the instance.

7Log on to the database as a privileged user, such as PRIVUSER.

8In the Ready to Begin Upgrading Data dialog box, choose 'YES, I Want to Upgrade My Database', then click Next. The current version of your existing database appears.

The upgrade process could take several minutes, depending on its size. 9Click Finish when the Database Upgrade Completed message is displayed. 10Run the Database wizard again to upgrade your methodology management database. This time, in step 6, log onto the

database as ADMUSER1 and in step 7, log on as PRIVUSER1. ADMUSER1 must have DBA privileges and must be the owner of the application tables. 11Run the Database Configuration wizard from the client and update your license in the database. Refer to Changing Database Configuration Settings on page 317 for more information. Your database is ready to use with P6.

The Undo feature enables you to change certain actions made to a project. For example, if you add a resource to an activity then decide you do not want the resource assignment, you can choose to undo this action. This chapter explains what actions you cannot undo, and what tasks will prevent you from undoing an action. In this appendix:
Understanding Undo Configuring Safe Deletes

Appendix B: Undoing Changes in the Project Management Database

Understanding Undo
Use undo to replace project data to its previous state before changes were made. You can undo edits, additions, and deletions in the Activity and Resource Assignments windows in the Project Management module. Undo stores actions that were made to the project database, however, certain actions will clear the stored actions:
Creating Opening

projects and closing projects data

Summarizing Updating Applying

progress Actuals data

Refreshing Importing Auto

scheduling in as a different user portfolios

Logging

Changing

Opening Exiting

the Project Portfolios, User Preferences, Admin Preferences, and Time Approval dialog boxes

the application

For more information on using the Undo feature, see the Project Management module Help.

Undo an action Choose Edit, Undo. The latest action stored for undo will display next to the Undo command. For example, if you add a resource assignment to an activity, then choose to remove the assignment from the activity, the Undo command in the Edit

menu will display as Undo Add Activity Resource Assignment.

Configuring Safe Deletes

The project management database normally handles restoring deleted data using a safe delete setting. Deleted data remains in the project management database until you choose to permanently clear it. Use the Undo command (Edit, Undo) to restore data that has been deleted. Turn off safe deletes To instantly clear deletes from the project management database when data is deleted, you have to turn off the safe deletes function. If you are running SQL Server, you can use its administrative tools to execute SQL commands. In the database, if the table ADMIN_CONFIG has the following row, a CONFIG_VALUE of 'N' means turn off safe deletes. CONFIG_NAME = 'SAFEDELETE' and CONFIG_TYPE = 'ACTIVE' This is only loaded at startup. If you change this value while PM is running, the setting will not apply. You can run the following statements. To turn off safe deletes for the first time: INSERT INTO ADMIN_CONFIG (CONFIG_NAME, CONFIG_TYPE, CONFIG_VALUE) VALUES ('SAFEDELETE', 'ACTIVE', 'N') To turn on safe deletes after its been turned off run the following update statement: UPDATE ADMIN_CONFIG SET CONFIG_VALUE = 'Y' WHERE CONFIG_NAME = 'SAFEDELETE' AND CONFIG_TYPE = 'ACTIVE' To turn off safe deletes after its been turned on run the following update statement: UPDATE ADMIN_CONFIG SET CONFIG_VALUE = 'N' WHERE CONFIG_NAME = 'SAFEDELETE' AND CONFIG_TYPE = 'ACTIVE'

A
Activities notebook topics420, 430 Additional components, installing279 Administer database settings57 Administration401420 Administrative categories415 preferences402 Administrative categories, defining425 Administrative preferences, defining425 APIxv, 6, 13, 16, 294 Application data installing for Oracle52 installing for SQL Server52 loading for Oracle30 loading for SQL Server35 auditing detailed configuration83 overview81 simple configuration82 Authentication configure for P6 Web Access161 configuring323338

LDAP104 login procedures338 Native324 Single Sign On106 Authentication Configuration wizard327 Authentication library, adding226 Automatic database install27 for Oracle30 for SQL Server or SQL Server Express database automatic install35

B
background processing monitoring64 reading writing setting values62 settings table61 Base currency, setting31, 53 for SQL database36 Baselines types415

C
Categories document417, 432 estimation factors433 expense416, 430 notebook420 risk419 units of measure420, 434 WBS431 work products417 Check in projects364 Check out projects364 Client modules changing user passwords320 installing285 minimum requirements16 CMS service, starting227 Codes maximum number of characters for, specifying407 overhead418 separator402, 426 Collaboration6 configuration tasks215 configuring P6 Web Access247 creating a configuration215 extending the schema243 migrating202 migrating on Windows192, 196, 204 new install210 Collaboration server overview6 CONFIGASST.EXE304, 482 Configuration Manager215 Controller server252 configure267 Costs summary calculation, specifying time interval for spreadsheet displays412

Currencies defining435 setting base436 Currency adding view422 defining421 setting base422 Custom portlets password encryption162 Customer supportxvi

D
Dashboards, team member access to375 Data limits, specifying maximum number of levels for428 Database administration57 automatic upgrade301 changing configuration settings for P6 Web Access152 client drivers, installing280 driver configurations161 extending the collaboration schema243 improve Oracle performance80 installing automatically27 MMDB28, 40 PMDB28, 40 upgrading Oracle304 SQL Server306 Database administratorxiv, xv role defined8 Database configuration change settings317 Database Configuration wizard application license changes320 database setting changes318 initialization (INI) files318 private database logins320 user password changes320 DBConfig. See Database Configuration wizard. DBExpress4 DCOM communication252 configure for distributed job service on Windows Server 2003 and XP256 Default duration402 hours in each timeperiod408, 429 Default settings402 Distributed Job Service configure DCOM on Windows Server 2003 and XP256 servers267 configuring251 disable Windows Firewall254 installing253, 282, 287 overview6, 252 planning issues12 prepare servers252 registry settings270 supported configurations18 Document formats, updating244

Documents categories417 status418 Documents, categories432 DomainAdmin user adding236 make manager of primavera.com240 Duration default402 Durations default type426

E
Earned value defining defaults411 E-mail, supported systems20 Enterprise project structure access and privileges to384 defined344 module-wide parameters and values, setting401 EPS. See Enterprise project structure. Estimation factors categories433 Exchange rate31, 36, 53, 421 Expenses categories416 defining standard categories430

F
Facility, adding234 Financial periods defining461 summarizing412 Firewall disabling for distributed Job Service254

G
Global profile assigning to users370 creating354 for the Methodology Management module394 definitions353 new privileges302 overview342 privileges defined354 for the Methodology Management module394 Group Server administrator applet108 configure LDAP authentication104 configure Single Sign On authentication106 configuring for Timesheets91 configuring settings108 creating multiple instances115 HTTP(S)99 installation overview93 installing95 international language support94 overview5 planning issues13

registry settings118 reviewing properties110 supported configurations18 taking offline108 uninstalling92 user connections111

H
Hierarchies specifying maximum number of levels406 Hours, defining default for timeperiod408 Hours, defining default number for each timeperiod429 HTTP(S), using for secure transmission of timesheet data99

I
ID lengths407 specifying maximum number of characters for407 ID lengths427 Incremental license, storing320 Indexer service adding228 starting230 Install Primavera client279 Integration API license, description of373 International language support47, 94 for Job Service293 Invited users, access to project data374

J
Java Web Start93 job scheduler configuring, Oracle59 configuring, SQL Server59 Job Service choose language293 configure Project Architect for P6 Web Access158 creating multiple instances288 distributed252 configure DCOM on Windows 2003 and XP256 configure servers267 Controller server252 disable Windows Firewall254 installing253 installing282, 287 overview6 planning issues12 registry settings270 running on multiple databases290 send jobs directly to printer292 summarizer jobs291 registry settings271 supported configurations18 Job Services uninstalling 5.x versions281

L
Language support47, 94

for Job Service293 LDAP authentication324 for Group Server/Timesheets104 login procedures338 provisioning336 LDAP servers configuring for authentication327 License assigning to users371 configuring320 incremental320 loading at database setup32, 36, 54, 470 named user371 License key file32, 36, 470 limits practical23 Login name, maintaining single login for project resources and users369

M
MDAC282 Methodology management database40 administering private logins320 changing connection settings318 client drivers280 combining with PMDB467 creating on Oracle44 on SQL Server50 installing application data52 removing from Oracle45 from SQL Server51 running in same Oracle instance as PMDB469 sample data30, 35, 53 upgrading on SQL Server306 Oracle304 Methodology Management module default settings426 installing282 minimum configuration requirements16 overview4 planning issues12 security393400 adding users398 global profiles394 methodology profiles396 Methodology profile creating396 privileges defined397 MMDB. See Methodology management database. myPrimavera uninstalling127

N
Native authentication324 login procedures338

Network administratorxiv, xv role defined8 Network protocols, supported software20 Notebook topics420 Notebook topics430

O
OBS assigning to the EPS385 to users383 defined344 denying access to project information383 in enterprise344 responsible361, 384 root385 Operations executivexiv Oracle automatic database install30 creating database structures41 improve database performance80 installing client drivers280 Methodology Management module sizing guide22 Project Management module sizing guide21 running MMDB and PMDB in one instance469 supported versions18 upgrading database304 Organizational breakdown structure. See OBS. ORMM_INS.SQL44 ORPM_INS.SQL41 Overhead codes418, 453

P
P6 Web Access accessing from client browsers147 adding configurations157 adding database instances157 administration application153 application server requirements19 available Team Member functionality374 changing database configuration settings152 client requirements17 collaboration6 configuration settings163 configure authentication161 custom portlets162 to run Project Architect158 configuring the application server133 database drivers161 defining user access391 deleting configurations158 deleting database instances158 deploying the application server133 financial period considerations462 implementing application server plugins186 installation process overview130 installing125

installing the application server128 invited users374 JSP server requirements19 licensing372 managing access to multiple database instances159 overview5 planning issues15 reviewing and modifying configurations155 starting the server145 stopping the server146 upgrading from a previous version126 Web server requirements19 Passwords changing320 encrypting for custom portlets162 Past period actuals462 performance optimizing80 PMDB. See Project management database. PMSDK294 Primavera additional components5 authentication324 choosing components12 client modules4 documentationxiv installation process overview10 license accessibility371 minimum requirements16 security342 server components5 solution overview4 uninstalling previous versions281 using the Administrators Guidexii Primavera client, installing279 Primavera ProjectLink licensing373 Primavera Software Development Kit documentation296 installing282, 294 overview6 planning issues13 supported configurations16 Primaveras Web Application uninstalling127 Primavision uninstalling127 Privileges, new in 5.0302 product limits23 Program managerxiv role defined9 Project Architect158 Project controls coordinatorxiv, xv role defined9 Project data Team Member access to376 Project management database28, 40 administering private logins320 changing connection settings318 client drivers280

combining with MMDB467 creating on Oracle41 on SQL Server47 installing application data52 removing from Oracle43 from SQL Server49 running in same Oracle instance as MMDB469 sample project data30, 35, 53 SQL Server parameters46 undoing changes487 upgrading on SQL Server306 Oracle304 Project Management license, description of372 Project Management module adding users368 defining financial periods461 installing282 minimum configuration requirements16 overview4 planning issues12 Project managerxiv role defined9 Project profile assigning to OBS elements382 to users383 creating361 definitions361 new privileges302 privileges defined362 Project Web Site, supported configurations19 ProjectLink installing282, 297 overview6 user access298 Projects checking in364 checking out364 Provisioning from LDAP336

Q
Quantity summary calculation, specifying time interval for spreadsheet displays412

R
Rate types defining414 RDBMS. See Relational database management system. Relational database management system overview5 planning12 supported configurations18 Reports defining defaults411 groups431 Resource security387

Resource/cost managerxiv Resources assignment level for summarization in spreadsheets413 associating with users369 defined344 defining access to387 Risks types419, 434 Roles assignment level for summarization in spreadsheets413 Root OBS385

S
Safe deletes, configuring489 SDK. See Primavera Software Development Kit. Security341400 associating resources and users369 defining access to resources389 global profiles353 assigning to users370 implementation process overview351 licensing371 Methodology Management module393400 OBS EPS assignments385 user and project profile assignments382 overview342 project profiles361 resource access387 users368 in the Methodology Management module398 OBS and project profile assignments383 Server components supported configurations18 Server databases, configuring39 Setting defaults402 Setup wizard, running282 Single Sign On authentication324 for Group Server/Timesheets106 login procedures338 Spreadsheets specifying time interval for cost and quantity summaries412 SQL Server automatic database install35 creating database structures46 installing client drivers280 international language support47 Methodology Management module sizing guide22 Project Management module sizing guide21 upgrading database306 SQL Server Express database installing299 installing client drivers280 SSPM_INS.SQL47, 50 Stand-alone version installing282, 299 upgrading automatically299 Standard categories and values, defining415 Status document418

work product418 Summarizer job settings271

T
Team leaderxiv Team memberxiv available P6 Web Access functionality374 Timesheets module4 Team Member license, description of372 Technical supportxvi Timeperiods, defining default number of hours429 Timesheet Approval configure access457 configure stand-alone application459 set approval levels404 Timesheet auditing, enable403, 443 Timesheets approval levels, set404, 444 creating batches450 default setup options403 maximum hours per day443 setting parameters for403 Timesheets application privileges, setting405 Timesheets license, description of372 Timesheets module configure LDAP authentication104 configure Single Sign On authentication106 configuring in the Project Management module439442, ??453 configuring resources to use449 creating timesheets450 user login447 entering overtime449 implementation overview440 installing Web files95 Java Web Start version defined14 JRE installation455 minimum requirements17 overview93 running454 overhead codes453 overview4 planning issues13 preferences442 project-specific preferences452 user privileges445 versions14 Web browser version defined14 JRE installation455 minimum requirements17 running454 TNSPING.EXE28, 40 Trustees, adding231, 234

Unattended setup creating file set310 planning issues12 running314 Undo, using488 Uninstalling Job Services 5.x versions281 the Group Server92 Units of Measure categories434 Upgrading automatically301 license320 Oracle database304 process overview302 SQL Server database306 stand-alone version299 User interface views, assigning391 Users adding368 Methodology Management module398 assigning global profile370 product licensing371 profiles in the Methodology Management module399 to OBS elements382 associating with resources369 changing passwords320 defined344 for the Timesheets module447

W
WBS defining custom category431 level, specifying for summarization413 WBS, defined344 Web browsers supported for P6 Web Access17 supported for the Timesheets module17 Web Scheduler12 Work products categories417 status418 Work products and documents categories432

Inde x