Web Dynpro - Problem with (SLD) JCO Connection

[Former Member]

Hi EP Experts,

I have a problem (EP6SPS12) in specifying a JCO Connection for a Web Dynpro application in the Portal. I have configured the SLD according to the documentation and it looks good. I configured a technical system and a JCO Connection there.

When i try to choose a JCO Connection in the Portal (Content Administration -> Web Dynpro), i get the following error below.

When i do not define JCO-Connection within the Technical System, i do not get an error in the portal, but there is (logically) no choice for any application or message server

<b>This is the Error Message</b>

<i>An error has occurred:

"Failed to process the request."

Please contact your system administrator.

-

---

Hide details

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.4012.00.0000.20050509073444.0000 (release=630_VAL_REL, buildtime=2005-05-09:20:05:04[UTC], changelist=346209, host=PWDFM026)

Web Dynpro code generators of DC sap.com/tc_wdtools:

No information available

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:

6.40 patchlevel 92160.313

Java VM:

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

Operating system:

Windows 2003, version: 5.2, architecture: x86

-

---

Error stacktrace:

java.lang.NullPointerException

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

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)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

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

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:775)

at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:359)

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

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

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

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

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)

</i>

[Former Member · Accepted solution]

Hi,

Check whether you have set your SLD port and host in J2ee runtime system.To do this, open visual admin -> SLD data supplier->runtime tab-> HTTP Settings,then set your host name or local host and your http port.

Do restart the server after the changes.

Check your SLD connection by going to http://host:port/sld.

Also check whether you have configured the ABAP system in technical landscape.

Refer the following link for further assistance :

Regards,

Vijith

[Former Member · Accepted solution]

Vijith,

thanks for your reply, but i coukld not solve the problem yet. The connection to the SLD is working fine. One thing, i'm not sure about, is the configuration of an ABAP system in the technical landscape.

I am using a WebAS Java (host netweaver) with no ABAP stack installed and want my Web Dynpro Application running on this system to call a bapi a R/3 4.6c (host ahsap2).

I have defined my Java system as a Web AS Java, and define therein 2 JCO Connections pointing to ahsap2.

And, when i do not define these 2 JCO Connections, i get no Error in the Portal

Beside I defined the R/3 4.6c as a third party system in the Technical Landscape, but i suppose, it is of no relevance in this context.

In the meantime i really tried everything ...

[Former Member · Accepted solution]

Andreas,

Here I am giving you stpes for creating JCO connection.

Please have re-check it with your stpes and hopefully you will resolve your issue

1. Go to Visual Administrator.

2. Navigate to Server>Services>Deploy>select the Application radio button at the

bottom.

3. Make sure the Deployed Component: sap.com/com.sap.lcr has started.

4. Via web browser enter: http://<enter_your_machine_name>:50000/sld

5. Log in as Administrator and enter password (default: sap).

6. Click on the Administration tab > Server Settings.

7. In the field Object Server enter: localhost and press the Set button under the Server

Parameters.

8. Select Administration link.

9. Click on Start Server button. (Starts the system landscape server).

10. Click on the Content > Import.

11. Browse to: C:\usr\sap\C11\SYS\global\sld\model

12. Import cimsap.zip first.

13. Import CR_Content.zip next.

Create separate systems: ABAP WAS

1. Via web browser go to Home>Technical Landscape>Technical System.

2. Leave the default: WEB AS ABAP.

3. Click New Technical System.

4. Select WEB AS ABAP.

5. Click Next.

6. Enter the R/3 system data:

a. System ID: PDC

b. Installation #: <Instalation Number>

c. DB Host Name: <R/3 System name>

7. Click Next.

9. Enter the following data:

a. Message Port: 36<system number> 3600

b. Log on Group: SPACE

c. Instance #: <system number> 00

10. Click Next on the optional settings.

11. Enter Client Number: <client number>

12. Hit Add.

13. Click Next.

14. At the screen to select Available Products select: SAP R/3 4.6B... or what ever is

appropriate.

15. Click Add. (Make sure the components are listed towards the bottom. If they do not

exist, you might need to re-import the content: cimsap.zip.)

16. Click Finish.

17. Now add a new technical landscape. Click New Technical System.

18. Click Finish.

Configure each system to point to local host (telling the engine to use the SLD on the local machine).

In C:\WINNT\system32\drivers\etc\host.cnf file add

<IP address of R/3 system> R/3 system name

In C:\WINNT\system32\drivers\etc\services.cnf file add

SapmsPDC 3600/tcp

1. Go to Visual Administrator.

2. Navigate to C11>Sever>Services>SLD Data Supplier

3. Go to CIM Client Generation Setting tab (at the bottom).

4. Enter the following:

a. Host: localhost

b. Port: 50000

c. User: Administrator

d. Password: default

5. Save

6. Click on CIM Client Test. You should get a prompt.

7. Click OK.

In WebDynpro Content Administration

A. Via web browser enter: http://localhost:50000/webdynpro/welcome

B. Enter logon: Administrator and password: default

C Click the Create JCO Destination

D. Fill in the following data for each of the JCO connections listed.

a. WD_RFC_METADATA_DEST

i. Click Create

ii. Client: <client number>

iii. Hit Next, Next

iv. Select Dictionary Meta Data

v. Hit Next, Next

vi. Enter user ID of the R3 system, password, and confirm password.

User should have the authorization to make RFC calls

vii. Hit Next

viii. Hit Finish.

ix. Click Test Connection.

B. WD_MODELDATA_DEST:

i. Click Create.

ii. Client: <client number>

iii. Hit Next, Next

iv. Leave the radio button as Application Data on this screen

v. Hit Next, Next

vi. Enter userID of the R3 system, password, and confirm

password.

vii. Hit Next

viii. Hit Finish.

ix. Click Test Connection.

Regards,

Hari

[Former Member · Accepted solution]

Hari,

thank you for your detailed message. I'll tryx again with a new installed system

Regards Andreas

[Former Member · Accepted solution]

Yes,

have installed a new system, EP6SPS13. Now i can create JCo-Connections within the portal

By the way: A logical Error in configuring the SLD is, that a 4.6c system must be declared as a technical system of type "Web AS ABAP".

[Former Member · Accepted solution]

Hi Andreas,

I have created the technical system Web As ABAP in SLD but now while creating the JCO connection I am getting the following error,can u please tell why this is happening.The short details are as follows

500 Internal Server Error

Web Dynpro Container/SAP J2EE Engine/6.40

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

java.lang.NullPointerException

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

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)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)

... 45 more

See full exception chain for details.

System Environment

Client

Web Dynpro Client Type HTML Client

User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)

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

Server

Web Dynpro Runtime Vendor: SAP, build ID: 7.0007.20060331081328.0000 (release=645_VAL_REL, buildtime=2006-03-31:06:24:04[UTC], changelist=396896, host=pwdfm101), build date: Mon Apr 23 17:10:46 GMT+05:30 2007

J2EE Engine 7.00 patchlevel

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

Operating system Windows XP, version: 5.1, architecture: x86

Session & Other

Session Locale en_US

Time of Failure Fri Apr 27 17:02:11 GMT+05:30 2007 (Java Time: 1177673531046)

Web Dynpro Code Generation Infos

sap.com/tc_wdtools

No information available null

sap.com/tc_wddispwda

No information available null

sap.com/tc_wdcorecomp

No information available null

Detailed Error Information

Detailed Exception Chain

java.lang.NullPointerException

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

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)

at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)

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

at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:412)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:536)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:705)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:560)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)

at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)

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

at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:690)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:536)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:770)

at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:762)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)

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)

Regards,

Pawan

[Former Member]

Hi

I think you haven't defined the SLD configuration properly. Check the SLD Data Supplier settings in VA.

Enter all the information, regarding your portal.

Then test for SLD.

If u followed the steps of SLD configuration u shud not do error.

i hope it helps

Srikant

[Former Member]

Hello D.V.

thanks for your reply, i also checked the Data Supplier settings, up to now with no effort.

But i just installed NW04 new, i will try to get on with my little problem when the system is up.

Regards Andreas