1. Module 4: Design IIS Maintenance and UDDI

2. Designing Internet Information Services Backup and Recovery Specifying Monitoring requirements Deploying UDDI Services Tuning and Troubleshooting IIS 7.0

3. Lesson 1: Designing Internet Information Services Backup and Recovery IIS 7.0 modular architecture IIS configuration history Centralized configuration for web farms Maintenance and recovery Designing backup and recovery for web farms

4. IIS 7.0 modular architecture Benefits: Componentized architecture Fault tolerant Scalable Line command and programmatic access

5. IIS configuration history VersionAuthenticationConfiguration file IIS 5 All websites run in-process under Local System account. Proprietary metabase IIS 6 Handling processes run as Network Service Account. Metabase.xml and MBSchema.xml IIS 7 Application Pool, anonymous user, and UNC access use specified local or AD account. Machine.config, Applicationhost.config, and web.config all xml

6. Centralized configuration for web farms Xcopy of applicationhost.config and deployment of modules Enabling shared web.config Enable distributed web farms with DFS

7. Maintenance and recovery IIS 7.0 Configuration History of applicationhost.config Application Pool maintenance  Compatibility modes set at application pool level Development environment  Application migration  Virtualization AttributeDefault SettingDefinition enabledTrue This value indicates whether configuration history is enabled or disables path %systemdrive%\inet pub\history The path where history directories will be created and stored maxHistories10 The maximum number of directories retained by IIS7 period00:02:00 The time between each check made for changes by IIS7

8. Designing backup and recovery for web farms For Config files use offline files, client side caching, or DFS-R Do not use for content. Server Configuration and Modules backed up using Appcmd Can be scripted to provide regular backups Backup content using your existing backup tool A solution utilizing VSS will work with open files and take less processor resources.

9. Failed Request Tracing Rules PropertyExampleCapability Content*.*, *.asp, *.? Create a rule for particular content types. Status codes 404.2, 500, 404, etc Log results that include particular status codes. TimeAny number Collect responses based on the amount of response time required. Trace Providers ASP, ASP.NET, ISAPI, WWW Server

10. Evaluate need for UDDI Scenarios Increase developer productivity Run-time and dynamic application configuration Connect with external partners