NWDI Upgrade !

Hi All,
We need upgrade our application from SPS18 to SPS20.I am unable to find related notes on SAP service. Can of you help me in finding the actual notes to be analyzed on SAP services.
I am not sure what all documents I am supposed to look into before upgrading application. 
Thanks and Regards ,
Vanita kulkarni

Dear Vanita,
Please go through Ervin's reply thoroughly, it covers your doubt.
Always remember one rule.
For every new release version of Application server, there's a compatible version of developer studio (NWDS).
And as per the best practice, we should always work in the version homogeneity as explained earlier.
So, If you are upgrading you EP server from...
version 7.0 EhP(A) SP(X) to version 7.0 EhP(A) SP(Y) ,where X < Y then,
you need to download the same developer studio version too, from SAP service marketplace.
And yes, all your existing projects will still work in the upgraded environment, as it is backward compatible.
You may encounter the obsolete warnings for certain projects,
but still you will be able to build and deploy your projects successfully without any compilation errors.
Also remember, that if you have NWDI in your landscape,
then, as a part of upgrade (in your case SP16 to SP20) you need to download the same version of .SCA files from SAP service marketplace and paste it into CMS transport directory (<specified in the domain tab>\CMS\inbox) in order to make these dependencies available for your tracks.
and then update all your tracks runtime systems, (Dev and Cons) with this latest version of SCAs that you will be using as a build time dependencies in your track SC as descibed in below mentioned procedure.
Step-by-step procedure for adding the new release of build time dependencies to your track.
1) Open the following URL to access NWDI web interface www.http://<hostname>:<port number>/devinf
2) goto Change Management Services
3) Open System Landscape Directory
4) Click on Software Components
5) Here in the Filter give your Software Component name
6) after the serach is over select your SC in the table and the below displayed tabs goto Dependencies.
7) in the Context dropdown chose "BuildTime"
8) click on "Define Prerequisite Software Component Versions"
7) In the Name column of the table search for the standard SC dependencies that you desire (for e.g. SAP-JEE, SAP_BUILDT, SAP_JTECHS) and then add one by one as a dependencies.
8) once you are done with this, go back to the 2nd step mentioned above.
9) Goto the Landscape Configurator link.
10) Chose your track inside the table on the left side.
11) goto the Domain Data option, Click on the "Change" button, and then click on "Update CMS" button (This may take some time)
12) once the CMS Update is finished, open the "Track Data" link that is beside "Domain Data"
13) Now click on the "Change" button, from the software component (SCs) table remove the WebDynpro SC, and add it back once again.
14) Save the Track Data.
15) Now goto Transport Studio, make sure your track is selected in the table
16) In the Check-In Tab select all the components displayed in the "Check-In" button.
17) Once the Check-In operation is completed all those component will now be queued up in the Development Tab,
18) In the Development Tab select all the components & click on "Import"
19) Once the Import operation is completed all those component will now be queued up in the Consolidation Tab,
20) In the Consolidation Tab select all the components & click on "Import"
21) Now come back to your NWDS and remove the configuration that you have imported previously and then again load the same configuration once again from the SLD.
You can repeat the same procedure for all your tracks present in your landscape.
Please revert in case of any further clarifications.
Regards,
Shreyas Pandya

Similar Messages

  • NWDI upgrade - Target Release Components

    Hello everybody!
    Currently, we are trying to upgrade our NWDI from 7.0 to 7.31. During the upgrade process of the server that contains DTR, CMS and CBS, in step 5.3 "Configuration - Information Gathering" we get a list of Java components (Target Release Components) with some additional information and the option to either remove these components or to "scan inbox" for component versions for NetWeaver 7.31.
    In this list, there are some components with a component name that matches the application name of some (not all) applications we developed (like anlUsrWD in the heavily edited and shortened screenshot below):
    My question is: What exactly do these items (those that match some of our self-developed applications) in this list represent ? Are they essential for CBS, CMS or DTR ?
    A long time ago, this server was used as a test portal server. Maybe these are leftovers from past deployments that can be deleted, but maybe they are needed on this server and our build and deploy processes will no longer work without them, maybe even DTR will no longer work. We are in no way sure of what we have to do with them.
    Can anyone help ?
    Thanks
    Michael

    Hi Michael,
    Hope you are doing good.
    Nice to hear from you again. The SUM guide has more details about this as the status changes if the server which is configured as runtime or not.
    Any components that you have modified in the source release have the status Managed by NWDI on the selection screen for the target release components. These components are not deployed during the update. After the update, you take the components from the NWDI transport directory and perform the modification adjustment by using the NWDI. You then deploy the adjusted software components (SCs) to the updated development or consolidation system.
    Else, you can deploy them manually at a later point of time with say the telnet tool ( note 1715441).
    Hope this helps.
    Kind Regards,
    Hemanth
    SAP AGS

  • To build all the DC because of NWDI upgrade

    Hi All,
    We are version upgrade of all the SC in the NWDI. Now because of this we had to build all our existing application once again. Since there are huge number of components so building each of them in NWDS could be very tedious task. Is there any way to build all the application directly from NWDI.
    Thanks and Regards,
    Vivek Saraogi

    Hi Vivek,
    Yes, it is possible to build all your DC inside your Track at one shot.
    This is possible from the Component Build Services (CBS) Web UI.
    But, before doing that you have to make sure that all the upgraded .SCA files are present inside CMS/inbox transport directory.
    And your track SC is has all the upgraded build-time dependent .SCA files added in SLD.
    You have updated the CMS and imported this new .SCA dependencies into Development and Consolidation runtime systems of your track.
    Now, to build all the DCs inside your Track at one go, you can build the entire SC from CBS and check the build status of each DC after the build operation is over.
    Please follow the below mentioned procedure to do the same.
    1) Goto Component Build Services (CBS) Web UI.
    2) Buildspaces >> Select the "<SID>_<Track-ID>_D" build space.
    3) Select your Track SC in the the first table and click on the Build button to build the entire SC.
    4) This will pop up an activation request.
    5) once the Activation is over check the activation request status.
    6) Now check the build status of all the DC under the same screen (path described in point 2).
    7) If all the DCs show green status then it implies that, if you reimport the track in developer studio, and then build all the DCs, then it should give the same build status results. as it is appearing in the CBS.
    I hope that helps.
    Regards,
    Shreyas Pandya

  • How to get the new dependency SCA's related to  7.4 version with out upgrading NWDI server

    Hi
    We are in process of upgrading the custom webdynpro and portal components to SAP Portal  7.4.
    I saw in some discussions that, we don't need to upgrade NWDI , we need to install new JDK version(1.6) to map that jdk to the new track for migrating the custom component to new track.
    But i have questions related to NWDI track dependency files.
    When i create new track to support 7.4 components need to be available in the respective track.
    we have central SLD and we create all the product and custom software components in that SLD(7.01) itself , To create the custom software component in SLD , i add  required dependency files. once the software component is ready, when i create the track  in nwdi system i will be able to fetch the custom software component in nwdi system by click on cms update.
    But now i  need following new new dependency software component versions   in SLD  related to  7.4 for creating new software component to those dependency's to support the new track in NWDI.
    EP_BUILDT
    SAP-JEE
    SAP_BUILDT
    SAP_JTECHS
    But my SLD server version is : 7.01 version.
    so do i need to upgrade the SLD server to  7.4 get the latest dependent SCA's  or just need import new SLD content in SLD server to add new custom software component to create?
    kindly advice how to get the new software components  in SLD without upgrading the NWDI  & SLD system to  7.4
    Thanks

    Jun,
    Thanks for the reply.
    But i am not able to find the  following two SCA's related to 7.4 version. I am able to find the rest of the SCA's. I able to see only 7.02 version related to following dependency files.
    SAP-JEE
    SAP_JTECHS
    SAP-EU (CA EU)  ( having only 7.01, 7.02, 7.10, 7.11 and 7.20) related to Guided procedures.
    Did they changed any naming conventions related to these software components? if so what are new software compnents names to use
    Please clarify.
    Thanks
    Vijay

  • NWDI in upgrade project - Recommendations

    Dear All,
    We are upgrading ECC and Portal. Earlier client doesn't have NWDI.
    Now we are using NWDI, so the customer wants the below recommendations.
    1. Provide a recommendation for use of NWDI within the Upgrade project.
    2. Provide a recommendation for possible ongoing / expanded usage of NWDI at the project.
    Please provide your suggestions.
    Thanks.

    Hi,
    1. If you are implementing ESS/MSS you can upgrade the components using NWDI.
    In general for deploying components you either use JSPM or SDM to deploy. And NWDI uses the same method to deploy the components.
    It's upto you to use NWDI or to deploy them directly.
    Recommendation would be if implementing ESS/MSS you can use NWDI. If you are not modifying the standard SAP Delivered component then you can deploy the components directly.
    2. It depends on what all things are you planning to implement.
    Hope this helps.
    Cheers-
    Pramod

  • Upgrade Plan - Web Shop - NWDI

    Hi Experts,
    My customer has planned to upgrade their portal from version 7.01 to 7.02 SPS4. They have four environments namely Dev, Quality, Acceptance & Production. They plan to upgrade Dev first, followed by Acceptance & then Production. (Quality is kept as it is for incident mitigation till Production is patched)
    The portal is effectively an e-commerce portal which has both portal components & Web shop deployed on it. The Web Shop code is hosted on NWDI which is configured to build the Dev server once the code is checked in.
    Now these are my questions:
    1. Lets say that while Dev is being upgraded, we need to fix a critical incident involving web shop code. Can we configure NWDI to build Quality rather than Dev. The current setup is that transports need to be done sequentially i.e. D->Q->A->P.
    And even if build fails in Quality, can i directly configure NWDI to point to production and do the build there?
    2. Is it possible to register the same instance multiple times (say quality instance)under 'target instance'. Will this help me at all?
    Regards,
    Ramanathan Palaniappan

    Hi Ramanathan,
    First of all let me make one thing clear.
    No matter how many Runtime systems you have in your landscape (In your case D->Q->A->P), your NWDI usage type or instance, whether it is hosted on your Development Server or some different host separately is common across these systems.
    To give you more clarity you need to understand the following concepts.
    1) Your Landscape consists D->Q->A->P.
    2) Here, lets assume that NWDI is running on your Development Server D.
    3) That means all the 3 pillars (DTR, CBS & CMS) of NWDI are present in Dev host.
    4) Now, Suppose are maintaining a Track named "Track-A"
    5) Whatever developments that are carried out (Source Code Modification) specific to "Track-A" are available in the DTR-Server present Dev Host only.
    6) So, the Build process is also specific to Development Host ONLY
    7) You cannot use terms like "Can we configure NWDI to build Quality rather than Dev", it simply doesn't make sense.
    OK, so far so good.
    Lets move further ahead.
    There's a big difference between Build process and Deploy Process.
    1) When you create a Track, you need to define the Runtime Systems of your Track.
    2) When you define runtime systems, your purpose is to provide information to the CMS about--> to which all systems you will be DEPLOYING your Compiled Source Code (Which is in the form .SCA that is created as an output in Assembly step) 
    3) Build Process as explained above happens only on Development Host in Development Buildspace and Consolidation Buildspace of your Track.
    You can also refer to the thread where i have explains step-by-step process about what happens under the hood in NWDI
    Re: Comparing records in Update Rules
    Now, if you meant to configure NWDI to point Quality rather than Dev in terms of Deployment only then Yes, It is very much possible.
    Follow the below mentioned procedure...
    1) Open the CMS Web UI >> Landscape Configurator >> Track Data >> Runtime Systems
    2) Here, you can configure your runtime system as you wish.
    3) For Example if you want to skip the deployment into Quality and directly deploy in production then you can uncheck the "Test" from Selected Runtime Systems.
    After you modify the setting in Runtime systems in Landscape configurator, then relevant changes will be reflected in the Transport Studio of your track. Considering the above example The "Test" tab will not be available.
    I hope my inputs will help you resolve your query.
    Regards,
    Shreyas Pandya

  • How to upgrade NWDI

    I want to upgrade my current NWDI server from 7.0 to EHP2.
    Which tool do I use? JSPM or EHPI?
    Thanks
    Jex

    Hi Jex,
    Please Look at these threads.
    [How To upgrade SAP NWDI (JDI) system   |How To upgrade SAP NWDI (JDI) system;
    [Upgrade Using SAPJup (SAP Library - Maintenance of an NWDI-Driven System Landscape|https://cw.sdn.sap.com/cw/docs/DOC-108684]
    [Maintenance of an NWDI-Driven System Landscape|http://help.sap.com/saphelp_nw70/helpdata/en/43/26b84d6c823f66e10000000a11466f/content.htm]
    [Upgrade NWDI driven system  |Upgrade NWDI driven system;
    Hope this is help full for u..
    Regards
    Vijay Kalluri

  • Portal-XSS Upgrade - Which version of NWDI/DI

    Hi,
    in a landscape with
    Instance 1 : Java - Portal/ERPXSS
    Instance 2 : ERP/HR
    Instance 3 : NWDI/DI for customization of XSS
    we are planning to upgrade to ERP/XSS SP15 and  Netweaver Portal SP17
    The Question:
    Can anybody tell, which version of DI we have to take?
    Is it possible to take the newest version of DI (7.0/EHP1 or even 7.1), because lower versions can be controlled by build plugs?
    Which NWDS - Version do we need then?
    Thanx in advance,
    Andi Lorinser

    Hi,
    the point is the following.
    With a dedicated NWDI-Server we might serve different Patch-Level of Java Code. Let's say ERP/XSS/SP14 on the one side and CE-Components on the other side.
    So if we take the newest version of NWDI-Server and developping for XSS/SP14. Does this work and what version of NWDS do we need for this scenario?
    Thanx Andi

  • XSS Upgrade to EhP3 - NWDI track question

    All,
    We are Upgrading XSS SP11 Ehp 1 to XSS SP14 Ehp 3.
    We have upgraded our ECC system, Portal system, We have deployed the related Business Packages.
    So far so fine. Then we come to the toughest part.
    Source code upgrades in NWDI
    We created two tracks XSSSP14 and XSS14MOD
    XSSSP14 does not have RTS as this will only be used for comparision
    XSS14MOD has runtime sysetm.
    Here is my question. For XSS14MOD, ( which will 'finally' have SP11 mods + SP 14) when we create runtime system, DO WE or NOT "disable automatic deployment" in the dev system.
    The question is becuase of the following thoughts of mine.
    If we do not 'disable automatic deployment', then SP14MOD will overwrite all SP11+MOD with standard SP14 code when we do the initial import to development system when creating the track. Is this alright, ? Please advise.
    And can anyone throw light on to their expereinces doing the manual comparisions and any better ways to track and implement changes. This is a hell lot of owork and is a project in itself

    Thanks Shikhil.
    FYI ... i am following the cookbook steps
    As much as have I closed the message, I would really appreciate if you can let know your experience, any pitfalls that you may have noticed during the upgrade etc
    Thanks Again

  • Migrating/Upgrading NWDI from 7.0 to CE 7.1

    Hi,
    Currently we have application developed on NW 7.0 (Web Dynpro, J2EE, EJB etc) and we have NWDI 7.0 for code repository.
    Now we are planning to migrate the NW 7.0 (Web Dynpro, J2EE, EJB etc) to CE 7.1 (we have documents & procedure to do this).
    My question is:
    1. Does repository NWDI 7.0 supports for all kind of DC/applications if we migrate NW 7.0 (Web Dynpro, J2EE, EJB etc) to CE 7.1, If not what are the chanllenges?
    2. Is it required to upgrade repository from NWDI 7.0 to NWDI CE 7.1? If so how we can achieve/migrate the code to NWDI 7.1
    Please suggest.
    Regards,
    Patana

    Hi Patana,
    Let me give you some background first...
    *1) Yes, NWDI 7.0 will support all the developments that you will be migrating to CE 7.1
    2) There is no 7.1 version of NWDI, that means you ned not worry about NWDI version as, it is just a platform that acts as repository for your source code and version control.*
    So you don't need to upgrade your NWDI.
    But wait it doesn't mean that you don't have to upgrade anything from NWDI side .
    As your Application Server will now be running on 7.1 version, you will have to get a compatible CE 7.1 version of developer studio too.
    Also the Tracks that are present in your NWDI 7.0 version will be required to be upgraded with the latest build time dependent SCA files of the 7.1 version too.
    This is a step-by-step guide for setting up NWDI for Composition Environment.
    Link:[HOW TO SETUP AN NWDI TRACK FOR COMPOSITION ENVIRONMENT DEVELOPMENT (SAP NETWEAVER CE 7.1)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
    To update all the tracks with the latest .SCA files, follow the below mentioned steps...
    1) you need to copy all the standard .SCA files of 7.1 version from the path /usr/sap/<SID>/SYS/EPS/buildarchives/ as mentioned in step 10 of the above manual to the CMS transport directory (<specified in the domain tab>CMSinbox) directory in order to make these dependencies available for your tracks.
    2) Then, in SLD you have to modify all your software components that are used in track and replace all their build time dependencies to the 7.1 version.
    3) Update the CMS,
    4) Remove and add the tracks SCs back for your track.
    5) Save the track, while saving always choose Save & Re-import button.
    6) Check-In the latest 7.1 version SCA into Development and Consolidation tab.
    You have repeat this for all the tracks.
    Please revert in case of any further clarification.
    You can also refer to the thread Re: source code of a track nwdi, for understanding how NWDI works under the hood.
    Regards,
    Shreyas Pandya

  • JSPM_MAIN error in upgrading netweaver- NWDI related error, please check !

    Here is the proper step by step explanation
    1.)Before any patching the portal
    The SP level of EP was SP17 and the ESS/MSS and the SAPPCUI_GP was at 600 .11
    2.)The we patched the EP to EHP1 using EHPI installer. Which was done without errors.
    3.) Then we patched the MSS to 600.15 and the SAPPCUI_GP to 603.4.1.
    4.) The ESS Needs to be patched to 603.4.1, but while patching we got the following errors attached.
    The first screen shot is the error we had received first. we resolved it by creating that directory.we donu2019t know why this directory it asked for.
    Please refer to this link
    JSPM error for applying ESS patch
    The second screenshot is the error where I am stuck.
    The 3 rd screen shots shows that the ESS is modified by NWDI.
    Can someone please explain as to what is the way out, or what it needs to be done in NWDI.
    for all the trace files and the screenshots... please download below file.
    http://rapidshare.com/files/300025619/ESSIssue.7z

    Hi,
    The problem has been solved,
    The prerequisite to the patching of the portal were not met initially.
    REgards,
    Rajat

  • NWDI Components not available after patch upgrade

    Hi,
    After upgrading patch 11 to 13 the existing components are not available in the track. What could be the reason for this?
    Thank,
    Padmanaban

    Hi,
    As I mentioned before the SCs cannot get away from the CMS track definition unless they are deleted manually. Is it the problem with the required SCs or Developed SCs?
    You can also check in the CMS who has saved the track last and then consult them if they did any manual deletion?
    What about CBS? If you are not able to see it in CMS then I am sure you cannot have the respective buildspace there as well. But if you see it in CBS and not in CMS, then it is strange.
    One more way is --> If you see the content/SCs(Developed SCs) in the corresponding DTR, then you can add the SCs again to CMS track definition, this will create the buildspace for those SCs in CBS if they are missing.
    Akshatha

  • Can Upgradation of NWDI track be reverted????

    Hi,
    I am facing an issue... Mine
    1) import com.sap.xss.hr.per.in.address.review13.wdp.IPrivateReviewView_13; error could not be resolved.
    2)Have lost all the last changes also from the development component.
    As my basis team has upgraded the track.
    How to resolve the issue.
    Thanks,
    Sweta

    Hi experts,
    Please any one give me solutions.
    Thanking U.
    Sweta

  • Error While Creating Runtime Systems on an Existing Track in NWDI

    Hi,
    There is already a track in NWDI with No runtime Systems.
    I have to create the RunTime Systems to do development on this track.
    When I try to select the Development checkbox in Runtime systems,
    select configure  without wizard, Gave   Deploy Host name: **********.com
                Deploy Port :50018  (SDM port)
               Deploy PSWD:  SDM Pswd
    It gives me a warning..
    Synchronization of Runtime System triggered for system dev. Log can be found at
    http://*****************************LogViewer?LogName=%2Fsapmnt%2FEPQ%2Fglobal%2FTCS%2FLOG%2FEPQ_WHRBD_D2010081322030045.log&Bsname=EPQ_WHRBD_D
    When i go to the  log file
    I see this Error Message
    20100813180502 Info   :cannot create a connection for the buildspace:  EPQ_WHRBD_D //connect to deploy tool failed:Server <Host Name> did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to <Host name> at port 50018: Connection timed out:could be due to invalid address
    Can you please tell me what could be the Reason.
    Basis has already opened the Ports : http port and SDM Port.
    I am able to ping the server from cmd prompt.
    Points will be allocated for the answer.
    Thanks.
    Venkat

    Hi,
    There's no need to update CMS or to check whether the buildspace is open, do not click on JSPM flag (unless you need nwdi control at upgrade)...
    The error message means only that from the host where you configure the RTS the SDM cannot be reached or logon request cannot be accepted.
    This can be either , because the
    - SDM password is wrong (you checked it already)
    - the port is wrong (you also checked it. If this is really a 700 RTS, i.e. it has SDM, and the instance number is 00, then the port is really 50018, so this should be fine as well. Only mention, because as of 71X we use the P4 port 5<xx>04 for the deploy controller, as there's no more SDM). Still you can use "netstat -a" to see the status of the ports.
    - The host is wrong. I agree with Dao, check not only FQDN, but also IP address.
    Using this guide you can always check whether the entered data is correct:
    http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002
    Best regards,
    Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

  • Check-in tab is not working in NWDI

    Hi Gurus,
    We have one NWDI (SP9) server instance installed on our EP Box(SP11),both of them have common oracle database.we have upgraded the patch level of NWDI also to SP11,run the template installer,configured the SLD and CMS.Our SLD is the XI box with SP stack 15 latest.All of these are development machines.
    But in CMS,under the Transport studio -->check-in tab,the check-in button is greyed out.
    Can anybody tell us the reason for this,we are not able to import any sca's(archive files) bacause of this ?
    Early and useful responses will be rewarded.
    Thanks & Regards
    Saurabh Sharma
    Edited by: Abhishek Goel on Jun 3, 2008 3:50 PM

    Hi,
    Yes I have.
    In my Track data,it is showing:-
    Software Components (SC)
    Software Components for development
    BP_ERP4ESS        Release 60.1
    BP_ERP4MSS       Release 60.1
    NWDIDEMO           Release 1.0
    Required Software Components
    SAP_JEE                    Release 7.0
    SAP_BUILDT               Release 7.0
    SAP_JTECHS              Release 7.0
    but still the check-in tab is greyed out.
    Kindly please suggest some solution.
    Regards
    Saurabh

Maybe you are looking for

  • Different Batch Classification at storage location level

    Dear guru , I have tested that i can insert different values of batch classification for the same material and the same batch number but in different plants. In MSC1N/MSC2N transaction the system allow a insertion at storage location level. Itu2019s

  • Creation of empty target group---URGENT!!!!!!!

    Hi...    I have a scenario in campaign automation where i need to create a target group automatically when ever a  customer clicks on yes/no in the survey.       I hope there is a standard workflow which creates target grooup.but do we need to have a

  • Illustrator CC is slow and crashes every time i close a file

    Illustrator CC is slow and crashes every time i close a file. Can anyone help me please? This is the report after the crash:   Adobe Illustrator [692] Path:            /Applications/Adobe Illustrator CC/Adobe Illustrator.app/Contents/MacOS/Adobe Illu

  • Afte mirgation from SP 2010 to 2013, change the search box image size in sharepoint 2013

    Hi, After migration from 2010 to 2013, the search box image size increased. Pls check the screenhot below, I i need to resize this searc image. Any help is much appreciated. Thanks Smile Always

  • Assignment of Cost Center

    Dear all, We want to do a manual posting into the Excise Duty on Sales G/l through F-02 but system is throwing an error Account 123456 requires an assignment to a CO object even if give a cost center then also the problem exists.We have maintained De