Transcript Views on Separate Server Required for clustered PS web

Lessons Learned
Project Server 2003
Sean Pales
Bennett Adelson
Agenda




Introduction
Designing a Scalable Architecture
Common Project Server Mistakes
Q&A
Who Are We?
Bennett Adelson Enterprise Project
Management is a division of Bennett
Adelson

What does this mean?




Microsoft’s go to partner for EPM in Ohio
Core focus and competency is EPM
Proven record of successful Project Server
implementations
Highest quality developers and implementation
specialist
Who Am I?




Director of Bennett Adelson Enterprise
Project Management
Microsoft Project user for over 5 years
Frequent contributor to Microsoft
Newsgroups
Former telecom analyst for New York
based investment bank
Designing a Scalable
Architecture
Top 5 Scalability Killers
1.
2.
3.
4.
5.
Inadequate network
infrastructure
Inadequate database hardware
No Pilot
Undefined project management
practices
Unrestricted access to data
Web Server Options




Single Server
Dual Servers
Single Cluster
Dual Clusters
Single Server


Simplest setup
Scale limited to size of hardware
Sharepoint “Front-End”
IIS
Project Server
IIS, ASP Pages
Project Data Service
XML Web Service
Dual Server



Separate WSS and Project Server
Allows ‘right sizing’ of each server based on
use
Use when significant WSS usage is expected
outside of project server
Sharepoint “Front-End”
IIS
Project Server
IIS, ASP Pages
Project Data Service
XML Web Service
Single Cluster



Efficient use of less expensive hardware
Flexibility of maintenance and adding
capacity
Use when balance of WSS to PS usage
unknown
WSS
Project Server
WSS
PDS
Project Server
WSS
PDS
Project Server
PDS
Dual Cluster



Max flexibility in adding capacity as
required
Separate admin and maintenance orgs
Max capacity strategy
Project Server
WSS
PDS
Project Server
WSS
PDS
Project Server
PDS
WSS
Views Processing Options




On Web Server
Separate Server
Multiple Separate Servers
On Database Server
Views on Web Servers


Default option
Only supported when using a single PS
web server
Sharepoint “Front-End”
IIS
Project Server
IIS, ASP Pages
View Processing Svc
NT Service
Project Data Service
XML Web Service
Views on Separate Server



Required for clustered PS web servers
Increased publishing capacity
Single processor speed is critical
WSS
PS
PDS
View Processing Svc
NT Service
Views on Multiple Server



New capability in SP1
Not ‘clustered’, additional separate
servers
Single processor speed is critical
View Svc
WSS
PS
PDS
View Svc
Views on Database Server



Eliminates network overhead during publish
Increased publishing speed
Single processor speed is critical
PS Views DB
View Processing Svc
NT Service
Database Partition Options



Single Database
Two Databases
Three Databases
Single Database


All three logical table sets on one
machine
Default install option
WSS DB
PS Views DB
PS Core DB
PS Projects
DB
Two Databases


Separate server for views data
Supported through PS Installer
WSS DB
PS Views DB
PS Core DB
PS Projects
DB
Three Databases



Separate server for views data
Separate server for project data
Requires use of command line tools
WSS DB
PS Core DB
PS Projects
DB
PS Views DB
Multi-Site Configurations



Multiple Project Server web sites on
single hardware platform
Separate database (not server) per
Project Server site
Additional flexibility for views
processing and database layout
Multi-Site Front End


Single or Dual web server clusters for
all sites
Number servers based on total number
of concurrent users supported
WSS
Project Server
WSS
PDS
Project Server
WSS
PDS
Project Server
PDS
Views Processing Options


Multiple sites per views server
Multiple views servers per site
View Svc
Site 1
Site 2
Site 3
View Svc
Database Options



Multiple servers, partition by site
Multiple servers, partition by usage
Multiple servers, partition by function
Site 1
Core
Site 1
Site 2
Core
Site 3
Site 2
Site 1
Views
Site 2
Views
Site 4
10 Common Project
Server Mistakes
Mistake #10



Problem: PWA Users receive a “size
limit error” when submitting Status
reports
Mistake: There are limits on the volume
of text users can submit through status
reports’ ActiveX control
Resolution:


Submit smaller quantity of text
Use WSS, InfoPath or “other”
Mistake #9



Problem: Portfolio Analyzer reports are
not interactive
Mistake: A licensed Office 2003 product
has not been installed
Resolution:


Install an Office 2003 product (isnt this
PWA?)
Unregister and Reregister the PWA DLL
Mistake #8



Problem: After installing WSS, the
Project Server site or pages with grid
controls won’t load
Mistake: WSS installed after Project
Server
Resolution:


Install WSS first
Modify the Exclude list
Mistake #7



Problem: You’ve upgraded from STS ’02
to WSS ’03 and issues have not
migrated
Mistake: Failed to run STSWiz.exe after
running OWS1002.exe
Solution:

Run STSWiz.exe before running
PSMIGRAT.exe
Mistake #6



Problem: Project Professional users
receive Spooler Error 0x80040E14 when
publishing
Mistake: PWA users self-assign
themselves to tasks and Project
Managers assign that user to the same
task
Resolution:


Change your company’s processes
Hotfix (not included in SP1)
Mistake #5



Problem: Users receive login error
when trying to download new
assignments
Mistake: IE Security allows for ONLY
“Automatic logon only in the intranet
zone”
Resolution:

Set IE Security to “Automatic logon with
current user name and password”
Mistake #4



Problem: Timesheet doesn’t reflect
changes to Tracking settings
Mistake: Project Professional users
have failed to Re-Publish assignments
Resolution:

Republish All Project Plans
Mistake #3



Problem: OLAP Cube fails to build!
Mistake: This could be a number of
things, but one of the main reasons is
the existence of special characters in
the ERP and/or EROCs
Resolution:

Refrain from using special characters in
the ERP and/or EROCs
Mistake #2



Problem: Project Server fails after
installing a hotfix or service pack!
Mistake: Not reading the instructions
Resolution:



Install in Test Environment
Make backups
Read ALL of the instructions
Mistake #1



Problem: Performance Issues!
Mistake: Poor Planning
Resolution:






Talk to Experts!
Plan, Plan, Plan… Plan
Proof of Concept
Explore Configuration Planning Guide
Test Pilot
Small Rollouts
How to contact us

Bennett Adelson

www.BennettAdelson.com

Sean Pales
 1-877-328-7122 ext. 103
 1-440-684-5000 ext. 103
 [email protected]
Thank you for attending
Q&A