Integration between EP 6.0 and ESS Webdynpro

[Former Member]

We have installed the XSS components for MyERP2004 and are now attempting to run the WebDynpro iViews within EP 6.0.

Has anyone encountered the following error? I get the same error when attempting to run the service from the Dynpro content administratrion.

Error recieved:

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException:

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

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.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)

at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:362)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:189)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:171)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)

at com.sap.tc.webdynpro.progmodel.generation.IControllerDelegate$LegacyAdapter.wdDoInit(IControllerDelegate.java:39)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

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

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:346)

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

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

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

Caused by: com.sap.dictionary.runtime.DdException:

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

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

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

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)

... 40 more

[Former Member · Accepted solution]

Hi Stephen,

Are you accessing functionModules in R/3 system ??

If so you need to configure SLD first in the visual administrator and create JCo connection in the content administrator.

Regards, VIP

[Former Member]

Hi

Did you get this working? We are experiencing a simoilar problem.

[Former Member]

If I navigate to the WebDynpro content administrator tab, the SAP_R3_HumanResources and SAP_R3_HumanResources_MetaData connections for the application components are gray.

When I develop local apps, I need to activate the JCO connection with SLD. It seems a step has been missed.

Are your JCO connections active or green? Has anyone seen the JCO connections gray/disabled after the XSS configuration? I assume that these will need to be enabled and activated.

[Former Member]

We have configured the sld and enabled the JCO connections. Everything shows green and the test and functions are successful.

However, we are executing the application component Per_address_Ar from the WebDynpro content administrator. We continue to see the following error. Please provide information on how to troubleshoot the same error listed above.

[Former Member]

Hi Stephan,

99% of the times this error is because the JCO Connections have not been setup correctly. When you goto "Maintain JCo Destinations" Page, what all destinations you see there? Do you see SAP_R3_SelfServiceGenerics and SAP_R3_SelfServiceGenerics_MetaData also? If yes, do maintain these.

Another possibility can be when you are maintaining these, on the third step it asks you about the Data Type, there you need to specify Application Data for SAP_R3_HumanResources and SAP_R3_SelfServiceGenerics. For SAP_R3_HumanResources_MetaData and SAP_R3_SelfServiceGenerics_MetaData you have to select the Dictionary Meta Data type.

Hope this helps.

Regards,

Shubham

[Former Member]

You are correct. I implemented the remaining connections and it solved my issue.

Thanks for the response.

[Former Member]

Hi Shubham: How did you get the JCo connections to work? If you have time, can you please read this thread, and respond if possible? Thanks!

/thread/261784 [original link is broken]