...
Property | Description | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
add_csrf_token_header_to_external_responses |
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 | ||||||||||||||||||||||||||||||||||||||||
channels_using_fallback | Specifies the channel(s) that use the default design configuration when no custom JSP can be found for it. | ||||||||||||||||||||||||||||||||||||||||
clusternode_eventlistener_heartbeat_ms |
Specifies how often, in milliseconds, the cluster event service listens for events on other servers in the cluster. | ||||||||||||||||||||||||||||||||||||||||
clusternode_registration_heartbeat_ms |
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_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 | The root URL of the static web application. | ||||||||||||||||||||||||||||||||||||||||
|
Specifies whether XperienCentral automatically creates revisions of content items. See Reverting a Content Item for more information. See also the settings | ||||||||||||||||||||||||||||||||||||||||
|
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:
| ||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||
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 the Advanced Forms are located. | ||||||||||||||||||||||||||||||||||||||||
google_sitemap_automatic_upload |
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 | 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:
| ||||||||||||||||||||||||||||||||||||||||
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.
| ||||||||||||||||||||||||||||||||||||||||
https_proxy_host |
The name of the HTTPS proxy host server to use to send requests to the XperienCentral server. | ||||||||||||||||||||||||||||||||||||||||
https_proxy_password |
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 |
The port number to connect to on the HTTPS proxy host. | ||||||||||||||||||||||||||||||||||||||||
https_proxy_username |
The username to use on the HTTPS proxy host. | ||||||||||||||||||||||||||||||||||||||||
https_use_proxy |
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_address | For use with IBM WebSphere. Contact your GX Software consultant for more information. | ||||||||||||||||||||||||||||||||||||||||
internal_frontend_address | For use with IBM WebSphere. Contact your GX Software consultant for more information. | ||||||||||||||||||||||||||||||||||||||||
internal_http_authentication_password | The password to use in conjunction with the username (below) for connections XperienCentral makes with itself through the front- or backend. | ||||||||||||||||||||||||||||||||||||||||
internal_http_authentication_username | The username to use for connections XperienCentral makes with itself through the front or backend. | ||||||||||||||||||||||||||||||||||||||||
internal_http_use_authentication | Specifies whether to use a username/password combination for authenticating connections that XperienCentral makes with itself through the front or backend. | ||||||||||||||||||||||||||||||||||||||||
internal_http_use_form_authentication | Specifies 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.
| ||||||||||||||||||||||||||||||||||||||||
limboelement_cleanup_schedule | The 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_interval | The 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_words | Specifies 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_distance | Password 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_entropy | Specifies how complicated a password must be. The allowed values are between 50 and 100, 100 being the most strict setting. | ||||||||||||||||||||||||||||||||||||||||
render_threads | Specifies 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_incontext | Specifies 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_key | The key used to sign configuration. | ||||||||||||||||||||||||||||||||||||||||
secure_rest_against_csrf | Specifies whether XperienCentral protects against CSRF attacks on its REST API.
| ||||||||||||||||||||||||||||||||||||||||
session_tracking_cookie_name | The name of the cookie used for tracking XperienCentral user sessions. | ||||||||||||||||||||||||||||||||||||||||
smtp_host | The host name of the SMTP-server. | ||||||||||||||||||||||||||||||||||||||||
stale_cluster_lock_retry_time | The 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_url | The 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.
| ||||||||||||||||||||||||||||||||||||||||
streaming_file_directory | The folder where streaming files are stored. | ||||||||||||||||||||||||||||||||||||||||
strict_servlet_api | Specifies whether to use the content-type header set by the first included JSP for the entire request. | ||||||||||||||||||||||||||||||||||||||||
url_cache_clean | Specifies the age (in milliseconds) that items can become before they are deleted from the cache. | ||||||||||||||||||||||||||||||||||||||||
url_cache_timeout | Specifies the amount of time (in milliseconds) between cache cleanups. | ||||||||||||||||||||||||||||||||||||||||
url_encoding | The encoding to use for encoding URLs, "UTF-8" for example. | ||||||||||||||||||||||||||||||||||||||||
urlsign_key | The key used to sign URLs. | ||||||||||||||||||||||||||||||||||||||||
weblogging_logfile_location | The location of the web logging log file. | ||||||||||||||||||||||||||||||||||||||||
xss_allowlist_siteworks_expressions |
See XperienCentral XSS Filters (login required). | ||||||||||||||||||||||||||||||||||||||||
xss_allowlist_siteworks_qs_parameters |
See XperienCentral XSS Filters (login required). |
...
Property | Description | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
application_filter_definition_url_base | Specifies the URL where the configuration for external application integration is located. | |||||||||||||
backend_base_url | Specifies the base URL for the backend system. | |||||||||||||
backend_hostname | Specifies the hostname for the backend system. | |||||||||||||
backend_server_alias | The name of the server alias used to reach the XperienCentral back-end. | |||||||||||||
default_contenttype | Specifies the default content type. | |||||||||||||
default_encoding | Specifies the default encoding, for example, UTF-8. | |||||||||||||
default_language | Specifies the default language. | |||||||||||||
default_mail_sender | Specifies the default e-mail sender. | |||||||||||||
default_mail_subject | Specifies the default e-mail subject. | |||||||||||||
| Specifies whether to allow an application server backend container to authenticate users who want to log in to XperienCentral. See also Backend Container-based Authentication. | |||||||||||||
enable_dynamic_user_creation | Specifies whether to create new users in XperienCentral who log in from an application server backend container who don't already exist in XperienCentral. See also Backend Container-based Authentication. | |||||||||||||
enable_email_two_factor_authentication |
Specifies whether XperienCentral's two factor authentication is enabled. | |||||||||||||
enable_external_role_synchronization | Specifies whether to synchronize the roles assigned to a user in an application server backend container with their role(s) in XperienCentral. See also Backend Container-based Authentication. | |||||||||||||
export_directory | Specifies the folder to use for exports. | |||||||||||||
file_backup_directory | Specifies the folder to use for backups. | |||||||||||||
file_browser_directories | Specifies the directories that you can browse through using the File Browser tab (Configuration > System Utilities). To add a directory, follow these steps:
| |||||||||||||
file_download_valid_mime_types | Lists the allowed MIME types for the different types of download files which can be uploaded in the Edit environment. This setting is also used for other uploads in the Edit environment. This setting is not used for uploaded images. Note that these MIME types are not configurable. | |||||||||||||
| Specifies the folder to use for uploads. | |||||||||||||
file_upload_mm_directory | Specifies the folder to use for uploaded multimedia items. | |||||||||||||
file_upload_mm_url | Specifies the URI of the file upload multimedia folder. | |||||||||||||
file_upload_url | Specifies the URI of the file upload folder. | |||||||||||||
| Specifies the local directories where files uploaded by the Interactive Forms Upload form element may be stored. To add a directory, follow these steps:
| |||||||||||||
friendly_url_cache_clear | Specifies the number of milliseconds that transpire before the friendly URL cache is cleared. | |||||||||||||
friendly_url_extension | Specifies the extension to use for friendly URLs (".htm" or ".html"). In XperienCentral versions R36 and higher, you can also leave this field blank which results in friendly URLs that have no extension. See SEO for complete information about search engine optimization in XperienCentral. | |||||||||||||
friendly_url_google_news_id | Specifies whether to assign a Google News ID to the friendly URL of Content Repository articles. | |||||||||||||
friendly_url_lowercase | Specifies whether uppercase characters are allowed in friendly URLs. When this setting is selected, all friendly URLs are converted to lowercase. | |||||||||||||
friendly_url_prefix | Specifies the prefix to use for friendly URLs. See SEO for complete information about search engine optimization in XperienCentral. | |||||||||||||
friendly_url_separator | Specifies the separator to use for friendly URLs. The allowed values are dash (-) or empty. If you configure an invalid character it will be converted to a dash (-). See SEO for complete information about search engine optimization in XperienCentral. | |||||||||||||
friendly_url_setting | Specifies which of the three possible titles that a page/content item can have will be looked at first and used in the friendly URL "urltitle", "navigationtitle", or "title". | |||||||||||||
frontend_hostname | Specifies the host name of the frontend. | |||||||||||||
frontend_https_portnr | Specifies the HTTPS port number for the frontend. | |||||||||||||
frontend_portnr | Specifies the HTTP port number for the frontend. | |||||||||||||
frontend_server_alias | Specifies the aliases to use for the frontend host name. | |||||||||||||
frontend_use_https |
Enables the HTTPS protocol for frontend servers. This setting is especially useful for the preview functionality introduced in XperienCentral R29. | |||||||||||||
generate_https_sitemap_urls | Specifies whether to generate HTTPS URLs for the website's sitemap. | |||||||||||||
handler_url_base | For internal use only. Do not change the default value. | |||||||||||||
identifier | Specifies the identifier for this website. | |||||||||||||
max_image_upload_size |
Specifies the maximum allowable size for uploaded images (backend). | |||||||||||||
oEmbed_enabled | Specifies whether the features of oEmbed that XperienCentral supports are enabled. | |||||||||||||
presentation_jsps_url | Specifies the URL to the design config JSPs for this website. | |||||||||||||
|
Specifies the amount of time, in minutes, that the preview URL for an unpublished content item remains valid. See also Previewing a Content Item. | |||||||||||||
productcatalog_name | Specifies the name of the catalog used by the Product Maintenance component. | |||||||||||||
projectid | For internal use only. Do not change the default value. | |||||||||||||
redirect_base_url | Only to be used for backward comparability with older versions of XperienCentral. Contact your GX Software consultant for more information. | |||||||||||||
redirect_basedirectory | Specifies the redirect base folder. | |||||||||||||
render_form_name_and_id | Specifies whether the name as well as the attribute ID for <form/> tags is rendered. This property is used for web guideline compliance. | |||||||||||||
|
Enables XperienCentral to send visitor statistics related to personalizations to Google Analytics. This functionality requires the XperienCentral Insights Platform. When enabled, this setting adds hidden | |||||||||||||
search_redirect_base | Specifies whether the name as well as the attirbute-ID for <form/>> tags is rendered. This property is used for web guideline compliance. | |||||||||||||
searchresult_replacement | This property is not used. | |||||||||||||
sitestat_url | Specifies the URL for Sitestat. | |||||||||||||
start_object_id | Specifies the identifier of the homepage for this website. | |||||||||||||
static_files_url | Specifies the URI to the static files for this website. | |||||||||||||
use_absolute_urls | Specifies whether to use absolute URLs. | |||||||||||||
use_inline_environment | Specifies whether to use the inline environment. *** wat in godsnaam betekent dit? | |||||||||||||
valid_link_schemes | Specifies the link prefixes that are allowed in hyperlinks in content in XperienCentral. The default prefixes are "http", "https" and "mailto". If your website uses other URL prefixes, you can add them to the allowed link schemes. A link scheme is everything that comes before the colon (:) in a URL (https://www.gxsoftware.com, for example). To add a link scheme, follow these steps:
When you add or delete a link scheme, the change is effective immediately. No restart of XperienCentral or refresh of a browser is necessary.
| |||||||||||||
www_root_directory | Specifies the www root directory. |
...