Scribd Logo
Unggah

Selamat datang di Scribd!

  • Forum Migrate Nwdi 1

    Diunggah oleh

    owl meadow
    97 tayangan2 halaman
    I want to move the NWDI but do not want to use the system copy method. Instead I would like to re-install a new NWDI and manually set up the other connections like SLD and redefine the tracks and import the SCA's from the other tracks. Naturally my namespace server will be moved and the object server name remain unchanged and my NWDI SLD entries will be repointed. I cannot see any issues in doing this as long as I have closed off all developments into SCA's.... has anyone done this before or can anyone see any issues?

    Hak Cipta

    © Attribution Non-Commercial (BY-NC)

    Format Tersedia

    PDF, TXT atau baca online dari Scribd

    Apakah menurut Anda dokumen ini bermanfaat?

    Apakah konten ini tidak pantas?

    Laporkan Dokumen Ini
    I want to move the NWDI but do not want to use the system copy method. Instead I would like to re-install a new NWDI and manually set up the other connections like SLD and redefine the tracks and import the SCA's from the other tracks. Naturally my namespace server will be moved and the object server name remain unchanged and my NWDI SLD entries will be repointed. I cannot see any issues in doing this as long as I have closed off all developments into SCA's.... has anyone done this before or can anyone see any issues?

    Hak Cipta:

    Attribution Non-Commercial (BY-NC)
    Unduh sebagai PDF, TXT atau baca online dari Scribd
    Tandai sebagai konten tidak pantas
    97 tayangan2 halaman

    Forum Migrate Nwdi 1

    Diunggah oleh

    owl meadow
    I want to move the NWDI but do not want to use the system copy method. Instead I would like to re-install a new NWDI and manually set up the other connections like SLD and redefine the tracks and import the SCA's from the other tracks. Naturally my namespace server will be moved and the object server name remain unchanged and my NWDI SLD entries will be repointed. I cannot see any issues in doing this as long as I have closed off all developments into SCA's.... has anyone done this before or can anyone see any issues?

    Hak Cipta:

    Attribution Non-Commercial (BY-NC)
    Unduh sebagai PDF, TXT atau baca online dari Scribd
    Tandai sebagai konten tidak pantas
    dari 2

    Expert Forums: Moving the NWDI ...

    Page 1 of 2

    Expert Forums SAP NetWeaver SAP NetWeaver Development Infrastructure (NWDI, formerly known as JDI)

    Thread: Moving the NWDI


    This question is answered.

    Welcome, Wai-Hon Lam Your Control Panel Your Reward Points Your Questions

    Reply to this Thread

    Search Forum

    Watch this Thread

    Back to Thread List

    Replies: 4 - Pages: 1 - Last Post: Jul 4, 2008 1:49 AM Last Post By: Graham Newport

    Graham Newport
    Posts: 180 Registered: 9/15/05 Forum Points: 308

    Moving the NWDI


    Posted: Jul 3, 2008 8:56 AM

    E-mail this message

    Reply

    I want to move the NWDI but do not want to use the system copy method. Instead I would like to re-install a new NWDI and manually set up the other connections like SLD and redefine the tracks and import the SCA's from the other tracks. Naturally my namespace server will be moved and the object server name remain unchanged and my NWDI SLD entries will be repointed. I cannot see any issues in doing this as long as I have closed off all developments into SCA's.... has anyone done this before or can anyone see any issues? regards Graham

    snehal kendre
    Posts: 368 Registered: 7/11/07 Forum Points: 698

    Re: Moving the NWDI


    Posted: Jul 3, 2008 9:35 PM in response to: Graham Newport

    E-mail this message

    Reply

    HI Graham, we did moved our NWDI. using 1. system copy 2. define comman SLD and You should define a Transport Connection between the two tracks. and if dont want any interaction of previous NWDI then 1. Export product and software component defined in your 1st NWDI track. 2. Assemble the new SCA. 3.Import product and software component into your new NWDI SLD. 4. create a new track and assign imported software component. put SCA of that software component in CMS inbox. and check in it from development to production in CMS.

    Graham Newport

    Re: Moving the NWDI


    Posted: Jul 4, 2008 12:32 AM

    E-mail this message

    Reply

    https://forums.sdn.sap.com/thread.jspa?messageID=5724729#5724729

    9/26/2008

    Expert Forums: Moving the NWDI ...

    Page 2 of 2

    Posts: 180 Registered: 9/15/05 Forum Points: 308

    in response to: snehal kendre

    Cheers, before I give you the 10 points, just a clarification. You did a system copy rather than a new install?..... why? The system copy of DI is a pain which is why I would rather do a fresh install and redefine the tracks.... the connection between tracks just puts the SCA in the inbox which is what you do with a new track anyway...

    snehal kendre
    Posts: 368 Registered: 7/11/07 Forum Points: 698

    Re: Moving the NWDI


    Posted: Jul 4, 2008 1:46 AM in response to: Graham Newport

    E-mail this message

    Reply

    Hi, i went through system copy as per SAP stander procedure, and it took too much of my time. mean while while doing R&D the copy SCA method i tried on new fresh installed server.. and it worked. so by the end of the day. i have three nwdi servers. one was original, second was using system copy, third was a fresh installed NWDI.

    Graham Newport
    Posts: 180 Registered: 9/15/05 Forum Points: 308

    Re: Moving the NWDI


    Posted: Jul 4, 2008 1:49 AM in response to: snehal kendre

    E-mail this message

    Reply

    Cheers Snehal, NWDI copy does look a bit of a pain and experience shows that a J2EE copy never changes all references so I just feel safer. much appreciated Graham

    Pages: 1

    Back to Thread List

    New content since your last visit Updated content since your last visit

    Powered by Jive Software

    https://forums.sdn.sap.com/thread.jspa?messageID=5724729#5724729

    9/26/2008

    Anda mungkin juga menyukai