We started off this chapter describing scenarios where a web content management (WCM) system should be used in a business application and where it should be avoided. WCM systems add value to organizations that have content-heavy websites that need to be updated with business-critical data at any given point of time, without the dependence on IT staff. On the other hand, organizations that require infrequent updates to their websites and do not have the capacity or the budget for training and CMS infrastructure costs should not use WCM systems.

We went ahead to discuss a sample WCM architecture using the Documentum product suite consisting of entities and tools such as Web Publisher, Content Server, Documentum Administrator, Content Rendition Services, Site Caching Services, Documentum JDBC Services, and Site Deployment Services.

Content Server, discussed in the earlier chapters, is the foundation of Documentum architecture, providing the basic content management services required for a content management system.

Web Publisher (WP) is a content authoring tool providing a rich user interface for creating and managing content for a business website.

Documentum Administrator (DA) is a web-based tool used for performing several system administration tasks in the Documentum system.

Content Rendition Services (CRS) is a tool used for generating multiple renditions/formats of documents in a Documentum Docbase.

Site Caching Services (SCS) helps in publishing documents and their associated attributes from Docbase to a pre-configured website.

Documentum JDBC Services is a Documentum tool that supports most of the standard JDBC APIs and helps applications make connections to either Docbase or SCS repository and manipulate data contained in these.

Lastly we saw that Site Deployment Services (SDS) is a Java-based application that helps in deploying business website content from an SCS Target server to directories on multiple local or remote servers.