Merge pull request #314581 from Xelu86/deploysdaf

[Update] SAP system deployment for SAP Deployment Automation Framework

Author: denrea

articles/sap/automation/deploy-system.md

@@ -1,52 +1,51 @@
 ---
-title: SAP system deployment for the automation framework
-description: Overview of the SAP system deployment process in SAP Deployment Automation Framework.
+title: SAP system deployment for SAP Deployment Automation Framework
+description: Learn about the SAP system deployment process in SAP Deployment Automation Framework, including database, application, central services, and web dispatcher tiers.
 author: kimforss
 ms.author: kimforss
-ms.reviewer: kimforss
-ms.date: 11/17/2021
+ms.date: 04/10/2026
 ms.topic: concept-article
 ms.service: sap-on-azure
 ms.subservice: sap-automation
 # Customer intent: As a system administrator, I want to deploy an SAP system using the automation framework, so that I can efficiently configure and manage virtual machines and supporting components for my SAP applications.
 ---
 
-# SAP system deployment for the automation framework
+# SAP system deployment for SAP Deployment Automation Framework
 
-The creation of the [SAP system](deployment-framework.md#sap-concepts) is part of the [SAP Deployment Automation Framework](deployment-framework.md) process. The SAP system deployment creates your virtual machines (VMs) and supporting components for your [SAP application](deployment-framework.md#sap-concepts).
+An SAP system deployment is a step in [SAP Deployment Automation Framework](deployment-framework.md) that provisions the virtual machines (VMs), disks, and load balancers your SAP application needs. Instead of manually creating each resource, you define parameters and the framework deploys a correctly sized infrastructure.
 
 The SAP system deploys:
 
 - The [database tier](#database-tier), which deploys database VMs, their disks, and a Standard instance of Azure Load Balancer. You can run [HANA databases](configure-extra-disks.md#hana-databases) or [AnyDB databases](configure-extra-disks.md#anydb-databases) in this tier.
-- The [SAP central services tier](#central-services-tier), which deploys a customer-defined number of VMs and a Standard instance of Load Balancer.
+- The [SAP central services tier](#central-services-tier), which deploys a customer-defined number of VMs and a Standard instance of Azure Load Balancer.
 - The [application tier](#application-tier), which deploys the VMs and their disks.
 - The [web dispatcher tier](#web-dispatcher-tier).
 
 ## Application tier
 
-The application tier deploys a customer-defined number of VMs. These VMs are size **Standard_D4s_v3** with a 30-GB operating system (OS) disk and a 512-GB data disk.
+The application tier deploys a customer-defined number of VMs. The default VM size is **Standard_D4s_v3**, with a 30-GB operating system (OS) disk and a 512-GB data disk.
 
-To set the application server count, define the parameter `application_server_count` for this tier in your parameter file. For example, use `application_server_count= 3`.
+To set the application server count, define the parameter `application_server_count` for this tier in your parameter file. For example, use `application_server_count=3`.
 
 ## Central services tier
 
-The SAP central services (SCS) tier deploys a customer-defined number of VMs. These VMs are size **Standard_D4s_v3** with a 30-GB OS disk and a 512-GB data disk. This tier also deploys a [Standard instance of Load Balancer](../../load-balancer/load-balancer-overview.md).
+The SAP central services (SCS) tier deploys a customer-defined number of VMs. The default VM size is **Standard_D4s_v3**, with a 30-GB OS disk and a 512-GB data disk. This tier also deploys a [Standard instance of Azure Load Balancer](../../load-balancer/load-balancer-overview.md).
 
 To set the SCS server count, define the parameter `scs_server_count` for this tier in your parameter file. For example, use `scs_server_count=1`.
 
 ## Web dispatcher tier
 
-The web dispatcher tier deploys a customer-defined number of VMs. This tier also deploys a [Standard instance of Load Balancer](../../load-balancer/load-balancer-overview.md).
+The web dispatcher tier deploys a customer-defined number of VMs. This tier also deploys a [Standard instance of Azure Load Balancer](../../load-balancer/load-balancer-overview.md).
 
-To set the web server count, define the parameter `web_server_count` for this tier in your parameter file. For example, use `web_server_count = 2`.
+To set the web server count, define the parameter `web_server_count` for this tier in your parameter file. For example, use `web_server_count=2`.
 
 ## Database tier
 
-The database tier deploys the VMs and their disks and also deploys a [Standard instance of Load Balancer](../../load-balancer/load-balancer-overview.md). You can use either [HANA databases](configure-extra-disks.md#hana-databases) or [AnyDB databases](configure-extra-disks.md#anydb-databases) as your database VMs.
+The database tier deploys the VMs and their disks and also deploys a [Standard instance of Azure Load Balancer](../../load-balancer/load-balancer-overview.md). You can use either [HANA databases](configure-extra-disks.md#hana-databases) or [AnyDB databases](configure-extra-disks.md#anydb-databases) as your database VMs.
 
 You can set the size of database VMs with the parameter `size` for this tier. For example, use `"size": "S4Demo"` for HANA databases or `"size": "1 TB"` for AnyDB databases. For possible values, see the **Size** parameter in the tables of [HANA database VM options](configure-extra-disks.md#hana-databases) and [AnyDB database VM options](configure-extra-disks.md#anydb-databases).
 
-By default, the automation framework deploys the correct disk configuration for HANA database deployments. For HANA database deployments, the framework calculates default disk configuration based on VM size. However, for AnyDB database deployments, the framework calculates default disk configuration based on database size. You can set a disk size as needed by creating a custom JSON file in your deployment. For an example, [see the following JSON code sample and replace values as necessary for your configuration](configure-extra-disks.md#custom-sizing-file). Then, define the parameter `db_disk_sizes_filename` in the parameter file for the database tier. An example is `db_disk_sizes_filename = "path/to/JSON/file"`.
+By default, the automation framework calculates the disk configuration for HANA database deployments based on VM size. For AnyDB database deployments, the framework calculates the disk configuration based on database size. You can set a disk size as needed by creating a custom JSON file in your deployment. For an example, see the [custom sizing file](configure-extra-disks.md#custom-sizing-file) and replace values as necessary for your configuration. Then, define the parameter `db_disk_sizes_filename` in the parameter file for the database tier. An example is `db_disk_sizes_filename = "path/to/JSON/file"`.
 
 You can also [add extra disks to a new system](configure-extra-disks.md#custom-sizing-file) or [add extra disks to an existing system](configure-extra-disks.md#add-extra-disks-to-an-existing-system).
 
@@ -55,16 +54,16 @@ You can also [add extra disks to a new system](configure-extra-disks.md#custom-s
 The following example parameter file shows only required parameters.
 
 ```bash
-# The environment value is a mandatory field, it is used for partitioning the environments, for example (PROD and NP)
+# The environment value is a required field, it is used for partitioning the environments, for example (PROD and NP)
 environment="DEV"
 
-# The location value is a mandatory field, it is used to control where the resources are deployed
+# The location value is a required field, it is used to control where the resources are deployed
 location="westeurope"
 
-# The network logical name is mandatory - it is used in the naming convention and should map to the workload virtual network logical name 
+# The network logical name is required - it is used in the naming convention and should map to the workload virtual network logical name
 network_name="SAP01"
 
-# sid is a mandatory field that defines the SAP Application SID
+# sid is a required field that defines the SAP Application SID
 sid="S15"
 
 app_tier_vm_sizing="Production"
@@ -108,32 +107,25 @@ ers_instance_number="02"
 
 # webdispatcher_server_count defines how many web dispatchers to deploy
 webdispatcher_server_count=0
-
-
 ```
 
 ## Deploy the SAP system
 
-The sample SAP system configuration file `DEV-WEEU-SAP01-X01.tfvars` is located in the `~/Azure_SAP_Automated_Deployment/samples/WORKSPACES/SYSTEM/DEV-WEEU-SAP01-X01` folder.
+The sample SAP system configuration file `DEV-WEEU-SAP01-X01.tfvars` is in the `~/Azure_SAP_Automated_Deployment/samples/WORKSPACES/SYSTEM/DEV-WEEU-SAP01-X01` folder.
 
 Run the following command to deploy the SAP system.
 
 # [Linux](#tab/linux)
 
-Perform this task from the deployer.
-
-You can copy the sample configuration files to start testing the deployment automation framework.
+Perform this task from the deployer. You can copy the sample configuration files to start testing the deployment automation framework.
 
 ```bash
 cd ~/Azure_SAP_Automated_Deployment
 
 cp -Rp sap-automation/deploy/samples/WORKSPACES config
-
 ```
 
-
 ```bash
-
 export CONFIG_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/config/WORKSPACES"
 export SAP_AUTOMATION_REPO_PATH="${HOME}/Azure_SAP_Automated_Deployment/sap-automation"
 
@@ -143,37 +135,34 @@ ${SAP_AUTOMATION_REPO_PATH}/deploy/scripts/installer.sh     \
         --parameterfile DEV-WEEU-SAP01-X01.tfvars           \
         --type sap_system --auto-approve
 ```
+
 # [Windows](#tab/windows)
 
 You can copy the sample configuration files to start testing the deployment automation framework.
 
 ```powershell
-
 cd C:\Azure_SAP_Automated_Deployment
 
 xcopy sap-automation\deploy\samples\WORKSPACES WORKSPACES
-
 ```
 
 ```powershell
-
 cd C:\Azure_SAP_Automated_Deployment\WORKSPACES\SYSTEM\DEV-WEEU-SAP01-X01
 
-New-SAPSystem -Parameterfile DEV-WEEU-SAP01-X01.tfvars 
--Type sap_system
+New-SAPSystem -Parameterfile DEV-WEEU-SAP01-X01.tfvars -Type sap_system
 ```
 
 # [Azure DevOps](#tab/devops)
 
 Open [Azure DevOps](https://dev.azure.com) and go to your Azure DevOps Services project.
 
-Ensure that the `Deployment_Configuration_Path` variable in the `SDAF-General` variable group is set to the folder that contains your configuration files. For this example, you can use `samples/WORKSPACES`.
+Make sure that the `Deployment_Configuration_Path` variable in the `SDAF-General` variable group is set to the folder that contains your configuration files. For this example, you can use `samples/WORKSPACES`.
 
 The deployment uses the configuration defined in the Terraform variable file located in the `samples/WORKSPACES/SYSTEM/DEV-WEEU-SAP01-X00` folder.
 
 Run the pipeline by selecting the `SAP system deployment` pipeline from the **Pipelines** section. Enter `DEV-WEEU-SAP01-X00` as the SAP system configuration name.
 
-You can track the progress in the Azure DevOps Services portal. After the deployment is finished, you can see the SAP system details on the **Extensions** tab.
+You can track the progress in the Azure DevOps Services portal. After the deployment finishes, you can see the SAP system details on the **Extensions** tab.
 
 ---