SUSE Linux Enterprise Server for SAP Applications 12 SP1

Guide

Publication Date: February 15, 2016
List of Tables
4.1 Media Source Path

Copyright © 2016 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 Trademark and Service Mark list http://www.suse.com/company/legal/. Linux* is a registered trademark of Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark symbol (®, ™ etc.) denotes a SUSE trademark; an asterisk (*) denotes a third party trademark.

All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.

About This Guide

SUSE® Linux Enterprise Server for SAP Applications is the reference platform for the software development of SAP. It is optimized in various ways for SAP applications. This guide provides detailed information about installing and customizing SUSE Linux Enterprise Server for SAP Applications.

SUSE Linux Enterprise High Availability Extension is also part of SUSE Linux Enterprise Server for SAP Applications.

1 Overview

The SUSE Linux Enterprise Server for SAP Applications Guide is divided into the following chapters:

What Is SUSE Linux Enterprise Server for SAP Applications?

An overview of SUSE Linux Enterprise Server for SAP Applications.

Planning the Installation

Information on hardware requirements, the installation workflow, partitioning, and other installation planning aspects.

Installing the Operating System

Installing the SUSE Linux Enterprise Server operating system that forms the basis of SUSE Linux Enterprise Server for SAP Applications.

Installing SAP Applications

Installing SAP applications on SUSE Linux Enterprise Server for SAP Applications, either directly after the installation of the operating system or in a running system.

Setting Up an Installation Server for SAP Media Sets

Setting up a server for all Installation Media used within your organization.

Software Components

Description of tools to configure SUSE Linux Enterprise Server for SAP Applications.

2 Additional Documentation and Resources

Chapters in this manual contain links to additional documentation resources that are either available on the system or on the Internet.

3 Feedback

Several feedback channels are available:

Bugs and Enhancement Requests

For services and support options available for your product, refer to http://www.suse.com/support/.

To report bugs for a product component, go to https://scc.suse.com/support/requests, log in, and select Submit New SR.

User Comments

We want to hear your comments about and suggestions for this manual and the other documentation included with this product. Use the User Comments feature at the bottom of each page in the online documentation or go to http://www.suse.com/doc/feedback.html and enter your comments there.

Mail

For feedback on the documentation of this product, you can also send a mail to doc-team@suse.de. Make sure to include the document title, the product version and the publication date of the documentation. To report errors or suggest enhancements, provide a concise description of the problem and refer to the respective section number and page (or URL).

4 Documentation Conventions

The following typographical conventions are used in this manual:

  • /etc/passwd: directory names and file names

  • placeholder: replace placeholder with the actual value

  • PATH: the environment variable PATH

  • ls, --help: commands, options, and parameters

  • user: users or groups

  • Alt, AltF1: a key to press or a key combination; keys are shown in uppercase as on a keyboard

  • File, File › Save As: menu items, buttons

  • amd64, em64t, ipf This paragraph is only relevant for the architectures amd64, em64t, and ipf. The arrows mark the beginning and the end of the text block.

    System z, ipseries This paragraph is only relevant for the architectures System z and ipseries. The arrows mark the beginning and the end of the text block.

  • Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in another manual.

1 What Is SUSE Linux Enterprise Server for SAP Applications?

Abstract

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).

Offerings of SUSE Linux Enterprise Server for SAP Applications
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, the kernel page-cache limit feature, 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 12 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 SAP instances.

  • 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 on SUSE Linux Enterprise High Availability Extension, see the High Availability Guide (https://www.suse.com/documentation/sle-ha-12/) 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 HA Resource Agents for SAP HANA System Replication

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).

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 in scale-up scenarios:

  • Performance-Optimized Scenario.  Two systems (A and B) in the same SUSE Linux Enterprise High Availability Extension cluster, one primary (A) and one secondary (B). The primary system (A) is replicated synchronously to the secondary system (B).

  • Cost-Optimized Scenario.  The basic setup of A and B is the same as in the Performance-Optimized Scenario. However, the secondary system (B) is also used for non-productive purposes, such as for a development or QA database. The production database is only kept on permanent memory, such as a hard disk. If a takeover needs to occur, the non-productive system will is 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 systems (A, B, and C), of which two are located in the same SUSE Linux Enterprise High Availability Extension cluster (A and B). The third system (C) is located externally. The primary system (A) is replicated synchronously to the secondary system (B). The secondary system (B) is replicated asynchronously to the external system (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 systems (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 system site 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 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 For More Information

For more information, see:

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.4, “Overview of the Installation Workflow”.

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

1.1.5 Page-Cache Limit

You can limit the kernel file system cache size to influence swapping behavior. With this feature, you can often gain better performance by allocating memory to an application. For more information, see Section 6.1, “Kernel: Page-Cache Limit”.

1.1.6 Antivirus Protection with ClamSAP

ClamSAP integrates the ClamAV antivirus 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. ClamSAP can be installed from the package clamsap. To use virus scanning within SAP NetWeaver, you need to enable it there (Transaction › VSCAN).

ClamSAP is a shared library that links between ClamAV and the SAP NetWeaver Virus Scan Interface (NW-VSI) by SAP. The version of ClamSAP shipped with SUSE Linux Enterprise Server for SAP Applications 12 SP1 supports NW-VSI version 2.0.

1.1.7 SAP HANA Security

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

1.1.7.1 Firewall for SAP HANA

SAP HANA often requires more firewall zones than the standard installation of SuSEFirewall2 provides. For this reason, SUSE Linux Enterprise Server for SAP Applications additionally provides the package HANA-Firewall which integrates with SuSEFirewall2. It contains preconfigured zone setups and rules to make securing SAP HANA as simple as possible.

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

1.1.7.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.8 Simplified Operations Management

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

1.1.8.1 ClusterTools2

ClusterTools2 provides tools that help setting up and managing 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 the most common cluster tasks. For more information, see the man page of the respective tool.

1.1.8.2 sapconf

sapconf allows you to automatically and comprehensively tune your system as recommended by SAP for use with SAP NetWeaver or SAP HANA/SAP BusinessOne. To do this, sapconf sets several kernel parameters, often depending on available hardware, such as RAM. For more information, see Section 6.4, “sapconf.

1.1.8.3 Patterns Providing Dependencies of Various 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
Important: Packages May Be Missing from Patterns

The selection of packages of the software patterns are defined as 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 may be missing from the patterns.

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

1.2 Included Services

Extended Service Pack Overlap Support

SUSE Linux Enterprise Server for SAP Applications includes Extended Service Pack Overlap Support which extends the overlap between the support periods of two consecutive service packs by one year. Within this period, you remain under full support and receive all relevant maintenance updates. As a standard offering, this is unique.

Extended Service Pack Overlap Support allows you to perform service pack migrations within 18 months instead of only 6 months. Migrations can be scheduled more easily and testing before a migration can be performed under lesser time constraints.

Additional Update Channel
  • Allows SAP-specific patches

  • Updates for SAP-specific packages

SUSE Linux Enterprise Server Priority Support for SAP Applications

Subscriptions for SUSE Linux Enterprise Server for SAP Applications include SUSE Linux Enterprise Server Priority Support for SAP Applications which offers technical support for SUSE Linux Enterprise Server for SAP Applications directly from SAP. The joint support infrastructure, used by support engineers from SUSE Technical Support and SAP, is based upon SAP Solution Manager and offers a seamless communication with both SAP and SUSE. This One Face to the Customer support model reduces complexity and lowers the total cost of ownership.

2 Planning the Installation

Read this chapter carefully, as it helps you plan the installation: It lists requirements and helps you collect data about your system.

2.1 Hardware Requirements

CPU

AMD64/Intel 64

Hard Disk

At least 35 GB of hard disk space for the system volume plus space for the swap partition and 200 GB for the data partition are required. For more information, see Section 2.6, “Partitioning”.

RAM

The SUSE Linux Enterprise Server operating system itself requires a minimum of 512 MB of RAM. However, any SAP application you install needs additional RAM resources. For more information information, see the Sizing Guidelines from SAP for your application.

2.2 Downloading the Installation Image

  1. Download the DVD ISO image of SUSE® Linux Enterprise Server for SAP Applications 12 SP1 (electronic media kit) from https://www.suse.com/products/sles-for-sap/.

  2. Burn the image onto a physical DVD and ensure that it is bootable. Alternatively, use a virtual DVD-ROM device for installation in a virtual machine.

2.3 Choosing How to Install

There are two ways of installing SUSE Linux Enterprise Server for SAP Applications:

2.4 Overview of the Installation Workflow

The installation workflow of SUSE Linux Enterprise Server for SAP Applications can be separated into steps:

  1. Installation of the operating system (SUSE Linux Enterprise Server). See Section 3.1, “Using the Installation Workflow”.

  2. SAP Installation Wizard, part 1: Copying all required SAP media to the local disk or selecting a shared storage medium to use. See Section 4.2, “Using the SAP Installation Wizard”, in particular Step 1.

  3. SAP Installation Wizard, part 2: Collecting all parameters for the actual installation by querying the user interactively. See Section 4.2, “Using the SAP Installation Wizard”, in particular Step 10.

  4. SAP Installation Wizard, part 3: Running the SAP Installer. See Section 4.2, “Using the SAP Installation Wizard”, in particular Step 12.

Note
Note: Installation of Only SUSE Linux Enterprise Server

You can also choose to only install a base SUSE Linux Enterprise Server system. In that case, only the first step of the installation workflow is executed.

Most of these steps do not need to be run immediately after each other which allows for flexibility in how you install systems. This means that you can prepare a single installation as a first step and then continue from there. For example:

  • Install the operating system (SUSE Linux Enterprise Server) only.

    or

  • Install the operating system (SUSE Linux Enterprise Server), copy SAP media, and collect SAP installation parameters.

Then, create disk images, copy them to other systems, and adjust SAP installation parameters. Finally, finish the installation on each machine individually.

2.5 Required Data for Installing

Operating System

The SUSE Linux Enterprise Server installation requires the following data for every physical server:

  • Network configuration parameters, such as host name, domain, IP address, subnet mask, domain searchlist (DNS), IP for name server, IP for gateway

  • Administrator (root) password for the SUSE Linux Enterprise Server installation

SAP Application

The installation of an SAP application generally requires:

  • SAP SID

  • SAP Instance Number

  • A password for the SAP application

Depending on the SAP application you are installing, more parameters may be necessary, such as T-Shirt Sizing or parameters for virtual networking.

2.6 Partitioning

SUSE Linux Enterprise Server for SAP Applications creates the partitioning table in two stages:

  1. Section 2.6.1, “Partitioning for the Operating System (stage 1)” (during the installation of the operating system)

  2. Section 2.6.2, “Partitioning for the SAP System (stage 2)” (during the installation of the SAP product)

2.6.1 Partitioning for the Operating System (stage 1)

During the installation of the operating system, partitions for the operating system are created.

A logical volume group (LVG) named /dev/system will be created. This LVG contains two logical volumes (LVs):

  • /dev/system/root (by default: 60 GB to account for the operating system and SAP media; even on virtualized installations, this should not be set smaller than 5 GB)

  • /dev/system/swap (by default: 2 GB, avoid setting a smaller size)

Additionally, a boot or UEFI partition will be created as necessary.

2.6.2 Partitioning for the SAP System (stage 2)

The partitioning for the SAP system is done by the SAP Installation Wizard and can only take place after the operating system has been installed. That means the partitions are created either during the installation workflow after the reboot or in the running system.

Depending on the product you are installing and your particular use case, the amount of hard disk space necessary can vary. Consider the following minimal amounts:

  • SAP NetWeaver. At least 80 GB of hard disk space are necessary.

  • SAP HANA. At least 60 GB of hard disk space are necessary.

Partitioning for the SAP system is controlled by the files from the directory /usr/share/YaST2/include/sap-installation-wizard/. Usually, base_partitioning.xml will be used. When installing SAP HANA on certified hardware, other files will be chosen, as defined in /etc/sap-installation-wizard.xml. Here, the content of the element partitioning is decisive.

If the installation is, for example, based on HA or a distributed database, no partitioning is needed. In this case, partitioning is set to NO, the file base_partitioning.xml is used.

The files that control partitioning are AutoYaST control files that contain a partitioning section only. However, these files allow using several extensions to the AutoYaST format:

  • If the partitioning_defined tag is set to true, the partitioning will be performed without any user interaction.

    By default, this is only used when creating SAP HANA file systems on systems certified for SAP HANA (such as from Dell, Fujitsu, HP, IBM, or Lenovo).

  • For every partition, you can specify the size_min tag. The size value can be given as a string in the format of RAM*N. This way you can specify how large the partition should minimally be (N times the size of the available memory (RAM)).

Procedure 2.1: Creating a Custom SAP Partitioning Setup

The steps below illustrates how to create a partitioning setup for TREX. However, creating a partitioning setup for other applications works analogously.

  1. In /usr/share/YaST2/include/sap-installation-wizard/, create a new XML file. Name it TREX_partitioning.xml, for example.

  2. Copy the content of base_partitioning.xml to your new file and adapt the new file to your needs.

  3. Finally, adapt /etc/sap-installation-wizard.xml to include your custom file. In the partitioning for TREX, insert the following line:

    <partitioning>TREX_partitioning</partitioning>
Important
Important: Do Not Edit base_partitioning.xml

Do not edit base_partitioning.xml directly. With the next update, this file will be overridden.

For more information on partitioning with AutoYaST, see AutoYaST Guide, Chapter 4.5 Partitioning (https://www.suse.com/documentation/sles-12/).

3 Installing the Operating System

The following section provides instructions on how to install the base operating system, SUSE Linux Enterprise Server either using the installation workflow, over the network or using AutoYaST.

3.1 Using the Installation Workflow

The installation workflow is a guided installation of the operating system with optimized settings for SAP applications. During the installation workflow, you can choose whether you want to install an SAP application. If so, you will be asked to provide SAP installation media when the SUSE Linux Enterprise Server installation is finished. You can also choose whether to install third-party extensions.

For more information, see Section 2.4, “Overview of the Installation Workflow”.

This section will guide you through the installation of the SUSE Linux Enterprise Server for SAP Applications operating system.

Procedure 3.1: Starting the OS Installation
  1. Boot from the DVD. From the DVD boot menu, select Installation.

    DVD Boot Menu
    Figure 3.1: DVD Boot Menu

    While the initial operating system is starting, you can view boot messages by pressing Esc. When this process has completed, the graphical installation workflow will start.

  2. Select the default system language under Language.

    Language, Keyboard and License Agreement
    Figure 3.2: Language, Keyboard and License Agreement
  3. Select a fitting keyboard layout Keyboard Layout. To test whether the selected layout matches your physical keyboard, use the text box Keyboard Test.

  4. Read the license agreement. If you agree, select I Agree to the License Terms. Proceed with Next.

    Otherwise, cancel the installation with Abort › Abort Installation.

  5. If automatic network configuration via DHCP fails, the screen Network Settings will open automatically.

    If instead the screen Registration appears, your network connection works. To change network settings anyway, click Network Configuration.

    When you are finished configuring networking, proceed with Next.

    Important
    Important: Configure Networking as Recommended by SAP

    Make sure to configure the network connection as recommended in the documentation provided to you by SAP.

    For details regarding network configuration, see Administration Guide, Chapter 19 Basic Networking, Section 19.4 Configuring a Network Connection with YaST (https://www.suse.com/documentation/sles-12/).

  6. On the screen Registration, enter your E-Mail Address and Registration Code. Successful registration is a prerequisite for receiving product updates and being entitled to technical support.

    Proceed with Next.

    Important
    Important: Register at This Step

    Make sure to register your system at this step in the installation. Otherwise, you will not receive vital package updates immediately.

    Additionally, your system will also not be set up to receive packages from the SUSE Linux Enterprise High Availability Extension repository. This is important if you want to install a highly available SAP product.

    Registration
    Figure 3.3: Registration
    Note
    Note: Release Notes

    From this point on, the Release Notes can be viewed from any screen during the installation process by selecting Release Notes.

  7. When asked whether to enable update repositories, choose Yes.

  8. On the screen, Extension and Module Selection, you can optionally choose additional SLE extensions and modules. The list contains free modules, such as the SUSE Linux Enterprise SDK and extensions requiring a registration key that is liable for costs. Proceed with Next.

  9. The following screen allows you to choose the Product Installation Mode. You can now choose between:

    • A SUSE Linux Enterprise Server installation.  To install a SLES system without SAP-specific customizations, choose Proceed with standard SLES installation. For details, see Installation Quick Start, Section 1.2 Installing SUSE Linux Enterprise Server (https://www.suse.com/documentation/sles-12/).

    • A SUSE Linux Enterprise Server for SAP Applications installation.  To install a SLES system with SAP-specific customizations, choose Proceed with standard SLES for SAP Applications installation.

      • To install an SAP Application together with the system, activate Start the SAP Installation Wizard right after the OS installation.

      • To prepare the system for later installation of an SAP application, leave Start the SAP Installation Wizard right after the OS installation deactivated.

      Proceed with Next.

    Installation Type
    Figure 3.4: Installation Type
Procedure 3.2: Finishing the OS Installation
  1. You can now choose whether to install an Add On Product. Proceed with Next.

  2. Review the proposed partition setup for the volumes /dev/system/root and /dev/system/swap. The volume /dev/system/data will be created later, as described in Section 2.6, “Partitioning”.

    Suitable values are preselected. However, if necessary, change the partition layout. You have the following options:

    Edit Proposal Settings

    Allows you to change the options for the proposed settings, but not the suggested partition layout itself.

    Create Partition Setup

    Select a disk to which to apply the proposal.

    Expert Partitioner

    Open the Expert Partitioner described in Deployment Guide, Chapter 14 Advanced Disk Setup, Section 14.1 Using the YaST Partitioner (https://www.suse.com/documentation/sles-12/).

    For partitioning advice specific to SUSE Linux Enterprise Server for SAP Applications, see Section 2.6, “Partitioning”.

    To accept the proposed setup without changes, proceed with Next.

    Suggested Partitioning
    Figure 3.5: Suggested Partitioning
  3. Select the clock and time zone to use in your system. To manually adjust the time or to configure an NTP server for time synchronization, choose Other Settings. For detailed information, see Deployment Guide, Chapter 6 Installation with YaST, Section 6.10 Clock and Time Zone (https://www.suse.com/documentation/sles-12/).

    Proceed with Next.

  4. Type a password for the system administrator account (called root) and repeat the password under Confirm Password. You can use the text box Test Keyboard Layout to make sure that all special characters appear correctly.

    For more information, see Deployment Guide, Chapter 6 Installation with YaST, Section 6.12 Password for the System Administrator root (https://www.suse.com/documentation/sles-12/).

    Proceed with Next.

    Important
    Important: Do Not Forget the root Password

    The user root has the permission to carry out all administrative tasks. Without this password, you cannot log in to the system as root.

    After you have entered the root password here, it cannot be retrieved again.

  5. On the screen Installation Settings, you can review and, if necessary, change several proposed installation settings. Each setting is shown alongside its current configuration. To change parts of the configuration, click the headline or other underlined items.

    Important
    Important: Firewall Configuration

    The software firewall of SLES for SAP is enabled by default. However, often, the ports your SAP product requires to be open are not opened automatically. This means that there may be network issues until you open the required ports manually.

    For details, see Section 6.2, “Configuring SuSEFirewall2”.

    Tip
    Tip: Pattern High Availability Is Necessary for High-Availability Installations Only

    If you are not planning to install a highly available SAP product, you can deselect the pattern High Availability from the installation. This saves space on the hard disk and download bandwidth for updates. Note that this pattern is distinct from the product SUSE Linux Enterprise High Availability Extension which you should not try to remove.

    To remove the pattern, click Software and then deselect Primary Functions › High Availability. Return to the overview with OK.

    Installation Settings
    Figure 3.6: Installation Settings
  6. When you are satisfied with the system configuration, click Install.

    Depending on your software selection, you may need to agree to further license agreements before you are asked to confirm that you want to start the installation process.

    Warning
    Warning: Deletion of Data

    Starting the installation process means that information on the disk you are installing on will fully or partly be deleted.

    In the installation confirmation box, click Install.

    When the installation if the operating system is finished, the system will reboot automatically.

    • If you chose to only prepare the system for installation, the system will boot to a desktop login screen.

    • If you chose to install an SAP application immediately after the operating system, the installation will continue after the reboot.

      In this case, continue with Chapter 4, Installing SAP Applications.

3.2 Using SLES for SAP Media from the Network

This section provides a short description of how to install from an installation medium served over the network.

  1. Copy the content of the SUSE Linux Enterprise Server for SAP Applications DVD to a Web server (for example, example.com), to the directory /srv/www/htdocs/sap_repo.

  2. Boot from DVD.

  3. Select one of the boot menu options using the keys /. Then add to the command line. To do so, specify the parameters listed below:

    • To start the network, add netsetup=1

    • Add the parameter autoyast=http://example.com/sap_repo/.

    • Add the parameter install=http://example.com/sap_repo.

  4. Follow the instructions in Section 3.1, “Using the Installation Workflow”.

For more information, see Deployment Guide, Chapter 13 Remote Installation (https://www.suse.com/documentation/sles-12/).

To avoid having to use a DVD to bootstrap the system, you can boot over the network via PXE. For details, see AutoYaST Guide, Chapter 6.2.3 Booting via PXE over the Network (https://www.suse.com/documentation/sles-12/).

3.3 Using an External AutoYaST Profile

Important
Important: AutoYaST Is Not Supported

Using AutoYaST to install SUSE Linux Enterprise Server for SAP Applications is not officially supported.

For more information on installing with AutoYaST, see:

For more information on partitioning for SAP applications with AutoYaST, see Section 2.6, “Partitioning”.

4 Installing SAP Applications

This section will guide you through the installation of SAP media sets you received from SAP.

4.1 First Steps

These first steps are only relevant during the installation workflow.

  1. When the system has booted, you will be presented with the screen Welcome. Proceed with Next.

  2. The screen Network Settings will now open. This gives you another chance to change the network settings.

    When you are finished configuring networking, proceed with Next.

    Important
    Important: Configure Networking as Recommended by SAP

    Make sure to configure the network connection as recommended by the documentation of your SAP application.

    For details regarding network configuration, see Administration Guide, Chapter 19 Basic Networking, Section 19.4 Configuring a Network Connection with YaST (https://www.suse.com/documentation/sles-12/).

    (While the next screen loads, the Welcome screen may appear again for a few seconds.)

  3. You can now choose how to continue:

    Create SAP file systems and start SAP product installation

    Allows installing an SAP application and setting up the system as a server providing SAP installation routines to other systems.

    Continue with Section 4.2, “Using the SAP Installation Wizard”.

    Only create SAP HANA file systems, do not install SAP products now

    Only create an SAP HANA file system.

    Important
    Important: Use Hardware Certified for SAP HANA

    To use this functionality, your hardware needs to be certified for SAP HANA. Otherwise, this option will not create a new file system and the installation workflow ends at this point.

    Finish wizard and proceed to OS login

    Do not install an SAP application and continue to the login screen of SUSE Linux Enterprise Server for SAP Applications.

    Proceed with Next.

4.2 Using the SAP Installation Wizard

Use the SAP Installation Wizard to install an SAP NetWeaver system (including database) or a simple SAP HANA system (single tenant, same password for all initial users, default settings).

To install other SAP applications or to create a more sophisticated SAP HANA setup, directly use one of the installation methods provided by SAP instead of this wizard.

Tip
Tip: Installing an SAP Application in a Fully Installed System

This process is documented as it appears during the installation workflow. However, there is a functionally equivalent YaST dialog available within the installed system. It has a different color scheme and lacks the left pane.

To start the SAP Installer, from the desktop, choose Applications › System › YaST, continue in the YaST control center by choosing Miscellaneous › SAP Product Installer.

Tip
Tip: SAP Installation Wizard Configuration

The SAP Installation Wizard configuration is specified and documented in /etc/sysconfig/sap-installation-wizard. You can change it according to your needs.

  1. In the screen SAP Installation Wizard, provide the Location of the SAP Installation Master (Figure 4.1, “Location of SAP Installation Master”). The location can either be a local, removable, or remote installation source.

    Location of SAP Installation Master
    Figure 4.1: Location of SAP Installation Master

    Select the corresponding option from the drop-down box. In the text box, specify the path to your source according to the format given in the following table.

    Table 4.1: Media Source Path

    Option

    Description

    Format of Path

    Local Sources

    dir://

    a local directory

    /path/to/dir/

    Removable Sources

    device://

    a locally connected hard disk

    devicename/path/to/dir/on/device

    usb://

    a USB mass storage device

    /path/to/dir/on/USB

    cdrom://

    a CD or DVD

    //

    Remote Sources

    nfs://

    an NFS share

    server_name/path/to/dir/on/device

    smb://

    an SMB share

    [user_name:password@]server_name//path/to/dir/on/server[?workgroup=workgroup_name]

    Tip
    Tip: Remote Location Specification

    To install from an NFS source, enter the name of the server and the complete path to the media data. For more information about setting up a remote installation server, see Chapter 5, Setting Up an Installation Server for SAP Media Sets.

    If you have installed from an installation server before or set up your system to be an installation server, you can also directly choose that server as the provider of the Installation Master. To do so, use the drop-down box below Choose an installation master.

  2. Under Advanced Options, choose from among the following options:

    Collect installation profiles but do not execute installation

    Use this option if you only want to set the installation parameters, but not perform the actual installation. If you choose this option, the installation will continue as it would without this option but the SAP Installer (SAPinst) will stop earlier. However, the following steps fully apply.

    For more information, see Section 4.3, “Continuing an Installation Using an Installation Profile”.

    Link to the installation master without copying its content to local location (SAP NetWeaver only)

    Use this option to avoid copying an Installation Master from one local location to another. This option is only active when the drop-down box above is set to dir://.

    Serve all installation media (including master) to local network via NFS

    Set up this system as an installation server for other SUSE Linux Enterprise Server for SAP Applications systems. The media copied to this installation server will be offered through NFS and can be discovered via Service Location Protocol (SLP).

    Proceed with Next.

    The SAP Installation Wizard will now copy the Installation Master to your local hard disk. Depending on the type of Installation Master you selected, the installation will continue differently:

    • If you are installing an SAP HANA database, skip ahead to Step 8.

    • If you are installing an SAP NetWeaver application, continue with the next step.

  3. You will now see the screen What Would You Like to Install. Under The SAP product is, choose how you want to install the product:

    SAP Standard System

    Install an SAP application including its database onto this system.

    SAP Standalone Engines

    Engines that add functionality to a standard product.

    Distributed System

    An SAP application that is separated onto multiple servers.

    SAP High-Availability System

    Installation of SAP NetWeaver in a high-availability setup.

    System Rename

    Allows changing the various system properties such as the SAP system ID, database ID, instance number or host name. This is useful, for example, when you want to install the same product in a very similar configuration on different systems.

    SAP Installation Wizard: Installation Mode and Database
    Figure 4.2: SAP Installation Wizard: Installation Mode and Database
  4. If you selected SAP Standard System, Distributed System, or SAP High-Availability System, additionally choose a back-end database under The back-end database system is.

    Proceed with Next.

  5. You will now see the screen Choose a Product. The products shown depend on the Media Set and Installation Master you received from SAP. From the list, choose the product you want to install.

    Proceed with Next.

    SAP Installation Wizard: Choose a Product
    Figure 4.3: SAP Installation Wizard: Choose a Product
  6. On the screen SAP Installation Wizard, you can provide the location of additional Installation Media you want to install. This can include, for example an SAP kernel, a database, and database exports.

    Copy a medium

    Provide a path to additional Installation Media. For more information on how to enter the path, see Table 4.1, “Media Source Path”.

    When providing a local path (dir://), you can additionally choose to only link to the Installation Media.

    Skip copying of medium

    Do not copy additional Installation Media. Choose this option if you do not need additional Installation Media or if you want to install additional Installation Media directly from their source, for example CDs/DVDs or flash disks.

    When choosing this option despite your SAP product requiring additional Installation Media, you will later need to provide the SAP Installer (SAPinst) with the relevant paths.

    Proceed with Next.

    If you chose to copy Installation Media, the SAP Installation Wizard will then copy the relevant files to your local hard disk.

    SAP Installation Wizard: Additional Installation Media
    Figure 4.4: SAP Installation Wizard: Additional Installation Media
  7. After copying the Installation Media, you will be asked whether you want to copy (prepare) more Installation Media. To do so, click Yes. After doing so, follow the instructions in Step 6.

    Otherwise, click No.

  8. You will be asked whether you want to copy Supplementary Media or Third-Party Media. To do so, click Yes. After doing so, follow the instructions in Step 6.

    Otherwise, click No.

    For information on creating Supplementary Media, see Appendix A, Supplementary Media.

  9. On the screen Additional software repositories for your SAP installation, you can add further software repositories. This can be useful, for example, for installing add-ons that are packaged as RPM. To do so, click Add new software repositories. For more information on adding repositories, see Deployment Guide, Chapter 8 Installing and Removing Software, Section 8.3.1 Adding Software Repositories (https://www.suse.com/documentation/sles-12/).

    Proceed with Next.

    Note
    Note: Location of Copied SAP Media

    At this point, all data required for the SAP installation should have been copied to /data/SAP_CDs (unless you chose to skip the process of copying). Each Installation Medium is copied to a separate directory. You might find the following directory structure, for example:

    tux > ls /data/SAP_CDs
    742-KERNEL-SAP-Kernel-742
    742-UKERNEL-SAP-Unicode-Kernel-742
    RDBMS-MAX-DB-LINUX_X86_64
    SAP-NetWeaver-740-SR2-Installation-Export-CD-1-3
    SAP-NetWeaver-740-SR2-Installation-Export-CD-2-3
    SAP-NetWeaver-740-SR2-Installation-Export-CD-3-3

    /data/SAP_CDs is the default directory as specified in the /etc/sysconfig/sap-installation-wizard configuration file.

  10. In SAP System Parameters, select the appropriate System T-Shirt Sizing.

    Proceed with OK.

    SAP System Parameters: T-Shirt-Sizing
    Figure 4.5: SAP System Parameters: T-Shirt-Sizing
  11. In the following dialog, choose the appropriate network settings for your system.

    Important
    Important: Configure Networking as Recommended by SAP

    Make sure to configure the network connection as recommended in the documentation provided to you by SAP.

    Proceed with OK.

    The SAP Installation Wizard will now download some additional software packages.

    Virtual Network Settings
    Figure 4.6: Virtual Network Settings
  12. The following steps differ somewhat depending on the type of SAP application you are installing:

    • When installing an SAP HANA database, you will be asked for a SID, an SAP HANA Instance Number, and a SAP HANA Master Password.

      Proceed with OK.

      SAP HANA will then be installed without further questions.

    • When installing an SAP NetWeaver application, the actual installation will be performed using the SAP Installer (SAPinst). Depending on your system, it can take a while until SAP Installer is ready.

      Follow the steps of SAP Installer as described in the documentation provided to you by SAP.

    SAP Installer: Defining Parameters
    Figure 4.7: SAP Installer: Defining Parameters
    Tip
    Tip: Installation Log Files

    If the installation of the SAP application fails, it may help to look at installation log files ending in .err located in /var/adm/autoinstall.

    For more information on log files, see Section 6.5, “Important Log Files”.

  13. On the screen Tune your system for optimal performance, you can choose a tuning option for your system. Normally, the best option is preselected and you do not need to change the Profile name.

    Proceed with Next, then click OK.

    You can later change this configuration using sapconf. For more information, see Section 6.4, “sapconf.

  14. The final screen is Installation Completed.

    To create an AutoYaST file for this installation, activate Clone This System for AutoYaST. The AutoYaST file will be placed in /root/autoinst.xml and will overwrite AutoYaST files created earlier in the same location.

    Proceed with Finish.

4.3 Continuing an Installation Using an Installation Profile

If you chose Collect installation profiles but do not execute installation during a previous run of the SAP Installation Wizard, this section will show you how to continue the installation of the selected SAP applications.

When collecting an installation profile, the SAP Installation Wizard copies product images to /data/SAP_CDs. It also prepares an installation environment for every product under the path /data/SAP_INST:

/data/SAP_INST/0/Instmaster
/data/SAP_INST/1/Instmaster
/data/SAP_INST/2/Instmaster
...

To continue the installation, follow these steps:

  1. In /etc/sysconfig/sap-installation-wizard, set the following:

    SAP_AUTO_INSTALL="yes"
  2. In the case of an SAP HANA/SAP BusinessOne installation, the SAP Installation Wizard will later use the parameters documented in the AutoYaST files in /data/SAP_INST/number.

    If you need to change any parameters, make sure to adapt the AutoYaST files at this point.

  3. Open the YaST control center and start SAP Product Installer.

  4. You will be asked whether to continue the pending installation. Select Install.

  5. All further interactions happen within the SAP Installer. Follow the steps of SAP Installer as described in the documentation provided to you by SAP.

    • In the case of an SAP NetWeaver installation, all parameter of the SAP Installer will be offered again for fine-tuning.

    • In the case of an SAP HANA/SAP BusinessOne installation, the installation will not be offering to make any changes to parameters.

5 Setting Up an Installation Server for SAP Media Sets

Using the SAP Installation Wizard, it is possible to copy the SAP media sets from a remote server (for example, via NFS or SMB). While the SAP Installation Wizard itself provides the option to create an installation server when installing an SAP product, it does not offer a way to copy all SAP media used in your organization to a single server.

However, you can easily create such a server on your own. For example, if you want to put the SAP media sets on an NFS Server, proceed as follows:

  1. On your installation server, create the directory /srv/www/htdocs/sap_repo.

  2. Open the file /etc/exports and add the following:

    /srv/www/htdocs/sap_repo *(ro,root_squash,sync)
  3. In /srv/www/htdocs/sap_repo, create a directory for every SAP medium you have. Give these directories speaking names, so you can identify them late. For example, you could use names like kernel, java, or maxdb.

  4. Copy the contents of each SAP medium to the corresponding directory with cp -a.

    Important
    Important: Avoid Using Windows* Operating Systems for Copying

    Using Windows operating system for copying or copying from/to Windows file systems like NTFS may break permission settings and capitalization of files and directories.

You can now install from the NFS server you set up. In the SAP Installation Wizard, specify the path this way: server_name/srv/www/htdocs/sap_repo. For more information on how to specify the path, see Table 4.1, “Media Source Path”.

For information about installing SUSE Linux Enterprise Server from an NFS server, see Deployment Guide, Chapter 13 Remote Installation, Section 13.2.2 Setting Up an NFS Repository Manually (https://www.suse.com/documentation/sles-12/).

6 Configuring SUSE Linux Enterprise Server for SAP Applications

6.1 Kernel: Page-Cache Limit

Problem

The kernel swaps out rarely accessed memory pages to use freed memory pages as cache to speed up file system operations, for example during backup operations.

SAP NetWeaver and SAP HANA use large amounts of memory for accelerated access to business data. Parts of this memory are rarely accessed. When a user request needs to access paged-out memory, the response time is poor. It is even worse when an SAP application running on Java incurs a Java garbage collection: The system starts heavy page-in (disc I/O) activity and has a poor response time for an extended period of time.

Solution

SUSE Linux Enterprise Server for SAP Applications includes a kernel tuning option that allows the system administrator to limit the amount of page cache that the kernel uses when there is competition between application memory and page-cache. This option tells the kernel that when the page cache is filled to the configured limit, application memory is more important and should thus not be paged out. No pages will be paged out if the memory footprint of the workload plus the configured page-cache limit do not exceed the amount of physical RAM in the system.

Tip
Tip: sapconf Configures These Parameters

The parameters reproduced below are also configured by sapconf.

For more information, see Section 6.4, “sapconf.

Important
Important: The Following Are Example Values

The values reproduced in the following are examples only. Do not set the following parameters on a productive system without first trying and calibrating them on a non-productive system.

If your system does not exhibit page-cache limit issues under the workloads it is running, there is no need to adjust this parameter.

These kernel options are available for configuration:

  • vm.pagecache_limit_mb (/proc/sys/vm/pagecache_limit_mb)

  • vm.pagecache_limit_ignore_dirty (/proc/sys/vm/pagecache_limit_ignore_dirty)

For permanent use, set them in /etc/sysctl.conf, for example:

vm.pagecache_limit_mb = 1024
vm.pagecache_limit_ignore_dirty = 0

For background information, see SAP Note 1557506: Linux Paging Improvements (https://service.sap.com/sap/support/notes/1557506).

6.2 Configuring SuSEFirewall2

By default, the installation workflow of SUSE Linux Enterprise Server for SAP Applications enables SuSEFirewall2. The firewall needs to be manually configured to allow network access for the following:

Additionally, open the ports 1128 (TCP) and 1129 (UDP).

SAP applications require many open ports and port ranges in the firewall. The exact numbers depend on the selected instance. For more information, see the documentation provided to you by SAP.

6.3 Configuring HANA-Firewall

To simplify setting up a firewall for SAP HANA, you can install an extension for SuSEFirewall2 using the package HANA-Firewall. Whereas standard SuSEFirewall2 allows only three zones (internal, DMZ, and external), HANA-Firewall enables you to configure more zones to accommodate all running SAP HANA instances.

HANA-Firewall consists of the following parts:

  • A YaST module: HANA Firewall

  • A command-line utility: hana-firewall

  • A service: hana-firewall

HANA-Firewall works by adding rule sets to your existing SuSEFirewall2 configuration. In the YaST module, you can configure which rule sets are applied.

For single-tenant databases, the specific port numbers that need to be inserted into the rules are automatically generated from the instance number of the SAP HANA database.

6.4 sapconf

sapconf can automatically tune a system for SAP NetWeaver and SAP HANA/SAP BusinessOne applications. To do so, it relies on the system tuning service tuned. (Before using sapconf, make sure that the package tuned is installed.)

If you used the SAP Installation Wizard to install an SAP application, sapconf is usually already active and configured for the application you installed.

If that is not the case, you can tune the system for SAP NetWeaver with:

root # sapconf start

To tune the system for SAP HANA or SAP BusinessOne (both use the same tuning profile), use:

root # sapconf hana start

To apply a different tuning profile when sapconf is already running, make sure to stop it first.

For more information, see the following man pages:

  • sapconf(8)

  • tuned-adm(8)

  • tuned-profiles-sap-hana(7)

  • tuned-profiles-sap-netweaver(7)

6.5 Important Log Files

The most important files for this product are:

  • The SAP Installation Wizard is a YaST module. You can find its log entries in /var/log/YaST/y2log.

  • All SAP knowledge is bundled in a library. You can find its log entries in /var/log/SAPmedia.log.

  • You can find log files related to auto-installation in /var/adm/autoinstall/logs.

A Supplementary Media

The idea behind Supplementary Media is to enable partners or customers to add their own tasks or workflows to the Installation Wizard.

This is done by adding a small XML file, which will be part of an AutoYaST XML file. This file must be called product.xml, then it will be included in the workflow.

This can be used for various types of additions, such as adding your own RPMs, running your own scripts, setting up a cluster file system or creating your own dialogs and scripts.

A.1 product.xml

The product.xml file looks like a normal AutoYaST XML file, but with some restrictions.

The restrictions relate to the fact that only the parts for the second stage of the installation can be run, because the first stage was executed before.

Both XML files (autoyast.xml and product.xml) will be merged after the media is read and a new AutoYaST XML file is generated on the fly for the additional workflow.

The following areas or sections will be merged:

<general>
  <ask-list>         1
  ...
<software>           2
  <post-packages>
  ...
<scripts>
  <chroot-scripts>   3
  <post-scripts>     4
  <init-scripts>     5
  ...

1

see Section A.2, “Own AutoYaST Ask Dialogs”

2

see Section A.3, “Installing Additional Packages”

3

after the package installation, before the first boot

4

during the first boot of the installed system, no services running

5

during the first boot of the installed system, all services up and running

All other sections will be replaced.

For more information on customization options, see AutoYaST Guide, Chapter 4 Configuration and Installation Options, Section 4.30 Custom User Scripts (https://www.suse.com/documentation/sles-12/).

A.2 Own AutoYaST Ask Dialogs

For more information on the Ask feature of AutoYaST, see AutoYaST Guide, Chapter 4 Configuration and Installation Options, Section 4.33 Ask the User for Values During Installation (https://www.suse.com/documentation/sles-12/).

For the Supplementary Media, you can only use dialogs within the cont stage (<stage>cont</stage>), which means they are executed after the first reboot.

Your file with the dialogs will be merged with the base AutoYaST XML file.

As a best practice, your dialog should have a dialog number and an element number, best with steps of 10. This helps to include later additions and could be used as targets for jumping over a dialog or element dependent on decisions. We also use this in our base dialogs and if you provide the right dialog number and element number, you can place your dialog between our base dialogs.

You can store the answer to a question in a file, to use it in one of your scripts later. Be aware that you must use the prefix /tmp/ay for this, because the Installation Wizard will copy such files from the /tmp directory to the directory where your media data also will be copied. This is done because the next Supplementary Media could have the same dialogs or same answer file names and would overwrite the values saved here.

Here is an example with several options:

<?xml version="1.0"?>
<!DOCTYPE profile>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
         xmlns:config="http://www.suse.com/1.0/configns">
<general>
  <ask-list config:type="list">
      <ask>
          <stage>cont</stage>
          <dialog config:type="integer">20</dialog>
          <element config:type="integer">10</element>
          <question>What is your name?</question>
          <default>Enter your name here</default>
          <help>Please enter your full name within the field</help>
          <file>/tmp/ay_q_my_name</file>
          <script>
             <filename>my_name.sh</filename>
             <rerun_on_error config:type="boolean">true</rerun_on_error>
             <environment config:type="boolean">true</environment>
             <source><![CDATA[
function check_name() {
           local name=$1
           LC_ALL=POSIX
           [ -z "$name" ] && echo "You need to provide a name." && return 1
           return 0
}
check_name "$VAL"
]]>
             </source>
             <debug config:type="boolean">false</debug>
             <feedback config:type="boolean">true</feedback>
          </script>
      </ask>
  </ask-list>
</general>
</profile>

A.3 Installing Additional Packages

You can also install RPM packages within the product.xml file. To do this, you can use the <post-packages> element for installation in stage 2.

For more information, see AutoYaST Guide, Chapter 4 Configuration and Installation Options, Section 4.8.5 Installing Packages in Stage 2 (https://www.suse.com/documentation/sles-12/). An example looks as follows:

...
<software>
 <post-packages config:type="list">
  <package>yast2-cim</package>
 </post-packages>
</software>
...

A.4 Example Directory for Supplementary Media

A minimal example for Supplementary Media contains only a file called product.xml.

B Documentation Updates

This section contains information about documentation content changes made to the SUSE Linux Enterprise Server for SAP Applications Guide.

This document was updated on the following dates:

B.1 February 15, 2016

Updates were made to the following sections. The changes are explained below.

Updates to the Structure of the Guide

Improve organization of the guide by updating its structure. Chapter 2, Planning the Installation, Chapter 4, Installing SAP Applications, Chapter 6, Configuring SUSE Linux Enterprise Server for SAP Applications, and Chapter 5, Setting Up an Installation Server for SAP Media Sets are now chapters instead of sections.

Appendix A, Supplementary Media is now an appendix instead of section.

Section 2.6, “Partitioning” is now a section within Chapter 2, Planning the Installation instead of a chapter.

Merge Section 1.1, “Software Components” and Chapter 5, SUSE Linux Enterprise Server for SAP Applications Components.

Move Section 3.2, “Using SLES for SAP Media from the Network” from Chapter 3, Remote Installation from a Network Server to Chapter 3, Installing the Operating System.

Move Section 2.5, “Required Data for Installing” from Chapter 3, Installing the Operating System to Chapter 2, Planning the Installation.

Move certain information from Section 1.1.4, “Installation Workflow” to Section 2.4, “Overview of the Installation Workflow”.

Chapter 1, What Is SUSE Linux Enterprise Server for SAP Applications?

Add figure.

Section 1.1.3, “HA Resource Agents for SAP HANA System Replication”

Add information on supported scenarios.

Section 1.1.6, “Antivirus Protection with ClamSAP”

Mention added support for NW-VSI 2.0.

Section 1.1.7, “SAP HANA Security”

Add new section.

Section 1.1.8, “Simplified Operations Management”

Add new section.

Section 3.1, “Using the Installation Workflow”

Remove outdated installation options. Update Installation Workflow.

Section 3.3, “Using an External AutoYaST Profile”

Remove information that duplicated.

Chapter 4, Installing SAP Applications

Update Installation Workflow.

Section 6.3, “Configuring HANA-Firewall

Add new section.

Section 6.4, “sapconf

Add new section.

B.2 May 29, 2015

Updates were made to the following sections. The changes are explained below.

Section 1.1, “Software Components”

Add more information on SUSE Linux Enterprise High Availability Extension.

There are also White Papers about SUSE Linux Enterprise High Availability Extension and SUSE Linux Enterprise Server for SAP Applications.

Chapter 2, Planning the Installation

Provide ISO image download URL.

Section 2.2, Booting the Installation Medium

The package scope of the SLES for SAP Applications — Installation is identical to a default SUSE Linux Enterprise Server installation.

Section 2.3, SLES for SAP — Installation

Add note about pre-selected packages in case of registration at this stage of the installation.

Section 2.4.3.5, Registration

Add note about pre-selected packages in case of registration at this stage of the installation.

Chapter 4, Installing SAP Applications

Rewrite remote location specification.

Section 2.6, “Partitioning”

SAP HANA requires 2 GB of swap.

Section 1.1.3, “HA Resource Agents for SAP HANA System Replication”

Address SAP HANA System Replication (https://bugzilla.suse.com/show_bug.cgi?id=929626).

Section 1.1.7.2, “Hardening Guide for SAP HANA”

New section (https://bugzilla.suse.com/show_bug.cgi?id=929625).

B.3 April 29, 2015

Updates were made to the following sections. The changes are explained below.

General

Replace SUSE Linux Enterprise Server 11 references with SUSE Linux Enterprise Server 12 everywhere, and adjust the text according to the new installation flow.

About This Guide

Update feedback information.

Section 3.3, “Using an External AutoYaST Profile”

Add note about loading an external profile via HTTP (https://bugzilla.suse.com/show_bug.cgi?id=925747).

B.4 October 28, 2013

Updates were made to the following sections. The changes are explained below.

Chapter 3, Installing the Operating System

Update Hardware Requirements, Hard Disk space, and adjust the following text accordingly.

Section 2.6, “Partitioning”

New chapter.

Appendix B, Documentation Updates

New appendix.

Print this page