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 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.
Developing
This section includes developer documentation on extending applications and development assets for HCL Portal and HCL Web Content Manager.
Developing themes and skins
You can create themes using modules to contribute to separate areas of pages to provide flexibility, enhance the user experience, and maximize performance. To optimize themes on your website, use the theme optimization module framework. The framework separates feature-specific logic and capabilities from the theme code.
Customizing the theme
The module framework allows themes to be customized in order to provide flexibility, enhance the user experience, and maximize performance.
Expression language beans for accessing programming models
Expression language (EL) beans are available for accessing WebSphere Programming models. These beans are accessed through the PortalBean represented in the global namespace by wp. The beans provide access to HCL Digital Experience models and associated classes.
wp.moduleList
The module list bean accesses modules that are part of the modularized theme architecture. You can query individual modules and their attributes and identify of the currently used modules within the scope of the currently selected and rendered page and theme.
CurrentModuleList
The current module list always represents the list of modules within the scope of the current request, which is the currently selected page and theme. This module iterates through all modules, locates individual modules and queries their capabilities. It is useful for portlet developers to check whether certain capabilities are available on the page or not.
ModuleCapabilitiesList
Represents the aggregated capabilities of a list of modules. This is usually the non-deferred or deferred capabilities of the currently selected page and depends on how this object was fetched. This is especially useful for portlet developers to check if certain capabilities are available on the page or not.
ModuleCapability
Represents one capability as defined by a module.

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.
- 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.
  - Overview
    HCL Digital Experience (formerly IBM WebSphere Portal and IBM Web Content Manager) empowers you to create, manage, and deliver engaging omnichannel digital experiences to virtually all audiences with responsive content, targeted offers, seamlessly integrated applications, and consistent branding across channels (web, mobile. and hybrid mobile/web applications and more).
  - Roadmaps to deploy your system
    Review the roadmaps to understand the common deployment, configuration, migration, and integration patterns.
  - Roadmaps to create your website
    Review the roadmaps to understand how to create your website.
  - Online Help
    This Online Help is made available in the HCL Digital Experience Help Center for quick references on how to install, configure, maintain, and use HCL Digital Experience.
  - 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.
  - 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 portal to do various day-to-day administration tasks. There are two methods for editing portal setup: using the administration portlets or the XML configuration interface. The administration portlets are a convenient way to make real-time updates to the portal's configuration. While the XML configuration interface is suited to more advanced administration, including batch processing of updates.
  - 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.
    - Changing to a developer mode environment
      Install HCL Digital Experience and then immediately change to a developer mode environment. Use this environment when you develop applications, themes, portals, and portlets. Startup performance is improved within a developer mode environment.
    - Dojo and HCL Digital Experience
      HCL Digital Experience contains an instance of the Dojo Toolkit, a JavaScript library that is based on the Dojo Toolkit. When you develop components that use Dojo, you must be aware of how the portal uses Dojo, and the tips and restrictions when you use Dojo.
    - Extending HCL Portal class path
    - Developing themes and skins
      You can create themes using modules to contribute to separate areas of pages to provide flexibility, enhance the user experience, and maximize performance. To optimize themes on your website, use the theme optimization module framework. The framework separates feature-specific logic and capabilities from the theme code.
      - Roadmap: Creating and customizing themes
        Theme creation and customization are easy when you use the Theme Manager and download your static theme files by using a WebDAV client. This roadmap provides an overview of the theme creation and customization process. Links to detailed instructions for each step are provided in the roadmap.
      - Getting started with Themes
        Before you begin to develop themes, learn about the resources and the tools you can leverage to create and customize them.
      - The module framework
        The module framework allows extensions to contribute to different areas of a page to provide flexibility, enhance the user experience, and maximize performance.
      - Understanding the Simple Theme
        With the Simple Theme, you can create, copy, and customize themes in minutes with just a few clicks and far fewer files than the Portal 8.5 theme.
      - Understanding the Portal Version 8.5 modularized theme
        Modern websites and browsers enable incredible new capabilities that can greatly enhance your user's web experiences. However, these capabilities are not without cost in terms of large page sizes and more processing in the browser when each page is rendered. These capabilities are worth it when you need them, but removing them for an entire site or including them only on pages that take advantage of these capabilities provides for more flexibility.
      - Customizing the theme
        The module framework allows themes to be customized in order to provide flexibility, enhance the user experience, and maximize performance.
        Theme Editor
        The Theme Editor portlet is a new addition to HCL Digital Experience on-premise CF196 and later release capabilities. The portlet allows an administrator to edit static theme resources in WebDAV without the use of a WebDAV client or tool.
        Editing static theme resources and connecting with WebDAV
        After you create a new theme, you can edit the static resources that are associated with the theme.
        Copying your theme
        Starting with Combined Cumulative Fix 08, you can now copy your theme by using the Theme Manager. You can also choose to copy your theme manually.
        Dynamic content spots
        The static template files use dynamic content spots to reference JSP files or other dynamic resources. The dynamic resources are stored in a WAR file.
        Layouts
        You can apply ready-use layouts to your portal pages, modify the existing layouts, or add your own custom layout to change how your pages display.
        Skins
        You can apply ready-use skins to your portal pages, modify the existing skins, or add your own custom skin to change how your pages display.
        Menus
        You can customize the appearance and performance of your menus.
        Theme templates (theme.html)
        You can use static HTML to write portal themes. The static theme template is named theme.html.
        Changing the theme logo
        You can change the theme logo to customize your portal site and rebrand it to reflect your business.
        Customizing navigation
        Use dynamic content spots to determine what is displayed by Top, Primary, and Secondary navigation. Use the navigation.jsp file to map properties to the dynamic content spot IDs in the theme.html files. Rendering of the navigation is done with a single JSP file with <ul> and <li> tags.
        Styles
        HCL Portal 8.5 provides a selection of ready-use styles that you can be applied to your portal pages. You can also modify the existing theme styles or add your own custom style to achieve the look that you want.
        Configuring the portal theme and modules
        Themes and modules are configured through theme metadata properties and resource environment provider custom properties.
        Expression language beans for accessing programming models
        Expression language (EL) beans are available for accessing WebSphere Programming models. These beans are accessed through the PortalBean represented in the global namespace by wp. The beans provide access to HCL Digital Experience models and associated classes.
        wp.ac - Access control
        Provides read access to the current access control permissions for a resource.
        wp.analyticsTagList
        Attaches marketing information to Portal resources such as portal pages, portlets, or web content items. Reads the analytics tags that are associated with an identifiable portal resource.
        wp.clientProfile
        Provides access to the client profile.
        wp.identification
        Provides access to the identification services to serialize and deserialize objectIDs.
        wp.languageList
        The wp.languageList provides access to the list of languages that are defined in portal.
        wp.layoutModel
        The wp.layoutModel provides access to the tree model representation of the layout of a page.
        wp.metadata
        Provides access to the aggregated metadata of a node. The metadata that can be provided by individual nodes of the content model are combined according to the hierarchy that the content model exposes for these nodes. Values set on the node itself take precedence over values set for its parents.
        wp.moduleList
        The module list bean accesses modules that are part of the modularized theme architecture. You can query individual modules and their attributes and identify of the currently used modules within the scope of the currently selected and rendered page and theme.
        Module
        Represents one individual module.
        CurrentModuleList
        The current module list always represents the list of modules within the scope of the current request, which is the currently selected page and theme. This module iterates through all modules, locates individual modules and queries their capabilities. It is useful for portlet developers to check whether certain capabilities are available on the page or not.
        Module
        Represents one individual module.
        ModuleCapabilitiesList
        Represents the aggregated capabilities of a list of modules. This is usually the non-deferred or deferred capabilities of the currently selected page and depends on how this object was fetched. This is especially useful for portlet developers to check if certain capabilities are available on the page or not.
        ModuleCapability
        Represents one capability as defined by a module.
        wp.navigationModel
        The wp.navigationModel provides access to the navigation model. The navigation model is a tree representation of all pages.
        wp.publicRenderParam
        Public render parameters can be used by portlets to share context information. They are addressed with qualified names. The wp.publicRenderParam expression bean can be used within a theme or theme module to read the first String value of a public render parameter.
        wp.publicRenderParamValues
        The wp.publicRenderParamValues expression bean can be used within a theme or theme module to read the values of a public render parameter. The public render parameter is read in the context of the currently selected page that is determined internally.
        wp.rep - Resource Environment Provider
        The wp.rep provides access to the set of configuration entries for the specified resource environment provider.
        wp.selectionModel
        The NavigationSelectionModel provides access to a selection model for a navigation model. The selection model is the navigation model from the perspective of the currently selected page, from which you can get to the selected page's ancestors and descendents.
        wp.themeConfig
        The wp.themeConfig encapsulates the theme configuration parameter lookup process.
        wp.themeList
        wp.themeList provides access to list of theme objects.
        wp.user - User
        The wp.user provides access to the active user.
        Common beans
        The following beans are returned by many different beans and are used flexibly.
        uiNavigationModel
        By default, the uiNavigationModel lists only visible pages as part of its iterator. When the Show Hidden Pages option is selected in the Toolbar, it also lists the hidden pages. There is a mobile hidden flag for pages. The model also helps you specify a mobile test device class expression, which is used to evaluate if the system is rendered as part of a mobile request.
        Drag-and-drop
        Drag-and-drop uses HTML5 code to facilitate the layout of content.
        Displaying messages in the status bar module
        You can display messages in the status bar to share important information with users.
        Displaying the draft page ribbon
        The draft page ribbon is a strip of text that appears along both sides of a page that has a draft in the current project.
        Adding jQuery to a theme
        The jQuery library is a JavaScript library. HCL Digital Experience includes a jQuery module for the jQuery core so you can use jQuery in a theme.
        Using Sametime with the HCL Portal 8.5 theme
        You can add modules to your profile to use HCL Sametime with the HCL Digital Experience Portal Version 8.5 theme.
        Tags used by the portal JSPs
        Learn about the most commonly used tags in the portal JSPs. Use these tags to modify the appearance and layout of the portal page.
      - Developing themes for a production portal
        Use the theme artifacts to package a theme for staging to production.
      - Device classes
        Device classes are used in HCL Digital Experience as an abstraction for common properties for the device of a client. For instance, tablet computers can be grouped into a device class tablets, since they share a form factor and possibly other traits such as touch interface, or additional hardware sensors.
      - Responsive Web Design
        Responsive Web Design provides content parity between mobile devices and desktop channels, which enhances user experience and brand consistency. Seamless changes in screen size, from small to large, are now possible while the order of the content is maintained. Content maintenance is simplified by having one site that is represented by one set of assets.
    - URL generation in HCL Portal
      Generating Portal URLs correctly is one of the most important tasks in programming an HCL Portal based application. There are several programming tools and techniques available for generating HCL Portal URLs in custom code. The following section introduces the programming tools available and discusses when it is most appropriate to use each of the tools.
    - Model SPI overview
      Models provide information that is needed by HCL Digital Experience to perform tasks such as content aggregation or building navigation to browse the aggregated content. The information that is aggregated is represented through models that can be accessed programmatically by using the Model SPI (read-only). The information of a model is usually persistent (stored in a database) but can also be transient (computed and stored only in memory). Models can be represented by using a tree structure (nodes have a parent-child relationship), a list structure, or a selection structure (a selected element in a tree structure).
    - Controller SPI
      You can use the Controller SPI for portal administration. It allows you to modify portal resources. It enhances the read-only portal Model SPI by adding writable aspects.
    - User and group management
      The Portal User Management Architecture (PUMA) System programming interface (SPI) provides interfaces for accessing the profiles of a portal User or Group.
    - Portal Access Control interfaces
      Portal Access Control provides interfaces for retrieving and modifying and access control information of portal resources, such as portlets or pages.
    - Developing portlets
      Get an overview of the process of creating portlets, learn about the concepts of the APIs used to develop portlets, and view the samples to get you started. Also, learn about integrating features such as single sign-on, cooperative sharing of information using the property broker, and migrating Struts applications to the portlet environment.
    - HCL DX Portlet Bridge support for JavaServer Faces 2.2
      HCL Digital Experience 8.5 and 9.5 includes the HCL Portlet 2.0 Bridge for JSF 2.2. The bridge provides customers an interface to developing and running JSF Portlets.
    - Web Developer Toolkit for HCL Digital Experience
      Learn more about what you can do with the Web Developer Toolkit for HCL Digital Experience.
    - The Script Application
      The Script Application enables script developers to create portlets for HCL Digital Experience with HTML, JavaScript, and CSS.
    - The HCL Web Content Manager API
      You can use the Web Content Manager API to extend functions of HCL Web Content Manager.
    - Search REST API specification
      The following document describes the API call to search HCL Digital Experience. You can search HCL Digital Experience to find content that contains a specific text string in its title or content, or is tagged with a specific tag.
    - Extending tagging and rating by using service APIs
      Developers can enhance and extend the tagging and rating features of the portal. For this purpose the portal tagging and rating feature provides service APIs that you can use to enhance tagging and rating by your requirements.
    - How to create a custom launch page
      You can configure an authoring portlet to use a launch page of your own design instead of the default user interface.
    - How to create a custom HTML editor integration
      You can use custom HTML editors in all HTML fields of the authoring interface or specific HTML elements that are defined in an authoring template. Custom HTML fields are used to integrate third-party editors into the authoring interface.
    - How to use remote actions
      Remote actions are used to trigger actions from the HCL Web Content Manager application.
    - How to create custom plug-ins
      A custom plug-in is a reusable Java class that you create to run a task. You can create custom plug-ins such as custom workflow actions, plug-ins to run when a page is rendered, plug-ins to store multi-locale text strings and plug-ins to run when a file is uploaded.
    - Digital Data Connector (DDC) for HCL Portal
      You can use the Digital Data Connector (DDC) for HCL Portal framework to integrate data from external data sources on your portal pages by using HCL Web Content Manager presentation components. External data means that the data does not need to be stored directly in HCL Web Content Manager. For example, you can use DDC to render social data that you have on your HCL Connections server or on other social platforms in the context of your portal pages. Other possible data sources include news feeds, task lists, product catalog information, to name just a few.
    - Determining the current web content context
      To determine the current web content context of a portal page or Web Content Viewer portlet, you can use the WCM Page Context Service. This service provides the ID of the currently rendered item of a page or portlet.
    - REST service for Web Content Manager
      Application developers can use Representational State Transfer (REST) services to work with Web Content Manager. The REST service for Web Content Manager provides authoring access to content items and elements. The service follows the Atom Publication Protocol, and Atom feeds, and entries are accessible in XML (application/atom+xml) and JSON (application/json) format.
    - Digital Experience Version 2 REST APIs (Beta)
      The API design for version 2.0 of the DX REST API is intended to facilitate the creation of HCL Web Content Manager assets.
    - How to display data from external sources
      You display data from external sources, such as SQL databases, by using the same methods as you would when you create a website.
    - Instrumenting web content for Active Site Analytics
      You can collect information from web content for Active Site Analytics.
    - Java messaging services for web content
      Web Content Manager supports for the notification of events such as item state changes, or services starting and stopping. These notifications can be delivered as messages to the Java messaging service.
    - Reference documents
      Reference copy of API, SPI, Javadoc, and more, for HCL Digital Experience 8.5 and 9.0.
    - Developing basic PAA file applications
      Solution developers can create their own Portal Application Archive (PAA) files. The developers can then use the Configuration Wizard to add on their applications to their HCL Digital Experience environment.
    - Developing advanced PAA file applications
      Developers can create their own advanced Portal Application Archive (PAA) file. The advanced PAA file contains custom content. The developers can then use the Configuration Wizard to add on their applications to their HCL Digital Experience environment.
    - HCL UX Screen Flow Manager
      The HCL UX Screen Flow Manager helps operators, developers, and dialog modelers develop fine-granular, small split portlets. Learn to configure the sequence, transitions, and workflow of a set of screens.
  - Troubleshooting
    This section helps you resolve problems, use diagnostic tools and tracing to capture HCL Digital Experience system errors.
  - Reference
    View information that can help you use the Digital Experience Help Center including directory conventions, terms of use, trademarks, a glossary, and more.
  - Glossary
    This glossary includes terms and definitions for HCL Digital Experience.
  - Content Template Catalog 4.4
    The Content Template (CTC) is a set of templates that accelerate the process of building a website.

ModuleCapability | HCL Digital Experience

Represents one capability as defined by a module.

Attributes:

name

Returns the name of the capability.

Example:

${wp.moduleList.current.capabilities['oneUI'].name}

Parameters: none

Returns: String; never null.

version

Returns the version of the capability.

Example:

${wp.moduleList.current.capabilities['oneUI'].value}

Parameters: none

Returns: String; never null.