Feature-specific capabilities are added and removed using a module profile. Network traffic that is used to download the resources that each module contributes to the browser for the client is optimized.
® WebSphere Portal do not need to be rebuilt every time a fix is applied to the portal.
Modules are also the way in which many portal runtime features are provided and used in themes.
Creating the references to load modules in your themeParent topic: Updating an existing theme to use the new features
Dynamic content spots start the combiner data source which injects markup necessary to load all of the modules that are identified in the module profile. To start modularizing your theme, create two dynamic content spot references in the static template for your theme to create references to load modules.
Creating the module profile
You can create a module profile or use the module profile from the ready-to-use IBM
WebSphere Portal 126.96.36.199 theme. Modify the profile as needed by editing the profile_full.json
file in the profiles
Creating the module definitions
Many of the modules listed in the profile are modules provided by IBM
WebSphere Portal and defined in various plugin.xml
files. Any modules that you create that are specific to your theme need to be defined in the plugin.xml
file for your theme.
Removing code that is now provided by modules
Do not include code in the JSP files within a modularized theme.