Skip to content

Commit e33eaca

Browse files
authored
Merge pull request #196903 from KimForss/main
Topology updates
2 parents 2cc11b5 + 6bc3363 commit e33eaca

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

articles/virtual-machines/workloads/sap/automation-deployment-framework.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,16 @@ You will use the control plane of the SAP deployment automation framework to dep
2727
>
2828
> This automation framework also follows the [Microsoft Cloud Adoption Framework for Azure](/azure/cloud-adoption-framework/).
2929
30+
The automation framework can be used to deploy the following SAP architectures:
31+
32+
- Standalone
33+
- Distributed
34+
- Distributed (Highly Available)
35+
36+
In the Standalone architecture all the SAP roles are installed on a single server. In the distributed 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 virtual machine and one or more application servers.
37+
38+
The Distributed (Highly Available) deployment is similar to the Distributed architecture but either the datebase or SAP Central Services are both highly available using two virtual machines each with Pacemaker clusters.
39+
3040
The dependency between the control plane and the application plane is illustrated in the diagram below. In a typical deployment a single control plane is used to manage multiple SAP deployments.
3141

3242
:::image type="content" source="./media/automation-deployment-framework/control-plane-sap-infrastructure.png" alt-text="Diagram showing the SAP deployment automation framework's dependency between the control plane and application plane.":::

0 commit comments

Comments
 (0)