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

Similar Messages

  • HOW TO UPGRADE FROM Release 10.2.0.1 TO 10.2.0.2

    Hi,
    HOW TO UPGRADE FROM Release 10.2.0.1 on Linux TO 10.2.0.2 ? Should we apply a patch ?
    Thank you.

    thank you. Of cours, I looked at metalink site for
    RDBMS patch familly, but I did not find any for
    upgrading from 10.2.0.1 TO 10.2.0.2
    Regards.
    Message was edited by:
    user522961What's your target OS ?
    Why are you specifically want this version?
    As you can see from Oracle download page, some OS come with 10.2.0.2 directly.
    http://www.oracle.com/technology/software/products/database/index.html
    Oracle Database 10g Release 2 (10.2.0.3) for Microsoft Windows Vista
    Oracle Database 10g Release 2 (10.2.0.1.0) for Microsoft Windows
    Oracle Database 10g Release 2 (10.2.0.1.0) for Microsoft Windows (x64)
    Oracle Database 10g Release 2 (10.2.0.1.0) for Microsoft Windows (64-bit Itanium)
    Oracle Database 10g Release 2 (10.2.0.1.0) for Linux x86
    Oracle Database 10g Release 2 (10.2.0.1.0) for Linux x86-64
    Oracle Database 10g Release 2 (10.2.0.1.0) for Linux Itanium
    Oracle Database 10g Release 2 (10.2.0.1.0) for Linux on Power
    Oracle Database 10g Release 2 (10.2.0.1.0) for AIX5L
    Oracle Database 10g Release 2 (10.2.0.1.0) for HP-UX PA-RISC
    Oracle Database 10g Release 2 (10.2.0.1.0) for HP-UX Itanium
    Oracle Database 10g Release 2 (10.2.0.2) for HP Tru64 UNIX
    Oracle Database 10g Release 2 (10.2.0.2) for HP OpenVMS Alpha
    Oracle Database 10g Release 2 (10.2.0.2) for OpenVMS Itanium
    Oracle Database 10g Release 2 (10.2.0.2) for Solaris Operating System (x86)
    Oracle Database 10g Release 2 (10.2.0.1.0) for Solaris Operating System (x86-64)
    Oracle Database 10g Release 2 (10.2.0.1.0) for Solaris Operating System (SPARC) (64-bit)
    Oracle Database 10g Release 2 (10.2.0.2) for z/Linux
    Oracle Database 10g Release 2 (10.2.0.2) for z/OS (OS/390)

  • How to Upgrade Target Agent from 10.2.0.3 to 10.2.0.4

    Hi Everybody,
    I am doing this first time so need some help
    Q1. I need to Upgrade Target Agent from 10.2.0.3 to 10.2.0.4 manually and can't seem to find the right patch I need.
    I tried p3731593, but this seems to be installing much more than what I need so I cancelled it
    One option I thought of was to uninstall 10203 agent and install 10204 in the same agent home But I was wondering if there is a way I can upgrade my agent.
    Q2. Does the agent version on target and host(OMS) need to be same or can I have Target Agent 10.2.0.4 and host agent 10.2.0.3?
    Thanks for helping in advance
    Jeet

    Hi Jeet,
    You can use Patch 3822442 to upgrade the agent.
    The agent can be of different version.
    Regards
    Lai

  • Error in Smartform Custom after Upgrade from Release 4.6C to 4.7

    Hi,
    we have applied the upgrade of release from 4.6c to 4.7. After the process, we recognized an unknown message when try to print an invoice from SD: Sales and Distribution ---> Billing ---> Billing Document ---> Change(VF02); i insert a invoice number, click on DISPLAY function, then GOTO ---> HEADER ---> OUTPUT;
    In the next screen , i insert a message type custom linked to a SMARTFORM custom and i click on SAVE; the message is set with a red status, no message system and no print on the paper.
    WHAT IS THE PROBLEM AFTER UPGRADE? PLEASE HEL ME!!
    The transaction with the link in customizing SD of smartform is V/40
    Thanks in advance for any reply!!

    I just know the configure of output setting id
    Tr-code : NACE

  • Some puzzle for the 'Upgrade Guide: Release 11i to Release 12'

    We are on 11.5.10.2 with 10g db,now we are going to upgrade to R12
    I have done all the pre jobs in the 'Upgrade Guide: Release 11i to Release 12''s character 2 except the 'Prepare for the Upgrade' section.
    In the 'Prepare for the Upgrade's step 3:Step 3 Run Rapid Install (required),it ask me to run Rapid Install wizard
    But i can not understand what use of the action?
    When run rapidwiz,should i close the app and db?or only keep the db running?
    Anyone can help me?
    Thanks!
    Remen
    2007.8.18

    When run rapidwiz,should i install the R12's app to the same dict that the 11i's files locate?
    Sample:
    Before Upgrade the APPL_TOP=/u8/TEST/app/testappl,and the $AD_top=/U8/TEST/app/testappl/ad/11.5.0
    After run rapidwiz,the dict will change to $AD_top=/U8/TEST/app/testappl/ad/12.0.0 automaticly??No need to create the dicts manualy??
    Remen
    2007.8.18

  • SAP OS kernel upgradation from release 700 to 710

    Dear Sir,
    We are upgrading kernel release 700 (185)  to 710 (160).
    In this we are getting an error of saposcol i.e saposcol is not started automatically when we run startsap.
    Currently we are running our application on Kernel release 700 patch level 185.
    Should we have to upgrade application pathes after to upgrade the kernel release 710 patch level 160 ?
    Is there any dependency in between SAP Application Patch and SAP Kernel Patch or we can run the application on current application patch level, kindly suggest
    Regards,
    Mushtaque

    Dear Mushtaque,
    I am not clear on your purpose for kernel upgrade from release 700 to 710. Your SAP_BASIS and SAP_ABA version showing as 710 or 700. If it is 700, there is no reason to change your kernel release. The latest patch is 201. You should go for this patch incase release 700.
    Also, as a post processing steps you need to run saproot.sh with root user after kernel upgrade.
    Also please find below link for saposcol options.
    http://help.sap.com/saphelp_46c/helpdata/en/c4/3a6c40505211d189550000e829fbbd/content.htm
    Regards
    Gautam

  • OATM after upgrading to Release 12

    Hi,
    Wanted to find out if anyone has done OATM after the e-business suite got upgraded to Release 12.0.4.
    All the new objects were created under new OATM model since the new tablespaces were created as part of Rapid Install.
    We need to move rest of the objects (old ones created at 11i) to the new tablespace model.
    Has anyone done this and if so, any issues faced, any specific step that is critical to success of OATM migration.
    If you can share any documentation please post or I can provide my email address to share.
    Initial/next extent for new tablespaces created by Rapid Install has default of 128K. I am thinking
    of using either 1MB or 10MB of uniform extents. What storage parameters did you choose and why?
    Are you happy with that parameter or do you wish you have changed to different one?
    Thanks in advance for sharing.
    -RJ

    Hi Sawwan,
    Thanks for your response.
    I agree but the client already upgraded to Release 12.0.4 and didn't migrate all the objects (old R11i objects, for example: gl_je_batches, gl_je_headers, gl_je_lines still uses GLD tablespace instead of APPS_TS_TX_DATA) to new tablespace model (OATM).
    My question is that have any one of you faced this situation and how did you go about using the OATM migration utility for migration and any specific steps that are critical to the success of OATM migration.
    Thanks,
    RJ.

  • Upgraded the release SP level

    Hi
    Just now we upgraded the release SP level and facing the problem.
    Our client is on release 600 and found that after upgrade, the resource selection
    button is missing while changing the course. This is OK when it is created.
    Please advise.

    Hello,
    If have not created a relationship between Resource type R and course type D . If this is not done prior to
    creating the business event you will not find the resource selection button.
    Best Regards,
    Deepak..

  • 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

  • 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

  • I wnet to a web site tonight and a meeage from FireFox displayed that I was not on the current release. I know which release I'm on and at this time I do not wish to upgrade my release.

    I use release 3.5.1 of FF because it is compatible with the software I use. Nothing worse than you nagging me that I'm not on the most current release. Get off my ******* back. Stop the nagging messages. I'll upgrade when I'm ******* good and ready to upgrade. Un F'n believable!
    ''Edited by a moderator due to language. See the [http://support.mozilla.com/kb/Forum+and+chat+rules+and+guidelines Rules & Guidelines] .''

    The solution is simple. Go to Tools, select Options, a window will pop up. Click Advanced, select Update tab. In the options 'Automatically check updated to', uncheck 'Firefox'. Click Ok, you're done. :)

  • EBS Upgrade from Release 11.5.10.2 to 12.1.3 - SLA Issues

    Hi,
    Before upgrading our EBS from Release 11.5.10.2 to 12.1.3, Patch 5233248 has been installed , and Concurrent Program "SLA Pre-Upgrade Program" has been registered and enabled correctly (See Note : 427639.1 )
    While running this Concurrent Program , on EBS 11.5.10.2, through "General Ledger Super User" Responsibility, the program ran several seconds.
    Parameters Used :
    Migrate all sets of books: Yes
    Start Date: 01-JAN-2010
    Are there Pre-Requisits while running this Concurrent Program ?
    Regards,

    Hi;
    Please see:
    R12.0 and R12.1: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch [ID 604893.1]
    Regard
    Helios

  • Upgrading Soalris8 release 02/02 to Solaris 8 02/04

    Transition of Solaris 8 02/02 from Sunfire V480 to V490.
    The server is currently on
    Hardware : V480
    Operating system : Solaris 8 Release 02/02
    Kernel version: SunOS 5.8 Generic_117350-24
    The minimum requirement for V490 is Solaris 8 02/04.
    The Upgrade procedures are not working as the orginal V480 server has higher patch levels. Installing with the cdrom takes it to " install" options and not to upgrade options.
    Iam running out of option now and this system has lot of customized programs and needs to be upgraded and not tgo be re-installed.
    Please help if you could.
    Note
    1. The 02/04 release of solaris 8 is required for enabling dual core cpu's on 490.
    2. V490 is not bootable with 02/02 release.
    3. The upgrade proceudres to upgrade from 02/02 to 02/04 are not working because the current 480 has latest patch cluster 117350-24 installed.
    Thanks in advance for your help!

    Usually the minimum solaris versions specified for hardware are to ensure a minimum kernel version.
    Since you have already patched past that minimum kernel version, chances are that it will work on the new hardware even if it isnt officially that release.
    I'd just run a recent recommended patch set through to make sure that you have the latest kernel and all associated device drivers etc.

  • Advice on upgradation of Hyperion components

    Hello All,
    I am planning to upgrade EIS from 9.3.1.0.00 to 9.3.1.5.00(installing the service pack). Should I upgrade other components(HSS, AAS & Essbase) also from 9.3.1.0.00 to 9.3.1.5.00
    Please advice. Thanks in advance
    Regards,
    Sudhir

    Yes if you are updating one component, it is best to upgrade everything to be in sync. While it is possible to upgrade parts, its better to do the whole thing

  • Upgrade IOS release

    Cert Advisory: http://www.cisco.com/warp/public/707/cisco-sa-20070124-crafted-ip-option.shtml
    Affect release: 12.1(EA) on our cisco switches
    Under the rebuild column of software versions and fixes, the rebuld for version 12.1EA = 12.1(22(E8). There is no mention of the word vulnerable in this row - but you see it in other releases.
    Should I upgrade ASAP (am I vulnerable right now or are they suggesting moving to a new release when possible)?
    Regards
    D. McDonald

    If there is a migration path, it is vulnerable. Please migrate to the specified release as soon as possible.
    Thanks
    Gilbert
    Rate it, if this helps.

Maybe you are looking for