Single-server topology for Web Content Manager

Organizations that only need a small web site or intranet site could implement a single server topology for IBM® Web Content Manager. In a single server configuration, authoring and delivery occur on the same server. This configuration is not recommended for organizations that need a larger Web site or intranet site.

The following topology diagram illustrates a single-server configuration for Web Content Manager. A Web server routes incoming requests from browser clients. Web Content Manager, IBM WebSphere® Portal, and IBM WebSphere Application Server are installed on the same server. The LDAP server that stores authorized user information is installed on a dedicated server. The database that stores content is also installed an a dedicated server. Although this diagram does not illustrate a cluster configuration, the Web Content Manager server could be clustered. Similarly the LDAP and database servers could be clustered for failover.

Illustration of a single-server Web Content Manager configuration. Refer to the text in this topic for details on this graphic.

The following actions occur on the single server:
  • Create drafts
  • Approve drafts
  • Test changes
  • Publish changes
  • Host content

Hardware and resource considerations

  • Authoring and delivering content within the same environment is resource intensive, so the type of environment you deploy needs to be robust enough to allow authoring and delivery to occur at the same time. Using clustered servers is a common solution for a single-server configuration.
  • Content can be delivered using either a web content viewer portlet, the web content servlet or a pre-rendered site.