Skip to Content
author's profile photo Former Member
Former Member

can we Customize of Biller Direct 6.35 without NWDI

Hi Team,

We are on NW 7.3 and UCES 6.35. We have to do lots of changes for UCES customization.

1. As per our Basis team they can not install NWDI into the same server where EP core is there from 7.3 onwards (This might be restriction from SAP for 7.3 onwards).

2. Because of the point 1 we can not install NWDI and we have to do customization without NWDI as we are not having any other JAVA server.

3. Now from 7.3 onwards SAP removed the SDM so we can not deploy from NWDS. so I think we can not customize without NWDI from 7.3 onwards. please confim? if yes please tell me the way to achieve?


Narpal Singh

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Aug 07, 2014 at 12:23 PM

    1. not the case

    2. not possible without nwdi

    3.sdm is removed since 7.1, but you still can deploy from nwds

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 13, 2014 at 04:42 PM

    Dear Narpal,

    The UCES sources are exported "DTR-Blobs" which can be imported only to DTR and not into NWDS directly. There are certain SCs which are including the sources as zipped DCs and these SCs can be imported into NWDS, but this is not the case for UCES.

    Therefore I regret to inform you that in case you intend to have a look at the sources of UCES and/or you would like to do modification on its DCs, then you have to have an NWDI track for it.

    Best Regards,

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      i think there is a work-around to import UCES & Biller Direct SC's as local SCs to the NWDS. You only have to find anywhere a NWDI system to be able to downlaod the DCs once. Then you take all the SC's and copy & paste the code into a local SC files. If you do not have a NWDI, you only have to find someone who does have it (import & export from NWDS works also). The alternative is to install NWDI quickly, which takes a few hours, setup the track, download and delete the image. The demo licence should give enough time to make that working. - however, working without NWDI is not recommend, you will easily increase your implementation cost by n-times

      The general problem is, why the client does simply setup a new system and installs the NWDI? It should by anyway a standalone system and not getting mixed up with EP or any other application (including BD & UCES).


  • author's profile photo Former Member
    Former Member
    Posted on Aug 19, 2014 at 10:49 PM

    Hi Narpal,

    #1. I don't think there is such limitation, as far I know you can have both running on the same machine (EP/NWDI)

    #2. Biller Direct does not need to run under anything 'SAP' branded, you can extract and run it locally in a Tomcat if you want, -- also, there is no real need for NWDS as far I'm aware.

    #3. Since you don't need a bloated AS like NetWeaver to develop, you can just use a Tomcat or Jetty Container pointing directly to the root folder - you would have 'instant' access to modifications, (change in eclipse, save and hit f5 in the browser)

    SISU has a paper for this (I used to work with those folks) and I can guarantee you this way is at least 1000x better to work than using NWAS, NWDS and NWDI.

    Hope it helps,


    PS: we are talking about Java here, and there is no bloody way SAP can be restrictive using such language.. so be aware of 'not possible' answers, they are usually possible.

    PS2: leaving the 'SAP Stack' you are also free of 'SAP Limitations' and they are quite A LOT.. removing NWDI out of the equation will bring you a solution for a problem you also mentioned in this thread.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      hi Daniel,

      well, working with the AS is pretty much the same for whatever product:

      1. Create a NWDI Track;

      2. Setup Runtime-Systems;

      3. Setup your Software Component;

      4. Add your Software Component into the newly created NWDI Track;

      5. Add the SAP Software Components you need or you have a direct dependency upon;

      6. Add the files (.SCA from SAP) into the 'Inbox' folder or your NWDI CMS;

      7. Check-In these files;

      8. CMS, Development Tab, Import all the SC's - this will build the _D compartment;

      9. CMS, Consolidation Tab, Import all the SC's - this will build the _C compartment;

      10. in NWDS, Development Infrastructure perspective, use the Import Development Configuration from SLD, and find your _dev track - this is usually where you do all your changes;

      after this, the new SC could be checked out into your machine, or you can modify and add your DC's on it.

      of course, the way I mentioned is not the only way of achieving this, there are always a lot of always to approach and resolve a given problem..

      and the reason why we didn't discuss this in here it's because the OP did not ask for it - so we try to keep discussions focused on subject of the thread, even thou sometimes we can't.

      last but not least, start a new thread about the topic - maybe there are others who would like to see or participate in such discussion.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.