error Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA

[Former Member]

Hello

I just tried to create the Jco connections for WD_FLIGHTLIST_MODELDATA_DEST and WD_FLIGTHLIST_RFC_METADATA_DEST.

The parameters for together Jco connections were:

Destination name

WD_FLIGHTLIST_MODELDATA_DEST

Client

020 (my mand in r3)

J2EE Cluster

J2E on pcc16298 (my pc)

Max. pool size:

5

Max. connections:

10

Connect timeout:

10

Max. waiting time:

30

Data Type:

Dictionary Metadata

Message Server:

(Theren´t nothing on the drop text)

Use SAProuter:

not activated

Used Method:

User/password(deffault,I can´t modify)

Name:

developer2 (my name in r3)

password: **** (my pass in r3)
Language:

spanish

SNC Mode:

Off

What´s wrong in that? because I get this error:

+Failed to create new JCO client connection WD_FLIGHTLIST_MODELDATA_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
...+


and for WD_FLIGTHLIST_RFC_METADATA_DEST, I am getting this error:

+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
...+

[RichHeilman · Accepted solution]

You need to set up your SLD. Here you will be able to create technical systems which can be used in setting up your jCo connections. Please search the forum for SLD.

Regards,

Rich Heilman

[Former Member · Accepted solution]

Thanks Rich for your suggestion, but , when I am setting my R3 under Web AS ABAP in SLD, I can´t continue because in the Technical System Wizard - Software Products And Components I don´t have products availables...

[Former Member · Accepted solution]

... Ohh I forget it... I just have installed SAP Web AS Java 640 Slim edition. I am setting the technicalsystem for for Web As Java & SLD.

[RichHeilman · Accepted solution]

You need to import the catalog. In the SLD, look for something that says "IMPORT".

Regards,

Rich Heilman

[Former Member · Accepted solution]

Hi Herman,

You need to import CIM contents to get product list in creating technical system wizard.

For that, open SLD and there goto <b>Administration</b> then choose Import under content list.

There, you can find CIM Content import button. Click on that.

It will import all product list and takes around 30-40 mins. to complete.

After that create your technical system and the configure JCO.

Regards,

Bhavik

[Former Member · Accepted solution]

Hi Bhavik... After do that. I got a new problem with SMC dis+work.exe doesnu00B4t start, so I can start SLD.

This is the error in the file
172.26.33.27\usr\sap\BWD\DVEBMGS00\work\dev_disp:

<i>

• DP_FATAL_ERROR => Gateway could not be started - I better exit now

• DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

• ERROR => DpWpKill: illegal pid (-1,5) [dpxxtool.c 2384]

• ERROR => DpWpKill: illegal pid (-1,5) [dpxxtool.c 2384]

• ERROR => DpWpKill: illegal pid (-1,5) [dpxxtool.c 2384]

• ERROR => DpWpKill: illegal pid (-1,5) [dpxxtool.c 2384]

</i>

Thanks

[Former Member · Accepted solution]

Hi Herman,

Imporing of CIM contents done successfully??

It should not give any such problem.

Give full error log.

Regards,

Bhavik

[Former Member · Accepted solution]

Hi Bhavik,

The importing of CIM was succesfully... but when I try to access to my webdynpro an error is shown. please refer to this link:

http://hernanrestrepo.4t.com/main.htm

that I have create to show you my configuration process.

Best & regards,

[Former Member · Accepted solution]

Hi Hernan,

Have you checked SLD by clicking on "Check SLD Connection" button in Content administration?

HAve you assigned SLD information in visual administration-> services-> SLD data supplier-> CIM Client settings.

Regards,

Bhavik

[Former Member · Accepted solution]

You're meta data connection has to connect to a server that has a logon group defined on it. Does your R3 server have a logon group defined?

[Former Member · Accepted solution]

Hi,

I have create a r3 logon group and I could create the JCo Connectors but now... I have set the sld and I´ve started it, but the

run button

in not active when I tried to execute my application. In the next link you can see my configuration and my problem...

Thanks a lot,

Hernán Restrepo

[Former Member · Accepted solution]

The link:

http://hernanrestrepo.4t.com/sld_config.HTML

Best & Regards,

Hernán Restrepo

[Former Member · Accepted solution]

Expand the node that you have highlighted. There should be a couple of choices in there. I can't remember which one you have to click on to activate the run button. You'll have to dig a bit but I think it should work now.

[Former Member · Accepted solution]

This is the structure of my application I have:

Local/TuWD_Flightlis

-> Applications

-> FlightListApp

-> Components

-> FlighListComp

-> Models

-> FlightModel

When I press FlightListApp at the bottom of the page appear the error:

Failed to path classpath for local/Tu_FlightList. So, the botton is not activated still.

[Former Member · Accepted solution]

Hi Hernan,

You have pinged your JCO connections. But have you tested it by clicking on test button for both jco connections? First, test those JCOs. The button disable problem should not come by that reason. But for avoiding future problems please test your JCOs.

And to run your application, use following link:

http://<server>:50000/webdynpro/dispatcher/local/TutWD_FlightList/<Application name>

You can find application name under Applications node.

Or choose node "Applications" under your webdynpro project "local/TutWD_FlightList". Expand it you will find your application there. Click on it. Now, you can see those buttons enabled.

Regards,

Bhavik

[Former Member · Accepted solution]

Hi Bhavik,

I have tested the JCOs, with that there´s not problem. I tried to execute my application with the link:

http://server:5000/webdynpro/dispatcher/TutWD_FlightList/FlightListApp

And the next error is shown:

500 Internal Server Error

Application error occurs during processing the request.

Details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Wrong WebDynpro-URL: no application name specified

at com.sap.tc.webdynpro.serverimpl.wdc.adapter.WebContextAdapter.resolvePath(WebContextAdapter.java:67)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.adapter.WebContextAdapter.getDeployableObjectName(WebContextAdapter.java:118)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:80)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:48)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

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)

[Former Member · Accepted solution]

I Expand Local/Tut_WDFLightList at the first time: The run botton was activated, I tried to run but the following error was shown:

<i>

An error has occurred:

"Failed to process the request."

Please contact your system administrator.

-

---

Hide details

Web Dynpro client:

HTML Client

Web Dynpro client capabilities:

User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; 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.4011.00.0000.20050201163348.0000 (release=630_VAL_REL, buildtime=2005-02-10:22:06:31[UTC], changelist=325302, host=PWDFM026)

Web Dynpro code generators of DC local/TutWD_FlightList:

SapDictionaryGenerationCore: 6.4011.00.0000.20050127161623.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:53:14[UTC], changelist=324383, host=PWDFM026.wdf.sap.corp)

SapMetamodelWebDynpro: 6.4011.00.0000.20050121170001.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:56:30[UTC], changelist=322883, host=PWDFM026.wdf.sap.corp)

SapMetamodelCore: 6.4011.00.0000.20050121165648.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:47:28[UTC], changelist=322878, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationTemplates: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-03-03:21:10:18[UTC], changelist=329752, host=PWDFM026)

SapWebDynproGenerationCTemplates: 6.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-03-03:21:10:18[UTC], changelist=329752, host=PWDFM026)

SapGenerationFrameworkCore: 6.4011.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:46:38[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)

SapIdeWebDynproCheckLayer: 6.4011.00.0000.20050215134310.0000 (release=630_VAL_REL, buildtime=2005-03-03:21:00:10[UTC], changelist=329103, host=PWDFM026.wdf.sap.corp)

SapMetamodelDictionary: 6.4011.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:50:44[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)

SapMetamodelCommon: 6.4011.00.0000.20050121165648.0000 (release=630_VAL_REL, buildtime=2005-03-03:20:47:38[UTC], changelist=322878, host=PWDFM026.wdf.sap.corp)

SapWebDynproGenerationCore: 6.4011.00.0000.20050215134310.0000 (release=630_VAL_REL, buildtime=2005-03-03:21:00:38[UTC], changelist=329103, host=PWDFM026.wdf.sap.corp)

SapDictionaryGenerationTemplates: (unknown)

Web Dynpro code generators of DC sap.com/tc_wddispwda:

No information available

Web Dynpro code generators of DC sap.com/tc_wdcorecomp:

No information available

J2EE Engine:

6.40 patchlevel 89291.313

Java VM:

Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.

Operating system:

Windows 2003, version: 5.2, architecture: x86

-

---

Error stacktrace:

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tut.wd.flightlist.model.types.FlightModel:com.sap.tut.wd.flightlist.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException: 'WD_FLIGHTLIST_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_FLIGHTLIST_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:297)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:753)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:371)

at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:400)

at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:138)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:746)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

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:41)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:134)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:371)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:599)

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.doGet(DispatcherServlet.java:48)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

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)

Caused by: com.sap.dictionary.runtime.DdException: 'WD_FLIGHTLIST_RFC_METADATA_DEST' not properly defined! Unable to create Metadata connection for Dictionary Provider. Either the logical System Name 'WD_FLIGHTLIST_RFC_METADATA_DEST' has not been properly defined in the System Landscape Directory, or you are not using a MsgServerDestination (AppServerDestinations are not permitted for Metadata connections)

at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:225)

at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)

at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)

at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)

at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)

at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:295)

... 45 more

-

---

end error----

---

</i>

at the second time: when I clicked the Application at the bottom of the page was shown the following error:

Failed to find classpath for local/TutWD_FlightList

[Former Member · Accepted solution]

Hi Hernan,

Error clearly say that 'WD_FLIGHTLIST_RFC_METADATA_DEST' JCO is not available. But, you said that you have tested JCOs correctly. Check your JCOs once again.

And why you are not trying to deploy and run your application from NWDS?

Regards,

Bhavik

P.S : Please award points if answer was helpful.

[Former Member · Accepted solution]

Is your metadata connection to a message server with a logon group defined? If not the connection will fail. As Bhavik mentioned, please try and test the JCo connection.

[RichHeilman · Accepted solution]

Please "test" and "ping" your connections, are they all "green"? If so, the next thing is to check to see if the BAPI being used actually exists in your r/3 system along with the structure Bapisfldat. In my case, it did not.

Regards,

Rich Heilman

[Former Member · Accepted solution]

Bhavik , Eric ...

I´ve tested and have done ping successfull but I was thinking that the problem could be caused by the bapi... But I don´t know how check this.

Thanks

Kings Regards,

Hernán Restrepo

[Former Member · Accepted solution]

Hi Hernan,

Do you have access to your SAP R/3 system?

If yes then logon to your SAP R/3 system. Goto SE37 transaction. There, write your FM name and execute it. Give proper input data and execute.

Regards,

Bhavik

[Former Member · Accepted solution]

Hi,

I´ve executed the BAPI_FLIGHT_GETLIST with SE37 in r3. the function is working but with not data. But I don´t understand why it doesn´t working when I try to run my application. I´ve tested and ping the JCo.

If I can test and ping the JCo, it means that my SLD setting is well ??? Even so, Is possible to have a bad SLD setting?

thanks,

Best & regards

[RichHeilman · Accepted solution]

I would say that if you can test and ping, that the jCo connection is good.

Regards,

Rich Heilman

[Former Member · Accepted solution]

Is there data in your system to support this transaction? I am thinking that you may be getting an error because those tables are empty.