Home
HCL Digital Experience 9.5 [Legacy content]
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.
Setting up marketing campaigns
Use these tools and features to setup marketing campaigns for your website.
Digital Experience Personalization
Digital Experience Personalization provides automatic customization of website content presented to individual users and user groups.
Personalization terms
The concepts and principles for working with Portal Personalization require an understanding of terminology.
Rules
Rules are used to define how your Web site interacts with individual and groups of Web site visitors.
Rule elements
Learn about the options in the rule editor for the different types of rules.
Current Browser Capability
Browser Capability is an application object that allows you to profile a Web site visitor based on the attributes or capabilities of the browser being used. When applicable, it appears in the rule editor as an option when you select Resource.Attribute.

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.
- 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.
  - Website building blocks
    Unless you are familiar with the HCL Digital Experience and HCL Web Content Manager website model, review the building blocks. Building blocks are the different parts that make up the website framework, such as pages, navigation, themes, content, content libraries, and more.
  - Creating reusable assets
    Use reusable assets to store or generate content that is used in more than one place in your website.
  - Building the website
    Building a website includes creating libraries, pages, and web content. You also create links and navigation to your content, and assign access to different types of users, such as editors and viewers.
  - Authoring tools
    There are multiple ways to create and manage content including using the site toolbar, inline editing, and the authoring portlet.
  - Preparing for content authors
    Before content authors can create content you must prepare your site to be ready for content creation, including preparing the site toolbar, enabling inline editing, and creating templates.
  - Developing and managing content
    Use these tools and processes to develop and manage your website.
  - Delivering web content
    The type of delivery method you use to deliver web content to your viewers depend on the type of content that is being delivered, and the type of viewers your website is intended for.
  - Vanity URLs
    You can associate vanity URLs with portal pages and labels. Vanity URLs are short URLs that people can easily remember. They are shorter than full HCL Portal URLs. They are sometimes also called marketing URLs. You can publish vanity URLs for marketing campaigns through different channels, such as email or print. This way, you can use vanity URLs to direct customers to a specific portal page or content item. Interested site visitors who want to view your campaign can then remember or copy the short vanity URL and type it into the browser address field.
  - Social rendering
    HCL Digital Experience page editors can use social rendering to feature social data that is hosted on a remote HCL Connections server in the context of portal pages.
  - Setting up marketing campaigns
    Use these tools and features to setup marketing campaigns for your website.
    - Digital Experience Personalization
      Digital Experience Personalization provides automatic customization of website content presented to individual users and user groups.
      - How a site is personalized
        Use this topic to understand how to define a personalized list of new articles for a website, such as a section of an intranet site for targeted employee bulletins or where the content of the site is tailored to the particular user.
      - Personalization terms
        The concepts and principles for working with Portal Personalization require an understanding of terminology.
        Resources, resource instances, and resource collections
        Before you can personalize HCL Digital Experience resources, you need to understanding the terms for portal objects stored in the content repository.
        User resources
        Your site visitors want to quickly access content that meets their needs and interests, which are stored as properties in the user profile data store.
        Content resources
        Web content resources consist of data that is formatted and displayed on Web pages. Examples include articles, statistics and educational materials.
        Attribute Based Administration
        Attribute based administration provides a facility to customize the layout of a page for individual authenticated users by using rules to show or hide pages or portlets.
        Rules
        Rules are used to define how your Web site interacts with individual and groups of Web site visitors.
        Actions
        Actions use simple evaluation statements to select content to use or display, or to set information.
        Profilers
        Profilers are typically used to categorize an individual (usually the current site visitor) according to his or her user properties.
        Bindings
        Bindings combine actions and profilers to specify actions to perform when defined conditions are encountered. Returned content can be sorted or filtered prior to display or use. Actions can be set to be performed by always, exclude, and otherwise blocks. In addition, the total number of items used can be limited.
        Recommend Content
        You use Recommend Content rules (also referred to as recommendation rules) to recommend content to your Web site visitors. Recommendation rules, powered by LikeMinds, recommend content based on users' past interactions with your Web site.
        Visibility Rules
        Visibility rules determine what a user will see, or what has been targeted towards a user. Visibility rules can be assigned to pages and portlets and will be triggered automatically by the portal as needed.
        Rule elements
        Learn about the options in the rule editor for the different types of rules.
        Arithmetic expressions
        Arithmetic expressions allow you to perform mathematical operations on resource attributes as part of your rule.
        Count of (quantifiable conditions)
        Create an evaluation based on a count or tally of attributes that meet your criteria.
        Current Action Count or Action Name
        Current Action Count and Current Action Name allows you to base a profiler or rule on Web visitor actions.
        Current Browser Capability
        Browser Capability is an application object that allows you to profile a Web site visitor based on the attributes or capabilities of the browser being used. When applicable, it appears in the rule editor as an option when you select Resource.Attribute.
        Current Date
        Learn what Current Date is as rule element option in the rule editor.
        Current Request Attributes
        Use Current Request Attributes to inspect request attributes which can be set on the current JSP.
        Current Request Parameters
        Use Current Request Parameters to inspect data contained within the query string (the variables and values that appear after a question mark on a URL).
        Current Session Attributes
        Use current Session Attributes to inspect parameters stored within the current session object for the Web site visitor.
        do Action
        Use the Do action, Otherwise do action, Always do action, and Exclude do action elements.
        Include Only
        Include Only is a choice within the Select Action and Recommendation Rule structures. You can select action or binding rule to be used as the include only cause.
        is
        Select IS to evaluate the relationship between two sides of a conditional statement.
        order as is
        ORDER AS IS is used to specify the order you want selected content to be returned and used. The default, order as is, will return data in the order it is stored in the repository.
        Profile
        Profile is an arbitrary name (of your choice) that provides information about the Web site visitor, the date and time the visit occurs, or other circumstances or conditions.
        Profiler
        Profiler is a choice within the binding rule structure, and within the Specify a Resource Attribute window when constructing a profiler.
        Quick Profiler
        Quick profilers are created within bindings to perform simple evaluations. By using a quick profiler, you can avoid creating simple profilers as separate rules.
        sender
        SENDER must be a valid email address, list of email addresses (comma separated), or a resource attribute containing valid email addresses to whom the email will be sent.
        set to
        Learn about the SET TO action and alternatives to SET TO.
        value
        Value is the placeholder for the result of an evaluation. This value can be one you enter, the value of another resource attribute, or an arithmetic expression.
        Email
        View the prerequisites for creating an email action or promotion within the Personalization workspace.
        Email administration
        View the steps you need to complete before your run time server can send personalized email.
        Content spots
        Learn what a content spot is, why it is used and how to personalize content spot for a rule on a Web page.
        Rule spot mappings
        For a rule to be used on your Web site, it must be mapped to an existing content spot.
        Campaigns
        Campaigns are a means of organizing and implementing sets of personalization behavior.
        Application object
        An application object is a java object existing at a known location in the request context.
        Request Context
        The Request Context is the interface used to access various attributes for rules.
        Query framework
        The query framework is an object representation of a query.
      - The Personalization interface
        The Portal Personalization user interface consists of three portlets: the Personalization Navigator, Personalization Editor, and the Personalized List.
      - Publishing personalization rules
        HCL Digital Experience Personalization sends published rules across HTTP to a servlet which resides on each personalization server.
      - The Web Content resource collection
        The Web Content resource collection allows you to write rules that select lists of content from the HCL Web Content Manager.
      - The Portal User resource collection
        The Portal User resource collection uses public APIs provided by HCL Digital Experience to access user information.
      - LikeMinds Recommendations
        Personalization contains a dynamic recommendation system based on LikeMinds, which is software that is used with your e-commerce applications.
      - Feedback and analytics
        Personalization provides a complete logging framework for collecting data on how visitors are using your Web site. If Feedback is enabled, data is automatically collected about each Personalization rule that is fired. In addition, development tools enable Web sites to collect a variety of data related to visitors' actions and behavior. By default this data is logged to a standard database schema for later analysis and reporting. The framework is also extensible, allowing Web sites to customize and supplement the way data is collected and stored to more fully meet their needs.
      - Developing a personalized portlet
        This exercise demonstrates how to use Personalization features of HCL Digital Experience and Rational Application Developer to build your first personalized portlet. Your final result is a working portlet that uses Personalization rules and content spots to display personal news based on user attributes (or profiles).
      - Personalization programming reference
        HCL Digital Experience provides the programming model, processes, and APIs for the Personalization rules and resource engines.
      - Personalization APIs
    - Social Media Publisher
      The Social Media Publisher for HCL Web Content Manager is an extension to HCL Web Content Manager that allows businesses to promote their web content on social networks, and provide some basic statistics about the promoted content.
  - HCL Web Content Manager Multilingual Solution
    The HCL Web Content Manager Multilingual Solution is a set of tools that are used to manage translated versions of localized and regionalized websites.
  - Syndicated Feed Portlet
    The Syndicated Feed Portlet for HCL Digital Experience offers enhanced feed subscription and presentation capabilities.
- 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.

Current Browser Capability rule | HCL Digital Experience

Browser Capability is an application object that allows you to profile a Web site visitor based on the attributes or capabilities of the browser being used. When applicable, it appears in the rule editor as an option when you select Resource.Attribute.

Purpose

Browser Capability currently supports these attributes:

AcceptLanguage: Returns the value of the header 'accept-language' from the request object.
AcceptMimeTypes: Returns the value of the header 'accept' from the request object.
Agent: Returns the value of the header 'user-agent' from the request object. This is a lowercase string that contains information about the client software, usually the browser name or version.
BrowserType: Returns the browser type. Choices are available for supported browsers.
FullVersion: Returns the version of the browser to one point of precision. For instance, 6.1 and 6.1.1 are both returned as 6.1.
MajorVersion: Returns the first digit of the browser version. For instance, 6.0, 6.1 and 6.1.1 are all returned as 6.