1. • On AMD64/Intel 64, boot from the installation media. From the boot menu, select Installation.

   • On POWER, follow the instructions in the SUSE Linux Enterprise Server documentation, see Deployment Guide, Part “Installation Preparation”, Chapter “Installation on IBM POWER” (https://documentation.suse.com/sles-15).

   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. As the first step, the installation workflow will check for updates for itself. After that, it will be ready to start the installation.

2. Select the default system language under Language.

   

   Figure 3.1: Language, keyboard and product selection #

     

3. Select the appropriate keyboard layout under Keyboard Layout. To test whether the selected layout matches your physical keyboard, use the text box Keyboard Test.

4. SLE 15 SP6 provides a single installation ISO for the entire product line. Therefore, you need to select the product to install on this page.

   Under Product to install, choose SUSE Linux Enterprise Server for SAP Applications 15 SP6.

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

6. (Optional) If automatic network configuration via DHCP fails, the screen Network Settings will open.

   However, if the Registration screen appears instead, this indicates that your network connection works. To change network settings anyway, click Network Configuration.

   When you are finished configuring networking, proceed with Next.

   

   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 information about configuring networking, see Administration Guide, Chapter “Basic Networking”, Section “Configuring a Network Connection with YaST” (https://documentation.suse.com/sles-15).

7. On the screen Registration, enter your E-mail Address and Registration Code. Successful registration is a prerequisite for receiving product updates and the entitlement to technical support.

   Proceed with Next.

   

   Important: Register at this step

   Make sure to register your system at this step in the installation. Otherwise, you can only install a minimal SLE system and will not receive updates.

   To install a full (but not updated) SLES for SAP system without network access during the installation, use the SLE 15 SP6 Packages ISO image from https://download.suse.com. You can then choose Skip registration on this page and select the SLE 15 SP6 Packages ISO image as an add-on product on the next page.

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

9. After the system is successfully registered, YaST lists available modules for SUSE Linux Enterprise Server for SAP Applications from the SUSE Customer Center. The default selection covers the most common cases. To enable an additional module, activate its entry.

   

   Note: Release notes

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

   Proceed with Next.

10. (Optional) The Add On Product dialog allows you to add additional software sources (so-called “repositories”) to SUSE Linux Enterprise Server for SAP Applications that are not provided by the SUSE Customer Center. Such add-on products may include third-party products, drivers or additional software for your system.

11. Choose the System Role. System roles are predefined use cases which tailor the system for the selected scenario. For SUSE Linux Enterprise Server for SAP Applications, you can choose between:

    • SLES for SAP Applications: Default, recommended for most situations. This system role contains the following properties:

      • Supports the installation wizard for SUSE Linux Enterprise Server for SAP Applications.

      • Enables RDP access (Remote Desktop Protocol).

      • Provides special partitioning recommendations.

    • SLES with GNOME: Can be necessary in specific cases. This installation path is not covered in this document. For more information about this installation path, see Installation Quick Start, Section “Installing SUSE Linux Enterprise Server” (https://documentation.suse.com/sles-15).

    Additional system roles are available for specific use cases (High Availability, text mode, minimal, and KVM/XEN virtualization hosts).

    Proceed with Next.

    

    Figure 3.2: System role #

      

1. Choose whether to enable the following options:

   • To install an SAP Application along with the system, activate Launch the SAP Installation Wizard right after the operating system is installed.

   • To enable RDP access (Remote Desktop Protocol) to this machine, activate Enable RDP service and open port in firewall.

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

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

3. Select the clock and time zone to use on 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 “Installation with YaST”, Section “Clock and Time Zone” (https://documentation.suse.com/sles-15).

   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.

   If you want to enable passwordless authentication via SSH login, you can import a key via Import Public SSH Key. If you want to completely disable root login via password, upload a key only and do not provide a root password. A login as system administrator will only be possible via SSH using the respective key in this case.

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

   Proceed with Next.

   

   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. The password entered here cannot be retrieved later.

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 appropriate headline or other underlined items.

   

   Figure 3.3: Installation settings #

     

6. When you are satisfied with the system configuration, click Install.

   

   Warning: Deletion of data

   The installation process fully or partially overwrites existing data on the disk.

   In the installation confirmation box, click Install.

   When the installation of 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 now, the installation will continue after a reboot. Continue with Chapter 4, Installing SAP applications.

1. When the system is booted, it displays the screen Welcome. Proceed with Next.

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

   When you are finished configuring networking, proceed with Next.

   

   Important: Configure networking as recommended by SAP

   Make sure to configure the network connection according to the documentation of your SAP application.

   For information about configuring networking, see Administration Guide, Chapter “Basic Networking”, Section “Configuring a Network Connection with YaST” (https://documentation.suse.com/sles-15).

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

3. Choose one of the following options:

   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

   Create an SAP HANA file system on SAP BusinessOne-certified hardware.

   

   Important: Hardware requirements

   Make sure your machine fulfills the hardware requirements for SAP HANA detailed in Section 2.1, “Hardware requirements”. 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.

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.

   

   Figure 4.1: Location of SAP installation master #

     

   Select the appropriate option from the drop-down list. 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]

   If you have installed an SAP application 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 list below Choose an installation master.

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

   Collect installation profiles for SAP products but do not execute installation

   Use this option to set the installation parameters, but not perform the actual installation. With this option, the SAP Installer (SAPinst) will stop without performing the actual SAP product installation. However, the steps that follow fully apply.

   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 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. On the screen SAP Installation Wizard, provide the location of additional Installation Media you want to install. This can include an SAP kernel, a database and database exports.

   Copy a medium

   Specify a path to additional Installation Media. For more information about specifying the path, see Table 4.1, “Media source path”.

   Skip copying of medium

   Do not copy additional Installation Media. Choose this option if you do not need additional Installation Media or 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 copy the relevant files to your local hard disk.

   

   Figure 4.2: SAP Installation Wizard: additional Installation Media #

     

4. After copying the Installation Media, you will be asked whether you want to prepare additional Installation Media. To do so, click Yes. Then follow the instructions in Step 3.

   Otherwise, click No.

5. In 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.

   SAP standalone engines

   Engines that add functionality to a standard product: SAP TREX, SAP Gateway and Web Dispatcher.

   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 can be used to install the same product in a very similar configuration on different systems.

   

   Figure 4.3: SAP Installation Wizard: installation type and database #

     

6. If you selected SAP Standard System, Distributed System or SAP High-Availability System, additionally choose a back-end database under Back-end Databases.

   Proceed with Next.

7. 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, select the product you want to install.

   Proceed with Next.

   

   Figure 4.4: SAP Installation Wizard: choose a product #

     

8. You will be asked whether to copy Supplementary Media or Third-Party Media. To do so, click Yes and then follow the instructions in Step 3.

   Otherwise, click No.

   

   Note: Difference between Supplementary Media/Third-Party Media and additional software repositories

   Both types of delivery mechanisms allow installing software that is neither part of the SUSE Linux Enterprise Server for SAP Applications media nor part of your Media Set from SAP. However, the delivery mechanism is different:

   • Supplementary Media/Third-Party Media is installed using an AutoYaST file which allows creating an installation wizard and custom installation scripts.

   • Additional software repositories are RPM package repositories that you will remain subscribed to. This means you receive updates for Third-Party Media along with your regular system updates.

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

   Proceed with Next.

   

   Note: Location of copied SAP media

   At this point, all data required for the SAP installation has 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:

   > 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. Depending on the product you are installing, one or more dialogs will prompt you to supply values for several configuration parameters for the SAP application you are installing.

    Supply the values as described in the documentation provided to you by SAP. Help for the configuration parameters is also available on the left side of the dialog. For more information, see Section 2.5, “Required data for installing”.

    Fill out the form (or forms), then proceed with OK.

    

    Figure 4.5: Product parameters #

      

    When you are done, the SAP Installation Wizard will download additional software packages.

11. You will be asked whether to continue the installation or prepare another SAP product for installation. If you choose to prepare another SAP product, start from the beginning of this procedure.

12. (Optional) When installing SAP HANA on a system that is not certified for SAP HANA and does not meet the minimum hardware requirements for SAP HANA TDI (Tailored Datacenter Integration), you will be asked whether to continue. If you receive this message unexpectedly, check Section 2.1, “Hardware requirements” and the sizing guidelines from SAP at https://service.sap.com/sizing (you need your SAP ID to access the information).

    Otherwise, continue with Yes.

13. The following steps differ depending on the type of SAP application you are installing:

    • When installing an SAP HANA database, SAP HANA will now be installed without further question.

    • When installing an SAP NetWeaver application, the actual installation will be performed using the SAP Installer (SAPinst). After a few seconds, SAP Installer will open automatically.

      Follow the SAP Installer as described in the documentation provided by SAP. Most configuration parameters are correctly filled already.

    

    Figure 4.6: SAP Installer: defining parameters #

      
    

    Tip: Installation log files

    If the installation of the SAP application fails, refer to the installation log files. They are located in /var/adm/autoinstall. Failed installations are recorded in files with names ending in .err.

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.

    Click Finish.

Ensure passwordless SSH access between the two nodes (primary and secondary) for root. Keep in mind, some cloud service providers might not have set up SSH access for the root by default.

1. Install the yast2-hana-update package on both nodes:

   # zypper install yast2-hana-update

   After the installation, you can find the module SUSE HANA Cluster Update in the YaST Control Center.

2. On the secondary node, start the YaST Control Center and open the SUSE HANA Cluster Update module.

3. In the YaST module, review the prerequisites. Make sure to fulfill all of them before continuing with the next step. Keep in mind that the wizard supports only the HANA Scale-up Performance Optimized scenario.

4. To upgrade the SAP HANA system, select the secondary node.

5. Select the location of the installation medium.

   Point to the location where the SAP medium is located. If wanted, check Mount an update medium on all hosts and provide the NFS share and path.

   

   Important: Differences between SAP HANA version 1.0 and 2.0

   If you are upgrading from SAP HANA version 1.0 to version 2.0, make sure to check This is a HANA 1.0 to HANA 2.0 upgrade.

   The YaST module will copy the PKI SSFS keys from the former secondary node to the former primary node. More information is available through the Help button.

1. Review the update plan generated by the wizard.

   The wizard shows you two steps: automatic and manual. In this automatic step, the wizard puts cluster resources into maintenance mode before it starts with the automatic steps. The manual steps are SAP HANA-specific and need to be executed by an SAP HANA administrator. For more information, see the official SAP HANA documentation.

2. Update the SAP HANA software.

   The wizard executes the automatic actions and waits until the SAP HANA administrator performs the SAP HANA upgrade.

3. Perform the SAP HANA upgrade.

4. Review the plan for the primary (remote) node.

   After the SAP HANA upgrade is done, the wizard shows the update plan. When you continue with this step, the wizard turns the primary node into a secondary node to make it ready for the upgrade.

   Keep in mind that this step can take some time.

1. Update the former primary node.

   Pay special attention to the --hdbupd_server_nostart option in this step.

2. Restore the previous state of the cluster.

   By default, the wizard registers the former master as now being secondary on the SAP HANA system replication. If you want to revert the system replication to its original state, click the Reverse button.

3. Review the update summary.

   You can review the original and current SAP HANA versions and the cluster state.

   

   Note: Dealing with intermediate cluster state

   If the wizard is faster than the status update of the cluster resources, the summary shows an intermediate cluster state. The cluster state is UNDEFINED or DEMOTED.

   To overcome this, check the cluster status again with the command SAPHanaSR-showAttr and make sure the former secondary node is now in the state PROMOTED.