Automating SAP NetWeaver 7.x on HANA db 3-tier architecture on IBM Cloud® VPC (Terraform and Ansible)

Terraform deployment script files

The configuration and script files are available in the GitHub repository:

• For Java stack : https://github.com/IBM-Cloud/sap-netweaver-java-hana
• For ABAP stack : https://github.com/IBM-Cloud/sap-netweaver-abap-hana

The input.auto.tfvars file allows the customization of the resources and variable values should be provided.

Other configuration files are provided and no modification is required.

Schematics script files

The configuration and script files are available in the GitHub repository:

• ABAP: https://github.com/IBM-Cloud/sap-netweaver-abap-hana/tree/main
• Java: https://github.com/IBM-Cloud/sap-netweaver-java-hana/tree/main

When the Schematics interface is used, the following information should be provided:

• the workspace information.
• the GitHub path for the chosen solution either on ABAP or Java stack.
• the values for the parameters in the Schematics interface. They are the same parameters as the input.auto.tfvars file that you use with the cli.

SAP Kits

For each IBM Cloud region, a dedicated deployment server (bastion server) is used for the Terraform environment. It is your responsibility to download the necessary SAP and DB kits to your Deployment (Bastion) Server. All file archives are decompressed by Ansible during the automatic deploying process. For more information, see the Readme file in the dedicated GitHub repository.

Before you begin

Before you use the scripts:

• If you have not created already, create a deployment server (bastion server) to store the SAP kits. For more information, see Automate SAP bastion server - SAP media storage repository.
• Log in to your previously created deployment server and verify that Terraform and Ansible are installed.
• Download the SAP kits from the SAP Portal to your Deployment Server. Make note of the download locations. Ansible decompresses all of the files. For more information, see the Java README file or the ABAP README file.
• Create or retrieve an IBM Cloud API key. The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
• Create or retrieve your SSH key ID. You need the 40-digit UUID for the SSH key, not the SSH key name.

Before you begin

Before you deploy SAP NetWeaver ABAP or Java stack on HANA db:

• Set up your account to access the VPC. Make sure that your account is upgraded to a paid account.
• If you have not already, create a deployment server (bastion server) to store the SAP kits. For more information, see Automate SAP bastion server - SAP media storage repository. You need the Floating IP from your deployment server (bastion server) for deployment.
• Download the SAP kits from the SAP Portal to your deployment server (bastion server). Make note of the download locations. Ansible decompresses all of the archive kits and needs the paths. For more information, see the Readme file for:
  • ABAP: Schematics, Terraform, or the Catalog Tile
  • JAVA: Schematics and Terraform
• Create or retrieve an IBM Cloud API key. The API key is used to authenticate with the IBM Cloud platform and to determine your permissions for IBM Cloud services.
• Create or retrieve your SSH key ID. You need the 40-digit UUID for the SSH key, not the SSH key name.
• Optional - (Catalog Tile) create secrets for your credentials and passwords by using the Secrets Manager.

Deploying SAP NetWeaver 7.x and SAP HANA by using the Schematics user interface

Use these steps to configure the NetWeaver ABAP or Java stack on your existing VPC by using the Schematics interface. The scripts can take 2 - 3 hours to complete.

1. From the IBM Cloud menu, select Schematics.

2. Click Create workspace.

3. On the Specify template page:

   • Enter the URL for the Schematics interface.
   • Select the Terraform version that is listed in the Readme file.
   • Click Next.

4. On the Workspace details page:

   • Enter a name for the workspace.
   • Select a Resource group.
   • Select a Location for your workspace. The workspace location does not have to match the resource location.
   • Select Next.

5. Select Create to create your workspace.

6. On the workspace settings page, in the Input variables section, review the default input variables and provide values that match your solution.

   For a more detailed description of each of the parameters, check the GitHub repo Java Readme or ABAP Readme file, chapter “Input parameter file”. Also, make sure to mark the parameters that contain sensitive information like passwords, API, and ssh private keys as "sensitive". These parameters are marked as “sensitive” in the Readme file, under “Input parameter file”.

7. On the workspace settings page, click Generate plan. Wait for the plan to complete.

8. Click View log to review the log files of your Terraform execution plan.

9. Apply your Terraform template by clicking Apply plan.

10. Review the log file to ensure that no errors occur during the provisioning, modification, or deletion process.

Deploying SAP NetWeaver (ABAP) Linux/HANA on VPC via Deployable Architecture tile

Use these steps to configure the SAP NetWeaver (ABAP) Linux/HANA on your existing VPC by using the catalog tile interface. The scripts can take 2 - 3 hours to complete.

1. From the IBM Cloud Catalog menu, select the VPC for SAP HANA NetWeaver ABAP on Deployable Architecture tile. For more information about this deployment, see the Readme file.

2. Select the latest version.

3. Select Standard variation.

4. Click Review deployment options:

   • Add to project to add this deployment to an IBM Cloud project and combine it with other deployments. The IBM Cloud projects include several other pipeline steps, including deployment validation, cost calculation, compliance verification, and approval process.
   • Create from the CLI to get the CLI command. With this command you can trigger the deployment from the CLI.
   • Work with code to embed the code into other terraform deployment.
   • Deploy with IBM Cloud Schematics to trigger deployment process directly.

5. Select Deploy with IBM Cloud Schematics option. Now, add the input parameters for this installation. There are 3 categories of parameters:

   • Workspace - These parameters define the workspace that is automatically created in the Schematics:

     • Enter a name for the workspace or use default name.
     • The Resource Group used to create resources. Use default or create a Resource Group.
     • Select a location to create your Schematics workspace. The workspace location need not match the resource location.

   • Required input variables - Review the default input variables and provide values that match your solution. These parameters are specific to your deployment. For more detailed information, see the Readme file.

     Parameter	Description
     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 the rules regarding hostnames for SAP systems, check SAP Note 611361: "Hostnames of SAP ABAP Platform servers".
     DB_HOSTNAME	The Hostname for HANA VSI. The hostname should be up to 13 characters as required by SAP. For more information on the rules regarding hostnames for SAP systems, check SAP Note 611361: "Hostnames of SAP ABAP Platform servers".
     BASTION_FLOATING_IP	Input the FLOATING IP from the Bastion Server.
     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.
     RESOURCE_GROUP	The name of an EXISTING Resource Group for VSIs and Volumes resources. The list of Resource Groups is available here.
     SECURITY_GROUP	The name of an EXISTING Security group. The list of Security Groups is available here.
     SSH_KEYS	List of SSH Keys UUIDs that are allowed to SSH as root to the VSI. Can contain one or more IDs. The list of SSH Keys is available here.
     SUBNET	The name of an EXISTING Subnet. The list of Subnets is available here.
     VPC	The name of an EXISTING VPC. The list of VPCs is available here.
     ZONE	The cloud zone where to deploy the solution.
     HANA_MAIN_PASSWORD	Common password for all users that are created during the installation. A list of images is available here.
     IBMCLOUD_API_KEY	IBM Cloud API key (Sensitive* value).
     PRIVATE_SSH_KEY	Input your id_rsa private key pair content in OpenSSH format (Sensitive* value). This private key should be used only during the terraform provisioning and it is recommended to be changed after the SAP deployment.
     SAP_MAIN_PASSWORD	Common password for all users that are created during the installation. See Obs* section.

   • Optional input variables - Review and update the optional parameters. For more detailed information, see the Readme file.

     Parameter	Description
     APP_IMAGE	The OS image used for SAP Application VSI. See Obs* section. A list of images is available here.
     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".
     DB_IMAGE	The OS image used for HANA VSI. See Obs* section. A list of images is available here.
     DB_PROFILE	The instance profile used for the HANA VSI. The 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".
     ID_RSA_FILE_PATH	The file path for private_ssh_key is automatically generated by default. If it is changed, it must contain the relative path from git repo folders.
     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".
     HANA_SID	The SAP system ID identifies the SAP HANA system.
     HANA_SYSNO	Specifies the instance number of the SAP HANA system.
     HANA_SYSTEM_USAGE	System Usage. Default: "custom". Valid values: "production", "test", "development", "custom".
     HDB_CONCURENT_JOBS	Number of concurrent jobs used to load and/or extract archives to HANA Host.
     KIT_HDB_CLIENT_FILE	Path to the HANA DB client archive (SAR), as downloaded from SAP Support Portal.
     KIT_IGSEXE_FILE	Path to the IGS archive (SAR), as downloaded from SAP Support Portal.
     KIT_IGSHELPER_FILE	Path to the IGS Helper archive (SAR), as downloaded from SAP Support Portal.
     KIT_NWHANA_EXPORT_FILE	Path to the NetWeaver Installation Export ZIP File. The archives downloaded from SAP Support Portal should be present in this path.
     KIT_SAPCAR_FILE	Path to the sapcar binary, as downloaded from SAP Support Portal.
     KIT_SAPEXE_FILE	Path to the SAP Kernel OS archive (SAR), as downloaded from SAP Support Portal.
     KIT_SAPEXEDB_FILE	Path to the SAP Kernel DB archive (SAR), as downloaded from SAP Support Portal.
     KIT_SAPHANA_FILE	Path to the SAP HANA ZIP file. See Obs* section. As downloaded from SAP Support Portal.
     KIT_SAPHOSTAGENT_FILE	Path to the SAP Host Agent archive (SAR), as downloaded from SAP Support Portal.
     KIT_SWPM_FILE	Path to SWPM archive (SAR), as downloaded from SAP Support Portal.
     SAP_ASCS_INSTANCE_NUMBER	Technical identifier for the internal processes of ASCS.
     SAP_CI_INSTANCE_NUMBER	Technical identifier for the internal processes of CI.
     SAP_SID	The SAP system ID identifies the entire SAP system.
     HANA_TENANT	SAP HANA tenant name.

6. Accept the license agreement.

7. Select Deploy. The deployment starts and you are directed to the Schematics page that displays the script log files for you to monitor the deployment progress.

Deploying SAP NetWeaver 7.x and SAP HANA by using Terraform

Use these steps to create the VPC resources and install the SAP architecture. The scripts can take 2 hours to complete.

1. Log in to the deployment server (bastion server) using ssh.

2. Clone the GitHub repository.

   For Java: Clone the repository https://github.com/IBM-Cloud/sap-netweaver-java-hana and change the path to the sap-netweaver-java-hana/cli folder.

   $ git clone https://github.com/IBM-Cloud/sap-netweaver-java-hana.git
   $ cd sap-netweaver-java-hana/cli
   

   For ABAP: Clone the repository https://github.com/IBM-Cloud/sap-netweaver-abap-hana and change to the sap-netweaver-abap-hana folder.

   $ git clone https://github.com/IBM-Cloud/sap-netweaver-abap-hana.git
   $ cd sap-netweaver-abap-hana
   

3. Define your existing VPC variables. Modify the input.auto.tfvars file to specify your zone, VPC component names, profile, and image. The file is preset with the minimal recommended disk sizes. You need your 40-digit SSH key ID for this file. The second SSH key is optional. For more options for profile, see Instance Profiles. For more options for image, see Images. For descriptions of the variables, see the Java README file or the ABAP README file.

   For Java, the following variable values should be modified:

   • REGION - Region for the VSI. See the Readme file.
   • ZONE - Zone for the VSI. See the Readme file.
   • VPC - The name of an existing VPC in the specified region.
   • SECURITY_GROUP - The name of an existing Security group in the same VPC
   • RESOURCE_GROUP - The name of an existing Resource group, previously created by the user.
   • SUBNET - The name of an existing Subnet in the same region and zone as the VSI
   • SSH_KEYS - A list of SSH keys UUIDs allowed to connect via SSH to the VSIs
   • DB_HOSTNAME - The hostname of the database VSI, up to 13 characters. For more information, see the Readme file.
   • APP_HOSTNAME - The hostname of the application server VSI, up to 13 characters. For more information, see the Readme file.

   # General VPC variables for Java stack
   REGION        = "ed-de"
   ZONE          = "eu-de-2"
   VPC           = "ic4sap"
   SECURITYGROUP = "ic4sap-securitygroup"
   SUBNET        = "ic4sap-subnet"
   SSH_KEYS      = [ "ssh key1" , "ssh key2" ]
   
   # SAP Database VSI variables:
   DB_HOSTNAME   = "sapjavadb"
   DB_PROFILE    = "mx2-16x128" 
   DB_IMAGE      = "ibm-redhat-8-6-amd64-sap-hana-2" # 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.
   
   # SAP APPs VSI variables:
   APP_HOSTNAME    = "sapjavci"
   APP_PROFILE     = "bx2-4x16"
   APP_IMAGE = "ibm-redhat-8-6-amd64-sap-applications-2" # 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.
   
   

   For ABAP, the following variable values should be modified:

   • REGION - Region for the VSI. See the Readme file.
   • ZONE - Zone for the VSI. See the Readme file.
   • VPC - The name of an existing VPC in the specified region.
   • SECURITY_GROUP - The name of an existing Security group in the same VPC
   • RESOURCE_GROUP - The name of an existing Resource group, previously created by the user
   • SUBNET - The name of an existing Subnet in the same region and zone as the VSI
   • SSH_KEYS - A list of SSH keys UUIDs allowed to connect via SSH to the VSIs
   • DB_HOSTNAME - The hostname of the database VSI, up to 13 characters. For more information, see the Readme file.
   • APP_HOSTNAME - The hostname of the application server VSI, up to 13 characters. For more information, see the Readme file.

   # General VPC variables for ABAP stack
   REGION          = "eu-de"
   ZONE            = "eu-de-2"
   VPC             = "ic4sap"                    # EXISTING Security group name
   SECURITY_GROUP  = "ic4sap-securitygroup"      # EXISTING Security group name
   RESOURCE_GROUP  = "wes-automation"
   SUBNET          = "ic4sap-subnet"             # EXISTING Subnet name
   SSH_KEYS        = [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
   
   # SAP Database VSI variables:
   DB_HOSTNAME     = "sapnwhdb"
   DB_PROFILE      = "mx2-16x128"
   DB_IMAGE        = "ibm-redhat-8-6-amd64-sap-hana-6"
   
   # SAP APPs VSI variables:
   APP_HOSTNAME	= "sapnwci"
   APP_PROFILE	= "bx2-4x16"
   APP_IMAGE 	= "ibm-redhat-8-6-amd64-sap-applications-6"
   

   The hostname must have up to 13 characters as required by SAP. For more information about the rules that apply to hostnames for SAP systems, see SAP Note 611361 - Hostnames of SAP ABAP Platform servers

4. Customize your SAP system configuration. Modify the input.auto.tfvars file to specify SAP system configuration and enter the location of the downloaded SAP Kits. For descriptions of the variables, see the Java README file or the ABAP README file.

   For Java:

   # SAP HANA DB configuration for Java stack
   HANA_SID                = "HDB"
   HANA_SYSNO              = "00"
   HANA_SYSTEM_USAGE       = "custom"
   HANA_COMPONENTS         = "server"
   
   # SAP HANA Installation kit path
   KIT_SAPHANA_FILE        = "/storage/HANADB/51055299.ZIP"
   
   # SAP system configuration
   SAP_SID                 = "JV1"
   SAP_SCS_INSTANCE_NUMBER = "01"
   SAP_CI_INSTANCE_NUMBER  = "00"
   
   # SAP JAVA APP Installation kit path
   KIT_SAPCAR_FILE = "/storage/NW75HDB/SAPCAR_1010-70006178.EXE"
   KIT_SWPM_FILE = "/storage/NW75HDB/SWPM10SP31_7-20009701.SAR"
   KIT_SAPEXE_FILE = "/storage/NW75HDB/SAPEXE_801-80002573.SAR"
   KIT_SAPEXEDB_FILE = "/storage/NW75HDB/SAPEXEDB_801-80002572.SAR"
   KIT_IGSEXE_FILE = "/storage/NW75HDB/igsexe_13-80003187.sar"
   KIT_IGSHELPER_FILE = "/storage/NW75HDB/igshelper_17-10010245.sar"
   KIT_SAPHOSTAGENT_FILE = "/storage/NW75HDB/SAPHOSTAGENT51_51-20009394.SAR"
   KIT_HDBCLIENT_FILE = "/storage/NW75HDB/IMDB_CLIENT20_009_28-80002082.SAR"
   KIT_SAPJVM_FILE = "/storage/NW75HDB/SAPJVM8_73-80000202.SAR"
   KIT_JAVA_EXPORT = "/storage/NW75HDB/export"
   

   For ABAP:

   # HANA DB configuration for ABAP stack
   HANA_SID                = "HDB"
   HANA_SYSNO              = "00"
   HANA_TENANT		= "NWD"
   HANA_SYSTEM_USAGE       = "custom"
   HANA_COMPONENTS 	= "server"
   
   # SAP HANA Installation kit path
   KIT_SAPHANA_FILE 	= "/storage/HANADB/SP07/Rev73/51057281.ZIP"
   
   # SAP system configuration
   SAP_SID = "NWD"
   SAP_ASCS_INSTANCE_NUMBER = "01"
   SAP_CI_INSTANCE_NUMBER 	 = "00"
   
   # Number of concurrent jobs used to load and/or extract archives to HANA Host
   HDB_CONCURRENT_JOBS 	 = "12"
   
   # SAP NW APP Installation kit path
   KIT_SAPCAR_FILE 	 = "/storage/NW75HDB/SAPCAR_1300-70007716.EXE"
   KIT_SWPM_FILE 		 = "/storage/NW75HDB/SWPM10SP42_0-20009701.SAR"
   KIT_SAPEXE_FILE 	 = "/storage/NW75HDB/KERNEL/754/SAPEXE_400-80007612.SAR"
   KIT_SAPEXEDB_FILE 	 = "/storage/NW75HDB/KERNEL/754/SAPEXEDB_400-80007611.SAR"
   KIT_IGSEXE_FILE 	 = "/storage/NW75HDB/KERNEL/754/igsexe_4-80007786.sar"
   KIT_IGSHELPER_FILE 	 = "/storage/NW75HDB/igshelper_17-10010245.sar"
   KIT_SAPHOSTAGENT_FILE 	 = "/storage/NW75HDB/SAPHOSTAGENT65_65-80004822.SAR"
   KIT_HDBCLIENT_FILE 	 = "/storage/NW75HDB/IMDB_CLIENT20_022_27-80002082.SAR"
   KIT_NWHANA_EXPORT_FILE   = "/storage/NW75HDB/ABAPEXP/51050829_3.ZIP"
   

5. Initialize the Terraform CLI.

   terraform init
   

6. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the virtual private cloud instance in your account. During the Terraform plan, you are prompted to enter your API key, and initial SAP and DB passwords.

   terraform plan --out plan1
   

   You will be asked for SAP main password, HANA main password, and the API key.

   The SAP main password must be 10 - 14 characters long and contain at least one digit (0-9). It can contain only the following characters: a-z, A-Z, 0-9, @, #, $, _. This password cannot contain !. It must not start with a digit or an underscore ( _ ).

7. Verify that the plan shows all the resources that you want to create and that the names and values are correct. If the plan needs to be adjusted, edit the input.auto.tfvars file to correct resources and run ``terraform plan --out plan1` again.

8. Create the virtual private cloud for SAP instance and IAM access policy in IBM Cloud.

    terraform apply "plan1"
   

   The virtual private cloud and components are created and you see output similar to the terraform plan output.