Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ektron 3-Tier Architecture


Published on

Learn how Ektron supports a true 3 Tier Architecture to provide increased scalability, security, and availability.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Ektron 3-Tier Architecture

  1. 1. The 3-Tier Architecture
  2. 2. Bill Cava• Chief Evangelist, Ektron••
  3. 3. AGENDA & OVERVIEW• What’s New in 8.5: 3-Tier Architecture• Benefits Scalability, Performance, Security, Availabilit y• Ektron in a 3-Tier Architecture – Installation & Configuration – Developer Experience • Framework API: New API in v8.5 • Framework UI: Templated .NET Server Controls – Implementing your Service Layer• Demo!
  4. 4. what is the 3-tier architecture and are its benefits…THE WHAT’S & WHY’S
  5. 5. 1Tier 2Tier 3Tier nTier
  6. 6. 1-TIER ARCHITECTURE • Mainframes • Single Machine • Dumb Terminal access • Pro – Simple • Con – Expensive – Tightly coupled
  7. 7. 2-TIER ARCHITECTURE • Client – UI, Resources Aqcuisition, Business Rules • Server – Data storage, shared function • Pros – Shared resources • Cons – Managing connections, Ineffeci ent utilization
  8. 8. 3-TIER ARCHITECTURE• Presentation Tier – Front End – Display Tier• Middle Tier – Application Server• Data Tier – Storage Server
  9. 9. BENEFITS OF THIS ARCHITECTURE• Security• Scalability• Performance• Availability
  10. 10. SECURITY• Publically accessible Presentation-Tier has no direct access to Data-Tier• Business Logic contained w/in Middle-Tier isolated• Structure of database hidden from Presentation-Tier
  11. 11. SCALABILITY• Each tier independently scales horizontally• Scale Presentation- Tier to handle connections• Free database to handle database transactions
  12. 12. PERFORMANCE• Cache requests between FE & MT – Serve data from memory – Minimize network utilization – Reduce MT and DT load• Load Balancing possible at each tier
  13. 13. AVAILABILITY• Redundancy of presentation-Tier and Middle-Tier servers for failover• Caching between FE & MT means system continues to serve content if Middle-Tier unavailable
  14. 14. what ektron looks like in a 3-tier architectureEKTRON & 3-TIER
  15. 15. EKTRON STILL SUPPORT 2-TIER!• You can upgrade from < 8.5 to 8.5 – This is supported and will continue to work – Upgraded site will be 2-Tier – Upgrading to 8.5 does NOT make your site “3-Tier”• You can develop a new site on v8.5 using 2- Tier – Standard approach for building a website• You can develop a new site on v8.5 using 3- Tier
  16. 16. VERSIONS PRIOR TO 8.5
  17. 17. VERSIONS PRIOR TO 8.5
  18. 18. VERSIONS PRIOR TO 8.5
  19. 19. VERSION 8.5
  20. 20. VERSION 8.5
  22. 22. MIDDLE-TIER FOOTPRINTFull Ektron Installation on Middle-Tier:• Ektron DLLs• Ektron Workarea• Ektron Windows Services• Ektron WCF Services• Custom WCF Services
  23. 23. PRESENTATION-TIER FOOTPRINTMinimal Footprint on Front-End• Standard ASP.NET Web site• Minimal set of Ektron.DLLs in ~/bin• Configuration files (web.config, unity.config)• Workarea not required
  24. 24. DEVELOPER EXPERIENCEDeveloper Experience on Front-End• Use Framework API & databind• Use Templated Server Controls• No difference in developer experience between the 2-Tier and 3-tier architectures • Same exact code syntax
  25. 25. UNITY – DEPENDENCY INJECTION Unity Application Block – Dependency injection framework; Part of MS Enterprise Library • Dynamically register dependencies at runtime • Introduction to Unity us/library/dd203319.aspx • Single unity.config on Front-End servers
  26. 26. DEREK SLIDE
  27. 27. COMMUNICATION FE-MT: WCFWindows Communication Foundation is• Used to communitcate between the Presentation- Tier and the Middle-Tier.• Implemented as a Unity container
  28. 28. CACHING LAYERThe Caching Layer• Caches all data retrieved from the middle-tier in memory on the servers in the presentation-tier• Caching is implemented as another Unity container• Is configured within the Unity config
  29. 29. getting things up & running in a 3-tier environment …INSTALLATION &CONFIGURATION
  30. 30. BASIC INSTALLATIONMiddle Tier & Data Tier• Perform full Ektron installation on the Middle- Tier / Data tier server using CMS400Basev85.exe (no difference) – Note: In 8.5 RC installation should be performed on the website root – As part of the installation, the 3TierMin site will be installed to: C:Program Files (x86)EktronCMS400v85startersites3TierMinContent
  31. 31. INSTALLATIONPresentation-Tier1. From Middle-Tier, copy folder C:Program Files (x86)EktronCMS400v85startersites3TierMinCo ntent to your web directory on the Presentation Tier server – This folder contains elements for a minimal-footprint front-end site, containing subset of DLLs from Middle-Tier to Presentation-Tier server • Which DLLs you need depends on which features you use • This documentation describes which DLLs are required • Note: not an issue to “just grab them all” -- even though you wont need them all -- and pair it down later2. Open IIS on Presentation Tier server and make this folder a Web Site
  32. 32. INSTALLATION (CONT’D)3. Update web.config & point to Middle-Tier <appSettings> <add key="ek_ServicesPath" value="http://[MT]/workarea/services/"/> </appSettings>
  33. 33. INSTALLATION (CONT’D)4. Browse to http://[FE]/default.aspx – You should be able to log into your front-end using any account defined within Ektron (Admin/Admin, etc).5. Deploy your own templates and code to the Presentation-Tier That’s it! … now let’s walk through the code footprint on the Front-End
  34. 34. development options in a 3-tier environmentDEVELOPING 3-TIER
  35. 35. TWO APPROACHES TO DEVELOPING IN 3-TIER1. Use Framework APIs and/or Templated Server Controls directly on the Presentation-Tier Server – Pros: Simpler (previous installation, ready to go) – Cons: Chattiness of API calls over wire2. Designing your own Service Layer on the Middle- Tier, consuming those services on the Presentation- Tier Server – Pros: • Designing a Service Oriented Architecture (SOA) • Leveraging Middle-Tier for its strength – Con: A little more complex to set up
  36. 36. APPROACH #2: DEVELOPING USING APIS• On the Front-End, use the APIs directly
  37. 37. FREQUENTLY ASKED QUESTIONSWhat about … – legacy APIs? – legacy Server Controls? – PageBuilder? – Widgets? – eSync? • data? code? • documents, images, etc.?
  38. 38. Questions?Bill Cava• Chief Evangelist, Ektron••