2. • Since we started this series of presentations, SAP have renamed
their Landscape Virtualization Manager (LaMa) product to
purely Landscape Management (LaMa) to avoid some
confusion
• This is the fifth presentation in our series dedicated to SAP
Landscape Management(LaMa)
• SAP LaMa Cloud Managers allow customers to integrate their
public cloud operations into SAPLaMa
• This document provides a quick overview of how you can
integrate the Deactivate/Active of Microsoft Azure virtual
machines hosting SAP systems with the Microsoft Azure
Connector for SAPLaMa
Introduction
3. Overview
• As of Q2/2018, SAP LaMa Cloud Managers support the following
public cloud platforms
– Microsoft Azure
– Amazon Web Services
• The MicrosoftAzure Connectorprovides the following scenarios
– Activate
– Deactivate (Power Off)
– SAP System Relocate
– SAP System Copy & Clone
– SAP System Refresh
• The setup described in this document is based on SAP LaMa 3.0 SP06
on SAP NetWeaver7.50 SP10
4. Drivers
• Monitoring hosting costs in public cloud environments is of
paramount importance otherwise some of the perceived
benefitswill not be realised
• The ability to deactivate virtual machines during periods of
system inactivity (e.g. weekends or overnight) coupled with an
activationwhen the system is required,becomes important
• To seamlessly integrate this deactivation/activation with the
stop/startof the hosted SAPsystem and database is crucial
• Up to 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
5. Pre-‐Requisites
• Some of the necessary configuration for the setup are taken
from SAP note “2343511 Microsoft Azure connector for SAP
Landscape Management(LaMa)”
• The use of Cloud Managers in SAP LaMa requires the
installation of the SAP Adaptive Extension 1.0 with patch level
39 or above
• An Azure Service Principle with sufficient level of access to the
virtual machines in the Azure Resource Group must be defined
in advance of the configuration in SAPLaMa
• Any firewall must be open to allow HTTPS access to
management.azure.comon port 443
6. Cloud
Manager
for
Azure
• Cloud connections are created in the Infrastructure è Cloud
Manager section within SAPLaMa
• Key fields for the Azure Cloud Manager configuration are Name,
Password,Subscription and AD Identity
• The Name and Password fields equate to the Service Principal
and Key
• Details of the Service Principal should be safe-‐guardedcarefully
7. Manual
Cloud
Operations
• Once the configuration has been completed cloud operations can be
performed within the Cloud tab from the Operations menu
• The Azure Service Principal is displayed with a summary of the resources in
from the resource groups it can access
8. Manual
Cloud
Operations
• Navigating to the Service Principal expands the available resource groups
shown under OS RESOURCE POOLS
• Selecting a resource group will further drill into the virtual machines
9. Manual
Cloud
Operations
• A listed virtual machine can be shutdown and deactivated in Azure by choosing
OperationsèDeativate (Power off)
• Monitor the progress of the operation by navigating to the Logs in the usual way
10. Scheduled
Cloud
Operations
• Since SAP LaMa 3.0 SP06 cloud operations can now be
scheduledin the LaMa scheduler
• This is a very interesting innovation which effectively allows SAP
systems to be stopped and their hosting VM(s) to be
deactivated on a time basis – thus saving pay-‐as-‐you-‐go hosting
costs
• Start by creatingtwo OperationTemplates:
– one to stop the SAP system and deactivate the VM
– one to activate the VM and start the SAP system
• Then include the two Operation Templates in the SAP LaMa
schedule
11. Reference
Material
• The
following
pages
on
SAP
Help
are
useful:
– SAP
Landscape
Management
3.0
– Configuring
Cloud
Managers
• The
following
SAP
notes
provide
some
information:
– 2343511
Microsoft
Azure
connector
for
SAP
Landscape
Management
(LaMa)”
• Further
details
are
available
on
request
from
our
SAP
LaMa
Certified
Consultants
– mailto:info@aliterconsulting.co.uk