Show TOC

Provision of Administrator Configuration FileLocate this document in the navigation structure

The administrator configuration file can be provided either by pull request or by push request.

Provision by Pull Request
If the administrator configuration file is provided by pull request, it is located in a central, shared storage such as a remote share or an HTTP platform. The administrator must specify the path to the administrator configuration file. Therefore, the administrator defines the path for the key Name: LandscapeFileOnServer in the following locations:
  • HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPLogon\Options (32 bits) (REG_EXPAND_SZ)
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPLogon\Options (64 bits) (REG_EXPAND_SZ)
The local client can then retrieve the administrator configuration file from the central storage.
Note

Paths to the administrator configuration file can also be defined in the environment variable SAPLOGON_LSXML_FILE. For more information, see the last section on this page.

Tip Having configuration files located on a central share or platform facilitates the update process of the files, and no deployment effort is required.

The concept described above is illustrated by the following figure:

Provision by Push Request
The administrator distributes (pushes) the administrator configuration file, for example with SAPSetup or another software distribution tool, from his central data storage repository to the clients. SAP Business Client then retrieves the administrator connection configuration from the local client, according to the path which is defined in the registry for the key Name: LandscapeFileOnServer in the following locations:
  • HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPLogon\Options (32 bits)
  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPLogon\Options (64 bits)
Note

Paths to the administrator configuration file can also be defined in the environment variable SAPLOGON_LSXML_FILE. For more information, see the last section on this page.

The concept described above is illustrated by the following figure:

Environment Variable SAPLOGON_LSXML_FILE

You can use a new environment variable SAPLOGON_LSXML_FILE to make your own landscape files (SAPUILandscape.xml and SAPUILandscapeGlobal.xml) to be used by SAP Business Client as in the former SAP GUI for Windows releases (see the related SAP Note 38119 Information published on SAP site ).

The value for the environment variable SAPLOGON_LSXML_FILE should contain a full path to the User Configuration File (Path). The folder in which this file is contained must also contain both the administrator and user configuration files, as detailed in the following points:

  • The value for this environment variable SAPLOGON_LSXML_FILE should contain a full path and a file name like SAPLOGON_LSXML_FILE=C:\Saplogon\SAPUILandscape.xml.

  • The SAPUILandscapeGlobal.xml file must be also provided under the same path like C:\Saplogon\SAPUILandscapeGlobal.xml.

The searching order of the landscape files in SAP Business Client is as follows:

  • Files set in the directory path from the environment variable SAPLOGON_LSXML_FILE

  • Files set under Administrator Configuration File and User Configuration File (Path) options in the SAP Business Client Personalize dialog box

  • Files set in the registry by the Administrator

If the files are not found using any of the searches outlined above, SAP Business Client starts the data migration automatically and tries to create the SAPUILandscape.xml and SAPUILandscapeGlobal.xml files according to the old configuration file settings, provided that the files can be written under the specified path.

For more information, see SAP Note 2075150 Information published on SAP site.