Make SUSE Linux Enterprise Server Ready for SAP Workloads
- WHAT?
A straightforward way to convert an existing SUSE Linux Enterprise Server system to a SUSE Linux Enterprise Server for SAP applications installation using a dedicated shell script.
- WHY?
To simplify the process of moving from a standard SUSE Linux Enterprise Server system to a fully functioning SUSE Linux Enterprise Server for SAP applications installation.
- EFFORT
15 minutes of reading time.
- GOAL
Understand how to convert a SUSE Linux Enterprise Server system to SUSE Linux Enterprise Server for SAP applications.
- REQUIREMENTS
A SUSE Linux Enterprise Server 16 system designated for running SAP workloads
A registered SUSE Linux Enterprise Server 16
A registration code for SLES for SAP
1 Converting a SLES system to SLES for SAP #
SUSE Linux Enterprise Server ships with a dedicated script that simplifies the process of converting a SLES system to SUSE Linux Enterprise Server for SAP applications.
To convert an installation of SUSE Linux Enterprise Server to an installation of SLES for SAP, use the script Migrate_SLES_to_SLES-for-SAP.sh. The script registers the system correctly and subscribes it to the appropriate repositories.
Make sure that you have an e-mail address for registration and a registration code for SLES for SAP.
Install the package migrate-sles-to-sles4sap.
Run the following command:
#Migrate_SLES_to_SLES-for-SAP.shWhen asked to confirm to continue the migration, press Y, then Enter.
When asked, type the e-mail address to use for registration, then press Enter.
When asked, type the registration key, then press Enter.
Wait until the script is finished. Afterward, you are subscribed to the SUSE Linux Enterprise Server for SAP applications software repositories, and the package SLES-release is removed in favor of SLES_SAP-release.
The script does not install all packages that are included with a default SLES for SAP installation. However, you can install these yourself manually. To install the default package selection, use:
#zypper in patterns-server-enterprise-sap_server
On public cloud instances (pay-as-you-go instances in particular), billing depends on internal mechanisms to identify the entitlement and to calculate the actual consumption. This makes the migration script ineffective, as it only performs migration of repositories inside the operating system.
To perform migration, you must follow image migration guidelines with your cloud solution provider.
2 Legal Notice #
Copyright© 2006–2025 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.