SAP BASIS: Administration and Monitoring Tools

 SAP BASIS: Administration and Monitoring Tools


SAP System provides various tools for monitoring the system and for making administration changes.
The tools can be accessed from SAP menu by selecting Administration-->System Administration, then under nodes Administration and Monitor.
The monitoring tools can also be directly executed using the transaction codes.

1. Consistency Check SICK: 

Transaction code SICK is executed immediately after the installation to get the information about any inconsistencies in the SAP installation process.
It crosschecks the release numbers and character sets in SAP Kernel with the database release numbers.

2. SAP Application Server Overview SM51: 

It displays all the application server instances of the SAP system. This transaction code is used to monitor application servers and change their states (Initial, Started, Active, Shutdown and Stop).

3. Monitoring ABAP Work processes SM50: 

It displays the activity of work processes of an instance. This transaction code is used to manage work process as well as utilization of work process.

4. Monitoring SAP Message Server SMMS: 

SAP Message Server is used to exchange messages between servers and it contains the information about the application servers.

5. Monitoring SAP system users SM04: 

Transaction code SM04 is executed to display which users are logged on the instance. This transaction is also used to manage the user sessions.

6. Managing lock entries SM12: 

SM12 is used to monitor which locks are active in the system and who is holding the lock entry.

7. Monitoring ICM SMICM: 

Internet Communication Manager (ICM) processes internet requests like client server, HTTP and SMTP requests.

8. Monitoring Global SAP Servers SM66: 

Transaction code SM66 is executed to display all the servers running with in the organization.

9. Monitoring users global AL08: 

AL08 is used to monitor the users logged on to the system globally or for all the instances in the system.

10. Monitoring ABAP Dumps ST22: 

ABAP short dumps are created when the ABAP program terminates abnormally. Use ST22 to display the information of short dumps created in the system.

11. Monitoring system logs SM21: 

System log records all the errors and warnings occurred in the system.  Transaction code SM21 is used to monitor the system logs.

12. System Trace ST01: 

Configure the system trace using ST01. It can be used to track errors.

13. SAP system Messages SM02:  

Transaction code SM02 is used to send short messages to all the users who are logged on to the system.

14. SAP Gateway Monitor SMGW: 

This is for monitoring and administering the SAP Gateway in SAP system.

15. SAP system statistics ST03N:  

System statistics are useful to monitor the work load of the SAP system. Workload monitor is the one which displays the statistics of the local SAP system. performance of the system can be analyzed using ST03N. Global workload monitor is the one which displays the statistics of the entire landscape. It includes ABAP systems and non ABAP systems, ITS and J2EE engine. Workload monitors are used to analyze response time and CPU time.

Please go through the videos of  SAP Basis Interview questions and Answers below to get more knowledge on the topics. 
SAP Basis Administration questions and Answers



Location: Chicago, IL, USA

Comments

Post a Comment

Popular posts from this blog

SAP Security: Critical Authorization Objects

SAP Security: Critical Authorization Objects 1. S_TABU_DIS: This authorization object enables authorization check for displaying or modifying the table content. For accessing the table data, users use SE16, SM30 or SM31 transaction codes. This object contains two fields, DICBERCLS (authorization group) and ACTCT. 2. S_RFC: This authorization object enables authorization check for remote function call to access program modules (function modules). This authorization object contains three fields, RFC_TYPE, RFC_NAME and ACTCT. 3. S_DATASET: This authorization object enable file access at operating system level. This gives permission to access files from ABAP programs. This object contains three fields, File name, Program and Activity. 4. S_ADMI_FCD: This authorization objects enable access to various administrator activities like system monitoring, spool administration, client creations, update administration etc. This object contains one field, system administration functions. 5. S_DE...
Read more

SAP Security: Creating New User Account using Transaction Code SU01

Image
Creating  New User Account U sing Transaction Code SU01 SAP User Administration functions include User Creation, Change, Display, Delete, Copy, Lock/Unlock, Password reset. The topic is about creating new user account in SAP system. I have explained two methods. This is relevant for SAP Security Consultants or SAP User Administrators who want to perform user administration activities in SAP system. The User Administrator must follow the company policies and approval process before creating user account. Prerequisites for creating New User Account User Administrator/SAP Security Consultant should have the roles with the below authorizations in it. 1. Authorization Object S_USER_GRP for creating user and assign to user group. 2. Authorization Object S_USER_PRO for assigning authorization profiles to user. 3. Authorization Object S_USER_AUTH for creating and modifying authorizations. 4. Authorization Object S_USER_AGR for assigning roles to user. 5. Authorization Object S_USER_TCD for...
Read more

SAP Security: How to set auto Logoff for Inactive users in SAP

Image
How to set auto Logoff for Inactive users in SAP SAP provides an options for logging of inactive users in SAP automatically. Inactive means if there is no activity for a specific period of time. By setting the auto logoff improves the security in the SAP system. The auto logoff options is not active in the system by default. This needs to be activated using the profile parameter called rdisp/gui_auto_logout. The value for this parameter should be set in the form of seconds. The inactive users are logout of the system after the specific time period that is set in the parameter. The SAP system doesn't save the data before auto logoff and it does not popup any prompt before auto logoff. Procedure to set the value in the Profile parameter: Execute transaction code RZ10 Select the DEFAULT profile from the selection menu. Select the Extended maintenance and click on change icon. Click on the create parameter icon as shown below. Enter the new parameter name as rdisp/gui_auto_logout and c...
Read more