Global Config Reference
Global config settings control the behavior of the Content Delivery application.
The following tables provide references for all the global configuration settings.
| Config Name | Description |
|---|---|
| app.language Default Language | Default language for the application user interface. The user interface will be presented in this language to a new visitor. A user can modify his or her preferences in order to select a different language. |
| app.skin UI Skin | The skin used by the application. All user interface resources will be loaded from this skin.
|
| audit.enable | A flag indicating whether the application should record user audit trails. If set to Yes, all user activity will be recorded in an XML audit trail. If set to no, the application will not record any audit trails. |
| analytics.optimization.enable | Enables indexing of the audit collection database, which improves the speed of generating analytics reports. |
| browsers.supported | A list of User Agent keys which identifies supported browsers. |
| cache.data.enable | If set to Yes this flag enables caching of the rendered content within your application. This can increase performance for your users. |
| commenting.polling.freq.secs | An interval indicating the period of time that the browser should wait before polling for new comments while a user is viewing a topic. If new comments are found by the poll, then they will be immediately displayed to the user. This value should not be lowered below 10. |
| commenting.identifiers | A pipe-delimited list of XML attributes used to identify the text or image that the user selects when adding an inline comment. This will control the behavior of inline comment targeting. |
| content.toc.depth | This setting indicates the number of levels of the table of contents to load at a given time. If a given table of contents is deeper than the content.toc.depth, as a user navigates deeper into the structure, additional chunks of the TOC are loaded with AJAX. By setting this value lower, you can control the size of the chunks which are loaded and increase load performance. The recommended value for content.toc.depth is 3. |
| host.id | A unique key to identify this installation of Content Delivery. A unique host.id is generated during installation, but this can be replaced with a human-readable identifier, such as the system hostname. The application's host.id is used to differentiate audit trails and form instances that may have been created across different systems. |
| http.cors | The full web address of the Content Manager web server used for collaborative team editing. Example: https://ish.example.com (where |
| lcde.edit.url | The full web address of the Content Manager web application used for collaborative team editing. Example: https://ish.example.com/ISHCM/ |
| index.binary.formats | The list of binary format types that should be indexed by the application's search engine. |
| pub.session.timeout | Content Delivery session timeout override for Tomcat during publish tasks. When user inactivity is detected in Content Delivery, a publish process may be terminated based on Tomcat's session timeout. This configuration overrides the timeout for publishing. Set to 600 minutes by default. When working with publications including several thousands of topics or more, it is suggested to at least double this number. |
| search.filter.enable | If set to Yes, all searches will take filtering conditions into account. Therefore, search results will check to insure that the terms are not in content sections that would be filtered out based on the current conditions. Setting the flag to Yes can have a negative impact on performance. |
| search.ignore | Lets you choose Content Manager object types (Libraries) to prevent them from appearing in the search results list. These are often (at many sites) conref libraries, which should not be an individual search result. |
| sitemap.changefreq and sitemap.priority | Global values that are used when generating the Sitemap for your application. These can be overwritten by publication and language variant configurations. See Configuring Sitemaps. |
| rss.apikey | An API key that allows access to RSS feeds including a secured system. |
| proxy.url | The full web address of the load balancer that is acting as a proxy for the Content Delivery server. For example: https://lb.lc.example.com/ (where lc refers to an example related to Content Delivery, and lb specifies it further as a load balancing server) |
| proxy.ugc.url | The full web address of the Content Delivery server which will be used as the centralized repository for users, groups, permissions, and all forms including comments. For example: http://contentdelivery.lc.example.com/ (where |
| social.enable | A flag indicating whether the Share links should be shown when a user is visiting publications and topics. If set to Yes, then the Share links to Facebook, LinkedIn and Google +1 will be shown. |
| cache.xsl.enable | A flag indicating whether the application should cache XSL stylesheets used in the skin. This flag should be left as Yes unless a skin developer is actively working on the system to add or modify XSL stylesheets. If set to Yes, then all XSL stylesheets will be cached and reused, which has a major positive impact on performance. If set to No, then any change to a stylesheet in a skin will be picked up immediately and the change will be seen the next time the content is rendered with the XSL. |
The following table provides a reference for all global configuration settings involved in setting up form instances and audit trail aggregation.
| Config Name | Description |
|---|---|
| audit.aggregation.enable | A flag indicating whether the application will aggregate audit trails. If set to Yes, the application will attempt to periodically transfer its local audit trails to the aggregation server, as defined in the audit.aggregation.url setting. |
| audit.garbagecollection.enable | A flag indicating whether the application will eventually delete older audit trails. If set to no, audit trails will be kept indefinitely. If set to Yes (aggregated only), the application will delete audit trails which have been successfully aggregated. If set to Yes (local), the application will delete all audit trails that have passed the age defined in audit.aggregation.age. |
| audit.aggregation.age | Defines the time limit before a local audit is transferred to the aggregation server, if aggregation is enabled. Therefore, if set as the value Week, when an audit trail was more than 7 days old, it would be transferred to the aggregation server. If this time period has passed, and audit.garbagecollection.enable is set to Yes (aggregated), this audit trail will be aggregated and then deleted. If this time period has passed and audit.garbagecollection.enable is set to Yes (all), the audit trail will be deleted without being aggregated. |
| audit.aggregation.key and xforms.aggregation.key | A unique string used to verify the connection between an aggregation client and an aggregation server. When aggregating either form instances or audit trails, the corresponding key is compared between the client and server. If the keys are not the same on the client and server, aggregation will not occur. See Setting Up Audit Trail Aggregation - Server and Setting Up the Forms Aggregation - Server. |
| audit.aggregation.url and xforms.aggregation.url | The URL of the aggregation server. When aggregating either XForm instances or audit trails, the corresponding URL is used by the client to contact the server. These URLs should include the fully qualified domain name, port number, and application context, such as http://aggregation.lc.example.com/ (where lc refers to an example related to Content Delivery, and aggregation specifies it further as a server dedicated to aggregation) See Setting Up Audit Trail Aggregation - Client and Setting Up Forms Aggregation - Client. |
| audit.filters.enable | Filtering can generate a large amount of audit data, which is currently not used in any Analytics reports; therefore, the default setting is disabled. To enable this setting, you must add the audit.filters.enable variable and set its value to true. To disable this setting, either remove the variable or set it to an empty value. |
| xforms.aggregation.enable | A flag indicating whether the application will aggregate form instances. If set to Yes, the application will attempt to periodically transfer its local form instances to the aggregation server, as defined in the xforms.aggregation.url setting. |