Bookshelf Home | Contents | Index | Search | PDF

Siebel Analytics Web Administration Guide > Administering Siebel Analytics Web >

Managing the Siebel Analytics Web Cache Settings

---

The entries described in this section are available for managing the Siebel Analytics Web cache:

• Specifying The Maximum Amount of Time an Entry Can Exist
• Specifying the Least Amount of Time an Entry Can Exist
• Specifying the Least Amount of Time an Entry Can Exist After Use
• Specifying the Maximum Number of Open Record Sets

The cache is accessed when users make requests in Siebel Answers. This is not the same cache that is accessed by the Analytics server. You can change the internal defaults by modifying the Windows registry or the Siebel Analytics Web configuration file instanceconfig.xml to add the following entries.

For information about working in the Windows registry or the configuration file instanceconfig.xml, see Making Siebel Analytics Web Configuration Changes.

Specifying The Maximum Amount of Time an Entry Can Exist

You can override the maximum amount of time, in minutes, that an entry in the cache can exist before it is removed. The internal default is 60 (one hour).

Depending on (the number of requests being run, an entry may be removed before the time limit expires.

NOTE:  The setting for CacheMinUserExpireMinutes, described in Specifying The Maximum Amount of Time an Entry Can Exist, can force an entry for a particular user to exist for a longer time than that specified by CacheMaxExpireMinutes.

• Windows registry example:

  HKEY_LOCAL_MACHINE\SOFTWARE\Siebel Systems, Inc.\Siebel Analytics\Web\7.7

  CacheMaxExpireMinutes     "60"

• instanceconfig.xml example:

  <CacheMaxExpireMinutes>60</CacheMaxExpireMinutes>

Specifying the Least Amount of Time an Entry Can Exist

You can override the minimum amount of time, in minutes, that an entry in the cache can exist before it is removed. The internal default is 10.

• Windows registry example:

  HKEY_LOCAL_MACHINE\SOFTWARE\Siebel Systems, Inc.\Siebel Analytics\Web\7.7

  CacheMinExpireMinutes     "10"

• instanceconfig.xml example:

  <CacheMinExpireMinutes>10</CacheMinExpireMinutes>

Specifying the Least Amount of Time an Entry Can Exist After Use

You can override the minimum amount of time, in minutes, that an entry in the cache can exist after it has been viewed by a user. The internal default is 10.

For example, suppose CacheMaxExpireMinutes is set to 60 minutes. If a user views the entry during the 59th minute, the entry exists for that user for an additional 10 minutes. This allows the user to continue paging through the data without requiring a new request to be run.

• Windows registry example:

  HKEY_LOCAL_MACHINE\SOFTWARE\Siebel Systems, Inc.\Siebel Analytics\Web\7.7

  CacheMinUserExpireMinutes     "10"

• instanceconfig.xml example:

  <CacheMinUserExpireMinutes>10</CacheMinUserExpireMinutes>

Specifying the Maximum Number of Open Record Sets

You can override the maximum number of open record sets that Siebel Analytics Web keeps open at any one time. The internal default is 10. The minimum value is 3. For systems under significant loads, you can increase this value to 500 or 1000.

• Windows registry example:

  HKEY_LOCAL_MACHINE\SOFTWARE\Siebel Systems, Inc.\Siebel Analytics\Web\7.7

  CacheMaxEntries     "100"

• instanceconfig.xml example:

  <CacheMaxEntries>100</CacheMaxEntries>

Bookshelf Home | Contents | Index | Search | PDF