Deploying Project Server 2007 into an Existing SharePoint Server 2007 Farm

Name: Akesh Lalla (Solutions Sales Professional: EPM)Bishan Ruder (Premier Field Engineer: EPM)

Company: MicrosoftSession Code: OFC310

Session Objectives And Takeaways

Session Objective(s): Learn benefits of deploying Project Server 2007 into a SharePoint server farm Learn best practices on how to deploy Project Server into an existing SharePoint server farm

Plan Deployment ScenarioPlan Site Collections carefullyDeploying Project Server 2007 is an enterprise undertaking

Agenda

Project Server OverviewBenefits of Deploying with SharePoint ServerDeployment Scenarios and Best PracticesNext Steps and Resources

Enterprise Project Management (EPM)Project & Portfolio Lifecycle

ManageSelectCreate Plan

Identify gaps between resource availability & demand at the skill level

Maximize resource utilization

Search for resources with availability & assign to projects

Capture all requests, from work orders to discretionary projects

Standardize metrics, valuation criteria and templates

Control investment through governance workflow

Prioritize business drivers Identify portfolios that align with strategy and maximize ROI

Adopt a rational portfolio selection methodology

Proactively monitor portfolio performance and visualize trends

Assess risks, issues & status for each project

Track and compare budget, actual and forecast values

Windows SharePoint Services (WSS) V3Document ManagementChange Request ManagementWIKIS, Blogs, FAQs, and more…

Project Server as a SharePoint ApplicationProject Web Access (PWA) contains:

Web Part pages13 Project Server web partsProject Workspace

Rich Gantt Chart ReportsIssues and Risk ManagementManage inter-project dependencies with DeliverablesAbility to import WSS Project Task list

Project Server and SharePoint ServicesOut of the box features

Project Server Web PartsData Analysis Reminders

My Queued JobsResource Assignments

My Schedule Resource Center

My TimesheetTask Update Request

Project Center Team TasksProject Details User TasksProject Workspaces

Project Server 2007Logical architecture

Application/PSI ServerWeb Service Tier Business Logic Tier

Remote Access

•Terminal Services•VPN

Domain

•Firewall•Active Directory•DNS•Exchange

Logs

•Web•ULS•Perf Counter•Event•PSConfig

Services

•Project •WSS •NT

Patch Management

•Binaries•Data Schema

Platform

•Virtualization•32/64 Bit•IIS

Sub-System

•Network•Processor•Memory•Disk

System

Fault Tolerance

•Loadbalancing•Clustering•Mirroring•Backup•Disaster Recovery

Client

•Scheduling Engine•Desktop Reporting•Local Cache•Soap Client•Serializer

Project Professional

•IE Browser Level•Security Zone•ActiveX Controls•Office Web Comp•Outlook Addin

Project Web Access

•Custom Logic•Impersonation•Local access to SSP

3rd Party Client

Web Server

Auth

entic

ation

PSI ForwarderLocal Server Cache

PSI Proxies

ASPX

Master Pages

Web PartsPr

ojec

t Use

r Con

text

Database Server

Central AdminContent Database

Web ApplicationContent Database(n)

Shared ServicesService Database

Shared ServicesContent Database

Project ServerDraft Database(n)

Project ServerPublished Database(n)

Project ServerReporting Database(n)

Project ServerArchive Database(n)

Farm Configuration Database

Exte

rnal

Web

Ser

vice

s

Inte

rnal

Web

Ser

vice

s

ASM

X D

efini

tion

Project User Context

Dat

a Ac

cess

Lay

er

Serializer

Filt

er D

ata

Acce

ss L

ayer

Bus

ines

s O

bjec

ts

Server Side Scheduling

QueuingService

EventingService

User session state

Root SiteWeb AppPWA and WSS content pages

CentralAdmin

Web Apphttp://ServerName:56737/SSPName/psi/*.asmx

All servers in farm (Timer Service)

http://ServerName/InstanceName/_vti_bin/psi/*.asmx

SSPWeb App

Agenda

Project Server OverviewBenefits of Deploying with SharePoint ServerDeployment Scenarios and Best PracticesNext Steps and Resources

Consistent User Interface

InnovationProcess

Management

ProjectPortfolio

Management

ApplicationLife-Cycle

ManagementInvestmentGovernance

Better Together Solution

Timesheet

Collaboration

Resource and Schedule Management

Project Management Capabilities

Collaboration Capabilities

Business InsightBusiness Process

& FormsEnterprise Content

Management

Collaborative Workspaces

Search

Portal

DemandManagement Plan & Execute Business Insight

Governance Workflow

Demand Management

Portfolio Selection

Reporting

Portfolio Analytics

Program Management

Business Intelligence PlatformSharePoint Server

Leverage the rich Project Server data stores usingExcel ServicesReport CenterKey Performance Indicators

PerformancePoint ServicesBusiness Data CatalogProject Server OLAP Cubes

Core Project

Timesheet Collaboration

Analysis Services Database

Project Server Reporting

Core ProjectServer Schema

CollaborationSchema

TimesheetSchema

RelationalDatabase

Integrates and exposes back end systems within SharePoint Server

Data can be queried, filtered, and indexedRespects permissions of back end systemsDatabases and web services

Incorporate other systems with SharePoint sitesReporting dashboardsLine of business applications

Search for data in other systems via the SharePoint Search servicePresent data in SharePoint through Web Parts, Lists, User Profiles

Line of Business IntegrationBusiness Data Catalog (BDC)

Customer Specific Business ProcessesInfoPath Forms Services

Three state Workflow for Project Server Proposals + standard SharePoint workflowsWeb based Interface with InfoPath Form ServicesData Validation ConditionBuild your own business workflow using Windows Workflow Foundation

Input Process Output

InfoPathWordExcel

Windows

Worflow

Customer

Specific

Processes

Why Deploy with SharePoint Server?

Project Server + SharePoint Server = Best of EPM + Best of CollaborationBenefits of deploying both

Business Intelligence OfferingsBetter Project Reporting

Line of Business IntegrationBest of Breed Applications

Customer Specific Business ProcessesBetter Change Management

SharePoint Server VersionsStandard

Project Proposals, Project Server 2007 specific featuresSearchWorkflowAudiencesContent Management

Enterprise

Project Proposals, Project Server 2007 specific featuresSharePoint StandardExcel ServicesInfoPath Forms ServicesKey Performance IndicatorsBusiness Data Catalog (BDC)

Refer to Microsoft Office SharePoint Server 2007 products comparison download http://office.microsoft.com/en-us/sharepointserver/HA101978031033.aspx

Existing SolutionsLeveraging both products

Project Portfolio ManagementCapital Planning & Investment Control for Federal GovernmentInnovation Process Management

Agenda

Project Server OverviewBenefits of Deploying with SharePoint ServerDeployment Scenarios and Best PracticesNext Steps and Resources

User requests

Load balances webfront end servers

Applicationservers

Clustered SQL server

Index Search Excel Project

Large Farm

User requests

Web front ends + application(s)

Application(s)

Clustered SQL server

Medium Farm

Small FarmUser requestsEach load-balanced server includes:

Web front end Applications

Dedicated SQL server

One Server which contains:

Single Server

• Web front end • Application • Database

User Requests

Availability

Perf

orm

ance

ImplementationSimple to Complex

Deployment ScenariosFrom WSS to SharePoint Server

New Farm, no existing dataExisting Project Server + WSS Farm to Another SharePoint Server FarmUpgrade existing Project Server + WSS Farm with SharePoint Server

ConfigDB

ContentDB

SSPDB

Draft DB

1 SPWebApplication = _Admin ContentDB = SharePoint_AdminContent

1 SPSite = Central Administration ConfigDB = SharePoint_Config

Objects

ContentDB

ContentDB

1 SPWebApplication ContentDB=WSS_SSPAdmin

1 SPSite Port XXXX= SharePoint - XXXX 1 SPDatabases:

<SSPName>_ SSP_DB 1 IIS web site = OfficeSharedWebServices 1 IIS vDir = <SSPName_ShareSvcs>

1 SPWebApplication = WSS ContentDB=WSS_Default_YY

1 SPSite Port YY = SharePoint - YY ContentSite

Web App

Web App

Web App

Published DB

Reporting DB

Archive DB

Site Collection Root = ProjectServer Databases

ProjectServer_DraftProjectServer_PublishedProjectServer_ReportingProjectServer_Archive

SharedWeb Services

SSP Site

CA Site

Project Server with WSS Farm

Central Admin

Shared Services

Site

Project Server

1 SPWebApplication = _Admin Site 1 SPDatabase = AdminContentDB

1 SPSite = Central Administration 1 SPDatabase = ConfigDB

1 SPWebApplication = WebAppSSP 1 SPDatabase = ContentDB

1 SPSite = <SSP Name> 2 SPDatabases:

<SSPName>_SSP_DB <SSPName>_SSP_Search_DB

1 IIS web site = OfficeSharedWebServices 1 IIS vDir = <SSPName_ShareSvcs>

1 SPWebApplication = WebApp 1 SPDatabase = ContentDB_YY

1 SPSite Port YY = SharePoint - YY

ConfigDB

ContentDB

SSPDB

Central Admin

Shared Services

Site

Objects

ContentDB

ContentDBContent

Site

Web App

Web App

Web App

Index Server

SharedWeb Services

SSP Site

CA Site

Minimum SharePoint Only Farm

Index File

SSP Search DB

ConfigDB

ContentDB

SSPDB

Central Admin

Shared Services

Site

ContentDB

ContentDBContent

Site

Web App

Web App

Web App

Index Server

SharedWeb Services

SSP Site

CA Site

Combined SharePoint Server + Project Server Farm Unique SSP

Index File

SSP Search DB

Draft DB

Published DB

Reporting DB

Archive DB

Project Server

Site ContentDBContent

Site

For MySite or other

For the Project Workspaces

1 SPWebApplication = _Admin ContentDB = SharePoint_AdminContent

1 SPSite = Central Administration ConfigDB = SharePoint_Config

1 SPWebApplication =WSS XXXX ContentDB=WSS_SSPAdmin_XXXX

1 SPSite Port XXXX= SharePoint - XXXX 1 SPDatabases:

<SSPName>_SSP__DB <SSPName>_SSP_Search_DB

1 IIS web site = OfficeSharedWebServices 1 IIS vDir = <SSPName_ShareSvcs>

1 SPWebApplication = WSSZZ ContentDB=WSS_Default_ZZ

1 SPSite Port ZZ = SharePoint - ZZ

Site Collection Root = ProjectServer Databases

ProjectServer_Draft,ProjectServer_Published,ProjectServer_Reporting,ProjectServer_Archive

1 SPWebApplication = WSSYY ContentDB=WSS_Default_YY

1 SPSite Port YY = SharePoint - YY

Microsoft Confidential

Project Server with SharePoint ServerName: Bishan RuderTitle: Premier Field EngineerCompany: Microsoft

demo

Project WorkspacesIncludes specific SharePoint collaboration lists

Project DocumentsProject RisksProject IssuesProject Deliverables

Site must be included in a Shared Service Provider with a running Project Server Application ServiceExtending the Project Workspace Template

Follow ALL instructionsStart customization from a new empty workspaceKeep the required lists Check Extending the Project Workspace Template on MSDN: http://msdn.microsoft.com/en-us/library/ms503640.aspx

Site Collection Recommendation Per Project Web Access (PWA) site

One web application in one content database by defaultOne site collection

Root PWA siteProject workspaces

Recommend two sites collections with separate content databaseFirst collection for root PWA siteSecond collection for Project workspacesAdvantages

Ability to restore without renaming PWA siteCan scale with multiple departments with independent site collections

May need several site collection for large organization (several 1000 workspaces)

Separate for each department/locationSite collection quotas/Locks

Creating a site collection in a separate DBStep 1: Add explicit inclusion on path /pwapwsStsadm –o addpath –url http://url/pwaPWS -type explicitinclusion

Step 2:stsadm -o createsiteinnewdb –url http://url/pwaPWS-owneremail AdminOwner@domain.Com

-ownerlogin domain\username-databaseserver SQLInstance-databasename WSS_Content_PWAPWS-sitetemplate PWS#0

+/- Deployment Scenarios Single versus Separate SharePoint Farms

Advantages and Disadvantages by Scenario

Together Apart

+ Server consolidation Minimize administration and

maintenance Leverage high availability

Farm updates Change management Security isolation

- Farm updates Additional Project Server

Licenses

Content management Additional SharePoint Licenses

Things to Consider for Each ScenarioTogether

Single maintenance planIsolate Project Server content

Separate Root Site CollectionSeparate Site Collection for Project Workspaces

Use same SSPTo synchronize Project Users permissions with project workspaces

Apart

More administrative tasksOut of the box Project Server content stored in workspaces cannot be stored on another farmSeparate maintenance/timing for handling Service Packs and Updates/Hot Fix

First Upgrade ScenarioAdd Project Server to an existing Farm

Install Office Project Server 2007 on all servers of the Farm + UpdatesEnable the Project Server Application service on any application serversCreate at least 2 sites collectionProvision an Office Project Server site on the FarmConfigure Project Server to use the specific site collection for workspaces

Second Upgrade ScenarioAdd SharePoint to an existing Project Server Farm

Install Office SharePoint Server 2007 on all servers of the Farm + UpdatesStart the Office Server Search service on any application serversConfigure additional Office SharePoint services

Merge scenario (1/2)With existing data

One Project Server Farm (with data)One SharePoint Farm (with data)Inter-Farm SSP not supported2 Possibilities

New hardware: Build a new Farm and migrate content of bothSame hardware: Upgrade SharePoint Farm scenario (Add PS) + Migrate contentDisconnect PS servers from PS FarmAdd SharePoint to PS Servers and join Farm

Merge scenario (2/2)With existing data

Migration of Project workspacesIf only one EPM site collection then site name issue:

Conflict when provisioning PWA site => Name clashNew PWA Site name orProject workspace manually restored if name is to stay

Project Server Capacity Planning

Refer to the TechNet documentation + White PaperProject Server Users are typically a fraction of the total Intranet User baseBut heavy use of dedicated relational databases and Analysis Services databases

Other Deployment ConsiderationsServer and Client licenses

Same SharePoint Products and Technologies installedMust install Office Project Server 2007 and Office SharePoint Server 2007 on each of your Web servers (load balancing requirement)

Isolate PS for performance and manageability purposes

New Site with its ownContent databaseApplication Pool

Isolate Reporting and OLAP databases64 bitAnd more…

Agenda

Project Server OverviewBenefits of Deploying with SharePoint ServerDeployment Scenarios and Best PracticesNext Steps and Resources

Deployment ProcedureOverview

Pre-requisites.NET 3.0, .NET 2.0, SQL Server Surface Area Configuration

Install binariesSharePoint Server (MOSS) on first serverProject Server (PS) on same serverRun the SharePoint Products and Technologies

Configuration WizardAdd servers to farm as needed (Repeat MOSS, PS, Wizard)

Configure servicesStart Project Server application serviceStart Office SharePoint Server Search ServiceCreate Web applications Create Shared Service Provider (SSP)Provision Project Server sites

PSCONFIG and STSADM are your friends!Details in TechNet

Once Deployed, You Must Have…It's an Enterprise Application!

Been trained all on all productsBackup/Restore PlanMonitoring PlanMaintenance PlanTested Disaster Recovery Plan

Supportability

June Cumulative Update

KB Description

971501 Project 2007

971502 Project Server 2007

970946 WSS V3

971537 SharePoint Server 2007

Service Pack 2

KB Description

953326 Project 2007

953334 Project Server 2007

953338 WSS V3

953334 SharePoint Server 2007

Check TechNet for deployment guidanceStay up to date with http://support.microsoft.com

Admin RolesIT Professional

Farm AdministratorSetup and Configuration of FarmInstallation of Project ServerProject Web ServersProject App (PSI / Queue) ServersSQL Server 2005

SQL Database ServerSQL Reporting ServicesAnalysis Services

Custom External InterfacesInstallation and Configuration

Admin ProfessionalShared Services AdministratorSSP level

Manage Configuration. withinSSP Page

Backup and RestoreProvisioning Sites

PWA Admin Settings PageEnterprise Objects, Queue, Cube Building, AD Sync

Assist PMO Pro functional setup and maintenance

Project Management OfficeProject Server AdministratorManaging features and functionalityManage Configurations within

PWA Admin Settings PageViews, Groups, Categories, Custom Fields, Calendars

Project Professional

SummaryCall-to-action

There are great benefits of deploying Project Server 2007 on top of SharePoint Server 2007Consider the platform elements as carefully as the application itselfPlan deployment scenario

Single SharePoint Farm (Together)Distinct SharePoint Farm (Apart)

Deploying Project Server 2007 is an enterprise undertaking

www.microsoft.com/teched

International Content & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources Tech·Ed Africa 2009 sessions will be made available for download the week after the event from: www.tech-ed.co.za

Learn MoreThe Microsoft Office Enterprise Project Management (EPM) Solution

http://www.microsoft.com/epmTechNet

Project Server TechCenter & SharePoint Server TechCenterProject Server 2007 Planning, Architecture, Deployment and OperationsDeploy Office Project Server 2007 with Office SharePoint Server 2007Newly published content for Office Project Server 2007IT Professionals webcast series

EPM Universityhttp://www.msepmu.com

EPM Connecthttp://www.epmconnect.com

BlogsProject Server IT Professionals Bookmarkshttp://blogs.msdn.com/project/http://blogs.msdn.com/project_programmability http://blogs.msdn.com/brismithhttp://blogs.msdn.com/shaden http://blogs.msdn.com/chrisfie

Upcoming Conferences

question & answer

Related Content

Breakout Sessions

Project Server 2007 Disaster Recovery (OFC314) | Tue 4 Aug (16:15 - 17:15) | 300 - Advanced| Session Room D1

Complete a session evaluation and enter to win!

10 pairs of MP3 sunglasses to be won

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.