ESS - JCO Connection and Performance

Hi Forum,
In ESS Package Applications we are not using Applications related to Travel Management and Finance but JCO connections are created for the respective application namely
1. SAP_R3_Travel & SAP_R3_Travel_MetaData
2. SAP_R3_Financials & SAP_R3_Financials_MetaData
I need to know performance impact of these JCO creations which we are not using anyway.
Many Thanks and Regards
Sudhir

Thank you Bala,
Will there be any performance impact - If I disable these unused JCO connection. Basically I need to know creating a JCO connection and keeping it idle - how much memory/pool etc it is going to consume. If it is going to impact then the plan is to identify all unused JCO connection in the complete system and disable it.
Regards
Sudhir

Similar Messages

JCo connection and SLD

Greetings, we have a federated portal which is using JCo connections as part of the MSS/ESS business package. We had a situation where the SLD was down therefore the JCo connections were down. Our question is JCo connection completely dependent on SLD. In other words if SLD is down, will that mean our JCo connection will fail thus an outage.
If this is the case what is the best way to make sure SLD is highly available? Our options are to make SLD highly available or distribute SLD on each system.
Also, what is the performance hit on making SLD distributed on all Portal system if this the route we go?
Thanks in advance!

Hi,
The distributed SLD servers can cause higher administration expense with regard to consistent data. Therefore, we recommend that you consider to use a single SLD server first.
but for large system landscapes that are distributed over different geographic locations, a single SLD server might slow down the performance of involved application systems. In this case, a distributed SLDserver installation can be taken into account.
Samrat

Forums server restting TCP connections and performance numbers

I have a packetsniffer running on my network because I was testing some
issues with the webservice interface when I noticed something strange.
The server accepted a request and started processing it, then after 72
seconds it suddenly closed the connection. My client obviously retried,
and the server immediately closed the connection again. I have attached
the TCP dump summary as "Server connection resets.txt" to this message.
Later on I captured the TCP dump of a server timeout. Or maybe not
really a timeout, but after 630 seconds waiting for a list of all forums
I decided it was enough. The TCP dump summary is attached as "Server
connection timeout.txt". If necessary I have the full dump, but I would
have to sanitize it.
This kill after 630 seconds is the worst case I have seen so far. On
average a call to the webservice API to download the list of all
communities takes approximately 110 seconds until the first response
bytes arrive. A full login cycle (request to forum, request to login
service, request to forum, request to API) consistently takes 17 seconds.
Jochem
Jochem van Dieten
http://jochem.vandieten.net/

I have a packetsniffer running on my network because I was testing some
issues with the webservice interface when I noticed something strange.
The server accepted a request and started processing it, then after 72
seconds it suddenly closed the connection. My client obviously retried,
and the server immediately closed the connection again. I have attached
the TCP dump summary as "Server connection resets.txt" to this message.
Later on I captured the TCP dump of a server timeout. Or maybe not
really a timeout, but after 630 seconds waiting for a list of all forums
I decided it was enough. The TCP dump summary is attached as "Server
connection timeout.txt". If necessary I have the full dump, but I would
have to sanitize it.
This kill after 630 seconds is the worst case I have seen so far. On
average a call to the webservice API to download the list of all
communities takes approximately 110 seconds until the first response
bytes arrive. A full login cycle (request to forum, request to login
service, request to forum, request to API) consistently takes 17 seconds.
Jochem
Jochem van Dieten
http://jochem.vandieten.net/

Tomcat connections and performances

Hy everyone, I have Tomcat 4 running on a Linux server my question is, how many connections can tomcat support simultaniously before it crashes is there a maximum number of conn. to set in its web.xml or server.xml file ?
I'm developing a 3- tiers application :
-DB Oracle
-servlets and javasbeans (for the business logic layer)
-Jsp for the presentation layer
Please reply
Thank you in advance
Fabry

Did you ever find out how many connections tomcat 4 could take before it crashes?
Is it dependant on the system resources available on your computer?

JCO Connection and Changing Parameters

Hi,
I am trying to retrive the content populated in changing parameter using the following code
                 JCoTable titles = function.getChangingParameterList()
                                              .getTable("TITLE_HELP");
                                  numEntries = titles.getNumRows();
I always get numEntries = 0 in one of the application server, but when the same application is deployed on the different server It is returning the number of entries correctly.
Do i need to maintian any configurations on the application server.
Please advice.
Regards,
Chandrashekar.

hi,
In the J2EE Engine the RFC functions are implemented by the JCo RFC Provider service, which is used for processing ABAP to Java requests. A feature is provided for receiving calls from the SAP systems this is done by registering the J2EE Engine as a RFC destination.
The JCo RFC Provider Service processes calls from the SAP systems. It dispatches the calls to a stateless session bean, which is registered in the J2EE Engine naming system. By naming convention the JNDI name used is identical to the name of the SAP function module.
cheers,
jo

Unable to create the JCO connections in webdypro (JAVA) No SLD Connection

HI All,
In webdynpro i am unable to create standard JCo connections. create Jco connections and Maintain Jco COnnections are disabled. when i click any of the standard content of the Jco connections it displays error message No sld check. But SLD is running fine. I have checked in Visual Admin there also SLD supplier is running fine.
But i am unable to create or maintain the Standard content of the JCo Destinations.
Thank You,
Mahesh C

Hi ,
I am having all admin rights. And also i have checked in Check SLD Connection. It showing the error connection to SLD Could not opened successfully. But SLD is running fine and i have checked in Visual admin SLD datasupplier is running fine.
When i check in the log of the SLD there it is showing
#2852 11/18/2008 18:27:18.265 [SAPEngine_Application_Thread[impl:3]_29] FATAL com.sap.lcr.cimsrv.CIMOMServlet: SLD initialization failure, can not set up cluster-wide event notification. Please check your JMS provider for errors.
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Failed to initialize cluster notification. Please check your JNDI service and JMS provider for errors.
Is that i need to change the CIM content?
I could not able to get clue on this.
Thank You,
Mahesh C

JCO Connection

Hi Experts,
We use two types of JCo connections while connecting to back-end .
1 . Modeldata
2 . Metadata
What is the use of each type of JCO connection ?
Thanks a lot .

Hi jain,
I think you have posted some wrong part in your post.
There no two type of JCo Connections; but you can create one JCo connection and specify different parameters to it; one is model data and other is meta data.
model data - shows the default logical system name for model instances that we use in application.
meta data - shows the default logical system name for RFC metadata (Backend R3 meta data).
and both together forms the JCo Connection for the WebDynpro Front-end application.
You can find more idea by login to ContentAdministrator and find your application name and view.
Regards
- Vinod
Edited by: Vinod V on Apr 3, 2008 10:20 AM

How to monitor (Create /Delete )JCo connections

Hi Gurus,
can anyone give me a clear picture of monitoring the Jco connections ,am i want to create the new Jco connection ,and where do i set the max.no connections ..
reward point guaranted
regards,
S.Rajeshkumar

Hi Rajesh
Read,
http://help.sap.com/Business_Packages/EN/ca/115e4088dc0272e10000000a155106/content.htm
regards
Juan

Error while obtaining JCO connection in t-code RSPLAN

Hi Gurus,
I have installed ECC 6.0 SR3 and i have added BI_CONT and updated all the patches. But while trying to access the t-code RSPLAN and after clicking on the START MODELER button it is opening in a browser . after giving the user id and password in the browser , while opening the page it is showing the error " Error while obtaining JCO connection". and how to create jco connections in visual admin.
can anybody please help me in this issue.
Thanks in advance.
Regards,
Babu.

Hi,
when i was trying to open RSPLAN T-Code in BI, i able to open start modeller it says that http://udnubd1:8003/sap/public/myssocntl?sap-client=320 and says that cannot find server. So i request you please can anyone help me onthis issue.
Thanks,
Reddy

Close jco connection

Hi
   Can anyone tell me how to retrieve the existing jco connection and close it. Can we write that code in wdExit.
Thanks
Vidyadhar

Hi,
Following code can be used
AAAAModel thisModel =
                    (AAAAModel) WDModelFactory.getModelInstance(
     AAAAModel.class);
               thisModel.disconnectIfAlive();
You can call this code's method in wdDoExit()

Multilingual JCO connection setup

We want to make our Portal multilingual with the following setup. We have Portal 7.31 installed with following technologies,
- Java web dynpro applications using JCO destinations using user mapping (one hard coded userid/password), language specified in JCO destination is English.
- DynPage HTMLB applications using System landscape connection to SAP using user mapping (one hard coded userid/password). "Master locale" specified in the Landscape object is English
I wanted to change the language attribute in the JCO connection and landscape object so that the RFCs know the language required to send the data back. For JCO connections I can make another french language JCO destination and use that when user switches to french, probably I can do the same thing in case of system landscape object. Is this the right approach?
Would leaving the JCO destination language empty use the Portal user's language preference? Even though I am using a hardcoded userid/password?
Any help and direction appreciated.

hi,
In the J2EE Engine the RFC functions are implemented by the JCo RFC Provider service, which is used for processing ABAP to Java requests. A feature is provided for receiving calls from the SAP systems this is done by registering the J2EE Engine as a RFC destination.
The JCo RFC Provider Service processes calls from the SAP systems. It dispatches the calls to a stateless session bean, which is registered in the J2EE Engine naming system. By naming convention the JNDI name used is identical to the name of the SAP function module.
cheers,
jo

Meta JCo connection issue - cannot have 2 systems for ESS????

I have a finance R/3 system and also an HR R/3 System.
I need to be able to use the FI system for the timesheet ESS screens and the HR system for the others. I have used the iView Application parameter as documented;
(sap-wd-arfc-useSys=SAP_R3_HumanResources:FIN&sap-wd-arfc-useSys=SAP_R3_HumanResources_MetaData:FIN)
The JCo destinations have been configured and do work ....
However the problem is that the meta data jco connection that is used first appears to be cached and is then used going forward for every subsequent screen.
Therefore if I leave the menu screens as they are by default my timesheet screen won't work because the meta connection has been opened to the HR system and therefore the meta and data connections now don't match - even though the parameter has been set as above the configuration is ignored.
I get the following error message
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
Accessing System DE7 is not possible because RFC Metadata was retrieved
using System DH7. Please assure you have configured the RFC Connections
properly. A Server restart may be necessary!
So if I change the menu to use the finance system then the timesheet screen will work but none of the HR screens will work. (same error with the systems reversed)
Is there any way of getting this to behave properly and make sure that the right Jco connection is used. It is very frustrating because the configuration is correct, I just need to be able to force the applications to use the the Jco destination that has been defined for the iView.
Regards
Marina

Hi, I have created new iview for Who's Who and put the below in Application Parameters:
sap-wd-arfc-useSys=SAP_R3_HumanResources:UTL&sap-wdarfc-useSys=SAP_R3_HumanResources_MetaData:UTL&sap-wd-arfc-useSys=WD_MODELDATA_DEST:UTL&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics:UTL&sap-wd-arfc-useSys=SAP_R3_SelfServiceGenerics_MetaData:UTL
The Home Page Framework is working fine. but when clicking on the who's who service the below error is there:
The initial exception that caused the request to fail, was: java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) ... 75 more See full exception chain for details. System Environment Client Web Dynpro Client Type HTML Client User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30) Version null DOM version null Client Type msie7 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.0103.20081111115141.0000 (release=NW701_03_REL, buildtime=2008-12-07:13:19:14[UTC], changelist=51958, host=pwdfm246), build date: Mon Dec 20 02:32:06 CST 2010 J2EE Engine 7.01 PatchLevel 56102. Java VM IBM J9 VM, version:2.3, vendor: IBM Corporation Operating system AIX, version: 6.1, architecture: ppc64 Session & Other Session Locale en_US Time of Failure Wed Feb 09 14:56:21 CST 2011 (Java Time: 1297284981490) Web Dynpro Code Generation Infos sap.com/pb SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwddispwda No information available null sap.com/pb_api SapDictionaryGenerationCore 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:10[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapDictionaryGenerationTemplates 7.0103.20071003090459.0000 (release=701_SP_REL, buildtime=2008-11-05:19:55:16[UTC], changelist=463950, host=PWDFM201.wdf.sap.corp) SapGenerationFrameworkCore 7.0103.20071003090713.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:07[UTC], changelist=463957, host=PWDFM201.wdf.sap.corp) SapIdeWebDynproCheckLayer 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:15[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapMetamodelCommon 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:51[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelCore 7.0103.20071003091208.0000 (release=701_SP_REL, buildtime=2008-11-05:19:48:46[UTC], changelist=463971, host=PWDFM201.wdf.sap.corp) SapMetamodelDictionary 7.0103.20071003090530.0000 (release=701_SP_REL, buildtime=2008-11-05:19:52:58[UTC], changelist=463951, host=PWDFM201.wdf.sap.corp) SapMetamodelWebDynpro 7.0103.20080730170953.0000 (release=701_SP_REL, buildtime=2008-11-05:19:57:29[UTC], changelist=494995, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationCTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) SapWebDynproGenerationCore 7.0103.20080730170941.0000 (release=701_SP_REL, buildtime=2008-11-05:20:00:20[UTC], changelist=494993, host=PWDFM201.wdf.sap.corp) SapWebDynproGenerationTemplates 7.0103.20081105123737.0000 (release=701_SP_REL, buildtime=2008-11-05:20:06:40[UTC], changelist=507414, host=pwdfm201) sap.com/tcwdcorecomp No information available null Detailed Error Information Detailed Exception Chain java.lang.NullPointerException at com.sap.pcuigp.tracking.BTrackingComp.isValuePackSystem(BTrackingComp.java:290) at com.sap.pcuigp.tracking.BTrackingComp.onInit(BTrackingComp.java:206) at com.sap.pcuigp.tracking.wdp.InternalBTrackingComp.onInit(InternalBTrackingComp.java:173) at com.sap.pcuigp.tracking.BTrackingCompInterface.onInit(BTrackingCompInterface.java:115) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface.onInit(InternalBTrackingCompInterface.java:124) at com.sap.pcuigp.tracking.wdp.InternalBTrackingCompInterface$External.onInit(InternalBTrackingCompInterface.java:198) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:219) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:273) at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:198) at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:258) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.FcWiwBusinessLogicComp.onInit(FcWiwBusinessLogicComp.java:217) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicComp.onInit(InternalFcWiwBusinessLogicComp.java:414) at com.sap.xss.hr.wiw.FcWiwBusinessLogicCompInterface.onInit(FcWiwBusinessLogicCompInterface.java:115) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface.onInit(InternalFcWiwBusinessLogicCompInterface.java:298) at com.sap.xss.hr.wiw.wdp.InternalFcWiwBusinessLogicCompInterface$External.onInit(InternalFcWiwBusinessLogicCompInterface.java:358) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891) at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084) at com.sap.xss.hr.wiw.selection.VcWiwSelectionComp.onInit(VcWiwSelectionComp.java:212) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionComp.onInit(InternalVcWiwSelectionComp.java:206) at com.sap.xss.hr.wiw.selection.VcWiwSelectionCompInterface.onInit(VcWiwSelectionCompInterface.java:162) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface.onInit(InternalVcWiwSelectionCompInterface.java:144) at com.sap.xss.hr.wiw.selection.wdp.InternalVcWiwSelectionCompInterface$External.onInit(InternalVcWiwSelectionCompInterface.java:220) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564) at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438) at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196) at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1289) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Unable to create JCO connections for ESS self service

Hello SDN,
I am configuring the ESS for an EP 7.0 and a ECC 6.0(EP and ECC are combined in one instance).
I need to configure some JCO connections at:
http://host:port/webdynpro/dispatcher/sap.com/tcwdtools/Explorer
But i cannot create any JCO connection from there. I filled in all fields that are necessary. But I keep receiving this error messages:
MsgServerName is not defined.
SystemName is not defined.
LogonGroupName is not defined.
Which is strange because I have defined the right message server. The SLD connection to the SLD is working fine. I have upgraded the SLD and the EP java stack to SP 9.0 which is the highest level.
Does anyone know the solution for this problem?
Thanx in advance,
Regards,
Bart

Hi ,
Add logon group Public in the tx smlg then execute tx RZ70 then try to create RFC destination
Regards,
Sreekantha

ModelData and MetaData Mapping in JCo Connection

Hi all
<b>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</b>
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)
<b>If i select modeldata for WD_FLIGHT_MODELDATA_DEST and metadata for WD_FLIGHT_RFC_METADATA_DEST it is giving testfails</b>
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

How to create a model and JCO connection

Hi all,
The Userid and Password given while creating new model at Singleserver/Load balancing tab should be same as the userid and password given while creating JCO connection. i.e in JCO creation while mapping modeldata to Application data and Metadata to metadata we will give some userid and password.
will those 2 userids and passwords should be same.
the error which i am getting is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Regards
Padma N

2 userids and passwords need not be same
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
xxxxxxxxxxxxxxxxxxxxx
Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

ESS - JCO Connection and Performance

Similar Messages

Maybe you are looking for