Repository Services
Knowledge Management offers a number of services that can be used with individual repositories. In contrast to global services, repository services must be explicitly registered with the repositories that are to make use of them.
The functions of the various repository services are of a more or less general nature. For example, the property service enables KM applications to store application properties with the resources of a repository. This in turn is a prerequisite for other services such as the (global) classification service, or the rating service, both of which need to store application properties. An example of a more specific repository service is the feedback service, which makes feedback functions available for the content of a given repository.
If you want to use a repository service in a specific repository, you must specify the name of the repository service in the Repository Servicesparameter of that repository's definition (see Repositories and Repository Managers ).
The table below gives an overview of the repository services that are available in KM (in brackets is the technical name under which the corresponding service is listed in the Repository Servicesparameter for a repository manager):
Overview of Repository Services in the Standard Delivery
| Repository Service | Description |
|---|---|
|
Application Property Service (properties) |
This service is required by every application or service that stores application properties with resources. It is a prerequisite, for example, for document classification, the rating service, or the access statistics service (read-flag). |
|
Archiving Property Service (archprop) |
Sets the archiving status as a property for the main KM resource of the KMC archiving object. The archiving property service is activated by default. |
|
(lastaccess) |
Gathers information about the read accesses to the resources for the needs of the archiving process. |
|
Service ACL service (svc_acl) |
Enables repository services to assign user permissions that are specific for certain repository services (for example, "delete subscription"). |
|
Access Statistics Service (accessstatistic) |
Stores user-specific data about access to content and generates a user-specific read flag for documents. Note that the access statistics service requires the application property service. This service cannot be configured. |
|
Subscription Service (subscription; subscription_collaboration) |
Enables users to keep track of changes to documents and folders. |
|
(tbp) |
Enables users to define a time frame during which documents are published (visible). Note that the time-dependent publishing service requires the application property service. This service cannot be configured. |
|
State Management Service (statemngt) |
Enables documents to be processed according to their current status, for example, in approval workflows. Note that the status management service requires the service ACL service and the application property service. |
|
Layout Service (layout) |
This service is used to store and manage layout profiles and to display thumbnail views of the various layout profiles. This service cannot be configured. |
|
Enables the following functions:
|
|
|
Allows users to move resources to a wastebasket and to restore them from there. |
All available repository services are preconfigured in the standard configuration. In most cases, you do not need to change its configuration. To call up the overview for repository services, choose Content Management → Repository Services from the Configuration iView.
You need to select a repository service in the configuration of the repositories with which you want to use the service.