Roadmap: Web content servers
A web content server is ideal to create presentation templates, content components, and other presentation elements of your website. In this roadmap, the web server, database, and user registry software are distributed to different physical servers.
Who should use this roadmap
- An organization that needs an environment to create and test your web content before they publish to other staging or production servers
- An organization that needs to create presentation templates (Authoring or Presentation) for content authors and content rendering
- An organization that needs to create the site structure and entitlements
- An organization that needs to develop content with HTML, CSS, JavaScript, JSP, or Java.
- An organization needs a staging server to perform final quality tests before publishing.
- An organization needs a server to publish content to end users.
Topology diagram
The topology for a web content server includes a remote database and LDAP server. The topology depicts an HCL Web Content Manager server, instead of a portal server. When you install HCL Digital Experience, it includes Web Content Manager. The configuration steps for the web content development server are different from a basic stand-alone server. The web content server configuration includes syndication with the rendering or test server.

Preparing for the installation process
Gather information and software before you install HCL Digital Experience.
Procedure
Installing prerequisites
Before you install HCL Portal, install any prerequisites that are necessary for your environment. You can use existing prerequisite software installations. Verify that your existing version is supported. If it does not, upgrade to the appropriate version.
Procedure
Installing the Exceptional Digital Experience
Installing HCL Digital Experience involves preparing your operating system, installing or upgrading the installation manager, and running the installation program.
About this task
Documentation resource: Installing HCL Digital Experience software
Applying the latest cumulative fix
Portal maintenance is delivered through two mechanisms: individual fixes (iFixes) and combined cumulative fixes. iFixes are provided, when necessary, for severe or security-related bugs. Combined cumulative fixes are delivered on a regular schedule. They provide a mechanism to deliver fixes faster, improve existing features, deliver new features, update documentation, and provide new documentation on a frequent basis. To deliver continuous improvements for your digital experience software, it is recommended that you apply the latest Combined Cumulative Fix to your environment.
About this task
Documentation resource: Roadmap: Applying maintenance
Transferring your database
After you install your web experience, Apache Server is your available database. Depending on your requirements, you might need to transfer to a different database. The Database Transfer configuration option in the Configuration Wizard assigns users and permissions, creates databases, obtains support for database collation, and transfers your database.
Before you begin
http://hostname.example.com:10039/wps/portal,
where hostname.example.com is the fully qualified host name of the server where
Portal is running and 10039 is the default transport port that is created by WebSphere® Application Server. The port number might be different
for your environment.
Procedure
Enabling federated security
After you install your web experience, a default file-based repository is your available user registry. Depending on your requirements, you might need to enable a federated LDAP user registry.
About this task
- Documentation resource: Updating user ID and passwords
Procedure
Tuning the servers in your environment
Tuning the servers is important to the performance of your portal environment. HCL Digital Experience is not tuned for a production environment after installation and deployment. Your database needs tuning for improved performance. You can organize your database now or soon after you finish your configuration. You need to tune and maintain your database on a regular basis.
Procedure
- Documentation resource: Portal server performance tuning tool
Configuring the Authoring portlet
Configure your Authoring portlet on your HCL Portal server.
Procedure
Syndication
Use syndication to synchronize content between authoring, staging, and publishing environments.
Procedure
Deploying the delivery environment
The delivery environment is used to deliver your website to your website viewers. The delivery environment is deployed based on the requirements that are defined in the project design document.
Procedure
Results
Going live with your website
When your environments are installed, the authoring system is completed, your default content is created, and fully tested the system, you are ready to go live.