You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sap/automation/deployment-framework.md
+25-30Lines changed: 25 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,16 @@ description: Overview of the framework and tooling for SAP Deployment Automation
4
4
author: kimforss
5
5
ms.author: kimforss
6
6
ms.reviewer: kimforss
7
-
ms.date: 12/21/2023
7
+
ms.date: 02/09/2026
8
8
ms.service: sap-on-azure
9
9
ms.subservice: sap-automation
10
10
ms.topic: concept-article
11
11
# Customer intent: As a cloud architect, I want to utilize the SAP Deployment Automation Framework, so that I can efficiently deploy, manage, and maintain SAP environments on Azure while ensuring optimal resource allocation and adherence to best practices.
12
12
---
13
+
13
14
# SAP Deployment Automation Framework
14
15
15
-
[SAP Deployment Automation Framework](https://github.com/Azure/sap-automation) is an open-source orchestration tool that can deploy, install, and maintain SAP environments. You can deploy the systems on any of the SAP-supported operating system versions and into any Azure region. You can create infrastructure for SAP landscapes based on SAP HANA and NetWeaver with AnyDB by using [Terraform](https://www.terraform.io/). The environments can be configured using [Ansible](https://www.ansible.com/).
16
+
[SAP Deployment Automation Framework](https://github.com/Azure/sap-automation) is an open-source orchestration tool that can deploy, install, and maintain SAP environments. You can deploy the systems on any of the SAP-supported operating system versions and into any Azure region. You can create infrastructure for SAP landscapes based on SAP High-Performance Analytic Appliance (HANA) and NetWeaver with AnyDB by using [Terraform](https://www.terraform.io/). The environments can be configured using [Ansible](https://www.ansible.com/).
16
17
17
18
[Terraform](https://www.terraform.io/) from Hashicorp is an open-source tool for provisioning and managing cloud infrastructure.
18
19
@@ -40,8 +41,7 @@ You can use the automation framework to deploy the following SAP architectures:
40
41
-**Distributed**: With this architecture, you can separate the database server and the application tier. The application tier can further be separated in two by having SAP central services on a VM and one or more application servers.
41
42
-**Distributed (highly available)**: This architecture is similar to the distributed architecture. In this deployment, the database and/or SAP central services can both be configured by using a highly available configuration that uses two VMs, each with Pacemaker clusters.
42
43
43
-
44
-
## About the control plane
44
+
## The control plane
45
45
46
46
The control plane houses the deployment infrastructure from which other environments are deployed. After the control plane is deployed, it rarely needs to be redeployed, if ever.
47
47
@@ -78,10 +78,9 @@ For more information about how to configure and deploy the control plane, see [C
78
78
79
79
These VMs are used to run the orchestration scripts that deploy the Azure resources by using Terraform. They're also Ansible controllers and are used to execute the Ansible playbooks on all the managed nodes, that is, the VMs of an SAP deployment.
80
80
81
-
82
81
## About the SAP workload zone
83
82
84
-
The workload zone allows for partitioning of the SAP systems deployments into different environments, such as development, test, and production. The workload zone provides the shared resources (networking and credentials management) that are used by the SAP systems.
83
+
The workload zone allows for partitioning of the SAP systems deployments into different environments, such as development, test, and production. The workload zone provides the shared resources (networking and credentials management) that are used by the SAP systems.
85
84
86
85
You would typically create a workload zone for each unique Azure Virtual network (VNet) that you want to deploy the SAP systems into.
87
86
@@ -91,22 +90,21 @@ The SAP workload zone provides the following services to the SAP systems:
91
90
- Azure Key Vault for system credentials (VMs and SAP accounts)
92
91
- Shared storage (optional)
93
92
94
-
It is recommended to deploy the workload zone into a spoke subscription in a [hub-and-spoke architecture](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) and use a dedicated deployment credential for each workload zone.
93
+
The recommendation is to deploy the workload zone into a spoke subscription in a [hub-and-spoke architecture](/azure/architecture/reference-architectures/hybrid-networking/hub-spoke) and use a dedicated deployment credential for each workload zone.
95
94
96
95
For more information about how to configure and deploy the SAP workload zone, see [Configure the workload zone](configure-workload-zone.md) and [Deploy the SAP workload zone](deploy-workload-zone.md).
97
96
98
97
## About the SAP systems
99
98
100
-
Each SAP system is deployed into a dedicated resource group and they use the services from the workload zone.
99
+
Each SAP system is deployed into a dedicated resource group and they use the services from the workload zone.
101
100
102
101
The SAP system deployment consists of the VMs and the associated resources required to run the SAP application, including the web, app, and database tiers.
103
102
104
103
For more information about how to configure and deploy the SAP system, see [Configure the SAP system](configure-system.md) and [Deploy the SAP system](deploy-system.md).
105
104
106
-
107
105
## Software acquisition process
108
106
109
-
The framework also provides an Ansible playbook that can be used to download the software from SAP and persist it in the storage accounts in the control plane's SAP library resource group.
107
+
The framework includes an Ansible playbook designed to automate the download of SAP software. This playbook retrieves the required software from SAP and stores it in the SAP library storage accounts within the control plane resource group.
110
108
111
109
The software acquisition is using an SAP application manifest file that contains the list of SAP software to be downloaded. The manifest file is a YAML file that contains the:
112
110
@@ -124,33 +122,30 @@ The following terms are important concepts for understanding the automation fram
> | System | An instance of an SAP application that contains the resources the application needs to run. Defined by a unique three-letter identifier, the *SID*.
131
-
> | Landscape | A collection of systems in different environments within an SAP application. For example, SAP ERP Central Component (ECC), SAP customer relationship management (CRM), and SAP Business Warehouse (BW). |
132
-
> | Workload zone | Partitions the SAP applications to environments, such as nonproduction and production environments or development, quality assurance, and production environments. Provides shared resources, such as virtual networks and key vaults, to all systems within. |
| System | An instance of an SAP application that contains the resources the application needs to run. Defined by a unique three-letter identifier, the *SID*. |
128
+
| Landscape | A collection of systems in different environments within an SAP application. For example, SAP ERP Central Component (ECC), SAP customer relationship management (CRM), and SAP Business Warehouse (BW). |
129
+
| Workload zone | Partitions the SAP applications to environments, such as nonproduction and production environments or development, quality assurance, and production environments. Provides shared resources, such as virtual networks and key vaults, to all systems within. |
133
130
134
131
The following diagram shows the relationships between SAP systems, workload zones (environments), and landscapes. In this example setup, the customer has three SAP landscapes: ECC, CRM, and BW. Each landscape contains three workload zones: production, quality assurance, and development. Each workload zone contains one or more systems.
135
132
136
133
:::image type="content" source="./media/deployment-framework/sap-terms.png" alt-text="Diagram that shows the SAP configuration with landscapes, workflow zones, and systems.":::
0 commit comments