Skip to Content
author's profile photo Former Member
Former Member

SAP R3 connector system for the Adaptative RFC model

Hi folks!

We´ve generated a Web Dynpro project using the Adaptative RFC model. When running the application we get the exception:

com.sap.dictionary.runtime.DdException: at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)

This surely happens because we haven´t defined the SAP R3 connector system:

Could someone please show us how to do this?

We are using SAP R3 Dedeicated connection, should we use the SAP R3 ConnectionString? At least, we need to know which is the Gateway Host, the SAP R3 machine or the J2EE WAS one? Is the other the Application Server Host? What would be the Gateway Service?

In the other hand, at defining the RFC Destinations on the SAP R3 server, we´re using the "Registered Server Program" Activation Type. Is this correct? When testing the connection, it fails because the program is not registered at the server.

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Related questions

10 Answers

  • Best Answer
    Posted on Oct 11, 2005 at 04:23 PM

    Bernardo,

    you have to configure your JCo-Destinations in the WebDynpro Content Administrator located at: http://<host>:<port>/webdynpro/welcome an then "Maintain JCo Connection" on the server, you have deployed your WD-Application.

    These JCo-Connections should point to the system you want to communicate with.

    This has nothing to do with (registered) RFC-Connections in SM59.

    kind regards, achim

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2005 at 04:45 AM

    Hi Bernardo,

    You need to configure SLD and then configure your JCO for SAP R/3 connection.

    Follow these links for the same.

    Configuring SLD:

    configuration-of-sld

    Configuring JCO:

    web-dynpro---problem-with-sld-jco-connection

    Regards,

    Bhavik

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2005 at 10:22 AM

    We´ve configured properly the SLD and the JCo connections mentioned in the link below, but after redeploying our test application we get the error:

    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.hesa.pruebas.ntw.models.rfcmodel.types.Bapimaxrow could not be loaded: com.sap.dictionary.runtime.DdException

    Caused by: com.sap.dictionary.runtime.DdException

    Could you please help us?!

    Is it necessary to define any System at the Portal System Admin?

    And what about "JCo RFC Provider" at "Visual Admin"? Here we always get: "Error changing bundle´s properties"

    Thank you very much in advance!

    Add a comment
    10|10000 characters needed characters exceeded

    • it's still a connetcion problem between your WAS and the backend system.

      Are the tests within the content administrator successful?

      Have you mainatained both(!) jco-connections (one for meta-data and one for application data)?

      when you open your application, you can see the required jco-connections on a tab of the right side.

      kind regards, achim

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2005 at 11:24 AM

    Hi Bernardo

    Were you able to Test the SLD and then the JCO connections(Destination Files connection to the system) in the WebDynpro -> Content Administration successfully. Check whether the connection is proper or not.

    Regards

    Vasundhara.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 13, 2005 at 03:34 PM

    Hi again:

    It seems the problem with the JCos is that there´s no Message Server defined at the WAS Abap. Could you please help me about this? I hope the end is near:)

    Thank you very much in advance.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi,

      certainly the PUBLIC group exists in my SAP WAS ABAP. We've created it today, but I can't logon by SAPGUI to a logon group. When I choose SAPGUI - groups - "generate list" in SAPGUI, I get the error:

      "The message server didn't found any group".

      This is the same error that occur when we test the JCO Metadata destination. Though the JCO Model data destination works fine because it's configured to use a single server.

      How can we test if the PUBLIC group and the message server are working fine? Can we check it by SAPGUI?

      Thanks in advance

  • author's profile photo Former Member
    Former Member
    Posted on Oct 14, 2005 at 10:03 AM

    Hi

    If your message server settings are correct then you can successfully login to the SAP GUI with this PUBLIC Group. But if still your JCO connection fails then try with some other groups like for example SPACE and check whether you are able to test the JCO successfully with this Group.

    If you are not able to connect to SAP GUI with PUBLIC Group then check the entry in the services.cnf in the WINNT/System32 folder. Hope this helps.

    Regards

    Vasundhara.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 14, 2005 at 11:45 AM

    Hi Augustin

    As specified by my earlier post make the entry in the services.cnf file of WINNT/System32 specifying your message server and the port/tcp. Then try connecting to the PUBLIC group using SAP GUI. This should work.

    Regards

    Vasundhara.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Vasundhara:

      My SAP WAS ABAP is windows xp. I supose that the file you've mentioned is:

      C:\Windows\system32\drivers\etc\services.

      In that file (windows XP service file) is the entry:

      sapmsNSP 3600/tcp # SAP System Message Port

      NSP is the SID of the WAS ABAP.

      Best regards.

  • author's profile photo Former Member
    Former Member
    Posted on Oct 14, 2005 at 12:22 PM

    Yes you r right. Did that work ?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 14, 2005 at 01:30 PM

    Are you sure that you are specifying the correct System Id(NSP) and Message Server IP while generating the list of Groups in SAP GUI?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Bhavik,

      I've cheked the case sensitivity of "PUBLIC" group in SMLG transaction and is in capital. Is there any important parameter in this configuration to check it?

      I think after the SLD configuration (RZ70), the logon group server is configurated to the SLD Portal itself in capitals automatically.

      But, what about the SAPGUI logon? I can't log in by a logon server group. As I've said, I got a error message in SAPGUI when I try to generate the group servers list.

      What can I do to check the PUBLIC logon server? Should I do anything to simulate load balancing in my WAS ABAP NW04?

      Best regards,

      Agustin.

  • author's profile photo Former Member
    Former Member
    Posted on Oct 19, 2005 at 01:48 PM

    Hello,

    We've solved the error.

    Once configured the SLD and JCo-Destinations in the WebDynpro Content Administrator, we had the problem with METADATA_DIRECTORY JCO-Connection. When we tested it, we got an error related with the PUBLIC LOGON GROUP. This JCO destination is a metadata directory connection and use the SAP message server to connect to an logon group.

    The PUBLIC logon group was created already in the new WAS 640 stack ABAP, but it is necesary to add a "Logon Favorite Storage" in "SMLG Transaction - Display control/status Area" called PUBLIC too.

    After that, all JCO connections and the webdybpro application run fine.

    Best Regards.

    Agustin Alvarez

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.