Skip to Content

NWDI on Portal systems where the applications are deployed


We are using NWDI with three systems and their landscapes connected. NWDI is on a dedicated system.

We are planning to distribute the NWDI on to each of the development environment. This is mainly to reduce the server count by one. Currently NWDI is on 7.4. Runtime systems are on 7.4 and 7.2.

Will it be an issue if NWDI is placed on the same system which is a runtime system?

Is it okay to distribute the NWDI onto each system instead of having a common system? What would be recommended approach?


Bhaskar B

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Posted on Mar 05, 2019 at 08:04 AM

    Hello Bhaskar,

    Both approach can work:

    1, The NWDI can be installed as distributed system.

    2, The NWDI JAVA AS can be used as a runtime AS.

    However you should consider these things:

    1, The distributed approach is recommended when customers would like to balance high load among the NWDI server components. e.g. such components are being assembled which require higher physical resources. By splitting the system performance issues can be avoided. Or an other good example is: even if the JAVA AS, hosting the CMS is down, the host which is running the DTR will be still accessible. So this scenario is not for reducing the number of the server hosts, rather for increasing availability and usability.

    Also the version of the servers have to be consistent, which means that if the CMS version is NW 7.40, the DTR and the CBS hosts have to be NW 7.40 as well.

    2, As I mentioned above the NWDI host can be used as a runtime system where you deploy the applications to, however you should use this only for DEV/QA landscapes. The recommended approach is to have a dedicated PRD JAVA AS where only PRD applications are running and there is no development activity on it.

    You should calculate whether the resources that the certain JAVA AS has, are enough for all your development and testing activities too. In this case you can use only one JAVA AS for running the NWDI and the developed applications as well.

    If you think that your custom applications are resource extensive then it is recommended to keep the current landscape setup.



    Add comment
    10|10000 characters needed characters exceeded