This post focuses on helpful configuration settings that developers can leverage in their Oracle Site Studio environments. This post is part of a blog series exploring best practices to consider when planning for and building a Site Studio website. Unlike my Getting Started with Site Studio post, for this series, I’m assuming you’re already working and fairly familiar with Site Studio - which is part of the Oracle WebCenter Content (WCC) offering.
The information below details some of the optional Site Studio global configuration settings that can be used. Configuration changes are made from the General Configuration page of the Admin Server in the Additional Configuration Variables text box.
Note that if you choose to use any of the configuration settings below, a restart of Oracle Content Server is required.
This entry is optional, but recommended. It improves the responsiveness of queries performed by Site Studio Designer and Contributor.
If you are having browser performance issues by contributors using the Contributor application and have a lot of editable elements per contribution region, then this config entry can be used to control when the element editors are loaded (i.e., either automatically upon opening of the Contributor application, or manually by clicking on the element). For example, if this entry is set to 4, then if 4 or more elements exist in the contribution region, then an element's editor will not load until the contributor manually clicks on it. Default value is 6.
If you are having browser performance issues by contributors using the Contributor application and have a lot of placeholders on a page, then this config entry can be used to control when the menus for those placeholders are generated. Each placeholder menu involves DOM manipulation and therefore the more placeholders that exist, the greater the CPU utilization. When set to true, a placeholder's menu will only be generated once it is manually clicked on. The default value is true, so if you see this config flag set to false and are having Contributor performance issues then you may wish to set it to true.
By default, the Content ID (dDocName) is the page identifier in URL’s. Since dDocName values have some restrictions in length, a custom metadata field can be used to provide the URL page name for data files and native documents.
For example, if you have a custom metadata field called xUrlPageName, add the following config entry:
Site Studio will then take the file portion of the URL and perform a search for a content item containing this value in its xUrlPageName metadata field. If no managed item is found, a database table lookup is performed for a content item containing this value in its dDocName (Content ID) metadata field. So even if you use the SSUrlFieldName config variable, the dDocName is always available as a URL page name component. It's important that unique values are entered in the metadata field.
The default page name of a section is index.htm. If you wish to change that, use the SSUrlPageNames entry to specify a comma-separated list of page names you want to support. Using this config entry will make it so that you do not have to manually set the page name for each section of the web site.
For example, SSUrlPageNames=index.html,default.html,home.html
If this variable is not present or is set to "false", then access to the Contributor application is allowed. This variable should be set to “true” on a production Consumption server, and not present or set to “false” on a Contribution server. Default value is false.
For additional information on Site Studio configuration variables, refer to section 12 (Site Studio Configuration Flags) of Oracle's Site Studio Technical Reference Guide.