Install CTC and Site Builder on virtual portals with no base portal

Install the page templates, libraries, and the Site Builder Portal page on each virtual portal to enable users to create sites.

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

1. Make a backup copy of the original ctc.properties file in case we 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

       If the 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 we only use a context path in the virtual portal, leave this setting blank.

   • Enter the virtual portal context in the VirtualPortalContext parameter. For example, if the virtual portal is accessed through /wps/portal/myVirtualPortal then VirtualPortalContext should be set to myVirtualPortal.

   The setting CTC_BASE is set to true by default and shouldn't be changed. This is important because 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 will occur without accessing external DTD files. If wer server has access to the Internet, we can set OFFLINE_MODE to false, and external DTD files will be accessed during install.

   • A sample site is installed by default. If we do not want to install the CTC Demo sample site, change CTC_DEMO to false. See The Content Template Catalog 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.

   • Site builder is used to create site and site section templates used to quickly build new sites, or sections of sites. If we do not want to install the Site Builder, change SITE_BUILDER to false.

   • Set FORCE_UPDATE to false to decrease the installation time when deploying to multiple virtual portals.

   • Set SB_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. Verify the WebSphere Portal server is running.

5. Start the installation program...
   ctc-install.bat

   If we did not set the administrator passwords in the wkplc.properties file, add them to the command line with the syntax:

   -PortalAdminPwd password -WasPassword password

6. Restart the server to enable features used by CTC and Site Builder.

7. When the server restarts, open a web browser and navigate to the Portal Administration page to check that CTC and Site Builder installed successfully. If we installed the demo content, we see a new set of pages at the page root, and a set of CTC libraries in the list of Web Content Libraries. If we installed Site Builder a new Site Builder page is also added under the Applications menu, and the Site Builder Template library is included in the list of libraries.

8. If we have any custom site templates in the base portal, these need to be exported and then imported into the site builder in the virtual portal, if we want them to be available in the virtual portal.

Parent First-time installation of CTC and Site Builder