[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-11。"],[],[],null,["# Deploy an SAP S/4HANA application\n\nThis document describes how to deploy an SAP S/4HANA application on Google Cloud\nby using the Guided Deployment Automation tool in Workload Manager.\n\nDeploy an SAP S/4HANA application\n---------------------------------\n\nTo configure and deploy an SAP S/4HANA workload, perform the following tasks:\n\n1. In the Google Cloud console, go the **Workload Manager** page.\n\n [Go to Workload Manager](https://console.cloud.google.com/workload-manager)\n2. In the **Workload Manager** navigation pane, click **Deployments**.\n\n3. Select the project in which you want to create the deployment.\n\n4. Click **Create deployment** and choose **SAP**.\n\n5. In the **Deployment basics** section, enter information about your\n deployment and workload requirements. Workload Manager uses this basic\n information to determine the data to be collected in the subsequent tabs.\n Workload Manager also provides recommendations for your\n deployment configuration based on these basic settings.\n\n6. In the **Service account** field, select a service account that\n you want to attach to the deployment. Workload Manager uses\n this service account to call other APIs and services for creating resources\n required for the deployment. You can either select an existing service\n account or create a new service account.\n\n 1. Click **New service account** to create a new service account for your\n deployment.\n The **Create service account** page opens. Enter the details of the\n service account and grant the required roles for deployment.\n\n For more information about the required roles,\n see [Service accounts](/workload-manager/docs/deploy/sap/prerequisites-sap#service-accounts).\n 2. Click **Refresh list** to populate the new service account in the list\n of service accounts.\n\n | **Note:** If the service account is missing any of the required roles for creating a deployment, Workload Manager prompts you to grant these roles. Click **Grant** to grant the missing roles to the attached service account.\n7. In the **Ansible Runner service account** section, select a service account\n for the temporary Ansible Runner VM created during the deployment process.\n You can either create a service account or choose an existing service account with the\n required IAM permissions. For more information, see\n [Service accounts and permissions](/workload-manager/docs/deploy/sap/prerequisites-sap#service-accounts).\n\n8. Optional: This step is required only if your organization enforces VPC Service Controls\n compliance. In the **Private pool** field, specify the name of a Cloud Build private pool\n that is configured for VPC Service Controls in the following format:\n\n ```\n projects/PRIVATEPOOL_PROJECT_ID/locations/REGION/workerPools/PRIVATEPOOL_ID\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003ePRIVATEPOOL_PROJECT_ID\u003c/var\u003e: the ID of the project that contains the private pool\n - \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region where you created the private pool\n - \u003cvar translate=\"no\"\u003ePRIVATEPOOL_ID\u003c/var\u003e: the ID of the private pool\n\n For more information, see [Use a Cloud Build private worker pool](/workload-manager/docs/deploy/prerequisites#vpc-sc-pool).\n9. In the **Product information** section, enter the details of your SAP system and\n the deployment model. See [Supported SAP workloads](/workload-manager/docs/deploy/about-wlm-deployment#supported-system).\n\n \u003cbr /\u003e\n\n10. In the **VM name prefix** field, enter a prefix that is applied to the names\n of all VMs created during the deployment.\n A maximum of seven characters are allowed for the prefix.\n\n11. In the **Software installation media bucket** field, select the Cloud Storage\n bucket that holds the SAP installation media you uploaded. The bucket\n must exist within the project in which you're creating the deployment.\n\n For more information, see [Prepare SAP installation files for deployment](/workload-manager/docs/deploy/sap-install-files).\n12. Click **Continue** to proceed.\n\n13. In the **Location \\& networking** tab, enter the following.\n\n14. Click **Continue**.\n\n15. In the **Database** tab, enter the following information:\n\n ^\\*^If you select Balanced Persistent Disk or SSD Persistent Disk\n during the deployment process, all disks in the deployment will be the\n selected disk type. If you select Hyperdisk Extreme, only\n the `/data` and `/log` volumes use Hyperdisk Extreme,\n and the other disk volumes use SSD Persistent Disk.\n Disk sizes for each volume is automatically calculated in accordance with\n the best practices for the selected machine type and block storage type.\n16. Click **Continue**.\n\n17. In the **Application** tab, configure the SAP Central services and\n application servers for your S/4HANA workload.\n\n **General**\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n \u003cbr /\u003e\n\n **Central services**\n\n **Application servers**\n\n18. To see the **Preview** page, click **Continue**.\n\n The **Preview** page summarizes the deployment details you entered in the\n previous tabs of the wizard. In addition, you can view errors from the\n previous steps in the Deployment dashboard.\n19. To deploy the SAP workload, click **Create**.\n\nReview the deployment status\n----------------------------\n\nAfter you create the deployment, you can monitor the status of the deployment on\nthe dashboard by hovering the mouse over the **Status** icon.\n\nYou receive a notification in the Google Cloud console when Workload Manager\ncompletes the deployment process. If the deployment is not successful, you\nreceive a failure notification. You can view additional information about the\nerror on the Deployment Details page by clicking the deployment name on the\ndashboard. See [Troubleshoot deployment errors](#troubleshoot).\n| **Note:** The entire deployment process can take up to two or three hours to complete. The deployment process continues in the background. You can check the deployment dashboard once you receive the notification.\n\nTroubleshoot deployment errors\n------------------------------\n\nWhen an error occurs during the deployment process, you receive a notification\non the Google Cloud console. You can view additional error details on the\n**Deployment Details** page. If possible, steps to resolve the error or root\ncause are also provided. Otherwise, the error message contains a link to logs\ncontaining additional information.\n\nIf the error occurred during the configuration or provisioning of resources:\n\n- If the underlying issue requires changing the deployment configuration (for\n example, deployment name was not unique):\n\n 1. Delete the deployment.\n 2. Create a new deployment by providing the correct information.\n- If the underlying issue does not require changing the deployment\n configuration (for example, insufficient quota):\n\n 1. Resolve the issue.\n 2. Click **Retry** on the error message to resume the deployment process.\n\nIf the error occurred during the Ansible process of the deployment:\n\n- If the underlying issue requires changing the deployment configuration\n (for example, you specified the wrong Cloud Storage bucket for SAP\n files):\n\n 1. Delete the deployment.\n 2. Create a new deployment by providing the correct configuration.\n- If the underlying issue does not require changing the deployment\n configuration (for example, OS package failed to download):\n\n 1. Resolve the issue, if applicable.\n 2. Delete the deployment\n 3. Create a new deployment by providing the correct configuration.\n\nWhat's next\n-----------\n\n- [Perform the post-deployment tasks](/workload-manager/docs/deploy/post-deployment)."]]
