Professional Documents
Culture Documents
Primavera P6 Admin Guide
Primavera P6 Admin Guide
Administrators Guide
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE
SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
*****
Copyright 1994-2006 Sun Microsystems, Inc. All Rights Reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistribution of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE
LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR
DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT,
SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND
REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO
USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
You acknowledge that this software is not designed, licensed or intended for use in the design, construction,
operation or maintenance of any nuclear facility.
*****
Portions copyright (c) Macromedia, Inc. All rights reserved.
*****
Copyright (c) 2002-2006 JGoodies Karsten Lentzsch. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
*****
Printed in the United States of America
vii
Table of Contents
Preface............................................................................................... xiii
Using the Administrators Guide....................................................................... xiv
Primavera Documentation ................................................................................. xvi
Where to Get Support ...................................................................................... xviii
viii
Table of Contents
Table of Contents
ix
Table of Contents
Table of Contents
xi
Index..................................................................................................571
Preface
xiii
Preface
In this preface
Using the Administrators Guide
Primavera Documentation
Where to Get Support
xiv
Preface
Preface
xv
Set up authentication
xvi
Preface
Primavera Documentation
Primavera documentation consists of printed and online manuals. You can
access online documentation by inserting the Primavera Documentation
CD (CD 3) in your workstations CD drive. In the \Documentation folder
on the CD-ROM, open the appropriate industry-specific documentation
folder, then double-click the applicable PDF file to view the information
using Adobe Acrobat Reader (available on CD 3). The following table
describes each manual and lists the recommended readers by role.
Primavera roles are described in Installation Process Overview on
page 3 of this manual.
Title
Description
Primavera Administrators
Guide
This guide explains how to set up the Primavera server, database, and components;
it also provides an overview of all the components in the Primavera solution. The
guide describes the workflow required to administer the Project Management
module, including setting up security and configuring global preferences. The
Project Management module network administrator/database administrator and
project controls coordinator should read this guide.
This guide explains how to plan, set up, and manage projects in a multiuser
environment. 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
Reference Manual
Primaveras Web Application Help describes how to create and manage projects,
group projects into portfolios, review resource allocation and requirements, and
evaluate budget, performance and ROI for project portfolios. The operations
executive, project controls coordinator, program manager, project manager,
resource/cost manager, and team leader should read this Help.
Timesheets Web-based Help describes how to use Timesheets to enter and update
time spent on assignments. Team members should read this Help.
Preface
xvii
Software Development Kit (SDK) This documentation describes how to use the SDK to connect to the project
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.
ProjectLink Help
xviii
Preface
Office
Telephone
FAX
E-mail Address*
Bala Cynwyd, ET
Pennsylvania,
USA
8:008:00
(MonFri)
9:002:00
(Sat)
+1-610-668-3030
+1-610-667-0652
support@primavera.com
London,
England, UK
GMT
8:306:30
(MonThur)
8:305:30
(Fri)
+44-20-8563-5555
+44-20-8563-5543
support@primavera.com
Hong Kong
GMT +8
8:005:00
(MonFri)
+852-2111-8299
+852-2111-9477
support@primavera.com
Part
Collaboration
Server
Browser Client
Primaveras Web
Application Server
Timesheets
Server
Job Services
Server(s)
Projects
Portfolios
Methodologies
Documents
You are not required to install the server-based components as shown here.
For example, Primaveras Web application and the collaboration server
can be installed on the same server (if necessary), and Job Services can run
on any computer with a constant connection to the project database.
10
11
12
13
14
15
Project Management
Methodology
Management
Timesheets
1
2
3
Primavera
Job Service
16
Supported Platforms
for Primavera
17
Ubuntu Linux7.0.4
Optional software:
Optional software:
18
Supported
Configurations for
Servers
Oracle 10.2.0.2 or higher on Windows 2003 Server (SP1 or SP2), HPUX 11i v2, Solaris 10 (SPARC), or RedHat Linux Enterprise 4.0
Job Service must run on Windows 2000 Server (SP4) or Windows 2003
Server (SP1).
19
The Oracle OLE DB driver compatible with your Oracle version. For
Oracle 9i, the minimum supported version of the OLE DB driver is
9.2.0.7.
The SQL Server client driver compatible with your SQL version
Solaris 9 (SPARC)
Solaris 10 (SPARC)
HP-UX11i v2
20
JBoss 4.0.4
Supported E-Mail
Systems and Network
Protocols
21
Small
Medium
Large
Temp TBS
300 MB
500 MB
1,000 MB
RBS TBS
300 MB
500 MB
1,000 MB
Index TBS
250 MB
500 MB
1,000 MB
Data TBS
250 MB
500 MB
1,000 MB
Lob TBS
250 MB
500 MB
1,000 MB
1,350 MB
2,500 MB
5,000 MB
384 MB
512 MB
1024+MB
Total
RAM:
Small
Medium
Large
Data
300 MB
500 MB
1,000 MB
Data Log
150 MB
250 MB
500 MB
Temp
100 MB
200 MB
275 MB
50 MB
100 MB
125 MB
Total
600 MB
1,050 MB
1,900 MB
RAM:
384 MB
512 MB
1024+MB
Temp Log
22
Recommended
Size
Index TBS
250 MB
Data TBS
250 MB
Lob TBS
250 MB
Total
750 MB
Recommended
Size
Data
300 MB
Data Log
150 MB
Total
450 MB
23
Practical Limit
100
100
100,000
100,000
Part
27
28
Overview
Two databases are used to run Primavera:
29
30
In the Key field, enter the product key located on the CD 1 label.
31
The base currency is the monetary unit used to store cost data for all
projects in the database and is controlled by a global administrative setting
in the Project Management module. The default base currency for
Primavera is US dollars ($). The view currency is the monetary unit used
to display cost data in Primavera and is controlled by a user preference.
The exchange rate for the base currency is always 1.0. When a user selects
a different currency than the base currency to view cost data, the base
currency value is multiplied times the current exchange rate for the view
currency to calculate the values displayed in cost and price fields.
For example, if the base currency is U.S. Dollars, the view currency is
Euros, and the exchange rate for Euros is .75, a value of $10 stored in the
database is displayed as 7.5 Euros in cost and price fields. Similarly, if you
enter 7.5 Euros in a cost or price field, it is stored in the database as $10.
When data is displayed in a view currency that is different than the base
currency, some cost and price values may vary slightly (e.g., due to
rounding). As long as the correct base currency is selected during database
installation, a user can view completely accurate cost and price data by
changing the view currency to match the base currency.
6 On the Select Application Database dialog box, choose the database
for which you are installing data.
32
If you choose to load the license key file now, browse to the
location of the LICENSE.TXT file. If the LICENSE.TXT file is
not available at this time, you can clear this checkbox and load the
file later using the Database wizard. Refer to Changing Database
Configuration Settings on page 299 for more information.
In the DBA Username field, type the Oracle system user name to
log on to the database; for example, system (which is the default).
33
11 On the Configure Oracle Users dialog box, accept the default names
for the Oracle administrative user, privileged user, and public user, or
specify the appropriate names. If necessary, choose a different default
tablespace and temporary tablespace from the dropdown list.
You cannot enter PRIVUSER as the administrative username;
doing so will cause conflicts.
You can choose a default tablespace from the dropdown list in the
Default Tablespace field. In the Temporary Tablespace field, use the
temporary tablespace that you created prior to starting this procedure.
The temporary tablespace must be of temporary type;
otherwise, errors can occur to your database.
13 On the Load Application Data dialog box, click Next to start the
process of loading the database tables with application data.
When the process has completed, the message Data Loading
Completed appears. Click Finish to exit the wizard.
14 If prompted, run the RUN_AS_SYS.SQL and GATHER_STATS.SQL
scripts. If you are not prompted, you can access these scripts in the
\install\database folder on CD 1.
34
15 Run the Database wizard again if you will be using the Methodology
Management module.
Once both sets of application data are installed (Project Management and
Methodology Management), you can begin to install client modules and
additional components. Refer to Part 3 and Part 4 for more information on
configuring the servers and installing client module(s) and additional
components.
35
In the Key field, enter the product key located on the CD 1 label.
36
The base currency is the monetary unit used to store cost data for all
projects in the database and is controlled by a global administrative setting
in the Project Management module. The default base currency for
Primavera is US dollars ($). The view currency is the monetary unit used
to display cost data in Primavera and is controlled by a user preference.
The exchange rate for the base currency is always 1.0. When a user selects
a different currency than the base currency to view cost data, the base
currency value is multiplied times the current exchange rate for the view
currency to calculate the values displayed in cost and price fields.
For example, if the base currency is U.S. Dollars, the view currency is
Euros, and the exchange rate for Euros is .75, a value of $10 stored in the
database is displayed as 7.5 Euros in cost and price fields. Similarly, if you
enter 7.5 Euros in a cost or price field, it is stored in the database as $10.
When data is displayed in a view currency that is different than the base
currency, some cost and price values may vary slightly (e.g., due to
rounding). As long as the correct base currency is selected during database
installation, a user can view completely accurate cost and price data by
changing the view currency to match the base currency.
6 On the Select Application database dialog box, choose the database
for which you are installing data.
37
In the System Admin Name field, type the Microsoft SQL Server
system administrator name to register to the server. If you chose
the defaults during the Microsoft SQL Server installation, accept
SA as the system administrator name.
In the System Admin Password field, type the password for this
system administrator. If you chose the defaults during the
Microsoft SQL Server installation, accept a blank password.
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.
38
11 On the Load Application Data dialog box, click Next to start the
process of loading the database tables with application data.
When the process has completed, the message Data Loading
Completed appears. Click Finish to exit the wizard.
12 Run the Database wizard again if you will be using the Methodology
Management module.
Once both sets of application data are installed (project management and
methodology management), you can begin to install client modules and
additional components. Refer to Part 3 and Part 4 for more information on
configuring the servers and installing client module(s) and additional
components. For information on configuring database settings to optimize
performance, refer to Database Administration on page 57.
39
40
Overview
Two databases are used to run Primavera:
41
These instructions assume you are an Oracle DBA or are familiar with
administering Oracle databases.
Create the PMDB Oracle database structures
1 Copy the ORPM_INS.SQL script to a local folder.
The script is located on CD 1 in the \install\database\scripts\install\or
folder. You must copy the script to a local drive so it can be edited.
2 Turn off the files read-only attribute.
Since files on a CD are read-only, this attribute is turned on when a
file is copied from a CD. In Windows Explorer, right-click the file,
choose Properties, and clear the Read-Only checkbox.
3 Edit the ORPM_INS.SQL script.
Follow the instructions in the header of this script to modify all
parameters with double question marks (??parameter??).
42
Once the database structures are created, you can install the application
data in the PMDB database as described in Installing the Application
Data (Oracle and Microsoft SQL Server) on page 53.
43
ORDP_SYN.SQL
drops synonyms
ORDP_GRN.SQL
revokes privileges
ORDP_FKC.SQL
ORDP_PK.SQL
ORDP_NDX.SQL
drops indexes
ORDP_TAB.SQL
drops tables
If data exists, you must drop the objects in the order they are listed. The
results of each script are spooled to a file with an .LST extension.
For example, ORDP_TAB.LST contains the results of the SQL script of
that name.
44
Once the database structures are created, you can install the application
data in the MMDB database as described in Installing the Application
Data (Oracle and Microsoft SQL Server) on page 53.
45
ORDP_SYN.SQL
drops synonyms
ORDP_GRN.SQL
revokes privileges
ORDP_FKC.SQL
ORDP_PK.SQL
ORDP_NDX.SQL
drops indexes
ORDP_TAB.SQL
drops tables
If data exists, you must drop the objects in the order they are listed. The
results of each script are spooled to a file with an .LST extension. For
example, ORDM_TAB.LST contains the results of the SQL script of that
name.
46
After configuring the server, stop and start Microsoft SQL Server to
ensure that the changes take effect.
47
Configuring for International Language Support (SQL Server 2000 and 2005)
For non-Latin language support (Traditional Chinese, Simplified Chinese,
Russian, or Japanese), the Group Server requires specific settings when
configuring the database. In the database setup, choose the codepage and
collation options that coincide with your installation when prompted.
Create the PMDB Microsoft SQL Server database structures
1 Copy the SSPM_DB.SQL, SSPM_LOGIN.SQL, SSPM_USER,SQL,
and SSPM_INS.SQL, SSscripts to a local folder.
These scripts are located on CD 1 in the
\install\database\scripts\install\ss folder. You must copy the scripts to
a local drive so they can be edited.
2 Turn off the files read-only attribute.
Since files on a CD are read-only, this attribute is turned on when a
file is copied from a CD. In Windows Explorer, right-click the file,
choose Properties, and clear the Read-Only checkbox.
3 Edit each of the scripts you copied in Step 1.
Follow the instructions in the header of each script for what to
replace.
Primavera Systems recommends that you use Microsoft SQL
Server Enterprise Manager to perform these steps.
48
49
SSDP_SYN.SQL
drops synonyms
SSDP_FKC.SQL
SSDP_PK.SQL
SSDP_NDX.SQL
drops indexes
SSDP_TAB.SQL
drops tables
You must connect to the server as SA to drop objects. Before running each
script, copy the scripts to a local drive, turn off the read-only attribute of
each file, and edit each script to replace the ??DATABASE_NAME??
parameter in the USE statement with the name of your database (for
example, PMDB). If data exists, you must run the scripts in the order
listed.
50
51
Once the database structures are created, you can install the application
data in the MMDB database as described in Installing the Application
Data (Oracle and Microsoft SQL Server) on page 53.
52
SSDP_SYN.SQL
drops synonyms
SSDP_FKC.SQL
SSDP_NDX.SQL
drops indexes
SSDP_PK.SQL
SSDP_TAB.SQL
drops tables
You must connect to the server as SA to drop objects. Before running each
script, copy the scripts to a local drive, turn off the read-only attribute of
each file, and edit each script to replace the ??DATABASE_NAME??
parameter in the USE statement with the name of your database (for
example, PMDB). If data exists, you must run the scripts in the order
listed.
53
In the Key field, enter the product key located on the CD 1 label.
54
The base currency is the monetary unit used to store cost data for all
projects in the database and is controlled by a global administrative setting
in the Project Management module. The default base currency for
Primavera is US dollars ($). The view currency is the monetary unit used
to display cost data in Primavera and is controlled by a user preference.
The exchange rate for the base currency is always 1.0. When a user selects
a different currency than the base currency to view cost data, the base
currency value is multiplied times the current exchange rate for the view
currency to calculate the values displayed in cost and price fields.
For example, if the base currency is U.S. Dollars, the view currency is
Euros, and the exchange rate for Euros is .75, a value of $10 stored in the
database is displayed as 7.5 Euros in cost and price fields. Similarly, if you
enter 7.5 Euros in a cost or price field, it is stored in the database as $10.
When data is displayed in a view currency that is different than the base
currency, some cost and price values may vary slightly (e.g., due to
rounding). As long as the correct base currency is selected during database
installation, a user can view completely accurate cost and price data by
changing the view currency to match the base currency.
6 On the Select Application Database dialog box, choose the database
for which you are installing data.
55
If you choose to load the license key file now, browse to the
location of the LICENSE.TXT file. If you do not have the
LICENSE.TXT file available to you at this time, you can clear this
checkbox and load the file later using the Database Configuration
wizard. See Changing Database Configuration Settings on
page 299 for more information.
8 On the Load Application Data dialog box, click Next to load the
database.
Before clicking Next, the database structure must already exist, or the
application data will not be installed.
9 On the Log on as Privileged User dialog box:
If you are connecting to SQL Server, you must specify the appropriate names in the Server Name field and the Database Name
field.
If you are running the Database Installation wizard from the server
machine, the wizard automatically enters the server name for you.
56
After you click Next, the process of clearing the database tables (if
they already exist) and loading them with data starts.
When the data is loaded, the message Data Loading Completed
appears.
11 Click Finish to close the Database Configuration wizard.
Once both sets of application data are installed, you can begin installing
other Primavera components and client modules.
Database Administration
57
Database Administration
In this chapter
Background Processes and
Cleanup in Version 6.0
Configuring the RDBMS
Scheduler
Setting Table
58
Both of these jobs are pre-configured with default settings. Since the
default settings are optimal for most environments, you generally do not
need to tune them. However, if further optimization is required, you can
change the settings to tune the behavior of the background jobs for specific
environments.
RDBMS Scheduler Since the background jobs are initiated by the job
scheduler supplied by the RDBMS, you need to ensure that the scheduler
for your specific RDBMS is properly configured. See Configuring the
RDBMS Scheduler on page 59 for the configuration parameters for your
RDBMS.
Database Administration
59
60
Database Administration
61
Setting Table
Settings Table Overview
The settings table contains name-value pairs that configure the behavior of
the background processes.
Setting Name The setting name comprises two components: the
namespace and the setting name. The namespace component is a dotnotation string representing a formal path to the parameter. The second
component identities the name of the setting. Together these two
components make up the full setting name.
Value Values in the SETTINGS table are case-sensitive. The value
portion of the pair can be one of the following types:
String. The string data type is a free text value. The most common
string sub-type is interval which represents an interval of time by
combining a numeric portion with a unit portion as depicted in the
table below.
Interval Subtype
Numeric portion
Unit portion
Example
Meaning
30d
2h
10m
30s
Boolean. The boolean data type can have one of two values: true or
false, where zero represents false and any non-zero number represents
true.
Date.
Namespace: database.cleanup.Usession
62
By way of example, the following code snippets for the Oracle and SQL
server databases demonstrate how these procedures are used to read the
setting values:
Oracle Example: To retrieve the value of the KeepInterval setting in
Oracle, use the following code:
SQL> variable vset varchar2(255)
SQL> exec settings_read_string(:vset,' database.cleanup.Usession' ,
' ExpiredSessionTimeout' );
Database Administration
63
The following code snippets for Oracle and SQL server databases
demonstrate how this procedure is used to set the value of the
ExpiredSessionTimeout setting to twelve hours:
Oracle Example: To set the value of the ExpiredSessionTimout setting
to twelve hours in an Oracle database, use the following procedure:
1 Log into SQL *Plus using PRIVUSER as your user name,
2 Run the following statement:
SQL > exec SETTINGS_WRITE_STRING
(' 12h' ,' database.cleanup.Usession' ,' ExpiredSessionTimeout' );
64
database.background.Symon
Setting Name
HeartBeatTime
Default Setting
N/A
database.background.Damon
Setting Name
HeartBeatTime
Default Setting
N/A
Database Administration
65
Inspecting the BGPLOG Table You can also track the execution of
background jobs by inspecting BGPLOG table. The BGPLOG table holds
detailed entries from the background processes including informational,
elapsed time, and error entries. Refer to the BGPLOG Table Descriptions
for information about what this table contains.
Description
Value
Log_time
Datetime
Source
system_monitor,
data_monitor
Type
Type of message
INFORMATION,
ELAPSED TIME, ERROR
Description
66
Database Administration
67
USESSION_CLEANUP_EXPIRED Settings
Setting Description: Time-out period for normal sessions.
Namespace
database.cleanup.Usession
Setting Name
ExpiredSessionTimeout
Default Setting
2h
Type
Interval
Setting Description: Time-out period for long running sessions based on the
function preformed in the application (i.e. Scheduling, Leveling, Summarizing,
etc.).
Namespace
database.cleanup.Usession
Setting Name
ExpiredLongSessionTimeout
Default Setting
12h
Type
Interval
68
Database Administration
69
BGPLOG_CLEANUP Settings
Setting Description: The oldest records to keep in the BGPLOG table.
Namespace
database.cleanup.BackGroundProcessLog
Setting Name
KeepInterval
Default Setting
5d
Type
Interval
70
REFRDEL_CLEANUP Settings
Setting Description: The oldest records to keep in the REFRDEL table.
Namespace
database.cleanup.Refrdel
Setting Name
KeepInterval
Default Setting
5d
Type
Interval
Setting Description: Determines whether the procedure will delete all of the
REFRDEL records possible on each pass.
Namespace
database.cleanup.Refrdel
Setting Name
DeleteAll
Default Setting
0 (false)
Type
Boolean
Database Administration
71
REFRDEL_CLEANUP Settings
Setting Description: Determines whether all of the records are cleaned up.
If the total record count is less than this number then all the records are cleanup
up.
Namespace
database.cleanup.Refrdel
Setting Name
DeleteAllThreshold
Default Setting
1,000
Type
Numeric
database.cleanup.Refrdel
Setting Name
DeletePercentage
Default Setting
10 (%)
Type
Numeric
database.cleanup.Refrdel
Setting Name
MaxRowsToDelete
Default Setting
10,000
Type
Numeric
72
OBSPROJ_PROCESS_QUEUE Settings
Setting Description: Maximum project-level queue records to process on
each run.
Namespace
database.obsproj.queue
Setting Name
MaxProjectUpdates
Default Setting
1000
Type
Numeric
Namespace
database.obsproj.queue
Setting Name
MaxEpsUpdate
Default Setting
25
Type
Numeric
Namespace
database.obsproj.queue
Setting Name
MaxRetries
Default Setting
50
Type
Numeric
Database Administration
73
CLEANUP_PRMQUEUE Settings
Setting Description: The oldest records to keep in the PRMQUEUE table.
Default is five days.
Namespace
database.cleanup.Prmqueue
Setting Name
KeepInterval
Default Setting
5d
Type
Interval
Setting Description: Determines whether the procedure will delete all of the
PRMQUEUE records possible on each pass.
Namespace
database.cleanup.Prmqueue
Setting Name
DeleteAll
Default Setting
0 (false)
Type
Boolean
Setting Description: Determines whether all of the records are cleaned up.
If the total record count is less than this number then all the records are cleanup
up.
Namespace
database.cleanup.Prmqueue
Setting Name
DeleteAllThreshold
Default Setting
1,000
Type
Numeric
74
CLEANUP_PRMQUEUE Settings
Setting Description: Percentage of records to delete on each pass.
Namespace
database.cleanup.Prmqueue
Setting Name
DeletePercentage
Default Setting
10(%)
Type
Numeric
database.cleanup.Prmqueue
Setting Name
MaxRowsToDelete
Default Setting
10,000
Type
Numeric
Database Administration
75
Refer to the following table for information about the settings associated
with the CLEANUP_LOGICAL_DELETES procedure:
CLEANUP_LOGICAL_DELETES Settings
Setting Description: The oldest logically deleted records to keep in tables.
Namespace
database.cleanup.LogicalDelete
Setting Name
KeepInterval
Default Setting
5d
Type
Interval
Setting Description: Determines whether the procedure will delete all of the
logically deleted records possible on each pass.
Namespace
database.cleanup.LogicalDelete
Setting Name
DeleteAll
Default Setting
0 (false)
Type
Boolean
76
CLEANUP_LOGICAL_DELETES Settings
Setting Description: Maximum rows to delete on each pass.
Namespace
database.cleanup.LogicalDelete
Setting Name
MaxRowsToDelete
Default Setting
10,000
Type
Numeric
Database Administration
77
PRMAUDIT_CLEANUP Settings
Setting Description: Should the procedure attempt to clean up PRMAUDIT
records.
Namespace
database.cleanup.auditing
Setting Name
Enabled
Default Setting
1 (true)
Type
Boolean
database.cleanup.auditing
Setting Name
KeepInterval
Default Setting
30d
Type
Interval
78
CLEANUP_USESSAUD Settings
Setting Description: The oldest records to keep in the USESSAUD table.
Namespace
database.cleanup.Usessaud
Setting Name
KeepInterval
Default Setting
5d
Type
Interval
database.cleanup.Usessaud
Setting Name
DeleteAll
Default Setting
0 (false)
Type
Boolean
Setting Description: Determines whether all of the records are cleaned up.
If the total record count is less than this number then all records are cleanup up.
Namespace
database.cleanup.Usessaud
Setting Name
DeleteAllThreshold
Default Setting
1,000
Type
Numeric
Database Administration
79
CLEANUP_USESSAUD Settings
Setting Description: Percentage of records to delete on each pass.
Namespace
database.cleanup.Usessaud
Setting Name
DeletePercentage
Default Setting
10 (%)
Type
Numeric
database.cleanup.Usessaud
Setting Name
MaxRowsToDelete
Default Setting
10,000
Type
Numeric
80
Database Administration
81
Auditing Levels
Level
Description
Level 0
No audit.
Level 1
Level 2
Level 3
82
Simple Configuration
There are two configuration procedures available that provide for the
simple control of the auditing feature:
auditing_enable(<table_name>, <level>)
auditing_disable(<table_name>)
These procedures allow for setting the audit level on an individual table or
the same audit level for all of the tables. However, the simple
configuration procedures do not allow for setting individual auditing levels
for insert, update, or delete operations within a table.
Examples for Oracle: Use the following examples as a guide to using
the simple audit configuration procedures to control the auditing feature.
The following code snippet enables full auditing on all tables:
exec auditing_enable(null,3);
The following code snippet enables level one auditing on the task table:
exec auditing_enable(' TASK' ,1);
The following code snippet completely disables auditing across the entire
database:
exec auditing_disable(null);
Database Administration
83
Detailed Configuration
You can configure auditing trigger behavior by changing values in the
settings table that enable or disable the following auditing features:
Turning Auditing Off and On You can enable or disable the auditing
feature itself by using the database.audit.Enable setting. Use the
settings_write_bool procedure to enable/disable the overall auditing
feature.
Oracle Example: To enable the overall auditing feature in Oracle, use
the following code:
exec settings_write_bool(1,' database_audit' ,' Enable' );
84
Update
Delete
Description
No audit.
Level
The following table provides some example uses of the options setting:
Setting
Value
Description
330
database.audit.PROJWBS
001
Row-level audit on
deletes only.
database.audit.TASKRSRC
333
Fully audit.
database.audit.TASK
Options
Database Administration
85
SQL Server Example: To set the table settings to fully audit insert and
update operations but ignore any delete operations, use the following code
for SQL Server:
exec setting_write_string ' 330' ,' database.audit.TASK' ,' Options'
Note: Changes to auditing settings will not necessarily be
reflected immediately in the application. In general the program
will need to close the database connection and then reconnect
to the database to get the new settings.
86
PRMAUDIT Table
Column
Type
Description
audit_date
Date
table_name
String(30)
Table Name
String(255)
oper
String(1)
prm_user_name
String(32)
audit_info
String(4000)
audit_info_extended
BLOB
logical_delete_flag
String(1)
rdbms_user_name*
String(255)
os_user_name*
String(255)
program*
String(255)
host_name*
String(255)
app_name*
String(25)
netaddress*
String(24)
Database Administration
87
Session Auditing
Activity for the USESSION table is audited with its own trigger and table.
When an application user logs out of the system they logically delete, or
mark, their session record in the USESSION table. One record is written
to the USESSAUD table for each logout. The format of the USESSAUD
table mirrors that of the USESSION table. This audit can be enabled using
the usessaud_enable procedure and disabled using the usessaud_disable
procedure.
Column-level Audit Data
The data changes for each audit are stored in the audit_info and
audit_info_extended columns. The audit_info column contains all the row
changes as long as they do not exceed 4000 characters. Changes over 4000
characters or any edit to a blob will be written to the audit_info_extended
BLOB column.
Data in the two audit_info columns has a specific format. Each column
audit within the data begins with either ":O" (old data) or ":N" (new data)
to distinguish between the audit of the previous (old) or the changed (new)
value (for BLOB columns the data starts with :BLOBO or :BLOBN).
Directly after this is the name of the column in lowercase. Following the
column name is the length of the audited value in a fixed four character
field. Finally the actual data is placed in the audit record. Updates will
have both an old and new value for each change. Inserts will have only a
new value and deletes only an old value.
The following is an example of the audit record for a change to the TASK
to change the task_code from 'A1010' to 'B102:'
audit_info =>:Otask_code: 5:A1010:Ntask_code: 4:B102
Part
91
92
93
Java Web Start Java Web Start provides a secure and platformindependent deployment of Timesheets using Java Network Launching
Protocol (JNLP) technology. Java Web Start also ensures that users always
launch the most recent version of Timesheets under the correct client-side
JRE version, even if there is more than one JRE version present.
Supported operating systems for Java Web Start:
Windows XP
Windows Vista
Red Hat Linux
Supported Web servers for Java Web Start:
Microsoft IIS
Apache
Client requirements for Java Web Start:
JRE
Internet Explorer or Firefox
94
Before performing these steps, you must have already set up the central
project management database.
95
4 On the Enter Product Key screen, enter the product key located on
the CD 1 label.
5 On the Welcome! dialog box, click Next.
6 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.
7 On the Choose Language dialog box, choose to install Timesheets in
any of the languages listed.
8 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.
If installing to Sun ONE Web Server, you must edit the
config\mime.types file to support the Primavera Timesheets
JRE auto-installation feature. See Support JRE autoinstallation on Sun ONE Web Server on page 102.
9 On the Help URLs dialog box, specify the location of the Timesheets
Help web site.
You can change the web site values later by manually editing
the proper files. For the Java Web Start version of Timesheets,
edit the timesheet.jnlp file in the \GroupServer\App folder. For
the applet version, edit the erps8x6.html in the
\GroupServer\en folder.
Primavera - Administrators Guide
96
10 On the Choose Database Type dialog box, select the database type.
The database must already be installed and configured.
11 On the Enter Database Parameters dialog box, specify the database
connection parameters.
97
In the Server Name field, type the name of the computer running
the Group Server.
To allow users to launch Timesheets via Java Web Start, you have to
enter the URL for the Java Web Start Web server. Enter the server IP
address, and change the folders if necessary.
Apache URLs are case-sensitive. In case of a mismatch,
instead of being processed by the server, the XML content of
the JNLP file is displayed in the browser.
98
If connecting to Oracle:
Provider=OraOLEDB.Oracle;Data Source=Oracle Service Name,
where the Oracle Service Name can be found in the
TNSNAMES.ORA file.
If connecting to Microsoft SQL Server:
Provider=SQLOLEDB; Data Source=MachineName; Initial
Catalog=DatabaseSchemaName
18 Click Next to continue.
19 On the Start Window service dialog box, mark the checkbox to start
the Primavera Group Server service now. If you do not start it now,
you can start it at any time with Microsoft Services in the Microsoft
Management Console (the Group Server runs as a Windows service.)
20 Click Next to continue.
21 Click Finish to close the Setup wizard.
Setup is now complete. You can run the Group Server Administrator to
review or modify additional configuration settings, as described in
Configuring Group Server Settings, page 108.
99
Web Server
Timesheets Web
Browser Version
HTTP(s)
Communication
Protocol
Java Application
Server
Looks at
GroupServer.war
file
Group Server
Socket
Connection
100
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 secure transmission using the HTTPS protocol, enter https and the
port number to which you have configured your Java application
server to service https requests.
The default secure port on Tomcat is 8443. In this case, for example,
specify the secure URL as,
:https://<tomcat_server_name:8443>/groupserver/groupserver.
Some Java application servers (e.g., IBM WebSphere) are
case-sensitive.
101
102
Edit the erps8x6.html File To change the URL specified for the
Group Server servlet during installation, edit the erps8x6.html file as
follows. The erps8X6.html file is located in the language folder within the
Group Server install location. For example, for English, the location is
GroupServer/en/erps8X6.html.
// *** Configurable variables.
// *** May be changed by the system administrator.
var ServerName='';
var ServerPortNum=9002;
var DebugLevel=0;
var Protocol='http'; // This should say 'http' for HTTP OR HTTPS, or,
// 'socket' for a traditional socket install.
In the erps8X6.html file,
the entire var url entry
must appear on a single
line.
var url='http://my_server_name:8080/groupserver/groupserver';
// Or, if you want to use HTTPS,
"var url='https://my_server_name:8443/groupserver/groupserver';".
Support JRE auto-installation on Sun ONE Web Server To
support successful operation of the JRE auto-installation feature, edit the
config\mime.types file to remove the exe reference as shown below.
Before:
type=magnus-internal/cgi
exts=cgi,exe,bat
After:
type=magnus-internal/cgi
exts=cgi,bat
103
Edit the web.xml File If either of the following conditions exists, once
the GroupServer.war file has been expanded, you must edit the web.xml
file.
the Primavera Group Server and Java application server do not reside
on the same machine
104
105
var ServerName=' ' (unused - this is specified in the web.xml in the Group
Server servlet)
var ServerPortNum=9002 (unused - this is specified in the web.xml in the
Group Server servlet)
var DebugLevel=0;
var Protocol='http';
In the erps8X6.html file,
the entire var url entry
must appear on a single
line.
var url='http://yourServerName:780/groupserver/groupserver';
var appType='atP3e'
var authMode='LDAP';
106
Configure the Web server plug-in you are using to proxy requests
var url='http://yourfullyqualifieddomainname:yourSiteMinder
protectedportnumber/groupserver/groupserver';
var appType='atP3e'
var authMode='WebSSO';
107
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.
SiteMinder requires yourfullyqualifiediPlanetservername to be a fully
qualified domain name that can be looked up in a DNS.
108
If you need to take the server offline to perform system maintenance, click
Take Off-Line.
Login requests are denied when the server is offline.
109
The Take Off-Line Options dialog box displays the number of users
currently connected to the server. Choose whether to wait for the last user
to exit from Timesheets before taking the server offline automatically, or
specify a number of minutes to wait before the server is taken offline.
When you choose either option, no new users can start Timesheets.
You can type @TIME in the
body of the message,
which will automatically
report the amount of time
remaining before the
server goes offline.
Mark the Send Message to Logged in Users checkbox and type a message.
You can specify how often to resend the message. Once the Group Server
is offline, all client connections are terminated and future connection
requests are denied.
110
111
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.
112
How does Java Web Start work? Java Web Start can launch a Java
application stored on a server by presenting a link in an HTML page to the
user. When the user clicks the link on the HTML page, Java Web Start
detects whether the user has the correct JRE version installed and the most
recent version of Timesheets cached. If not, Java Web Start automatically
downloads the necessary files, then launches Timesheets from the users
machine. This enables the user to run the most recent version of
Timesheets with the required version of the JRE without performing a
manual upgrade process. By temporarily hiding, but not overwriting other
versions of the JRE, Java Web Start ensures that other applications that
need those JRE versions will still run.
Java Web Start allows you to launch more than one instance of
Timesheets at the same time. Previously, Timesheets did not
allow multiple instances running at the same time.
113
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
114
Remember that Apache URLs are case sensitive, even if the user has a
Windows client that does not differentiate.
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.
115
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.
116
117
Set up the Web site for a new instance You must create a new
Timesheets Web site for each new instance. Once a new Group Server
instance is set up in the TPGS Administrator, you must copy the
Timesheets Web site to enable clients to connect to the new instance. For
example, copy the GroupServer Web site folder to a new name,
GroupServer2.
In the GroupServer2 folder, edit the erps8x6.html file to update the port
number. For example, by default, the original Group Server instance has a
port number equal to 9002. In the erps8x6.html file, change the
ServerPortNum variable to match the port number of the newly created
instance (9003), as shown.
// *** Configurable variables.
// *** May be changed by the system administrator.
var ServerName='servername
var ServerPortNum=9003
Clients can visit the original instance by visiting the index.html file in the
GroupServer folder; clients can visit the newly created instance by visiting
the index.html file in the GroupServer2 folder.
118
Value
Description
Yes/No
Cycle Seed
Yes/No
Edit Subordinate
Resources Timesheets
Yes/No
Yes/No
Enable Performance
Counters
Greeting
Sets the message that appears in the client when first connected to
the TPGS server.
119
Value
Description
15
Log Transactions
Port
9002
Sets the TCP/IP port number used by the Group Server to communicate with the Java client. This port must be opened to the Internet,
or you can change this setting to specify another port that is open to
the Internet. The default value is 9002.
Amount of time the TPGS service delays before starting. Use this
setting if dependent services (such as a database server service)
need time to start first.
600
Value
Description
Amount of time to wait while executing a command before terminating the attempt and generating an error message.
30
Yes/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)
120
Value
Description
60
Frequency of the TPGS server for refreshing cached data from the
database.
30000
Connection String
Database Type
DB Connectivity Check
Yes/No
DB User
PRIVUSER
Logs invalid login attempts to the event log. The default value is
No.
Log SQL
Password
Session Setting
Sync Period
(seconds)
60
121
Value
Description
Synchronize ADO
Connection Creation
Yes/No
Temporary Connections
150
Verbose Logging
Yes/No
Description
Caching Threads
50
Coalescing Threads
Coalescing Timeout
(milliseconds)
750
60
122
120
Description
Frequency that the license manager is checked for concurrent users.
Maximum Temporary
Threads Per CPU (SMP)
15
180
Transaction Threads
Update Threads
120
[Security keys]
Keys
Value
Description
Accept Filters
Reject Filters
Value
Description
HTML Path
c:\inetpub\wwwroot\GroupServer
123
125
126
127
128
To install Tomcat
On Solaris, copy, unzip, and launch the Tomcat installer (apachetomcat-5.5.20.tar.gz) file in the \apache-tomcat-5.5.20 folder on CD 2.
An installation wizard will guide you through the Tomcat installation.
129
130
131
132
133
134
135
136
Users can access Primaveras Web application from client browsers using
the following URL structure, depending on the application server
platform.
On a WebLogic application server
http://serverIP:listenport/ContextRoot/login_cmt
Example: http://192.168.0.1:7001/myprimavera/login_cmt
The default listenport for new WebLogic domains is 7001. The
default context root is myprimavera.
On a WebSphere application server
http://serverIP:listenport/ContextRoot/login_cmt
Example: http://192.168.0.1:9080/myprimavera/login_itcmt
The default listenport is 9080. The default context root is
myprimavera.
On a Tomcat application server
http://serverIP:listenport/ContextRoot/login_cmt
Example: http://192.168.0.1:8080/myprimavera/login_cmt
The default listenport is 8080. The default context root is
myprimavera.
On a JBoss application server
http://serverIP:listenport/ContextRoot/login_cmt
Example: http://192.168.0.1:8080/myprimavera/login_cmt
The default listenport is 8080. The default context root is
myprimavera.
The context root is configurable on all supported application
servers. For information about context root configuration, refer
to your application server documentation.
Also, URLs may be case-sensitive, depending on your
application server configuration.
137
138
139
140
141
142
To display brief setting descriptions in Tree or Table view, mark the Show
tool tips checkbox. Then, position the mouse over a setting to read the
popup description.
Configurations highlighted in red are out of date. Primavera
recommends that you delete these configurations.
143
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.
144
Click to display
configuration settings
in a table format.
To create a new configuration based on factory default settings, rightclick on Factory Defaults in Tree View and choose Duplicate.
145
146
147
148
For example, the following URL would log a user into the database
instance named Sample.
http://serverIP:listenport/login_cmt?db=Sample
As the administrator, you can specify a keyword that bypasses the
database parameter requirement, so that you can access all databases
through the Login page database drop-down list.
149
Database Type
Database Driver
Default
WebLogic
Oracle
WebLogic
SQL Server
WebSphere
Oracle
WebSphere
SQL Server
Tomcat
Oracle
Tomcat
SQL Server
JBoss
Oracle
Tomcat
SQL Server
150
Authentication.Mode
Authentication.WebSSO.UserNameHeaderKey
Authentication.WebSSO.ContextPathOverride
Authentication.WebSSO.ServerandPortOverride
Authentication.LDAP.SSLCertificateStore
Authentication.LDAP.SSLStorePassword
The Authentication.Mode settings must match the mode
selected for Group Server.
151
152
[Localization settings]
Setting Name and Description
Default
Valid Ranges/Values
Localization.SystemLanguage
Language for server string constants
en
Localization.SystemCountry
Country for server string constants
US
153
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.Name
The name of this database instance.
up to 32 characters
Database.Instance.Description
A description of this database instance.
up to 128 characters
Database.Instance.Driver
The class name of the JDBC driver.
com.microsoft.sqlserver.jdbc.
SQLServerDriver
oracle.jdbc.driver.OracleDriver
Database.Instance.URL
The database URL used to establish a connection to the
database.
Database.Instance.PublicGroupId
The public group ID used to establish a connection to the
database.
Database.Instance.UserName
The name used to establish a connection to the database.
pubuser
Database.Instance.Password
pubuser
The password used to establish a connection to the database.
Database.Instance.CollaborationDomain
The collaboration domain name used by Primaveras Web
application.
Oracle example:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(A
DDRESS=(PROTOCOL=TCP)
(HOST=xx.xxx.xxx.xx)(PORT=yyyy)))(CONNECT_DATA=
(SID=zzzz)))
Oracle short form example:
jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
jdbc:sqlserver://xxxx:yyyy;database=zzzz
x = SQLServer IP address or hostname
y = database listen port
z = database name
154
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.
TRANSACTION
SQLServer2000TransactionIsolationLevel
_READ_UNCO
The transaction isolation level for SQL Server 2000 databases MMITTED
only. Controls the locking and row versioning behavior of
SQL statements issued by a connection.
Database.Instance.ConnectionPool[aaa].
4m
ConnectionPoolResizeRate
The timeout period after which the system will adjust the
number of database connections to be equal to the maximum
number of database connections concurrently used during the
last period.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
4m - 12h
Database.Instance.ConnectionPool[aaa].
1m
MaintenanceFrequency
The run frequency of the maintenance that ensures leases
have not exceeded the maximum duration.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
10s - 1h
155
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.ConnectionPool[aaa].
30s
LeaseRequestWaitTimeout
The amount of time a request for a database connection will
wait.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
5s - 2h
Database.Instance.ConnectionPool[aaa].
50
MaxConnections
The maximum number of connections the server will have to
the database.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
5 - 15000
Database.Instance.ConnectionPool[aaa].FetchSize
120
A hint to the database driver for how many rows to fetch at a
time.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
156
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.ConnectionPool[aaa].TraceSQL
false
Trace all SQL sent to the database.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
true/false
Database.Instance.ConnectionPool[aaa].
3
RenewableFreeLimit
The minimum number of connections that should be available
for leases to be renewed.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
3-5
157
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.ConnectionPool[aaa].
PMR - false
RenewableLeases
PML - false
If false, each connection can be leased only for the
PMT - true
MaxLeaseDuration period.
If true, connection leases are renewed if database statements
are completed within the MaxLeaseDuration time period.
When true, the code can hold onto the connection as long as it
needs, provided SQL statements are completed within the
MaxLeaseDuration period. When true, the connection is
revoked if no SQL statements are issued within the
MaxLeaseDuration period or if one statement takes longer to
execute than that period.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
true/false
Database.Instance.ConnectionPool[aaa].
PMR - 2m
PML - 10m
MaxLeaseDuration
The maximum amount of time a database connection can be PMT - 10m
leased before it is revoked.
[PMR] Used for the standard connection pool, which is the
most frequently used connection pool in the Business Rule
Engine.
[PML] Used for the long running connection pool, which is
used in the Business Rule Engine when scheduling long
running jobs.
[PMT] Used for the transactional connection pool, which is
used in the Business Rule Engine when a client transaction is
requested.
PMR - 5s - 4h
PML - 5s - 6h
PMT - 5s - 6h
Database.Instance.GroupServer.Protocol
Protocol for GroupServer
socket
Database.Instance.GroupServer.Server
GroupServer host machine name
servername
Database.Instance.GroupServer.Port
GroupServer host listen port
9002
158
[Database Settings]
Setting Name and Description
Default
Database.Instance.GroupServer.URL
GroupServer servlet URL.
http://servername
Database.Instance.MethodologyManagement.Name
Name of this database instance.
Database.Instance.MethodologyManagement.Description
Description of this database instance.
Database.Instance.MethodologyManagement.Driver
Class name of the JDBC driver.
Valid Ranges/Values
oracle.jdbc.driver. com.microsoft.sqlserver.jdbc.
OracleDriver
SQLServerDriver
oracle.jdbc.driver.OracleDriver
Database.Instance.MethodologyManagement.URL
Oracle example:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(A
DDRESS=(PROTOCOL=TCP)
(HOST=xx.xxx.xxx.xx)(PORT=yyyy)))(CONNECT_DATA=
(SID=zzzz)))
Oracle short form example:
jdbc:oracle:thin:@xx.xxx.xxx.xx:yyyy:zzzz
SQL example:
jdbc:sqlserver://xxxx:yyyy;database=zzzz
x = SQLServer IP address or hostname
y = database listen port
z = database name
Database.Instance.MethodologyManagement.UserName
The name used to establish a connection to the database.
Database.Instance.MethodologyManagement.Password
The password used to establish a connection to the database.
Database.Instance.MethodologyManagement.
1
PublicGroupID
The Group ID used to establish a connection to the database.
Database.Instance.MethodologyManagement.
MMDB
DBAlias
The DB Alias name used by the Project Architect job service
to create a project plan from a methodology.
159
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.MethodologyManagement.
4m
ConnectionPool[MMR].ConnectionPoolResizeRate
The timeout period after which the system will adjust the
number of database connections to be equal to the maximum
number of database connections concurrently used during the
last period.
4m - 12h
Database.Instance.MethodologyManagement.
ConnectionPool[MMR].MaintenanceFrequency
The run frequency of the maintenance that ensures leases
have not exceeded the maximum duration.
1m
10s - 1h
Database.Instance.MethodologyManagement.
ConnectionPool[MMR].LeaseRequestWaitTimeout
The amount of time a request for a database connection will
wait.
30s
5s - 2h
Database.Instance.MethodologyManagement.
50
ConnectionPool[MMR].MaxConnections
The maximum number of connections the server will have to
the database.
5 - 15000
Database.Instance.MethodologyManagement.
120
ConnectionPool[MMR].FetchSize
A hint to the database driver for how many rows to fetch at a
time.
Database.Instance.MethodologyManagement.
ConnectionPool[MMR].TraceSQL
Trace all SQL sent to the database.
true/false
false
Database.Instance.MethodologyManagement.
3
ConnectionPool[MMR].RenewableFreeLimit
The minimum number of connections that should be available
for leases to be renewed.
3-5
160
[Database Settings]
Setting Name and Description
Default
Valid Ranges/Values
Database.Instance.MethodologyManagement.
false
ConnectionPool[MMR].RenewableLeases
If false, each connection can be leased only for the
MaxLeaseDuration period.
If true, connection leases are renewed if database statements
are completed within the MaxLeaseDuration time period.
When true, the code can hold onto the connection as long as it
needs, provided SQL statements are completed within the
MaxLeaseDuration period. When true, the connection is
revoked if no SQL statements are issued within the
MaxLeaseDuration period or if one statement takes longer to
execute than that period.
true/false
Database.Instance.MethodologyManagement.
ConnectionPool[MMR].MaxLeaseDuration
The maximum amount of time a database connection can be
leased before it is revoked.
2m
5s - 4h
Database.Instance.SessionSettings.Setting1-5
Alter session commands used to establish cursor sharing,
rule-based mode, SQL trace, and more. Invalid settings in
these fields are ignored.
Database.Instance.CostBasedOptimizationSettings.
EnableCBO
Enable Cost Based Optimization if true.
false
true/false
Default
Valid Ranges/Values
ThreadPool.NumThreads
The number of server threads.
25
2-300
ThreadPool.MaxTaskDuration
The maximum duration a thread can be used for one task.
3m
10s - 24d
ThreadPool.MaxTaskDurationLongRunning
The maximum duration a thread can be used for a long
running task.
5m
10s - 24d
ThreadPool.MaintenanceFrequency
The frequency at which threads are checked for excess time
durations.
45s
15s - 24d
161
[Log Settings]
Setting Name and Description
Default
Valid Ranges/Values
Log.HtmlLogger.Severity.SeverityLevel
Log severity level for the HTML Logger.
error
Log.HtmlLogger.WriteFrequency
The time period for which log messages will be cached
between writes.
3s
3s - 24d
Log.HtmlLogger.ArchiveSize
The minimum size (in bytes) a log file must be before it is
archived.
1048576
1042 - 2147483647
Log.HtmlLogger.ArchiveNumber
6
Maximum number of log files to be used. The default files are
named myprimaveralog0.html through
myprimaveralog5.html.
2 - 2147483647
Log.HtmlLogger.Enabled
Enable the HTML Logger.
true/false
true
162
[Log Settings]
Setting Name and Description
Default
Valid Ranges/Values
Log.ConsoleLogger.Severity.SeverityLevel
Log severity level for the Console Logger.
error
Log.ConsoleLogger.WriteFrequency
The time period for which log messages will be cached
between writes.
3s
3s - 24d
Log.ConsoleLogger.Enabled
Enable the Console Logger
false
true/false
Default
Valid Ranges/Values
Performance.Enabled
Performance monitor packets are sent when true.
false
true/false
Performance.MonitorHost
The destination IP or machine name for the performance
monitor packets
localhost
Performance.MonitorPort
The destination port for the performance monitor packets
6990
1024 - 65535
Performance.UpdateInterval
The rate at which the performance monitor packets are sent.
1s
250 - 1m
[Performance Settings]
163
[LicenseService Settings]
Setting Name and Description
Default
Valid Ranges/Values
LicenseService.CalcRate
5m
The rate at which the database is checked for changes in total
license counts.
10s - 10m
LicenseService.UpdateRate
The rate at which a Business Rule Engine synchronizes with
the database for license counts.
30s
100 - 1m
LicenseService.ExpirationCheckRate
The rate at which licenses are checked to see if they should
expire.
2m
500 - 15m
Default
Valid Ranges/Values
TimestampService.RefreshRate
The rate at which the database is queried to determine if a
table change notification is necessary.
1m
15s - 1h
Default
Valid Ranges/Values
[TimestampService Settings]
[RegistryService Settings]
Setting Name and Description
RegistryService.RefreshRate
1m30s
The rate at which the database is updated with the status of the
Business Rule Engine.
15s - 1h
RegistryService.StalePeriod
The duration of inactivity that indicates an inoperable
Business Rule Engine.
4m
1m - 10m
RegistryService.Port
The TCP/IP port on which requests to revive dead Business
Rule Engines will be received.
9192
1024 - 65535
164
[NextKeyService Settings]
Setting Name and Description
Default
Valid Ranges/Values
NextKeyService.RefreshRate
The rate at which nextkey cache is refreshed.
1m
15s - 1h
NextKeyService.MaxCachedKeys
Maximum nextkeys to cache per table
10
1 - 100
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.PrototypeUser
Application.IgnoreDaylightSavingsTime
Set to false to account for daylight savings time.
true
true/false
Application.TimesheetURL
URL for invoking timesheet program
/action/launchTimesheetSe-
emlessly
Application.TimesheetCodebase
URL for the timesheet application Web site
server/GroupServer
Application.JavaPluginURL_IE
URL for Internet Explorer users to download Java Plug-in
(JRE).
Application.JavaPluginVersionID_IE
JRE version used by applets in Internet Explorer
Application.ExcelImportMaxTransactions
2000
The maximum number of transactions (activities or resources)
that can be imported at once from a .xls or .csv file
100 - 2000
Application.ExcelImportMaxFileSize
The maximum size of the .xls or .csv file uploaded during an
import attempt (KB)
64 - 4096
1048
Application.AllowAutoSummarizeOption
true
Set to true to allow automatic summarization to be available in
resource staffing user preferences.
true/false
165
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.DBDropdownKeyword
blank
Keyword to use for enabling database selection control in the
login page. Pass this as a URL parameter db=keyword. Set this
to an empty string if you do not want to require the keyword.
Application.LogoutURL
Directs Primaveras Web application to a specific URL when
the user exits with the Logout/Close icon in the banner of
Primaveras Web application. Any valid URL can be used. If
no URL is specified, the Web application directs the user to
the launch page of Primaveras Web application.
Application.CompressAppletCommunication
Set to true to compress communication between applets and
the server.
true
true/false
Application.CompressHtmlContent
true
Set to true to compress HTML-related content generated by
Primaveras Web application, including .html, .js, and css files,
and Ajax content.
true/false
Application.MaxProjectsInPortfolio
The maximum number of projects returned when creating a
portfolio with a filter.
1000
1 - 100000
Application.MaxRPSpreasheetProjects
LoadedFromPortfolio
The maximum number of projects that can be open in the
Resource Planning spreadsheet.
100
1 - 1000
Application.MaxPortletsPerDashboard
The maximum number of portlets that can be displayed in a
dashboard on the Dashboards Home page.
12
1 - 50
Application.MaxProjectsPerPortfolioView
The maximum number of projects that can be displayed in a
portfolio view on the Portfolio Analysis tab and in Portfolio
View portlets on dashboards.
5000
1 - 20000
Application.MaxActivitiesPerActivityView
The maximum number of activities that can be displayed in
the Activities tab of the Projects section.
2000
1 - 5000
Application.MaxMRUListItems
The maximum number of items that can be displayed in a
Most Recently Used (MRU) list.
1 - 10
166
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.CustomPortletURLUserInfoEncryptionKey
Encryption key for custom portlet user password.
Application.TransactionMonitorExecutionInterval
The frequency at which the transaction monitor job runs,
which ensures transactions have not bee orphaned.
10m
1s - 24d
Application.Performance.UseEnterpriseSummary
Use enterprise level summary data for resources and roles.
false
true/false
1-50000
Application.Tracer.Enabled
If true, debugging messages are sent to Tracer application.
true/false
false
Application.Tracer.ServerName
localhost
Hostname or IP address of destination for sending tracer information.
Application.Tracer.SocketPort
Port to use for Tracer socket connection
9210
1024-65535
Application.Tracer.UseBackGrndSendThread
If true, use background thread for sending TCP messages to
tracer.
true
true/false
Application.WebScheduler.Enabled
true
If true, scheduling for jobs from Primaveras Web application
is performed using the Web Scheduler. If false, scheduling is
performed using the Job Service Scheduler.
true/false
167
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.WebScheduler.SchedulingInterval
Amount of time the Web Scheduler will wait before scheduling the next available job.
5m
1s - 24d
Application.WebScheduler.ConcurrentSchedulers
The number of processes (active schedulers) used for scheduling on this server. A value of 0 (zero) indicates that scheduling will not be performed on this server.
0-20
Application.WebScheduler.ActiveSchedulerMode
If true, jobs are processed continuously until all jobs are
scheduled. If false, each job is processed according to the
Scheduling Interval.
true
true/false
Application.WebScheduler.ASAPCleanupRate
1d
Amount of time at which completed WebASAP scheduler jobs
are removed from the database.
1h - 24d
Application.PeriodPerformance.Enabled
Service for storing period performance. If true, ThisPeriod
values are stored in the specified financial period.
true/false
true
Application.PeriodPerformance.ExecutionInterval
5m
Amount of time the service will wait before checking for any
period performance jobs.
1s - 24d
Application.PeriodPerformance.ConcurrentThreads
The number of processes used for the PeriodPerformance
service on this server. A value of 0 (zero) indicates that the
service is not available on this server.
0 - 20
Application.SyncActualThisPeriod.Enabled
Service for synchronizing actuals and ActualThisPeriod
values. If true, recalculates actual units and costs for
ThisPeriod.
true
true/false
Application.SyncActualThisPeriod.ExecutionInterval
5m
Amount of time the service will wait before checking for any
SyncActualThisPeriod jobs.
1s - 24d
Application.SyncActualThisPeriod.ConcurrentThreads
The number of processes used for the SyncActualThisPeriod
service on this server. A value of 0 (zero) indicates that the
service is not available on this server.
0 - 20
168
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.ProjectHierarchyCache.CachePolicy
The cache policy to use. The cache policy determines how
much data is in the cache and which data is removed to
reclaim memory.
PRR
5000
1000 - 30000
Application.ProjectHierarchyCache.CacheMaintentance- 5h
Frequency
The frequency for applying the specified cache policy. Application of the cache policy might result in memory used by the
cache to be reclaimed.
1m - 24d
Application.CollaborationServer.ServerName
Hostname of the collaboration server of Primaveras Web
application.
Application.CollaborationServer.LibraryName
The name of the database where library data resides.
Application.CollaborationServer.Collaboration
WorkspaceName
The default collaboration workspace name.
PrimaveraRootContainer
Application.CollaborationServer.Initiation
WorkspaceName
The default initiation workspace name.
primavera_initiations
169
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.CollaborationServer.AppName
The default app name used by Primaveras Web application.
primaveraApp
Application.CollaborationServer.PoolSize
The number of collaboration connections initialized.
20
0 - 2147483647
Application.CollaborationServer.PoolUserName
The name used to start the connection pool.
PROXYUSER
Application.CollaborationServer.PoolUserPassword
proxyuser
Password for the user name used to start the connection pool.
Application.CollaborationServer.AdminUserName
The Admin user with full privileges.
Admin
Application.CollaborationServer.AdminPassword
The password of the admin user.
admin
Application.CollaborationServer.CacheUserName
The user name that enables Primaveras Web application to
access the application cache.
CACHEMANAGER
Application.CollaborationServer.CachePassword
The password that corresponds to the CacheUserName.
cachemanager
Application.CollaborationServer.CacheLimit
The maximum number of CMS objects that are kept in the
application cache.
1000
0 - 2147483647
Application.CollaborationServer.
StrictDocumentVersioning
If true, document checkout is restricted to the most recent
version of a document. If false, any document version can be
checked out.
true
true/false
Application.Notifications.EnableIssueNotifications
Enable or disable automated notifications when Issues are
added or modified.
false
true/false
Application.Notifications.EnableEventNotifications
Enable or disable automated notifications when Events are
added or modified.
false
true/false
Application.Notifications.EnableInvitationNotifications
false
Enable or disable automated notifications when Invitations are
added.
true/false
170
[Application Settings]
Setting Name and Description
Default
Valid Ranges/Values
Application.Notifications.EnableInitiationNotifications
false
Enable or disable automated notifications when Invitations are
pending.
true/false
Application.Notifications.Notifications
false
FromEmailOverride
Set to true to always use the systems From email address. Set
to false to use the email address of the user who causes notifications to be sent, if their email address is configured.
true/false
Application.Notifications.NotificationsFromEmail
Joe User <joeuser@
The email address from which Notifications will be sent when uninitabc123z.com>
either NotificationsFromEmailOverride is true or the users
email address is not configured
Application.CollaborationSyncService.
1h
SynchronizationInterval
The interval at which the collaboration synchronization
service will run. The synchronization moves documents
marked for deletion to the collaboration server \trash folder.
Additionally, other collaboration items (e.g., discussions or
issues) that should be removed (e.g., when a project is deleted)
are moved to the \trash folder.
1m - 24d
Application.CollaborationRecyclerService.Automatic
If true, enables the collaboration recycler service, which
purges deleted documents and other collaboration items
(in the collaboration file server \trash folder).
false
true/false
24d
10m - 24d
171
[Authentication settings]
Setting Name and Description
Default
Valid Ranges/Values
Authentication.Mode
The method used for client authentication.
NATIVE
Authentication.WebSSO.UserNameHeaderKey
The name of the http header you specified in SiteMinder.
smuser
http://
servername.domain.com:
82
Authentication.LDAP.SSLCertificateStore
The full path to the keystore that holds the SSL certificate for
the LDAP server.
Authentication.LDAP.SSLStore Password
The password for the keystore that holds the SSL certificate.
Default
Valid Ranges/Values
AsynchJobs.PurgeInterval
The frequency at which long running job records will be
removed from the database.
1h
0 -24d
AsynchJobs.GraceTime
1d
The minimum age of long running job records removed during
purge.
172
[MailService Settings]
Setting Name and Description
Default
Valid Ranges/Values
MailService.EmailNotificationServer
Hostname or IP address of the E-mail notification server for
Timesheet Approval.
MailService.SmtpPort
The tcp/ip port of the outgoing SMTP server.
25
1 - 65535
MailService.SendInterval
The frequency at which queued mail messages are sent.
1m
0 - 24d
MailService.MaxQueueLength
The maximum size of the mail message queue
250
0 - 2147483647
MailService.AuthorizedUser
The name of the account to use to send mail from this mail
server.
MailService.AuthorizedPassword
The password of the account used to send mail from this mail
server.
Default
Valid Ranges/Values
IntegrationServer.RMI.RegistryPort
The port for the RMI Registry. This value is usually set to at
least 1024.
9099
1024 - 65535
IntegrationServer.RMI.Enable
The setting that enables the RMI server.
true
true/false
IntegrationServer.RMI.CompressionServiceEnable
The setting that enables compression service mode.
true
true/false
IntegrationServer.RMI.SSLServiceEnable
The setting that enables SSL service mode.
true
true/false
IntegrationServer.RMI.StandardServiceEnable
The setting that enables Standard service mode.
true
true/false
173
Default
Valid Ranges/Values
IntegrationServer.RMI.HTTPServiceEnable
The setting that enables HTTP tunneling mode.
false
true/false
IntegrationServer.RMI.HTTPsServiceEnable
The setting that enables secure HTTP (SSL) tunneling mode.
false
true/false
IntegrationServer.RMI.CompressionServicePort
0
The port to use for Compression service mode. A setting of 0
indicates that any available port will be used. If the server will
be accessed across a firewall, you must set this to a specific
port.
0 - 65535
IntegrationServer.RMI.SSLServicePort
0
The port to use for SSL service mode. A setting of 0 indicates
that any available port will be used. If the server will be
accessed across a firewall, you must set this to a specific port.
0 - 65535
IntegrationServer.RMI.StandardServicePort
0
The port to use for Standard service mode. A setting of 0
indicates that any available port will be used. If the server will
be accessed across a firewall, you must set this to a specific
port.
0 - 65535
IntegrationServer.RMI.HTTPServicePort
The port to use for HTTP tunneling mode. A setting of 0
indicates that any available port will be used.
0 - 65535
IntegrationServer.RMI.HTTPsServicePort
0
The port to use for secure HTTP tunneling mode. A setting of
0 indicates that any available port will be used.
0 - 65535
IntegrationServer.SessionTimeOut
120
The amount of time after which an idle client connection will
be terminated.
1 - 24d
174
Collaboration Setup
175
Collaboration Setup
In this chapter
Preparing the Installation
Installing the Collaboration Server
Migrating Worksite MP Server 3.1
SP1
Applying the HFB7 Update
Creating a Collaboration
Configuration
Configuration Tasks
Adding the Indexer Service
Adding Trustees
Enabling Expired Trustees
Adding a Facility
Adding a Domain and Admin User
Extend the Collaboration Schema
176
Collaboration Setup
177
The Indexer service requires approximately 10% to 20% of the total file
server disk space consumption. For example, if the disk space usage on the
file server is 5 GB, the Indexer disk space requirement would rage
between 500 MB (10%) to 1 GB (20%).
178
Collaboration Setup
179
180
Collaboration Setup
181
You may view the results of any command line execution in the
corresponding log files found in the
c:\worksitemp3\mpserver\logs\hostname directory.
1 Make a backup copy of the database and file servers. The default
location for 3.1 file servers is c:/worksitemp.
182
After installing the service, launch the services control panel and set
the startup type of the WorkSite MP Process Manager service to
Automatic, then start the service if it is not already running.
10 Copy the DAT file for the existing library from the
<31installationdirectory>\worksiteserver\config\objectmodels to the
c:\worksitemp4\mpserver\config\objectmodels directory. The default
name for the extended Primavera data model DAT file is
finalschema.dat. In the following steps, the DAT file will be referred
to as finalschema.dat.
Primavera - Administrators Guide
Collaboration Setup
183
If you plan to create a new library for use by the same server
(either as a local or remote library), you must use the
model_41.dat file or its extensions.
184
16 (SQL Server Database Only) From the Start menu, open Microsoft
SQLServer Query Analyzer and log in as the database owner (the
default login uses IMANAGE as the name and password).
17 Select the database for the library being migrated.
18 Open and execute c:\worksitemp4\mpserver\31to41\migrate.sql
Disregard the following error messages:
Warning: The table 'con_notification_message' has been created but
its maximum row size (13004) exceeds the maximum number of bytes
per row (8060). INSERT or UPDATE of a row in this table will fail if
the resulting row length exceeds 8060 bytes.
19 (Oracle Database Only) Using SQLPlus or other Oracle client,
execute the migrate.sql file from the c:\worksitemp4\mpserver\31to41
directory as the database owner (the default login uses IMANAGE as
the name and password).
After running the script on an Oracle database, commit your
changes (using commit;).
Collaboration Setup
185
186
This will generate a log file named cms.DocumentModByMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
31 From the WorkSite MP 4.1 directory (default is
c:\worksitemp4\mpserver\bin\win), run End Date Migrate as follows:
enddatemigrate <cluster name> <library name> <admin password>
<proxy password>
This will generate a log file named cms.EndDateMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
Collaboration Setup
187
This will generate a log file named cms.ConnectionMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
33 From the WorkSite MP 4.1 directory (default is
c:\worksitemp4\mpserver\bin\win), run Workflow Field Migrate as
follows:
workflowfieldmigrate <cluster name> <library name> <admin password>
<proxy password>
This will generate a log file named cms.workflowFieldMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
188
This will generate a log file named cms.workflowMonikerMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
35 From the WorkSite MP 4.1 directory (default is
c:\worksitemp4\mpserver\bin\win), run Desktop ID Migrator as
follows:
desktopidmigrator <server name> <library name> <proxy password>
<facility admin ID> <facility admin domain> <facility admin password>
<optional facility name>
This command updates all facilities for which the specified account
has administrator access. Ideally, use an account that has administrator access to all facilities. If a single account does not have administrator access to all facilities, run this command multiple times,
changing the account information until all facilities have been
updated. If necessary, you can target a specific facility with the
<optional facility name> parameter.
Collaboration Setup
189
37 Click OK to continue.
This completes the WorkSite MP Server 4.1 migration in a Windows
environment.
Migrating on Solaris
Perform the following to migrate from WorkSite MP Server version 3.1
SP1 to version 4.1:
This procedure assumes that the default WorkSite MP 4.1
installation directory is /worksitemp4/mpserver/. If you install
WorkSite MP 4.1 into a different directory, modify the
commands to accommodate your installation directory.
190
You may view the results of any command line execution in the
corresponding log files found in the /worksitemp3/mpserver/
logs/hostname directory.
1 Make a backup copy of the database and file servers. The default
location for the 3.1 file servers is c:/worksitemp.
2 Extract the migrate31To41V2.zip migration files from the
\collab\41Upgrade directory on CD3 to the WorkSite MP 4.1
installation directory (/worksitemp4/mpserver by default) and
overwrite existing files when prompted. Ensure that the Use Folder
Names option is checked when extracting the files.
Use the migrate31To41V2.zip migration package. Do not use
migrate31To41.zip, which might have been included with your
Worksite MP Server software.
10 Copy the DAT file for the existing library from the
<31installationdirectory>\worksiteserver\config\objectmodels to the
c:\worksitemp4\mpserver\config\objectmodels directory. The default
name for the extended Primavera data model DAT file is
finalschema.dat. In the following steps, the DAT file will be referred
to as finalschema.dat.
Collaboration Setup
191
If you plan to create a new library for use by the same server
(either as a local or remote library), you must use the
model_41.dat file or its extensions.
192
16 (SQL Server Database Only) From the Start menu, open Microsoft
SQLServer Query Analyzer and log in as the database owner (the
default login uses IMANAGE as the name and password).
17 Select the database for the library being migrated.
18 Open and execute /worksitemp4/mpserver/31to41/migrate.sql
Disregard the following error messages:
Warning: The table 'con_notification_message' has been created but
its maximum row size (13004) exceeds the maximum number of bytes
per row (8060). INSERT or UPDATE of a row in this table will fail if
the resulting row length exceeds 8060 bytes.
19 (Oracle Database Only) Using SQLPlus or other Oracle client,
execute the migrate.sql file from the /worksitemp4/mpserver/31to41
directory as the database owner (the default login uses IMANAGE as
the name and password).
After running the script on an Oracle database, commit your
changes (using commit;).
Collaboration Setup
193
194
This will generate a log file named cms.DocumentModByMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
31 From the WorkSite MP 4.1 directory (default is /worksitemp4/
mpserver/bin/unix), run End Date Migrate as follows:
./enddatemigrate <cluster name> <library name> <admin password>
<proxy password>
This will generate a log file named cms.EndDateMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
Collaboration Setup
195
This will generate a log file named cms.ConnectionMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
33 From the WorkSite MP 4.1 directory (default is /worksitemp4/
mpserver/bin/unix), run Workflow Field Migrate as follows:
./workflowfieldmigrate <cluster name> <library name> <admin password>
<proxy password>
This will generate a log file named cms.workflowFieldMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
34 From the WorkSite MP 4.1 directory (default is /worksitemp4/
mpserver/bin/unix), run Workflow Moniker Migrate as follows:
./workflowmonikermigrate <cluster name> <library name> <admin password>
<proxy password>
196
This will generate a log file named cms.workflowMonikerMigrate.<hostname>.log in the server logs directory. The final line in
this log file should read Finished Migration.
35 From the WorkSite MP 4.1 directory (default is /worksitemp4/
mpserver/bin/unix), run Desktop ID Migrator as follows:
./desktopidmigrator <server name> <library name> <proxy password>
<facility admin ID> <facility admin domain> <facility admin password>
<optional facility name>
This command updates all facilities for which the specified account
has administrator access. Ideally, use an account that has administrator access to all facilities. If a single account does not have administrator access to all facilities, run this command multiple times,
changing the account information until all facilities have been
updated. If necessary, you can target a specific facility with the
<optional facility name> parameter.
Collaboration Setup
197
37 Click OK to continue.
This completes the WorkSite MP Server 4.1 migration in a Solaris
environment.
198
1 If necessary, insert/mount CD 3.
2 Launch the installer from the following folder:
\collab\41hfb7\WSMP_Server41SP1HFB7\install.htm
3 On the Update page, click Start Installer.
4 After the download is complete, select the installation language and
review the introduction.
5 Accept the license agreement.
Collaboration Setup
199
6 When prompted for the existing installation directory, verify that the
path listed is correct. If not, click Choose... and select the base
installation directory (this directory contains the "mpserver"
directory).
7 When prompted for a backup directory, you can leave the default
directory, type the path to a new directory, or click Choose... and
select a backup directory.
200
9 Delete any temporary files (all files) in the \fxfer directory of your
Worksite MP installation. The default location of this directory is
c:\worksitemp4\<library_name>\fxfer\.
10 Restart the Worksite Process Manager (or restart the service on
Windows). If CMS and Indexer are not set to Auto-Start, restart them
from the Configuration Manager.
Collaboration Setup
201
202
Collaboration Setup
203
204
Field
Definition
Value
Library Name
User-defined
DBInstance Name
Driver
Owner
Connection
Collaboration Setup
205
The Content Library Creation Wizard creates the database tables and
indices required to run the collaboration server. Click Next to move to the
next step in the wizard. The following information is required:
Library Object Model - choose worksitemp40
206
File Server Path - type or browse to the full path to the location where the
library files should be created and stored (this can be any desired location)
Collaboration Setup
207
Once the wizard is finished, the new library must be defined as the
Authentication Library.
Add an Authentication Library
1 Right-click the cluster name and select Edit.
208
When CMS has started successfully, the red square on the CMS
service icon changes to a green arrow.
2 After starting the CMS service, right-click the service name and select
Auto-Start from the menu.
Collaboration Setup
209
Configuration Tasks
After installing the collaboration server, several configuration tasks are
required to prepare the server for use in the Primavera environment. The
two main interfaces used to configure the collaboration server are the
Configuration Manager and the Library Manager.
This section describes the main configuration interfaces and highlights the
tasks for which each interface is used.
Configuration Manager The Configuration Manager is used to
configure one or more server clusters and to control the CMS, Indexer, and
other collaboration services. The entire WorkSite MP server cluster can be
controlled via this application, which is what makes the Configuration
Manager such a powerful tool.
When you set up your WorkSite MP Server, you must run the
Configuration Manager to create a configuration for all the components
that make up a WorkSite MP Server Cluster. The list below denotes the
components that are configured for each WorkSite MP Server Cluster
using the Configuration Manager:
Server Clusters
Servers
Services
Cluster node
Server node
Services
Library node
210
Facilities
WorkGroups
Metadata classes
Metadata Relationships
Privileges
System Configuration
System Users
Collaboration Setup
211
Directory frame
Display frame
Menus
Toolbar
Look-Up toolbar
Clusters
Server Cluster
Library
Login to a Library
212
Edit Privileges
Collaboration Setup
213
214
Collaboration Setup
215
6 Select the library to which you are adding the Indexer service from
the Available list. To select multiple libraries, use Ctrl or Shift.
When the Indexer has started successfully, the red circle on the
Indexer service icon changes to a green arrow.
216
2 After starting the Indexer service, right-click the service name and
select Auto-Start from the menu.
Collaboration Setup
217
Adding Trustees
1 Launch the Library Manager according to your operating system:
Windows:Start, Programs, Worksite MP Server 4, Library Manager
Solaris:/worksitemp4/mpserver/bin/unix/imlibmgr
The CMS service must be running before the Library Manager
can be launched.
218
7 Enter a name for the master realm next to RDN (the suggested default
name is ImanageRealm), then click OK.
Enter master
realm name.
Click OK when
finished.
8 Expand the Realms node, right-click the new master realm, then
select Add to add a trustee.
Collaboration Setup
219
RDN
Class
Label
UID
Domain
220
Collaboration Setup
221
Adding a Facility
After adding at least one trustee to the master realm, the next step is to add
a default facility.
1 Right-click on the Facilities node and select Add.
2 Enter a name for the facility. Select the master realm under the
Trustee Selection Tree, select the new trustee from the Trustee
Selection list, then click Add to move the trustee to the Grants list.
Select the
master realm
Select the
desired trustee
Click Add
Click OK
222
Select Members
Collaboration Setup
223
2 Enter the following details for the primavera.com domain, then click
OK:
RDN - primavera.com
Class - Domain
Label - d (changed automatically when Class is changed)
RDN
Class
Label
224
3 Click on the Libraries tab and uncheck each of the Inherit boxes under
Preferences Facility and Homepage Workspace.
Collaboration Setup
225
226
RDN
Class
You should
always select
this option.
Label
UID
Domain
Collaboration Setup
227
2 Click on the Trustee Managers tab, expand the Trustee Selection Tree,
select the DomainAdmin user under Person Selection, then click Add
to add the user to the Trustee Managers list.
Click OK
228
Select the
primavera.com
domain
Select the
DomainAdmin
user
Click Add
Click OK
Collaboration Setup
229
Select the
primavera.com
domain
Select the
DomainAdmin
user
Click Add
Click OK
230
Collaboration Setup
231
The log file should end with the following line in the case of a successful
upgrade:
<Date/Time>: INFO [main] Library Migrate ended successfully
232
EXTENSION
NAME
dgn
DGN
dwg
DWG
2 Expand the cluster and library nodes to display the library sub-nodes.
3 Expand the Metadata node.
4 Right-click on the Application Formats node and select Add.
Collaboration Setup
233
5 Enter the values listed on the previous page for one of the document
formats.
To enter data in a Value cell, left-click the desired cell and enter the
text required.
6 Click OK when finished.
If the file format is used frequently, you may want to mark the
IS_INDEXABLE checkbox to enable faster loading of the
specified document format.
234
Collaboration Setup
235
Additional Settings
The remaining collaboration settings can be modified as needed, but
changes are not required to enable collaboration functionality in
Primaveras Web application.
Application.CollaborationServer.Collaboration
WorkspaceName - The default collaboration workspace name.
Application.CollaborationServer.Initiation
WorkspaceName - The default initiation workspace name.
Application.CollaborationServer.PoolUserPassword - Password
for the user name used to start the connection pool.
Application.CollaborationServer.StrictDocumentVersioning - If
true, document checkout is restricted to the most recent version of a
document. If false, any document version can be checked out.
Application.CollaborationSyncService.
SynchronizationInterval - The interval at which the collaboration
synchronization service will run. The synchronization moves
documents marked for deletion to the collaboration server \trash
folder. Additionally, other collaboration items (e.g., discussions or
issues) that should be removed (e.g., when a project is deleted) are
moved to the \trash folder.
Application.CollaborationRecyclerService.Automatic - If true,
enables the collaboration recycler service, which purges deleted
documents and other collaboration items (in the \trash folder).
236
Application.CollaborationRecyclerService.
RecycleInterval - The interval at which the collaboration recycler
service should run.
237
238
On the Controller and all DJS servers, define the Temp and TMP
variables in Environment variables (both User variables and System
variables).
Synchronize the system clocks of the Controller and all DJS servers to
have identical time stamps in the log files.
239
240
241
242
243
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.
244
6 For each custom permission type, click the associated Edit button and
perform steps 7-9. When you have completed steps 7-9 for all three
custom permission types, continue with Step 10.
The Registry Value Permissions dialog opens.
For access
permissions,
this field says
Allow Access.
For launch
permissions, this
field says Allow
Launch. For
configuration
permissions, this
field says Full
Control.
245
8 In the Add Users and Groups dialog, select the user group you
previously created (in this example, PrmJobAdmins). In the Type of
Access field, select Allow Access. Click OK.
When you repeat this step for the Use Custom Launch
Permissions option you selected in step 5, select Allow Launch
in the Type of Access field. When you repeat this step for the
Use Custom Configuration Permissions option you selected in
step 5, select Full Control in the Type of Access field.
246
10 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.
247
14 In the Properties dialog, select This Account and enter the password
of an administrative user on the Controller.
Steps 12-14 enable the DJS to use the name and password of
the administrator you specified during DCOM configuration as
the launching user for all servers.
248
249
2 In the Component Services dialog, expand the tree in the left panel by
clicking Component Services, Computers, My Computer, DCOM
Config.
250
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.
251
7 In the Properties dialog, Security tab, click the Edit button associated
with Launch and Activation Permissions.
8 In the Launch Permission dialog, Security tab, click Add.
9 In the Select Users, Computers, or Groups dialog, enter the user group
name you created previously (for example, PrmAdmins). Click OK.
252
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.
11 In the Properties dialog, Security tab, click the Edit button associated
with Access Permissions.
253
13 In the Select Users, Computers, or Groups dialog, enter the user group
name you created previously (for example, PrmAdmins). Click OK.
254
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.
15 In the Properties dialog, Security tab, click the Edit button associated
with Configuration Permissions.
255
17 In the Select Users, Computers, or Groups dialog, enter the user group
name you created previously (for example, PrmAdmins). Click OK.
256
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.
257
258
259
Select Disabled
to disable the
DJS on that
machine. In this
example, the
Controller will
execute jobs on
the servers but
not on itself.
If you have already used the configuration tool, all servers you
previously configured appear in the list of servers (bottom grid
of previous figure).
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).
260
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 Windows Server 2000, you must
reboot the machine(s) on which you made the modifications.
261
Default
Valid Ranges/Values
EstablishDBConnectionRetryCount
1-10
1-(no maximum)
3600
60-604800
1-3600
600
60-1440
MaxNumRecurringJobs
The maximum number of recurring jobs that can run
simultaneously.
NonRecurringJobCleanupRate
Frequency (in seconds) in which completed Primaveras Web
application jobs are removed from the database (1 minute to 7
days).
NonRecurringJobRefreshRate
Frequency (in seconds) in which Primaveras Web application
jobs are loaded from the database.
RecurringJobRefreshRate
Frequency (in seconds) in which Project Management jobs are
loaded from the database.
262
[Summarizer settings]
Setting Name and Description
Default
Valid Ranges/
Values
NumProjectsSummarizedAtATime
1-xx
50
0-100
-1
Number of projects that can be summarized at the same time by the Job Service
or the Project Management module. To achieve the best possible performance,
Primavera recommends that the value of this setting = 20.
PreQuerySummarizablePct
The percentage threshold that determines how the summarizer will analyze a
projects need for summarization. If the value of the equation shown below is
less than the threshold, each project is considered for summarization individually. If the value of the following equation is greater than the threshold, all
projects to be considered for summarization are analyzed simultaneously. The
equation that determines this behavior is:
# of projects to be summarized / # of projects user can access*100.
MaxDurationToSummarize
The maximum remaining duration or the maximum original duration, in hours,
that an activity or activity assignment can have in order to be summarized. If an
activity or activity assignment has a remaining duration greater than this
threshold, it is ignored during summarization. To ensure that all activities are
summarized, Primavera recommends that the value of this setting = 100000.
263
[Summarizer settings]
Valid Ranges/
Values
Default
EnterpriseSummaries
0 (false)
0 (false)
1 (true)
1 (true)
0 (false)
1 (true)
0 (false)
0 (false)
1 (true)
ResourceSummaries
If true, resources are summarized.
Applies to the Job Service and the Project Management module.
ForceEnterpriseSummaries
If true, forces an enterprise-level summarization even when no
projects are summarized.
Applies only to the Job Service.
EnterpriseCommit
Controls how frequently to commit EPS summary records
to the database, based on the number of rows of data that
have been processed. Useful for improving performance
when summarizing large jobs.
264
[Summarizer settings]
Setting Name and Description
Default
Valid Ranges/
Values
RetrySleep
The time, in milliseconds, to wait between retry attempts
when there is a connection failure.
60000
10
MaxRetries
The maximum number of retry attempts to make when
there is a connection failure.
Applies only to the Job Service.
0 (false)
DumpSettings
Set to true to log all settings to a Job.txt file for the summarization job.
Applies only to the Job Service.
0 (false)
1 (true)
Part
267
268
269
270
271
272
273
274
275
1 On the Select Features to install dialog box, expand Other Components, expand Job Service, and choose the type of job service to
install.
Choose Job Service when:
you want to use the Distributed Job Service but the machine on
which you are installing is NOT the controller server.
276
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 2000/2003 server machine. Create one job service
instance for each database.
When installing multiple instances of the Job Service, you
should first stop all existing job services.
For more information on
running jobs on multiple
databases using the Job
Service, see Running Job
Services on Multiple
Databases on page 278.
The Job Service uses the DB alias to connect to the database server.
277
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.
9 On the Connection Successful dialog box, click Finish.
You are prompted to test the Job Service alias.
If you are installing on a SERVER machine in a Distributed Job
Services environment, DO NOT click the Test button as
described in the following step.
278
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.
279
280
281
Specify a different language for the Job Service You can specify
the output language for Job Service jobs. Complete the following steps to
specify a language other than English.
1 Complete the steps in the previous section, Configure the Job
Service to send jobs directly to a printer, to login to the Job Service
using your administrator account rather than the system account.
2 If you did not install the Project Management module when you
installed the Job Service (as described in Step 1 on page 275), install
the Project Management module on the Job Service machine.
For detailed instructions on installing the Project Management
module, refer to Installing Client Modules on page 272.
3 After the Project Management module is installed and the database
configured, start the module by choosing Programs, Primavera,
Project Management from the Start menu.
4 Login to the Project Management module using the same
administrator account you used to login to the Job Service.
5 On the Welcome dialog, choose Open Global Data Only.
6 Choose Tools, Set Language, then select the desired language.
The Job Service will run jobs in the selected language
assuming that the Job Service continues to run using the
administrator account you used to login in Step 1. If, at any
time, a different login is specified, you must repeat these steps
using the alternate login. You cannot run Job Service jobs in a
different language using the local system account.
282
1 On the Select Features to install dialog box, expand Other Components and choose Software Development Kit.
2 Click Install.
3 Click OK after reading the explanation of the remaining process.
You will be creating a DB alias named PMSDK for use with the SDK.
You will then create an ODBC user data source name (DSN) called
PrimaveraSDK. The ODBC DSN will use the DB alias to connect to
the project management database.
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.
If you are configuring Microsoft SQL Server or SQL Server Express,
on the Configure SQL Server Connection dialog box, type the
database name and server computer name.
283
6 On the Enter Public Information dialog box, enter your public login
information that was defined by your administrator; for example, a
Username of pubuser, and a group ID of 1.
7 On the Validate Database Connection dialog box, click Next to
validate the database connection.
8 On the Connection Successful dialog box, if the connection was
successful, a DB alias named PMSDK was created. Click Finish.
If the connection was not successful, click Back to re-enter the
database information.
9 On the Primavera Software Development Kit Setup dialog box,
verify that the ODBC connection values are correct for your database,
and click OK.
An ODBC DSN named PrimaveraSDK is created.
Once the SDK is installed on your computer, you can connect to the
project management database using the ODBC DSN. The SDK
documentation is located in your \Program Files\Common Files\Primavera
Common\PMSDK\Doc folder.
284
285
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 utilize MSP for daily project maintenance
while also having access to the enterprise capabilities available within
Primavera applications.
Install ProjectLink
Complete the following steps to install ProjectLink.
The following instructions assume you are installing ProjectLink
only and that you have completed the steps detailed in
Preliminary steps for installing the client modules, additional
components, and the stand-alone version on page 270.
1 On the Select Features to install dialog box, expand Other Components and choose Project Link.
2 Enter or select the program folder.
3 Click Install.
4 Click Finish when the download is complete.
After you have successfully completed the installation, Primavera
ProjectLink will appear as a toolbar in Microsoft Project. You can also
choose Tools, Primavera ProjectLink in Microsoft Project to access any
ProjectLink dialog box. ProjectLink Help is automatically installed in the
same folder in which you installed the program. You can also access
ProjectLink Help by clicking the help icon in any ProjectLink dialog box.
286
287
Be sure you check in any projects that are checked out before
you upgrade the database.
288
3 Enter the following commands to pump the data from your 4.1
Interbase PM and MM databases to 6.0 standalone databases and
upgrade their schema.
For the PM database, enter a command in the following form:
ca pump /sourcestring:db:ib:sysdba/masterkey@<database
location>pmdb.gdb /targetstring:db:ss:sa/<password>@<SQL server
name>:<PM database name> /auto /verbose /truncate /dbtype:pmdb
For example:
ca pump /sourcestring:db:ib:sysdba/masterkey@C:\Program
Files\Primavera\database\pmdb\pmdb.gdb /targetstring:db:ss:sa/
password@<machine name>\primavera:pmdb$primavera /auto /
verbose /truncate /dbtype:pmdb
For the MM database, enter a command in the following form:
ca pump /sourcestring:db:ib:sysdba/masterkey@<database
location>mmdb.gdb /targetstring:db:ss:sa/<password>@<SQL server
name>:<MM database name> /auto /verbose /truncate /dbtype:mmdb
For example:
ca pump /sourcestring:db:ib:sysdba/masterkey@C:\Program
Files\Primavera\database\mmdb.gdb /targetstring:db:ss:sa/
password@<machine name>\primavera:mmdb$primavera /auto /
verbose /truncate /dbtype:mmdb
For information about the default password for the username
sa, see prim53061 in the Primavera Knowledgebase.
289
1 On the Select Features to install dialog box, mark the checkbox next
to Sample Projects if you want to install sample projects.
2 Select the program folder name in which the Primavera icons will be
stored on the Start menu.
If you make no changes, these icons are stored under Programs,
Primavera.
If you are upgrading from a previous version, you may be
prompted that a Primavera folder already exists. Click Yes to
install version 6.0 in this folder.
3 If installing the standalone version for the first time on this computer,
on the Select License File dialog box, in the Select a license file for
the newly created database field, browse to the location of the
LICENSE.TXT file.
4 Click Install to begin the installation/upgrade.
During the installation, the setup program automatically installs and
configures Microsoft.NET Framework and Microsoft SQL Server
Express. The setup also installs/upgrades the project management and
methodology management databases.
If a Primavera MSDE instance is already present on your
computer, the setup will upgrade it to a SQL Server Express
instance.
291
292
293
6 On the Product Code dialog box, enter the product key located on the
CD 1 label.
7 Accept the license agreement.
294
295
16 On the Select Driver Type dialog box, choose the database type from
the list in the Project Management driver type field.
17 If users will be connecting using SQL Server, on the Configure SQL
Server Connection dialog box, enter the server host name and the
database name. The host name is the name of the computer or IP
address where Microsoft SQL Server is installed. The database name
was specified when the database was created; for example, PMDB.
If users will be connecting using Oracle, on the Configure ORACLE
Connection dialog box, enter the Oracle connection string; for
example, PMDB.
Before you enter the database information, confirm that all
users with administrator privileges who will be running the
unattended setup have access to the specified database.
296
297
If you are unsure of the location of the unattended setup file, refer to
your system administrator.
3 Enter a command line to run the unattended setup, where pathname =
the directory you accessed in Step 2 (e.g., Primavera_install). For
example:
setup.exe /s /f1"e:\pathname\setup.iss" /f2"c:\pathname\setup.log"
Do not include a space between the f1 and f2 and the quote ".
299
300
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.
6 Type the new connection settings for the database.
If the client computer is connecting to an Oracle database, on the
Configure ORACLE Connection dialog box, type the connection
string, which can be found in the TNSNAMES.ORA file.
301
302
303
304
305
306
Authentication in Primavera
Typically, within an organization, 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 Primaveras Web
application. In this mode, when a user attempts to log in to a
Primavera module (protected resource), a Web agent intercepts the
request and prompts the user for login credentials. The users
credentials are passed to a policy server and authenticated against a
user data store. With Single Sign On, a user logs on only once and is
authenticated for all Web applications for the duration of the browser
session (provided that all Web applications authenticate against the
same policy server).
307
308
Process Overview
By default, all Primavera modules are installed using Native
authentication. After you install Primavera client/server modules and
additional components, you can choose a different authentication scheme.
To specify an authentication scheme:
The Borland Database
Engine and the database
client software must be
installed on the machine
used to run the
Authentication
Configuration wizard.
309
310
2 Select the database alias you want to provision LDAP information for,
then type the database user name and password.
311
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.
312
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.
For Primaveras Web application, if choosing SSL, you will need
to configure two settings that identify the location and password
for the keystore that holds the SSL certificate. For details about
configuration settings for Primaveras Web application, see
Installing Primaveras Web App on page 125.
313
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.
314
USER_NAME is a required
field that must be mapped
and can not be deleted. Up
to four fields can be
mapped between the
LDAP store and the project
management/methodology
management database.
315
10 To import from an LDIF file, click Load LDIF, then navigate to the
file you want to import and click OK.
To import from an LDAP server, you can run an existing search or
define a new search.
If one or more previously defined searches exist, the name of the most
recently run search is displayed next to the Search Name drop-down
list. To initiate the current search, click Run Search. Results display in
the Available Users section. To specify a new search, click Define
Criteria.
316
Displays the
name of the
current search.
Starts the
search based
on the filter
selected in the
Search Name
drop-down list.
Click to save
information
for the
selected
users to the
Primavera
database.
Click to
remove the
current search
results or
currently
selected
users.
317
To add a search, click Add. Type a unique name for the search. In
the Search criteria field, specify the LDAP search filter you want
to use. When finished specifying criteria, click Save, then click
Close.
Search filter syntax should adhere to the rules outlined in RFC
2254.
318
319
320
In LDAP mode
321
322
You can create a set of profiles that limit access to global information and
then assign the appropriate global profile to each user. Similarly, to limit
privileges for each project, you assign the appropriate project profile to
each user via an organizational breakdown structure (OBS) element.
When you create the EPS for your company, you must identify an OBS
element, or person responsible, for each node and project within the EPS.
This OBS element assignment determines the users rights to the EPS level
(and all levels below it). You can further control access to specific project
data by assigning a responsible OBS element to each work breakdown
structure (WBS) element within a project. You can also control user access
to resource data by implementing resource security.
The following diagram illustrates the relationships between a user, the
OBS, EPS, and WBS. If a user will be accessing Timesheets to update
time, he/she will also need to be associated with a resource in the Project
Management module.
Timesheets Resource
User
OBS
License
Resource Security
EPS
WBS
Project Profile
Global Profile
323
324
Oak
County
Water/
Sewer
Dept
Dept of
Transport
Major
Streets
Highway
101 Project
Bridges
Pine Ave
Project
WBS.1
WBS.2
Green Lane
Project
Hickory
Bridge
325
State of PA
Labor Mgmt
President
Dept of
Transportation
Engineering
Division
Management
Director
Water/Sewer
Department
Project
Controls
Engineer
Project
Manager
Management
Engineering
Division
Design
Team
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 Controls
Coordinator profile), and one that allows viewing and editing of most, but
not all, project data (the Project Management module profile). Joe Nolan,
the President of Labor Management, is assigned to the Project Controls
Coordinator profile. The OBS element, Labor Mgmt President, is assigned
as the responsible manager at the Oak County node of the EPS, indicating
that Joe Nolan has access to all nodes and projects within Oak County.
326
Capital
Improvement
Labor
Management
President
Joe Nolan - PCC
Oak
County
DOT
Water/
Sewer
Dept
Dept of
Transport
Director
Major
Streets
Highway
101 Project
Bridges
Pine Ave
Project
Green Lane
Project
Hickory
Bridge
WBS.1
WBS.2
Project Profiles:
Project Controls Coordinator (PCC)
Project Manager (PM)
You can further control the access to projects by assigning OBS elements
at the project and/or WBS level. In the previous example, if Marie Ross is
the Project Manager in the Engineering Division responsible for the
Highway 101 project, you can assign her to that OBS element with a
Project Manager profile. She would then have editing access to just that
project.
327
As another example, if the Design Team needs access to only the design
portion of the Highway 101 Project. You can assign the Design Team to
just the WBS branch in the Highway 101 project that involves the project
design.
You can assign multiple users to the same OBS element and/or you can
assign each user to multiple OBS elements. This flexibility enables you to
provide access to the same EPS branch or project to more than one
responsible manager (OBS element), and it allows you to control access
by the same user across different EPS nodes and projects.
For example, suppose Marie Ross, who is a Project Manager in the
Engineering Division responsible for the Highway 101 project, also needs
access to the Pine Avenue project; however, you want to limit her access to
reviewing and editing financial data only. Also suppose that Jim Harkey,
another Project Manager in the Engineering Division, is responsible for
the Pine Avenue project. He needs Project Manager access to the Pine
Avenue project, but he also needs to review financial information in
Maries Highway 101 project.
328
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:
OBS Assignments to the EPS
Capital
Improvement
Labor
Management
President
Joe Nolan - PCC
Oak
County
DOT
Director
Water/
Sewer
Dept
Dept of
Transport
Major
Streets
DOT
Project
Manager
Highway
101 Project
Marie Ross - PM
Jim Harkey - AM
WBS.1
WBS.2
Bridges
Pine Ave
Project
Green Lane
Project
Hickory
Bridge
Project Profiles:
Project Controls Coordinator (PCC)
Project Manager (PM)
Account Manager (AM)
329
To designate that Jim Harkey has Project Manager rights to the Pine
Avenue project and Marie Ross has Account Manager rights to the Pine
Avenue project, you would need to add another element to the OBS.
Capital
Improvement
Labor
Management
President
Joe Nolan - PCC
Oak
County
DOT
Director
Water/
Sewer
Dept
Dept of
Transport
Major
Streets
Highway
101 Project
WBS.1
WBS.2
Bridges
Pine Ave
Project
Green Lane
Project
Hickory
Bridge
Project Profiles:
Project Controls Coordinator (PCC)
Project Manager (PM)
Account Manager (AM)
With these assignments, Jim Harkey and Marie Ross now have Project
Manager rights to their primary projects and Account Manager rights to
their secondary projects.
The following section provides guidelines for setting up users and
administering security in Primavera.
330
Process Overview
Organization-wide 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 organization are essential. Before you can use
Primavera to manage your projects successfully, you must first administer
users and set up structures in the Project Management module, including
the organizational breakdown structure (OBS), enterprise project structure
(EPS), and resource hierarchy. Once users and structures are in place, you
can implement security to restrict and/or provide access to project data.
The Methodology
Management module uses its
own security model to control
access to the methodology
management database. See
Setting Security in the
Methodology Management
Module on page 370.
331
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
Reference Manual
(PMRefMan.pdf) is
available online and can be
accessed from your
industry-specific folder in
the \Documentation folder
of CD 3. View the
information using Adobe
Acrobat Reader (available
on CD 3).
Project managers perform this step. They can further control security
within their own projects by assigning 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.
The remainder of this chapter provides additional information on this
process.
332
333
Select a global
profile...
334
Privilege Name
Privilege Definition
Add Resources
Edit Resources
Approve Resource
Timesheets
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 Create
P3*
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*
Edit Roles
335
Privilege Name
Privilege Definition
Delete Global Activity Delete global activity codes and code values. This
Codes
privilege automatically enables you to add and edit
global activity codes and code values as well.
Edit Issue Forms
Edit Resource
Calendars
Edit Users
Add/Edit Global
Activity and
Assignment Layouts
and Filters
Edit OBS
336
Privilege Name
Privilege Definition
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
Administer Global
External Applications
Administer Job
Services
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
Primaveras Web application.
Primavera - Administrators Guide
Privilege Name
337
Privilege Definition
338
Privilege Name
Privilege Definition
Add/Edit Global
Project/WBS Layouts
and Portfolio Views*
Edit Global Issue Codes Edit issue codes and issue code values in Primaveras
Web application. Enables access to the Issues menu in
Primaveras Web application.
Delete Global Issue
Codes
Edit Global Scenarios* Create, edit, and delete global scenarios in the Portfolio
Management module of Primaveras Web application.
Edit Global
Dashboards*
339
Project profiles are applied to users via OBS assignments. The Project
Management module requires that all EPS and WBS elements, and
projects, are assigned a responsible OBS. The combination of the project
profile/user assignment to an OBS assignment, and the OBS assignment to
the EPS/WBS, determines which projects and data the user can access.
Create project profiles Choose Admin, Security Profiles. Choose
Project Profiles, then click Add. Type the new profiles name. To make the
new profile the default project profile, mark the Default checkbox. In the
Privilege area, mark the appropriate Has Privilege checkboxes to grant
privileges to the profile.
340
To allow read-write
privileges for all aspects of
a project, you can assign a
user to a projects root
OBS element and then
apply the Project
Superuser profile to the
OBS assignment.
Privilege Name
Privilege Definition
Summarize Project
Administer Project
External Applications
Schedule Project
Schedule a project.
Level Resources
Apply Actuals
Store Period
Performance
Store actual this period values for actual units and costs
in a projects financial periods. A user must be assigned
the Add/Edit Project Activities Except Relationships
project privilege before you can assign this privilege.
Edit Period
Performance
Maintain Project
Baselines
Privilege Name
Privilege Definition
341
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
Products and
Documents
Add/Edit Project
Template Documents
Delete Project Activity Remove a projects activity codes from the project
Codes
database.
Edit EPS Activity
Codes
342
Privilege Name
Privilege Definition
Monitor Project
Thresholds
View Timesheets in
Reports*
Import/View Contract
Manager Data
Project Top-Down
Estimation
Approve Timesheets
as Project Manager
Edit Project
Thresholds, Issues
and Risks
343
Privilege Name
Privilege Definition
Add/Edit Project
Activities Except
Relationships
Perform Activity
Resource Requests
Delete Project
Activities
Delete Project
Data with Timesheet
Actuals
Create Workgroups
Delete Workgroups
Modify Project
In Primaveras Web application, customize the project
Workspace and
workspace and workgroup preferences.
Workgroup Preferences
Edit Resource
Assignments for
Resource Planning*
Edit Contract Manager Create, edit, and delete a link to a Primavera Contract
Project Link
Manager project.
Edit Activity ID
344
Privilege Name
Privilege Definition
Add/Edit Project Level Create, edit, and delete project level layouts in
Layouts*
Activities, Assignments, or WBS views.
345
Add new users Choose Admin, Users. Click Add. Click the General
tab, type the users login name and personal name, then click Password.
Type the users password, then retype the password to verify it. Click OK.
If the user will be accessing Timesheets, you can associate the user with a
resource in the Project Management module at this time, or you can create
the link when you add resources. Click the Contact tab and type the users
e-mail address and telephone number.
346
347
348
349
350
351
import appointments
352
Dashboards
In the Dashboards section of the Primavera Web application, Team
Member-licensed users can create private and multi-user dashboards,
create private and multi-user portfolios, and import appointments.
Dashboard portlets display data for projects the user is associated with that
meet the criteria of the specified Dashboard Filter. Together, a users
association with a project, OBS access, and security privileges, determine
the level of view and edit access that is granted to project data. A licensed
Team Member can be associated with a project via OBS access, by
assignment as an activity resource, through invitation to join a project, and
by assignment as activity owner in a Reflection project.
The Reflection project and Activity Owner features can be used
together to collect and review activity progress information from
licensed Team Members who are not assigned as activity
resources and who do not use the Timesheets application for
status reporting. For more details, refer to Using Reflection
projects and Activity Owner features to collect and review
activity status in the Project Management Help.
My Projects
My Workgroups
My Activities
Communication Center
My Events
My Calendar
My Reports
Action Required
Cost Worksheet
Custom Portlet
353
Projects
In the Projects section of the Primavera Web application, Team Memberlicensed users can access the Projects Home page, the Project Workspace,
and the Activities tab.
The Projects Home page displays all projects to which the user has OBS
access, all projects in which the user is assigned as an activity resource, all
Reflection projects in which the user is designated as an activity owner,
and all projects the user is invited to. From the Projects Home page, a
Team Member-licensed user can create and edit private and multi-user
activity views.
The Activities tab in the Projects section displays all activities the user is
associated with either as an assigned resource or as an activity owner.
Users who are associated with activities, but who do not have OBS access
rights, can view, print, and export data but can not access features and
functions that change project data. For example, they can not edit activity
data in the table, modify the Gantt chart, or modify activity details. Users
associated with activities who have OBS access to the project and the
required security privileges can access and edit activity details, edit fields
in the activity table, modify Gantt Chart bars, establish relationships, and
view cost information.
Team Member-licensed users can not add/delete activities or
add/edit WBS elements.
Primavera - Administrators Guide
354
Project Risks Users can view, but not add or edit, project risks.
Project Notebooks Users can view, but not add or edit, project
notebooks.
Overallocated Resources
Milestone status Users can view all milestone activities for the
project. For users without OBS access to the project, all activity
details accessed from this portlet are read-only. For users with
OBS access to the project, users can edit activity details accessed
from this portlet if they have the appropriate security privileges
and are a resource on the activity or are the activity owner.
Project Reports
Project Discussions
Project Events
News
Communication Center
Project Calendar Users can view all activities for the project
scheduled for the selected week. For users without OBS access to
the project, all activity details accessed from this portlet are readonly. For users with OBS access to the project, users can edit
activity details accessed from this portlet if they have the
appropriate security privileges and are a resource on the activity or
are the activity owner.
355
Workgroups
Custom Portlet
All other Project Workspace portlets are not available to Team Memberlicensed users.
The Communication Center, News, Project Discussions, Project
Documents, and Workgroups portlets are only available if the
Primavera Web application is installed with collaboration
functionality. Additionally, some functionality within available
portlets requires collaboration functionality to be installed.
356
357
358
You can assign a user an OBS element and a corresponding project profile
in the Users dialog box when you are adding users, or you can make the
assignment in the OBS dialog box during or after creating the OBS.
The Project Management module does not require that each
user have a project profile; however, a user cannot access a
project without a project profile or the global profile, Admin
Superuser.
359
Double-click to select
another project profile. To
grant the user read-write
privileges for all aspects of a
project, select Project
Superuser.
360
Assign OBS elements and project profiles to users You can also
assign OBS elements and project profiles to a user when you first add the
user. Choose Admin, Users. Click the Project Access tab. Select the user to
whom you want to assign an OBS element and project profile, then click
Assign. Select the OBS element associated with the user, then click the
Select button. A default project profile is associated with the user. Doubleclick the project profile to choose another profile from the predefined list.
If an OBS element is the Responsible Manager for several
projects in the EPS, any user you associate with that OBS
element will have access to all the corresponding projects.
361
362
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.
363
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.
364
You can grant one of the following three types of resource access to each
user:
365
366
367
To provide all resource access to the selected user, mark the All
Resource Access checkbox.
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.
368
369
You can also utilize user interface views to hide Primavera Web
application functionality your organization does not use. For example, if
your organization does not use Primavera Timesheets for time reporting,
you can hide the Approve Timesheets Action Bar item in the Resources
section and the Timesheet Approval tab in the Projects section.
Assign a user interface view to a user in the Project
Management module Choose Admin, Users. Select the user to whom
you want to assign a user interface view, then click the Global Access tab.
In the User Interface Views section, click the Browse button to select a
user interface view. Mark the 'Enable user to modify view settings'
checkbox if you want to enable the user to change personal user interface
view settings in the Primavera Web applications View Preferences.
In addition to customizing
the Primavera Web
application 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 the Primavera Web
application on page 356.
370
371
Select a global
profile...
372
Privilege Name
Privilege Definition
Edit Users
Edit Resources
Edit Roles
Edit Work Products and Create, delete, and change work product and document
Documents
records.
Import Global /
Methodology
Information
Edit Reports
Edit OBS
Edit Methodology
Codes and Resource
Codes
373
Privilege Name
Privilege Definition
374
Privilege Name
Privilege Definition
Edit Methodology
Properties
Edit Methodology
WBS
Edit Methodology
Links
Edit Methodology
Activities
Edit Methodology
Expenses
View Methodology
Costs
Edit Methodology
Risks
Edit Activity ID
375
Add new users Choose Admin, Users. Click Add. Click the General
tab, type the users login name and personal name, then click Password.
Type the users password, then retype the password to verify it. Click OK.
If the Methodology Management module is running in LDAP
authentication mode, when you click Add, a dialog appears for
you to enter a user name and verify it against the LDAP store.
When you click Test, if the user exists in the LDAP store, the
actual name, e-mail address, and telephone number fields are
populatedif you previously mapped those fields through the
Authentication Configuration tool. To add the user, click Add.
When you click Test, if the user is not found in the LDAP store, a
message appears to notify you that the user cannot be added.
376
Product licensing You do not need to assign product licensing for the
Methodology Management module. For each license of the Project
Management module that you have purchased, you automatically are
granted one license of the Methodology Management module.
Assign a global profile and methodology profiles A global
profile determines a users access to global data, such as resources and
roles; methodology profiles restrict the users access to methodology data.
The Methodology Management module requires that each user be
assigned a global profile. To open a methodology, the user must be
assigned a methodology profile for that methodology. Choose Admin,
Users. Select the user to whom you want to assign a global profile and
methodology profiles. Click the Methodology Profiles tab.
Double-click in the
Global Profile column
and choose the
appropriate profile for
the selected user.
Click to select a
methodology to which the
user requires access...
377
Implementing Timesheets
379
Implementing Timesheets
In this chapter
Implementation Overview
Setting Timesheet Preferences
Configuring Resources to Use
Timesheets
Creating Timesheets for
Timesheets Users
Setting Project-Specific
Timesheets Preferences
Using Overhead Codes
Running Timesheets Web
Browser Version and Java Web
Start Version
380
Implementation Overview
Timesheets enables project team members to use the web to communicate
timesheet and activity status directly to their organizations database,
regardless of their location. This ensures that project managers are always
working with the most up-to-date project information, making it easier to
plan resource use or resolve conflicts.
Timesheets consists of the Timesheets client, the database server that
contains your organizations projects, and the Group Server, which links
the Timesheets client and database server.
Installation and configuration of Timesheets is slightly different
for the Web Browser version and the Java Web Start version.
Refer to Configuring the Group Server for Timesheets on
page 91 for complete details on how to configure either version
of Timesheets.
Before you implement Timesheets, first ensure that the following steps
have been completed:
If you are using Timesheets Java Web Start version, configure Java
Web Start as described in Setting up Java Web Start for Timesheets
on page 112.
Implementing Timesheets
381
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:
Create timesheets.
382
Implementing Timesheets
383
384
Implementing Timesheets
385
386
Implementing Timesheets
387
388
Implementing Timesheets
389
4 Click to select an
approval manager.
Set overtime policy You can enable users to enter overtime in their
timesheets. In the Project Management module, choose Enterprise,
Resources, then click the Details tab. Mark the Overtime Allowed
checkbox. Type the overtime factor by which the resources standard price
is multiplied to determine the overtime price (standard price * overtime
factor = overtime price).
Resources indicate overtime with a slash (/) in the time field.
For example, if a resource worked 10 hours in one eight-hour
day, the user types 8/2 for that day.
Primavera - Administrators Guide
390
To create another set of timesheets, reset the batch start and end dates,
select the appropriate timesheet period, then click Batch Create.
Create a single timesheet In the Project Management module,
choose Admin, Timesheet Dates. Click Add.
You cannot create new timesheets that have start and end
dates that overlap existing timesheet dates.
Primavera - Administrators Guide
Implementing Timesheets
391
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 begin next.
392
Implementing Timesheets
393
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).
<Web server>/GroupServer/App/index.html.
For example, http://10.12.14.123/Groupserver/App/index.html.
If the Web Server is not using the default port, you must enter
the port number after the IP address separated by a semicolon
(:).
394
If the required JRE version is present, Java Web Start uses the
existing JRE.
Implementing Timesheets
395
397
398
You can upgrade your database automatically using the Database wizard.
The wizard runs the necessary scripts to upgrade the database structure
and an upgrade program to add data required by the new version.
To upgrade from version 4.1 or 5.x The following list summarizes
the steps required to upgrade to version 6.0:
399
If you are currently running Primavera with Microsoft SQL Server, see
Upgrading a Microsoft SQL Server Database to Version 6.0 on
page 402.
400
The upgrade will fail if you are using any Oracle version prior to
9.2.0.7.
In the Key field, enter the product key located on the CD 1 label.
401
402
In the Key field, enter the product key located on the CD 1 label.
403
In the System Admin Password field, type the password for the
user.
In the Server Name field, specify the name of the server machine
you are connecting to.
In the Database Name field, specify the name of the database you
are connecting to.
Part
407
Project, resource, and role data can be transferred from one Project Management module
user to another Project Management module
user by exporting and importing XER files
(Primavera proprietary exchange format).
Project data can also be exchanged between
Project Management databases in XML
format. This chapter describes how to use the
Export and Import wizards to share project
information and roles/resources.
408
Exporting Projects
For information about
importing XER and XML
files, see Importing Projects
on page 417.
For information about the
tables and fields that are
converted in XER format, see
the XERPROJECTS.PDF
file, located in the
\Documentation\Technical
Documentation\Data
Mapping Docs folder on CD
3.
You can transfer project data from the Project Management module as
XER files (Primavera proprietary exchange format) or XML files, which
can be used with any other Project Management module installation,
regardless of the database type on which it runs. Use the Export wizard to
export Project Management projects.
When you export project data, some data is not exported,
including timesheets and baselines. You can export secure
codes and secure code assignments to XML format, if you have
the correct access; however, you cannot export them to XER
format. For more information about secure codes, refer to the
Defining Global Profiles on page 332.
409
XML
Data formats
XML is an industry-standard format, while XER
is proprietary.
XER
Multiple projects
XER supports exporting multiple projects at
once, to a single XER file.
XML exports only a single project to a separate
XML file, at a time.
Job Service
XER supports scheduling exports on a regular
basis as services.
XML does not.
410
411
Clear the Export checkbox next to each project that should not be
exported, then click Next.
Specify filename and location Type a name for the XER file. To
specify a different location to store the file, click the Browse button. If
you do not specify a folder, the file is stored in the My Documents folder
of the current user. Click Finish to export the project to a single file with
an XER extension.
412
You must have the appropriate access rights to set up job services. The Job
Service does not interact with the Project Management client when
running jobs. All jobs are run on the server on which the Job Service is
installed.
413
If multiple projects are open, select the Export checkbox next to the single
project that you want to export. You can select only one project when
exporting to XML format. Then click Next.
414
Specify filename and location Type a name for the XML file. To
specify a different location to store the file, click the Browse button. If you
do not specify a folder, the file is stored in the My Documents folder of the
current user. Click Finish to export the project to a single file with an
XML extension.
415
The Project Management module enables you to export only the roles or
resources in your resource hierarchy to XER files. You might want to
choose this option to include existing roles or resources in a new database.
When you export roles and resources, secure codes and
secure code assignments related to the roles and resources
are not exported. For more information about secure codes,
refer to Defining Global Profiles on page 332.
416
Type a name for the XER file. To specify a different location to store the
file, click the Browse button. If you do not specify a folder, the file is
stored in the My Documents folder of the current user. Click Finish to
export the roles or resources to a single file with an XER extension.
Click to
select the
location
where the
file will be
stored.
417
Importing Projects
For information on exporting
project data, see Exporting
Projects on page 408.
For information about the
tables and fields that are
converted in XER files, see
the XERPROJECTS.PDF
file, located in the
\Documentation\Technical
Documentation\Data
Mapping Docs folder on CD
3.
You can transfer project data to the Project Management module as XER
files (Primavera proprietary exchange format) or XML files, which can be
used with any other Project Management module installation, regardless
of the database type on which it runs. You can use the Import wizard to
bring XER or XML files into the Project Management module. You can
also use a command line (batch) interface to import XER files. You might
want to use these methods to quickly restore one or more projects. The
Import wizard guides you through the steps for importing projects.
When you import project data, some data is not imported,
including timesheets and baselines. You can import secure
codes and secure code assignments to XML format, if you have
the correct access; however, you cannot import them to XER
format. For more information about secure codes, refer to
Defining Global Profiles on page 332.
418
XML
Security.
XML always enforces individual user security
settings, and never violates your security restrictions. If there is a security conflict, the import
will try will continue and ignore data that a user
should not have access to; if it is not possible to
continue while ignoring data, the import is
stopped. Security is never bypassed when
updating data.
XER allows updates to all data if you have the
Import Global Data security privilege set.
Committing Data
XML will not commit partial data. If an import
action for a specific transaction fails before all
data is committed, XML rolls back the data;
global and project-specific imports are treated as
separate transactions.
XER can end up with partial commits of data.
subset only
XER
XML
Functionality
419
XER
Multiple projects
XER supports importing multiple projects at
once, from a single XER file.
XML imports only a single project, from a
separate XML file, at a time.
Documents
XER supports importing documents that are not
related to collaboration, such as work products
and other documents.
XML does not.
Version Checking
XER checks project versions while importing,
and ensures you cannot import projects older
than 2 prior releases.
XML does not; instead, if there is a version
incompatibility, bad data is ignored.
420
421
Click the
Browse
button to
select the
file you
want to
import.
Click
Next.
Specify import project options An XER file can contain data from
several projects. The first column in the Import Project Options dialog box
lists all the projects included in the XER file. If a project with the same
name already exists in the current installation of the Project Management
module, the Match checkbox next to it is marked.
422
Create New Project The existing projects data remains the same. A
new project is created. Click the Import To field to select where the
new project will be placed in the EPS. A number is appended to the
end of the project name. When the import is complete, you can
rename the project. For example, if you are creating a new project
from the existing project, AUTO, the new project is named AUTO-1.
You must select the Create New Project option if you want the
Project Management module to import past period actual data.
If you choose any other option, past period actual values are
not imported. If you select the Create New Project option, past
period actual data will only be imported if the defined financial
periods are exactly the same in both databases.
Add Into Existing Project You can merge the project you are
importing within an existing project. Click the Import To field, then
select a specific WBS level within an existing project. The imported
project is appended to the selected WBS.
423
424
The Modify Import Configuration dialog box lists the data types for which
you can set options. Mark the Delete checkbox next to a data item to
remove data that exists in the project you are updating, but is not included
in the file you are importing. For example, if several activities are defined
in the project you are updating, but they are not included in the file to be
imported, mark the checkbox in the Delete column to remove the activities
from the project being updated.
The Delete field applies only to risks, relationships to external
projects, thresholds, activities, activity relationships, and activity
resource assignments. Global data types are not affected by
this setting.
Primavera - Administrators Guide
425
Select one of the following in the Action field to indicate how the data
type is updated:
Keep Existing Retains data in the existing project and does not
overwrite it with the updated data; adds new data if the record does
not exist.
Insert New Retains data in the existing project and adds any new
data items. For example, if a new role was added in the XER file, but
you dont want to change the existing roles, choose Insert New to add
the new role to the existing project.
Do Not Import Retains data in the existing project and does not
import the updated data.
If you manually plan future period assignments to activities, be sure to
select the appropriate import action when importing data; otherwise,
manually-planned future period assignment values may be lost. For
example, if you are updating an existing project with imported data and
you choose to import activity resource assignments, future period
assignment values that exist in the project you are importing will
overwrite future period assignment values in the project you are
updating. Therefore, if the project you are importing does not contain
manually-planned future period assignment values and the project you
are updating does contain manually-planned future period assignment
values, the manually-planned future period values will be lost when the
same assignment exists in both projects.
The action you choose for importing the items in the Activity Data Type
group are dependent on each other. For example, if you choose to update
existing relationships, you must also update existing resource assignments
and activities associated with the relationships.
426
427
Click the
Browse
button to
select the
file you
want to
import.
Click
Next.
428
Specify import project options An XML file can contain data from
only one project. Select the appropriate import action and click Next.
Create New Project The existing projects data remains the same. A
new project is created. Click the Import To field to select where the
new project will be placed in the EPS. A number is appended to the
end of the project name. When the import is complete, you can
rename the project. For example, if you are creating a new project
from the existing project, AUTO, the new project is named AUTO-1.
429
430
The Modify Import Configuration dialog box lists the data types for which
you can set options. Mark the Delete checkbox next to a data item to
remove data that exists in the project you are updating, but is not included
in the file you are importing. For example, if several activities are defined
in the project you are updating, but they are not included in the file to be
imported, mark the checkbox in the Delete column to remove the activities
from the project being updated.
The Delete field applies only to risks, thresholds, activities,
activity relationships, and activity resource assignments. Global
data types are not affected by this setting. External
relationships are not treated as a separate data type in XML
import; they are in XER import.
431
Select one of the following in the Action field to indicate how the data
type is updated:
Keep Existing Retains data in the existing project and does not
overwrite it with the updated data; adds new data if the record does
not exist and you have the appropriate security privileges.
Insert New Retains data in the existing project and adds any new
data items. For example, if a new role was added in the XML file, but
you dont want to change the existing roles, choose Insert New to add
the new role to the existing project.
Do Not Import Retains data in the existing project and does not
import the new or updated data.
The Activity Resource Assignments item includes role
assignments.
432
To use the Windows command line interface to import an XER file, do the
following:
1 Copy the file actiontemplate.xml from the \Support\CmndLineImport
folder of CD 3) and edit it to specify the EPS you want to import the
project to, the layout you want to use, and the XER file you want to
import from.
You can specify more than one import action in a single file, by
including multiple <action> nodes.
433
Tag
Description
<type>
<importFormat>
<importType>
<importAction>
<importTo>
<importConfiguration>
<importFile>
434
Internationalization Notes
If you include non-English characters in the actions.xml file, save the file
as Unicode, and use the XML encoding attribute to specify the language,
prior to the <actions> tag. For example, to specify German or French
encoding:
<?xml version=1.0 encoding=windows-1252?>
If you are using a batch file, use the chcp command to specify the appropriate language encoding. See Microsoft.com for details.
2 Close the PM module if it is running.
3 From the Windows command line, a batch file, or code, issue a
command in the following form from the folder where PM.EXE is
located:
PM.EXE /username=<name> [/password=<name>] [/alias=<name>]
/actionScript=<path> [/logfile=<path>]
Parameter
Description
/username=<name>
/password=<name>
/alias=<name>
For example:
PM.EXE /username=admin /password=admin /alias=PMDB
/actionScript=c:\somefolder\importprojects.xml /logfile:c:\somefolder\myLog.txt
435
If any values include spaces, enclose the value in double quotes ().
For example:
PM.EXE /username=admin /password=admin /alias=PMDB
/actionScript=c:\some folder\importprojects.xml
/logfile=c:\some folder\myLog.txt
Processing results are written to the log file, or you can echo them to the
command line interface. Possible results are:
Code
Description
Success.
Invalid alias.
436
The Project Management module enables you to import XER files that
contain only roles or resources. You might want to choose this option to
add new roles/resources to the resource hierarchy or overwrite the existing
role/resource hierarchy. Roles and resources are defined at the global
level.
When you import roles and resources, secure codes and
secure code assignments related to the roles and resources
are not imported. For more information about secure codes,
refer to Defining Global Profiles on page 332.
437
The data in the import file must match the type being imported.
For example, you cannot import resource data from an XER file
that contains project data.
438
439
Select one of the following in the Action field to indicate how the roles or
resources are updated:
440
441
442
Exporting Methodologies
For more information about
importing methodologies as
XER files, see Importing
Methodologies on page 446.
443
Specify filename and location Type a name for the XER file. To
specify a different location to store the file, click the Browse button. If
you do not specify a folder, the file is stored in the My Documents folder
of the current user. Click Finish to export the methodology to a single file
with an XER extension.
444
445
Type a name for the XER file. To specify a different location to store the
file, click the Browse button. If you do not specify a folder, the file is
stored in the My Documents folder of the current user. Click Finish to
export the roles or resources to a single file with an XER extension.
Click to
select
the
location
where
the file
will be
stored.
446
Importing Methodologies
For more information on
exporting methodologies, see
Exporting Methodologies
on page 442.
447
Select the action to take with the imported data If you have a
methodology open when you import, you are prompted to choose an
action. Choose one of the following actions, then click Next:
448
449
The Modify Import Configuration dialog box lists the data types for which
you can set options. Mark the Delete checkbox next to a data item to
remove data that exists in the methodology you are updating, but is not
included in the file you are importing. For example, if several activities are
defined in the methodology you are updating, but are not included in the
file to be imported, mark the checkbox in the Delete column to remove the
activities from the methodology being updated.
The Delete field applies only to activities, activity cores, and
risks. Global data types are not affected by this setting.
Select one of the following in the Action field to indicate how the data
type is updated:
Keep Existing Retains data in the existing methodology and does not
overwrite it with the updated data; adds new data if the record does
not exist.
450
Insert New Retains data in the existing methodology and adds any
new data items. For example, if a new role was added in the XER file,
but you dont want to change the existing roles, choose Insert New to
add the new role to the existing methodology.
451
452
The data in the import file must match the format being
imported. For example, you cannot import a project from an
XER file that contains only role or resource data.
453
Click the
Browse
button to
select the
file you
want to
import.
Click Next.
454
Select the source data for estimates You use either the actual
effort and cost data from the project or the projects planned data as the
basis of the methodologys effort and cost estimates.
455
456
The Modify Import Configuration dialog box lists the data types for which
you can set options. Mark the Delete checkbox next to a data item to
remove data that exists in the methodology you are updating, but is not
included in the file you are importing. For example, if several activities are
defined in the methodology you are updating, but are not included in the
file to be imported, mark the checkbox in the Delete column to remove the
activities from the methodology being updated.
The Delete field applies only to activities, activity cores, and
risks. Global data types are not affected by this setting.
Select one of the following in the Action field to indicate how the data
type is updated:
Keep Existing Retains data in the existing methodology and does not
overwrite it with the updated data; adds new data if the record does
not exist.
Insert New Retains data in the existing methodology and adds any
new data items. For example, if a new role was added in the XER file,
but you dont want to change the existing roles, choose Insert New to
add the new role to the existing methodology.
457
458
The data in the import file must match the format being
imported. For example, you cannot import resource data from
an XER file that contains project data.
459
Double-click to select
the action to take
when duplicate data is
encountered.
Select one of the following in the Action field to indicate how the roles or
resources are updated:
460
461
462
Exporting Projects
For information about the
fields that are converted, see
MSPMAPPINGS.PDF or
MPXMAPPINGS.PDF,
located in the
\Documentation\Technical
Documentation\Data
Mapping Docs folder on CD
3.
Select export type and project Open the projects in the Project
Management module you want to export. Choose File, Export. Choose
Microsoft Project and select the type of file to which you want to export,
then click Next.
Microsoft Projects MPX file format does not support resource
curves. Therefore, if the project(s) you are exporting contain
resource curves or manual assignment values (manual curves),
you should select a different export file format to retain these
values.
463
Clear the Export checkbox next to each project that should not be
exported. Double click in the Export File Name field if you want to change
the name and location of the Microsoft Project file. If you do not specify a
folder, the file is stored in the My Documents folder of the current user.
Click Next.
464
465
Click the Activity tab in the Modify Template dialog box. In the Export
section, choose the text field to which to export the Activity ID from the
Project Management module. If you choose not to export the Activity ID
to a text field in Microsoft Project (the checkbox is not marked), the
Project Management Activity ID is not exported to Microsoft Project.
Click the Notebooks tab in the Modify Template dialog box. Notebook
fields are defined in the Project Management module in Admin Categories
(choose Admin, Admin Categories, then click the Notebook Topics tab).
These notebook fields can be exported to project, WBS, and activity notes
fields in Microsoft Project.
466
Click the Custom Field Mappings tab in the Modify Template dialog box.
To export your user-defined fields to a particular Microsoft Project field,
select the user-defined field in the Project Management Field column.
467
468
Exporting Resources
For information about the
fields that are converted, see
MSPMAPPINGS.PDF or
MPXMAPPINGS.PDF,
located in the
\Documentation\Technical
Documentation\Data
Mapping Docs folder on CD
3.
The Project Management module enables you to export only the resources
in your resource hierarchy. When you export the Project Management
modules resource data to MPX, MPP, or XML format, you can then
import the file into Microsoft Project. MPX files can also be imported into
other software applications that support the MPX format. The Export
wizard guides you through the steps for exporting resources.
When you export resources, secure codes and secure code
assignments related to the resources are not exported. For
more information about secure codes, refer to Defining Global
Profiles on page 332.
469
470
Type a name for the MPX/MPP/XML file. To specify the location where
the file will be stored, click the Browse button. If you do not specify a
folder, the file is stored in the My Documents folder of the current user.
Click to
select the
location
where the
file will be
stored.
471
Click the Custom Field Mappings tab in the Modify Template dialog box.
Choose Resources from the drop down list. To export your user-defined
fields to a particular Microsoft Project field, select the user-defined field in
the Project Management Field column.
472
You may want to transfer data from Microsoft Project to the Project
Management module. You can import several different types of Microsoft
Project files. The files you can import are determined by the version of
Microsoft Project you have installed on your computer. If Microsoft
Project 98 or later resides on your computer, you can import MPP, MPX,
MPD, MDB, and MPT files; however, Microsoft Project 2007 is not
supported. If Microsoft Project does not reside on your computer, you can
import MPX files. MPX files may have been created in other third-party
applications. The Import wizard guides you through the steps for
importing projects.
When you import project data, secure codes and secure code
assignments related to the project are not imported. For more
information about secure codes, refer to Defining Global
Profiles on page 332.
473
Select import type and file Choose File, Import. Choose Microsoft
Project, then click Next.
474
Click Select to choose the files you want to import. If there is a password
on the Microsoft Project file, type the password. If you do not enter a
password on a protected file, the project will not import.
Suspend and resume dates can only be imported from MPP
files (not MPX files). When an activity contains multiple
suspend and resume dates in Microsoft Project, the first
suspend and resume dates (split task dates in Microsoft
Project) are imported into the Project Management module.
Any remaining suspend and resume dates are ignored.
Double click the Import Action field to select how the Microsoft Project
file should be imported:
Create New Project The existing projects data remains the same. A
new project is created. Select the level of the EPS at which the project
should be imported. Click the Browse button in the Import To field to
select an EPS node.
Add into Existing Project Click the Browse button in the Import To
field to select a specific WBS level within an existing project. The
imported project is appended to the selected WBS. The existing
project must be open in the Project Management module.
The MPX file format does not support time-phased data and
therefore does not support manual assignment values (manual
curves). When you import an MPX file, if you choose the
Replace Existing import action and the project you are
replacing contains manual assignment values, all manual
values will be deleted.
475
476
Click the General tab in the Modify Template dialog box. The Project
Management module cannot read the currency defined in Microsoft
Project. Click the Browse button in the Select a Currency field to select a
currency to use for values in cost fields. If your currency is not listed,
cancel the Import wizard and add the currency in the Currencies dialog
box (Admin, Currencies). You can also choose to schedule and/or
summarize the project once it is imported.
Click the Activity tab in the Modify Template dialog box. In the Import
section, choose how you want to import milestone activities that have
resource assignments. You can import them into the Project Management
module as Start Milestone activities with associated expenses, or as Task
Dependent activities with associated resource assignments. Then, choose
to import the Task ID from Microsoft Project to the Activity ID field in the
Project Management module or to a selected user-defined text field.
Finally, choose if you want to import MSPs fixed costs as project
expenses; if you do not choose this option, fixed costs are not imported.
477
Click the Resource tab in the Modify Template dialog box. Choose
whether you want to import the Resource Initials or the Resource Name
from Microsoft Project to the Resource ID field in the Project
Management module.
478
Choose whether you want to add a new resource if the resource does not
already exist in the project management module database but is contained
in the Microsoft Project import file. Then, select the level of the hierarchy
at which resources should be imported. Click the Browse button, then
select the resource under which to place all resources from the Microsoft
Project file.
Click the Notebooks tab in the Modify Template dialog box. Project,
WBS, and activity notes from Microsoft Project are imported into
Notebook fields in the Project Management module. Notebook fields are
defined in the Project Management module in Admin Categories (choose
Admin, Admin Categories, then click the Notebook Topics tab). Select the
Notebook fields into which you want to import the Microsoft Project
notes.
479
Click the Custom Field Mappings tab in the Modify Template dialog box.
You can import information from Microsoft Project into user-defined
fields in the Project Management module. For each Microsoft Project field
you want to import, select a user-defined field in the Project Management
Field column.
480
481
You may want to transfer resources from Microsoft Project to the Project
Management module. You can import several different types of Microsoft
Project files. The files you can import are determined by the version of
Microsoft Project you have installed on your computer. If Microsoft
Project 98 or later resides on your computer, you can import MPP, MPX,
MPD, MDB, and MPT files; however, Microsoft Project 2007 is not
supported. If Microsoft Project does not reside on your computer, you can
import MPX files. MPX files may have been created in other third-party
applications. The Import wizard guides you through the steps for
importing resources.
When you import resources, secure codes and secure code
assignments related to the resources are not imported. For
more information about secure codes, refer to Defining Global
Profiles on page 332.
482
Select import type and file Choose File, Import. Choose Microsoft
Project, then click Next.
483
Click Select to choose the files you want to import. If there is a password
on the Microsoft Project file, type the password. If you do not enter a
password on a protected file, the resources will not import.
484
Click the Resource tab in the Modify Template dialog box. Choose
whether you want to import the Resource Initials or the Resource Name
from Microsoft Project to the Resource ID field in the Project
Management module. If you select Resource Initials, only one resource is
imported if multiple resources in Microsoft Project use the same initials. If
you select Resource Name, the first 20 characters of the name import
(based on your setting in the Admin Preferences, ID Lengths tab in the
Project Management module).
Choose how to handle resources that already exist in the project
management database but are also contained in the Microsoft Project
import file.
485
Choose whether you want to add a new resource if the resource does not
already exist in the project management database but is contained in the
Microsoft Project import file. Then, select the level of the hierarchy at
which resources should be imported. Click the Browse button, then select
the resource under which to place all resources from the Microsoft Project
file.
486
Click the Custom Field Mappings tab in the Modify Template dialog box.
You can import information from Microsoft Project into user-defined
fields in the Project Management module. Choose Resources from the
drop-down list. For each Microsoft Project field you want to import, select
a user-defined field in the Project Management Field column. The Field
column is sorted by field type.
487
488
When you export Project Management project data to XLS file format,
you can then open the file in Microsoft Excel. You can also import the file
into other software applications that support the XLS file format. The
Export wizard guides you through the steps for exporting projects.
To import data from an XLS file, you must have the Project
Superuser security profile.This setting is available in the Project
Access tab in the Admin, Users dialog box.
Export does not support the sub-unit time format. Make sure
the Sub-unit checkboxes are clear in the Edit, User
Preferences, Time Units tab.
489
Select export format and subject area Open the project in the
Project Management module you want to export. Choose File, Export to
start the Export wizard. Choose Spread Sheet, then click Next.
490
Select the project to export from a list of open projects. Click Next.
If you choose Resources as the only subject area to export, you
do not have to select a project to export. This step is skipped
during the Export wizard. The Project Management application
exports all resources in the Project Management database.
491
Select a Subject Area in the Modify Template dialog box to modify its
options. In the Columns tab, select the fields to export. The available
options are based on the selected subject area.
You cannot remove a subject areas required columns from the
Selected Options section.
492
In the Modify Template dialog box, click the Filter tab to select the
activities you want to export for the selected subject area. If using more
than one filter, choose to show activities that meet all selection criteria in
each filter, or to show activities that must meet only one selection criteria
in each filter. Select the filter(s) to use for the export file. If necessary,
click Modify to edit the selected user-defined filter. The fields available for
filtering are based on the selected subject area.
493
Click the Sort tab in the Modify Template dialog box to apply order to the
columns during export. Select the sort order for each field name. Click OK
to save your modifications to the template.
Click Next to define the location to save the export file. Double click in the
File Name field and click the Browse button if you want to change the
name and location of the export file.
Click Next to view the summary information for the export file. Click
Finish to export the project data to an XLS file.
494
In the copied file, update the necessary field for an activity. In that activity
row, blank out the remaining fields that are not marked (*) to give it a null
value. As a result, during import, PM will not update the fields with null
values in the project, and PM will calculate the other fields as necessary.
Updated field
495
Column(s)
Activities
Activity ID
Activity
Relationships
Expenses
Resource
Assignments
496
You can import data that has been exported and updated in Microsoft
Excel into the Project Management module. However, you cannot import
any global data that does not currently exist in the database, such as
resources, codes, cost accounts, and so on. If Microsoft Excel does not
reside on your computer, you can still import XLS files that may have
been created in other third-party applications. The Import wizard guides
you through the steps for importing projects.
The User Preference settings are stored in the USERDATA
sheet of the exported file. If this sheet is deleted, information
will not be imported based on the user preference settings that
were used while exporting data.
When you import multiple fields, fields are updated in the order
reflected in the XLSmappings.PDF, not in the order of the Excel
spreadsheet.
497
Type the location of the XLS file or click the Browse button to select the
file you want to import. Click Next.
Select import type and options Choose the subject areas to import
into the project. Click Next.
Each subject area is exported to a separate worksheet in the
XLS file. The Import wizard will not import a subject area if its
title has been changed in the worksheet within the XLS file. If
the title has been changed, the subject area will be grayed out
on the Import Type window.
498
Select the project to update The existing project is updated with any
new/modified data in the XLS file. Click the Browse button in the Import
To field to select the project to update. The project must be open in the
Project Management module to use this option.
Click Next to display information about the import file. Click Finish to
complete the import.
499
500
501
Mark the Export checkbox next to the project you want to export, then
click Next.
Type a four-character
name for the project.
502
Select planning unit Choose the planning unit (hours or days) that you
want P3 3.x to use to schedule project data. The Project Management
module uses only hourly planning units. If you choose Days, you can
select to export the resource units as hours or days. Click Next.
Choose cost calculation rules You can set several Autocost rules for
the exported project. Default settings are used for all other Autocost rules.
These calculations apply only when the project is scheduled in P3 3.x. You
can change these settings when you open the project in P3 3.x.
503
When this checkbox is cleared, P3 3.x can adjust the units per
time-period when the estimate to complete or the remaining duration
changes:
Units per Timeperiod = Estimate to Complete / Remaining Duration
504
After selecting the cost calculation rules, click Finish to export the project.
P3 3.x files are created in the folder specified. These files can be opened
directly through P3 3.x.
Special considerations The following list describes the data items
that are transferred from the Project Management module to P3 3.x.
505
Cost accounts The Cost Accounts Dictionary in both P3 3.x and the
Project Management module can contain an unlimited number of cost
accounts; however, in the Project Management module the dictionary
is global, while in P3 3.x it is project-specific. Only the cost accounts
assigned in the Project Management project are converted to P3 3.x.
In the Project Management module, cost accounts can contain 15
characters; in P3 3.x they can contain 12 characters. P3 3.x truncates
cost accounts to 12 characters. When duplicate accounts exist, P3 3.x
automatically increments the last two characters of the account.
506
You can define work hours in the Project Management module in half
hour increments. The smallest unit in P3 3.x is hour. If one half of an
hour is work time and the other half is nonworktime in the Project
Management module, the entire hour will be nonworktime in P3 3.x.
Custom data items The first eight custom data items in the Project
Management module are converted to P3 3.x.
507
P3 3.x
508
EPS Codes
Financial periods
Issues
OBS
Resource curves
Risks
Roles
Secure codes
Steps
Thresholds
Timesheet data
509
510
511
512
Mark the Create separate projects option if you want to import each
selected subproject as an individual project. If you select this option, you
cannot import the master project. For example, in P3 3.x, the project group
APEX contains three subprojects, AUTO, BLDG, and CONV. This group
is converted to three individual projects (APEX is not converted). Before
the import, create an EPS node to select as the location for the converted
projects.
Regardless of whether subprojects exist for the selected project
group, f you choose to combine subprojects, project activity
codes are imported as global activity codes; if you choose to
create separate projects, project activity codes are imported as
project activity codes.
513
514
Create new project The existing projects data remains the same. A
new project is created. If the project does not fit within the existing
EPS, create a new level before importing the project. Click the
Browse button in the Import To field to select the level of the EPS at
which the project should be imported.
If you chose Create New Project in the Import Action field, click the
Browse button in the Import To field to select the level of the EPS at which
the project should be imported. To keep your projects organized, it is best
to set up a basic EPS before you import projects.
If you chose Update Existing Project or Replace Existing Project in the
Import Action field, click the Browse button in the Import To field to
select the project you want to update or replace.
515
516
Select location for resources For each project, select the level of the
hierarchy at which resources should be imported. Click in the Import To
field, then click the Browse button. Select the resource under which to
place all resources from the P3 3.x project. To better organize your
resources, it is best to set up a basic resource hierarchy before you import
projects. If you leave the field blank, the Project Management module
creates a root node with the same name as the P3 project. The resource
field is disabled for the Replace Existing Project and Update Existing
Project import types.
If resource security is enabled in the Project Management
module, users with restricted resource access will only have the
option to select their assigned resource access node.
Resources contained in the import file that do not exist in
Project Managements resource dictionary are added to the
users resource access node. Users with no resource access
cannot import resources.
517
Select location for activity logs P3 3.x activity logs are converted to
notes in the Project Management module. Notebook topics are predefined
categories in the Project Management module that help to organize your
project notes. Choose to create a new notebook topic for the notes, or
select from the existing list of notebook topics. To display notes in the
Project Management module, in the Activities window click the Layout
Options bar, then choose Show on Bottom, Activity Details. Click the
Notebook tab.
518
519
The Modify Import Configuration dialog box lists the data types for which
you can set options. Mark the Delete checkbox next to a data item to
remove data that exists in the project you are updating but is not included
in the file you are importing. For example, if several activities are defined
in the project you are updating, but are not included in the file to be
imported, mark the checkbox in the Delete column to remove the activities
from the project being updated.
The Delete field applies only to relationships to external
projects, activities, activity relationships, and activity resource
assignments. Global data types are not affected by this setting.
520
Select one of the following in the Action field to indicate how the data
type is updated:
Keep Existing Retains data in the existing project and does not
overwrite it with the updated data; adds new data if the record does
not exist.
Insert New Retains data in the existing project and adds any new
data items. For example, if a new calendar was added in the P3 3.x
file, but you dont want to change the existing calendars, choose Insert
New to add the new calendar to the existing project.
Do Not Import Retains data in the existing project and does not
import the updated data.
The actions you choose for importing the items in the Activity Data Type
group are dependent on each other. For example, if you choose to update
existing relationships, you must also update existing resource assignments
and activities associated with the relationships.
521
When importing a daily project that has resources with a blank unit of
measure in P3 3.x, choose to convert the resource assignments in days
or hours. If you choose hours, the Project Management module retains
the resource values as-is. If you choose days, the Project Management
module multiplies all resource values by a factor of eight (assuming 8
hr/day). You can change the multiplier in the PRMCONVERT.INI
file. Refer to Advanced Conversion Options section later in this
chapter.
522
Click to
import the
P3 project.
523
Import unused WBS codes Mark this setting to keep all the WBS
codes within each project, even if they are not assigned to any
activities.
Planning unit You can only convert projects with an hourly or daily
planning unit. Weekly and monthly planning units are not supported.
To display duration units in hours, choose Edit, User Preferences,
Time Units. Choose Durations as the time unit and Hour as the unit.
524
Task
Task Dependent
Independent
Resource Dependent
Start Milestone
Start Milestone
Finish Milestone
Finish Milestone
Meeting
Resource Dependent
Start Flag
Start Milestone
Finish Flag
Finish Milestone
Hammock
Level of Effort
WBS
WBS Summary
525
526
Custom data items P3 3.x custom data items are converted to the
following user-defined data items in the Project Management module.
Character (C)
User Text
User Text
Start (S)
Finish (F)
Numeric (N)
User Integer
User Integer
Precision (P)
User Number
User Number
527
528
529
Cost accounts Cost accounts are converted from P3 3.x to the Project
Management module. Cost accounts are global across all projects in
the Project Management module. A sample cost account hierarchy is
provided when you install the Project Management module. When
you import a project, the Project Management module creates a
branch for the project cost accounts, and the project name is added to
the beginning of each cost account. The cost category in P3 3.x
becomes part of the cost account in the Project Management module.
For example, cost account 11101 from project APEX creates the
following branch in the Project Management module:
APEX
APEX.11101
APEX.11101.L
530
Start On or After
Start On or Before
Finish On or After
Finish On or Before
Start On
Start On
Expected Finish
Mandatory Start
Mandatory Start
Mandatory Finish
Mandatory Finish
Not Converted
As Late As Possible
Target projects You can convert target projects just as you would
any other project; however, the target designators are not converted.
To designate a target project in the Project Management module,
choose Projects, Maintain Baselines. Click Add and choose Convert
Another Project to a New Baseline of the Current Project. Select the
converted target project as the baseline for the current project.
531
P3 3.x
Project Management
Calculate start-to-start lag from (Actual Calculate start-to-start lag from (Early
start or Early start)
Start or Actual Start)
Calculate total float as (Most critical,
Start float, or Finish float)
532
Webster time data Time data entered through Webster for Primavera
is not supported in the Project Management module. The actual
values from Webster are imported into the Project Management
module as a lump sum value. However, all actual values are lost the
first time you use Timesheets. To retain the actual values, you must
first run the Timesheet Actualizer utility. Refer to the readme file in
the \Support\Utilities\ folder on CD 3.
Refer to Appendix C:
Defining Financial Periods
on page 567 for more information on defining financial
periods in the Project
Management module.
533
534
535
[Resource Units]
Labor=a1,test,bbb
NonLabor=hrs,hr.
Material=lb,lbs
BlankIsLabor=[0,1,2]
Set to 0 to convert blank resource unit of measure fields to nonlabor
resources in the Project Management module; set to 1 to convert blank
resource unit of measure fields to labor resources; set to 2 to convert blank
resource unit of measure fields to material resources. The default setting is
1.
HourlyAdd=[comma-delimited string] Specify resource unit strings to
be added to the default list of units treated as hourly.
HourlyRemove=[comma-delimited string] Specify resource unit strings
to be removed from the default list of units treated as hourly.
DailyAdd=[comma-delimited string] Specify resource unit strings to be
added to the default list of units treated as daily.
DailyRemove=[comma-delimited string] Specify resource unit strings
to be removed from the default list of units treated as daily.
In the following example, the unit strings a1, test, and bbb are treated as
hourly units:
[Resource Units]
HourlyAdd=a1,test,bbb
The default string for Hourly = h,h.,hr,hr.,hrs,hrs.,hour,mh,mh.,mhs,mhs.,
rh,rh.,rhs,rhs.,ph,ph.,phs,phs.
The default string for Daily = d,d.,day,days,md,md.,mds,mds.,rd,rd.,
rds,rds.,pd,pd.,pds,pds.
536
[UOM Mapping]
UOM1=unit of measure=unit of measure string
Specify the units of measure used in P3 that are equivalent to the unit of
measure specified in the Admin Categories in the Project Management
module.
In the following example, all abbreviations of cubic yard listed in the unit
of measure string will convert to the standard cubic yard (cu. yard) unit of
measure defined in the Project Management module:
[UOM Mapping]
UOM1 =cu. yard=cy, cuyd, cuy, kf
537
538
Exporting Projects
For more information about
importing Primavera
Contractor XER files, see
Importing Projects in XER
Format with the Import
Wizard on page 420.
539
Mark the Export checkbox next to the project that you want to export. You
can only export one project at a time. Click Next.
Specify filename and location Type a name for the XER file. To
specify the location where the file will be stored, click the Browse button.
If you do not specify a folder, the file is stored in the My Documents
folder of the current user. Click Finish to export the project to a single file
with an XER extension.
Click to
select the
location
where the
file will be
stored.
540
Budget data
EPS Codes
Financial periods
Funding data
Issues
Issue Codes
Portfolios
Project Codes
Resource Shifts
Risks
Roles
Thresholds
541
Exporting Resources
For more information about
importing Primavera
Contractor XER files, see
Importing Roles or
Resources on page 436.
The Project Management module enables you to export only the resources
in your resource hierarchy to Primavera Contractor 5.0 XER files. Use the
Export wizard to export Project Management module resources to
Primavera Contractor 5.0 XER files; use the Import wizard to bring XER
files into the Project Management module. The Export wizard guides you
through the steps for exporting projects.
Export resource data In the Project Management module, choose
File, Export. Choose Primavera Contractor 5.0, then click Next. Then,
choose Resource Only as the export type and click Next.
542
Type a name for the XER file. To specify the location where the file will
be stored, click the Browse button.If you do not specify a folder, the file is
stored in the My Documents folder of the current user. Click Finish to
export the resources to a single file with an XER extension.
Click to
select the
location
where the
file will be
stored.
543
544
Process Overview
The following steps outline the process for running the PMDB and
MMDB databases in one Oracle instance.
Install the Primavera client, which can install the Project Management
and/or Methodology Management modules, as described in
Primavera Client Installation and Configuration on page 265.
Create the MMDB database and load data as described in this section.
At the end of the process, your database should look like the following:
For PMDB
User
Default Tablespace
admuser
pmdb_dat1
privuser
pmdb_dat1
pubuser
pmdb_dat1
For MMDB
User
Default Tablespace
admuser1
mmdb_dat1
privuser1
mmdb_dat1
pubuser1
mmdb_dat1
545
546
547
5 Type the Oracle system user name and password to log on to the
database. Also, enter the Oracle connect string.
6 Click Next to accept the name for the Data, Index, and LOB
tablespaces and estimated tablespace sizes.
548
7 Accept the default location for the Oracle tablespaces, Data, Index,
and LOB.
549
10 Follow the remaining steps in the Database wizard to create the tables
and load the data. Click Finish to exit the wizard when it has
completed.
If you need to drop the MMDB objects created by the database
installation script, run the scripts in the
install\database\scripts\install\or\OneInstance\drop\MMDB
folder of CD 1. You must log onto the database as ADMUSER1.
To drop PMDB objects, refer to Configuring the Server
Databases on page 39.
550
551
552
553
554
555
3 Enter MMDB as the database alias and select Oracle as the driver
type.
556
557
Once you complete these steps, you should be able to run the
Methodology Management and Project Management modules using the
aliases you established, while still connecting to the same database.
558
559
560
561
562
563
564
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
Summarizing data
Updating progress
Applying Actuals
Refreshing data
Importing
Auto scheduling
Changing portfolios
Undo an action Choose Edit, Undo. The latest action stored for undo
will display next to the Undo command. For example, if you add a
resource assignment to an activity, then choose to remove the assignment
from the activity, the Undo command in the Edit menu will display as
Undo Add Activity Resource Assignment.
565
567
568
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.
569
All periods start and end at midnight, and the end date must be
at least one day later than the start date; therefore, the shortest
financial period you can create spans two days.
571
Index
A
Administer database settings 57
Application data
installing for Oracle 53
installing for SQL Server 53
loading for Oracle 30
loading for SQL Server 35
auditing
detailed configuration 83
overview 81
simple configuration 82
Authentication
configure for Primaveras Web application 150
configuring 305320
LDAP 104
login procedures 320
Native 306
Single Sign On 106
Authentication Configuration wizard 309
Authentication library, adding 207
Automatic database install 27
for Oracle 30
for SQL Server or SQL Server Express database
automatic install 35
B
background processing
monitoring 64
reading writing setting values 62
settings table 61
Base currency, setting 31, 54
for SQL database 36
C
Check in projects 342
D
Dashboards, team member access to 352
Database
administration 57
automatic upgrade 397
changing configuration settings for Primaveras
Web application 137
client drivers, installing 268
driver configurations 149
572
Index
E
E-mail, supported systems 20
Enterprise project structure
access and privileges to 361
defined 323
EPS. See Enterprise project structure.
Exchange rate 31, 36, 54
Export
format
P3 500
XER 410, 442
XML 413
F
Facility, adding 221
Financial periods, defining 567
Firewall
disabling for distributed Job Service 240
G
Global profile
assigning to users 347
creating 333
for the Methodology Management module 371
definitions 332
new privileges 398
overview 322
privileges defined 333
for the Methodology Management module 371
Group Server
administrator applet 108
configure LDAP authentication 104
configure Single Sign On authentication 106
configuring settings 108
creating multiple instances 115
HTTP(S) 99
installation overview 93
installing 95
international language support 94
overview 5
planning issues 13
registry settings 118
reviewing properties 110
supported configurations 19
taking offline 108
uninstalling 92
user connections 111
H
HTTP(S), using for secure transmission of timesheet
data 99
I
Import
Index
format
P3 509
XER 420, 446
XML 427
methodologies, XER files 446
projects
as methodologies 451
P3 files 509
XER files 420
XML files 427
projects, command line
XER files 432
resources 436, 457
roles 436, 457
Incremental license, storing 302
Indexer service
adding 214
starting 215
Integration API license, description of 350
International language support 47, 94
for Job Service 281
Invited users, access to project data 351
J
Java Web Start 93
job scheduler
configuring, Oracle 59
configuring, SQL Server 59
Job Service
choose language 281
configure Project Architect for Primaveras Web
application 146
creating multiple instances 276
distributed 238
configure DCOM on Windows 2000 242
configure DCOM on Windows 2003 and
XP 248
configure servers 258
Controller server 238
disable Windows Firewall 240
installing 239
exporting projects 412
installing 270, 275
overview 6
planning issues 12
registry settings 261
running on multiple databases 278
send jobs directly to printer 280
summarizer jobs 279
registry settings 262
supported configurations 18
573
Job Services
uninstalling 5.x versions 269
L
Language support 47, 94
for Job Service 281
LDAP
authentication 306
for Group Server/Timesheets 104
login procedures 320
provisioning 318
LDAP servers
configuring for authentication 309
Library Manager 210
License
assigning to users 348
concurrent user 348
configuring 302
incremental 302
loading at database setup 32, 37, 55, 546
named user 348
License key file 32, 37, 546
limits
practical 23
Login name, maintaining single login for project
resources and users 346
M
MDAC 270
Methodologies
exporting, XER format 442
importing
from projects 451
XER files 446
transferring to other Project Management module
users 441, 460
Methodology management database 40
administering private logins 302
changing connection settings 300
client drivers 268
creating
on Oracle 44
on SQL Server 50
installing application data 53
removing
from Oracle 45
from SQL Server 52
running in same Oracle instance as PMDB 545
sample data 31, 36, 54
upgrading
on SQL Server 402
574
Index
Oracle 400
Methodology Management module
installing 270
minimum configuration requirements 16
overview 4
planning issues 12
security 370377
adding users 375
global profiles 371
methodology profiles 373
Methodology profile
creating 373
privileges defined 374
Microsoft Project files
exporting projects 462, 488
exporting resources 468
importing projects 472, 496
importing resources 481
Microsoft Project-managed projects
See MSP-managed projects
MMDB. See Methodology management database.
MSP-managed projects
exporting to XER files 408
importing 475
myPrimavera
uninstalling 127
N
Native authentication 306
login procedures 320
Network administrator xvi, xvii
role defined 8
Network protocols, supported software 20
O
OBS
assigning
to the EPS 362
to users 360
defined 323
denying access to project information 360
in organization 323
responsible 339, 361
root 362
Operations executive xvi
Oracle
automatic database install 30
creating database structures 41
improve database performance 80
installing client drivers 268
Methodology Management module sizing
guide 22
P
P3 projects
exporting 500
data not converted 508
special considerations 504
importing 509
advanced conversion options 533
data not converted 532
special considerations 523
Passwords
changing 302
encrypting
for custom portlets 151
Past period actuals 568
performance
optimizing 80
PMDB. See Project management database.
PMSDK 282
Primavera
additional components 5
authentication 306
choosing components 12
client modules 4
documentation xvi
installation process overview 10
license accessibility 348
minimum requirements 16
security 322
server components 5
solution overview 4
uninstalling previous versions 269
using the Administrators Guide xiv
Primavera Contractor, exporting projects for use
with 537
Primavera ProjectLink
licensing 350
Primavera Software Development Kit
documentation 284
installing 270, 282
overview 6
planning issues 13
supported configurations 16
Primaveras Web application
Index
accessing from client browsers 136
adding configurations 144
adding database instances 144
administration application 139
application server requirements 19
available Team Member functionality 351
changing database configuration settings 137
client requirements 18
collaboration 5
configuration settings 152
configure
authentication 150
custom portlets 151
for collaboration 234
to run Project Architect 146
database drivers 149
defining user access 368
deleting configurations 145
deleting database instances 145
implementing application server plugins 174
installation process overview 129
installing 125
installing the application server 128
invited users 351
JSP server requirements 20
licensing 349
managing access to multiple database
instances 147
overview 5
planning issues 15
reviewing and modifying configurations 142
starting the server 133
stopping the server 135
upgrading from a previous version 126
Web server requirements 20
Primavision
uninstalling 127
Privileges, new in 5.0 398
product limits 23
Program manager xvi
role defined 9
Project Architect 146
Project controls coordinator xvi, xvii
role defined 9
Project data
Team Member access to 353
transferring
between P3 and the Project Management
module 499
to other Project Management module
users 407, 440
to Primavera Contractor users 537542
using Microsoft Excel files 487498
575
576
Index
R
RDBMS. See Relational database management
system.
Relational database management system
overview 5
planning 12
supported configurations 18
Resource security 364
Resource/cost manager xvi
Resources
associating with users 346
defined 323
defining access to 364
exporting 415, 444
Microsoft Project format 468
importing 436, 457
Microsoft Project format 481
Roles
exporting 415, 444
importing 436, 457
Root OBS 362
S
Safe deletes, configuring 565
SDK. See Primavera Software Development Kit.
Security 321377
associating resources and users 346
defining access to resources 366
global profiles 332
assigning to users 347
implementation process overview 330
licensing 348
Methodology Management module 370377
OBS
EPS assignments 362
user and project profile assignments 359
overview 322
project profiles 339
resource access 364
users 345
in the Methodology Management module 375
T
Team leader xvi
Team member xvi
available Primavera Web application
functionality 351
Timesheets module 4
Team Member license, description of 349
Technical support xviii
Timesheets
approval levels 384
creating batches 390
Timesheets license, description of 349
Timesheets module
configure LDAP authentication 104
configure Single Sign On authentication 106
configuring
in the Project Management module 379383,
??392
configuring resources to use 389
creating
timesheets 390
user login 387
entering overtime 389
implementation overview 380
installing Web files 95
Java Web Start version
Index
defined 14
JRE installation 394
minimum requirements 17
overview 93
running 393
overhead codes 392
overview 4
planning issues 13
preferences 382
project-specific preferences 391
user privileges 385
versions 14
Web browser version
defined 14
JRE installation 394
minimum requirements 17
running 393
TNSPING.EXE 28, 40
Tomcat, installing 128
Trustees, adding 217, 220
U
Unattended setup
creating file set 292
planning issues 12
running 296
Undo, using 564
Uninstalling
4.1 client modules 269
Job Services 5.x versions 269
the Group Server 92
Upgrading
automatically 397
license 302
Oracle database 400
process overview 398
SQL Server database 402
stand-alone version 287
User interface views, assigning 368
Users
adding 345
Methodology Management module 375
assigning
global profile 347
product licensing 348
profiles in the Methodology Management
module 376
to OBS elements 359
associating with resources 346
changing passwords 302
defined 323
W
WBS, defined 323
Web browsers
supported for Primaveras Web application 18
supported for the Timesheets module 17
Web Scheduler 12
X
XER files
exporting
methodologies 442
MSP-managed projects 408
projects 410
resources 415, 444
roles 415, 444
importing
methodologies 446
projects 420
projects as methodologies 451
resources 436, 457
roles 436, 457
importing, command line
projects 432
XML files
exporting
projects 413
importing
projects 427
577