Applies to SUSE Linux Enterprise Server for SAP Applications 15 SP1

1 What Is SUSE Linux Enterprise Server for SAP Applications? #

SUSE® Linux Enterprise Server for SAP Applications is a bundle of software and services that addresses the specific needs of SAP users. It is the only operating system that is optimized for all SAP software solutions.

Target use cases include:

Unix to Linux migrations and replatforming
SAP appliances
SAP cloud deployments

SUSE Linux Enterprise Server for SAP Applications consists of software components and service offerings which are described in the following sections. The figure Offerings of SUSE Linux Enterprise Server for SAP Applications shows an overview of which software components and services are also available with other products from SUSE (green) and which are exclusively available with SUSE Linux Enterprise Server for SAP Applications (blue).

Figure 1.1: Offerings of SUSE Linux Enterprise Server for SAP Applications #

1.1 Software Components #

As depicted in Figure 1.1, “Offerings of SUSE Linux Enterprise Server for SAP Applications”, SUSE Linux Enterprise Server for SAP Applications is based on SUSE Linux Enterprise Server but contains several additional software components such as SUSE Linux Enterprise High Availability Extension, and the installation workflow. These software components are briefly explained in the following sections.

1.1.1 SUSE Linux Enterprise Server #

The current release is based on SUSE Linux Enterprise Server 15 SP1. SUSE Linux Enterprise Server is the most interoperable platform for mission-critical computing, both physical and virtual.

1.1.2 SUSE Linux Enterprise High Availability Extension #

This component consists of:

Flexible, policy-driven clustering
Cluster-aware file system and volume management
Continuous data replication
Setup and installation
Management and administration tools
Resource agents, also for SAP
Virtualization-aware

SUSE Linux Enterprise High Availability Extension provides two resource agents specifically for working with SAP applications:

SAPInstance which allows starting and stopping instances of SAP products.
SAPDatabase which allows starting and stopping all databases supported by SAP applications (SAP HANA, SAP MaxDB, SAP ASE, Oracle, Sybase, IBM DB2).

For more information about SUSE Linux Enterprise High Availability Extension, see the Administration Guide (https://documentation.suse.com/sle-ha-15) and the White Papers and Best Practice Guides in the SUSE Linux Enterprise Server for SAP Applications Resource Library (https://www.suse.com/products/sles-for-sap/resource-library/).

1.1.3 Simplified SAP HANA System Replication Setup #

SUSE Linux Enterprise Server for SAP Applications supports SAP HANA System Replication using components of SUSE Linux Enterprise High Availability Extension and two additional resource agents (RA). Additionally, SUSE Linux Enterprise Server for SAP Applications ships with a YaST wizard that simplifies the cluster setup.

1.1.3.1 `SAPHana` Resource Agent #

This resource agent from SUSE supports scale-up scenarios by checking the SAP HANA database instances for whether a takeover needs to happen. Unlike with the pure SAP solution, takeovers can be automated.

It is configured as a master/slave resource: The master assumes responsibility for the SAP HANA databases running in primary mode, whereas the slave is responsible for instances that are operated in synchronous (secondary) status. In case of a takeover, the secondary (slave resource instance) can automatically be promoted to become the new primary (master resource instance).

This resource agent supports system replication for the following scale-up scenarios:

Performance-Optimized Scenario. Two servers (A and B) in the same SUSE Linux Enterprise High Availability Extension cluster, one primary (A) and one secondary (B). The SAP HANA instance from the primary server (A) is replicated synchronously to the secondary server (B).
Cost-Optimized Scenario. The basic setup of A and B is the same as in the Performance-Optimized Scenario. However, the secondary server (B) is also used for non-productive purposes, such as for an additional SAP HANA database for development or QA. The production database is only kept on permanent memory, such as a hard disk. If a takeover needs to occur, the non-productive server will be stopped before the takeover is processed. The system resources for the productive database are then increased as quickly as possible via an SAP hook call-out script.
Chain/Multi-Tier Scenario. Three servers (A, B, and C), of which two are located in the same SUSE Linux Enterprise High Availability Extension cluster (A and B). The third server (C) is located externally. The SAP HANA system on the primary server (A) is replicated synchronously to the secondary server (B). The secondary server (B) is replicated asynchronously to the external server (C).
If a takeover from A to B occurs, the connection between B and C remains untouched. However, B is not allowed to be the source for two servers (A and C), as this would be a “star” topology, which is not supported with current SAP HANA versions (such as SPS11).
Using SAP HANA commands, you can then manually decide what to do:
- The connection between B and C can be broken, so that B can connect to A.
- If replication to the external site (C) is more important than local system replication, the connection between B and C can be kept.

For all of the scenarios, SUSE Linux Enterprise Server for SAP Applications supports both single-tenant and multi-tenant (MDC) SAP HANA databases. That is, you can use SAP HANA databases that serve multiple SAP applications.

1.1.3.2 `SAPHanaTopology` Resource Agent #

To make configuring the cluster as simple as possible, SUSE has developed the SAPHanaTopology resource agent. This agent runs on all nodes of a SUSE Linux Enterprise High Availability Extension cluster and gathers information about the status and configurations of SAP HANA system replications. It is designed as a normal (stateless) clone.

1.1.3.3 YaST Wizard to Set Up SAP HANA Clusters #

SUSE Linux Enterprise Server for SAP Applications now additionally ships a YaST wizard that manages the initial setup of such clusters according to best practices. The wizard is part of the package yast2-sap-ha and can be started using YaST, via HA Setup for SAP Products.

For more information, see Chapter 7, Setting Up an SAP HANA Cluster.

1.1.3.4 For More Information #

For more information, see:

The Administration Guide at https://documentation.suse.com/sles-15.
The Best Practices in the Resource Library at https://www.suse.com/products/sles-for-sap/resource-library/. In particular, see Setting up a SAP HANA SR performance optimized infrastructure and Setting up a SAP HANA SR cost optimized infrastructure.

1.1.4 Installation Workflow #

The installation workflow offers a guided installation path for both the SUSE Linux Enterprise Server operating system and the SAP application. For more information, see Section 2.5, “Overview of the Installation Workflow”.

Additionally, the installation workflow can be extended by third-party vendors or customers using Supplementary Media. For more information about creating Supplementary Media, see Appendix C, Supplementary Media.

1.1.5 Malware Protection with ClamSAP #

ClamSAP integrates the ClamAV anti-malware toolkit into SAP NetWeaver and SAP Mobile Platform applications to enable cross-platform threat detection. For example, you can use ClamSAP to allow an SAP application to scan for malicious uploads in HTTP uploads.

For more information, see Chapter 13, Protecting Against Malware with ClamSAP.

1.1.6 SAP HANA Security #

SUSE Linux Enterprise Server for SAP Applications contains additional features to help set up well-secured SAP HANA installations.

1.1.6.1 Firewall for SAP HANA #

Securing SAP HANA can require many additional firewall rules. To simplify firewall setups for SAP HANA, SUSE Linux Enterprise Server for SAP Applications contains the package HANA-Firewall which provides preconfigured rules and integrates with firewalld.

For more information, see Section 11.2, “Configuring HANA-Firewall”.

1.1.6.2 Hardening Guide for SAP HANA #

For information on hardening the underlying operating system, see the SUSE Linux Enterprise Server for SAP Applications resource library: https://www.suse.com/products/sles-for-sap/resource-library/. There, find the document OS Security Hardening for SAP HANA.

1.1.7 Simplified Operations Management #

SUSE Linux Enterprise Server for SAP Applications combines several features that enable simplified operations management.

1.1.7.1 System Tuning with `saptune` #

The system tuning application saptune allows you to automatically and comprehensively tune your system as recommended by SAP for use with SAP S/4HANA, SAP NetWeaver, or SAP HANA/SAP BusinessOne. This allow tuning several kernel parameters, depending on the hardware components you are using, such as the amount of available RAM.

For more information, see Chapter 9, Tuning systems with saptune.

1.1.7.2 Storage Encryption for Hosted Applications with `cryptctl` #

Today, databases and similar applications are often hosted on external servers that are serviced by third-party staff. Certain data center maintenance tasks require third-party staff to directly access affected systems. In such cases, privacy requirements necessitate disk encryption.

cryptctl allows encrypting sensitive directories using LUKS and offers the following additional features:

Encryption keys are located on a central server, which can be located on customer premises.
Encrypted partitions are automatically remounted after an unplanned reboot.

For more information, see Chapter 12, Encrypting Directories Using cryptctl.

1.1.7.3 Patterns Providing Dependencies of SAP Applications #

To simplify working with software dependencies of SAP applications, SUSE has created patterns that combine relevant dependency RPM packages for specific applications:

SAP BusinessOne Server Base
SAP HANA Server Base
SAP NetWeaver Server Base

Important: Packages May Be Missing from Patterns

The selection of packages of the software patterns is defined while a specific release (Service Pack or major version) of SUSE Linux Enterprise Server for SAP Applications is developed. This package selection is stable over the lifetime of this particular release. When working with SAP applications that have been released more recently than your SUSE Linux Enterprise Server for SAP Applications version, dependencies can be missing from the patterns.

For definitive information about the dependencies of your SAP application, see the documentation provided to you by SAP.

1.1.7.4 `ClusterTools2` #

ClusterTools2 provides tools that help set up and manage a Corosync/pacemaker cluster. Among them are wow which helps create highly available system resources, and ClusterService which allows managing a cluster.

Additionally, ClusterTools2 provides scripts that automate common cluster tasks:

Scripts that perform checks. For example, to find out whether a system is set up correctly for creating a pacemaker cluster.
Scripts that simplify configuration. For example, to create a Corosync configuration.
Scripts that monitor the system and scripts that show or collect system information. For example, to find known error patterns in log files.

For more information, see the man page of the respective tool, included with the package ClusterTools2.

1.2 Software Repository Setup #

Software included with operating systems based on SUSE Linux Enterprise is delivered as RPM packages, a form of installation package that can have dependencies on other packages. On a server or an installation medium, these packages are stored in software repositories (sometimes also called “channels”).

By default, computers running SUSE Linux Enterprise Server for SAP Applications are set up to receive packages from multiple repositories. Of each of the standard repositories, there is a “Pool” variant that represents the state of the software when it was first shipped. There is also an “Update” variant that includes the newest maintenance updates for the software in the “Pool” variant.

If you registered your system during installation, your repository setup should include the following:

Table 1.1: Standard Repositories #

Content	Base repository (“Pool”)	Update repository
Base packages of SUSE Linux Enterprise Server	`SLE-Module-Basesystem15-SP1-Pool`	`SLE-Module-Basesystem15-SP1-Updates`
Basic server functionality of SUSE Linux Enterprise Server	`SLE-Module-Server-Applications15-SP1-Pool`	`SLE-Module-Server-Applications15-SP1-Updates`
Packages specific to SUSE Linux Enterprise Server for SAP Applications	`SLE-Module-SAP-Applications15-SP1-Pool`	`SLE-Module-SAP-Applications15-SP1-Updates`
Packages specific to SUSE Linux Enterprise High Availability Extension	`SLE-Product-HA15-SP1-Pool`	`SLE-Product-HA15-SP1-Updates`

The tables in this section do not show Debuginfo and Source repositories, which are also set up but disabled by default. The Debuginfo repositories contain packages that can be used for debugging regular packages. The Source repositories contain source code for packages.

Depending on your installation method, you may also see SLE-15-SP1-SAP-15.1-0 which is the installation medium. It contains packages from all of the base software repositories listed above.

Because there are own repositories for SUSE Linux Enterprise Server for SAP Applications, SUSE can ship packages and patches that are specific to SUSE Linux Enterprise Server for SAP Applications.

Note: ESPOS Updates Shipped Directly in Update Repositories

Unlike in SUSE Linux Enterprise Server for SAP Applications 11, updates related to Extended Service Pack Overlay Support (ESPOS) are shipped directly from the Update repositories. This means there is no separate ESPOS repository to set up.

In addition to the standard repositories, you can enable SLE Modules and SLE Extensions either during the installation or from the running system using YaST or the command SUSEConnect.

For information about all modules and extensions available for the SUSE Linux Enterprise product line, see https://documentation.suse.com/sles/15-SP1/html/SLES-all/art-modules.html.

For more information about SUSE Package Hub, see Section A.3, “SUSE Package Hub”.

1.3 Support #

Find the support statement for SUSE Linux Enterprise Server for SAP Applications and general information about technology previews below. For details about the product lifecycle, see https://www.suse.com/lifecycle.

If you are entitled to support, find details on how to collect information for a support ticket at https://documentation.suse.com/sles-15/html/SLES-all/cha-adm-support.html.

1.3.1 Support statement for SUSE Linux Enterprise Server for SAP Applications #

To receive support, you need an appropriate subscription with SUSE. To view the specific support offerings available to you, go to https://www.suse.com/support/ and select your product.

The support levels are defined as follows:

L1: Problem determination, which means technical support designed to provide compatibility information, usage support, ongoing maintenance, information gathering and basic troubleshooting using available documentation.
L2: Problem isolation, which means technical support designed to analyze data, reproduce customer problems, isolate problem area and provide a resolution for problems not resolved by Level 1 or prepare for Level 3.
L3: Problem resolution, which means technical support designed to resolve problems by engaging engineering to resolve product defects which have been identified by Level 2 Support.

For contracted customers and partners, SUSE Linux Enterprise Server for SAP Applications is delivered with L3 support for all packages, except for the following:

Technology previews.
Sound, graphics, fonts, and artwork.
Packages that require an additional customer contract.
Some packages shipped as part of the module Workstation Extension are L2-supported only.
Packages with names ending in -devel (containing header files and similar developer resources) will only be supported together with their main packages.

SUSE will only support the usage of original packages. That is, packages that are unchanged and not recompiled.

1.3.2 Technology previews #

Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses into upcoming innovations. Technology previews are included for your convenience to give you a chance to test new technologies within your environment. We would appreciate your feedback! If you test a technology preview, please contact your SUSE representative and let them know about your experience and use cases. Your input is helpful for future development.

Technology previews have the following limitations:

Technology previews are still in development. Therefore, they may be functionally incomplete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
Details and functionality of technology previews are subject to change. As a result, upgrading to subsequent releases of a technology preview may be impossible and require a fresh installation.
SUSE may discover that a preview does not meet customer or market needs, or does not comply with enterprise standards. Technology previews can be removed from a product at any time. SUSE does not commit to providing a supported version of such technologies in the future.

For an overview of technology previews shipped with your product, see the release notes at https://www.suse.com/releasenotes/x86_64/SLE-SAP/15-SP1/.