1. Frank DiMauro Web App Specialist Information Services Division fdimauro@unch.unc.edu Case Study: Updating Plone and Replacing Apache

2. Outline Previous vs Current Setup Why Apache? Why Enfold Server over Apache? Architectural Challenges Migration Path New Products/Deprecated products Working with Enfold Conclusion Case Study: Updating Plone and Replacing Apache Metrics:  First Go-live to Plone 2.0.4 in April 2005  Site hits of 6 million/month then, currently over 17 million hits/month (July/06)  Staff assigned to maintain site: FTE = 3 ; Content managers = 60+  Domain names pointing to site = 20

3. Previous Setup Notes  Windows Server 2003 SP1  Apache 2.0.53  Plone 2.0.4, upgraded to 2.0.5  Production Server also serving 2 IIS sites

4. Current Setup Notes  Windows Server 2003 SP1  Enfold Server 2.8 includes Plone 2.1.2, and iFilter integration  Enfold Proxy 2.5.2  SQL Server 7.0

5. Current Setup: Delta Copy Notes  rsync of ZODBs running thru DeltaCopy twice/day  ZODB on HOT BACKUP serves as backup copy  Plone files on HOT BACKUP kept in synch with LIVE server  Production Server also serving 2 IIS sites

6. Specs: Updating Plone and Replacing Apache S/WPreviousCurrent Plone2.0.52.1.2 Python2.3.42.3.5 Zope2.7.42.8.3 Apache2.52n/a Windows Server 2003SP1 SQL Server77 Enfold Servern/a2.8 Enfold Proxyn/a2.5.2 Enfold Desktop1.03.0 eGenix ODBCn/a2.0.7 DeltaCopyn/a1.1.3

7. Why Apache? Original contractor developed site using Apache re-write rules Windows not ideal for complexity of site in Plone 2.0.4 Our site would not run w/o apache or linux OS Apache: Open source and relatively simple to install/administer Limited staff experience with Apache/Eclipse/WebSphere Case Study: Updating Plone and Replacing Apache

8. Why Enfold Server and NOT Apache? As site grew / needs multiplied Server maintenance and apache support less reliable. Primarily a “Windows” shop Upgrading to Plone 2.1.2 anyway Site complexity / non-Plone core plug-ins required outside expertise to migrate Enfold has solid Windows / open source expertise Case Study: Updating Plone and Replacing Apache

9. Architectural Challenges Non-core products Apache rewrites and VHM SSL enforcement Intranet portion of site restricted by IP range Customized templates in “custom” folder Code reuse not optimized Multiple domain names… www.unchealthcare.org www.unchealthcare.net unchweb.unch.unc.edu unchweb2.unch.unc.edu unchealthcare.org unchealthcare.net ncchildrenshospital.org ncchildrenshospital.net ncchildrenshospital.com uncchildrenshospital.org uncchildrenshospital.net uncchildrenshospital.com ncwomenshospital.org ncwomenshospital.org ncwomenshospital.org uncwomenshospital.org uncwomenshospital.org uncwomenshospital.org intranet.unchealthcare.org Migration: Updating Plone and Replacing Apache

10. Additional Challenges Custom workflow Some non-core products broken IP restricted Intranet access via LDAP offsite Need for redundancy / failover protection Dovetail with UNC School of Medicine CMS/Plone efforts Migration: Updating Plone and Replacing Apache

11. New Products LocalFS mxODBCDA SmartFormsSkins (Cignex) zSiteWeaver (Cignex) IPRange plug in PlonePAS (Pluggable Authentication Service) iFilter (Enfold Server) Migration: Updating Plone and Replacing Apache Notes  EES Sheduled tasks:  Log rotation  Backup  ZODB pack

12. New Products iFilter (Enfold Server) Microsoft's interface into Index server. Converts certain types of documents into plain text. Windows allows over 50 types including Microsoft Office content. Coupled with TextIndexNG, allows ES to search various types of documents uploaded to the server. Migration: Updating Plone and Replacing Apache

13. Obsolete Products CMFCTIResources (Cignex) ZODBCDA (Cignex) Migration: Updating Plone and Replacing Apache Notes  Apache turned off  Apache proxy/rewrite function assumed by Enfold Proxy  SSL assignment assumed by IIS and external method  Data.fs doubled size  ODBC connector replaced by eGenix product  iFilter plug-in repaired the indexing feature missing in CMFCTIResource product

14. Migration Path Plone migration script Run external methods Fix templates Migrate CMFCTIResource objects Cleanout missing resources Import custom workflow and update (internal published) Uninstall Epoz Install ES/EP on Backup Server rSync / DeltaCopy setup Migration: Updating Plone and Replacing Apache Notes  Install ES and EP  Install eGenix ODBC  Setup IPrange plug-in  Setup PlonePAS  Portal_squid purges domains  Unchealthcare.org  Unchealthcare.net  www.unchealthcare.net www.unchealthcare.net  www.unchealthcare.org www.unchealthcare.org  Intranet.unchealthcare.org  Custom caching configuration

15. Enfold Server Notes  Enfold Server application controller is “encontrol” screen.  Provides control over  Zeo server  Zeo Clients (set by default)  Create new clients  Create emerg user  Start/Stop service  Scheduled tasks  etc.

16. Enfold Server

23. Enfold Proxy Notes  Enfold Proxy  Full caching proxy inside IIS that talks to any Plone instance and specifically ESE.

24. Enfold Proxy

25. Working with enfold systems Pros Plone architects (Alan Runyan, Andy McKay, etc.) Small company / personalized service IIS / Windows expertise Committed to open source / legacy system integration International consulting associates (Brazil, Australia, etc.) Issue collector and online documentation SVN site subversion

26. Working with enfold systems Cons Andy McKay & Cam Cooper gone Small company User support not 24/7

27. Questions? Migration: Updating Plone and Replacing Apache