On Upgrading Ektron, Or Why It’s A Headache Out Of The Box
Recently, we did an upgrade to an Ektron project from 8.6.1 to 9.1 SP1, as well as converting the search system from MS Search to Solr. It’s set up as a pretty default Ektron deal…the project was built in the web site project that comes in the site setup (CMS400Min), the database didn’t have any custom tables inside it, etc. But after we ran the upgrade, we ran into performance issues, even though we’d heavily cached the application.
On another project that’s 8.7 SP2, we’ve been asked to evaluate the project for an eventual upgrade to 9.1 SP1 (or whatever the latest is at that point). Again, built off CMS400Min (as well as eIntranet, if you remember that chestnut), but they have a lot of custom tables in the Ektron database. And the project’s a mess of files.
After both of these, I was banging my head into the wall (sometimes not figuratively). How could this be so difficult? There’s a function built into the site setup to do this, after all! So I became inspired to write this. Consider this a setup best practice guide to help make your upgrades easier, I hope.