This note is only intended for checking the contents of the Saplogon.ini file used in SAPlogon.
If you have found incorrect contents (attributes) in an entry, such as invalid server names or IP addresses, you should NOT edit the saplogon.ini manually. Instead, start SAPlogon and correct the entry.
Your systems administrator can manually edit the Saplogon.ini-file or you can edit it yourself as a systems administrator only if you have no other way of correcting the entry, for example, if you cannot start SAPlogon or if several saplogon.ini files are to be combined (however, we do not recommend this).
This first part of this document contains a description of the file format used for the saplogon.ini file used by SAPLogon and the SAP Session Manager(up to the 46D GUI), and the second part contains a description of how to repair an entry with incorrect content (attributes) in the SAPlogon.
1. Description of the format of Saplogon.ini
Here, the list entries in SAPLogon or the Session Manager are designated as a 'SAP link'. The configuration data is correspondingly referred to as 'link data'.
The file format basically uses the standard Microsoft Windows INI file implementation as a reference, for more information, see the Microsoft Windows help.
The file contains the following sections:
1. Sections with program-specific parameters
1.1 [Configuration]
Configuration data for the SAPlogon program that was saved by SAP logon after you made the settings on the "SAP Logon configuration" dialog box (this dialog box appears when you click on the icon to the left of the "SAP Logon" title in SAPlogon and call the "Options ..." menu).
1.2 [MSLast]
last selected SAP System link
1.3 [Storage]
last window position of the SAPLogon processing dialogs
1.4 [LogonWindowPos]
last window position of the SAPLogon program.
1.4 [MSWinPos]
The position of the dialog for group or server selection
2. Sections of the list entries
The list entries are also saved in sections. The sections are divided into required fields and optional fields. Required fields must always be maintained. The logon is not successful without correct settings or if the settings are missing. The sections contain the respective link data to an SAP link. In entries can exist under these sections. At present, the limit is 1000 entries. These entries are identified using an index: Item1...Item1000.
All section entries with a certain index belong to an SAP link. (thus all fields of the different sections, for example, those which begin with Index1.)
2.1 Sections of the required fields
2.1.1 [Description]
Description of an SAP link as it appears in the SAPlogon.
The description can be any length but it should be kept to a size in which it can be maintained (up to 50 characters).
In the case of a manual entry, we recommend that you maintain the SAP System ID (SID) with the first three characters in upper case. This is a precondition so that the Sap shortcut or SAP Session Manager works correctly because the first three characters from the description of a manual entry for Sapshortcut or SAP Session Manager are required in order to determine the SAP System ID (SID).
2.1.2 [Origin]
Type of lists entry:
MS_SEL_GROUPS = group-based logon, corresponds to load distribution
MS_SEL_SERVER = server-based logon using message server
USEREDIT = entry carried out manually without message server.
2.1.3 [Server]
The application server is entered in this section. If the SAP link is defined as a group-based logon (MS_SEL_GROUPS), the name of the user group of load distribution is entered here instead of the application server host name.
2.1.4 [System]
The SAP System version is defined in this section.
3 = R/3 System
2 = R/2 System
2.1.5 [Database]
SAP database number. This number is used to determine the TCP port for communication with the SAP System. This number has two digits and accordingly can contain values from "00" to "99".
If the system entry was created by the group or server selection (the value under the [Origin] selection is MS_SEL_*), this number was calculated automatically by the relevant message server and written into the saplogon.ini file.
With user-specific system entries (the value under the [Origin] selection is USEREDIT), this number was specified by the user.
For server selection entries (Origin: MS_SEL_SERVER, MS_SEL_SERVER_SNC) and the user-specific system entries, a connection to the relevant system can only be set up if this number is correct.
For the group selection entries (Origin: MS_SEL_GROUPS, MS_SEL_GROUPS_SNC), a connection is still set up for the system with the system ID (under section [MSSysName]) if this number is incorrect. However, we recommend that you correct this number or delete the affected entries in SAP Logon and create new entries accordingly.
2.1.6 [Address]
The IP address of the application server is stored in this section.
If the SAP link is a group-based logon (MS_SEL_GROUP), the IP address of the favoured application server is entered here. This application server is determined when a new entry is inserted and saved in the Saplogon.ini.
The application server that is actually chosen during logon does not depend on the favored application server saved in the Saplogon.ini., rather it is determined for the logon time.
If this saved IP address is invalid, you can delete the string of the IP address (but not the whole line) so that the line looks similar to the following:
after: before:
Item12= Item12=10.10.10.10
This maintenance is not absolutely necessary.
2.1.7 [MSSysName]
The SAP system ID (SID) is saved in this section. The SID is a three-digit abbreviation for the short specification of the SAP target system. For a link configured manually (USEREDIT), the SID is missing. However, you can insert it here.
2.1.8 [MSSrvName]
The host name of the message server is saved in this section.
2.2 Sections of the optional fields
2.2.1 Router-specific fields
2.2.1.1 [Router]
Router specification for the router to the application and message server. In the field, the router string to the message server and to the application server is specified.
2.2.1.2 [RouterChoice]
This section informs you whether different router strings exist for the link to the application server or message server.
1 = different router strings for application server and message server are used. (--> see Router2)
0 = the same router string for appl.server and message server.
2.2.1.3 [Router2]
In this section the router strings are defined for the application server if there are different strings for message and application servers. Otherwise, the entry is empty. (See also RouterChoice)
2.2.2 Language support (Native Language support)
2.2.2.1 [Code page]
In this section the code page of the client can be defined, this way the local installation of the client is ignored.
The number of the code page is saved in this field. The number is set as a default to 1100, if another code page is used, it appears here. The setting can be changed using the extended dialog in the SAPlogon.
2.2.2.2 [Code page index]
-1 = default code page is used: 1100
0 to nn = index on the language ID according to the sequence in the selection box in the extended dialog in SAPlogon.
2.2.3 SNC Support (Secure Network Settings)
2.2.3.1 [SncName]
The SNC name defined in the relevant SAP System.
2.2.3.2 [SncChoice]
The required SNC level:
-1 SNC not possible
0 SNC possible but not activated
1 SNC authentication
2 SNC integrity
3 SNC encryption
9 SNC max. availability
2.2.4 Connection speed [LowSpeedConnection]
1 Low Speed Connection activated
0 Low Speed Connection deactivated
2.2.5 Other sections
2.2.5.1 [SessManKey]
Unique key together with the use of the Session Manager. The numbers appearing here must be unique in this section, that is, no number may appear twice. This number is used for internal communication between Session Manager and SAPlogon.
This section is no longer relevant in 6.x GUI because Session Manager has not been delivered since 610 GUI.
3. Optional Sections
3.1 [MSSrvPort]
In this section, the port number of the TCP link is saved. The entry need not be entered, SAPlogon rather determines this value by a request in the message server.
When you define the saplogon.ini file, this section can be omitted, SAPlogon creates this automatically and fills it when it is used.
If this number is maintained incorrectly, no connection to the relevant message server can be set up. The incorrect number must be corrected.
2. Repair the entry with incorrect contents (attributes) in the SAPlogon
a) Start SAPlogon.
b) Click on the SAPlogon icon (above left on the title bar) and call the 'options' menu.
c) The path for the file name saplogon.ini is displayed under 'Configuration files' in the 'SAPlogon configuration' dialog box as, for example:
C:WINNTsaplogon.ini
Copy this file to another file, such as:
C:WINNTsaplogon_error.ini
d) Close the 'SAP Logon configuration' dialog box.
e) Select the entry that you want to correct.
f) Check whether the entry can be repaired using attribute maintenance ('attribute' and 'Other ... ' button, if necessary).
g) If this is the case, you need not follow the steps below.
h) If you cannot make repairs using attribute maintenance, proceed as follows:
Select the entry that you want to correct.
Choose the 'Delete' button (if a warning message appears, simply confirm it) to delete the entry.
Then input a new entry with the same attributes of the deleted entry. In other words,
if the deleted entry was generated by group selection, the new entry should be generated with the same group and the same attributes.
If the deleted entry was generated by server selection, the new entry should also be created with the same application server and the same attributes.
If the deleted entry was generated by User-Edit ('New...' button), the new entry should have the same definition and attributes as the deleted entry.
To help you remember the attributes of the deleted entry, you can use the following command line to start SAPlogon with the saplogon_error.ini (before inserting the new entry):
saplogon.exec /INI_FILE=C:WINNTsaplogon_error.ini
You can then display the attribute of the entry to be repaired in the restarted Saplogon, which makes it easier to insert the new entry in the original Saplogon.