Skip to end of metadata
Go to start of metadata

Author: Snehal Kendre
Submitted: 5/19/2009
Related Links:

Reference 1

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60c7c351-1344-2a10-a6b0-c2f148f59ef0

Reference 2

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b2b146-5776-2910-4a8f-9b3190eab060

Reference 3

http://help.sap.com/saphelp_nw04/helpdata/en/63/7a4d40eae76f13e10000000a1550b0/frameset.htm

Getting started

You must have administrator rights of both the server. Here we are going to create a new track at other NWDI server and then we'll move development from previous NWDI server to new NWDI server (fresh installation, not a system copy of previous NWDI).

Scenario

The steps to migrate a development done at one track from one server to other server are as follow

1.    Assemble the new SCA file from previous development track.

2.    Export the product and software component created for the development from previous NWDI.

3.    Import the product and software component into the new NWDI.

4.    Keep the SCA file of development into CMS inbox with the SCAs of other dependencies.

5.    Go to CMS Create a new development track at new NWDI.

6.    Check in all the SCAs from CMS inbox to Development compartment of new track.

7.    Import from Development to Consolidation, do same up to the production.

Procedure

Assemble the new SCA file from previous development track

Open CMS of NWDI/JDI.
Go to the transport studio and click on development track.
Create a new SCA of development at assembly.

Export the product and software component created for the development from previous NWDI.

Open system landscape directory of server.

Go to the software catalog-> products.
Export the product, and download exported file.

Same way you can export and download software component.

Import the product and software component into the new NWDI

 Open system landscape directory of server. Go to the administration.
In content you have an option to import. Import the product's and software component's downloaded zip file.

Keep the SCA file of development into CMS inbox with the SCAs of other dependencies

Go to the directory
usr\sap\trans\CMS\inbox
and copy SCA file of the development assembled from previous NWDI with SCAs of other dependencies(like  sap_buildt, sap_jtechs etc). These files will be imported into the track using transport studio.

Go to CMS Create a new development track at new NWDI.

In CMS->landscape configurator
Create a new track. and add SC which is imported into SLD from previous NWDI server.

Save the track and move to transport studio.
Check in all the SCAs from CMS inbox to Development compartment of new track.
 

4 Comments

  1. Former Member

    Does this procedure bring the version history over?

  2. Unknown User (bztvy05)

    Does this procedure bring the version history over?

    The answer is No...if you are asking about the versions of assembled SCA files n previous track, or about the change version about the DCs.

  3. Unknown User (ow29u68)

    Hi,

    can we copy the track,version history,DTR from one server to other via this method.

    Actually we are using NWDI on our Dev server and we have modified some ESS/MSS components now we want to move complete NWDI to our sandbox (Replica of NWDI at Dev server) server and start applying new sap patches.Id this possible with this method ?

    Thanks

    Alok

  4. Unknown User (p8sbwte)

    Hi,

    not sure if someone is watching this article. In case, I need some help. I'm trying to migrate a track between NWDI, I created the SCA and copied it to the ne inbox.

    Unfortunately, I cant see the file into the check-in folder of the new NWDI.

    Any idea or suggestion?

    Many thanks

    Tiberio