Home
HCL Digital Experience 9.5 [Legacy content]
Setting up a website
Setting up a website includes, creating pages, adding navigation, setting up search, and adding content to the site. Themes are used to customize the portal's look-and-feel. Out-of-the-box templates and the site wizard can help you set up your portal site faster. You can add wikis and blogs to your site and let users tag and rate content on your site.
Delivering web content
The type of delivery method you use to deliver web content to your viewers depend on the type of content that is being delivered, and the type of viewers your website is intended for.
Pre-rendered delivery
You can pre-render a complete HCL Web Content Manager site into HTML and save it to disk. The pre-rendered site can then be used as your live site and displayed to users that use either Web Content Manager or a web server. You deploy a pre-rendered site when you are not using any HCL Portal features and your content is static and is only updated periodically.
Pre-render methods
Pre-rendering can be configured to run automatically, or you can manually pre-render a website by using a URL.

HCL Digital Experience 9.5 [Legacy content]
- Overview
  HCL Digital Experience provides a single access point to web content and applications, while it delivers differentiated, personalized experiences for each user across multiple touchpoints, such as web, mobile, hybrid mobile/web applications, and more.
- Supported migration paths
  Migration is supported between equivalent HCL Digital Experience offerings.
- Supported installation and upgrade paths
  Installation and upgrade is supported between equivalent HCL Digital Experience offerings.
- Getting the software
  New and existing users need to register at the HCL Software License Portal and download their entitled HCL Digital Experience package(s).
- Creating your website
  Review the following topics to understand how to create your website using the latest HCL Digital Experience.
- Installing HCL Digital Experience
  Review the planning information on HCL Digital Experience, then select your operating system and installation pattern that most reflects your business needs.
- Configuring
  Run the following tasks after you install and deploy HCL Digital Experience. They address tasks that are typically run one time and have a global effect. Some configuration changes are made more frequently or do not have a global effect. These tasks are addressed in the Administering section.
- Backup and restore
  Backup and recovery of data files and databases is an essential operation for any business system, particularly for data and applications that run in production environments. Create and follow a plan for backing up and recovering data on all tiers of your HCL Digital Experience deployment. IBM Installation Manager must also be included in backup and recovery planning. If you back up the HCL Portal file structure and then install a fix pack, your HCL Digital Experience and IBM Installation Manager become out of sync after you restore the HCL Portal file system. This condition is not recoverable.
- Migrating
  Successful migration requires significant planning and preparation, understanding the tools that are involved, and careful execution of the appropriate steps in the order provided.
- Integrating
  Integrate HCL Digital Experience with software such as HCL Sametime to enable your users to collaborate more easily. You can also use the unified task list portlet to integrate HCL with your backend business process software, such as IBM Process Server.
- Administering
  Use the administration tools that are provided with the HCL Digital Experience to do various day-to-day administration tasks.
- Securing
  Security tasks include setting up property extension databases and custom user repositories, configuring and activating SSL, and configuring authentication. In addition, tasks such as activating Federal Information Processing Standards (FIPS) and NIST SP800-131a security modules and configuring external security managers such as Security Access Manager might be required to secure your portal environment.
- Monitoring
  HCL Portal includes tools and features to help you monitor the portal site.
- Setting up a website
  Setting up a website includes, creating pages, adding navigation, setting up search, and adding content to the site. Themes are used to customize the portal's look-and-feel. Out-of-the-box templates and the site wizard can help you set up your portal site faster. You can add wikis and blogs to your site and let users tag and rate content on your site.
  - Website building blocks
    Unless you are familiar with the HCL Digital Experience and HCL Web Content Manager website model, review the building blocks. Building blocks are the different parts that make up the website framework, such as pages, navigation, themes, content, content libraries, and more.
  - Creating reusable assets
    Use reusable assets to store or generate content that is used in more than one place in your website.
  - Building the website
    Building a website includes creating libraries, pages, and web content. You also create links and navigation to your content, and assign access to different types of users, such as editors and viewers.
  - Authoring tools
    There are multiple ways to create and manage content including using the site toolbar, inline editing, and the authoring portlet.
  - Preparing for content authors
    Before content authors can create content you must prepare your site to be ready for content creation, including preparing the site toolbar, enabling inline editing, and creating templates.
  - Developing and managing content
    Use these tools and processes to develop and manage your website.
  - Delivering web content
    The type of delivery method you use to deliver web content to your viewers depend on the type of content that is being delivered, and the type of viewers your website is intended for.
    - Delivering web content on a portal page
      Using tools like Web Content Viewer Portlets, content associations, and web content page templates, you can build portal pages and display web content. You can also combine web content with other portlet-based content. Content associations tie viewers and portal pages to the site structure of your web content libraries.
    - Access web content by using a servlet
      Users can access content that is displayed by using the Web Content Manager servlet by connecting to a URL. A servlet delivered website is used when you don't need to use any HCL Portal based features such as authoring tools.
    - Pre-rendered delivery
      You can pre-render a complete HCL Web Content Manager site into HTML and save it to disk. The pre-rendered site can then be used as your live site and displayed to users that use either Web Content Manager or a web server. You deploy a pre-rendered site when you are not using any HCL Portal features and your content is static and is only updated periodically.
      - Pre-render methods
        Pre-rendering can be configured to run automatically, or you can manually pre-render a website by using a URL.
      - How to access the pre-rendered site
        Pre-rendered sites are accessed either through HCL Web Content Manager, or through a web server.
    - Rendering modes for web content
      Different presentation templates are created to render web content in different modes to display content in different contexts, such as a web content viewer portlet, or mobile devices.
  - Vanity URLs
    You can associate vanity URLs with portal pages and labels. Vanity URLs are short URLs that people can easily remember. They are shorter than full HCL Portal URLs. They are sometimes also called marketing URLs. You can publish vanity URLs for marketing campaigns through different channels, such as email or print. This way, you can use vanity URLs to direct customers to a specific portal page or content item. Interested site visitors who want to view your campaign can then remember or copy the short vanity URL and type it into the browser address field.
  - Social rendering
    HCL Digital Experience page editors can use social rendering to feature social data that is hosted on a remote HCL Connections server in the context of portal pages.
  - Setting up marketing campaigns
    Use these tools and features to setup marketing campaigns for your website.
  - HCL Web Content Manager Multilingual Solution
    The HCL Web Content Manager Multilingual Solution is a set of tools that are used to manage translated versions of localized and regionalized websites.
  - Syndicated Feed Portlet
    The Syndicated Feed Portlet for HCL Digital Experience offers enhanced feed subscription and presentation capabilities.
- Staging to production
  During portal solution development, the solution is initially developed, tested, and refined on one server or a limited number of servers. The solution is deployed later on live systems, referred to as the production environment. The process of moving the solution from the development environment to the production environment is called staging.
- Developing
  This section includes developer documentation on extending applications and development assets for HCL Portal and HCL Web Content Manager.
- Docker and Containerization
  Find topic information about Docker and Containerization for HCL Digital Experience.
- Practitioner Studio
  Practitioner Studio is a newly designed user experience for HCL Digital Experience. Please see the following pages to understand how the new navigation is organized.
- HCL Experience API
  This shows developers how to provision, configure, and use the HCL Experience API with the HCL Digital Experience 9.5 platform.
- HCL Content Composer
  The HCL Content Composer delivers simplified processes for creating and managing Digital Experience site content.
- HCL Digital Asset Management
  HCL Digital Asset Management (DAM) adds a central platform to store and include rich media assets in Digital Experience site content to present engaging, consistently branded experiences across digital channels.
- The Woodburn Studio demo site
  The Woodburn Studio is a website that demonstrates the use of some of the popular HCL Digital Experience features.
- Reference
  View information that can help you use our product documentation including terms of use, trademarks, and more.

Pre-render methods | HCL Digital Experience

Pre-rendering can be configured to run automatically, or you can manually pre-render a website by using a URL.

Administrator access: To pre-render a website, you must have administrator access to the library that contains the site area.

Automatically pre-rendering a website

Pre-rendering can be run according to the cacher settings specified for the WCM WCMConfigService service as part of the pre-rendering configuration.

Manually pre-rendering a website

Pre-rendering can also be initiated through the URL interface. For example:

http://host_name:port_number/wps/wcm/connect?MOD=Cacher&SRV=cacheSite&sitearea=sitearea_name&library=library_name

Table 1. CacherModule options
Service	Required Parameters	Optional Parameters
`SRV=cacheSite` Initializes pre-rendering for the site area with a delay as given (in seconds).	`sitearea=`site area name	DELAY=<delay> LIBRARY=<library> Note: If no library is specified, the default library is used, as specified by the `defaultLibrary` property in the `WCM WCMConfigService` service.
`SRV=flushSiteCache` Clears (flushes) the site cache. Deletes all pre-rendered data.	`sitearea=`site area name	LIBRARY=<library> Note: If no library is specified, the default library is used, as specified by the `defaultLibrary` property in the `WCM WCMConfigService` service.
`SRV=flushPageCache` Flushes the page from the site cache. The site area and page are determined from the request URL.
`No SRV specified` The CacherModule attempts to retrieve the page from the cache.

Pre-rendering individual content items

You can also pre-render individual content items by using the following URL:

http://host_name:port_number/wps/wcm/connect/library_name/site_area_name/content?MOD=Cacher

Note:

To pre-render individual content items, the site area that is specified in the URL must either be a site area set in connect.moduleconfig.cacher.task.siteareas in the WCM WCMConfigService service, or you must have previously manually pre-rendered the site area using "SRV=cacheSite" so that the site area already exists in the location you pre-render to.