SAP Web AS Administration By: ALY ADEL

1. ADM100 SAP Web AS Administration I By : ENG. ALY ADEL Senior SAP Netweaver Consultant

2. UNIT 1 : FUNDAMENTALS Objectives What is SAP system ? Process of a System Logon Configuring SAP Logon Analysis Transactions

3. What Is SAP System ? Exactly one database and one or more instances. The instance that together with the database, creates a runnable SAP system, is called the “ central instance ”. It is certainly possible to install two instances of a system or even of different systems on one server. When configuring two systems (or their databases) on one server, you should ensure that the two systems are clearly differentiated, otherwise a conflict situation will eventually occur during the use of common resources (such as program libraries), An SAP System consists of the components shown in the graphic:

4. What Is SAP System ?

5. What Is an Instance of an SAP System? An instance of an SAP system is an administrative unit that provide one or more services . The services provided are commonly started and stopped. These components currently include the Dispatcher , the work processes , the gateway , the assigned main memory areas, and an Internet Communication Manager (ICM), if one is configured. An instance always has exactly one dispatcher. The start of an instance always begins with the start of the associated dispatcher. An instance requires a minimum of two dialog work processes. Otherwise it is not possible to start it. An instance is also called the Application Server .

6. SAP System instance .

7. Hardware / Software-oriented View

8. Process Of System Logon SAP GUI sends the user’s logon data to the instance (step 3 in the above figure). After the dispatcher has determined a free work process to process the logon, it transfers the logon data to this work process (step 4). The work process, in turn, checks whether the received combination of user ID and password is known to the system using a request to the database (steps 5-8). A positive response from the database prompts the work process to return the initial screen of the system to the front end.

9. Dialog Work Process Multiplexing The processing of a transaction that consists of multiple screens is usually executed using multiple, different dialog work processes. This distribution is called “ work process multiplexing ”.

10. Dialog Work Process Multiplexing

11. SAP Logon The SAP Logon program provides users with a convenient logon to a SAP system with the SAP GUI for Windows

12. Analysis Transactions

13. UNIT 2 : Starting & Stopping The SAP System Objectives System Start : Process System Start : Logs System Shutdown : How and Why ?

14. System Start : Process The starting of an SAP system is the basic prerequisite for being able to work with the system. Restarts of SAP systems are also required after maintenance work on the hardware in use and changes to the SAP system’s profile. Starting an SAP system is an initial process with which every administrator should be familiar.

16. System Start

17. System Start The status of the SAP system , individual instances , and the message server and dispatcher are displayed in the Microsoft Management Console ( MMC) in accordance with the following color legend: GRAY : not running YELLOW : is starting GREEN : Active RED : Terminated after errors

18. System Start : Logs Logging the Start Process The start process is an especially important phase, which is logged by the operating system, the SAP system, and the database. If the SAP system does not start up, you can find the relevant error message in the log files. All messages that are created by services or the Microsoft Management Console are recorded at operating system level by an event logging service the Event Manager.

19. System Start : Logs The system displays a list of errors, warnings, and information that have been generated

22. System Shutdown : How and Why ? The stopping of the SAP system is performed in the opposite order to the start. Stopping the instances: In the SAP system itself (transaction RZ03 ) by choosing Control -> Stop SAP instance . In the Microsoft Management Console, right-click to show the context menu and choose the Stop function. Depending on whether you have selected an individual instance or the SAP system, the following are stopped: – A single instance – Central instance and all dialog instances The SAP service waits for a stop message from the MMC or from the CCMS and then stops the SAP system. The service itself is not stopped. The services themselves can be stopped and restarted with the Microsoft Windows Service Control Manager.

23. UNIT 3 : Introduction To System Configuration Objectives How The System Evaluate It’s Parameters How To Set System Parameters Setting Up Operation Modes

25. System Parameters The instance-specific start profile ( START<instance><instance number>_<host name> ), specifies for each instance which processes are to be started. These are, for example, the message server and the dispatcher. There is only one default profile (DEFAULT.PFL ) 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 logon client. 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, and is therefore instance-specific.

28. UNIT 4 : Access To HELP Objectives Configuring The Online Documentation Support Online Help SAP Marketplace

30. support Online Help ( http://help.sap.com )

31. SAP Service Marketplace ( http://service.sap.com )

32. UNIT 5 : Fundamentals of Working with the Database Objectives Architecture of Database Systems Backing Up the Database Contents Overview: Monitor the Database

38. UNIT 6 : Archiving Objectives Fundamentals of SAP Data Archiving Performing Data Archiving Accessing Archived Data

40. Fundamentals of SAP Data Archiving

41. UNIT 7 : Working with the Transport System Objectives Data Structure and System Landscapes Performing and Checking Transports

43. System Landscapes SAP recommendation for a three-system landscape is based on the data structure of an SAP system, in which the object repository only exists once.

44. Performing and Checking Transports

45. Transports in a Three – System Landscape

46. Checking Transports .

47. UNIT 8 : Support Packages, Plug-Ins, and Add-Ons Objectives Term Definition: Support Packages Importing Support Packages Updating the Tools Importing SAP Notes

50. Support Packages SAINT

52. SAP Notes

53. UNIT 9 : Scheduling Background Tasks Objectives Fundamentals of Background Processing Time-Based Scheduling of Jobs Event-Based Scheduling of Jobs Background Processing: Other Topics

56. Event-Based Scheduling of Jobs

57. Background Processing: Other Topics LOAD BALANCING

58. UNIT 10 : Including Printers in SAP Systems . Objectives Configuring Printers in SAP Systems Concept of Logical Spool Servers Managing Spool Requests

60. UNIT 13 : System Monitoring Objectives Monitoring Architecture Including Remote Systems Creating Your Own Monitors

62. Monitoring Architecture

63. Monitoring Architecture

64. Monitoring Architecture

65. Creating Your Own Monitors

66. UNIT 14 : SAP Solution Manager Objectives Concept of the SAP Solution Manager

68. SAP Solution Manager

69. UNIT 15 : Structured Troubleshooting Objectives Trace Options Troubleshooting Procedure

71. Troubleshooting Procedure

72. UNIT 16 : Introduction To System Security Objectives Security in the SAP Environment

74. Security of The SAP System

75. End Of ADM100