SAP Basis Tech Supports

Symptom

This note describes how the NWDI related components (DTR, CBS, CMS) can be moved to another host by using the System Copy Tool.
Other terms

NWDI, System Copy, DTR, CBS, CMS, Development Infrastructure, DI, System Copy Tool, Move, Migration
Reason and Prerequisites

An installed NWDI system should be moved to another host.
This is only possible if you have at least 6.40 SP15 or 7.00 SP7.
Solution

To move an installed NWDI system to another host you must use the System Copy Tool. The System Copy Tool will also take care to install the target system.
The prerequisites and the system copy procedure are described in the System Copy Guide which can be downloaded from the SAP Service Marketplace. To find the System Copy Guide start from the following page in SDN and follow the instructions from the section ‘System Copy Guide’:
https://www.sdn.sap.com/irj/sdn/systemcopy
IMPORTANT for 6.40:
For 6.40 ensure that you are using the version of the System Copy Guide that contains the Patch Collection:
“Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP Web AS Java 6.40 Patch Collection”
DO NOT USE the old version “Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP Web AS Java 6.40 SR1″ since in this version the JDI specific instructions are incomplete.
IMPORTANT for 7.00:
For 7.00 ensure that you are using one of the following System Copy Guides:
- “System Copy Guide – System Copy for SAP Systems Based on SAP NetWeaver 7.0 – Including Enhancement Package 1 SR 1 Java”
- “System Copy for SAP Systems Based on SAP NetWeaver 2004s SR2 Java”
- “System Copy Guide – System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 Java”
DO NOT USE the old version “System Copy Guide – System Copy for SAP Systems Based on SAP NetWeaver – 7.0 Including Enhancement Package 1 Java” since in this version the DI specific instructions are incomplete.
The System Copy Guide contains a detailed description of all the manual steps that must be executed BEFORE AND AFTER the System Copy in order to ensure a successful JDI/NWDI migration. In addition to all the general instructions, follow all the instructions in the System Copy Guide that are specific to ‘Java Development Infrastructure (JDI)’ (in 6.40) or ‘Development Infrastructure (DI)’ (in 7.00).
IMPORTANT:
When doing a System Copy for the DTR Server you have the choice to do a MOVE or a COPY. This decision is important. If you do a MOVE you are not allowed to use the source DTR Server anymore after the System Copy is done. This especially means that you must not do any transport between the source and the target DTR Server. If transports are done anyway this can lead to inconsistencies in the database of the target DTR Server.
If you want to continue development in the source DTR Server after the System Copy was done, you have to choose the COPY option. In this case it is possible to do transports between the two DTR Servers by doing DTR exports and DTR imports. However in this case the IDs for some resources in the target DTR Server will be newly generated (as part of the System Copy procedure) in order to ensure that the IDs are globally unique.
IMPORTANT:
CBS and CMS do NOT support the COPY option. This means after the System Copy migration was done you are not allowed to use the CBS and CMS in the source system anymore. If the COPY option is selected only for DTR a COPY is done, for CBS and CMS only a MOVE is done.
HINT:
As described in the System Copy Guide one prerequisite from DTR is that there must be no open activities/propagation lists in the source DTR when the System Copy is done. Since in the DTR WebUI it is not possible to globally search for open activities/propagation lists (you can only search for open activities/propagation lists in a workspace) it might be difficult to find all open activities/propagation lists. The easiest way to find all open activities/propagation lists is to execute the following SQL query against the DTR database:
SELECT r.PATHURI, r.OBJNAME FROM PVC_VERSIONSET vs JOIN DAV_RESOURCE r ON vs.VERSIONSETID = r.RESOURCEID WHERE (vs.EXTERNALTYPE = 2 OR vs.EXTERNALTYPE = 4) and vs.OBJSTATE = 1
Before the System Copy is done, this SQL query should return no results.
If there are open activities they must be either checked-in or reverted. Open propagation list must be either closed or deleted.