Common Component Service
We can use the Common Component configuration service to configure the behavior of the common components framework, the enabler widget container and the client side APIs.
- cc.multipart.enabled = true|false
- Whether or not multipart requests can be used for batch processing. This applies to using the enabler client side APIs. The theme uses this primarily during bootstrap when it loads remote data.
- cc.multipart.correlatehosts = true|false
- Whether or not you want hosts in multipart requests to be correlated.
- cc.multipart.pageLoadOptimization
- Optional. Used with user interface components to modify page loading for optimization if required. If you do not specify a value for this property, it defaults to false .
- cc.multipart.pageLoadOptimizationTheme
- Optional. Used with user interface components to modify theme loading for optimization if required. If you do not specify a value for this property, it defaults to false .
- cc.multipart.pageLoadOptimizationAppWidgets
- Optional. Used with user interface components to modify widget loading for optimization if required. If you do not specify a value for this property, it defaults to false .
- cc.theme.context
- Specify the context root of the default theme.
- cc.theme.id
- Specify the ID of the default common component theme.
- cc.enabler.sandboxenabled
- Whether or not the sandbox is enabled. If you have widgets loaded in a sandbox, this means that the widgets are loaded inside an iFrame to keep them from interacting with the other Javascript and DOM resources on the same page.
- cc.enabler.subdomains
- Array of strings with the names of the subdomains used to create sandboxed widgets. iFrames that load sandboxed iWidgets use subdomains to create an alternate domain than the default one so that cross-domain browser security settings are put in place. Specify the subdomains that you have set uthat can be resolved correctly via DNS.
- cc.enabler.serverdomain
- Name of the server domain that we use with the sandbox.
- cc.enabler.useridattribute
- User registry attribute that uniquely identifies users.
- cc.enabler.user.displaynameattribute
- User registry attribute used to display the name of users. This is the attribute on the object that represents a user in the user registry, for example LDAP or otherthat refers to the user's name to display.
- cc.enabler.groupidattribute
- User registry attribute that uniquely identifies groups.
- cc.enabler.group.displaynameattribute
- User registry attribute to is used to display the name of groups.
- cc.enabler.acceptedPagesParentNode
- Specify the navigation node that becomes the parent of shared pages that users accept.
- cc.enabler.remote-cache-expiry
- Number of seconds for the remote expiration time for new pageso that is the amount of time that specifies how long cache entries for newly created pages can be cached.
- cc.page.autowiredefaultenabled
- Whether or not widgets are autowired automatically.
- cc.isDebug = true|false
- Whether you want debugging to be enabled or not.
- cc.traceConfig
- Array of strings used to set client side tracing on user interface components. Use the exact syntax of a Javascript array, including brackets and double or single quoted values for each item. Example: ["com.ibm.mashups.enabler.*","com.ibm.pb.*"]
- cc.productname = product name
- Product name; user interface components such as themes can use the value from this property. Themes or other user interface components can use this to display a global brand name.
For example, in a default portal installation this is used to specify the product display name WebSphere Portal.
- cc.theme.autoEditNewPages = true|false
- Whether you want blank pages to go into edit mode automatically ( true ) or not ( false ).
- cc.theme.alwaysRefreshOnPageSave
- Whether you want the page always to refresh when it is saved ( true ) or not ( false ).
The following list gives the navigational state parameters. Use them to set the configuration for the navigational state model. By default the w (width), h (height), and st (state) attributes are persisted to persistence store and are not included in the URL. The page identifier (PID) of the current page and the space identifier (SID) of the current space are added to the URL. In general all navigational state parameters that are not defined in the parameter navstate.persistence.pstore are added to the URL. This way all widget navigational state parameters are added to the URL.
- cc.enabler.navstate.persistence.url = ['sid','pid']
- Array of strings specifying which attributes of the navigation state are stored in the URL.
- cc.enabler.navstate.persistence.pstore = ['w','h','st']
- Array of strings specifying which attributes of the navigation state are stored in the persistence store.
- cc.enabler.navstate.persistence.url.limit = 10
- How many widgets can store their navigation state in the URL.
- cc.enabler.navstate.persistence.url.splimit = 10
- How many shared parameter sets can be stored through encoding in the URL.
Add new parameters
We can add new parameters by prefixing the key with dyn:, for example:dyn:com.ibm.mashups.someKey = someValue
The new name value pair must be of type string, . Restart the server after adding the new parameter.
Parent: Portal configuration services