1 / 26

Microsoft Office Project Server 2007 – Solution Overview and System Elements

Microsoft Office Project Server 2007 – Solution Overview and System Elements. Michael Jordan Lead Architect (EPM Global Practice) Microsoft Corporation michjor@microsoft.com. Webcast Series What to expect. Solution Overview and System Elements Solution Elements and Data Flow

vic
Download Presentation

Microsoft Office Project Server 2007 – Solution Overview and System Elements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Microsoft Office Project Server 2007 – Solution Overview and System Elements Michael Jordan Lead Architect (EPM Global Practice) Microsoft Corporation michjor@microsoft.com

  2. Webcast SeriesWhat to expect • Solution Overview and System Elements • Solution Elements and Data Flow • Workload Scenarios and Reference Architecture • Network Communication • Server Administration • Maintenance and Monitoring • Deployment into a SharePoint Server Intranet Farm • Disaster Recovery • Virtualization

  3. Prerequisite Knowledge • Deployed Microsoft® Office Project Server 2007 as a proof of concept (POC) • Reviewed these TechNet and Microsoft® Developer Network (MSDN®) sites: • http://technet.microsoft.com/en-us/library/cc303399.aspx • http://msdn.microsoft.com/en-us/office/aa905469.aspx Level 300

  4. What We Will Cover • Introduce the solution and the main components • Describe key concepts • Discuss main considerations when planning for deployments that require high availability: when to scale up and out, points of failure, and software/hardware boundaries.

  5. Agenda • Concepts • Consolidation • Solution overview • System elements

  6. ConceptsContainment Hierarchy FARM SYSTEM Platform, Network, Multiple NICs, Storage, Logs, Load balancing SERVERS WFE, PSI, SQL, AS, SSRS, MOSS DATABASES Config, Admin, SSP, Content, Project, Reporting, Cubes, Custom, TempDB APPLICATIONS Central admin, Shared service provider, Site, Web services, Queue, IIS, Security, AVS PROJECT PROFESSIONAL PROJECT WEB ACCESS Win32®, Office 200(x) Web parts, Aspx, OWC, ActiveX®, Outlook® add-in SITE COLLECTIONS ENTERPRISE OBJECTS C/Field, Resource, Duration, Calendar, Baseline, #Task/Assn Team site, Templates RENDERING COMPLEXITY DATA COMPLEXITY LOCAL OBJECTS WORK SPACES Cache, CBS (Visual reports), MLU, Macros Instances, Projects, Issues, Risks, Documents SCHEDULE RELATIONSHIP VIEWS Project views, Workspace views, Security Master/sub projects, Dependencies, Constraints, Ext Links SYSTEM SYSTEM Network environment, OS, Memory, CPU, AV Browser, Network environment, OS, Memory, CPU, AV TEAM USER PROFILE PROJECT MANAGER PROFILE Operations, Workload scenarios, Concurrency, Location Operations, Workload scenarios, Concurrency, Location

  7. ConceptsHigh Availability/Scalability High availability with clustering, scaling out, distribution, and load balancing Workload Scenarios High availability with clustering, scaling out, and load balancing Other increases Firewall IT Resources – E.g.: Skills Help Desk Budget – E.g.: Hardware SLA Cross technology – E.g.: Load balancing Virtualization Offloaded SQL for performance Workload Scenarios Load balance Scalability Workload Scenarios Load balance Web Server Single point of failure for all Web Server App Server Web Server App Server Workload Scenarios App Server Web Server App Server Database Clustered or Mirrored Database Clustered or Mirrored Database Database High Availability

  8. Agenda • Concepts • Consolidation • Solution overview • System elements

  9. ConsolidationCharacteristics Business Process Help desk Billing, charge backs, and service level agreement (SLA) Project, work, content, and search management Reduce application redundancy Applications (Rationalization) Work, content, and search management Subscription models + Software as a Service (SaaS) Software licensing cost reduction Coexistence, MOSS/WSS/PWS + Instance enumeration Infrastructure Physical coexistence (MOSS/EPM) Virtualization Outsourcing management Cost reduction – Watts * BTU * Rack Space

  10. Agenda • Concepts • Consolidation • Solution overview • System elements

  11. Line-of- business systems Solution Overview Line-of- business systems Project Managers Executives Portfolio Analysts Project Managers Application Managers Executives Resource Managers Team Members Project Server Gateway

  12. Solution OverviewThe Farm • Servers have roles • App servers have all services installed • Web front ends are always mirrors • Database is farm agnostic • Config DB: Heart of the farm • Takes place of registry - 1 per farm • Maintains server farm integrity • SPTimer Service: Heartbeat of farm (2 tier) • Shared Services • Grouped, high-value, resource-intensive services • One to many per farm • Inter-farm capable (SharePoint Server only)

  13. Solution OverviewLogical Architecture Client Database Server Application/PSI Server All servers in farm (Timer Service) Business Logic Tier Web Service Tier http://ServerName:56737/SSPName/psi/*.asmx Internal Web Services External Web Services ASMX Definition Project User Context Filter Data Access Layer Data Access Layer Business Objects Eventing Service Queuing Service Server-Side Scheduling Serializer Web Server Project Professional Authentication Project User Context Project Web Access 3rd Party Client Custom Logic Impersonation Local access to SSP Scheduling Engine Desktop Reporting Local Cache Soap Client Serializer IE Browser Level Security Zone ActiveX Controls Office Web Comp Outlook Addin http://ServerName/InstanceName/_vti_bin/psi/*.asmx User session state Project Server Draft Database(n) Shared Services Content Database PSI Forwarder Local Server Cache Farm Configuration Database Central Admin Content Database Shared Services Service Database Project Server Reporting Database(n) Project Server Published Database(n) Web Application Content Database(n) Project Server Archive Database(n) Central Admin Web App Root Site Web App ASPX Web Parts PSI Proxies Master Pages System PWA and WSS content pages SSP Web App Patch Management Remote Access Services Logs Domain Sub-System Platform Fault Tolerance • Terminal Services • VPN • Virtualization • 32/64-bit • IIS • Binaries • Data schema • Project • WSS • NT • Web • ULS • Perf Counter • Event • PSConfig • Firewall • Active Directory • DNS • Exchange • Load balancing • Clustering • Mirroring • Backup • Disaster recovery • Network • Processor • Memory • Disk

  14. Agenda • Concepts • Consolidation • Solution overview • System elements

  15. System ElementsGeneral • Exchange/SMTP • WSS and Project Setting • DNS and AD “burst activity” • AD (Reduce latency) • Host files –DNS roundtrips • Firewalls/Security • System clocks synced Services Domain • Domain accounts • Appropriate permissions • SSP: AD Sync, OLAP • Timer Service - WSS “Queue” • Use SSP account • Multi-instance shares threads Remote Access Logs • Unapproved apps • Latency/WAN users • Cache profile – load balanced • Cache share: network latency • Virtualized (CPU/memory) • CPU burn – IE users • IIS Web Logs: WebService calls • Unified Logging System (ULS) • WFE + PSI: Load balance • Event Viewer • Performance Counters • PCDiagnostic

  16. System ElementsSub System – Cost Analysis CPU Memory • 32/64-bit (Virtual/Physical) • Ratio – CPU::RAM • 32-bit - 1:2 • 64-bit – 1:4 • Application behavior • WFE, APP, SQL, and SSRS • Virtualization (Virtual:Physical) • Sockets vs. Cores (Caching) • Ratio - Front End::SQL • Application behavior E.g.: • WSS: WFE security trimming and payload • Project: PSI RDSSync • Virtualization (Virtual:Physical) Network Disk • Storage – SAN or DAS • Shared SAN? • Speed – spindles and striping • Tolerance - RAID • Virtualization • VHD vs. disk pass through • PWA - HTTP Payload (objects) • WinProj – Bandwidth (cache) • Inter-farm communication • Client latency • Virtualization (Virtual:Physical) • Ratio – Host::Guest

  17. System ElementsSub System – Disk • IO Characteristics • Reads/Writes • Index seek/creation • Backups/Checkpoints • OLAP/OLTP • Disk Topology • SAN • DAS – OS + App + Logs • Physical Topology • Bus bandwidth • Memory • Cache • Network + HBA + Log share • Storage Design • LUNs • Volume alignment, # spindles • Shared (Exchange/MOSS) • File and group isolation • Data • Log (Presize) • TempDB (Presize) - 1 file per CPU • Indexes • RAID Level • 0 – Striping • 1 - Mirroring • 5 – Striping + parity • 10 – Striping + mirroring (Best) \\External Share RAID: 1 RAID: 1 RAID: 1 RAID: 1 Logs: Web, ULS RAID: 10 RAID: 10 RAID: 10 Web and PSI Logs Data TempDB SQL Config Admin SSP Services SSP Content WSS Content (n) Project Draft (n) Project Published (n) Project Reporting (n) Project Archive (n) Config Admin SSP Services SSP Content WSS Content (n) Project Draft (n) Project Published (n) Project Reporting (n) Project Archive (n) 1 X 20Mb file::CPU C:\ OS D:\ Apps D:\Logs C:\ OS D:\ Apps D:\Logs Storage

  18. System ElementsFault Tolerance Load Balancing Clustering • Web front end • Hardware appliance • Software NLB • Application/PSI • SSP Internal Round Robin SQL Server® application level Appears as single server Automatic failover SAN storage Backup Disaster Recovery DB Snapshots SQL/Third Party SharePoint BUR Admin BUR (Enterprise Objects) SSBR Versioning and Recycle Bin Database mirroring Transaction log shipping

  19. System ElementsFault Tolerance – hardware loadbalancing Intranet Users Extranet Users Remote Users Load-balancing Methods (Required) Static: Virtual Server: ProjIntranet Virtual Server: ProjRAS Virtual Server: ProjExtranet VIP: 192.168.0.97 Dynamic: Observed VIP: 192.168.0.99 Dynamic: Observed VIP: 192.168.0.98 Dynamic: Observed Round Robin (Default): BIG-IP sends new connection to the next server in the pool. Ratio (member/node): BIG-IP distributes connections based on defined weight ratios. E.g.: 32-bit and 64-bit WFE - define a ratio for 64-bit WFE to receive more traffic. HTTP Profile: ProjExHTTP HTTP Profile: ProjInHTTP VS Type: http-wan-optimized-compression-caching Default HTTP Profile Dynamic: TCP Profile: ProjInTCP TCP Profile: ProjExTCP TCP Profile: ProjRASTCP Least Connections: BIG-IP sends new connection to server with least current connections. Can cause clumping with short bursts of connections. Fastest: BIG-IP sends new connection to server responding the fastest and allows slower servers to recover. Observed: BIG-IP uses a combination of Least Connections and Fastest. Great for short burst activity – Project Server recommendation. Predictive: BIG-IP uses observed as well as trending to identify which servers trend towards saturation – Project Server recommendation. Performance L4 tcp-lan-optimized tcp-lan-optimized tcp-lan-optimized Cookie Persistence Profile: ProjInCookie Cookie Persistence Profile: ProjExCookie RDP Persistence Profile: ProjRASCookie Timeout: 3600s Cookie Insert ‘0’ Cookie Insert ‘0’ Web Server Web Server Web Server IP Pool: ProjExWFE IP Pool: ProjInWFE IP Pool: RASServers Persistence (Optional) 192.1.1.1 192.1.1.2 192.1.1.3 192.1.1.1 192.1.1.2 192.1.1.3 192.6.25.45 192.6.25.46 192.6.25.47 Terminal Services • Source Affinity Address (SAA): Persists connection based on the source IP. If behind NAT’ing device (Proxy/TS farm), all users appear from same address and BIG-IP sends all users to the same server – clumping. • Cookie: BIG-IP persists connection based on cookie in HTTP header. Priority choice when load balancing HTTP stateless applications and WebParts - Project Server recommendation with Cookie Insert ‘0’ (expiration value). • * Note on persistence: • BIG-IP bypasses the load-balancing algorithm and sends user to the prior server connection. • If BIG-IP Health Monitor detects clumping, it overrides persistence and uses load-balancing algorithm to determine best connection. F5 Health Monitor 192.1.1.3 192.1.1.2 192.1.1.1 Alternate Access Mapping Table ** Please test optimal settings that will apply to your configuration

  20. System ElementsPlatform App Pools 32/64 -Bit Memory hungry WSS uses more kernel memory 64-bit apps on 64-bit OS WSS/MOSS data heavy SQL and reporting Performance parity Ratio – AppPool::WebApp .NET Framework loads/app pool Account access to DB resources 32-bit memory pressure (800Mb) Virtual (Hyper-V) Patch Mgmt WSV vs. VMware Host container characteristics Ratio – Guests::Host Saturation - Disk IO/Network CPU/Memory allocation Shared agility environments Hotfix:5000/Service Pack:1000 Binaries / Data Schema Upgrade against schema version WSS, MOSS, and Project Client, Active X, and SMS scripts Install/Uninstall sequence

  21. Session Summary • Deploying Project Server 2007 is an enterprise undertaking • Consider the platform elements as carefully as the application itself • Be aware of the many integration points to external applications required for business continuity

  22. Webcasts SeriesWhat to expect next • Solution Overview and System Elements • Solution Elements and Data Flow • Workload Scenarios and Reference Architecture • Network Communication • Server Administration • Maintenance and Monitoring • Deployment into a SharePoint Server Intranet Farm • Disaster Recovery • Virtualization

  23. For More Information… • Project Server TechCenter • http://technet.microsoft.com/en-us/office/projectserver • Project Developer Portal • http://msdn.microsoft.com/en-us/office/aa905469.aspx • Microsoft® Enterprise Project Management (EPM) University • www.msepmu.com • EPM Connect • www.epmconnect.com • The Microsoft® Office Enterprise Project Management (EPM) Solution • www.microsoft.com/epm

  24. Next Steps • View other EPM-related webcasts • www.microsoft.com/events/series/epm.asp • Check the latest download and content available for Project Server • http://technet.microsoft.com/en-us/office/projectserver

  25. Questions and Answers • Submit text questions using the “Ask” button. • Don’t forget to fill out the survey. • For upcoming and previously live webcasts: www.microsoft.com/webcast • Got webcast content ideas? Contact us at: http://go.microsoft.com/fwlink/?LinkId=41781

More Related