Background:
You can use the Personalization features of WebSphere Portal to deliver
personalized Web content to your users.
Server architecture:
A typical Web Content Management environment consists of the following
WebSphere Portal servers:
Development server:
This WebSphere Portal server is used to initially develop a Web Content
Management and to develop and test major updates to your Web site after
your initial Web site has gone live. As
only a small team of Web site developers will be responsible for developing
and updating the design of your web site, you only need to install a single
WebSphere Portal server to act as your development server.
Authoring cluster:
As many users will be authoring content at the same time, a clustered authoring
environment is deployed to spread the load across multiple servers to improve
performance.
Staging server:
This WebSphere Portal server can be used to review your Web site prior
to syndicating your latest changes to your delivery server. It can also
be used to collate changes made during the day on your authoring cluster
and syndicated those changes at a time best suited to making updates to
your delivery server, such as between midnight and dawn.
As only a small number of users will
need to access the staging server, you only need to install a single WebSphere
Portal server.
Delivery cluster:
The delivery cluster is used to render Web content using the Web content
servlet. As many users will be viewing content at the same time, a clustered
delivery environment is deployed to spread the load across multiple servers
to improve performance.
Other servers:
Database servers:
It is recommended that you store your data on a database located on a server
separate from yourWebSphere Portal servers. Each of the Web Content Management
environments listed above must have separate data repositories.
LDAP servers:
It is recommended that the same LDAP environment be used across all your
Web Content Management environments. This will ensure your user IDs are
consistent across your Web Content Management environments when you syndicate
items between environments.
HTTP servers and load balancers:
A HTTP server is used in front of your clustered servers. This is used
to redirect users to a node within the cluster. HTTP servers can also be
used as load balancers.
Deployment process:
1.
WCM
6.1-B: 1.0 Setting up the Development server
2.
WCM
6.1-B: 2.0 Setting up the Authoring cluster
3.
WCM
6.1-B: 3.0 Setting up the Staging server
4.
WCM
6.1-B: 4.0 Setting up the Delivery cluster
5.
WCM
6.1-B: 5.0 Setting up the Authoring system
6.
WCM
6.1-B: 6.0 Enabling syndication and using the system
7.
WCM
6.1-B: 7.0 Delivering content