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

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

(*) not required for TREX.

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

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 #

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://launchpad.support.sap.com/#/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.

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 #

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.

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 #

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.

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

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

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 #

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.

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.3.2, “Ports Configuration”.

After an automatic reboot and applying previously supplied 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.

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.

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://documentation.suse.com/sles/11-SP4/).

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.

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:

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.

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.

For more information, see:

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

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.

The most important files for this product are:

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.

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

<?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>

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

# ls
/
|--product.xml

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). An 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 at http://freshmeat.net/projects/clamsap/. The library allows integration of ClamAV into SAP and works also on Unix, where most other antivirus 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.