SAPGUI 640 Logonpad ???

[Former Member]

hi there,

we are upgrading vom sapgui 620 to 640. we do it with software distribuation tool, to roll it out to 700 clients here.

i have the following problem: i want to have a 'flexible' sap-logon-pad. the reason is that in the next month systems are changed/upgraded, get a new System-ID, and so on..............meaning that the values in the sap-logon-pad will change from time to time.

i want to have ONE(!!) sap-logon-pad for all users. but how should i distribute this to all our clients every time it is changing ?

reg, Martin

[Matt_Fraser]

Martin,

You are in luck. There is a way, assuming that you are using an installation server as the central SAPGUI distribution point as described in the FrontEnd Installation Guide.

When you upgrade your clients, make sure you have defined a "package" on the installation server (using SAPAdmin) containing the frontend components you want them to have. Then, use
<server>\<share>\sapgui\setup\sapsetup.exe /p:"<package>" to distribute the upgrade with the packaged components.

Before you roll that out, though, you'll find (or create) a "custom" folder under the "sapgui" folder on the installation server. In this folder place a copy of saplogon.ini and sapmsg.ini from a client configured the way you want the rest to be configured. When the clients install or upgrade, they will automatically get these versions of the saplogon.ini and sapmsg.ini without you having to do anything else.

If you are using logon load balancing on your SAP server (and you probably are, with 700 clients), then you'll also need to add a custom entry to the services file (c:\windows\system32\drivers\etc\services) on each client to represent your SAP message server. You can automatically distribute this entry without having to completely replace the services file by editing the guisetup.xml file found in the \sapgui\setup folder on the installation server. Open this file with Notepad or an XML editor and search for "System Modifications". This will lead you to the area of the file where the services file entries come from. Just after the "System Modifications" comment, there's a CDATA section containing a list of entries like

sapdp00; 3200/tcp;;

sapdp01; 3201/tcp;;

etc. You can edit this section to remove entries you don't need, but you will probably need to ADD one entry for your message server, as follows:

sapmsSID; 3600/tcp;;

Replace SID with the actual SID of your system, of course. After you're done, you might want to open the file with Internet Explorer and see that it reads through to the end, just to make sure that it's still well-formed.

Now you're all set for the current SAPGUI upgrade. Now, when you later want to change the SID or other SAPLogon entries and distribute that to everyone, you edit the saplogon.ini and sapmsg.ini files in the custom folder, and the guisetup.xml file in the setup folder, with the appropriate entries. However, to trigger clients to receive the update, you have to do one extra thing in the guisetup.xml. In the "System Modifications" area where you have the services file entries, there's a "component guid" line. In this line is a parameter 'version="1"'. Increment the version number by one. Then, just above this section is another "component guid" line with 'name="$CustomerConfigFiles"'. Increment the "version" by one for this component, too.

Once you've done this, the clients should auto-update the next time they start SAPLogon. However, if for some reason they don't, then you can use logon scripts to have them run "sapsetup.exe /update" from the installation server, which will definitely do it. The clients will also auto-update when you apply a new patch to the installation server via SAPAdmin.

You can find more information about this process in Note 512040.

I trust this has answered your question.

Best regards,

Matt