Topics covered included network architecture, SQL Server configuration, .NET configuration, and Kentico CMS configuration and optimization. Network Architecture - Server configuration - Load balancing - Traffic routing - HTTP/HTTPS considerations - File replication SQL Server Configuration - Clustered SQL server architecture - Active/Passive - Database configuration/settings .NET Configuration - Session state management - Web server configuration Kentico configuration - Web farm synchronization - Best practices

2. Deploying and Configuring Kentico CMS in a Load-Balanced, Highly Available Environment Bryan Soltis – Senior Software Engineer Kentico Certified Developer Kentico Certified Trainer

5. Session Management

7. Site Deployment

10. Web.config settings

12. WebAnalytics

13. SmartSearchQuestions/Answers

14. Overview of Load Balancing / High Availability What is Load Balancing / High Availability?Load balancing is a technique to distribute workload evenly across two or more computers, network links, CPUs, hard drives, or other resources, in order to get optimal resource utilization, maximize throughput, minimize response time, and avoid overload.

15. Load Balancing Basics Load balancing a Kentico website consists of deploying the site to multiple web servers/databases to deliver the application. Load balancing appliance/software for traffic Multiple web servers Clustered SQL Servers Session Management

16. Configuring Site Traffic Configuring site traffic involves deciding how inbound traffic will directed to the multiple servers. This can be managed by hardware or software, with varying configuration options.

18. Objects held in session must be serializable. Kentico objects are by default.

19. Microsoft provides scripts to create database

21. Configuring Site Traffic NLB Free with Microsoft Windows Server Easy installation / configuration Limited customization “Simple” load balancing

22. Configuring Site Traffic HTTP / HTTPS Traffic can be secured at load balancer level. This can alleviate processing on the web farm servers because all encryption will occur at the load balancer level. Note: Typically only available with hardware load balancing.

23. Web Server Configuration Standard IIS sites. Site will have 1 external IP Each web server will contain a unique internal IP. Load balancer will route traffic to each internal IP as configured. Site is fully deployed to each server in the web farm.

27. Kentico Site Web Farm Support Each server will have its internal IP and identifier defined in the web.config file. Additional parameters can be configured to specify exact content to synchronize.

28. Kentico Site Web Farm Support Servers can be enabled/disabled directly from CMS Site Manager Site modifications are listed as tasks for each server Scheduled tasks can be configured to automate synchronizations

29. Testing the System Deploy to web farm environment Configure Kentico site for web farm support Configure site to store files on file system Update content within the site Upload files (Bizform, content, etc.) Check Synchronization tasks Confirm file modifications are replicated

31. CMSWebFarmSynchronizeBizFormFiles

32. CMSWebFarmSynchronizeDeleteFiles

33. CMSWebFarmMaxFileSize

35. CMSDebugAllWebFarm

36. CMSDebugWebFarmLive

37. CMSDebugWebFarmLogLength“Smart” load balancing Scheduled tasks No-downtime server maintenance “Sticky sessions”

38. Special Considerations Web analytics files SmartSearch index files DFS Code updates Hardware vs Software load balancing Affinity Session Management HTTPS

39. Questions /Answers

40. Start a Conversation With Uswww.BitWizards.com800.651.4948Bryan@BitWizards.comhttp://blogs.bitwizards.com/bryan_soltis