LaMa 3.0 SP15 released today!
Despite the COVID-19 pandemic crisis, we’re keeping our commitment to you and delivering our latest feature pack SP15 for SAP Landscape Management 3.0 (LaMa).
You can find the new features listed in the table below.
New Features in SP15
|REST Application Programming Interface||New REST API methods are now available to retrieve and modify HTTP proxies, networks, characteristics, provider definitions, custom operations, and custom hooks. And to retrieve provisioning blueprints, operation templates, and custom processes. For more information, see the Developer Guide.|
|SAP HANA Client Update||You can now execute an SAP HANA process to update an SAP HANA client that is either located on an application server or on a central instance, connected with an SAP HANA database. After the update, the application server or central instance is started again with the updated client component in place.|
|Activate Virtual Tenant Addresses||You can now execute an SAP HANA process to activate the virtual tenant IP address of the SAP HANA node in the potential nameserver candidates.|
|Refresh a Database Using Third-Party Backup Tools with Backint for SAP HANA||You can now perform a restore based refresh on a system with SAP HANA databases and therefore use backup data that has been written to an SAP-certified third-party tool that supports the Backint for SAP HANA interface.|
|AWS Nitro Support||You can now use Nitro-based instances for performing operations or system provisioning scenarios on Amazon Web Services (AWS).|
|Create an Activity per Entity When Executing a Custom Processes as Mass Operation||You can now choose to create an activity per entity when executing a custom process as mass operation.|
|Custom Property Filter||You can now filter custom properties on the Operations > Systems screen.|
|Manage Favorite Views||You can now manage your favorite views for the following screens:
|Invisible Takeover Support||You can now choose to either force the application server to quiesce the connection to the databases or if configured perform an invisible takeover when executing the SAP HANA processes Near Zero Downtime Maintenance on Primary Tier, Near Zero Downtime SAP HANA Update on Primary Tier, Near Zero Downtime Takeover, or Failback for SAP HANA System Replication. An invisible takeover ensures that the client reconnects to the primary system and the sessions are restored to the secondary system.|
|Define Maintenance Timestamp||You can now define a timestamp at which your maintenance tasks are finished before executing the SAP HANA processes Near Zero Downtime Maintenance on Primary Tier or Near Zero Downtime SAP HANA Update on Primary Tier. With that you ensure that the process waits for the specified date and time in the stated time zone before executing subsequent steps. If you’ve also defined a timeout, you can ensure that SAP Landscape Management doesn’t execute subsequent steps after the specified timeout.|