Escolar Documentos
Profissional Documentos
Cultura Documentos
Appendix F 230
Installing Project Server 2003 From the Command Line............230
Command-Line Parameters for Installing Project Server 2003......................
....230
Select a Location for Installation..............................................
.....................231
Choose the Services You Want to Install on This Server..........................
....231
Installing the Session Manager Service Without the Front-End Service.....232
Create the View Processing Share................................................
.................232
Enter the Session Manager Server Name...........................................
..........233
Enter the View Processing Server Information....................................
..........233
Enter Database Server Information...............................................
................234
Enter Connection Information for Views Tables...................................
.........234
Enter Database Account Information..............................................
..............236
Enter Analysis Services Connection Information..................................
........236
Select a Web Site...............................................................
.............................237
Enter Web Server Address Information............................................
.............237
Enter SMTP Mail Server Information..............................................
...............238
Connect to a Web Server Running Windows SharePoint Services..............238
Connect to a Web Site Running SharePoint Portal Server 2003.................239
Choose an Installation Environment..............................................
................240
Enter the Administrator Password................................................
.................240
Appendix G 242
Working with the Outlook Add-in..............................................242
Send us your feedback. Please let us know what you think about the quality of th
is
content. If this text does not meet your needs, let us know how we can improve i
t. If this
text was helpful to you, let us know how it helped.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server
2003 Installation
Guide
Microsoft Office Project Server 2003 Online Books Series
The Microsoft Office Project Server 2003 Online Books series documents the Micro
soft
Office Enterprise Project Management (EPM) Solution and provides a detailed refe
rence
for all phases of deploying Project Server 2003, including planning, installatio
n,
configuration, and administration. Each book is designed to stand alone and can
be
referred to on an as-needed basis. You can also read these books in the order li
sted below
for a complete guide to deploying Project Server 2003:
Microsoft Office Project Server 2003 Solution Planning Guide
http://go.microsoft.com/fwlink/?LinkID=20235
A key part of deploying Project Server 2003 as part of a Microsoft Office Enterp
rise
Project Management (EPM) Solution is proper planning. These books will help your
organization plan for deployment by explaining Project Server 2003 in detail, hi
ghlighting
the questions you should ask throughout the planning phase, and providing a refe
rence for
the requirements during each phase of deployment. These books are not intended t
o be a
substitute for proper planning within your organization as to what your EPM Solu
tion
should be. The Microsoft Office Project Server 2003 Online Books series will hel
p you
succeed in deploying your organization s project management solution.
What Can You Learn from This Book?
This guide covers the installation of Microsoft Office Project Server 2003 and i
ts related
components. The following topics are covered:
Migrating to Project Server 2003 from Microsoft Project Server 2002 and Project
Central.
Preparing your servers for installation of Project Server 2003, Microsoft Window
s®
SharePoint® Services, and other related components.
Deploying your Project Server 2003 database, both manually and automatically, by
means of the Project Server Setup program.
Database optimization and partitioning.
Project Server 2003 installation tools.
Date
Revision
October 2003
Initial Publication.
January 2004
Added Chapter 9, Extranet and Non-
Trusted Domain Scenarios.
Added Chapter 11, International
Deployment Considerations.
Added Appendix F, Installing Project
Server 2003 from the Command Line.
Added Appendix G, Working with the
Outlook Add-In.
Added Appendix H, Installing Project Web
Access ActiveX Controls.
Updated Appendix C, Project Server
Installation Tools.
March 2004
Updated Chapter 5, Configure Windows
SharePoint Services.
Updated Appendix H, Installing Project
Web Access ActiveX Controls.
August 2004
Added Appendix B, Project Server Service
Accounts.
Added Appendix I, Service Packs for
Project Server Components.
September 2004
Updated the section Database
Partitioning in Chapter 10, System
Optimization.
Added the section Load Balancing the
Project Server Views Notification Service
to Chapter 10, System Optimization.
1
Overview of Project Server 2003
Microsoft® Office Project Server 2003 is designed to support collaboration between
project managers who are using Microsoft Office Project Professional 2003 and te
am
members who are using Microsoft Office Project Web Access 2003. The Microsoft Of
fice
Enterprise Project Management (EPM) Solution is an integrated system that includ
es
Project Professional 2003, Project Web Access 2003, and Project Server 2003.
Project Server 2003 provides timesheets, status reports, portfolio analysis and
modeling,
enterprise resources, and enterprise templates. When integrated with Microsoft W
indows®
SharePoint® Services, Project Server 2003 provides document management and issues
and
risk tracking features.
Users access Project Server 2003 by means of Project Web Access, a browser-based
client
that enables team members, resource managers, and executives to enter and view t
imesheet
information and view portfolio reports. Project managers can create projects or
create or
modify the Enterprise Resource Pool by using Project Professional and save that
data to
the Project Server database.
Project Server 2003 is flexible and is designed to enable you to extend your EPM
Solution.
You can begin by using a limited number of enterprise features and then add addi
tional
features as needed.
Project Server 2003 Components
Project Server 2003 consists of the following software components:
Project Server Front-End service Handles all Project Web Access and Project Data
Service requests.
View Processing Generates static views of published data for Project Web Access.
Session Manager Handles the session-state information for each client that is
connecting to Project Server 2003 from Project Web Access.
Project Server 2003 requires the services and support of the following Microsoft
applications:
Internet Information Services (IIS) 5.0 or later Provides the foundation for sec
ure
and scalable Web-based solutions. IIS is included as part of the Microsoft
Windows 2000 Server and Microsoft Windows Server 2003 operating systems.
Microsoft SQL Server 2000 Provides database management for users who want
to take advantage of all enterprise functionality that is built in to Project Se
rver 2003 in
a scalable environment. Both SQL Server 2000 Standard Edition and SQL Server 200
0
Enterprise Edition support the enterprise functionality of Project Server 2003,
but only
SQL Server 2000 Enterprise Edition supports advanced deployment features such as
failover or HTTP Internet support. You must install SQL Server 2000 before you c
an
install Project Server 2003 or configure Windows SharePoint Services for Project
Server 2003.
SQL Server 2000 Analysis Services Provides online analytical processing (OLAP)
services, which are required for the Portfolio Analyzer feature of Project Serve
r 2003.
The Portfolio Analyzer feature is only available as an enterprise feature of Pro
ject
Server 2003.
Windows SharePoint Services Provides document library and issues and risks
tracking services when properly configured for Project Server 2003. You can down
load
Windows SharePoint Services from the Microsoft Web site
(http://go.microsoft.com/fwlink/?linkid=23448), or you can configure an existing
installation of Windows SharePoint Services for Project Server 2003.
Note Project Server 2003 is not compatible with SharePoint® Team Services.
Microsoft Office SharePoint Portal Server 2003 Enables the indexing and
searching of Project Server 2003 document libraries.
Project Professional Provides enterprise-wide project and resource management
capabilities, collaboration functionality, and scenario analysis tools for organ
izations
that require an enterprise project management solution. To access Project Server
2003,
Project Professional 2003 has the following Internet browser requirements:
o Internet Explorer 5.01 with SP3 or later
o Internet Explorer 5.5 with SP2 or later
o Internet Explorer 6 with SP1 or later (recommended)
The Microsoft Office Project Add-in for Outlook® Enables users to keep track of
tasks that are assigned to them in projects. Tasks can be tracked in Microsoft
Outlook 2000 or later (or Outlook Web Access in a limited capacity). The Outlook
Integration add-in is available from the Project Web Access Home page.
Microsoft Internet Explorer version 5.01 (or later) Enables access to the Projec
t
Web Access user interface (UI). Internet Explorer 5.5 or later is required in or
der to
use all available Project Web Access features.
Project Professional 2003 runs on Windows 2000 and later. Project managers can u
se
Project Professional 2003 to publish projects to the Project Server database and
manage
updates to the project information that is stored on the server. You can also us
e Project
Professional 2003 to open, modify, and save enterprise projects and resources.
Application Tier
The application tier is made up of Web-based front-end applications that are int
egrated
with Internet Information Services (IIS). These applications include Project Ser
ver 2003
and Windows SharePoint Services.
Project Server 2003 is the central component of an EPM Solution and is a robust
and
highly scalable Web-based server application. Project Server 2003 runs on Window
s 2000
Server or later and requires Internet Information Services (IIS) version 5.0 or
later.
Windows SharePoint Services is an optional component that integrates with Projec
t
Server 2003 to provide document management and risk and issue tracking. Windows
SharePoint Services is available as a free download from Microsoft at www.micros
oft.com
and is only supported on a computer running Windows Server 2003, IIS 6.0, and
ASP.NET.
Database Tier
SQL Server provides the database tier of the EPM Solution. Project Professional
and
Project Web Access work with both the non-enterprise and enterprise tables in th
e SQL
Server database. Project Server 2003 uses View tables that contain time-phased d
ata for all
projects that are published to the server to reduce the load on the computer run
ning SQL
Server and to allow for greater scalability. Project Server 2003 provides the pr
imary means
of access to the database, although Project Professional can save projects direc
tly to the
database by means of Open Database Connectivity (ODBC).
2
Installation Roadmaps
This chapter describes four examples of hardware deployments for Microsoft® Office
Project Server 2003. Each example includes a roadmap of, or high-level steps for
, the
installation process to assist you in planning your deployment. Identify the dep
loyment
roadmap in this chapter that most closely matches the architecture that you requ
ire for
your organization, and then follow the procedures in that topic to complete your
installation.
Note Before you install Project Server 2003, read the Microsoft Office Project S
erver 2003
Configuration Planning Guide (http://go.microsoft.com/fwlink/?LinkID=20235). The
Microsoft
Office Project Server 2003 Configuration Planning Guide includes hardware recomm
endations for
various tested configuration scenarios. When you are planning your hardware requ
irements, be
sure to consider the type of hardware that was used to test the configurations a
nd compare it
against the hardware that you intend to use. If you are using different hardware
, you will see
different performance results.
The procedures in this chapter assume that you have the required hardware for yo
ur
deployment, and that you have installed an appropriate version of Microsoft Wind
ows®,
along with Microsoft SQL Server 2000, Analysis Services (if applicable), and the
required
service packs.
If you are upgrading or migrating from an earlier version of Microsoft Project S
erver, see
Chapter 3, Upgrading to Project Server 2003 from Earlier Versions of Microsoft
Project in the Microsoft Office Project Server 2003 Installation Guide before be
ginning your
deployment. You will need to follow the steps in this chapter when you deploy Pr
oject
Server 2003.
Important Document your installation thoroughly, in case you need to duplicate i
t when recovering
from a system failure or disaster. Keep track of the accounts that you create, c
omputer names,
passwords, and setup options. Be sure you keep a copy of this documentation with
your disaster
recovery materials, preferably in an off-site location.
Single Computer Installation Roadmap
A single computer deployment can support a small- to medium-sized organization a
nd can
be used by a large organization to test Project Server 2003. A single computer d
eployment
supports up to 500 users, but is not ideal for a large-scale production environm
ent. For
information about single computer deployments, including sample hardware sets an
d
performance numbers, see the topic Configuration Scenario 1 in Chapter 6, select
ing a
Project Server Configuration, of the Microsoft Office Project Server 2003 Config
uration Planning
Guide (http://go.microsoft.com/fwlink/?LinkID=20235).
Note You must use a single computer deployment if you are installing the Project
Server 2003
Sample database.
Create these accounts by using the procedures in the topic Create User Accounts
in
Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Insta
llation
Guide.
2. Create an OLAP administrator by using the procedure in the topic Create an OL
AP
Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project
Server 2003 Installation Guide.
3. If your implementation of SQL Server is not configured to use mixed-mode
authentication, configure it to use mixed-mode authentication by using the proce
dures
in the topic Configure SQL Server Authentication in Chapter 4, Prepare the
Servers of the Microsoft Office Project Server 2003 Installation Guide.
4. Configure Internet Information Services by using the procedures in the topic
Configure Internet Information Services in Chapter 4, Prepare the Servers of the
Microsoft Office Project Server 2003 Installation Guide.
5. Configure Microsoft Internet Explorer security on Microsoft Windows Server 200
3
by using the procedure in the topic Configure Internet Explorer Enhanced
Security in Chapter 4, Prepare the Servers of the Microsoft Office Project Serve
r 2003
Installation Guide.
Create these accounts by using the procedures in the topic Create User Accounts
in
Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Insta
llation
Guide.
2. Create an OLAP Administrator by using the procedure in the topic Create an OL
AP
Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project
Server 2003 Installation Guide.
3. If your implementation of SQL Server is not configured to use mixed-mode
authentication, configure it to use mixed-mode authentication by using the proce
dures
in the topic Configure SQL Server Authentication in Chapter 4, Prepare the
Servers of the Microsoft Office Project Server 2003 Installation Guide.
4. Install the Analysis Services Decision Support Objects by using the procedure
in the
topic Install Decision Support Objects in Chapter 4, Prepare the Servers of the
Microsoft Office Project Server 2003 Installation Guide.
5. Configure Internet Information Services on the computer on which you will ins
tall
Project Server by using the procedures in the topic Configure Internet Informati
on
Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Serve
r 2003
Installation Guide.
6. Configure Internet Explorer security on Windows Server 2003 by using the proc
edures
in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare
the Servers of the Microsoft Office Project Server 2003 Installation Guide.
.. To install Windows SharePoint Services
1. Install Windows SharePoint Services on your server by using the procedure in
the topic
Install Windows SharePoint Services in Chapter 5, Configure Windows
SharePoint Services of the Microsoft Office Project Server 2003 Installation Gui
de.
2. Configure the administrative virtual server for Windows SharePoint Services b
y using
the procedure in the topic Configure the Administrative Virtual Server in Chapte
r
5, Configure Windows SharePoint Services of the Microsoft Office Project Server
2003
Installation Guide.
3. Configure the Windows SharePoint Services configuration database by using the
procedure in the topic Set the Configuration Database Server in Chapter 5,
Configure Windows SharePoint Services of the Microsoft Office Project Server 200
3
Installation Guide.
4. Extend the virtual server by using the procedure in the topic Extend the Virt
ual
Server in Chapter 5, Configure Windows SharePoint Services of the Microsoft Offi
ce
Project Server 2003 Installation Guide.
5. Create a Windows SharePoint Administrator by following the procedure in the t
opic
Create a Windows SharePoint Services Administrator in Chapter 5, Configure
Windows SharePoint Services of the Microsoft Office Project Server 2003 Installa
tion
Guide.
6. Run the Windows SharePoint Service Configuration Wizard by following the
procedure in the topic Run the Windows SharePoint Services Configuration
Wizard in Chapter 5, Configure Windows SharePoint Services of the Microsoft Offi
ce
Project Server 2003 Installation Guide.
7. If you are upgrading from a SharePoint Team Services installation, and you wa
nt to
migrate your data, follow the procedures in the topic Migrating from SharePoint
Team Services in Chapter 3, Upgrading to Project Server 2003 from Earlier
Versions of Microsoft Project of the Microsoft Office Project Server 2003 Instal
lation Guide.
Create these accounts by using the procedures in the topic Create User Accounts
in
Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Insta
llation
Guide.
2. Create an OLAP Administrator by using the procedure in the topic Create an OL
AP
Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project
Server 2003 Installation Guide.
3. If your implementation of SQL Server is not configured to use mixed-mode
authentication, configure it to use mixed-mode authentication by using the proce
dures
in the topic Configure SQL Server Authentication in Chapter 4, Prepare the
Servers of the Microsoft Office Project Server 2003 Installation Guide.
4. Install the Analysis Services Decision Support Objects using the procedure in
the topic
Install Decision Support Objects in Chapter 4, Prepare the Servers of the Micros
oft
Office Project Server 2003 Installation Guide.
Note If you are installing the View Processing service on a different computer f
rom the
Front-End service, you must install the Decision Support Objects on both compute
rs.
5. Configure Internet Information Services on the computer on which you will ins
tall
Project Server by using the procedures in the topic Configure Internet Informati
on
Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Serve
r 2003
Installation Guide.
6. Configure Internet Explorer security on Windows Server 2003 by using the proc
edures
in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare
the Servers of the Microsoft Office Project Server 2003 Installation Guide.
Create these accounts by using the procedures in the topic Create User Accounts
in
Chapter 4, Prepare the Servers of the Microsoft Office Project Server 2003 Insta
llation
Guide.
2. Create an OLAP Administrator by using the procedure in the topic Create an OL
AP
Administrator in Chapter 4, Prepare the Servers of the Microsoft Office Project
Server 2003 Installation Guide.
3. If your implementation of SQL Server is not configured to use mixed-mode
authentication, configure it to use mixed-mode authentication by using the proce
dures
in the topic Configure SQL Server Authentication in Chapter 4, Prepare the
Servers of the Microsoft Office Project Server 2003 Installation Guide.
4. Install the Analysis Services Decision Support Objects by using the procedure
in the
topic Install Decision Support Objects in Chapter 4, Prepare the Servers of the
Microsoft Office Project Server 2003 Installation Guide.
Note If you are installing the View Processing service on a different computer f
rom the
Front-End service, you must install the Decision Support Objects on both compute
rs.
5. Configure Internet Information Services on the computer on which you will ins
tall
Project Server by using the procedures in the topic Configure Internet Informati
on
Services in Chapter 4, Prepare the Servers of the Microsoft Office Project Serve
r 2003
Installation Guide.
6. Configure Internet Explorer security on Windows Server 2003 by using the proc
edures
in the topic Configure Internet Explorer Enhanced Security in Chapter 4, Prepare
the Servers of the Microsoft Office Project Server 2003 Installation Guide.
If you are upgrading from Microsoft Project Central, you must first upgrade the
database
from Microsoft Project Central to Microsoft Project Server 2002. After you upgra
de the
database to Microsoft Project Server 2002, you can run the scripts to upgrade to
Project
Server 2003.
.. To upgrade from Microsoft Project Central
1. Open a command prompt window, and then browse to the Database folder.
2. Copy the file osql.exe to the PC2PS02 folder.
3. Open the PC2PS02 folder.
4. Run UPG09DB.cmd by using the following syntax:
UPG09DB.CMD <ServerName> <DatabaseName> <UserName> <Password>
For example:
UPG09DB.CMD PROJSQL2000 ProjectCentral sa hello
5. When the script finishes successfully, follow the procedure To upgrade from
Microsoft Project Server 2002.
6. In SQL Server 2000 Enterprise Manager, create the following two logins by usi
ng SQL
Server Authentication in the database: MSProjectServerUser and MSProjectUser.
7. Create the two database roles that are needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
8. Grant each role that you created in the previous step login access to the Pro
ject Server
database.
9. Assign the MSProjectServerRole role to the MSProjectServerUser login, and the
n
assign the MSProjectRole role to the MSProjectUser login.
3. When the script finishes successfully, install Project Server 2003 and connec
t to the
upgraded database from the Enter database account information page of Project
Server Setup.
Note When you set up Microsoft Project Server 2002, random passwords are assigne
d to the
ProjectUser and ProjectServerUser accounts. If you do not know the passwords for
these accounts,
you will need to reset them with new passwords before you install Project Server
2003. You must
provide the password information for these accounts when you run Project Server
Setup. To reset
the password, in SQL Server Enterprise Manager, right-click the login, click Pro
perties, and then
type the new password in the Password box.
Note Microsoft Project Server 2002 is configured to use MSDE when you choose the
Install Now
option in Microsoft Project Server 2002 Setup.
.. To upgrade from Microsoft Project Server 2002 and MSDE 2000
1. Detach your Microsoft Project Server 2002 database from MSDE 2000:
a. Click Start, click Run, type osql -U sa in the Open box, and then click OK.
This connects you to the local, default instance of MSDE 2000 by using the
System Administrator (sa) account.
b. At the Password prompt, type the sa password, and then press ENTER.
c. Retrieve the names of the database (.mdf) and log (.ldf) files for the Micros
oft
Project Server 2002 database by typing the following text on separate lines, and
then pressing ENTER after each line of text:
select a.filename as Filename from sysaltfiles a,
sysdatabases b where a.dbid = b.dbid and b.name =
N'ProjectServer'
go
This returns two rows, one that ends in .mdf, indicating the full path of the
database file, and one that ends in .ldf, indicating the full path of the log fi
le.
d. Close any running transactions, detach the database, and detach the log files
by
typing the following text on separate lines and pressing ENTER after each line:
EXEC sp_detach_db N'ProjectServer', N'true'
go
Note There might be a long delay after running this command.
2. After the database is detached, back up the .mdf file and the .ldf file from
the
directories that were identified in step 1.c by copying them to an alternate dir
ectory.
3. Remove Microsoft Project Server 2002 by doing the following:
a. Click Start, click Control Panel, and then click Add or Remove Programs.
b. In the Add or Remove Programs box, click Microsoft Project Server 2002, and
then click Remove.
c. Follow the on-screen instructions to remove Microsoft Project Server 2002.
d. Restart your computer regardless of whether or not you are prompted to do so.
4. Install MSDE 2000 SP3 or higher by doing the following:
a. Go to the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=19683).
b. Select the language that matches your version of Microsoft Project Server 200
2
from the Full Download box on the right side of your screen, and then click Go.
c. Locate the download link to the SQL2KDeskSP3.exe file, and then click the
download link to start the download.
Note Non-English versions of the download are listed as
language_SQL2KDeskSP3.exe where language represents the language version of the
download.
i. Click OK.
j. Restart your computer.
5. Attach your Microsoft Project Server 2002 databases to MSDE 2000 by doing the
following:
a. Click Start, click Run, type osql -U sa in the Open box, and then click OK.
This connects you to the local, default instance of MSDE 2000 by using the sa
account.
b. At the password prompt, type the sa password that you set in step 4.h, and th
en
press ENTER.
c. Attach the Project Server .mdf and .ldf files by typing the following text on
separate lines, and then pressing ENTER after each line:
EXEC sp_attach_db @dbname=N'ProjectServer', @filename1=N'
<mdf_path>',@filename2=N'<ldf_path>
go
where mdf_path and ldf_path are the paths to the .mdf file and the .ldf file tha
t you
previously backed up to a safe location in step 2.
Note There might be a long delay after running this command.
8. Upgrade your database for Project Server 2003 by following the steps in Migra
ting
Data from Project Central or Microsoft Project Server 2002 earlier in this chapt
er.
9. Install Project Server 2003 and connect to the upgraded MSDE 2000 database fr
om
the Enter database server information page of the installation wizard.
If you have fields with these names, change the names before you migrate to Wind
ows
SharePoint Services.
2. On the server running SharePoint Team Services, be sure that you have install
ed
Microsoft Office XP Service Pack 3 (SP3).
Note Office XP SP3 contains the OWS1002.exe update file that is required for mig
rating
SharePoint Team Services to Windows SharePoint Services. This enables SharePoint
Team
Services to export additional schema information about SharePoint Team Services
subwebs
and is required by the Windows SharePoint Services Backup and Restore tool
(SMigrate.exe) during the migration process.
For more information about Office XP SP3, see Appendix I, Service Packs for Proj
ect Server
Components, in the Microsoft Office Project Server 2003 Installation Guide.
3. Run STSWiz.exe on the server running SharePoint Team Services. STSWiz.exe can
be
found in the Support folder on the Microsoft Project Server 2002 CD.
4. Run PSMigrat.exe. Insert your Office Project Server 2003 CD into your CD-ROM
drive. Click Start and then click Run. Type CMD and click OK. At the command
prompt, change to your CD-ROM drive and change to the \SUPPORT\PSMIGRAT
folder. This tool requires the following information:
The Windows SharePoint Services managed path under which the newly migrated
sites will be created.
The folder where all the backup files will be stored.
The connection information for the Project Server 2003 database.
The range of project IDs (optional).
The location of the log file (optional).
Note To view parameter options that can be run with PSMigrate.exe, see the topic
Project
Server Data Migration Tool in Appendix B, Project Server Installation Tools of t
he Microsoft
Office Project Server 2003 Installation Guide.
For example, you can run the following:
PSMigrat.exe w http://wss_svr/projects
-f \\<serverName>\<path to server> -dbserver <serverName>
-dblogin <loginName> -dbpassword <password> -p <prefix>
Note You must run PSMigrat.exe from the computer running Windows SharePoint Serv
ices.
Note Some deployments do not have separate computers for each of the components
listed.
A Windows domain user account or local user account on the server running
Microsoft Windows SharePoint® Services, to allow Project Server 2003 to access
Windows SharePoint Services. You can use a generic name for this account, such a
s
MSProjServ, and set the password to never expire. You will use this account when
you
create a Windows SharePoint Services administrator, and you will specify this ac
count
on the Enter account information for Microsoft Windows SharePoint Services
(continued) page in Project Server Setup.
A Windows domain user or local user account to allow the Project Server Front-En
d
service to access the Views Staging shared folder on the computer on which the V
iew
Processing service is located. This account must be located on both the computer
running the Project Server Front-End service and the computer running the Projec
t
Server View Processing service. During Project Server Views Processing Setup, a
Views Staging folder is specified and created. The Windows account that you spec
ify is
then assigned the required permissions to the folder.
Note This account is only required if you plan to install the View Processing se
rvice on a
different computer than the computer on which you install the Project Server Fro
nt-End
service.
A SQL Server account on the instance of SQL Server 2000 where the Project Server
database will be located. This account must belong to the Database Creators and
Security Administrators roles. This account will only be used for the purposes o
f
creating the Project Server database. It will not be stored and used after insta
llation.
Note You can use your system administrator (sa) account or an existing account t
hat is a
member of the same roles. If your Windows account belongs to the appropriate SQL
Server
roles, you can use Windows authentication as long as you are not partitioning yo
ur
database.
A SQL Server login for the computer on which Windows SharePoint Services is
installed. This account must belong to the Database Creators and Security
Administrators roles. Windows authentication is the preferred authentication met
hod,
although you can also select SQL Server authentication. This account will be use
d to
create the Windows SharePoint Services database on the computer running SQL
Server.
Note For more information about accounts needed to install and configure Project
Server 2003, see Appendix B, Project Server Service Accounts, in the Microsoft O
ffice Project
Server 2003 Installation Guide.
.. To create a Windows domain user account
1. Open Active Directory Users and Computers.
2. In the console tree, right-click the folder in which you want to add a user a
ccount.
3. Point to New, and then click User.
4. On the New Object User page, type the user s first name, initial, last name, an
d user
logon name, and then click Next.
5. In the Password box, type a password, and in the Confirm Password box, retype
the
password.
6. Clear the User must change password at next logon check box.
Note You must clear this check box or the account will not work properly with Pr
oject
Server 2003.
7. Select the Password Never Expires check box, and then click Next.
8. Click Finish.
Note To perform this procedure, you must be a member of the Account Operators gr
oup, Domain
Admins group, or the Enterprise Admins group in Active Directory® directory servic
e, or you must
have been delegated the appropriate authority.
.. To create a local user account
1. On the computer on which you want to create the account, open Computer
Management.
2. Expand Local Users and Groups.
3. Right-click Users and click New User.
4. In User name, type a name for the user (for example, ProjServ).
5. In Description, type a description for the user account.
6. In Password and Confirm password, type the user's password.
7. Clear the User must change password at next logon check box.
Note You must clear this check box or the account will not work properly with Pr
oject
Server 2003.
8. Click Create.
8. On the Confirm Password page, in the Confirm New Password box, reenter the
password, and then click OK.
9. Click OK.
.. To create a SQL Server login for the computer running Windows SharePoint Serv
ices
1. Open SQL Server Enterprise Manager.
2. Expand the server group containing the server on which you want to add the ac
count,
and then expand the server.
3. Expand Security, right-click Logins, and then click New Login.
4. In the Name box, type a name for the SQL Server login. Use the form
domain\username; for example, XABYTE2\ProjServ.
Note You can also configure this account to use SQL Server authentication, altho
ugh Windows
authentication is recommended. To configure this account using SQL Server Authen
tication, see
the previous procedure: To create a SQL Server 2000 account.
Note Some deployments do not have separate computers for each of the components
listed.
.. To create an OLAP Administrator
1. On the computer on which you want to create an OLAP Administrator, open
Computer Management.
2. In the console tree, under System Tools, expand Local Users and Groups.
3. Click Groups.
4. Right-click the OLAP Administrators group and then click Properties.
5. Click Add.
6. In Enter the object names to select, type the name of the Windows account tha
t you
want to add to the group, and then click OK.
7. Click OK.
Note The OLAP Administrators user group to which you want to add the account wil
l not
exist unless you have Analysis Services or DSO on your computer. If Analysis Ser
vices is not
installed on the computer on which Project Server 2003 is installed, you must in
stall DSO
on that computer. For more information about DSO, see the topic Install Decision
Support
Objects, in Chapter 4, Prepare the Servers, of the Microsoft Office Project Serv
er 2003
Installation Guide.
For more information about configuring IIS to use SSL, see your IIS documentatio
n.
.. To enable IIS on a computer running Windows 2000 Server
1. Click Start, click Settings, and then click Control Panel.
2. Double-click Add/Remove Programs.
3. Select Configure Windows, click the Components button, and then follow the on
-
screen instructions to install, remove, or add components to IIS.
6. Click Next, and then click Next again to begin the installation.
7. When the installation is complete, on the This Server is Now an Application s
erver
page, click Finish.
8. Close the Manage Your Server application.
9. Click Start, point to Administrative Tools, and then click Internet Informati
on
Services (IIS) Manager.
10. In Internet Information Services Manager, click the plus (+) sign next to th
e server
name, and then right-click the Web Sites folder and select Properties.
11. Click the Service tab.
12. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolatio
n
mode check box, and then click OK.
Note The Run WWW service in IIS 5.0 isolation mode check box is only selected if
you
upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Windows 2000 Server.
New
installations of IIS 6.0 default to IIS 6.0 worker process isolation mode.
Configure Internet Explorer Enhanced Security
By default, Microsoft Windows Server 2003 provides a set of security settings cal
led
Internet Explorer Enhanced Security Configuration. These settings limit the type
s of
content that a user at the server can view by using Microsoft Internet Explorer,
except for
sites listed in the Local intranet and Trusted sites zones. For example, by defa
ult,
scripting on Internet pages will not run. The goal of these settings is to help
ensure that a
local user on a computer that is also running as a server will not download a vi
rus or other
harmful files from the Internet and infect the server. Internet Explorer Enhance
d Security
Configuration does not affect remote users who view content on the server; it af
fects only
users running Internet Explorer on the server itself.
Using Internet Explorer Enhanced Security Configuration on a Web server running
Project
Server 2003 or Windows SharePoint Services prevents some code that is necessary
for
viewing site pages or Administration pages from running. Remote users with prope
r access
rights can still view the pages correctly, but a user running Internet Explorer
on the server
will be unable to view or administer the site. The user at the server will also
be unable to
view and administer a remote SharePoint or Project Server site, because of the s
ecurity
settings.
To help ensure that Windows SharePoint Services and Project Server 2003 work pro
perly
in your environment, you can do one of the following:
Uninstall Internet Explorer Enhanced Security Configuration. If you are not
concerned about users working locally at the Web server, an administrator can un
install
Internet Explorer Enhanced Security Configuration by using Add or Remove
Programs.
Add the SharePoint and Project Server sites to the list of Local intranet sites.
This is a more time-consuming solution, but potentially more secure. A server
administrator can add the URLs of all virtual servers that are being hosted to t
he
Internet Explorer Local intranet zone.
5. Click Finish.
.. To add the SharePoint and Project Server sites to the list of Local intranet
sites
1. On the computers on which you will install Windows SharePoint Services and Pr
oject
Server, open Internet Explorer.
2. On the Tools menu, select Internet Options.
3. Click the Security tab, and then click the Local intranet icon.
4. Click Sites.
5. Click Advanced.
6. Type the URL for the site that you want to add, and then click Add.
7. Repeat step 6 for each site that you want to add. When you are finished addin
g sites,
click Close, and then click OK.
5
Configure Windows SharePoint
Services
You can install Microsoft® Windows® SharePoint® Services in one of the following
configurations:
New database If you are installing the first instance of Windows SharePoint Serv
ices
in your Microsoft Office Project Server 2003 deployment, and you are using Micro
soft
SQL Server 2000 for your Windows SharePoint Services database, follow the
procedures for installing Windows SharePoint Services with a new database.
Existing database If you are installing a second copy of Windows SharePoint
Services for use on a network load balancing cluster, or if you need to reinstall
Windows SharePoint Services and connect to your existing Windows SharePoint
Services content database, follow the procedures for installing Windows SharePoi
nt
Services with an existing database.
WMSDE If you are installing Windows SharePoint Services to use Microsoft
Desktop Engine (Windows) (WMSDE), follow the procedures for installing Windows
SharePoint Services with WMSDE.
If you choose to install Windows SharePoint Services later, you must use Project
Web
Access to configure Project Server 2003 to connect to Windows SharePoint Service
s. For
more information, see the topic Configuring Windows SharePoint Services Settings
in
Chapter 8, Post-Installation Tasks of the Microsoft Office Project Server 2003 I
nstallation
Guide.
Note If you configure Windows SharePoint Services to use Secure Sockets Layer (S
SL), you must
use SSL for both the Administration site and the virtual server. The virtual ser
ver must be
configured to use the default port of 443.
If you do not have Windows SharePoint Services, you can download it from the Mic
rosoft
Web site (http://go.microsoft.com/fwlink/?LinkId=23448).
Installing Windows SharePoint Services with a New Database
If you are installing the first instance of Windows SharePoint Services in your
deployment,
follow the procedures in this topic.
Install Windows SharePoint Services
Install Windows SharePoint Services by using the following procedure.
.. To install Windows SharePoint Services
1. Go to the Windows SharePoint Services Technology Center on the Microsoft Web
site
(http://go.microsoft.com/fwlink/?LinkId=23448).
2. Download the Windows SharePoint Services installation files to your computer
and
start the Windows SharePoint Services Setup program. When selecting the Windows
SharePoint Services file to download, select the language pack that matches the
Project
Server 2003 default installation language.
Note If you selected to Open the file on the File Download page, the Windows Sha
rePoint
Services Setup program will start automatically after the file is downloaded. If
you selected
to Save the file on the File Download page, after the download completes, click
the file to
start the Windows SharePoint Services Setup program.
3. In the End-User License Agreement (EULA) dialog box, review the terms, select
the I accept the terms in the License Agreement check box, and then click Next.
4. In the Type of Installation dialog box, select the Server Farm option, and th
en click
Next.
5. In the Summary dialog box, verify that only Windows SharePoint Services will
be
installed, and then click Install.
Setup runs and installs Windows SharePoint Services. When Setup completes, a bro
wser
opens and the Configure Admin Virtual Server page is displayed.
Note If you receive a Page cannot be displayed error, in the Internet Explorer a
ddress bar, replace
localhost with the name of the computer on which you installed Windows SharePoin
t Services.
Configure the Administrative Virtual Server
After Windows SharePoint Services Setup is complete, you can configure your
administrative virtual server, including specifying an application pool to use f
or the virtual
server processes, by using the Configure Administrative Virtual Server page.
Application pools are an Internet Information Services 6.0 feature that enables
you to use
an isolated process to run Web applications. Each pool is uniquely identified on
the Web
server, so you know which applications are performing which actions. If an appli
cation
fails, it will not affect other applications that are also running. Each applica
tion pool must
be configured with a security account that the application pool will run under.
When configuring Windows SharePoint Services to work with Project Server 2003, i
t is
suggested to create a new application pool and to select the predefined Network
Services
account (NT AUTHORITY\Network Services) that is available on the local computer.
Note The Configure Administrative Virtual Server page opens automatically when t
he Windows
SharePoint Services installation is complete. You can also access the Configure
Administrative
Virtual Server page by selecting SharePoint Central Administration in Administra
tive Tools.
The Configure Administrative Virtual Server page.
10. When Internet Information Services (IIS) restarts, close the command prompt
window
and return to your browser.
11. On the Application Pool Changed page, click OK.
7. Click OK.
This user will receive any quota or auto-deletion notices, and is automatically
granted
Windows SharePoint Services administrator rights. You can use any Windows domain
account for this purpose.
7. In the E-mail box, type the e-mail address for the owner of this virtual serv
er.
8. Click OK.
8. On the next page, in the Site Owner User Name box, type the Windows account
name for the site owner.
For more information about Windows SharePoint Services site owners, see the
Microsoft Windows SharePoint Services Administrator s Guide
(http://go.microsoft.com/fwlink/?LinkId=12860).
9. In the Site Owner E-mail address box, type the e-mail address for the site ow
ner,
and then click Next.
Windows SharePoint Services is now configured to work with Project Server 2003.
Installing Windows SharePoint Services with an Existing
Database
If you are installing a second copy of Windows SharePoint Services for use on a
network
load balancing cluster, or if you need to reinstall Windows SharePoint Services an
d
connect to your existing database, follow the steps in this topic.
Install Windows SharePoint Services
Install Windows SharePoint Services by using the following procedure.
.. To install Windows SharePoint Services
1. Go to the Windows SharePoint Services Technology Center on the Microsoft Web
site
(http://go.microsoft.com/fwlink/?LinkId=23448).
2. Download the Windows SharePoint Services installation files to your computer
and
start the Windows SharePoint Services Setup program. When selecting the Windows
SharePoint Services file to download, select the language pack that matches the
Project
Server 2003 default installation language.
Note If you selected to Open the file on the File Download page, the Windows Sha
rePoint
Services Setup program will start automatically after the file is downloaded. If
you selected
to Save the file on the File Download page, after the download completes, click
the file to
start the Windows SharePoint Services Setup program.
3. In the End-User License Agreement (EULA) dialog box, review the terms, select
the I accept the terms in the License Agreement check box, and then click Next.
4. In the Type of Installation dialog box, select the Server Farm option, and th
en click
Next.
5. In the Summary dialog box, verify that only Windows SharePoint Services will
be
installed, and then click Install.
Setup runs and installs Windows SharePoint Services. When Setup completes, a bro
wser
opens and the Configure Admin Virtual Server page is displayed.
Configure the Administrative Virtual Server
After the setup process is complete, you can configure your administrative virtu
al server
including specifying an application pool to use for the virtual server processes b
y using
the Configure Administrative Virtual Server page.
Application pools are an Internet Information Services 6.0 feature that enables
you to use
an isolated process to run Web applications. Each pool is uniquely identified on
the Web
server, so you know which applications are performing which actions. If an appli
cation
fails, it will not affect other applications that are also running. Each applica
tion pool must
be configured with a security account that the application pool will run under.
When configuring Windows SharePoint Services to work with Project Server 2003, i
t is
suggested to create a new application pool and to select the predefined Network
Services
account (NT AUTHORITY\Network Services) that is available on the local computer.
Note The Configure Administrative Virtual Server page opens automatically when t
he Windows
SharePoint Services installation is complete. You can also access the Configure
Administrative
Virtual Server page by selecting SharePoint Central Administration in Administra
tive Tools.
The Configure Administrative Virtual Server page
For more information about Windows SharePoint Services site owners, see the
Microsoft Windows SharePoint Services Administrator s Guide on the Microsoft Web s
ite
(http://go.microsoft.com/fwlink/?LinkId=12860).
9. In the Site Owner E-mail address box, type the e-mail address for the site ow
ner,
and then click Next.
3. In the End-User License Agreement (EULA) dialog box, review the terms, select
the I accept the terms in the License Agreement check box, and then click Next.
4. In the Type of Installation dialog box, select the Typical Installation optio
n, and
then click Next.
5. In the Summary dialog box, click Install.
9. In the Site Owner E-mail address box, type the e-mail address for the site ow
ner,
and then click Next.
6. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
7. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
8. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
When the script finishes successfully, partition the database if necessary, and
then install
Project Server 2003 and connect to the new database during Project Server Setup.
Important These procedures should only be used by someone who is familiar with S
QL
Server 2000 and experienced with the database creation process, security, and ed
iting and
executing scripts across a multi-server environment. All steps listed in these p
rocedures must be
performed in the order in which they are listed.
The files required for the procedures in this topic can be found on the Project
Server 2003
CD in the Support/Database folder. It is recommended that you copy this folder t
o each
of the database computers in your deployment.
Partitioning the View Tables
You can move the Project Server 2003 View tables to a separate database server.
This
configures the databases as follows:
Main database server Contains the Web tables, Cube tables, Project tables, and
Security views.
View Tables database server Contains the View tables.
Project Server Setup can partition the View tables for you when you are installi
ng Project
Server 2003. If you prefer to do so manually before running Project Server Setup
, complete
the following procedures.
.. To configure the View Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database f
or the
View tables (for example, ProjectServerVIEW).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
4. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
5. Using SQL Server Query Analyzer and connecting with your login account, run
ViewTbls.sql from within the Project Server View database context.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your View Tables database server.
4. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
5. Using SQL Server Query Analyzer and connecting with your login account, run t
he
following scripts from within the Project Server database context:
a. ProjTbls.sql
b. WebTbls.sql
c. CubeTbls.sql
d. SecViews.sql
e. ProjSPS.Sql
f. WebSPS.Sql
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database f
older)
and connecting to the main database with your login account, run PjcrtSPS.sql.
Important You must run this script with Osql. SQL Server Query Analyzer will not
open this
script file because of the line length of the binary data in the last UPDATE com
mand. The
Osql command must be in the following format and must be run from the command li
ne on
the server. You can run this command-line tool from either database server.
osql S <MainDatabaseServerName> -d <MainDatabaseName> -U <Login>
-P <Password> -i <Input File>
For example:
osql S PSMain d ProjectServerMAIN U MyAccount P hello i
PjcrtSPS.sql
7. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
8. Using SQL Server Query Analyzer and connecting with your login account, run
LnkViews.sql from within the Project Server database context.
9. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW
10. Using SQL Server Query Analyzer and connecting with your login account, run
the
following scripts in order listed:
Note These files can be found in the Database\1033 folder.
a. LocData.sql
b. EGlobal.sql
Important You must run this script with Osql. For more information about using O
sql,
see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=20509).
c. InsDef.sql
d. InsDefLP.sql
3. In the Database server box, type the name of the SQL Server instance that you
will
use for the Main database server.
4. In the Database name box, type the name of the Project Server database that y
ou
created on the server, and then click Next.
5. On the Enter connection information for View tables page, clear the Connect t
o
the main Project Server 2003 database check box.
6. In the Database server box, type the name of the View Tables database server.
7. In the Database name box, type the name of the Project Server View database t
hat
you created on that server.
Main database server Contains the Web tables, Cube tables, and View tables.
Project Tables database server Contains the Project tables and Security views.
Project Server Setup cannot create this database configuration when you are inst
alling
Project Server 2003. If you want to partition the Project tables, follow the pro
cedures in
this topic before you run Project Server Setup.
.. To configure the Project Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database f
or the
Project Tables (for example, ProjectServerPROJ).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
4. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
5. Using SQL Server Query Analyzer and connecting with your login account, run t
he
following scripts in the listed order from within the Project Tables database co
ntext:
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database f
older)
and connecting to the ProjectServerPROJ database with your login account, run
PjcrtSP1.sql.
Important You must run this script with Osql. SQL Server Query Analyzer will not
open this
script file because of the line length of the binary data in the last UPDATE com
mand. The
Osql command must be in the following format and must be run from the command li
ne on
the server. You can run this command-line tool from either database server.
osql S <DatabaseServerName> -d <DatabaseName> -U <Login> -P
<Password> -i <Input File>
For example:
osql S PSProj d ProjectServerPROJ U MyAccount P hello i
PJCRTSP1.SQL
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your Project Tables database server.
7. Using SQL Server Query Analyzer and connecting with your login account, run
LNKPROJ.SQL from within the Project Server Main database context.
8. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
9. Using SQL Server Query Analyzer and connecting with your login account, run t
he
following scripts in the order listed:
Note These files can be found in the Database\1033 folder.
a. LocData.sql
b. EGlobal.sql
Important You must run this script with Osql. For more information about using O
sql,
see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=20509).
c. InsDef.sql
d. InsDefLP.sql
10. Modify the PjcrtSP2.sql script and change the <WinProjServerName> and
<WinProjDatabaseName> parameters on the line where the
MSP_PDS_SP_INSERT_PROJECT_BINARY stored procedure is called, to the
name of the Project Tables SQL Server and the Project Server database respective
ly.
11. Using SQL Server Query Analyzer and connecting with your login account, run
PjcrtSP2.sql from within the Project Server Main database context.
3. In the Database server box, type the name of the instance of SQL Server that
you will
use for the Main database server.
4. In the Database name box, type the name of the Project Server database that y
ou
created on the server, and then click Next.
5. On the Enter Connection Information for View Tables page, select the Connect
to
the main Project Server 2003 database check box.
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select Project Tables.
4. In the SQL Server box, type the name of the Project Tables database server.
5. In the Database box, type the name of the Project Server database that you cr
eated on
that server.
Main database server Contains the Web tables and Cube tables.
Project Tables database server Contains the Project tables and Security views.
View Tables database server Contains the View tables.
The Project Server Setup program cannot create this database configuration when
you run
Setup. If you want to create a three-way partition, follow the procedures in thi
s topic
before you run Project Server Setup.
.. To configure the Project Tables database server
1. Create a new Project Server database (for example, ProjectServerPROJ).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the new database on the Database
Access tab.
4. On the Database Access tab, assign the MSProjectServerRole role to the
MSProjectServerUser login, and then assign the MSProjectRole role to the
MSProjectUser login.
5. Using SQL Server Query Analyzer and connecting with your login account, run t
he
following scripts in the listed order from within the Project Tables database co
ntext.
a. ProjTbls.sql
b. ProjSPS.sql
c. SecViews.sql
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database f
older)
and connecting to the Project Tables database with your login account, run
PjcrtSP1.sql.
Important You must run this script with Osql. SQL Server Query Analyzer will not
open this
script file because of the line length of the binary data in the last UPDATE com
mand. The
Osql command must be in the following format and must be run from the command li
ne on
the server. You can run this command-line tool from either database server.
osql S <MainDatabaseServerName> -d <MainDatabaseName> -U <Login>
-P <Password> -i <Input File>
For example:
osql S PSMain d ProjectServerMAIN U MyAccount P hello i
PJCRTSP1.SQL
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the View Tables database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your Project Tables database server.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your Project Tables database server.
6. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ProjectTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSProj, N'SQL Server'
7. Using SQL Server Query Analyzer and connected with your login account, create
a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
8. Using SQL Server Query Analyzer and connecting with your login account, run
LnkProj.sql from within the Project Server Main database context.
9. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
10. Using SQL Server Query Analyzer and connecting with your login account, run
LnkViews.sql from within the Project Server database context.
11. Using SQL Server Query Analyzer and connecting with your login account, exec
ute the
following stored procedure as follows:
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW
12. Using SQL Server Query Analyzer and connecting with your login account, run
the
following scripts from in the listed order:
Note These files can be found in the Database\1033 folder.
a. LocData.sql
b. EGlobal.sql
Important You must run this script with Osql. For more information about using O
sql,
see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=20509).
c. InsDef.sql
d. InsDefLP.sql
13. Modify the PjcrtSP2.sql script and change the WinProjServerName and
WinProjDatabaseName parameters on the line where the
MSP_PDS_SP_INSERT_PROJECT_BINARY stored procedure is called, to the
name of the Project Tables SQL Server and the Project Tables database respective
ly.
14. Using SQL Server Query Analyzer and connecting with your login account, run
PjcrtSP2.sql from within the Project Server database context.
3. In the Database server box, type the name of the instance of SQL Server that
you
used for the Main database server.
4. In the Database name box, type the name of the Project Server database that y
ou
created on that server, and then click Next.
5. On the Enter connection information for Views tables page, clear the Connect
to
the main Project Server 2003 database check box.
6. In the Database server box, type the name of the View Tables database server.
7. In the Database name box, type the name of the View Tables database that you
created on that server.
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select Project Tables.
4. In the SQL Server box, type the name of the Project Tables database server.
5. In the Database box, type the name of the Project Server database that you cr
eated on
that server.
7. In the MSProject Role Member section, type MSProjectUser for the user name an
d
the password that you chose for that account.
10. In the Database box, type the name of the View Tables database that you crea
ted on
that server.
11. In the MSProjectServer Role Member section, type MSProjectServerUser for the
user name and the password that you chose for that account.
12. In the MSProject Role Member section, type MSProjectUser for the user name a
nd
the password that you chose for that account.
13. From the list, select Web Tables.
14. In the SQL Server box, type the name of the Project Server Main database ser
ver.
15. In the Database box, type the name of the Project Server Main database.
16. In the MSProjectServer Role Member section, type MSProjectServerUser for the
user name and the password that you chose for that account.
17. In the MSProject Role Member section, type MSProjectUser for the user name a
nd
the password you that chose for that account.
18. Click Save, and then click Exit.
9. Click OK.
7
Install Project Server 2003
Microsoft® Office Project Server 2003 is composed of three services:
Project Server Front-End service The Project Server Front-End service runs on th
e
computer running Internet Information Services (IIS).
Session Manager service The Session Manager service manages user session state i
n
Microsoft Office Project Web Access 2003. When used in a clustered environment,
the
Session Manager service should be deployed on its own server outside the cluster
. This
enables users to be directed to any one of the clustered application servers.
View Processing service The View Processing service creates the project views fo
r
Project Web Access. Each time a resource or project is checked in to Project Ser
ver,
the View tables are updated. Because this can be extremely processor-intensive,
moving this service to a separate server can greatly reduce the workload for the
computer running Project Server 2003.
Project Server Setup installs these services. You can install all services on th
e same
computer, or you can distribute the services across multiple computers.
If you distribute Project Server services across multiple computers, you must ru
n Project
Server Setup on each computer on which you want to run a service.
For more information about when to install Project Server services on separate c
omputers,
see the Microsoft Office Project Server 2003 Configuration Planning Guide
(http://go.microsoft.com/fwlink/?LinkID=20235).
To see a visual representation of the relationships between the various Project
Server Setup
steps, see the Project Server Setup Flow Diagram on the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=21681).
Note Do not install Project Server 2003 on a computer running Project Profession
al 2002.
Starting Project Server Setup
Use the following procedure to start Project Server Setup.
.. To start Project Server Setup
1. On the computer on which you want to install Project Server 2003, insert the
Project
Server 2003 CD into the CD-ROM drive, or connect to a network installation point
.
2. If you are installing from the Project Server 2003 CD with AutoPlay enabled,
Setup
starts automatically. Otherwise, on the Project Server 2003 CD (or network insta
llation
point), browse for and run the file Setup.exe.
User Information
You can use the User Information page to enter your user information. This infor
mation
is not required by Project Server 2003.
The User Information page.
Note This page appears for all installations.
The Choose the services you want to install on this server page.
Note This page appears for all installations.
If you are installing the View Processing service or the Session Manager service
on a
different computer than the Project Server Front-End service, you must install t
he Project
Server Front-End service after you have installed the View Processing and Sessio
n Manager
services. Setup will require you to specify the location of the View Processing
and Session
Manager services when you install the Front-End service.
If you are installing the Project Server Sample Data, all Project Server service
s must be
installed on the same computer along with Microsoft SQL Server 2000, Microsoft
Windows® SharePoint® Services, and SQL Server Analysis Services (if applicable). For
information about configuring the sample data after installation, see Appendix D
,
Configuring the Sample Database in the Microsoft Office Project Server 2003 Inst
allation
Guide.
Note You cannot install the Project Server Sample Data on a domain controller.
If you are not installing all of the Project Server services on this computer, c
lear the service
options that you do not want to install.
.. To clear an option
Click the arrow next to the option name, and then click Not Available.
.. To select an option
Click the arrow next to the option name, and then click Run from My Computer.
When you are finished selecting the options that you want to install, click Next
.
Create the View Processing Share
When projects are published to Project Server 2003, a copy of the project is use
d to create
project view data. When you install the View Processing service on a different c
omputer
than the computer on which the Project Server Front-End service is installed, Se
tup creates
a shared folder (also called a share) where Project Server will stage updated vi
ew
information that is generated when projects are published from Microsoft Office
Project
Professional 2003.
Use the Enter the Views Processing server information page to specify the name o
f this
share, as well as a computer account that has sufficient rights to create it.
Note If the Views Staging share is located in a non-trusted domain, Setup might
not be able to
validate the Windows user account that you specified. If Setup is not able to va
lidate your user
account, use Windows Explorer to log on to the share and then try again.
Choosing Database Options
If you are running Project Server 2003 more than once in order to install servic
es on more
than one computer, be sure to create a new database only once, and connect to th
at
database on subsequent installations.
Connecting to an Existing Database
If you have already created your Project Server database, or if you are connecti
ng to an
upgraded Microsoft Project Server 2002 or Microsoft Project Central database, ch
oose the
Connect to another existing database option on the Enter database server
information page.
Connect to an Existing Database
When you are connecting to an existing database, the Enter database server infor
mation
page prompts you for the name of the database and the server on which it is loca
ted.
.. To specify a password for Project Server 2003 to use to connect to the databa
se
1. In the top Password box, type the password that you want to use.
2. In the top Confirm password box, type the password again.
.. To create View tables as part of the main Project Server 2003 database
1. Select the Connect to the main Project Server 2003 database check box.
2. Click Next.
.. To create View tables on a different server from the main Project Server 2003
database
1. Clear the Connect to the main Project Server 2003 database check box.
2. In the Database server box, type the name of the SQL Server instance on which
you
want to create the View tables.
3. In the Logon name box, type the name of the SQL Server account that you want
to
use to create the database.
4. In the Password box, type the password for the SQL Server account.
5. Click Next.
Create Database Account Information
When Setup creates a new database for use with Project Server 2003, the accounts
used by
Project Server 2003 and Project Professional 2003 to access the database are cre
ated
automatically. Use the Create database account information page to specify the
password to use with these accounts.
.. To specify a password for Project Server 2003 to use to connect to the databa
se
1. In the top Password box, type the password that you want to use.
2. In the top Confirm password box, type the password again, and then click Next
.
It is recommended that you enter this information when you install Project Serve
r 2003,
unless the analysis server is in a non-trusted domain. If the analysis server is
in a non-
trusted domain, choose the Enter this information later option.
If you choose the Enter this information later option, you need to run the Proje
ct Server
COM+ Settings tool (PSCOMPlus.exe) and update the analysis server information in
Project Web Access 2003. For more information, see the topic Configuring Analysi
s
Services Settings in Chapter 8, Post-Installation Tasks of the Microsoft Office
Project
Server 2003 Installation Guide.
Select a Web Site
Use the Select a Web site page to select the Web site on which the Internet Info
rmation
Service (IIS) virtual directory for Project Server 2003 is to be installed. You
can choose the
default Web site or another site that you have created for the purpose.
The Select a Web site page.
Note This page appears when you are installing the Project Server Front-End serv
ice.
If you choose the Enter this information later option, you need to enter this in
formation
after Project Server Setup finishes. For more information, see the topic Configu
ring Web
Server Address Settings in Chapter 8, Post-Installation Tasks of the Microsoft O
ffice
Project Server 2003 Installation Guide.
Note If you upgraded your database from Microsoft Project Server 2002 and you ch
oose the Enter
this information later option, Microsoft Project Server 2002 Web server address
information might
remain in the database. It is strongly recommended that you enter this informati
on when you are
installing Project Server 2003.
Enter SMTP Mail Server Information
Use the Enter SMTP mail server information page to specify the Simple Mail Trans
fer
Protocol (SMTP) mail server that you want to use for Project Server notification
s and
reminders.
The Connect to a Web server running Microsoft Windows SharePoint Services page.
Note This page appears when you are installing the Project Server Front-End serv
ice.
Important If you use a fully qualified domain name (FQDN) for the Windows ShareP
oint Services
administration URL, you must use a FQDN for the Windows SharePoint Services URL
as well.
It is recommended that you enter this information when you install Project Serve
r 2003. If
you choose the Enter this information later option, you need to enter this infor
mation
after Project Server Setup completes. For more information, see the topic Config
uring
Windows SharePoint Services Settings in Chapter 8, Post-Installation Tasks of th
e
Microsoft Office Project Server 2003 Installation Guide.
Enter Windows SharePoint Services Account Information
Use the Enter account information for Microsoft Windows SharePoint Services
(continued) page to specify the Windows SharePoint Services administrator accoun
t.
The Enter account information for Microsoft Windows SharePoint Services (continu
ed)
page.
Note This page appears when you are installing the Project Server Front-End serv
ice. This page will
not appear if you chose the Enter this information later option on the Connect t
o a Web server
running Microsoft Windows SharePoint Services page.
The Connect to a Web server running Microsoft SharePoint Portal Server 2003 page
.
Note This page appears when you are installing the Project Server Front-End serv
ice. This page will
not appear if you chose the Enter this information later option on the Connect t
o a Web server
running Microsoft Windows SharePoint Services page.
3. Click Next.
b. In the Username box, type the user name for the account that you are using as
the Analysis Services administrator.
6. In the Cube Name box, type the name for the OLAP cube you want to build.
.. To update pds.wsdl
1. On the computer running the Project Server Front-End service, using Notepad,
edit
install path\IIS Virtual Root\Pds.wsdl.
2. Replace servername with the name of the server running Project Server 2003 in
the
following line:
<soap:address
location="http://servername/ProjectServer/PDS.WSDL"/>
3. Under Analysis Services (OLAP) Access Identity, clear the Process this identi
ty
update check box.
4. Click Create/Update COM+ Apps.
5. In the Create a site under this SharePoint URL box, type the URL for the Proj
ect
Server 2003 site on the computer running Windows SharePoint Services.
6. In the From address box, type the default e-mail address. This address is the
reply-to
address for all notification and reminder e-mails.
7. In the Company e-mail address box, type the host and domain portion of your
organization s default e-mail address. The company e-mail address is appended to u
ser
e-mail addresses where a host and domain are not specified.
8. Optionally, in the Default e-mail message box, type the default message that
you
want to be appended to all notification e-mails.
9. Click Save Changes.
6. Log on to the computer running Analysis Services by using a user account that
has
permissions that are equivalent to either the Administrators group or OLAP
Administrators group, and start Analysis Manager.
7. In the left pane, expand Analysis Servers.
8. Right-click the name of your server, and then click Migrate Repository to sta
rt the
Migrate Repository Wizard. Migrate the repository to the database that you creat
ed.
Note It is recommended that you choose the Analysis Services native format when
migrating the repository.
9. After you migrate the repository to a SQL Server database, you can safely del
ete the
old repository. By default, this database is \Program Files\Microsoft Analysis
Services\Bin\msmdrep.mdb.
5. On the Membership tab, click Add to add users and groups to the role, and the
n click
OK.
6. On the Cubes tab, click Check All to enable access to all three cubes in the
database.
For more information about the Windows administrative tools, see your Microsoft
Windows 2000 Server or Microsoft Windows Server 2003 documentation.
.. To enable Basic authentication for the Project Server virtual directory
1. On the left pane of the Internet Information Services window, right-click the
virtual
directory, and then click Properties.
2. Click the Directory Security tab and then click Edit in the Authentication Co
ntrol
section.
3. Select the Basic authentication check box, and then click Yes when asked if y
ou
want to continue.
4. Click OK to apply your changes, and then click OK to close the dialog box.
5. Click OK to close the Inheritance Overrides dialog box without making any cha
nges.
Note For more information about these deployment methods, see the topic Installi
ng Office 2003
in the Microsoft Office 2003 Resource Kit (http://go.microsoft.com/fwlink/?LinkI
d=31582).
Set Up Connection Information for Project Server 2003
In order for you to connect Project Professional to Project Server 2003, the use
r s account
name and connection information must be entered in the Account Properties dialog
box
in Project Professional. This information must specify a valid user name that ca
n
authenticate to the computer running Project Server 2003 as well as specify the
URL for
the computer running Project Server 2003.
.. To set up connection information
1. In Project Professional, click Tools, point to Enterprise Options, and then s
elect
Microsoft Office Project Server Accounts.
2. In the Project Server Accounts dialog box, click Add to open the Account
Properties dialog box.
3. In the Account Properties dialog box, enter the user account name, the URL fo
r the
computer running Project Server 2003, and the type of user account, and indicate
whether this is the default account. If Use Windows user account is selected und
er
When connecting, Project Professional will authenticate by using the user s
Windows NT user account.
4. Click Test Connection to verify that the URL for the computer running Project
Server 2003 enables you to connect to the server properly. When you are finished
, click
OK twice to save the user account information.
5. Close and restart Project Professional.
5. In the Add This Web site to the zone box, enter the URL.
6. Click Add.
7. Click OK twice to exit the Internet Options menu.
4. Set the new copy of Msolap.asp to use Basic authentication and Integrated Win
dows®
authentication by doing the following:
a. Open Internet Information Services (IIS) Manager.
b. Expand Web Sites and find the Web site on which you placed the copy of
Msolap.asp.
c. Right-click Msolap.asp and then click Properties.
d. Click the File Security tab and then make changes in the Anonymous Access
and Authentication Control dialog box.
e. Be sure that both the Basic authentication and Integrated Windows
authentication check boxes are selected.
Note It is strongly recommended that SSL be used on the server running Analysis
Services so that data is encrypted when it is sent between client and server. It
is
particularly important that Microsoft Windows passwords are encrypted by means o
f
SSL.
5. Set up connection strings in the Portfolio Analyzer view. After the server ru
nning
Analysis Services is configured to be available over the Internet, you must comp
lete the
following steps for all Portfolio Analyzer views that will be available over the
Internet::
a. On a computer that is within the intranet, log on to Microsoft Office Project
Web
Access 2003 as an administrator.
b. Click Admin.
c. On the Administration overview page, click Manage enterprise features.
d. In the OLAP cube name and description section, in the Analysis Server
extranet address box, type the extranet address for the server running Analysis
Services. This will be used later when a user tries to view a Portfolio Analyzer
view
that is built on the intranet from the extranet. This enables the administrator
to
create views that are accessible from the intranet as well as the extranet.
Optionally, you can create views that are accessible only by means of the extran
et by
doing the following:
a. On the Administration overview page, click Manage views.
b. Click Add View.
c. Select the Portfolio Analyzer option.
d. In the Analysis Server box, type the extranet address for the analysis server
, and
then click Apply to bind to the cube over the extranet.
When you save this view, it will be accessible only by means of the extranet.
When users try to access this extranet-enabled view from Microsoft Project or fr
om the
Resource Center of Microsoft Project Web Access, they will be prompted to enter
their
Windows user account name and password before they can see the view. Because the
Windows user account name and password are sent in plaintext, you should be sure
to
configure Project Web Access to use SSL so that information will be sent encrypt
ed.
Configure Your Deployment
To configure your Project Server deployment for extranet access, complete the fo
llowing
procedure.
Name
Type
Data
IsExtranet
REG_DWORD
1
6. On the Project Server installation that is located outside your firewall, add
the
following registry keys under HKLM\Software\Microsoft\Office\11.0\MS
Project\Webclient Server\ProjectServer\Datasets\Application:
Name
Type
Data
ExtranetServerName
REG_SZ
Server name; for example,
example.com.
ExtranetServerProtocol
REG_SZ
Http or https.
ExtranetServerPort
REG_SZ
Extranet port number.
7. On the computer running Windows SharePoint Services, edit the web.config file
in the
home directory of the Web site on which Windows SharePoint Services is installed
(C:\Inetpub\WWWRoot if Windows SharePoint Services is extended on the Default
Web Site) by doing the following:
a. Open Web.Config in Notepad.
b. Search for the Section called <appSettings>. It might or might not exist.
c. If it does not exist, search for </Sharepoint>. The next section is <system.w
eb>
d. Just after </Sharepoint>, and just before <system.web>, add the following lin
es:
<appSettings>
<add key="PWANetwork" value="EXTRANET" />
</appSettings>
e. Save web.config.
f. Reset Internet Information Services.
If you are using Windows SharePoint Services, create identical local Windows acc
ounts
that have identical passwords for the Windows SharePoint Services administrator
on
the computer running Project Server 2003 and on the computer running Windows
SharePoint Services.
If you are using Analysis Services, create identical local Windows accounts that
have
identical passwords for the Analysis Services administrator on the computer runn
ing
Project Server 2003 and on the computer running Analysis Services.
Note In a Novell environment, Project Server 2003 does not support the synchroni
zation of users
with the Novell Directory Service (NDS). Project Server 2003 can only synchroniz
e users with Active
Directory® directory service.
.. To create a local user account
1. On the computer on which you want to create the account, open Computer
Management.
2. Expand Local Users and Groups.
3. Right-click Users and click New User.
4. In the User name box, type a name for the user.
5. In the Description box, type a description for the user account.
6. In the Password and Confirm password boxes, type the user's password.
7. Clear the User must change password at next logon check box.
8. Click Create.
MSP_UTIL_EXEC_MOVE_DATABASE_FILES
This stored procedure moves the default (or current) data file and log file to a
new location
(for example, it can move .mdf and .ldf files from drive C to drives D and E, re
spectively).
The new data and log files do not need to be created ahead of time. If the datab
ase has
more than one data or log file, the stored procedure can be edited accordingly.
This stored procedure is self-contained and calls no component utility stored pr
ocedures.
MSP_UTIL_EXEC_MOVE_TABLES_TO_FILEGROUP
This stored procedure moves tables from the default (or current) file group to a
new file
group. You must create the file group ahead of time. You can choose to move all
tables in
the database, or you can move tables of a particular type. The types of tables i
nclude:
MSP_PROJ_n (Microsoft Office Project tables)
MSP_PROJ_WEB_n (Microsoft Office Project Web Access online transaction
tables)
MSP_VIEW_n (Project Web Access View tables)
MSP_CUBE_n (Microsoft Office Project Server OLAP staging tables)
The new file group must be created ahead of time. You can create the new file gr
oup by
using the stored procedure MSP_UTIL_ADD_FILEGROUP_AND_DATAFILES
provided in the script file. If you want to move an explicit list of tables, the
associated
component utility stored procedures must be updated. The master stored procedure
calls
the following component utility stored procedures:
MSP_UTIL_ADD_CLUSTERED_IDENTITY_TO_BLOBS
MSP_UTIL_MOVE_CLUSTERED_INDEXES
MSP_UTIL_DROP_TEMP_CLUSTERED_IDENTITY
MSP_UTIL_EXEC_MOVE_INDEXES_TO_FILEGROUP
This stored procedure moves non-clustered indexes from the default (or current)
file group
to a new file group. The file group must be created ahead of time. You can move
all non-
clustered indexes in the database, or indexes of a particular type. The types in
clude:
MSP_PROJ_n (Microsoft Office Project tables)
MSP_PROJ_WEB_n (Project Web Access online transaction tables)
MSP_VIEW_n (Project Web Access View tables)
MSP_CUBE_n (Microsoft Office Project Server OLAP staging tables)
Database Partitioning
As the number of users who access the computer running Project Server 2003 incre
ases,
performance can degrade. During the Project Server Setup process, you can choose
to use
a different instance of SQL Server for the View tables than you use for the rest
of the
database. You can also manually partition databases after installation to create
two- and
three-way partitions. When the database is partitioned, additional SQL views are
created in
each database to enable access to the tables that are located in the other serve
rs. Separate
registry keys are created that include the connection information for each serve
r.
Database partitioning for Project Server 2003 improves the performance of open,
save, and
publish operations. It is important to note, however, that a partitioned databas
e
configuration is beneficial for only a small percentage of Project Server deploy
ments, and
can negatively impact some aspects of the performance of a Project Server deploy
ment..
Before using database partitioning, explore ways to improve the performance of S
QL
Server 2000. Most organizations can find ways to improve the performance of thei
r system
without partitioning the database.
Before applying a partitioned database configuration to your Project Server depl
oyment,
consider the following:
Partitioning the database does not improve the overall performance of the Projec
t
Server database. A partitioned database configuration is beneficial for the foll
owing
types of Project Server deployments:
Deployments that include several thousand Project Web Access users and with a
high ratio of project managers to team members (Project Web Access users).
Deployments for which projects require frequent updates, and the average project
contains a large number of tasks and assignments.
Deployments in which the open, save, and publish operations are used at a high
frequency throughout the day.
A partitioned database configuration includes the following possible disadvantag
es:
Increased administrative overhead required for the maintenance of the computer
running Project Server 2003, including a proportional increase of backup and
restore procedures and a greater number of servers that need to be maintained in
a
failover scenario.
Increased sensitivity to server downtime; organizations are required to maintain
more servers for a single installation of Project Server 2003.
Slower performance of certain types of Project Web Access views, including the
Resource Center (potentially a significant decrease in performance), Timesheets,
and the Project Center. These views require the retrieval of large amounts of da
ta
across all partitioned databases. Do not partition the Project Server database i
f
your organization must use the Resource Center frequently; for example, if your
organization includes several thousand users and is planning to use the Timeshee
ts
feature in Project Web Access to track and record actual work against project
tasks.
Important These procedures should only be used by someone who is familiar with S
QL
Server 2000 and experienced with database creation, security, and editing and ex
ecuting scripts
across a multi-server environment. All steps in these procedures must be perform
ed in the order
listed. Always create full database backups before attempting any database parti
tioning.
Partitioning the View Tables
If your deployment is configured with all the Project Server database tables in
one
database, you can move the Project Server View tables to a separate database ser
ver. The
databases are configured as follows:
Main database server Contains the Web tables, Cube tables, Project tables, and
Security views.
View database server Contains the View tables.
Important Always create full database backups before attempting any database par
titioning.
.. To configure the View Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database f
or the
View tables (for example, ProjectServerVIEW).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the View Tables database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your View tables database server.
2. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
3. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateViewTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ViewTablesDatabaseServerName>, <ViewTablesDatabaseName>,
<ViewTablesDatabaseServer Account Login Name>,
<ViewTablesDatabaseServer Account Password>, <Local File Path to
Temporarily Hold BCP Files>
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServer, MyAccount, hello,
PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
4. Using SQL Server Query Analyzer and connecting with your login account, run
LnkView.sql, from within the Project Server database context.
5. Verify that the View tables were successfully created and populated on the ne
w View
Table database server.
6. On the Main database server, using SQL Server Query Analyzer and connected wi
th
your login account, execute the ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW.
The local View table will no longer be used and database views pointing to the V
iew
table on the new View Table database server will be created.
2. Select the Partitioned database configuration option, and then select the Sta
ndard
2-Way Deployment option.
3. From the list, select View Tables.
4. In the SQL Server box, type the name of the View Tables database server.
5. In the Database box, type the name of the Project Server View database that y
ou
created on that server.
6. In the MSProjectServer Role Member section, type MSProjectServerUser for the
user name and the password that you chose for that account.
7. In the MSProject Role Member section, type MSProjectUser for the user name an
d
the password that you chose for that account.
Server running the Main database Contains the Web tables, Cube tables, and View
tables.
Server running the Project Tables database Contains the Project tables and
Security views.
Important Always create full database backups before attempting any database par
titioning.
.. To configure the Project Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database f
or the
Project tables (for example, ProjectServerPROJ).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSROLES.SQL from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your Project Tables database server.
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database f
older)
and connecting to the Project Tables database with your login account, run
PjcrtSP1.sql.
Important You must run this script with Osql or SQL Server Query Analyzer will n
ot open
this script file because of the line length of the binary data in the last UPDAT
E command.
The Osql command must be in the following format and must be run from the comman
d
line on the server. You can run this command-line tool from either database serv
er.
osql S <ProjectTablesDatabaseServerName> -d
<ProjectTablesDatabaseName> -U <Login> -P <Password> -i <Input
File>
For example:
osql S PSProj d ProjectServerPROJ U MyAccount P hello i
PJCRTSP1.SQL
2. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ProjectTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSProj, N'SQL Server'
3. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateProjTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ProjectTablesDatabaseServerName>, <ProjectTablesDatabaseName>,
<ProjectTablesDatabaseServer Account Login Name>,
<ProjectTablesDatabaseServer Account Password>, <Local File Path
to Temporarily Hold the BCP Files>
For example:
EXEC MigrateProjTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSProj, ProjectServerPROJ, MyAccount, hello, c:\temp
4. Using SQL Server Query Analyzer and connecting with your login account, run
LnkProj.sql from within the Project Server database context.
5. Verify that the Project tables were successfully created and populated on the
new
server running the Project Tables database.
6. On the server running the Main database, using SQL Server Query Analyzer and
connecting with your login account, execute the ExecLinkedViewsSP stored
procedure as follows:
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
This deletes the local Project tables and creates database views that point to t
he Project
tables on the new server that is running the Project Tables database.
7. Using SQL Server Query Analyzer and connecting with your login account, run
DropSecV.sql from within the Project Server database context.
This deletes the local security views, which now exist in the Project Tables dat
abase.
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select Project Tables.
4. In the SQL Server box, type the name of the Project Tables database server.
5. In the Database box, type the name of the Project Server database that you cr
eated on
that server.
7. In the MSProject Role Member section, type MSProjectUser for the user name an
d
the password that you chose for that account.
Server running Main database Contains the Web tables and Cube tables.
Server running Project Tables database Contains the Project tables and Security
views.
Server running View Tables database Contains the View tables.
Important Always create full database backups before attempting any database par
titioning.
.. To configure the Project Tables database server
1. In SQL Server 2000 Enterprise Manager, create a new Project Server database (
for
example, ProjectServerPROJ).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both the server running the Main database and the server running the Pro
ject
Tables database.
6. Using the Osql tool (on the Project Server 2003 CD in the /Support/Database f
older)
and connecting to the Project Tables database with your login account, run
PjcrtSP1.sql.
Important You must run this script with Osql. SQL Server Query Analyzer will not
open this
script file because of the line length of the binary data in the last UPDATE com
mand. The
Osql command must be in the following format and must be run from the command li
ne on
the server. You can run this command-line tool from either database server.
osql S <ProjectTablesDatabaseServerName> -d
<ProjectTablesDatabaseName> -U <Login> -P <Password> -i <Input
File>
For example:
osql S PSProj d ProjectServerPROJ U MyAccount P hello i
PJCRTSP1.SQL
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the View Tables database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both the server running the Main database and the server running the Vie
w Tables
database.
2. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ProjectTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSProj, N'SQL Server'
3. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
4. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateProjTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ProjectTablesDatabaseServerName>, <ProjectTablesDatabaseName>,
<Project Server Account Login Name>, <ProjectTablesDatabaseServer
Account Password>, <Local File Path to Temporarily Hold BCP
Files>
For example:
EXEC MigrateProjTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSProj, ProjectServerPROJ, MyAccount, hello, c:\temp
5. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateViewTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ViewTablesDatabaseServerName>, <ViewTablesDatabaseName>,
<ViewTablesDatabaseServer Account Login Name>,
<ViewTablesDatabaseServer Account Password>, <Local File Path to
Temporarily Hold BCP Files>
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
6. Using SQL Server Query Analyzer and connected with your login account, run
LnkProj.sql from within the Project Server database context.
7. Verify that the Project tables were successfully created and populated on the
new
server running the Project Tables database.
8. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
The local View table will no longer be used and database views pointing to the V
iew
table on the new View Table database server will be created.
9. Using SQL Server Query Analyzer and connecting with your login account, run
LNKVIEWS.SQL, from within the Project Server database context.
10. Verify that the View tables were successfully created and populated on the n
ew View
Server.
11. Using SQL Server Query Analyzer and connecting with your login account, exec
ute the
ExecLinkedViewsSP stored procedure as follows:
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW
The local View table will no longer be used and database views pointing to the V
iew
table on the new View Table database server will be created.
12. Using SQL Server Query Analyzer and connecting with your login account, run
DropSecV.sql from within the Project Server database context.
This will drop the local security views; these views now exist in the Project Ta
bles
database.
13. Modify the PjcrtSP2.sql script and change the <WinProjServerName> and
<WinProjDatabaseName> parameters on the line where the
MSP_PDS_SP_INSERT_PROJECT_BINARY stored procedure is called, to the
name of the Project Tables SQL Server and the Project Tables database respective
ly.
14. Using SQL Server Query Analyzer and connecting with your login account, run
PjcrtSP2.sql from within the Project Server database context.
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select View Tables.
4. In the SQL Server box, type the name of server running the View Tables databa
se.
5. In the Database box, type the name of the Project Server database that you cr
eated on
that server.
7. In the MSProject Role Member section, type MSProjectUser for the user name an
d
the password that you chose for that account.
10. In the Database box, type the name of the Project Server database that you c
reated on
that server.
11. In the MSProjectServer Role Member section, type MSProjectServerUser for the
user name and the password that you chose for that account.
12. In the MSProject Role Member section, type MSProjectUser for the user name a
nd
the password that you chose for that account.
13. Click Save, and then click Exit.
Server running the Main database Contains the Web tables and Cube tables.
Server running the Project Tables database Contains the Project tables and
Security views.
Server running the View Tables database Contains the View tables.
Important Always create full database backups before attempting any database par
titioning.
.. To configure the server running the Project Tables database
1. In SQL Server Enterprise Manager, create a new Project Server database for th
e
Project tables (for example, ProjectServerPROJ).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both the server running the Main database and the server running the Pro
ject
Tables database.
2. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ProjectTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSProj, N'SQL Server'
3. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateProjTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ProjectTablesDatabaseServerName>, <ProjectTablesDatabaseName>,
<ProjectTablesDatabaseServer Account Login Name>,
<ProjectTablesDatabaseServer Account Password>, <Local File Path
to Temporarily Hold BCP Files>
For example:
EXEC MigrateProjTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSProj, ProjectServerPROJ, MyAccount, hello, c:\temp
4. Using SQL Server Query Analyzer and connecting with your login account, run
LnkProj.sql from within the Project Server database context.
5. Verify that the Project tables were successfully created and populated on the
new
server running the Project Tables database.
6. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows.
EXEC ExecLinkedViewsSP <ProjectTablesDatabaseServerName>,
<ProjectTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSProj, ProjectServerPROJ
This will drop the local Project tables and create database views pointing to th
e Project
tables on the new Project Tables server.
7. Using SQL Server Query Analyzer and connecting with your login account, run
DropSecV.sql from within the Project Server database context.
This will drop the local security views; these views now exist in the Project Ta
bles
database.
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select Project Tables.
4. In the SQL Server box, type the name of the Project Tables database server.
5. In the Database box, type the name of the Project Server database that you cr
eated on
that server.
7. In the MSProject Role Member section, type MSProjectUser for the user name an
d
the password that you chose for that account.
Instance running the Main database Contains the Web tables and Cube tables.
Instance running the Project Tables database Contains the Project tables and
Security views.
Instance running the View Tables database Contains the View tables.
Important Always create full database backups before attempting any database par
titioning.
.. To configure the View Tables database server
1. In SQL Server Enterprise Manager, create a new Project Server database for th
e View
tables (for example, ProjectServerVIEW).
2. Using SQL Server Query Analyzer and connecting with your login account, run
PSRoles.sql from within the Project Server database context.
This script creates the two database roles needed by the Project Server logins:
MSProjectServerRole and MSProjectRole.
3. Using SQL Server Enterprise Manager, go to the Security folder, select Login,
and
create the following two logins: MSProjectServerUser and MSProjectUser. Be sure
to
use SQL Server authentication and to select the Project Server database on the
Database Access tab.
Important Be sure that the user names and passwords for these database logins ar
e the
same on both your Main database server and your Views Tables database server.
2. Using SQL Server Query Analyzer and connecting with your login account, creat
e a
linked server by using the following command:
EXEC sp_addlinkedserver <ViewTablesDatabaseServerName>, N'SQL
Server'
For example:
EXEC sp_addlinkedserver PSView, N'SQL Server'
3. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
following command:
EXEC MigrateViewTablesSP <MainDatabaseServerName>,
<MainDatabaseName>, <MainDatabaseServer Account Login Name>,
<MainDatabaseServer Account Password>,
<ViewTablesDatabaseServerName>, <ViewTablesDatabaseName>,
<ViewTablesDatabaseServer Account Login Name>,
<ViewTablesDatabaseServer Account Password>, <Local File Path to
Temporarily Hold BCP Files>
For example:
EXEC MigrateViewTablesSP PSMain, ProjectServerMAIN, MyAccount,
hello, PSView, ProjectServerVIEW, MyAccount, hello, c:\temp
4. Using SQL Server Query Analyzer and connecting with your login account, run
LinkViews.sql from within the Project Server database context.
5. Verify that the View tables were successfully created and populated on the ne
w Project
Tables server.
6. Using SQL Server Query Analyzer and connecting with your login account, execu
te the
ExecLinkedViewsSP stored procedure as follows.
EXEC ExecLinkedViewsSP <ViewTablesDatabaseServerName>,
<ViewTablesDatabaseName>
For example:
EXEC ExecLinkedViewsSP PSView, ProjectServerVIEW
2. Select the Partitioned database configuration option, and then select the Cus
tom
Deployment option.
3. From the list, select View Tables.
4. In the SQL Server box, type the name of the View Tables database server.
5. In the Database box, type the name of the View Server database that you creat
ed on
that server.
Number of Projects
Publishing Time
10
30 seconds
100
601 seconds
500
3539 seconds
The following table lists the publishing times for two offloaded Project Server
Views
Notification Services.
Number of Projects
Publishing Time
10
Server 1, 25 seconds
Server 2, 25 seconds
100
Server 1, 330 seconds
Server 2, 345 seconds
500
Server 1, 1803 seconds
The following table lists the publishing times for three offloaded Project Serve
r Views
Notification Services.
Number of Projects
Publishing Time
10
Server 1, 23 seconds
Server 2, 28 seconds
Server 3, 34 seconds
100
Server 1, 242 seconds
Server 2, 240 seconds
Server 3, 250 seconds
500
Server 1, 1384 seconds
Server 2, 1425 seconds,
Server 3, 1385 seconds
With a single Project Server Views Notification Service running in the tested en
vironment,
publishing 500 projects took 3539 seconds. With two services running, publishing
500
projects took 3517 seconds total, but when the load is split across two servers,
the average
time to publish was 1758 seconds and the average savings was 1830 seconds. With
three
services running, publishing 500 projects took 4194 seconds, but when the load i
s split
across three servers, the average time to publish was 1398 seconds and the avera
ge savings
was 2141 seconds.
Note While up to 1000 servers can be configured to support a load-balanced Proje
ct Server Views
Notification Service, performance testing indicates a rate of diminishing return
on real performance
improvement.
Configuring the Computers Running the Project Server Views
Notification Service
Load-balancing the Project Server Views Notification Service involves the follow
ing steps:
Using Project Server Setup to install the components required for load balancing
the
Project Server Views Notification Service on the additional servers.
Completing a few manual steps on the new servers (including disabling the Projec
t
Server Scheduled Process Service).
Updating the registry on the front-end application server or servers so that it
is aware
of the new load-balanced configuration for the Project Server Views Notification
Service. Only the front-end application server needs to be aware of the load-bal
anced
configuration.
If you are running Analysis Services, you must also do the following on any serv
er running
the offloaded Project Server Views Notification Service:
Create the same OLAP administrator account that is used on other servers in your
deployment.
Install Decision Support Objects (DSOs).
Apply SQL Server 2000 Service Pack 3 (SP3).
Disable the Project Server Scheduled Process Service on all but one of the serve
rs
running the offloaded Project Server Views Notification Service. If you do not d
o this,
OLAP cube generation might fail and resource tables will not be updated.
Before installing Project Server 2003, determine which languages users in your o
rganization
need to use, and then determine which primary language makes the most sense for
your
deployment. For example, the Latin code page is a subset of the Japanese code pa
ge. If
your organization has users in Japan, England, and France, using Japanese as the
primary
language will enable all users to interact with Project Server 2003 in their own
languages,
with the exception of some French characters that are not supported by the Japan
ese code
page. Some combinations of languages are not possible; for example, Korean and J
apanese
cannot be on the same server because one of the code pages is not a subset of th
e other.
Data stored in the Project Server database and the interaction between Project S
erver 2003,
Microsoft SQL Server 2000, Project Web Access, and Project Professional are based
on
your choice of a primary language and the code pages that are associated with th
em. The
code pages for Project Server 2003, SQL Server 2000, and Project Professional mu
st match
in order for users of Project Professional to connect to the Project Server data
base.
Installing Project Server Multilingual User Interface Packs
After you install Project Server 2003 (which sets your primary language), determ
ine the
additional languages that your organization needs to make available to its users
. Apply these
languages to Project Server 2003 by installing the appropriate MUI Pack. The MUI
Packs
for Project Server 2003 are available from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkID=20897). Twenty-two languages are availab
le. The MUI
Pack for Microsoft Office Project Professional 2003 is available through Microso
ft
licensing programs. Some users will need to install the language upgrades for Mi
crosoft
Internet Explorer in order to take advantage of the full multilingual capabiliti
es of Project
Web Access.
If Project Server 2003 has more than one MUI Pack installed, users can choose th
e
language for their notification and reminder e-mails. This option is available i
n the
Subscribe to Notifications and Reminders page on the Project Web Access home pag
e.
Note The data in an e-mail message remains in the language in which the message
was originally
created.
The Project Server MUI Pack Setup program installs features that allow you to ch
ange the
language of the following:
The user interface
Help
User interface fonts (Asian languages and Hebrew)
Project Web Access detects a user's Internet Explorer language setting. If the l
anguage
pack for that language is installed on Project Server 2003, Project Web Access d
isplays the
user interface in that language. If you install a localized version of Project S
erver 2003, the
default language setting for Project Web Access is the same language. All locali
zed versions
of Project Server 2003 contain an English version as well, so that you can chang
e the
language settings to English. For example, if you want to view Project Web Acces
s in
Korean, and the Korean MUI Pack is installed on Project Server 2003, you can vie
w the
Project Web Access user interface in Korean. If Korean is unavailable, Project W
eb Access
displays the user interface in the Project Server installation language or in En
glish.
Note If you want to input Asian language or Hebrew text into most areas of Proje
ct Web Access,
including status reports, the timesheet, notifications and reminders, and so on,
you can use the
Input Method Editor.
MUI Packs for Project Server 2003 can only be installed on a computer on which P
roject
Server 2003 is already installed. MUI Packs are available for the following lang
uages:
Brazilian Portuguese (PSMUIPTB.exe)
Chinese (Simplified) (PSMUICHS.exe)
Chinese (Traditional) (PSMUITCH.exe)
Czech (PSMUICSY.exe)
Danish (PSMUIDAN.exe)
Dutch (PSMUINLD.exe)
Finnish (PSMUIFIN.exe)
French (PSMUIFRA.exe)
German (PSMUIGER.exe)
Greek (PSMUIELL.exe)
Hebrew (PSMUIHEB.exe)
Hungarian (PSMUIHUN.exe)
Italian (PSMUIITA.exe)
Japanese (PSMUIJPN.exe)
Korean (PSMUIKOR.exe)
Norwegian (PSMUINOR.exe)
Polish (PSMUIPLK.exe)
Portuguese (PSMUIPTG.exe)
Russian (PSMUIRUS.exe)
Spanish (PSMUISPA.exe)
Swedish (PSMUISWE.exe)
Turkish (PSMUITRK.exe)
5. Click OK.
Send us your feedback. Please let us know what you think about the quality of th
is
content. If this text does not meet your needs, let us know how we can improve i
t. If this
text was helpful to you, let us know how it helped.
mailto:projdocs@microsoft.com?subject=Feedback: Microsoft Office Project Server
2003 Installation
Guide
B
Project Server Service Accounts
A number of service accounts are required in order for Microsoft® Office Project
Server 2003 components to access one another. This appendix includes summary
information about the required accounts, their purpose, their characteristics, a
nd how and
when they are used.
Analysis Services Account
The Analysis Services account is a Microsoft Windows® account that enables the
computer running Project Server 2003 to access Microsoft SQL Server 2000 Analysis
Services. The Analysis Services account has the following characteristics:
It is either a domain or local user account.
It must be added to the online analytical processing (OLAP) Administrators group
on
the computers on which the account is located.
It is located on the computer or computers on which SQL Server 2000 Analysis
Services or the Decision Support Objects (DSO) are located.
Note You do not need this account if you are not using Analysis Services with Pr
oject
Server 2003.
The account information for this account is used on the Enter Analysis Services
Information page during Project Server Setup. It is also used when you are creat
ing an
OLAP Administrator.
If you are using a local user account for the Analysis Services account, you mus
t create
identical accounts and passwords on the computer running Analysis Services, the
computer
running the Project Server Front-End service, and the computer running the Proje
ct Server
View Processing service. If Analysis Services is not installed on the same compu
ter on
which Project Server 2003 is installed, you must also add the Analysis Services
account to
the OLAP Administrators user group on the computers on which the Project Server
Front-
End service and the View Processing service are located.
Note The Decision Support Objects (DSO) must be installed on the computers on wh
ich the Project
Server Front-End service and the View Processing service are running. If they ar
e not installed on
these computers, the OLAP Administrators group will not appear in Computer Manag
ement.
If during Project Server Setup you selected to add the Analysis Services informa
tion later,
you must update the account by using the Project Server COM+ Settings tool
(PSCOMPlus.exe).
Windows SharePoint Services Administrator Account
The Windows SharePoint Services Administrator account enables the computer runni
ng
Project Server 2003 to access Microsoft Windows SharePoint® Services. This account
has
the following characteristics:
It is either a Windows domain or local user account.
It must be assigned to a user who is part of the Administrators group on the com
puter
that is running Windows SharePoint Services.
It is located on the computer or computers on which Windows SharePoint Services
and the Project Server Front-End service are installed.
Note You do not need this account if you are not using Windows SharePoint Servic
es with Project
Server 2003.
The account information for this account is used on the Enter Account Informatio
n for
Windows SharePoint Services page during Project Server Setup.
If you are using a local user account for the Windows SharePoint Services accoun
t, you
must create identical accounts with identical passwords on each computer running
Windows SharePoint Services as well as each computer running the Project Server
Front-
End service. On computers running the Project Server Front-End service, run
PSCOMPlus.exe to enter the user name and password of the Windows SharePoint Serv
ices
Administrator.
If during Project Server Setup you selected to add the Windows SharePoint Servic
es
information later, you will have to update the account by using PSCOMPlus.exe.
Project Server Database Account
The Project Server Database account is a SQL Server account that is used to crea
te the
Project Server database. This account has the following characteristics:
It can use either Windows or SQL Server authentication.
It must belong to the Security Administrators and Database Creators roles.
It is located on the computer or computers running SQL Server 2000 on which the
Project Server database is located.
The account information for this account is used on the Enter Database Server
Information page during Project Server Setup. If you select SQL Server authentic
ation on
this page, you can use the SQL Server system administrator (sa) account.
Windows SharePoint Services Database Account
The Windows SharePoint Services Database account is used to create the Windows
SharePoint Services database in SQL Server. This account is required only for th
e
installation of Windows SharePoint Services. The Windows SharePoint Services Dat
abase
account has the following characteristics:
It can use either Windows or SQL Server authentication. (Windows authentication
is
recommended.)
It must belong to the Security Administrators and Database Creators role.
It is located on the computer running SQL Server on which the Windows SharePoint
Services database is located.
The account information for this account is used on the Set Configuration Databa
se
Server page during Windows SharePoint Services Setup.
Project Server User Database Account
The Project Server User Database account is used by the computer running Project
Server 2003 to access the Project Server database. This account is created autom
atically
when a new Project Server database is created during Project Server 2003 Setup,
but it can
also be created manually. When it is created automatically, the default logon na
me is
MSProjectServerUser. If this account already exists, the default logon name is
MSProjectServerUserXXXX (where XXXX is a random four-digit number).
You must enter a password for this account on the Create Database Account
Information page during Project Server Setup. If you are connecting to an existi
ng
database, you also have the option to enter the logon name on this page.
If you create the account manually, you must configure the account in the SQL Se
rver 2000
Enterprises Manager when you create the Project Server database.
The Project Server User Database account is located on the computer running SQL
Server
on which the Project Server database is located.
Project User Database Account
The Project User Database account is used by Microsoft Office Project Profession
al 2003
to access the Project Server database. This account is created automatically whe
n a new
Project Server database is created during Project Server Setup, but it can also
be created
manually. When it is created automatically, the default logon name is MSProjectU
ser. If
this account already exists, the default logon name is MSProjectUserXXXX (where
XXXX is a random four-digit number).
You must enter a password for this account on the Create Database Account
Information page during Project Server Setup. If you are connecting to an existi
ng
database, you also have the option to enter the logon name on this page.
If you create the account manually, you must configure the account in the SQL Se
rver 2000
Enterprises Manager when you create the Project Server database.
This account is located on the computer running SQL Server on which the Project
Server
database is located.
View Administrator Account
The View Administrator Account is used by the Project Server Front-End service t
o access
the View Staging shared folder if the View Processing service is located on anot
her
computer. This account has the following characteristics:
It is either a Windows domain or local user account.
It must have read and change permissions to the View Staging shared folder.
It is located on the computer running the View Processing service and the comput
er
running the Project Server Front-End service.
The account information for this account is used on the Enter the Views Processi
ng
Server Information page (for both the Project Server Front-End service and the V
iew
Processing service installations) during Project Server Setup. Project Server Se
tup assigns
the account the required permissions for the folder.
C
Project Server Installation Tools
This appendix describes tools that are available to the Microsoft® Office Project
Server 2003 administrator. These tools can be used during initial deployment and
for day-
to-day operations following deployment.
Connection Information Tool
Microsoft Office Project Server 2003 stores information in the registry about th
e location
of the Project Server database and which accounts are associated with Project Se
rver roles.
If you change your configuration by moving all or part of the database to a new
computer,
you must update the information in the registry. Also, if you change which users
are
members of the MSProjectRole or MSProjectServerRole roles, you must update this
information in the registry. Use the Connection Information tool (ConnInfo.exe)
to update
this information.
.. To use ConnInfo.exe for a single database
1. Start ConnInfo.exe. You can find this tool in the BIN\1033 folder of your Pro
ject
Server installation, or you can download it from the Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=20878).
2. Select the Single database configuration option.
3. In the SQL Server box, type the name of the instance of Microsoft SQL Server
2000 on which the Project Server database is located.
4. In the Database box, type the name of the Project Server database.
5. Under MSProjectServerRole Member:, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server datab
ase.
6. Under MSProjectRole Member:, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database.
7. Click Save, and then click Exit.
4. Select one of the following options for the database that you want to configu
re:
Project Tables To configure the database that contains the Project tables and
Security views.
View Tables To configure the database that contains the View tables.
Web Tables To configure the database that contains the Microsoft Office
Project Web Access tables and Cube tables.
Note If you select the Standard 2-Way Deployment option, the Web Tables option i
s not
available.
5. In the SQL Server box, type the name or IP address of the instance of SQL Ser
ver on
which the Project Server database is located.
6. In the Database box, type the name of the Project Server database.
7. Under MSProjectServerRole Member, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server datab
ase.
8. Under MSProjectRole Member, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database.
9. Repeat steps 4 through 8 for each database that you want to configure.
10. Click Save, and then click Exit.
EditSite Tool
You can use the EditSite tool (EditSite.exe) to create a Project Server hosted d
eployment
and to edit the properties for existing hosted sites. A hosted deployment is a l
arge
installation of Project Server 2003 that hosts Project Server site collections f
or departments
or divisions within the organization. The host can also be an application servic
e provider
that hosts Project Server site collections for other companies, similar to the w
ay that an
Internet service provider hosts Web sites.
In a Project Server hosted deployment, a single installation of Project Server 2
003 hosts
multiple instances of Project Web Access, each with its own SQL Server database.
Typically, in a hosted deployment, multiple Project Server sites share a single
Microsoft
Windows® SharePoint® Services content database.
When you install Project Server 2003, only one site is available (called Project
Server),
accessible by means of the URL http://computername/projectserver. When you use
EditSite.exe to add a Project Server site, a new URL (http://computername/sitena
me) is
available from which you can access a new instance of Project Web Access.
.. To install the Edit Site tool
1. Download and run the file EditSite.exe from the Microsoft Download Center:
http://go.microsoft.com/fwlink/?LinkId=20891.
2. Double-click the Setup file to complete the installation.
5. Select one of the following options for the database that you want to configu
re:
Project Tables To configure the database that contains the Project tables and
Security views.
View Tables To configure the database that contains the View tables.
Web Tables To configure the database that contains the Microsoft Office
Project Web Access tables and Cube tables.
Note If you select the 2 Way Deployment option, the Web Tables option is not ava
ilable.
6. In the SQL Server box, type the name of the instance of SQL Server on which t
he
Project Server database for this site is located.
7. In the Database box, type the name of the Project Server database for this si
te.
8. Under MSProjectServer Role Member, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server datab
ase
for this site.
9. Under MSProject Role Member, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database for
this
site.
10. Repeat steps 5 through 7 for each database that you want to configure.
11. Click Save.
.. To delete a site
1. In the Virtual Directory list, select the site that you want to delete.
2. Click Delete.
EditSite.exe deletes the virtual directory and the registry information associat
ed with the
site. EditSite.exe does not delete the ODBC connection registry keys because tha
t ODBC
connection might be used for other purposes.
.. To add a new site
1. Create a database for the new site. For more information about creating a Pro
ject
Server database, see Chapter 6, Deploy the Database in the Microsoft Office Proj
ect
Server 2003 Installation Guide.
2. Run EditSite.exe.
3. Click Add. The Microsoft Office Project Server 2003 Site Editor Add Site page
is
displayed.
4. Enter the site, database, and Windows SharePoint Services information as desc
ribed in
the following procedures.
3. Select one of the following options for the database that you want to configu
re:
Project Tables To configure the database that contains the Project tables and
Security views.
View Tables To configure the database that contains the View tables.
Web Tables To configure the database that contains the Microsoft Office
Project Web Access tables and Cube tables.
Note If you select the 2 Way Deployment option, the Web Tables option is not ava
ilable.
4. In the SQL Server box, type the name of the instance of SQL Server on which t
he
Project Server database for this site is located.
5. In the Database box, type the name of the Project Server database for this si
te.
6. Under MSProjectServer Role Member, type the user name and password for the
account that is a member of the MSProjectServer role in the Project Server datab
ase
for this site.
7. Under MSProject Role Member, type the user name and password for the account
that is a member of the MSProjectServer role in the Project Server database for
this
site.
8. Repeat steps 3 through 5 for each database that you want to configure.
9. Click the Windows SharePoint Information tab to specify Windows SharePoint
Services information for the new site.
Parameter
Description
-?
Display syntax information.
-S
SQL Server. Specify the instance of SQL Server on which the main Project
Server database is located.
-D
Database. Specify the main Project Server database to be used with the new
site.
-U
MSProjectServer Role Member. Specify the user in the database that is a
member of the MSProjectServer role.
-P
MSProjectServer Role Member password. Specify the password for the user
that is a member of the MSProjectServer role.
-E
MSProject Role Member. Specify the user in the database that is a member
of the MSProject role.
-A
MSProject Role Member password. Specify the password for the user that is
a member of the MSProject role.
-V
Name of the Project Server site. Used when adding and deleting a site.
-W
The Web root number of the Web site on which you want to install Project
Server 2003. The Web root number is found in the Internet Information
Services (IIS) metabase. You can use a tool such as the Meta-Data Edit Tool
from the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=21727) to
determine the Web root number of the site that you want to use.
-L
Project Server path. The path in which Project Server 2003 is installed.
-G
Session Manager. Specify the name of the server running the Project Server
Session Manager service.
-H
Application Pool. Microsoft Windows Server 2003 only. Specify the
application pool to use with the new site.
-I
View Tables server. Specify the instance of SQL Server on which the View
Tables are located. Only required when the View Tables are located on a
different server from the main database.
-T
View Tables database. Specify the name of the database that contains the
View Tables. Only required when the View Tables are located on a different
server from the main database.
-O
Windows SharePoint Services AdminPort. Specify the URL for the Windows
SharePoint Services Central Administration page.
-Y
Windows SharePoint Services site URL. Specify the URL where you want to
create Windows SharePoint Services sites for projects.
-C
Windows SharePoint Services Admin NT Account. Specify the domain
account for the Windows SharePoint Services site administrator.
-N
Windows SharePoint Services Admin Name. The name of the Windows
SharePoint Services site administrator.
-M
Windows SharePoint Services Admin Mail. The e-mail address for the
Windows SharePoint Services site administrator.
-Q
Quiet mode. Use Q to suppress alerts.
-K
Delete site. Deletes the site specified by the -V option.
To add a site, run EditSite.exe by using the following syntax:
EditSite [-S database server] [-D database] [-U Project Server user]
[-P Project Server password] [-E Project user] [-A Project password
[-V site name] [-W Web site number] [-L Project Server path]
-G Session Manager -H Application Pool
-I View Tables server -T View Tables database -B Web Tables server -
F Web Tables database -O Windows SharePoint Services Admin URL -Y
Windows SharePoint Services Site URL
-C Windows SharePoint Services Admin NT Account -N Windows
SharePoint Services Admin Name -M Windows SharePoint Services Admin
Mail
3. If you are not updating the Analysis Services Access Identity, clear the Proc
ess this
identity update check box in the Analysis Services (OLAP) Access Identity
section.
4. Click Create/Update Com+ Apps.
Parameter
Description
*-w
The managed path (URL) for Microsoft Windows SharePoint Services
project sites. Optional only if bo (backup only) is specified.
*-ownerlogin
A Windows account with permission to create a top-level Web site.
*-owneremail
The e-mail address of the user specified in ownerlogin.
-i
Indicates the Project ID numbers (in Project Server 2003) whose
SharePoint Team Services subwebs will be migrated to Windows
SharePoint Services. It can be a single project ID, a range of project IDs, or
a series of project IDs that is out of order. If this parameter is not used, all
subwebs will be migrated. Use -1 to migrate the Public Document library.
*-f
The path of the backup file and the working subfolder. Required for
PSMigrat.exe to run.
*-dbserver
The Project Server database server.
*-dbname
The name of the Project Server database.
-dblogin
Required if SQL Server authentication is used.
-dbpassword
Required if SQL Server authentication is used.
-c
Connection string. Can be used in place of the db* parameters.
-l
The path to the log file. Optional; defaults to %temp% if not specified.
-s
Specifies that PSMigrat.exe is to run in silent mode. Optional.
-ro
Restore only from the expanded format (with Manifest.xml and other files
listed in a directory) from the work directory (-f). Optional.
-bo
Back up the SharePoint Team Services subwebs into an .fwp file. This also
keeps the expanded file list out of the .fwp file.
*-p
Accepts a prefix for the site name. For example, for a site with a target
name of ProjectServer_101, the prefix is "ProjectServer".
-u
User name for computers running Microsoft Windows Server 2003 with
Internet Explorer Enhanced Security installed.
-pw
Password for computers running Windows Server 2003 with Microsoft
Internet Explorer Enhanced Security installed.
-psintraneturl
If specified, this URL will be set as a site property on each Project Web site
upon restoration.
-psextraneturl
If specified, this URL will be set as a site property on each Project Web site
upon restoration.
When you use WSSMigr.exe to restore subsites, the tool runs STSAdm.exe for each
subsite
in the backup by using the following syntax:
Stsadm.exe -o restore -url [subsiteURL] -file [-f parameter +
filename] overwrite
Note You must be a Windows SharePoint Services administrator to run WSSMigr.exe.
-l c:\temp\psmlog.txt
W
The managed path (the URL) of Windows SharePoint Services wheresubsites will be
restored. Optional when backing up; required when
restoring. You must use the NetBIOS name for the server name. When uswith the -b
o parameter, this value will override the Windows SharePoint
Services m
Required. The directory path where the backup files are s
Required. The name of the server running SQL Serve
Required. The n
Required if using SQL Server authentication to access the Project Server
database. T
Required if
database.
database connection parameters.
Optional. The range of Project IDs whose Windows SharePoint Services
subsites will be backed up. If this parameter is not specified, all Windows
SharePoint Services subsites created by Project Server 2003 in that sicollection
will be backed up.
e
Specify eithProject IDs.
Examples:
-i 101-111 (Backs up the subsites for project 101-111)
-i 103,109,111 (Backs up the subsites for project 103, 109, 111)
-i 103,109-111 (Backs up the subsites for pro
ject 1-i 103 (Backs up the subsite for project 103)
-i -1 (Only backs up the public documents sub
(Note: You cannot include spaces in the list.)
Optional. This switch denotes a prefix to append to each Project Web site.
For example, if '-p Org1' is specified, site ProjectServe
become Org1_MS_ProjectServer_PublicDocuments.
Optional. The path and filename for the log file. If you do not specify a file
name, a file called WSSMigr.log will be created. If you do not specify a path,
the log file will be created in the %temp% directory for your use
-s
Optional. Runs in silent mode with no output of the progress.
Required when restoring. Restores all Wi
subsites from the working directory (-f).
subsites into the working directory (-f) as .bak files.
Optional. Administrator user name for Windows SharePoint Services.
Required if authentication credentials need to be passed. (W
Server 2003 Enhanced Security configurations.)
Optional. Administrator password. Re
Parameter
Description
Parameter Description
configurations.)
TTP Proxy Configuration Tool
h
Wen you run Project Server Setup, proxy settings are automatically configured fo
r your
Project Server installation. If you need to change or update the proxy server co
nfiguration,
can use the WinHTTP pro
xy configuration tool (Proxycfg.exe), which is installed on
the server when you run Project Server Setup.
To run Proxycfg.exe
On the computer on which Projeccmd, and then click OK.
then run Proxycfg.exe by using the parameters listed in t3. Restart Internet Inf
ormation Services (IIS).
Note New or updated information for Proxycfg.exe will not take effect un
Informa
l Options
Description
This com
prox
This command specifies that all HTTP andHTTPS servers should be accessed directl
y.
Use this command if there is no proxy
server.
This command specifies one or more proxy
servers
should be accessed directly. If a proxy serveis not specified for a given protoc
ol and thserver is not in the bypass list, the -p option
specifies that the server cannot be accessedat all.
Description
This command specifies on
should be accessed directly. If a proxy server
is not specified for the given protocol, the -d
option specifies that the server shouldaccessed directly instead.
When you are finished configuring the Sample database, see the files Samprm.htm
and
Sampepm.htms in the \Sample Data\1033 folder of your Project Server installation
for
more information about using the Sample database.
User Accounts
The Sample Data Configuration Wizard creates local computer user accounts on you
r
server for each of the roles listed in the following table. If you prefer, you c
an specify user
accounts for these roles.
Name
Type
Demo Role
Jo Brown
User
Executive, Portfolio Management Scenario
Scott Bishop
User
Resource Manager, Portfolio Management Scenario
Steve Masters
User
Project Manager, Portfolio Management Scenario
Brad Sutton
Power User
Team Member, Portfolio Management Scenario
Eva Corets
User
Project and Resource Manager, Resource Management
Scenario
Wendy Wheeler
User
Resource Manager, Resource Management Scenario
Rob Young
Power User
Team Member, Resource Management Scenario
Each user listed in the table has a Windows password of pass@word1 and uses Wind
ows
authentication to access the computer running Project Server. All other users in
the sample
data have a blank password.
Note The administrator account is not created by the Sample Data Configuration W
izard.
Sample Data Installation and Configuration
To install and configure the sample data, run the Sample Data Configuration Wiza
rd.
.. To run the Sample Data Configuration Wizard
1. On the Start menu, point to Programs, click Microsoft Office Project Server 2
003,
and then click Restore and Configure Sample Data.
The Sample Data Configuration Wizard starts.
5. On the Microsoft Office Project 2003 Database page, the path and file name fo
r the
Project Server Sample database file, and the new database name, are included as
default
values. Edit these values if you want to restore a different backup or use a dif
ferent
database name, and then click Next.
6. On the Windows SharePoint Services Database page, the path and file name for
the
Windows SharePoint Services Sample database file, and the new database name, are
included as default values. Edit these values if you want to restore a different
backup
or use a different database name, and then click Next.
7. Specify the URL that you will use to access the sample data, and then click N
ext.
8. Either choose to allow the wizard to create user accounts on your computer, o
r specify
existing user accounts to use for each role (remember the option that you select
here;
you will need it later). It is recommended that you allow the wizard to create u
ser
accounts this will help you to follow demo scripts provided.
Note If you choose not to have the wizard create user accounts for you, you will
need to
manually add the users Brad Sutton and Rob Young to the Power Users group when y
ou
create the user accounts.
9. Click Install.
10. Click Finish.
Note You might want to set up multiple copies of the sample data on the server s
o that different
people can use their own copy of the sample data. To do this, run this wizard mu
ltiple times. Each
time that you run the wizard, specify a different database name and URL. If you
need to install
multiple copies of the Windows SharePoint Services sample data, see the topic In
stalling Multiple
Copies of the Windows SharePoint Services Data in Appendix D, Configuring the Sa
mple Database
of the Microsoft Office Project Server 2003 Installation Guide.
Configuring Windows SharePoint Services for Project
Server 2003
Because you are restoring a database from a different computer, you must reconfi
gure
Windows SharePoint Services and Project Web Access. This involves completing the
following steps:
3. In the left pane, expand the tree until you view the Web Sites folder.
4. Click the Web Sites folder and on the Action menu, click New, and then click
Web
Site.
5. In the Web Site Creation Wizard, click Next.
6. On the Web Site Description page, type a description (for example, SharePoint
Sample Database) and then click Next.
7. On the IP Address and Port Settings page, change the TCP port to a value such
as
5555 and then click Next. This number must be unique. Do not use 80 or any other
port you have previously defined for a Web site.
8. On the Web Site Home Directory page, click the Browse button. On the drive on
which Windows is installed, find and select the Inetpub folder.
9. Click Make New Folder. Type Sample and then click OK.
10. Click Next.
11. On the Web Site Access Permissions page, click Next.
12. Click Finish.
13. Close IIS Manager.
If the NT Authority\Network Service login does exist, you need to verify that
this account exists as a db_owner on the MPSWSSSampleDatabase database.
Double-click NT Authority\Network Service, and then select the Database
Access tab. Select the Permit box next to the Windows SharePoint Services
database; it should be the same database restored previously (default name
MPSWSSSampleDatabase). Do not change the settings for any other database.
Under Database roles, enable db_owner and then click OK.
Note This step assumes that Windows SharePoint Services sample content database
application pool is running under the identity of NT Authority\Network Service.
.. To add Project Serve 2003 to the Windows SharePoint Services exclusion list
1. In Administrative Tools in Control Panel, open the Windows SharePoint Service
s
Central Administration page.
2. Under Virtual Server Configuration, click Configure virtual server settings.
3. On the Virtual Server List page, click the Default Web Site link that points
to the
server running Project Server 2003.
4. On the Virtual Server Settings page, under Virtual Server Management, click
Define Managed Paths.
5. On the Define Managed Paths page, under Add a new path, type the name of the
Project Server Sample database path (for example, sample ) in the Path text box.
6. Under Type, select Excluded Path.
Note If you click Check URL, the page will not load. This is expected behavior.
7. Click OK. The name of the Project Server Sample database virtual directory ap
pears in
the list of excluded servers under Excluded Paths.
IF [%1]==[r] (
REM Restore the si
Se
)
Follow the procedure To add Project Server 2003 to the Windows SharePoint
Services exclusion list in the topic Configuring Windows SharePoint Services for
Project Server 2003 in Appendix D, Con
Building the OLAP Cube
Project Web Access uses an online analytical processing (OLAP) cube for modeling
and
analyzing data. If you make major changes to the database, such as renaming a pr
oject or
significantly modifying assignments or views, you will need to rebuild the OLAP
cube to
ensure that Portfolio Analyzer views are updated accordingly.
Note If you install multiple instances of the Project Server Sample database and
do not specify
unique names for the OLAP cube, each instance of the Project Server Sample datab
ase will point to
the same OLAP cube. If you specify a new name for the OLAP cube, you will also n
eed to change the
Portfolio Analyzer view configuration to point to the new cube.
Under OLAP cube name and description, specify the name of the Analysis
Services server, the OLAP cube name, and description.
Under Date range for resource availability, specify the range that you want to
use for resource updates.
6. Under Update frequency, select Update only when specified, and then click
Update Now. The OLAP cube will be created. This might take several minutes. You
can check the status of the OLAP cube by refreshing the page and then referring
to the
Current Cube Status section. Remember the name of the OLAP cube that you are
generating as you will need to refer to it later.
Note If you receive an error message stating that the connection to the reposito
ry cannot be
established, you might need to set additional permissions for the OLAP repositor
y.
.. To set additional permissions for the OLAP cube
1. On the Start menu, select My Computer.
2. Browse to and open the \Program Files\Microsoft Analysis Services folder.
3. Right-click the Bin directory and select Properties to open the Bin Propertie
s dialog
box.
4. Select the Security tab, and then click the Add button to open the Select Use
rs,
Computers, or Groups dialog box.
5. In the Enter the object names to select text box, type servername\OLAP
Administrators, and then click OK.
6. In the Bin Properties dialog box, under Groups or user names, select the OLAP
Administrators group.
7. Under Permissions for, set Full Control to Allow.
8. Click OK.
.. To remove user roles for Project Server and Windows SharePoint Services
1. Log on to the computer running Project Server 2003 as an administrator.
2. On the Start menu, point to All Programs, Microsoft SQL Server, and then clic
k
Enterprise Manager.
3. Under Console Root, expand the tree until the Databases folder appears.
4. Expand the Databases folder, and then expand the folder for the database that
you
intend to back up (for example, MPSSampleDatabase).
5. Select the Users folder.
6. Right-click MSProjectSampleDBUser and select Delete.
7. Right-click MSProjectServerSampleDBUser and select Delete.
Note You can also type sampcfg.exe /b at the command line to back up your data.
.. To restore the Sample database
1. Log on to the computer running Project Server 2003 as an administrator.
2. On the Start menu, point to All Programs, Microsoft Office Project Server 200
3,
and then select Configure Sample Data to open the Sample Data Wizard. Click
Next.
3. If you agree to the terms of the End-User License Agreement, select the I acc
ept the
terms of the License Agreement option, and then click Next.
4. On the Data Type page, choose Install Microsoft Office Project Server data if
you
are not restoring Windows SharePoint Services data, or choose Install Microsoft
Office Project Server 2003 and Windows SharePoint Services data if you are
restoring Windows SharePoint Services. Click Next.
5. On the Microsoft Office Project Server 2003 Database page, under Microsoft
Office Project Server database backup file to restore, specify the path name for
the
database. Under Restore as, specify the name of the backup file. Click Next.
6. If you are restoring the Windows SharePoint Services database, on the Windows
SharePoint Services Database page, edit the path and file name if necessary, and
then click Next.
7. On the URL page, specify the URL for the server running Windows SharePoint
Services, for example, http:// servername/sample).
8. On the User Accounts page, specify the user accounts that you want to use for
the
restored database. Select Create Windows user accounts for each role on this
computer for me if you want the user accounts to be created automatically, or se
lect
Use existing Windows user accounts for the roles if you want to preserve existin
g
user accounts. You will need to provide the credentials for these user accounts
during
the restore process if you choose this option.
9. Click Install.
10. After the Sample Data Wizard restores the backup file, click Finish.
Note You can also type sampcfg.exe /r at the command line to restore and configu
re the data.
E
Uninstalling Project Server 2003
You can uninstall Microsoft® Office Project Server 2003 by using Add or Remove
Programs in Control Panel. When you uninstall Project Server 2003, the following
components are unaffected:
Database files in Microsoft SQL Server 2000 or the Microsoft Desktop Engine
(MSDE).
System files installed by Project Server Setup (such as the files for Microsoft
XML).
Additional products or components, such as Microsoft Windows® SharePoint®
Services.
Project Server templates and sites that Project Server 2003 created by using tho
se
templates.
On the other hand, the registry keys that were created for Project Server 2003 a
re removed
when you uninstall the software.
You can use the Windows SharePoint Services Configuration Wizard to uninstall th
e
Project Server templates and restore the Windows SharePoint Services templates t
o their
original state (existing subsites are not affected). To uninstall Windows ShareP
oint Services
completely, use the Windows SharePoint Services Configuration Wizard to uninstal
l the
Project Server templates, unextend the virtual server, and delete the content da
tabase.
Then, uninstall Windows SharePoint Services by using Add or Remove Programs in
Control Panel.
Uninstalling Project Server 2003 does not remove the database. You can delete th
e
database after uninstalling Project Server 2003, but this is not recommended, as
this is the
record stored on the server of all projects that were planned.
F
Installing Project Server 2003 From
the Command Line
When you run Project Server Setup for Microsoft® Office Project Server 2003, you c
an
use command-line options to enter the parameters that Project Server Setup uses
during
installation, instead of entering them on the Project Server Setup pages or ente
ring them
later by using Microsoft Office Project Web Access 2003.
Note The command-line functionality described in this appendix only works on ver
sions of Project
Server 2003 that are sold by means of a volume licensing agreement.
This appendix provides the command-line options that are available to you for ea
ch of the
steps within Project Server Setup.
To see a visual representation of the relationships between the various Project
Server Setup
steps, see the Project Server Setup Flow Diagram, available on the Microsoft Web
site
(http://go.microsoft.com/fwlink/?LinkId=21681).
Important It is strongly recommended that you install Project Server 2003 by usi
ng Project Server
Setup, as described in Chapter 7, Install Project Server 2003, in the Microsoft
Office Project
Server 2003 Installation Guide, rather than by using the command line. It is eas
ier to install Project
Server 2003 by using Project Server Setup.
Command-Line Parameters for Installing Project Server 2003
To install Project Server 2003 from the command line, run the setupsvr.exe progr
am
(which is located in the prjsvr folder on the Project Server 2003 CD) from the c
ommand
line, followed by the required parameters and values. Use the following syntax t
o install
Project Server 2003 from the command line:
setupsvr.exe AddLocal=value1, value2, value3 parameter=value
parameter=value parameter=value parameter=value
Important When you install Project Server 2003 from the command line, no validat
ion of
parameters or values is performed. If parameters or values are used incorrectly,
the installation will
roll back and Project Server Setup will be unable to provide error information.
The AddLocal parameter is used to specify which features of Project Server 2003
you are
installing. The following sections describe the values that you need to include
with the
AddLocal parameter.
Important Specify the AddLocal parameter only once on the command line. Include
all the
AddLocal parameters for the features that you want to install in one comma delim
ited string after
the AddLocal parameter.
Select a Location for Installation
In Project Server Setup, on the Select a location for installation page, you spe
cify the
location where Project Server 2003 will be installed on your computer. To do thi
s, use the
following parameter at the command prompt:
Parameter
Description
PRJSERVERDIR=path
Specify the Project Server installation
directory. For example, C:\Program
Files\Microsoft Office Project Server 2003
Parameter
Description
AddLocal=PrjSvrFrontEnd
Add the value PrjSvrFrontEnd to your
AddLocal parameter string if you want to
install the Project Server Front-End service.
AddLocal=PrjSvrViews
Add the value PrjSvrViews to your AddLocal
parameter string if you want to install the
Project Server View Processing Service.
AddLocal=PrjSvrSessionMgr
Add the value PrjSvrSessionMgr to your
AddLocal parameter string if you want to
install the Project Server Session Manager
service.
AddLocal=PrjSvrSampleDB
Add the value PrjSvrSampleDB to your
AddLocal parameter string if you want to
install the Project Server Sample database.
You must install all services on the same
computer if you are installing the Sample
database.
Parameter
Description
SMSERVER=servername
Specify the NetBIOS name of the computer
on which you are installing the Session
Manager Service.
Parameter
Description
SMSERVER=server name
Specify the NetBIOS name of the computer
where the Session Manager is installed.
Parameter
Description
VWPATH=path
Specify the path to the qualified path to the
View Staging share in the format:
\\server\share
VWSVCLOGONNAME=domain\user
Specify a domain user account with read
and change permissions to the View Staging
share. Use the format: domain\user.
VWSVCPASSWORD=password
Specify the password for the domain user
account.
Enter Database Server Information
In Project Server Setup, on the Enter database server information page, you can
specify
database server and connection information. To do this, use the following parame
ters at
the command prompt:
Parameter
Description
AddLocal=PrjSvrCreateDBFeature
If you are creating a new database, add the
value PrjSvrCreateDBFeature to your
AddLocal string. If you are connecting to an
existing database, do not include this value.
SERVERNAME=server\instance
Specify the instance of SQL Server where
you will set up the Project Server database.
SQLDBNAME=database name
Specify the name of the Project Server
database.
SAAUTHTYPE=[WIN | SQL]
Specify the type of authentication to use
when connecting to the computer running
SQL Server. Use a value of WIN for Windows
authentication or SQL for SQL Server
authentication.
DBADMIN=ServerSA
If you are using SQL Server authentication
(SAAUTHTYPE=SQL), you must include the
DBADMIN=ServerSA parameter.
SANAME=login
If you are using SQL Server authentication,
use the SANAME parameter to specify the
SQL Server login that you want to use.
SAPASSWORD=password
If you are using SQL Server authentication,
use the SAPASSWORD parameter to specify
the SQL Server password that you want to
use.
Enter Connection Information for Views Tables
In Project Server Setup, on the Enter connection information for Views tables pa
ge,
you can specify server and connection information for the Project Server Views t
ables. To
do this, use the following parameters at the command prompt:
Parameter
Description
AddLocal=PrjSvrCreateDBFeature2
If you are creating a new database and
offloading the View tables to a different
server, add the value
PrjSvrCreateDBFeature2 to your AddLocal
string.
AddLocal=PrjSvrSplitDBFeature
If you are offloading the View tables to a
different server, add the value
PrjSvrSplitDBFeature to your AddLocal
string.
SERVERNAME2=SQL Server instance
Specify the instance of SQL Server where
you will set up the Project Server View
Tables database. Use the same value that
you specified for SERVERNAME if you are
not offloading the View tables.
SQLDBNAME2=database
Specify the name of the Project Server
database. Use the same value that you
specified for SQLDBNAME if you are not
offloading the View tables.
DB2ADMIN=[ServerSA | Server2SA]
Required. Use ServerSA if you are not
offloading the View tables; otherwise, use
Server2SA.
SANAME2=username
If you are using SQL Server authentication,
use the SANAME2 parameter to specify the
SQL Server login that you want to use. If you
are not offloading the View tables, use the
same value that you specified for SANAME.
SAPASSWORD2=password
If you are using SQL Server authentication,
use the SAPASSWORD parameter to specify
the SQL Server password that you want to
use. If you are not offloading the View
tables, use the same value that you
specified for SAPASSWORD.
Enter Database Account Information
In Project Server Setup, on the Enter database account information page, you can
specify the account information to be used by Project Server 2003 and Project Pr
ofessional
to access the database. To do this, use the following parameters at the command
prompt:
Parameter
Description
PSNAME=username
Specify the name of the SQL Server login
that is a member of the
MSProjectServerRole role (normally
MSProjectServerUser).
PSPASSWORD=password
Specify the password for the SQL Server
login that is a member of the
MSProjectServerRole role.
PRJNAME=use name
Specify the name of the SQL Server login
that is a member of the MSProjectRole role
(normally MSProjectUser).
PRJPASSWORD=password
Specify the password for the SQL Server
login that is a member of the MSProjectRole
role.
Parameter
Description
AddLocal=PrjSvrDBInfoAS
If you want to specify Analysis Services
connection information, add the value
PrjSvrDBInfoAS to your AddLocal string.
ASSERVERNAME=server
Specify the NetBIOS name of the server
running Analysis Services.
ASLOGINNAME=username
Specify the user account that is a member
of the OLAP Administrators group on the
server running Analysis Services. Use the
format: domain\user
ASPASSWORD=password
Specify the password for the user account.
Parameter
Description
WEBVROOT=web root number
The Web root number of the Web site where
you want to install Project Server. The Web
root number is found in the IIS metabase.
You can use a tool such as the Meta-Data
Edit Tool from the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=21727)
to determine the Web root number of the
site that you want to use.
Parameter
Description
AddLocal=PrjSvrDBInfoAS
If you want to specify the intranet and
extranet addresses for Project Server 2003,
add the value PrjSvrDBInfoAS to your
AddLocal string.
INTRANETURL=url
Specify the intranet URL for Project
Server 2003. For example:
http://redbird/ProjectServer
EXTRANETURL=url
Optionally, specify the extranet address for
Project Server 2003. For example:
http://www.example.com/ProjectServer
Parameter
Description
AddLocal=PrjSvrDBInfoSMTP
If you want to specify SMTP mail server
settings, add the value PrjSvrDBInfoSMTP to
your AddLocal string.
SMTPSERVERNAME=server
Specify the name of the SMTP mail server.
SMTPSERVERPORT=port number
Specify the port number for the SMTP mail
server.
SMTPFROMADDRESS=e-mail address
Specify the e-mail address that you want to
appear in the From field on all notification e-
mail messages. Use the format:
someone@example.com
Parameter
Description
AddLocal=PrjSvrDBInfoSTS
If you want to connect Project Server 2003
to a server running Windows SharePoint
Services, add the value PrjSvrDBInfoSTS to
your AddLocal string.
STSADMINURLTYPE=[http:// | https://]
Specify the protocol (http:// or https://) that
is used to access the Windows SharePoint
Services Central Administration site.
STSADMINURLSERVER=server:port
Specify the server name and port of the
Windows SharePoint Services Central
Administration site. For example:
tribeca:3456
STSCREATEURLTYPE=[http:// | https://]
Specify the protocol (http:// or https://) to
use when connecting to Windows
SharePoint Services.
STSCREATEURLSERVER=path
Specify the URL at which to create Windows
SharePoint Services sites. For example:
rockaway:443/sites
STSADMINNAME=username
Specify the Windows account for the user
who will administer Windows SharePoint
Services. Use the format domain\user.
STSADMINPWD=password
Specify the password for the user account.
Parameter
Description
AddLocal=PrjSvrDBInfoSPS
If you want to connect Project Server 2003
to SharePoint Portal Server, add the value
PrjSvrDBInfoSPS to your AddLocal string.
Note: If you use this parameter, you must
also add the value PrjSvrDBInfoSTS to your
AddLocal string and specify connection
parameters for connecting to Windows
SharePoint Services.
SPSURLTYPE=[http:// | https://]
Specify the protocol (http:// or https://) to
use when connecting to SharePoint Portal
Server.
SPSURLSERVER=server/portal
Specify the Web address for accessing
SharePoint Portal Server. Use the format:
servername/portalname.
SPSPORTALNAME=portal
Specify the portal display name. Use the
format: "My Portal".
Parameter
Description
AddLocal=PrjSvrDBInfoSecurityHigh
If you want to install Project Server 2003 in
Enterprise mode, add the value
PrjSvrDBInfoSecurityHigh to your AddLocal
string.
AddLocal=PrjSvrDBInfoSecurityLow
If you want to install Project Server 2003 in
Non-enterprise mode, add the value
PrjSvrDBInfoSecurityLow to your AddLocal
string.
Enter the Administrator Password
In Project Server Setup, on the Enter the Administrator password page, you can s
pecify
the Administrator password to access Project Web Access. To do this, use the fol
lowing
parameter at the command prompt:
Note Only use this parameter if you are installing the Project Server Front-End
service.
Parameter
Description
PRJSVRADMINPWD=password
Specify the Administrator password for
Project Web Access.
G
Working with the Outlook Add-in
You can use the Microsoft® Office Project Add-in for Outlook® to update tasks from
within Microsoft Outlook 2000 and later versions of Outlook.
Installing the Outlook Add-in
You can install the Outlook Add-in from the Microsoft Office Project Web Access
2003
home page.
.. To install the Outlook Add-in
1. Log on to Project Web Access.
2. Click Tasks, and then in the left navigation pane, click View and report on y
our
tasks from your Outlook calendar.
3. Click Download Now.
Note This procedure is optional because the Other tab only appears when you open
a Project
Professional task assignment.
You can delete all of your Project Professional tasks from your calendar by usin
g the
following procedure. This procedure is optional. For example, you might want to
keep a
record of work done in the past six months.
ActiveX Control
Description
pj11xxxc.dll (where xxx is the abbreviation
for your language)
Contains strings and bitmaps used by the
grid and the text converter.
pjres11c.dll
Loads strings and bitmaps from the
resource dynamic-link libraries (DLLs).
pjtextconv11.dll
Converts raw numeric data into strings, and
vice-versa.
pjcalendar11.ocx
Provides a drop-down calendar for picking
dates.
pjgrid11.ocx
Displays task details, the timesheet, and the
Gantt Chart.
pjoutlook11.ocx
Pulls task and calendar entries from
Microsoft Outlook® and converts them into
ActiveX Data Objects (ADO) record sets that
the grid can interpret. This control warns the
user before it reads data from Outlook. It
cannot be used to access Outlook
information without the user being aware.
Note PjOutlook.ocx is marked as unsafe for
scripting.
pjprint11.dll
Provides print control.
pjquery11.ocx
Acts as a general-purpose control for all
miscellaneous client utility functions.
pjupdate11.ocx
Updates tasks and calendar entries from
Project Web Access to the Project
Server database.
pjoffline11.ocx
Caches pages for offline use when users
switch to offline mode.
Note You need to have administrative access on the computers on which you will b
e registering
these controls.
Because there are no specific installation directory requirements, you can copy
these
controls to any directory on the client computer; however, you must register the
m by using
the Regsvr32 tool (Regsvr32.exe).
Important You must register these controls in the order listed above. They are a
vailable for
download from the Microsoft Web site Project Server 2003: ActiveX Controls
(http://go.microsoft.com/fwlink/?LinkId=31562).
If you are installing the Project Web Access ActiveX controls for multiple langu
ages, you
must also include the file pj11xxxc.dll (where xxx is the abbreviation for your
language) for
each language in the same directory in which you install the other controls. You
must
register each of these files by using Regsvr32.exe.
You can deploy the files manually or by using an automated deployment tool such
as
Systems Management Server (SMS). For more information about SMS, see the Microso
ft
Web site (http://go.microsoft.com/fwlink/?LinkId=20341). You only need to instal
l the controls
once on each computer in order for all users of the computer to have access to t
hem. If
you need to uninstall these controls at any time, you can use Regsvr32.exe to un
install
them.
I
Service Packs for Project Server
Components
You must install all required service packs for Microsoft® Office Project Server 2
003
components in order for your installation to function properly. In addition, som
e service
packs are required in order for you to enable specific functionality in your env
ironment.
This appendix lists and describes the service packs that are available for Proje
ct Server 2003
and related Project Server components.
Note This appendix lists the service packs that are available at the time that t
his document was
published. Be sure to visit the product pages on the Microsoft Web site for more
information about
available service packs.
The following table lists the service packs that are currently available for Pro
ject Server
components and provides the download location for each.
Service Pack
Description
Location
Microsoft Office Project
Server 2003 Service
Pack 1 (SP1)
Contains the latest updates to
Microsoft Office Project
Server 2003. Also contains
significant security
enhancements and stability and
performance improvements.
Some of the updates that are
included in Project Server 2003
SP1 were previously released as
separate updates. Project
Server 2003 SP1 combines the
You can download this
service pack from the
Microsoft Download Center
(http://go.microsoft.com/fwlink/?LinkId=33336).
previously-released updates into
one update.
Microsoft SQL
Server 2000 Service
Pack 3
Update to SQL Server 2000. This
service pack is required for a
Project Server installation.
You can download this
service pack from the
Microsoft SQL Server page
(http://go.microsoft.com/fwlink/?linkid=19683). Select
the file sql2k3.exe.
SQL Server 2000
Analysis Services Service
Pack 3
Update to SQL Server 2000
Analysis Services. This service
pack is required for a Project
Server installation if your
organization requires the use of
online analytical processing
(OLAP) services, which are
required for the Portfolio
Analyzer feature.
You can download this
service pack from the
Microsoft SQL Server page
(http://go.microsoft.com/fwlink/?linkid=19683). Select
the file sql2kasp3.exe.
Microsoft Office XP
Service Pack 3
Contains the OWS1002.exe
update file. Install this service
pack if you are migrating
SharePoint® Team Services from
Microsoft to Microsoft Windows®
SharePoint Services.