The theme has two types of resoursces:
Dynamic J2EE resources
Dynamic J2EE resources consist of JSPs. Dynamic resources must be located in a WAR file, as they must be compiled and executed on the server.Static resources
Do not edit any of the themes provided with WebSphere
® Portal, as they are updated by WebSphere
Portal fixes and are static. Instead, update and deploy your own copy of the theme WAR in WebSphere
Theme resources reside in the following locations:
When you work with J2EE theme resources, be aware of the following:
- Theme J2EE resources are deployed at installation to the directory PortalServer_root/theme/wp.mashup.cc.theme/installedApps/wp.mashup.cc.theme.ear/PageBuilder2.war/.
- In the past themes were also deployed to PortalServer_root/installer/wp.ear/installableApps/wps.ear/wps.war/. Deploying customer themes to this location is no longer supported.
- Note that PortalServer_root is a read only directory. Do not make any changes to these files, as they can be updated by service updates. Instead, if you want to customize a theme shipped with Portal, deploy your own copy of the theme WAR in WebSphere Application Server. For instructions about deploying themes see Deploying a theme.
- When you deploy your theme in its own WAR file, the resources are deployed to the portal profile directory wp_profile_root/installedApps/node/your-ear-name.ear/your-war-name.war/ .
In earlier portal versions themes deployed their static resources with their WAR file. With the page builder theme in portal Version 7 and later versions, static resources are deployed to WebDAV. You can access all WebDAV file store entry points through the root URL http://hostname:port/wps/mycontenthandler/dav/entrypoint/
Administration entry points:
/themelist/ File store entry points:
This is the administrative entry point for managing themes./skinlist/
This is the administrative entry point for managing skins.
For more details about these entry points, see Using WebDAV to manage themes and skins
This is the entry point for creating, updating, or deleting static layout templates./fs-type1/common-resources/
This is the entry point for common static resources that are shared by multiple themes.
You can access all WebDAV entry points listed previously through the root WebDAV entry point URL. This URL is http://hostname:port/wps/mycontenthandler/dav/entrypoint/
. For more details refer to the topics about Working with static themes.
Directory structure of theme resources
Dojo is deployed to the directory PortalServer_root/theme/wp.theme.dojo/installedApps/dojo.ear/dojo.war/
. Multiple versions of dojo are provided here to support migrated themes that were implemented for a particular version of dojo. Dojo V 1.3.2 is provided in the root directory of dojo.war
. Dojo V 1.4.3 and future versions are provided in a subdirectory named by the version, for example /v1.4.3/
. Both are located at PortalServer_root/theme/wp.theme.dojo/installedApps/dojo.ear/dojo.war/v1.4.3/com/ibm/themes/PageBuilder2
This layer is included when the page is initially rendered. It includes all modules and widgets required for view mode. theme.edit..js
This layer is included when a page enters Edit mode. It includes all modules and widgets required for customizing the page.
The same directory includes uncompressed versions of both files, You can edit these files during development or use them for debugging purposes. To use these uncompressed files, follow these steps:
- Access the WebSphere Application Server administrative console.
- Select Resources -> Resource Environment -> Resource Environment Providers.
- Locate the WP CommonComponentConfigService.
- Select Custom Properties.
- Select the property cc.isDebug. Note that this property is on the second page of the properties list.
- Change the value of the property cc.isDebug to true.
- Restart your portal.
Parent topic: The Page Builder theme
Using WebDAV to manage themes and skins
Deploying the theme
Deploying the theme
Working with dynamic content spots
Inside a WAR file or WebDAV root folder, theme resources are grouped in the directory /themes/
. There are additional folders such as, css
, and system
. This directory can be structured into subdirectories as follows:
. For more information see Aggregation
under the section about the Search order for portal resources.