IBM BPM, V8.0.1, All platforms > Customize and rebranding interfaces > Customize Process Portal > Customize Process Portal spaces > Customize themes

Enabling banner customization in a custom theme for Process Portal spaces

The default theme allows for the customization of the banner that appears at the top of a space. You can allow the same banner customization in spaces that make use of your custom theme by providing your own dynamic content spot for your banner.

You must have administrator privileges to complete this task.

Follow the steps for creating the artifacts for a new custom theme.

Procedure

1. Open the theme.html file in your custom theme folder.
2. Edit the following section of the file to refer to your own banner content, as shown below.

   
   Before:

   <a rel="dynamic-content" href="dyn-cs:id:bannerHtml@tl:oid:csa2.theme"></a>

   
   After:

   <a rel="dynamic-content" href="dyn-cs:id:customBannerHtml@tl:oid:csa2.theme"></a>

3. Define your own dynamic content spot for your theme as follows:
   1. Locate the Mashups_DynamicSpotMapping file.
      

      For a stand-alone server:

      profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config

      For a cluster:

      dmgr_profile_root/BusinessSpace/cluster/mm.runtime.prof/config

   2. Add a new property, such as customBannerHtml, with a value of the path to the banner file in your custom theme, including the WebDAV directory.

      For example,

      res:/mum/mycontenthandler/mm/dav/filestore/public/themes/customTheme/banner/customBanner/banner.html

   3. Run the updatePropertyConfig command using the wsadmin scripting client to update the configuration.
      

      • For a stand-alone server:

        The following example uses Jython:

        AdminTask.updatePropertyConfig('[-serverName server_name -nodeName node_name -propertyFileName "profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config/DynamicSpotMapping.properties" -prefix "Mashups_"]')
        
        AdminConfig.save()

        The following example uses Jacl:

        $AdminTask updatePropertyConfig {-serverName server_name -nodeName node_name -propertyFileName "profile_root/BusinessSpace/node_name/server_name/mm.runtime.prof/config/DynamicSpotMapping.properties" -prefix "Mashups_"} 
        $AdminConfig save

      • For a cluster:

        The following example uses Jython:

        AdminTask.updatePropertyConfig('[-clusterName cluster_name -propertyFileName "dmgr_profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/DynamicSpotMapping.properties" -prefix "Mashups_"]')
        
        AdminConfig.save()

        The following example uses Jacl:

        $AdminTask updatePropertyConfig {-clusterName cluster_name -propertyFileName "dmgr_profile_root/BusinessSpace/cluster_name/mm.runtime.prof/config/DynamicSpotMapping.properties" -prefix "Mashups_"} 
        $AdminConfig save

Results

By defining your own content spot, you ensure that your theme functions independently from the default theme and only depends on resources from within your custom theme.

What to do next

To make your changes to the theme available, restart the server that hosts the Process Portal space.

Customize themes in a Process Portal space

Related tasks:
Create custom banner files for Process Portal spaces