NWDI in NW04s

Hi,
We have installed NW04s recently and would like to configure our NWDI.
However we are unable to create Software Component.
When we ran the template for NWDI,it went through successfully.
Do we need to do anything before creating SC that I may have missed?
Thanks,
Suparna

Hi Siddarth,
I was creating a new product.
As suggested by some other posts,i upgraded the system to SP8.Now I am able to create a component but I cant find the build time SCs for dependency.
When I run by template for DI Pst installation it gives me error during build time SCs/plugins imports.
Thanks and Regards,
Suparna

Similar Messages

  • NWDI error after system copy

    Dear All,
    We have copied our NWDI system ( NW04s Java SP08) to a new host, while doing the post install steps we are facing numerous errors.
    Changing the Domian data went fine. But when we try to update the urls in indivudual tracks we get CBS communication failure error. As mentioned in the system copy guide we changed the Idle start value of the CBS to true through visual admin and then tried but still the error remains the same. How to correct the error ?
    And is there any way to do a NWDI refresh i.e delete everything that is existing including the tracks and configure the NWDI from scratch.
    Please advice
    Warm Regards
    Mazdul

    i read note 145029 on the same problem which says i should copy CONPUTTB.TAB to BIN folder of Upgrade directory, but i am not sure i have upgrade directory in my system as there is no any PUT directory inside folder 'USR\SAP' as said in upgrade guide. is it because i build a system from an export image of the upgraded system? And will i be able to do it only on the Main system (on which upgrade was perform).
      I seen a tcode SRTT0 which generate PUTTB entries but it did not generate for me?
    any comment would be appreciated.
    As suggested i allready opened up message with SAP for the same will let know result once i finished it.
    Mani

  • NWDI: CMS Track Authority

    Hello, we have an NWDI SP15 (nw04s) and we want that developers are able to transport. We activated CMS Track Authority for your tracks and have added our developers. But still developers aren't able to import transports. The import button is grey. Our developers have the authorization NWDI.Developers. If I give them NWDI.Administrator. They are able to import transports. What have I missed during the CMS Track Authority?
    Regards,
    Alexander

    Hi Alexander,
    did you do what is desciben on help.sap.com for [track specific authorizations|http://help.sap.com/saphelp_nw70/helpdata/EN/04/551b42d10b5633e10000000a155106/frameset.htm]?
    Could you please check whether your developers have the right to execute the actions CMS.Export* (Own or Foreign) as desibed in [here|http://help.sap.com/saphelp_nw70/helpdata/EN/94/6c7b401c976d1de10000000a1550b0/frameset.htm]?
    Kind regards
    Karin

  • NWDS - autodeploy into runtime systems

    Hello,
    we have an NWDI on NW04s SP13 with a track. Several developers have their own NWDS with each thier own J2EE. The developers are created on the NWDI. I have configured for the DEV_RUNTIME system automatic deployment.
    The developers told me, that they need the sdm password for the DEV_RUNTIME system. Could you please explain me, if this is true? I thougth a user and pw from the NWDI would be all what they need.
    Regards,
    Alexander

    The developers should only need the SDM password for their local J2EE Engines. Deployment to the Dev runtime system of the track is done by NWDI using the SDM password provided in the runtime system definition.
    In order to deploy changes to the Dev runtime system, developers must Check-In and Activate their activities. An activation triggers a central build by CBS and if this build is successful, it triggers deployment to the Dev runtime system.

  • DTR Migration

    Greetings--
    I need some help understanding DTR projects and if its possible to migrate closed activities onto another system or can this ony be done via Java System Copy?
    We are currently using DTR for storing portal projects that are sdeveloped in eclipse, we now have been tasked to move NWDI onto another piece of hardware.
    My question is: Since we are only using DTR and not CBS/CMS/SLD, can I simply migrate closed activites onto a separate installation (the will be 2004s).
    Original NWDI version (NW04 SPS18)
    Proposed NWDI verions (2004s SPS18)
    -John

    The way that we did was to manually move all the DCs to the new NWDI server. I am not sure if there is an automated way of moving the DTR workspaces from one system to other.
    The method we followed was similar to moving the local DCs to NWDI. Follow this blog, it might be helpful.
    /people/raj.peddisetty/blog/2007/03/02/migrating-localdcs-onto-jdinwdi-track
    Revert back with questions.

  • NWDI Setup in Sneak Preview NW04 SP16

    Hi All,
      I am sorry to post to this message in this forum. I didnt get any response in another forum. It would be great if you can help me out.
    I am trying to setup NWDI for Sneak Preview NW04 SP16. I didnt find a guide to setup the same. So, I am following the guide available for Sneak Preview SP15, which is at http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/419b479b-0801-0010-f8a1-c26208b4b209
    I dont get where the file CopyState.properties is located at ?
    1) What is the file CopyState.properties all about ?
    2) Where is it exactly located.
    3) Can we really setup JDI in Sneak Preview and work with it ? I mean like creating Tracks, etc
    Thanks in advance for your help,
    Kumar

    Hi Kumar,
       I am following the same guide you have mentioned and facing the same problem. Have you found out something about the file CopyState.properties?

  • Installation of NWDI Add in for NW04s

    Hi,
    I have an ABAP+JAVA BI 7.0 system.
    I want to install a DI Add in.
    When I try ot use the lifecycle management option in sapinst & select only DI usage type,it installs the java engine again & deletes the curent "j2ee" folder.
    Is there any way of installing only DI without disrupting the current Java setup.
    Pls. help.
    Thanks a lot.
    Saba.

    Hi Rajeev,
    At Sapinst go to SAP NW'04 Java System (J2EE) -> <DB> Server ->
    -> Distributed Systems -> Dialog Instance Installation
    Or
    If NW'04s go to Sapinst -> Additional Software Life-Cycle Tasks -> Application Server -> <DB> Server -> Dialog Instance
    <b>Note: If you installing and DI in the same box, change the system number!</b>
    This should solve your problem....
    Regards
    Juan
    Please reward with points if helpful

  • DI installation on NW04S

    Dear Gurus,
    i have installed Central system on NW04S with components
    1. Engine - AS ABAP and AS JAVA
    2. PI(XI)
    3. EP(PortalKMGuided Procedure-CAF+Visual Composer )
    4. BI(Business Intelligence)
    5. BI Java Components
    Server is running fine.
    But i dont remember if i selected the component DI(NWDI)during the installation so how do i check this if it is installed on my server and if it is not installed then how can i installed it. is there any standalone installation exist for DI or while doing Central server installation i have to choose DI as part of instalaltion and deselect all other components from installation.
    Please suggest.
    Dheeraj Thareja

    Yes, it was my fault. I have only read the german sap note but this version is old fashioned (Validation till end of february, didn't see that!!)).
    I have deployed the sca files over SDM menschioned in the english sap note and the NWDI is working now. We had some other problems by deploying these files because sdm and Adminstrator password were not the same. After changing it with one password the Deployment was succesfull.
    Thanks and regards,
    Frank

  • JSPM: NWDI-controlled SC in REVISE due to SC Version Error

    Hello,
    We are still very new to working with the J2EE Engine and NWDI, so naturally we are finding our way through our mistakes.  We are in the process of implementing Enterprise Portal for ESS/MSS, and we have made some custom modifications to both of these components.  We are using NWDI to control the modifications, and after some initial mis-steps, we think we now have a reasonable working landscape.  However, we are now unable to apply support packages for ESS to our Test system.
    We successfully applied sps8 for ESS/MSS/PCUI_GP/ASR and sps11 for NetWeaver to our Development system, using NWDI and NWDS to re-apply our modifications to ESS and MSS.  The combined SP's and modifications went into DEV just fine, they imported into the CONS queue (no runtime system) fine, they assembled successfully, and now I am trying to import them into TEST using JSPM, but here is where the problem lies.
    In the "Check Queue" phase of JSPM, the ESS component is in status REVISE, and the detail message says "New component sap.com/SAP_ESS with version 600.8.0 and provider JD1 does not cover existing component with version 600.7.2 and provider JD1."  JD1 is our NWDI system/domain.  I think the basic problem is that for whatever reason, our TEST system has ESS in version 600.7.2, whereas in DEV it was in 600.7.0 (prior to applying sp8), and I have no idea why there is a difference.
    I have tried the import as a support package stack and as a collection of single support packages, but I get the same result.
    The MSS component has no such issue.  The status in Check Queue indicates that it has admitted our modification from the CMS track for deployment.  The assembled directory contains files for MSS, ESS, PCUI_GP, and ASR, as expected.
    The only thing I can think of is that prior to applying this sp stack, we had a misconfigured NWDI landscape (the transport directory was on the portal DEV server instead of the NWDI server, transports were variously held on the portal DEV server or the NWDI server depending on whether they were controlled by CMS, etc -- all of this is now fixed, but perhaps the damage is done), and the previous sp stack went into the systems prior to any modifications being done, it went in without NWDI control, and then modifications were transported into TEST separately.  However, supposedly the DEV and TEST systems had the same versions prior to this sp stack being applied.
    I know the documentation says that the component in the transdir must be replaced to fix the REVISE status, but we have nothing to replace it with.  It IS the correct version.  What I really need is a way to tell JSPM to ignore the version error and force the new (modified) component in, without losing the version history and track control in the CMS.
    Any advice on how to proceed will be much appreciated.  The NWDI and Portal are both NW04s release, and the NWDI is already at sps11.
    Best regards,
    Matt

    We resolved this problem by undeploying all ESS components via SDM, then applying all the support packages to still-deployed components with JSPM, and then redeploying the new/modified ESS package via JSPM with the option of "New Software Components."  I still don't know how the funny 7.2 sp.patch version number got there in the first place.
    --Matt

  • Upgrading Portal from NW04 Sp14 to NW04S SP 9

    Hi,
    We are preparing to upgrade our EP 6 , NW04 SP 14 highly available installation to NW04S SP 9. It seems JSPM is the tool that comes with NW04s SP 9 which runs the upgrade for existing NW04s systems. However NW04 SP14 does not have this tool it only has SDM. Would be grateful if someone could tell me how to start off the upgrade? Do we need to deploy the JSPM from NW04s SP9 via SDM first on existing system? or is there another tool to start this upgrade?
    Tarek

    Hi,
    1.Is this SP25 upgrade from SP24 will support the IE8 and Firefox 3.5
    without any issues for webdynpro application running as of now?
    For this you can refer SAP note 1098009, 1296463 and 960549.
    2.is it required to upgrade ESS and MSS and anything on ERP side along
      with Portal upgrade to SP25
    Yes, you should upgrade ESS/MSS to keep it in sync with NW SP level. You can check below link for SP level of ESS/MSS with NW patch level and backend system patch level:
    [Link|https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOW%20TO%20GET%20RID%20OF%20SP%20STACK%20MISMATCH%20ISSUES]
    3.After upgrade NWDI to SP25, all the present tracks with custom
    components will work as it is?
    It should work as such there is no well known issue with existing track after upgrade.
    Thanks
    Vijay Kalluri

  • Need advise on Installation and Configuration NWDI frame work.

    Our SAP R/3 is  4.6C and here at nVidia we are very new to SAP Netweaver world, we have already implemented EP 6.0 and XI on NW04 SP 13 and we are very close to go production.
    Going forward we are planning to implement ESS, MSS, xRPM 4.0, CRM 5.0 with some customization to use the features like Guided Procedures(workflow capabilities outside of R/3), Composite Application Framework, Mobile Infrastructure for Help Request, workflow, myCRM etc. Apart from this, our custom developed intranet runs on .NET and some day it will move into SAP EP.
    We are currently planning on building our Development Infrastructure (i.e. SLD->NWDI-> Dev->Qa->Prod) to implement  above mentioned new product with some customization.
    Currently our EP6 and XI are on NW04 SP 13, but we heard that Guided Procedures, Composite Application Framework only works with SAP NetWeaver 2004s and Mobile Infrastructure need Dual stack (ABAP + Java addin).
    So we are currently little confused on how to build our development infrastrucre to support above products and any advise is highly appreciated.
    1. Should the Development, Congregate, QA, Production machines have WAS 6.4 J2EE or WAS 6.4 with (ABAP + Java Addin) to support both custom java & ABAP development, at this point we are only planning on developing/customizing Java based apps/components.
    2. We also need to Install Mobile Infrastructure, so should our MI go on top of Development, Congregate, QA, Production machines, in which case it needs to be WAS 6.4 with (ABAP + Java Addin) and not just J2EE stack, because MI needs both stacks Or should the MI be on its own boxes and configured to connect to NWDI servers.
    3. We heard that Guided Procedures, Composite Application Framework only works on net weaver 2004s, in which case should our development infrastructure be build on net weaver 2004s or NW04 SP 13.
    4, If we go with NW04 SP 13, will there be a path to upgrade to net weaver 2004s so that we can implement Guided Procedures, Composite Application at a later point.
    5. How will net weaver 2004s work with our current EP & XI infrastructure which run on WAS 6.4 sp13
    Once again your help is appreciated.
    -Shivpal Reddy
    [email protected]

    Hi,
    I'd say - Stick to your plan and configure all InternalURLs to be the same as the ExternalURL, the name you have in your certificate. The same goes for AutodiscoverServiceInternalUri. The key is to have Split DNS set up
    See: http://support.microsoft.com/kb/940726
    That is what most people do, even the one that can add their internal FQDN name to the certificate.
    Understanding Digital Certificates and SSL
    http://technet.microsoft.com/en-us/library/dd351044(v=exchg.141).aspx
    Martina Miskovic

  • Web Dynpro callable object without NWDI

    Hello Forum,
    does anybody know if it is possible to create a web dynpro dc as a callable object without using nwdi? I have written a webdynpro app know I want to use it in a guided procedure where I can provide an input field for the dc and also get an output field from the dc.
    Does somebody have a step by step solution?
    Regards
    Michael

    Hi,
    You need to have the SCs for local development of Web Dynpro callable object.
    Refer the following documents for more details:
    <a href="/people/andre.truong/blog/2006/06/26/working-with-the-apis-of-caf-guided-procedures-nwdi-or-local-development with the APIs of CAF Guided Procedures: NWDI or Local Development?</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f7be53bb-0b01-0010-1c96-be3cb6799c1b">How to Get NW04s SP7 Guided Procedure APIs for Local Development</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3f07a7a-0601-0010-ebbd-b9cfb445b814">Implementing a Web Dynpro Callable Object</a>
    Let me know if this solves your issue.
    Thanks,
    Dipankar

  • NWDI Questions

    Hello All:
                   I am very new to NWDI and WEB AS concepts and need help regading NWDI. We are running NW04S portal on Sun box. I have some questions regarding NWDI landscape. Please help me on this so that we can go forward on setting up NWDI.
    - Can we run NWDI on Windows while Portal is running UNIX?
    - We have 1 developer who is going to work on ESS & MSS Customization. So do we need a consolidation environment in our landscape?
    Based on my understanding we just need to import all the SCA files into the track and start customizing using NWDS. Once everything is done we need to build the SCA files based on customized components and transfer across the landscape.
    Is my above assumption correct?
    Your help is greatly appreciated.
    Surekha.

    Hi there,
    NWDI is a recent tool for everybody. About the interoperability between EP and NWDI it doesn' matter what is the operational system, because the NWDI will communicate with the WAS where is the Portal is installed and the requiriment is the connectivity between this instances. Doesn't matter Service package level, which version and system operational. The consolidation environment is recomended but isn't a requeriment. For instance, you can use the DEV environment as consolidation.
    Your assumption is correct, but I prefer say the same with other words
    Take a look on the ESS cookbook customization ann then I guess everything will be more clear.
    Type a quickly search on the foruns by "ESS cookbook".
    I hope it help you!
    Regards,
    Luciano

  • Unable to open Popup Window after transporting using NWDI

    Hi
    I am using Nw04 SP19. I have created a window using createWindow() and createModalWindow() too. The Window opens if we use direct deployment into  the server, whereas afer we transport thru NWDI the window dosent open and gives null pointer exception.
    Even creating ConfirmationDialog has the same problem.
    The Issue occurs after Assembly is Done in NWDI i.e after SCA files created ( just thought this info is useful).
    Any comments on this is appreciated.
    Thanks
    With Wishes
    Krishna kanth

    You say its urgent
    So urgent, so oh oh urgent
    Just wait and see
    How urgent my love can be
    Its urgent

  • What to use for NW04s development systems

    Hi all,
    till now we were developing on NW04, with the devlopers having XP (SP2) laptops with an installed WebAS 6.40, Portal, KMC running with an MSDE(MSSQL 2000). So far so good. But we now have to switch to NW04s. Looking into service.sap.com/swdc I find unter update just Updatemasters for Win Server not XP. Therefore I also get an error while installation that this setup is not ment to be used with this OS. Is it possible at all to install 04s under XP? Where do I get the installation files from? How are you guys doing it? WE do have a develop server ( unix)  in place which is attached to the NWDI - but it is not very handy with a bunch of webdynpro developers to all do the testing on one server. Maybe somebody can help me on this - would appreciate it!

    Hi Christian,
    Well you should download SR2 cd's How to get into it.
    service.sap.com/swdc. This is the software distribution center. Go to download and down load by application group. select netweaver and then NW2004s. There you get the option of selecting the OS and inside a particular OS you have the option to chose your database. You get a list of cd's. Here you can select the Instalation master, export, database, kernel, java, Components cd. Rest of the choice is your's. Proceed to download.
    Remember that this SR2 is the SPS09 level. While the current release is SPS11. So hence forth you can go to service.sap.com/sp-stacks and select the patches of your choice moving quite the same way and then download those patches and further apply them using JSPM. Ensure that your SDMKIT.JAR and kernel files are included in the list.
    To use JSPM you should login as sidadm and also place all the contents under trans/EPS/in folder.
    DO reward good points as it helps keeping the spirit of the forum alive.

Maybe you are looking for