Show TOC

Migration of Documents into the CM RepositoryLocate this document in the navigation structure

Use
Note

We recommend that you only perform a migration into the CM repository if it is necessary for performance reasons.

In the BEx Web runtime (Java), you can integrate Business Content by migrating documents onto the portal. You can migrate documents from the BW server into a special CM repository configured for BW. This repository is used exclusively for BW documents. This storage improves performance and allows documents for master data and InfoProvider data to be assigned at hierarchy node level (as well at characteristic value level).

Caution

The migrated documents are not available in BEx Analyzer. Only migrate the documents if they do not use BEx Analyzer or in connection with documents.

Caution

KM on the portal does not support language versions. If there is more than one version of a document on the BW server, only one version is migrated. This version is determined as follows: The system uses the logon language of the user executing the migration to search for the most recent version of the document in this particular language. If no document is found, the most recent version of the document is migrated (regardless of the language).

Prerequisites

Before you can migrate documents, the following prerequisites have to be met:

  • You have performed the necessary steps for integration onto the portal. For example, you have set up the SAP NetWeaver Portal and Knowledge Management (KM). You perform these steps in Customizing, under Start of the navigation path SAP Customizing Implementation Guide Next navigation step SAP NetWeaver Next navigation step BW Next navigation step  Settings for Reporting and Analysis  Next navigation step  BEx Web Next navigation step Integration into Portal End of the navigation path.

  • A configured BW system exists in the system landscape.

  • You have set up the BW Document Repository Manager and have entered values for the properties of BW documents for the InfoProviders, master data, and metadata of the BW system. See BW Document Repository Manager.

  • You have configured a CM repository manager for BW documents on the portal. You have set the persistence mode of the CM repository to Save All Data (Documents, Folders and Metadata) in the Database (DB). You have configured a security manager for the CM repository manager using BW Security Manager for Documents. This ensures that BW documents are protected against unauthorized access (you can only set up the security manager after migration; this improves system performance during migration).

  • In Knowledge Management, you have assigned the required portal authorizations to the user who is performing the migration. These are:

    • Authorizations for reading and writing document properties. To do this, choose Start of the navigation path System Administration Next navigation step Configuration Next navigation step Content Mangement Next navigation step Utilities Next navigation step System Principals Next navigation step System User. End of the navigation pathEnter the user and give him/her the read, write,delete authorizations in the Resource Permission column.

    • Authorizations to change the BW system in the PCD. Assign the user read and write authorizations.

You find the required settings in Customizing, under Start of the navigation path  SAP Customizing Implementation Guide Next navigation step SAP NetWeaver Next navigation step BW Next navigation step  BW Documents Next navigation step Create a CM Repository for Documents End of the navigation path andMigration of Documents to the CM Repository.

Features

During migration, documents from the BW server are copied to the portal-based KM and are stored there physically in the CM repository. The CM repository has a fixed folder structure and uses the BW security manager for authorization checks. You can migrate each document class individually or migrate several document classes simultaneously. You can display documents from SAP GUI on the portal and make changes to migrated documents. Migrating documents enables a wider scope of functions. For example, you can assign documents for master data and InfoProvider data at hierarchy-node level (as well as characteristic-value level).

Activities

Displaying migrated documents on the portal

You perform document migration on the portal. When you perform migration, the system automatically enters the target CM repository in table RSPOR_T_PORTAL. You can then display Data Warehousing Workbench documents on the portal.

Changing Migrated Documents

When you make changes to migrated documents on the portal:

  • The changes are not written back to the BW system

  • The documents are not visible in the BEx Analyzer

  • The changes to documents on the server are not visible on the portal after migration If you want to make these changes available on the portal, you have to migrate the documents onto the portal again.

For more information about migrating documents, see Migrating Documents.