Home
HCL Digital Experience 9.5 [Legacy content]
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.
HCL Connections
HCL Connections portlets give the HCL Digital Experience users access to more collaboration and social networking features such as activities, blogs, and bookmarks.
Configure HCL Portal to work with HCL Connections
Integrate the power of HCL Connections with HCL Portal application.
Configuring the Ajax proxy to allow FileNet requests
Configure the Ajax proxy so that direct requests that the CCM portlet makes to the FileNet server are allowed to pass through the proxy server.

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.
  - 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
    HCL Digital Experience is not tuned for a production environment by default. Complete the steps in the Performance Tuning Guide to optimize performance.
  - 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.
  - HCL Web Content Manager
    Set up a content server by installing HCL Web Content Manager in various deployments to provide robust and flexible environments for web content development and delivery. After you install the content server, more configuration steps must be completed according to the role that the server plays in your web content environment.
  - Syndication
    Use syndication to replicate web content library data from one server to another server. Syndication is based on a syndicator and subscriber relationship. The syndicator has the current data. The subscriber received the current data from the syndicator.
  - 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 Digital Experience Portal Search to search for text that is displayed in websites that are created by HCL Web Content Manager and additional web sources integrated to your Digital Experience platform.
  - Document Conversion Services
    Document Conversion Services are used when you work with HCL Web Content Manager authoring, previewing, and search.
  - Setting up a remote spell checker
    Using a local spell checker is not supported. You cannot run spell checker on 64-bit systems. Instead, you must install and configure spell checker on a remote application server and access that server from the local HCL Portal server.
  - HCL Connections
    HCL Connections portlets give the HCL Digital Experience users access to more collaboration and social networking features such as activities, blogs, and bookmarks.
    - Configuring Portal to work with HCL Connections
      For HCL Portal to work with HCL Connections you must configure the portal Ajax proxy, and set up single sign-on.
    - Configure HCL Portal to work with HCL Connections
      Integrate the power of HCL Connections with HCL Portal application.
      - Configure HCL Connections on-premise
        Bring the power of HCL Connections to your portal applications.
      - Configure HCL Connections on Cloud
        Bring the power of HCL Connections to your portal applications.
      - Configuring common Directory Services for your security configuration
        Configure the common Directory Services to work with your security configuration.
      - Configuring the Ajax proxy to allow FileNet requests
        Configure the Ajax proxy so that direct requests that the CCM portlet makes to the FileNet server are allowed to pass through the proxy server.
      - Testing the Ajax proxy configuration
        Test the configuration of the application-specific Ajax proxy to manage authentication for the HCL Connections portlets.
      - Optional and recommended configuration
        Depending on your deployment, follow these steps to optimize the HCL Connections portlets.
      - Addressing HCL Connections content from a portlet
        Use custom URIs to identify, access, and display HCL Connections in a portlet.
    - Import SSL certificate to set up trust association
      To prevent security alert pop-up windows, add HCL Connections certificates to your portal server. The signer certificate that is used by the HCL Connections server must be trusted by the portal server. The instructions for deploying the HCL Connections portlets include a procedure to import the SSL certificate. If you did not complete that procedure, you must import the certificate to use community pages. For best results, follow the procedures that are provided in the HCL Connections documentation.
    - Configuring HCL Connections features
      Configure the features that site visitors need to use from your portal site.
    - Configuring community pages
      Configure how you want community pages access to work in your portal site. For example you can configure community pages to automatically grant access to the page, how many child pages affected by community associations, and more.
    - Configuring Portal to work with HCL Connections in SmartCloud for Social Business
      The HCL Connections integration assets that are used to integrate HCL Portal with on-premise HCL Connections can be used to integrate HCL Portal with HCL Connections in SmartCloud for Social Business as well.
  - Reference: Configuration properties
    For your convenience, the properties files that are used to configure HCL Digital Experience are included in the product documentation. Information that is specified in the properties files is used to configure databases, LDAP integration, security, including external security managers, and more.
- 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.
- 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 Ajax proxy to allow FileNet requests | HCL Digital Experience

Configure the Ajax proxy so that direct requests that the CCM portlet makes to the FileNet server are allowed to pass through the proxy server.

About this task

The CCM portlet makes direct requests to the FileNet server, which might be embedded with HCL Connections or deployed to a separate server. You must configure the Ajax proxy so that requests can pass through the Ajax proxy.

Note: If you installed the embedded option when you installed HCL Connections, you do not need to do these steps.

Procedure

Determine the HTTP and HTTPS URLs for the FileNet server.
1. Find the URLs configured for HCL Connections by looking in LotusConnections-config.xml at:
  - For a clustered deployment: /AppServer/profiles/dmgr_profile/config/cells/cell_name/LotusConnections-config
  - For a stand-alone deployment: /AppServer/profiles/app_server_profile/config/cells/cell_name/LotusConnections-config
2. Locate the <sloc:serviceReference> entry with the value serviceName="ecm_files". The entry looks like:
```
<sloc:serviceReference bootstrapHost="" bootstrapPort="" clusterName="" enabled="true" serviceName="ecm_files" ssl_enabled="true">
        <sloc:href>
            <sloc:hrefPathPrefix>/dm</sloc:hrefPathPrefix>
            <sloc:static href="https://support.hcltechsw.com/csm" ssl_href="https://xxx.rtp.raleigh.ibm.com"/>
            <sloc:interService href="https://xxx.rtp.raleigh.ibm.com"/>
        </sloc:href>
    </sloc:serviceReference>
```
3. Take note of the href and the ssl_href attributes to use to run the command in step 3.
Open a command line and change to the following directory:
- AIX: wp_profile_root/ConfigEngine
- Linux: wp_profile_root/ConfigEngine
- Solaris: wp_profile_root/ConfigEngine
- Windows: wp_profile_root\ConfigEngine

Run this command to configure the Ajax proxy to handle all requests to FileNet:

ConfigEngine action-config-ajax-proxy-SNPortlets-filenet -DICfilenetURL=ssl_href_attribute -DICfilenetURLunsecured=href_attribute

-DWasPassword=password

Run the following command if you want to remove the Ajax proxy configuration for FileNet:
```
ConfigEngine action-remove-ajax-proxy-SNPortlets-filenet -DWasPassword=password
```