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/get-started.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,10 +19,10 @@ Get started quickly with [SAP Deployment Automation Framework](deployment-framew
19
19
To get started with SAP Deployment Automation Framework, you need:
20
20
21
21
- An Azure subscription. If you don't have an Azure subscription, you can [create a free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
22
-
- The ability to [download the SAP software](software.md) in your Azure environment.
23
-
- An [Azure CLI](/cli/azure/install-azure-cli) installation on your local computer.
24
-
- An [Azure PowerShell](/powershell/azure/install-az-ps#update-the-azure-powershell-module) installation on your local computer.
22
+
- An SAP USer account with permissions to [download the SAP software](software.md) in your Azure environment. See [SAP S-User](https://support.sap.com/en/my-support/users/welcome.html) for more information.
23
+
- An [Azure CLI](/cli/azure/install-azure-cli) installation.
25
24
- A service principal to use for the control plane deployment.
25
+
- A service principal to use for the workload zone deployment.
26
26
- An ability to create an Azure DevOps project if you want to use Azure DevOps for deployment.
27
27
28
28
Some of the prerequisites might already be installed in your deployment environment. Both Azure Cloud Shell and the deployer have Terraform and the Azure CLI installed.
## Get SAP software by using the Bill of Materials
600
-
601
-
The automation framework gives you tools to download software from SAP by using the SAP BOM. The software is downloaded to the SAP library, which acts as the archive for all media required to deploy SAP.
602
-
603
-
The SAP BOM mimics the SAP maintenance planner. There are relevant product identifiers and a set of download URLs.
604
-
605
-
A sample extract of a BOM file looks like this example:
- name: "Kernel Part I ; OS: Linux on x86_64 64bit ; DB: Database independent"
641
-
```
642
-
643
-
For this example configuration, the resource group is `MGMT-NOEU-DEP00-INFRASTRUCTURE`. The deployer key vault name contains `MGMTNOEUDEP00user` in the name. You use this information to configure your deployer's key vault secrets.
644
-
645
-
1. Connect to your deployer VM for the following steps. A copy of the repo is now there.
646
-
647
-
1. Add a secret with the username for your SAP user account. Replace `<vaultID>` with the name of your deployer key vault. Also replace `<sap-username>` with your SAP username.
648
-
649
-
```bash
650
-
export key_vault=<vaultID>
651
-
sap_username=<sap-username>
652
-
653
-
az keyvault secret set --name "S-Username" --vault-name $key_vault --value "${sap_username}";
654
-
```
655
-
656
-
1. Add a secret with the password for your SAP user account. Replace `<vaultID>` with your deployer key vault name and replace `<sap-password>` with your SAP password.
657
-
658
-
> [!NOTE]
659
-
> The use of single quotation marks when you set `sap_user_password` is important. The use of special characters in the password can otherwise cause unpredictable results.
660
-
661
-
```azurecli
662
-
sap_user_password='<sap-password>'
663
-
664
-
az keyvault secret set --name "S-Password" --vault-name "${key_vault}" --value "${sap_user_password}";
665
-
```
666
-
667
-
1. Check the version number of the S/4 1909 SPS03 BOM for the active version.
668
-
669
-
Record the results.
670
-
671
-
```bash
672
-
673
-
ls -d ${DEPLOYMENT_REPO_PATH}/deploy/ansible/BOM-catalog/S41909SPS03* | xargs basename
674
-
675
-
```
676
-
677
-
1. Configure your SAP parameters file for the download process. Then, download the SAP software by using Ansible playbooks. Run the following commands:
1. Update the `bom_base_name` with the name BOM previously identified.
688
-
689
-
Your file should look similar to the following example configuration:
690
-
691
-
```yaml
692
-
693
-
bom_base_name: S4HANA_2021_FP01_v0001ms
694
-
695
-
```
696
-
697
-
1. Replace `<Deployer KeyVault Name>` with the name of the deployer resource group Azure key vault.
698
-
699
-
Your file should look similar to the following example configuration:
700
-
701
-
```yaml
702
-
703
-
bom_base_name: S4HANA_2021_FP01_v0001ms
704
-
deployer_kv_name: <Deployer KeyVault Name>
705
-
706
-
```
707
-
708
-
1. Ensure that `check_storage_account` is present and set to `false`. This value controls if the SAP library is checked for the file before it's downloaded from SAP.
709
-
710
-
Your file should look similar to the following example configuration:
Select the playbook `1) BoM Downloader` to download the SAP software described in the BOM file into the storage account. Check that the `sapbits` container has all your media for installation.
735
-
736
597
## Collect workload zone information
737
598
738
599
1. Collect the following information in a text editor. This information was collected at the end of the "Deploy the control plane" phase.
Check that the system resource group is now in the Azure portal.
901
762
763
+
## Get SAP software by using the Bill of Materials
764
+
765
+
The automation framework gives you tools to download software from SAP by using the SAP BOM. The software is downloaded to the SAP library, which acts as the archive for all media required to deploy SAP.
766
+
767
+
The SAP BOM mimics the SAP maintenance planner. There are relevant product identifiers and a set of download URLs.
768
+
769
+
A sample extract of a BOM file looks like this example:
- name: "Kernel Part I ; OS: Linux on x86_64 64bit ; DB: Database independent"
805
+
```
806
+
807
+
For this example configuration, the resource group is `MGMT-NOEU-DEP00-INFRASTRUCTURE`. The deployer key vault name contains `MGMTNOEUDEP00user`in the name. You use this information to configure your deployer's key vault secrets.
808
+
809
+
1. Connect to your deployer VM for the following steps. A copy of the repo is now there.
810
+
811
+
1. Add a secret with the username for your SAP user account. Replace `<vaultID>` with the name of your deployer key vault. Also replace `<sap-username>` with your SAP username.
812
+
813
+
```bash
814
+
export key_vault=<vaultID>
815
+
sap_username=<sap-username>
816
+
817
+
az keyvault secret set --name "S-Username" --vault-name $key_vault --value "${sap_username}";
818
+
```
819
+
820
+
1. Add a secret with the password for your SAP user account. Replace `<vaultID>` with your deployer key vault name and replace `<sap-password>` with your SAP password.
821
+
822
+
> [!NOTE]
823
+
> The use of single quotation marks when you set `sap_user_password` is important. The use of special characters in the password can otherwise cause unpredictable results.
824
+
825
+
```azurecli
826
+
sap_user_password='<sap-password>'
827
+
828
+
az keyvault secret set --name "S-Password" --vault-name "${key_vault}" --value "${sap_user_password}";
829
+
```
830
+
831
+
1. Configure your SAP parameters file for the download process. Then, download the SAP software by using Ansible playbooks. Run the following commands:
832
+
833
+
```bash
834
+
cd ~/Azure_SAP_Automated_Deployment/WORKSPACES
835
+
mkdir BOMS
836
+
cd BOMS
837
+
838
+
vi sap-parameters.yaml
839
+
```
840
+
841
+
1. Update the `bom_base_name` with the name BOM amd replace `<Deployer KeyVault Name>` with the name of the deployer resource group Azure key vault..
842
+
843
+
Your file should look similar to the following example configuration:
1. Run the Ansible playbook to download the software. One way you can run the playbooks is to use the **Downloader** menu. Run the `download_menu` script.
Select the playbook `1) BoM Downloader` to download the SAP software described in the BOM file into the storage account. Check that the `sapbits` container has all your media for installation.
869
+
870
+
902
871
## SAP application installation
903
872
904
873
The SAP application installation happens through Ansible playbooks.
@@ -945,6 +914,10 @@ This playbook installs the HANA database instances.
945
914
946
915
This playbook invokes the database load task from the primary application server.
947
916
917
+
### Playbook: HANA HA playbook
918
+
919
+
This playbook configures HANA system replication and Pacemaker for the HANA database.
920
+
948
921
### Playbook: PAS install
949
922
950
923
This playbook installs the primary application server.
@@ -955,9 +928,6 @@ This playbook installs the application servers.
955
928
956
929
You've now deployed and configured a standalone HANA system. If you need to configure a highly available (HA) SAP HANA database, run the HANA HA playbook.
957
930
958
-
### Playbook: HANA HA playbook
959
-
960
-
This playbook configures HANA system replication and Pacemaker for the HANA database.
0 commit comments