SAP Partner Integrations with SAP Landscape Management

SAP Landscape Management provides three main integration points for SAP partner technologies:

Virtualization and Cloud

Allows the integration of LaMa into a Cloud or Virtualization management infrastructure. This gives LaMa the visibility and access to the underlying infrastructure and the ability to manage, migrate, visualize and perform VM-based clones.

Storage

LaMa can be integrated into shared/centralized storage management infrastructure so that adaptively installed SAP systems can be relocated and be able to perform storage-based clones. Note that storage-based clone refers to the use of the storage subsystem technology capabilities to perform storage level replication and/or snapshots.

LaMa also offers custom clone/provisioning function to easily integrate customer scripts that can perform the data replication step within the LaMa End-to-End process. This can be leveraged where an integration is not currently provided for example a storage system that is not listed on this page or the use of backup/restore infrastructure.

Management/Orchestration (“External Interfaces”)

Other generic higher-level Management/Orchestration tools can be integrated such that they trigger LaMa to perform operations against SAP landscapes.

Below is a high-level summary of what SAP Partners are supporting with SAP Landscape Management. For the official, detailed documentation of these SAP Partner integrations, please see the sections below and follow the links.

Cloud

Microsoft Azure

Further/detailed information:


Amazon AWS

Further/detailed information:

  • There are two adapters, one virtualization adapter and one storage adapter
  • SAP Notes 2251474 and 1861561

Virtualization

VMware vSphere

    IBM PowerVM

      Storage

      Dell EMC 

      Hitachi/HDS

      Further/detailed information:

      • Hitachi VSP, HUS-VM and AMS/HUS storage
      • P2P, P2V, V2P and V2V operations
      • SAP SCN Page: Hitachi / HDS
      • Supported OS’s
        • AIX [supported on a per project basis]
        • RHEL (Physical and VMware) [supported on a per project basis]
        • SLES (Physical and VMware) [supported on a per project basis]
        • Windows (Physical and Hyper-V) [supported on a per project basis]

      HPE

      IBM

      NetApp (NFS)

      Further/detailed information:

      NetApp (SAN/iSCSI)

      Further/detailed information:

      NetApp (SAN/Fiber Channel)

      Further/detailed information:

      Management/Orchestration (“External Interfaces”)

      HPE (Operations Orchestration (OO) integration for SAP Landscape Management)

      Miscellaneous

      OpenStack

      SUSE

      Glossary

      P2P = Physical-to-Physical
      P2V = Physical-to-Virtual
      V2P = Virtual-to-Physical
      V2V = Virtual-to-Virtual (i.e. relocate from VM to another VM, not the same as “migrate”)