Home
HCL Digital Experience Product Documentation
Welcome to the product documentation for HCL Digital Experience. Find information about how to install, configure, maintain, and use HCL Web Content Manager and HCL Portal Server, Enable, and Extend solutions.
HCL Digital Experience 9.0
Learn how to install, configure, troubleshoot, maintain, and use Version 9.0 of HCL Web Content Manager and HCL Portal Server, Enable, and Extend.
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.
Search
You use Portal Search to search for text that is displayed in websites that are created by HCL Web Content Manager.
Crawling web content with search seedlists
Portal Search supports the use of seedlists to make crawling websites and their metadata more efficient and to provide content owners fine-grained control over how content and metadata are crawled. You can configure the portal to use seedlist support when crawling content generated with HCL Web Content Manager.
The search seedlist 1.0 format
Portal Search is configured to support the HCL Web Content Manager search seedlist 1.0 format by default.

HCL Digital Experience Product Documentation
Welcome to the product documentation for HCL Digital Experience. Find information about how to install, configure, maintain, and use HCL Web Content Manager and HCL Portal Server, Enable, and Extend solutions.
- HCL Digital Experience 9.5
- HCL Digital Experience 9.5 [Legacy Content]
- HCL Digital Experience 9.0
  Learn how to install, configure, troubleshoot, maintain, and use Version 9.0 of HCL Web Content Manager and HCL Portal Server, Enable, and Extend.
  - Overview
    HCL Digital Experience provides a single access point to web content and applications, while it delivers differentiated, personalized experiences per user.
  - Supported migration paths
    Migration is supported between equivalent offerings. Starting with CF17, additional migration options are supported for HCL Portal server and HCL Web Content Manager offerings.
  - Getting the software
    New and existing users need to sign up or register at HCL Software and download their HCL Digital Experience package.
  - Installing
    HCL Digital Experience provides flexible deployment options that range from proof-of-concept where you can examine and test functionality to a highly available and scalable production environment. Review the planning information to learn more about hardware and software requirements, high availability, scalability, supported topologies, and much more. Select your operating system and then select the installation pattern that most reflects your business needs.
  - Migrating to WebSphere Application Server V9.0
    If you are installing HCL Digital Experience Version 9.0, migrate your IBM WebSphere Application Server to Version 9.0.
  - 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.
    - Configuration Wizard
      Use the Configuration Wizard to set up stand-alone servers and new deployments, create clusters, migrate and update to new versions, and add new capabilities to existing deployments.
    - Setting up a stand-alone server
      Use the Configuration Wizard to set up a stand-alone server. A stand-alone server is useful for different environments, such as a content authoring environment, test environment, and more.
    - Setting up a cluster
      Use the Configuration Wizard to set up either a dynamic or static horizontal cluster.
    - Tune your environment
      Tuning the servers is important to the performance of your environment. By default, HCL Digital Experience is not tuned for a production environment. Therefore, to ensure optimal performance review and complete the steps in the HCL Digital Experience Tuning Guide. If a tuning guide is not available for the current release, use the tuning guide from the previous product version.
    - Web servers
      HCL Digital Experience uses the internal HTTP transport within IBM WebSphere Application Server to handle requests. However, because WebSphere Application Server also supports the use of an external web server, you can access HCL Portal from your web server. You can use a local web server on the same server as HCL Portal or you can use a remote web server on a different server. A remote web server is typical for a production environment or other high-traffic configuration and is also typically placed in DMZ outside a firewall to protect portal ports.
    - HCL Portal
      First, finish your HCL Digital Experience deployment with the Configuration Wizard. Then, you can configure your environment further. For example, you can tune your servers to improve performance. You can change the default context root.
    - Database Management Systems
      Configure the connection between HCL Digital Experience and your database management system. The Database Transfer configuration option in the Configuration Wizard assigns users and permissions, creates databases, obtains support for database collation, and transfers your database.
    - User registry
      User information is stored in your user registry. You can enable LDAP referrals, configure HCL Digital Experience to use dynamic groups, update your user registry, or delete your user registry configurations.
    - Search
      You use Portal Search to search for text that is displayed in websites that are created by HCL Web Content Manager.
      - Searching pages
        By selecting a search type in Manage Pages, you can quickly locate and work with pages, labels, or URLs.
      - Searching for tagged content
        Users can search the tag space by using the browser search box.
      - Planning and preparing for Portal Search
        Learn about some planning considerations and first steps that you need to apply before working with Portal Search.
      - Indexing web content
        To search for web content, your content must first be indexed by the HCL Portal search engine. When the content is indexed, you can run searches by using the search center or by using a search component. If you search for documents in the HCL Portal search center, be aware that you see search results for published documents only. Unpublished pending changes in a project are not included in the results.
      - Configuring Web Content Manager search options
        You can edit the following search options to manage how the search service works with Web Content Manager search forms
      - Configuring Search Center to search for web content
        You can use the Search Center to search for web content by adding a web content search collection to the Search Center.
      - Language and region support in Portal Search
        Depending on your portal environment and your users, you might want to make multilingual content available and searchable in your portal.
      - Crawling web content with search seedlists
        Portal Search supports the use of seedlists to make crawling websites and their metadata more efficient and to provide content owners fine-grained control over how content and metadata are crawled. You can configure the portal to use seedlist support when crawling content generated with HCL Web Content Manager.
        The search seedlist 1.0 format
        Portal Search is configured to support the HCL Web Content Manager search seedlist 1.0 format by default.
        Enabling support for search seedlist 1.0
        If you want to use Portal Search to crawl your web content and use features like web content pages, you must enable seedlist 1.0 support for the Portal Search crawler.
        Customizing metadata field search support
        With the search seedlist 1.0 support, custom metadata fields that are specified on content items are added to the search seedlist as metadata information, without requiring the metadata to appear in the HTML source for the content items.
        Seedlist 1.0 REST service API
        The HCL Web Content Manager API for retrieving application content through a seedlist is based on the REST architecture style. To obtain seedlist content, third-party crawlers or administrator applications need to construct and send only HTTP requests to the application servlet.
      - Searching your local portal
        View information on setting up your local portal for your users to search.
      - Configuring your portal site for search by internet search engines
        You can enable your portal site for search by using search services such as Google or Yahoo! Search on your portal site by external search services works for public portal pages only, that is, for pages that users can access without a user ID and password.
      - Enabling anonymous users to search public pages of your portal
        You can enable anonymous users (sometimes also called unauthenticated users) to search public pages of your portal by using the portal Search Center portlet. Search by anonymous users works only on public pages of your portal, as the users are not logged in to your portal.
      - Configuring your custom portal themes to include the search box
        Enable your portal users to use the Portal Search box and Search portlet in your own custom theme.
      - Redirecting search requests from a custom search form to the Search Center
        If you plan to develop a custom search form, you might want to redirect search requests issued by the search form to the Search Center.
      - Remote search service
        You can configure the search portlets for local operation, or you can configure them for remote search service. Depending on your configuration, remote search service might have performance benefits by offloading and balancing system load.
      - Configuring search in a cluster
        HCL Digital Experience provides two distinct search capabilities. You can use both types of search capabilities in a clustered environment.
      - Configuring search in a portal farm
        HCL Digital Experience provides two distinct search capabilities. You can use both types of search capabilities in a portal farm environment.
      - Configuring search collections for a virtual portal
        Configuring JCR search collections for a virtual portal might require additional administration, depending on how you set up the virtual portal.
  - Reference
    View information that can help you use, including directory conventions, terms of use, trademarks, a glossary, and more.
- HCL Digital Experience 8.5
  Learn how to install, configure, troubleshoot, maintain, and use Version 8.5 of HCL Web Content Manager and HCL Portal Server, Enable, and Extend.

The search seedlist 1.0 format

Portal Search is configured to support the HCL Web Content Manager search seedlist 1.0 format by default.

About this task

Search seedlist 1.0 provides several features:

You can use the web content page type to render content that is found in the search results on the corresponding web content page.
You can include custom metadata fields from a web content item that appear in the search seedlist but not in the HTML source.
You can search within a specific library or site area, across all web content libraries, or across a list of libraries.
You can run incremental crawling of libraries for faster seedlist processing. With incremental crawling, when a crawl requests new items, only items that have been added, changed, or deleted since the previous crawl are retrieved.

Important: The syntax of the seedlist URL has changed with seedlist format 1.0. Older search collections that are created by using seedlist format 0.9 cannot be reused or migrated to the new format. Be sure that you index all your content again after you update the Web Content Manager seedlist format from 0.9 to 1.0.

Software note: As of fix pack 43 for Web Content Manager, search seedlist 1.0 uses a cache to improve the time that is required to process large content libraries. To ensure that the cache is available, you must install fix pack 10 or later for HCL Portal.

Search seedlist 1.0 can make access control information available in a way that makes pre-filtering of contents possible. Pre-filtering provides the fastest filtering approach because it takes place in the search index level. Another advantage of pre-filtering is that remote secured content sources can be searched from the portal. The filtering mode is defined as part of the search service configuration parameters.

Restriction: The seedlist must only be used for search. For example, do not use the seedlist as an alternative logging method. For the purposes of event logging, the Java messaging service (JMS) is used.