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.
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.
Updating your user registry
After you deploy HCL Digital Experience, you can adjustment your federated user repository configurations. You can update these configurations to achieve the correct user registry configuration.
Updating a group member
After you create your LDAP user registry, you might find that your group member is not correct. You can update the group member in your LDAP user registry configuration.

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.
      - Enable federated security
        You can use the Configuration Wizard to configure HCL Portal to use a federated LDAP for security. Use the following information to get familiar with the information you must provide in the wizard and the configuration procedure that it generates.
      - Adding more attributes to VMM
        After you install HCL Digital Experience and configuring your LDAP user registries, you must adapt the attribute configuration to match the configured LDAP servers and your business needs. However, do not complete these steps if you configured only a database user registry or the default federated file-based repository for out-of-box installations.
      - Enabling application groups
        You can define user groups within the database user registry with members (users or groups) contained in the federated LDAP user registry you configured with application groups. The benefit of application groups is that you can create groups that are only used in HCL Digital Experience.
      - Advanced group configurations
        It is possible to use HCL Digital Experience ConfigEngine helper tasks to set up advanced Virtual Member Manager (VMM) group configurations. Specifically, it is possible to configure VMM to understand and use the "Group membership attribute" that many directories support.
      - Adding a database user registry
        Add a database user registry to the default federated repository to store user account information for authentication and authorization. You can add multiple database user registries to the default federated repository although you can add only one database user registry at a time.
      - Adding realm support
        A realm is a group of users from one or more user registries that form a coherent group within HCL Digital Experience. Realms allow flexible user management with various configuration options. A realm must be mapped to a Virtual Portal to allow the defined users to log in to the Virtual Portal. When you configure realm support, complete these steps for each base entry that exists in your LDAP and database user registry to create multiple realm support.
      - Updating your user registry
        After you deploy HCL Digital Experience, you can adjustment your federated user repository configurations. You can update these configurations to achieve the correct user registry configuration.
        Updating the context pool configuration
        After you configure your LDAP user registry, you can adjust the number of context instances that the context pool concurrently maintains to improve performance.
        Creating the entity type
        If an entity type exists within HCL Digital Experience but not within your LDAP user registry, create the entity type within your LDAP user registry. Then, add the relative distinguished name (RDN) to the entity type to map it between HCL Portal and your LDAP user registry.
        Changing from a stand-alone repository to a federated repository
        If you originally configured a stand-alone LDAP user registry but require a robust security configuration, you can change to the federated user repository.
        Restoring the VMM setup with a federated file repository
        If your business changes or your user registry configuration is inoperable, run the wp-restore-default-repository-configuration task to restore the default VMM setup with a federated file repository. Then, reconfigure your user registry. The task deletes all existing repositories, creates a realm, and configures a file repository in VMM. The task also creates a user and group, which is set to the HCL Digital Experience administrator.
        Updating an entity type
        After you add your user registry, you can update a single entity type with the value of the default parent. For example, if you delete a repository, you must update the entity type if it points to the deleted repository.
        Updating the base entry
        After you create your base entries, you can update the distinguished name (DN) in the repository that uniquely identifies the base entry name. This task applies only to federated repository configurations. This task does not update the base DN entry if you use a stand-alone repository.
        Updating the database user registry
        After you create and use the database user registry, you can update the database user ID, password, and where the data is stored. This task does not change the DN structure that is stored in the database repository.
        Updating a group member
        After you create your LDAP user registry, you might find that your group member is not correct. You can update the group member in your LDAP user registry configuration.
        Updating the federated LDAP user registry
        After you create and use the LDAP user registry in the default federated repository, you might find that your LDAP user registry is not working correctly. You can update the LDAP user registry and make the necessary changes. For example, you can change your LDAP Bind password.
        Updating the realm configuration
        After you create and use the realm in the default federated repository, you might find that your realm configuration is not working correctly. You can update the realm configurations and make the necessary changes.
        Configuring a property extension database
        A property extension database stores attributes that the LDAP directory does not or cannot store, but that you want to include in your portal user registry. This situation often occurs when you are using an LDAP directory that does not allow schema extensions for new attributes to support portal applications. When you configure a property extension database, you effectively extend the user registry to make new attributes available as part of your portal user profile. However, it is preferable to store all user attributes in the main user registry. Complete this task only if you cannot add attributes to your LDAP directory.
      - Deleting your user registry configurations
        After you deploy HCL Digital Experience, you might not require some of the LDAP entity types, realms, realm base entries, or repositories that you created. You can delete these configurations to achieve the correct user registry configuration.
    - Search
      You use Portal Search to search for text that is displayed in websites that are created by HCL Web Content Manager.
  - 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.

Updating a group member | HCL Digital Experience

After you create your LDAP user registry, you might find that your group member is not correct. You can update the group member in your LDAP user registry configuration.

Before you begin

In a stand-alone server environment, you can complete the following task when the servers are either stopped or started. In a clustered environment, start the deployment manager and node agent. Then, verify that they are able to synchronize.

Procedure

Open a command prompt.
Change to the wp_profile_root/ConfigEngine directory.

Optional: Run the following task to list the names and types of configured repositories:

AIX® HP-UX Linux™ Solarisz/OS®:

./ConfigEngine.sh wp-query-repository -DWasPassword=password

IBM® i:

ConfigEngine.sh wp-query-repository -DWasPassword=password

Windows™:

ConfigEngine.bat wp-query-repository -DWasPassword=password

Go to the wp_profile_root/ConfigEngine/properties directory.
Open the wkplc.properties file with a text editor.
Enter a value for the following parameters under the VMM LDAP group member attribute configuration heading:
Note: Go to the properties file for specific information about the parameters.
- gm.ldap.id
- gm.groupMemberName
- gm.objectClass
- gm.scope
- gm.dummyMember
Save your changes to the wkplc.properties file.

Run the following task to update the group member information for your LDAP user registry or to create the group member if it does not exist:

AIX® HP-UX Linux™ Solaris:

./ConfigEngine.sh wp-update-ldap-groupmember -DWasPassword=password

IBM® i:

ConfigEngine.sh wp-update-ldap-groupmember -DWasPassword=password

Windows™:

ConfigEngine.bat wp-update-ldap-groupmember -DWasPassword=password

z/OS®:

./ConfigEngine.sh wp-update-ldap-groupmember -DWasPassword=password

Stop and restart the appropriate servers to propagate the changes. For instructions, go to Starting and stopping servers, deployment managers, and node agents.