[B2B/B2C] Create a JCO Connection using XCM Framework

Hello colleagues,
I need to create a Java class that create and initializate the XCM framework.
I need to create a JCO Connector to a custom Function Module in my Backend, by
using RFC XCM Configuration.
Any kind of Idea? I see this example from SAP http://help.sap.com/saphelp_nw04/helpdata/en/d2/561106b8b3bc449f890cddfdc8d3e2/content.htm , but I don't want to maintain
myself rfc logon configuration.
I see that I need to configure a BO on ISA framework by modify backend-object.xml, but I don't now if
it's enougth
Thanks in advance
Nicola

Hi -
But I have a question,
It isn.t possible to read the jco information and add it manually to the JCO Connection class?
Does this mean to provide the JCO connectivity details in your JCO class? Try the below code which is not a best practice to my knowledge.
   JCO.Client mConnection;
   JCO.Repository mRepository;
        try {
        // Change the logon information to your own system/user
        mConnection =   JCO.createClient("001", // SAP client
                                                              "<userid>", // userid
                                                                "****", // password
                                                                  null, // language
                                                                 "<hostname>", // application server host name
                                                                 "00"); // system number
        mConnection.connect();
        mRepository = new JCO.Repository("ARAsoft", mConnection);
     catch (Exception ex) {
One question, why do you want to do this if the the JCO - XCm is handling this in a standard way , and what are you trying to do?
Raj-

Similar Messages

  • How to we give alternate JCO connection in XCM.

    Hi Gurus,
    We are using CRM 7.0 Web Channel B2B and B2C applications with Lean Order Framework.
    In B2B XCM we have used  "ERP standard configuration for CRM catalog and marketing support "as base configuration
    and to connect to CRM and ECC we have two JCO connections.
    Similarly which base configuration in B2C will provide  two JCO connections
    OR
    how do we give alternate JCO connection in XCM.
    Any idea please help.......

    Have a look at this
    /people/deborah.corsi/blog/2009/02/17/sap-crm-70-web-channel--understanding-the-lord-basket
    Regards
    Mark

  • Error  while creating a JCO Connection

    Hi i am trying to create a JCO Connection from sapj2ee engine
    my problem is i am getting an error  connection to msg server host failed ..
    When i select the Message Server the System Name and Logon Group fields are disabled and cannot be modified and the problem is there is a default system name field already present there  which remains there irrespective of whther i change
    the msg server...
    why is this happening...
    regards
    Nilesh Taunk.

    Hi Nilesh,
    exactly follow this link for the set up in Visual Admin..
    http://help.sap.com/saphelp_nw04/helpdata/en/ea/cd2e807e0e45bf9da67354f452fc05/content.htm
    then refer these forums also...
    Re: Metadata problem
    i have already explained in step by step setting up of SLD.. in thisforum... refer this also
    Re: getting a BAPI from an R/3 system
                     Regards
                     Kishor Gopinathan

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

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

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

  • Unable to create a jco destination using remote AS Java system on myjava sy

    Dear SAP Gurus,
                  I had ce 7.1 and nw 2004s based AS java Systems.I want to create a jco destination in my CE 7.1 system using usermapping data of  nw 2004s for jco communication.So i created a AS Java  system of NW2004s in my CE 7.1 SLD .when i try to create a jco destination using the AS JAVA as Nw2004s system it is not creating .Please help me to solve this issue.
    regards,
    vanamaSanthosh.

    Hi vanamaSanthosh
    try this
    1. In your CE1 System where u define your JCO destination, Go to C:\WINDOWS\system32\drivers\etc
    open hosts file and define the  identity of AS System like <IP address> <name of the system>
    for example 159.858.2.45  abcd
    restart the server and then check.
    Best Regards
    Satish Kumar

  • Cannot create/maintain JCO connection : NullPointerException in SLD

    When I want to create a new JCO connection in SLD (via WebDynpro->Content Administrator) , I get an exception :
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:285)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:250)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:157)
    Because the following document "[Adaptive RFC Troubleshooting Guide|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0019b1a-775f-2910-beb8-d81f27d0d8d0]" suggests that the problem could be an incomplete JCO connection definition, I removed all other existing connections (it's a sandbox system), but this action has not solved the problem.
    I also get the message "Exception while getting JCo Clients Failed to get list of defined JCO clients for deployable object 'sap.com/spider_search' " when the Content Administrator screen is displayed.
    Any idea of what is missing ?
    Thanks,
    Eric.

    Hi Eric,
    Check this forum link using this similar problem got resolved.
    can not create jco destination  500   Internal Server Error  after sp 13
    Thanks
    Anup

  • JCo Connection using file.properties doesn't work when deployed

    Hello Experts,
    I'm trying to connect to a SAP backend system using the JCo connection.
    I've tyed with the standard connection, crating dinamically the connection and it works fine:
    mConnection = JCO.createClient("001", // SAP client
    "sap.user", // userid
    "********", // password
    "IT", // language
    "ashost.domain.dom", // application server host name
    "06"); // system number
    mConnection.connect();
    Then I tryed to store the login data in a file 'login.properties' put in the same package of my connection classes.
    The code is:
    String[] logonStr = new String[5];
    Properties properties = new Properties();
    try {
    InputStream is = getClass().getResourceAsStream("login.properties");
    properties.load(is);
    } catch (Exception e) {
    e.printStackTrace();
    logonStr[0] = PropertyManager.getProperty(applicationProperties,"jco.client.client");
    logonStr[1] = PropertyManager.getProperty(applicationProperties,"jco.client.user");
    logonStr[2] = PropertyManager.getProperty(applicationProperties,"jco.client.passwd");
    logonStr[3] = PropertyManager.getProperty(applicationProperties,"jco.client.ashost");
    logonStr[4] = PropertyManager.getProperty(applicationProperties,"jco.client.sysnr");
    mConnection = JCO.createClient(logonStr[0],      // SAP client
    logonStr[1],    // userid
    logonStr[2],    // password
    "IT",           // language
    logonStr[3],    // application server host name
    logonStr[4]);   // system number
    If I test locally this code it works fine and the login datas are extracted from the 'login.properties' file.
    But when I deploy my PAR file in the Portal seems that the 'login.properties' file isn't found by my application...
    Which could be the cause??
    Could it be a permission problem??
    Any Ideas?
    Thanks in Advance,
    Best Regards

    Hi Shyam,
    Thanks for your answer!
    I could use the string "ashost.domain.dom" instead to extract it from the 'login.properties' but I need also the others login info as username and password.
    My problem is that the 'login.properties' file is not found by my application when the PAR file is deployed in the portal...
    I need to know if I need to move the 'login.properties' file in another package or something else...
    Any ideas??
    Have I to declare the .properties file in some configuration file (for example portalapp.xml or somthing similar..) ??
    Best Regards...

  • How to create a database connection using Jdeveloper 10g

    when i try to create a database connection,its asking for connection name.is that connection name is user-defined or predefined name??In the next step its asking for username and password.where do i get that username and password.if anyone know this please explain me in detail coz this is for the first time am using JDeveloper.
    Thanks in advance.

    Hi user583040,
    May be you could have a look on this: http://my.opera.com/Tiftif/blog/faq-jdeveloper-english §5.2. If you have suggestions to improve this document, i will greatly appreciate to add them to it.
    Regards,
    Tif

  • How to monitor  (Create /Delete )JCo connections

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

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

  • How to use PPPLib to create a PPP connection using specific service?

    I wanna use a specific service in the System Preference to create a PPP connection by PPPLib. I saw PPPConnect(int ref, uint8t *serviceid) second parameter is serviceid, but i do not know how to assign this value, because even serviceid is NULL the whole work is OK.
    Does anyone knows how to specific a service?
    Thanks a lot!

    Does anyone knows?

  • I am getting the error while creating the JCO connection -Urgent

    Hi iam gettng the following error. Can any body identify what will be the error.
    com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM  TYPE=B MSHOST=buzzard GROUP=SPACE R3NAME=MT4 MSSERV=sapmsMT4 PCS=1 ERROR       service 'sapmsMT4' unknown TIME        Mon Oct 22 20:01:09 2007 RELEASE     700 COMPONENT   NI (network interface) VERSION     38 RC          -3 MODULE      ninti.c LINE        530 DETAIL      NiPGetServByName2: service 'sapmsMT4' not found SYSTEM CALL getservbyname_r COUNTER     3
    Vijay

    Hi,
       One small correction and addition. Check for group 'SPACE'. Check for appropriate entry in services and also hosts file from C:\WINDOWS\system32\drivers\etc. If possible, restart both the servers and check.
    Regards,
    Harini S

  • How to create SDA file for using AXIS Framework in the SOAP Adapter

    Hi experts,
    I have the following question:
    How I can create the SDA file aii_af_axisprovider.sda for using the AXIS Framework in the SOAP Adpater described in http://help.sap.com/saphelp_nw04/helpdata/en/45/a4f8bbdfdc0d36e10000000a114a6b/content.htm ?
    I have downloaded the files axis.jar, commons-discovery-0.2.jar, commons-logging-1.0.4.jar, commons-net-1.0.0-dev.jar and wsdl4j-1.5.1.jar. But how to create the SDA file aii_af_axisprovider.sda? Which tool I have to use for this? It is enough to compress these 5 jar-files in the sda file or need I further files with further information (meta information etc.)?
    Thanks and best regards
    Christopher

    Hi Christopher,
        Check this discussion if you have not checked already.
    Re: NTLM Authentication dosent work with XI ?
    Regards,
    Ravi

  • Error creation of JCO connection: System Already Exist

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

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

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

Maybe you are looking for

  • Check payment through APP

    Dear Experts, How to issue a single cheque payment for multiple open item for a single vendor in automatic payment program, normally we issue single cheque for each open item but if we want to issue single for a number of open items then how to cuzto

  • DML on LOB objects in the web based forms/devl6i

    hi, I have to migrate and build a new forms using devl6i in web architecture. At present the application is using Long Raw column and OLE container in Client/server mode. How I can insert ,update and delete the LOB/Long raw objects using the three Ti

  • Corrrect procedure to upgrade

    What is the correct procedure to upgrade from Forms30 to Forms60 ? Is it Forms30 to Form4.5 to Forms60 ? Is there any direct method ? I tried using f60genm, but it only generates the .fmx file not the .fmb file. what I am missing ??

  • Are datatypes plattform independent?

    Hi all, maybe this one is a silly question (if so sorry for that..), but as we are migrating a MaxDB 7.6 database from a Win32 to a Win64 server machine we came up with concerns if the datatypes - esp. INTEGER - were plattform independent; meaning: i

  • Customizing "Myinformation"  SSHR page..Issues with flexfields

    Personalizing Myinformation page in SSHR I am trying to personalize myinformation page. On the header leve, there is a job field. (which is a key flexfield),but when I try to personalize, it never shows up as flexfield. It is showing as messagestyled