There are several alternatives for where to store the GuiXT profile:
1. Windows Registry
GuiXT uses the following logic: First it searches a file “guixt.ini” in the current program directory (see below). If the file is found, and if there is an entry
in the file, the profile options are taken from guixt.ini; otherwise they are taken from Windows registry.
Using the command
in the local guixt.ini file, you can switch to a second, centrally stored guixt.ini file. It can be on a network file server, on an http/ftp server, or in SAP web repository in the SAP database. In the case of web repository, or if you use an &database variable in the “switchto” file name, the guixt.ini file is read separately for each SAP system.
Where is guixt.ini searched?
C:\Program files\SAP\Frontend\SAPgui (SAP GUI 6.20, 7.10)
C:\Program files\SAPpc\SAPgui (SAP GUI 4.6D)
C:\Program files\SAP\ITS\2.0\programs (ITS)
With Help->About->Loaded dlls in SAP GUI you can display the location of the SAP GUI dlls and guixt.dll.
1. Windows Registry
How to proceed: No guixt.ini file. Or, if guixt.ini exists: no “IgnoreRegistry Yes” in this file.
The registry entries can be found in
Changing them directly (e.g. using regedit) instead of GuiXT profile editing is possible as well, but can be dangerous, as with any direct registry manipulation.
When you use a tool that is able to change registry entries centrally for all users, storing the GuiXT profile in registry is a reasonable method even for large numbers of users. Without such a tool, using a central guixt.ini is the better approach.
2. Local guixt.ini
How to proceed: Create a guixt.ini file and use “IgnoreRegistry Yes”
The names of all guixt.ini parameters can be found in profile documentation . You can also use help function in GuiXT profile editing (click on the “?” symbol). An additional hint: GuiXT Designer allows us to generate a guixt.ini file from Windows registry.
3. Central guixt.ini
How to proceed: Create a guixt.ini file, use “IgnoreRegistry Yes” and “SwitchTo”
In the local guixt.ini, you name the central guixt.ini file (e.g. \\server12\GuiXT\guixt.ini) in the “SwitchTo” command:
If this central guixt.ini is not found, for example if the server is not running, GuiXT continues with the next statement in local guixt.ini. Thus you can use several “SwitchTo” commands pointing to different servers if necessary:
4. System specific guixt.ini
How to proceed: Create a guixt.ini file, use “IgnoreRegistry Yes” and “SwitchTo SAPWR:…” or “SwitchTo ….&database…”
When using SAP web repository, please specify RFC user and password for the web repository access before the SwitchTo statement. Special GuiXT start options (StartMinimized or StartHidden) are also put in the local guixt.ini, before the SwitchTo. Example:
For web repository access, client 000 is used. You can also specify a different client, using the notation “SAPWR,client=xxx”. Example:
If it is not possible to read the system specific guixt.ini for a certain system (since it does not exist, or since the RFC user is not valid), no error message is issued, and GuiXT remains inactive for this system You will find a log entry in the GuiXT window when you click on View->Protocol.
As a further example, a system specific guixt.ini using the “&database” variable:
When the user logs on to the SAP system P46, for example, GuiXT reads the file http://www.xxx.com/guixt/ini/guixt.P46.ini. For UNIX web servers, please observe upper/lower case characters in the file name. The system id “&database” is put into the file name in upper case.
A final remark: You can also combine 3 and 4, i.e. using SwitchTo to a central guixt.ini where you set the RFC parameters and then use a system specific SwitchTo.