Upgrading Content Template Catalog and Site Builder on virtual portalsAdded by IBM | Edited by IBM on January 8, 2014 | Version 11 (Show original)
|You must install the Content Template Catalog page templates, libraries, and the Site Builder Portal page on each virtual portal to enable users to create sites.
You must have installed Content Template Catalog and Site Builder, with or without the CTC Demo site, on the base portal.
Follow these steps to distribute a shared version of templates and libraries to a virtual portal.
Parent topic: Upgrade installation steps
- Make a backup copy of the original ctc.properties or ctc-zos.properties file in case you need to revert to it.
- Open the properties file in a text editor and make these changes:
Mandatory settings when upgrading from Content Template Catalog version 3
- 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
- Change CTC_BASE to false. This is important, because you should not install the core CTC files when they already exist on the base portal.
- Change SB_PAGE_BASE to false.
- Change SB_PAGE_VP to true.
- Change SB_APP to true.
- Change SB_CONTENT to false.
- Change SB_CONTENT_VP to true.
- 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.
- If upgrading from Content Template Catalog version 3, you must change UPGRADE_CTC_3 to true. Content Template Catalog requires that the Page Templates are located under Hidden Pages. This is an optional step when migrating to WebSphere® Portal or Web Content Manager 22.214.171.124, but is required for the Content Template Catalog install. By setting UPGRADE_CTC_3 to true, the Page Templates will be moved under Hidden Pages if they have not been already.
- By default, the installer is designed to work offline. This means installation will occur without accessing external DTD files. If your server has access to the Internet, you can set OFFLINE_MODE to false, and external DTD files will be 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.
- Site builder is used to create site and site section templates that can be used to quickly build new sites, or sections of sites. If you do not want to install the Site Builder, change SITE_BUILDER to false.
- If you want to install the default empty site templates, then instead change SB_CONTENT to true and SB_CONTENT_VP to false.
- 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.
- Save and close the file.
- Ensure your WebSphere Portal server is running.
- 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
ctc-install.batAIX® HP-UX Linux
When the script finishes successfully, the installation is complete.
- Restart the server to enable features used by Content Template Catalog and Site Builder.
- When the server restarts, open a web browser and navigate to the Portal Administration page to check that Content Template Catalog and Site Builder 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 Catalog libraries in the list of Web Content Libraries. If you installed Site Builder a new Site Builder page is also added to the page root, and the Site Builder Template library is included in your list of libraries.
- If you 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 you want them to be available in the virtual portal.