Page Comparison

...

1. Navigate to Configuration > Server Configuration.
2. Click [Redirects]. The "Redirects" tab displays:
   
   
   
   
   
   
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 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 web initiative, 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.

...

In XperienCentral, you can save static versions of dynamic web pages to disk in a process known as "dumping". When you dump a page, a static HTML file containing the page's contents is created. There is a speed advantage for pages that have been dumped because XperienCentral does not have to generate the content for a page when it is requested. You can set how often a static variant of a page should be is saved to disk (for instance, once every two minutes). Often the home page of a website is dumped because it is the most visited page and therefore has the highest number of requests. Pages that have been dumped with the extension ".html" are processed by the Apache web server:

...

1. Navigate to Configuration > Server Configuration.
2. Click the [Dumped contentContent] tab:
   
   
   
   
   
   
   
3. In the "Description" field, enter a description for the page you want to dump.
4. Click [Apply]. Fields for specifying the name of the page and how often it should be dumped appear.

5. In the "Relative URL" field, enter the friendly URL for the page, for example /GX/Contact.htm.
   
   

   Note
   The relative URL that you specify must match the friendly URL listed under "URLs used by active versions" in the "SEO" tab of the Properties Widget.

6. In the "Filename" field, specify the name of the HTML file.
7. In the time "Time" field, enter the number of minutes and seconds after which XperienCentral will create a new static version of the page.
8. Select "Yes" for "Active" if you want the page to be dumped every x minutes and x seconds as specified in the time field. Select "No" if you want to dump the page only one time.
9. Click [Dump now]. The page will be dumped immediately.

Thereafter, the page will be dumped every x minutes and y seconds that you specified if "Active" is set to "Yes". (every 2 minutes in the example below). For each page, the last time the page was dumped is always indicated. For example:

Back to top

...

Caching

Caching is essential for high traffic websites. It will handle the load created by the many page requests by using an intelligent mechanism that returns pages without having to regenerate them completely. The XperienCentral caching module is also tailored to not interfere with interaction and personalization, therefore visitors to your site will not notice that they are looking at a largely static website.

This topic explains how the Caching tab options available in the Server Configuration panel works. For a complete discussion of caching in XperienCentral, see Caching.

...

There are more complex situations, for example when several page sections are involved or situations where a lot of caching timeouts are set for individual parts of a page or when the load on the server is very high and there's no time to regenerate pages. Content is normally regenerated automatically, however, in some situations, you do not want to wait until a visitor requests the content, but instead you want to manually force all the content to be regenerated.

...

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 frontend front-end 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.

...

...