Interwoven tames unwieldy Web sites

Enterprise CMSes (content management systems) do a fine job helping business users update Web page text and rollback changes when necessary. But that’s just one facet of maintaining an engaging site. Unfortunately, few tools currently exist for overseeing changes to intricate applications such as shopping carts and Web-enabled self-help. True, most IT shops employ systems management tools such as Microsoft Application Center to deploy custom programming of this nature. These products, however, usually work with particular file types and often lack controls mandated by Sarbanes-Oxley and other legislation.

Enter Interwoven’s CPS (Content Provisioning Solution), a source- and target-agnostic solution that plays well with popular SCM (software configuration management) systems to recognize content changes made via various CMS apps. What’s more, CPS bundles these changes and deploys them at once to a wire array of Web application servers.

Sure, stuffing in features of individual provisioning tools is a feat, but what will make IT executives take notice of CPS is that it operates as a single system of record for changes. That way, you can prove that only authorized modifications get moved into production, making your infrastructure audit-ready.

Interwoven customers may recognize some of CPS’s capabilities, as they were originally part of TeamSite -- the company’s CMS -- and then Interwoven’s stand-alone OpenDeploy product. CPS 2.0 retains key OpenDeploy features, such as content encryption during data transfer using SSL, and now includes version control and workflow, courtesy of a new component called ControlHub Server.

That said, this is an IT operations solution and therefore takes time and patience to configure and use. I spent a few days assembling a test, staging, and production environment of 10 Windows servers. In fairness, part of that effort was devoted to rethinking existing processes and how they could be improved. For example, I didn’t originally have a test server in my workflow and lacked a few intermediate approval steps, which I needed to model in CPS.

Using a Web interface, I instructed OpenDeploy to recognize my content servers and built deployment projects. One usability quibble is that you must jump between the UI and a text editor to make configuration changes. These control files typically follow an XML format, so support staff shouldn’t have much difficulty with this task. It does introduce the potential for error and more testing steps, though.

With the configuration set and verified, I had no trouble scheduling jobs to run automatically, adding users from a Microsoft Active Domain, and running reports.

ControlHub, the workhorse of this solution, also comes with a significant learning curve. Considering the intended developer or IT audience, however, it shouldn’t prove too intimidating. For example, the Content area of the tabbed Web UI presents a navigation tree where I created Branches, for managing my various Web apps; Editions, for capturing versions of each change; and Workareas, for aggregating code and content.

As noted, files can come from different departments, hosts, file shares, and even databases -- an optional add-on. In my test environment, CPS easily oversaw ASP files controlled by Microsoft Visual SourceSafe, HTML pages developed through Macromedia Contribute, and XML-formatted Web content published through SilkRoad’s Eprise enterprise CMS. CPS also works with IBM Rational ClearCase and Serena Merant PVCS and recognizes content changes made in EMC Documentum, Stellent, Vignette, and, of course, Interwoven CMSes.