What is profile???

SAP profiles are operating system files that contain instance configuration information. SAP systems can consist of one or more instances. Individual configuration parameters can be customized to the requirements of each instance.

The profile file is structured as follows:

Parametername1 = Value1 Parametername2 = Value2

Parameter names that logically belong together have a common root. For example, the parameters that control the dispatcher within an application server have the root: rdisp/.

The SAP profiles are stored in a special file directory.

UNIX systems:/usr/sap/<SID>/SYS/profile Microsoft Windows systems:\\<SAPGLOBALHOST>\sapmnt\<SID>\sys\profile\ NT

START Profile:

When you start an SAP instance on a host, the start profile defines which SAP services are started (message server, dialog, gateway or enqueue process. for example). The startsap program is responsible for starting these service processes, and it uses a start profile to begin the startup process.

Apart from the general profile parameters, such as the name of the SAP System ( SAPSYSTEMNAME ), instance number ( SAPSYSTEM ) and name of the SAP instance (INSTANCE_NAME ), the only parameter names that are permitted in a start profile are:
Execute_XX (XX: 00-99) Start_program_XXX (XX: 00-99) Stop_Program_XX (XX: 00-99)

Default Profile:
If you want to assign the same parameter value for all application servers (such as the name of the database host, or the host on which the message server is running), enter it in the default profile. In general, you can list any parameter you like here. SAP recommends that you use the following values:
Parameter Name in Profile SAPDBHOST rdisp/vbname rdisp/enqname

Parameter Definition Name of the database host Name of the update server Name of the enqueue server

Name of the server for handling background processing rdisp/btcname events Name of the computer on which the message server is rdisp/msname running Name of the TCP service under which the message server rdisp/msserv can be reached Name of the computer on which the SNA Gateway is running Name of the TCP Service under which the SNA Gateway can be reached rdisp/sna_gateway rdisp/sna_gw_service

Instance Profile:
Instance profiles provide an application server with additional configuration parameters that complement the settings in the default profile. Typically, these are parameter settings that are adapted to the instance according to the required resources and applications. They also define the available instance resources (main memory, shared memory, roll memory, and so on), and how to allocate memory to the SAP application buffers. You can choose any name for an instance profile. The SAP naming convention has the following structure:<SID>_<Instanzname> or <SID>_<Instanzname>_<Hostname> Eg: ECP_DVEBMGS12. ECP_DVEBMGS12_host01

Transaction code: RZ10

Importing Profiles: When you first install an SAP System, upgrade to a new SAP release or add a new application server, the system automatically generates or updates SAP instance profile at operating system level. Unfortunately, the installation program cannot save these profiles directly to the database. You must therefore import the SAP instance profiles before you can then edited them.

Editing Profile: There are two modes for editing profiles: In basic mode, you can edit a set of parameters that are changed most frequently. You do not need to know the technical parameter names. Interdependent parameters are grouped together. If you change a parameter, any parameters that depend on it are adjusted automatically. The basic maintenance option displays general data on the profile and the parameters for the buffer sizes, number of work processes and the swap requirement. In extended mode, you can use a editing tool. You need to know the technical names of parameters and their dependencies. It displays all individual parameter values for the profile.

Creating New profiles:

Call the RZ10. Specify the name of the profile that you want to create and choose Create. The system creates the version number automatically. Enter a short description of the profile, the filename into which the profile should be activated, a reference server and the profile type. Then choose Copy. You can maintain parameters and their values by flagging either Basic or Extended maintenance and choosing Maintain.

To create a new profile manually:

Changing Profile Parameters:

Call Transaction RZ10. Specify the name of the profile whose parameters you want to change in the Profile field. If you want to change the name of the file in which the profile should be activated, check Administration data and choose Change. Once you have made the changes, choose Copy. If SAP System profiles are imported automatically, the system creates administration data automatically. Maintain the most important profile parameters by checking Basic maintenance and choosing Change. Once you have made the changes, choose Copy. You can create, change or delete all parameters in a profile by choosing Extended maintenance. Once you have made the changes, choose Copy.

Important Profile Parameters:

Description
System ID of 3 characters. Name of Database server. Message Server name. Instance that provide Enqueue service. Specifies no. of Dialog process. Specifies no. of Spool process. 2 0

Parameter
sapsystemname sapdbhost rdisp/mshost Rdisp/enqname Rdisp/wp_no_dia Rdisp/wp_no_spo

Default value

Rspo/host_spool/ print
Rdisp/wp_no_vb Rdisp/wp_no_btc Rdisp/wp_no_enq Abap/buffersize

OS command for printing.

Specifies no. of Update process. Specifies no. of Background process. Specifies no. of Enqueue process. Size of ABAP program buffer. 0 0 0 300000

To check all the parameters name: tcode : sa38----> program name: rsparam---->Execute----> Execute.

Rdisp/roll_maxfs

Size of Roll area.

Recommend ed/Default 16000

Rdisp/pg_maxfs

Size of Paging area.

Ztta/roll_first
Ztta/roll_area

Size of first allocated memory area from roll area.

Size of roll area (in bytes)

1
2,000,000 bytes for NT 8236842496 3

Abap/heap_area_tot al Login/fails_to_sessio n_end

Maximum heap process of all Work Process. No. of permitted failed logon attempts before SAPGUI closed.

Login/fails_to_user_l ock
Login/min_password /lng Login/system_client

No. of permitted failed logon attempts after which user will lock out.
Minimum length of password required. Default logon client.

12

3 200 1000000

Rslg/max_diskspace/ Max size of file for local system log. local

You can define operation modes to suit specific system requirements, for example, to provide additional dialog or background processing resources during a particular period of time without having to restart the system. Operation modes define:

The number of work processes used for each service in the instance
The times that the services are available Operation modes support: 24 hour uninterrupted system operation

Automatic switching of work process types

Switching Operation Modes

When operation modes are switched, the work processes are redistributed automatically without stopping and restarting the instances. Only the work process types are changed. For example, a work process used as a dialog process can be switched for use as a background process. Processing is not interrupted. Normal system operation continues uninterrupted during the operation mode switch.

Switching Operation Modes Automatically (RZ04)

Normal Operation: The time interval defined for Op mode are repeated in 24 hours. Exception operation: The time intervals defined for the operation modes are activated once for a specified time period

Two ways:

Switching Operation Modes Manually (RZ03)

Call transaction RZ03. The system displays information about operation modes and server status. Choose Operation Mode. The system displays a list of defined operation modes. Choose the operation mode that you want to switch to. You return to the list of operation modes and servers.

Step 1: Call transaction rz04

Step 2: Click on create

Step 3: Fill Operation Mode as day and give short description and Save.

Step 4: Repeat Step 2 and Step 3 for Night Operation. Step 5: Click on instance/Operation Mode

Step 6: Go to Settings based on current status Existing or New instance.

Step7:Save Step 8:Double click on defined on Operation Mode and adjust Background Job and Save.

Step9: Go to Operation Mode Timetable and select Normal or Exception mode as per requirement and click on change.

Step10: Select time interval and assign the operation mode.

Step 11:Select day and night operation Modes for particular time interval and Save.