Installing Content Template Catalog on virtual portals with no base portal

You must install the Content Template Catalog page templates and libraries on each virtual portal to enable users to create sites.

Before you begin

Note: You must import the Site Builder library onto the virtual portal before installing Content Template Catalog: How to import the Site Builder library onto a new virtual portalHow to import the Site Builder library onto a new virtual portal.

About this task

Follow these steps to distribute a shared version of templates and libraries to a virtual portal when no base portal is being used.

Procedure

  1. Make a backup copy of the original ctc.properties or ctc-zos.properties file in case you need to revert to it.
  2. Open the properties file in a text editor and make these changes:
    Mandatory settings
    • Enter the path of the server profile directory in the PROFILE_DIR parameter. For example:
      • Linux™: /opt/WebSphere/wp_profile
      • Windows™: C:\IBM\WebSphere\wp_profile
        Note: If your server path contains spaces, use the dos name. For example: C:\Progra~2\IBM\WebSphere\wp_profile
    • Enter the virtual portal host name in the VirtualPortalHostName parameter. The host name value takes precedence over VirtualPortalContext. If you only use a context path in your virtual portal, leave this setting blank.
    • Enter the virtual portal context in the VirtualPortalContext parameter. For example, if your virtual portal is accessed through /wps/portal/myVirtualPortal then VirtualPortalContext should be set to myVirtualPortal.
    Note: The setting CTC_BASE is set to true by default and shouldn't be changed. This is important because you must install the core CTC files in the virtual portal if they have not been installed in a base portal.
    Optional settings
    • By default, the installer is designed to work offline. This means installation occurs without accessing external DTD files. If your server has access to the Internet, you can set OFFLINE_MODE to false, and external DTD files are accessed during install.
    • A sample site is installed by default. If you do not want to install the CTC Demo sample site, change CTC_DEMO to false. See The Content Template demonstration site for further information.
    • To install the Multilingual solution and the CTC Multilingual Demo site, change CTC_MLS to true and ensure that CTC_DEMO is set to true. See The localized CTC demonstration sites for further information.
    • Set FORCE_UPDATE to false to decrease the installation time when deploying to multiple virtual portals.
    • A set of CTC ready groups and users can be installed by setting CTC_USERS to true.

    Leave all other parameters to their default settings.

  3. Save and close the file.
  4. Ensure your HCL Portal server is running.
  5. Start the installation program from the command line. If you did not set the administrator passwords in the wkplc.properties file, you must add them to the command line with the syntax:

    -PortalAdminPwd password -WasPassword password

    Windows
    ctc-install.bat
    AIX® HP-UX Linux
    ctc-install.sh
    Note: Ensure that ctc-install.sh is enabled to run as program before you run the command.
    z/OS®
    ctc-install-zos.sh

    When the script finishes successfully, the installation is complete.

  6. Restart the server to enable features that are used by Content Template.
  7. When the server restarts, open a web browser and navigate to the Portal Administration page to check that Content Template installed successfully. If you installed the demo content, you see a new set of pages at the page root, and a set of Content Template libraries in the list of Web Content Libraries.