...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Redirects
Alias redirects route URL requests for nonexistent URLs to a valid target URL. The target URL for an alias redirect can be a page in the current web initiative(s) as well as an external URL. Redirects allow you to make available simple, easy to remember URLs to direct visitors to pages on your website in cases where your tree structure is complicated or the target URL contains a difficult to remember path structure. URL aliases can only be a single identifier that contains no hierarchical structure. The address of the alias URL is relative to the root URL of your website. For the website www.gxsoftware.com,, for example, any alias URL you create can only be reached in a browser via a URL that adds the identifier to the root address, www.gxsoftware.com/<alias> for example, where <alias> is an identifier such as "Products", "Services", "Developer Support" and so forth.
...
- Select the checkbox to the left of the redirect that you want to delete.
- Click [Delete]:
The redirect is deleted.
...
...
Dumped Content
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 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:
...
| Info |
|---|
The extension given to the dumped HTML file should be different from the extension of the friendly URLs. Apache determines, based on a fixed pattern in the URL, where the page data should come from. By default, Apache transfers those URLs beginning with |
For performance reasons, XperienCentral will always use the static variant of a page if one exists. For example, a page with the title "Economy" has the corresponding friendly "Economy.htm" URL and is also dumped to "Economy.html". When "Economy" is requested, XperienCentral will refer to "Economy.html" because it can be loaded faster. Requests to "Economy.htm" will also work but the response could be somewhat slower because the web server has to generate the page.
...
- Navigate to Configuration > Server Configuration.
- Click the [Dumped Content] tab:
- In the "Description" field, enter a description for the page you want to dump.
- Click [Apply]. Fields for specifying the name of the page and how often it should be dumped appear.
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.
- In the "Filename" field, specify the name of the HTML file.
- In the "Time" field, enter the number of minutes and seconds after which XperienCentral will create a new static version of the page.
- 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.
- 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):
...
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.
...
| Detail | Description |
|---|---|
| Minimum | The "Minimum" date entry shows the oldest timestamp in the database for an object of that type. For example, if the "Minimum" date for "Pages and page sections" is 2/28/2014, then the oldest timestamp for a page or page section is that date. This allows you to monitor the oldest date of a page or page section and gives you the option of manually updating it if you find it too old. |
| Maximum | The date shown as the "Maximum" reflects the newest timestamp in the database for an object or set of objects. |
| Update from | Specifies the beginning of the date period an object's timestamp must be to schedule it for an updated timestamp. |
| Update to | Specifies the end of the date period an object's timestamp must be to schedule it for an updated timestamp. |
Updating the Timestamps
To immediately update the timestamps to the current date and time, click the [Update Timestamps] next to the specific content type. When this action is performed, each content item will be regenerated and placed in the cache the next time it is requested. If your website contains a large number of the specific type that you update, use caution because this action could put a large load on the server.
...
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 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.
Initializing the Cache
...
| 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 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. |
...
...