- SAP Basis Tutorial
- SAP Basis - Home
- SAP Basis - Overview
- SAP Basis - Installation of SAP GUI
- SAP Basis - GUI Selection
- System Landscape & Architecture
- Hardware & Software Installation
- SAP Basis - NW System
- SAP Basis - NW Architecture
- SAP Basis - SAP Client Administration
- SAP Basis - User Activities
- Number of Login Attempts
- SAP Basis - Job Processing
- Unscheduling a Background Job
- Monitoring a Background Job
- Deleting a Background Job
- SAP Basis - Managing Transports
- Managing Transport Routes
- SAP Basis - Patch Management
- SAP Basis - Importing A Queue
- Kernel Upgrade & Patching
- SAP Basis - System Monitoring
- SAP Basis - Remote Function Call
- RFC Between ECC & HANA
- SAP Basis - New Dimensional Product
- SAP Basis Useful Resources
- SAP Basis - Questions Answers
- SAP Basis - Quick Guide
- SAP Basis - Useful Resources
- SAP Basis - Discussion
- Selected Reading
- UPSC IAS Exams Notes
- Developer's Best Practices
- Questions and Answers
- Effective Resume Writing
- HR Interview Questions
- Computer Glossary
- Who is Who
System Landscape & Architecture
SAP system landscape is defined as an arrangement of SAP servers. Ideally, in a Sap environment, a three-system landscape exists. A system landscape consists of Development Server (Dev), Production Server (PROD), and Quality Assurance server (QAS).
SAP Architecture is defined as a technology framework of SAP system and it changes with time unlike the system landscape. SAP Architecture changes with new software like SAP ECC 6.0, the most recent one.
The following is a request in SAP System Landscape −
DEVELOPMENT >>>> Quality >>>> PRODUCTION
The following figure represents SAP three tier system landscape where work flows from Dev > QAS > PROD and not in backward direction.
Let us now discuss the system landscape −
When a project is implemented, at the initial stages, a sandbox server is used where all the customization, configuration is performed.
Next is to save the configuration in development server and saved in workbench requests and this has to be transported to Production server.
You can consider it as the final or the most refined stage where the work is done when project is in production/go live. All the changes that are required by the client are performed in the DEV environment and later, the request is transported to production.
SAP System 3 – Tier Architecture
The image given below shows 3-tier architecture of the SAP system. The presentation layer is the topmost one. This contains the device/application to control the SAP system. This can include mobile devices, end user systems or SAP GUI or web browser based client.
The presentation layer communicates with the application server to perform all the processing and which is known as brains of an SAP system.
An application server consists of multiple instances and communicates with the database layer of the three-tier architecture.
The bottom layer is called the database layer. This is responsible to store all the data. The database of SAP system is kept on a separate server for performance and security reasons.
The presentation layer consists of different components for ABAP and JAVA that enables the communication and processing of data in SAP system.
The key components of the presentation layer include the following −
Message Server − This is used to manage communication between distributed dispatchers in the ABAP system.
Message Server − This is used to manage server processes and JAVA dispatchers. It is used to manage communication within JRE.
Dispatcher Queue − This is used to store multiple work process types.
Dispatcher − This is used to distribute the requests to the work processes.
Memory Pipes − This is used to manage communication between ICM and ABAP work processes.
Enqueue Server − This is used to handle logical locks set by the executed Java application program.
Java Dispatcher − This is responsible to receive the client requests via presentation layer and forward to the server process.
Gateway − This is used to manage communication between SAP system and external systems.
ABAP Work processes − This separately executes dialog steps in R/3 applications separately.