You are on page 1of 9

Server preparation details - Linux Supported O/S - LINUX REDHAT EL6/X86_64 64BIT 1.

Supportability prerequisites

In order for your SAP system to be fully supported on Red Hat Enterprise Linux 6, the following prerequisites must be fulfilled (this list is not exclusive, other notes may apply): You need to use the RHEL 6 server variant. You need to have valid support and update entitlements ("subscriptions") from Red Hat for Red Hat Enterprise Linux 6 and any additional layered components (e.g. Virtualization, Clustering, Cluster Storage). Red Hat recommends to get "RHEL for SAP Business Applications" subscriptions for all RHEL6 servers running SAP applications. Go to http://www.redhat.com/products/enterprise-linux/for-sap/ for more information. Please contact your local Red Hat sales representative to purchase RHEL subscriptions. Your machine must be able to retrieve additional software and updates from "Red Hat Network" (RHN) either directly via HTTP or an RHN proxy or through a RHN Satellite server. You need to use hardware that is certified for SAP use on Linux by your hardware vendor. See the respective notes on certified hardware which are listed in SAP note 171356. You can use any Linux kernel version shipped by Red Hat for Red Hat Enterprise Linux 6 You can use any glibc version shipped by Red Hat for Red Hat Enterprise Linux 6 It is recommended to always install the latest available patches and quaterly updates. Please note that Red Hat Enterprise Linux 6 does not support the Intel Itanium platform.

2. RHEL Linux 6 Installation options When asked to customize the software selection, choose "Basic Server" and then select the "Customize now" option. It is recommended to select the software groups

listed in the following at a minimum for an SAP server machine. When customizing the list of optional packages for a software group, keep the packages selected by default and add packages eventually listed with the group. This is the list of categories/groups that should be selected during installation: Base System Base Compatibiliy Libraries Debugging Tools Directory Client Hardware Monitoring Utilities Large Systems Performance Network File System client Perl support Storage Availability Tools Desktops X window system Development Development tools (only required when installing SAP with Oracle DB)

Please make sure that the following packages are always included in the list of packages selected for installation:

uuidd

3. Configuration steps necessary after the initial OS installation

3.1 Firstboot

When you first boot your system you will be presented with "firstboot", a post installation configuration tool: If you leave the firewall enabled, you need to open up the ports for your SAP product either in firstboot if you already know them or by e.g. using the systemconfig-firewall tool at a later point. These ports are listed during the installation of the SAP software but can also be found in /etc/services after it is installed. Red Hat Enterprise Linux uses SELinux technology for additional security which is enabled by default. Because several components of an SAP server system (like the installation tools or some underlying RDBMS) are not aware of SELinux, we recommend setting it to "Permissive" for the time being so that these components won't break. We don't recommend setting it to "Disabled" as this would require relabeling the whole filesystem if you want to enable it again at a later point for additional security when these components are made compatible or suitable procedures exist to make them function properly with SELinux. You can change SELinux settings by editing /etc/sysconfig/selinux for future boot processes. On a running system, you can switch between "Enforcing" and "Permissive" modes using the command "setenforce". If you can access an NTP time server from the machine, we strongly recommend choosing "Enable Network Time Protocol" in the "Date and Time" dialog to keep all SAP applications servers' time and date synchronized. You have to register the system in the Red Hat Network (RHN) to retrieve update packages for your machine. It is recommended that you update all program packages (including kernel and glibc) to the latest version available on RHN after the first OS installation and at regular intervalls later on.

3.2 Hostname

Ensure that the system hostname is set to the short name as described above, i.e. both commands "hostname" and "hostname -s" must return the hostname without domain, "hostname -f" must return the fully qualified hostname and domain:

# hostname sapserver1 # hostname -s sapserver1

# hostname -f sapserver1.example.com

To do that, check that HOSTNAME is set to the short name without domain in /etc/sysconfig/network:

# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=sapserver1 ...

Also set up /etc/hosts so that it is configured similar to the following example:

# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost

192.168.0.1 sapserver1.example.com sapserver1 (any additional hosts should be added after these two lines)

It is important that the fully qualified domain name is in the second column, followed by any alias names and that the hostname of the machine is not associated with the IP address 127.0.0.1.

If you entered the fully qualified hostname during installation you can run the command 'hostname <shorthostname>' to set the short hostname without having to reboot the system.

3.3 Linux kernel parameters Some Linux kernel parameters have to be adjusted to meet the requirements of SAP software.To do this append the following lines to /etc/sysctl.conf, or change the

already existing parameters accordingly (these are the required minimum values, higher values are okay as well):

# SAP settings kernel.msgmni=1024 kernel.sem=1250 256000 100 1024 vm.max_map_count=1000000

Run the command "sysctl -p" to activate the modified kernel parameters. 3.4 Process resource limits

Some components (e.g. the SAP J2EE engine, Oracle RDBMS software, ...) need to keep a large number of file handles opened simultaneously. You need to increase the limit of files one process can open at a time by extending /etc/security/limits.conf with the following lines:

@sapsys @sapsys @dba @dba

hard soft hard soft

nofile nofile nofile nofile

32800 32800 32800 32800

Please logout and login again for these settingss to take effect.

With these settings the users in the sapsys group (J2EE engine) and the dba group (Oracle) can open up to 32800 files simultaneously. If needed, adjust these lines to match your setup. Please refer to the comments in said file for information about its format.

By default RHEL 6 limits the number of simultaneous processes for each user to 1024 to prevent so called "fork-bomb" attacks. This can cause problems when running multiple SAP JAVA app server instances under the same userid. If you plan to run such a setup on RHEL6, please also add the following line in /etc/security/limits.conf: @sapsys soft nproc unlimited

To ensure that the process resource limits also get adjusted when the SAP system is started via sapcontrol or a web service client (e. g. SAP MMC) please make sure to adjust the limits in the file /usr/sap/sapservices as described in SAP note 1437105. You can determine if your system is under control of sapcontrol by checking if its start command is contained in /usr/sap/sapservices.

4. YUM groups The following yum groups correspond to the groups listed for the installation program above:

base compat-libraries debugging directory-client hardware-monitoring large-systems network-file-system-client perl-runtime storage-client-multipath x11 development (only required when installing SAP with Oracle DB)

5. Additional RHEL parameters for installation with Sybase ASE At least Sybase ASE 15.7 is required.

Some additional kernel parameters have to be adjusted for Sybase ASE to work on RHEL 6: kernel. randomize_va_space=0 kernel. exec-shield=0

Please add those two lines to /etc/sysctl. conf and activate the new settings with "sysctl -p".

6. UUIDD RPM package Please update to latest available e2fsprogs/libuuid/uuid-runtime/uuidd RPM package for your Linux operating system. On SLES 11 and all RHEL and OL releases make sure to afterwards activate the UUID daemon (see below).

7. System language You must select English as the operating system language on all Linux hosts that are running SAP software.

8. Swap space While the Linux distribution is being installed, create partitions of the type "swap" when you organize the hard disk(s). Physical Memory (RAM) < 32 GByte 32 - 63 GByte 64 - 127 GByte 128 - 255 GByte 256 - 511 GByte Recommended Swap-Space

2 x RAM 64 GByte 96 GByte 128 GByte 160 GByte

512 - 1023 GByte 1024 - 2047 GByte 2048 - 4095 GByte 4096 - 8191 GByte > 8192 GByte

192 GByte 224 GByte 256 GByte 288 GByte 320 GByte

When running SAP systems, the use of Linux swap-space is mandatory. SAP recommends to setup a dedicated swap-partition on a fast storage, like a system internal HDD, RAID-Array, SSD or a LUN in a SAN. 9. Additional recommendation about RPM packages SAP recommend that you import the latest available "Service Pack" (Novell SUSE), the latest "Minor Release" (Red Hat), or the latest "Update" (Oracle Linux). You should use the latest available installation media when you are installing this. If an update does not work unexpectedly, return to the last "Service Pack", "Minor Release", or "Update" that worked.

10.O/S Users : User root <sapsid>adm <dasid>adm sapadm SAPSR3DB syb<dbsid> Group group sapinst is assigned as secondary group sapsys (sapinst as secondary group) sapsys (sapinst as secondary group) sapsys (sapinst as secondary group) db<dbsid>mon sapsys (sapinst as secondary group)

11. File System Partition: /sapmnt/<SID> -- For Application 10 GB

/usr/sap/<SID> /usr/sap/trans on the go /sybase

-- For Application -- For Application -- For database

10 GB 05 GB -- May need to increase 90 GB

12. Ports to be Open: R/3 Sevice Name TCP Port Dispatcher 3200/TCP SAP Gateway 3300/TCP Message server 3600 SAProuter Listener Sapinst GUI Server HTTP Server Sybase DB Port 21212 4239 2638 2360 21200 Default TCP Service Name sapdp00 sapgw00 sapms<SID> 3299 Default

You might also like