Versions Compared

Key

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

neral

Anchor
top
top
In the Server Configuration panel you can configure settings related to URL redirects, caching, and static content. The settings/commands described in this topic that have an effect on the performance of your XperienCentral website(s) are just a small subset of the complete set available in XperienCentral. See the Setup Tool for all of the other settings that you can configure for your installation. To reach the Server Configuration panel, navigate to Configuration > Server Configuration in the XperienCentral Workspace.

...

  1. Navigate to Configuration > Server Configuration.
  2. Click [Redirects].





  3. Click [Add Redirect]. The "Add Redirect" section appears.




  4. In the "Name" field enter the internal name of the alias. This name is descriptive and only used to identify the alias URL in XperienCentral.
  5. In the "Alias URL" field, enter the string for the alias. The alias can include spaces but no special characters. The string can but does not have to 't include an extension such as .htm or .html and likewise can be just the alias string or the string preceded by a forward slash (/home for example).
  6. To select a page in the current channel, click [Choose URL]. The Advanced Search dialog box appears. For example:





  7. Select the page to assign as the target URL and then click [Select].
  8. To assign an external address as the target URL, enter the fully qualified address in the "Target URL" field.
  9. Set the frameset option. Selecting "Yes" means that the alias URL will appear in the browser's address bar. Selecting "No" means that the target URL will not appear in the browser's address bar. For example:



  10. Click [Apply]. The redirect is added.
  11. Click [Dump now] to complete the operation. For example:



  12. Click [Apply]. The alias redirect is added to the list.

...

To update the timestamps for all content types on your website, click [Update Timestamps] next to "General Timestamp". Updating the timestamps in this manner is a relatively safe action to perform on all environments. After activating the "General Timestamp", requests from the front-end frontend trigger two actions. The first action is that the requested content is directly served from the cache without first being updated. The second action is that the backend is requested to regenerate the content in the background. When this has finished, the cache is updated with the latest version of the content.

...

Warning

GX Software strongly recommends that you do not use this command on production environments. This command immediately sets the timestamp for all content (pages, articles, database objects, etc). If you have a site with a lot of content, this process could take a long time and will put a heavy load on the server. The effect of executing this command is that each request on the front-end frontend may not be served from the cache, which leads to a request on the backend. In most cases, this has a negative impact on the performance of your website(s) and on the XperienCentral Workspace.

...