Jco connections Logical System

Hi All
i have a problem with Jco destinations--the logical systems.
-->For META DATA i have used one userid and for MODELDATA i have used another user id.
-->When accessing the RFC from SAP Webdynpro am using another userid to get connect to R/3 system( at Single Server tab while getting the RFC/ Creating the model class).
-->When i deployed this application i am facing with following  error:
Could not create JCOClientConnection for logical System: PWC_OTR_RFC_MODEL_DATA - Model: class pwc.ca.otr.model.OpenTaskReportModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!
Please give me the best / path to the solution atleast.
regards
Prasad

Hi Varaprasad,
Did you check your JCOs? Whether you are able to test and ping the JCO destination? Ask your basis team to check JCO settings.
Regards,
Gopal

Similar Messages

  • Couldn't create jco client connection for logical system

    Dear Experts,
    we are facing a strange issue in our custom webdynpro java application, few of our portal users are getting the "couldn't create jco client connection for logical system" for Model Data JCO Destination. below are details
    1. portal version 7.02 SP14 (we have recently updated to SP14 from SP02-- is this is causing the issue ?)
         1.1. updated the NWDI track with SP14 SCA files as well as added latest WD Runtime SCA file deployed the applications to Production also.
    2. above said exception is inconsistent and happening for only few users
    3. ping and test of jco destinations are successfull in content administration as well as in SLD, destinations were added in the SLD system.
    4. cleared the JCO ARFC meta data cache in webdynpro console
    5. jco destinations are configured using uid/pwd, configured user is not locked active and tested in the backend by logging in with the same user.
    6. restarted the portal server
    even though, we are getting the above said exception for few of portal users randomly.
    Please help me on this ASAP, as i am not getting any further help on this.
    Thanks,
    Ram.

    Hello Ram,
    Check the JCo Pool Configuration settings of your JCO Destination. This message normally comes when the maximum connections has been reached. Increase the "Maximum Connections" to some number depending on the usage. A good habit is to disconnect the jco connection after executing the same in your webdynpro code if you don't want it to be synchronous.
    <ModelName>.modelInstance().disconnectIfAlive()
    Hope this helps.
    Regards
    Vijay

  • 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

  • Logical System Creation & JCO Connection.................

    Hi,
    I have configured ESS in my portal 6.0 but I am confused with some concepts.
    I have created System in portal System Landscape with alias "SAP_WebDynpro_XSS" . & also i have created JCO Connection SAP_R3_HumanResources (Appln data/Metadata).These are the steps in configuration guide.....
    My backend system is ECC 5.0.
    If i can access my backend for my webdynpro iview through JCO connectiones why i need to create system in portal ????
    Thanks in advance!!!
    Smita.

    Hi,
    All the Standard iviews use this System for calling the JavaWD Application.
    This Java WD Application in turn uses the JCo to communicate with backend to get the application sensitive data to the application and display it.
    Regards,
    <i><b>Raja Sekhar</b></i>

  • Error while trying to creat a RFC_METADATA JCo Connection to R/3 system

    hi,
    i have installed the EP . when i am trying to maintain the JCo connection for RFC_METADATA i am getting an error.
    the error states : "com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=esuides GROUP=PUBLIC R3NAME=ESR MSSERV=sapmsESR PCS=1 ERROR       Group PUBLIC not found TIME        Fri Aug 26 14:46:24 2005 RELEASE     640 COMPONENT   LG VERSION     5 RC          -6 MODULE      lgxx.c LINE        3515 DETAIL      LgIGroup COUNTER     1"
    cna you please tell me how to resolve this error.
    thanks
    -uday

    Hi Uday,
    you have to create a logon Group named PUBLIC with Transaction SMLG in your Backend system. Also don't forget to add the line:
    sapmsXYZ   <port_number on which XYZ listens>/tcp <For ex: 3600>
    to your services file in C:\winNT\system32\drivers\etc (for the Windows 2000 system). XYZ means your Instance Name.
    Regards
    Gregor

  • Error in the logical system (BW - R3 connection)

    Hey guys, i need help, actually i created a connection between BW and R3 system, but i think i wrongly assigned the details to another BW system and now whenever i tried to load the data, it's not being processed.
    And i checked and it shows me that the connecetion is between source system (538) and BW (B3T800), though my BW client is BW (BW TEST). so how do you think i can change my background users i assigned while creating the source systems, because i think, while creating the source system, i used wrong background users. So instead of connecting via logical system (BW test), its connecting via (B3T800) to SAP R3 (538).
    --> Also i tried changing the Logical system name, as i checked and showed that for my BW client now it has a entry of the BW system (B3T800) and when i tried chnging it, it let me change that, but when i went to the RSA1, SAP doesn't let me access that, saying a message "your logical system has been changed", so can i change the logical system, do you guys think my problem will be solved?
    Regards,
    Amit Jaidka

    I have checked in SM37 taking that request number and when i checked the job log , its showing
    5 LUWs confirmed and 5 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    Lock table overflow
    Job cancelled after system exception ERROR_MESSAGE
    what is the reason for this termination in R/3.
    Thanks

  • RSA1 - Source system connection : Change in logical system name

    Dear friends,
    Can you please tell me how can i change the logical system name for a source system connection.
    There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
    Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
    thanks
    ashish

    HI Sunny,
    This is not the same problem, may be similar though..i am not getting a way.
    let me describe u in a bit more details.
    Currently, we have a working source system connection to a system SID_CLT.  there is no change in source system.
    now, can i change this system connection technical name from SID_CLT to SIDCLNT*** .. 
    thanks
    ashish

  • Creating and assigning logical systems foe connecting BW to R/3

    Hello ABAP Pundits,
    I have to connect R/3 (sender) to BW (reciever). So I guess, I need to create logical systems in both BW and R/3.
    So does this mean that I have to create two logical systems on R/3 and two logical systems on B/W ?
    Do I need to do assignement of these newly created logical systems on both R/3 and BW separately ?
    Pleae elaborate...
    Regards,
    Tushar.

    I think the following documents should clear your doubts.
    http://www.sappro.com/downloads/OneClientDistribution.pdf
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    Regards,
    Ravi
    Note - Please mark all the helpful answers

  • How many logical systems are required to connect between one XI and R3 sytm

    Hi Experts,
                   I need to know how many Logical systems we need to create when connecting an SAP XI and SAP R3 system.
    details wht I configured is as follows :
    For XI :  LOGSYSXI assigned to 100 client
    For R3:  LOGSYSR3 assigned to 800 client.
    Do I need to create two log'cal systems on one side?
    How many logical systems can a Client can support simultaneously? is it only one or more that one?
    THANKS IN ADVANCE.
    Sunil K Shetty

    Hi,
    >>>>I need to know how many Logical systems we need to create when connecting an SAP XI and SAP R3 system.
    as you've noticed you only need 2 - one for r3 one for XI
    this is enough
    also shown in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    >>>>How many logical systems can a Client can support simultaneously?
    one per client
    but you can create as much as you wish
    wihtout connecting them to a client
    but use one for XI
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • BI - 2 OLTP with same logical system canu0092t be connected to SAP BI

    Bi 7.0
    SAP ECC 6.0
    I am in a test environment in SAP ECC and SAP BI.
    I have 1 SAP BI and 2 SAP ECC. Both SAP ECC have the same logical system name: 10.
    I could connect the 1st SAP ECC to SAP BI, but I am not able to connect the 2nd SAP ECC because the logical system name is the same than the 1st one.
    Question 1: is there a possibility / way to connect the 2nd SAP ECC without changing the logical system name?
    Question 2: if I am in test environment what is the risk to change the logical name in SAP ECC?
    Regards

    Not solved.

  • JCO connection to SRM system - in Supplier collaboration 2.0 BP

    Hi Friends,
    We have deployed the Supplier Collaboration 2.0 Business Package on SAP Enterprise Portal 7.
    After deployed, we need to configure the JCO to SRM System. We are not configuring for catalog, IHS, et.
    Now, Under the 'Supplier Portal Administration'->'System Integration' Workset, There are 4 iViews which talks about the JCO, Integration to BP.
    1. JCO Client Maintanance
    2. External JCO connection configuration
    3. Application maintenance
    4. System type configuration
    I searched for documentation in tthe sap.help.com, sdn, service.sap.com but nowhere anyone mentioned the step-by-step details.
    Could anyone please let me know how integrate Backend to BP of Supplier Collaboration 2.0 with JCO's using the BP iViews.
    Thanks for your time.
    Thanks,
    Raghavendra Pothula

    Hi all,
    Please advise if any of you managed to resolve your query? Im busy with Supplier Collaboration 4.0 BP u2013 and am completely new to the portal area. Would appreciate any advice? I went through the SAP documentation (http://help.sap.com/saphelp_srm70/helpdata/en/55/c88265d15b4f0f9ee1653bc1146414/content.htm). So I was currently trying to set up RFC users for the systems, but not sure if Im on the right track. Would you be able to advise?
    Thanks,
    Emily

  • JCO  connection getting expired when system restart...

    Hi experts,
               I configured the JCO connection.It worked at first time..when i restart the system...It gives the following error
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message serverhost failed Connect_PM  TYPE=B MSHOST=Hostname GROUP=SPACE R3NAME=D MSSERV=sapmsDEV PCS=1 ERROR       hostname '?' unknown TIME       
    Fri Dec 21 04:25:25 2007 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC -2 COUNTER     1
    I have to configure the jco connection each and every time when restart the system..Please tel me what may be the reason..
    Thanks & Regards
    Mathi

    Hi Mathi,
    Did u add the the sapgw<instance> 3600\tcp in the services file of the path mentioned above.
    If so can you atleast ping the Destinations created by you successfully?
    If everything goes on well then a final option would be tryingto Restart the Server.
    Also to analyse the problems caused by JCO this manual should be helpful for you.
    http://help.sap.com/saphelp_nw04/helpdata/en/f6/daea401675752ae10000000a155106/content.htm
    Regards,
    Nagarajan.

  • Error creation of JCO connection: System Already Exist

    Hi Experts,
    We have created the SLD connection to the ECC6.0 from the Portal 7.0.
    Created one JCO connection using that SLD successfully for the Clinet 100.
    Now we required to create one more JCO Connection for client200 also. But it is giving the Error that
    System Already Exist.
    How can we resolve this. When we create the JCO connection for one client, con't we create one more JCO connection for the same system for the differt client or not?
    If so How do it?
    Regards

    I think you can add one more client in the existing connection. well, I am not sure about that even.
    nikhil

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

  • Retrieving System Name used in JCO connection ?

    Hi All,
    Do you know how to retrive the System Name paramer value used in JCO connection using Web Dynpro programe. If so can you please sen me how.
    I promise to award points for the correct answer.
    Thank you and Regards
    Maruti CR

    Hi Jennifer,
    Thank you for your reply. I am still trying to get the SAP system name for the model used. I trind to your your code but I am getting some compilation errors.
    Bapi_User_Get_Detail_Input iasmodel  = new Bapi_User_Get_Detail_Input();
    The code I used is
    Bapi_User_Get_Detail_Input iasmodel = (Bapi_User_Get_Detail_Input)WDModelFactory.getModelInstance(Bapi_User_Get_Detail_Input.class);
    IWDJCOClientConnection jcoClientConn = (IWDJCOClientConnection)iasmodel.modelInstance();
    I am getting compile errors..
    The type of model represented by class 'com.ias.Bapi_User_Get_Detail_Input' is not compatible for creation by WDModelFactory
    Can you please suggest?
    Thank you and Regards
    Maruti CR

Maybe you are looking for