Web DynPro : JCO Connection

[Former Member]

Hi All,

I am getting following exception while deploying my application.

<b>com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.demo.model.types.Saknr could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.</b>.

I have followed the configuration steps for SLD.

All the JCO connection status is showing as green.

But there is some problem over here. When I am creating JCO Connection for Model (Application Data), The connection test is successful.

But same is failing for dictionary type meta data.

<b>Error is com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection</b>.

While running the application (JCO Coonection) from WebDynPro-Content administrator, it is showing error as above

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.demo.model.types.Saknr could not be loadedcom.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.</b>

Please help me to sort this out.

I will reward point freely who ever will help me in this.

Regards

Satya

[Former Member]

Hi All,

You can add PUBLIC Logon Group using SMLG transaction

Thanks

Denis

[arun_srinivasan]

hi,

Check out whether the following r done

Set the service name in the path as shown below

c:\windows\system32\drivers\etc\services file and save the service file.

Make sure that the service name and port no are correctly copied there

It should be in the format

sapms<SID> 3600/tcp

Some times the group does not exists in R/3. Please create PUBLIC in R/3. If you are having different group in R/3 than PUBLIC, use that one and you need to change settings in SLD.

hope this helps,

Regards,

Arun

[Former Member]

Dear Arun,

Thanks for your reply.

I checked in the services file ..The entry is there.

<b>sapmsMI1 3600/tcp # SAP System Message Port</b>

MI1 is the SID.

But I could not get what does that PUBLIC in R/3 means. How to check that out? What does that R/3 means ? Is this ABAP component of WebAS or the Actual IDES system where the BAPI resides? Please help me in this. I am very much new to webdynpro programming.

Thanks

Satya

[arun_srinivasan]

hi,

while creating technical system for MI1 check whether public is coming in logon groups of message server.

Regards,

Arun

[Former Member]

<b>Please refer to the complete stack trace of the error</b>

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.4011.00.0000.20050217164947.0000 (release=630_VAL_REL, buildtime=2005-02-20:21:49:12[UTC], changelist=329752, host=PWDFM026)

Web Dynpro code generators of DC local/SampleProject1:

SapDictionaryGenerationCore: 6.4009.00.0000.20041026131628.0000 (release=630_REL, buildtime=2004-11-02:22:13:11[UTC], changelist=295793, host=PWDFM027.wdf.sap.corp)

SapMetamodelWebDynpro: 6.4009.00.0000.20041026132448.0000 (release=630_REL, buildtime=2004-11-02:22:17:25[UTC], changelist=295810, host=PWDFM027.wdf.sap.corp)

SapMetamodelCore: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:29[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)

SapWebDynproGenerationTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)

SapWebDynproGenerationCTemplates: 6.4009.00.0000.20041102105304.0000 (release=630_REL, buildtime=2004-11-02:22:38:28[UTC], changelist=297524, host=PWDFM027)

SapGenerationFrameworkCore: 6.4009.00.0000.20041026132141.0000 (release=630_REL, buildtime=2004-11-02:22:05:28[UTC], changelist=295805, host=PWDFM027.wdf.sap.corp)

SapIdeWebDynproCheckLayer: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:21:59[UTC], changelist=295820, host=PWDFM027.wdf.sap.corp)

SapMetamodelDictionary: 6.4009.00.0000.20040805191532.0000 (release=630_REL, buildtime=2004-11-02:22:10:20[UTC], changelist=270520, host=PWDFM027.wdf.sap.corp)

SapMetamodelCommon: 6.4009.00.0000.20040909194107.0000 (release=630_REL, buildtime=2004-11-02:22:06:42[UTC], changelist=280398, host=PWDFM027.wdf.sap.corp)

SapWebDynproGenerationCore: 6.4009.00.0000.20041026133106.0000 (release=630_REL, buildtime=2004-11-02:22:22:31[UTC], changelist=295820, host=PWDFM027.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:

No information available

Java VM:

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

Operating system:

Windows XP, version: 5.1, architecture: x86

-

---

Error stacktrace:

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.demo.model.types.Saknr could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)

at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)

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

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.clientserver.cal.ClientComponent.init(ClientComponent.java:346)

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

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: TypeBroker failed to access SLD: Error while obtaining JCO connection.

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)

at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)

at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)

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

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.getSimpleType(DdBroker.java:170)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)

... 31 more