Skip to Content
author's profile photo Matt Fraser

[Status Update] I Still Hate NWDI


I have worked with it for more than ten years now, and it continues to be one of the touchiest, least reliable, and frankly murkiest applications of my experience (no offense, Ervin). It is the main reason we avoid updates to our Portal like the plague, because every single time the NWDI-modified components do not go well. I long for the day when we have no more Web Dynpro Java components from SAP in our system, when it is all either WDA or Fiori, and I can drop this application like the hot stone it is, letting it sink into a deep, deep well from which hopefully it will never be retrieved.


* Please Login or Register to Comment on or Follow discussions.


  • Mar 08, 2017 at 02:00 AM

    Feel your pain. Thankfully, I waved good bye to it once and for all many Many MANY years ago and avoid it at all costs. careful what you wish for...the grass is not always greener. haha

  • Mar 14, 2017 at 06:53 AM

    lol, Matt, none taken :) I think I know exactly what you mean.

    function anotherRant() {

    Oh I wish @mention was working.

    Found this thread by accident.


    greetings from Vancouver ! ;-)

    • Mar 14, 2017 at 03:45 PM

      Well, in this case notifications worked! So what's going on in Vancouver? Are you working there now, or is this a site visit?

  • Mar 22, 2017 at 04:03 PM

    Well, what an odd coincidence. We have currently (re)started debating whether we should "modernize" the Transport Management of our Portals with CTS+ or NWDI. At the moment, we still use "ye good ol'" System Administration --> Import/Export Webtools which don't allow for much automatization and after listening to your 'song of praise' :-) maybe we should stick with those after all

    • Mar 22, 2017 at 07:37 PM

      I don't believe in coincidence. ;)

      More seriously, does System Administration -> Import/Export work for moving Java Web Dynpro customizations? We have only used that for Portal Content transports (and we still do).

      • Mar 23, 2017 at 12:31 PM

        AFAIK, no, it doesn't. We've switched from all WDJ-Applications we had to WDA alternatives where we had the chance right after our EHP6-Upgrade in 2013, because we never had any chance modifying existing WDJs (since we have no NWDI/NWDS). The only WDJ we have left nowadays is the Universal Worklist which we will ultimately replace with the Fiori My Inbox in the not so distant future. Hence, there was no real pressure to use anything else than the Webtools (except for the lack of automatization).

        • Mar 23, 2017 at 10:45 PM

          Then I would definitely not put in NWDI just to manage Portal Content. That's like the proverbial bus to cross the street. NWDI is a relatively complex tool, and this would be pretty massive over-complication for just managing PCD content. If everything you customize (besides content) is now WDA, I would continue to use the good old TMS for that. I don't yet have experience with managing Fiori transports. I imagine it probably depends on whether you host the apps in the ABAP system or in the Portal. If I'm not mistaken, they'll reside on the ABAP side, won't they? And the Portal will just contain the Launchpad? Or something like that?

          • Mar 24, 2017 at 02:02 PM

            Yep, pretty much. :)

          • Mar 27, 2017 at 04:50 PM

            You got different deployment options. As far as I understood (I have no real clue about Fiori yet), the Frontend Server can theoretically also be on the Portal. In our landscape (which we're still busy building), though, we plan to have a Portal with Fiori Framework Page with integrated Fiori Launchpad via Reverse Proxy consumed from a Gateway based on Netweaver AS ABAP + respective Backends with oData Services. And then we'll have all the clickedy-coloured super fancy tiles and whatnot. I must say, though, now that I'm getting involved in the "fiori-post-hype" I'm becoming more and more a disbeliever when it comes to Fiori replacing WDA Apps. The functionality depth simply isn't there. Except maybe for the Payslip or Leave Request... but that's an entirely different topic ;-)

            BTT: I conclude: NWDI only for Portal transports = bad ;-D

            • Mar 27, 2017 at 10:07 PM

              Today I noticed, as I prepared a Portal Content Transport for export to send to our newly upgraded-to-7.5 QAS portal (what I spent 5 "business days" over the past 3 days completing), that in the Portal Content Transport area there is a feature for activating recording of portal content changes! Wow, just like ABAP transports? I haven't experimented with that yet, but if it works reasonably well, I can see that making the process of figuring out what content to transport much simpler.

              A big part of those "5 business days" of effort was getting a WDJ app to properly deploy to DEV and then release to NWDI, then the process of consolidation and assembly in that environment.

  • Add a comment
    10|10000 characters needed characters exceeded