Microsoft Office Project Server 2007: Network Communication

1. Microsoft Office Project Server 2007: Network Communication Michael Jordan Lead Architect (EPM Global Practice) Microsoft Corporation michjor@microsoft.com

2. Webcasts 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 TechNet and MSDN® • 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 • Review the logical solution • Cover network communication in the farm • Review ActiveCache mechanism • Cover network considerations when deploying Server and Client

5. Agenda • Solution Review • Network Communications • Network Considerations - Project Server • Network Considerations - Project Professional

6. Agenda • Solution Review • Network Communications • Network Considerations - Project Server • Network Considerations - Project Professional

7. Solution OverviewLogical Architecture Client Database Server Application/PSI Server All servers in farm (Timer Service) Business Logic Tier Web Service Tier http://SvrName/InstanceName/_vti_bin/psi/*.asmx http://ServerName:56737/SSPName/psi/*.asmx Internal Web Services ASMX Definition External Web Services Data Access Layer Project User Context Business Objects Filter Data Access Layer 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 Central Admin Content Database Farm Configuration Database Project Server Draft Database(n) PSI Forwarder Local Server Cache Shared Services Content Database Shared Services Service Database Project Server Reporting Database(n) Project Server Published Database(n) Project Server Archive Database(n) Web Application Content 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 Services Patch Management Remote Access Logs Domain Fault Tolerance Sub-System Platform • Project • WSS • NT • Web • ULS • Perf Counter • Event • PSConfig • Binaries • Data Schema • Firewall • Active Directory • DNS • Exchange • Network • Processor • Memory • Disk • Loadbalancing • Clustering • Mirroring • Backup • Disaster Recovery • Virtualization • 32/64 Bit • IIS • Terminal Services • VPN

8. Agenda • Solution Review • Network Communications • Network Considerations - Project Server • Network Considerations - Project Professional

9. Network CommunicationPorts, protocols, and network traffic WAN LAN VPN VPN HTTP: 80 OWC: 2393 CA: Installed port SSP: Installed port HTTP: 80 HTTPS: 443 HTTP: 80 OWC: 2393 Terminal Services: 3389 Backup Restricted Mgmt Un-Restricted Mgmt Log Share Trusted Cross Domain Controller Central Admin Server Web Server Terminal Server App Server HTTP Pump Analysis Services Inter-Farm Timer Service CA: Installed port SSP: Installed port Web Services: 56737 SQL: 1434 HTTP: 80 HTTPS: 443 SQL: 1434 Intranet Isolate network traffic Loadbalancer Extranet Domain Controller Exchange Server VPN: 22 TS: 3389 Intranet VS RAS VS Extranet VS SSP:Installed port Web Services: 56737 AD Sync: 389 OLAP: 2393 SQL: 1434 SMTP: 25 DNS Server OLAP: 2393 SQL: 1434 Terminal Service Users Internal Users Corp Net Users Corp Net Users WINS Server VPN: 22 HTTP: 80 OWC: 2393 HTTP:80 HTTPS: 443 OLAP: 2393 Default Instance:1434 Named Instance: Custom SQL Server Alleviate AD latency and DNS Pressure Internet Farm Administrator LDAP: 389 LDAP GC: 3268 Naming: 53 LDAP: 389 Naming: 137 SMTP: 25 HTTPS: 443 (OWC): 443

10. Network CommunicationPorts, protocols, and network traffic

11. Agenda • Solution Review • Network Communications • Network Considerations - Project Server • Network Considerations - Project Professional

12. Network ConsiderationsProject Server • Isolate network traffic for 2-tier and 3-tier traffic • Web Front End calls to Database • Web Front End calls to Application Server (PSI) • Application Server (PSI) calls to database (Web Front End Requests) • Application Server (PSI) calls to database (Queue Service Jobs) • Backup and server management network • Sync operations – • Active Directory® • Online analytical processing (OLAP) Cube Build • Windows® SharePoint® Service (WSS) workspaces - permission changes (global, group) • Firewall for Data Analysis Views – Configure HTTP Pump www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx • Create sites in their own Web applications (CA, SSP, PWA) with unique port numbers

13. Agenda • Solution Review • Network Communications • Network Considerations - Project Server • Network Considerations - Project Professional

14. Network ConsiderationsProject Professional - ActiveCache • Project Server 2007 is “cache heavy”: • Project Professional • Published Database (projects) • Reporting Database (projects, timesheets, WSS data and metadata) • Draft database (metadata) • These caches speed performance but must be kept coherent • Data locality • Delta transfers • Data transformations

15. Network ConsiderationsProject Professional - ActiveCache • Local Cache • Local Project Cache is on the computer with Project Professional 2007 • “Cache Size Limit” limits the amount of hard disk space used up by the Project Local Cache • If size of cached projects exceed this limit, unable to open or save • Cache Folder - Each folder name is titled by the following naming convention: • <Project Server Account GUID>.<Project Server Account>.<user name>. • For example, the Local Project Cache for Eva Corets: {CB23031D-19CD-4FFC-B6D2-0A2843A20173}.2007 PWA. Eva Corets.evac • A Project Server user can log on using multiple login names • Eva Corets Windows-authenticated login (for example, contoso\evac). - {43C6A643-08AF-466E-81EE-646FF8095A9F}.Eva Corets2007 PWA.evac • Eva Corets as EGlobal Admin to edit the Enterprise Global Template file - {A9D93E0E-CE18-4662-A877-CD70AF4420C0}.Eva Corets.Server2007 PWA.EGlobal Admin • Cache Subfolders. • Cache.dat – Internal file • <GUID>.hash – Internal file • global<Internal Numbering>.mpc – Enterprise Global cache file • <Project Name><Internal Numbering>.mpc –Project Cache file • ** None of these files should be externally modified, moved, copied, or deleted. Tampering with these cache files may result in data loss or undefined behavior in Project Professional 2007

16. Network ConsiderationsProject Professional - ActiveCache SOAP - HTTP 1a 2b 3b Project Professional (1a) User opens a project for the first time. (1b) Project is cached. (2a) User opens the project for the second time; project is opened from cache. (2b) Project changes (if any) are downloaded from the server. (3a) User saves the project; project is saved to the cache. User gets control back with minimal delay (3b) Project Professional saves the cached project to the server. 1b 2b 3a Active Cache

17. Network ConsiderationsProject Professional • Monitor file size and cache limit size • Virtual memory management • Master/Sub projects • Monitor corporate network latency on intranet and extranet to determine performance impacts to Project Professional (full versus delta open/save) • Terminal Services (TS) • Avoid roaming profiles • Avoid load balanced access to TS farm • Set user to dedicated TS server for local cache and rev counter fidelity • Avoid network share to user cache • Introduces network latency and performance issues

18. Session Summary • Deploying Project Server 2007 is an enterprise undertaking • Consider all the external dependencies such as ports, protocols, applications, etc. when designing and implementing a Project Server deployment

19. 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

20. 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 • EPM University • www.msepmu.com • EPM Connect • www.epmconnect.com • The Microsoft® Office Enterprise Project Management (EPM) Solution • www.microsoft.com/epm

21. 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

22. 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