Managing Content Caching

This chapter describes caching in the Content Management (CM) subsystem and includes these topics:

About caching in CM

Several CM elements are cached by default while an exteNd Director application is running. Caching can increase the efficiency of an application (because the application makes fewer SQL queries of the database).

For most of these elements, you can configure your exteNd Director EAR to override the default settings for caching.

NOTE: If you make any changes to the caching settings, you must redeploy your exteNd Director EAR for the changes to take effect.

Summary of CM caching information

Caching behavior

The table below provides the following information on caching behavior for several elements of documents in the CM subsystem:

Element—The name of the CM element
CM API object name—The com.sssw.cm.api interface name that corresponds to the CM element
CM cache holder used—The name of the cache holder used for the element
Default behavior—The default caching behavior for the element

Setting in the CM config.xml file—The setting to change to alter the default behavior

For more information For information, see the section on reconfiguring your EAR project in Developing exteNd Director Applications.

Element	CM API object name	CM cache holder used	Defaultbehavior	Setting in CM config.xml
Extension metadata fields	EbiDocField	ContentMgmtService/-CacheHolder/Fields	Cached	com.sssw.cm.cacheFields
Document types	EbiDocType	ContentMgmtService/-CacheHolder/DocTypes	Cached	com.sssw.cm.cacheDocTypes
Folders	EbiDocFolder	ContentMgmtService/-CacheHolder/Folders	Cached	com.sssw.cm.cacheFolders
Categories	EbiDocCategory	ContentMgmtService/-CacheHolder/Categories	Cached	com.sssw.cm.cacheCategories
Document metadata	EbiDocument	ContentMgmtService/-CacheHolder/Documents	Always cached	None
Document contents	EbiDocContent	None	Never cached	None
Document content versions	EbiDocVersion	None	Never cached	None

Caching of folders, categories, and document metadata

Folders, categories, and document metadata, when cached, are cached by both UUID and URL.

Document metadata is always cached.

About document content and versions

Document contents and versions of document content are not cached, because some cached content might require excessively large amounts of memory.

Controlling caching in the DAC

Another place you can control the caching process is on the Cache tab of the Configuration section of the DAC. For example, you can flush a single cache or all caches at once. This can be helpful when you are doing diagnostic work on a running exteNd Director application.

For more information on controlling caching in the DAC, see the discussion of the Cache tab in Developing exteNd Director Applications.