Red:NWDS version

Hi all,
          I have some bit confusion in nwds..actually nwds has some version such as 7.0, 7.1,7.2 and 7.3....
For instance....nwds 7.0 support jdk 1.4 only. in similar way i want to know about nwds version and which are the jdk version will support for the particular nwds..
can you suggest me regarding this...
Regards,
Dharmaraj

Dear Dharmaraj
Better yor have same version and SP Level as SAP J2EE Server for NWDS Developer Studio.
Even It is compatible for SAP Server Version 7.0, 7.1, 7.2, 7.3 with NWDS NWDS Developer Studio 7.0, 7.1, 7.2, 7.3 respectively.
For more details you can refer to installation guide and production availability matris in the service market place for more details.
Hope it will helps
Best Regards
Arun Jaiswal

Similar Messages

  • Build is not working in SAP NWDS version 7.0.09

    Suddenly the build is not working for my SAP NWDS version 7.0.09. It used to work fine before.
    When you create a DC and do a Development Component --> build . nothing is happening. In the
    General user output view, nothing is printed also.. I think the built is not actually happening now. So I tried uninstalling the NWDS and installing again. I also tried changing the default workspace. But still the problem do exist. what can be the possible reasons for this ? Please help.. Your valuable answers will be highly appreciated.

    Hi Garcia,
    I have checked with the Network team who manages Exchange server and they have mentioned that it is bouncing back from our CRM host with the error as below,
    said: 553 5.1.8 <[email protected]>... Domain of sender address
        [email protected] does not exist (in reply to MAIL FROM command)
    Regards,
    Arpit

  • NWDS Versions

    Hi all,
    our NWDI is installed on a CE 7.1 EHP1 and we need to create different applications in three systems: NW 7.0 SP07, PI 7.1 SP09 and NW CE 7.1 EHP1 SP03. 
    I have some simple questions:
    can I use NWDS 7.1 EHP1 to create and deploy all the applications?
    Should I use different NWDS versions for every runtime system? And in this case, which version si correct for PI 7.1? NWDS CE 7.1 or NWDS CE 7.1 EHP1?
    The creation of a track for NW 7.0 SP07 involves the definition of a Build Variant to specify the correct JDK ( 1.4.2 ). As far as I know there are two sets of options to achive this purpose: 
    com.sap.jdk.javac.source 1.4
    com.sap.jdk.javac.target   1.4
    OR
    com.sap.jdk.home_path_key JDK1.4.2_HOME
    ( Add a key-value pair to the CBS Service Property 'JDK_HOME_PATHS' where the key is 'JDK1.4.2_HOME' and the value is the home path of the JDK. )
    What is the best way?
    Thanks and Regards,
    Andrea Campo

    Hi,
    Yes you can use the same NWDS for all the three systems.
    Your java version is 1.4.2 i think NWDS 7.1 doesn't support the Java version below 1.5.11
    Regards,
    Vamshi.

  • NWDS version for EP7.0 EHP1 & CE7.1

    Hi All,
    Which NWDS version I need to install to support both EP7.0 EHP1 and CE7.1 for development and deployment of Web Dynpro Java .
    I am new to CE7.1. I am aware of settings need to done in NWDS for the deployment of WDJ application. For CE7.1 server what necessary steps I need to follow for development and deployment.
    Thanks,
    Deepak!!!

    Ervin,
    Thanks so much for the reply.
    I am collecting the necessary EP7.0 and CE7.1 server information on which I suppose to do development work. As per shared URL I have to go for 2 NWDS version in the same machine pointed to different work space.
    I'm trying to know how to use CE7.1 portal & NWDS development and deployment. Can you share your view on this?
    Can I use NWDS7.1 for the development and deploy the application in both CE7.1 & EP7.0 EHP1?
    What I am trying to achieve here is:-
    1>I need to do MDM/EP integration.
    2>Need to use MDM Java API's for customization for Search, Match & Merge and Gold copy creation functionality with work flow. This need to decide if there are SAP provided standard content coming with the BPM & CE7.3 for MDM functionality.
    3>MDM Workflow using EP-MDM-BPM scenario with CE7.1/7.3.
    Please share your thought on this.
    Deepak!!!

  • NWDS version compatibility !!

    Dear Friends,
    I would like to pose a simple question on the compatiblity of the NWDS version with my Portal version
    My client set up has Portal version of NW 7.0.1 SP3 .The information i get from the SLD has the following info
    Software Components all components...
    Name Version Applied
    sap.com/SAP-JEECOR 7.01 SP3 (1000.7.01.3.0.20081208163400) 20090713142753
    sap.com/SAP-JEE 7.01 SP3 (1000.7.01.3.0.20081208163400) 20090713142549
    Now the client says it has an NWDS version with 7.01.03
    Now we need to set up a system at offshore as well.I couldnt find an NWDS version of the afore said 7.01.03 so i got NWDS 7.1 EHP1 SP4 Preview version from SDN .I would like to ask you if this version is compatible with the NW 7.0.1 SP3. You can also suggest me a more compatible version of NWDS or a place in SDN where i can look up for the compatibility between NWDS and the NW .
    Kindly do the needful.

    Hi Nishita,
    I agree with Gilles... You can not use NWDS 7.1 for your portal 7.0.1. it wont support.
    Always see to it that ur portal version matches with NWDS (even lower version of NWDS works).
    For confirmation check below threads...
    /thread/1551768 [original link is broken]
    NWDS Compatability issue
    Thanks,
    pradeeP

  • Upgrade linux Red Hat version 4 to Red Hat version 5 on an appliance CWWLSE-1130-K9

    Hi.
    I have a WCS 5.0 installed on an appliance CWWLSE-1130-K9 to Red Hat Linux 4.0. I need to upgrade to Linux Red Hat version 5 in order to use WCS version 6.0. Does anyone know the procedure to do it?

    You do need to have either your WLSE under warranty or a TAC smartnet contract for support on this device as far as product evolution and upgrades.
    You may have a support contract since you have a WCS.

  • Compatible NWDS version for SP 22 ?

    Hi All,
    We are using NW2.0 version, EP 6 version.
    Client has upgraded only the QA portal to SP 22.
    (not sure about DEV sp details)
    Note: DEV portal and QA portal are not in same patch level.
    Which is the compatible NWDS version for SP 22?
    Please suggest.
    Regards,
    Subashini.

    Hi,
    Did you check the PAM?
    https://websmp107.sap-ag.de/pam
    Regards
    Ayyapparaj

  • NWDS version for WebDynpro Java

    Hi,
    I have WAS 7.0 SP10 ABAP+Java. NWDS and WAS needs to be on the same SP. But servicemarketplace has got only SP4 and SP15.
    Could you advise on which version is the right one to download?
    Regards,
    Shobhit

    Hi,
       SP4 should be the right one to download since NWDS version must not be newer than the Web AS version.
    Regards,
    Satyajit.

  • What's the correct Red Hat version?

    Good morning.
    We want to install MySAP ERP 2005 on Linux on a IBM xseries 346 64 bit.
    I've seen that Red Hat EL 4 is certified by SAP
    In this page, http://www50.sap.com/linux/platforms/index.asp, is also specified the kernel to use.
    But I haven't find any other suggestions on http://service.sap.com/pam
    I'm a little bit confused about the correct version: AS, ES... 4.2, 4.4, 5?
    Can anyone please give me a suggestion about the correct version to choose??
    Regards,
    Luca

    This is the java version that I've installed:
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
    IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060824 (JIT enabled)
    J9VM - 20060802_1551_LHdSMr
    JIT  - r7_level20060707_1808ifx1)
    I've not yet set JAVA_HOME variable, nor PATH. Any other "customization" to do?
    This is the last part of the "import.monitor.java.log" when start errors:
    Import Monitor jobs: running 3, waiting 31, completed 38, failed 0, total 72.
    Loading of 'SAPAPPL0_9' import package: ERROR
    Import Monitor jobs: running 2, waiting 31, completed 38, failed 1, total 72.
    Loading of 'SAPAPPL1_9' import package: ERROR
    Loading of 'SAPAPPL2_5' import package: ERROR
    Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
    Import Monitor jobs: running 0, waiting 31, completed 38, failed 3, total 72.
    Import Monitor jobs: running 1, waiting 30, completed 38, failed 3, total 72.
    Import Monitor jobs: running 2, waiting 29, completed 38, failed 3, total 72.
    Import Monitor jobs: running 3, waiting 28, completed 38, failed 3, total 72.
    Loading of 'SAPSSEXC_6' import package: ERROR
    Import Monitor jobs: running 2, waiting 28, completed 38, failed 4, total 72.
    Loading of 'SAPSSEXC_2' import package: ERROR
    Import Monitor jobs: running 1, waiting 28, completed 38, failed 5, total 72.
    Loading of 'SAPAPPL0_5' import package: ERROR
    Import Monitor jobs: running 0, waiting 28, completed 38, failed 6, total 72.
    Import Monitor jobs: running 1, waiting 27, completed 38, failed 6, total 72.
    Import Monitor jobs: running 2, waiting 26, completed 38, failed 6, total 72.
    Import Monitor jobs: running 3, waiting 25, completed 38, failed 6, total 72.
    Loading of 'SAPAPPL0_1' import package: ERROR
    Import Monitor jobs: running 2, waiting 25, completed 38, failed 7, total 72.
    Loading of 'SAPAPPL0_8' import package: ERROR
    Import Monitor jobs: running 1, waiting 25, completed 38, failed 8, total 72.
    Loading of 'SAPAPPL0_6' import package: ERROR
    Import Monitor jobs: running 0, waiting 25, completed 38, failed 9, total 72.
    Import Monitor jobs: running 1, waiting 24, completed 38, failed 9, total 72.
    Import Monitor jobs: running 2, waiting 23, completed 38, failed 9, total 72.
    Import Monitor jobs: running 3, waiting 22, completed 38, failed 9, total 72.
    Loading of 'SAPAPPL0_4' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 38, failed 10, total 72.
    Loading of 'SAPPOOL' import package: ERROR
    Import Monitor jobs: running 1, waiting 22, completed 38, failed 11, total 72.
    Loading of 'SAPSDIC_1' import package: ERROR
    Import Monitor jobs: running 0, waiting 22, completed 38, failed 12, total 72.
    Import Monitor jobs: running 1, waiting 21, completed 38, failed 12, total 72.
    Import Monitor jobs: running 2, waiting 20, completed 38, failed 12, total 72.
    Import Monitor jobs: running 3, waiting 19, completed 38, failed 12, total 72.
    Loading of 'SAPSSEXC_11' import package: ERROR
    Import Monitor jobs: running 2, waiting 19, completed 38, failed 13, total 72.
    Loading of 'SAPSSEXC_8' import package: ERROR
    Import Monitor jobs: running 1, waiting 19, completed 38, failed 14, total 72.
    Loading of 'SAPAPPL1_11' import package: ERROR
    Import Monitor jobs: running 0, waiting 19, completed 38, failed 15, total 72.
    Import Monitor jobs: running 1, waiting 18, completed 38, failed 15, total 72.
    Import Monitor jobs: running 2, waiting 17, completed 38, failed 15, total 72.
    Import Monitor jobs: running 3, waiting 16, completed 38, failed 15, total 72.
    Loading of 'GLFUNCA' import package: ERROR
    Import Monitor jobs: running 2, waiting 16, completed 38, failed 16, total 72.
    Loading of 'SAPAPPL1_2' import package: ERROR
    Import Monitor jobs: running 1, waiting 16, completed 38, failed 17, total 72.
    Loading of 'SAPAPPL0_10' import package: ERROR
    Import Monitor jobs: running 0, waiting 16, completed 38, failed 18, total 72.
    Import Monitor jobs: running 1, waiting 15, completed 38, failed 18, total 72.
    Import Monitor jobs: running 2, waiting 14, completed 38, failed 18, total 72.
    Import Monitor jobs: running 3, waiting 13, completed 38, failed 18, total 72.
    Loading of 'SAPSSEXC_13' import package: ERROR
    Import Monitor jobs: running 2, waiting 13, completed 38, failed 19, total 72.
    Loading of 'SCPRSVALS' import package: ERROR
    Import Monitor jobs: running 1, waiting 13, completed 38, failed 20, total 72.
    Loading of 'SAPAPPL1_6' import package: ERROR
    Import Monitor jobs: running 0, waiting 13, completed 38, failed 21, total 72.
    Import Monitor jobs: running 1, waiting 12, completed 38, failed 21, total 72.
    Import Monitor jobs: running 2, waiting 11, completed 38, failed 21, total 72.
    Import Monitor jobs: running 3, waiting 10, completed 38, failed 21, total 72.
    Loading of 'SAPAPPL0_3' import package: ERROR
    Import Monitor jobs: running 2, waiting 10, completed 38, failed 22, total 72.
    Loading of 'SAPSDOCU' import package: ERROR
    Import Monitor jobs: running 1, waiting 10, completed 38, failed 23, total 72.
    Loading of 'SAPAPPL1_3' import package: ERROR
    Import Monitor jobs: running 0, waiting 10, completed 38, failed 24, total 72.
    Import Monitor jobs: running 1, waiting 9, completed 38, failed 24, total 72.
    Import Monitor jobs: running 2, waiting 8, completed 38, failed 24, total 72.
    Import Monitor jobs: running 3, waiting 7, completed 38, failed 24, total 72.
    Loading of 'SAPSLOAD' import package: ERROR
    Import Monitor jobs: running 2, waiting 7, completed 38, failed 25, total 72.
    Loading of 'SAPSSEXC_1' import package: ERROR
    Import Monitor jobs: running 1, waiting 7, completed 38, failed 26, total 72.
    Loading of 'SAPSPROT' import package: ERROR
    Import Monitor jobs: running 0, waiting 7, completed 38, failed 27, total 72.
    Import Monitor jobs: running 1, waiting 6, completed 38, failed 27, total 72.
    Import Monitor jobs: running 2, waiting 5, completed 38, failed 27, total 72.
    Import Monitor jobs: running 3, waiting 4, completed 38, failed 27, total 72.
    Loading of 'SAPDFACT' import package: ERROR
    Import Monitor jobs: running 2, waiting 4, completed 38, failed 28, total 72.
    Loading of 'SAPDDIM' import package: ERROR
    Import Monitor jobs: running 1, waiting 4, completed 38, failed 29, total 72.
    Loading of 'SAPUSER' import package: ERROR
    Import Monitor jobs: running 0, waiting 4, completed 38, failed 30, total 72.
    Import Monitor jobs: running 1, waiting 3, completed 38, failed 30, total 72.
    Import Monitor jobs: running 2, waiting 2, completed 38, failed 30, total 72.
    Import Monitor jobs: running 3, waiting 1, completed 38, failed 30, total 72.
    Loading of 'SAP0000' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 38, failed 31, total 72.
    Loading of 'SAPUSER1' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 38, failed 32, total 72.
    Loading of 'SAPDODS' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 38, failed 33, total 72.
    Can you have some suggestions to solve the problem?
    <b>Can I retry to resume installation from the point 17 or I've to start from the beginning and clear my last installation?
    </b>

  • NWDS Version usage

    Hi,
    One simple clarification with respect to NWDS.
    Can you please confirm I can use NWDS 7.0.15 for enhancing and bug fixing of WD and PAR component that are been developed on NWDS 2.0.19 version ??
    Regards,
    Sushil Jain
    Edited by: SushilBlr on Dec 21, 2009 10:23 AM
    Edited by: SushilBlr on Dec 21, 2009 10:23 AM

    Hello Chintan,
    "Most likely yes, but you will need to repair & rebuild your projects."
    Where can i find documention on this topic ?
    Kond regards.
    Dirk

  • How to know the nwds version ?

    Hi,
    how can i find whether my nwds is which version of the following ?
    NW04s SP09 (Hotfix from 7. March 2007)
    NW04s SP10 (Hotfix from 9. March 2007)
    NW04s SP11 (Hotfix from 11. April 2007)
    NW04 SP18 (Hotfix from 17. April 2007)
    NW04 SP19 (Hotfix from 9. March 2007)
    thanks in advance for help
    dipti

    Hi dipti ,
    In NWDS studio, in Help tab you will find "About NetWeaver DeveloperStudio" tab. Ther you will get the version
    Regards
    Sagar Ingalwar

  • NWDS Version?

    Hello,
    i want to install the nwds for our pi 7.11 ehp 1 installation on my computer and found this site to download it:
    https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/711/NWDS_platform.html
    Can i just take the latest release?
    What das the PAT mean in SP/PAT?
    SP = Service Pack, PAT = ?
    Is the AS Java SP always the same as in ABAP?
    I know i can see the SP-level in the abap system over System>Status>Component Information>Level, does this correspond to the AS JAVA? Where can i see this in JAVA?
    Thanks in advance!
    Kind regards,
    Markus

    Download version NWDS 7.2. This is compatible for latest features of 7.1 + versions.

  • NWDS version? Where do i downwload it from?

    Dear All,
    I am new to this whole BPM thing !
    We have a CE v7.1, and I would like to know :
    1. Which version of NWDS to use? - I guess there were some issues with some versions, creating some errors
    2. Where can I download it from?
    Many thanks!
    -Rohit

    Hi Rohit
    I use the last trial version - NWDS 7.1 EHP1 SP1 - and i found some issue too. When i mapping node with cardinality greater than 1.
    Is this your issue? If yes there are some way to resolve.
    You can download the trial version of nwds in this directory:
    [https://www.sdn.sap.com/irj/scn/nw-ce-downloads|https://www.sdn.sap.com/irj/scn/nw-ce-downloads]
    Regards
    Marcos

  • Large PNG shows up red in version 9.0.115.0

    For this project we did we used a very large PNG in the
    background (about 9800px in width). I know it's not the most
    efficient way of doing this... next time we'll probably chop it up
    into smaller pieces.
    The problem as of playerversion 9.0.115.0 is that this large
    PNG shows up red in the background. I've tested it in FIrefox with
    flashswitcher and in any version lower than this an higher than 8
    it shows up perfectly. The problem seems to appear on a Mac as well
    but i don't have one i can use to test this on.
    I've put up a test version of the problem here:
    http://clients.merge-media.com/ara/test/test.html
    You can download the test fla here:
    http://clients.merge-media.com/ara/test/test.zip
    (25mb)
    Does any of you guys know if there's a workaround for this or
    maybe something to fix this?
    Thanks in advance,
    J.

    Did anyone open a support case for this?
    http://www.adobe.com/support/contact/
    Important Note: These online forums are for user-to-user
    discussions of Adobe products, and are not an official customer
    support channel for Adobe. If you require direct assistance, or
    prefer to contact Adobe support staff directly, please contact
    Adobe support.

  • 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

    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

Maybe you are looking for

  • Why do I keep getting an error message when trying to use passbook?

    Why do I keep getting an error message when trying to use passbook?

  • List status function in menu of  ALV list is not active

    Hi, Most output of reports in SAP PM (like IW28 or IW38) is based on ALV (SAP list viewer). I used to have a list status function that reported amongst others the number of records in the report. You can find this function in the menu: settings -> li

  • Time Machine and USB Drive

    I use Time Machine to backup my datas. The problem is that my HDD (on my MAC) was full, and added an Firewire DD on my MAC. Is it possible to include my firewire in the backup on Time Machine ( no problem with the capacity of this drive)?

  • Pictures Order: Version & Stacks jumps to end when worked on?

    Has anyone experienced pictures jumping around when they are worked on in the Standard Layout Mode? More specifically when I create a new stack or a new version of a master file I am editing, it systematically jumps to the end of the whole project or

  • IS THERE ANY WAY TO FORCE KEY COMMIT

    Hi: Is there any way in forcing when inserting/updating a record in a block to call KEYCOMMIT. For Example, if the user inserted/updated a record and before saving the user may quit the form. I would like to enforce the keycommit trigger to be called