How
to change profile parameter in SAP (RZ10) and (RZ11)
Step-by-step procedure: (Profile Parameter Change – RZ10)
- Login to the SAP system
- Hit the transaction code ‘RZ10′
- Click Utilities and click import profiles
- Click back (F3)
- Place the cursor at profile and click f4
- Double click on Default profile
- Select the Extended maintenance and click change
- Click Parameter (Create F5)
- Place the cursor at parameter name and click F4
- Click a small triangle shape which is available on top
of the box
- Type *login* and hit enter
- Double click on ‘login/no_automatic_user_sapstar’
parameter or search for parameter
which you want to change
- Type the NEW
parameter value
- Click ‘Copy’ Tab and click back (F3)
- Click ‘Copy’ Tab again to transfer The changed profile
- Click Back (F3)
- Click Save, Click back and Click Yes to activate the
profile
- Log out from the SAP system
- Stop the SAP System (Server)
- Start the SAP System (Server)
I think I have covered all the steps related to changing a
profile parameter; you can validate changes in parameter value through T-Code
RZ11 after system restart.
What
is Dynamic and Static profile parameter in SAP
Basically there are 2
types of parameters:
- Static
- Dynamic
Static are the
parameters those won't take effect immediately the value is set. Restart of a
sap system is required for them to take effect.
Dynamic are the
parameters those will take effect immediately in the run time. Restart of a sap
system is not required for them to take effect.
Profile
Parameters for Logon and Password (Login Parameters)
Parameter
|
Explanation
|
login/min_password_lng
|
Defines the minimum length of the
password.
Default value: 3; permissible
values: 3 – 8
|
login/min_password_digits
|
Defines the minimum number of digits
(0-9) in passwords.
Default value: 0; permissible
values: 0 – 8
Available as of SAP Web AS 6.10
|
login/min_password_letters
|
Defines the minimum number of
letters (A-Z) in passwords.
Default value: 0; permissible
values: 0 – 8
Available as of SAP Web AS 6.10
|
login/min_password_specials
|
Defines the minimum number of
special characters in the password Permissible special characters are
$%&/()=?'`*+~#-_.,;:{[]}\<>│ and space
Default value: 0; permissible
values: 0 – 8
Available as of SAP Web AS 6.10
|
login/password_charset
|
This parameter defines the
characters of which a password can consist.
Permissible values:
● 0
(restrictive): The password can only consist of digits, letters, and the
following (ASCII) special characters :!"@ $%&/()=?'`*+~#-_.,;:{[]}\<>|
and space
● 1
(backward compatible, default value): The password can consist of any
characters including national special characters (such as ä, ç, ß from ISO
Latin-1, 8859-1). However, all characters that are not contained in the set
above (for value = 0) are mapped to the same special character, and the system
therefore does not differentiate between them.
● 2
(not backward compatible): The password can consist of any characters. It is
converted internally into the Unicode format UTF-8. If your system does not
support Unicode, you may not be able to enter all characters on the logon
screen. This restriction is limited by the code page specified by the system
language.
With login/password_charset = 2, passwords are stored in a format that systems with older
kernels cannot interpret. You must therefore only set the profile parameter
to the value 2 after you have ensured that all systems involved support
the new password coding.
Available in the standard system
as of SAP Web AS 6.40.
|
login/min_password_diff
|
Defines the minimum number of
characters that must be different in the new password compared to the old password.
Default value: 1; permissible
values: 1 – 8
Available as of SAP Web AS 6.10
|
login/password_expiration_time
|
Defines the validity period of
passwords in days.
Default value: 0; permissible
values: any numerical value
|
login/password_change_for_SSO
|
If the user logs on with Single
Sign-On, checks whether the user must change his or her password.
Available as of SAP Web AS 6.10,
as of SAP Basis 4.6 by Support Package
|
login/disable_password_logon
|
Controls the deactivation of
password-based logon
This means that the user can no
longer log on using a password, but only with Single Sign-On variants (X.509
certificate, logon ticket). More information: Logon Data Tab Page
Available as of SAP Web AS 6.10,
as of SAP Basis 4.6 by Support Package
|
login/password_logon_usergroup
|
Controls the deactivation of
password-based logon for user groups
Available as of SAP Web AS 6.10,
as of SAP Basis 4.6 by Support Package
|
Multiple Logon
Parameter
|
Explanation
|
login/disable_multi_gui_login
|
Controls the deactivation of multiple
dialog logons
Available as of SAP Basis 4.6
|
login/multi_login_users
|
List of excepted users, that is,
the users that are permitted to log on to the system more than once.
Available as of SAP Basis 4.6
|
Incorrect Logon
Parameter
|
Explanation
|
login/fails_to_session_end
|
Defines the number of unsuccessful
logon attempts before the system does not allow any more logon attempts. The
parameter is to be set to a value lower than the value of parameter login/fails_to_user_lock.
Default value: 3; permissible
values: 1 -99
|
login/fails_to_user_lock
|
Defines the number of unsuccessful
logon attempts before the system locks the user. By default, the lock applies
until midnight.
Default value: 12; permissible
values: 1 -99
|
login/failed_user_auto_unlock
|
Defines whether user locks due to
unsuccessful logon attempts should be automatically removed at midnight.
Default value: 1 (Lock applies
only on same day); permissible values: 0, 1
|
Initial Password: Limited Validity
Parameter
|
Explanation
|
login/password_max_new_valid
|
Defines the validity period of
passwords for newly created users.
Available as of SAP Web AS 6.10,
as of SAP Basis 4.6 by Support Package
|
login/password_max_reset_valid
|
Defines the validity period of
reset passwords.
Available as of SAP Web AS 6.10,
as of SAP Basis 4.6 by Support Package
|
SSO Logon Ticket
Parameter
|
Explanation
|
login/accept_sso2_ticket
|
Allows or locks the logon using
SSO ticket.
Available as of SAP Basis 4.6D, as
of SAP Basis 4.0 by Support Package
|
login/create_sso2_ticket
|
Allows the creation of SSO
tickets.
Available as of SAP Basis 4.6D
|
login/ticket_expiration_time
|
Defines the validity period of an
SSO ticket.
Available as of SAP Basis 4.6D
|
login/ticket_only_by_https
|
The logon ticket is only
transferred using HTTP(S).
Available as of SAP Basis 4.6D
|
login/ticket_only_to_host
|
When logging on over HTTP(S),
sends the ticket only to the server that created the ticket.
Available as of SAP Basis 4.6D
|
Other Login Parameters
Parameter
|
Explanation
|
login/disable_cpic
|
Refuse inbound connections of type
CPIC
|
login/no_automatic_user_sapstar
|
Controls the emergency user SAP*
(SAP Notes 2383 and 68048)
|
login/system_client
|
Specifies the default client. This
client is automatically filled in on the system logon screen. Users can type
in a different client.
|
login/update_logon_timestamp
|
Specifies the exactness of the
logon timestamp.
Available as of SAP Basis 4.6
|
Other User Parameters
Parameter
|
Explanation
|
rdisp/gui_auto_logout
|
Defines the maximum idle time for
a user in seconds (applies only for SAP GUI connections).
Default value: 0 (no restriction);
permissible values: any numerical value
|
Profile
parameters to increase/decrease the number of workprocesses
To increase/decrease
the number of workprocesses, value to be changed accordingly for the following
parameters as per workprocess in RZ10 Transaction.
rdisp/wp_no_dia
(for dialog workprocess)
rdisp/wp_no_btc
( for background workprocess)
rdisp/wp_no_spo
(for spool workprocess)
rdisp/wp_no_enq
(for enqueue workprocess)
rdisp/wp_no_vb
(for update workprocess)
rdisp/wp_no_vb2
(for update2 workprocess)
In RZ10 transaction,
select the profile of the instance, for which workprocess number to be
changed and edit the profile through extended maintenance and save the changes
done and activate the profile.
Please note that as
this parameter is not dynamic one, restart of the application server is
required for the changes to become effective.
No comments:
Post a Comment