Copyright 1999, 2011, Oracle and/or its affiliates. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle and Primavera are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. To view the P6 Commercial Notices and Disclosures for Documentation, go to the \Documentation\<language>\Notices and Disclosures folder of the P6 physical media or download.
Notes: This Quick Install Guide now applies to 7.0 and 7.0 SP3. Starting with P6 version 7.0, a license file is no longer required during the P6 installation and configuration process.
After you familiarize yourself with the contents of the media pack, do the following: 1. Download the .zip file or access the .zip file on the media provided, based on your product implementation. 2. Unzip the files. 3. Install the products. See the next section, Installation Requirements and Instructions, for information on where to find documentation for installation. 4. Refer to the Readme file that is installed with the products for more information on the release.
COMPONENTS A list of the P6 components and references to resources, information, and files needed for installation will be presented in the following format: <COMPONENT NAME> Description Resource needed P6 Administrator's Guide new installation instructions (by page number) Location of installation file(s) in media pack
DATABASE Description: A database is required to store the P6 project data. The database may be either an ORACLE or MICROSOFT SQL SERVER database: The project management database (PMDB) stores the Project Management data used by Oracle Primavera software. It is a required database. During database creation, you will be given the option to create the database schema object for the optional Content Repository (document management) functionality in the same database as PMDB or two different databases. This option can be disregarded since the Content Repository functionality is only available for use with P6 Web Access. (optional) The methodology management database (MMDB) stores project templates that can be used when creating new projects. You must install this database if you will be using the Methodology Management module. Resource needed: Database Administrator or equivalent to prepare the database system environment and to run the P6 Database Utility wizard to create the P6 schema in the database.
P6 Administrator's Guide new installation instructions: Overview on page 46 Automatic database installation instructions o Oracle database on page 49 o Microsoft SQL Server database on page 53 Location in Media Pack: Installation wizard utility may be run from either of the following two locations: \Client_Applications\setup.exe (choose Other Applications > P6 Database Utility) \Client_Applications\install\database\dbsetup.bat DESKTOP CLIENTS Description: A database client (Oracle or MICROSOFT SQL SERVER) must be installed and configured for database connectivity on each desktop client workstation connecting to a database. The Project Management desktop client enables users to access the project database to plan and control a large number of projects. End users may access the project management database via either a desktop client or the P6 Web Access client, however at least one Project Management Desktop Client must be installed for user account access administrative purposes . (Optional): Methodology Management desktop client enables user to access the optional Methodology Management database to create project templates. Notes: (Distributed) Job Service is installed with the Client Applications installer and may be installed during a client installation or may be installed separately. [See (Distributed) Job Services component description below.] The Desktop Clients are designed to be used when connecting via a LAN connection from the workstation to the database. If users are accessing over a WAN connection, options are to implement the P6 Web Access client , or use the Desktop Client in a Citrix environment, or use Compression Server (Oracle only, see Additional Components section below.)
Resource needed: Desktop Administrator or equivalent to install the Oracle database client and P6 Desktop client. P6 Administrator's Guide new installation instructions: Pre-Installation Overview on page 260 Installation on page 263 Location in Media Pack: \Client_Applications\setup.exe, chose Primavera Client Applications JOB SERVICE Description: A database client (Oracle or MICROSOFT SQL SERVER) must be installed and configured for database connectivity on each desktop client workstation connecting to a database. The (Distributed) Job Service is a Windows service that performance two functions: 1) Users can create jobs in the Project Management module and have (Distributed) Job Service run the jobs on project data at preconfigured intervals. 2) (Distributed) Job Service runs on-the-fly jobs for some of the P6 Web Access functionality.
Job details are stored in the central project management database. The (Distributed) Job Service periodically reads the database and performs jobs as directed. Notes: This service must run on a server that has a constant connection to the database server. (Distributed) Job Service may not be installed on a workstation that is shut down at the end of the day. Each database may only have one Job Service configured to run its jobs. However, Distributed Job Service is an extension of the Job Service that enables a controller machine to manage multiple servers running job services for one database. Job Service is installed with the Client Applications installer and may be installed during a client installation or may be installed separately, as desired.
Resource needed: Desktop administrator or equivalent P6 Administrator's Guide new installation instructions: (Distributed) Job Service Overview on page 232 Installation of 7.0 Job Service on page 268 Continuation of Installation for (Distributed) Job Service on page 233 Location in Media Pack: \Client_Applications\setup.exe, choose custom.
10
COMPONENTS A list of the P6 components and references to resources, information, and files needed for installation will be presented in the following format: <COMPONENT NAME> Description Resource needed P6 Administrator's Guide upgrade instructions (by page number) Location of installation file(s) in media pack
DATABASE Description: A database is required to store the P6 project data. The database may be either an ORACLE or MICROSOFT SQL SERVER database: The project management database (PMDB) stores the Project Management data used by Oracle Primavera software. It is a required database. During database creation, you will be given the option to create the database schema object for the optional Content Repository (document management) functionality in the same database as PMDB or two different databases. This option can be disregarded since the Content Repository functionality is only available for use with P6 Web Access. (optional) The methodology management database (MMDB) stores project templates that can be used when creating new projects. You must install this database if you will be using the Methodology Management module. Resource needed: Database Administrator or equivalent to prepare the database system environment and to run the P6 Database Utility wizard to create the P6 schema in the database. P6 Administrator's Guide upgrade instructions: Upgrade Process Overview on page 286 Automatic database upgrade instructions o Oracle database upgrade instructions on page 288 o Microsoft SQL Server database upgrade instructions on page 291
11
Location in Media Pack: Installation wizard utility may be run from either of the following two locations: \Client_Applications\setup.exe (choose Other Applications > P6 Database Utility) \Client_Applications\install\database\dbsetup.bat DESKTOP CLIENTS Description: A database client (Oracle or MICROSOFT SQL SERVER) must be installed and configured for database connectivity on each desktop client workstation connecting to a database. The Project Management desktop client enables users to access the project database to plan and control a large number of projects. End users may access the project management database via either a desktop client or the P6 Web Access client, however at least one Project Management Desktop Client must be installed for user account access administrative purposes. (Optional): Methodology Management desktop client enables user to access the optional Methodology Management database to create project templates. Notes: (Distributed) Job Service is installed with the Client Applications installer and may be installed during a client installation or may be installed separately. [See (Distributed) Job Services component description below.] The Desktop Clients are designed to be used when connecting via a LAN connection from the workstation to the database. If users are accessing over a WAN connection, options are to implement the P6 Web Access client , or use the Desktop Client in a Citrix environment, or use Compression Server (Oracle only, see Additional Components section below.)
Resource needed: Desktop Administrator or equivalent to install the Oracle database client and P6 Desktop client. P6 Administrator's Guide upgrade instructions: Upgrade Process Overview on page 262 Upgrading Client Modules on page 263 Location in Media Pack: \Client_Applications\setup.exe, chose Primavera Client Applications JOB SERVICE Description: A database client (Oracle or MICROSOFT SQL SERVER) must be installed and configured for database connectivity on each desktop client workstation connecting to a database. The (Distributed) Job Service is a Windows service that performance two functions: 1) Users can create jobs in the Project Management module and have (Distributed) Job Service run the jobs on project data at preconfigured intervals. 2) (Distributed) Job Service runs on-the-fly jobs for some of the P6 Web Access functionality. Job details are stored in the central project management database. The (Distributed) Job Service periodically reads the database and performs jobs as directed.
12
Notes: This service must run on a server that has a constant connection to the database server. (Distributed) Job Service may not be installed on a workstation that is shut down at the end of the day. Each database may only have one Job Service configured to run its jobs. However, Distributed Job Service is an extension of the Job Service that enables a controller machine to manage multiple servers running job services for one database. Job Service is installed with the Client Applications installer and may be installed during a client installation or may be installed separately, as desired.
Resource needed: Desktop administrator or equivalent P6 Administrator's Guide upgrade instructions: Uninstalling Previous Version of Job Service on page 262 Installation of 7.0 Job Service Location in Media Pack: \Client_Applications\setup.exe, choose custom.
13
P6 Industry Types
P6 requires you to choose an industry during database setup and application installation. The industry type that you choose determines the terminology and default settings that display in P6. The following table lists each industry type and its corresponding terminology and default settings. When prompted during installation procedures, choose the option that best matches your industry. Oracle recommends, but does not require, that you use the same industry for each database or application installation.
ec
Cmt
Claim Digger
Activities
pd
It
Schedule Comparison
User-defined
HighTechnology, Manufacturing
it
It
Schedule Comparison
Projects
mt
Cmt
Claim Digger
Projects
Other Industry
it
It
Schedule Comparison
User-defined
14
15