Credential Alias in JCO connection - xMII 12.1.4

Hi All,
We are using SAP xMII of version 12.1.4 Build (46).
We are trying to add SAP server details over system configuration editor under data services.
While adding entries for JCO connection, we didn't find any place to update login credentials for SAP server.
Created connection successfully, we opened a new transaction and add SAP JCO interface as an action block.
When we try to configure, there is drop down named "Credentail Alias".
We could not see any data gets populated in drop down.
On clicking "Get List" button, we got an error saying "JCO Proxy Error : No Credential Alias Defined".
Kindly help us to overcome the error.
Thanks.
Rajesh.S

Rajesh,
you can define the Credential Alias under the MII Admin Menu -> Security Services  -> Credential Editor .
After defining a New entry go back to your TRX and open again the Configuration of your JCO Action Block.
Now you will find in the Credential Alias dropdown box the Alias that you created before.
BR
Pedro Iglseias

Similar Messages

  • Trouble saving Credential Alias in Credential Editor

    Dear Experts,
    I am having trouble creating a Credential Alias for my JCO connector to an ECC6 system.  When I go to the Credential Editor in my MII 12.1.8(Build 36) system (using Firefox 3.6.17), which is on Netweaver CE 7.1 EP5, I do not have any buttons.  Very odd!  Shouldnu2019t I at least see u2018Newu2019, u2018Saveu2019, u2018Editu2019 and u2018Deleteu2019 buttons?  I am unable to save the password I am setting for the Credential Alias.  The alias name is there, but when I try to change the username or add the password I am unable to save it.
    I have tried creating a test transaction just to confirm I have a connection and I get u201CJCOProxy error: u2018passwordu2019 missingu201D when trying to get a list of available BAPIu2019s.  I have tried creating a local variable with the password and setting it directly in the links of the JCO Start Session, but I still get the same error.  Apparently the alias setting is overriding the link setting within the action block.
    Has anyone ever seen this issue?  Any ideas as to what I may be doing wrong?  Am I completely missing something?
    Thanks in advance for any and all help in this matter.
    Mari Santangelo

    Have you checked your role.
    It is SAP_XMII_Developer or SAP_XMII_Administrator/SAP_XMII_Super_Administrator.
    u2018Newu2019, u2018Saveu2019, u2018Editu2019 and u2018Deleteu2019 buttons will not be visible to you if you are not having Administrator roles.
    You can change the roles according to screens as well.
    Check the following Link: [Link|http://help.sap.com/saphelp_mii121/helpdata/en/48/d0c6efbcb810b6e10000000a421138/frameset.htm]
    after determine Credential Alias under the MII Admin Menu -> Security Services -> Credential Editor .
    open your TXN. In Configuration of your JCO Action Block you will find in the Credential Alias dropdown box the Alias that you created.
    Just map Credential Alias and test it again.
    Thanks
    Anshul

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

  • JCO connection without the use of HCM util.?

    Hi Guru's!
    I have developed a dynpage application where i call a function module inside sap, using the Sap Enterprise Connector.
    I use this code to get the JCO connection, where "SystemIdentifier" is the System Alias parameter maintained in the portalapp.xml file eg. "SAP_R3_HumanResources"
    the code looks like this:
    public SapConnection(Object originator, IPortalComponentRequest request, String systemIdentifier) {
              try {
                   IJCOClientPoolEntry poolEntry = Util.getJCoPoolEntry(originator, request, systemIdentifier);
                   client = poolEntry.getJCOClient();
              } catch (BaseException e) {
                   System.out.println("Fejl BaseException: " + e.getMessage());
              } catch (Exception e) {
                   System.out.println("Fejl Exception: " + e.getMessage());
    Normally this code works well, but today we where trying to use the iView in a portal which doesnt have ESS or MSS installed.
    And therefore the HCM_util.jar is not deployed on the server.
    So my question is: Is it possible to connect to the sap system using a System Alias, but wihtout the HCM_Util.jar ?
    Help is very much apreciated!
    Br
    Ronni

    Hi again.
    Seems that i found another way to do this:
    IJCOClientService clientService = (IJCOClientService)request.getService(IJCOClientService.KEY);
                IJCOClientPoolEntry poolEntry;
                try
                     poolEntry = clientService.getJCOClientPoolEntry(systemIdentifier, request);
    Sorry for the commotion
    Br
    Ronni

  • JCO connection problem at web dyn pro

    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 <b>RFC destination </b> there are some fields which i need to enter those are  (a)Program ID as <b>mySLD</b>  (b) Gateway Host as <b>10.10.10.125</b> (c)Gateway service as <b>sapgw00</b>  (d)Number of processes as <b>1</b>
          Under <b>Repository</b>  (a) Application server host <b>10.10.10.125</b> (b)system number as <b>00</b> (c)Client number as <b>100</b> (d)Language as <b>en</b> (e)user as <b>ABCD</b>  (f)password as <b>1234</b>
      I haven't choosed the check boxes <b> Local bundle </b> and <b> Unicode </b> and pressed the set button. So like this i created the RFC destinations. under the <b>properties</b> tab  there is a property called <b>RFC_DEFAULT_DESTINATION</b> by default it was false so i made it as <b>true.</b> .
    I also went to <b>SLD Data Supplier</b>,under <b>Runtime</b> 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: 10.10.10.125 (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 <b> sm59 </b> transaction. There under TCP/IP connections i been to <b> SLD_NUC </b>, opened this by double clicking that and under Technical settings for <b> Program ID </b> I had given the ID which I created at visual administrator [JCO RFC Provider] which is <b>mySLD </b>, under gateway options for Gateway Host as <b>10.10.10.125</b>and Gateway service as <b> sapgw00 </b> 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 <b>sapmsUV0         3600/tcp </b> entry at
    <b>WINDOWS\system32\drivers\etc</b>\services file, and also there are some required entries which are already existing those are <b>sapgw00</b> <b>3300/tcp</b> to <b>sapgw99</b> <b>3399/tcp</b> , another entry starts from  <b>sapdp00s</b> <b>4700/tcp</b> to <b>sapdp99s</b> <b>4799/tcp</b> , next entry starts from  <b>sapgw00s</b> <b>4800/tcp</b> to <b>sapgw99s         4899/tcp</b> and <b>sapmsJ2E      3601/tcp </b> .
    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
                (1) COMPANY_CODE_MODEL
                (2) COMPANY_CODE_RFC_METADATA
    So I started creating connection for COMPANY_CODE_RFC_METADATA.
      First one is
                   General data <b> Name </b>: COMPANY_CODE_RFC_METADATA
                                        <b> Client </b> : 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
                                       <b>Dictionary Meta Data</b> and <b>application Data </b>
                            I choosed the first one.
                 Then
                           Msg. Server Connection
                            Security
                            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.

    answer in your other thread on the same topic
    problem in connecting JCO destination in web dynpro
    (Kindly avoid double posting)
    Regards
    Raja

  • How to connect xMII 11.5 and MaxDB?

    Hi All,
    Someone know how to connect xMII 11.5 and MaxDB (7.6 or 7.7)?
    Thanks in advance,
    Vinicius Martins
    Axia Consulting
    São Paulo - Brasil

    Hi Rick,
    I read my log and found nothing about the SAP DP connection problem, only a reference about the JCO server error:
    2008-05-26 13:54:31,617 [JCO.ServerThread-1] ERROR  SERVER-EXCEPTION - [null,null,null,] com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Mon May 26 13:54:31 BRT 2008.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 512 seconds.
    Missing -a<Program ID>
    2008-05-26 13:58:42,999 [ServletExec: request: time=1211821122929, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Disabling server MaxDB
    2008-05-26 13:58:42,999 [ServletExec: request: time=1211821122929, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM ConnectionPool - Destroy Connection pool [jdbc:sapdb://localhost/xmii?timeout=0]:
    2008-05-26 13:58:42,999 [ServletExec: request: time=1211821122929, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Enabling server MaxDB
    2008-05-26 13:58:43,089 [ServletExec: request: time=1211821122929, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM ConnectionPool - Created Connection pool [jdbc:sapdb://localhost/xmii?timeout=0]:
    2008-05-26 13:58:43,089 [ServletExec: request: time=1211821122929, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Create Server [name=MaxDB,className=com.lighthammer.Illuminator.connectors.IDBC.IDBC,description=SAP MaxDB 7.6,enabled=true,connected=true,holder=[email protected]4d]
    2008-05-26 13:59:59,509 [ServletExec: request: time=1211821199509, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Disabling server MaxDB
    2008-05-26 13:59:59,509 [ServletExec: request: time=1211821199509, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM ConnectionPool - Destroy Connection pool [jdbc:sapdb://localhost/xmii?timeout=0]:
    2008-05-26 13:59:59,509 [ServletExec: request: time=1211821199509, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Enabling server MaxDB
    2008-05-26 13:59:59,559 [ServletExec: request: time=1211821199509, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM ConnectionPool - Created Connection pool [jdbc:sapdb://localhost/xmii?timeout=0]:
    2008-05-26 13:59:59,559 [ServletExec: request: time=1211821199509, uri=/Lighthammer/Admin/CMSAdmin] SYSTEM Connector - Create Server [name=MaxDB,className=com.lighthammer.Illuminator.connectors.IDBC.IDBC,description=SAP MaxDB 7.6,enabled=true,connected=true,holder=[email protected]a]
    2008-05-26 14:03:03,653 [JCO.ServerThread-1] ERROR  SERVER-EXCEPTION - [null,null,null,] com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Mon May 26 14:03:03 BRT 2008.
    This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 1024 seconds.
    Missing -a<Program ID>
    2008-05-26 14:03:12,015 [ServletExec: request: time=1211821391815, uri=/Lighthammer/Illuminator] ERROR  ErrorHandler - Server is currently disabled (IDBC).
    com.lighthammer.Illuminator.logging.LHException: Server is currently disabled (IDBC).
         at com.lighthammer.Illuminator.services.handlers.IlluminatorService.getServer(Unknown Source)
         at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source)
         at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
         at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
         at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)
         at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)
         at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)
         at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)
         at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)
         at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)
         at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)
         at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)
    2008-05-26 14:03:13,918 [ServletExec: request: time=1211821393738, uri=/Lighthammer/Illuminator] ERROR  ConnectionHolder - Unable to get a connection from the pool
    com.sap.dbtech.jdbc.exceptions.DatabaseException: [-4004] (at 22): Unknown table name:XMII_LANGUAGES
         at com.sap.dbtech.jdbc.packet.ReplyPacket.createException(ReplyPacket.java:64)
         at com.sap.dbtech.jdbc.ConnectionSapDB.throwSQLError(ConnectionSapDB.java:984)
         at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:622)
         at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:489)
         at com.sap.dbtech.jdbc.StatementSapDB.sendCommand(StatementSapDB.java:859)
         at com.sap.dbtech.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:923)
         at com.sap.dbtech.jdbc.StatementSapDB.execute(StatementSapDB.java:266)
         at com.sap.dbtech.jdbc.StatementSapDB.execute(StatementSapDB.java:234)
         at com.sap.dbtech.jdbc.trace.Statement.execute(Statement.java:368)
         at com.lighthammer.Illuminator.tools.database.ConnectionPool.validateConnection(Unknown Source)
         at com.lighthammer.Illuminator.tools.database.ConnectionPool.createConnectionObject(Unknown Source)
         at com.lighthammer.Illuminator.tools.database.ConnectionPool.getConnectionObject(Unknown Source)
         at com.lighthammer.Illuminator.tools.database.ConnectionHolder.getConnection(Unknown Source)
         at com.lighthammer.Illuminator.connectors.IDBC.IDBC.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source)
         at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
         at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
         at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)
         at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)
         at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)
         at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)
         at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)
         at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)
         at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)
         at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)
    2008-05-26 14:03:14,048 [ServletExec: request: time=1211821393738, uri=/Lighthammer/Illuminator] ERROR  ErrorHandler - An error occurred while creating a DB connection. Connection may have been prevented due to too many waiting connections in pool.
    com.lighthammer.Illuminator.logging.LHException: An error occurred while creating a DB connection. Connection may have been prevented due to too many waiting connections in pool.
         at com.lighthammer.Illuminator.tools.database.ConnectionHolder.getConnection(Unknown Source)
         at com.lighthammer.Illuminator.connectors.IDBC.IDBC.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source)
         at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
         at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
         at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)
         at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)
         at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)
         at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)
         at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)
         at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)
         at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)
         at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)
    2008-05-26 14:03:14,048 [ServletExec: request: time=1211821393738, uri=/Lighthammer/Illuminator] ERROR  ErrorHandler - An error occurred while creating a DB connection. Connection may have been prevented due to too many waiting connections in pool.
    com.lighthammer.Illuminator.logging.LHException: An error occurred while creating a DB connection. Connection may have been prevented due to too many waiting connections in pool.
         at com.lighthammer.Illuminator.tools.database.ConnectionHolder.getConnection(Unknown Source)
         at com.lighthammer.Illuminator.connectors.IDBC.IDBC.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source)
         at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source)
         at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638)
         at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236)
         at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96)
         at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source)
         at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60)
         at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159)
         at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823)
         at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091)
         at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973)
         at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167)
         at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204)
         at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)
    Thanks for any help,
    Vinicius

  • JCO connection pool is exhausted

    hi
    I am using RFC module in my web dynpro application. When the application is used for sometime, the JCO connection will get exhusted. The JCO connection will not release itself. I can't find any method in web dynpro to release the connection manually. How can I solve this problem?

    Hi,
    What is scope of the connection. View properties of MODELDATA and METADATA  destinations.
    You can change the scope of the connection..
    or
    wdContext.current<BAPI INPUT>Element().modelObject().modelInstance().disconnectIfAlive();
    For more ways , give a forum search.. There are a lot of close forum posts.. Gud luc..
    Regards
    Bharathwaj

  • Problem with JCo Connection Pool

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

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

  • Unable to close metadata jco connection

    Hi Experts,
    when checking the JCo Connection Pools in Web Dynpro Console, I found that all MetaData JCo are in use and unable to disconnect automatically.
    the following is metadata jco destination setting
    Maximal Pool Size 1
    Maximum Connections 5
    Connection Timeout 60
    Maximum Wait Time 10
    how can i do to close these jco connection?

    Hi Sidney,
    I dont really understand why you want to remove the Jco connections. If you click on the "Remove" button as posted earlier by someone, it will completely remove your Jco configurations and you have to create them again on your own. SO, dont do that.
    If you want to disconnect the Jco connection in webdynpro java, we can do that by using the following piece of code at the end of the  connection process.
    As far as I know, by default the Jco connections gets disconnected after certain time limit. Because, I never had to disconnect the Jco whenever I used one.
    wdContext.currentModelElement().modelObject().modelInstance().disconnectIfAlive()
    Regards,
    Gopal.

  • How to use a JCO connection pool in an EJB?

    Hi *,
    I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
    I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
    Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
    Kind regards,
    Lars

    Hi *,
    I want to build a WebService using SAP Web AS (J2EE Engine) that connects to a R/3 ERP (release 4.7).
    I thought of building a stateless session bean that will be deployed as webservice. The session bean shall connect to the R/3 in order to call some BAPIs. I'd like to use a JCO connection pool. But I'm not sure, where I should create and destroy the connection pool. Are the EJB methods ejbCreate() and ejbRemove() the right ones? If so, my businness methods would just have to get a connection from the pool and call the BAPIs, right? If not, what do you suggest?
    Another question: I already deployed a bean as webservice. Since not really knowing how to use the connection pool, I created a bean with one business method that creates a connection pool whenever it gets called. But if I have to change something in the bean so that I have to redeploy the bean I can't call my business method anymore, because JCO cannot load a native library once again, as it is already loaded, This leads to an exception. So I have to restart the complete engine everytime I redeploy my bean. Are there any workarounds for this problem? I'm not sure whether this is connected to the wrong use of the JCO connection pool.
    Kind regards,
    Lars

  • Single Webdynpro Application with multiple JCO Connection ?

    Hi Experts,
    I have a strange requirement ......
    We have a Webdynpro Application which is connected to
    say (using JCO connection)
    client:- A
    now i want to connect the same Webdynpro application to
    Client:- B which is again in the same server as the client A.
    Please help me how to handle this.
    how it possible to connect a single Webdynpro application to two different clients using JCO Connection.
    Please help.
    Points would be rewarded to helpful answers.
    Regards,
    Sanjyoti.

    Hi experts
                        We have to use  wd application for both client at a same time e.g. as follow
    Client A -
    > Travel app--->Featches data from A for   employee hired in client A ,in same server as B
    Client B -
    > Travel app--->Featches data from B for   employee hired in client B , in same server as A
    we  are using same EP for both client but using diffrent roles for employees of both client.
    Please reply asap.

  • Error while obtaining JCO connection when creating JCO connection

    Hey,
    im having a problem when creating a JCO connection in the Web Dynpro Content Administrator.  Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
    In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
    After pushing the finish button i get the following stacktrace:
    Failed to create new JCO client connection WD_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at
    com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at
    com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
    com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
    com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
    com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
    com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
    com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
    java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at
    com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at
    com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at
    com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
    We are running WebAS 640 SP 14 on Unix.
    Greetings,
    Hannes
    Message was edited by: Hannes Defloo

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

  • Error while creating  jco connection for metadata?

    Hi all,
    we are using ep 6 sp 16.
    I could create the  JCO connection for application data  but i am not able to create the jco connection for metadata for the same  r3 server .
    while creating  the   the connection
    system name and  logon group  and disable
    and when i click finish
    it is giving  following error
    Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) 
    Thanking.
    Rajendra

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

  • Error while obtaining JCO connection.

    Hi I'm trying to put in place since BW-SEM RSPLAN the transaction, I'm pointing at my portal from the transaction RSPLSA
    But when it signs the user gets the message Error while obtaining JCO connection.
    I was reviewing my WebDynpro on my site by following these steps:
    1 I will http://portal:port
    2 I clicked Webdynpro
    3 I click on Content Administrator
    I clicked on 4 Maintain JCO destinations
    and then I log shows the following:
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    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:485)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
        at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
        ... 39 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type     HTML Client
    User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
    Version     null
    DOM version     null
    Client Type     ns7
    Client Type Profile     nn7
    ActiveX     disabled
    Cookies     enabled
    Frames     enabled
    Java Applets     enabled
    JavaScript     enabled
    Tables     enabled
    VB Script     enabled
    Server
    Web Dynpro Runtime     Vendor: SAP, build ID: 7.0014.20071210061512.0000 (release=645_VAL_REL, buildtime=2007-12-10:05:23:29[UTC], changelist=470565, host=pwdfm101), build date: Wed Oct 01 12:15:02 CDT 2008
    J2EE Engine     7.00 patchlevel 109886.44
    Java VM     IBM J9 VM, version:2.3, vendor: IBM Corporation
    Operating system     AIX, version: 5.3, architecture: ppc64
    Session & Other
    Session Locale     en_US
    Time of Failure     Thu Nov 06 16:00:23 CST 2008 (Java Time: 1226008823202)
    Web Dynpro Code Generation Infos
    sap.com/tcwdtools
    No information available     null
    sap.com/tcwddispwda
    No information available     null
    sap.com/tcwdcorecomp
    No information available     null
    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:485)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.updateJCOClientStatus(JCOConnectionsDetails.java:480)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:699)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.addJCOClientToList(JCOConnectionsDetails.java:663)
         at com.sap.tc.webdynpro.tools.explorer.JCOConnectionsDetails.wdDoInit(JCOConnectionsDetails.java:121)
         at com.sap.tc.webdynpro.tools.explorer.wdp.InternalJCOConnectionsDetails.wdDoInit(InternalJCOConnectionsDetails.java:262)
         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.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:319)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    What should I do??

    Hi Antonio,
    Follow the below note for Jco related troubleshooting.
    https://service.sap.com/sap/support/notes/919850
    Are you able to see the 4 Jco connections green?
    Regards,
    Debasis.

  • Error while obtaing JCO connection

    In Bussiness planning in portal. When i click Planning tab in Enterprise portal, its throwing an error that "error while obtaining JCO connection". I cant proceed furtherI
    I am working in my own system.
    I have checked many posts and i have done some JCO destinations as per the instructions but it's vain.
    The detailed error is as follows;
    500   Internal Server Error
    Web Dynpro Container/SAP J2EE Engine/6.40
    Failed to process request. Please contact your system administrator.
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(CharRelInst): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.ensureActiveComponent(ComponentUsage.java:773)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceControllerInternal(ComponentUsage.java:348)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.getInterfaceController(ComponentUsage.java:335)
    at com.sap.ip.bi.plan.workbench.wdp.InternalInfoprovController.wdGetCharRelInstInterface(InternalInfoprovController.java:296)
    at com.sap.ip.bi.plan.workbench.InfoprovController.checkSavable(InfoprovController.java:254)
        ... 48 more
    please give some pointers like what needs to be done JCO settings in Backend.
    Thanks in advance.

    Niranjan,
    3 causes and many more....
    First and most probable cause is that your CR content in SLD is old....
    FIX - to fix this download latest cimsap and crcontent from service.sap.com and implement in SLD.
    Second cause user is locked
    FIX - unlock in R/3
    Third cause could be that the connection pool in JCO is exhausted.
    FIX - increase connection pool in JCO.
    More causes.
    With this new version it appears that any error before connection is created ends up showing this, so I would really go into default trace and look there for original errors, that is the way I found JCO pool was exhausted, that error was not being forwarded and instead it was showing this error...
    reward points if helpful

Maybe you are looking for

  • Tiger upgrade on MacBook Pro, which one?

    I have a 15" MacBook Pro (2.2 GHz Intel Core 2 Duo) running Tiger (OS10.4.11) that I just got off of eBay. It has 2 GB 667 MHz DDR2 SDRAM.  Would like to upgrade the OS to the latest version it can run.  What OS can run on this machine & how do I pro

  • Http404-File not found  - again

    First let me say I've scoured this forum and cannot solve my problem. I was attempting to expose my server to the internet and appear to have done a fine job of messing things up. I have been using AppEx 1.6, 10g db and the Http server from the compa

  • IBook working only when propped up

    Hi all, my iBook G4 has had its blips in past months, most notably not recognizing that the battery was inside. Nothing too major. It did this again a day or two ago. Then suddenly today programs started working extremely slowly and then crashing, pa

  • Any similar transaction in PM/CS like CO1P in PP

    Hi, This is just for clarification. We have CO1P transaction(Predefined Confirmation processes) in PP and as like that do we have any similar transaction in service/maintenance order confirmation. As I know we have only IW46,COGI and COFC for post pr

  • Using digital editions 2.0, I cannot transfer books downloaded to digital editions from library to my nook.  Error message: failed to write destination file.

    Using digital editions 2.0, I cannot transfer books downloaded to digital editions from the library to my nook.  I get an error message: failed to write destination file. At first, this happened once in a while but now every time. Help!!!