Deploy a SAP S/4HANA application

This document describes how to use the Guided Deployment Automation tool in Workload Manager to deploy a SAP S/4HANA application.

Deploy a SAP S/4HANA application

To configure and deploy a SAP S/4HANA workload, perform the following tasks:

  1. In the Google Cloud console, go the Workload Manager page.

    Go to Workload Manager

  2. In the Workload Manager navigation pane, click Deployments.

  3. Select the project in which you want to create the deployment.

  4. Click New SAP Deployment.

    The New workload deployment page opens.

  5. In the Deployment basics section, enter information about your deployment and workload requirements. Workload Manager uses this basic information to determine the data to be collected in the subsequent tabs. Workload Manager also provides recommendations for your deployment configuration based on these basic settings.

    Field Description
    Name Enter a name to describe the workload you are deploying.

    Example: "S4-Prod-EP1"

    This name must be unique in the current project and is involved in naming some resources that are deployed. A maximum of 25 characters is allowed.
    Description Optional: An additional field that describes your workload. This description is displayed on the dashboard for your deployment.

  6. In the Service account field, select a service account that you want to attach to the deployment. Workload Manager uses this service account to call other APIs and services for creating resources required for the deployment. You can either select an existing service account or create a new service account.

    1. Click New service account to create a new service account for your deployment. The Create service account page opens. Enter the details of the service account and grant the required roles for deployment.

      For more information about the required roles, see Service accounts.

    2. Click Refresh list to populate the new service account in the list of service accounts.

  7. In the Product information section, enter the details of your SAP system and the deployment model. See Supported SAP workloads.

    Field Description
    SAP application Specify the SAP product to install.
    SAP version Select the version of the specified SAP application.
    Environment type Select whether the workload is intended for production use or non-production use
    Deployment model Select a deployment model:
    • Distributed with high availability: recommended for production systems and other critical workloads to achieve the highest availability.
    • Distributed: suitable for non-production workloads where availability is not critical to achieve lower cost.
    HANA scaling method Select the scaling method for the database.

  8. In the VM name prefix field, enter a prefix that is applied to the names of all VMs created during the deployment. A maximum of seven characters are allowed for the prefix.

  9. In the Software installation media bucket field, select the Cloud Storage bucket that holds the SAP installation media you uploaded. The bucket must exist within the project in which you're creating the deployment.

    For more information, see Prepare SAP installation files for deployment.

  10. Click Continue to proceed.

  11. In the Location & networking tab, enter the following.

    Field Description
    Project name Select the Google Cloud project in which you want to deploy the workload.
    Region Select the Google Cloud region in which you want to deploy the workload.
    Primary zone Select a zone from the specified region.
    Secondary zone Select a zone from the specified region for deploying the secondary system.
    This field is visible only if you've specified high availability (HA) as the deployment model in the basics section.
    Network Select the Virtual Private Cloud (VPC) network into which you're deploying the workload
    Subnet Select the subnet in the specified VPC network where you want to deploy the workload.
    Internet access Select a method for providing external internet access to the VMs. For more information, see Prerequisites.

    • Cloud NAT: If you want to provide external internet access using a Cloud NAT gateway that you've already created for the specified network.
    • Allow External IP: If you want to provide external internet access by reserving a static external IP address on each VM.
    DNS Zone Workload Manager automatically creates a DNS to allow communication between VMs in the deployment.

  12. Click Continue.

  13. In the Database tab, enter the following information:

    Field Description
    HANA SID Specify the SAP system ID (SID) for the database layer. The SID must consist of three alphanumeric characters and begin with a letter. All letters must be uppercase.
    Operating system Select a supported OS image. For more information, see Supported operating systems.

    All database VMs created during the deployment process use this operating system.
    Secret name for database credentials Select the name of the secret that corresponds to the password for SAP HANA database. Workload Manager uses this password throughout the deployment and installation process. This secret must exist in the Google Cloud project in which you create the deployment.
    Machine family Select a machine family for the database VMs.
    Series Select a machine series for the database VMs.
    Machine type Select a machine type for the database VMs.
    Block storage option Select the type of block storage for the HANA database VM.*

    *If you select Balanced Persistent Disk or SSD Persistent Disk during the deployment process, all disks in the deployment will be the selected disk type. If you select Hyperdisk Extreme, only the /data and /log volumes use Hyperdisk Extreme, and the other disk volumes use SSD Persistent Disk. Disk sizes for each volume is automatically calculated in accordance with the best practices for the selected machine type and block storage type.

  14. Click Continue.

  15. In the Application tab, configure the SAP Central services and application servers for your S/4HANA workload.

    General

    Field Description
    NetWeaver SID Specify the SAP system ID (SID) for the application layer. The SID must consist of three alphanumeric characters and begin with a letter. All letters must be uppercase.
    Operating system Select a supported OS image. For more information, see Supported operating systems.

    All application VMs created during the deployment process use this operating system.
    Secret for application credentials Select the name of the secret that corresponds to the password for your SAP application. Workload Manager uses this password throughout the deployment and installation process. This secret must exist in the Google Cloud project in which you create the deployment.
    Shared storage Workload Manager creates an NFS shared file storage solution for the deployment. For more information, see Filestore Enterprise.

    Central services


    Field
    Description
    Central services machine family Select a machine family for the ASCS VMs.

    Central services machine series    		 Select the machine series for the ASCS VMs.
    Central services machine type
    Select a machine type for the ASCS VMs.

    Application servers


    Field
    Description

    Number of application servers per zone    		 Specify the required number of application servers in each zone.

    For example, a value of 2 creates two application VMs in a non-HA deployment model or a total of four application VMs in a HA deployment model, where the four VMs are divided evenly across both zones.
    Application server machine family Select a machine family for the application servers.
    Application server machine series Select a machine series for the application servers.
    Application server machine type Select a machine type for the application servers.

  16. To see the Preview page, click Continue.

    The Preview page summarizes the deployment details you entered in the previous tabs of the wizard. In addition, you can view errors from the previous steps in the Deployment dashboard.

  17. To deploy the SAP workload, click Create.

Review the deployment status

After you create the deployment, you can monitor the status of the deployment on the dashboard by hovering the mouse over the Status icon.

You receive a notification in the Google Cloud console when Workload Manager completes the deployment process. If the deployment is not successful, you receive a failure notification. You can view additional information about the error on the Deployment Details page by clicking the deployment name on the dashboard. See Troubleshoot deployment errors.

Troubleshoot deployment errors

When an error occurs during the deployment process, you receive a notification on the Google Cloud console. You can view additional error details on the Deployment Details page. If possible, steps to resolve the error or root cause are also provided. Otherwise, the error message contains a link to logs containing additional information.

If the error occurred during the configuration or provisioning of resources:

  • If the underlying issue requires changing the deployment configuration (for example, deployment name was not unique):

    1. Delete the deployment.
    2. Create a new deployment by providing the correct information.

  • If the underlying issue does not require changing the deployment configuration (for example, insufficient quota):

    1. Resolve the issue.
    2. Click Retry on the error message to resume the deployment process.

If the error occurred during the Ansible process of the deployment:

  • If the underlying issue requires changing the deployment configuration (for example, you specified the wrong Cloud Storage bucket for SAP files):

    1. Delete the deployment.
    2. Create a new deployment by providing the correct configuration.

  • If the underlying issue does not require changing the deployment configuration (for example, OS package failed to download):

    1. Resolve the issue, if applicable.
    2. Delete the deployment
    3. Create a new deployment by providing the correct configuration.

What's next