Home
HCL Digital Experience 9.5 [Legacy content]
Administering
Use the administration tools that are provided with the HCL Digital Experience to do various day-to-day administration tasks.
WSRP services
By using the Web Services for Remote Portlets (WSRP) standard. HCL Digital Experience can provide portlets, applications, and content as WSRP services.
Using your portal as a WSRP Consumer
Learn about the tasks that you perform when you use your portal as a WSRP Consumer portal to consume remote portlets. You can consume portlets from a HCL Digital Experience or from a different WSRP Producer such as the IBM WSRP Version 2.0 Producer for IBM WebSphere Application Server.
Customizing the WSRP configuration of your Consumer portal
You can customize some aspects of you WSRP Consumer portal.
Customizing the WSRP resource proxy
The WSRP resource proxy is used by the WSRP Consumer to load resources that are referenced by remote portlets.
Customizing the WSRP resource proxy for LTPA token forwarding
The WSRP resource proxy can forward single sign-on cookies (LTPA, LTPA2) from the client requests to resources in the same single sign-on domain.

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.
  - Roadmap: Syndication
    Syndication is the tool that is used to replicate data from a web content library on one server to a web content library on another server. The relationship between a syndicator and a subscriber can be either a one-way or two-way relationship.
  - Portal administration tools
    Learn about the different tools that you can use to administer your portal.
  - Web content administration tools
    HCL Web Content Manager includes tasks and tools to help maintain your content management system. For example, use the member fixer task to resolve renamed or deleted users and user groups. Use the workflow checker and updater tools to modify workflow security settings, reschedule pending actions, and add workflow to items. Web Content Manager also includes tools to assist with library and item management, and item and version history management.
  - Starting and stopping servers
    Various installation and configuration tasks require you to start and stop IBM WebSphere Application Server and the HCL Digital Experience application servers, deployment managers, and node agents.
  - Users and groups
    HCL Digital Experience offers you centralized administration of users and user groups, allowing you to better define users and manage user access rights. Users can register and manage their own account information, or an administrator can provision and manage users. Group memberships can be used to give the required permissions to access an object or perform a request.
  - Managing portlets, portlet applications, and iWidgets
    You must do some preparatory tasks before you make your portlets, portlet applications, or iWidgets available to your users by putting them on portal pages. This preparatory task includes installing, deploying, and configuring portlets, applications, and iWidgets.
  - Administering managed pages
    You can run advanced administration tasks for managed pages, such as generating URLs for projects or working with projects by using scripts, or working with vanity URLs.
  - Manage pages portlets
    Use Manage Pages to create, edit, activate, order, and delete pages and external web pages and labels.
  - Managing theme capabilities
    You can administer the theme module framework. This includes deploying resources that can be cached, configuring capability filters, and disabling the automatic prerequisite loading feature.
  - Managing community pages
    Community associations associate a portal page with a community in HCL Connections.
  - Managing your cluster
    After installing and configuring your clustered environment, you will need to manage the different parts of your cluster to ensure a highly available production environment.
  - Managing your site
    Earlier versions of HCL Digital Experience provided the Resource Manager portlet for performing site management. With Version 8.0 of HCL Portal and HCL Web Content Manager, this site management functionality has been replaced by the new functionality for managing pages.
  - Tagging and rating
    Get an overview of the administrative tasks related to tagging and rating.
  - Using WebDAV with HCL Portal
    HCL Digital Experience provides a Web-based Distributed Authoring and Versioning (WebDAV) implementation that individual services can use by plugging into. WebDAV is a set of extensions to the HTTP protocol that allows you to collaborate on editing and managing files on remote Web servers.
  - Virtual portals
    View information on how you can scope your HCL Portal to have multiple virtual portals.
  - Language support
    To reach as many users as possible, HCL Digital Experience supports different languages for different locations. For instance, a large, international corporation might address users in different countries or regions through multilingual Web sites. In this context the portal can concurrently serve portal views to large numbers of users, each in the user's preferred language.
  - WSRP services
    By using the Web Services for Remote Portlets (WSRP) standard. HCL Digital Experience can provide portlets, applications, and content as WSRP services.
    - What is new in WSRP
      WSRP in HCL Portal 8.5 is now based on the JAX-WS standard for Java based web services. It takes advantage of the improvements of the current JAX-WS based web services stack that is part of IBM WebSphere Application Server. The WSRP services are implemented as JAX-WS compliant service providers and service clients. To configure web service security and quality of service, you can manage them in the WebSphere Integrated Solutions Console by using policy sets.
    - Learning about WSRP
      Web Services for Remote Portlets (WSRP) allows easy integration of remote portlets, applications, and content into portal.
    - Planning for WSRP
      Before you work with WSRP, plan your configuration based on the information in the following topics.
    - Using your portal as a WSRP Producer
      Learn about the tasks that you perform when you use your portal to provide WSRP services as a WSRP Producer portal.
    - Using your portal as a WSRP Consumer
      Learn about the tasks that you perform when you use your portal as a WSRP Consumer portal to consume remote portlets. You can consume portlets from a HCL Digital Experience or from a different WSRP Producer such as the IBM WSRP Version 2.0 Producer for IBM WebSphere Application Server.
      - Information that the Consumer exchanges with the Producer
        Before a Consumer can consume portlets from a Producer, the Consumer needs specific information about the Producer. Depending on your configuration, you might also need to provide information about your Consumer portal to the Producer.
      - Working with Producer definitions
        To make a WSRP Producer known to your Consumer portal, you create a Producer definition for that WSRP Producer in your Consumer portal. You can also configure the Producer definition.
      - Consuming portlets in a Consumer portal
        After you create a Producer definition, you can proceed to consume the portlets that are provided by that Producer. This way, you integrate them into your Consumer portal as remote portlets.
      - Customizing the WSRP configuration of your Consumer portal
        You can customize some aspects of you WSRP Consumer portal.
        Customizing the WSRP resource proxy
        The WSRP resource proxy is used by the WSRP Consumer to load resources that are referenced by remote portlets.
        Customizing the WSRP resource proxy SSL settings
        The WSRP resource proxy uses one SSL configuration for all secure outbound connections.
        Customizing the WSRP resource proxy for LTPA token forwarding
        The WSRP resource proxy can forward single sign-on cookies (LTPA, LTPA2) from the client requests to resources in the same single sign-on domain.
        Customizing the WSRP resource proxy for proxy server support
        The WSRP resource proxy supports HTTP proxy servers. It can connect directly to remote resources or to a proxy server that forwards the requests to remote resources.
        Disabling support for relative URLs for the WSRP resource proxy
        By default, the WSRP resource proxy serves resources relative to the current resource proxy URI. You can disable the support for relative URLs.
        Customizing the WSRP resource proxy for basic authentication
        You can customize the WSRP resource proxy for HTTP basic authentication.
        Customizing the WSRP resource proxy HTTP header forwarding behavior
        By default, the WSRP resource proxy forwards all HTTP headers from the client request except for the host header and cookie headers. You can define further headers that you do not want to be forwarded.
        Configure timeout properties for the WSRP communication
        You can configure web service timeout properties for the WSRP communication on the Consumer. You can configure the timeout properties in the WP Configuration Service or as a preference specifically for remote portlets.
        Configure a limit for the size of file uploads
        You can configure a limit for the size of file uploads during an action request. You can also configure the Consumer behavior if a file upload exceeds the defined limit.
        Switch off the caching of Producer service descriptions
        By default, the Consumer portal caches the WSRP service descriptions that it receives from Producers. If required, you can switch off the caching.
        Customizing Client Cookie Forwarding
        A client can send cookies to the WSRP Consumer as part of an HTTP request. You can customize the WSRP Consumer to forward specific client cookies to the Producer ports or to other resources that are served by the WSRP Consumer as a proxy.
        Configuring remote session invalidation
        You can configure the WSRP Consumer to invalidate the remote session when a user explicitly logs out of the Consumer portal. If you enable remote session invalidation and a user logs out of the Consumer portal, the Consumer sends a releaseSessions WSRP request to all the Producers with which the user interacted. The Producers portals can then invalidate these sessions.
    - Using handlers for WSRP web services
      You can extend your WSRP Producer or WSRP Consumer portal by handlers that comply with JAX-WS.
    - Reference for using WSRP with the portal
      Reference information about using WSRP with the portal includes WSRP markup caching and Known limitations.
  - Browser behavior and scenarios
    Browser behavior for the back button, bookmarks and history affect user interaction and cause unexpected results.
- 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.

Customizing the WSRP resource proxy for LTPA token forwarding | HCL Digital Experience

The WSRP resource proxy can forward single sign-on cookies (LTPA, LTPA2) from the client requests to resources in the same single sign-on domain.

About this task

You can influence the LTPA token forwarding behavior. To do so, proceed as follows:

Procedure

Set the following property in the HTTP Client Service: wsrp.resourceproxy.sso.domain = Single sign-on domain.
Use this property to specify the single sign-on domain. If the WSRP resource proxy loads a resource from a host inside this domain and the client request contains LTPA or LTPA2 cookies, these cookies are forwarded to the remote resource.
Restart the portal or the cluster for the new setting to become active.