Skip to Content

Read Dictionary Meta Data with a Single Server Connection

Hello,

I've Enterprise Portal 6.0 SP4 NetWeaver Stack 2 Developer Workplace Sneak Preview from https://www.sdn.sap.com/sdn/downloads.sdn running on my computer and implemented the Tutorial: "Creating A Web Dynpro Application Accessing ABAP Functions" from https://www.sdn.sap.com/sdn/developerareas/webdynpro.sdn?page=TutWD4_AccessingABAP.htm.

During the setup of the JCo Conneciton for the WD_FLIGHTLIST_RFC_METADATA_DEST in the Web Dynpro Content Administrator in Step 3 I came across the problem that I can not use a Single Server Connection to read Dictionary Meta data.

So my Question: Why is it not possible to read Dictionary Meta Data with a Single Server Connection?

Regards

Gregor

Add comment
10|10000 characters needed characters exceeded

5 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jul 27, 2004 at 08:17 AM

    There are two reasons for reading dictionary metadata in a separate connection:

    1) Special priviledges are required to read dictionary metadata. Usually the RFC user does not have this permission.

    2) Dictionary metadata is cached and reused by ALL users on the frontend. This means, that you have a max of one connection per J2EE node for reading dictionary metadata, even if you have 250 concurrent RFC connections being used by 250 different user sessions. In general, this is the best compromise between performance, scalability, and administrative overhead.

    Hope that helps.

    Best regards, karin

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Mital,

      one necessary step for getting the connection to work is to define one logon group in transaction * smlg * of the R/3 system.

      (Enter a name, e.g. 'PUBLIC', in the box at the beginning that is empty by default.)

      Best regards

      Ruth

  • author's profile photo Former Member
    Former Member
    Posted on Jul 27, 2004 at 10:56 PM

    So can I ask, how do you setup the Metadata JCO in a single server system? I have the sneak preview WAS Server Java 6.4 (J2EE) and I have also installed the MINIWAS 6.2. I have successfully setup the SLD and imported the 2 zip files. I can start SAP, and through SM59 test connect to SLD_NUC. I can use RZ70 to 'send' info. I can successfully load, build, archieve the Flightlist demo. I can go to http://localhost:50000/Webdynepro/welcome... and create and test the Model data under JCO connections (not using load balancing). When I test 'metadata_dest' I get the RFC_error_communication Group Public not found. I tried your fix (services fiel sapmsBSP 3200, but this makes it not possible to connect to sap since SAP listens on port 3200. Any thoughts? Can I spoof my system to think its has load balancing?

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Russ:

      I was wondering if you will be so nice to tell me how you configure SLD_NUC at SM59. I can not created because it already exists and it have the connection type: TCP/IP connection and I can not change it.

      I configured at the SM59 RFC destinations ->

      R/3 connections -> double click at BSP which is my system ID and completed Gateway options with my was 6.20 data (IP and sapgw00 as service). The Targethost is my was 620 too. The connection test works OK !!! but when I go back RZ70 and test it (pressing the clock button) a line which didn´t appear before:

      "RFC call failed: program SLD_NUC not registered / CPI-C error CM_ALLOCATE_FAILURE_RETRY.

      How can I resolve it ?

      I missing a set up ?

      Thanks a lot.

  • Posted on Aug 05, 2004 at 10:53 AM

    Hi,

    if you encounter the symptom that the single server connection to a system works but the Load-balanced connection doesn't, you can try the following two steps:

    1. Check that a logon group is defined in transaction * SMLG * of the R/3 system.

    (If there is none, enter a name, e.g. 'PUBLIC', in the box at the beginning that is empty by default. I'm not sure, but you may have to select the option 'Enable RFC' on the properties tab)

    2. Enter the required R/3 system into your services file on the WebAS server and restart the WebAS afterwards (the restart is necessary).

    You can find the services file in folder

    C:\WINDOWS\system32\drivers\etc .

    Sample entry for a system called 'IDX' with system number 00:

    sapmsIDX 3600/tcp # SAP IDX Message Port

    Hope this helps,

    Ruth

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 20, 2004 at 12:18 AM

    Hi Gurus,

    I had same issue with that. Is there anyone had the solution with that?

    Thanks,

    Bo

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on May 09, 2005 at 03:28 PM

    The problem disappeared.

    Add comment
    10|10000 characters needed characters exceeded