Skip to Content
avatar image
Former Member

NWDI Question

Hey All,

I'm building a NW 7.4 PO landscape with NWDI integration.

A few clarifications around it.

During the install of PO, is asks to check box a intergration into NWDI landscape.

Do I need to have the NWDI infrastructure built first?

If not, Do I need to check mark this because I will have one?

if i don't check it, can i make or turn on the changes later? or is it only done at installation?

Last question, Can NWDI exist on the same server as SAP PO? If so, would you put it on DEV? I guess it also depends on SLD configurations?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    May 14, 2014 at 05:52 PM

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Joshua,


      use this option on the runtime system where you intend to deploy your product (this is typically used for products like ESS which is delievered by SAP but also modifiable by customers. If you don't tell the system this product is modified by you (controlled by NWDI) then you might "overwrite" it by accident when your admin colleagues are deploying latest pathes or upgrading the SP stack. To avoid that you tell the upgrade tool that this product is under modification by you, so the upgrade tool won't touch it but skip it during deployment).


      Notice, you can enable this feature later as well, read more on this here:

      Configuring Runtime Systems in NWDI - Using the Development and Production Infrastructure - SAP Library --> see Maintaining an NWDI-Controlled System Landscape


      Regarding the checkbox itself "Prepare SAP System for NWDI Integration" indeed it only does what Jun said.

      Regarding your other question, NWDI musn't be on any system which is a runtime system (dev, cons, test, prod). I recommend to have a separate engine installed that runs NWDI.
      For more information on this see the note

      "754143 -- CMS remarks/restrictions" which says:

      • Do not use CMS server as a runtime system:

                Do not use the J2EE Engine, on which the CMS is running, as a runtime system. When you import software components that have offline deployment portions, deployment causes a deadlock. In other words, the CMS is shut down by the import that it is supposed to check.

      Best Regards,

      Ervin

  • May 15, 2014 at 03:25 PM

    that check box is nothing,

    if check, it just copy all the SCA files to your server, which can be used to setup track if you install nwdi in the same server(instance)

    nwdi can be setup in the same dev po server.

    Add comment
    10|10000 characters needed characters exceeded