Some of the default values for settings configurable on the General tab should not be changed. If you are unsure what the value for a specific setting should be, contact your GX Software consultant. In a multi-channel configuration, each channel has its own configuration set with the name <configuration_set_name> (name) where "name" is the ID of the channel.

In This Topic

application_settings

Property Description

add_csrf_token_header_to_external_responses

This setting was introduced in XperienCentral version R33.

When enabled, an X-CSRF-Token header is included in the response to GET requests from external domains, which must be used in a subsequent POST or PUT request. The exposed_headers and allowed_http_headers settings in the corsfilter section (below) must also be set to "X-CSRF-Token". See /wiki/spaces/PD/pages/24718337 for more information.

authorization_lockout_ip_whitelist

A list of IP's that can not be locked out of XperienCentral's Edit environment. Enter a valid IPv4 or IPv6 address.

channels_using_fallback Specifies the channel(s) that use the default design configuration when no custom JSP can be found for it.

check_url_signature If this option is turned on, URL's containing a presentation ID and/or an SSI object ID are suffixed with a sign parameter when they are rendered, which contains a hash of the parameters in the URL. When the URL is called, the value of the sign parameter is checked versus a newly calculated hash based on that URL. If the value of the sign parameter does not match that of the newly calculated hash, that means that the URL has been tampered with and the request will be refused.

clusternode_eventlistener_heartbeat_ms

This setting was introduced in XperienCentral version 10.22.1.

Specifies how often, in milliseconds, the cluster event service listens for events on other servers in the cluster.

clusternode_registration_heartbeat_ms

This setting was introduced in XperienCentral version 10.22.1.

Specifies how often, in milliseconds, the cluster event service checks for multiple active sessions for the same XperienCentral user. See Active Sessions for more information,

company_name

This setting was introduced in XperienCentral version R42.

This setting allows you to add your company name (or another string) to the XperienCentral Login page. See Customizing the Login Page for complete information. In XperienCentral versions R47 and higher, the company_name text supports basic HTML formatting tags such as <b>, <i>, <u>, <ol>, <ul> and <pre>.

contentindex_index_readonly_nodes

This setting was introduced in XperienCentral version R37.

If the Search & Retrieve API is used on a clustered environment, this setting should be enabled, otherwise the API will not return any results. When this setting is enabled, the content index must be rebuilt.

content_item_lock_poll_interval A content locking poll thread that checks whether a content item lock is expired. If so, the lock is removed. The value is in milliseconds.

content_item_lock_timeout Specifies the number of milliseconds that have to elapse after a lock on a content item has been claimed before the lock is closed.

contentindex_location The directory where the content index and its configuration are stored.

contentindex_optimize_schedule The Crontab schedule that dictates when the content index is optimized. This should be set to happen at least once a day, preferably at the time that website activity is at its lowest (typically at night).The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

contentindex_queue_database_entries_schedule The Crontab schedule that dictates when to put database entities in the queue for the search indexing. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

contentindex_queue_empty_reindex Specifies whether to disable the regeneration of the full background index when the queue is empty. Because a full index regeneration is performed regularly according to the contentindex_queue_reindex_schedule, you might want to block a full index generation at other times for performance reasons.

contentindex_queue_iteration_limit The maximum batch size for each poller iteration. The default is 100. The larger the number, the greater the impact is on performance.

contentindex_queue_janitor_schedule The Crontab schedule that dictates when the index journal is cleaned up. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

contentindex_queue_poller_schedule The Crontab schedule that dictates when the index journal is polled for changes. The more frequently this is performed, the more up to date the index will be. Note that each cycle must be able to finish before the next begins. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

contentindex_queue_reindex_schedule The Crontab schedule that dictates the triggering of a full background index. This should happen no more then once a day, preferably at the time that website activity is at its lowest (typically at night). The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

context_static

This setting was removed from XperienCentral in version R36. Use the setting application_settings.static_files_url instead.

The root URL of the static web application. In XperienCentral versions R36 and higher, use the setting static_files_url instead.

create_content_revisions

This setting was introduced in XperienCentral version R29.

Specifies whether XperienCentral automatically creates revisions of content items. See Reverting a Content Item for more information. See also the settings max_age and schedule.

csrf_ignore_url_paths_regex

This setting was introduced in XperienCentral version R33.1.

Specifies the URL paths that are not checked for CSRF vulnerabilities. Define the excluded URLs using a Regular Expressions that matches the URL path, excluding the context path. For example, to disable the protection for all requests to "myservlet" (https://mydomain.com/web/myservlet/foo/bar?q=xxx), add an expression like the following:

/myservlet(/.*)?

Exempting URLs from the CSRF checks weakens the security of your channel(s), therefore you should exercise caution with this setting.

current_rollover_detector_schedule The Crontab schedule that dictates when the rollover detector service runs. The detector service detects changes in the outcome of ContentItem.getCurrent(Language) and if any is detected, it updates the caching timestamps and friendly URLs. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

date_format The format in which dates are represented (for example, dd-MM-yyyy).

default_timezone

Specify the default time zone for the XperienCentral installation. The time zone you specify is the absolute time upon which all timestamps in XperienCentral are based (creation date, publication date, expiration date, etc.). When users select their own time zone in My Settings, the time zone they select is calculated as an offset based on the default XperienCentral time zone. The following are the most commonly used time zones. For the full list of acceptable time zones, see http://en.wikipedia.org/wiki/List_of_tz_database_time_zones.

Time Zone	Value
Amsterdam	Europe/Amsterdam
Berlin	Europe/Berlin
Istanbul	Europe/Istanbul
London	Europe/London
Lisbon	Europe/Lisbon
Moscow	Europe/Moscow
Atlantic time	Canada/Atlantic
Eastern time	America/New_York
Central time	America/Chicago
Mountain time	America/Edmonton
Pacific time	America/Los_Angeles
Alaska time	America/Anchorage
Hawaiian time	America/Hawaii
India	Asia/Calcutta
China	Asia/Shanghai
Japan	Japan
Western Standard time	Australia/Perth
Central Standard time	Australia/North
Lord Howe Standard time	Australia/LHI

disable_unused_content_schedule

Schedule in cron format for the disable unused content job. The Crontab schedule for disabling unused content. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning.For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

enable_non_jndi_database_configuration Select this option if you are using a non-JNDI database for your XperienCentral project.

form_handler_base Specifies the URL where the definitions for Interactive Forms are located.

google_sitemap_automatic_upload

This setting was introduced in XperienCentral version R33.

Specifies whether XperienCentral automatically uploads generated sitemaps to Google. When enabled, if a Google sitemap is generated, it is automatically uploaded according to the schedule configured in the setting google_sitemap_generator_schedule. When disabled, the latest generated sitemap is not uploaded.

google_sitemap_excluded_types

Specifies the content type(s) to exclude from your generated google sitemap. To see which content types are present in your channel, execute the following query on the Queries tab in the Database Maintenance panel:

SELECT value FROM wmjellycontenttype

The results show the content type identifiers. To exclude a content type, enter its identifier in the text field and click [Add value].

google_sitemap_generator_schedule The Crontab schedule that dictates when the Google sitemap will be generated. The Crontab schedule used is a variant of the standard UNIX Crontab scheduler with a "seconds" field prefixed to the beginning. For complete information on scheduling jobs in XperienCentral, see Scheduling Jobs.

http_non_proxy_hosts

Specifies the hosts that should be directly contacted for requests via HTTP and HTTPS (not through the proxy server). You can enter multiple host names separated by the pipe character (|) and also use wildcards. For example:

*.wm.com|localhost

Notes

This setting also applies to HTTPS requests even though the name of the setting suggests that it only applies to HTTP requests. This has to do with how Java itself is structured. See Networking Properties (Oracle documentation).
If you use a proxy, GX Software recommends that you always add the host names of the XperienCentral front-end and backend servers to this list.

http_proxy_host The name of the HTTP proxy host server to use to send requests to the XperienCentral server.

http_proxy_password The password to use to log in to the proxy host via HTTP. If no password is required, leave this field blank.

http_proxy_port The port number to connect to on the HTTP proxy host.

http_proxy_username The username to use on the HTTP proxy host.

http_use_proxy

Specifies whether to use one or more proxy servers to log in to the XperienCentral server.

Beginning in XperienCentral R26, proxy system properties set outside of XperienCentral are no longer overwritten when this setting is clear (false).

https_proxy_host