Changing the Active or Default Content Repository Connection Using Fusion Middleware Control

Managing Content Repositories 11-43 cache-mapping cache-mapping cache-namebinaryCache.cache-name scheme-nameContentBinaryCachesscheme-name cache-mapping cache-mapping cache-namerepo.ucm.searchCriteriaCache.cache-name scheme-nameContentSearchCachesscheme-name cache-mapping cache-mapping cache-name repo.ucm.indexedFieldsCache.cache-name scheme-nameContentSearchCachesscheme-name cache-mapping cache-mapping cache-namerepo.ucm.securityUserCache.cache-name scheme-nameContentSecurityCachesscheme-name cache-mapping cache-mapping cache-namerepo.ucm.profileTriggerValueCache.cache-name scheme-nameContentProfileCachesscheme-name cache-mapping caching-scheme-mapping caching-schemes -- The following schemes are all local. For a clustered deployment, a distributed, replcated, or other clustered scheme is recommended. See Coherence documentation for more information. -- local-scheme scheme-nameContentNodeCachesscheme-name expiry-delay1mexpiry-delay high-units100high-units local-scheme local-scheme scheme-nameContentTypeCachesscheme-name expiry-delay30mexpiry-delay high-units50high-units local-scheme local-scheme scheme-nameContentBinaryCachesscheme-name expiry-delay1mexpiry-delay high-units100000high-units unit-calculator class-scheme class-namecom.tangosol.net.cache.SimpleMemoryCalculatorclass-name class-scheme unit-calculator local-scheme local-scheme scheme-nameContentSearchCachesscheme-name expiry-delay5mexpiry-delay high-units50high-units local-scheme local-scheme scheme-nameContentSecurityCachesscheme-name expiry-delay10mexpiry-delay high-units50high-units local-scheme local-scheme scheme-nameContentProfileCachesscheme-name 11-44 Oracle Fusion Middleware Administrators Guide for Oracle WebCenter expiry-delay1hexpiry-delay high-units100high-units local-scheme -- class-scheme scheme-nameContentDisabledCachesscheme-name class-namecom.tangosol.util.NullImplementationNullMapclass-name class-scheme -- caching-schemes cache-config Table 11–9 Cache Entries in content-coherence-cache-config.xml Cache Entry Name Description repo.ucm.nodeUidCache . Stores a list of nodes for a repository based on an ID. The size of this cache entry depends upon the number of nodes in the active repository. This cache expires based on when the node data is refreshed and how many times the data is modified from another application. Key - Node UID - String Value - A UCM Node object repo.ucm.nodePathToUi dCache. Stores a list of nodes for a repository based on a path. The size of this cache depends upon the number of nodes in the active repository. This cache entry expires based on when the node data is refreshed and how many times the data is modified from another application. The size and expiration time must be the same as that of nodeUidCache. Key - Node path - String Value - Node UID - String repo.ucm.securityInfo Cache. Stores cached security information for a node. The size of this cache depends upon the number of nodes in the repository. This cache expires based on the frequency of node security data updates. Key - Node UID - String Value - Security information for a node repo.ucm.typeNameCach e. Caches Content Type information. The size of this cache depends upon the number of types in the repository. This cache expires based on when the type information is refreshed and how many times the types are modified from another application. Key - Content Type UID - String Value - A ContentType object repo.ucm.typeNamesCac he. Caches all the type names known to UCM. All type names are cached together one key, and thus all expire at the same time. This cache expires based on the frequency of new types being created or removed. Key - There is only one key to this cache: typeNames Value - An ArrayListString of the type names