RealTime IT News

Rushing Content Through The Keyhole

Enterprise content management (ECM) vendor Interwoven has launched a Web content tool that it claims can cut provisioning time for browser-based applications by 40 percent.

The Interwoven Content Provisioning system takes application code and content from a development system, aggregates and standardizes it through the Sunnyvale, Calif., company's provisioning zone and deploys them enterprise-wide.

Company officials said the provisioning process is normally a resource-intensive process for IT staffers, taking days to update Web sites or intranet portals with new functionality or content.

"The IT operations folks for these large financial services, healthcare and telecom companies are trying to use FTP or RSYNC or Robocopy scripts to move these hundreds of moving parts from their respective development systems out in a synchronized fashion to a distributed production environment," said Todd Scallan, Interwoven director of product management.

In addition to using the development system devised by Interwoven, TeamSite, the company's provisioning software also uses connectors from competing development companies such as Microsoft's Visual SourceSafe, IBM's Rational and content developments systems like Vignette and Stellent.

The files are sent to the provisioning zone, which contains Interwoven's OpenDeploy and ControlHub products, where the file types are standardized and synchronized for deployment.

From there, it's a matter of deploying the content or code to the database, application server and Web servers. ControHub helps IT staffers roll back any changes made network-wide.

An added benefit is the audit trail the Interwoven Content Provisioning application provides, officials said. Section 404 of the Sarbanes-Oxley Act requires companies to keep documentation of all changes to company code, content and changes.

Scallan said processes performed using FTP and other scripts to make changes to enterprise servers can often break the requirements of that federal requirement.

"If you've got 1,500 servers in your production environment, you can be sure that the rollout of code, content and configurations in one package goes live in unison across those 1,500 servers," he said. "That compliance and accuracy are a key part."