Wednesday, November 28, 2007

Repository Manager for BW Documents

Definition

Repository manager for documents in the SAP Business Information Warehouse.

Use

The repository manager for BW documents allows you to integrate documents created in SAP BW into Knowledge Management in the SAP Enterprise Portal. The Structure linkdocuments are broken down into three Structure linkdocument classes: Metadata, Master Data and InfoProvider Data. The Metadata document class contains manually created documents on metadata. These documents are not the automatically generated documents from the metadata repository. In the Master Data document class there are documents on characteristic values, such as images for personnel numbers, descriptions and technical specifications for materials. The InfoProvider Data document class contains documents on a combination of characteristic values, such as comments on key figures.

You can use the Administrator Workbench or Web applications to create the documents. For more information on displaying, creating and changing documents in Web applications, see Structure linkUsing Documents in Web Applications.

Structure

The parameters of the repository manager for BW documents are explained in the following. When you choose Show Advanced Options you get a complete list of parameters. A plus sign (+) indicates the advanced setting options.

Parameters of the repository manager for BW documents

Parameter

Obligatory

Description

Name

Yes

Name of the repository manager

Description

No

Description of the repository manager

Prefix

Yes

URI prefix for which the repository manager for BW documents is registered.

This entry lists the repository in the master directory.

The URIs for all resources managed by this repository manager have this common prefix. The prefix is used to identify the repository manager that is responsible for a resource with a particular URI. Note: The prefix has to be entered with a diagonal slash, for example, /bw_documents.

The prefix in the BW system has to agree with the one in the portal.

Active +

No

You can activate or deactivate the repository manager by setting this parameter.

Hide in root folder +

No

This parameter specifies whether the repository is listed in the master directory.

If you activate this parameter, the repository is not listed in the master directory.

Repository services

No

Identification of the Structure linkRepository Services that you want to use for a repository.

Property search manager

Yes

Selection of the manager for the property search.

Choose com.sap.ip.bi.km.repository.manager.bidoc.BidocPropertySearchManager.

Security manager

Yes

This parameter cannot be changed and specifies the BW Document Security Manager security manager that controls access to the repository content. The BW Document Security Manager provides a connection to the BW system and checks whether authorization exists to display or change the documents.

Send Events +

No

This parameter specifies whether the repository sends events when operations like “delete” or “refresh content” are performed.

The parameter has to be activated if you want the repository to send events. This is necessary, for example, when using services like the subscription service.

Show empty folders

No

If you activate this parameter you are also able to see folders that do not contain any documents. Using the repository manager, you can then create new documents in the BW system in these empty folders.

If you do not intend to use the repository manager to create new documents, we recommend that you deactivate this parameter.

Show technical names

No

If you activate this parameter, the technical names of the BW objects upon which the documents are based are displayed.

If you deactivate the parameter you can still see the technical names of the BW objects using the quick info.

Read only

No

This parameter specifies whether the repository is write-protected.

Lifetime metadata cache

No

Here you can set the lifetime of cache elements for metadata in seconds. If you enter the value 0, the cache is deactivated.

Lifetime property cache

No

Here you can set the lifetime of cache elements for the properties of documents in seconds. If you enter the value 0, the cache is deactivated.

Lifetime security cache

No

Here you can set the lifetime of cache elements for the user-specific access authorizations in seconds. The security cache is deleted automatically in the background according to the time specification entered here. If you enter the value 0, the cache is deactivated.

If a number of users are accessing the repository manager for BW documents, we recommend that you deactivate the cache and set the value at 0 to avoid too great a memory consumption.

Alias of BW System

Yes

Here you enter the alias of the BW system that you specified in the portal system landscape directory when you set up the BW system. See Creating BW Systems in the Portal.

metadata.repository.manager

No

If you are using the repository manager for BW documents as well as the repository manager for BW metadata you can enter its prefix here. The two repository managers are now linked and you can, for example, see the documents created for an InfoObject in addition to the automatically generated documentation for the metadata.

Example

Configuration of a Repository Manager for BW Documents

Name = BWDocumentsRepositoryManager

Description = BW Documents AB

Prefix = /bw_documents

Active = activated

Hide in Root Folder = deactivated

Repository services = comment, discussion, properties, rating, subscription

Property Search Manager = com.sap.ip.bi.km.repository.manager.bidoc.BidocPropertySearchManager

Security Manager = BWDocumentSecurityManager

Send Events = activated

Show empty Folders = deactivated

Show technical Names = deactivated

Read only = deactivated

Lifetime Metadata Cache = 7200 seconds

Lifetime Property Cache = 7200 seconds

Lifetime Security Cache = 3600 seconds

Maximum Connections per User = 5

Alias of BW System = SAP_BW

metadata.repository.manager = /bw_metadata

End of Content Area

No comments:

Blog Archive