Set dynamic content spot resource references for a theme

Define dynamic content spot resource references using module wp_dynamicContentSpots_85.

1. Edit...
   WP_profile/installedApps/cell/myTheme.ear/myTheme.war/WEB-INF/plugin.xml

   ...and set IDs and names to have a unique custom name. For example

   <?xml version="1.0" encoding="UTF-8"?>
   
    <plugin id="com.ibm.mytheme" 
            name="myTheme Modules" 
            provider-name="IBM" 
            version="1.0.0">
   
    <extension id="wp_dynamicContentSpots_custom" 
           point="com.ibm.portal.resourceaggregator.module">
   
        <module id="wp_dynamicContentSpots_custom">
   
          <contribution type="dyn-cs">
   
            <sub-contribution type="markup" ref-id="mytheme_footer">
             <uri value="res:{war:context-root}/themes/html/dynamicSpots/footer.jsp"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_crumbTrail">
             <uri value="res:{war:context-root}/themes/html/dynamicSpots/crumbTrail.jsp?rootClass=wpthemeCrumbTrail&amp;startLevel=2"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_topNav">
             <uri value="res:{war:context-root}/themes/html/dynamicSpots/navigation.jsp?rootClass=wpthemeHeaderNav&amp;startLevel=0&amp;primeRoot=true"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_primaryNav">
             <uri value="mvc:res:{war:context-root}/themes/html/dynamicSpots/navigation.jsp?rootClass=wpthemePrimaryNav%2520wpthemeLeft&amp;startLevel=1,smartphone@,tablet@"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_secondaryNav">
             <uri value="mvc:res:{war:context-root}/themes/html/dynamicSpots/navigation.jsp?rootClass=wpthemeSecondaryNav&amp;startLevel=2&amp;levelsDisplayed=2,smartphone@,tablet@"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_sideNav">
             <uri value="mvc:res:{war:context-root}/themes/html/dynamicSpots/sideNavigation.jsp?startLevel=2,smartphone@,tablet@"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_mobileNav">
             <uri value="mvc:smartphone/tablet@res:{war:context-root}/themes/html/dynamicSpots/mobileNavigation.jsp"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_commonActions">
             <uri value="res:{war:context-root}/themes/html/dynamicSpots/commonActions.jsp"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_layout">
             <uri value="lm:template"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_pageModeToggle">
             <uri value="mc:wp_toolbar@res:{war:context-root}/themes/html/dynamicSpots/pageModeToggle.jsp"/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_head">
             <uri value="res:{war:context-root}/themes/html/dynamicSpots/head.jsp/>
           </sub-contribution>
   
            <sub-contribution type="markup" ref-id="mytheme_status">
             <uri value="mc:wp_status_bar@res:{war:context-root}/themes/html/dynamicSpots/status.jsp"/>
           </sub-contribution>
          </contribution>
       </module>
   
     </extension>

2. Connect WebDAV client
   http://host:port/wps/mycontenthandler/dav/fs-type1/

3. Modify custom theme profiles to include the module in our updated plugin.xml.
   1. Copy files in...
      themes/myTheme/profiles

      ...to a backup location.

      Remove existing wp_dynamicContentSpots_85 module.

   2. Modify plugin.xml to include wp_dynamicContentSpots_custom

   3. Copy profiles back to the profiles folder.

4. From themes/myTheme/nls, copy theme_en.html to the local drive.

   Repeat for other supported locale files

5. Edit theme*.html files, and replace all occurrences of 85theme with myTheme.
   dyn-cs:id:85theme_head

   ...becomes...

   dyn-cs:id:myTheme_head

6. Save the files.

7. Copy the files into the fs-type1 folder.

8. Restart IBM WebSphere Portal.

We do not need to modify the theme.html file in the themes\myTheme folder. That file is not used other than to redirect to the appropriate locale file in the nls folder. We need to modify it only if you add or remove locales.

Parent Link the static resources to the dynamic resources for the theme