Digital Data Connector caches

IBM Digital Data Connector provides the caches listed here.framework.

Both social rendering and the DDC framework use the following caches to cache bean list information:

com.ibm.workplace.wcm.pzn.plr.BeanListCache

The bean list cache caches the bean list Java objects the Digital Data Connector plug-ins return. The DDC plug-ins control the cache key generation for the individual entries and whether the bean lists are automatically removed from the cache during user login. By default, this cache is enabled.

com.ibm.workplace.wcm.pzn.plr.xml.DocumentCache

The document cache is used by the generic XML DDC plug-in for caching the Document Object Model (DOM) objects for individual source URIs. This cache specifically the DOMs for associated item attributes. If an individual associated item attribute is flagged as shared in the list-rendering profile, the cache entries are shared between different users. Such shared documents do not get invalidated on user login. Documents that are loaded through non-shared associated item attributes are cached separately per user. These cache entries are automatically invalidated during login. By default, this cache is enabled.

com.ibm.workplace.wcm.pzn.plr.ListRenderingCache

The list-rendering cache caches the markup that a specific appearance component generates for a specific bean list instance. If we enable this cache, updates in the appearance component might not become visible immediately, as updates to the corresponding Web Content Manager design components do not invalidate this cache. In general, the entries in this cache are invalidated together with the corresponding bean list objects in the bean list cache listed earlier in this topic. As a result, it is good practise to disable this cache on authoring systems and enable it on delivery systems.

To use this cache, use the ListRenderingCache rendering plug-in to instrument the WCM design components involved in the markup generation for this cache. For more information, read Use the list-rendering cache.

We configure the caches through the WP Cache Manager Service resource environment provider in the WAS console. For more information, read the Portal service configuration and Setting service configuration properties.

Parent Digital Data Connector cache tuning

Related tasks:

Set service configuration properties

Related reference:

Portal service configuration