How to enable Practitioner Studio | HCL Digital Experience

This section outlines how to enable Practitioner Studio and Woodburn Studio in both base portal and virtual portal environments.

Enabling Practitioner Studio and Woodburn Studio in base portal

Note: It is not necessary to stop or restart Portal when running these configuration tasks. Please note that in order for you to deploy Practitioner Studio and Woodburn Studio to a virtual portal, you must first enable the 95 UI features in base Portal.
  1. Open a command line.
  2. Change to the wp_profile-root/ConfigEngine directory.
  3. Run the enable-v95-UI-features config task.
    • AIX: ./ConfigEngine.sh enable-v95-UI-features -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password>
    • Linux: ./ConfigEngine.sh enable-v95-UI-features -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password>
    • Windows: ConfigEngine.bat enable-v95-UI-features -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password>
    Note: Any actions taken when using the Preview As User feature in DAM and CC shows the site as the original user, not the one that you are using to preview.

Enabling Practitioner Studio and Woodburn Studio in an existing virtual portal

  1. Open a command line.
  2. Change to the wp_profile-root/ConfigEngine directory.
  3. Run the enable-v95-UI-features-virtual-portal config task.
    • AIX: ./ConfigEngine.sh enable-v95-UI-features-virtual-portal -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password> -DVirtualPortalContext=
    • Linux: ./ConfigEngine.sh enable-v95-UI-features-virtual-portal -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password> -DVirtualPortalContext=
    • Windows: ConfigEngine.bat enable-v95-UI-features-virtual-portal -DWasPassword=<WAS admin password> -DPortalAdminPwd=<Portal admin password> -DVirtualPortalContext=
    Notes:
    • To configure the virtual Portal Manager so that Practitioner Studio is deployed for the newly created virtual portals, see How to configure Practitioner Studio.
    • To enable Practitioner Studio and Woodburn Studio on all available Virtual Portals, you can use the following parameter: -DUpdateVPs=true
    • If -DVirtualPortalContext= has a space in the context name, please add quotes around the name of the context.

Controlling the access to the Applications menu

In Practitioner Studio, the Applications menu is displayed only if the user has access to either the page with the unique name hcl.portal.applications or its child pages that are inherited from a parent page. Before the Practitioner Studio was introduced, the access to the Applications menu was controlled by the ibm.portal.page.Applications page as that had WCM and the like.

There are two options to enable the Application menu for users:
  1. Grant User role access to the page with the unique name hcl.portal.applications (and block the propagation if you want to control the access to the child pages).
  2. Starting with release CF205, you can change your preference from the default hcl.portal.applications page to another page by using the following configuration:
    WP ConfigService: toolbar.page.icon.check=somepage.uniquename
    where somepage.uniquename refers to the page of your choice. For example, hcl.portal.practitionerstudio
    Note: Ensure that you restart your application.

Enabling HCL DX site to be seen in SiteMap

Enabling Practitioner Studio via the enable task has the following effect to your previous view: The Administration pages will be disabled, the Home pages will be excluded from the SiteMap, and first-level navigation drop downs in the toolbar and Practitioner Studio.

Follow the steps to enable your site to be seen in SiteMap:
  1. Navigate to Administration > Managed Pages.
  2. Click Edit Page Properties for your home page.
  3. Expand Advanced Options and then click I want to set parameters.
  4. Create a new parameter com.ibm.portal.Hidden with value false.
  5. Save, then test.