Primavera P6 Administrative Guide
Primavera P6 Administrative Guide
Primavera P6 Administrative Guide
Administrator’s Guide
Version 6.2
Copyright © 1999 - 2008 Primavera. All rights reserved.
The software described herein and this documentation is furnished under a Software License Agreement and
may be used only in accordance with the terms of the Agreement.
Except as provided in the applicable Software License Agreement, Primavera assumes no liability resulting from
any omission or inaccuracies in this document or from use of the information obtained herein. Except as
provided in the applicable Software License Agreement, Primavera does not assume any liability arising out of
the application or use of any product described 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.
The software products described in this document may not be copied, reproduced, modified, or distributed,
except as indicated in the Software License Agreement. You may not reproduce the printed version of the User
Documentation or other printed materials accompanying the software, except as expressly permitted in the
Software License Agreement or in writing by Primavera. However, you are permitted to reproduce and
distribute as many copies of the electronic version of the User Documentation, in printed and electronic format,
as you reasonably require in support of your use of the software.
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, as set
forth in the Software License Agreement. Use, modification, reproduction, release, performance, display or
disclosure of the software and accompanying documentation by the U.S. Government are subject to the restric-
tions set forth in the Software License Agreement.
Trademarks: Primavera, the Primavera sundial, Authorized Representative, Solution Provider, Business
Solutions for a Project-Driven World logos, P6, P5, P3, Primavera Project Manager, Primavera ProSight,
Primavera Contract Manager, Pertmaster, Primavera Cost Manager, Evolve, Primavera Contractor, Primavera
Inspire, Claim Digger and SureTrak are either trademarks, services marks or registered trademarks of Primavera
in the United States and/or other countries. All other trademarks mentioned herein are the property of their
respective owners.
Table of Contents
Preface................................................................................................ vii
Using the Administrator’s Guide .......................................................................viii
Primavera Documentation..................................................................................... x
Where to Get Support ........................................................................................xiii
Primavera
Table of Contents v
Primavera
vi Table of Contents
: Appendices
Appendix A: Running Primavera Databases in One Oracle
Instance ...........................................................................................423
Process Overview.............................................................................................. 424
Running MMDB and PMDB in a Single Oracle Instance ................................ 425
Upgrading a Single Instance Database from Primavera 5.0, 6.0, or 6.1 to
P6 version 6.2.................................................................................................. 435
Appendix B: Undoing Changes in the Project Management
Database..........................................................................................441
Understanding Undo ......................................................................................... 442
Configuring Safe Deletes .................................................................................. 443
Index..................................................................................................445
Primavera
vii
Preface
Primavera provides comprehensive,
In this preface: multiproject planning and control software,
built on Microsoft® SQL Server and Oracle
Using the Administrator’s Guide
databases for enterprise-wide project
Primavera Documentation
management scalability. Smaller multiuser
Where to Get Support
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.
viii Preface
Primavera Documentation
You can access reference manuals and administrator’s guides from the
Primavera Documentation Center, located in the
\Documentation\<language> folder of the P6 physical media or
download. When viewing a PDF, view the information using Adobe
Acrobat Reader (also available in the Documentation folder). The
following table describes documentation publications and lists the
recommended readers by role. Primavera roles are described in
“Installation Process Overview” on page 3 of this manual.
Title Description
Primavera Administrator’s This guide explains how to set up the Primavera server, database, and
Guide 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.
Project Management Reference This guide explains how to plan, set up, and manage projects in an enterprise
Manual 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.
Methodology Management This guide explains how to establish methodologies, or project templates, using
Reference Manual 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 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 Timesheets Web-based Help describes how to use Timesheets to enter and
update time spent on assignments. Team members should read this Help.
ProjectLink 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.
Integration API Administrator’s This guide explains how to install and configure the Integration API
Guide (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 in the \Integration\API folder of the P6 physical media or
download.
P6 Web Services Administrator’s The P6 Web Services Administrator’s Guide explains how to install and configure
Guide, P6 Web Services P6 Web Services, which enables organizations to seamlessly integrate Primavera
Programmer’s Guide, and P6 functionality into other web-based applications using web services standards.
Web Services Reference Manual The P6 Web Services Programmer’s Guide, available as an HTML help system,
describes how to invoke, use, and troubleshoot the available services/methods
within supported environments. The P6 Web Services Reference Manual, also
available as an HTML help system, describes all services and operations
available in P6 Web Services in a comprehensive manner. Those creating client
code in Java and needing direct access to the project management database
should read all of this documentation. After installing P6 Web Services, this
documentation is available in the \docs folder of your P6 Web Services installation
folder; it is also available in the \Integration\Web_Services folder of the P6
physical media or download.
SDK (Software Development This documentation describes how to use the SDK to connect to the project
Kit) Web-based documentation 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.
Projects
Portfolios
Methodologies
Content Repository
Workflows Repository
For details on the You are not required to install the server-based components as shown
configuration requirements
here. For example, the P6 Web Access and Timesheets applications can
of each component, see
“Planning Your be running from the same server, and Job Services can run on any
Implementation” on computer with a constant connection to the project database. For
page 13.
optimal performance, Primavera recommends that the components be
installed as shown above.
The planning phase is Phase 1: Plan your Primavera configuration Before you begin
covered in this part of this
the installation, decide how your organization will implement the
guide.
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 247.
Automatic and manual Phase 2: Configure your Primavera servers Once you have set
configuration of the
databases is covered in
up your network and prepared your servers, you can begin to configure
Part 2 of this guide. Server the servers. Start by setting up the project management and
configuration is covered in methodology management databases on the database server. You can
Part 3.
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 Phase 3: Configure your Primavera client modules Once your
configuration phase is
covered in Part 4 of this
servers are configured and the databases are installed, you can begin to
guide. 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.
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.
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 savings—no 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.
The following table lists each client component and the corresponding
server-based components that it requires.
Oracle
Oracle
Recommended
File
Size
Total 950 MB
Recommended
File
Size
Data 300 MB
Temp 100 MB
Temp Log 50 MB
Total 600 MB
Practical
Application Element
Limit
If you choose not to follow the automated steps, you can also
manually set up the database and load the data. See “Manual
Database Configuration” for detailed instructions.
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 Primavera supports Oracle, Microsoft SQL Server, and Microsoft SQL
on installing Oracle for the Server Express databases. The MS SQL Server or Oracle server
server and client, or SQL software must be installed on the database server(s) before you can
Server for the server, create the database.
contact Primavera
Customer Support.
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 a batch file to load
application data. This chapter walks you through the automatic method,
while the next chapter, Manual Database Configuration, covers the
manual instructions.
For additional tips and Oracle considerations Before installing the Primavera database,
considerations related to
consider the following:
database performance
along with additional
settings, refer to ■ If you intend to run Primavera on an Oracle database server, the
“Database Administration”
on page 63. 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 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 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.
If you will be using the Methodology Management module, you will run
through 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.
Clicking Create on this step will begin the initial setup of the
project management database. After this step, you will no
longer be able to click Previous to change your prior
selections. On the next step, however, you will have the
option to either click Next or Cancel.
If you are using Oracle 11g, the case used for user names
will be the same case used for passwords. For example, if
ADMUSER is typed for the user name, the password will also
be ADMUSER, in all uppercase letters.
14 On the Finish dialog box, click Next to run the Database wizard
again if you will be using the Methodology Management module.
Otherwise, click Finish to exit the wizard.
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.
The database code page will default to what is already selected for
Microsoft SQL Server. Select a different code page, if necessary.
Clicking Next after this step will begin the initial creation of
the project management database. After this step, you will no
longer be able to click Previous to change your prior
selections. On the next step, however, you will have the
option to either click Install or Cancel.
11 On the Finish dialog box, click Next to run the Database wizard
again if you will be using the Methodology Management module.
Otherwise, click Finish to exit the wizard.
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 Primavera supports Oracle, Microsoft SQL Server, and Microsoft SQL
on installing Oracle for the Server Express databases. The MS SQL Server or Oracle server
server and client, or SQL software must be installed on the database server(s) before you can
Server for the server, create the database.
contact Primavera
Customer Support.
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.
You can also use a wizard These instructions assume you are an Oracle DBA or are familiar with
that automatically creates administering Oracle databases. All steps need to be completed and in
the database structures the order specified. If you have any questions about the manual setup
and loads the data for you. process, please contact Customer Support before proceeding.
Refer to “Automatic
Database Installation” on
Primavera recommends that you use SQL Plus to run scripts referenced
page 29 for more
in the following instructions.
information.
You must connect to the server as admuser to drop objects. If data exists,
you must drop the objects in the order they are listed above.
1 Create two folders on a local drive, one named “install” and the
other named “source.” If these folders were already created for the
PMDB instructions, the existing folders can be used.
2 From the Client_Applications folder of the P6 physical media or
download, browse to \install\database\scripts\install. Copy the
MM_06_02_00 folder to the install folder on the local drive.
3 From the P6 Client_Applications folder of the P6 physical media or
download, browse to \install\database\scripts\source. Copy the
MM_06_02_00 folder to the source folder on the local drive.
You must connect to the server as admuser to drop objects. If data exists,
you must drop the objects in the order they are listed above.
Creating Users
1 Log on to the new Oracle database as SYSTEM or other DBA
privileged user.
2 Go to \install\JR_01_01_00 and execute the orjr_create_users.sql
script.
Running the script creates a user named CRUSER.
See “Client and Server Primavera supports Microsoft SQL Server 2005. These instructions
Requirements” on page 18 assume you are a DBA or are familiar with how to administer Microsoft
for more detailed
information. SQL Server databases. All steps need to be completed and in the order
specified. If you have any questions about the manual setup process,
please contact Customer Support before proceeding.
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 Management Studio:
■ 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.
You can change the initial tablespace sizes and 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.
Refer to “Project Management Database Server Sizing Guide” on
page 23 for guidelines on sizing.
You must connect to the server as the SA user to drop objects. If data
exists, you must run the scripts in the order listed above.
1 Create two folders on a local drive, one named “install” and the
other named “source.” If these folders were already created for the
PMDB instructions, the existing folders can be used.
2 From the Client_Applications folder of the P6 physical media or
download, browse to \install\database\scripts\install. Copy the
MM_06_02_00 folder to the install folder on the local drive.
3 From the Client_Applications folder of the P6 physical media or
download, browse to \install\database\scripts\source. Copy the
MM_06_02_00 folder to the source folder on the local drive.
You can change the initial tablespace sizes and 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.
Refer to “Methodology Management Database Server Sizing
Guide” on page 24 for guidelines on sizing.
You must connect to the server as the SA user to drop objects. If data
exists, you must run the scripts in the order listed above.
Database Administration
Read this chapter to learn how to configure
In this chapter: the job scheduler supplied by your RDBMS,
how to optimize performance of your Oracle
Background Processes and Clean
Up in P6 and SQL Primavera databases, and how to
Configuring the RDBMS configure the native database auditing
Scheduler feature to monitor edits, deletions, and
Setting Table additions to the databases.
Reading and Writing Setting
Values
Tracking Background Job
Execution
SYMON (System Monitor)
DAMON (Data Monitor)
Improving Oracle Database
Performance
Native Database Auditing
64 Part 2: Database Installation and Configuration
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.
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.
Setting Table
Settings Table Overview
The settings table contains name-value pairs that configure the behavior
of the background processes.
■ 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.
■ Namespace: database.cleanup.Usession
■ Setting Name: ExpiredSessionTimeout
■ Value: 2h (two hour interval)
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:
Namespace database.background.Symon
Default N/A
Setting
Namespace database.background.Damon
Default N/A
Setting
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.
For example, setting the value to "2d" deletes expired sessions older
than two days.
Namespace database.cleanup.Usession
Default 2h
Setting
Type Interval
Namespace database.cleanup.Usession
Default 12h
Setting
Type Interval
Refer to the following table for information about the settings associated
with the BGPLOG_CLEANUP procedure.
Namespace database.cleanup.BackGroundProcessLog
Default Setting 5d
Type Interval
Refer to the following table for information about the settings associated
with the REFRDEL_CLEANUP procedure:
Namespace database.cleanup.Refrdel
Default 5d
Setting
Type Interval
Namespace database.cleanup.Refrdel
Default 0 (false)
Setting
Type Boolean
Namespace database.cleanup.Refrdel
Default 1,000
Setting
Type Numeric
Namespace database.cleanup.Refrdel
Default 10 (%)
Setting
Type Numeric
Namespace database.cleanup.Refrdel
Default 10,000
Setting
Type Numeric
Refer to the following table for information about the settings associated
with the OBSPROJ_PROCESS_QUEUE procedure.
Namespace database.obsproj.queue
Default 1000
Setting
Type Numeric
Namespace database.obsproj.queue
Default 25
Setting
Type Numeric
Namespace database.obsproj.queue
Default 50
Setting
Type Numeric
Refer to the following table for information about the settings associated
with the CLEANUP_PRMQUEUE procedure:
Namespace database.cleanup.Prmqueue
Default 5d
Setting
Type Interval
Namespace database.cleanup.Prmqueue
Default 0 (false)
Setting
Type Boolean
Namespace database.cleanup.Prmqueue
Default 1,000
Setting
Type Numeric
Namespace database.cleanup.Prmqueue
Default 10(%)
Setting
Type Numeric
Namespace database.cleanup.Prmqueue
Default 10,000
Setting
Type Numeric
Refer to the following table for information about the settings associated
with the CLEANUP_LOGICAL_DELETES procedure:
Namespace database.cleanup.LogicalDelete
Default Setting 5d
Type Interval
Namespace database.cleanup.LogicalDelete
Type Boolean
Namespace database.cleanup.LogicalDelete
Type Numeric
Refer to the following table for information about the settings associated
with the PRMAUDIT_CLEANUP procedure:
Namespace database.cleanup.auditing
Default 1 (true)
Setting
Type Boolean
Namespace database.cleanup.auditing
Default 30d
Setting
Type Interval
Refer to the following table for information about the settings associated
with the CLEANUP_USESSAUD procedure:
Namespace database.cleanup.Usessaud
Default Setting 5d
Type Interval
Namespace database.cleanup.Usessaud
Type Boolean
Namespace database.cleanup.Usessaud
Type Numeric
Namespace database.cleanup.Usessaud
Type Numeric
Namespace database.cleanup.Usessaud
Type Numeric
Level Description
Level 0 No audit.
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.
exec auditing_enable(null,3);
The following code snippet enables level one auditing on the task table:
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:
Operation
0 0 0 No audit.
The following table provides some example uses of the options setting:
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:
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.
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.
For more information about Java Web Start Java Web Start provides a secure and platform-
Java Web Start, visit the independent deployment of Timesheets using Java Network Launching
http://java.sun.com Web Protocol (JNLP) technology. Java Web Start also ensures that users
site. 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.
Before performing these steps, you must have already set up the central
project management database.
3 On the Enter Product Key screen, enter the product key that was
provided via e-mail or as listed on the License CD label.
4 On the Welcome! dialog box, click Next.
5 On 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.
6 On the Choose Language dialog box, choose to install Timesheets
in any of the languages listed.
7 On 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.
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.
9 On the Choose Database Type dialog box, select the database type.
The database must already be installed and configured.
10 On 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 Oracle’s 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.
13 If 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 109).
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 114.
Web Server
3 On 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 For secure transmission using the HTTPS protocol, enter https and
the URL after Setup by
editing the erps8x6.html
the port number to which you have configured your Java
file in the application server to service https requests.
\GroupServer\Language
folder. For more The default secure port on JBoss is 8443. In this case, for example,
information, see “Edit the specify the secure URL as,
erps8x6.html or
timesheets.jnlp File” on https://<jboss_server_name>:8443/groupserver/groupserver.
page 108.
Before:
type=magnus-internal/cgi exts=cgi,exe,bat
After:
type=magnus-internal/cgi exts=cgi,bat
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.
<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>
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.
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 Mark the Send Message to Logged in Users checkbox and type a
body of the message, message. You can specify how often to resend the message. Once the
which will automatically Group Server is offline, all client connections are terminated and future
report the amount of time connection requests are denied.
remaining before the
server goes offline.
For an explanation of each Mark the Show Advanced Properties checkbox to show additional
property and its location in
the system registry, see
properties that you can change. You should not change these properties
“Group Server casually; incorrect settings may prevent the server or operating system
Configuration Settings” on from working properly.
page 125.
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.
To learn how to run How does Java Web Start work? Java Web Start can launch a
Timesheets after Java Web
Java application stored on a server by presenting a link in an HTML
Start has been configured,
refer to “Running page to the user. When the user clicks the link on the HTML page, Java
Timesheets Web Browser Web Start detects whether the user has the correct JRE version installed
Version and Java Web Start
Version” on page 411. and the most recent version of Timesheets cached. If not, Java Web Start
automatically downloads the necessary files, then launches Timesheets
from the user’s 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.
.jnlp application/x-java-jnlp-file
Double-click the MIME Types icon, and click Add in the Actions area.
Enter .jnlp for the File name extension and application/x-java-jnlp-file
for the MIME type.
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
Troubleshooting
■ Remember that Apache URLs are case sensitive, even if the user
has a Windows client that does not differentiate.
■ For non-Windows clients, the server IP address has to be mapped to
the server name in the host file.
■ For 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.
Select an instance,
then use these tabs
to view properties/
users for that
instance.
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.
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 Oracle’s Net
Configuration Assistant, or you can refer to your TNSNAMES.ORA file
located in \Oracle_Home\Network\Admin.
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.
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.
Allow Negative Actuals Yes/No Allow negative actuals when calculated. No - Disallow. Yes -
Allow.
Cycle Seed Yes/No 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.
Enable Primary Resource to Yes/No If Y, overrides OBS access to edit step’s UDF values. Gives edit
Edit Step’s UDF Values rights to primary resources.
Counters If N, steps can be edited if user has OBS access to the project.
The default value is N.
Greeting Sets the message that appears in the client when first connected
to the TPGS server.
LDAP Connect Timeout 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.
Log Transactions Records transactions for tracing to the event log
Maximum Auto-Fetch Size 2048 Maximum size of blobs (notes/memos) in bytes that will be sent
(bytes) automatically in low bandwidth mode.
Maximum Request Size 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.
Startup Wait Period 0 Amount of time the TPGS service delays before starting. Use this
(seconds) setting if dependent services (such as a database server service)
need time to start first.
User Inactivity TimeOut 600 Amount of time in seconds a connection can remain idle before
Period being logged off. The default value is 600.
ADO Connection TimeOut 15 Amount of time to wait while establishing a connection before
(seconds) terminating the attempt and generating an error message.
ADO Command TimeOut 30 Amount of time to wait while executing a command before
(seconds) terminating the attempt and generating an error message.
ADO RecordSet Cache Size 5 The number of records stored in memory at any given time.
ADO Stalled Check Period 30 Frequency with which the connection is checked for stalled
(seconds) operations.
Apply Session Setting Yes/No Determines whether to execute the SQL command specified in
the Session Setting property. The default value is No.
Auto Translate Yes/No The Auto translate property of the SQL Server ODBC Driver for
a SQL Server Unicode database.
Base Connections 25 (default=10) Default number of database connections that the TPGS server
makes on startup.
Cache Refresh Interval 60 Frequency of the TPGS server for refreshing cached data from
(seconds) the database.
Connect Retry Period 30000 Amount of time to wait before retrying to connect.
(milliseconds)
DB User privuser User name with privileged access used to connect to the
database. The default value is privuser.
License Inactivity TimeOut 900 Period that inactive licensed client connections are considered to
(seconds) be bad.
Log Invalid Login Attempts Yes/No Logs invalid login attempts to the event log. The default value is
No.
Log SQL 0 Sets SQL tracing flags for tracing to the event log.
Max Search Result Records 100 Maximum number of records in search results.
Sync Period 60 Period between updating the sync table in the database.
(seconds)
Synchronize ADO Yes/No Blocks other requests while connecting to a database. The default
Connection Creation value is Yes.
Temporary Connections 150 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.
Verbose Logging Yes/No Determines if verbose logging is enabled when sending error
messages to the event log.
Coalescing Jobs Busy 50 Number of coalesced jobs that determine when the coalescing
Threshold processor is considered busy.
Coalescing Threads 1 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.
Coalescing Timeout 750 Frequency that coalesced requests are fulfilled.
(milliseconds)
Connection TimeOut Period 300 Period of inactivity for which attached database
(seconds) connections are assumed to be good.
License Manager Interval 120 Frequency that the license manager is checked for concurrent
(seconds) users.
Message Threads Per CPU 3 (default=1) 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 Coalescing Size 20 Maximum number of coalesced transactions that can be queued
before they are processed.
Maximum Temporary 15 Maximum number of threads that can be started by each
Threads Per CPU (SMP) processor.
MaxTempThreads=CPU>1?MaxTempThreads+(MaxTempThre
ads*4/CPU
Thread Inactivity TimeOut 180 Period of inactivity before a temporary thread is shut down.
Period (seconds)
Transaction Threads 1 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.
Update Threads 1 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.
Watch Dog Period 120 Frequency that the TPGS server checks for connection problems.
(seconds)
Accept Filters Filter #1, *.*.*.* TCP/IP client addresses that will be accepted.
Reject Filters Filter #1, *.*.*.255 TCP/IP client addresses that will be rejected.
For the full list of tested To upgrade from myPrimavera 5.0, Primavera’s Web
configurations for P6 Web Application 6.0, or P6 Web Access 6.1 to P6 Web Access 6.2:
Access, go to the
■ Uninstall the current version of myPrimavera, Primavera’s Web
\Documentation\
Application, or P6 Web Access. See “Uninstalling Previous
<language>\Tested
Configurations folder of the Versions” on page 133.
P6 physical media or ■ Install one of the supported application servers. See “Installing the
download. Application Server for P6 Web Access” on page 135.
For a list of supported application servers, see “Client and Server
Requirements” on page 18.
■ Install P6 Web Access 6.2. See “Installation Process for P6 Web
Access” on page 137.
■ Configure and Deploy the application server. See “Configuring and
Deploying the Application Server for P6 Web Access” on page 142.
5 Select the folder ‘default,’ press Ctrl-C to copy it, and then press
Ctrl-V. This creates a folder named ‘default(copy)’.
6 Rename the folder called 'default(copy)' to be 'primaveraweb'.
Installing WebLogic
Install the JDK
The 10 (sp1) version of WebLogic automatically installs Java 2 JDK
version 5.0 update 11 (1.5.0_11) for Windows and Red Hat Enterprise
Linux and Java 2 JDK version 5 update 8 (1.5.0_08) for HP-UX. These
are the required JDK versions for P6 Web Access.
Installing WebSphere
Install the JDK
The 6.1 version of WebSphere automatically installs the IBM JDK.
Installing the recommended fix pack will update the JDK automatically,
which is the required JDK for P6 Web Access. For information on
which fix packs were tested, refer to the Tested Configurations
document.
The installer for P6 Web Access provides a wizard to guide you through
the installation process, which includes:
For the full list of tested The application EAR file (primaveraweb.ear) is copied to the
configurations for P6 Web home folder for P6 Web Access. You must then use the
Access, go to the application server’s deployment tools to deploy the P6 Web
\Documentation\ Access EAR file. Also, make sure that the supported JDK is
<language>\Tested set as an environment variable in your path to provide access
Configurations folder of the to the java command.
P6 physical media or
download.
5 On the P6 Web Access will be installed. . . dialog box, click Next
to start the installation.
6 On the Setup and Configuration of the Primavera Database
dialog box, select the database type (Oracle or SQL).
7 On 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.
For more information 8 If there is an existing Primavera configuration, on the The installer
about configurations, see
“Using the Administration
has detected. . . dialog box, you can choose whether you want to
Application” on page 164. use it, or create a new configuration.
For more information, see After installation, you can use the Database Configuration
“Changing Database Setup wizard to choose a different configuration, if
Configuration Settings” on
page 163.
necessary.
For information about The schedule, apply actuals, and summarize functions of P6
installing the Job Service, Web Access require you to install the Job Service.
see “Installing the Job
Service and Distributed Job
Service” on page 235.
After installing the Workflow Repository, you will need to input the
Database/Instance/Workflow Repository Administration Application
settings. For detailed information about these settings, refer to the
Database Settings subsection in “Configuration Settings for P6 Web
Access” on page 174.
set JAVA_OPTS=
"-Dprimavera.bootstrap.home=<webaccesshome>"
%JAVA_OPTS%
Make sure to change <webaccesshome> to the proper location (for
example, c:\p6wahome). Also, there is a space between
<webaccesshome>” and %JAVA_OPTS%.
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 (as all one line):
-Djava.awt.headless=true
set CLASSPATH=c:\<webaccesshome>\license\;c:\
<webaccesshome>\lib\ojdbc5.jar;%SAVE_CLASSPATH%
CLASSPATH=''/usr/local/<webaccesshome>/license'':''/user/
local/<webaccesshome>/lib/ojdbc5.jar'':${CLASSPATH}
9 Save the changes to the startWebLogic file.
10 Make a backup copy of the setDomainEnv.cmd (or
setDomainEnv.sh for Linux) file in case you need to undo any
changes.
11 Edit the setDomainEnv file.
12 Increase 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 Windows, the line should look similar to the following:
if “%JAVA_VENDOR%”==”Sun” (
set MEM_ARGS=%MEM_ARGS% %MEM_DEV_ARGS%
-XX:MaxPermSize=256m
)
5 Restart the application server, and the change will immediately take
effect.
Installation on Windows
These steps should be performed immediately after installing
P6 Web Access.
The file path of the P6 Web Access EAR file cannot contain
spaces.
Click to
display a
hierarchical
view of the
configuration
data.
To change a
setting
value, triple-
click on the
setting
name, then
type a new
value. On
Windows,
you can also
press F2 to
change to
Edit mode.
To sort the
table, click a
column
heading.
Sorting can
help you
distinguish
similar
settings
contained in
multiple
configurations.
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 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 163).
For information on These instructions assume you have already installed the
installing and configuring Job Service.
the job service, refer to
“Installing the Job Service
and Distributed Job
Service” on page 235.
1 If 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 270.
For example, the following URL would log a user into the database
instance named Sample.
http://serverIP:listenport/login_it?db=Sample
■ Authentication/Mode
■ Authentication/Web Single Sign-On/User Name Header Key
■ Authentication/Web Single Sign-On/Context Path Override
■ Authentication/Web Single Sign-On/Server and Port Override
■ Authentication/LDAP/SSL Certificate Store
■ Authentication/LDAP/SSL Store Password
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, use the 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.
[Localization Settings]
Localization/System Language en —
Language for server string constants
Localization/System Country US —
Country for server string constants
[Authentication Settings]
[Database Settings]
Database/Instance/Name — up to 32 characters
The name of this database instance.
Database/Instance/Schema PMDB —
The schema that will be defined for the database.
Database/Instance/URL — —
The database URL used to establish a connection to the
database.
Oracle example:
jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
jdbc:sqlserver://xxxx:yyyy;database=zzzz;
x = IP address or hostname
y = database listen port
z = database name
Database/Instance/Public Group ID 1 —
The public group ID used to establish a connection to the
database.
Database/Instance/User Name pubuser —
The name used to establish a connection to the database.
Database/Instance/Password pubuser —
The password used to establish a connection to the database.
[Database Settings]
[Database Settings]
[Database Settings]
[Database Settings]
[Database Settings]
Database/Instance/Methodology Management/Name — —
Name of this database instance.
Database/Instance/Methodology Management/ — —
Description
Description of this database instance.
Database/Instance/Methodology Management/URL — —
Database URL used to establish a connection to the
database.
Oracle example:
jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
jdbc:sqlserver://xxxx:yyyy;database=zzzz;
x = 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/ 1 —
Public Group ID
The Group ID used to establish a connection to the database.
[Database Settings]
[Database Settings]
Database/Instance/Content Repository/URL — —
Database URL used to establish a connection to the
database.
Oracle example:
embedded://jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
embedded://jdbc:sqlserver://xxxx:yyyy;database=zzzz;
x = IP address or hostname
y = database listen port
z = database name
[Database Settings]
Database/Instance/Workflow Repository/URL — —
Database URL used to establish a connection to the
database.
Oracle example:
jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
jdbc:sqlserver://xxxx:yyyy;database=zzzz;
x = IP address or hostname
y = database listen port
z = database name
[Database Settings]
[Log Settings]
[Log Settings]
JBoss on Windows:
<webaccesshome>\WebAccessLogs
JBoss on Red Hat Enterprise Linux:
/mount_point/<webaccesshome>/AppServer/
WebAccessLogs
WebLogic on Windows:
<webaccesshome>\WebAccessLogs
WebLogic on Solaris:
/mount_point/<webaccesshome>/WebAccessLogs
WebSphere on Windows:
<webaccesshome>\WebAccessLogs
WebSphere on Red Hat Enterprise Linux:
/mount_point/WebSphere/AppServer/WebAccessLogs
[Application Settings]
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 true true/false
Set to false to account for daylight savings time.
[Application Settings]
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 true true/false
Set to true to compress communication between applets and
the server.
[Application Settings]
This setting is only valid when using JRE version 1.6.0_10 (or
later).
[Application Settings]
[Services Settings]
[Services Settings]
[Services Settings]
[Services Settings]
[Services Settings]
[Tracer Settings]
In addition to the Prepare the Controller and DJS servers for installation and
preparations described in
this section, you must
configuration
configure the database for Be sure to complete the following tasks before you install and configure
P6 Web Access to run the
Project Architect job DJS on the Controller and servers:
service. Refer to
“Configure P6 Web Access
to run the Project Architect
■ On the Controller and all DJS servers, define the “Temp” and
job service” on page 169. “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.
On the server that controls the domain in which the Controller and DJS
servers reside, perform the following steps:
3 On the Controller and each DJS server, add the group you created to
the Local Administrator Group.
4 In the Security tab of the DCOM Configuration dialog, add the
group you created to each Custom permission.
1 From the command line (or Start, Run utility), run dcomcnfg. The
Component Services dialog is displayed.
2 In the Component Services dialog, expand the tree in the left panel
by clicking Component Services, Computers, My Computer,
DCOM Config.
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.
10 In 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.
14 In 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.
19 In 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.
23 In the Properties dialog, select This Account and enter the password
of an administrative user on the Controller.
Select Disabled
to disable the
DJS on that
machine. In this
example, the
Controller will
execute jobs on
the servers but
not on itself.
4 Set 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).
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 204, you must reboot the
machine(s) on which you made the modifications.
My Computer\HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\PrmJobSvXXXX\Parameters
(where XXXX equals the DB Alias of the database connection).
EstablishDBConnectionRetryCount 3 1-10
Number of times to try to connect to database on startup.
MaxNumNonRecurringJobs 1 1-5
The maximum number of non-recurring (P6 Web Access)
jobs that can run simultaneously.
NonRecurringJobRefreshRate 5 1-3600
Frequency (in seconds) in which P6 Web Access jobs are
loaded from the database.
For more information Edit registry settings for summarizer jobs Type 'regedit' in the
about summarizer jobs,
refer to “About summarizer
Start, Run utility to open the Registry Editor. In the Registry Editor,
jobs and P6 Web Access” navigate to the following directory:
on page 239.
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.
[Summarizer settings]
Valid Ranges/
Setting Name and Description Default
Values
NumProjectsSummarizedAtATime 1 1-xx
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 50 0-100
The percentage threshold that determines how the summarizer will analyze a
project’s 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:
MaxDurationToSummarize -1 -
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.
[Summarizer settings]
Valid Ranges/
Setting Name and Description Default
Values
[Summarizer settings]
Valid Ranges/
Setting Name and Description Default
Values
RetrySleep 60000 -
The time, in milliseconds, to wait between retry attempts when
there is a connection failure.
MaxRetries 10 -
The maximum number of retry attempts to make when there is a
connection failure.
[Summarizer settings]
Valid Ranges/
Setting Name and Description Default
Values
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.
4 On 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 client’s 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.
If you are working with more than one project management database,
you can run jobs for all of the databases from one Windows 2003/2008
Server machine by installing multiple instances of the Job Service, as
described in this section.
For more information on If you want to be able to run multiple jobs simultaneously on separate
the distributed job service,
servers, you can install the Distributed Job Service on a controller server
refer to “Configuring the
Distributed Job Service” on that manages the Job Service and distributes jobs to the Job Service
page 199. servers.
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.
2 On 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/2008 Server machine. Create
one job service instance for each database.
For more information on When installing multiple instances of the Job Service, you
running jobs on multiple should first stop all existing job services.
databases using the Job
Service, see “Running Job
Services on Multiple
Databases” on page 238.
The Job Service uses the DB alias to connect to the database server.
7 On 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.
8 On the Validate Database Connection dialog box, click Next to
validate the database connection.
The DB alias that you specified is created.
11 Click Finish.
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.
4 On the Select Driver Type dialog box, select the driver type of
your database server. You can select Oracle or Microsoft SQL
Server/SQL Express.
5 Type 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.
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.
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 user should now be able to access ProjectLink on the local machine.
3 If you are upgrading the standalone version and have kept the
default password for logging into Microsoft SQL Server Express
(“prima” for P5 and “Prima123Vera” for P6 versions 6.0 and 6.1),
skip to step 5. If you are upgrading from P5, your password for
logging into Microsoft SQL Server Express will automatically
update to “Prima123Vera,” in accordance with strong password
policy requirements.
If you are upgrading the standalone version and have a different
password other than the default for Microsoft SQL Server, you will
be prompted to enter the password. After entering the password, the
following will occur, depending on the version from which you are
upgrading:
• If upgrading from P5, your password will automatically be
changed to “Prima123Vera.” You may set up a custom password
after completing the upgrade to P6 version 6.2.
• If upgrading from P6 version 6.0 or 6.1, your custom password
will remain intact.
To upgrade a stand-alone You can upgrade your database automatically using the Database
installation, see “Installing
wizard. The wizard runs the necessary scripts to upgrade the database
and/or Upgrading the
Stand-Alone Version” on structure and an upgrade program to add data required by the new
page 247. version.
If you are currently running Primavera with Microsoft SQL Server, see
“Upgrading a Microsoft SQL Server Database to P6” on page 257.
■ 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:
8 On the Finish dialog box, click Next to run the Database wizard
again if you are using the Methodology Management module.
Otherwise, click Finish to exit the wizard.
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.
5 On the Ready to Begin Upgrading Data dialog box, verify that the
the current version of your existing database is listed correctly.
Choose Yes, upgrade my database, then click Upgrade.
The upgrade process could take several minutes, depending on its
size.
7 On the Finish dialog box, click Next to run the Database wizard again
if you are using the Methodology Management module. Otherwise,
click Finish to exit the wizard.
For information on running You can also rerun the Setup wizard to recreate a set of
an attended setup, see unattended setup files or to create multiple sets of files for
“Running an Unattended
Setup” on page 266.
different configurations.
6 On the Product Code dialog box, enter the product key that was
provided via e-mail or as listed on the License CD label.
7 Accept the license agreement.
8 On the Setup Type dialog box, choose Custom.
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.
3 On the What would you like to do? dialog box, choose Configure
my database connections.
4 On the Select Database Alias dialog box, choose the appropriate
database; for example, PMDB.
5 On 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.
If you create a new DB alias for a module, the module’s 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 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.
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.
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 user’s 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 user’s identity is confirmed in an
LDAP-compliant directory server database. Additionally,
Primavera supports the use of LDAP referrals, which allows
authentication to extend to another domain.
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.
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.
5 To add a new LDAP server, click Add.
6 On 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. To use referrals, mark the Chase
Referrals checkbox.
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 7 Select an LDAP server. Then, in the LDAP attribute column,
field that must be mapped specify the term/field in the LDAP store that corresponds to the
and can not be deleted. Up Primavera project management/methodology management database
to four fields can be USER_NAME field.
mapped between the
LDAP store and the project Optionally, specify the LDAP term/field for e-mail address, actual
management/methodology name, and office phone number. To add fields, click Add. To
management database. remove a field, select it and click Remove.
If you are unsure of the correct LDAP terms, check with your
LDAP directory server administrator.
Click to
remove the
current
search
results or
currently
selected
users.
After running a search, select the Available For the selected users, click to compare
users you want to add to the Primavera records between the Primavera db and
database, then click the right arrow button. To LDAP store. Status is indicated by
remove a user from the Selected users list, background color. White indicates a
click the left arrow button. Click the double match, blue indicates that the db record
arrows to add or remove all listed users. differs from the record in the LDAP store,
and red indicates that the user record
does not exist in the database.
• 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.
After provisioning users, 11 When finished importing user information, in the Import LDAP
you will need to set up Users dialog box, click Close. To exit the Authentication
Primavera user accounts Configuration wizard, click Finish.
for the imported users by
assigning security profiles
and licenses through the
Project Management or
Methodology Management
modules.
For detailed information on 1 On the server where the Project Management module is installed,
authentication
go to \Program Files\Common Files\Primavera Common\Java and
configuration settings for
P6 Web Access, see run admin.cmd to launch the Administration Application.
“Configure Authentication”
on page 172. 2 Ensure that the Custom/INTERNAL_PLUGINS/Authentication/
Mode configuration setting has a value of LDAP.
In Native mode
■ Primavera modules present a login dialog that prompts for a user
name and password. In Native mode, the use of passwords may be
optional, depending on the password policy chosen in
Administrative Preferences.
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.
XYZ
Corporation
Tech.
Services
Internal External
IT Projects Projects
IT HR
Maintenance System
WBS.1
WBS.2
XYZ
Corporation
Technology
Services
Information
Technology Consulting
Department Department
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.
XYZ
Corporation
Technology
Services Tech.
Services
Marie Ross - PA
Information
Technology
Internal External
Department
IT Projects Projects
Gretchen Schantz - PA
IT HR
Maintenance System
WBS.1
Project Profiles:
Project Administrator (PA)
Project Manager (PM)
WBS.2
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.
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:
XYZ
Corporation
Technology
Tech.
Services
Services
Marie Ross - PA
Information
Technology External
Department Internal
IT Projects Projects
Gretchen Schantz - PA
IT HR
Maintenance System
XYZ
Corporation
Technology
Services Tech.
Services
Marie Ross - PA
Information
Technology External
Department Internal
IT Projects Projects
Gretchen Schantz - PA
IT Project
Manager 2
IT HR
Maintenance System
Jim Harkey - PM
Dee Morris - AM
Network Hardware HR System HR System
IT Project Upgrade Upgrade Development Testing
Manager project project project project
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.
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 The following steps provide guidelines and a general process for
Management module uses
administering users and security in Primavera. Because the structures
its own security model to
control access to the are global across the company, some steps may require information
methodology management from many participants. You can vary the order depending on your
database. See “Setting
Security in the company’s implementation plan. Also, some of these processes, such as
Methodology Management defining resource security and user interface views, are optional
Module” on page 350.
depending on the needs of your enterprise.
3 Set up the OBS for your company and assign each element of the
OBS to the appropriate users and project profiles.
The Project Management Identify your company’s management structure and include the
Reference Manual roles or names of those who will be responsible for the projects and
(PMRefMan.pdf) is work to be completed. See “Setting Up the Organizational
available online and can be Breakdown Structure” in the Project Management Reference
accessed from your Manual for more information. Also, see “Assigning OBS Elements
industry-specific folder in
and Project Profiles” on page 338.
the \Documentation\
<language>\ folder of the
P6 physical media or 4 Set up the EPS for your company and assign the responsible
download. View the manager (OBS) to each node.
information using Adobe Identify your company’s project structure, which is global across
Acrobat Reader (also
the enterprise. See “Setting Up the Enterprise Project Structure” in
available in the
the Project Management Reference Manual for more information.
Documentation folder).
Administrators can also set 8 Add projects to the EPS and define the WBS for each project.
preferences for data in the
Project Management Project managers perform this step. They can further control
module. See “Defining
Administrative Preferences
security within their own projects by assigning specific OBS
and Categories in Project elements to WBS levels. Refer to the Project Management
Management” on page 357. Reference Manual for more information.
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.
Select a global
profile...
Edit Global Change Create, edit, and delete Global Change specifications
Definitions available to all users.
View Resource Role View, group/sort, filter, and report on resource and
Proficiency role proficiency. A user must have this privilege to
view and search by resource and role proficiency in
P6 Web Access.
Approve Resource Review, approve, and reject submitted timesheets as a
Timesheets Resource Manager in the Timesheet Approval
application.
Edit Cost Accounts Create, edit, and delete cost accounts.
Import Global Data for Import projects, resources, and roles from XER, MSP,
XER, MSP, XLS, and XLS, and P3 formats. A user must also have the
P3 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 XML Import projects from the Project Management module
XML and Microsoft Project XML format. A user
must also have the Create Project within EPS project
privilege to import and create new projects.
Edit Global Reports Create, edit, and delete global reports; edit report
groups and global report batches; and save global
reports created or modified by the Report Wizard.
Edit Global Tracking Create, edit, and delete global tracking layouts in the
Layouts Project Management module.
Edit Global Activity Edit the name of global activity codes in both P6 Web
Codes Access and the Project Management module. This
privilege automatically enables you to add, edit, and
delete global activity code values as well.
Add Global Activity Add new global activity codes and code values in both
Codes 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 Delete global activity codes and code values in both
Codes 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.
Edit Issue Forms Add, edit, and delete issue forms and issue form
categories in P6 Web Access.
Edit Global Calendars* Create, edit, and delete global calendars and shifts in
both P6 Web Access and the Project Management
module.
Edit Resource Create, edit, and delete resource calendars and shifts
Calendars* in both P6 Web Access and the Project Management
module.
Edit Security Profiles Create, edit, and delete global and project security
profiles.
Edit Users Add, edit, and remove Project Management module
users.
Add/Edit Global Create, edit, and delete global activity and resource
Activity and assignment layouts, views, and filters.
Assignment Layouts
and Filters
Edit OBS Create, edit, and delete global OBS hierarchy.
Edit Project Codes Edit the name of project codes. This privilege
automatically enables you to add, edit, and delete
project code values as well.
Add Project Codes Add new project codes and code values. This
privilege automatically enables you to edit existing
codes and code values as well.
Delete Project Codes Delete project codes and code values. This privilege
automatically enables you to add and edit project
codes and code values as well.
Edit Resource Codes Edit the name of resource codes. This privilege
automatically enables you to add,
edit, and delete resource code values as well.
Add Resource Codes Add new resource codes and code values. This
privilege automatically enables you to edit resource
codes and code values as well.
Delete Resource Codes Delete global resource codes and code values. This
privilege automatically enables you to add and edit
resource codes and code values as well.
Edit Global Portfolios Create, edit, and delete global portfolios in the Project
Management module and in P6 Web Access.
Administer Global Administer the list of global external applications.
External Applications
Edit Funding Sources Create, edit, and delete funding sources in the
Funding Sources Dictionary.
Run Project Architect 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 View all values for labor and nonlabor resource costs
Role 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 Job Administer the Job Services; set up the Apply
Services Actuals, Batch Reports, Export, Schedule, and
Summarize services to run at specific time intervals.
Edit Personal Resource Enables users to edit their own resource calendars if
Calendar 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.
Create Project Initiate predefined workflow processes for reviewing
Requests* new project requests. A separate privilege, Edit
Project Requests, is required to create the templates
that define the available workflow processes.
Edit Project Requests Create, edit, and modify templates that define
Templates* workflow processes for reviewing new project
requests.
Add and Delete Secure Create, edit, assign, view, and delete all global and
Codes EPS-level secure activity codes and values, as well as
all global secure issue codes and values.
Edit Secure Codes Edit, assign, and view global and EPS-level secure
activity codes and values, as well as all global secure
issue codes and values.
Assign Secure Codes Assign and view global and EPS-level secure activity
codes and values, as well as all global secure issue
codes and values.
View Secure Codes View global and EPS-level secure activity codes and
values, as well as all global secure issue codes and
values.
Edit User Interface Create, edit, and delete user interface views in P6 Web
Views 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.
View All Global/ Access the SDK in read only mode, without superuser
Project Data via SDK privileges.
Edit Global Resource Create, edit, and delete global Resource Teams and
and Role Teams Role Teams. A Resource/Role Team is a collection of
resources/roles. Resource/Role Teams are available in
P6 Web Access.
Edit Resource Curves Create, edit, and delete resource distribution curves.
Edit User Defined Create, edit, and delete user defined fields. Without
Fields* 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.
Add/Edit Global Create, edit, and delete global project and WBS
Project/WBS Layouts layouts. In P6 Web Access, create, edit, and delete
and Portfolio Views portfolio views. This privilege is required to save
view changes made to the Portfolios > Portfolio
Analysis page in P6 Web Access.
Edit Microsoft Project Create, edit, and delete Microsoft Project Templates
Templates used to import/export data from/to Microsoft Project.
Edit Activity Step Create, edit, and delete Activity Step Templates used
Templates to add a set of common steps to multiple activities.
Add Global Issue Create new issue codes and issue code values in P6
Codes Web Access.
Edit Global Issue Codes Edit issue codes and issue code values in P6 Web
Access.
Delete Global Issue Delete issue codes and issue code values in P6 Web
Codes Access. This privilege automatically enables you to
add and edit global issue codes and issue code values
as well.
Edit Financial Period Create, edit, and delete financial periods in the
Dates Financial Period dictionary. A user must also be
assigned the Edit Period Performance project
privilege to edit period data.
Edit Global Scenarios Create, edit, and delete global scenarios in P6 Web
Access.
Edit Global Dashboards Create, edit, and delete global dashboards in P6 Web
Access.
Edit Projects from Add, edit, and delete projects from scorecards in the
Scorecards Portfolio View portlet and the Portfolio Analysis page
in P6 Web Access. This privilege is required to save
data changes made to the Portfolio Analysis page.
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.
For more information on Project profiles are applied to users via OBS assignments. The Project
assigning users to OBS
Management module requires that all EPS and WBS elements, and
elements, see “Assigning
OBS Elements and Project projects, are assigned a responsible OBS. The combination of the
Profiles” on page 338. 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 within Create, copy, and paste projects within the EPS.
EPS
Delete Project within Delete, cut, and paste projects within the EPS.
EPS
Store Period Store actual this period values for actual units and
Performance costs in a project’s financial periods. A user must be
assigned the Add/Edit Project Activities Except
Relationships project privilege before you can assign
this privilege.
Edit Period Edit period performance values for labor and
Performance 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.
Maintain Project Add, save, and delete a project’s baselines. A user
Baselines must be assigned this privilege, and the Edit Project
Details Except Financials project privilege, to add a
project baseline in the Project Management module.
Run Baseline Update Update a project’s baselines with new project data
using the Update Baseline utility.
Assign Project Baseline 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.
Edit Project Work Create, edit, and delete a project's work products and
Products and documents. In P6 Web Access, relate items to
Documents documents, change a document's access level, add and
delete folders, and start project document reviews. In
addition to this privilege, the Content Repository must
be configured to change a document's access level,
add and delete folders, and start project document
reviews.
Add/Edit Project In P6 Web Access, create, edit, delete, check out, and
Template Documents start reviews for project template documents. A user
needs to have the privilege to 'Edit Project Work
Products and Documents' also. In addition to this
privilege, the Content Repository must be configured
to check out and start reviews for project template
documents.
View Project Costs/ View all monetary values for a project. If a user
Financials 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.
Edit Project Activity Modify a project’s activity codes in both P6 Web
Codes Access and the Project Management module.
Add Project Activity Create a project’s activity codes in both P6 Web
Codes Access and the Project Management module.
Delete Project Activity Remove a project’s activity codes from the project
Codes database in both P6 Web Access and the Project
Management module.
Edit EPS Activity Modify EPS-level activity codes in both P6 Web
Codes Access and the Project Management module.
Edit Project Reports Edit a project’s reports and edit a project’s report
batches.
Edit Project Calendars* Create, edit, and delete a project’s calendars in both
P6 Web Access and the Project Management module.
If your company’s OBS is At a minimum, each user requires a login name, global profile, and
established, and you know licensing information (component and access level). You can also
which OBS elements to provide additional information about the user, such as an e-mail address
associate with each user, and office phone number.
you can make the
assignments in the Project
Access tab in the Users If your organization centralizes user information in an LDAP
dialog box. See “Assigning directory, you can add Primavera users by provisioning from
OBS Elements and Project the LDAP store. For more information, see “Configuring
Profiles” on page 338. Authentication Modes” on page 277. After you provision
users, you will need to assign each user a security profile and
license.
If your company uses P6 Add new users Choose Admin, Users. Click Add.
Web Access, you might
want to create a default ■ If Password Policy is not enabled in Administrative Preferences,
prototype user before click the General tab, type the user’s login name and personal
adding new users. The name, then click Password. Type the user’s password, then retype
prototype user enables you
the password to verify it. Click OK. If the user will be accessing
to define default
dashboards and global
Timesheets, you can associate the user with a resource in the
preference settings that Project Management module at this time, or you can create the link
apply to all users of P6 when you add resources. Click the Contact tab and type the user’s
Web Access. See “Adding e-mail address and telephone number.
a prototype user and
■ If Password Policy is enable in Administrative Preferences, the Add
defining default settings for
User dialog box will appear. You will be required to fill in the Login
P6 Web Access” on
page 335 for more name, Personal name, Enter new password, and Confirm new
information. password fields. 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 user’s e-mail
address and telephone number.
For more information, see Assign a global profile A global profile determines a user’s access
“Defining Global Profiles”
to application-wide features, such as resources and roles. The Project
on page 309.
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
user’s global profile.
.
You can also double-click
in the Global Profile
column and choose the
appropriate profile for the
selected user.
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.
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 user’s 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.
• My Projects
• My Workgroups
• My Activities
Projects
In the Projects section of P6 Web Access, Team Member-licensed users
can access the Open Project dialog, the Manage Activity Views page,
the Project Workspace, and the Activities page.
The Activities page 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.
All other Project Workspace portlets are not available to Team Member-
licensed users.
Click Help on the Manage 6 From the Dashboards action menu in the global navigation bar,
Dashboards or Dashboard choose Manage Dashboards to create default global dashboards that
Preferences pages for will be displayed for each new P6 Web Access user. Be sure to
details on creating a select All Users as the access type on the Access tab of Dashboard
dashboard, choosing the Preferences to ensure that each dashboard you create is a global
portlets to display in a
dashboard.
dashboard, and specifying
user access.
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.
For more information on You can assign a user an OBS element and a corresponding project
project profiles, see
“Defining Project Profiles”
profile in the Users dialog box when you are adding users, or you can
on page 317. make the assignment in the OBS dialog box during or after creating the
OBS.
Double-click to select
another project profile. To
grant the user read-write
privileges for all aspects of a
project, select Project
Superuser.
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.
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.
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:
You can assign only one resource node to each user. Multiple
resource nodes are not supported.
Refer to the “Defining Implementing resource security Before you implement resource
Resources and Roles”
chapter in the Project
security, you must first set up your resource hierarchy in a manner that
Management Reference enables you to assign users to single resource nodes. For example, you
Manual for more can use resource security to restrict user’s access to resources who are
information on setting up
the resource hierarchy. 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:
Resource access settings 4 Set resource access for the selected user as follows:
are ignored for Admin
Superusers. Admin • To provide all resource access to the selected user, mark the All
Superusers always have all Resource Access checkbox.
resource access. • 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.
When creating user Creating user interface views is a useful way to enhance security and
interface views in P6 Web enable users to more easily access the functionality they use when
Access, provide a name for performing project work and managing projects. For example,
each user interface view executives may require access to some, but not all, project information.
that enables you to easily In this case, you can create a user interface view named 'Executive' that
identify the user interface
provides access to some or all Portfolios functionality, along with access
view’s associated
functionality.
to the Projects data executives require.
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 Menu item in the Dashboards
section.
In addition to customizing
the P6 Web Access
interface using user
interface views, you can
create a prototype user to
specify default
dashboards and global
preference settings.
Refer to “Adding a
prototype user and
defining default settings
for P6 Web Access” on
page 335.
This section discusses the process of creating security profiles and users
in the Methodology Management module.
Select a global
profile...
Edit Work Products and Create, delete, and change work product and
Documents document records.
Edit Reports Create, edit, and delete reports; save reports in the
Report Wizard.
Edit Activity Codes Create, change, and delete global activity codes and
values.
Edit Estimation Factors Create, change, and delete estimation factors.
Edit Global Activity Create, delete, and change global activity layouts and
Layouts and Filters filters.
Edit User Defined Create, edit, and delete user-defined fields. Users that
Fields do not have this privilege can view user-defined
fields.
Edit Microsoft Project Create, edit, and delete Microsoft Project Templates
Templates used to import/export data from/to Microsoft Project.
Edit Activity Step Create, edit, and delete Activity Step Templates used
Templates to add a set of common steps to multiple activities.
Double-click in the
Global Profile column
and choose the
appropriate profile for
the selected user.
The character
The first day of the week for that separates
global, project, and hierarchy
resource calendars levels in roles,
resource
codes, project
codes, cost
The default duration for new accounts, and
activities in all projects; activity codes;
simplifies the process of it is also the
adding new activities default
separator for
WBS codes in
all new
projects. You
The policy used for password can enter a
creation and changes. Mark WBS code
to enable a strong password separator for
policy. When unmarked, specific
projects in the
passwords can be from 0 to
Settings tab
20 characters and can be all of Project
letters or numbers. Details.
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.
The default
number of
days users
can review an
activity after it
ends
Specify resource
privileges for
entering hours in
timesheets.
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.
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.
Valid entries range from 1.0 to 168.0. Valid entries range from 1.0 to 744.0.
Type a one-character
abbreviation to use when
displaying the time units
and duration display
formats you select.
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 activity’s calendar. For example,
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.
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.
You can select whether users can access methodologies to add activities
or create new projects using Project Architect. To enable users to launch
Content Repository 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 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).
The time
Choose this option to enable interval to
users to view summary data which
and edit high-level planning resource/role
assignments in financial period assignment
timescale intervals in P6 Web cost and
Access, and to ensure quantities
accurate data display in should be
financial period timescale summarized.
intervals in the Project
Management module.
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.
For more information Baseline types Use the Baseline Types tab to create, edit, and delete
about baselines, see the
baseline types. Baseline types enable you to categorize and standardize
Project Management
Reference Manual. 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.
For more information Expense categories Use the Expense Categories tab to create, edit,
about expenses, see the
Project Management
and delete expense categories. Expense categories can be used to
Reference Manual. 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 WBS custom category Use the third tab on the Admin Categories
about the WBS, see the
dialog box to define a custom WBS category and category values. The
Project Management
Reference Manual. 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.
For more information Document status Use the Document Status tab to create, edit, and
about work products and
documents, see the Project
delete document status types. Status types identify the current status of
Management Reference work products and documents within a project. Use them to determine
Manual. 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 Overhead codes Use the Overhead Codes tab to create, edit, and
about the Timesheets
module, see the Project
delete overhead activity codes for Timesheets module users. Timesheets
Management Reference module users add overhead activities to their timesheets to log timesheet
Manual. 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 Risk types Use the Risk Types tab to create, edit, and delete risk
about risks, see the Project
types, or categories of possible risks. Risk types allow you to classify
Management Reference
Manual. 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 Notebook topics Use the Notebook Topics tab to create, edit, and
about activity notes, see
the Project Management
delete notebook topics. Notebook topics typically consist of instructions
Reference Manual. 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, double-click it, then type a new name. The
change applies to all notebook 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.
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 want to view costs in the old base currency, you will
need to add it to the list of available currencies.
Data limits Use the Data Limits tab to specify the maximum number
of levels for hierarchical structures.
The maximum
number of hierarchy
levels in these
structures: 1 is the
lowest, and 25 is the
highest.
The maximum number of
hierarchy levels in these
code types: 1 is the lowest,
and 25 is the highest.
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.
For more information Expense categories Use the Expense Categories tab to create, edit,
about expenses, see the
and delete expense categories. Expense categories can be used to
Methodology Management
Reference Manual. 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 Notebook topics Use the Notebook Topics tab to create, edit, and
about activity notes, see
the Methodology
delete notebook topics. A notebook typically consists of instructions or
Management Reference descriptions for performing an activity. You can also assign notebooks
Manual. 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 WBS custom category Use the third tab on the Admin Categories
about the WBS, see the
Methodology Management
dialog box to define a custom WBS category and category values. To
Reference Manual. 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.
Report groups Use the Report Groups tab to create, edit, and delete
report groups, which help you organize reports.
For more information Factor categories Use the Factor Categories tab to set up categories
about establishing
estimation data, see the
for organizing estimation factors in methodologies. These factors are
Methodology Management used in Project Architect to calculate a project size and complexity
Reference Manual. 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.
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.
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 want to view costs in the old base currency, you will
need to add it to the list of available currencies.
Implementing Timesheets
Project team members can use Timesheets to
In this chapter: submit timesheets that update their activities
in the Project Management module. This
Implementation Overview
chapter describes how to configure the
Setting Timesheet Preferences
Project Management module for use with
Configuring Resources to Use
Timesheets Timesheets, how to run Timesheets once it
Creating Timesheets for has been configured, and how to configure
Timesheets Users access to the Timesheet Approval application
Setting Project-Specific for timesheet approval managers.
Timesheets Preferences
Using Overhead Codes
Running Timesheets Web
Browser Version and Java Web
Start Version
Configure Access to Timesheet
Approval
396 Part 5: Primavera Application Administration
Implementation Overview
Timesheets enables project team members to use the web to
communicate timesheet and activity status directly to their
organization’s 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.
Before you implement Timesheets, first ensure that the following steps
have been completed:
■ Install the project management database, as described in “Database
Installation and Configuration” on page 27.
■ Install a Web server, if one is not already available.
■ Install the Group Server, as described in “Configuring the Group
Server for Timesheets” on page 97.
■ Install the Timesheets Java files on the Web server, as described in
“Installing the Group Server and Timesheets Web Site” on page 99.
■ 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 118.
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.
■ Configure resources to use Timesheets.
■ Create timesheets.
■ Set project-specific preferences for Timesheets.
■ Create overhead codes for recording nonproject hours.
The Timesheet Approval ■ Install and configure P6 Web Access as described in “Installing P6
application, when properly Web Access” on page 131.
configured, is accessible
from P6 Web Access, the ■ Specify timesheet approval requirements in Admin Preferences as
Project Management described in this chapter.
module, and as a stand-
■ Assign product licensing and the required security privileges to
alone application. Since P6
timesheet approval managers as described in “Administering Users
Web Access hosts the
Timesheet Approval and Security” on page 297.
application, you must ■ Configure access to Timesheet Approval as described in “Configure
install P6 Web Access Access to Timesheet Approval” on page 414.
regardless of how users
will access the application.
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. For more information, see the readme in the
\Tools\Actualizer folder of the P6 physical media or
download.
For information on The Timesheet Approval Level section contains the following options:
approving timesheets, see
the “Updating, Scheduling, ■ Auto Submission Choose to indicate that resource timesheets do
and Leveling” chapter in
not need to be submitted or approved. Timesheet data are
the Project Management
Reference Manual. 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 timesheet’s
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.
For more information on The Timesheet license provides access to the Timesheets application
the functionality
and enables the user to log into P6 Web Access to import appointments
associated with licenses,
refer to “Assign product only (provided that this functionality is configured for the user). The
licensing” on page 327. 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.
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 resource’s standard
price is multiplied to determine the overtime price (standard price *
overtime factor = overtime price).
To create another set of timesheets, reset the batch start and end dates,
select the appropriate timesheet period, then click Batch Create.
You cannot create new timesheets that have start and end
dates that overlap existing timesheet dates.
Mark to allow
resources to view
activities that belong
to inactive projects,
to report activities or
assignments as
completed, and to
choose which
activities they should Choose whether resources indicate
begin next. progress on activities by entering
percentages or units of time remaining.
Run Timesheets
1 To 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.
If the Web Server is not using the default port, you must enter
the port number after the IP address separated by a
semicolon (:).
You will only be prompted to download the Java files the first
time you click the Run Timesheets link.
For new user interface views you create, and for organizations that do
not utilize user interface views, the Approve Timesheets Action Menu
item appears by default; if a user does not have rights to access
Timesheet Approval, the menu item will not appear, even if you include
it in the user's assigned user interface view.
For users upgrading to P6.1 and later, the Approve Timesheets Action
Menu item appears for users who had rights to approve timesheets in
previous releases.
For more information on In P6 Web Access, for the range of defined financial periods, users can
displaying a financial
period timescale in P6 Web
display summary project data in financial period timescale intervals in
Access, refer to the P6 Web charts and spreadsheets, as well as edit high-level planning assignments
Access Help. in financial period intervals.
Choose the
timescale for each
financial period in
the batch, along
with the day of the
week you want the
periods to end on.
Click to generate the batch of
financial periods.
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).
Process Overview
The following steps outline the process for running the PMDB and
MMDB databases in one Oracle instance.
At the end of the process, your database should look like the following:
For PMDB
admuser pmdb_dat1
privuser pmdb_dat1
pubuser pmdb_dat1
For MMDB
admuser1 mmdb_dat1
privuser1 mmdb_dat1
pubuser1 mmdb_dat1
2 On the Finish dialog box, click Next to run the Database wizard
again for the Methodology Management module. Use the
instructions below to continue.
• In the DBA User Name 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 Database Host Address field, enter the server machine
name or IP address where Oracle is installed.
• In the Database Host Port field, enter the port number that
Oracle is using. The default is 1521.
• In the Database Name (SID) field, enter the Oracle SID used
for MMDB. It can be found in the TNSNAMES.ORA file,
which was created when you or your DBA set up the Oracle
client.
4 On the Configure Oracle Tablespaces dialog box, click Next to
accept the name for the Data, Index, and LOB tablespaces and
estimated tablespace sizes.
You can change the estimated tablespace sizes. Refer to
“Methodology Management Database Server Sizing Guide” on
page 24 for guidelines on sizing.
Mark Use existing tablespaces only if the database server to which
you are connecting already has existing tablespaces. For a new
database server, do not mark this option.
5 On the Specify Oracle Tablespace Locations dialog box, accept
the default locations for the Oracle tablespaces (Data, Index, and
LOB), or specify different locations.
Clicking Create on this step will begin the initial setup of the
methodology management database. After this step, you will
no longer be able to click Previous to change your prior
selections. On the next step, however, you will have the
option to either click Next or Cancel.
1 Enter MMDB as the database alias and select Oracle as the driver
type.
Once you complete these steps, you will be able to run the Methodology
Management and Project Management modules using the aliases you
established, while still connecting to the same database.
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 Customer Support 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.
• In the Product Key field, enter the product code that was
provided via e-mail or as listed on the License CD label.
4 On the Ready to Begin Upgrading Data dialog box, verify that the
the current version of your existing database is listed correctly.
Choose Yes, upgrade my database, then click Upgrade.
The upgrade process could take several minutes, depending on its
size.
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 projects
■ Opening and closing projects
■ Summarizing data
■ Updating progress
■ Applying Actuals
■ Refreshing data
■ Importing
■ Auto scheduling
■ Logging in as a different user
■ Changing portfolios
For more information on Undo an action Choose Edit, Undo. The latest action stored for undo
using the Undo feature, see
the Project Management
will display next to the Undo command. For example, if you add a
module Help. 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.
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.
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'
Index
A Base currency, setting 35, 61, 427
Activities for SQL database 39
notebook topics 376, 386 Baselines
Additional components, installing 227 types 371
Administer database settings 63
Administration 357–376 C
Administrative Categories
categories 371 document 373, 388
preferences 358 estimation factors 389
Administrative categories, defining 381 expense 372, 386
Administrative preferences, defining 381 notebook 376
API xi, 6, 15, 18, 242 risk 375
Application data units of measure 376, 390
loading for Oracle 32 WBS 387
loading for SQL Server 37 work products 373
auditing Check in projects 320
detailed configuration 89 Check out projects 320
overview 87 Client modules
simple configuration 88 changing user passwords 272
Authentication installing 233
configure for P6 Web Access 172 minimum requirements 18
configuring 277–293 Codes
LDAP 110 maximum number of characters for,
login procedures 293 specifying 363
Native 278 overhead 374
Single Sign On 112 separator 358, 382
Authentication Configuration wizard 281 Collaboration
Automatic database install 29 overview
for Oracle 32 See Content Repository
for SQL Server or SQL Server Express database See Workflows Repository
automatic install 37
CONFIGASST.EXE
See dbsetup
B Content Repository
background processing installing 141
monitoring 70 overview 6
reading writing setting values 68 Contract Manager
settings table 67 connection to 369
446 Index
U
Unattended setup
creating file set 262
planning issues 14
running 266
Undo, using 442
Uninstalling
Job Services 5.x versions 229
the Group Server 98
Units of Measure
categories 390
Upgrading