WCM scoped settings for virtual portals
WCM configuration settings can be scoped for individual virtual portals.
- Log in to the WAS console and click...
Resources | Resource Environment | Resource Environment Providers | WCM WCMConfigService | Custom properties
If the WCM server is part of a cluster, use the dmgr console.
- Add a configuration setting for each virtual portal that requires unique configuration settings. We can this for either the host name or context path:
- Host name:
vp.uniquename.hostname=ExistingVPHost
- Context path:
vp.uniquename.context=ExistingVPContext
- To add a scoped configuration settings for a virtual portal, use this format:
PropertyKey.vp.uniquename=override_value
This setting will override the property key in the virtual portal specified in the unique name.
- Restart the server or cluster.
Example
Create a scoped configuration for virtual portal "vpfoo"...
vp.foo.context=vpfoo
For that scoped configuration, set value for subscriber status...
deployment.subscriberOnly.vp.foo=true
If the base configuration for a setting is different from all the virtual portals, it is more efficient to use a base override setting...
enable.base.portal.overrides=true
To add a setting just for the base portal, add ".base" to the end of the parameter name. For example, if we use the default setting...
deployment.subscriberOnly=true
...we can add another setting named...
deployment.subscriberOnly.base=false
...that will be applied to the base portal only. All the virtual portals will use the default value of...
deployment.subscriberOnly=true