This guide uses Deployment Manager to deploy all of the required Google Cloud resources to run SAP NetWeaver on Linux, including the Compute Engine virtual machine (VM), the Linux operating system, and the persistent disks. You define the values for the installation, such as machine type, resource names, disk sizes, and so forth, in a Deployment Manager configuration file template.
If your SAP NetWeaver installation requires more control over the deployment process than the Deployment Manager template provides, see Manual VM deployment for SAP NetWeaver on Linux.
To deploy a VM that is running Windows, see the Windows deployment guide.
VM configuration deployed by these instructions
The VM that is deployed by these instructions is for use in a 3-tier configuration, where SAP NetWeaver runs on one VM and the database server runs on another.
To set up a 2-tier configuration, where SAP NetWeaver runs on the same VM as the database server, you deploy the database server first and create the VM and the required disk drives for both the database server and for SAP NetWeaver at that time. You then install SAP NetWeaver on the same VM as the database server.
For instructions about deploying the VM for a database server, see the database deployment guide for your database server.
Google Cloud resources deployed by these instructions
The Google Cloud resources that are deployed by Deployment Manager include:
- A VM that uses an SAP-certified version of Linux.
- A persistent disk for the boot disk.
- A persistent disk for SAP binaries.
- A persistent disk for swap space.
- The recommended APIs.
The following instructions use Cloud Shell, but if you prefer, you can use the Cloud SDK in your local terminal instead.
Creating a project
To create a project:
- 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.
In the Google Cloud Console, on the project selector page, select or create a Google Cloud project.
Make sure that billing is enabled for your Cloud project. Learn how to confirm that billing is enabled for your project.
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
which provides the
gcloud command-line interface. Therefore, the
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
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
Some basic actions you can take with a configuration in Cloud Shell include:
Initialize a configuration with
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:
Go to Cloud Shell.
To create a new network in the custom subnetworks mode, run:
gcloud compute networks create [YOUR_NETWORK_NAME] --subnet-mode custom
[YOUR_NETWORK_NAME]is the name of the new network. The network name can contain only lowercase characters, digits, and the dash character (-).
--subnet-mode customto avoid using the default auto mode, which automatically creates a subnet in each Compute Engine region. For more information, see Subnet creation mode.
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 10.1.0.0/24. 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.
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.
- SSH connections to your VM instance, including
SSH from the browser,
- Connections to your VM instance from third-party tools, such as a local terminal or PuTTY. Create a rule to allow access for the tool through your firewall. For more information, see Connecting using third-party tools.
To create a firewall rule:
In the Cloud Console, go to the Firewall Rules page.
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
Click Create to create your firewall rule.
Deploying a Linux VM for SAP NetWeaver with Deployment Manager
The following instructions use Cloud Console, Cloud Shell, and Deployment Manager to deploy a VM instance with Linux and all of the persistent disks that SAP NetWeaver requires.
About Deployment Manager
In these instructions, you define the resource options for your installation in a Deployment Manager configuration file template.
Deployment Manager treats all of the resources that are created for your SAP system as a single entity called a deployment. You can view and work with all of the deployments for your project on the Deployments page in the Cloud Console.
Be aware of the following behaviors when using Deployment Manager:
- Deleting a deployment deletes all of the resources associated with the deployment, including the VMs, the persistent disks, and any SAP systems that are installed on the VM.
By default, Deployment Manager uses the
ACQUIREresource creation policy. If you specify a VM name that is already in use by another VM in your project, Deployment Manager doesn't create a new VM, but instead adds the existing VM to your new deployment. If your original VM was created by a previous run of Deployment Manager, the VM is associated with two deployments.
If you then delete the new deployment, the acquired VM is deleted from the deployment that originally created it. To avoid such a scenario, either set the Deployment Manager resource policy to
CREATE, or make sure that you use unique resource names in your new deployment.
For information about the policies you can use while creating resources with Deployment Manager and how to specify them, see the Deployment Manager documentation.
Open Cloud Shell.
template.yamlconfiguration file template to your working directory:
Optionally, rename the
template.yamlfile to identify the configuration it defines. For example,
To open the
template.yamlfile in Cloud Shell code editor, click the pencil (edit) icon in the upper right corner of Cloud Shell terminal window to launch the editor.
template.yamlfile, update the following property values by replacing the brackets and their contents with the values for your installation.
Property Data type Description type String
Specifies the location, type, and version of the Deployment Manager template to use during deployment.
The YAML file includes two
typespecifications, one of which is commented out. The
typespecification that is active by default specifies the template version as
typespecification that is commented out specifies a specific template version with a timestamp.
If you need all of your deployments to use the same template version, use the
typespecification that includes the timestamp.
String The name of the VM instance on which SAP NetWeaver will be installed. The name must be 13 characters or less and be specified in lowercase letters, numbers, or hyphens. Use a name that is unique within your project.
String The type of Compute Engine virtual machine that you need. If you need a custom VM type, specify a small predefined VM type and, after deployment is complete, customize the VM as needed.
String The zone in which you are deploying your SAP NetWeaver. It must be in the same region that you selected for your subnetwork.
String The name of the subnetwork that you created in a previous step. If you are deploying to a shared VPC, specify this value as
[SHAREDVPC_PROJECT]/[SUBNETWORK]. For example,
String The name of the Linux operating-system image or image family that you are using with SAP NetWeaver. To specify an image family, add the prefix
family/to the family name. For example,
family/rhel-7-sap-hana. For the list of available image families, see the Images page in the Cloud Console.
String The Google Cloud project that contains the image you are going to use. This project might be your own project or a Google Cloud image project, such as
suse-sap-cloud. For a list of Google Cloud image projects, see the Images page in the Compute Engine documentation.
Integer The size of the `/usr/sap` disk. The minimum size is 8 GB.
Integer The size of the `/sapmnt` disk. The minimum size is 8 GB.
Integer The size of the swap volume. The minimum size is 1 GB.
String Optional. A network tag that represents your VM instance for firewall or routing purposes. If you specify `publicIP: No` and do not specify a network tag, be sure to provide another means of access to the internet.
Boolean Optional. Determines whether a public IP address is added to your VM instance. The default is
Boolean Optional. If this value is set to
Yes, the deployment generates verbose deployment logs. Do not turn this setting on unless a Google support engineer asks you to enable debugging.
The following configuration file creates a VM that is configured to run SAP NetWeaver. The configuration file directs Deployment Manager to deploy the
n1-standard-16VM that is running a SLES 12 SP2 operating system. The VM includes all of the directories that are required in order to run SAP NetWeaver.
resources: - name: sap_nw type: https://storage.googleapis.com/cloudsapdeploy/deploymentmanager/latest/dm-templates/sap_nw/sap_nw.py # # By default, this configuration file uses the latest release of the deployment # scripts for SAP on Google Cloud. To fix your deployments to a specific release # of the scripts, comment out the type property above and uncomment the type property below. # # type: https://storage.googleapis.com/cloudsapdeploy/deploymentmanager/202103310846/dm-templates/sap_nw/sap_nw.py properties: instanceName: ex-vm-nw-lin instanceType: n1-standard-16 zone: us-central1-f subnetwork: example-sub-network-sap linuxImage: family/sles-12-sp2-sap linuxImageProject: suse-sap-cloud usrsapSize: 15 sapmntSize: 15 swapSize: 24
Create the VM instance:
gcloud deployment-manager deployments create [DEPLOYMENT_NAME] --config [TEMPLATE_NAME].yaml
[DEPLOYMENT_NAME]represents the name of your deployment.
[TEMPLATE_NAME]represents the name of your
The preceding command invokes the Deployment Manager, which deploys the VM according to the specifications in your
template.yamlfile. The process may take a few minutes. To check the progress of your deployment, follow the steps in the next section.
After the VM instance deploys, if you need Compute Engine to save the boot disk in the event the VM instance is deleted:
In the Cloud Console, go to the VM Instances page.
To open the VM instance details page for your VM instance, click the name of the VM instance.
Under Boot disk and local disks, clear the Delete boot disk when instance is deleted checkbox.
The following steps use Cloud Logging, which might incur charges. For more information, see Cloud Logging pricing.
Open Cloud Logging to check for errors and monitor the progress of the installation.
On the Resources tab, select Global as your logging resource. If
INSTANCE DEPLOYMENT COMPLETEis displayed for a VM, Deployment Manager processing is complete for the VM.
After the VM instance deploys, connect to your VM by using
Change to the root user.
sudo su -
At the command prompt, enter
df -h. Ensure that you see output similar to the following.
Confirm that the swap directory was created:
cat /proc/meminfo | grep Swap
You see results similar to the following example:
If any of the validation steps show that the installation failed:
- Correct the error.
- On the Deployments page, delete the deployment to clean up the VMs and persistent disks from the failed installation.
- Rerun your deployment.
Connecting to your VM
If you have defined a firewall rule that allows access
22, you can connect to a Linux VM using common SSH tools.
Google Cloud provides two connection methods. You can connect through the
Cloud Console or you can connect from a terminal by using a
To connect by using
ssh directly from your browser in the
Google Cloud Console:
- In the Cloud Console, go to the VM instances page.
In the list of virtual machine instances, click SSH in the row of
the instance that you want to connect to.
gcloud command-line tool manages your SSH keys for you by generating
and applying new project-wide SSH keys when you need them.
Connect to your VM instance:
gcloud compute --project "[VM_GCP_PROJECT]" ssh --zone "[VM_ZONE]" "[VM_NAME]"
[VM_CGP_PROJECT]is the name of the Google Cloud project in which you have created your VM.
[VM_ZONE]is the zone in which you have located your VM.
[VM_NAME]is the name of your VM instance.
After you submit this command, the terminal is connected to your
VM on Google Cloud and you can run commands on your Linux VM. When
you are done, use the
exit command to disconnect from the VM.
You can also generate a new key-pair for your Linux VM and apply it to your project, which allows you to connect using third-party tools such as PuTTY on Windows workstations. For more details, see Creating a new SSH key pair.
Other connection options, which aren't discussed here, are also possible.
For more detailed information about connecting to a Linux VM on Google Cloud, see Connecting to Linux instances.
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:
- SAP HANA guides
- SAP ASE guides
- SAP MaxDB guides
- IBM Db2 guides
- Windows SQL Server guide: when SAP NetWeaver is running on Linux, Windows SQL Server is supported only in 3-tier architectures.
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.
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:
- Download and install the agent:
#sudo curl -s https://storage.googleapis.com/cloudsapdeploy/netweaver-agent/setupagent_linux.sh | sudo bash
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
After you install SAP NetWeaver:
Update the SAP kernel to the minimum supported patch level.
For details on the supported SAP kernel patch levels, see SAP Note 2446441 - Linux on Google Cloud (IaaS): Adaptation of your SAP License.
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:
- SAP Note 2460297 - SAP on Linux on Google Cloud Platform: Enhanced Monitoring.
- To update your SAP Host Agent by default on a regular basis, see SAP Note 1473974 - Using the SAP Host Agent Auto Upgrade Feature.
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:
In the Cloud Console, open Cloud Shell.
Connect to the VM instance you want to monitor. For details on how to connect, see Connecting to your VM.
At the command prompt, enter the following command:
If the monitoring agent is functioning properly, the value for
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
- Cloud Provider:
Google Cloud Platform
- Enhanced Monitoring Access:
- Enhanced Monitoring Details:
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 connecting to your VM
If you are having issues connecting to your VM through
ssh, ensure that you
have created a firewall rule to open port
22 on the Google Cloud network
you are using.
For other possible issues, see Known issues for SSH from the browser.
Troubleshooting Google's monitoring agent
To troubleshoot the monitoring agent, see the Operations guide.