Administration and Configuration (Changed) 

Technical Data

Function Is	Changed
For Release	Software component ●      Component: SAP NetWeaver ●      Release: 7.0
Assignment to Application Component	EP-KM (Knowledge Management)
Country Setting	Valid for all countries

Use

Note the following changes and new features in the administration and configuration of Enterprise Knowledge Management in SAP NetWeaver 7.0.

 

Default Proxy System (New)

If repository access always takes place through a certain proxy server in your company, you can use the default proxy server. This saves you having to repeatedly enter the proxy host and proxy port during the configuration of repository managers. You simply have to activate a parameter instead.

For more information, see Default Proxy System.

 

URL Generator Service (Enhanced)

New parameters have been added to the configuration of the URL generator service. These parameters are used internally by the system and contain predefined values that may not be changed under normal circumstances.

For the updated list of parameters, see URL Generator Service.

 

Configuration Steps Before Implementing the Sponsored Links Function (New)

Before you can use the Sponsored Linksfunction, you must work through several configuration steps. For more information about this, see Configuration of the Sponsored Links Function.

 

Using Bundle Files (Changed)

In order to be able to implement your own bundle files in Knowledge Management, you must create a project in SAP NetWeaver Developer Studio, which you can integrate the bundle files in. To do this, you can use an example project that SAP makes available. You create your bundle files in here. Then you export the project as a PAR file and deploy it in your portal. The PAR file is written to the portal database during deployment. The change in this procedure has the benefit that your bundle files are automatically taken into account during a backup.

For more information, see Importing an Example Project Into SAP NetWeaver Developer Studio and Exporting and Deploying PAR Files.

 

Configuration of Commands (Enhanced)

You can use the Roles with Visibilityparameter to determine, whether a command on the user interface appears for certain roles only.

For more information, see Commands and Command Groups.

 

WebDAV Repository Manager and Web Repository Manager (Enhanced)

The WebDAV Repository Manager and Web Repository Manager now support NTLM authentication.

For more information, see WebDAV Repository Manager and Web Repository Manager.

 

Indexing Monitor (New)

The indexing monitor provides the most important information on the status of running indexing processes. It contains various functions that allow you to intervene in indexing.

If you want to display detailed information on an index, you can launch a new iView that displays the crawler monitor together with the TREX monitor. Only the information on the selected index is displayed at the same time.

For more information, see Indexing Monitor in the KM administration guide.

 

Security Manager (Changed)

The various security managers support hot reload. If you change the security manager in the configuration of a repository manager, you do not have to restart the portal.

A new security manager for Web repositories (instance name WebSecurityManager) is available. If a Web site is accessed directly, the Web server carries out the permission check. However, text snippets in the search results list and HTML preview of documents are located outside the Web server in CM. When a security manager is being used, users without permission to read a document cannot see text snippets in the search results list or the HTML preview for the document in question.

It should only be selected for Web repository managers whose content is indexed and can be searched. This security manager should not be implemented in scenarios in which searching in Web repositories is not planned.

Using this security manager can considerable hamper performance, since additional requests are sent to the Web server. You should therefore check that you need to use it and only implement it if the additional security really is required.

For more information, see Security Managers in the KM administration guide.

 

iView for Setting Permissions (New)

There is a new iView for content administrators for checking and setting permissions and service permissions. This iView is based on the KM Navigation iView and lists all repositories and their folders. Different icons illustrate whether a folder or document inherits the permissions of the superordinate folder, or whether it has been assigned its own different permissions.

The iView is suitable for restricting the initial permissions that apply after installation.

In the tree view, an icon in front of each repository indicates additionally whether a security manager is assigned for the repository, and if yes, which one.

In the portal, to launch the iView, choose Content Administration ® KM Content. In the detailed navigation, choose Toolbox ® Permissions.

For more information, see Permissions iView in the KM administration guide.

 

iView for Resetting Folder Settings (New)

There is a new iView for content administrators for resetting the folder display. You can reset the layout settings for a specific user or the layout settings defined for all users to the default layout or another layout profile or layout set. This can be necessary if the layout was configured in such a way that the link to the Details dialog box, which you can normally use to change the layout, no longer appears.

You can also use this iView to define a new layout for all users, so that they do not have to change the folder settings themselves.

In the portal, to launch the iView, choose Content Administration ® KM Content. In the detailed navigation, choose Toolbox ® Folder Settings.

For more information, see Resetting Folder Settings in the KM administration guide.

 

Export and Import of Properties (New)

In the Configuration iView, you can use the import and export functions to transfer existing predefined properties between portals. For example, you can create a property in a test system and then transport this using an XML file to a production system.

For more information, see Export and Import of Properties and Metadata in the KM administration guide.

 

System Templates (Changed)

In order to implement user mapping in KM repositories until now, you had to manually create system templates in the portal system landscape. This is no longer necessary. For the following repository managers, the corresponding system templates are already created in the standard system:

 

Repository	System Template in the Portal System Landscape
WebDAV repository	KM WebDAV System
Lotus Notes repository	KM Lotus System
File system repository (based on Windows®)	KM Windows System