"XML Configuration File in Server" caching problem

[Former Member]

Hello,

I have a caching problem with "XML Configuration File in Server" option in SAPGUI.

See SAP note 1426178 - SAP Logon (Pad): create/distribute server configuration file

I set up a Apache Webserver with standard settings, that distribute SapLogonTree.xml to SAPGUI clients.

If I change the saplogon.ini, SapLogonTree.xml on server side,

a restart of SAP logon pad does not read the new files.

It does also not help to delete files in "Path for caching" or remove "XML Configuration File in Server" option and configure it again. Old files are cached in Internet Explorer browser cache.

The only thing, which forces update is to clear Internet Explorer browser cache or set up a htaccess file to forbid browser-caching.

Has anyone similar experience ?

Best regards,

Tibor

[Matt_Fraser · Accepted solution]

Hi Tibor,

If you distribute SapLogonTree.xml locally to each client, then you aren't setting them up to use a central shared configuration file. You don't need to distribute any configuration file to the client if you want them to use a central shared one; you just need to set the appropriate registry setting to point the clients to the central file.

I describe how to do this in detail in the Created Shared Configuration Files section of my document .

Best regards,

Matt

[Former Member · Accepted solution]

Hi Matt,

Now I got it. Only \\server\... is allowed.

I used:

http://username:password@server.domain.com/sapgui/pad/SapLogonTree.xmlpassword@server.domain.com/sapgui/pad/SapLogonTree.xml

I never realized this in SAP note, because my first try was http:// and it worked too.

You get an error message, if the file can not be loaded and

there is no error message, if the file can be loaded.

It is just cached 'somewhere' in the OS, if you use http://

I moved to \\server\... and everything is fine now.

A check for only supported '\\...' would be helpful.

thx.

Tibor

[Matt_Fraser · Accepted solution]

Glad to hear it's working now. That's right, unless you configured your installation server somehow as a web server, but "out of the box" it isn't, it is a collection of files sitting on a network file share, plus a running service on the server if you use LSH.

Best regards,

Matt

[Former Member]

It looks like SAPGUI 7.40 PL6 will fix the caching problem with http://

SAP note 2207460 - SAP Logon (Pad): refresh problem for server Configuration ini files via HTTP

Symptom 

In SAP GUI 730 and 740 without NWBC installed, you can set "XML Configuration File on Server" to a server file via http like: http://mywebserver:port/SAPLogon/SapLogonTree.xml 
This server file contains the saplogon.ini and sapshortcut.ini files that are also on the same server side, as defined in the <Files> block: 
  <File type="Connections" name="http://mywebserver:port/SAPLogon/saplogon.ini" />   <File type="Shortcuts" name="http://mywebserver:port/SAPLogon/sapshortcut.ini" /> 
If you update the SapLogonTree.xml file like renaming a node name and restart SAP Logon (Pad), you can see the update in SAP Logon (Pad)  window immediately. 
However update in the ini files like renaming a connection/Sapshortcut name will not be shown in SAP Logon (Pad) window if your IE option  "Check for newer versions of stored pages" is set to "Automatically" that is default.

...
The issue described above will be fixed by SAP GUI for Windows 730 patch 15 and 740 patch 6.
...

SAP note 1053737 - Expected release dates for SAP GUI for Windows

- 730: Patchlevel 15 (last Patch) is expected to be shipped in week 43 2015 (19th - 23rd of October 2015)

- 740: Patchlevel 6 is expected to be shipped in week 52 (21st - 23rd of December 2015)