...
| Table of Contents | ||
|---|---|---|
|
...
Architecture and Overview
...
You can find most of the caching settings in the frontend_system_settings section of the General tab of Setup Tool. The relevant cache options are:
| Parameter | Description |
|---|---|
| Enables/disables caching in the XperienCentral frontend. |
| Specifies the URL where the configuration for external application integration is located. |
| A 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. |
| The folder where the files containing cached content is stored. |
| The maximum depth that the folder tree used for caching can reach. The recommended value is 3. |
| The 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. |
| The maximum number of subfolders that will be created for the caching directory structure. The recommended value is 30. |
| Specifies the number of seconds between queries from the frontend to ensure the validity of cached content. |
| The 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. |
Caching Optimization in the Edit Environment
...
For debugging purposes it might be necessary to look at the timestamps more closely. Timestamps are stored in the XperienCentral external database in the following seven tables:
| Table | Description |
|---|---|
| Used for database detail pages. Timestamps are identified by the "dbid" parameter. |
| Used for all databases. Timestamps are identified by the database ID. |
| Used for discussion timestamps. Timetamps are identified by the thread ID. |
| Used for Content Repository items. Timestamps are identified by media repository content ID. |
| Used for an Content Repository of a web initiative. Timestamps are identified by web initiative ID. |
| Used for various XperienCentral objects such as pages and page sections. Timestamps are identified by object ID. For pages this is also the ID in the URL of a page, for example |
| Used for Content Repository terms. When terms are changed they could influence content overviews so they have their own table. Timestamps are identified by term ID. |
...
Performance Checklist
...