Skip to Content
avatar image
Former Member

NWDI - NWDS version

Hello everybody,

just a quick question. Does the version of both the NWDI and the NWDS have to be the same? Is it recommend to have both on the same version? What happend if both are not on the same version?

regards,

Markus

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 10, 2006 at 01:47 PM

    If you use an NWDS with a higher version than your NWDI, you could be using features that your NWDI does not support. The idea is to have the NWDI at the highest SP level available and to have your NWDS at the same level as your target runtime systems.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Yes, you should be safe.

      It might be worthwhile to read <a href="/people/marion.schlotte/blog/2005/10/25/jdi-software-vs-jdi-content blog</a> as well.

  • avatar image
    Former Member
    Apr 10, 2006 at 05:23 PM

    Hi,

    Please make sure that the three file which you import in your track should belong to SP 16.

    Normaly it is ok if you use SP 14 NWDS with SP 16 NWDI. But in slowly you should upgrade these NWDS to SP16.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 10, 2006 at 01:47 PM

    Hi Markus

    This is not recommended by SAP , you need to keep them on the same level , otherwise you will get funny compile errors

    Theo

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 25, 2006 at 11:51 PM

    Short Text

    Broken DCs in ESS Track when upgraded to JDI SP16

    Long Text

    Hi,

    Track Information – Name – ESSTrack

    Business Package – SAP_ESS Release 100 SP7

    WAS 6.40 SP 16

    JDI – SP16

    We have recently upgraded our JDI from SP11 to SP16. We already had a

    track configured for ESS SP7 in which we have made MANY CUSTOM

    MODIFICATIONS which are in production. After the upgrade of the J2EE

    stack to SP16 we upgraded the Netweaver Developer Studio to SP16 also.

    After doing that, we checked out a DC for modifications but we had

    errors in this. In the investigation we saw that the ESS track still

    had the reference of the SP11 base SCs.

    So, we copied the new base SCs (SP16) i.e. the "SAP-JTECHS.sca", "SAP-

    BUILDT.sca", "SAP-JEE.sca" from usr -> sap -> <instance name> -> SYS ->

    global -> CMS_CBS -> plug-ins (according to the SAP documentation) into

    the inbox folder, checked them into the track and imported them to the

    Development and Consolidation runtime systems. Now these dependent SCs

    show SP16 which is consistent with the rest of the landscape SP.

    On doing this, we found that most of the DCs of the SAP_ESS SC were

    broken.

    To resolve this issue, we even tried to rebuild all the DCs in the

    compartment using the “Initialize Compartment” button in the

    Compartments view, CBS Buildspace Details. Still no positive result.

    This break has a very big impact on Freescale as this is the only JDI

    environment we have and if today something breaks in production we HAVE

    NO WAY to correct this.

    P.S.

    1) All of the broken DCs are showing the error with this F4TextHelper

    class of ess~per.

    2) We cannot import the ESS package again as we have already done many

    customizations in the existing track. Also, they have not yet been

    assembled.

    PLEASE HELP

    Regards

    Jay Kapadia

    Add comment
    10|10000 characters needed characters exceeded