ModelData and MetaData Mapping in JCo Connection

Hi all
<b>i tried the example given in webdynpro tutorials(Creating a Web Dynpro Application Accessing ABAP Functions)
but i got dout while creating JCo connection
After clicking "Create" button of WD_FLIGHT_MODELDATA_DEST
two radiobuttons of 1)modeldata 2)metadata are comming
if i select modeldata for both WD_FLIGHT_MODELDATA_DEST, WD_FLIGHT_RFC_METADATA_DEST it is giving test sucess but while running it is giving errror as</b>
Error stacktrace:
com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.sap.tc.webdynpro.tutorial.model.types.FlightModel:com.sap.tc.webdynpro.tutorial.model.types.Bapisfldat could not be loaded: com.sap.dictionary.runtime.DdException:
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:297)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:753)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
<b>If i select modeldata for WD_FLIGHT_MODELDATA_DEST and metadata for WD_FLIGHT_RFC_METADATA_DEST it is giving testfails</b>
so can u plz solve my problem

Hi,
Create a new JCO(for both Meta Data,Model Data) connection in Content administrator>Webdynpro>Create JCO destination
and Make use of that Jco.Otherwise check the status of your Meta data.ModelData Jco connection in Content administrator>Webdynpro>Maintain Jco destination.
Regards
Nandha

Similar Messages

Model and MetaData configarations in JCO Connection

Hi all,
while creating new model i used Load Balance option instead of Single Server.So while creating JCO connection what should be selected for ApplicationData and MetaData radio buttons.The error which i am got aftet deploying and running is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Is this error is because of LoadBalance configarartion while creating JCO for Destinations or at the client num which we gave at the starting step of creating JCO
Regards
Padma N

i got similar problem and this is how i resolved
this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
please make sure user is there in the backend system from which you are getting data
xxxxxxxxxxxxxxxxxxxxxxx
Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

Model and Metadata in JCO creation

Hi all,
I am having dout regarding Modeldata and Metadata.For example i am having 2 function modules.Is it that the name given to the fields " Default logical name for model instances " and
"Default logical name for metadata instances " should be same for both the function modules as WD_BAPI_MODELDATA_DEST and WD_BAPI_RFC_MODELDATA_DEST so that JCO connection created for the above 2 names can be used for all the function modules
Regards
Padma N

Hi Chaitanya,
For example i want to work with 5 function modules in my application.So while creating model i used model data and metadata as
Modeldata Name : WD_BAPI_MODELDATA_DEST
MetaData : WD_BAPI_RFC_MODELDATA_DEST
and i selcted all the 5 function modules and i clicked finish.
If i delpoy the application now and tried to create JCO connection the above 2 names are visible with red button besides them.
If i create JCO connection for the above model and metaData instances will the 5 function modules will work fine or not
Regards
Padma N

Difference between model and metadata JCos

Hello,
What is the difference between modeldata and metadata JCos ?
Regards
Mrinalini

Hi Mrinalini,
The difference between the Model & Meta data is:
Model data is the data coming through the table (which means it describes the actual data present in the table).
Metadata is the structure of the table (which contains structure definitions, type definitions etc.)
Thus, model data destination will fetch actual data while metadata destination will contain descrition of the data.
Hope this helps you
Cheers!!!
Umang

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

How to change JCO Connection in a WD project?

Hi to all,
I want to deploy my WD projects to another J2EE server, but I have to change the JCO connection (modeldata and metadata) in my WD projects, otherwise I can't deploy. Where can I re-assign the new jco connection?
thank you very much,
Antonio

hi Antonio,
you have to make two changes:
1) double-click on the generated adaptive-rfc-class below "Models / <Name> / Model classes" and change the property "modelInstance_defaultLogicalSystem" in the Properties-Editor for the modeldata-connection
2)double-click on the dictionary that was generated for your adaptive-rfc-call below Dictionaries and change the "Logical System Name" in the Properties-Editor for your Metadata-Connection
kr, achim
feel free to reward points, if this answers your question

Error while obtaining JCO connection in t-code RSPLAN

Hi Gurus,
I have installed ECC 6.0 SR3 and i have added BI_CONT and updated all the patches. But while trying to access the t-code RSPLAN and after clicking on the START MODELER button it is opening in a browser . after giving the user id and password in the browser , while opening the page it is showing the error " Error while obtaining JCO connection". and how to create jco connections in visual admin.
can anybody please help me in this issue.
Thanks in advance.
Regards,
Babu.

Hi,
when i was trying to open RSPLAN T-Code in BI, i able to open start modeller it says that http://udnubd1:8003/sap/public/myssocntl?sap-client=320 and says that cannot find server. So i request you please can anyone help me onthis issue.
Thanks,
Reddy

Exceptions in Flights Webdynpro using JCO Connection

I followed all the steps that are in the help for creating a webdynpro accessing ABAP BAPI calls and
Flights webdynpro using JCO Connection,
Carried out,,
===================
1) All necessary codings.
2) Deploying the application.
3) SLD .
4) JCO Connections to model data and meta data.
5) At the time of running the application ,, getting the stack trace errors like this,,
Web Dynpro product information:
Product: null, Vendor: SAP AG, Version: null, Build ID: 6.3003.00.0000.20031125134518.0000, Build Date: Tue Dec 14 19:17:19 GMT+05:30 2004
Error stacktrace:
java.lang.NullPointerException
     at com.sap.dictionary.runtime.ProviderFactory$PhysicalBackendProviderKey.hashCode(ProviderFactory.java:131)
     at java.util.HashMap.hash(HashMap.java:261)
     at java.util.HashMap.get(HashMap.java:317)
     at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:227)
     at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:178)
     at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:53)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:137)
     at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:201)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:290)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:743)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:751)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:751)
     at com.sap.tc.webdynpro.progmodel.context.Node.init(Node.java:215)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:36)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:177)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:359)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:300)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:328)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:132)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:736)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:751)
     at com.sap.tc.webdynpro.progmodel.context.Node.init(Node.java:215)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:36)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:177)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:513)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:371)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:528)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:395)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:113)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.displayToplevelComponent(ClientComponent.java:133)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:347)
     at com.sap.tc.webdynpro.clientserver.task.Task.createApplication(Task.java:177)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:485)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:48)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:236)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:137)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:100)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:37)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:363)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:222)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:301)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:682)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:220)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:94)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:142)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Hi Kishore
Going by the error, there is some attribute which does not have a value at runtime. Hence you must be getting the Null Pointer Exception.
Can you let me know the following so that i could be able to help you further.
1. Name of the SLD connections. Have you tested them
2. Where are you making a call to the BAPI. Is it inside the wdDoInit() method.
3. How are you passing the parameters to the BAPI_FLIGHT_GETLIST.
I have done this example and there is no problem. If you let me know the above points i would be able to help you further.
regards
Ravi

Can we use JCo connection with non-Web Dynpro J2EE project in NW

With Web Dynpro, we have the RFC wizard to call RFCs using JCo connection. I am wondering, if I create a J2EE project in NW development studio, can I and how to use JCo connection to call RFCs?
Thanks.

yes, of course.
Add jar sapjco.jar then
import com.sap.mw.jco.*;
public class Bapi1 extends Object {
   JCO.Client mConnection;
   JCO.Repository mRepository;
   public Bapi1() {
      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("SAPJCo", mConnection);
      catch (Exception ex) {
        ex.printStackTrace();
        System.exit(1);
      JCO.Function function = null;
      JCO.Table codes = null;
      try {
         function = this.createFunction("BAPI_COMPANYCODE_GETLIST");
         if (function == null) {
           System.out.println("BAPI_COMPANYCODE_GETLIST" +
                              " not found in SAP.");
           System.exit(1);
         mConnection.execute(function);
         JCO.Structure returnStructure =
           function.getExportParameterList().getStructure("RETURN");
         if (! (returnStructure.getString("TYPE").equals("") ||
                returnStructure.getString("TYPE").equals("S")) ) {
           System.out.println(returnStructure.getString("MESSAGE"));
           System.exit(1);
         codes =
           function.getTableParameterList().getTable("COMPANYCODE_LIST");
         for (int i = 0; i < codes.getNumRows(); i++) {
           codes.setRow(i);
           System.out.println(codes.getString("COMP_CODE") + '\t' +
                              codes.getString("COMP_NAME"));
      catch (Exception ex) {
        ex.printStackTrace();
        System.exit(1);
      try {
        codes.firstRow();
        for (int i = 0; i < codes.getNumRows(); i++, codes.nextRow()) {
          function = this.createFunction("BAPI_COMPANYCODE_GETDETAIL");
          if (function == null) {
            System.out.println("BAPI_COMPANYCODE_GETDETAIL" +
                               " not found in SAP.");
            System.exit(1);
     function.getImportParameterList().
       setValue(codes.getString("COMP_CODE"), "COMPANYCODEID");
     function.getExportParameterList().
       setActive(false, "COMPANYCODE_ADDRESS");
     mConnection.execute(function);
     JCO.Structure returnStructure =
       function.getExportParameterList().getStructure("RETURN");
     if (! (returnStructure.getString("TYPE").equals("") ||
            returnStructure.getString("TYPE").equals("S") ||
            returnStructure.getString("TYPE").equals("W")) ) {
        System.out.println(returnStructure.getString("MESSAGE"));
     JCO.Structure detail =
       function.getExportParameterList().
       getStructure("COMPANYCODE_DETAIL");
     System.out.println(detail.getString("COMP_CODE") + '\t' +
                        detail.getString("COUNTRY") + '\t' +
                        detail.getString("CITY"));
catch (Exception ex) {
    ex.printStackTrace();
    System.exit(1);
mConnection.disconnect();
public JCO.Function createFunction(String name) throws Exception {
   try {
     IFunctionTemplate ft =
        mRepository.getFunctionTemplate(name.toUpperCase());
     if (ft == null)
       return null;
     return ft.getFunction();
   catch (Exception ex) {
     throw new Exception("Problem retrieving JCO.Function object.");
public static void main (String args[]) {
   Bapi1 app = new Bapi1();
Link: [http://help.sap.com/saphelp_nw04/helpdata/en/35/42e13d82fcfb34e10000000a114084/frameset.htm]

How to create a model and JCO connection

Hi all,
The Userid and Password given while creating new model at Singleserver/Load balancing tab should be same as the userid and password given while creating JCO connection. i.e in JCO creation while mapping modeldata to Application data and Metadata to metadata we will give some userid and password.
will those 2 userids and passwords should be same.
the error which i am getting is
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Error connecting using JCO.Client: null
Regards
Padma N

2 userids and passwords need not be same
i got similar problem and this is how i resolved
this is because jco connections are Using SSO and the user who is accessing that webdynpro application is not present in the backend system.
please make sure user is there in the backend system from which you are getting data
xxxxxxxxxxxxxxxxxxxxx
Edited by: Armin Reichert on Feb 18, 2008 7:26 PM

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.

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.

JCO connection issue with MetaData

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

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

FDM ERPI metadata mapping with EBS and Planning

Hi,
ERP integrator metadata mapping in its showing only Planning dimension names and EBS segments ,then mapping.
suppose source(EBS) Account to Target(planning) Account,in this the EBS member codes and planning memeber codes are different ,
how can i know this mapping is happend,
If possible to see all the members?,and connect each and every member?,
Can you please...
regards,
SV

Thanks for your help. I hit against another issue though.
On clicking on Open Source document, an error page opens up with an error - HTTP: 400 Bad Request.
On checking the properties for this page I noticed that the address for the url is
res://ieframe.dll/http_400.htm#http://localhost:6550/workspace/index.jsp
My workspace is on port 80.
6550 is the ERPI port.
The url should have read localhost/workspace/index.jsp
Is there some settign that I am missing.
Thanks.

Logical systems for modeldata and RFC metadata

Hi All,
I want to know how I can display the my own created logical system names under the drop-down menu when i have to select the logical system names for modeldata and rfc metadata. I don't want to them to be written instead i want them to be one of the options in the drop down menu, as we have them in the FLIGHT_LIST_INIT example found in the sample applications and examples.
Thanks in advance
Srikant

Hi,
While creating SLD for your R/3 systems give the desired name of wht u want instead of logical name.
For configuring the same refer the link below :-
http://help.sap.com/saphelp_erp2004/helpdata/en/29/e0b75c2b7d40c5bfbda82e905b701c/frameset.htm
Regards,
guru

ModelData and MetaData Mapping in JCo Connection

Similar Messages

Maybe you are looking for