Versions Compared

Old Version 44

changes.mady.by.user Matthew Wagner

Saved on

compared with

New Version 45

changes.mady.by.user Matthew Wagner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PropertyDescription
add_csrf_token_header_to_external_responses


Panel
borderColor#0081C0
titleColor#0081C0

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 Security Guidelines for Developers for more information.

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


Panel
borderColor#0081C0
titleColor#0081C0

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


Panel
borderColor#0081C0
titleColor#0081C0

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,

content_item_lock_poll_intervalA 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_timeoutSpecifies the number of milliseconds that have to elapse after a lock on a content item has been claimed before the lock is closed.
contentindex_locationThe directory where the contenti ndex and its configuration are stored.
contentindex_optimize_scheduleThe 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_scheduleThe 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_reindexSpecifies 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_limitThe 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_scheduleThe 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_scheduleThe 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_scheduleThe 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_staticThe root URL of the static web application.

Anchor
create_content_revisions
create_content_revisions
create_content_revisions


Panel
borderColor#0081C0
titleColor#0081C0

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



Panel
borderColor#0081C0
titleColor#0081C0

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(/.*)?


Warning

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


current_rollover_detector_scheduleThe 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_formatThe 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 ZoneValue
AmsterdamEurope/Amsterdam
BerlinEurope/Berlin
IstanbulEurope/Istanbul
LondonEurope/London
LisbonEurope/Lisbon
MoscowEurope/Moscow
Atlantic timeCanada/Atlantic
Eastern timeAmerica/New_York
Central timeAmerica/Chicago
Mountain timeAmerica/Edmonton
Pacific timeAmerica/Los_Angeles
Alaska timeAmerica/Anchorage
Hawaiian timeAmerica/Hawaii
IndiaAsia/Calcutta
ChinaAsia/Shanghai
JapanJapan
Western Standard timeAustralia/Perth
Central Standard timeAustralia/North
Lord Howe Standard timeAustralia/LHI


enable_non_jndi_database_configurationSelect this option if you are using a non-JNDI database for your XperienCentral project.
form_handler_baseSpecifies the URL where the definitions for the Advanced Forms are located.
google_sitemap_automatic_upload


Panel
borderColor#0081C0
titleColor#0081C0

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_generator_scheduleThe 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

Note
titleNotes
  • 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 frontend and backend servers to this list.


http_proxy_hostThe name of the HTTP proxy host server to use to send requests to the XperienCentral server.
http_proxy_passwordThe password to use to log in to the proxy host via HTTP. If no password is required, leave this field blank.
http_proxy_portThe port number to connect to on the HTTP proxy host.
http_proxy_usernameThe 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.

Note

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


https_proxy_host


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R26.

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

https_proxy_password


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R26.

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

https_proxy_port


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R26.

The port number to connect to on the HTTPS proxy host.

https_proxy_username


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R26.

The username to use on the HTTPS proxy host.

https_use_proxy


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R26.

Specifies whether to use one or more proxy servers to log in to the XperienCentral server. Proxy system properties set outside of XperienCentral are not overwritten when this setting is clear (false).

internal_backend_addressFor use with IBM WebSphere. Contact your GX Software consultant for more information.
internal_frontend_addressFor use with IBM WebSphere. Contact your GX Software consultant for more information.
internal_http_authentication_passwordThe password to use in conjunction with the username (below) for connections XperienCentral makes with itself through the front- or backend.
internal_http_authentication_usernameThe username to use for connections XperienCentral makes with itself through the front or backend.
internal_http_use_authenticationSpecifies whether to use a username/password combination for authenticating connections that XperienCentral makes with itself through the front or backend.
internal_http_use_form_authenticationSpecifies whether internal HTTP connections use HTTP form
jcr_datastore_cleaner_schedule

The Crontab schedule that dictates when the JCR datastore cleaner runs. 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.

Info

Beginning in version R28, XperienCentral no longer uses the Apache Jackrabbit JCR indexing solution by default. This topic is only relevant to users of XperienCentral versions R27 and lower. See the XperienCentral upgrades notes for version R28 for more information.


limboelement_cleanup_scheduleThe Crontab schedule that dictates when limbo elements are 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.
limboelement_expiration_intervalThe Crontab schedule that dictates when limbo elements expire and are deleted. 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.
password_banned_wordsSpecifies the string(s) that may not be used as passwords. To add a new value, enter the string in the text field and click [Add value].
password_min_distancePassword minimum distance. Specifies the extent to which a string to be used as a password must differ from any of the banned passwords. Take the following example: the string "Administrator" is banned as a password. If the minimum distance is 2, then the allowed strings to be used as a password must differ in at least two ways from "Administrator". The password "Administrat0r" (using a zero "0" instead of an "o") is unacceptable because it differs in only one way from "Administrator".
password_min_entropySpecifies how complicated a password must be. The allowed values are between 50 and 100, 100 being the most strict setting.
render_threadsSpecifies the number of parallel threads to use when rendering content on the website frontend. If the content on your website does not change at a high rate, it is recommended that you do not set this value too high.
render_threads_incontextSpecifies the number of parallel threads to use when rendering content on the website backend. Using multiple threads can significantly increase the performance of rendering content in the Editor.
secret_keyThe key used to sign configuration.
secure_rest_against_csrf

Specifies whether XperienCentral protects against CSRF attacks on its REST API.

Note

This setting should always be on (selected).


session_tracking_cookie_nameThe name of the cookie used for tracking XperienCentral user sessions.
smtp_hostThe host name of the SMTP-server.
stale_cluster_lock_retry_timeThe amount of time, in seconds, that indicates that a lock that a server in a clustered environment has for a particular item is no longer valid.
static_files_urlThe URL where static files from plugins are stored.
statistics_cycle_duration

Specifies the number of milliseconds into the past that the XperienCentral performance statistics are saved. The minimum value is 10000. The default is 7200000 (2 hours). GX Software advises that you do not set the cycle duration to a value lower than the default value.

Note

Setting this property to a high value, such as 6 hours or more, will naturally have an effect on how long the page takes to load. The statistics can be viewed by navigating to the Statistics Administrative Page.


streaming_file_directoryThe folder where streaming files are stored.
strict_servlet_apiSpecifies whether to use the content-type header set by the first included JSP for the entire request.
url_cache_cleanSpecifies the age (in milliseconds) that items can become before they are deleted from the cache.
url_cache_timeoutSpecifies the amount of time (in milliseconds) between cache cleanups.
url_encodingThe encoding to use for encoding URLs, "UTF-8" for example.
urlsign_keyThe key used to sign URLs.
weblogging_logfile_locationThe location of the web logging log file.
xss_allowlist_siteworks_expressions


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R29.3.

See XperienCentral XSS Filters (login required).

xss_allowlist_siteworks_qs_parameters


Panel
borderColor#0081C0
titleColor#0081C0

This setting was introduced in XperienCentral version R29.3.

See XperienCentral XSS Filters (login required).

...