If a user requests recommendations before the sifter has found mentors for that user, the Preference Engine checks the cache for mentors for the user. Set span translate"0"enginstancename.db.engine.tune.maxcachedmentorsspan to the number of potential mentors which it should ...

The list of archetypes is kept in the cache for a specified number of uses before it is reloaded. To change the number of users, set span translate"0"enginstancename.db.engine.tune.maxarchetypelistusespan . The default is 100000. For example: {code:35670} ...

Personalization uses the WebSphere® Application Server Dynamic Cache service to cache the results of select rules and to cache the rules themselves in a DistributedMap. When publishing, importing or saving rules, the cache is flushed automatically to ensure that the site is current.

Use the export cache settings task to display a summary of the current cache settings of your system.

You can apply caching to elements by using "connect" tags to reference elements within presentation templates instead of the component or element tag.

You use "cache" parameters in IBM® Web Content Manager tags and URLs to specify whether the retrieved data should be cached or not, and if so, how it should be cached. The "cache" parameter is not mandatory.

You can overrule the default caching parameters of a site by using "cache" and "expire" parameters in URLs and IBM® Web Content Manager tags.

You use the "expires" parameter in IBM® Web Content Manager tags and URLs to specify how long to maintain data in the cache before it is expired. Once data expires from a cache, the next request for the data will be retrieved from the original server. The expires parameter is not ...

The WSRP implementation in the portal uses expirybased markup caching for remote portlets to improve performance. This reduces the number of interactions between the Consumer and the Producer and enables the use of remote caches for pages containing remote portlets. You can disable this feature ...

If a user requests recommendations before the sifter has found mentors for that user, the Preference Engine checks the cache for mentors for the user. Set span translate"0"enginstancename.db.engine.tune.maxcachedmentorsspan to the number of potential mentors which it should ...

Personalization uses the WebSphere® Application Server Dynamic Cache service to cache the results of select rules and to cache the rules themselves in a DistributedMap. When publishing, importing or saving rules, the cache is flushed automatically to ensure that the site is current.

The list of archetypes is kept in the cache for a specified number of uses before it is reloaded. To change the number of users, set span translate"0"enginstancename.db.engine.tune.maxarchetypelistusespan . The default is 100000. For example: {code:35670} ...

Replication is a service provided by IBM® WebSphere® Application Server that transfers data, objects, or events among application servers. Data replication can be used to make data for session manager, dynamic cache, and stateful session beans available across many application servers in a ...

The WSRP implementation in the portal uses expirybased markup caching for remote portlets to improve performance. This reduces the number of interactions between the Consumer and the Producer and enables the use of remote caches for pages containing remote portlets. You can disable this feature ...

If a user requests recommendations before the sifter has found mentors for that user, the Preference Engine checks the cache for mentors for the user. Set span translate"0"enginstancename.db.engine.tune.maxcachedmentorsspan to the number of potential mentors which it should ...

Personalization uses the WebSphere® Application Server Dynamic Cache service to cache the results of select rules and to cache the rules themselves in a DistributedMap. When publishing, importing or saving rules, the cache is flushed automatically to ensure that the site is current.

The list of archetypes is kept in the cache for a specified number of uses before it is reloaded. To change the number of users, set span translate"0"enginstancename.db.engine.tune.maxarchetypelistusespan . The default is 100000. For example: {code:35670} ...

This article demonstrates the rationale for and benefits of using anonymous pages as well as a process for configuring IBM WebSphere Portal, IBM Web Content Manager, and the Web server to provide maximum performance.

This article describes how to use portlet fragment caching for the Web Content Viewer (JSR 286) Portlet. Configuration of caching policy and id generation are outlined and an example cachespec.xml is provided for further adjustment.

WebSphere Personalization (PZN) uses many different types of caching. There are three main different types of caching, Internal Cache, Resource Domain, Visibility Rule Caching. Internal cache, resource domain are covered in the Best Practices for using Personalization ( ...

Learn about the different caching strategies that can improve performance of IBM® Lotus® Web Content Management. The PDF also includes examples and other reference material. Lotus Web Content Management Caching and Performance Tuning presentation

Page visibility rules and unreachable Search results Author: Paul Kelsey, pkelsey@us.ibm.com Introduction There are 2 primary ways to control a users' view into their Portal Server: Portal Acces

Workplace Web Content Management caching, servlet caching (dynamic cache service), and prerendering are tools you can use to improve the performance of Workplace Web Content Management Web sites. Although prerendering is the fastest option, it has limitations. Determining which cache to use ...