There are 3 types of profiles in SAP :-
1. DEFAULT.PFL (known as System profile)
2. SID_DVEBMGS00_SID (Instance Profile)
3. START_DVEBMGS00_SID (Start Profile)
Path of profiles :-
In Unix Systems :
- /usr/sap/SID>/SYS/profile or /sapmnt/SID>/profile
In Windows NT :
Description of SAP profiles :-
1. DEFAULT.PFL
It contains system-wide settings which include -
- Name of the SAP system
- The database system
- Name of the Enqueue server
It is used to provide global parameters for all the instances. For example:
- Buffer parameters
- Message server host
- Enqueue host
- Security parameters(password,user restrictions)
There is only one default profile for each SAP system and it is read by all instances.It contains system-wide settings such as the system name, the name of the database server, the name of the enqueue server or also the Default log on client.
2. START PROFILE :
Start up profile consists of start up parameters like
- Starting database
- Starting Message Server
- Dispatcher+work
- Work Process
The naming convention of START PROFILE will be as below :
START_instance>instance_number>_host_name>
Eg: START_DVEBMGS00_prds4
For the start profile default names are assigned during the installation of an instance based on the services that are running on the instance.
D – Dialog
V – Update
E – Enqueue
B – Batch
M – Message
G – Gateway
S -- Spool
00 -Instance number
3. INSTANCE PROFILE :
The instance profile is therefore instance-specific. This is used to set the instance specific parameters.The instance profile (SID>_instance>instance number>_host 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 the main memory area used by the Sap system.
The run time environment of the instance is configured in the instance profile. In instance profile parameters specific to an instance can be set like auto gui logout time(rdisp/gui_auto_logout), number of various work processes (rdisp/wp_no_dia), memory related parameters like :
- A. abap/buffer_size
- B. em/initial_size_MB
- C. rdisp/PG_SHM
- D. rdisp/ROLL_SHM etc.
The naming convention for the instance profile will be as below :
SID>_instance>instance_number>_hostname>
Eg : SID_DVEMBSG00_PRD
Sequence of SAP profiles that are read while starting SAP system :
| SAP Server | SAP Server |
SAP Server
|
|---|
| START Profile | DEFAULT.PFL |
INSTANCE Profile
|
- First start profiles of various instances are read by the sapstart program.
- Secondly Default profile is read.
- Finally, instance profiles of various instances are read.
Static Profile :
Static are the parameters those won't take effect immediately the value is set. Restart of an sap system is required for them to take effect.
1. Administrative Data: - Which will give the path of each profile. Do not change this until there is change in path of profile.
2. Basic Maintenance: - This is used by Technical Team where maintenance is performed without knowing the parameter names. We can toggle between the values. It’s used to maintain Work process, Buffers, Memory Management.
3. Extended Maintenance: - It’s used to change the parameters based on parameter names. It’s used by experts and ensures that necessary care is taken while modifying the parameters.
Dynamic Profile :
Dynamic are the parameters those will take effect immediately in the run time. Restart of an sap system is not required for them to take effect.
Parameter are two types :
- Static Parameters: When ever we can change a static parameter value we need restart the SAP system. It is permanent change in SAP and it will be done using RZ10 only.
Eg:-
rdisp/wp_no_dia
rdisp/wp_no_btc
rdisp/wp_no_spo
Dynamic Parameters: When ever we can change dynamic parameter values we don't need restart the sap system,when we restart goes back to peivious values . It will be change in RZ11 and RZ10 also.
Eg:-
rdisp/gui_autologout
rdisp/max_wp_runtime
rdisp/j2ee_start
Regards,
JUNAID AHMAD
SAP BASIS
