Register existing SAP system (preview)

Important

Azure Center for SAP solutions is currently in PREVIEW. See the Azure Center for SAP solutions - Legal Terms for legal notices applicable to Azure Center for SAP solutions.

In this how-to guide, you'll learn how to register an existing SAP system with Azure Center for SAP solutions. After you register an SAP system with Azure Center for SAP solutions, you can use its visualization, management and monitoring capabilities through the Azure portal. For example, you can:

  • View and track the SAP system as an Azure resource, called the Virtual Instance for SAP solutions (VIS).
  • Get recommendations for your SAP infrastructure, based on quality checks that evaluate best practices for SAP on Azure.
  • Get health and status information about your SAP system.
  • Start and Stop SAP application tier.
  • Monitor the Azure infrastructure metrics for the SAP system resources.

Prerequisites

  • Check that you're trying to register a supported SAP system configuration
  • Check that your Azure account has Contributor role access on the subscription or resource groups where you have the SAP system resources.
  • Register the Microsoft.Workloads Resource Provider in the subscription where you have the SAP system.
  • A User-assigned managed identity which has Virtual Machine Contributor role access to the Compute resource group and Reader role access to the Network resource group of the SAP system. Azure Center for SAP solutions service uses this identity to discover your SAP system resources and register the system as a VIS resource.
  • Make sure each virtual machine (VM) in the SAP system is currently running on Azure. These VMs include:
    • The ABAP SAP Central Services (ASCS) Server instance
    • The Application Server instance or instances
    • The Database instance for the SAP system identifier (SID)
  • Make sure the sapstartsrv process is currently running on all the VMs in the SAP system.
    • Command to start up sapstartsrv process on SAP VMs: /usr/sap/hostctrl/exe/hostexecstart -start
  • Grant access to your Azure Storage accounts from the virtual network where the SAP system exists. Use one of these options:
    • Allow outbound internet connectivity for the VMs.
    • Use a Storage service tag to allow connectivity to any Azure storage account from the VMs.
    • Use a Storage service tag with regional scope to allow storage account connectivity to the Azure storage accounts in the same region as the VMs.
    • Allowlist the region-specific IP addresses for Azure Storage.

Supported systems

You can register SAP systems with Azure Center for SAP solutions that run on the following configurations:

  • SAP NetWeaver or ABAP stacks
  • Windows, SUSE and RHEL Linux operating systems
  • HANA, DB2, SQL Server, Oracle, Max DB, and SAP ASE databases

The following SAP system configurations aren't supported in Azure Center for SAP solutions:

  • HANA Large Instance (HLI)
  • Systems with HANA Scale-out configuration
  • Java stack
  • Dual stack (ABAP and Java)
  • Systems distributed across peered virtual networks
  • Systems using IPv6 addresses

Enable resource permissions

When you register an existing SAP system as a VIS, Azure Center for SAP solutions service needs a User-assigned managed identity which has Virtual Machine Contributor role access to the Compute resource groups and Reader role access to the Network resource groups of the SAP system. Before you register an SAP system with Azure Center for SAP solutions, either create a new user-assigned managed identity or update role access for an existing managed identity.

Azure Center for SAP solutions uses this user-assigned managed identity to install VM extensions on the ASCS, Application Server and DB VMs. This step allows Azure Center for SAP solutions to discover the SAP system components, and other SAP system metadata. Azure Center for SAP solutions also needs this user-assigned managed identity to enable SAP system monitoring and management capabilities.

Setup User-assigned managed identity

To provide permissions to the SAP system resources to a user-assigned managed identity:

  1. Create a new user-assigned managed identity if needed or use an existing one.
  2. Assign Virtual Machine Contributor role access to the user-assigned managed identity on the resource group(s) which have the Virtual Machines of the SAP system and Reader role on the resource group(s) which have the Network components on the SAP system resources exist.
  3. Once the permissions are assigned, this managed identity can be used in Azure Center for SAP solutions to register and manage SAP systems.

Register SAP system

To register an existing SAP system in Azure Center for SAP solutions:

  1. Sign in to the Azure portal. Make sure to sign in with an Azure account that has Contributor role access to the subscription or resource groups where the SAP system exists. For more information, see the resource permissions explanation.

  2. Search for and select Azure Center for SAP solutions in the Azure portal's search bar.

  3. On the Azure Center for SAP solutions page, select Register an existing SAP system.

    Screenshot of Azure Center for SAP solutions service overview page in the Azure portal, showing button to register an existing SAP system.

  4. On the Basics tab of the Register existing SAP system page, provide information about the SAP system.

    1. For ASCS virtual machine, select Select ASCS virtual machine and select the ASCS VM resource.

    2. For SID name, enter the SID name.

    3. For SAP product, select the SAP system product from the drop-down menu.

    4. For Environment, select the environment type from the drop-down menu. For example, production or non-production environments.

    5. For Managed identity source, select Use existing user-assigned managed identity option.

    6. For Managed identity name, select a User-assigned managed identity which has Virtual Machine Contributor and Reader role access to the respective resources of this SAP system.

    7. Select Review + register to discover the SAP system and begin the registration process.

      Screenshot of Azure Center for SAP solutions registration page, highlighting mandatory fields to identify the existing SAP system.

    8. On the Review + register pane, make sure your settings are correct. Then, select Register.

  5. Wait for the VIS resource to be created. The VIS name is the same as the SID name. The VIS deployment finishes after all SAP system components are discovered from the ASCS VM that you selected.

You can now review the VIS resource in the Azure portal. The resource page shows the SAP system resources, and information about the system.

If the registration doesn't succeed, see what to do when an SAP system registration fails in Azure Center for SAP solutions.

Fix registration failure

The process of registering an SAP system in Azure Center for SAP solutions might fail for the following reasons:

  • The selected ASCS VM and SID don't match. Make sure to select the correct ASCS VM for the SAP system that you chose, and vice versa.
  • The ASCS instance or VM isn't running. Make sure the instance and VM are in the Running state.
  • The sapstartsrv process isn't running on all the VMs in the SAP system.
    • Command to start up sapstartsrv process on SAP VMs: /usr/sap/hostctrl/exe/hostexecstart -start
  • At least one Application Server and the Database aren't running for the SAP system that you chose. Make sure the Application Servers and Database VMs are in the Running state.
  • The user trying to register the SAP system doesn't have Contributor role permissions. For more information, see the prerequisites for registering an SAP system.
  • The user-assigned managed identity doesn't have Virtual Machine Contributor role access to the Compute resources and Reader role access to the Network resource groups of the SAP system. For more information, see how to enable Azure Center for SAP solutions resource permissions.

There's also a known issue with registering S/4HANA 2021 version SAP systems. You might receive the error message: Failed to discover details from the Db VM. This error happens when the Database identifier is incorrectly configured on the SAP system. One possible cause is that the Application Server profile parameter rsdb/dbid has an incorrect identifier for the HANA Database. To fix the error:

  1. Stop the Application Server instance:

    sapcontrol -nr -function Stop

  2. Stop the ASCS instance:

    sapcontrol -nr -function Stop

  3. Open the Application Server profile.

  4. Add the profile parameter for the HANA Database:

    rsdb/dbid = HanaDbSid

  5. Restart the Application Server instance:

    sapcontrol -nr -function Start

  6. Restart the ASCS instance:

    sapcontrol -nr -function Start

  7. Delete the VIS resource whose registration failed.

  8. Register the SAP system again.

If your registration fails:

  1. Review the previous list of possible reasons for failure. Follow any steps to fix the issue.
  2. Review any error messages in the Azure portal. Follow any recommended actions.
  3. Delete the VIS resource from the failed registration. The VIS has the same name as the SID that you tried to register.
  4. Retry the registration process again.

Next steps