Copy the static resources for your themeAdded by IBM | Edited by IBM on March 31, 2014 | Version 7 (Show original)
|You need to make a unique copy of the Portal 8.0 theme static resources before you start customizing your custom theme.
Enable development mode before you copy the static resources. Set the resourceaggregation.development.mode
property to true within the WP ConfigService resource environment provider. If you do not enable development mode, be sure to restart your portal server at the end before you use your copied theme on a page.
Parent topic: Create a copy of the theme
Deploying themes with cacheable resources
- Connect your WebDAV client, such as WebDrive or AnyClient, to http://host:port/wps/mycontenthandler/dav/themelist/.
- Copy the ibm.portal.80Theme folder to a local disk.
- Rename the folder to the name of your theme, such as customTheme.
- In the metadata folder, edit the localized_en.properties file, or whichever file is your default locale, and change the value of the title key to the display name of your theme, such as Custom Theme. Save the file. Repeat this step for any of the other locale files for the languages that you plan to support.
- Edit the metadata.properties file and change the Portal8.0 part of the com.ibm.portal.layout.template.href value to customTheme. Make sure that you have two properties that look like the following example:
- Save the file.
- Delete the skins folder from your customTheme, which removes the extra copies of the skins that are shipped with IBM® WebSphere® Portal.
Your custom skin is created in a later step.
- Copy the entire customTheme folder into the themelist folder.
- Double-check the contents of the customTheme folder in the themelist to ensure that everything is copied correctly. Compare each subfolder in customTheme to the corresponding subfolder in ibm.portal.80Theme to ensure that it looks like the correct number of files were copied. Recopy any files or subfolders that are missing. In particular, be sure to:
- Double-check the contents of the metadata.properties file in the themelist.
- Double-check the contents of the profiles folder. You now have four files in that folder: