Page tree
Skip to end of metadata
Go to start of metadata

Some of the default values for properties configurable on the General tab should not be changed. If you are unsure what the value for a specific property 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 name of the channel.

In This Topic



application_settings


PropertyDescription
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

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,

content_item_lock_poll_intervalA content locking poll thread that checks if 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 contentindex 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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
context_staticThe root URL of the static web application.
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 the Crontab format, see Crontab.
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_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 the Crontab format, see Crontab.
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 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.

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

https_proxy_host

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

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

This setting was introduced in XperienCentral version R26.

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

https_proxy_username

This setting was introduced in XperienCentral version R26.

The username to use on the HTTPS proxy host.

https_use_proxy

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_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 authentication.
jcr_datastore_cleaner_scheduleThe 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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
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 the Crontab format, see Crontab.
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.

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.

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.

Back to top



backend_system_settings


PropertyDescription
ignore_backend_cookiesSpecifies whether to ignore cookies relayed by a frontend proxy to the backend server.
max_charSpecifies the code of the highest ASCII character that XperienCentral will output. The default is "127" (all standard ASCII characters).
max_includes_depthSpecifies the maximum number of includes allowed in a config.
max_includes_per_requestSpecifies the maximum number of includes that are allowed during a single request.
max_recursion_depthSpecifies the maximum depth of includes recursion.
ntlm_auth_domain_controllerSpecifies the IP address of the NTLM authentication server.
ntlm_auth_enabledEnables/disables NTLM authorization.
ntlm_auth_ignore_hostsSpecifies the names of the hosts from which requests will be ignored. Separate multiple host names using a comma (,).
ntlm_auth_ignore_user_agentsSpecifies the user agents that will be ignored.
package_image_urlSpecifies the location where XperienCentral menu-related images are stored.
presentation_jsps_urlThe relative URL of the XperienCentral design config JSPs.
replicate_uploads_on_readonlySpecifies whether to replicate uploaded files on read-only servers in a cluster.
static_files_locationSpecifies the directory where static files are stored (relative to the XperienCentral installation).
user_profiles_export_maxSpecifies the maximum number of user profiles that can be exported in one export file.


Back to top



corsfilter

XperienCentral can send and receive requests from a different domain than the one in which it is running. It does so using the cross-origin sharing standard (CORS). Configure the following properties in order to allow XperienCentral to handle cross domain requests and to control the extent to which it may do so. See http://enable-cors.org/ for complete information on CORS.


CORS support is available in XperienCentral versions 10.14.0 and higher.



PropertyDescription
allowed_http_headersSpecifies the HTTP headers that are allowed to be used in a request. To add an HTTP header, enter it in the text field and then click [Add value]. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS for a list of the supported HTTP headers.
allowed_http_methodsSpecifies the HTTP methods that are allowed to be used in a request. To add an HTTP method, enter it in the text field and then click [Add value]. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS for a list of the supported HTTP methods.
allowed_originsSpecifies the URIs that may access XperienCentral. For requests that do not contain credentials, you can add "*" (without quotes) as a wildcard which will allow any origin to access the resource. To add an origin URI, enter it in the text field and then click [Add value].
exposed_headersSpecifies the header(s) that a server can whitelist in order to allow a browser to access the resource.
preflight_max_age"Preflighted" requests send an HTTP request to the resource on the other domain in order to determine whether the actual request is safe to send. Specify the value, in seconds, for how long the response to the preflight request can be cached without sending another preflight request.
support_credentialsSpecifies whether requests can be made using credentials.


Back to top



development_settings


PropertyDescription
enable_debug_messagesSpecifies whether to log debug information.
enable_view_resolve_cacheSpecifies whether to cache the views of the Workspace. Caching the views improves performance.


Back to top



file_distribution_settings


PropertyDescription
max_file_size_mbSpecifies the maximum allowed size of a static file, in megabytes for files added to an XperienCentral deployment (Download element, etc.).


Back to top



forms_config_set


PropertyDescription
forms_exportimport_dirSpecifies the directory used by the Interactive Forms component to store temporary import and export files.


Back to top



formsengine_config_set



formsengine_autotrim_valuesSpecifies whether to strip any leading or trailing white space from values entered in forms.
formsengine_check_referrerSpecifies whether forms can be submitted from unrecognized servers. GX Software recommends that this option be selected as an extra safeguard against CSRF attacks.
formsengine_clear_errors_on_back

This setting was introduced in XperienCentral version 10.22.0.

Specifies whether to clear error messages from a form session if the visitor clicks the [Back] button. For example, consider the following scenario:

  • A visitor fills in the fields in step 1 of a form and submits it.
  • On step 2, the visitor does not fill in a required field and submits the step. An error message appears informing the visitor that a required field has not been filled in and they do not proceed to step 3.
  • The visitor clicks the [Back] button and returns to step 1.
  • The visitor resubmits step 1 and proceeds to step 2.

With this option enabled, the visitor will not see an error message on step 2. With this option disabled, the visitor will see the error message upon returning to step 2.

formsengine_prehandling_cachetimeoutTo ensure good performance for interactive forms, a cache is maintained that defines where they are located. This setting defines the number of seconds that the interactive forms cache lasts.
formsengine_prehandling_check_blocksSpecifies whether to prehandle forms on page sections. Because the creation of the prehandling cache can have a negative effect on performance, GX Software recommends that this setting be switched off unless you need to prehandle forms on page sections.
formsengine_prehandling_check_mediaitemsSpecifies whether to prehandle Content Repository items on page sections. Because the creation of the prehandling cache can have a negative effect on performance, GX Software recommends that this setting be switched off unless you need to prehandle Content Repository items on page sections.
formsengine_prehandling_check_pagesSpecifies whether to prehandle forms on pages. Because the creation of the prehandling cache can have a negative effect on performance, GX Software recommends that this setting be switched off unless you need to prehandle forms on pages.
formsengine_session_cleaner_thread_intervalSpecifies the number of seconds between which a check will be done to see whether there are any timed out form sessions. This setting is tied to the following setting (forms_session_timeout).
formsengine_session_timeoutSpecifies the amount of time, in minutes, after which an Interactive Forms session will time out if a website visitor remains idle. For example, if a website visitor starts filling out a form and proceeds through one or more steps and then does nothing, the session will time out after the specified number of minutes. The visitor will be redirected to a "session expired" page when he or she attempts to proceed further after a timeout has occurred.
formsengine_uploaddirSpecifies the temporary directory where uploads in Interactive Forms are stored.



Back to top



frontend_system_settings


PropertyDescription
allow_cacheEnables/disables caching in the XperienCentral frontend.
cache_cacheable_response_codesA comma-separated list of cacheable response codes. The default is "200" (successful response from the server). Only codes that denote an immediate successful response should be entered.
cache_directoryThe folder where the files containing cached content is stored.
cache_directory_depthThe maximum depth that the folder tree used for caching can reach. The recommended value is 3.
cache_max_stale_timeThe number of seconds that the frontend will serve an old version of a page from the cache while the page is being regenerated by the backend. The recommended value is 0.
cache_number_of_directoriesThe maximum number of subfolders that will be created for the caching directory structure. The recommended value is 30.
cache_statement_timeoutSpecifies the number of seconds between queries from the frontend to ensure the validity of cached content.
cache_timestamp_expireThe maximum number of seconds that a query to the Timestamp database is allowed to take. If there is no response from the database within this time period, the cached version of the page is returned. The recommended value is 2.
crawler_useragentContact your GX Software consultant for information on setting this property.
definition_url_baseThe base URL of the forms definitions.
form_upload_directoryThe folder where uploads are temporarily stored.
friendly_url_datasourceThe datasource to use for friendly URLs.
friendly_url_extensionThe extension to use for friendly URLs. See SEO for complete information on XperienCentral's search engine optimization.
ignore_user_agentIndicates whether the user agent should be ignored.
log_event_type_factoryFor internal use only. Do not change the default value.
log_file_charsetSpecifies the character set used to encode log files (UTF-8 for example).
max_upload_sizeThe maximum allowed file size, in bytes, for uploads. The default is 10 MB.
proxy_cached_read_timeoutThe number of milliseconds that the proxy waits for a response from the backend. If the backend doesn't respond within the specified time, the cached version of the page is returned. The recommended value is 10000.
proxy_connect_timeoutThe number of milliseconds that the proxy waits for a successful connection to the backend. If the connection cannot be made within the specified time, the cached version of the page will be returned. The recommended value is 30000.
proxy_ip_numberFor internal use only. Do not change the default value
proxy_max_concurrent_requestsThe maximum allowable number concurrent requests to the proxy server.
proxy_number_of_threadsThis property is not used.
proxy_read_timeoutThe number of milliseconds the proxy waits for an HTTP response. The recommended value is 120000.
proxy_retry_timeoutDetermines the number of milliseconds that the proxy will wait after retrying a page request. The recommended value is 10000.
redirect_disallowedSpecifies whether to allow redirects.
redirect_encodingThe encoding to use for redirects (UTF-8, for example).
registration_forwardbaseThe base URI for registration forms.
timestampfetcher_classnameSpecifies the name of the alternative class to use to fetch timestamps.


Back to top



search_settings


PropertyDescription
date_format_parameterSpecifies the format to use for dates (dd-MM-yyyy, for example).
from_parameterSpecifies the "from" parameter to use when results are shown (for example, "From x to y").
maxSpecifies the maximum number of results to show.
order_by_parameterSpecifies how results are ordered.
query_parameterSpecifies the name of the query to use for searches.
scopeSpecifies the location where the XperienCentral internal search engine temporarily stores search results. The valid values are "session" and "request". "Session" means that the search results are stored for the duration of the user's XperienCentral session or until the results have been overwritten by a subsequent search. "Request" means that the search results are only stored for the duration of the current request. For best performance results, you should use "Session" for search results that return multiple pages for a limited number of sessions. If the server handles multiple requests over time, "Request" should be used.
search_serviceThe RMI URL for the Search Service.
to_parameterSpecifies the "to" parameter to use when results are shown (for example "From x to y".


Back to top



startup_settings


PropertyDescription
base_directorySpecifies the base folder for application data.
config_filenameSpecifies the location of the XperienCentral configuration file that determines which license components you have purchased.
contextSpecifies the context path. This is the path that appears directly after the base URL of the home page of the website, /web for example.
use_distributed_siteworksSpecifies whether to use distributed Siteworks.
wcb_directorySpecifies the folder to use for deploying plugins.


Back to top



system_constants


PropertyDescription
cleansite_locationSpecifies the location of the "clean" website that is initially imported when XperienCentral is first run.
config_filenameSpecifies the location of the configuration.xml file that contains XperienCentral settings.
element_controller_uriFor internal use only. Do not change the default value.
file_controller_uriSpecifies the URI of the file controller.
form_handler_uriSpecifies the URI of the form handler.
gettext_uriSpecifies the URI of the gettext servlet.
login_redirect_uriSpecifies the URI of the login redirect.
mediaitem_controller_uriSpecifies the URI of the mediaitem controller.
page_controller_uriSpecifies the URI of the page controller.
panel_controller_uriSpecifies the URI of the panel controller.
redirect_servlet_uriSpecifies the URI of the redirect servlet.
registration_code_servlet_uriSpecifies the URI of the registration code servlet.
search_filter_uriSpecifies the URI of the search filter.
show_servlet_uriSpecifies the URI of the show servlet.
showobject_servlet_uriSpecifies the URI of the showobject servlet.
showobject_servlet_uri_closed_areaSpecifies the URI of the showobject servlet for closed area.
sphtml_servlet_uriSpecifies the URI of the SPHTMLservlet.
spring_mvc_controller_uriSpecifies the URI of the Spring MVC controller.


Back to top



website_settings


PropertyDescription
application_filter_definition_url_baseSpecifies the URL where the configuration for external application integration is located.
backend_base_urlSpecifies the base URL for the backend system.
backend_hostnameSpecifies the hostname for the backend system.
backend_server_aliasThe name of the server alias used to reach the XperienCentral back-end.
default_contenttypeSpecifies the default contenttype.
default_encodingSpecifies the default encoding, for example, UTF-8.
default_languageSpecifies the default language.
default_mail_senderSpecifies the default e-mail sender.
default_mail_subjectSpecifies the default e-mail subject.

enable_backend_container_filter

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

This setting was introduced in XperienCentral version R24.2.

Specifies whether XperienCentral's two factor authentication is enabled.

enable_external_role_synchronizationSpecifies 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_directorySpecifies the folder to use for exports.
file_backup_directorySpecifies the folder to use for backups.
file_browser_directoriesSpecifies the directories that you can browse through using the File Browser tab (Configuration > System Utilities). To add a directory, follow these steps:
  1. Add the fully qualified path to the directory in the text field next to [Add value].
  2. Click [Add value]. The new directory is added.
  3. Click [Save Changes] to save the change.
  4. To delete a directory, select the "Delete" checkbox to the right of the directory and then click [Save Changes].
file_download_valid_mime_typesLists 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 and flash files. These MIME types are not configurable.
file_upload_directory
Specifies the folder to use for uploads.
file_upload_mm_directorySpecifies the folder to use for uploaded multimedia items.
file_upload_mm_urlSpecifies the URI of the file upload multimedia folder.
file_upload_urlSpecifies the URI of the file upload folder.

file_upload_valid_directories

Specifies the local directories where files uploaded by the Interactive Forms Upload form element may be stored. To add a directory, follow these steps:
  1. Add the fully qualified path to the directory in the text field next to [Add value].
  2. Click [Add value]. The new directory is added.
  3. Click [Save Changes] to save the change.

To delete a directory, select the "Delete" checkbox to the right of the directory and then click [Save Changes].
friendly_url_cache_clearSpecifies the number of milliseconds that transpire before the friendly URL cache is cleared.
friendly_url_extensionSpecifies the extension to use for friendly URLs (".htm" or ".html"). See SEO for complete information about search engine optimization in XperienCentral.
friendly_url_google_news_idSpecifies whether to assign a Google News ID to the friendly URL of Content Repository articles.
friendly_url_lowercaseSpecifies whether uppercase characters are allowed in friendly URLs. When this setting is selected, all friendly URLs are converted to lowercase.
friendly_url_prefixSpecifies the prefix to use for friendly URLs. See SEO for complete information about search engine optimization in XperienCentral.
friendly_url_separatorSpecifies the separator to use for friendly URLs. See SEO for complete information about search engine optimization in XperienCentral.
friendly_url_settingSpecifies 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_hostnameSpecifies the host name of the frontend.
frontend_https_portnrSpecifies the HTTPS port number for the frontend.
frontend_portnrSpecifies the HTTP port number for the frontend.
frontend_server_aliasSpecifies the aliases to use for the frontend host name.
generate_https_sitemap_urlsSpecifies whether to generate HTTPS URLs for the website's sitemap.
handler_url_baseFor internal use only. Do not change the default value.
identifierSpecifies the identifier for this website.
oEmbed_enabledSpecifies whether the features of oEmbed that XperienCentral supports are enabled.
presentation_jsps_urlSpecifies the URL to the design config JSPs for this website.
productcatalog_nameSpecifies the name of the catalog used by the Product Maintenance component.
projectidFor internal use only. Do not change the default value.
redirect_base_urlOnly to be used for backward comparability with older versions of XperienCentral. Contact your GX Software consultant for more information.
redirect_basedirectorySpecifies the redirect base folder.
render_form_name_and_idSpecifies whether the name as well as the attribute ID for <form/> tags is rendered. This property is used for web guideline compliance.

render_personalization_markers

Personalization markers were introduced in XperienCentral version 10.15.0.

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 <div> tags which contain data personalization attributes needed by Google Analytics to personalized content. The only information sent to Google Analytics is the name of the personalization.

search_redirect_baseSpecifies whether the name as well as the attirbute-ID for <form/>> tags is rendered. This property is used for web guideline compliance.
searchresult_replacementThis property is not used.
sitestat_urlSpecifies the URL for Sitestat.
start_object_idSpecifies the identifier of the homepage for this website.
static_files_urlSpecifies the URI to the static files for this website.
use_absolute_urlsSpecifies whether to use absolute URLs.
use_inline_environmentSpecifies whether to use the inline environment.
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:
  1. Enter the link scheme in the text field next to the [Add value] button.
  2. Click [Add value]. The link scheme is added.

To delete a link scheme, follow these steps:
  1. Select the "Delete" check box to the right of the link scheme.
  2. Scroll to the bottom of the "General" tab and click [Save Changes]. The link scheme is deleted.

When you add or delete a link scheme, the change is effective immediately. No restart of XperienCentral or refresh of a browser is necessary.


System Administrators and Application Managers: In general, it is a good idea to communicate to your users of XperienCentral which link schemes are acceptable.



www_root_directorySpecifies the www root directory.


Back to top



wmasolrsearch


PropertyDescription
clearrestSpecifies whether to clear all "remaining URLs" from the search index.
config_directory

Specifies the name of the directory where the Solr search directories are located.

Note: You can override the default XperienCentral Solr configuration. Perform the following steps in order for the modifications to the Solr configuration files to be applied and saved:

  1. Start XperienCentral.
  2. Create a new directory for the Solr configuration files.
  3. Copy the directory <xperiencentral-root>/work/searchengine/conf/core0/conf to the directory you created in the previous step.
  4. Modify the configuration file(s) as desired in the new directory.
  5. Add the Solr directory that you created above to the property "config_directory" in the "wmasolrsearch" section (above).
  6. Click [Save Changes] in the Setup Tool.
  7. In the XperienCentral Workspace, navigate to the Plugins dialog (Configuration > Plugins).
  8. Stop and restart the plugin "wmasolrsearch".

If after performing the steps above you modify the override configuration files in the directory set as config_directory, you must perform the following steps for them to take effect:

  1. Modify the configuration file(s) as desired in the config_directory.
  2. In the XperienCentral Workspace, navigate to the Plugins dialog (Configuration > Plugins).
  3. Stop and restart the plugin "wmasolrsearch".
crontabscheduleThe Crontab schedule that dictates when the search index 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 the Crontab format, see Crontab.
fullindexSpecifies whether to generate the entire index instead of just the pages that have been added/changed.


Back to top








Write a comment…