Skip to Content

AS ABAP Sneak Preview Lessons: Logon Groups

The other day I wrote about my experiences while trying to repair my ABAP Netweaver Sneak Preview installation after a computer rename. Today I wanted to write about another “opportunity to learn” that I encountered while trying to write a Java WebDynpro application on my local systems.

SLD Setup
My goal was to create a Java WebDynpro application that ran on my local Netweaver installation that could access data from the local ABAP sneak preview system. I was using Adaptive RFC to make the calls from Java to ABAP. For those of you who have worked with Adaptive RFC, you know that there are several setup steps that must be done.

First you have use the SLD to store all your system information. Adaptive RFC will only connect to a system that is setup in the SLD. So my first goal was to get my ABAP Sneak Preview system installed into my Java system’s SLD.

I had already gone through the SLD’s Post-Installation setup guide and I had the Local Java system information populating just fine. I figured all that I had to do was go into transaction RZ70 inside the ABAP system and send my information over to the SLD.

On my first try, the call to the SLD failed. I was getting Gateway registration errors. I even went directly to SM59 and tried just testing the SLD RFC destination (SLD_NUC) and I continued to get gateway errors. After looking in the gateway logs (transaction SMGW), I found entries where it looked like the system was trying to connect to the gateway on a hostname that had been truncated. I just recently corrected my problems following the computer rename, so this seemed rather ironic. My computer name was very long: 13 characters. I incorrectly assumed that this truncation was the problem and that gateway communications were failing because my hostname was too long. Later I would find out the truth was quite different and that this truncation was probably just the harmless shorting of a variable within an error message.

I thought that I had found a problem that I couldn’t work around. After all I couldn’t change my computer name to be shorter. I thought I would just have to work around the problem by manually entering my ABAP system information into the SLD.

Adaptive RFC
With my ABAP system information finally resting comfortably in my SLD, I was ready to finish the Adaptive RFC setup for my WebDynpro application. Inside the WebDynpro Content Administrator, each deployed component is shown. Inside the maintenance for each component, you should already see any Adaptive RFC destinations that you created in your application.
Image 1 – WebDynpro Content Administrator

I started by setting up my Model Data Destination. This Adaptive RFC type allows you choose between Load-balanced and single server connections. I am running locally with the sneak preview, so I assumed there was no real reason to go with the load balanced connection. I finished the setup, which grabbed the rest of the connection information from the SLD. The new RFC destination tested fine, so I assumed that my ABAP system was setup correctly.
Image 2 – Application Data RFC Setup

Next I needed to setup the second RFC destination. For ever Adaptive RFC, there are two destinations. The first one I setup is used to make the actual model method calls. This next one is used to retrieve Dictionary Meta Data. However when I reached the screen for the connection type, I learned that the Meta Data connection only support Logon Balanced connections.
Image 3 – Meta Data RFC Setup

I had gone into the ABAP system in transaction SMLG and setup some logon groups. I had even remembered to enter them manually into the SLD information for the ABAP systems. However when I finished the Adaptive RFC setup and did a test, I received a connection failure. Little did I know that I had actually hit upon the same problem that caused my SLD connection to originally fail as well.

The Message Server
I returned to transaction SMLG to try and determine the cause of my problem. Everything appeared to be setup correctly. However when I viewed the Load Distribution for the logon groups, I found it strange that each logon group’s Current Logon Instance was listed as initial. It appeared as though the load statistics were not being populated into the Message Server.

Turning to my trusty friend, the note search on OSS, I soon found a note that gave some background on how this information is populated. According to note 26317, there is a program that should be running every 5 minutes or with every 5th SAPGui logon to populate this information. Could the answer to all my problems really be as simple as logging on 5 times! Sure enough, after logging on 5 times my message server load information now showed up in SMLG.

The root cause of the problem has to do with the instance profile parameter rdisp/autoabaptime. This is the parameter that controls how often the program RSRZLLG0 runs to populate this information. The parameter had a value in my sneak preview system of 0. There is a special check in RSRZLLG0 for value of <= 0. If the program finds this value, it assumes an upgrade is process and doesn’t populate the load statistics. This is also why even if you submit RSRZLLG0 manually, the information doesn’t populate. You can change this instance parameter or just run program rsrzllg0_actual with FRCE_SAV unchecked.

Not only did the properly working Logon Groups fix my Adaptive RFC connection, but it also corrected my inability to automatically send my ABAP information to the SLD. In the end I finally have my application working that combines processing from my local Java and ABAP systems.

You must be Logged on to comment or reply to a post.
  • Starting Java from ABAP point of view definitely holds more interest for the ABAP cult and such detailed information is of great value.

    Thank you.

    Subramanian V.

    • I’ve never thought of us ABAP Lovers as a cult before. 🙂

      Wikipedia defines a cult as:
      a cult is a cohesive group of people (often a relatively small and new religious movement) devoted to beliefs or practices that the surrounding culture or society considers to be far outside the mainstream.

      Thanks to SDN we are a cohesive group.  Most of us are people (no offense meant to EDI).  Relatively small – well there quite a lot of us on SDN, but compaired to the world population we are still a small group.  Devoted to beliefs or practies – yes most ABAP Lovers are quite devoted.  Scarry – I guess we are a cult.

  • Hello Thomas,

    I have installed NW SP15 Java.

    Can I also install NetWeaver ABAP while having the NW Jave already installed?  Having the same database, will that not give me a problem?

    I tried installing NW ABAP at first, and had problems installing it, so I formatted my hard drive, the installed NW SP15 Java successfully.

    Any advice?


    • Yes you can install both.  The two instances can both be installed into the same SAPDB database.  Just be sure to use different instance numbers and IDs for the two systems.  There are some instructions in the Sneak Preview Install forum on how to get both installed.  I started with Java.  When I ran my ABAP installation, the SAPINST did stop very shortly into the installation.  I found the exact error on the forum with a search.  The solution was quite simple – I needed to stop my J2EE server and stop the already installed SAPDB services in the service control panel while I did the ABAP installation.
      • Thomas,

        This is the error I get;

        ERROR 2006-02-23 20:20:04
        MDB-07057  The system is inconsistent. Registry or SAP_DBTech information is available, but software is not complete.
        ERROR 2006-02-23 20:20:04
        MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
        ERROR 2006-02-23 20:20:04
        FCO-00011  The step CheckExistingServerSoftware with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|ind|ind|ind|ind|6|0|Sdb_ServerSoftware_Dialogs|ind|ind|ind|ind|0|0|CheckExistingServerSoftware was executed with status ERROR .

        This error I got in stage 2 of installation ‘Define Parameters’.  I this the error you had?


        • Hi Spiro,

          I have the same problem as you had. Did you get the result in the meantime?

          @ALL: Does anybodyelse has an idea how the solve the following error message:

          ERROR      2006-03-13 18:52:05 [iaxxinscbk.cpp:264]
          MDB-07057  The system is inconsistent. Registry or SAP_DBTech information is available, but software is not complete.

          ERROR      2006-03-13 18:52:05
          MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.

          ERROR      2006-03-13 18:52:05
          FCO-00011  The step CheckExistingServerSoftware with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|ind|ind|ind|ind|6|0|Sdb_ServerSoftware_Dialogs|ind|ind|ind|ind|0|0|CheckExistingServerSoftware was executed with status ERROR .

          INFO       2006-03-13 18:55:14 [iaxxgenimp.cpp:700]
          An error occured and the user decide to stop.\n Current step “|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_CreateDB|ind|ind|ind|ind|9|0|NW_ADA_DB|ind|ind|ind|ind|6|0|Sdb_ServerSoftware_Dialogs|ind|ind|ind|ind|0|0|CheckExistingServerSoftware”.

          Exit status of child: 1

          Thanks and Regerds

  • Thanks very much for this tip, much appreciated. After struggling with this problem for a couple of days, I followed your directions and everything now works like a charm.

    Best Regards,

  • Hi,

    This article was useful for me to create SLD, and JCO data connection. But when I try to create a Jco metadata channel I get a “Logon group SPACE not found” exception while trying to test the connection.

    As per the blog I tried to login 5 times still I get the same exception.

    What might be the problem.

    I tried to login in SAP GUI using logon group. But the group/server option in SAP GUI is constructed automatically , it is not taking my values. If this might be the soultion pl let me know how to enable the group/server option in SAP GUI.

    Thanks in advance.


    • Have you tried running rsrzllg0_actual with FRCE_SAV unchecked? This solution however was something I found in relation to the Sneak Preview system.  That is just one possible problem/solution in a NetWeaver system around logon groups.  Your situation may vary.
    • Hi Srini.

      Try to create another logon group than the default Space. Remember to check the option “Ext. RFC-Enabled” on the creation process, on transaction SMLG (Attributes Tab). Then go to SE38 and execute the program rsrzllg0_actual with FRCE_SAV option unchecked. This is what I did and worked fine. Only thing I’m trying to figure out is how to set this program to run periodically (like it should?), because everytime you boot the server you have to do it all again 🙁
      Hope it helps, let me know if it worked.

  • Hi Thomas,
    I encountered the same problem when setting up the connection between my CE 7.1 EHP 1 and my NSP 7.01. Thankfully, somebody in the forums pointed me to your 2006 blog, which is still valid. Running the R…_ACTUAL report made the logon group I had configured usable both in Saplogon and in the Web Dynpro Content Administrator.