What is SAP Landscape Management (LAMA) SAP Landscape Management ( LaMa ) is a SAP product which helps customers to deploy, manage and automate SAP application landscapes in physical and virtualized data centers and cloud infrastructures. From an administrator's perspective, LaMa is the central tool that communicates with the application and infrastructure (virtualization layer and storage), and therefore the complexity of the underlying infrastructure is hidden from SAP application administrators. In addition to creating SAP system copies, refreshes, and clones, LaMa provides extensive monitoring capabilities and controls for SAP system interaction (start, stop, relocate, and so on)
New capabilities introduced with LaMa 3.0 SP13 cover support of SAP HANA environments Simplified provisioning and management of SAP HANA Multi-Tenant Database Container (MDC) setups Fully automated SAP system refresh procedure for SAP HANA using backup and restore Fully automated procedure to setup and monitor SAP HANA System Replication Fully automated procedure for nZDM Takeover and Failback for SAP HANA Near Zero Downtime ( nZDM ) maintenance for SAP HANA (e.g. facilitating OS updates, SAP HANA upgrades, Hardware maintenance)
SAP HANA Management with LaMa 3.0 LaMa 3.0 introduced many new capabilities focused on management of SAP HANA. A key feature in this area is around SAP HANA High Availability and Disaster Recovery management. Diagrams below illustrate how LaMa can help a Basis Administrator to takeover or failback a HANA based environment
What are the Key Capabilities of LaMa ?
CUSTOMER CHALLENGES
EXAMPLE OF SYSTEM REFRESH USING MANUAL METHOD AND USING LAMA REFRESH METHOD
System Combination details refreshes
Using LaMa system refresh
LaMa – Benefits for System Refresh
LaMa – Benefits of Automated Operation Mass Operations of SAP systems start/stop Customized Unix scripts and integrated in LaMa to suspend & resume High Availability (HA) cluster Production systems recycle time reduced from 45 minutes to less than 10 minutes with Mass Operation Automating the Cloud systems start/stop reduces the cost of maintenance Notification of system maintenance via emails Upto 50% savings could be achieved by running a system 16 hours per day for 20 days per month as opposed to 24 hours per day for 30 days per month. Scheduled Cloud Operations will effectively allows SAP systems to be stopped and their hosting VMs to be deactivated on a time basis thus saving pay-as-you-go hosting costs
SAP Landscape Management with Microsoft Azure To support customers on their journey into a cloud model (hybrid or entirely public cloud), SAP and Microsoft partnered to create an adapter that integrates the SAP management capabilities of LaMa with the IaaS advantages of Microsoft Azure. Many SAP customers are running their applications on Microsoft Azure infrastructure and some are already using LaMa to manage such landscapes. However, they do not get the full infrastructure automation capabilities that Microsoft Azure provides. To make available the powerful infrastructure automation capabilities of Microsoft Azure within LaMa , an adapter was built by Microsoft and is shipped with LaMa . This adapter can be leveraged by the administrator via the LaMa dashboard and allows a real end to end automation covering the entire stack of SAP application and the infrastructure. Before getting into the details of the adapter we will first cover some basics of running SAP applications in Microsoft Azure regardless of using LaMa .
The Microsoft Azure Adapter for LaMa was developed by Microsoft to bring the capabilities of standardized SAP application management to the Microsoft Azure Cloud. All the functionality that is available in LaMa and described earlier in this paper becomes available to be used on SAP landscapes including SAP HANA running in Microsoft Azure. The adapter is built as a Java library and is installed directly into the LaMa application. Once in place, actions that require interaction with the Microsoft Azure infrastructure can now be handled by the adapter by making the necessary Microsoft Azure API calls. For example, an SAP Basis administrator may choose a clone of an SAP system based on Microsoft Azure cloning technology, LaMa will do this via the Adapter. The diagram below conceptually illustrates the solution and what can be accomplished with it.
Microsoft Azure Templated Deployment (Auto Installations) using Teraform Modules, Ansible Playbook, Ansible Roles The Microsoft Azure adapter can deploy a template (existing customer created template in JSON format) that defines the infrastructure and configuration of the Microsoft Azure based SAP landscape. By using a template, you can repeatedly deploy your solution throughout its lifecycle and have confidence your resources are deployed in a consistent state. A customer may have a need to provision and teardown SAP landscapes for training purposes. In this scenario, Microsoft Azure templates would be created (by the customer) from a running environment and then used to deploy additional environments. All the above would be done from the LaMa interface