Skip to Content
avatar image
Former Member

NWDI Landscape deploy strategy

Hi All,

What is the "standard" NWDI Landscape deploy strategy: 1 instance or 2 instance (DEV + PRD), from BASIS point of view.

Is any advantage of having a second NWDI instance? I think I can support all development lifecycle using track systems or several tracks.

Can you please advice.

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jun 08, 2010 at 12:52 PM

    Hi Luis,

    this highly depends on your budget if you are willing to afford a second NWDI instance, or not.

    On a technical point of view, there is no real use for a second NWDI instance in my opinion, Because normally you will not develop things that are running on your NWDI instance.

    The only real advantage of a second NWDI is that you are able to test, Patches, SP-Stacks on your test machine before you touch your production machine. But it is not really that importent to test this in my opinion.

    We where running a singel production NWDi with round about 70 developers and 25 tracsk for 2 years now without a test instance. We patched from SP10 to 19 so far (NW7.0). Some issues which might have been prevented by doing a test on a test NWDI with SPs, but nothing serious. Good time planning and good backups will do the trick 😊

    Now we have a test NWDI, since we are planning to upgrade to EHP1 and implement CM Services. This I do not want to test on our live NWDI 😉

    So after all it really depends if there is a real benefit four you if you have a test NWDI.

    Kind regards

    Jan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jan

      Thanks for the reply.

      I've the same opinion, but nothing better to confirm with someone with more experience.

      Best Regards