Using your configuration properties
Create a JavaScript object for your theme on the client side. Theme metadata properties must be loaded dynamically. If you must load a property statically, use a resource environment provider custom property instead.
About this task
Configuration properties can be loaded either statically, type="config_static", or dynamically, type="config_dynamic". You can use one or the other or both depending on your needs. Static is intended for property values that do not commonly change after they are loaded initially, and is better for performance because the values are cached. Dynamic is intended for property values that change more frequently.
In this way, all configuration properties that your module must reference on the client side get merged together into a single convenient global config object, whether they are theme metadata properties or resource environment provider custom properties. You can then easily reference any property within the yourcoCfg.themesConfig object, such as yourcoCfg.themesConfig.yourTheme_yourRepProperty.
The theme and the modules that are provided with WebSphere® Portal merge their configuration properties into the ibmCfg global variable. You can run this variable in a browser console and inspect what the property names and values are. Because changes to values in the WP GlobalThemeConfig REP are global to all themes, you can override certain values on the client side if you need the values to be different in only your themes that include your module. You can do so with syntax similar to the following example in one of the config*.jsp files for your module:
i$.merge({<%--
--%>ibmCfg: {<%--
--%>themeConfig: {<%--
--%>loadingImage: "css/images/yourloading.gif"<%--
--%>}}});
If your module requires the wp_portal module then the portal configuration loads before the configuration for your module, ensuring that your override is merged in last.
Replace occurrences of your* in italics with the actual names of your items.