Web content system overview
The type of web content system you deploy is determined by the size of web content system, the type of website being delivered and the number of users creating and viewing web content.
Web content system types
There are three main types of web content systems:Single environment systems
- This is where authoring and delivery occur within a single environment. This type of environment would be deployed by a small organization delivering a small website, such as an intranet. Authoring and delivering content within the same environment can be 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. For example, using clustered servers is a common solution for a single instance system.
Dual environment systems
- This is where authoring and delivery are split into different environments. This model reduces the load on both authoring and delivery and also allows you to locate authoring environment behind a firewall. This type of system would be used when delivering externally facing websites, or where you have many users authoring content or many users viewing a website.
Staged systems
- This is where a staging environment is added between the authoring and delivery environments. The staging environment can be used for user acceptance testing (UAT) or to allow to accumulate changes from authoring environment before syndicating changes to delivery environment in a single batch. This system would be deployed when delivering large, complex sites with many content creators and you need to ensure that the website being delivered is accurate, error-free and can perform under load.
Environment types
Authoring environment
- An authoring environment is used to create and manage web content. This is the environment used by content creators and website designers. An authoring system can consist of:
- an authoring server or cluster.
- individual UAT servers where site and content updates can be tested before being syndicated to the delivery environment.
Staging environment
- A staging environment can consist of:
- individual holding servers where changes from authoring environment can be accumulated before syndicating changes to delivery environment in a single batch. Pairs of holding servers can be used to provide you with built-in redundancy.
- a complete replica of delivery environment where UAT can occur to both review site and content updates, and to test the performance of delivery environment.
Delivery environment
- This environment is used by website viewers. A delivery environment can consist of:
- pre-rendered sites where a web content site is pre-rendered as a set of HTML files which are then used to deliver a static website.
- a WebSphere Portal server or cluster where content is delivered using a servlet. Servlet delivery is used to deliver websites that contain dynamic content, but do not include any WebSphere Portal content or applications.
- a WebSphere Portal server or cluster where content is delivered using either a local or remote web content viewer portlet. web content viewer portlets are used to deliver websites that contain dynamic web content alongside other portlets or applications.
- A combination of all the above.
Parent
Web Content Manager topologies