Skip to Content
avatar image
Former Member

Copy SCs with sources from one track to another in different SLDs.

Hello SDN!

We require to copy our developed SCs with their sources from old track to new for continiuing developing in new track. The problem is that these tracks belongs to different SLDs and there is no way to make connection between these SLDs or tracks. How we can copy it?

Thanks and regards,

Lev

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jun 21, 2013 at 09:24 AM

    Hi,

    what I don't understand is that 1 NWDI domain can operate with only 1 very SLD.

    Meaning, in 1 NWDI system all the tracks has to use the very same SLD, since SLD is maintained per NWDI domain, and not per track (you assign SLD on the domain data tab, i.e. that is a global setting for the entire NWDI system).

    Therefore I assume you wanted to write that you even move the development to a different NWDI system (a different j2ee engine). If not , please elaborate your requirement , if yes, please proceed as described below:

    I suggest you to do move your development to the new system according to the following SCN thread: http://scn.sap.com/thread/1815071

    If you intend to stay on the same NWDI domain, but still you would like to replace SLD to another one, then proceed as per the note:

    #1031984 - Changing the SLD in the Change Management Service (CMS)

    The note contains also information how to move your development related data from one SLD to the other (e.g. name space prefixes, software catalog data, etc).

    I hope this helps.

    Regards,

    Ervin

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Lev,

      this is great news, and what you say makes perfect sense. The development configuration was invalid then due to some russian characters, thank you letting me know. I assume the description is just a single string which has no problems with special characters, but perhaps during the parsing of xml files (like the dev config) it causes some trouble as we have just seen.

      Best Regards,

      Ervin