The Repository Manager for BW metadata allows you to integrate the metadata created in the BW system (InfoCubes, queries, Web templates, workbooks, and so on) and their associated documents into Knowledge Management of the portal as write-protected documents. The repository manager for BW metadata also allows you to access online links created with BEx Information Broadcasting.
The repository manager for BW metadata allows you to access automatically generated HTML-based documents for metadata. The documents correspond to the information in the metadata repository in the Data Warehousing Workbench. You can also create manual documents for metadata that can be integrated into Knowledge Management using the Repository Manager for BW Documents .
Log on to the portal.
Choose
.Enter the required data.
By choosing Show Advanced Options , you can display a complete list of parameters.
For performance reasons, we recommend deactivating the following parameters:
Show objects data is received from (Data Flow Before)
Show objects data is sent to (Data Flow Afterwards)
Show usage (Where-Used list)
For central objects, the where-used list or data flow lists a large number of objects, which makes the online documentation extensive. As a result, it can take some time to build the online documentation.
The following table contains descriptions of each of the parameters; a plus sign (+) denotes advanced settings options.
Parameter |
Mandatory |
Description |
Description |
No |
Description of the repository manager |
Prefix |
Yes |
URI prefix for which the BW Metadata Repository Manager is registered. The repository is listed in the master directory using this entry. The URIs for all resources managed by this repository manager have this prefix. The prefix is used to identify the repository manager that is responsible for a resource with a particular URI. Note that the prefix has to be entered with a forward slash, for example, /bi_metadata. 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 repository 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.mo.MoPropertySearchManager . |
Security Manager |
Yes |
This parameter cannot be changed and specifies the BW Metadata Security Manager . This controls access to the repository content. The BW Metadata Security Manager provides a connection to the BW system and checks whether authorizations for displaying metadata exist. |
Send Events + |
No |
This parameter specifies whether the repository sends events when operations such as "delete" or "refresh content" are executed. The parameter must be activated to allow the repository to send events. This is necessary, for example, for the use of services such as the subscription service. |
Lock Manager |
No |
Leave this field empty. |
Show Objects data is received from |
No |
In data flow before: If you activate this parameter, links to the online documentation for the object from which the current object receives data are displayed. |
Show Objects data is sent to |
No |
In data flow after: If you activate this parameter, links to the online documentation for the objects to which the current object sends data are displayed. |
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 tool tip. |
Show usage |
No |
Where-used list: If you activate this parameter, links to the online documentation for the objects that the current object uses are displayed. |
BW Lock Cache |
By default, the cache is ca_bi_lock . |
|
BW Property Cache |
No |
This parameter specifies the cache for BW documents. By default, the cache is ca_bi_auth . You can also create a new cache, if required. To do this, choose . When setting the Capacity and Default Time-to-Live parameters note how many documents are accessed simultaneously by all users. More information: Caches |
BW Security Cache |
No |
You use this parameter to specify the cache for BW documents with access authorizations. In the default setting, the cache is ca_bi_auth . To do this, choose . When setting the Capacity and Default Time-to-Live parameters note how many documents are accessed simultaneously by all users. |
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. The naming convention for the alias is <BW System ID>CLNT<Client>. |
Prefix of BW Document Repository |
No |
If you are using the Repository Manager for BW Metadata as well as the Repository Manager for BW Documents you can enter its prefix here. The two repository managers are now connected and you are able to see not only the metadata and its documentation, but also the corresponding documents. |
Example
Configuration of a Repository Manager for BW Metadata
Parameter |
Value |
Description |
BWDocumentRepositoryManager |
Prefix |
/bw_metadata |
Active |
Activated |
Hide in Root Folder |
Deactivated |
Repository Services |
comment, properties |
Property Search Manager |
com.sap.ip.bi.km.repository.manager.mo.MoPropertySearchManager |
Security Manager |
BWMetadataSecurityManager |
Send Events |
Activated |
Lock Manager |
Deactivated |
Show Objects data is received from |
Deactivated |
Show Objects data is sent to |
Deactivated |
Show technical Names |
Deactivated |
Show usage |
Deactivated |
BW Lock Cache |
ca_bi_lock |
BW Property Cache |
ca_bi_prop |
BW Security Cache |
ca_bi_auth |
Alias of BW System |
BWP_CLNT_000 (<BW System ID>CLNT<Client>) |
Prefix of BW Document Repository |
/bw_documents |