Sie sind auf Seite 1von 5

PC Installation

When you upgrade an SAP System from Release 2.x to Release 3.x, copy the file saplogon.exe to the directory in which the sapgui.exe file was installed. The saplogon.ini file should be saved locally in the Windows directory. You should save the sapmsg.ini and saproute.ini files, however, in the frontend installation directory.

1. In your Windows installation directory, check the sapmsg.ini file.

With Windows 3.1/3.11, the files are normally in the directory c:\windows. With Windows NT they are normally in the directory c:\winnt . The first line must contain the entry [Message Server] . For each SAP System that is available, the following entry should exist: <SID> = <host name on which the message server is running> .

[Message Server] C11 = hostname.yourdomain O01 = oss001 saproute.ini The first line must contain the item [Router] For each possible network connection, the following entry should exist: <route name>=<route> Here <route> is formulated as: /H/<hostname on which the SAProuter is running>/S/<service> You can concatenate several of these strings if the connection uses multiple SAProuters.

[Router] SAP Walldorf=/H/hostname.your.saprouter/S/sapdp99/H/ /sapdp99

SAP Foster City=/H/hostname.your.saprouter/S/sapdp99/H/ /sapdp99

2. Ensure that the services file (with Windows 3.1/3.11 normally in the directory c:\windows ) for each
system contains the following entry in the sapms.ini file: sapms<SID> <nr.>/tcp

sapmsC11 3670/tcp sapmsO01 3616/tcp The configuration data is stored in the saplogon.ini file in the Windows installation directory. You can configure the file names and the path specifications of the saplogon.ini file as you like. You should also save this individually-configured file locally. If you are the administrator and want to preset a particular selection for the user, you can either deactivate: selection options for Group Selection and Server Selection unrestricted user logon

To deactivate the selection options for Group Selection and Server Selection:
To log on to the system, you only need the saplogon.ini file. If sapmsg.ini and saproute.ini are not available locally, the selection options are not available to the user. Alternatively, you can call the saplogon.ini file and insert the entry Restricted Mode=1 in the Configuration section. To be on the safe side, save saplogon.ini as a write-protected file. You could also set the environment variable to slg_restriction=1 for the entire system.

To deactivate unrestricted logon for the user:

You can use the saplgpad program so that users cannot edit or log on freely to the SAP Logon. To log on to the system, you only need the preconfigured file saplogon.ini .

sapmsg.ini and saproute.ini are not required at runtime. saplgpad and saplogon use .ini files from the installation directory. If no .ini files are available in the installation directory, the programs access the Windows directory. If the system still cannot find any .ini files, saplogon creates saplogon.ini in the Windows directory as well as sapmsg.ini (if this is required). When the user logs on, the system displays the SAP Logon. This only contains the selection list.

Configuring Logon Groups

In SAP Logon, you can create and delete group entries, remove instances from groups, and delete entire logon groups. When you call transaction SMLG, the CCMS: Maintain Logon Groups screen shows a table with entries for logon groups and the associated instances. An entry in this table, which is characterized by an instance and a logon group, is known as as assignment. A logon group to which multiple instances belong therefore consists of multiple assignments in this table, where an assignment contains one instance in each case.

Creating a Logon Group or Adding an Instance to a Logon Group


Choose CCMS Configuration Logon Groups, or call transaction SMLG.

2. Choose (Create Assignment), and specify the desired name of the logon group in the Logon Group input field. Enter the name of the desired Instance that is to belong to the logon group. The logon group SPACE is reserved for SAP; therefore, do not use this name. 3. 4.

Repeat the last step until you have entered all instances that are to belong to the logon group. Save your changes.

Deleting a Logon Group or Removing an Instance from a Logon Group 1. Choose CCMS Configuration Logon Groups, or call transaction SMLG. 2. Select any assignment for the logon group that you want to delete or from which you want to remove an instance. 3. To remove an instance from the selected logon group, choose instance on the next screen, and confirm your choice by choosing 4. To delete the desired logon group, choose (Delete) on the next screen. 5. Save your changes.

Remove Instance, enter the desired (Delete).

Delete Group and confirm your choice by choosing

Changing Properties of an Assignment, a Logon Group, or an Instance 1. Choose CCMS Configuration Logon Groups, or call transaction SMLG. 2. To change the properties of an assignment, double-click the assignment, and switch to the Properties tab page. 3. You can change the following properties: IP address of the application server Only enter a value in this field if the application server associated with the instance needs to be addressed by the front end with a different IP address to the one used for application server-internal communication. This value applies only for the selected assignment. Settings for external RFC call You can use this indicator to determine whether logon using an external RFC connection is to be permitted. This value applies to the selected logon group. Threshold values for dialog response time and number of users logged on If you log on using a logon group, the logon is automatically performed using the instance of the group that currently has the best dialog quality. This quality is a key figure that is calculated from the number of users logged on and the average dialog response time. To allow the different prerequisites of different instance to be taken into account in this calculation, you can set threshold values for the dialog response time and the number of users yourself. The larger the actual values for response time

and the number of users are in comparison to the threshold values set, the lower the quality. These figures apply for the selected instance.

The values for Response Time and Users are not absolute limits, but rather thresholds. Even if the current value for response time or number of users is higher than this threshold value, it is possible to log on to another instance. The threshold values only influence the calculation of the current logon server of the logon groups. You can use a preview to see how the settings of the threshold values can affect the quality calculation, based on the current performance data. Choose Test to do this. In a logon group, the instance with the highest quality key figure is always selected for the logon. 4. Choose Copy, and save your changes.

Recommendations for Logon Load Balancing and Logon Groups

Definition Logon Load Balancing
Logon load balancing increases efficiency with respect to performance and the use of system resources for variously defined workgroups by distributing users across available application servers based on requirements for workgroup service and utilization. In a system landscape where there are multiple application server instances, specific servers are best assigned to a particular application workgroup, with the available resources and buffers of that server tuned specifically to that application and not shared with other applications. This is highlighted in the following sections:

With logon load balancing and servers assigned to specific applications: Logon Group FI/CO Logon Group SD
Server A FI/CO Server B FI/CO Server C SD Server D SD

With logon load balancing and shared, or homogeneous, properties of servers across logon groups: Logon Group FI/CO Logon Group SD
Server A FI/CO Server B FI/CO Server C FI/CO Server C SD Server D SD Server E SD

Not recommended:
With logon load balancing and servers available to all applications:
Logon Group PUBLIC
Server A FI/CO + SD Server B FI/CO + SD Server C FI/CO + SD Server D FI/CO + SD

With only two servers with logon load balancing and servers assigned to specific groups: Logon Group FI/CO Logon Group SD
Server A Server B

Logon Groups
Each SAP application has different resource requirements. Certain applications may therefore require more servers and logon groups. For example, you should assign separate servers for the application component PP. Generally, each logon group should have two servers. If one server is not available, the users are automatically connected to the second server. Servers can be added or removed while the SAP system is running. If it is not practical for you to assign separate servers to integrated applications such as the application components SD-MM and FI-CO, you should assign common logon groups to these applications.

Checking the Logon Load

You can check the logon load by displaying a list of the servers that are available and an overview of load distribution in your system.

1. Choose CCMS Configuration Logon groups Goto Load distribution.
This list also shows the current performance status of the application servers that are both assigned to logon groups and currently running. Every five minutes, or after every five logons, each application server writes its own performance statistics data to a memory-resident table on the message server. The current logon server is refreshed for each group.

2. To refresh the performance status of an application server, double-click an application server line in the
Instance column. To display which users are logged on:

3. Choose Goto Back and then choose Goto User list.

The list shows how users are distributed over the different servers, and whether a particular server is full. You can sort this list by: o o o o user instance terminal time of the last user action.