Configuring SAP Systems via Profile Parameters

Objectives

After completing this lesson, you will be able to:
  • Describe profiles used for system configuration
  • Describe the evaluation sequence of profile parameters
  • Display profile parameters and their values
  • Maintain profile parameters
  • Monitor configuration changes

Profile Files Used for System Configuration

When an SAP system is being installed, at least two profile files are created automatically. One is the default profile with profile parameters that are valid system-wide. The other one is an instance profile created for each instance with which profile parameter values can be configured for a specific instance.

As the figure Profile Files at Operating System Level shows, after the installation is complete, the profile files are stored at the operating system level in the directory: /usr/sap/<SID>/SYS/profile. This directory can be read by all instances of an SAP system using the share or mount technique.

The figure Profile Files: Naming Convention displays the naming conventions for the available profile files.

There is only one default profile (DEFAULT.PFL) for each SAP system and it is read by all instances during the startup procedure. It contains system-wide settings, such as the system name, the name of the database server, the name of the enqueue server, or the default logon client, and so on.

The instance profile (<SID>_<instance><instance number>_<server name>) defines parameters that apply for one instance, such as the number and type of work processes, or the definition of the size and allocation of memory areas used by the SAP instance. The content of the instance profile is instance-specific. The instance profile also contains the entries for the start up procedure.

The profile files are, in fact, created during the installation of the system and have some parameter already set. However, they can be edited afterward.

Evaluation of Profile Parameters

SAP systems consist of one central services instance (ASCS instance) and one or more application server instances. The SAP system and its instances are configured by profile parameters that are stored in profile files.

Initially, the default values of the profile parameters are defined and delivered in the program code of the SAP Kernel. That is why you need to differentiate between values coming from the SAP Kernel, referred to as kernel default, values set in the default profile, and in instance profiles. During the start up procedure of the SAP system, there is certain sequence of how the parameter values are evaluated and which value is valid at the end.

You can change the kernel default values using the default profile file and the instance profile files. These are read when an instance is started. The figure Evaluation Order of Profile Parameters shows the sequence in which the values for the profile parameters are evaluated by each instance of your AS ABAP.

First, the environment variables and the kernel default values are read. After that, the system reads the profile parameters that have been set in the default profile. So, if the value of a parameter in the default profile differs from the kernel default value, the value in the default profile is valid for all instances of the system. Only after that the instance profiles are read. So, if the same profile parameter has been explicitly set in the instance profile, this value is valid for this specific instance.

Note

Changes to profile parameters require a restart of the affected instance or of the complete SAP system depending on in which profile the parameter has been set.

Certain profile parameters can be switched dynamically without a restart required.

Tools for Displaying Profile Parameters

Displaying Profile Parameters Inside the SAP System

The current values of the profile parameters can be displayed within the SAP system. There are two ways of doing this:

  • You can use transaction RSPFPAR, which by the way, can also be run as a report with the same name.
  • You can use transaction RZ11.

Both functions display the profile parameters for the instance to which the user is currently logged on.

Transaction RSPFPAR displays a list of all instance-specific profile parameters in a table view, including system-wide parameters. You can restrict this list to specific parameters. The table displays the system default value for the individual profile parameters as it is defined in the program code of the kernel or in the default profile. If the value of a profile parameter is set in the instance profile or if it has been overridden dynamically, the table also displays the user-defined (temporary) value. A short description and, if required, documentation of the parameters can also be displayed.

Transaction RZ11 displays information and documentation for individual profile parameters. It also shows whether the parameter is a dynamic parameter and can be changed while the system is running so a restart of the system is not required.

Note

If you want to display an overview of all dynamically switchable parameters, you can use the following method: call transaction RZ11, then choose Goto → All Dynamic Parameters.

Values of profile parameters can contain set values or variables, such as parameter references or formulas.

Parameter references are indicated by a single $ symbol and the referenced parameter in round brackets. Double $$ symbol indicates the instance number.

As of SAP Basis 7.40 SP02 and higher, parameter values can be specified as formulas. A formula is always surrounded by round brackets ( ). The formula can reference other parameters and use standard operators such as +,-,*,/,^,(,). A formula can also include several standard functions such as min, max, sin, cos, tan, sqrt, exp, log2, log10, ceil, and floor. Use a period "." for decimal places. The individual values for the formula are displayed in transaction RSPFPAR. When long formulas are used, however, the formulas themselves cannot be displayed completely in this transaction. To display long formulas in their entirety, use transaction RZ11.

For more information, check the official documentation: https://help.sap.com/docs/ABAP_PLATFORM_NEW/e067931e0b0a4b2089f4db327879cd55/e05f0c5000efc06fe10000000a423f68.html

Example

The profile parameter rdisp/myname is set to $(SAPLOCALHOST)_$(SAPSYSTEMNAME)_$$ in the kernel. It references two other profile parameters, which is indicated by a single $ symbol. Double $$ symbol references the instance number.

If the two parameters are set, for example, as follows: SAPLOCALHOST=s4qhost, SAPSYSTEMNAME=S4Q, and the instance number is 12, the parameter rdisp/myname is derived from those values and is set to s4qhost_S4Q_12.

Error messages from formulas are logged in the stderr files during the start process. We recommend examining the stderr0 file first.

Hint

When evaluating profile parameters using the tools described, some profile parameter values are used system-wide, while others can be set differently for each instance. Transaction RSPFPAR displays the configuration of the instance on which you are running the report.

Displaying Profile Parameters Outside the SAP System

You can also display the values of the profile parameters outside the SAP system. This is done at the operating system level with the user <sid>adm by executing the program sappfpar. The sappfpar program determines the instance where the call is to be performed by evaluating the pf=<instance profile> option. Here, <instance profile> is the full path and file name.

If you want to display parameters interactively, call sappfpar with the profile option: sappfpar pf=<instance profile>. It will return a list of all parameters. When you enter a specific parameter, its current value is displayed.

You can check the parameters that are set with: sappfpar check pf=<instance profile>.

Calling sappfpar without any options displays the help function of this program.

Analyze Profile Parameters

Task 1: Determine the Values of Profile Parameters

Business Example

As a system administrator, you want to determine values of profile parameters set in your SAP system. You want to find out the names of several profile parameters and display their values.

Steps

  1. Display all profile parameters (transaction RSPFPAR).

    1. Log on to your SAP system.

    2. Start transaction RSPFPAR to display all profile parameters.

      Alternatively, you can run the report RSPFPAR in transaction SA38.

    3. Leave the Profile Parameters entry field empty and choose Execute.

      Result

      The profile parameters and their values are displayed in a table.

  2. Evaluate how the unique name of the application server you are currently logged on to is defined. This is the value of the profile parameter rdisp/myname.

    1. Start transaction RSPFPAR.

    2. In the Profile Parameters entry field, enter rdisp/myname.

    3. Choose Execute.

      Result

      The profile parameter and its values are displayed in a table.

      This parameter determines the name of the application server/instance you are working on.

      In column System Default Value (Unsubstituted Form), you can see that the name is being created out of the values of two other profile parameters (SAPLOCALHOST and SAPSYSTEMNAME separated by "_") and a placeholder for the local instance number ($$). It means, that the kernel default references other parameter values.

      In column User Value, you see the resolved values. For example, the result could look like s4qhost_S4Q_21.

  3. Determine, how many dialog, background, update, and spool work processes are configured on the primary application server (PAS) of your training system.

    1. Make sure you are currently logged on to the PAS of your SAP system. If not, use transaction SM51 to switch instances.

    2. Start transaction RZ11.

    3. Search for the profile parameters that define the number of work processes:

      Dialogrdisp/wp_no_dia
      Backgroundrdisp/wp_no_btc
      Updaterdisp/wp_no_vb
      Spoolrdisp/wp_no_spo

    4. Choose Display.

      Result

      On the Display Profile Parameter Details screen, you will find the current number of configured work processes in the Current Value row. Also you will see where the value originates from.

  4. Check the parameter rdisp/max_alt_modes to determine the maximum number of GUI windows or modes that a user can open during a single logon session.

    1. Start transaction RZ11.

    2. Search for parameter rdisp/max_alt_modes.

    3. Choose Display parameter.

      Result

      On the Display Profile Parameter Details screen, the maximum number of GUI windows is displayed in the Current Value row. Also you will see where the value originates from.

Task 2: Change a Dynamic Parameter

Business Example

As a system administrator, you want to change specific profile parameters without restarting the SAP system.

Steps

  1. In transaction RZ11, reduce the maximum number of ABAP sessions by changing parameter rdisp/max_alt_modes dynamically.

    1. Start transaction RZ11.

    2. Search for parameter rdisp/max_alt_modes.

    3. Choose Display parameter.

    4. Choose Change Value in the application pane.

    5. On the displayed dialog window, enter a new value into the New Value field.

      Decrease the maximum number of ABAP sessions.

    6. Choose Switch on all servers to set the same parameter value for all AS instances.

    7. Choose Save.

    8. Confirm the dialog box by choosing Continue.

      Result

      You have reduced the number of maximum number of ABAP sessions. However, you have to consider that the change is not permanent and will be lost when you restart the instance or the entire system.

  2. In transaction RZ11, display dynamic parameters and check the new value for rdisp/max_alt_modes.

    1. Start transaction RZ11.

    2. In the system menu, choose Goto → All Dynamic Parameters.

    3. Review the list of all parameters that can be changed dynamically.

      In the Dynamic Profile Parameters table, you can see the old value before the change and the dynamically changed value of the parameter.

    4. On the keyboard, press Strg-/Ctrl and F keys to enable the Find function.

    5. Search for parameter rdisp/max_alt_modes.

    6. Choose Search.

    7. Compare the Old Value and the New Value of the parameter.

      Result

      You should see the value that you have set in the previous step.

Profile Administration and Maintenance

To not only display, but also set the profile parameter values, you need to edit profiles. You can do this by using transaction RZ10. Also, you can edit the profile files with operating system tools or editors.

Caution

In this case, however, you must ensure that the changes are performed and documented correctly. Parameters that were set incorrectly can prevent an instance from starting. Before you make changes to the profile files, create backups. If an error occurs, you can start the SAP system with the restored files and perform troubleshooting.

It is, however, recommended to use RZ10 for profile administration and parameter maintenance. It is safer and more convenient.

As shown in figure Profile Administration, in RZ10 you can edit profiles that are created during the installation of the SAP system.

RZ10 offers a number of advantages to the user:

  • Central administration and maintenance of the profile files

  • Consistency checks when changing profile parameters

  • Administration of multiple versions of a profile file

  • Comparison between the actively used profile and the profile stored in the database

Immediately after installation, the profile files are created in the profile directory in the file system. They exist only at the operating system level. The installation program does not save profile files directly in the database. However, to administer the profile files in RZ10, they must be imported into the database, as shown in the figure Profile Maintenance: Import and Edit.

1. Importing Profile File Import After Installation

After installing the SAP system, profile files exist only at the operation system level. In transaction RZ10, you have to manually import the profile files from the file directory of the operating system into the database.

In the first step, you import the default profile and the instance profiles of the ASCS, PAS, and AAS into the database. To do so, choose Utilities → Import Profiles → Of active servers in RZ10.

During the import, the system performs an import check and compares the versions stored at the operating system level and in the database. After the check, the check log with the import results is displayed.

2. Editing Profile Files

After the profile file have been imported to the database, they can be edited. Changes to profile parameters can then be performed in the SAP system with the advantages described previously.

You can edit the imported profiles by changing the parameter values, adding new profile parameters, or deleting profile parameters. Changes are made in the database.

To edit a profile file, you have to select it, so you can change individual profile parameters. There are three different levels for maintaining the profiles. The Administrative Data contains the type of profile (default, or instance profile), a short description, the path of the file, the name of the instance and the time of the last activation. In Basic maintenance and Extended maintenance, you can maintain the parameters.

Basic maintenance allows you to adjust the most important parameters and supports you through the use of logical descriptions.

Extended maintenance displays the unformatted content of the profile; that is, the technical names of the profile parameters. In Extended maintenance, you can not only change the values of individual parameters but also add new parameters and delete existing parameters. Usually, the administrator uses Extended maintenance rather than Basic maintenance.

Hint

If you have installed a new application server instance or you have changed a profile file at operating system level, you can import profile files for individual instances. To do so, choose Profile → Import or the Import button.

3. Saving Changes to the Database

As the figure Profile Maintenance: Save and Activate shows, in the third step, you have to save the changed values permanently. To do so, choose Profile → Save in RZ10. The changes are therefore successfully saved to the database.

4. Activating the Changed Profile Files

However, they need to be written back to the operating system level, meaning to the profile files in the file system. The changes only take effect when they are read by the system out of the profile files stored in the file directory; that is, at a restart of the system.

Thus, in the fourth step, the changed files in the database must be activated. To do so, choose Profile → Activate in RZ10.

Hint

Activation can be done either automatically during saving by confirming the relevant query, or manually from the menu.

Changes to instance-specific profiles take effect after a restart of the corresponding instance.

Changes to the default profile take effect after a restart of all the instances (entire system).

Note

Changes in the default profile are not propagated throughout the system until all instances of the system are restarted.

Hint

The profile directory of the operating system also stores all old versions of the profile files, starting with .1. In earlier releases, there was only one older version of each profile, with the file extension .BAK.

Add and Change Parameters in Profiles

Business Example

As an administrator, you want to adjust the configuration of the entire SAP system and of single instances by changing profile parameter values.

Task 1: Import System Profiles

After system installation, profile files are stored in the profile directory at the operating system level. Before you can edit profile files in the SAP system, you need to import them into the database so you can edit them in transaction RZ10.

Steps

  1. Import the profile files of the PAS, AAS, and ASCS instances into the database of your SAP system using transaction RZ10.

    1. In your training SAP system, start transaction RZ10.

    2. In the menu bar, choose Utilities → Import profiles → Of active servers to import the profile files of PAS, AAS, and ASCS instances.

      Result

      In the profile check log, the import result is displayed. Only profiles that have changed versions at operating system level are imported. This is the reason why the log displays results that are highlighted in red color.

    3. Choose Back to return to the Edit Profiles input screen.

Task 2: Edit Profile Files

You want to edit the profile files that you have imported to the SAP system to adjust the system or single instance configuration.

Steps

  1. Check the current number of dialog work processes on the AAS instance.

    1. In a new GUI window, start transaction SM51, for example, by entering /o SM51 in the command field.

    2. Select the AAS instance and choose Work Processes to check the current number of dialog work processes.

    3. Examine how many work processes of type Dialog are configured.

  2. Increase the number of dialog work processes for the AAS instance by 1 using parameter rdisp/wp_no_dia.

    1. Go back to Edit Profiles input screen in RZ10 or start the transaction RZ10 again.

      Hint

      Since application servers of your SAP system can be installed on different hardware providing different hardware resources, you would probably change the number of work processes in the respective instance profile of an application server.

    2. In the Profile field, use the F4 value help to choose the instance profile of the AAS instance (<SID>_<instance name><instance number>_<host name>).

      Result

      The profile file in the current version has been selected.

    3. On the Edit Profiles screen, select the Extended maintenance radio button.

    4. Choose Change to change the selected profile.

    5. Check if parameter rdisp/wp_no_dia has already been added to the list.

      Result

      rdisp/wp_no_dia appears in the list that means it has been added to the profile file.

    6. In the list of profile parameters, select rdisp/wp_no_dia.

    7. Choose Parameter where the tool tip displays Change (F2) or double-click the parameter to change its value.

    8. In the Parameter Value field, increase the number of dialog work processes by 1.

    9. Choose Copy.

      Result

      The system message The changes were applied is displayed in the status bar.

    10. Go back to the Maintain Profile where all parameters of the profile are displayed.

    11. Choose Copy here too.

      Result

      The system message The changed profile was applied is displayed in the status bar.

    12. Go back to the Edit Profiles screen.

    13. In the menu bar, choose Profile → Save.

      Result

      The system will create a new version of the profile.

    14. The system will prompt you in a dialog box to activate the new profile version. Choose Yes to confirm the activation.

      Result

      The new version of the profile has been saved and activated.

    15. Choose Continue.

    16. A note that appears informs you that you have to restart the system to make profile changes effective. Choose Continue.

  3. Check the current maximum number of windows a user can open within the same logon session that is configured via rdisp/max_alt_modes parameter.

    1. In a new GUI window, start transaction RZ11, for example, by entering /o RZ11 in the command field.

    2. Search for parameter rdisp/max_alt_modes.

      The parameter limits the maximum number of windows (modes) that a user can open during one logon session.

    3. Choose Display.

      Result

      On the Display Profile Parameter Details screen, the maximum number of GUI windows is displayed in the Current Value row.

  4. Set the value for the maximum number of windows that a user can open during a logon session to 8 by changing the value of rdisp/max_alt_modes. Think about in which profile(s) you would make the change - depending on the scenario.

    1. Go back to Edit Profiles in transaction RZ10 or start RZ10 again.

      Hint

      In general, you would want the users to open the same maximum number of windows on all application servers, so you would set the parameter in the global default profile.

    2. In the Profile field, use the F4 value help to choose the default profile (DEFAULT).

      The system automatically fills the Version field with the most recent version.

    3. Select the Extended maintenance radio button.

    4. Choose Change to change the selected profile.

    5. Check if parameter rdisp/max_alt_modes has already been added to the list.

      Result

      rdisp/max_alt_modes is not in the list, which means it is not set in the default profile.

    6. In the list of profile parameters, select the line where you want to insert the parameter.

      Hint

      The parameter will be inserted above the line you have selected.

    7. Choose Parameter where the tool tip displays Create (F5).

    8. On the Maintain Profile screen, enter the parameter rdisp/max_alt_modes in the Parameter Name filed.

    9. As Parameter Value, enter 8 to limit the maximum number of windows that a user can open during a logon session.

    10. Choose Copy.

      The change has been saved but not applied.

    11. Choose Copy again.

      Result

      The system message The changes were applied is displayed in the status bar.

    12. Go back to the Maintain Profile where all parameters of the profile are displayed.

    13. Check if rdisp/max_alt_modes appears in the list.

      Result

      rdisp/max_alt_modes with the set value appears in the list.

    14. Choose Copy here too.

      Result

      The system message The changed profile was applied is displayed in the status bar.

    15. Go back to the Edit Profiles screen.

    16. In the menu bar, choose Profile → Save.

      Note

      An error message may occur. You can ignore it and choose No.

      Result

      The system will create a new version of the profile.

    17. The system will prompt you in a dialog box to activate the new profile version. Choose Yes to confirm the activation.

      Result

      The new profile version has been saved and activated.

    18. Choose Continue.

    19. A note that appears informs you that you have to restart the system to make profile changes effective. Choose Continue.

Task 3: Make the Profile Changes Effective

You want to make the changes to the profile files effective, so you need to restart the SAP system.

Steps

  1. Restart the SAP system by using the start/stop tool of your choice

    1. Restart your training SAP system by using the SAP Management Console or the command sapcontrol at the operating system level.

      Note

      You have to restart the entire SAP system since you have made changes to the default profile too. If you make changes only to an instance profile, the restart of only this instance is sufficient.

  2. After the system is running again, log on to it and check how many dialog work processes are now configured on the AAS instance.

    1. Log on to your training SAP system.

    2. To check the number of work processes, start transaction SM51.

    3. Select the AAS instance and choose Work Processes.

      Result

      You should see the increased number of dialog work processes that you have changes in the AAS instance profile.

  3. Check how many windows you can open within your logon session.

    1. Start transaction RZ11.

    2. Search for parameter rdisp/max_alt_modes.

      The parameter limits the maximum number of windows (modes) that a user can open during one logon session.

    3. Choose Display.

      Result

      On the Display Profile Parameter Details screen, the maximum number of GUI windows is displayed in the Current Value row. This should be the value that you have set in the default profile.

      Also you see that the value originates from Default Profile.

    Result

    All changes have become effective.

Profile Files Checks

In transaction RZ10, you can run several checks. For example, if a profile has been changed, you can perform a check for it. You can also perform a consistency check, to check the syntax, the semantics, and the parameter names of individual profiles or for all profiles. The results are displayed in a check log.

Check single profiles

By selecting a profile and choosing Profile → Check, you can check a single profile. This check detects errors in parameter values. You can execute it before activating a new version of the profile to avoid any configuration errors.

Check all profiles of active servers

The Utilities → Check all profiles → Of active servers option provides a consistency check of all profiles of running instances and the default profile. The system checks, for example, the unknown profile parameters or if existing formulas have been overwritten.

For more details on the checks and the check rules, please read the official documentation: https://help.sap.com/docs/ABAP_PLATFORM_NEW/e067931e0b0a4b2089f4db327879cd55/48c6090d895a154ee10000000a421937.html

Compare profiles

During the comparison of profiles, the system compares the active version of the profile at the operating system level with the most recent version of the profile stored in the database. To execute the comparison, select the profile file and choose Profile → Comparisons → Profile in database → With active profile. The system displays a check log that shows if the profile in the database is different that in the file system.

Monitor Parameter Changes

In transaction TU02, you can display an overview of parameter changes.

In the transaction, you get an overview of when profile parameters have been changed for the last time and for which application server instances. Also, you can select a time period to see which individual parameters have been changed on specific dates. You can also display a list of all active parameters and their values valid for a specific instance.

The report RSPFL_HISTORY_DISPLAY provides you the changelog of profile parameter values as well as the parameter snapshots.

In the changelog you can display which parameters have been changed for an instance, and you can search for a specific parameter to see the changed value and when the parameter has been changed last. You are also able to see the change history and all the timestamps. This data is stored in the database.

Note

If you do not see the most recent date, you have to choose Update Changelog in the application toolbar to refresh the data.

The parameter snapshot files are created by the each application server instance during the startup procedure and stored in the global directory. The data that is displayed in the changelog is based on the snapshot files.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn