Skip to content

Commit c544d0b

Browse files
v-regandownerv-regandowner
authored
Merge pull request #195496 from KimForss/main
Oracle support
2 parents deb3ee4 + fbe7ef0 commit c544d0b

File tree

2 files changed

+180
-5
lines changed

2 files changed

+180
-5
lines changed

‎articles/virtual-machines/workloads/sap/automation-configure-sap-parameters.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,43 @@ disks:
107107
- { host: 'rh8scs01l84f', LUN: 0, type: 'sap' }
108108
```
109109
110+
### Oracle support
111+
112+
From the v3.4 release, it is possible to deploy SAP on Azure systems in a Shared Home configuration using an Oracle database backend. For more information on running SAP on Oracle in Azure, see [Azure Virtual Machines Oracle DBMS deployment for SAP workload](dbms_guide_oracle.md).
113+
114+
In order to install the Oracle backend using the SAP Deployment Automation Framework, you need to provide the following parameters
115+
116+
> [!div class="mx-tdCol2BreakAll "]
117+
> | Parameter | Description | Type |
118+
> | ---------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------- |
119+
> | `platform` | The database backend, 'ORACLE' | Required |
120+
> | `ora_release` | The Oracle release version, for example 19 | Required |
121+
> | `ora_release` | The Oracle release version, for example 19.0.0 | Required |
122+
> | `oracle_sbp_patch` | The Oracle SBP patch file name | Required |
123+
124+
### Shared Home support
125+
126+
To configure shared home support for Oracle, you need to add a dictionary defining the SIDs to be deployed. You can do that by adding the parameter 'MULTI_SIDS' that contains a list of the SIDs and the SID details.
127+
128+
```yaml
129+
MULTI_SIDS:
130+
- {sid: 'DE1', dbsid_uid: '3005', sidadm_uid: '2001', ascs_inst_no: '00', pas_inst_no: '00', app_inst_no: '00'}
131+
- {sid: 'QE1', dbsid_uid: '3006', sidadm_uid: '2002', ascs_inst_no: '01', pas_inst_no: '01', app_inst_no: '01'}
132+
```
133+
134+
Each row must specify the following parameters.
135+
136+
> [!div class="mx-tdCol2BreakAll "]
137+
> | Parameter | Description | Type |
138+
> | ---------------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------- |
139+
> | `sid` | The SID for the instance | Required |
140+
> | `dbsid_uid` | The UID for the DB admin user for the instance | Required |
141+
> | `sidadm_uid` | The UID for the SID admin user for the instance | Required |
142+
> | `ascs_inst_no` | The ASCS instance number for the instance | Required |
143+
> | `pas_inst_no` | The PAS instance number for the instance | Required |
144+
> | `app_inst_no` | The APP instance number for the instance | Required |
145+
146+
110147
## Next steps
111148

112149
> [!div class="nextstepaction"]

‎articles/virtual-machines/workloads/sap/automation-naming-module.md

Lines changed: 143 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Configure custom naming module for the automation framework
2+
title: Configure custom naming for the automation framework
33
description: Explanation of how to implement custom naming conventions for the SAP deployment automation framework on Azure.
44
author: kimforss
55
ms.author: kimforss
@@ -9,13 +9,151 @@ ms.topic: conceptual
99
ms.service: virtual-machines-sap
1010
---
1111

12-
# Configure custom naming module
12+
# Overview
1313

1414
The [SAP deployment automation framework on Azure](automation-deployment-framework.md) uses a standard naming convention for Azure [resource naming](automation-naming.md).
1515

16-
The Terraform module `sap_namegenerator` defines the names of all resources that the automation framework deploys. The module is located at `/deploy/terraform/terraform-units/modules/sap_namegenerator/` in the repository.
16+
The Terraform module `sap_namegenerator` defines the names of all resources that the automation framework deploys. The module is located at `/deploy/terraform/terraform-units/modules/sap_namegenerator/` in the repository. The framework also supports providing you own names for some of the resources using the [parameter files](automation-configure-system.md).
1717

18-
The framework also supports providing you own names for some of the resources using the [parameter files](automation-configure-system.md). If these capabilities are not enough you can also use custom naming logic by modifying the naming module used by the automation.
18+
If these capabilities are not enough, you can also use custom naming logic by either providing a custom json file containing the resource names or by modifying the naming module used by the automation.
19+
20+
## Provide name overrides using a json file
21+
22+
You can specify a custom naming json file in your tfvars parameter file using the 'name_override_file' parameter.
23+
24+
The json file has sections for the different resource types.
25+
26+
The deployment types are:
27+
28+
- DEPLOYER (Control Plane)
29+
- SDU (SAP System Infrastructure)
30+
- VNET (Workload zone)
31+
32+
### Key Vault names
33+
34+
The names for the key vaults are defined in the "keyvault_names" structure. The example below lists the key vault names for a deployment in the "DEV" environment in West Europe.
35+
36+
```json
37+
"keyvault_names": {
38+
"DEPLOYER": {
39+
"private_access": "DEVWEEUprvtABC",
40+
"user_access": "DEVWEEUuserABC"
41+
},
42+
"SDU": {
43+
"private_access": "DEVWEEUSAP01X00pABC",
44+
"user_access": "DEVWEEUSAP01X00uABC"
45+
},
46+
"VNET": {
47+
"private_access": "DEVWEEUSAP01prvtABC",
48+
"user_access": "DEVWEEUSAP01userABC"
49+
}
50+
}
51+
```
52+
53+
> [!NOTE]
54+
> This key vault names need to be unique across Azure, SDAF appends 3 random characters (ABC in the example) at the end of the key vault name to reduce the likelihood for name conflicts.
55+
56+
The "private_access" names are currently not used.
57+
58+
### Storage Account names
59+
60+
The names for the storage accounts are defined in the "storageaccount_names" structure. The example below lists the storage account names for a deployment in the "DEV" environment in West Europe.
61+
62+
```json
63+
"storageaccount_names": {
64+
"DEPLOYER": "devweeudiagabc",
65+
"LIBRARY": {
66+
"library_storageaccount_name": "devweeusaplibabc",
67+
"terraformstate_storageaccount_name": "devweeutfstateabc"
68+
},
69+
"SDU": "devweeusap01diagabc",
70+
"VNET": {
71+
"landscape_shared_transport_storage_account_name": "devweeusap01sharedabc",
72+
"landscape_storageaccount_name": "devweeusap01diagabc",
73+
"witness_storageaccount_name": "devweeusap01witnessabc"
74+
}
75+
}
76+
```
77+
78+
> [!NOTE]
79+
> This key vault names need to be unique across Azure, SDAF appends 3 random characters (abc in the example) at the end of the key vault name to reduce the likelihood for name conflicts.
80+
81+
### Virtual Machine names
82+
83+
The names for the virtual machines are defined in the "virtualmachine_names" structure. Both the computer and the virtual machine names can be provided.
84+
85+
The example below lists the virtual machine names for a deployment in the "DEV" environment in West Europe. The deployment has a database server, two application servers, a Central Services server and a web dispatcher.
86+
87+
```json
88+
"virtualmachine_names": {
89+
"ANCHOR_COMPUTERNAME": [],
90+
"ANCHOR_SECONDARY_DNSNAME": [],
91+
"ANCHOR_VMNAME": [],
92+
"ANYDB_COMPUTERNAME": [
93+
"x00db00l0abc"
94+
],
95+
"ANYDB_SECONDARY_DNSNAME": [
96+
"x00dhdb00l0abc",
97+
"x00dhdb00l1abc"
98+
],
99+
"ANYDB_VMNAME": [
100+
"x00db00l0abc"
101+
],
102+
"APP_COMPUTERNAME": [
103+
"x00app00labc",
104+
"x00app01labc"
105+
],
106+
"APP_SECONDARY_DNSNAME": [
107+
"x00app00labc",
108+
"x00app01labc"
109+
],
110+
"APP_VMNAME": [
111+
"x00app00labc",
112+
"x00app01labc"
113+
],
114+
"DEPLOYER": [
115+
"devweeudeploy00"
116+
],
117+
"HANA_COMPUTERNAME": [
118+
"x00dhdb00l0af"
119+
],
120+
"HANA_SECONDARY_DNSNAME": [
121+
"x00dhdb00l0abc"
122+
],
123+
"HANA_VMNAME": [
124+
"x00dhdb00l0abc"
125+
],
126+
"ISCSI_COMPUTERNAME": [
127+
"devsap01weeuiscsi00"
128+
],
129+
"OBSERVER_COMPUTERNAME": [
130+
"x00observer00labc"
131+
],
132+
"OBSERVER_VMNAME": [
133+
"x00observer00labc"
134+
],
135+
"SCS_COMPUTERNAME": [
136+
"x00scs00labc"
137+
],
138+
"SCS_SECONDARY_DNSNAME": [
139+
"x00scs00labc"
140+
],
141+
"SCS_VMNAME": [
142+
"x00scs00labc"
143+
],
144+
"WEB_COMPUTERNAME": [
145+
"x00web00labc"
146+
],
147+
"WEB_SECONDARY_DNSNAME": [
148+
"x00web00labc"
149+
],
150+
"WEB_VMNAME": [
151+
"x00web00labc"
152+
]
153+
}
154+
```
155+
156+
## Configure custom naming module
19157

20158
There are multiple files within the module for naming resources:
21159

@@ -30,7 +168,7 @@ The different resource names are identified by prefixes in the Terraform code.
30168
- SAP landscape deployments use resource names with the prefix `vnet_`
31169
- SAP system deployments use resource names with the prefix `sdu_`
32170

33-
The calculated names are returned in a data dictionary which is used by all the terraform modules.
171+
The calculated names are returned in a data dictionary, which is used by all the terraform modules.
34172

35173
## Using custom names
36174

0 commit comments

Comments
 (0)