Knowledge Management Configuration
To modify the standard installation of Knowledge Management (KM) in line with your system environment, you have to make small changes to the configuration data. Depending on your usage scenario, you may have to make more significant changes to other technical components, such as the user interface, in line with other needs.
As an integrated solution, the KM configuration is based on technical components of the portal infrastructure. The portal system landscape is used to access servers with user mapping.
Knowledge Management uses the user management functions of SAP NetWeaver Application Server for Java (AS Java) as provided by the User Management Engine (UME). KM uses the Configuration Manager of AS Java to store central configuration data. For more information, see Configuration Manager .
The configuration framework for KM makes use of the AS Java locking mechanism and the AS Java cache management infrastructure.
For more information about the AS Java locking mechanism, see Locking in AS Java: Architecture .
For more information about the AS Java cache management infrastructure, see Cache Management System .
You have carried out the initial configuration for KM. For more information, see Basic Configuration for Knowledge Management .
Technical Components
You can modify the following KM technical components in the portal using the Configuration iView:
|
Technical Components |
Configuration Scope |
Description |
|
Protocols |
Low |
Protocols provide only one protocol - WebDAV. The WebDAV protocol is configured by default for accessing documents. For more information, see WebDAV Protocol . |
|
Repository Managers |
Medium |
Repositories are used for storing and/or retrieving content and metadata. The KM standard configuration uses several internal repositories that are controlled system internally. They are used for storing and staging various content and metadata and for navigating in this data. These repositories are preconfigured and preactivated in the KM standard configuration. You do not normally need to modify their configuration. In addition to the internal repositories, you can integrate additional external repositories into KM, such as WebDAV or file system repositories. You can establish a connection to these repositories by configuring appropriate repository managers. For more information, see Repositories and Repository Managers . |
|
Repository Filters |
Low |
Used for editing content and metadata. Most of the repository filters contained in the KM standard configuration are content filters that are used when resources of particular MIME types are displayed in the browser. Most filters have already been preconfigured. If you store documents in repositories you created yourself, you have to enter the repositories in question into the configuration of certain filters, such as the XML forms repository filter. For more information, see Repository Filters . |
|
Repository Services |
Low |
Repository services provide functions for repositories. All repository services are preconfigured in the KM standard configuration. In contrast to the global services, you must explicitly assign the services to the repositories in which you want to use them. Generally, you do not need to change the configuration settings of the repository services. For more information, see Repository Services . |
|
Global Services |
Low to Medium |
Used system-wide in KM. Global services provide generic functions that can be used with any repository. They are preconfigured and preactivated in the KM standard configuration. For more information, see Global Services . |
|
Utilities |
Low |
Deliver enhancing functions for services and applications. You can change existing configuration objects and create new ones. For example, you can carry out the following actions:
For more information, see Utilities . |
|
User Interface |
High |
KM offers a flexible user interface for navigating in repositories. You can use parameters to modify the explorer that you use to navigate in folder hierarchies, the results list, and parts of the Details dialog box. For more information, see User Interface . |
|
Form-Based Publishing |
Low |
You can make some settings for form-based publishing with the XML Forms Builder , including setting the availability of forms. For more information, see Form-Based Publishing . |
Configuration Data
Configuration data is stored in the following locations:
-
In the database
-
On the portal server in a directory hierarchy that is accessible through the /etc repository
Configuration Framework
The configuration framework for KM stores and manages configuration parameters. It manages the deployment, persistence, retrieval and update of KM configurations. KM configuration data which is managed by the configuration framework is packed in configuration archives and contains meta information, such as what services should be started at runtime, which repositories should be active and so on.
The access to the KM configuration framework is managed by the Config Framework Service. The Config Framework Service is an AS Java service which implements the service start and stop methods and provides access to the configuration framework. You can change the value of the online modifiable properties of the service using the SAP NetWeaver Administrator. For more information, see Modifying Config Framework Service Properties .
Central Configuration Data
The central configuration data is managed by the configuration framework and stored in XML form in the database. Data models for the parameter settings of configurable components are defined in XML and DTD files. You edit this data in the portal using a separate iView.
The deletion of SAP default configuration data is not supported. You can delete only custom configuration data.
Backing Up and Restoring Central Configuration Data
For more information about backing up and restoring existing KM configuration data, see SAP Note
1571384 
.
Configuration Data in the /etc Repository
The file system hierarchy at /usr/sap/<SAP System ID>/SYS/lobal/config/cm/etc is structured on the /etc file system repository manager and is therefore accessible from KM in the portal. It contains configuration data and user-defined configuration data for CM.
Other subdirectories of the /etc repository contain configuration and data for applications and services in various formats. They contain stylesheets for content filters ( etc/filter) and form-based publishing ( etc/xmlforms), for example. You can usually edit this data with an ASCII text editor.
You should restrict access permissions to much of the
/etc repository's content. For more information, see SAP Note
599425
Configuration iView
The Configuration iView is a front-end client for the configuration framework that manages KM configuration data. The iView presents a navigation hierarchy that gives you access to all configurable components. Mandatory parameters of configuration objects are indicated by a red asterisk. For more information, see KM Configuration iView .
Navigation Hierarchy in the Configuration iView
The configuration framework implements a folder schema that facilitates the integration of new configurable services and applications. The folder structure is reflected in the navigation hierarchy of the Configuration iView.
A folder represents a set of configuration data and resource bundles that pertain to a functional domain, such as repository managers or communication channels.
A folder can contain multiple configuration classes (classes of configuration objects). The repository manager folder comprises several repository manager classes: CM repository manager, file system repository manager, WebDAV repository manager and so on. You set up repository managers in your environment by specifying configuration objects based on configuration classes.
In the navigation hierarchy of the Configuration iView, some folders contain not only configuration classes but also other functionally-related folders. For example, the repository manager folder contains a folder for registering the systems accessed by Web repository managers (Web Sites).
Hot Reload
Many components support hot reload and can therefore be configured dynamically. However, for some parameter changes you have to restart the servlet engine in order to activate the new or changed settings. Parameters that require a restart are displayed on the user interface with the symbol
.
Valid Character List for IDs
You can use alphanumeric characters and certain special characters ( -_!~\)($,:@+ ) when specifying IDs in the configuration.
Length of Property Values
The length of the property values can be up to 25 000 characters.
History
The Configuration iView provides a history display that you can use to call up configuration objects that you have already opened during your current session in the portal. To call up the history, choose History from the menu bar of the Configuration iView.
Use this function when configuring the flexible user interface, for example.
Validity Check
In special cases, you might not use the Configuration iView to edit the configuration data stored in the database. However, you should consult with SAP first. To check this configuration data, use the validity check function in the Configuration iView. To start a validity check, choose
Actions 
Check Configuration 
. Invalid configuration data is displayed in a list. You can then call up and correct this data from the Configuration iView.
Overview of Instances
The overview table of configuration objects includes eight instances by default. If a configuration object has more than eight instances, you can navigate using the arrow symbols. Use the Objects Per Page selection box to define the number of instances to be displayed per page. You can display 8, 16, 32, or all instances.
Filtering the Overview Table
Some configuration objects have several hundred instances. You can use a filter function to call up a particular instance quickly. In the input field above the overview table for a configuration object, enter the name or a part of the name of the instance you are looking for, and choose Apply Filter . The overview table then only displays instances whose names match your filter entry.
Displaying All Objects
In the configuration of an object, several options may be available for a parameter. These options are depicted in a table. If the table has more than eight entries, you can use the arrow symbols to navigate. To display all entries in the table, choose Show all objects (link next to the table).
Use the Configuration iView to configure Knowledge Management in the portal. To call up the configuration objects, choose
System Administration System Configuration in the portal. Then choose
Knowledge Management Content Management in the detailed navigation pane.
Note that the path to the configuration objects is often specified from the Configuration iView in the documentation below. The path specification always begins with Content Management . Do not confuse this path specification with the tab page of the same name in the top-level navigation area of the portal.