SAP Landscape Virtualization Management (LVM) is an application running on the top of SAP NetWeaver Java stack. SAP NetWeaver Java stack consists of a few different instances – DB Instance, SCS instance, one Primary Application Sever – PAS (Central Instance) and (optional) Additional Application Severs – AAS (Dialog Instances)
Initially LVM 1.0 supported only one J2EE application server, e.g. only Primary Application Sever.
This was a bit limitation for following scenarios:
- High Availability (HA) of LVM – the standard way to achieve SAP application HA of SAP Java NetWeaver (regardless of what applications are running on the top) is to cluster Single Points Of Failures e.g. DBMS and SCS Instance with failover cluster solutions, and to install at least two application servers (e.g. one primary and one additional app. server) on two separate hosts.
HA of SAP systems is always an important topic, but for LVM it is even more important due to the fact that LVM is a central tool for management of SAP systems and landscapes running across different physical and virtual infrastructure.
For more information on SAP NetWeaver HA in physical and virtual environment you can check in this White Paper: SAP NetWeaver High Availability and Business Continuity in Virtual Environments with VMware and Hyper-V on Microsoft Windows
- Scalability of LVM – the best way to solve bottleneck issues for SAP Java NetWeaver applications server is to deploy additional application server(s), so that new load can go to a new java application server.
With the new release LVM 1.0 SP04 this limitation is removed, e.g. you can install multiple java application server nodes. Check SAP Note 1527538 (“As of LVM 1.0 SP04 Multiple server nodes are supported.”)
Now your LVM can be fully deployed in standardized supported HA settings and you scale up even up to the clouds 🙂