Problem testing Metadata in JCO connections (Flightlist)

Hello:
I have the sneak preview WAS Server Java 6.4 (J2EE) and I have also installed the MINIWAS 6.2. I have successfully setup the SLD and imported the 2 zip files. I can start SAP, and through SM59 test connect to SLD_NUC. I can use RZ70 to 'send' info. I can successfully load, build, archieve the Flightlist demo. I can go to http://localhost:50000/Webdynepro/welcome... and create and test the Model data under JCO connections (not using load balancing). When I test 'metadata_dest' I get the RFC_error_communication Group Public not found. I tried your fix (services file sapmsBSP 3200 from another post), but this makes it not possible to connect to sap since I think SAP listens on port 3200. Any thoughts? Can I spoof my single server system to think its has load balancing?
Thanks
Russ Wagner
Canada

Hi,
If in SMLG menu "goto->load distribution" the field "current logon instance" is empty run report RSRZLLG0_ACTUAL without the flag FRCE_SAV...
After the run the field should be the name of your instance...
check with:
lgtst -H pc -S sapmsnsp -D 1
the output should be:
list of reachable application servers
[pc_NSP_00] [pc] [192.168.1.6] [sapdp00] [3200] [DIA UPD ENQ BTC SPO ICM ]
list of selectable logon groups with favorites
[SPACE] [192.168.1.6] [3200] [700]
bye
sambarza

Similar Messages

Problems during creation of JCo Connections

Hi everybody,
i've a problem while creating JCo Connections in the Content Administrator of me WebAS.
I can selct the connection i want to maintain, but at the second step, an new window appears and i get the following message. Does anybody have an idea and could help me.
Best regards,
Maik.
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.0), 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.4010.00.0000.20040921144040.0000 (release=630_SP_REL, buildtime=2004-09-21:22:25:54[UTC], changelist=283399, host=PWDFM067)
Web Dynpro code generators of DC sap.com/tcwdtools:
No information available
Web Dynpro code generators of DC sap.com/tcwddispwda:
No information available
Web Dynpro code generators of DC sap.com/tcwdcorecomp:
No information available
J2EE Engine:
6.40 patchlevel 86216.32
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_05-b04, vendor: Sun Microsystems Inc.
Operating system:
Windows 2000, version: 5.0, architecture: x86
Error stacktrace:
java.lang.NullPointerException

Hi Henrik,
I got exactly the same problem has you have with the same version (6.40 SP9). I have opened an OSS message ..
Best regards,
Christian DUCRET (SAP BAsis Team)

Creating MetaData type JCo Connections

Hi SDN,
I am aware that I should use User Method as User/Password.
But which user should I use?
( In SAP Online Help, it is mentioned that, 'Enter a user in the mySAP ERP system for which you have created for the metadata connection.)
How can I proceed with this one?
Initially I used ticket, there were a lot of connection errors.
Thanks,
Vamshi

If you select User/Password, you must define a user and the corresponding password.
This authentication method is used to define JCo destinations for metadata. The user is predefined for authentication method User/Password and cannot be changed. This user is a technical user who does not need dialog authorization. The name and password assigned to this user must be known in the backend. The authorizations for this user must be set in the backend so that this user can access all DDIC function modules.
Please have look at <a href="http://help.sap.com/saphelp_nw04/helpdata/en/3a/3b1b40fcdd8f5ce10000000a155106/frameset.htm">this like</a> for more details.

MetaData Jco Connection without MsgSvr

Hi all!
I have again a problem setting up the Jco Connections for the WebDynpro tutorial. Now, I'm able to create a JcoConnection for the application data, but none for the MetaData, because the IDes, I want to connect to, is not installed with a message server (in that case it really wouldn't make sense, as there is only one app server).
So, please, can anybody tell me, if there is a way to define a MetaData Jco Connection without load balancing?! Or give me a hint, how I can make that tutorial run?
Thx in advance!
Nick

Hi Nicolas,
It is for load balancing purposes that message server is required for the creation of JCO metadata. When large volumes of users are accessing the metadata it becomes necessary that it should be load balanced.
Also using the transaction SMLG you will have to add the message server to the Public logon group. Then only you can create the metadata connection
Also check the services file for the entry sapms<SID> 3600/tcp
Hope this helps you
Regards
Rohit

Problem with JCo Connection Pool

Hi,
I have a problem with using an RFC Model in my WebApplication. So sometimes the access to the function block works, and sometimes it doesn't work. Now I know, that there is a problem with the connection pool. Look at this message:
com.sap.mw.jco.JCO$Exception: (106) JCO_ERROR_RESOURCE: Connection pool WD_X24_MODELDATA_DEST_CPIC_REKTO_DE_useDefinedUser is exhausted. The current pool size limit (max connections) is 10 connections.
So it looks like a problem with closing the JCo Connections after using. Do know where the problem is? Because I'm using many other function blocks with no problems.

Hello,
You need to increase the pool size via Visual Administrator.
Server 0 -> Services -> JCO RFC Connections.
Change the pool size from there. I believe a restart is in order.
Regards,
Jan

Error while obtaining JCO connection when creating JCO connection

Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_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: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 WD_RFC_METADATA_DEST 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
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes Defloo

Hi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi

JCo Connection Performance Tuninng

Hi all,
Here's a performance tuning problem occurs when I do the Stress Test for a JCo Connection.
I call bapi with abap model autogenerated by webdynpro wizard, then I developped a method to do this post job(with same data, suppose each post get the right response) for 1, 10, 20, 50 times.
I found the first time it will cost a real long time(such as 21s) to get return, then performance can be better, an average time cost is about 700 ms.
So I think there must be someplace to cache the post data, if I can modify the size of the cache, maybe I can improve the performance.
Now the question is where is it?
Any idea?

Hallo William,
read the SDN article on <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/how%20to%20configure%20the%20jco%20destination%20settings.pdf">How to configrue the Jco Destination Settings</a>
Regards, Bertram

JCO Connection Errors

Hi Experts,
we have configured the ECC6.0 backend system in to SLD and tested the same, its succesfully running and configured.
next we tried to create the Jco connection(META DATA and MODEL DATA) for the backend system, it was created with out any issues. but whenever going to Test /Ping the JCO connections we got an error.....please find the below error message.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=iginsap1 GROUP=public2 R3NAME=EHT MSSERV=sapmsEHT PCS=1 ERROR       internal error TIME        Mon Jul 18 12:32:52 2011 RELEASE     700 COMPONENT   MS (message handling interface, multithreaded) VERSION     4 RC          -101 COUNTER     5
Note: As per some S-notes, we added the system details in to the Service file and checked the Login group also.
and aso ran below commands at the ECC server
1) niping -v -H iginsap1
2) niping -v -S sapmsEHT
3) telnet iginsap1 sapmsEHT
But still we are getting the same error... please provide the solution as soon as possible..
Regards,
Arjun.

Hi Arjunab,
Have you tried to ping the destination server from the source? Please try to mention the details like below in the source (J2EE Server) host file:
Ip Address of the backend system                FQN                                 hostname
xx.xx.xx.xxx                                       *abcdx.xxxxatxyz.com *            abcd
Hope this will help you.
Regards,
Faisal

Cockpit doesnu0092t work (SAP AII 4.0) - Error in JCO connection

Hi all,
After some days working with the "Cockpit" in AII 4.0, today we can not access to it and we dont know why.
When we execute the transaction /AIN/DTUIURL - Auto-ID Cockpit, we do logon and after that it appears the error:
"Failed to process the request. Please contact your system administrator. Pressing on Show Details, in Error stacktrace we can see the following:
"com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.ain.model.utility.types.Syuname could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection."
In fact, we have the same problem (an error in JCO connection) when IDOCs try to be sent from R3 to AII or vice versa. We can see in transaction sxmb_moni of XI system this error.
Does anybody know where the problem could be?
Thanks in advance,
Xavier

Hi,
Thank you for this question. What you are reporting looks to me like a bug. The channel for such questions is the Service Marketplace http://service.sap.com/. Please post it there.
Best regards,
Steve

JCO Connection test fails taking wrong IP Address

Hi All,
We are configuring JCO Destinations(MODEL & METADATA) for ECC 6.0 system. Our portal is on EP7.0 SP8. Our server i.e.ECC and Portal are in two different networks.
The problem here is, for our ECC system we have two IP Addresses.
1. Internal IP Address (130...*) -- on which our ECC system is configured
2. External IP Address (10...*) -- to access the ECC from outside network.
We are able to connect to ECC system with external IP address from Portal server using SAP GUI. We have configured hosts file entries referring ECC system for external IP.
We have configured the ECC system in SLD and configured the JCO destinations for the same. But, Connection tests to the JCO system are failing (partner not reached) as it is referring to internal IP even though we have configured ECC system for external IP address in portal server.
We are getting the follwoing error for JCO Connection test:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=B MSHOST=sapsys GROUP=ESS R3NAME=SYS MSSERV=sapmsSYS PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '130.7.8.88:sapgw00' not reached TIME Thu Dec 21 10:25:24 2006 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -10 MODULE nixxi.cpp LINE 2764 DETAIL NiPConnect2 SYSTEM CALL connect ERRNO 10061 ERRNO TEXT WSAECONNREFUSED: Connection refused COUNTER 1
Why JCO destinations are trying to connect ECC system using the internal IP address even though we didn't mention it anywhere in our portal server configurations?
Please Suggest
Thanks much in advance.
Cheers...
S..S

Hi
Please try this:
First remove the configured ECC from SLD.
Logon the SAP R/3 (ECC).
Run rz70 (T-code).
Enter the serverIP:port of the EP server in the host.
Enter the sapgw in the service.
Check the option SLDRFC for test and activate the current configuration
Then again add the ECC in your SLD.
And please check the entry in the host file also and try to ping the ECC server from the EP server.
Hope this will help you.
Thanks & regards
Arun Singh

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: 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(AccessController.java:180) 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 testmetadata 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.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) 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(AccessController.java:180) 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: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) 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.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) 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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

ModelData and MetaData Mapping in JCo Connection

Hi all
i tried the example given in webdynpro tutorials(Creating a Web Dynpro Application Accessing ABAP Functions)
but i got dout while creating JCo connection
After clicking "Create" button of WD_FLIGHT_MODELDATA_DEST
two radiobuttons of 1)modeldata 2)metadata are comming
if i select modeldata for both WD_FLIGHT_MODELDATA_DEST, WD_FLIGHT_RFC_METADATA_DEST it is giving test sucess but while running it is giving errror as
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tc.webdynpro.tutorial.model.types.FlightModel:com.sap.tc.webdynpro.tutorial.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException:
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:297)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:753)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
If i select modeldata for WD_FLIGHT_MODELDATA_DEST and metadata for WD_FLIGHT_RFC_METADATA_DEST it is giving testfails
so can u plz solve my problem

Hi,
Create a new JCO(for both Meta Data,Model Data) connection in Content administrator>Webdynpro>Create JCO destination
and Make use of that Jco.Otherwise check the status of your Meta data.ModelData Jco connection in Content administrator>Webdynpro>Maintain Jco destination.
Regards
Nandha

Model and MetaData configarations in JCO Connection

Hi all,
while creating new model i used Load Balance option instead of Single Server.So while creating JCO connection what should be selected for ApplicationData and MetaData radio buttons.The error which i am got aftet deploying and running is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Is this error is because of LoadBalance configarartion while creating JCO for Destinations or at the client num which we gave at the starting step of creating JCO
Regards
Padma N

i got similar problem and this is how i resolved
this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
please make sure user is there in the backend system from which you are getting data
xxxxxxxxxxxxxxxxxxxxxxx
Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

JCO Connection Problem

Hi Experts,
This is not related to Java Web Dynpro directly.
We are encountering strange behavior with respect to JCo Destination.
Up to yesterday we had no problems with JCo. But when we tried to run run a Web Dynpro application, it
was not able to extract data from SAP backend.
On further investigation it was found out that JCo Destination test is failing. Following is the error when we
tried to test JCo Destination:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Client 100 is not available in this system
Backend is working fine with username and password in the client. Connection from ABAP server to
the the problematic ABAP server is also working (SM59). But connection from any Java portal to ABAP
server is not working.
Has anybody encountered this problem?
Best Regards,
Pramod

Hi Promod,
It would be some Username and password issue. If you manage to change them you issue will be resolved. Have a look at the the following useful discussion. It would be helpful for you.
JCO Connection Error
Also have a look at the following Wiki for troubleshooting the RFC Communication problems with Java Connectors.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/ep/troubleshooting%252bsap%252bjava%252bconnector%252b(JCo)
I hope this helps you.
Regards,
Gopal.

Error while testing JCO connections

Hi,
Can anyone please help me with the following error.I am getting this when I'm testing my JCO connection :
RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=cgnsap13 SYSNR=01 GWHOST=cgnsap13 GWSERV=sapgw01 PCS=1 LOCATION SAP-Gateway on host cgnsap13 / sapgw01 ERROR max no of cpic clients exceeded (300)
Thanks and regards,
Lisha

Hi
Please ensure that you have the msgserver entry in your services file. The problem you are getting is because of the message server. you need to have a entry like
sapms<System ID> tcp/3601
Also go to your SAP logon pad and check for groups. and type the sid in the box along with the appserver and then click on generate list. You should get some logon groups. If not you can be sure that your message server is not configured properly. Talk to your SAP Basis person
regards
Ravi

Problem testing Metadata in JCO connections (Flightlist)

Similar Messages

Maybe you are looking for