Migrating Tracks Content from SAP NetWeaver 7.0 to a Higher Version

Once you have decided to migrate from your old SAP NetWeaver 7.0 landscape to a higher SAP NetWeaver version's landscape, you also have to think about how to migrate the applications that you have already developed inside the SAP NetWeaver 7.0 landscape. To perform this migration, you have to manually move the software components (SCs) that you have used for your development inside the SAP NetWeaver 7.0 track to the new version's track. Then you have to update the list of required SCs for your development in the new track. Note that the list of required SCs for SAP NetWeaver 7.0 and the other SAP NetWeaver versions might differ. You have to know the name of the SCs that are present in your old track and the names of the SCs that are needed in the new version's track.

The following topic describes the different aspects of moving the development SCs to the new track.

You must have installed and set up the SAP NetWeaver Development Infrastructure (NWDI) with the Change Management Service (CMS) inside it.

General Overview

1. Create new versions of all your developed SCs from your current track (you are also allowed to customize the number of the SCs you want in the new track) in the SLD with dependencies to the new SAP NetWeaver release. You can use the Configuration Wizard to create the new SC in the SLD (see below) or if you need to create more than one SC, you can choose to perform the steps manually. To find the correct required SCs for your track, see SAP Notes 1465468, 1463541 and 1457908. See also Creating a Software Component in the SLD and Defining New Versions of Software Components .
2. Sync the CMS with the SLD. To do that, in the CMS Landscape Configurator in tab Domain Data, choose Update CMS. See Updating CMS .
3. Create a new track for the new release and add the newly created SCs that you want to develop further. Depending on the default JDK in CBS settings, you may need to create a build variant and specify JDK 1.6 as JDK to be used for this track. For more information about creating tracks, see Creating a Development Track . For more information about build variants, see Configuring Build Variants and Build Options . For more information about configuring CBS, see CBS Service Properties .
4. Copy SCA files of the required SCs to CMS inbox and check them into the newly created track in CMS Transport Studio. Make sure that you take the SCAs you have used to set up your upgraded AS Java where you want to develop.
5. Import the required SCAs to DEV.
6. Assmble all your developed SCs in the old track.
   Caution
   Note Make sure all latest development is consolidated before the assembly and that there is no further development in the old track, once you start the migration process.
7. Forward your developed SCs from the old to the new track. See Forwarding Software Component Archives .
8. Import your SCs in DEV.
9. Migrate content with SAP NetWeaver Developer Studio and release the changes. See Running the Application Projects' Migration Wizard .
10. Import all SCs and migration changes you have done to CONS.
11.  

Creating a Track Using the Configuration Wizard

1. Some of the steps of this process can be perfomed using the Configuration Wizard to create a track. That covers the steps 1 to 5 of the General Overview above, and can be applied for a single SC version only. The wizard allows you to define the type of development that you want to be supported inside this track. Then you point to the location where the required SCs are stored. These required SCs are automatically collected inside the track. For more information about using this wizard, see Setting Up Tracks Using the Configuration Template .
2. Note that the wizard may not be available on servers with old NWDI version. In such case, you can use a newer AS Java server and execute the wizard in it. This should be the AS Java version that you plan to develop for (that is, you shall use it as a runtime system later on in the track).