Manual VM deployment for SAP NetWeaver on Windows

This guide shows you how to manually deploy and connect to a VM that is configured to run SAP NetWeaver on Microsoft Windows Server-based systems on Google Cloud. To deploy a VM that is running Linux, see the Linux Deployment Guide.

These instructions give you the details for setting up a 2-tier system, with all the SAP components and the database running on a single VM. During deployment, you also install Google's monitoring agent and can validate that it is sending metrics to SAP. This guide also includes considerations for migrating an existing system and for setting up a 3-tier scale-out system.

For more details on planning your implementation, see the Planning Guide. For an overview of IT ops for your system, see the Operations Guide.

Creating a project

To create a project:

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
  2. In the Google Cloud Console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.

Configuring the gcloud command environment

These instructions use Cloud Shell to enter gcloud commands that deploy or configure your Google Cloud resources. Cloud Shell is accessed through the Cloud Console in your browser.

Cloud Shell runs on a VM that Google Cloud provisions each time you start Cloud Shell. The first time you use Cloud Shell, Google Cloud also creates a persistent $HOME directory for you, which is restored each time you open Cloud Shell.

The provisioned VM includes the latest Cloud SDK, which provides the gcloud command-line interface. Therefore, the gcloud commands that you use in Cloud Shell are the same as those you would use in a locally installed instance of the Cloud SDK.

If you have the Cloud SDK installed, you can issue the gcloud commands that are used in these instructions from your local machine. However, with a locally installed Cloud SDK you must always make sure that you are using the latest version of the Cloud SDK.

Whether you use Cloud Shell or Cloud SDK, you can can set and change the properties of your gcloud command environment and save them as a configuration. Configurations are collections of key-value pairs that influence the behavior of the gcloud commands.

Some basic actions you can take with a configuration in Cloud Shell include:

  • Initialize a configuration with gcloud init.

  • Check the settings of your current gcloud configuration with gcloud config list.

  • Change the Google Cloud project you are working in with gcloud config set project [PROJECT_ID] where [PROJECT_ID] represents your Google Cloud project.

  • Set a default region with gcloud config set compute/region [REGION] where [REGION] represents a Google Cloud region.

  • Set a default zone with gcloud config set compute/zone [ZONE] where [ZONE] represents a Google Cloud zone.

  • Create a new configuration with gcloud config configurations create [NAME] where [NAME] represents the name for the configuration.

For more information about working with configurations, see Managing Cloud SDK configurations.

Creating a network

For security purposes, create a new network. You can control who has access by adding firewall rules or by using another access control method.

If your project has a default VPC network, don't use it. Instead, create your own VPC network so that the only firewall rules in effect are those that you create explicitly.

During deployment, VM instances typically require access to the internet to download Google's monitoring agent. If you are using one of the SAP-certified Linux images that are available from Google Cloud, the VM instance also requires access to the internet in order to register the license and to access OS vendor repositories. A configuration with a NAT gateway and with VM network tags supports this access, even if the target VMs do not have external IPs.

To set up networking:

  1. Go to Cloud Shell.

    Go to Cloud Shell

  2. To create a new network in the custom subnetworks mode, run:

    gcloud compute networks create [YOUR_NETWORK_NAME] --subnet-mode custom

    where [YOUR_NETWORK_NAME] is the name of the new network. The network name can contain only lowercase characters, digits, and the dash character (-).

    Specify --subnet-mode custom to avoid using the default auto mode, which automatically creates a subnet in each Compute Engine region. For more information, see Subnet creation mode.

  3. Create a subnetwork, and specify the region and IP range:

    gcloud compute networks subnets create [YOUR_SUBNETWORK_NAME] \
            --network [YOUR_NETWORK_NAME] --region [YOUR_REGION] --range [YOUR_RANGE]


    • [YOUR_SUBNETWORK_NAME] is the new subnetwork.
    • [YOUR_NETWORK_NAME] is the name of the network you created in the previous step.
    • [REGION] is the region where you want the subnetwork.
    • [YOUR_RANGE] is the IP address range, specified in CIDR format, such as If you plan to add more than one subnetwork, assign non-overlapping CIDR IP ranges for each subnetwork in the network. Note that each subnetwork and its internal IP ranges are mapped to a single region.
  4. Optionally, repeat the previous step and add additional subnetworks.

Setting up a NAT gateway

If you need to create one or more VMs without public IP addresses, you need to use network address translation (NAT) to enable the VMs to access the internet. Use Cloud NAT, a Google Cloud distributed, software-defined managed service that lets VMs send outbound packets to the internet and receive any corresponding established inbound response packets. Alternatively, you can set up a separate VM as a NAT gateway.

To create a Cloud NAT instance for your project, see Using Cloud NAT.

After you configure Cloud NAT for your project, your VM instances can securely access the internet without a public IP address.

Adding firewall rules

By default, incoming connections from outside your Google Cloud network are blocked. To allow incoming connections, set up a firewall rule for your VM. Firewall rules regulate only new incoming connections to a VM. After a connection is established with a VM, traffic is permitted in both directions over that connection.

You can create a firewall rule to allow access to specified ports, or to allow access between VMs on the same subnetwork.

Create firewall rules to allow access for such things as:

  • The default ports used by SAP NetWeaver, as documented in TCP/IP Ports of All SAP Products.
  • Connections from your computer or your corporate network environment to your Compute Engine VM instance. If you are unsure of what IP address to use, talk to your company's network admin.
  • Communication between VMs in a 3-tier, scaleout, or high-availability configuration. For example, if you are deploying a 3-tier system, you will have at least 2 VMs in your subnetwork: the VM for SAP NetWeaver, and another VM for the database server. To enable communication between the two VMs, you must create a firewall rule to allow traffic that originates from the subnetwork.
  • RDP connections to your VM instance through port 3389.
  • PowerShell connections to your VM instance through port 5986.

To create a firewall rule:

  1. In the Cloud Console, go to the Firewall Rules page.

    Open Firewall Rules page

  2. At the top of the page, click Create firewall rule.

    • In the Network field, select the network where your VM is located.
    • In the Targets field, select All instances in the network.
    • In the Source filter field, select one of the following:
      • IP ranges to allow incoming traffic from specific IP addresses. Specify the range of IP addresses in the Source IP ranges field.
      • Subnets to allow incoming traffic from a particular subnetwork. Specify the subnetwork name in the following subnets field. You can use this option to allow access between the VMs in a 3-tier or scaleout configuration.
    • In the Protocols and ports section, select Specified protocols and ports and specify tcp:[PORT_NUMBER];.
  3. Click Create to create your firewall rule.

Deploying a VM manually

The following instructions show you how to deploy a VM for an example 2-tier SAP system running Microsoft Windows and Microsoft SQL Server, SAP ASE, or IBM Db2 for Linux, UNIX, and Windows (IBM Db2). All the SAP NetWeaver components and the central database run on one VM.

For general considerations for a 3-tier system, see Deploying a 3-tier scale-out system.

Before you begin, ensure that you have consulted the Planning Guide and, if you are going to use Microsoft SQL Server, that you have decided how you want to install the SQL Server database from the following options:

  • Use a Google Cloud image that includes the database.
  • Install it using installation media.

Creating and setting up a VM

When you create a VM, you can specify several options, including the operating system, region, machine type, and persistent disks. Later, after the VM is deployed, you must also install the Google Cloud monitoring agent for SAP NetWeaver on the VM.

To create a VM:

  1. Go to the Images page in Compute Engine:

    Go to the Images page

  2. Choose a public image that contains a version of Microsoft Windows Server that is supported by SAP.

    If you are using Microsoft SQL Server as your database, you can migrate your existing license to GCP or use a Compute Engine Windows Server image that has SQL Server preinstalled. For more information about the SQL Server images provided by Google Cloud, see Windows on Compute Engine.

    For the versions of Windows Server and SQL Server that are supported by SAP on GCP, see SAP Note 2456432: SAP Applications on Google Cloud Platform: Supported Products and Google VM types.

  3. Click the Create instance button.

  4. Enter a name for the VM.

    Limit your name to 13 characters, because this is the maximum supported by SAP. For more information, see SAP Note 611361: Hostnames of SAP servers.

  5. Select the region and zone for your VM based on the location of your internal resources and users, and based on the CPU platform you want to use.

    For more details on the zones supported for SAP NetWeaver, see the following guides and SAP Notes:

  6. Under Machine type, select a pre-defined n1-standard or n1-highmem machine type or customize a VM to more precisely match the VM's vCPUs and memory to your expected workload.

    To compare the supported machine types and their persistent-disk limitations, see the Planning Guide.

  7. Optionally, in the Boot disk section, click Change to adjust the size of your boot disk. Ensure that the boot disk is at least 50 GB.

  8. Under Service account, select a service account that appropriately limits access to Google Cloud resources from the VM.

    If you haven't created a service account, you can use the default service account, but it is usually too permissive for most enterprise users. For more information about service accounts, see IAM for SAP programs.

  9. Under Access Scopes:

    • If you are using the Compute Engine default service account, select Set access for each API.
    • If you are using a custom service account that limits access to Google Cloud resources, select Allow full access to all APIs.

    Compute Engine recommends configuring your VM instances to allow full access to all Cloud APIs and using only the IAM permissions of the instance service account to control access to Google Cloud resources. For more information, see Best practices.

    If you selected Set access for each API, to ensure that your VM instance can interact with Compute Engine and Cloud Monitoring and that the Google monitoring agent functions correctly, the following API access scopes are recommended for the service account:

    API Access
    Cloud Source Repositories Read Write
    Compute Engine Read Write
    Service Control Enabled
    Service Management Read Only
    Cloud Logging API Full
    Cloud Monitoring API Full
    Cloud Trace Write Only
    Storage Full
  10. Expand the Management, disks, networking, sole tenancy section.

  11. If you are using a NAT gateway, in the Networking tab, under Network tags, add the tag that you specified as [YOUR_TAG_NAME] when you set up the route that directs traffic through the gateway.

  12. In the Management tab, under Availability policy, ensure that you leave the following default settings:

    • To ensure availability of your SAP systems, keep the Preemptibility setting Off (recommended).
    • To ensure that your VM can restart if there's a maintenance or failure event, keep the Automatic restart setting On (recommended).
    • To ensure that your VM is migrated to other hardware during infrastructure maintenance, keep the On host maintenance setting on Migrate VM instance (recommended).
  13. Optionally, in the Disks tab, under Boot disk > Deletion rule, deselect the Delete boot disk when instance is deleted checkbox.

  14. In the Disks tab, under Additional disks, click Add new disk to add persistent disks for storage.

    For NetWeaver, add disks for the SAP NetWeaver binaries and the pagefile disk. For the database server, you also need disks for things like the database data and logs. For information about the types of persistent disks that you can choose, see Persistent disk storage.

    1. Optionally, specify a name in the Name field.

    2. In the Create a disk window, under Disk Type select the disk type.

    3. Under Source type, select Blank disk.

    4. Specify the size of your disk.

    5. Click Done to save your disk settings.

    6. Repeat these steps for each disk you need to add to your system.

  15. In the Networking tab, under Network interfaces, click the pencil icon to edit the selected network interface. Select the network that you created previously.

  16. Click Create to create and start the instance.

At the bottom of the page, you can click REST or command line to see the equivalent REST and gcloud commands for the instance you are creating. These can be useful for creating additional VMs.

Connecting to your VM

To connect to a Windows-based VM, you must first generate a password for the VM. You can then connect to the VM using RDP or PowerShell.

Generating passwords
  1. Go to the VM instances page.


  2. Click the name of the VM instance for which you need a new password.

  3. On the instance details page, click the Set Windows Password button. A password is generated for you.

Using RDP

If you have defined a firewall rule that allows access on port 3389, you can use RDP to connect to a Windows instance and start a Remote Desktop session. Alternatively, you can connect to Windows instances using the PowerShell terminal.

Connect to the remote desktop on Windows instances using one of the following methods:

  • Use a Chrome browser that has the Chrome RDP for Google Cloud extension installed and establish an RDP connection from Cloud Console.
  • Download the RDP file and manually connect through the Windows Remote Desktop Connection client or a third-party client.


  1. If the Chrome RDP for Google Cloud extension is not installed already in your Chrome browser, install it now.

    To check for the Chrome RDP for Google Cloud Platform extension, enter chrome://extensions/ in your browser address bar and look for the extension under Chrome Apps on the Extensions page of your Chrome browser.

  2. Go to the VM instances page in Cloud Console.


  3. Click the RDP button next to the instance that you want to connect to. A new browser window opens with the Chrome RDP for Google Compute Engine extension.

  4. Enter your username and password. If this is your first time connecting to this instance, or if you have forgotten your password, create or reset your Windows password.

  5. Click OK to connect.

RDP Client

  1. Install an RDP client. If you don't have a preference, install the Chrome RDP for Google Compute Engine Engine extension.

  2. Get your Windows VM's external IP address. Go to the VM instances page in Cloud Console or run gcloud compute instances list to see a list of your instances with their external IP values.

  3. In your RDP client, provide your VM's external IP address as the IP address to connect to. For example, in the Chrome RDP extension, you would enter the IP address in the following format:

    Screenshot of the instance creation window with the required options

  4. Enter your sign-in information and leave the Domain field blank. If this is your first time connecting to this VM, or if you have forgotten your password, create or reset your Windows password.

    Screenshot of the instance creation window with the required options

Using PowerShell
  1. If you have not created a username and password on the Windows VM yet, create your Windows password.

  2. Add a firewall rule or edit your existing firewall rule to open port 5986 on the Google Cloud network where your Windows Server VM is located.

  3. On your local workstation, open the PowerShell terminal.

  4. Optionally, you can initialize a variable to hold your user credentials so you do not need to enter them each time you connect to the instance. If you skip this step, you receive a prompt for your username and password later.

    $credentials = Get-Credential

  5. Use the Enter-PSSession command to start a remote PowerShell session and include the flags to use SSL and skip credentials checks.

    Enter-PSSession -ComputerName [IP_ADDRESS] -UseSSL -SessionOption (New-PSSessionOption -SkipCACheck -SkipCNCheck) -Credential $credentials

Formatting and mounting disk drives

After you have connected to your Windows VM, format your disks so that you can begin using them. You also configure the Windows pagefile.

  1. From the Windows Start menu, search for and open the Server Manager.

  2. Select File and Storage Services and then select Disks.

    Server Manager

  3. In the Disks dialog box, right-click the first disk, and then select New Volume. The New Volume Wizard opens.

  4. Optionally, on the Drive Letter or Folder panel, select a drive letter for the disk. For example, S for the SAP disk, or P for the pagefile disk. You can accept all other defaults.

  5. On the File System Settings panel, enter a volume label that describes the disk with a meaningful name, such as SAP or Pagefile.

    New Volume Wizard

  6. Accept all other defaults.

  7. Repeat these steps for the additional disks.

Preparing the operating system

After you have created your VM, configure the operating system:

Setting up the database

If you haven't yet deployed your database on Google Cloud, follow the instructions for setting up your database in both the Google Cloud deployment guide for your database, and in the database documentation that is provided by your database vendor.

Google Cloud provides deployment guides for the following SAP-certified databases:

When SAP NetWeaver and the database server are running on different VMs in a 3-tier architecture, make sure that your firewall rules are defined to allow communication between the VMs.

If you used the Google Cloud-provided Windows image that contains SQL Server, you must change the collation to use the SAP collation.

Configuring the Google Cloud Microsoft SQL Server image

If you selected the Google-provided SQL Server Enterprise operating system image when you created your VM, you must configure SQL Server to use the SAP collation (SQL_Latin1_General_CP850_BIN2) so that SQL Server is compatible with SAP systems. The default collation in the Google Cloud-provided SQL Server image is (SQL_Latin1_General_CP1_CI_AS).

To change the collation after the VM is deployed:

  1. Connect to your Windows instance by using either RDP or remote PowerShell.
  2. Sign in to Windows as an admin and stop the MSSQLSERVER service.
  3. Go to the directory that contains the binaries for your SQL Server instance, for example, C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn.
  4. From an elevated command prompt, change the collation by running:

    sqlservr -m -T4022 -T3659 -s"[SQL_SERVER_INSTANCE_NAME]" -q"SQL_Latin1_General_CP850_BIN2"


    • The parameter -m starts the SQL Server instance in single-user mode.
    • The trace flag 4022 forces SQL Server to skip any stored startup procedures.
    • The trace flag 3659 allows all errors to be logged to the SQL Server logs.
    • The parameter -s specifies the name of the SQL Server instance to start. Replace [SQL_SERVER_INSTANCE_NAME] with your SQL Server instance name.
    • The parameter -q rebuilds all databases and objects to the specified SAP collation, without reinstalling the instance or rebuilding system databases.
  5. Restart the SQL Server Service MSSQLSERVER after the collation is changed.

  6. Confirm your change in the most recent SQL Server ERRORLOG or the server's collation properties.

For more information about the configuration of SQL Server for SAP, see:

Installing the Cloud Logging agent

The Cloud Logging agent provides you with a solution for Google Cloud system-activity logging, including operating system events and, if you are using SAP HANA, SAP HANA events. The Cloud Logging agent is an optional but recommended component. See the SAP NetWeaver on Google Cloud operations guide for more information about Google Cloud logging.

To install the Cloud Logging agent in your new VM, see the instructions for Linux and Windows in Installing the agent.

Install the monitoring agent for SAP NetWeaver

The Google Cloud monitoring agent for SAP NetWeaver is required for SAP support of SAP NetWeaver on Google Cloud.

When you install the agent on a Compute Engine VM, the monitoring agent for SAP NetWeaver combines monitoring data from Monitoring and the Compute Engine APIs and provides that data to the SAP Host Agent.

The monitoring agent for SAP NetWeaver is also required when you run SAP NetWeaver on a Bare Metal Solution machine, in which case, the agent does not include data from Monitoring. To install the monitoring agent for SAP NetWeaver on a Bare Metal Solution machine, see Install the monitoring agent for SAP NetWeaver.

Prerequisites for the monitoring agent for SAP NetWeaver

Compute Engine recommends configuring your VM instances to allow full access scopes to all Cloud APIs and using only the IAM permissions of the instance service account to control access to Google Cloud resources. For more information, see Best practices.

If you do limit access to the Cloud APIs, the monitoring agent for SAP NetWeaver requires the following minimum Cloud API access scopes on the host VM instance:

  • Compute Engine: Read Only
  • Stackdriver Monitoring API: Read Only

If you are running SAP NetWeaver on a VM that does not have an external IP address, you must enable Private Google Access on the VM's subnet so that the monitoring agent for SAP NetWeaver can access Google APIs and services.

To enable Private Google Access on a subnet, see Configuring Private Google Access.

Installing the monitoring agent for SAP NetWeaver

To install the monitoring agent for SAP NetWeaver, as an administrator on the host VM, issue the following command:

. { iwr -useb } | iex

After you install SAP NetWeaver and the SAP Host Agent, validate the installation of the monitoring agent for SAP NetWeaver, as described in Validating your installation of the monitoring agent.

For an overview of installation actions, see the Installation overview.

Installing SAP NetWeaver

For instructions on installing SAP NetWeaver on your new VM, see the SAP help portal and the SAP NetWeaver Master Guide.

After you install SAP NetWeaver:

  1. Update the SAP kernel to the minimum supported patch level.

    For details on the supported SAP kernel patch levels, see SAP Note 2456953 - Windows on Google Cloud (IaaS): Adaptation of your SAP License.

  2. Install your permanent SAP NetWeaver license.

    For more information from SAP about managing your SAP NetWeaver licenses, see SAP Licensing Procedure.

Installing the SAP Host Agent

The SAP Host Agent has been enhanced for running on Google Cloud. Ensure that you run at least the minimum SAP Host Agent version required for the Google Cloud environment.

For details, refer to the following SAP Notes:

Validating your installation of the monitoring agent

After you have deployed a VM and installed SAP NetWeaver, validate that Google's monitoring agent is functioning properly with SAP's enhanced monitoring.

Verifying that Google's monitoring agent is running

You can check whether the monitoring agent is running by polling for a health check from the server. Follow these steps:

  1. Use RDP to connect to the VM instance you want to monitor.

  2. In a browser, visit http://localhost:18181/health.

If the monitoring agent is functioning properly, the value for status is UP. For example:


If the monitoring agent isn't running, see the Operations Guide section about restarting Google's monitoring agent.

Verifying that SAP NetWeaver is receiving metrics

To check whether the connection between Google's monitoring agent and SAP NetWeaver works as intended, enter transaction ST06 in your SAP NetWeaver ABAP system. In the overview pane, check the availability and content of the following fields for the correct end-to-end setup of the SAP and Google monitoring infrastructure:

  • Cloud Provider: Google Cloud Platform
  • Enhanced Monitoring Access: TRUE
  • Enhanced Monitoring Details: ACTIVE

Deploying a 3-tier scale-out system

The steps to deploy each VM in a 3-tier system are very similar to the steps for deploying the example system. In a 3-tier scale-out system, you deploy several VMs, all in the same zone:

  • A primary VM that runs the SAP NetWeaver application server (AS) and ABAP central services. This VM also hosts a shared file system that contains the shared profile and must be accessible from each VM that runs SAP NetWeaver in the system.
  • Some number of additional VMs that run the AS, for scaling purposes.
  • A VM that is dedicated to the central database.

The high-level steps are as follows:

  1. Create the VM that hosts the database and then install the database. If you used a Compute Engine image that includes SQL Server, the database is already installed.

  2. Create the primary instance.

    • Run SWPM on the first VM that you want to run SAP NetWeaver.
    • Install central services.
    • Install the AS.
    • Point to the existing database.
  3. Create additional instances.

    • Run SWPM on each additional VM that you want to run SAP NetWeaver.
    • Install the AS.
    • Point to the existing database.
    • Point to the network share that contains the profiles and is managed by the primary instance.


This section contains information about how to correct common issues.

Troubleshooting communication problems to the database server

If you are setting up a 3-tier SAP system and having connection issues between your VMs, ensure that you have created a firewall rule to allow traffic between VMs on your subnetwork.

Troubleshooting Google's monitoring agent

To troubleshoot the monitoring agent, see the Operations guide.