Start of Content Area

Process documentation Relocating a Repository  Locate the document in its SAP Library structure

This section deals with the scenario where you want to move a repository from one SAP Content Server to another SAP Content Server.

Caution

The following instructions presume that both the source repository and the target repository are located on an SAP Content Server, and not on a third-party content server. Otherwise, you can relocate individual documents (see also note 389366).

Relocating Using the Database

If the target content server is being newly set up, proceed as follows:
  1. Create a copy of the complete content server. You can use the database to do this. For more information on this procedure, see note 350067.
  2. Change the Customizing of the relocated repositories so that they point to the new content server.

Note

You are thus preventing documents from being stored on the affected repositories during the relocation procedure. Therefore, you must carry out this step before deleting the repositories.
  1. On the source content server, delete all the repositories that you want to relocate, and delete all others from the target content server. You can use transaction CSADMIN to delete the repositories.

Relocating Using Export and Import

  1. Ensure that no new data is saved to the affected repositories during the relocation procedure.
  2. Use report RSCMSEX to export the repository.
  3. Create a repository of the same name on the target content server and change the Customizing of the repository so that it points to the target content server.
  4. Import the data into the target repository using report RSCMSIM.
  5. Delete the relocated repositories from the source content server.

The program sapkprotp controls the export and import. sapkprotp is started on the application server by default. If required, you can start sapkprotp on the content server or on another server. To set this up, enter an RFC destination when starting the report. Set the path of the transport file relative to sapkprotp.

You should use this option if sapkprotp is not available on the application server (so far, sapkprotp is not available for AS/400). You should also use it if the content server is at a remote location, to avoid the data being transferred twice over the WAN.

See also:

Note 371220

 

 

End of Content Area