Jco destinations

hi,
i have a little problem configurating SLD for Web Dynpro.
i run my web dynpro application which uses rfc model wd_rfc_flightlist_metadata_dest,
i'm getting error:
"com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_FLIGHTLIST_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD."
As I understand I have to create a new destination... can anybody tell me the exact parameters for it,
destination name, type, url..?
Thank you.
MaryM

Thank you for your answers.
I still hae a littel doubt. I checked and both SLD and JCo are running.
I was able to define JCo destination (ping ok), but testing it gives me an error:
"com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Nombre o clave de acceso incorrectos (repita la entrada al sistema) "
When defining a destination, what authentication info i must enter?
And when I define the particular SAP system to receive data from?
Thank you!
MaryM

Similar Messages

  • R/3 Accessibility via JCo Destination

    Hello
    We have a WebDynpro application running in an SAP EP 7.0 SP15.
    We have metadata and modeldata JCo destinations defined for an R/3 backend system.
    The WebDynpro application is using the modeldata JCo destination to reach a BAPI in the R/3 backend system.
    As far as SSO access is configured for the modeldata JCo destination, it is required that the Portal user of the WebDynpro applications has an user defined in the R/3 system.
    We would need to find some solution so that the WebDynpro application can access the BAPI in spite the runtime Portal user does not exist in R/3 backend system (e.g. accessing R/3 system with another user, that could be hardcoded or mapped to the Portal user or whatever).
    Is that possible? If yes, how?
    Thanks a lot!
    Regards,
    Jon

    I think that perhaps you posted this question in the wrong Web Dynpro forum. This question appears to be Web Dynpro Java related and not Web Dynpro ABAP. Please confirm otherwise I will be moving this thread to the WDJ forum where it seems to belong.

  • 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 !!!

  • Error when trying to create a JCO Destination

    Hi
    I receives the following error when trying to creat a JCO Destination, clicking on the button in the host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
    I get the following error:
    Error stacktrace:
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:880)
         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:740)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640)
         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:391)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)
         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: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)
    Any ideas?
    Regards
    Kay-Arne

    Hi,
    Have you configured your SLD? Check JCO Destination error out or search for "com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus" in the SDN forums.
    Best regards,
    Vladimir

  • 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

  • ERROR WHEN I CREATE A JCo DESTINATIONS

    Hi to all
    I have the SLD running. I want create two JCo destinatios. I want create a Web Dynpro application with adaptive RFC Model.
    But, I login to http:///webdynpro/dispatcher/sap.com/tcwdtools/Explorer
    and when I attempt create a JCo destinations, appear the following error:
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    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:985)
        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)
        ... 45 more
    Can someone say me, why occurs this error ? I have reviewed all my configuration, but I haven´t found nothing.
    Thank you very much.
    Regards
    Dario Rodriguez

    I think while creating the JCOs you must hav left some field with a NULL  value.Try to check out that all the connection properties hav been specified correctly also make sure that the connection pooling has a small range.

  • Error while creating the JCO destinations

    Hi All,
    I am getting the following error while creating the JCO destinations.
    <b>There are no message servers maintained in the associated SLD. Please contact your system administrator.</b>
    Please help me in resolving this
    Thanks

    http://help.sap.com/saphelp_erp2005vp/helpdata/en/24/8fa93e08503614e10000000a114084/frameset.htm
    Creating New Web AS ABAP Technical Systems
    /*Reward if helpful
    Message was edited by:
            Anant
    Message was edited by:
            Anant

  • 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

  • JCo destination error while executing the webservice model

    Hi,
    I have explained what I have done so far and whats my issue right now.
    My requirement is calling a PI interface (exposed as webservice) from webdynpro for java and setting some parameter value to the PI interface based on which our functional flow will continue.
    Done so Far :
    1. Created a webdynpro for java application using NWDI.
    2. received the WSDL file of the PI interface and imported as "Adaptive webservice model" into webdynpro.
    3. used the model and set the parameters to PI interface and executed the model.
    4. I have created JCO destinations in the source system (where the application runs) to communicate to the PI system. A special user has been created and assigned in the connection for communicating.
    5. Also I have created the "Dynamic Webseviceproxies" in visual admin with the same name as the JCO destinations. It had a property "URL" for which I have tested with providing both the PI server URL (Http://<Hostname>:<Port no>) and also the complete webservice URL (Which calls the WSDL file directly)
    when I run the application, I get the following error.
    1. Exception on creation of service metadata for WS metadata destination 'WD_RFC_METADATA_DEST' and WS interface '{<Interface Name>'. One possible reason is that the metadata destination 'WD_RFC_METADATA_DEST' has not been properly configured; check configuration.
    after some exception the next error follows
    2. Invalid Response Code 403 while accessing URL: <The URL which I have provided in the webservice proxy in Visual admin tool> Response Message: Forbidden.
    after some lines of exception from PI server the next error follows.
    3. Error: You are not authorized to view the requested resource
    My Question :
    1. Do I miss anything in Configuration?
    2. Is my way of approach wrong?
    3. Any additional authorization needed?
    Kindly provide some ideas and inputs.
    Regards,
    Mahendran B.

    Dear Mahendran
    JCO destination will not used for the Web Service Model. While creating the webservice model, you need to use the logical destination which you have created in the Visual Admin.
    Please refer to the Secured WebServices II and verify currently used webservice logical destination How To Reimport Web Service Models in Web Dynpro for Java
    You can also refer to
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/900bbf94-a7a8-2910-e298-a651b4706c1e?QuickLink=index&overridelayout=true
    Hope it will helps
    Best Regards
    Arun Jaiswal

  • Error In JCO Destination Creation

    Hi,
    I'm creating JCO Destination in Web Dynpro for Java. While finishing the JCO Destination wizard it shows a error as follows:
    Root Cause
    The initial exception that caused the request to fail, was:
    java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
        at java.util.ArrayList.RangeCheck(ArrayList.java:507)
        at java.util.ArrayList.get(ArrayList.java:324)
        at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.getElement(Node.java:2022)
        at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:617)
        at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:749)
        ... 45 more
    But the JCO Destination is created successfully and I can test and ping tit successfully. But it becomes the part of System Denied JCO Destinations.
    In the server log file I'm getting the following log:
    1.5#00112F5374F1005B0000011100000EDC000443BF97417983#1200390062389#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0#####SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Cannot navigate via outbound plug tointeractiveForm of view InvoiceListView because there is no navigational link attached to it
    Exception id: [00112F5374F1005B0000010F00000EDC000443BF974176DF]#
    #1.5#00112F5374F1004F0000055B00000EDC000443BFA0A4587B#1200390219953#com.sap.tc.webdynpro.sessionmanagement#sap.com/tcwddispwda#com.sap.tc.webdynpro.sessionmanagement.ExceptionHandler.handleThrowable#subhayuds#116#####J-Integra for .NET TP Thread 2##0#0#Error#1#/System/UserInterface#Java###Exception occured during processing of a Web Dynpro application: "java.lang.IndexOutOfBoundsException: Index: 0, Size: 0".
    [EXCEPTION]
    #1#java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
         at java.util.ArrayList.RangeCheck(ArrayList.java:507)
    Can anybody help to find out this problem.

    Hi,
    This is a Web Dynpro bug. You need to apply the latest patch for Web Dynpro runtime.
    Regards
    Srinivasan T

  • 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

  • Problem in connecting JCO destination in web dynpro

    HI all,
    I was installed sneak preview of Net weaver 6.4,
    I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
    The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
    I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
    for the above requirement what I did was
    (1)I created SLD setting.
    (a)Web as Java (I am not having any problem to
    Create this.
    (b) Web as ABAP.
    When i am trying to create
    This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
    under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as 10.10.10.125 (c)Gateway service as sapgw00 (d)Number of processes as 1
    Under Repository (a) Application server host 10.10.10.125 (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
    I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
    I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
    (a)Host: pava-vis75
    (b) Port: 50000
    (c) user: administrator
    (d) password: abcd1234
    RFC Settings, I mentioned as
    (a)Gateway Host: 10.10.10.125 (which is SAP R/3 system)
    (b)Gateway Service/Host: sapgw00
    CIM Client Generation settings, as
    (a)Host: pava-vis75
    (b)Port (http/https):50000
    (c) user: administrator
    (d) Password : abcd1234
    I tested the CIMClient Test by click the the button. I got the successful message.
    Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
    Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as 10.10.10.125and Gateway service as sapgw00 then i tested the connection, it was also successfully.
    Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
    (a)Alias: vissldtest
    (b)Host Name: pava-vis75
    (c)Port: 50000
    (d) user: administrator
    (e) password: abcd1234
    Then saved it.
    Next I created sapmsUV0 3600/tcp entry at
    WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
    I restarted the system, as well as server.
    Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as “create JCO Destination &#61664;Deployed Content&#61664;local-&#61664;local/CompanyCodeGetList-&#61664;Applications&#61664; CompanyCodeGetList
    I Choosed the JCO Connections tab-&#61664; there are 2 entries those are
    (1) COMPANY_CODE_MODEL
    (2) COMPANY_CODE_RFC_METADATA
    So I started creating connection for COMPANY_CODE_RFC_METADATA.
    First one is
    General data Name : COMPANY_CODE_RFC_METADATA
    Client : 100
    I didn’t changed any default JCo pool configuration.
    J2EE Cluster
    There is a check box called “Use Local J2EE engine J2E on pava-vis75’ so I choosed that.
    Connection Type
    Dictionary Meta Data and application Data
    I choosed the first one.
    Then
    Msg. Server Connection
    Security
    After these, I tried to test the connection by clicking the ‘Test Connection.
    It is saying the error as
    First time
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
    second time
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
    Can any body please help me to solve this problem.
    From past 1 week on wards I have been trying to resolve this. But in vain.

    It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
    Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
    Regards,
    Eduardo.
    Message was edited by: Jesus Cil

  • How To Populate Application Server Dropdown List In JCo Destination

    Hi guys, I'm currently working on EP7 and just finished installing the ESS Business Package. The next step is to maintain the JCo Destinations in the Web Dynpro Console and here's where I got stuck. When I got to step 4.1 the field for the Application Server is a drop down list with no items in the list. How do you populate this list? Thanks in advance!

    Figured it out! Maintain an Web AS ABAP Technical System in the SLD.

  • No such JCO destination is defined in the SLD

    Hi All,
    Following JCo are not available in Portal 7.0 for MSS configuration.
    Already MSS Buss Pkg has been deployed in Portal.
    u2022     SAP_R3_SelfServiceGenericsFIN
    u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
    u2022     SAP_cProjects
    u2022     SAP_cProjects_MetaData
    Getting mention error for MSS application:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaDataFIN' in the SLD. No such JCO destination is defined in the SLD.
    Please suggest for resolution.
    Regards,
    SK

    You have to get this fixed through BASIS / Web Dynpro Content Administrator.
    Check under Content administrator -> Webdynpro whether all the JCO connections are working fine.
    Setting Up JCo Connections for MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/15d2060e344c2fbf22e526104c24bb/frameset.htm
    Once the ESS / MSS Business Packages are deployed, as a part of the post deployment steps JCO set up is to be completed
    Below JCO are to be set up for MSS -
    ●      General connections:
    ○       SAP_R3_SelfServiceGenerics
    ○       SAP_R3_SelfServiceGenerics_MetaData
    ●       Connections for the Team area:
    ○       SAP_R3_HumanResources
    ○       SAP_R3_HumanResources_MetaData
    ●      Connections for the Budget area:
    ○       SAP_R3_Financials
    ○       SAP_R3_Financials_MetaData
    ○       SAP_R3_SelfServiceGenericsFIN
    ○       SAP_R3_SelfServiceGenerics_MetaDataFIN
    Set up the following for branching to the details screen from Travel work items in the universal worklist:
    ○       SAP_R3_Travel
    ○       SAP_R3_Travel_MetaData
    ●      Connections for the Projects area:
    ○       SAP_cProjects
    ○       SAP_cProjects_MetaData

  • Failed JCO destination name 'WD_RFC_METADATA_DEST'    and MODEL DATA

    Hi Friends
    I am created "WD_RFC_METADATA_DEST". this meta data.When i am created this metadata i was called message server as technical system of CRM server.
    means i am created metadata for CRM System
    Once metadata had complted then i was cheing click on "Text"
    Here it display this error message
    Model Data test
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=ecc15 GROUP=PUBLIC R3NAME=E15 MSSERV=sapmsE15 PCS=1 ERROR       Group PUBLIC not found TIME        Fri Feb 19 01:12:26 2010 RELEASE     700 COMPONENT   LG VERSION     5 RC          -6 MODULE      lgxx.c LINE        4299 DETAIL      LgIGroupX COUNTER     1
    Meta data test
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=ecc15 GROUP=PUBLIC R3NAME=E15 MSSERV=sapmsE15 PCS=1 ERROR       Group PUBLIC not found TIME        Fri Feb 19 01:13:19 2010 RELEASE     700 COMPONENT   LG VERSION     5 RC          -6 MODULE      lgxx.c LINE        4299 DETAIL      LgIGroupX COUNTER     1
    What is problem. i m not getting can u tell me how slove this problem.
    Regards
    Vijay Kalluri

    Hi Vijay,
    You need check following thing to resolve this issue.
    1. Check the your host file entries for CRM System (Start>Run>enter 'drivers'>etc>hosts)
    2. Check SLD test is successfull or not.
    3. As per your error message group PUBLIC not found. Check in the CRM system (T-code : SMLG) whether PUBLIC group is available or not.
    Then check JCO destination parameter again and test it.
    Hope this will helps you.
    Thanks
    Arun

  • Jco Destinations not available in GRC AC 5.3

    Hello,
    We have installed GRC AC 5.3 with latest patch and configured SLD configuration. It is working fine but the standard virsa Jco destinations are not visible.
    Is there any additional settings required to get that Jco destinations?
    Regards,
    Kumar Rayudu

    Hi Kumar,
    JCo destinations not showing might be happening because of following two reasons
    1. AC capabilities are not deployed properly as mentioned by our friends in this message.
    2. Might be an issue with SLD Data Supplier in Visual Admin(VA):
    To resolve this logon to VA and select "SLD Data Supplier" under services. On right hand side bottom, you will see
    tabs of "Information", "HTTP Settings" & "CIM Client Generation Settings".
    Make sure entries in these tabs are correct and check for Data Transfer through SLD in these tabs. Once these tests are passed. Restart who system (not just J2ee).
    If the issue still persists, redploy AC capabilities via SDM with "Deployment Configuration" is set to "Update deployed SDA/SCAs that have any version".
    Hope this resolves your issue.
    Best Regards,
    Sirish Gullapalli.

Maybe you are looking for