Deploying SAP NetWeaver 7.x and Db2 on an existing IBM Cloud® VPC (Terraform and Ansible)

Terraform deployment

You use Terraform on the Bastion server CLI to download and run the scripts that are located in SAP NetWeaver ABAP Db2 GitHub repository for Terraform.

To run the Terraform scripts, you modify:

• The input.auto.tfvars file to specify the information for your solution:

  • Enter the floating IP and subnet information from the Bastion server.

  • Enter existing VPC information:

    • VPC name
    • Security group
    • Subnet
    • HostName
    • Profile
    • Image
    • Up to two SSH keys

  • You can change the default SAP system configuration settings to match your solution.

  • You also specify the location where you downloaded the SAP kits.

The IBM Cloud Provider plug-in for Terraform on IBM Cloud uses these configuration files to install NW7.X with Db2 on the specified VPC in your IBM Cloud account.

Schematics deployment

When you run the scripts with the Schematics interface, you:

• Enter Workspace information.
• Enter the GitHub path.
• Modify the parameters in the Schematics interface. They are the same parameters as the input.auto.tfvars file that you use with the cli.

Catalog Tile deployment

When you use the Catalog Tile for deployment, you:

• Select the SAP NetWeaver (ABAP stack) with Db2 standard system tile from the catalog
• Enter information for your workspace. The Catalog Tile creates a Schematics workspace for you.
• Modify the parameters for your bastion server, personal credential information, and other parameters specific to your solution.

Support - Catalog Tile

The Catalog Tile offering is IBM Cloud supported. For more information, see Getting help and support from IBM Cloud or SAP.

If client issues are identified with SAP software, then SAP Support will assist client. Please follow the recommendations of SAP Note 90835, which describes the SAP Incident Escalation Procedure. This SAP Note (and others) is found at https://support.sap.com/en/index.html

Deploying SAP NetWeaver 7.x and Db2 by using Terraform with the Bastion server CLI

Use these steps to configure the IBM Cloud Provider plug-in and use Terraform to install SAP NW7.X with Db2 on your existing VPC. The scripts can take 1 - 2 hours to complete.

1. Access the Bastion server cli.

2. Clone the solution repository from https://github.com/IBM-Cloud/sap-netweaver-abap-db2-standard and cd to the sap-netweaver-abap-db2-standard folder:

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

3. Specify your VPC. Modify the input.auto.tfvars file to specify the information for the existing VPC, your zone, VPC and component names, profile, and image. 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 README file.

   #Infra VPC variables
   REGION = "eu-de"
   ZONE = "eu-de-2"
   VPC = "ex-vpc"
   SECURITY_GROUP = "bastion-sg-ex-bastion"
   RESOURCE_GROUP = "exres-group"
   SUBNET = "ex-subnet"
   SSH_KEYS = [ "r018-6c00506b-6be1-4395-b02e-ab8b052e2a6a" , "r018-6c00506b-6be1-4395-b02e-bb8b052e2a6b" ]
   HOSTNAME = "exdb2nwss1"
   PROFILE = "bx2-4x16"
   IMAGE = "ibm-redhat-8-4-amd64-sap-applications-4"
   

4. Customize your SAP system configuration. In the same file, input.auto.tfvars, edit the SAP system configuration variables that are passed to the Ansible automated deployment.

   For descriptions of the variables, see the README file.

   ##SAP system configuration
   sap_sid	= "DB2"
   sap_ci_instance_number = "00"
   sap_ascs_instance_number = "01"
   
   #Kits paths
   kit_sapcar_file = "/storage/NW75DB2/SAPCAR_1010-70006178.EXE"
   kit_swpm_file =  "/storage/NW75DB2/SWPM10SP37_2-20009701.SAR"
   kit_saphotagent_file = "/storage/NW75DB2/SAPHOSTAGENT51_51-20009394.SAR"
   kit_sapexe_file = "/storage/NW75DB2/SAPEXE_800-80002573.SAR"
   kit_sapexedb_file = "/storage/NW75DB2/SAPEXEDB_800-80002603.SAR"
   kit_igsexe_file = "/storage/NW75DB2/igsexe_13-80003187.sar"
   kit_igshelper_file = "/storage/NW75DB2/igshelper_17-10010245.sar"
   kit_export_dir = "/storage/NW75DB2/51050829"
   kit_db2_dir = "/storage/NW75DB2/51055138/DB2_FOR_LUW_11.5_MP6_FP0SAP2_LINUX_"
   kit_db2client_dir = "/storage/NW75DB2/51055140"
   

   Remember, you must manually decompress the kit_export_dir, kit_db2_dir, and kit_db2client_dir files. Ansible decompresses the rest of the SAP kit files. For more information, see the README file.

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.

    terraform plan --out plan1
   

   You must enter an SAP main password and your 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 of 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 again.

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

   ```teraform
    terraform apply "plan1"
    ```
   
   The virtual private cloud and components are created and you see output similar to the `terraform plan` output.
   

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

10. Add the SAP credentials and the virtual server instance IP to the SAP GUI. For more information about the SAP GUI, see SAP GUI.

Deploying SAP NetWeaver 7.x and Db2 by using the Catalog Tile user interface

Use these steps to configure the SAP NetWeaver 7.X with Db2 on your existing VPC by using the Catalog Tile user interface. The scripts can take 1 - 2 hours to complete.

1. From the IBM Cloud Catalog, select the SAP NetWeaver (ABAP stack) with Db2 standard system tile. The Tile opens the Create tab for AP NetWeaver (ABAP stack) with Db2 standard system. For more information about this deployment, see the About tab or the Readme file link.

2. On the SAP NetWeaver (ABAP stack) with Db2 standard system page, configure your workspace:

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

3. Enter the required deployment values, 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
   BASTION_FLOATING_IP	Input the floating IP of the Bastion Server you created before you started this deployment. For more information, see Automate SAP bastion server - SAP media storage
   HOSTNAME	VSI hostname
   REGION	Cloud Region where resources are deployed
   RESOURCE_GROUP	EXISTING Resource Group for VSIs and Volumes
   SECURITY_GROUP	EXISTING Security group name
   SSH_KEYS	SSH Keys ID list to access the VSI
   SUBNET	EXISTING Subnet name
   VPC	EXISTING VPC name
   ZONE	Cloud Zone where resources are deployed
   ibmcloud_api_key	IBM Cloud API key or use a secret that is stored in Secrets Manager
   private_ssh_key	Input id_rsa private key content or use a secret that is stored in Secrets Manager
   sap_main_password	SAP main password or use a secret that is stored in Secrets Manager

4. Review and update the optional parameters. The Ansible scripts expect the SAP kits to be in the default locations listed. For more detailed information, see the Readme file.

   Parameter	Description
   IMAGE	VSI OS image
   PROFILE	VSI profile
   kit_db2_dir	kit_db2_dir
   kit_db2client_dir	kit_db2client_dir
   kit_export_dir	kit_export_dir
   kit_igsexe_file	kit_igsexe_file
   kit_igshelper_file	kit_igshelper_file
   kit_sapcar_file	kit_sapcar_file
   kit_sapexe_file	kit_sapexe_file
   kit_saphotagent_file	kit_saphotagent_file
   kit_swpm_file	kit_swpm_file

5. Accept the license agreement.

6. Select Install. 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 Db2 by using the Schematics user interface

Use these steps to configure the SAP NetWeaver 7.X with Db2 on your existing VPC by using the Schematics user interface. The scripts can take 1 - 2 hours to complete.

1. From the IBM Cloud menu, select Schematics.

2. Click Create workspace.

3. On the Specify template page:

   • Enter the GitHub URL with the code you plan to deploy.
   • 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:

   • Your API key
   • Your private SSH key from your local machine
   • (Optional) you can change the ID_RSA_FILE_PATH for your SSH key that will be autogenerated on Schematics and Bastion Server
   • The ID for the SSH key that you created and uploaded to IBM Cloud. Enter the SSH key ID in square brackets and quotation marks, for example [ "ibmcloud_ssh_key_UUID1","ibmcloud_ssh_key_UUID2",... ].
   • The Region for your resources
   • The Zone for your resources
   • Whether to use an existing VPC or create one
   • Whether to use an existing subnet
   • Whether to create new port only when a new subnet is created
   • TCP port range, nimimun and maximum
   • VPC name
   • Subnet name
   • Security group name
   • Hostname
   • Profile
   • Image
   • Minimal recommended disk sizes
   • SAP main password - must be at least 10 characters, upper and lowercase letters, a number, and a special character, not an exclamation point.
   • Click Save changes.

   For a more detailed description of each of the parameters, check the GitHub repo readme file, chapter “Input parameter file”. Also, make sure to mark as “sensitive” the parameters that contain sensitive information like passwords, API, and ssh private keys (they 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 occurred during the provisioning, modification, or deletion process.

Next steps

If you need to rename your resources after they are created, modify the input.auto.tfvars file to change the names and run terraform plan and terraform apply again. Do not use the IBM Cloud Dashboard and user interface to modify your VPC after it is created. The Terraform scripts create a complete solution and selectively modifying resources with the user interface might cause unexpected results.

If you need to remove the SAP NetWeaver 7.X and Db2 installation, go to your project folder and run terraform destroy. The terraform destroy command does not remove the VPC in this scenario because the VPC was not created with the Terraform scripts.