Getting error in creating JCo destination for WebDynpro

Hi Guys,
I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
When I am seeing the details:
Web Dynpro client:
HTML Client
Web Dynpro client capabilities:
User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Web Dynpro runtime:
Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
Web Dynpro code generators of DC sap.com/tcwdtools:
No information available
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 87289.311
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
Error stacktrace:
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Please help me guys.
Paritosh

You should post your question to the Webdynpro forum:
Web Dynpro Java

Similar Messages

  • Error in creating JCO Destination

    Hi All
    I want to create Adaptive RFC model and after creating JCO destinations when i am trying to execute my application I am getting this error
    Can anyone guide...
       com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 ERROR service 'sapmsB07' unknown TIME Mon Apr 23 16:01:08 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE ninti.c LINE 530 DETAIL NiPGetServByName2: service 'sapmsB07' not
    found SYSTEM CALL getservbyname_r COUNTER 3
    Thanks,Arch

    Hi
    I made entries in host as well as service files .
    192.168.8.42 B0001001      # added by me R/3 System
    192.168.9.24           # Portal host
    sapmsB07     3610/tcp      # added by me R/3 Msg Server Sevice
    I changed the status to PUBLIC in r/3. it was space there.
    Now the error I got is.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM  TYPE=B MSHOST=b0001001 GROUP=PUBLIC R3NAME=B07 MSSERV=sapmsB07 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       partner '127.0.0.1:3310' not reached TIME        Tue Apr 24 11:06:51 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -10 MODULE      nixxi.cpp LINE        2764 DETAIL      NiPConnect2 SYSTEM CALL connect ERRNO       10061 ERRNO TEXT  WSAECONNREFUSED: Connection refused COUNTER     1
    Thanks

  • Getting the following error while creating the model for webdynpro app.

    Plugin Name: Web Dynpro Model Editor Services
    Plugin ID  : com.sap.ide.webdynpro.service.modeleditor
    Class      :ap.ide.webdynpro.modeleditor.wizards.model.              creation.ModelDialog
    Method     : nextPressed
    Exception  : org.eclipse.swt.SWTException: Failed to  execute runnable (java.lang.NoClassDefFoundError)
    This is the error i am getting while creating the model for the webdynpro application. Can some one help ?
    Thanks & Regards
    Lalith

    hi
    This error occurs mainly due to the reason that particular plugin is not there in the NWDS.
    So please try to reinstall the NWDS or try tracing out whether that particular plugin is there or not.
    Thank,
    kris

  • RFC error while creating JCo Destinations

    Hi Team,
    We have been getting RFC_Communication_Error over time and again while creating MetaData type JCo Destination in EP 7. Actually We am configuring a Business package for ESS.
    I am pasting the error,
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=<server> GROUP=public R3NAME=<xxx> MSSERV=sapms<yyy> PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapms<yyy>' unknown TIME        Tue Jun 12 16:43:08 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      ninti.c LINE        530 DETAIL      NiPGetServByName2: service 'sapms<yyy>' not found SYSTEM CALL getservbyname_r COUNTER     4
    We have created Application type connections successfully. the tests on these were also successful.
    Thank you,
    Vamshi

    Can u pl check for the entry in the services file of the  JAVA Engine/portal.
    sapmsQ10  36XX/tcp
    If this entry is  not there please create the same @ ..WINDOWS\system32\drivers\etc\   open the services file in notepad and make an entry in the last line.
    format is
    sap<SID> Press TAB once 36XX/tcp<Press Enter>
    where XX is the Instance no of your Java Central Instance.
    If the prob persists please update.
    Priyabrata

  • Error while creating  jco connection for metadata?

    Hi all,
    we are using ep 6 sp 16.
    I could create the  JCO connection for application data  but i am not able to create the jco connection for metadata for the same  r3 server .
    while creating  the   the connection
    system name and  logon group  and disable
    and when i click finish
    it is giving  following error
    Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
    Thanking.
    Rajendra

    Hello Rajendra,
    Good to hear from u. Let me try to give a soln for this problem of yours.
    I think probably the logon group has not been specified in the backend.If thats the case then do the following:
    Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
    Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
    When you create the JCO connection, it should now show the logon group 'PUBLIC'.
    Regards,
    Prathamesh.

  • I am getting error while creating Control file for a fla file upoad in HANA

    Hi Experts,
    I am getting the following error when I try to create crtrol file for a flat file extraction in SAP HANA.
    Could not execute 'import data into table P935718."COPATBL" from 'COPATBL.csv' record delimited by '\n' fields ...'
    SAP DBTech JDBC: [257] (at 14): sql syntax error: incorrect syntax near "into": line 2 col 1 (at pos 14)
    Here is the code I have used to create control file after I creating the table.
    import data
    into table P935718."COPATBL"
    from 'COPATBL.csv'
        record delimited by '\n'
        fields delimited by ','
        optionally enclosed by '"'
    error log 'P935718.COPATBL.err'
    p935718 is my user ID, COPATBL is my table created, COPABL.CSV is a flat file.
    Please help me in this regard.
    Thanks,
    Guna

    Hello,
    guessing from the error message it looks that you are trying to execute "import data" as SQL command.
    Please note that import data is NOT SQL command but it is syntax for control file. You need to create file with this syntax on server and then use command: IMPORT FROM '/<path>/<filename>.ctl'
    In a shortcut:
    1.- create comma separated CSV file with your data - <source cvs>.csv
    2.- upload CVS file to HANA server
    3.- create the control file <filename>.ctl:
    import data
    into table <schema>."<table name>"
    from '<source cvs>.csv'
    record delimited by '
    fields delimited by ','
    optionally enclosed by '"'
    error log '<file name>.err'
    4.- execute command:
    IMPORT FROM '/<path>/<filename>.ctl'
    Please check following threads:
    How to load CSV files into HANA
    Will HANA supports Bulkload
    Tomas

  • Can not create jco destination  500   Internal Server Error  after sp 13

    hi friends
    i have strange problem in my landscape with webdynpro -
    >Web Dynpro Tool Applications----->Content Administrator  -
    >login as  j2ee_admin  in 
    Web Dynpro Content Administrator  page  when start click on  ceartin Jco destination  i am facing this problem  -
    >6
    1. i can not create any  jco destination .
    2. is there any other  way to create jco destination to back end (arfc connection to retrive the back end data .
    3 . we are using one meta and one model data for all the application in my enviroment we do have some performance issus because one arfc connection is it correct?
    4 . what is best scanario to our applications(bussiness package ) we do have 30 diffrent application can i
    have 30 arfc connections .
    5.with  one arfc how much data can i retive per 1 min is there any performance tunning docment is there for the  ep tunning .
    <6>error is showing like this
    500   Internal Server Error
      SAP NetWeaver Application Server 7.00/Java AS 7.00 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
        ... 45 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Sat May 24 22:16:36 PKT 2008
    J2EE Engine 7.00 patchlevel 109044.44
    Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale en_US
    Time of Failure Thu Jul 03 01:56:32 PKT 2008 (Java Time: 1215032192285)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available null
    sap.com/tcwddispwda
    No information available null
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    thanks in advance  to all the friends spending there valuable time to read this thread
    any  suggtions  are realy help for my issue
    this is very high  priorty issue in our  landscape
    regards
    raja

    thanks to all for helping

  • Creation of JCO Destinations for web dynpro

    Hi all,
    I read quite a lot of post concerning the subject but unfortunately I did not found a solution to my problem.
    My goal is to create JCO Destinations to make my web dynpro to connect to an R3 system.
    In order to realise this I followed these steps :
    - Launch visual admin and set http settings, rfc settings, and cim client settings. I click on CIM client test and the result is a success so I assume this part is correct.
    - In R3, I execute transaction smgw, go to remote gateway to get the gateway settings. I execute RZ70 and filled the parameters just checked. Then I activate and launch the data collect. I have no error message and everythings seemed to work fine.
    - In the sld (<host>:<port>/sld) I configured my server settings, the I go to data bridge, set update local sld to true and fill RFC gateway info with the same values as in my R3 system. Then I restarted the sld.
    - Finally I went to Web Dynpro content administrator to create my destinations and there I failed. After entering all settings (the message server appears in my technical landscape in SLD), when I click on finish I've got the following exception :
    [code]
    Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:140) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection
    (SystemLandscapeFactory.java:286) at
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish
    (ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:252) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:641) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at
    com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more[/code]
    I tried to create a generic destination (no for the web dynpro tutorial) and failed again.
    I do not undestand what I did wrong.
    Does someone have an idea ?
    Thanks for reading this !
    Sylvain
    Message was edited by: Sylvain

    This thread helped me too because before reading it I didn't thought that I had to create a logon group "PUBLIC".
    Anyway I succed in creating 'WD_FLIGHTLIST_MODELDATA_DEST' and the test is ok. The problem was that in sld / technical system / web as abap, my Central Application Server host was wrong. It is not possible to change it so I just add a secondary server with the right host and select this one when creating the destination.
    The only pb remaining is now 'WD_FLIGHTLIST_RFC_METADATA_DEST'. I think the pb is my message server such this is the only difference between the two destinations
    Thanks for your help
    Message was edited by: Sylvain

  • AS Java 7.10: Can't create JCO destination 'WD_RFC_METADATA_DEST' in SLD

    Hello,
    I registered my J2EE 7.10 in the central SLD (sldmain.wdf.sap.corp:53000) successfully and created JCO destinations WD_RF_METADATA_DEST + WD_MODELDATA_DEST there. But the deployment of a WD application using Adaptive RFC fails because the above JCO destinations are not found (or access to SLD fails at all?). I didn't find any documentaion on how exactly the 2 destinations must be configured. On the central SLD there's no test/ping function for JCO-destinations! Could it be that my WD-deployer still tries to access a local SLD?
    <b>Root Cause</b>
    The initial exception that caused the request to fail, was:
       <b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.</b>
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:442)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:230)
        at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:215)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:106)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138)
    Thanks and regards,
    Jens

    Jen,
    Edit your JCo destinations and make sure you have Metadata as data type.  I am guessing you are getting this error becuase you might have selected Application data as data type.
    Hope this helps

  • Create JCO destination option not available

    Dear All,
    I am trying to make a JCO connection in CE.
    However the buttons for
    "Create JCo Destination","Maintain JCo Destinations" are disabled.
    The status for built-in JCO destinations  WD_MODELDATA_DEST
    WD_RFC_METADATA_DEST is shown as unknown.
    The "Enable" button is also disabled.
    Also i am getting the error "Connection to System Landscape Directory (SLD) could not be opened successfully".
    Can anyone please help me in this.
    Thanks and regards,
    Mayuresh.

    Hi Mayuresh,
    In nwa go to Configuration Management->Infrastructure->SLD Data Supplier Connection->Destinations.
    Create a Destination.
    Ping the destination to check if it is successful.
    After that you can create a JCO Connection.
    Regards
    pankaj

  • Exception while creating JCO destinations

    Hello,
    I have deevloped a webdynpro application as a local DC and trying to deploy and run it. While doing this step it throws an exception as "NullPointerException" when i click on create JCO connection.
    The error details are like :
    "at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)"
    Can anyone please help me how to resolve this problem.
    Thanks.
    - points rewarded for helpful solution

    Hi,
    The Following Procedure Follow  To Create JCO Destinations.
    First You Configure SLD Correctly.If You Have ECC And BW.You Maintaing Two WEBAS ABAP Systems.
    You Create WEB AS ABAP System In SLD And Maintain Connection Properties Of ECC.And
    Similarly For BW Also.
    If You Want To Create JCO Destinations.You Go To Login Portal
    Content Administration->Webdynpro->Create JCO Destinatiion
    A.General Data -> Specify Model Name,Client And JCO Pool Configuration
    B.Specify J2EEE Cluster
    C.Destination type
    Data Type-> Application DataModel,Dictionary MetaDataMetadata
    Destination Type->Load Balancing Or Single Server
    D.Specify Either Application Server Or Message Server
    E.SecurityUsername,password,confirm password,language
    F.SummaryWhole Information
    Similarly Metadata Created Follow Same Steps As Above
    After Creating JCO Destinations, Go For Maintain JCO Destination And test The JCO Destinations Works Fine Or Not you Con Test.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/webdynpro/wd%20java/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a
    http://help.sap.com/saphelp_nw04/helpdata/en/77/931440a1c32402e10000000a1550b0/frameset.htm
    The Given Below Links To Help You SLD Cofiguration For J2EE
    http://www.*********************/solution_manager/solution_manager_sld.html
    SLD Configuration
    It's Useful Rewards Points
    Bye
    Thanks
    SubbaRao

  • Not able to create JCO destination

    Experts,
    I have deployed ESS/MSS package and I have maintained the JCo Destinations.But When I try to create a JCo destination for "SAP_R3_SelfServiceGenerics" JCO,I am getting the error message with some null pointer exception.
    Can anyone let me know how to resolve this?
    Regards,
    Karthick

    Hello Karthick,
    Just send me the exception and i will get back to you.
    Regards,
    Shikhil

  • In portal where we will create JCO destinations?

    HI Gurus,
    In portal where we will get the option or screen for creating JCO destinations....
    I guess its somemwhere in System Admin---->
    If anybody knows the path please share with me.......
    Thanks in Advance,
    Dharani

    Hi,
    Please check the below document for help
    configure ESS:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
    ESS/MSS Installation to R/3 4.7 Enterprise
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
    MSS - http://help.sap.com/saphelp_erp2004/helpdata/en/0a/8b3b40b1607a56e10000000a1550b0/frameset.htm
    help.sap.com - Configuration of Employee Self-Service (ESS)
    http://help.sap.com/saphelp_erp2005/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    help.sap.com - Technical Description and Configuration Information
    http://help.sap.com/saphelp_erp2005/helpdata/en/76/77594d165144a1a9bff9aae1e26b26/frameset.htm
    BP for ESS Document
    https://www2.iviewstudio.com/support_content/_17295/BP_ESS_05_P1.pdf
    General Settings for Self-Service Applications
    Configuring MSS on Portal 6.0
    Implementation and Configuration guide for ESS into Portal,Backend R/3 4.7C
    Thanks & regards
    Santosh
    Reward if helpful !!!

  • Creat RFC destination for portal

    Hello,
    when i am doing RSPOR_SETUP , i am getting java and abap support package versions are different error message for step 2, i.e creating RFC destination for portal.
    Please send me suggestion regarding this issue.
    regards
    Sreesudha

    is ur BI and Portal SP versions different ?? ....if true ?? make sure they have the same SP
    use this link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00bed70a-7501-2a10-ec9e-9a04485ab477
    for guidance......

  • Getting error while creating the variable of Schema Element type

    Hi everybody,
    For creating a variable of schema element type I am doing the following steps...
    Select 'Variables' after right clicking on bpel process. IN this window, go to 'Create VAriable' then select 'Element' type. Now in Type Choose, I expanded the my imported schema files. And selected a element type, then click ok to create this variable... I am getting the message...
    IN ORDER TO SAVE IMPORTED WSDL/SCHEMA FILES, YOU MUST HAVE A PARTNER LINK LOCATED UNDER THE CURRENT PROJECT DIRECTORY.
    What is mean by that.
    I have imported the schema files in project. AFter that I have imported them into the WSDL also. Now why I am getting error while creating the variable. However I can create variable directly in .BPEL file then everything is fine. And it is working also. But what is mean with the above error? Why I am not able to create variable through GUI?
    Thanks.

    Hi,
    I have this same problem this morning, and I was going crazy, until I found this webpage on the internet:
    [http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process|http://technology.amis.nl/blog/1803/problem-importing-xml-schema-in-bpel-process]
    The idea is that the jdeveloper is not very good working with directories with spaces on the directory name. If you move all your work to a directory without spaces, it will work smoothly. At least, it had worked for me.
    Regards,
    Nacho

Maybe you are looking for

  • Upgrading from 32 bit to 64 bit windows 7

    I have a 32 bit system with windows 7 home premium on it. i have the ff. question and i hope someone can provide me some answers: 1. My laptop is 64bit enabled, can i use the oem os key at the back of my laptop to install the win7 home premium 64 bit

  • IDOC Output for Payment Run through F110

    Gurus, I am trying to generate IDOCS for the payment run through F110 transaction. I have setup the following but still unable to generate the IDOCS. - Bank partner setup with IDOC PEXR2001 and message PAYEXT. - House bank configuration. Can anyone h

  • Importing from iPhoto to Aperture failed

    I have iPhoto 9.2.1 and Aperture 3.2.2 and Lion 10.7.2 with a newly re-installed Lion.  After buying Aperture, I imported my entire iPhoto library. There are 16,182 pictures in iPhoto. In Aperture, I now have 19,568 pictures. But, in Aperture, not al

  • PSE 12.1 not saving in version set

    I have been successfully using PSE 12.1 on Windows 7 since last August.  However I've started having problems in the last 2 or 3 days.  I start the Organizer and select a photo to edit.  When I "save as" I get one of two results.  In the first case i

  • HOW-TO specify database credentials in LDAP user

    Hi: I want to know how can i specify oracle database credentials (oracle database usernname) that one specific user will use to connect to the database for instance when using Oracle Forms. I saw in OID some "tags" like orcluserv1, etc... is this ? h