ESS - JCo Destination using Meta data fails

[Former Member]

I am trying to configure ESS 50.4 on NW SP14 with Web AS Java 6.40. I imported the ESS BP, defined a system for R/3 system and its aliases (SAP_R3, SAP_R3_Cross, SAP_R3_Financials, SAP_R3_HumanResources, SAP_R3_Travel). On assinging the role. I got Java exceptions in all the iviews ( such as <b>Record Working Times - [Method getCatsData] java.lang.Exception: SAP_R3_Cross: No connection to SAP R/3 System; check user name and connection

Time Recording Calendar - [Method connectToSAP(SAP_R3_Cross)] java.lang.Exception: R3_CONNECTION_FAILED

Clock In/Out - [Method connectToBackend(SAP_R3_HumanResources)] java.lang.Exception: R3_CONNECTION_FAILED</b>)).

The reason for this was that my SLD was not configured. So configured the SLD and started the SLD server (according to weblog: /people/sugree.phatanapherom/blog/2005/08/14/configuring-sld-in-sneak-preview-sap-netweaver-04-sneak).

Added the entry in services file and restarted the system.

I was able to create Jco Destinations for: SAP_R3_HumanResources, SAP_R3_Financials, SAP_R3_SelfServiceGenerics, SAP_R3_Travel.

But i'm unable to Create any Jco Destinations using META DATA .... When I try to create SAP_R3_HumanResources_MetaData, I get the following error

"<b>Failed to create new JCO client connection SAP_R3_HumanResources_MetaData: 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:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) 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: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:95) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for SAP_R3_HumanResources_MetaData at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more</b> "

When i ran transaction "SMLG", i can see only one logon group.

On the iviews of ESS i still see the java exceptions same as before. None of them vanished. Do I need to install JCo or does it come when i installed Web AS Java 6.40.

Did I miss anything ?

Can anyone help me out?

[Former Member]

Hi Deepa D,

first of all JCO does come with the J2EE Eingine so there is no installation. Right now I am a littel confused on what you exactly want to install.

ESS 50.4 is an old ESS based on ITS. In there you do not need to set up an SLD for any R/3 backend connection. You only define the Systems in the Poral if you want to run it from the portal.

ESS 6.XX is based on WebDynpro and does require a running SLD.

Anyway I asume you want to use the Webdnpro ones and do guess that the problem is that you have no entry in your services file on *nix based OS's found under /etc/services on Windows %WINDOWS%\system32\drivers

etc on your system where the J2EE/Portal is running on. Search for an entry sapms<SID>. It should point to the port where the backend message server is running on. In general for Systems with instance number 00 this is 3600.

so the entry does look something like this

sapmsTTT 3600/tcp

if you cannot find it make an entry apropriate to your backendsystem in the services file and wait a few minutes before testing again. If you are using WebDynpro based ESS then you can do the test via.

http://<yourserver>:<yourport>/webdynpro/welcome and then use "Content Administration" and then the button "Maintain JCO Destination". There is a test button behind all the configured entries.

regards Ingo

[gregorw]

Hello,

I would suggest that you add a Logon Group called PUBLIC via Transaction SMLG and try again.

Regards

Gregor