This automation solution is designed for the deployment of Three Tier SAP S/4HANA Stack using IBM Cloud Schematics or CLI. The SAP solution will be deployed on top of one of the following Operating Systems: Red Hat Enterprise Linux 8.6 for SAP, Red Hat Enterprise Linux 8.4 for SAP, SUSE Linux Enterprise Server 15 SP 4 for SAP, SUSE Linux Enterprise Server 15 SP 3 for SAP in an existing IBM Cloud Gen2 VPC, using an existing bastion host with secure remote SSH access.
The solution is based on Terraform scripts and Ansible playbooks and it is implementing a 'reasonable' set of best practices for SAP hosts configuration.
It contains:
- Terraform scripts for the deployment of two servers, in an EXISTING VPC, with Subnet and Security Group. The servers are intended to be used: one for the data base instance and the other for the application instance. The automation has support for the following versions: Terraform >= 1.5.7 and IBM Cloud provider for Terraform >= 1.57.0. Note: The deployment was tested with Terraform 1.6.6
- Bash scripts used for the checking of the prerequisites required by SAP servers deployment and for the integration into a single step in IBM Schematics GUI of the server provisioning and the SAP S/4HANA Stack installation.
- Ansible scripts to configure the LVM and filesystems, the OS parameters, a Three Tier SAP S/4HANA primary application server and a HANA 2.0 node. Please note that Ansible is started by Terraform and must be available on the same host.
- 1.1 Installation media
- 1.2 Server Configuration
- 1.3 VPC Configuration
- 1.4 Files description and structure
- 1.5 General input variabiles
- 2.1 Executing the deployment of Three Tiers SAP S4HANA Stack in GUI (Schematics)
- 2.2 Executing the deployment of Three Tiers SAP S4HANA Stack in CLI
- 3.1 Related links
SAP HANA installation media used for this deployment is the default one for SAP HANA, platform edition 2.0 SPS07 available at SAP Support Portal under INSTALLATION AND UPGRADE area and it has to be provided manually in the input parameter file.
SAP S/4HANA installation media used for this deployment is the default one for SAP S/4HANA 2.0 available at SAP Support Portal under INSTALLATION AND UPGRADE area and it has to be provided manually in the input parameter file.
The Servers are deployed with one of the following Operating Systems for DB server: Red Hat Enterprise Linux 8.6 for SAP HANA (amd64), Red Hat Enterprise Linux 8.4 for SAP HANA (amd64), Suse Linux Enterprise Server 15 SP 4 for SAP HANA (amd64), Suse Linux Enterprise Server 15 SP 3 for SAP HANA (amd6) and with one of the following Operating Systems for APP server: Red Hat Enterprise Linux 8.6 for SAP Applications (amd64), Red Hat Enterprise Linux 8.4 for SAP Applications (amd64), Suse Enterprise Linux 15 SP4 for SAP Applications (amd64), Suse Enterprise Linux 15 SP3 for SAP Applications (amd64). The SSH keys are configured to allow root user access. The following storage volumes are creating during the provisioning:
HANA DB VSI Disks:
- the disk sizes depend on the selected profile, according to [Intel Virtual Server certified profiles on VPC infrSAP HANA DB Server Disks:
- the disk sizes depend on the selected profile, according to Intel Virtual Server certified profiles on VPC infrastructure for SAP HANA - Last updated 2023-12-28 and to Bare metal servers certified profiles on VPC infrastructure for SAP HANA - Last updated 2024-05-13
Note: For SAP HANA on a VSI, according to Intel Virtual Server certified profiles on VPC infrastructure for SAP HANA - Last updated 2022-01-28 and to Storage design considerations - Last updated 2024-01-25, LVM will be used for /hana/data, hana/log, /hana/shared and /usr/sap, for all storage profiles, with the following exceptions:
/hana/dataand/hana/sharedfor the following profiles:vx2d-44x616andvx2d-88x1232/hana/sharedfor the following profiles:vx2d-144x2016,vx2d-176x2464,ux2d-36x1008,ux2d-48x1344,ux2d-72x2016,ux2d-100x2800,ux2d-200x5600.
For example, in case of deploying a SAP HANA on a VSI, using the value mx2-16x128 for the VSI profile , the automation will execute the following storage setup:
- 3 volumes x 500 GB each for
<sid>_hana_vgvolume group- the volume group will contain the following logical volumes (created with three stripes):
<sid>_hana_data_lv- size 988 GB<sid>_hana_log_lv- size 256 GB<sid>_hana_shared- size 256 GB
- the volume group will contain the following logical volumes (created with three stripes):
- 1 volume x 50 GB for
/usr/sap(volume group:<sid>_usr_sap_vg, logical volume:<sid>_usr_sap_lv) - 1 volume x 10 GB for a 2 GB SWAP logical volume (volume group:
<sid>_swap_vg, logical volume:<sid>_swap_lv)
In case of deploying a SAP HANA on a Bare Metal Server, using the value bx2d-metal-96x384 for the Bare Metal Server profile, the automation will execute the following storage setup:
- 4 disks x 2.9 TB each for
<sid>_vg0volume group- the volume group will contain the following logical volumes (created with raid10, mirror and two stripes):
<sid>_hana_log_lv- size 384 GB<sid>_hana_shared- size 384 GB
- the volume group will contain the following logical volumes (created with raid10, mirror and two stripes):
- 4 disks x 2.9 TB each for
<sid>_vg1volume group- the volume group will contain the following logical volumes (created with raid10, mirror and two stripes):
<sid>_hana_data_lv- size 100%FREE
- the volume group will contain the following logical volumes (created with raid10, mirror and two stripes):
- 1 directory
/usr/sap - 1 SWAP file of 2 GB
/<sid>_swapfile
SAP APPs VSI Disks:
- 1 disk with 10 IOPS / GB - SWAP (the size depends on the OS profile used, for
bx2-4x16the size will be 48 GB) - 1 x 128 GB disk with 10 IOPS / GB - DATA
In order to perform the deployment you can use either the CLI component or the GUI component (Schematics) of the automation solution.
The Security Rules inherited from BASTION deployment are the following:
- Allow all traffic in the Security group for private networks.
- Allow outbound traffic (ALL for port 53, TCP for ports 80, 443, 8443)
- Allow inbound SSH traffic (TCP for port 22) from IBM Schematics Servers.
The solution is based on Terraform remote-exec and Ansible playbooks executed by Schematics and it is implementing a 'reasonable' set of best practices for SAP server configuration.
modules- directory containing the terraform modules.ansible- directory containing the SAP ansible playbooks.main.tf- contains the configuration of the server for the deployment of the current SAP solution.output.tf- contains the code for the information to be displayed after the server is created (VPC, Hostname, Private IP).integration*.tf & generate*.tffiles - contain the integration code that makes the SAP variabiles from Terraform available to Ansible.provider.tf- contains the IBM Cloud Provider data in order to runterraform initcommand.variables.tf- contains variables for the VPC and server.versions.tf- contains the minimum required versions for terraform and IBM Cloud provider.sch.auto.tfvars- contains programatic variables.
The following parameters can be set:
General input parameters:
| Parameter | Description |
|---|---|
| IBMCLOUD_API_KEY | IBM Cloud API key (Sensitive* value). The IBM Cloud API Key can be created here |
| SSH_KEYS | List of SSH Keys UUIDs that are allowed to SSH as root to the server. Can contain one or more IDs. The list of SSH Keys is available here. Sample input (use your own SSH UUIDs from IBM Cloud): [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ] |
| BASTION_FLOATING_IP | BASTION FLOATING IP. It can be copied from the Bastion Server Deployment "OUTPUTS" at the end of "Apply plan successful" message. |
| RESOURCE_GROUP | The name of an EXISTING Resource Group for servers and Volumes resources. Default value: "Default". The list of Resource Groups is available here. |
| REGION | The cloud region where to deploy the solution. The regions and zones for VPC are listed here. Review supported locations in IBM Cloud Schematics here. Sample value: eu-de. |
| ZONE | The cloud zone where to deploy the solution. Sample value: eu-de-2. |
| VPC | The name of an EXISTING VPC. The list of VPCs is available here |
| SUBNET | The name of an EXISTING Subnet. The list of Subnets is available here. |
| SECURITY_GROUP | The name of an EXISTING Security group. The list of Security Groups is available here. |
Server input parameters
| Parameter | Description |
|---|---|
| HANA_SERVER_TYPE | The type of SAP HANA Server. Allowed vales: "virtual" or "bare metal" |
| DB_HOSTNAME | The Hostname for the HANA Server. The hostname should be up to 13 characters as required by SAP. For more information on rules regarding hostnames for SAP systems, check SAP Note 611361: Hostnames of SAP ABAP Platform servers |
| DB_PROFILE | The instance profile used for the SAP HANA Server. The list of the certified profiles for SAP HANA on a VSI is available here. The list of the certified profiles for SAP HANA on a Bare Metal Server is available here. Details about all x86 instance profiles are available here. For more information about supported DB/OS and IBM Gen 2 Servers, check SAP Note 2927211: SAP Applications on IBM Virtual Private Cloud |
| DB_IMAGE | The OS image used for HANA Server (See Obs*). A list of images is available here. Default value: ibm-redhat-8-6-amd64-sap-hana-6 |
| APP_HOSTNAME | The Hostname for the SAP Application VSI. The hostname should be up to 13 characters as required by SAP. For more information on rules regarding hostnames for SAP systems, check SAP Note 611361: Hostnames of SAP ABAP Platform servers |
| APP_PROFILE | The instance profile used for SAP Application VSI. A list of profiles is available here For more information about supported DB/OS and IBM Gen 2 Virtual Server Instances (VSI), check SAP Note 2927211: SAP Applications on IBM Virtual Private Cloud Default value: "bx2-4x16" |
| APP_IMAGE | The OS image used for SAP Application VSI (See Obs*). A list of images is available here. Default value: ibm-redhat-8-6-amd64-sap-applications-6 |
SAP input parameters
| Parameter | Description | Requirements |
|---|---|---|
| S4HANA_VERSION | The version of S/4HANA | The version can take one of the following values: 2020, 2021, 2022, 2023. |
| HANA_SID | The SAP system ID identifies the SAP HANA system. Default value: HDB (See Obs.*) |
|
| HANA_TENANT | SAP HANA tenant name. Default value: HDB | |
| HANA_SYSNO | Specifies the instance number of the SAP HANA system |
|
| HANA_SYSTEM_USAGE | System Usage | Default: custom Valid values: production, test, development, custom |
| HANA_COMPONENTS | SAP HANA Components | Default: server Valid values: all, client, es, ets, lcapps, server, smartda, streaming, rdsync, xs, studio, afl, sca, sop, eml, rme, rtl, trp |
| KIT_SAPHANA_FILE | Path to SAP HANA ZIP file (See Obs*). | As downloaded from SAP Support Portal |
| SAP_SID | The SAP system ID identifies the entire SAP system |
|
| SAP_ASCS_INSTANCE_NUMBER | Technical identifier for internal processes of ASCS |
|
| SAP_CI_INSTANCE_NUMBER | Technical identifier for internal processes of CI |
|
| HDB_CONCURRENT_JOBS | Number of concurrent jobs used to load and/or extract archives to HANA Host | Default: 23 |
| KIT_SAPCAR_FILE | Path to sapcar binary | As downloaded from SAP Support Portal |
| KIT_SWPM_FILE | Path to SWPM archive (SAR) | As downloaded from SAP Support Portal |
| KIT_SAPEXE_FILE | Path to SAP Kernel OS archive (SAR) | As downloaded from SAP Support Portal |
| KIT_SAPEXEDB_FILE | Path to SAP Kernel DB archive (SAR) | As downloaded from SAP Support Portal |
| KIT_IGSEXE_FILE | Path to IGS archive (SAR) | As downloaded from SAP Support Portal |
| KIT_IGSHELPER_FILE | Path to IGS Helper archive (SAR) | As downloaded from SAP Support Portal |
| KIT_SAPHOSTAGENT_FILE | Path to SAP Host Agent archive (SAR) | As downloaded from SAP Support Portal |
| KIT_HDBCLIENT_FILE | Path to HANA DB client archive (SAR) | As downloaded from SAP Support Portal |
| KIT_S4HANA_EXPORT | Path to S/4HANA Installation Export dir | The archives downloaded from SAP Support Portal should be present in this path |
| Parameter | Description | Requirements |
|---|---|---|
| SAP_MAIN_PASSWORD | Common password for all users that are created during the installation |
|
| HANA_MAIN_PASSWORD | HANA system master password |
|
Obs:
- Sensitive - The variable value is not displayed in your Schematics logs and it is hidden in the input field.
- The following parameters should have the same values as the ones set for the BASTION server: REGION, ZONE, VPC, SUBNET, SECURITYGROUP.
- For any manual change in the terraform code, you have to make sure that you use a certified image based on the SAP NOTE: 2927211.
Installation media validated for this solution:
| Component | Version | Filename |
|---|---|---|
| SAPCAR | 7.22 | SAPCAR_1010-70006178.EXE |
| SOFTWARE PROVISIONING MGR | 2.0 SP17 PL 0 | SWPM20SP17_0-80003424.SAR |
| SAP KERNEL | 7.93 64-BIT UNICODE | SAPEXE_60-70007807.SAR SAPEXEDB_60-70007806.SAR |
| SAP IGS | 7.81 PL 4 | igsexe_4-70005417.sar |
| SAP IGS HELPER | PL 17 | igshelper_17-10010245.sar |
| SAP HOST AGENT | 7.22 SP61 | SAPHOSTAGENT61_61-80004822.SAR |
| HANA CLIENT | 2.18 | IMDB_CLIENT20_018_27-80002082.SAR |
| HANA DB | 2.0 SPS07 rev73 | 51057281.ZIP |
OS images validated for this solution:
| OS version | Image | Role |
|---|---|---|
| Red Hat Enterprise Linux 8.6 for SAP HANA (amd64) | ibm-redhat-8-6-amd64-sap-hana-6 | DB |
| Red Hat Enterprise Linux 8.6 for SAP Applications (amd64) | ibm-redhat-8-6-amd64-sap-applications-6 | APP |
| SUSE Linux Enterprise Server 15 SP4 for SAP HANA | ibm-sles-15-4-amd64-sap-hana-7 | DB |
| SUSE Linux Enterprise Server 15 SP4 for SAP Applications | ibm-sles-15-4-amd64-sap-applications-8 | APP |
| Red Hat Enterprise Linux 8.4 for SAP HANA (amd64) | ibm-redhat-8-4-amd64-sap-hana-10 | DB |
| Red Hat Enterprise Linux 8.4 for SAP Applications (amd64) | ibm-redhat-8-4-amd64-sap-applications-10 | APP |
| SUSE Linux Enterprise Server 15 SP3 for SAP HANA | ibm-sles-15-3-amd64-sap-hana-10 | DB |
| SUSE Linux Enterprise Server 15 SP3 for SAP Applications | ibm-sles-15-3-amd64-sap-applications-11 | APP |
| Component | Version | Filename |
|---|---|---|
| SAPCAR | 7.22 | SAPCAR_1010-70006178.EXE |
| SOFTWARE PROVISIONING MGR | 2.0 SP15 PL 5 | SWPM20SP15_5-80003424.SAR |
| SAP KERNEL | 7.89 64-BIT UNICODE PL 200 | SAPEXE_200-70006642.SAR SAPEXEDB_200-70006641.SAR |
| SAP IGS | 7.81 PL 4 | igsexe_4-70005417.sar |
| SAP IGS HELPER | PL 17 | igshelper_17-10010245.sar |
| SAP HOST AGENT | 7.22 SP61 | SAPHOSTAGENT61_61-80004822.SAR |
| HANA CLIENT | 2.18 | IMDB_CLIENT20_018_27-80002082.SAR |
| HANA DB | 2.0 SPS07 rev73 | 51057281.ZIP |
OS images validated for this solution:
| OS version | Image | Role |
|---|---|---|
| Red Hat Enterprise Linux 8.6 for SAP HANA (amd64) | ibm-redhat-8-6-amd64-sap-hana-6 | DB |
| Red Hat Enterprise Linux 8.6 for SAP Applications (amd64) | ibm-redhat-8-6-amd64-sap-applications-6 | APP |
| SUSE Linux Enterprise Server 15 SP4 for SAP HANA | ibm-sles-15-4-amd64-sap-hana-7 | DB |
| SUSE Linux Enterprise Server 15 SP4 for SAP Applications | ibm-sles-15-4-amd64-sap-applications-8 | APP |
| Red Hat Enterprise Linux 8.4 for SAP HANA (amd64) | ibm-redhat-8-4-amd64-sap-hana-10 | DB |
| Red Hat Enterprise Linux 8.4 for SAP Applications (amd64) | ibm-redhat-8-4-amd64-sap-applications-10 | APP |
| SUSE Linux Enterprise Server 15 SP3 for SAP HANA | ibm-sles-15-3-amd64-sap-hana-10 | DB |
| SUSE Linux Enterprise Server 15 SP3 for SAP Applications | ibm-sles-15-3-amd64-sap-applications-11 | APP |
| Component | Version | Filename |
|---|---|---|
| SAPCAR | 7.22 | SAPCAR_1010-70006178.EXE |
| SOFTWARE PROVISIONING MGR | 2.0 SP15 PL 5 | SWPM20SP15_5-80003424.SAR |
| SAP KERNEL | 7.89 64-BIT UNICODE PL 200 | SAPEXE_200-70006642.SAR SAPEXEDB_200-70006641.SAR |
| SAP IGS | 7.81 PL 4 | igsexe_4-70005417.sar |
| SAP IGS HELPER | PL 17 | igshelper_17-10010245.sar |
| SAP HOST AGENT | 7.22 SP61 | SAPHOSTAGENT61_61-80004822.SAR |
| HANA CLIENT | 2.18 | IMDB_CLIENT20_018_27-80002082.SAR |
| HANA DB | 2.0 SPS07 rev73 | 51057281.ZIP |
OS images validated for this solution:
| OS version | Image | Role |
|---|---|---|
| Red Hat Enterprise Linux 8.6 for SAP HANA (amd64) | ibm-redhat-8-6-amd64-sap-hana-6 | DB |
| Red Hat Enterprise Linux 8.6 for SAP Applications (amd64) | ibm-redhat-8-6-amd64-sap-applications-6 | APP |
| SUSE Linux Enterprise Server 15 SP4 for SAP HANA | ibm-sles-15-4-amd64-sap-hana-7 | DB |
| SUSE Linux Enterprise Server 15 SP4 for SAP Applications | ibm-sles-15-4-amd64-sap-applications-8 | APP |
| Red Hat Enterprise Linux 8.4 for SAP HANA (amd64) | ibm-redhat-8-4-amd64-sap-hana-10 | DB |
| Red Hat Enterprise Linux 8.4 for SAP Applications (amd64) | ibm-redhat-8-4-amd64-sap-applications-10 | APP |
| SUSE Linux Enterprise Server 15 SP3 for SAP HANA | ibm-sles-15-3-amd64-sap-hana-10 | DB |
| SUSE Linux Enterprise Server 15 SP3 for SAP Applications | ibm-sles-15-3-amd64-sap-applications-11 | APP |
| Component | Version | Filename |
|---|---|---|
| SAPCAR | 7.22 | SAPCAR_1010-70006178.EXE |
| SOFTWARE PROVISIONING MGR | 2.0 SP15 PL 5 | SWPM20SP15_5-80003424.SAR |
| SAP KERNEL | 7.81 64-BIT UNICODE PL 100 | SAPEXE_100-70005283.SAR SAPEXEDB_100-70005282.SAR |
| SAP KERNEL | 7.85 64-BIT UNICODE PL 300 | SAPEXE_300-80005374.SAR SAPEXEDB_300-80005373.SAR |
| SAP KERNEL | 7.89 64-BIT UNICODE PL 200 | SAPEXE_200-70006642.SAR SAPEXEDB_200-70006641.SAR |
| SAP IGS | 7.81 PL 1 | igsexe_1-70005417.sar |
| SAP IGS | 7.81 PL 3 | igsexe_3-70005417.sar |
| SAP IGS | 7.81 PL 4 | igsexe_4-70005417.sar |
| SAP IGS HELPER | PL 17 | igshelper_17-10010245.sar |
| SAP HOST AGENT | 7.22 SP61 | SAPHOSTAGENT61_61-80004822.SAR |
| HANA CLIENT | 2.17 | IMDB_CLIENT20_017_22-80002082.SAR |
| HANA CLIENT | 2.18 | IMDB_CLIENT20_018_27-80002082.SAR |
| HANA DB | 2.0 SPS05 rev59.05 | 51056441.ZIP |
| HANA DB | 2.0 SPS07 rev73 | 51057281.ZIP |
OS images validated for this solution:
| OS version | Image | Role |
|---|---|---|
| Red Hat Enterprise Linux 8.6 for SAP HANA (amd64) | ibm-redhat-8-6-amd64-sap-hana-6 | DB |
| Red Hat Enterprise Linux 8.6 for SAP Applications (amd64) | ibm-redhat-8-6-amd64-sap-applications-6 | APP |
| SUSE Linux Enterprise Server 15 SP4 for SAP HANA | ibm-sles-15-4-amd64-sap-hana-7 | DB |
| SUSE Linux Enterprise Server 15 SP4 for SAP Applications | ibm-sles-15-4-amd64-sap-applications-8 | APP |
The solution is based on Terraform remote-exec and Ansible playbooks executed by Schematics
The following parameters that can be set in the Schematics workspace are described in General input variables Section section.
Beside General input variables Section, the below ones, in IBM Schematics have specific description and GUI input options:
Server input parameters:
| Parameter | Description |
|---|---|
| PRIVATE_SSH_KEY | id_rsa private SSH key content in OpenSSH format (Sensitive* value). This private SSH key should be used only during the terraform provisioning and it is recommended to be changed after the SAP deployment. |
| ID_RSA_FILE_PATH | The file path for the private ssh key. It will be automatically generated. If it is changed, it must contain the relative path from git repo folders. Example: ansible/id_rsa_s4hana_dst |
SAP and HANA Passwords
The passwords for the SAP and HANA systems will be hidden during the schematics apply step and will not be available after the deployment.
-
Make sure that you have the required IBM Cloud IAM permissions to create and work with VPC infrastructure and you are assigned the correct permissions to create the workspace in Schematics and deploy resources.
-
Generate an SSH key. The SSH key is required to access the provisioned VPC virtual server instances via the bastion host. After you have created your SSH key, make sure to upload this SSH key to your IBM Cloud account in the VPC region and resource group where you want to deploy the SAP solution
-
Create the Schematics workspace:
- From the IBM Cloud menu
select Schematics.
- Push the
Create workspacebutton. - Provide the URL of the Github repository of this solution
- Select the latest Terraform version.
- Click on
Nextbutton - Provide a name, the resources group and location for your workspace
- Push
Nextbutton - Review the provided information and then push
Createbutton to create your workspace
- Push the
- On the workspace Settings page,
- In the Input variables section, review the default values for the input variables and provide alternatives if desired.
- Click Save changes.
- From the IBM Cloud menu
select Schematics.
-
From the workspace Settings page, click Generate plan
-
From the workspace Jobs page, the logs of your Terraform execution plan can be reviewed.
-
Apply your Terraform template by clicking Apply plan.
-
Review the logs to ensure that no errors occurred during the provisioning, modification, or deletion process.
In the output of the Schematics
Apply Planthe private IP address of the Servers, the hostname of the servers, the VPC and the Activity Tracker instance name will be displayed.
For the script configuration add your IBM Cloud API Key in terraform planning phase command 'terraform plan --out plan1'.
The solution is configured by editing the variable values in the file input.auto.tfvars. See the example below:
Server input parameters
##########################################################
# General VPC variables:
######################################################
REGION = "eu-de"
# Region for the server. Supported regions: https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zones#zones-vpc
# Example: REGION = "eu-de"
ZONE = "eu-de-1"
# Availability zone for the server. Supported zones: https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zones#zones-vpc
# Example: ZONE = "eu-de-1"
VPC = "ic4sap"
# EXISTING VPC, previously created by the user in the same region as the server. The list of available VPCs: https://cloud.ibm.com/vpc-ext/network/vpcs
# Example: VPC = "ic4sap"
SECURITY_GROUP = "ic4sap-securitygroup"
# EXISTING Security group, previously created by the user in the same VPC. The list of available Security Groups: https://cloud.ibm.com/vpc-ext/network/securityGroups
# Example: SECURITY_GROUP = "ic4sap-securitygroup"
RESOURCE_GROUP = "wes-automation"
# EXISTING Resource group, previously created by the user. The list of available Resource Groups: https://cloud.ibm.com/account/resource-groups
# Example: RESOURCE_GROUP = "wes-automation"
SUBNET = "ic4sap-subnet"
# EXISTING Subnet in the same region and zone as the server, previously created by the user. The list of available Subnets: https://cloud.ibm.com/vpc-ext/network/subnets
# Example: SUBNET = "ic4sap-subnet"
SSH_KEYS = ["r010-8f72b994-c17f-4500-af8f-d05680374t3c", "r011-8f72v884-c17f-4500-af8f-d05900374t3c"]
# List of SSH Keys UUIDs that are allowed to SSH as root to the server. The SSH Keys should be created for the same region as the server. The list of available SSH Keys UUIDs: https://cloud.ibm.com/vpc-ext/compute/sshKeys
# Example: SSH_KEYS = ["r010-8f72b994-c17f-4500-af8f-d05680374t3c", "r011-8f72v884-c17f-4500-af8f-d05900374t3c"]
ID_RSA_FILE_PATH = "ansible/id_rsa"
# The id_rsa private key file path in OpenSSH format with 0600 permissions.
# This private key is used only during the terraform provisioning and it is recommended to be changed after the SAP deployment.
# It must contain the relative or absoute path from your Bastion.
# Examples: "ansible/id_rsa_s4hana_dst" , "~/.ssh/id_rsa_s4hana_dst" , "/root/.ssh/id_rsa".
##########################################################
# SAP HANA Server variables
##########################################################
HANA_SERVER_TYPE = "virtual"
# The type of SAP HANA Server. Allowed vales: "virtual" or "bare metal"
# Example: HANA_SERVER_TYPE = "bare metal"
##########################################################
# DB server variables:
##########################################################
DB_HOSTNAME = "ic4sapdb"
# The Hostname for the DB server. The hostname should be up to 13 characters, as required by SAP
# Example: DB_HOSTNAME = "ic4sapdb"
DB_PROFILE = "mx2-16x128"
# The profile used for SAP HANA Server.
# The list of certified profiles for SAP HANA Virtual Servers is available here: https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-vs-vpc
# The list of certified profiles for SAP HANA Bare Metal Servers is available here: https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-intel-bm-vpc.
# Details about all x86 instance profiles are available here: https://cloud.ibm.com/docs/vpc?topic=vpc-profiles.
# Example of Virtual Server Instance profile for SAP HANA: DB_PROFILE ="mx2-16x128".
# Example of Bare Metal profile for SAP HANA: DB_PROFILE = "bx2d-metal-96x384".
# For more information about supported DB/OS and IBM VPC, check SAP Note 2927211: "SAP Applications on IBM Virtual Private Cloud".
DB_IMAGE = "ibm-redhat-8-6-amd64-sap-hana-6"
# OS image for DB server. Validated OS images for DB serverss: ibm-redhat-8-6-amd64-sap-hana-6, ibm-redhat-8-4-amd64-sap-hana-10, ibm-sles-15-4-amd64-sap-hana-7, ibm-sles-15-3-amd64-sap-hana-10.
# The list of available VPC Operating Systems supported by SAP: SAP note '2927211 - SAP Applications on IBM Virtual Private Cloud (VPC) Infrastructure environment' https://launchpad.support.sap.com/#/notes/2927211; The list of all available OS images: https://cloud.ibm.com/docs/vpc?topic=vpc-about-images
# Example: DB_IMAGE = "ibm-sles-15-4-amd64-sap-hana-7"
##########################################################
# SAP APP VSI variables:
##########################################################
APP_HOSTNAME = "ic4sapapp"
# The Hostname for the SAP APP VSI. The hostname should be up to 13 characters, as required by SAP
# Example: APP_HOSTNAME = "ic4sapapp"
APP_PROFILE = "bx2-4x16"
# The APP VSI profile. Supported profiles: bx2-4x16. The list of available profiles: https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=ui
APP_IMAGE = "ibm-redhat-8-6-amd64-sap-applications-6"
# OS image for SAP APP VSI. Validated OS images for APP VSIs: ibm-redhat-8-6-amd64-sap-applications-6, ibm-redhat-8-4-amd64-sap-applications-10, ibm-sles-15-4-amd64-sap-applications-8, ibm-sles-15-3-amd64-sap-applications-11.
# The list of available VPC Operating Systems supported by SAP: SAP note '2927211 - SAP Applications on IBM Virtual Private Cloud (VPC) Infrastructure environment' https://launchpad.support.sap.com/#/notes/2927211; The list of all available OS images: https://cloud.ibm.com/docs/vpc?topic=vpc-about-images
# Example: APP-IMAGE = "ibm-sles-15-4-amd64-sap-applications-8"Edit your SAP system configuration variables that will be passed to the ansible automated deployment:
##########################################################
# S/4HANA version
##########################################################
S4HANA_VERSION = "2023"
# The version of S/4HANA. The version can take one of the following values: 2020, 2021, 2022, 2023.
# Example: S4HANA_VERSION = "2022"
##########################################################
# SAP HANA configuration
##########################################################
HANA_SID = "HDB"
# SAP HANA system ID. Should follow the SAP rules for SID naming.
# Example: HANA_SID = "HDB"
HANA_SYSNO = "00"
# SAP HANA instance number. Should follow the SAP rules for instance number naming.
# Example: HANA_SYSNO = "01"
HANA_TENANT = "HDB"
# SAP HANA tenant name
# Example:HANA_TENANT = "HDB_TEN1"
HANA_SYSTEM_USAGE = "custom"
# System usage. Default: custom. Suported values: production, test, development, custom
# Example: HANA_SYSTEM_USAGE = "custom"
HANA_COMPONENTS = "server"
# SAP HANA Components. Default: server. Supported values: all, client, es, ets, lcapps, server, smartda, streaming, rdsync, xs, studio, afl, sca, sop, eml, rme, rtl, trp
# Example: HANA_COMPONENTS = "server"
KIT_SAPHANA_FILE = "/storage/HANADB/SP07/Rev73/51057281.ZIP"
# SAP HANA Installation kit path
# Example for Red Hat 8 or Suse 15: KIT_SAPHANA_FILE = "/storage/HANADB/SP07/Rev73/51057281.ZIP"
##########################################################
# SAP system configuration
##########################################################
SAP_SID = "S4A"
# SAP System ID
SAP_ASCS_INSTANCE_NUMBER = "01"
# The central ABAP service instance number. Should follow the SAP rules for instance number naming.
# Example: SAP_ASCS_INSTANCE_NUMBER = "01"
SAP_CI_INSTANCE_NUMBER = "06"
# The SAP central instance number. Should follow the SAP rules for instance number naming.
# Example: SAP_CI_INSTANCE_NUMBER = "06"
HDB_CONCURRENT_JOBS = "23"
# Number of concurrent jobs used to load and/or extract archives to HANA Host
##########################################################
# SAP S/4HANA APP Kit Paths
##########################################################
KIT_SAPCAR_FILE = "/storage/S4HANA/SAPCAR_1010-70006178.EXE"
KIT_SWPM_FILE = "/storage/S4HANA/SWPM20SP17_0-80003424.SAR"
KIT_SAPEXE_FILE = "/storage/S4HANA/KERNEL/793/SAPEXE_60-70007807.SAR"
KIT_SAPEXEDB_FILE = "/storage/S4HANA/KERNEL/793/SAPEXEDB_60-70007806.SAR"
KIT_IGSEXE_FILE = "/storage/S4HANA/KERNEL/793/igsexe_4-70005417.sar"
KIT_IGSHELPER_FILE = "/storage/S4HANA/igshelper_17-10010245.sar"
KIT_SAPHOSTAGENT_FILE = "/storage/S4HANA/SAPHOSTAGENT61_61-80004822.SAR"
KIT_HDBCLIENT_FILE = "/storage/S4HANA/IMDB_CLIENT20_018_27-80002082.SAR"
KIT_S4HANA_EXPORT = "/storage/S4HANA/2023"For initializing terraform:
terraform initFor planning phase:
terraform plan --out plan1
# you will be asked for the following sensitive variables:
'IBMCLOUD_API_KEY', 'SAP_MAIN_PASSWORD' and 'HANA_MAIN_PASSWORD'.For apply phase:
terraform apply "plan1"For destroy:
terraform destroy
# you will be asked for the following sensitive variables as a destroy confirmation phase:
'IBMCLOUD_API_KEY', 'SAP_MAIN_PASSWORD' and 'HANA_MAIN_PASSWORD'.