This is an updated version of the former http://scn.sap.com/docs/DOC-34907 FAQ
What is SAP Landscape Management (LaMa)?
- SAP Landscape Management is the new name we use beginning with version 3.0 of the product. The “virtualization” part of the name was misleading to some customers and we decided to remove it . This also required a change of the abbreviation which is now LaMa.
What is SAP Landscape Virtualization Management (LVM)?
- SAP Landscape Virtualization Management software is a management tool that enables the SAP basis administrator to automate SAP system operations including end-to-end SAP system copy/refresh operations
- The software is shipped as an add-on to SAP NetWeaver 7.3 (Application Server Java) and is available in two additions: Standard Edition and Enterprise Edition.
- The last version of LVM is 2.1, beginning with version 3.0 the product is called SAP LaMa.
I would like to take a look at the Product, are there any demos available ?
- Yes, there are several demo videos available on the SAP Technology youtube channel
- SAP LVM – YouTube
- SAP LaMa 3.0 – YouTube
- SAP CAL trial System. With SAP CAL you are able to deploy a running SAP LaMa into AWS (Amazon Web Services) and try out SAP LaMa for 30 days.The System comes pre-configured and with several test scenarios.
You do need an AWS account and will be charged for the runtime of the System.
Go to http://cal.sap.com and look for the SAP Landscape Management Enterprise Edition (trial edition)
Is LaMa a licensed product? If yes, how does the licensing model work?
- Yes, SAP Landscape Virtualization Management software is a licensed product and the product is available in two editions: Standard edition and Enterprise edition.
- Standard edition is available to all SAP customers with at least one active SAP application license and has no license cost associated with it. The customer will have to obtain a license for Standard Edition but, do not have to incur any additional cost..
- Enterprise edition is available to all SAP customers as a separately licensed product. Please contact your SAP Account Executive or Sales Representative for further details.
What is the value proposition of LaMa and what are the business benefits ?
With SAP Landscape Management software (LaMa), you can simplify and automate the management and operations of your SAP systems running on traditional, virtual or cloud infrastructures.
- Greater operational continuity through centralized management, visibility and control of your entire SAP landscape using a single console.
- Reduced time, effort and cost to manage and operate your SAP systems through automation of time-consuming basis administration tasks.
- Increased operational agility through acceleration of application lifecycle management operations and fast response to workload fluctuations.
I would like to convince my senior management of SAP LaMa, can you help me ?
- Yes. We can support you with arguments and help on calculating things like an ROI (Return on Investment). Please contact michael.jilgATsap.com for EMEA and jens.rolkeATsap.com for the Americas.
I am an existing SAP NetWeaver Adaptive Computing Controller (ACC) customer, how will I be supported in the future and how can I make the switch to LVM?
- ACC customers can continue to use the product and will be supported as part of their ongoing SAP NetWeaver support. However, we strongly recommend switching to SAP Landscape Virtualization Management (LVM) as it has taken over and continue all use cases from ACC.
- Switching from ACC to LVM is really simple and straightforward. All you have to do is export your existing ACC system configuration using export/import functionality in ACC and import it back into the LVM system using the same export/import feature available in LVM. As a best practice, SAP recommends installing a fresh LVM system and migrating the configuration from ACC to the new LVM system as explained above.
When will the next version of LaMa be released ?
- LaMa 3.0 is GA since March 6th 2017
- LVM 2.1 is GA since Feb. 2, 2015
- For upcoming releases, please refer to our Roadmap presentation.
Are there any prerequisites for using LaMa ?
- Yes, there are certain prerequisites for using LaMa as it consists of several software components.
- The LaMa software itself is shipped as an add-on to SAP NetWeaver (Application Server Java) and the minimum requirement is SAP NetWeaver 7.50 SP04 or higher (Application Server Java – “basic” usage type). Please check SAP Note 1527538 for further details.
- Depending on the product edition that you are using (i.e. standard or enterprise edition) and the product functionality that you would like to use, there are certain additional components required.
- The minimum dependency for managed systems is the SAP Host Agent, which must be running on each managed host (both SAP as well as non-SAP systems require SAP Host Agent for them to be managed via LaMa).
The SAP Host Agent FAQ can be found here: FAQ
The SAP Host Agent Troubleshooting Guide: Troubleshooting guide
It is possible to use x509 certificates for authentication to the Host Agent: SSO
Blog Post on how to setup the certificates from Benny Märcz: Blog
Click to enlarge
For further information on virtualization, storage or other infrastructure dependencies, please check the collective SAP Note 1527538.
You can find an overview of current Partner integrations with LVM 1.0 here.
You can find an overview of current Partner integrations with LVM 2.x here.
If your Infrastructure is not listed in the SAP Note 1527538, please contact email@example.com for help.
There is a best practices guide available for system provisioning including an adaptive setup here.
How do i install SAP LaMa ?
You can find an installation overview here.
Are there any best practices recommendations for the Landscape setup?
System provisioning: There is a best practices guide available for system provisioning here.
Adaptive setup: We highly recommend to install your systems following the Adaptive Design concept. An overview of this Design concept is available here.
High availability:For a highly available setup we recommend to setup two independent instances of SAP LaMa. Both instances can point to the same systems without problems. To replicate the configuration, please use the export/import functionality of SAP LaMa (under the setup tab, export/import tab export the config on a regular basis and then import it back to the second instance) on a regular basis.
We recommend to disable all validations (setup tabvalidations/general/switch validation on) and the monitoring
(NWadmin/Java scheduler/tasks LVM_Job_Monitoring to hold) at the secondary site to reduce the resulting network traffic.
With LaMa 3.0 this process can be automated
How do i size my LaMa installation/Is there a sizing Guide for LaMa ?
We have released a sizing guide for LaMa here.
You can find it at the Service Marketplace alias Sizing -> Sizing Guidelines -> SAP NetWeaver Landscape Virtualization Management
What key functionality does LaMa standard edition offer?
- Mass operations
- Task planner
- AS (un-)installation
- Basic dashboards
- Virtualization integration
- Inter-system dependencies
- Extensibility (custom operations/hooks/services)
- Fine granular access control
What key functionality does LaMa enterprise edition offer?
- All features in LaMa standard edition, plus the following:
- Advanced Dashboards
- Performance monitoring
- System clone / copy / refresh
- Automatic capacity management
- Landscape visualization
- SAP HANA procedures like takeover
For further details, please refer to slide 50 of the Roadmap presentation.
What is the relationship between SAP Solution Manager and LaMa? Are there any dependancies between these two products?
- SAP Solution Manager addresses Application Lifecycle Management for SAP systems (ALM). SAP Landscape Management software enables running SAP systems on virtualized and cloud infrastructures and addresses infrastructure layer complexities. In addition, SAP Landscape Management provides additional capabilities such as a framework for automated system copy/refresh and automatic capacity management which deal with the complexities of both the infrastructure and the applications through a single tool.
Can I run LaMa as an add-on to the SAP Solution Manager Java instance ?
- No, this is not possible. LaMa runs as an add-on on top of SAP NetWeaver 7.5 (Application Server Java) and the minimum requirement is SAP NetWeaver 7.50 SP04. Since, the latest release of SAP Solution Manager (i.e. SAP Solution Manager 7.1) runs on an earlier release stack of the Application Server Java Furthermore, even if this technical restriction is resolved in future, we would not recommend running LaMa and SAP Solution Manager instances on the same host as part of best practices. Running both of these systems in the same host may cause performance degradation and moreover, in case of a system performance issue, it would become very difficult to diagnose and troubleshoot the root cause.
Does LaMa integrate with SAP Test Data Migration Server (TDMS) ?
- No, currently there is no standard integration available between LaMa and TDMS. However, TDMS compliments the use case of LaMa and could be used in parallel to LaMa. TDMS offers data extraction of SAP business data and data scrambling which can be executed on SAP system copies that have been produced via LaMa. Currently, we are evaluating various integration scenarios between LaMa and TDMS and if something is available in future, we will update the product roadmap and communicate the same to our customers. We are looking into extending the SAP system copy workflow in LaMa so that TDMS could be triggered as an optional step in one of the future releases of LaMa.
Can I manage and monitor non-SAP Systems with LaMa? If yes, what functionality is provided by LaMa for management of non-SAP systems?
- Yes, LaMa supports the management and monitoring of non-SAP systems and applications and this capability of LaMa is called “custom services”. Technically, any application that can be detected as a service running an operating-system can be detected and managed by LaMa
- LaMa provides the following functionality for non-SAP systems (some examples of typical non-SAP systems would be middleware systems like Tibco/Biztalk, non-SAP data warehousing solutions etc.):.
- Performing basic monitoring and management of non-SAP systems such as, starting or stopping a system, collecting basic monitoring data such as CPU usage, memory usage, running state etc.).
- Performing mass-operations on non-SAP systems such as, mass-start or mass-stop).
- Configure Inter-System Dependencies (ISD) between SAP and non-SAPsystems:
Does LaMa support management of SAP Sybase based systems?
- Yes. It is possible to manage SAP Sybase ASE based systems with LVM 1.0 SP5 onwards – including SAP System Copy operations. This requires the latest version of System rename. (system rename SP02 part of SAP SL Toolset)
Does LaMa support management of SAP HANA based systems?
- Yes. It is possible to perform the basic operations (start/stop/monitor) for SAP HANA systems with LVM 1.0 SP04 onwards.
- System copy/provisioning is available since LVM version 2.1
- LaMa 3.0 support a wide range of additional functionality for SAP HANA based systems
What are the steps that are automated by the Post Copy Automation functionality ?
- Initial Consistency Check
- Check for BW system
- ALE Configuration
- ALE Customizing
- Batch Jobs Configuration
- Batch Server Groups
- CCMS Configuration
- CCMS History
- Customer defined Tables
- DBACOCKPIT Configuration
- Operating System Commands
- Cross-Client File Names/Paths
- Logon Groups
- Operation Modes
- Printer Config / Spool Cleanup
- System Profiles
- RFC Connections
- Inbound qRFC
- SLD Data Supplier Configuration
- SCOT Configuration
- SICF Configuration
- SLD Access Data Configuration
- Update Program Server Groups
- STRUST Configuration
- Last Transport Request Number
- TMS QA Configuration
- Users (all, selected clients, exclude)
- Development Versions
- Virus Scan Definitions
- Web Service Configuration
Initial System Copy:
- Cleanup of ABAP Basis Tables
- Cleanup of Batch Jobs
- Cleanup of DBA Cockpit Configuration
- Cleanup of RFC In / Outbound Queue
- Cleanup of SAPConnect
- Cleanup of Spool Requests
- Cleanup of TRUST Manager Config
- Configuration of Standard Jobs
- Scheduling in DBA Planning Calendar
- Configuration of MSSQL
- Configuration of Licenses
- Configuration of Logon Groups
- Configuration of System Profiles
- Configuration of Operation Modes
- Configuration of Secure Store
- Configuration of Spool, TMS
- Schedule of job RDDIMPDP
You can check out the details in your ABAP system by opening the Task List editor and browsing through the system copy / refresh lists, once your system is on the minimum SP level (see note).
For Java Systems: System Refresh:
- RFC destinations
- Security configuration (SSL key store, ticket key store)
- User management handling
Initial System Copy:
- RFC destinations
- Security configuration (SSL key store, ticket key store)
- TREX property setting
- SLD configuration (SLD CIM client, SLD HTTP configuration)
- System Rename for SAP – https://service.sap.com/sap/support/notes/1619720
- Post Copy Automation – https://service.sap.com/sap/support/notes/1614266
- SAP System Copy approach – https://service.sap.com/sap/support/notes/1767253
Where can i find more information on the Post-Copy Automation for ABAP ?
My BDLS (logical system name conversion) takes forever can you help me ?
- Yes. Even though we use the SAP standard BDLS functionality we have optimized it in several ways.
As you probably are aware, the normal BDLS is a single task, which means everything is sequential.
With the LaMa PCA task list, we enable parallel processing with up to 26 tasks, which already speeds up things
significantly. In addition it is possible to convert multiple logical system names in one run.
The second major point is, that the standard BDLS goes through every table, independently if a conversion is needed or not.
We address this with a a preparation task. This task runs before the copy and actual conversion, scans all
the tables and creates a list of the tables that actually need a conversion. This list is then read after the copy
and only those tables that really need a conversion are being processed.
These features of the LaMa ABAP Post-Copy Automation lead to significantly reduced runtimes.
Is it possible to manage or copy MCOD (multiple components in one database) with LaMa
- Yes, with some restrictions. For details please refer to SAP note 1942083
Which stacks are supported by LaMa for End-to-End automated system clone/copy/refresh (including System Rename and PCA) ?
|End-to-End Clone||End-to-End Copy||End-to-End Refresh|
|Java Stack||Yes||Yes||Yes (workaround with manual steps available, see sectionJava System Refresh Workaround below)|
|Dual-Stack||Yes||No (see section Notes on Dual-Stack below)||No (see section Notes on Dual-Stack below)|
Java System Refresh Workaround
User & passwords need to be manually exported and imported – for more information, see SAP Note 1807150
Notes on Dual-Stack
Mandatory dual-stack systems (such as SAP Process Integration or SAP Solution Manager) are not supported by system copy/refresh of SAP Landscape Virtualization Management today.
For optional dual-stack systems (such as SAP Business Warehouse systems with BI Java), see the following best practice to use SAP Landscape Virtualization Management for copying or refreshing them:
· General recommendation: use the dual-stack split procedure to change the layout of your
optional dual-stack systems to single stack
· SAP communicated to discontinue optional dual-stack systems with higher releases than SAP
NetWeaver 7.31 and SAP Business Suite 7i2011. As a result, by splitting your optional dual-
stack systems, you are prepared for future updates/upgrades to releases that do no longer
support optional dual-stack (such as to SAP NetWeaver 7.40). You profit from the benefits that
single stack deployments offer, such as higher flexibility, availability and scalability. Customer
feedback shows that the dual-stack split procedure is easy, fast and reliable. For more
information, see the dual-stack page in SAP Community Network at:
· After the split, you can profit from all the benefits SAP Landscape Virtualization Management is
offering in the area of system copy and system refresh, as outlined in SAP Note 1527538.
· Reasonable alternative: un-install and re-install the Java stack of dual-stack SAP BW systems
· If you are using the Java stack of a dual-stack SAP BW system for BI Java only, it might be a
reasonable procedure to un-install the Java stack and perform a new installation of a stand-
alone BI Java system from scratch. For more information, see the SAP BW landing page in
SAP Community Network at: http://scn.sap.com/docs/DOC-785 .
· After the un-installation, you can profit from all the benefits SAP Landscape Virtualization
Management is offering in the area of system copy and system refresh, as outlined in SAP
· Possible exception: stay with dual-stack systems
· If you decide to keep the dual-stack layout for your optional dual-stack systems, you cannot
profit from the benefits SAP Landscape Virtualization Management is offering in the area of
system copy and system refresh as of today.
What about post-copy automation for AS Java systems?
For details, see the document FAQ – Java Post-Copy Automation.
Where can I get further information?
- Product Page : http://go.sap.com/product/technology-platform/landscape-management.html
- Central SAP Note: LaMa 3.0 2350235 LVM 1.0 1527538 LVM 2.1 1973341
- LVM 1.0 Application Help: http://help.sap.com/nwlvm10ent (This product is out of maintenance)
- LVM 2.0 Application Help: http://help.sap.com/lvment20 (This product is out of maintenance)
- LVM 2.1 Application Help: http://help.sap.com/lvment21
- LaMa 3.0 Application Help: http://help.sap.com/nwlvm
- LVM Roadmap