cancel
Showing results for 
Search instead for 
Did you mean: 

can't create JCo Destinations. javalang.nullexception error

Former Member
0 Kudos

in my web dynrpo content administrator, i cannot create JCo Destinations. I immediately get a

java.lang.NullPointerException error

at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:990)

at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237).....

The list is quite lengthy, but overall I can't see anything that stands out as the reason.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Dave,

Before create the JCO you should configure the SLD.

After Check the SLD connection sucess then connect the JCO connection

Kind Regards

Mukesh

Former Member
0 Kudos

SLD is configured and successfully test connects.

Former Member
0 Kudos

Hi,

Try this:

1. Open http://<yourserver>:<port>/sld

2. Navigate to content maintenance

3. Navigate to subset: landscape definition

Class JCO message server destination & JCO application server destination

Delete everything that doesn't belong there.

Regards,

Satyajit.

Message was edited by: Satyajit Chakraborty

Former Member
0 Kudos

Hi Dave,

U have Successfully completed SLD Configuration,

Go through the Following Steps(JCo Connection)Like,

-- General Data, Enter the Client of the System and Client No. (JCo Connection is Pointing to)

--J2EE Cluster, Select the J2EE Cluster you wish the JCo destination to be assigned

-- Select the Destination Type, Either Application/Dictionary data

-- Appl.Server, You may only select Servers/Logon Groups From the Drop down list that have first been defined as technical Systems in SLD.

-- Message Server, Application Data JCo destination is connected must have atleast one logon group.( if this is not done ,use SMLG transaction code to create in SAP System)

--Security, If you have selected connection Type as Application Data , then in the Security Screen you would appear Authentication Techniques and select a appropriate one .

if you have selected connection type as a Dictionary meta data then provide User Name and Password

If this is useful to you ,don't forget to award Points

--Venkat

Award Points

Former Member
0 Kudos

Hi Guru.

While created JCO i got following exception.

I dint select message server information while cretin of JCO. it would mandatory for creating JCO. because i dint get in information about message server while creating of JCO. if it need where can configure to get Message server in formation. please give me some guide lines

Failed to create new JCO client connection WD_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: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:659) 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.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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_MODELDATA_DEST at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:106) 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.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) ... 35 more

Best regards

Ramana

Former Member
0 Kudos

Even i am facing the same problem as above mentioned plz someone suggest us on this issue

Answers (4)

Answers (4)

Former Member
0 Kudos

thanks to all for the helpful input, and especially Satyajit Chakraborty. My problem was that I couldn't even get past the 'create JCo Destination' without getting the exception error. Deleting the unneeded destinations in that path Satyajit provided worked.

Former Member
0 Kudos

Hi,

Create the JCO WD_MODELDATA_DEST with Single Server and WD_RFC_METADATA_DEST with Mesage Server

Kind Regards

Mukesh

former_member85655
Active Participant
0 Kudos

You have missed out something while defining the JCO destinations. Please use this documentation wheile defining the connections.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/526bd490-0201-0010-038e-d3f...

Regards,

Arun

Former Member
0 Kudos

Hi,

In the tab JCO Destinations, are you able to see the names of JCO used to import models in the Web Dynpro application? If they are there, give necessary credentials of the SAP R/3 system such as userid, password, client. Also ensure that you have included the message server of the R/3 and port, in the service file of the Web AS system.

Still facing error, place the full error trace.

Regards

Srinivasan T

<b>Helpful answer=>points</b>