Schematics deployment

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

• Enter the URL for the GitHub repository for the Schematics Terraform files
• 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

The configuration and script files are provided on GitHub. Each supported interface for the SAP solution installation has its own folder in the GitHub repository:

• Using Terraform on the Bastion server for standard - https://github.com/IBM-Cloud/sap-netweaver-abap-ase-syb-standard/tree/main
• Using Terraform on the Bastion server for distributed deployment - https://github.com/IBM-Cloud/sap-netweaver-abap-syb-distributed/tree/main

Before you run the Terraform scripts, you modify:

• The input.auto.tfvars file to specify the existing VPC resources for your solution. You specify the variables for the existing VPC:

  • 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 SAP NetWeaver 7.X with ASE SYB v16 on the specified VPC in your IBM Cloud account.

Creating the infrastructure with the Schematics user interface

Use these steps to configure the SAP NetWeaver 7.X with ASE SYB 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 URL of Schematics folder.
   • 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 systems.
   • 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, uppercase 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 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 make sure that no errors occurred during the provisioning, modification, or deletion process.

Creating the infrastructure 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 NetWeaver 7.X with ASE SYB (standard or distributed architecture) on your existing VPC. The scripts can take 1 - 2 hours to complete.

1. Access the Bastion server cli.

2. For Standard deployment: Clone the solution repository from https://github.com/IBM-Cloud/sap-netweaver-abap-ase-syb-standard and cd to the sap-netweaver-abap-ase-syb-standard folder.

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

3. For Distributed deployment:

   Clone the solution repository from https://github.com/IBM-Cloud/sap-netweaver-abap-syb-distributed and cd to the sap-netweaver-abap-syb-distributed/cli folder.

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

4. Specify your VPC variables, for standard or distributed deployment. 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 standard readme file or distributed readme file.

   For standard deployment:

   #Infra VPC variables for standard deployment
   ZONE			= "eu-de-2"
   VPC			= "sap"
   SECURITYGROUP		= "sap-securitygroup"
   SUBNET			= "sap-subnet"
   HOSTNAME		= "db2saps1"
   PROFILE			= "bx2-4x16"
   IMAGE			= "ibm-redhat-8-6-amd64-sap-applications-2"
   SSH_KEYS		= [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
   

   For distributed deployment:

   #Infra VPC variables for distributed deployment
   ZONE			= "eu-de-2"
   VPC			= "sap"
   SECURITYGROUP		= "sap-securitygroup"
   SUBNET			= "sap-subnet"
   DB-HOSTNAME = "sapnwasedb"
   DB-PROFILE = ""bx2-4x16"
   DB-IMAGE = "ibm-redhat-8-6-amd64-sap-applications-2"
   APP-HOSTNAME = "sapnwapp"
   APP-PROFILE = "bx2-4x16"
   APP-IMAGE = "ibm-redhat-8-6-amd64-sap-applications-2"
   
   SSH_KEYS		= [ "r010-57bfc315-f9e5-46bf-bf61-d87a24a9ce7a" , "r010-3fcd9fe7-d4a7-41ce-8bb3-d96e936b2c7e" ]
   

5. Customize your SAP system configuration, standard or distributed. 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.

   For standard deployment:

   #SAP system configuration for standard deployment
   sap_sid	= "NWD"
   sap_ci_instance_number = "00"
   sap_ascs_instance_number = "01"
   
   #Kits paths
   kit_sapcar_file = "/storage/NW75SYB/SAPCAR_1010-70006178.EXE"
   kit_swpm_file = "/storage/NW75SYB/SWPM10SP31_7-20009701.SAR"
   kit_saphotagent_file = "/storage/NW75SYB/SAPHOSTAGENT51_51-20009394.SAR"
   kit_sapexe_file = "/storage/NW75SYB/SAPEXE_900-80002573.SAR"
   kit_sapexedb_file = "/storage/NW75SYB/SAPEXEDB_900-80002616.SAR"
   kit_igsexe_file = "/storage/NW75SYB/igsexe_13-80003187.sar"
   kit_igshelper_file = "/storage/NW75SYB/igshelper_17-10010245.sar"
   kit_ase_file = "/storage/NW75SYB/51055443_1.ZIP"
   kit_export_dir = "/storage/NW75SYB/EXP"
   

   For distributed deployment

   #SAP system configuration for distributed deployment
   sap_sid  = "NWD"
   sap_ci_instance_number = "00"
   sap_ascs_instance_number = "01"
   
   #Kits paths
   kit_sapcar_file = "/storage/NW75SYB/SAPCAR_1010-70006178.EXE"
   kit_swpm_file =  "/storage/NW75SYB/SWPM10SP31_7-20009701.SAR"
   kit_saphotagent_file = "/storage/NW75SYB/SAPHOSTAGENT51_51-20009394.SAR"
   kit_sapexe_file = "/storage/NW75SYB/SAPEXE_900-80002573.SAR"
   kit_sapexedb_file = "/storage/NW75SYB/SAPEXEDB_900-80002616.SAR"
   kit_igsexe_file = "/storage/NW75SYB/igsexe_13-80003187.sar"
   kit_igshelper_file = "/storage/NW75SYB/igshelper_17-10010245.sar"
   kit_ase_file = "/storage/NW75SYB/51055622_1.ZIP"
   kit_export_dir = "/storage/NW75SYB/EXP"
   

6. Remember, you must manually decompress the kit_export_dir file. Ansible decompresses the rest of the SAP kit files. For more information, see the readme file.

7. Initialize the Terraform CLI terraform init

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

   Enter the 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 exclamation points '!'. The password must not start with a digit or an underscore ( _ ).

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

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

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

12. 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 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 that 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 system
   • (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 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 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 make sure 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 Netweaver 7.X and ASE SYB 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 created before these Terraform scripts were run.