Page Comparison

...

...

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.

The validity of the string that forms the identifier is dependent on the operating system on which XperienCentral is running. When an alias redirect is created, a new directory is created on the file system of the server in this location: <xperiencentral-root>\webmanager-webapps\webmanager-static-webapp\target\webmanager-static-webapp-xx, where "xx" is the version of XperienCentral you are running. The name of the directory matches the name of the alias that you create. For example, if you create an alias URL named "Products", then you would see the following folder created in the path listed above:

 
Image Modified

The name of the alias URL you create must be a valid directory or folder name for the operating system in which XperienCentral is running.

To create an alias redirect, follow these steps:

1. Navigate to Configuration > Server Configuration.
2. Click [Redirects].
   
   
   Image Modified
   
   
   
3. Click [Add Redirect]. The "Add Redirect" section appears.
   
   Image Modified
   
   
   
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:
   
   
   Image Modified
   
   
   
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:
   
   Image Modified
   
   
10. Click [Apply]. The redirect is added.
11. Click [Dump now] to complete the operation. For example:
    
    Image Modified
    
    
12. Click [Apply]. The alias redirect is added to the list.

Deleting a Redirect

To delete a redirect, follow these steps:

1. Select the checkbox to the left of the redirect that you want to delete.
2. Click [Delete]:
   
   Image Modified
   
   
   The redirect is deleted.

Back to top

...

Dumped Content

...

For each object type in XperienCentral, the following caching details are shown:

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

Back to top