Home
HCL Digital Experience 9.5 [Legacy content]
Monitoring
HCL Portal includes tools and features to help you monitor the portal site.
Portlet load monitoring for HCL Portal
HCL Digital Experience now provides Portlet load monitoring. This can make your portal safer and more responsive.
Configuring and administering Portlet load monitoring
Here is an overview of the configuration and administration tasks and parameters for Portlet load monitoring.

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.
- 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.
  - Portlet load monitoring for HCL Portal
    HCL Digital Experience now provides Portlet load monitoring. This can make your portal safer and more responsive.
    - Configuring and administering Portlet load monitoring
      Here is an overview of the configuration and administration tasks and parameters for Portlet load monitoring.
    - Portlet load monitoring properties
      By setting the portal and portlet configuration parameters, you can monitor the session load and configure the parameters to increase performance.
    - Administering Portlet load monitoring
      You can administer Portlet load monitoring and the portlets that it monitors. You can determine whether and in which cases Portlet load monitoring blocks or reenables a portlet by setting its portlet preferences. You can also check which portlets Portlet load monitoring monitors, and you can manually block or activate these portlets. For example, you can reenable a portlet after Portlet load monitoring has blocked it.
    - Logging and auditing events
      Portlet load monitoring allows you to log events. For example, this can help you audit events. When Portlet load monitoring blocks or enables a portlet, it creates a log file entry in the HCL Digital Experience log file SystemOut.log. This log file entry contains the portlet object ID, the portlet name, the WAR file name of the portlet and the EAR file display name. The log file entries consist of translated messages. If you use tools that monitor log files for events, you can check for log file entries that are related to Portlet load monitoring as described here.
    - API for accessing Portlet load monitoring data
      Portlet load monitoring provides an API for accessing the monitoring data. You can use this API to write custom code to access that data.
  - Analyzing portal usage data
    You can collect data about the usage of your portal and analyze them.
  - Auditing
    HCL Digital Experience includes an auditing function that allows users to log certain events and their originators in to a separate log file. This file can then be used to track administrative activities.
- 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 and administering Portlet load monitoring | HCL Digital Experience

Here is an overview of the configuration and administration tasks and parameters for Portlet load monitoring.

Portal wide configuration

You can do the following configuration tasks for Portlet load monitoring:

Enabling or disabling Portlet load monitoring in your portal.
Setting the sample number of requests by which the average response time for portlets is calculated. For example, if you set the sample number to 50, the average response time is calculated from the latest 50 requests that this portlet served. This setting is related to the average response time setting listed under administrative tasks.

Perform both of these tasks in the WebSphere® Integrated Solutions Console. These settings apply to all portlets that Portlet load monitoring monitors.

Portlet preferences configuration and administration

You can set the following parameters for individual portlets in the portlet preferences. You can either configure these parameters in the portlet.xml file before you deploy the portlet or administer them later by using the Manage Portlets administration portlet:

Maximum number of concurrent requests that are allowed for a portlet
Reactivation limit of concurrent requests that are allowed for reactivating the portlet
Allowed average response time. You can configure the sample number of requests by which this average response time for portlets is calculated as mentioned previously under configuration tasks.

Portlet load monitoring administration

You can also do the following administrative tasks on individual portlets by using the Manage Portlets portlet only:

Check whether a portlet is being monitored by Portlet load monitoring
Manually reenable a portlet that Portlet load monitoring has blocked
Manually block a portlet that is being monitored by Portlet load monitoring from responding to requests.