Single-server topology for Web Content Management
Organizations that only need a small Web site or intranet site could implement a single server topology for Web Content Management. 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 Management. A Web server routes incoming requests from browser clients. Web Content Management, WebSphere Portal, and WAS 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 Management server could be clustered. Similarly the LDAP and database servers could be clustered for failover.
The following actions occur on the single server:
- Create drafts
- Approve drafts
- Test changes
- Publish changes
- Host content
Hardware and resource
- Authoring and delivering content within the same environment will be resource intensive, so the type of environment you deploy will need 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.
Parent topic:
Server topologiesRelated concepts
Single-server topology
Stand-alone server topology
Horizontal cluster topology
Vertical cluster topology
Combination of horizontal and vertical clusters
Multiple clusters
Dual-server configuration for Web Content Management
Staging-server topology for Web Content Management