Skip to content

Planning to install HCL Digital Experience

Before you install HCL Digital Experience in a production environment, assess your hardware and software requirements, possible database configurations, security options, and LDAP server options.

Restriction

The serverName parameter is hardcoded in the HCL Portal. The serverName parameter cannot be changed in a stand-alone environment. If you change the name, the ConfigEngine scripts do not work. For a clustered environment, see Roadmaps for clusters for more information.

  • System requirements
    Before you install HCL Digital Experience, you must review the system requirements to ensure that you have the supported versions of prerequisite and co-requisite software and hardware.
  • HCL Digital Experience Support Statement
    This support statement proposes a revision to the definition of "supported" and "unsupported" regarding the various products on which HCL Digital Experience depends for correct operation.
  • User IDs and passwords
    Understanding character limitations for user IDs and passwords is important because they are used throughout the system to provide access and secure content.
  • HCL Web Content Manager environments
    Reviewing the Web Content Manager environments helps you understand what happens in each environment and how you might set up your physical servers.
  • Database considerations
    HCL Digital Experience includes an Apache Derby database that is configured and ready for immediate use. However, for a production environment or any environment for HCL Web Content Manager, you must use another supported database management system.
  • User registry considerations
    A user registry or repository authenticates users and retrieves information about users and groups for security-related functions, including authorization.
  • High availability
    The HCL Portal Express offering is licensed for use in a single-server configuration and cannot be used in either a cloned configuration or a clustered configuration except when implementing idle standby for the purpose of failover.
  • Cluster considerations
    Multiple portal servers can be clustered with IBM WebSphere Application Server Network Deployment.
  • Virtual environment overview
    Use virtualized environments to meet your business needs like production server consolidation, centralized management, or dynamic test environments.
  • Multiple profile support
    Multiple profiles give you the ability to have multiple, independently configured portal instances that run from the same installation.
Related information