NIH Enterprise Architecture Home

Web Content Management Service Pattern

Description

Web Content Management Systems (WCMS) consist of applications used to create, manage, store and deploy content on the Web, including text, graphics, video or audio, an application code. Web Content Management Systems are often a component of Enterprise Content Management (ECM) solutions, and some of these features are represented in the Other ECM Services Layer. However, this pattern is focused specifically on basic web content management services.

This pattern can be viewed in the following layers:

  • Interface Layer
  • Integration Layer
  • Other ECM Services
  • The Content Management Layer
  • Storage Layer

Interface Layer

The pattern below depicts different levels of users, from passively browsing users and active contributors in a Web 2.0 framework, to the authors, content managers/administrators, and system administrators in a traditional Web publishing model. While some WCMS solutions include Web 2.0 tools that allow users to actively contribute to the site, all WCMS solutions will have content authors, managers, and administrators contributing content either through a Web interface or desktop application linked to the site. Access is typically granted to the user interface layer through the authentication layer in order to enforce the appropriate security policies. At NIH, due to the importance of collaboration with external stakeholders, support for Federated Identity and Authentication should be provided throughout the WCM solution.

Integration Layer

The Integration layer provides other applications the means to exchange data with the Web content management application document management software. It typically consists of Web Services, Application Programming Interfaces (API), or other Integration Services.

Other ECM Services

In a robust ECM implementation, some of these ECM services might be coupled with the WCMS application to form a large, often costly, ECM suite. Some of the other components of an ECM suite include Enterprise Search, Workflow or Business Process Management tools, Document Management, Digital Asset Management, and Collaboration Tools.

Content Management Layer

The Content Management layer contains the core components for the Web Content Management Application. The authorization component grants the appropriate privileges to users, based on their respective roles. Library Services provide the core content management functionality (check-in/out, version control), along with Publish, Staging, Logging, and Content Reporting/Auditing. Basic Workflow, embedded in most WCM solutions, provides for basic routing of content jobs. The Web Interface and Portal Application present the content to the various user segments, based on their authorization. Remote portlets (e.g., webparts, gadgets, widgets) can be used to embed content management functionality or sourced content in portals provided by other vendors. The search indexing engine can create searchable indexes from websites supported by WCMS solutions. Websites may also be independently indexed by NIH enterprise search engines.

Storage Layer

The storage layer provides a repository for these assets: Web Content, Content Archive, Metadata, Collaboration data, ECM content, and the Search Index.

Please view the Web Content Management Service Pattern below:

Diagram

Benefits

  • This pattern illustrates levels of functionality, any or all of which may be necessary for a project.
  • This pattern standardizes conversation between mission and technical teams regarding components and complexity.
  • This pattern can be applied to many business scenarios depending on scale and functional requirements.

Limitations

  • This pattern does not illustrate true complexity of security integration in NIH’s federated environment.
  • This pattern does not alleviate the need for requirements and policy analysis (e.g. taxonomies, usability metadata, security and appropriate usage guidelines).
  • This pattern does not address the specific workflow, task profiles, or content creation that are necessary for any website project.

Time Table

This architecture definition approved on: February 12, 2008

The next review is scheduled in: TBD