Skip to Content
author's profile photo Former Member
Former Member

Unmanageable JCo Connection - some help pls.

Hi experts,

For a while I try to figure out how to use ABAP functionality (via JCo destinations) from within Web Dynpro, e.g. the tutorial application

TutWD_Flightlist

.

My system:

Specifies the version of the system
Cluster-Version: 6.40   PatchLevel 102141.313
Build-On:Monday, February 20, 2006 19:58 GMT
Perforce-Server: 
Project-Dir:JKernel/630_VAL_REL
JKernel Change-List:102141
Build machine:SAPInternal
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
SP-Number: 16
Source-Dir: D:\make\engine\630_VAL_REL\builds\JKernel\630_VAL_REL\archive\dbg

The SLD connection is up and running - tested via CIM Client Test button...

Creating the JCo Connections in the Content Administrator there are following facts:

starting with WD_FLIGHTLIST_MODELDATA_DEST (= application data) I pass through all relevant steps like

1 General data

2 J2EE Cluster

3 Destination Type (here appl. data as datatype)

4.1 Appl. Server

4.2 Msg. server

5 Security

6 Summary

and so, pressing the button Finish succeeds in a positive system answer.

(Rem.: it's a feature that the JCo Destination Details are not actualized yet in that moment, and that you must go back through all the steps for finishing the ...MODELDATA_DEST destination to be prepared for the next configuration run of ...RFC_METADATA_DEST destination?!)

Remembering that rfc_metadata are not appl. data, I set in the step 3

Destination Type

the radiobutton for Dictionary Meta Data (Data Type) and vice versa the Destination Type sounds load-balanced connection (here you can change nothing). All other steps for this destination make no problems. The system gives JCo destination 'WD_FLIGHTLIST_RFC_METADATA_DEST' was successfully updated in SLD. . Also, here are the JCo Destination Details not actualized in that moment.

Starting the Web Dynpro gives

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: failed to create provider: Connect to message server host failed
Connect_PM  TYPE=B MSHOST=obiwan GROUP=PUBLIC R3NAME=NSP MSSERV=sapmsNSP PCS=1

ERROR       Group PUBLIC not found

TIME        Tue Jun 03 18:32:03 2008
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3515
DETAIL      LgIGroup
COUNTER     1

	at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
	at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:229)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:660)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:660)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:660)
	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:436)
	at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:374)
	at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:403)
	at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
	at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
	at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
	at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:207)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:660)
	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:539)
	at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:397)
	at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:554)
	at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:421)
	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:135)
	at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:404)
	at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:618)
	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:390)
	at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
	at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
	at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
	at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
	at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
	at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
	at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
	at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.dictionary.runtime.DdException: failed to create provider: Connect to message server host failed
Connect_PM  TYPE=B MSHOST=obiwan GROUP=PUBLIC R3NAME=NSP MSSERV=sapmsNSP PCS=1

ERROR       Group PUBLIC not found

TIME        Tue Jun 03 18:32:03 2008
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3515
DETAIL      LgIGroup
COUNTER     1

	at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
	at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
	at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
	at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
	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:303)
	... 49 more
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
	at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
	... 56 more
Caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed
Connect_PM  TYPE=B MSHOST=obiwan GROUP=PUBLIC R3NAME=NSP MSSERV=sapmsNSP PCS=1

ERROR       Group PUBLIC not found

TIME        Tue Jun 03 18:32:03 2008
RELEASE     640
COMPONENT   LG
VERSION     5
RC          -6
MODULE      lgxx.c
LINE        3515
DETAIL      LgIGroup
COUNTER     1

	at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:414)
	at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:889)
	at com.sap.mw.jco.JCO$Client.connect(JCO.java:3159)
	at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:90)
	at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:122)
	... 61 more

After this, I remove and repeat configuring the last "METADATA"

destination but at step 3 I set now appl. data for data type to get the possibility to change to single server connection. After finishing I get a positive answer from the system like before, and starting the Web Dynpro there are the same errors as before.

So, pls. help me to get my system running.

Thank you in advance

Karl-Christian

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 03, 2008 at 05:47 PM

    This error is due to problem in Configuring ECC / R3 system as Tehcnical System in your SLD Sever. Go to "Technical System Browser" in your SLD and select "Web AS ABAP" in Technical System Type dropdown. Please pay attention to "ERROR Group PUBLIC not found" in your error message.

    Cheers,

    ~kranthi

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.