| Status | |
| Owner | |
| Stakeholders |
Introduction
Purpose
The purpose of the document is to outline the application architecture of S/4HANA instance deployed in Europe region.
Scope & Objectives
This document describes the high-level architecture design for S/4HANA and the supporting systems that are deployed together in the RISE environment. It will cover the following topics:
- Landscape overview
- Application and components
- Application security and access
- Operational architecture
Out of scope:
- Detailed architecture designs that are managed by SAP RISE.
- RISE operating model.
Key Decisions and Requirement
| Description | Rationale |
|---|---|
Application Architecture
Overview
Insert the Architecture design below. Architecture can be designed in either Visio or word or another format.Application Architecture Components
Provide the details of each and every major component used in the Application Architecture. Below are some of the sample application components provided as a reference.Landscape and Environment
Application Security
Classification
Security configuration or hardening depends on the classification and the associated risks. Security controls are implemented depending on the classification of the data per IT policy and risk management policy.Authentication
Provide the details of authentication architecture used for the applicationAuthorisation
Provide the authorization guidelines/principles followed for the applicationCommunication Security
Provide the details of the communication security controls implemented based on the classificationData Security
Provide the details of the data security controls implemented based on the classificationOther Controls
Provide the details of any other controls implemented based on the classificationSystem Landscape
Development Environment
Include the DEV environment detailsProject Test Environment
Include the Project Test environment details. Mention Not Applicable, if the environment is not relevant for the applicationQuality Environment
Include the Quality environment details. Mention Not Applicable, if the environment is not relevant for the applicationProduction Environment
Include the PROD environment detailsOperation Architecture
Change and Configuration Management
This section will include the details related to change and configuration management of SAP and non-SAP systems.Transport Management
Provide the details on how transport management will be handledRelease Management
Provide the details on how release management will be handledMonitoring
This section will include the details related to monitoring enabled for the applicationApplication Monitoring
Provide the details of application monitoring configurationSystem Monitoring
Provide the details of System monitoring configurationSizing
Provide the details of sizing approach and the future recommendationsHigh Availability
Provide the details of High Availability. You may provide a reference to other document or attach a document, if the section contains lot of contentDisaster Recovery
Provide the details of Disaster Recovery. You may provide a reference to other document or attach a document, if the section contains lot of contentBackup/Restore
Provide the details of Backup/Restore. You may provide a reference to other document or attach a document, if the section contains lot of contentMaintenance Plan
Provide the details of system and application maintenance plan. This should follow the upgrade strategyService Introduction
Application Category
Provide the details of application category based on application classification. Application category is defined based on RPO, RTO requirementsSupport Team
Provide the details of support team that may be required to support the applicationSkill required
Provide the details of skills that are required to support this applicationChecklist
Provide the checklist for support organization to support the applicationExceptions
This section covers any exceptions to the reference architecture. Some Applications may have limitations and may not meet the Enterprise Architecture, Reference Architecture and IT Policy guidelines. All exceptions should be included in this section.See also
Provide links or references to relevant documents for further context on this architecture decision and its impact. Listing related architectural decisions here can clarify dependencies.