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.

Terraform deployment

You can use Terraform on the bastion server CLI to download and run the scripts that are located in SAP NetWeaver ABAP Db2 3-tier 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 NW 7.x with Db2 3-tier on the specified VPC in your IBM Cloud account.

Deploying SAP NetWeaver 7.x and Db2 on 3-tier by using the Schematics user interface

Use these steps to configure the SAP NetWeaver 7.x with Db2 3-tier 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 for 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.
   • Click 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, minimum 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 in the “Input parameter file”).

7. On the workspace Settings page, click Generate plan. Wait for the plan to complate.

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.

Deploying SAP NetWeaver 7.x and Db2 3-tier 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 NW 7.x with Db2 3-tier 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-distributed and cd to the sap-netweaver-abap-db2-distributed folder.

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

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 profiles, see Instance profiles. For more options for images, see Images. For descriptions of the variables, see the README file.

   # Infra VPC variables
   REGION          = "eu-de"
   ZONE            = "eu-de-2"
   VPC             = "sap"                  # EXISTING VPC name
   SECURITY_GROUP	= "sap-securitygroup"    # EXISTING security group name
   SUBNET          = "sap-subnet"           # EXISTING subnet name
   RESOURCE_GROUP  = "wes-automation"       # EXISTING resource group
   SSH_KEYS        = [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
   
   # SAP Database VSI variables:
   DB-HOSTNAME     = "sapnwdb2"
   DB-PROFILE      = "bx2-4x16"
   DB-IMAGE        = "ibm-redhat-8-4-amd64-sap-applications-4" # 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    = "sapnwapp"
   APP-PROFILE     = "bx2-4x16"
   APP-IMAGE       = "ibm-redhat-8-4-amd64-sap-applications-4" # 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.
   

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 = "NWA"
   sap_ascs_instance_number = "01"
   sap_ci_instance_number = "00"
   
   # 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.

   terraform apply "plan1"
   

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

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

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 distributed 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.