IBM Cloud Docs
Before you begin deploying

Before you begin deploying

This tutorial walks through necessary steps required to be preformed which enables a user to successfully deploy the architecture.

IAM Permissions

IAM access roles are required to install this deployable architecture and create all the required elements.

You need the following permissions for this deployable architecture:

  1. Create services from IBM Cloud catalog.
  2. Create and modify IBM Cloud VPC services, virtual server instances, networks, network prefixes, storage volumes, SSH keys, and security groups of this VPC.
  3. Create and modify Power® Virtual Server services, virtual server instances, networks, storage volumes, ssh keys of this Power® Virtual Server.
  4. Create and modify IBM Cloud direct links and IBM Cloud Transit Gateway.
  5. Access existing Object Storage services.
  6. The Editor role on the Projects service.
  7. The Editor and Manager role on the Schematics service.
  8. The Viewer role on the resource group for the project.

For information about configuring permissions, contact your IBM Cloud account administrator.

IBM® Power® Virtual Server with VPC landing zone deployable architecture

  1. You must have an existing deployment of IBM® Power® Virtual Server with VPC landing zone deployable architecture. This can be deployed from IBM catalog tile. Instructions are provided here.

Only following variations are supported to proceed with the deployment of SAP Ready PowerVS and SAP S/4HANA or BW/4HANA.

  • Create a new architecture: Standard Variation

  • Extend IBM® Power® Virtual Server with VPC landing zone: Standard Variation

  • Create a new architecture: Import Variation

    If you already have a PowerVS workspace, then you can use the Import PowerVS workspace variation of IBM® Power® Virtual Server with VPC landing zone deployable architecture instead of deploying a new IBM® Power® Virtual Server with VPC landing zone deployable architecture. The 'import' solution creates a schematics workspace by taking pre-existing VPC and PowerVS infrastructure resource details as inputs. The ID of this schematics workspace will be the pre-requisite workspace id required by 'IBM® Power® Virtual Server for SAP HANA' to create and configure the PowerVS instances for SAP on top of the existing infrastructure. Check the pre-requisites for this variation here.

The ID of this schematics workspace will be the pre-requisite workspace id required by 'IBM® Power® Virtual Server for SAP HANA' to create and configure the PowerVS instances for SAP on top of the existing infrastructure.

Check the pre-requisites for this variation here.

Define hostnames

Define hostnames for all the SAP services that you will deploy in the landscape. You will map the hostnames to the IP addresses later after the resources are provisioned. The domain name must be the same for all hostnames that belong to one SAP system.

Determine size parameters

Determine the size parameters for each SAP workload that you plan to deploy. The most important parameters are memory size (especially for SAP HANA) and the number of SAPs. Most of the other configurations can be derived from these two key metrics.

For more information, see Sizing process for SAP Systems and see SAP Sizing.

For deployment of each SAP system, you must be aware about how many SAP NetWeaver instances you plan to deploy. Decide whether you plan to use a separate PowerVS instance for hosting SAP shared files.

For deployment of each SAP NetWeaver PowerVS instance, you must be aware of the following sizing parameters:

  • Memory size
  • Number of CPUs

For deployment of SAP HANA PowerVS instance, you must be aware of the following sizing parameters:

  • SAP t-shirt size as combination of memory and number of CPUs. Check for certified profiles here

SAP software installation packages for the SAP S/4HANA or BW/4HANA variation only

You must have an existing IBM Cloud Object Storage instance.

These steps apply to the SAP S/4HANA or BW/4HANA variation only.

  1. Within the instance, an Object Storage bucket that contains the SAP Software installation media files is required.
  2. To configure access to these software packages from a running virtual server instance, you need the following information:
    • Object Storage endpoint
    • Object Storage bucket name
    • Object Storage HMAC access key
    • Object Storage HMAC secret access key

Follow the tutorial here which details the steps to create a Cloud Object Storage (COS) instance and organizing the SAP binaries in correct structure.

Learn about deployment input parameters

Ensure that you are familiar with the required input for the deployment execution. See description for input parameters.

Additional background information