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.
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.
Preparing the site toolbar
The site toolbar enables content authors to work with content from the website instead of using the authoring portlet. Customize the site toolbars to improve the authoring experience for content authors.
Configuring the behavior of toolbar tabs
You can use the following page parameters to configure the main properties of your toolbar tabs.

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.
    - Adding content: Site Toolbar or Site Manager
      When adding content to a site in edit mode, a content author has the choice of using either the Site Toolbar or Site Manager. Site developers need to consider which option is best for their content authors.
    - Generate author-ready templates
      You can generate author-ready templates in Web Content Manager to provide content authors a set of predefined content templates that can be selected from the toolbar and used to add content to a page.
    - Page components
      Create page components by using Web Content Manager to provide content authors a set of predefined page components that can be selected from the toolbar and added to a page.
    - Enabling and disabling segments in the Add Segments view
      You can customize the Add Segments view so that you see only segments, only managed segments, or both segments and managed segments.
    - Preparing the site toolbar
      The site toolbar enables content authors to work with content from the website instead of using the authoring portlet. Customize the site toolbars to improve the authoring experience for content authors.
      - Configuring the behavior of toolbar tabs
        You can use the following page parameters to configure the main properties of your toolbar tabs.
      - Configuring display options in the primary and secondary toolbar frames
        When you open the site toolbar, Site Manager automatically opens in the primary toolbar frame. You can control what displays in the primary and secondary toolbar frames by setting page parameters on the hidden page Toolbar Content Root.
      - Disabling the toolbar logo
        You can disable the toolbar logo for the entire portal that includes all the virtual portals or for a specific virtual portal.
      - Implementing portlets for the site toolbar
        The toolbar tabs of the Portal 8.5 site toolbar are represented as portal pages. The content of the toolbar tabs can be implemented by using portlets.
      - Customizing the More menu of the action bar
        The More menu is a public extension point that you can use to plug in your own menu actions that you want to make available in the action bar.
      - Customizing the Page Component palette
        The Page Component palette, which is accessed from the site toolbar, contains the content items a content author can add to a page. This was known as the Content palette prior to CF08.
      - Customizing the Applications palette
        HCL Portal includes ready to use portlets that you can browse through in the site toolbar. To ease browsing through this set of portlets, HCL Portal supports assigning portlets to one or more categories. As the site administrator, you can create, delete, and modify categories and assign portlets to them.
      - Customizing page creation and page editing options
        When content authors edit a page, they can choose layouts and styles. As an administrator, you can customize these page editing options. If you are on Combined Cumulative Fix 8 or later, you can also customize page creation for your content authors.
      - Customizing toolbar layouts
        The toolbar layouts can be customized by adding theme metadata to the theme deployment file.
      - Customizing site manager User Interface
        The site manager user interface can be customized by adding additional functionality.
      - Controlling the visibility of the site toolbar and toolbar tabs
        You can control the visibility of the site toolbar and single toolbar tabs per virtual portal by using Portal Access Control.
      - Removing the site toolbar on a production server
        The site toolbar provides access to editing features for managed pages, including adding and editing pages and web content. Although essential for an authoring server, it is recommended that you disable the site toolbar on a delivery server. You can disable the toolbar for an entire portal or for specific virtual portals.
      - Delete pages and their contents
        When you delete a page (or tree of pages) while using Site Manager, the page, its child pages or child content are also deleted. But, the content that is referred by WCM rendering portlets on the page is not deleted. Beginning with CF205, a new feature is added that allows you to delete the page as well as the content that is referenced by the WCM rendering portlets on the page. The new delete feature comes disabled by default, and you can enable the same by setting the following in the WP ConfigService Resources Environment Provider:
      - Disabling the language switcher
        The language switcher allows you to switch from any of the supported languages. This feature is available only for authenticated portal users.
    - Creating custom icons for the Page Components palette and Web content authoring interface
      You can assign a custom image to an item type in the Page Components palette and Web content authoring interface. You can either use a single image or a collection of images that are bundled into a ZIP file, called multi-scale icons. Supported image file formats are PNG, JPG, and SVG. If you are using multi-scale icons, the collection of images must be compressed into a ZIP file. No other format is supported. You can add custom images by either adding a file element directly into the content, or by creating a reference to a file component.
    - Customizing Site Manager
      You can configure Site Manager by setting portlet preferences for the Site Manager portlet in Manage Portlets.
    - Creating project templates
      Projects help content authors group and manage changes across the website. As a site administrator, you can create templates for your authors to use.
    - Customizing the Web Content Authoring portlet
      To customize each Web Content Authoring portlet for the people who use that portlet, you can edit the shared settings of each Web Content Authoring portlet on your authoring system.
  - 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.
  - 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.

Configuring the behavior of toolbar tabs | HCL Digital Experience

You can use the following page parameters to configure the main properties of your toolbar tabs.

The page parameters can either be set through the Manage Pages admin portlet or by using the XML configuration interface. If you want to use the Manage Pages admin portlet, you need to go to the respective toolbar page first. Toolbar pages are listed as children pages to the hidden page Toolbar Content Root. To set the parameters, select the Edit Page Properties icon, expand the Advanced options, and select the I want to set parameters link. Close and reopen the toolbar to implement and view your changes.

ibm.portal.toolbar.reloadOnResize = true | false

This page parameter indicates whether you want your toolbar tab to be reloaded automatically if a resize event occurs in your browser window. Depending on how your content is rendered, it might be useful to set this parameter to true. Defaults are set to false.

If you are using the XML configuration interface, you can set the parameter as follows:

<parameter name=“ibm.portal.toolbar.reloadOnResize“ type=“string“ update=“set“>true</parameter>

com.ibm.portal.Hidden = true | false

This page parameter shows or hides the toolbar page in the toolbar navigation. If you want to hide the toolbar page, you need to set the value to true. Defaults are set to false.

If you are using the XML configuration interface, you can set the parameter as follows:

<parameter name=“com.ibm.portal.Hidden“ type=“string“ update=“set“>true</parameter>

ibm.portal.toolbar.target = "primary" | "secondary"

This page parameter specifies the target toolbar frame that your toolbar page should be displayed in. By default, toolbar pages are displayed in the secondary toolbar frame that overlays the main page. The Site Manager is displayed in the primary frame. This setting might be set for only the first-level toolbar pages, which are direct children of the toolbar content root.

If you are using the XML configuration interface, you can set the parameter as follows:

<parameter name=“ibm.portal.toolbar.target“ type=“string“ update=“set“>primary</parameter>

ibm.portal.toolbar.disableStateSynchronization = true | false

The special setting that disables the context synchronization feature for a toolbar tab. If this feature is unavailable, your toolbar page is not reloaded in case of context or navigational state changes in the view frame. Typically, toolbar pages depend on the context, for example on the page that is displayed in the view frame. If your toolbar page displays content that is independent of the current context, you can set the value of this parameter to true to prevent the reloading in case of context changes. Defaults are set to false, which means that the context synchronization feature is enabled.

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.disableStateSynchronization“ type=“string“ update=“set“>true</parameter>

ibm.portal.toolbar.width = value

The page parameters specify the width of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 300px or 80%. Relative values are relative to the markup container, the toolbar tab is displayed in. For example, if you set the width to 100%, your tab content spans the entire width between the Site Manager and the opposite end of your browser window.

You can set the width parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.width = 100%
ibm.portal.toolbar.minWidth = 360px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.width“ type=“string“ update=“set“>30%</parameter>

ibm.portal.toolbar.minWidth = value

The page parameters specify the width of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 300px or 80%. Relative values are relative to the markup container, the toolbar tab is displayed in. For example, if you set the width to 100%, your tab content spans the entire width between the Site Manager and the opposite end of your browser window.

You can set the width parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.width = 100%
ibm.portal.toolbar.minWidth = 360px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.minWidth“ type=“string“ update=“set“>320px</parameter>

ibm.portal.toolbar.maxWidth = value

The page parameters specify the width of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 300px or 80%. Relative values are relative to the markup container, the toolbar tab is displayed in. For example, if you set the width to 100%, your tab content spans the entire width between the Site Manager and the opposite end of your browser window.

You can set the width parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.width = 100%
ibm.portal.toolbar.minWidth = 360px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.maxWidth“ type=“string“ update=“set“>1024px</parameter>

ibm.portal.toolbar.height = value

The page parameters specify the height of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 800px or 100%. Relative values are relative to the markup container that the toolbar tab is displayed in. For example, if you set the height to 100%, your tab content spans the entire height between the Action bar and the end of your browser window.

You can set the height parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.height = 50%
ibm.portal.toolbar.minHeight = 300px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.height“ type=“string“ update=“set“>80%</parameter>

ibm.portal.toolbar.minHeight = value

The page parameters specify the height of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 800px or 100%. Relative values are relative to the markup container that the toolbar tab is displayed in. For example, if you set the height to 100%, your tab content spans the entire height between the Action bar and the end of your browser window.

You can set the height parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.height = 50%
ibm.portal.toolbar.minHeight = 300px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.minHeight“ type=“string“ update=“set“>320px</parameter>

ibm.portal.toolbar.maxHeight = value

The page parameters specify the height of your toolbar tab. The value of these parameters can either be a floating point number, for example 0.5, or a pixel or percentage value in CSS syntax, for example 800px or 100%. Relative values are relative to the markup container that the toolbar tab is displayed in. For example, if you set the height to 100%, your tab content spans the entire height between the Action bar and the end of your browser window.

You can set the height parameters only for toolbar tabs that are displayed in the secondary frame container. The parameters are optional. If you do not set them, the following default values are applied:

ibm.portal.toolbar.height = 50%
ibm.portal.toolbar.minHeight = 300px

If you are using the XML configuration interface, you can set these parameters as follows:

<parameter name=“ibm.portal.toolbar.maxHeight“ type=“string“ update=“set“>800px</parameter>

Note:

If you do not set the height parameter, but only the minHeight and maxHeight parameters, the toolbar framework resizes the outer toolbar frame to match the height of the rendered content if it is greater than the specified minimum height and less than the specified maximum height.

If the values of the configuration parameters ibm.portal.toolbar.minHeight and ibm.portal.toolbar.maxHeight are equivalent, the toolbar framework enforces this height, regardless of the size of the tab content that is being loaded.