Recreating WD_RFC_METADATA_DEST JCo Destination

Hi all!
I'm trying to access some bapis from a webdypro application and when creating the JCo Connections i get the following error when i test them:
"com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=idesdev GROUP=PUBLIC R3NAME=DEV MSSERV=sapmsDEV PCS=1 ERROR service 'sapmsDEV' unknown TIME Fri May 13 11:54:24 2005 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 MODULE ninti.c LINE 494 DETAIL NiPGetServByName2: service 'sapmsDEV' not found SYSTEM CALL getservbyname_r COUNTER 1 "
Actually, I have deleted the standard WD_RFC_METADATA_DEST destination and while recreating this JCo I am facing this problem.
WD_MODELDATA_DEST JCo is working fine.
The R/3 system I have is a single server and not a load balanced server. Hence, I am not able to generate the list in logon pad for the given message server(sapmsDEV), which can be used in creation of Data Dictionary based JCo.
How can I mask a Single server as a Load Balanced server, so that I can use it for METADATA_DEST JCOs?
Thanks.
Puneet.

Hi SG,
I guess I am getting confused
In the R/3 system(DEV) I have this entry:
      sapmsDEV      3600/tcp
and in J2EE system(J2E) I have this entry:
      sapmsJ2E      3600/tcp
and you are suggesting that in the J2EE system (J2E) I should now have:
      sapmsJ2E      3600/tcp
      sapmsDEV      36??/tcp
Kindly confirm if I am getting it right and also help me with the port for sapmsDEV entry (which as per your last mail should be 3600, can two services run on same port?)
Thanks.
Puneet

Similar Messages

  • 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

  • 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

  • Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST'

    Hi Experts,
    I am using NWDS 7.1 ehp1 version and  i developed a sample application here to retreive the data from r/3.
    when i try to execute the application it's giving the following error..
    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.
    can anybody help me to solve this issue..
    thanks,
    viswa

    Hi,
    First test your destination.
    'WD_RFC_METADATA_DEST'
    Login as an Administrator, then click on "Check SLD", Check if if in your System Landscape Directory Both the ABAP technical system and a Web AS JAVA. are created or not????
    If not create the two systems.
    If they are already created then,
    click on "Maintain JCo Destinations" and there you can see all the applications and their corrosponding metadatas. If JCo is already created then status comes in green color or else status comes in red color.
    Check if these JCos are created or not....
    If they are not created then create the JCo destinations.
    If they are already created then Ping them....
    But as per your error, it seems like you haven't maintained JCo destinations.
    Refer this link,
    http://YourPortalURL:50000/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
    Regards,
    Sunaina Reddy T

  • Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD

    Hi!!!
          I am facing a problem, when I run any application, I get the following error,
    *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. *
    Can any one please give some suggestion, on how to overcome this problem.
    Cheers!!!
    Umang

    Hi Umang,
    It seems like you have not activated or Defined your JCO (Java Connectors) in the System Landscape Directory(SLD). Please Login to your SLD and check if you can find the JCO ('WD_RFC_METADATA_DEST'). If you manage to find the Specified JCO, then you need to activate the
    Java Connector.
    I hope this helps. Please let me know if you have any more issues. Dont forget to close the thread if it is answered.
    Best Wishes,
    PG.

  • 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

  • Unable to create the Jco destination

    Hi Experts,
    I am facing a strange issue, As part of ESS and MSS i have to create some Jco destinations in the Wedynpro content administrator.I am giving the all the necessary information for the Jco creation when i click on Finish, jco is not getting creted.
    And the status is in Red color...
    Can any one help me what i am missing???

    Hi Anil,
    Hope you are doing good.
    Is the SLD up and running?
    If the issue persists:
    1.)Delete all the JCO destinations from Content Admin and then from SLD
    2.)Restart the complete cluster once and do a SLD data trigger.
    3.)Then recreate all the jco destinations again from content admin. (Important note: using the "New JCO Message Server Destination" button in SLD will create an inconsistent state. Please do not use it.)
    let me know how this goes.
    Thank you!
    Kind Regards,
    Hemanth
    SAP AGS

  • Wrong JCO destination used at Runtime

    hi,
    I created a Model using the following JCO Destinations
    'WD_RFC_METADATA_DEST_HCM'
    When I run the application, it gives me folowing error
    Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD
    Where is it getting this 'WD_RFC_METADATA_DEST'  ? though my JCO destination name is 'WD_RFC_METADATA_DEST_HCM'
    Thanks !
    seventyros

    Hi,
    Make sure you deploying to the SAME server where you have configured and maintained the JCo destination.
    Also check the server name and port when you are running your WD application and server name and port you are using for WD content administration.
    Also What is the version of your NWDS ?
    In NWDS 7.1, we would require a totally different way to maintain the JCo destinations comparing to the past.
    We now have to maintain the JCo destinations not in the JCo Connection Administrator, but in the NWA under u201CConfiguration Managementu201D - > Security -> Destinations.
    This [doc|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09527da-39a7-2b10-9f99-c6a007e516a5?overridelayout=true] explains the same...
    Regards,
    Vijay.

  • 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

  • Failed to resolve JCO destination name 'WD_ALV_METADATA_DEST' in the SLD

    Hello,
    I've got the following problem and hope anybody here could help me with this issue.
    There are two servers (CE 7.1). One DEV and one PROD system.
    At the DEV system "create print version" functionality of an alv-table in my visual composer app works fine.
    But not at the PROD system: There the following message comes up:
    failed to create or init instance of model ''com.sap.ip.bi.alv.service.persist.model.Persist'' in scope APPLICATION_SCOPE with instanceId ''<null>'': com.sap.tc.webdynpro.progmodel.model.api.WDModelException: failed to create instance of model 'com.sap.ip.bi.alv.service.persist.model.Persist'
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:336)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getOrCreateModelInstanceFromScopeMaintainer(ModelFactory.java:263)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getModelInstance(ModelFactory.java:70)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:94)
    at com.sap.tc.webdynpro.progmodel.model.api.WDModelFactory.getModelInstance(WDModelFactory.java:73)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.RFCInit(PersistRFC.java:317)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.RFCGetHandle(PersistRFC.java:250)
    at com.sap.ip.bi.alv.service.persist.PersistRFC.setPersonalizationKey(PersistRFC.java:164)
    at com.sap.ip.bi.alv.service.persist.Persist.setPersonalizationKey(Persist.java:157)
    at com.sap.ip.bi.alv.ui.persist.dialog.PersistUI.onSetPersonalizationKey(PersistUI.java:107)
    at com.sap.ip.bi.alv.ui.persist.dialog.PersistUIComp.setPersonalizationKey(PersistUIComp.java:244)
    at com.sap.ip.bi.alv.ui.persist.dialog.wdp.InternalPersistUIComp.wdInvokeMethod(InternalPersistUIComp.java:244)
    at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
    at $Proxy650.setPersonalizationKey(Unknown Source)
    at com.sap.ip.bi.alv.ui.settings.SettingsComp.setPersonalizationKey(SettingsComp.java:545)
    at com.sap.ip.bi.alv.ui.settings.wdp.InternalSettingsComp.wdInvokeMethod(InternalSettingsComp.java:466)
    at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
    at $Proxy649.setPersonalizationKey(Unknown Source)
    at com.sap.ip.bi.alv.util.UISettingsComponent.setPersonalizationKey(UISettingsComponent.java:485)
    at com.sap.ip.bi.alv.ALVController.refreshListInternal(ALVController.java:2794)
    at com.sap.ip.bi.alv.ALVController.refreshServicesInternal(ALVController.java:2943)
    at com.sap.ip.bi.alv.ALVRefreshManager.refresh(ALVRefreshManager.java:510)
    at com.sap.ip.bi.alv.ALVController.refresh(ALVController.java:2235)
    at com.sap.ip.bi.alv.TableView.render(TableView.java:285)
    at com.sap.ip.bi.alv.wdp.InternalTableView.render(InternalTableView.java:329)
    at com.sap.ip.bi.alv.TableView.wdDoModifyView(TableView.java:189)
    at com.sap.ip.bi.alv.wdp.InternalTableView.wdDoModifyView(InternalTableView.java:554)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:89)
    at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:569)
    at com.sap.tc.webdynpro.progmodel.window.ViewController.modifyView(ViewController.java:251)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:430)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:443)
    at com.sap.tc.webdynpro.clientserver.phases.ModifyViewPhase.execute(ModifyViewPhase.java:70)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:512)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:52)
    at com.sap.tc.webdynpro.clientimpl.scxml.client.SmartClient.executeTasks(SmartClient.java:687)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1549)
    at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1363)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoProcessing(AbstractExecutionContextDispatcher.java:154)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppProcessing.doService(DispatchHandlerForAppProcessing.java:35)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoProcessing(ExecutionContextDispatcher.java:114)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:80)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:618)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:649)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:570)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:309)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:743)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:258)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:259)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
    at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
    at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToDispatcherContext(ExecutionContextDispatcher.java:146)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
    at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
    at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:486)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
    at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
    at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
    at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
    at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
    at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
    at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
    at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Unable to create connection for RFC Metadata Repository WD_ALV_METADATA_DEST
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:180)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModel.metadataRepository(AiiModel.java:106)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModel.<init>(DynamicRFCModel.java:106)
    at com.sap.ip.bi.alv.service.persist.model.Persist.<init>(Persist.java:144)
    at com.sap.ip.bi.alv.service.persist.model.Persist.<init>(Persist.java:119)
    at sun.reflect.GeneratedConstructorAccessor2233.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
    at java.lang.Class.newInstance0(Class.java:350)
    at java.lang.Class.newInstance(Class.java:303)
    at com.sap.tc.webdynpro.progmodel.model.core.ModelFactory.getNewModelInstance(ModelFactory.java:330)
    ... 109 more
    Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)
    at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:38)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.RFCMetadataRepository.getSingleton(RFCMetadataRepository.java:174)
    ... 119 more
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_ALV_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:420)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:234)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:219)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)
    ... 121 more

    Hi
    Check This Thread
    [Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST']
    See this help
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20use%20the%20web%20dynpro%20content%20administrator.pdf]
    Kind Regards
    Mukesh

  • How to Maintain Jco Destinations ( using ARFC2 )

    Hi Friends
    I call ARFC2  setting WD_MODELDATA_DEST and WD_RFC_METADATA_DEST.
    ... then get error message.
    com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination WD_RFC_METADATA_DEST does not exist
        at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:195)
        at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:344)
        at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:96)
        at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
        at com.sap.tc.cm.arfc2.metadata.RFMParser.<init>(RFMParser.java:78)
        ... 74 more
    I wnat to Maintain the demo01's JCo Destinations, but the page is null.
    Where can I create WD_MODELDATA_DEST、WD_RFC_METADATA_DEST.
    thx.

    Hi BenChen,
    You need to create JCO Destination in the SAP Portal >> Content Administration >> Web dynpro >> Maintain Jco Destinations.
    If "Create" button not active,then you need to check SLD running or not and SLD data supplier.
    Please refer to below documents will helps
    [System Landscape Directory Process and JCo Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0c1d495-048e-2b10-babd-924a136f56b5?quicklink=index&overridelayout=true]
    [JCO Destination Errors|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0?quicklink=index&overridelayout=true]
    [How to Configure the JCo Destination Settings|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/user-interface-technology/wd%20java/7.0/portal%20integration/how%20to%20configure%20the%20jco%20destination%20settings.pdf]
    Hope it will helps
    Regards
    Arun Jaiswal

  • 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

Maybe you are looking for

  • Link to files in iWeb

    Newbie to iWeb! I have created a site in iWeb, and want to create links to pages (.htm) generated by another program (Reunion). When I try to create the links I can't get iWeb to bring up the "linked" page. I've tried using link to file (clearly wron

  • Connecting PS4 or Xbox to iMac

    From what I've heard from people, it is not impossible to connect either PS4 or Xbox to iMac. But apparently it is very complicated. So what do I exactly need to make this happen? And... how and in what order do I connect these to iMac? How much will

  • Undo a batch job

    Hi, I uploaded entries into table T499S using LSMW.  Now, I need to undo this upload, meaning that the newly added entries need to be deleted.  Is it possible to reverse / undo the batch job that was run? Thanks Muru

  • Importing Material transaction on a FIFO organization.

    We are trying to load material transactions using MTL_TRANSACTION_INTERFACE. The organization is setup as FIFO costed. We are able to load the MTL_TRANSACTION_INTERFACE, we can also sees the transaction on the Open Interface from inventory and to run

  • Navigation Panel not displayed

    Hi, I have just installed my EP server. When I log in, I do not see the navigation panel. It gives me an error "Error: Access is denied" followed by an error "Error: 'undefined' is null or not an object". I checked the browser settings for security,