Setting up Content as a Service

To be able to work with Content as a Service pages in HCL WebSphere Portal, you must enable it by using an HCL Digital Experience configuration task.

For Content as a Service pages to work, you must have the new functions for HCL WebSphere Portal and HCL Web Content Manager Version 8.5 CF05 enabled. For more information, see the readme file for WebSphere Portal and Web Content Manager V8.5 CF05.

The setup for Content as a Service pages comprises both resources that are shared across virtual portals and virtual portal scoped resources.

1. Change the directory to the wp_profile_root/ConfigEngine directory. If you are using IBM z/OS®, open a UNIX System Services command prompt to change directories.

2. Run the following command to initiate the setup of shared resources:
   ./ConfigEngine.sh install-caas -DPortalAdminID=user_id -DPortalAdminPwd=password -DWasUserid=user_id -DWasPassword=password

3. Run the following command to initiate the setup of default virtual portal scoped resources:
   ./ConfigEngine.sh install-caas-vp -DPortalAdminID=user_id -DPortalAdminPwd=password -DWasUserid=user_id -DWasPassword=password

4. If you have virtual portals, run the following command on each virtual portals to initiate the setup of virtual portal scoped resources:

   Note: Add either the -DVirtualPortalContext or -DVirtualPortalHost parameter to the install-caas-vp.

   ./ConfigEngine.sh install-caas-vp -DPortalAdminId=user_id -DPortalAdminPwd=password -DWasUserid=user_id -DWasPassword=password -DVirtualPortalContext=virtual_portal_context

5. Restart your portal server.