SUSE Linux Enterprise Server for SAP Applications 11 SP3

The Guide

Publication Date 30 Oct 2013

Copyright © 2013 Novell, Inc. 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 Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell.com/company/legal/trademarks/tmlist.html. 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 Novell 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 Novell, Inc., SUSE LINUX Products GmbH, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.


Contents

About This Guide
1. Overview
2. Additional Documentation and Resources
3. Feedback
4. Documentation Conventions
1. What is SUSE Linux Enterprise Server for SAP Applications?
1.1. Overview
1.2. Software Components
1.3. Services for SUSE Linux Enterprise Server for SAP Applications
2. Default Installation Scenarios
2.1. Planning the Installation
2.2. Booting the Installation Medium
2.3. SLES for SAP Applications — Installation
2.4. SLES for SAP Applications — Installation with Wizard
2.5. SLES for SAP Applications — Installation with External Profile
3. Background Information on Partitioning
3.1. Stage 1: Partitioning for the Operating System
3.2. Stage 2: Partitioning for the SAP System
4. Remote Installation from a Network Server
4.1. Installing with Installation Media from the Network
4.2. Copying SAP Media Sets from a Remote Server with the Installation Wizard
5. SUSE Linux Enterprise Server for SAP Applications Components
5.1. SUSE Linux Enterprise High Availability Extension
5.2. Configuring SUSE Linux Enterprise Server for SAP Applications
5.3. The Installation Wizard
A. Downloading CryptoAddOn (SAPCryptoLib)
B. Documentation Updates
B.1. October 28, 2013

List of Figures

1.1. What is SUSE Linux Enterprise Server for SAP Applications?
2.1. DVD Boot Menu
2.2. System Volume Configuration
2.3. Password for root User
2.4. Hostname, Domain Name, and IP Address
2.5. Domain Name Service (DNS) and Time Server (NTP)
2.6. Registration
2.7. SAP Product Installation
2.8. YaST Control Center: SAP Product Installer
2.9. SAP Installation Wizard: SAP Installation Master Location
2.10. SAP Installation Wizard: Products Available
2.11. SAP Installation: Location of the Database Medium
2.12. SAP Installation: Path to a Kernel or Java Medium
2.13. SAP Installation: Type of Installation
2.14. SAP Installation: Location of the Export Media
2.15. SAP System Parameters
2.16. SAP Virtual Network Settings
2.17. SAP Database Log Mode
2.18. SAP Installation: Supplement Medium
2.19. SAP Installation: Compatibility Mode
2.20. SAP Installer (SAPinst)

About This Guide

SUSE® Linux Enterprise Server for SAP Applications is the reference platform for SAP's software development. 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 Server 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?

Here you will find an overview of SUSE Linux Enterprise Server for SAP Applications.

Default Installation Scenarios

This chapter explains in detail the available installation scenarios for SUSE Linux Enterprise Server for SAP Applications.

Remote Installation from a Network Server

This chapter provides details about remote installation scenarios for SUSE Linux Enterprise Server for SAP Applications.

SUSE Linux Enterprise Server for SAP Applications Components

In this chapter the components are listed and additionally you will find hints about configuring 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.

For an overview of the documentation available for your product and the latest documentation updates, refer to http://www.suse.com/documentation.

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, log into the Novell Customer Center from http://www.suse.com/support/ and select My Support+Service Request.

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/documentation/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, please 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 filenames

  • placeholder: replace placeholder with the actual value

  • PATH: the environment variable PATH

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

  • user: users or groups

  • Alt, Alt+F1: 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.

    ►ipseries zseries: 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.

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

Figure 1.1. What is SUSE Linux Enterprise Server for SAP Applications?

What is SUSE Linux Enterprise Server for SAP Applications?

1.1. Overview

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 (see Section 1.2, “Software Components”) and service offerings (see Section 1.3, “Services for SUSE Linux Enterprise Server for SAP Applications”).

1.2. Software Components

SUSE Linux Enterprise Server

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

Installation Wizard

The Installation Wizard offers a guided installation path for both the SUSE Linux Enterprise Server operating system and the SAP application.

Additionally, the workflow can be extended by 3rd party vendors or customers with the help of the Supplement Media (see Section 5.3.1, “Supplement Media”).

SUSE Linux Enterprise High Availability Extension

This component consists of:

  • Cluster manager

  • Cluster file system

  • Resource agents, also for SAP

For more information about SUSE Linux Enterprise High Availability Extension, see the High Availability Guide (http://www.suse.com/documentation/sle_ha/) and the Best Practice Guides (http://www.suse.com/products/sles-for-sap/resource-library/sap-best-practices.html).

Page-Cache Limit

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

ClamSAP

ClamSAP is a new antivirus toolkit integration. For more information, see Section 5.3.2, “ClamSAP”.

1.3. Services for SUSE Linux Enterprise Server for SAP Applications

Extended Service Pack Overlap Support

SUSE Linux Enterprise Server for SAP Applications includes Extended Service Pack Overlap Support. This extends the overlapping support period for two service packs by one year. This allows to perform a service pack migration within a 18 months time period as opposed to 6 months. With Extended Service Pack Overlap Support migrations can be scheduled more easily and testing before migration can be performed under lesser time constraints, while still remaining under full support and receiving all relevant maintenance updates. Extended Service Pack Overlap Support is a unique offering being part of SUSE Linux Enterprise Server for SAP Applications.

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. SUSE Linux Enterprise Server Priority Support for SAP Applications 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 in a 1 Face to the Customer manner, thus reducing complexity and lowering the total cost of ownership.

For background information, see SAP Note 1056161: SUSE Priority Support for SAP Applications https://service.sap.com/sap/support/notes/1056161.

Chapter 2. Default Installation Scenarios

After planning the installation with downloading the software and checking the minimal hardware requirements, there are three default installation scenarios:

2.1. Planning the Installation

Plan the installation with downloading the software and checking the minimal hardware requirements.

2.1.1. Download and Installation Preparations

  1. Download the DVD ISO image of SUSE® Linux Enterprise Server for SAP Applications 11 (electronic media kit).

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

2.1.2. Hardware Requirements

CPU

64bit (x86_64).

Hard Disk

For the Installation with Wizard, at least 10 GB hard disk space for the system volume plus space for the swap partition and 200 GB for the data partition are required.

2.2. Booting the Installation Medium

Different scenarios are available to install SUSE Linux Enterprise Server for SAP Applications 11. Select the preferred installation scenario from the DVD boot menu:

Figure 2.1. DVD Boot Menu

DVD Boot Menu

Boot from Hard Disk

Booting the system installed on the local hard disk.

SLES for SAP Applications — Installation (see Section 2.3, “SLES for SAP Applications — Installation)

A standard SLES installation prepared for installing SAP applications later. You can install SAP applications with 3rd party installation routines.

This scenario is suitable for experienced administrators who want to install SUSE Linux Enterprise Server for SAP Applications according to their own plan. The default package selection is already adapted to SAP installations.

SLES for SAP Applications — Installation with Wizard (see Section 2.4, “SLES for SAP Applications — Installation with Wizard)

This is a guided installation of the operating system and a SAP application. After the installation of the operating system the SAP Installation Wizard will start for installation of a validated SAP solution.

SLES for SAP Applications — Installation with External Profile (see Section 2.5, “SLES for SAP Applications — Installation with External Profile)

This installation is driven by a user-provided AutoYaST profile. There are no SUSE-provided SAP optimizations.

This scenario is suitable for experienced users who are familiar with AutoYaST and want to deploy their own AutoYaST profiles to install SUSE Linux Enterprise Server for SAP Applications.

Rescue System

Starting a minimal Linux system without a graphical user interface. For more information, see the Administration Guide, Chapter 34, Common Problems and Their Solutions; find the Administration Guide at https://www.suse.com/documentation/sles11/.

Memory Test

Testing the system RAM using repeated read and write cycles. For more information, see the Administration Guide Chapter 34, Common Problems and Their Solutions.

2.3. SLES for SAP Applications — Installation

The first part is a standard manual SUSE Linux Enterprise Server installation; for details about such a SLES installation, see the SLES Deployment Guide, Chapter 6, Installation with YaST. In addition, the SAP Application Server Base (sap-loc and sapconf) pattern will be installed by default and basic settings will be configured.

You will be prompted for all common installation settings, like partitioning of storage devices, network, or software packages.

2.4. SLES for SAP Applications — Installation with Wizard

This is a guided installation of the operating system with optimized settings for SAP applications.

During this installation scenario, the following installation and configuration steps will take place and interactive settings are required or possible.

2.4.1. Data Required for Installing the System (with Wizard)

The following data is required for the SUSE Linux Enterprise Server part of the installation (required per physical server):

Hostname

Domain

IP address

Subnet mask

Domain searchlist (DNS)

IP for nameserver

IP for gateway

Master password for the system installation (root password)

The following data is required for the SAP part of the installation (required per SAP system):

SAP System ID of the system to be built up

Virtual hostname (*)

Virtual IP address for SAP service (*)

Virtual netmask (*)

Instance number of the SAP system

Solution Manager key for the SAP system (*)

System T-Shirt Sizing (S, M, L, or customer-specific size) (*)

Database Log Mode (*)

(*) not required for TREX.

2.4.2. Selecting SLES for SAP Applications — Installation with Wizard from the DVD Boot Menu

From the DVD boot menu (see Figure 2.1, “DVD Boot Menu”), select SLES for SAP Applications — Installation with Wizard. The installation process loads and configures a Linux system with all requirements for a SAP installation. To view the boot messages and copyright notices during this process, press Esc. On completion of this process, the YaST installation program starts and displays the graphical installer, which will run mostly automatically.

2.4.3. Preparing System for Automated Installation

After analyzing your computer, the next YaST pop-up dialog will let you specify the volume configuration. Here you configure the volume for the system and swap space. The data volume comes later, after you select the SAP Application.

Figure 2.2. System Volume Configuration

System Volume Configuration

If there is just one hard disk, keep it as the system volume device and set the size of the system volume (and the swap space) in GB in the lower field and confirm it; see Figure 2.2, “System Volume Configuration”.

[Tip]Size of the System Volume

Normally, at least 10 GB is required for the system volume. The swap space depends on the available main memory (RAM). For more information, see the SAP Note 1597355: https://service.sap.com/sap/support/notes/1597355.

If there is more than one hard disk, select the right one as the system volume device and set the size of the system volume (and the swap space) in GB in the lower fields and confirm it. For more information about partitioning, see Chapter 3, Background Information on Partitioning.

[Warning]Deleting Data

If you confirm the storage volume configuration, all existing data on the hard disk will be deleted. If you do not want this to happen, turn off the system.

After confirmation, YaST performs the software installation. Packages are installed one by one, so you can see the progress.

2.4.4. Password for the System Administrator root

When all packages are installed, the basic installation is finished, and the system is rebooted for initial configuration, you will be prompted to enter a Password for the System Administrator root; see Figure 2.3, “Password for root User”.

Figure 2.3. Password for root User

Password for root User

root is the name of the superuser, or the administrator of the system. Unlike regular users (who may or may not have permission to access certain areas or execute certain commands on the system), root has unlimited access to change the system configuration, install programs, and set up new hardware. The root account should only be used for system administration, maintenance, and repair. Logging in as root for daily work is rather risky: a single mistake could lead to irretrievable loss of system files.

For verification purposes, the password for root must be entered twice. Do not forget the root password. Once entered, this password cannot be retrieved.

The root password can be changed any time later in the installed system. To do so, run YaST and start Security and Users+User and Group Management.

[Warning]The root User

The root user has all the permissions needed to make changes to the system. To carry out such tasks, the root password is required. You cannot carry out any administrative tasks without this password.

2.4.5. Hostname, Domain Name, and IP Address

The next dialog starts with the network configuration; see Figure 2.4, “Hostname, Domain Name, and IP Address”.

Figure 2.4. Hostname, Domain Name, and IP Address

Hostname, Domain Name, and IP Address

The Hostname is the computer’s name in the network. The Domain Name is the name of the network. A hostname and domain are proposed by default. If your system is part of a network, the hostname has to be unique in this network, whereas the domain name has to be common to all hosts on the network.

Also enter the IP Address and Netmask for this host. The IP address must be unique and the netmask has to be common to all hosts on the network.

2.4.6. Domain Name Service (DNS) and Time Server (NTP)

The next dialog continues with the network configuration; see Figure 2.5, “Domain Name Service (DNS) and Time Server (NTP)”.

Figure 2.5. Domain Name Service (DNS) and Time Server (NTP)

Domain Name Service (DNS) and Time Server (NTP)

For Domain Name Service (DNS) configuration, enter the Domain Searchlist and the IP Address of DNS Server plus the IP address of the Default Gateway of your network.

Also enter the address of the NTP Server to synchronize automatically via Network Time Protocol (NTP).

2.4.7. Registration

To get technical support and product updates, you need to register and activate your product with the Novell Customer Center; see Figure 2.6, “Registration”. This dialog provides assistance for doing so. Find detailed information about Novell Customer Center at http://www.novell.com/documentation/ncc/.

Figure 2.6. Registration

Registration

Enter your E-Mail Address and Registration Code for the product. If you provide the registration code now, operating system updates will be installed automatically during the installation of the system.

2.4.8. System Configuration Settings

After confirming the registration data, the system will be configured with the supplied settings.

No user action is required at this stage.

[Warning]Firewall Disabled

This wizard-based installation scenario disables the firewall (SuSEfirewall2) completely.

If needed, you can activate the firewall after the installation. If you activate the firewall after the installation, you must open all required ports manually. For more information about required ports, see Section 5.2.2, “Ports Configuration”.

2.4.9. SAP Product Installation

After applying the configuration settings, you are prompted to continue with the SAP Product Installation using the SAP Installation Wizard. The SAP Installation Wizard will install the SAP application from the SAP media kits you received from SAP.

[Tip]SAP Product Installation Default Settings

The SAP Product Installation default settings are specified and documented in /etc/sysconfig/sap-installation-wizard. You can change them according to your needs.

Procedure 2.1. SAP Product Installation

  1. Confirm the pop-up (see Figure 2.7, “SAP Product Installation”) if you want to continue with the installation right away. Otherwise, it is possible to interrupt the installation process at this point and resume it after a system restart.

    Figure 2.7. SAP Product Installation

    SAP Product Installation

    [Tip]Resuming SAP Installation after System Restart

    To resume the SAP installation with the wizard, start YaST and select the SAP Product Installer (Computer, then in the YaST Control Center click Miscellaneous+SAP Product Installer; see Figure 2.8, “YaST Control Center: SAP Product Installer”). The functionality is the same, but the layout of the dialogs is different; the left progress pane is only displayed when continuing with the installation without a restart.

    The following screen shots document the installation with the SAP Product Installer that runs after a restart of the system.

    Figure 2.8. YaST Control Center: SAP Product Installer

    YaST Control Center: SAP Product Installer

  2. In the next dialog provide the Location of the SAP Installation Master; see Figure 2.9, “SAP Installation Wizard: SAP Installation Master Location”. The location could be a local source (either directory (dir://), locally connected hard disk (device://), USB mass storage (usb://), or CD-ROM (cdrom://)), or a remotely provided installation source (either NFS (nfs://) or SMB (smb://))—select the corresponding option from the pull-down list on the left.

    [Tip]Remote Location Specification

    If you want to install from an NFS source, you must 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 the SUSE Linux Enterprise Server 11 Deployment Guide, Section 14.2, Setting Up the Server Holding the Installation Sources (the Deployment Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

    To save time and space, you can also loop mount ISO images on the installation server. For more information, see the SUSE Linux Enterprise Server 11 Deployment Guide, Section 14.2.6, Using ISO Images of the Installation Media on the Server.

    Figure 2.9. SAP Installation Wizard: SAP Installation Master Location

    SAP Installation Wizard: SAP Installation Master Location

  3. In the next dialog you can select the SAP products you want to install. The offerings of available products depend on the media set and installation master you received from SAP; for example, see Figure 2.10, “SAP Installation Wizard: Products Available”.

    Figure 2.10. SAP Installation Wizard: Products Available

    SAP Installation Wizard: Products Available

  4. For example, select Enhancement Package 5 for SAP ERP and click Next. Now the relevant part of the SAP media will be copied to the hard drive of the machine for the following SAP installation (after copying, see the contents of /data/SAP_CDs; the layout is explained later in this chapter). This is repeated for all necessary SAP media, with some additional simple questions.

  5. After copying the Installation Master Media, as step 2 enter the location of the database medium (e.g., the SAP MaxDB RDBMS); see Figure 2.11, “SAP Installation: Location of the Database Medium” for an NFS installation example.

    Figure 2.11. SAP Installation: Location of the Database Medium

    SAP Installation: Location of the Database Medium

  6. Now you must provide the medium with the application server framework. As step 3 you are asked for the Path to a Kernel or Java Medium. For example, if you want to install an ABAP-based system, provide the SAP Kernel for NW70 EHP1 Linux; see Figure 2.12, “SAP Installation: Path to a Kernel or Java Medium” for an NFS installation example.

    Figure 2.12. SAP Installation: Path to a Kernel or Java Medium

    SAP Installation: Path to a Kernel or Java Medium

  7. As step 4 for the Type of Installation, select Central Installation; see Figure 2.13, “SAP Installation: Type of Installation”.

    Figure 2.13. SAP Installation: Type of Installation

    SAP Installation: Type of Installation

  8. As step 5 enter the location of the Export Media (e.g., the SAP CRM Installation Export DVD); see Figure 2.14, “SAP Installation: Location of the Export Media” for an NFS installation example.

    Figure 2.14. SAP Installation: Location of the Export Media

    SAP Installation: Location of the Export Media

    If needed, add the additional export media when installation wizard asks about it.

  9. Then you can then copy a CryptoAddOn medium; this is optional. Generally, the encryption feature depends on the SAP product. Starting with SAP NetWeaver 7.03/7.3 the cryptographic functionality is already included in the SAP NetWeaver DVDs and does not have to be specified separately. If the wizard asks you to insert the medium containing the cryptographic functionality, see the Appendix A, Downloading CryptoAddOn (SAPCryptoLib) on how to obtain the encryption files.

  10. At this point, all data required for the SAP installation is selected and copied to /data/SAP_CDs/0, one directory per medium:

    /data/SAP_CDs/0:
    total 48
    drwxr-xr-x 12 root root 4096 Sep 27 14:01 ./
    drwxr-xr-x  4 root root 4096 Sep 27 14:06 ../
    drwxr-xr-x  4 root root 4096 Sep 27 13:54 EXPORT1/
    drwxr-xr-x  4 root root 4096 Sep 27 13:56 EXPORT2/
    drwxr-xr-x  4 root root 4096 Sep 27 13:58 EXPORT3/
    drwxr-xr-x  4 root root 4096 Sep 27 14:00 EXPORT4/
    drwxr-xr-x  4 root root 4096 Sep 27 14:01 EXPORT5/
    drwxr-xr-x  4 root root 4096 Sep 27 14:03 EXPORT6/
    drwxr-xr-x 15 root root 4096 Sep 27 13:43 Instmaster/
    drwxr-xr-x  4 root root 4096 Sep 27 13:44 RDBMS-ADA/
    drwxr-xr-x  2 root root 4096 Sep 27 13:46 SAPLUP/
    drwxr-xr-x  7 root root 4096 Sep 27 13:46 UKERNEL/

    Each time you start the installation process again, a new directory will be created with a higher number (/data/SAP_CDs/0, /data/SAP_CDs/1, /data/SAP_CDs/2, etc.):

    /data/SAP_CDs/1:
    total 16
    drwxr-xr-x  4 root root 4096 Sep 27 14:07 ./
    drwxr-xr-x  4 root root 4096 Sep 27 14:06 ../
    drwxr-xr-x 15 root root 4096 Sep 27 14:06 Instmaster/
    drwxr-xr-x  4 root root 4096 Sep 27 14:07 RDBMS-ADA/
    

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

  11. In the following configuration dialogs, enter the details for the SAP installation.

    Figure 2.15. SAP System Parameters

    SAP System Parameters

    In Figure 2.15, “SAP System Parameters”, as SID (SAP System ID) enter the three letter SAP System ID such as ERP. Enter the SAP Instance Number. Enter and repeat the SAP Master Password, which must fulfill the requirements described in the help text. Finally, specify the System T-Shirt-Sizing. The SAP SCS Instance Number is only required for Java installations. For details, see the online help on the left.

  12. In Figure 2.16, “SAP Virtual Network Settings”, enter the virtual network settings, if needed.

    Figure 2.16. SAP Virtual Network Settings

    SAP Virtual Network Settings

  13. In Figure 2.17, “SAP Database Log Mode”, select the the database log mode, and—if needed—install the SAP Cryptographic Library. Provide the location of the Crypto Add-On medium, if the wizard asks for it.

    Figure 2.17. SAP Database Log Mode

    SAP Database Log Mode

  14. At this stage it is possible to install a Supplement Medium; see Figure 2.18, “SAP Installation: Supplement Medium”. For more information about a Supplement Media, see Section 5.3.1, “Supplement Media”.

    Figure 2.18. SAP Installation: Supplement Medium

    SAP Installation: Supplement Medium

  15. SUSE Linux Enterprise Server for SAP Applications 11 SP3 is delivered with the Linux Kernel 3.0. If the SAP Kernel does not support Linux Kernel 3.0 yet, a pop-up dialog (Figure 2.19, “SAP Installation: Compatibility Mode”) will inform you about the activation of a compatibility mode, which will make sure that you can still install your SAP product.

    Figure 2.19. SAP Installation: Compatibility Mode

    SAP Installation: Compatibility Mode

  16. As the last step of the installation procedure, you can prepare the installation of another SAP product, if wanted. If you confirm that you wish to install an additional product, the installation procedure will enter into a new iteration and restart the installation process beginning with Step 4 to set up an additional product.

  17. Now all installation data (media and settings) is available to the wizard, and the final deployment of the SAP system can take place with the SAP installer (SAPinst). The SAP installer displays a visualization of the installation steps it performs; see Figure 2.20, “SAP Installer (SAPinst)”.

    Figure 2.20. SAP Installer (SAPinst)

    SAP Installer (SAPinst)

[Note]Installation Progress

Depending on your machine, it takes a while until the SAPinst tool shows up.

After the SAP installer has finished, you will see a short summary of the installation data.

2.5. SLES for SAP Applications — Installation with External Profile

This installation is driven by a user-provided AutoYaST profile and there is no wizard support. This scenario is suitable for experienced users who are familiar with AutoYaST and want to deploy their own AutoYaST profiles to install SUSE Linux Enterprise Server for SAP Applications. For more information about AutoYaST profiles, see the SLES AutoYaST Guide (the AutoYaST Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

In order to use a user-provided AutoYaST profile, select Install SLES for SAP Applications — Installation with External Profile from the DVD Boot Menu. Within the boot options, change the autoyast=usb:/// parameter to the location of a user-provided AutoYaST profile, or enter the location when YaST asks for it in the next dialog.

You can also reference the SAP specific pattern, the HA and WebYaST components and SAP-specific IBM Java in your AutoYaST profile and then install it during this installation scenario. As everything else, these components are not preselected and you must include this yourself in your autoyast.xml file.

2.5.1. About AutoYaST

AutoYaST is a system for installing one or more SUSE Linux systems automatically and without user intervention. AutoYaST installations are performed using an AutoYaST profile with installation and configuration data. That profile can be created using the AutoYaST configuration interface and can be provided to YaST during installation in different ways.

For more information about AutoYaST, see the SUSE Linux Enterprise Server 11 AutoYaST Guide (the AutoYaST Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

2.5.2. Partitioning with AutoYaST

For standard systems find pre-defined partitioning settings in /usr/share/YaST2/include/sap-installation-wizard/. These could serve as examples if you want to create your custom partitioning scripts.

For background information on partitioning, see Chapter 3, Background Information on Partitioning.

Chapter 3. Background Information on Partitioning

During installation partitioning will be done in two steps. The first step happens while installing the operating system (stage 1, see Section 2.4.3, “Preparing System for Automated Installation”), and the second step while installing your SAP product (stage 2, see Section 2.4.9, “SAP Product Installation”).

3.1. Stage 1: Partitioning for the Operating System

During stage 1 of the installation (see Section 2.4.3, “Preparing System for Automated Installation”), partitions for the operating system will be created.

A logical volume group (LVG) named system will be created. This LVG contains two logical volumes (LVs) named root_lv and swap_lv. The size of swap_lv will be calculated according to the SAP Note 1597355 (https://service.sap.com/sap/support/notes/1597355). For root_lv, 35 GB will be assumed at first, and the sum of root_lv and swap_lv will be displayed as Set the system volume size in GB.

You can change both, the size of the system volume (Set the system volume size in GB) and the size of the swap partition (Set the SWAP size in GB). When doing this, mind some caveats:

  • The size of the system volume could not exceed the physical size of the device minus 1 GB; 1 GB will be reserved for boot or for UEFI.

  • Better do not change the size of the swap partition.

  • root_lv should not be smaller than 5 GB.

[Note]Error Messages

Only if the size of the system volume (plus 1 GB) exceeds the phuysical size of the device or if the swap partition exceeds the size of the system volume, error messages are issued.

3.2. Stage 2: Partitioning for the SAP System

After installing the operating system the partitioning for the SAP system will take place. This can be done during stage 2 of the installation phase or in the running system.

The partitioning for the SAP system is not controlled by autoinst.xml that is used for the installation of the operating system. The autoinst functionality no longer exists in the running system. Instead the following files are controlling the partitioning for the SAP system:

In /etc/sap-installation-wizard.xml the <partitioning> tag defines for which SAP programs which files for controlling the partitioning are used. These files will be taken from /usr/share/YaST2/include/sap-installation-wizard/. In case there is no <partitioning> tag for the wanted SAP product, base_partitioning.xml will be used.

The files for controlling the partitioning are basically AutoYaST control files that contain a partitioning section only. There are several extensions:

  • If the <partitioning_defined> tag is set to true, the partitioning will be performed without any user interaction. This, for example, is preconfigured in files for controlling the partitioning of known hardware such as Dell, Fujitsu, HP, or IBM Server systems. If the SAP Installation Wizard recognizes this hardware, the appropriated file will be selected.

  • 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 be minimally (x-times (N) the size of the available memory (RAM)).

For all NW based products base_partitioning.xml will be used.

If you need something different (e.g., for TREX), proceed as follows:

  1. In /usr/share/YaST2/include/sap-installation-wizard/ create a new file for controlling the partitioning (e.g., TREX_partitioning.xml). You can base the new file on base_partitioning.xml and change it according to your needs.

  2. In /etc/sap-installation-wizard.xml, at the TREX following tag insert:

    <partitioning>TREX_partitioning.xml</partitioning>
[Warning]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 the Chapter 4.4 Partitioning of the AutoYaST Guide.

Chapter 4. Remote Installation from a Network Server

For detailed information about installing SUSE Linux Enterprise Server from a network server in general, see the Deployment Guide, Chapter 14, Remote Installation (the Deployment Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

The following section provides a short description about installing from a network server.

4.1. Installing with Installation Media from the Network

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

  2. Boot from DVD.

  3. Choose one of the boot menu options and edit the command line:

    1. remove the parameter instmode=cd from the command line

    2. change netsetup=0 to netsetup=1 and autoyast=file:/// to autoyast=http://example.com/sap_repo/, and

    3. add the parameter install=http://example.com/sap_repo.

    With netsetup=1 you will start the network.

This is all you need for a network installation. If you want to avoid using a DVD to bootstrap the system and boot from the network via PXE, read the AutoYaST Guide about setting up a PXE environment (the AutoYaST Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

4.2. Copying SAP Media Sets from a Remote Server with the Installation Wizard

It is possible to copy the SAP media sets from a remote server (NFS, SMB, etc.). For example, if you want to put the SAP media sets on an NFS Server, proceed as follows:

  1. Create a directory /srv/www/htdocs/sap_repo on your installation server.

  2. Edit the /etc/exports file on the installation server by adding the following:

    /srv/www/htdocs/sap_repo *(ro,root_squash,sync)
  3. In /srv/www/htdocs/sap_repo create a directory for every SAP media you have, for example kernel, java, maxdb, etc., which will give you a hint about the contents.

  4. Copy the contents of all SAP media with cp -a to the corresponding directory.

    [Tip]Avoid Copying on a Windows Operating System

    Do not copy the media on a Windows operating system because it may break permission settings and capitalization of files and directories.

Now you can install from the NFS server; e.g., from http://example.com:/srv/www/htdocs/sap_repo.

For information about installing SUSE Linux Enterprise Server from an NFS server, see the Deployment Guide, Chapter 14.2, Remote Installation and Section 14.2.2.

Chapter 5. SUSE Linux Enterprise Server for SAP Applications Components

SUSE® Linux Enterprise Server for SAP Applications consists of several components such as SUSE Linux Enterprise High Availability Extension, the Kernel page-cache limit feature, and an Installation Wizard, which are briefly explained in the following sections.

5.1. SUSE Linux Enterprise High Availability Extension

The SUSE Linux Enterprise High Availability Extension add-on is part of SUSE Linux Enterprise Server for SAP Applications.

For more information about SUSE Linux Enterprise High Availability Extension, see

5.2. Configuring SUSE Linux Enterprise Server for SAP Applications

5.2.1. Kernel: Page-Cache Limit

Problem

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

Some SAP solutions use large amounts of memory for accelerated access to business data. Parts of this memory are seldom accessed. When a user request then needs to access paged out memory, the response time is poor. It is even worse, when an SAP solution 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

A new kernel tune option has been introduced 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 once 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.

Two new 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, e.g.

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.

5.2.2. Ports Configuration

SAP applications require many open ports and port ranges in the firewall. The exact numbers depend on the selected instances, for example:

  • 3200-3399,

  • 3600,

  • 4700-4899,

  • 7200-7299,

  • 50000-59999.

It is also necessary to open 1128 and 1129 (TCP and UDP), and all the ports needed for the databases used (Oracle, DB2, MaxDB, Sybase).

[Warning]Firewall Activation

The firewall is disabled if you use the wizard, and enabled if you use the normal setup.

5.2.3. Important Log Files

The most important files for this product are:

  • Auto-installation related log files are in /var/adm/autoinstall/.

  • The installation wizard is a YaST module. Thus you will find wizard related log entries in /var/log/YaST/y2log.

  • We use a library for all SAP knowledge. Thus you will find related log entries in /var/log/SAPmedia.log.

5.3. The Installation Wizard

The Installation Wizard offers a guided installation path for both the SUSE Linux Enterprise Server operating system and the SAP applications.

Additionally, it includes an installation framework for 3rd party extensions.

The Installation Wizard consists of four parts:

  1. Installation of the operating system (SUSE Linux Enterprise Server).

  2. SAP Wizard Part 1: Copying all required SAP media to the local disk or use a shared storage medium.

  3. SAP Wizard Part 2: Collecting all parameters for the actual installation by querying the user interactively.

  4. SAP Wizard Part 3: Running the SAP Installer.

It is possible to run most of these parts separately. This way, very flexible installation scenarios are possible. Here are some examples:

  • Just prepare a machine with the operating system (SUSE Linux Enterprise Server) and run the SAP Wizard later.

  • Just prepare a machine with the operating system (SUSE Linux Enterprise Server), copy the SAP media, and collect the SAP installation parameters.

You can copy such an installation to other machines, maybe adjusting just a few SAP installation parameters. Then finally run the SAP Installer.

5.3.1. Supplement Media

The basic idea of the Supplement Media is to enable partners or customers to add their own tasks or workflows to the Installation Wizard.

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

5.3.1.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 5.3.1.2, “Own AutoYaST Ask Dialogs”

2

see Section 5.3.1.3, “Install 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 the details of other customization options, see the SLES AutoYaST Guide, Chapter 4.12. Custom User Scripts.

5.3.1.2. Own AutoYaST Ask Dialogs

For a general overview and details of the Ask feature of AutoYaST, see Chapter 4.17. Ask the User for Values During Installation of the SLES AutoYaST Guide (the AutoYaST Guide comes with the product or is available from http://www.suse.com/documentation/sles11/).

For the supplement 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 also 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 supplement 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>

5.3.1.3. Install 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 the SLES AutoYaST Guide, Chapter 4.5.6. Installing Packages during Stage 2. An example looks as follows:

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

5.3.1.4. Example Directory for the Supplement Media

# ls
/
|--product.xml

5.3.2. ClamSAP

ClamSAP is a new antivirus toolkit integration with the SAP Virus Scan Interface that improves cross-platform threat detection.

ClamSAP is a ‘C’ shared library to link between ClamAV and the virus scan interface of SAP (NW-VSI). A SAP application can use the ClamAV engine to scan for malicious uploads in HTTP uploads for example. If you want to use Virus Scan within SAP applications, you can use Virus Scan Interface in SAP (transaction VSCAN). There is an open source adapter for the ClamAV engine on http://freshmeat.net/projects/clamsap/. The library allows integration of ClamAV into SAP and works also on Unix, where most other anitvirus products do not run.

ClamAV is an open source (GPL) antivirus engine designed for detecting Trojans, viruses, malware, and other malicious threats. It is the de facto standard for mail gateway scanning. It provides a high performance multi-threaded scanning daemon, command line utilities for on-demand file scanning, and an intelligent tool for automatic signature updates. For more information, see http://www.clamav.net.

Appendix A. Downloading CryptoAddOn (SAPCryptoLib)

Starting with SAP NetWeaver 7.03/7.3 the cryptographic functionality is already included in the SAP NetWeaver DVDs for most countries and does not have to be specified separately. In case the cryptographic functionality is not included, download the SAPCRYPTOLIB and follow the documentation on how to install the library: Installing the Cryptolib.

SAPCRYPTOLIB is available to entitled customers and partners on http://www.service.sap.com/swdc. Click Installations and Upgrades+Browse our Download Catalog+SAP Cryptographic Software. If you are an SAP customer or partner, contact the SAP subsidiary in the country from which you want to download the library, e.g. by opening a message on Service Marketplace under component XX-SER-SWFL-EXPORT asking for access to this section of the download area. You will be provided with the instructions required to download the package. You need the package for platform linux-x86_64-glibc2.3.

[Tip]Renaming Downloaded File

It might be necessary to rename the downloaded file to SAPCRYPTO.SAR.

[Important]

If you are not an SAP partner yourself but rather working together with an SAP partner, contact your partner to get access to the required archive. Be aware that the installed server must not cross a border in order to avoid violating export regulations.

Appendix 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. October 28, 2013

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

Chapter 2, Default Installation Scenarios

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

Chapter 3, Background Information on Partitioning

New chapter.

Appendix B, Documentation Updates

New appendix.


SUSE Linux Enterprise Server for SAP Applications The Guide 11 SP3