Knowledge Management
First Steps
The Knowledge Management capabilities of SAP NetWeaver offer you a central, role-specific point of entry to unstructured information from various data sources in the portal.
This section provides information about the administration and maintenance of Knowledge Management in the Enterprise Portal (EP) usage type. You can find information in it about the different administrative tasks and the associated tools. In addition, this section also points you to further documentation that you require for performing these tasks.
Tools
You use the following tools to administrate and monitor Knowledge Management:
Tool |
Task |
Configuration iView |
Presents a
navigation hierarchy that gives you access to all configurable components. See
(
|
For managing indexes for searching and classifying documents. |
|
Displays the status of objects and allows you to identify configurations with errors. The component monitor shows you an overview of all nodes of a load-balancing environment with their assigned scheduler tasks. Choose Services → Scheduler in the component monitor. If a task is not assigned to a node, a red symbol is displayed. If this is the case, check the configuration of the corresponding task. |
|
Displays statuses and statistics for active caches and allows you to empty caches manually. |
|
Displays information on the active crawlers and allows you to control them. |
|
Returns information on the status of current indexing processes. |
|
Displays error messages, warnings, and information generated by KM applications and services. This information is not logged in the J2EE Engine log. |
|
|
You can use reports to perform analyses and certain operations across the system. For system administrators, there are reports that search the database for orphaned objects that originate in CM repositories. |
Content
Management Configuration
Prerequisites
Note that you require the Search and Classification (TREX) standalone engine to run Knowledge Management. For information about the technical operation of TREX, see Search and Classification (TREX).
Tasks
Tasks On Demand
The following section lists the most important administration tasks that are performed as required:
Task |
Additional Information |
Extending the configuration |
For example, you
can integrate further repositories or change the user interface (see
|
Creating indexes |
If you have
integrated other data sources as repositories in KM, and want to be able to
search them, you must create new indexes (see
|
Configuring security settings |
For example, you
assign new permissions or modify the existing settings (see
|
Periodic Tasks
The following tasks must be completed periodically:
Task |
Additional Information |
Recommended Frequency |
Monitoring KM |
The different monitors provide information on the status and function of various objects, and contribute to recognizing critical system events. For more information, see Monitoring. |
The frequency can be different for each monitor. During indexing runs, you should use the indexing monitor. If errors occur, you should use the component monitor or check the application log. For example, you can check the cache load weekly. You can use the results to optimize performance. |
Backing up and restoring data |
To prevent data loss, you should regularly back up the data. If ever required, you can then restore your data. For more information, see Administration. |
The frequency depends on how often there are changes to system data, configuration data, and documents. |
Reindexing and carrying out an incremental update of data sources |
You have to update
Web repository indexes to update or repair them (see
|
The frequency depends on how often document changes take place on the remote Web server. If regular updates are necessary, you can set up an automatic cycle. |
Running reports |
You can check that CM repositories are functioning correctly and check for orphaned data objects. |
We recommend running these reports monthly. ●
●
●
|