Christophe Fiessinger Senior Technical Product Manager Microsoft Corporation Rolly Perreaux, PMP, MVP, MCSE, MCT Sr. EPM Consultant/Instructor PMO Logistics Inc SESSION CODE: OSP303

Project Server Clients SQL Server PWA Server Project Server 2010 Client Tier Application Tier Database Tier Web Tier Project Professional Published Active Cache PSI Forwarder Project Server Interface (PSI) Internet Explorer Microsoft SharePoint Foundation 2010 Microsoft SharePoint Server 2010 Microsoft SharePoint Foundation 2010 Microsoft SharePoint Server 2010 Draft Archive Reporting Config LOB Applications 3rd Party Applications Data Access Layer (DAL) Business Objects ASPX Pages Eventing System Queuing System Scheduling Engine Project Server Workflow System PWA Server ASPX Pages Content

EntitySmallMediumLarge Projects1005,00020,000 Tasks17,125856,250342,5000 Avg. Tasks Per Project Task Transaction History Assignments22,2631,113,1254,500,000 Avg. Assignments Per Task1.3 Approvals Users1,00010,00050,000 Custom Fields Project (Formula)32025 Project (Manual)24050 Task (Formula)61215 Task (Manual)4810 Assignment Rolldown50% Resource Look up Table Custom Fields Timesheets (per year)52,000780,0008,320,000 Timesheet Lines510

or higher

Central Admin Configuration Project Web Access Admin Configuration Post Configuration Install Project Server Run SharePoint Configuration Wizard Project Server 2010 Run Pre-Requisite Installer Install SharePoint Server 2010 SharePoint Server 2010 Install Windows Server Run Windows Update Base Installation Install SQL Server and Components Install Software Updates SQL Server

Project Server 2003Project Server 2007Project Server 2010 Project Professional 2003Full connectivityNot Supported Project Professional 2007Not SupportedFull connectivity Connectivity to Server in BCM* (Project Professional 2007 SP2 required) Project Professional 2010Not Supported Full connectivity Installation RequirementWill coexist on the same farm with Will NOT work with Project Server 2010SharePoint Server 2010 Enterprise Office SharePoint Server 2007 Project Server 2007Windows SharePoint Services 3.0 Office SharePoint Server 2007 SharePoint Server 2010 Project Desktop and Project Server Project Server and SharePoint Server

Existing Office Project Server 2007Install SharePoint Server 2010Install Project Server 2010Run the “Configuration Wizard” (PSConfig)

Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub.

Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31 st You can also register at the North America 2011 kiosk located at registration Join us in Atlanta next year

Client Scheduling Engine Desktop Reporting Client Active_Cache Soap Client Serializer Project Professional IE Browser Level Security Zone AJAX Project Web Access Custom Logic Impersonation 3 rd Party Client Web Server Database Server Central Admin Content Database Web Application Content Database(n) Shared Services Service Database Shared Services Content Database Project Server Draft Database(n) Project Server Published Database(n) Project Server Reporting Database(n) Project Server Archive Database(n) Farm Configuration Database PWA and WSS content pages WCF Services State Service Database Application/PSI Server Web Service Tier Business Logic Tier External Web Services Internal Web Services Project User Context Data Access Layer Serializer Filter Data Access Layer Filter Data Access Layer Business Objects Business Objects Server Side Scheduling QueuingService EventingService WCF Interface ASMX Interface Workflow Platform Windows Workflow Foundation Microsoft SharePoint Server 2010 Microsoft SharePoint Foundation 2010 Authentication PSI Forwarder Server Active_Cache PSI Proxies ASPX Master Pages Web Parts Project User Context Microsoft SharePoint Server 2010 Microsoft SharePoint Foundation 2010 Web Analytics Database WCF Services ASMX over http/soap

Sizing: 1.NOT about how many users 2.NOT about how many servers 3.IS how many workloads/profile 4.IS how many system resources General considerations: 1.# Instances 2.# web applications 3.Throughput tolerance 4.Co-existence 5.64 bit (scale up) Virtualization: 1.Size for physical first 2.Extrapolate to virtual 3.Dedicate high demand to physical 4.Allow host machine overhead Storage: 1.SAN configuration 2.RAID level & optimization 3.# spindles 4.Storage size 5.File group allocation Balance: 1.Physical footprint 2.Scalar depth vs. concurrency 3.System ratios vs. server role 4.Physical vs. virtual allocation FINAL STEPS: 13.Size to physical server count 14.Size to virtual guest count Physical Virtual Primary Team Heartbeat Backup Restricted Management Un-Restricted Management Network Memory 16Gb Bus Hardware Processor Internal Storage 72GB RAID 1 72GB RAID 1 1.Determine workloads 2.Determine data profile 3.Determine throughput 4.Determine queue model 5.Size application resources Application Server Primary Team Heartbeat Backup Restricted Management Un-Restricted Management Network Memory 32Gb Bus Hardware Processor Internal Storage 72GB RAID 1 72GB RAID 1 External Storage 1TB RAID 1+0 SAN Connections Host Bus Adaptor 6.Determine workloads 7.Determine resource ratios against application server 8.Determine resource ratios against SQL server 9.Determine file allocation SQL Server Primary Team Heartbeat Backup Restricted Management Un-Restricted Management Network Memory 16Gb Bus Hardware Processor Internal Storage 72GB RAID 1 72GB RAID 1 10.Determine workloads 11.Determine user concurrency 12.Determine resource ratios Web Server

1.TCC (Total CPU Count): The TCC represents the number of CPUs required for the SQL Server. Apply a ratio of 1:2 against the Application Server TTC. 2.TRC (Total RAM Count): The TRC represents the amount of memory for the SQL Server. Apply a 1:4 ratio of CPU to RAM. This is imperative on a SQL Server using 64bit. 3.Total TempDB Count: The total number of TempDB files to allocate from the TCC. Apply a 1:1 ratio with the TCC. 4.Total TempDB Size: The total size of the TempDB to allocate from the Profile Database Size. The size is calculated as 25% of the Draft database size. As the Database Size column includes all 4 databases for that instance. TempDB Size = [Profile Database Size] X [.25] / [TCC] 5.TempDB Spindle Count: This represents the number of spindles to allocate across TempDB. The rule is one spindle per file group. RAID 10 is recommended, therefore doubling the count. InputValueCalculation ProfileThreeN/A # Users5000N/A # Projects1500N/A Application Server TCC4Refer to Application Server table SQL Server TCC81:2 TRC16Gb1:4 Total TempDB count81:1 with SQL Server TCC Total TempDB size2.6Gb86Gb * 0.25 / 8 TempDB Spindle Count168 * 2 SQL File Allocation - C:\80GbOperating System file. RAID SQL File Allocation - D:\120GbLocal storage, log files. RAID SQL File Allocation - E:\110GbData files RAID 10 or RAID 5: Database Size + 25% (Disk Defrag space). SQL File Allocation - F:\30GbLog Files RAID 10: Total Database Size * 25%. SQL File Allocation - G:\2.6GbTempDB Data files RAID 10. SQL File Allocation - H:\1GbTempDB Log files RAID 10. Total TempDB Size * 25%. † = † = Minimum startup value 8Gb RAM

1.Profile: Use the Profile column the Estimated Database Size table to determine the number of projects in the system for processing. 2.# Users: Resource column from the chosen Profile row. 3.# Jobs: Project column from the chosen Profile row. 4.JTM = minutes. (Refer to whitepaper for details) 5.HT (High Throughput): To reduce a race condition on the Queue Group, set the Queue thread count to 1.5 per CPU on the server (do not exceed more than 12 threads for the entire farm – the Queue thread count is per Application Server). For each Application Server role added to the farm, the Queue thread count must be reduced proportionately to ensure Maximum Thread Count (MTC) of 12 is not exceeded. 6.PW (Processing Window): The PW represents a processing window through the Queue during peak load of 30 minutes. 7.TPT (Total Processing Time): The TPT represents the total estimated time to process all jobs on a single Queue thread - JTM x # Jobs. 8.TTC (Total Thread Count): The TTC represents the number of Queue threads to process the # Jobs within the desired processing window. TPT / PW. 9.TCC (Total CPU Count): The TCC represents the number of CPUs required for the Application Server. HT / TTC. 10.TRC (Total RAM Count): The TRC represents the amount of memory for the Application Server. Apply a 1:2 ratio of CPU to RAM. InputValueCalculation ProfileThreeN/A # Users5000N/A # Projects1500N/A JTM0.146N/A HT1.5N/A TPT219 minutesJTM * #Projects TTC7.3 threads (Round up to 8)TPT / PW. TTC not to exceed 12. TCC4.66 (Round down to 4 CPU)TTC / HT TRC8Gb1:2 † = † = Minimum startup value 8Gb RAM

1.TCC (Total CPU Count): The TCC represents the number of CPUs required for the Web Front End server. 1 – 1000 users = 2 CPU 1001 – 5000 users = 4 CPU 5001 – 15,000 users = 8 CPU 2.TRC (Total RAM Count): The TRC represents the amount of memory for the Web Front End Server. Apply a 1:2 ratio of CPU to RAM. InputValueCalculation ProfileThreeN/A # Users5000N/A TCC4N/A TRC8Gb1:2 † = † = Minimum startup value 8Gb RAM

Dedicated Project Server FarmDedicated SharePoint Server Farm CoexistenceAdd SharePoint ServerAdd Project Server Merge into a single Farm StandaloneSplit Existing Farm into two Farms EPM and Office SharePoint Server 2007 Coexistence — Intranet ScenarioEPM and Office SharePoint Server 2007 Coexistence — Intranet Scenario (TechNet whitepaper applicable to 2010)

Together Pros and Cons Single Project and SharePoint Server Farm

Apart Pros and Cons Separate Project and SharePoint Server Farm

Project Workspaces cannot be created in another Farm, but can belong to multiple Site Collections Content Integrating Project Server Web parts in other SharePoint sites Supported scenarios documented in TechNet Page Viewer Web part Web Part Surfacing Project Server data KPI, Excel Services, PerformancePoint Services, Business Connectivity Services, SQL Reporting Services, Dashboards Reporting Querying Project Server data Enterprise Search and Business Connectivity Services Search