Deploying EPM 2007 Solution into an Existing MOSS environment

2. IBP303 Deploying EPM 2007 Solution into an Existing MOSS environment Emmanuel P. Fadullon Jean-Noël Lienhart Microsoft Services – WW COE EPM

3. Abstract • EPM solution 2007 is a very unique form of WSS V3. This session will provide you with best practices learned from field deployments which you will want to keep in mind when deploying EPM 2007 into an existing MOSS farm.

4. Agenda • Overview • Key Architectural Considerations • Architecture • Implementation • Hosting • Authentication/Authorization • DEMO – Project Server on MOSS • Deployment and Operational Considerations • Installation • Licensing • Workspaces • Maintenance and Disaster Recovery • Admin Roles • Performance Lab • Supportability • Resources

5. Objectives • Learn about EPM solution and deployment considerations • Learn about EPM on MOSS licensing and operational considerations • Learn about EPM performance considerations

6. OverviewWSS v3 Core Services Management DelegationProvisioningMonitoringStaging Security Rights\RolesPluggable Auth.Per ItemRights Trimming Storage RepositoryMetadataVersioningBackup Topology Config. Mgmt.Farm ServicesFeature PolicyExtranet Site Model RenderingTemplatesNavigationVisual Blueprint APIs Fields\Forms OM and SOAPEventsDeployment Web Parts | Personalization | Master Pages | Provider Framework (Navigation, Security…) Database services Search services Workflow services Operating System Services

7. OverviewEPM with WSSv3 • Demand Mgt • Capture proposals • Business case development • Activity & maintenance • 3rd party integration • Initiation workflow • Portfolio Selection • Strategy prioritization • Project Prioritization • Portfolio Optimization • Advanced Portfolio Analytics • Resource Mgt • Skill & named resources • Resource pools • Capacity planning • Capture resource requirements • Search for resources, availability, skills • Scheduling • Macro + detailed level • Full project scheduling • Dependency management • Budget vs. Actual vs. Forecast • Time Tracking • Time sheets • Outlook integration • Capture non project time • Financial Period • Closing Process • Financial Mgt • Cost resources • Budgeting • Cost hierarchy • Budget vs. Actual vs. Forecast • Capture benefits • Change request • Governance • Best practices & methodology • Templates to standardize data/metrics • Governance models • Customizable detailed workflow • Reporting • Report template • KPIs • Dashboards • Scorecards • Workspaces • Extensibility • SDK • Web Services • Line of Business Integration • Reporting Services • Excel Services • Performance Point • Collaboration • Workspaces • Document management • Notification + Alerts • Issues and risk management (list) • Workflows Core Services Web Parts | Personalization | Master Pages | Provider Framework (Navigation, Security…) Database services Search services Workflow services Operating System Services

8. OverviewEPM with MOSS/WSSv3 EPM Portfolio Selection Resource Mgt Scheduling Time Tracking Governance Reporting Extensibility IBP208: Why customers are deploying SharePoint Server in conjunction with Project Server 2007 for effective project management and collaboration? Portal MySites Targeting People Finding Social Networking Privacy Profiles Site Directory Collaboration DiscussionsCalendarsE-MailPresenceProject MgtOffline Content Mgt AuthoringApprovalWeb PublishingPolicy & AuditingRights MgtRetentionMulti-LingualStaging Search IndexingRelevanceMetadataAlertsCustomizable UX BPM Rich\Web FormsBiz Data CatalogData in ListsLOB ActionsSingle Sign-OnBizTalk Integ. BI Excel ServicesReport Center KPIsDashboardsSQL RS\AS Integ. Data Con. Library Core Services Web Parts | Personalization | Master Pages | Provider Framework (Navigation, Security…) Workflow services Database services Search services Operating System Services

9. CPICCapital Planning & Investment Control for Federal Government • Gather accurate investment data • Consolidate agency data • Provide a portfolio level with drill down to project level • Reduce if not eliminate additional tool procurement • Regulatory challenges: • The Federal Acquisition Streamlining Act of 1994 (FASA), Title V, requires agencies to define cost, schedule, and performance goals for federal acquisition programs (including IT projects) and monitor these programs to ensure that they remain within prescribed limits • The Government Performance and Results Act of 1995 requires federal agencies to set goals, measure performance, and report their accomplishments • The Paperwork Reduction Act of 1995 requires federal agencies to use information resources to improve efficiency and effectiveness of operations • The Clinger-Cohen Act of 1996 requires federal agencies to focus on the results they are achieving through IT investments

10. CPIC • http://www.epmconnect.com/CPIC%20in%20Federal%20Government%20for%20EPM/Pages/ScenarioContent.aspx Project Workspaces

11. ArchitectureProject Server 2007

12. ImplementationSimple to Complex

13. HostingIn-hosting versus Out-hosting

14. HostingConsiderations • In-hosting • Easy to set up and manage • Uses same Web Content Application - application pool • Same SSP, same Config DB, but separate databases • Same SSP – single app pool credentials can see data for all instances • Same SSP admin, must be trusted by all organizations using the SSP • Application pool crashes affects all organizations using the SSP • Out-hosting • Repeat SSP instance provisioning • Separate, isolated instances • Multiple SSPs, separate ports • Different app pools, different credentials • One app pool crash affects one instance • Separate perf throttling • Same Config DB • Performance could start degrading faster due to several app pools

15. Authentication & Authorization • Windows Authentication • Single logon account • Seamless experience across all Project Server components • WSS Forms Authentication (Project Server user) • WSS provides logon page • Allows users to access Project Server from Extranet or without Windows accounts • WSS does Authentication • Project Server user needs logon permissions in WSS Content Database and Workspaces • Project Server does Authorization • Project Server user needs logon permissions in Project Server database

16. Project Server on MOSS demo

17. Installation • Pre-requisites • .Net 3.0, .Net 2.0, SQL Server Surface Area Configuration • Install binaries • MOSS on first server • Project Server on same server • Run the SharePoint Products and Technologies Configuration Wizard • Add servers to farm as needed (Repeat MOSS, PS, Wizard) • Configure services • Start Project Server application service • Start Office SharePoint Server Search Service • Create Web applications • Create SSP • Provision Project Server sites • Details http://technet2.microsoft.com/Office/en-us/library/fd6640e9-d7c6-4108-b6fd-7eba162a5b621033.mspx?mfr=true

18. Licensing • Same SharePoint Products and Technologies installed • Cannot add Project Server only to MOSS farm • Must install Project Server and MOSS • Secure by reducing attack surface area -- turn off services on particular servers • Server and Client licenses • Project Professional • Project Server • Project Web Access CAL • MOSS • SQL Server • Windows • Exchange Server • Outlook

19. Workspaces WinProj • Users are created • Users are granted access to PWA • Users are added to project team (do not have to be assigned a task) • On publish • A plan is published • The Project Workspace (PWS) is created • Roles/Users added to the PWS Content Web App ContentDB PWA PWS PWS SSP ProjDBs Project Server Interface

20. Administrative backup Settings backup Recycle Bin Versioning Maintenance and Disaster Recovery Backup/Restore Content Recovery Disaster Recovery • SharePoint Backup/Restore • SQL-Only • DPM 2007 • 3rd Party Tools • Database Mirroring • Log-Shipping • SQL Clustering Which combination of tools is right for your environment? Once a DRP has been implemented it is IMPERATIVE to test it regularly !!!

21. Admin Roles Admin Pro IT Pro PMO Pro Project Users

22. IT Pro Role • Farm Administrator • Responsible for • Setup and Configuration of Farm • Installation of Project Server • Project Web Servers • Project App (PSI / Queue) Servers • SQL Server 2005 • SQL Database Server • SQL Reporting Services • Analysis Services • Custom External Interfaces • Installation and Configuration

23. Admin Pro Role • Shared Services Administrator • Responsible for • Administrative control at SSP level • Manage Configurations within • SSP Page • Backup and Restore • Provisioning Sites • PWA Admin Settings Page • Enterprise Objects, Queue, Cube Building, ADSync • Assist PMO Pro with functional setup and maintenance of project management features

24. PMO Pro Role • Project Server Administrator • Responsible for • Managing features and functionality • Manage Configurations within • PWA Admin Settings Page • Views, Groups, Categories, Custom Fields, Calendars • Project Professional

25. Performance Lab

26. Performance LabCustomer Statistics • Mon and Tue - ~50% of users; project updates, review tasks (9 – 11 AM) • Fri - ~90% of users; task update submit, logoff (4 – 5 PM) • IIS Web Logs/Page Hits – 77% My Tasks, 44% Home

27. Performance LabData Profile

28. Performance LabPWA Concurrency • Focus on My Tasks • Peak throughput should support less trafficked PWA pages • User Concurrency (UC) Calculation • User Load/Min = Total Users/(#Hrs*60)

29. Performance LabPWA Test Pattern • Test 1 - Load My Tasks • Test 2 - Load Home, My Tasks, Logoff • Test 3 - Load Home, Project Center, Project View, My Tasks • Over 6-hour duration • Step 10 users every half-minute to expected usage concurrency • Test 4 - Constant Load Home, Project Center, Project View, My Tasks • 4-hour duration • 40 users • Measurements: CPU, RAM, RPS, Avg. Test Time, Avg. Page Time

30. Performance LabQ Drain Test Pattern • Freshness of Data dictated by how quickly save/publish jobs are completed by the Queue service • Test 1 - No Load Test (Benchmark) • Increment Queue Threads • Test 2: Load Test • 40 users on Fri PM test pattern

31. Performance Lab % Processor (Test 1,2,3,4)

32. Performance Lab Test 4 – Constant Load (H,PC,PV,MT) A1 1 x 4 CPU B1 WFE = 1 x 2 CPU PSI = 1 x 4 CPU SQL = 1 x 4 CPU B2 WFE = 1 x 4 CPU PSI = 1 x 2 CPU SQL = 1 x 4 CPU B3 WFE = 2 x 4 CPU PSI = 2 x 2 CPU SQL = 1 x 4 CPU Profile 2750 users 400 projects RTM Build

33. Performance Lab Q Drain Test Pattern WFE = 2 x 4 CPU PSI = 2 x 2 CPU SQL = 1 x 4 CPU

34. Performance LabClient Pro Tests

35. Performance LabClient PWA Tests

36. Performance Lab Observations • Project Server does not scale linearly • Adding hardware scales to a point • Given adequate WFE/PSI hardware, the Data Access Layer (DAL) appears to be the main bottleneck • WFE processing is substantial relative to P11 • Web page/web part rendering • User session state management • Highest trafficked pages (e.g. Project Center, My Tasks)

37. Performance Lab Observations • Calls to Home, Project Center and Project View quickly increase PSI CPU utilization • WFE and PSI on same server increases system resource contention • Optimizing the system requires data volume with all components in concert – WFE, PSI, Queue operations and SQL • Increasing queue threads and queue processing load decreases WFE performance (manifests “Page White Out” condition)

38. Performance Lab Scenarios – 500, 2500, 5000, 7500 Users

39. Performance Lab Scenario - 10,000 Users

40. Supportability • SP1 • Post-SP1 Rollup Fixes • Apply WSS SP1 first, then MOSS SP1 (contains Project Server) • Why? • ~90 fixes in SP1 • 30+ fixes in Rollup • Cumulative • No dependencies between Project Professional and Project Server

41. SP1 • Lookup table and custom fields • Active cache • Queue • Timesheet and statusing • Performance • Stability • KB 942386 – Project 2007 fixes • KB 942387 – Project Server 2007 fixes • KB 942388 – WSSv3 fixes • KB 942390 – OSS 2007 fixes • KB 942722 – PPS 2007 fixes

42. Post-SP1 Rollup • KB articles • KB 941657 – Project 2007 fixes • KB 941426 – Project Server 2007 fixes • KB 942679 – Project 2007 localization fixes • KB 941422 – WSSv3 fixes • KB 941274 – MOSS 2007 fixes

43. Resources • Project Server 2007 Planning, Architecture, Deployment and Operations • Project 2007 Software Development Kit • Sample Code (e.g. Impersonation, ProjTool) • RDB and OLAP schema • SSRS Report Pack • Project 2007 Project Resource Kit • Portfolio Analyzer Views Migration • Project Server Settings Backup and Restore (Playbooks) • Project Server Data Populator • Project Workspace Site Relinker • View Effective Rights • Project 2007 Codeplex Code • Project Server 2007 Timesheet Tied-Mode Service and Event Handler • Project Server 2007 Queue Watch Tool • Project Server 2007 Log File Report Tool • Project Server 2007 VSTS Connector • Project Product Team blogs • Changing Status Manager • Cost and Budget Resources • IBP208: Why customers are deploying SharePoint Server in conjunction with Project Server 2007 for effective project management and collaboration?

44. Post Event DVD brought to you courtesy of:

45. SUBMIT AN EVALUATION For a chance to win an 8GB ZUNE! Submit evaluations on MySPC www.MicrosoftSharePointConference.com

46. © 2008 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.