Problem creating aJCO Connection in Web Dynpro Content Admin

[Former Member]

Hi everybody,

I am trying to get the Web DynPro Tutorial #4 (FlightList) running on my machine. Now I have encountered a problem: When I try to create the JCO Connections in Web Dynpro Content Administrator and select the "Message Server Connection" I get the following exception:

Web Dynpro product information:

Product: null, Vendor: SAP AG, Version: null, Build ID: 6.3003.00.0000.20031125134518.0000, Build Date: Fri Jan 23 12:05:52 CET 2004

-

---

Error stacktrace:

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

at java.util.ArrayList.RangeCheck(ArrayList.java:507)

at java.util.ArrayList.get(ArrayList.java:324)

at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.getElement(Node.java:1832)

at com.sap.tc.webdynpro.progmodel.context.Node$MappedElementList.getElement(Node.java:2177)

at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:568)

at com.sap.tc.webdynpro.progmodel.context.Node.setLeadSelection(Node.java:684)

at com.sap.tc.webdynpro.tools.sld.MessageServerConnectionDefinition.wdDoInit(MessageServerConnectionDefinition.java:139)

at com.sap.tc.webdynpro.tools.sld.wdp.InternalMessageServerConnectionDefinition.wdDoInit(InternalMessageServerConnectionDefinition.java:835)

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:236)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:137)

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

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

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

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

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:301)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:682)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:220)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:94)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:142)

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

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

When I select the "Application Server Connection" I cannot select anything as the listbox is empty.

Testing of SLD-Connection etc. went well.

Any ideas?

Thanks, in advance!

Josef

[Former Member]

Hi Franz,

this is a bug in the WD content admin and will be fixed in future releases. Please have a look at this topic:

Hope that helps.

Regards

Stefan

[Former Member]

Hi Stefan,

thanks a lot. Just editing the BC Message Server Caption to something like "NW4 works now" resolved the problem.

I was surprised that the BC Message Server (and other classes) were completely empty. Did I miss a step during setup to import values into this classes or is this a manual step to fill in the values here?

Thanks again!

Josef

[Former Member]

Hi Franz,

the J2EE engine is able to transfer lots of data to the SLD via the "SLD Data Supplier" service. The transfer can be triggered in the Visual Administrator.

AFAIK the "BC message server" is not transferred by a J2EE engine, maybe there is a possibility to do this from a WAS ABAP engine.

Best regards

Stefan

PS: To be more precise, the data transfer is triggered automatically and periodically, you don't have to do this manually, if the supplier is configured correctly.

Message was "enhanced" by: Stefan Klensch