Web dynpro sld / jco setup

i have an erp system installed. on my local computer i installed the netweaver developer studio. i build the flights example from sap. after building and running the application an error occures:
The initial exception that caused the request to fail, was:
   com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:467)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:233)
    at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:218)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:129)
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150)
so, i want to configure the jco. but on the page where i can do it, it says that my sld could not be open. in the visual administrator i set the http settings. and i tried to open the sld in browser, but it says that i have no authority for this.
but i logged in with the j2ee admin, which i gave the sap_sld_administrator rights too.
do you know what went wrong?

Hi Marcus,
If you are using UID/PWD mapping for JCO destination please check wether you have provided correct uname and password.
If you are using SSO instead of UID/PWD mapping then check wether SSO is working properly between portal and ECC.
Mostly this problem is due to authorization failures during the logon phase.
Please check if the SAP user-id & password you are using to connect to the SAP system are correct.
Get the logon data from the JAVA application or JCo trace
for the error description visit,
Have a look at the solution provided in the below threads :
1>Re: com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Incomplete log
2>JCO Error
Hope this helps you.
Saleem Mohammad.

Similar Messages

  • Web Dynpro SLD - No Visual Admin for CE 7.1

    I used NWA to configure an SLD, able to ping, Collect and Send, etc. - all is good.
    But when I go into Content Administrator for Web Dynpro the SLD is undefined.  How do I set it if there's no VA?

    Never mind .... SLD_Client .....

  • JCO , Web Dynpro & SLD connection

    Can anyone please let us know why do we need JCO, WebDynpro  and SLD configuration.  I trying to configuring EP/BI and EP/ERP (MSS/ESS) using SAP configuration guide but not sure what they are used for.
    is JCO/SLD/Web Dypro is the requirement for EP/BI & EP/ERP configuration.
    Thank you everybody

    The SAP Java Connector (SAP JCo) allows a Java application to communicate with any SAP System.
    It provides the bridge to fetch data across stacks and from different r/3 destinations.
    check the following Link:
    /message/1648513#1648513 [original link is broken] ...
    Check out the following.
    what is sld:
    configuring SLD:
    /message/1648513#1648513 [original link is broken]
    creation of themes:
    EP Themes
    All the Best
    Do reward the points

  • All Web Dynpros are down... I really need help.

    Hi. I really need help because our portal has serious problems since yesterday. All of them seem to be related to missing Jar files.
    After installing several SCA files using SDM (Software Deployment Manager) yesterday, all Web Dynpros stopped working (even SAP Dynpros such as User Management).
    I've been looking for solutions all day and can't find anything. Any help would be greatly appreciated. Here are the errors I get:
    All homemode Dynpros show the following error:
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:168)
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:178)
        at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
        at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
        at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:437)
        ... 61 more
    For SAP's Dynpros, I get the following error:
       java.lang.NoSuchMethodError: com.sap.portal.activitydatacollector.ICollectorHook.isActive()Z
        at com.sap.portal.activityreport.ActivityReportHookInterface.updateADCAfterInteraction(ActivityReportHookInterface.java:176)
        at com.sap.portal.activityreport.ActivityReportHookInterface.onAfterInteraction(ActivityReportHookInterface.java:145)
        at com.sap.portal.activityreport.wdp.InternalActivityReportHookInterface.onAfterInteraction(InternalActivityReportHookInterface.java:128)
        at com.sap.portal.activityreport.wdp.InternalActivityReportHookInterface$External.onAfterInteraction(InternalActivityReportHookInterface.java:167)
        at com.sap.portal.pb.hook.PortalHooksManager.updateHooks(PortalHooksManager.java:58)
        ... 34 more

    I do have access to it.
    Here are two examples of errors/warnings we got a lot during the upgrade:
    Caused by: com.sap.engine.frame.core.locking.LockException: Cannot lock [2010112417061085000000portail......................3814850, DEPLOY_LOCK_AREA, sap.com/com.sap.lcr, X]; it is in use by the same owner. In case of lock mode "R" the lock propagation failed, because the optimistic lock is gone.
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Already started operation with application sap.com/com.sap.lcr in the cluster. No other operation with this application is allowed at the moment..
    Another thing that could help you understand my problem: when I log into Portal and go to Content Admin / Web Dynpro / Main JCO destinations, even if my destination's status is set to OK (green light), I get this Java error if I click on "test":
        at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection (SystemLandscapeFactory.java:150)
        at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.getJCOClientConnection(WDSystemLandscape.java:30)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.onActionTestConnection(JCOConnectionsDetails.java:226)
        at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdInvokeEventHandler(InternalJCOConnectionsDetails.java:303)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        ... 28 more
    Thanks again.
    Edited by: Mathieu St-Gelais on Nov 29, 2010 3:13 PM

  • Settings SLD and JCO connection for Java Web Dynpro

    Hi BI Gurus,
    I'm a Business Intelligence newbye and I'm a bit confused about Web Dynpro configurations.
    I try to execute, through Netweaver Developer Studio 7, a simple java Web Dynpro who call the standard Flight List BAPI.
    My configuration is: NW 2004s installed on BI server (with java instance and j2EE Server) and Flight List BAPI stored on R/3 ECC. 5 System in another server.
    Now, my doubt are:
    1) in SLD Data Supplier (J2EE Visual Admin on BI Server) CIM configuration, what are the connections parameter necessary?The BI host or R/3 host?
    2)if I set BW system parameters in SLD and in NWDS when I try to run my simple web dynpro an error occour This is the output:
    The initial exception that caused the request to fail, was:
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'WD_FLIGHTLIST_RFC_METADATA_DEST' in the SLD. No such JCO destination is defined in the SLD.
    Correction Hints
    Accessing the System Landsape Directory (SLD) failed. Depending on the concrete reason (see root cause) check the following:
    is the SLD Supplier in the J2EE engine configured correctly? See the SLD documentation for more details about the SLD and about how to configure it.
    are all JCO destinations maintained correctly? Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
    Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
    Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
    3)where can I create new JCO connections?What are the requirements settings?
    I am always available for answers about the post!!
    Help me please!!
    Thanks thousand and sorry for my incorrect english!!

    You can Create the JCo destination from Content Administrator. You must login as Administrator.
    use the link as
    http://<server>:<port>/webdynpro/welcome/Welcome.jsp, select Content Administator->Create JCo Destinations/Maintain JCo Destinations.
    Please have a look on the following links regarding creating/maintaining JCo destinations. The are usally asked questions regarding JCo destinations.
    Create JCo destinations:
    /message/4947478#4947478 [original link is broken]
    Creating JCO Destinations
    /message/5369333#5369333 [original link is broken]

  • JCO Connection for web-dynpro tutorials (EP 6.0 SP9 downlaod from SDN)

    I have a question regarding JCO connections for web-dynpro example/tutorials. I have installed WAS 6.40 sneak preview from EP 6.0 SP9 download from SDN. Installation instruction says: Choose "No SLD available"
    but the web-dynpro example/tutorial asks to create JCO connections by going to web-dynpro -> content admin..etc on http:<host>:50000..Here, all the tabs relating to creating JCO connections appear to be "protected" on my screen. so I can't do anything further. By going to http:<host>:50000/sld, I also tried to add SLD server..but that is not helping. There is some "import" button, but which CIM file (in which folder etc) am i supposed to import for a simple test system? What are the steps for a bare minimum setup so that I can use the WAS 6.20 system at work-place as my backend & try out the web-dynpro examples? Do I really need SLD setup? Where is documentation about all this after one installs the WAS 6.40 JAva? I was expecting it somewhere at least in the eclipse IDE help-documentation..None of the web-dynpro tutorials explain this !

    Thanks everybody.
    NagaKishore, after doing all the steps, when I goto
    localhost:50000-> web dynpro -> content administartor, and try to "maintain JCO Destinations" I am getting this error: (full stack trace not included)
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Error stacktrace:
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:485)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:438)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:634)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:598)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:120)
         at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:238)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

  • Creation of JCO Destinations for web dynpro

    Hi all,
    I read quite a lot of post concerning the subject but unfortunately I did not found a solution to my problem.
    My goal is to create JCO Destinations to make my web dynpro to connect to an R3 system.
    In order to realise this I followed these steps :
    - Launch visual admin and set http settings, rfc settings, and cim client settings. I click on CIM client test and the result is a success so I assume this part is correct.
    - In R3, I execute transaction smgw, go to remote gateway to get the gateway settings. I execute RZ70 and filled the parameters just checked. Then I activate and launch the data collect. I have no error message and everythings seemed to work fine.
    - In the sld (<host>:<port>/sld) I configured my server settings, the I go to data bridge, set update local sld to true and fill RFC gateway info with the same values as in my R3 system. Then I restarted the sld.
    - Finally I went to Web Dynpro content administrator to create my destinations and there I failed. After entering all settings (the message server appears in my technical landscape in SLD), when I click on finish I've got the following exception :
    Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:140) at
    (SystemLandscapeFactory.java:286) at
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish
    (ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:252) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:641) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) 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:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more[/code]
    I tried to create a generic destination (no for the web dynpro tutorial) and failed again.
    I do not undestand what I did wrong.
    Does someone have an idea ?
    Thanks for reading this !
    Message was edited by: Sylvain

    This thread helped me too because before reading it I didn't thought that I had to create a logon group "PUBLIC".
    Anyway I succed in creating 'WD_FLIGHTLIST_MODELDATA_DEST' and the test is ok. The problem was that in sld / technical system / web as abap, my Central Application Server host was wrong. It is not possible to change it so I just add a secondary server with the right host and select this one when creating the destination.
    The only pb remaining is now 'WD_FLIGHTLIST_RFC_METADATA_DEST'. I think the pb is my message server such this is the only difference between the two destinations
    Thanks for your help
    Message was edited by: Sylvain

  • Problem in connecting JCO destination in web dynpro

    HI all,
    I was installed sneak preview of Net weaver 6.4,
    I want to do some web dynpro (java) programs which connect to back end systems.(R/3 system).
    The R/3 system which I want to connect is at remote place, i have connectivity to that R/3 system using VPN connectivity. With this I am not having any problem. Since I am able to connect using User name and password, and able to do some transactions like RZ70, etc.
    I developed an application which calls COMPANY_CODE_GET_LIST (BAPI function).
    for the above requirement what I did was
    (1)I created SLD setting.
    (a)Web as Java (I am not having any problem to
    Create this.
    (b) Web as ABAP.
    When i am trying to create
    This, there are some steps like i need to go to SAP log in and I need to run the transaction RZ70. For this i need to create an enter in visual administrator>JCO RFC Provider>runtime-->Bundles i need to create an entry for RFC destination as well as Repository.
    under RFC destination there are some fields which i need to enter those are (a)Program ID as mySLD (b) Gateway Host as (c)Gateway service as sapgw00 (d)Number of processes as 1
    Under Repository (a) Application server host (b)system number as 00 (c)Client number as 100 (d)Language as en (e)user as ABCD (f)password as 1234
    I haven't choused the check boxes Local bundle and Unicode and pressed the set button. So like this i created the RFC destinations. under the properties tab there is a property called RFC_DEFAULT_DESTINATION by default it was false so i made it as true. .
    I also went to SLD Data Supplier,under Runtime tab , HTTP Settings , I mentioned
    (a)Host: pava-vis75
    (b) Port: 50000
    (c) user: administrator
    (d) password: abcd1234
    RFC Settings, I mentioned as
    (a)Gateway Host: (which is SAP R/3 system)
    (b)Gateway Service/Host: sapgw00
    CIM Client Generation settings, as
    (a)Host: pava-vis75
    (b)Port (http/https):50000
    (c) user: administrator
    (d) Password : abcd1234
    I tested the CIMClient Test by click the the button. I got the successful message.
    Then I came back to HTTP settings and clicked the button with tilted arrow mark [This triggers data transfer to system landscape directory], for this also I got a successfully message.[data transferred successfully]
    Next I been to SAPLOGON and went to RFC Destinations by using sm59 transaction. There under TCP/IP connections i been to SLD_NUC , opened this by double clicking that and under Technical settings for Program ID I had given the ID which I created at visual administrator [JCO RFC Provider] which is mySLD , under gateway options for Gateway Host as Gateway service as sapgw00 then i tested the connection, it was also successfully.
    Then I opened the SLDAPICUST and i created a new entry for maintaining the SLD Access Data by giving some couple of entries as
    (a)Alias: vissldtest
    (b)Host Name: pava-vis75
    (c)Port: 50000
    (d) user: administrator
    (e) password: abcd1234
    Then saved it.
    Next I created sapmsUV0 3600/tcp entry at
    WINDOWS\system32\drivers\etc\services file, and also there are some required entries which are already existing those are sapgw00 3300/tcp to sapgw99 3399/tcp , another entry starts from sapdp00s 4700/tcp to sapdp99s 4799/tcp , next entry starts from sapgw00s 4800/tcp to sapgw99s 4899/tcp and sapmsJ2E 3601/tcp .
    I restarted the system, as well as server.
    Now my problem is when I was trying to create JCO destination at web dynpro content administrator. For that I navigated as “create JCO Destination &#61664;Deployed Content&#61664;local-&#61664;local/CompanyCodeGetList-&#61664;Applications&#61664; CompanyCodeGetList
    I Choosed the JCO Connections tab-&#61664; there are 2 entries those are
    So I started creating connection for COMPANY_CODE_RFC_METADATA.
    First one is
    General data Name : COMPANY_CODE_RFC_METADATA
    Client : 100
    I didn’t changed any default JCo pool configuration.
    J2EE Cluster
    There is a check box called “Use Local J2EE engine J2E on pava-vis75’ so I choosed that.
    Connection Type
    Dictionary Meta Data and application Data
    I choosed the first one.
    Msg. Server Connection
    After these, I tried to test the connection by clicking the ‘Test Connection.
    It is saying the error as
    First time
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service 'sapmsUVO' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
    second time
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=v011 GROUP=DEFAULT R3NAME=UV0 MSSERV=sapmsUV0 PCS=1 ERROR service '?' unknown TIME Fri Jul 01 07:20:41 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 1
    Can any body please help me to solve this problem.
    From past 1 week on wards I have been trying to resolve this. But in vain.

    It does not necessarily mean that you have to change that parameter. I read that blog as I had a similar problem, and after reading it and understanding the reasons and possible causes for the error, I found that my particular problem was that I was using "PUBLIC" as the logon group in my JCO destinations, but such a group does NOT exist at my backend. I went to transaction SMLG, had a look at Logon Groups, noted that there were none other than SPACE, figured out that I had to include that information in SLD (Web AS ABAP tech. system --> Message Server --> Logon Groups), put it there. Voilá. It works.
    Edit: That SPACE logon group is the one I had to use at JCO destinations. Sorry I forgot to mention that one...
    Message was edited by: Jesus Cil

  • No connection to SLD from Web Dynpro COntent Administrator

    Hi guys!
    I need to set up JCO connections to systems in Web Dynpro Admin, but I have no connection to SLD...  What is needed to set up?
    One more info: SLD has already imported CR content and is in status RUNNING..
    Thanx a lot!

    Pls try the link below..
    Hope this helps.
    [Reward points if useful]

  • ERP2004: ESS JCO session handling in Web Dynpro apps?

    we run ESS/MSS Web Dynpro scenarios, running on WAS 6.40, SP12 in
    Enterprise Portal EP6 SP2 Patch 32. Our go live will be with > 1000 ESS users.
    1. When will the sessions in R/3 backend system be terminated by the
    Web Dynpro Application?
    How is the session handling in FPM (Floor Plan Manager) implemented?
    2. Are there any recommendations regarding the JCO connection settings
    in Web Dynpro Content Administrator (Maximum Pool Size, Maximum Connections,
    Connection Timeout, Maximum Wait Time) to reduce / optimize the load for the
    backend system? I found a documentation in SDN but it is not
    specific for ESS / MSS based on Web Dynpro.
    Background of questions above: The customer is worry about the load on
    SAP R/3 backend side: too much current users in the R/3 backend system,
    possibly bad performance etc. because the JCO sessions are open a long time.
    Are there any experiences with customers running productive ESS / MSS scenarios
    based on Web Dynpro?
    Thanks & Best regards,

    1. For best practices on JCO settings follow the tutorial below and do it accordingly for your no of users. YOu might have to do some trial and error procedure.
    2. For standards, security settings, cache management etc, SAP will give a TODO list after a remote audit of your project.
    Sukanta Rudra

  • SLD info not updated in Web Dynpro Content Admin of NW CE 7.1 EHP1

    Hello Everyone,
    I have installed the CE 7.1 on my PC and am having this problem. I have created the destinations SLD_DataSupplier and SLD_Guest in NWA and uploaded using SLD Data Supplier service. The Java WAS is now reflected in the SLD as a TS and a Datasupplier. I have also performed all the SLD Initilization and config. However the SLD is still not reflected in the Web Dynpro content admin. When I press the Check SLD Connection button all the values are blank.
    Am I missing anything, Should I be doing any config in the Configtool? Any help is appreciated. Thanks in advance.

    Hi Satish Varma Vegesna.
    Check this link.

  • Strange JCO error when running Web Dynpro App

    I am developing a new WebDynpro application to be deployed on our SAP
    Portal interfacing with a SAP R/3 backend. The application uses
    multiple JCo destinations (two for each model) all of which were
    configured according the SAP guides (userid/password for metadata and
    ticket for model data). The tests work fine for all connections.
    However, we get HTTP 500 errors when executing the application. The
    main message is : "com.sap.mw.jco.JCO$Exception: (101)
    RFC_ERROR_PROGRAM: 'password' missing".
    I have not been able to find anything to help and SAP themselves have yet to provide us an explanation.
    - I was able to run the application fine in dev and it worked with this error occasionally appeared but now it always appears.
    - Our portal is 2004s SP 10
    - All of the JCOs are configured properly as per SAP instructions
         - modeldata use SSO with user configured in R/3
         - metadata use userid/password
    - Another prototype Web Dynpro application has the same error.
    - All of the Web Dynpro models are Adaptave RFC.
    Any ideas would be greatly appreciated.

    Here is the full exception I am getting.
    com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.pwc.servicecenter.sapwai.wdmodel.types.Klassenart could not be loaded: com.sap.dictionary.runtime.DdException: failed to create provider: 'password' missing
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
         at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
         at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:932)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
         at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
         at com.pwc.servicecenter.sapwai.wdcomponents.Z_CLASS_COPY_MAIN.wdDoInit(Z_CLASS_COPY_MAIN.java:97)
         at com.pwc.servicecenter.sapwai.wdcomponents.wdp.InternalZ_CLASS_COPY_MAIN.wdDoInit(InternalZ_CLASS_COPY_MAIN.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:429)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:1248)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:190)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         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:429)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.dictionary.runtime.DdException: failed to create provider: 'password' missing
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         ... 63 more
    Caused by: java.lang.reflect.InvocationTargetException
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
         ... 70 more
    Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
         at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)
         at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
         at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
         ... 75 more

  • Quick Question: ABAP web-dynpro model relies on JCO?

    Hi gurus,
    As mention in subject. Does ABAP web-dynpro model relies on JCO?
    Did a quick search without solid answers...

    JCO, is Java Connectors to connect SAP from Java world
    You don't need any JCO when you are in the same ABAP Stack
    There is no model Nodes/Attributes in Web Dynpro ABAP as in Java, because you are in the same ABAP Stack
    Edited by: Abhimanyu Lagishetti on Jul 10, 2008 11:35 AM

  • Web dynpro console - monitor - JCO Connection pools

    If you go to the web dynpro console -> monitor -> JCO connection pools you see a table with information.
    JCo Clients MonitorJCO Pools - 12:31:02.992
      Name Size Currently used Maximum used Max.connections Max.pool size
    Can somebody explain what for example the "Size" and "Maximum used" mean in this table?
    And if you have set max.pool size to 20, what things can override this setting in the SAP system?

    You can follow this link for information on JCO in Web Dynpro Java:
    -Kunal Kotak

  • Developing a web dynpro application compatible to two JCO destinations

    I have created a web dynpro application and integrated into a portal, which access R/3 using a JCo destination and retieves the data using a BAPI.
    But I want to integrate the same application into another portal, which would access the different R/3 system having the same function module.
    Is there any way for switching between two Jco destinations as the same application could be made to work for both the systems.
    please suggest me as I am stuck up with this issue.
    Thanks and regards

    hi Radha Krishna
    Thanks for your reply,
    Currently I have three iviews for the complete application Can you please tell me where to do the settings:
    In the application properties dothe following:
    Use the following url parameter to the
    application URI sap-wd-arfc-useSys=<DEFAULT_SYSTEM>:<SUFFIX_OF_MAPPED_SYSTEM>
    In the default system you can change your JCo destination name.
    where do I do all these settings.
    Kindly let me know.
    Thanks and regards

Maybe you are looking for