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.
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. NWBC
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)
.
The concept described above is illustrated by the following figure: