While waiting for the DD ACTIVATION phase of an add-on installation to finish, my mind wandered off to something I’d noticed with my new WAS 6.40 testdrive for Linux is here! system, with the SID “NW4” (NetWeaver ’04). Normally, when you start transaction OSS1, and hit the button to connect to OSS, you’re presented with a popup giving you a choice of groups, like the one in the screenshot here.
But it wasn’t happening from my NW4 system. So I rolled up my sleeves, and wielded the mighty “/h” in the ok-code (in the R/2 days we used to call this “hobble mode” :-), cleaving my way into the ABAP that lay beneath OSS1. What I found was quite interesting.
There’s a command-line program called lgtst that can be used to query the message server of an SAP system and have information on logon groups and so on returned. This lgtst program is not, apparently, supported on all operating systems, so there’s a condition in the ABAP that checks that.
Direct SAPGUI call
If the server’s operating system is not supported, then a simple logon string is constructed from the technical settings held in OSS1 (menu path Parameter -> Technical settings). For example, if you specify a SAProuter at your site thus:
Name: host01 IP Address: 192.168.0.66 Instance: 99
with SAProuter details thus:
Name: sapserv3 IP Address: 18.104.22.168 Instance: 99
and the SAPnet message server details thus:
Name: oss001 DB Name: O01 Instance: 01
then the route string constructed is just the concatenated saprouters leading to the dispatcher at O01’s ’01’ instance, like this:
This route string is then used in conjunction with a direct local call to your SAPGUI client, so that the end result is that a new SAPGUI instance is started for that connection.
So far, so good (or not, depending on your luck with SAProuter routing :-).
Logon group popup, then SAPGUI call
On the other hand, if the server’s operating system is supported, then something rather different happens. In this case, the lgtst program is executed on the server, to discover what logon groups are available for OSS. How does this happen? Well, the SAProuter information we’ve already seen is used to construct a route string:
but, instead of pointing to a dispatcher at the SAP OSS end:
it points to system O01’s message server:
Once this route string has been constructed, it’s used in a call to lgtst like this:
lgtst -H /H/.../H/oss001/S/sapmsO01 -S x -W 30000
This is basically requesting that the message server for O01 send back information on available servers (instances) and logon groups. A typical reply looks like this:
list of reachable application servers ------------------------------------- [pwdf1120_O01_01] [pwdf1120] [10.16.0.11] [sapdp01]  [DIA UPD BTC SPO ICM ] [pwdf1302_O01_01] [pwdf1302] [22.214.171.124] [sapdp01]  [DIA BTC SPO ICM ] [pwdf0936_O01_01] [pwdf0936] [10.16.0.19] [sapdp01]  [DIA BTC SPO ICM ] [pwdf0810_O01_01] [pwdf0810] [10.16.0.18] [sapdp01]  [DIA BTC SPO ICM ] [pwdf1307_O01_01] [pwdf1307] [126.96.36.199] [sapdp01]  [DIA BTC SPO ICM ] [pwdf1300_O01_01] [pwdf1300] [188.8.131.52] [sapdp01]  [DIA BTC SPO ICM ] [pwdf1301_O01_01] [pwdf1301] [184.108.40.206] [sapdp01]  [DIA BTC SPO ICM ] [pwdf1177_O01_01] [pwdf1177] [10.16.1.13] [sapdp01]  [DIA UPD BTC SPO ICM ] [pwdf0937_O01_01] [pwdf0937] [10.16.0.20] [sapdp01]  [DIA BTC SPO ICM ] [pwdf0809_O01_01] [pwdf0809] [10.16.0.17] [sapdp01]  [DIA BTC SPO ICM ] [pwdf0808_O01_01] [pwdf0808] [10.16.0.16] [sapdp01]  [DIA UPD BTC SPO ICM ] [pwdf0807_O01_01] [pwdf0807] [10.16.0.15] [sapdp01]  [DIA BTC SPO ICM ] [pwdf0392_O01_01] [pwdf0392] [10.16.0.10] [sapdp01]  [DIA BTC SPO ICM ] [o01main_O01_01] [pwdf1070] [220.127.116.11] [sapdp01]  [DIA UPD ENQ BTC SPO UP2 ICM ] list of selectable logpn groups with favorites ------------------------------------------------ [1_PUBLIC] [18.104.22.168]   [2_JAPANESE] [22.214.171.124]   [DO_NOT_USE] [126.96.36.199]   [EWA] [188.8.131.52]   [REPL] [10.16.1.13]   [SPACE] [10.16.1.13]  
What we’re interested in are the lines in the second half of the output – the list of selectable logon groups. The key data items here are the group names themselves (e.g. 1_PUBLIC), the IP addresses (e.g. 184.108.40.206), and the port numbers (e.g. 3201). The ABAP behind transaction OSS1 receives this lgtst output and parses it out into a nice list of groups, which it then presents to the user as shown in the screenshot above.
(And it goes almost without saying that if the call to lgtst fails, we get that friendly message “Unable to connect to message server (default connection will be used)” and revert back to the direct SAPGUI call).
So that’s where this popup comes from. Ok. Now I understand. It’s amazing how you use a transaction for years and never really look into how it actually works.
Why not Linux?
So, just to get back to why I came here in the first place – why doesn’t this popup appear in NW4? NW4 is a Linux-based testdrive system. lgtst works fine. But look at this:
*---- Folgende Betriebssysteme werden unterstützt IF ( SY-OPSYS = 'HP-UX' ) OR ( SY-OPSYS = 'AIX' ) OR ( SY-OPSYS = 'OSF1' ) OR ( SY-OPSYS = 'SINIX' ) OR ( SY-OPSYS = 'SunOS' ) OR ( SY-OPSYS = 'Windows NT' ) OR ( SY-OPSYS = 'Relia' ) OR ( SY-OPSYS = 'SP_DC' ) OR ( SY-OPSYS = 'OS/400' ).
No Linux? Hmm, I soon fixed that, by copying the transaction (OSS1 -> ZSS1) and the ABAP behind OSS1 (RSEFA910), adding a line to this IF statement to bring a bit of love the choice operating system of a “Gnu generation” 😉
Now I can call ZSS1 and delight in the group logon popup. Hurrah!