Administration and Configuration (Changed) 

Technical Data

Function Is	Changed
For Release	Software Component ●      Component: SAP NetWeaver ●      Release: 7.0 ●      Support Package: Stack 14
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 Knowledge Management in SAP NetWeaver 7.0 SPS 14.

 

Activity Reporting (New)

You can use activity reporting to record activities in KM repositories.

For example, you can find out which users have performed which file operations at what time in a repository.

Since the written log files are machine-readable, you can trigger statistical evaluations of the collected data. For example, you can calculate how often a document has been called or which use has created the most documents.

For more information, see Activity Reporting.

 

User Resources Report (Changed)

As of the new support package, the user resources report searches not only for users, but also for groups and roles by default. In addition, you can use the Transfer to Another Principal command to transfer permissions not only to users, but also to groups or roles.

Furthermore, you can configure whether or not the system is to check if the ID you are searching for exists in user management. This allows you to find deleted users, for example.

For more information, see User Resources.

 

Notification Cleanup Report (New)

You can use this report to delete KM notifications from the Universal Worklist for specific users, for example, old subscription notifications.

You can specify users, groups, and roles as well as a time interval or a number of days. The system finds all KM notifications that were sent in the specified period or that are older than the specified number of days. You can configure whether the system is to immediately delete the notifications or display them in a results list, from which you can delete them manually.

For more information, see Notification Cleanup.

 

FS-DB Database Synchronization Report (Changed)

As of the new support package, you can specify more than one repository in this report. If you specify more than one repository, the report processes them sequentially.

For more information, see CM Repository: FS-DB Synchronization.

 

Indexing Properties as Text and as String (New)

The benefits of storing a property in TREX as a string are that it requires less space and the search performance is better. Another benefit of indexed String properties is that you can perform operations such as is larger than and is smaller than. However, you cannot perform a linguistic search for String properties.

Until now, you could index properties either as Text or as String. As of the new support package, you can combine both options.

For more information, see Indexing Properties in TREX as Strings.

 

Placeholders in URLs (Changed)

To date, the URL generator supports URLs with placeholders in the format <token> (for example, .../<user.id>/...). Certain tools from third-party vendors do not allow these characters for security reasons.

As of the new support package, the URL generator supports placeholders with a new character in the format !token! (for example, .../!user.id!/...).

 The existing placeholders are supported in the future.

Effects on System Administration

If you have had no problems with the existing placeholders in the past, you do not have to do anything.

If you have had problems with the existing placeholders in the past, you should replace them with the new placeholders. For example, you can change the parameters Path to Initially Displayed Folder and Path to Root Folder for Navigation in the Portal Favorites iView as follows:

/~alias~/userhome/!user.id!/favorites

 

Subsequent Change of the Persistence Mode for CM Repositories (New)

With this support package, a subsequent change of the persistence mode is possible from the DB mode to the DBFS mode. Changing from DB to FSDB, from FSDB to DB/DBFS, or from DBFS to DB/FSDB is not possible.

To change the mode, work through the following steps:

...

       1.      Make sure that enough free disk space is available to migrate the content from the database to the file system.

       2.      Change the configuration of the CM repository manager. In the Root Directory parameter, specify the path to the file system that the documents from the database are to be stored under. Change the entry in the Persistence Mode parameter from DB to DBFS.

       3.      Restart the application server.

       4.      Run the CM Store: Content Crawler report.

For more information, see CM Repository Manager and CM Store: Content Crawler.

 

Subscription Service (Enhanced)

In the configuration of the subscription service, you can now define the values that users can choose from in the fields Frequency, Expires, and Scope when managing notifications.

For more information, see Subscription Service.