EP: KM – Cache Management
As we know the Enterprise Portal and a NW enviornment provide our end-users with an centralized point of access to all vital organizational data, information and applications. With broad, diverse business operations Portal enviornments and system landscapes can play host to a wide range of different data flows.
If you have experience with the Enterprise Portal you will be aware that there are a wide range of different caches in association to it’s operation such as the:
- Navigation Cache
- HTTP Provider Cache
- Browser Cache
- FPN Cache
- KM Cache
KM Folders are utilized as the base platform in which KM Documents are stored. For example through KM End-Users can access, obtain, manage and review data information through documents sourced from the business intranets, external WWW feeds, and file servers. The KM Documents themselves are presented in the standard formats of PPT, excel, word documents and html.
Knowledge Management Cache Management
Due to Knowledge Managements heavy association to documents & system repositiories the involvement of caches is of heavy importance (as is their subsequent management).
Utilizing the “Cache Monitor” provides you with a means of overviewing current Cache Operations of system flow:
- To call up the Cache Monitor, choose System Administration → Monitoring → Knowledge Management → Cache Monitor.
Many caches are used in Knowledge Management in order to ensure that the system performs well. It is important that you configure the caches correctly after they have been created initially.
For an overview on the caches (their relationships) along with the recommended value settings + the means of changing values kindly see the documentation guides outlined below:
All KM caches can be configured through the following:
- System Administration > System Configuration > KM > CM > Utilities > Caches > Memory Cache
An important point to highlight here is not to confuse instances of KM Caches with the cache itself. For example if you highlight and notice entries such as
- documents_RID_ca_cm (1)userhome_NODE_ca_cm (1),
- userhome_PROP_ca_cm (1)
- userhome_RID_ca_cm (1)
In true essence these are instances of the ca_cm cache and if you check the configuration of the /documents or /userhome repositories, you will see that the ca_cm cache is being used.The entries highlighted on the cache monitor relate to the individual separate components for this cache for each repository which is using it.
If there are multiple repository managers using the ca_cm cache, it is not possible to configure the cache differently across each repository manager. You can configure the ca_cm cache but it will be the same configuration for all of these repository caches which are all actually part of this cache.
To summarize you can configure the ca_cm cache and then those changes will effect all the cache entries as you will see in the ‘cache monitor’ which end in ‘ca_cm’. It’s not possible to configure each of these individually as they’re all created from the one cache.