Setting up configuration of your own modulesAdded by IBM | Edited by IBM on January 9, 2013 | Version 3 (Show original)
|Create your own module if IBM® WebSphere Portal does not provide a module with the functions or configurability that you need.
Do not modify the source of modules provided with WebSphere Portal to meet your needs, as such changes are unsupported and would impact all themes using those modules. The new modular theme architecture was created for this reason, so that you do not have to get involved with the inner-workings of WebSphere Portall modules to make customizations. Instead, you have the flexibility to create and turn on your own modules and turn off certain unneeded or unwanted modules.
Make your own modules configurable as needed in the same way that WebSphere Portal modules are: through theme metadata properties and resource environment provider custom properties.
Setting up custom theme metadata propertiesParent topic: Configuring the portal theme and modules
Theme metadata properties are specific to a single theme. To reinforce this scope, it is good practice to prefix your property names with yourTheme
. If you have a property that you want to apply across multiple themes or a property that is specific to a module, set up a resource environment provider custom property instead as described in Setting up resource environment provider custom properties.
Setting up resource environment provider custom properties
Resource environment provider (REP) custom properties are flexible in scope. These properties are all technically global in scope, but you can use a consistent naming convention to imply that they apply across multiple themes, to just a single theme or to just a single module.
Using your configuration properties