JCO Connection issue

Dear All,
I have created WebDynpro  application by importing track.
When I deploy the application, it say,
Deployment completed with warning.
The warning is "Clusterwide exception: Failed to prepare application".
Here I guess I need to find out which JCO connection is getting used and to which backend system it is pointing to.
Could you please tell me where to look for to find out the JCO connection for the application.
I am not creating new connection for the application, need to use the already created one.
Thanks and regards,
Pradnya Ghalsasi

Hello Pradnya,
to see what JCO connection you are using
Go to Contant Admin Role
click on  Weddynpro Contant there you can see Create Jcos and Maintan Jcos ,
click on maintain Jcos
check weather you have WD_METADATA and WD_MODELDATA , if not create one and use it.
i think you know how to create JCos
Points if helpful
Please Close thread if problem solved
Thanksyou,
Regards
Vijai

Similar Messages

  • 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)

  • JCO connection issue with MetaData

    Hi all,
    I have created Jco connection...and while creating them i have used SSO method for creating application data and user/id method for Metadata...it works fine now...but my concerns is with MetaData.
    I have used user/id of an employee who is a user in r3...no whenever this user gets locked for some or the other reason ....all the ess user face a problem in accessing user specific data...
    can i use user/id of a user who is not an employee but has SAP_ALL for creating MetaData Jco...will this workout or is it a complusion that the user must be an employee in r3 ????
    If this is not possible than what is the way out to resolve this???
    Awaiting response...
    Thanks & Regards,
    JJ

    generally we use SAPJSF user as and set this user as communication users that means SAPJSF can't enter R/3 backend system unless it's a Dialog user.
    also you can assign SAP_ALL profile to the user
    Vijay
    Edited by: Vijay Mohan on Oct 27, 2008 12:55 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.

  • JCO Connection User

    Hi gurus,
    I'd like to ask you what kind of user you use for connection in JCO connections. For our test system I used my own user but in live system a stable user must be used?
    Any ideas?
    Tolga

    Hi Tolga,
    You can have the JCO connection user having only the following authorizations from the S_DDIC_MDI profile.
    But i do not think there should be any issue if you have the JCO connection user having the SAP_ALL also. As this is the main connector user between the system.
    Thanks & regards
    Arun

  • What is the best Practice JCO Connection Settings for DC  Project

    When multiple users are using the system data is missing from Web Dynpro Screens.  This seems to be due to running out of connections to pull data.
    I have a WebDynpro Project based on component development using DC's.  I have one main DC which uses other DC's as Lookup Windows.  All DC's have their Own Apps.  Also inside the main DC screen, the data is populated from multiple function modules.
    There are about 7 lookup DC Apps accessed by the user
    I have created JCO destinations with following settigns
    Max Pool Size 20
    Max Number of Connections 200
    Before I moved to DC project it was regular Web Dynpro Project with one Application and all lookup windows were inside the same Project.  I never had the issue with the same settings.
    Now may be becuase of DC usage and increase in applications I am running out of connections.
    Has any one faced the problem.  Can anyone suggest the best practice of how to size JCO connections.
    It does not make any sense that just with 15-20 concurrent users I am seeing this issue.
    All lookup components are destroyed after its use and is created manually as needed.  What else can I do to manage connections
    Any advise is greatly appreciated.
    Thanks

    Hi Ravi,
    Try to go through this Blog its very helpful.
    [Web Dynpro Best Practices: How to Configure the JCo Destination Settings|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417600)ID2054522350DB01207252403570931395End?blog=/pub/wlg/1216]
    Hope It will help.
    Regards
    Jeetendra

  • JCO connection error:Couldn't create JCOClientConnection for logical System

    Hi All,
    We are facing a production outage issue.
      We have a Federated Portal Network setup where one of our producer goes down automatically (seems on heavy load).
      On this Producer server we have 3 Web Dynpro applications deployed and default trace is full with JCO connection error   saying Could   not create JCOClientConnection for logical System: CSVMR_WD_MODELDATA_DEST.
    We had issue with max allowed JCO connections so we changed the below mentioned parameters for JCO connection settings in portal:
    u2022     Minimum value of JCo Pool Size in total = 80
    u2022     Minimum value for CPIC_MAX_CONV per SAP Web AS = 320
    u2022     Maximum Number JCo Connections = 160
    Please let us know if we are missing on some settings, any help in this regard is appreciated.
    Regards,
    Priyanka

    Hi,
    As you have already increased the maximum number of connections/pool size but still you are facing this problem. I would suggest you to check the web dynpro application which might not be able to release/disconnect the JCO connection.
    Please check this [Thread|How to close a model object connection for Adaptive RFC?; for more details.
    Regards
    Puneet

  • Setting up web Bex in BWsystem:error com.sap.mw.jco.JCO$Exception:Issuer of

    Dear SAP Gurus,
    I'm facing an error when seting up web Bex in BW system which is based on AS java patch 14 when i run Diagnostics & Support Desk Tool as described in Note 937697  there is only one red signal which is BI Mastersystem
    the error is
    RFC connection using properties in Portal System Landscape to ABAP backend has failed. Reason:
    com.sap.mw.jco.JCO$Exception:Issuer of SSO ticket is not authorized
    thanks in advance
    Rgds
    George Varghese

    thanks Deepika ,unfortunately I posted this a Long back ,time limit was very less ,we were not in a situation to do more R&D on that,it will be a Waste of time ,what I did is that I uninstall ed SAP and installed again with latest available Patches and we were succeed
    thanks
    George Varghese

  • JCO Connection close

    Hi  All,
    I wanted to know is the connection to close the JCO should be handled in the program or the system will handle since I am using the JCO connection handled by content admin with JCo Pool Configuration.
    <b>I am seeing in SAP backend all the sessions are still open.</b>
    Thanks,
    Rakesh

    Valery,
    We are having an issue wherein the JCo connections are still listed in AL08 output long after the applications are closed. We do call disconnectIfAlive method after executing the Adapative RFC calls.
    Do let me know if there is anyway we can force webdynpro to release connections to the backend or is there any timeout setting in R3 that has to be configured so these connections dont stay open for indefinite time.
    Thanks in advance !

  • JCO Connection giving error when try to edit or preview it.

    Hi,
    We have in our project PD6(Portal) only java stack & CD1(ECC6.0) system is acting as respective backend.
    The JCO connection has already been configured for it,but when I try to edit or preview one of the JCO connection it is giving below error.
    Error :
    500   Internal Server Error
    Failed to process request. Please contact your system administrator.
    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:991)
        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:285)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
        at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
        ... 45 more
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         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:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:251)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:158)
         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:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         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:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:881)
         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:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         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)
    Please let us know your input on this.
    Regards
    Nilesh

    Likely Cause would be some fields for the backend system used to setup the JCO destination are not updated properly (i.e.
    empty) in SLD. Once you have configured your SLD please also ensure that you have selected the relevant u201CMessage Server Connectionu201D. The Message Server, System Name and Logon Group must not be left empty. Ensure that SLD contains up-to-date and complete information about backend systems.
    Check that the SLD is setup properly, check whether you have registered the system through config tool into SLD If not please register system into SLD so that all the parameters are transfered to SLD automatically. You need to do this even the u201CTest Connectionu201D to SLD is successful. Once you are registered you should be able to create the JCO destinations with out any issue.
    Thank you.
    Shyam

  • 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

  • Maintain JCO Destination Issue

    Hi ,
    I have configured SLD and maintained JCO destination WD_MODELDATA_DEST and WD_MODELDATA_DEST with SAP backend connection details.
    When i tried to create the JCO desitnation , i m getting the following issues:
    JCo destination 'RFC_MODEL' was successfully created in SLD.
    Exception while getting JCo Clients Failed to get list of defined JCO clients for deployable object 'sap.com/cafeugpcroomwd'.
    Exception while getting the JCo clients Failed to get list of defined JCO clients for deployable object 'sap.com/cafeugpcroomwd'.
    Exception while getting the JCo clients Failed to get list of defined JCO clients for deployable object 'sap.com/cafeueruico~km'.
    Exception while getting JCo Clients Failed to get list of defined JCO clients for deployable object 'sap.com/cafeugpcroomwd'.
    when i try to test the connection, i m having the following issue.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=op60vimt75 GROUP=SPACE R3NAME=T75 MSSERV=sapmsT75 PCS=1 ERROR       service 'sapmsT75' unknown TIME        Sat Apr 17 03:32:23 2010 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      nixxhsl.cpp LINE        776 DETAIL      NiHsLGetServNo: service name cached as unknown COUNTER     1
    Can somebody help me out what went wrong or let me know changes i have to do ?
    your help is appreciated!!!
    Regards,
    Ravi.
    Edited by: ravikanth kasim on Apr 17, 2010 9:45 AM

    Hi Ravi,
    Please refer to below document for jco errors
    [Troubleshooting SAP Java Connector |http://wiki.sdn.sap.com/wiki/display/EP/TroubleshootingSAPJavaConnector(JCo)]
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0?quicklink=index&overridelayout=true
    Creating JCO Connectivity from J2EE to SAP
    Hope it helps
    Regards
    Arun

  • Reg. JCo Connection

    Hi,
    I am trying to establish JCO from my system.
    There are certain issues that I am not able to resolve/fix.
    1. I am not getting any values in the table that populates all available JCo Destination details.
    2. I am trying to create a new JCo destination. It throws an exception after the step where I select Data Type as Application Data (the Data Type step).
             The exception is as below.
      [code]java.lang.StringIndexOutOfBoundsException: String index out of range: -1
         at java.lang.String.substring(String.java:1444)
         at com.sap.tc.webdynpro.tools.sld.MessageServerConnectionDefinition.updateSelection(MessageServerConnectionDefinition.java:300)
         at com.sap.tc.webdynpro.tools.sld.MessageServerConnectionDefinition.wdDoInit(MessageServerConnectionDefinition.java:168)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalMessageServerConnectionDefinition.wdDoInit(InternalMessageServerConnectionDefinition.java:830)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:71)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:197)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:250)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:182)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:529)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:387)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:609)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:262)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:710)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:339)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:538)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:49)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:239)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:130)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:92)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:42)
         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:373)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:250)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:319)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:297)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:696)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:221)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:146)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
    [/code]
    In the SLD parameter settings, I have defined a BC Message Server and all Server parameters.
    Please guide me to find out whats wrong with this?
    DONT WORRY ABOUT POINTS, I AM AWARE OF THAT..
    Regards
    Ashutosh

    hi
      Well looks like a problem with your Message Server config. Have you configured your SLD. Ensure that you have a entry in your services file which can be found in
    c:\winnt\system32\etc\drivers\services
    There should be a entry like
    sapms<DEV>    tcp/3601
    now DEV is the 3 letter System ID
    and 36 + instance number is your message server port.
    Have you loaded the CIM models into your SLD?. If not that also needs to be done.
    In your SLD ensure that you have created a WebAS ABAP System.
    Then in your Visual Administrator --> Server --> services ---> SLD DATA Supplier
    ensure you have maintained the details to connect to the SLD. Also here you can grant permissions for your WebDynpro Content admin.
    After the above steps try creating a JCO connection. That should help you.
    Let me know if you still face some problem.
    regards
    Ravi

  • 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

  • Execute BAPI Using Current User ID, Not JCo Connection User ID (v7.0)

    Currently when I call a BAPI, it executes under the username of the JCo Connection. User management is done via ECC, and not portal, so the User IDu2019s are identical.
    Is it possible to call a BAPI from Web Dynpro using the current portal user User ID?

    Hi,
        Select the model which is created for the Bapi (in the webdynpro content Administrator),  edit the JCO connection(modeldata) and select user method - Ticket, for the metadata you ca use a common communication userid.
    By this the BAPI is executed with the current logged in portal userid.
    Note:  For using this your portal as to be configured with SAP ECC with SSO.
    Hope this solves your issue.
    Regards,
    Manjunath

Maybe you are looking for