SAP ERP 6 EHP5 - Installation Java Linux

> SAP ERP

In Progress

1 - About

SAP ERP 6.0 is new name of the application formerly known as mySAP ERP 2005.

New Installation of SAP ERP 6.0 with Enhancement Packages (EHP) on a central system architecture (Chapter 3 of the master guide - Installation of an Enhancement Package - Scenario B).

3 - SAP Note

More SAP Installation Notes can be found in the installation guide.

Advertising

4 - Central system Architecture

A central system is installed on a single host.

These are the following instances:

  • Central instance (Primary Application Server Instance). Every SAP system must have one primary application server instance (central instance).
  • Central services instance. The central services instance – central services instance for Java (SCS instance) and central services instance for ABAP (ASCS instance) – forms the basis of communication and synchronization for the Java and ABAP clusters.
  • Database instance (DB instance). The database instance is a mandatory installation component for the installation of an SAP system. ABAP and Java each have their own database schemas.

In a central system, all mandatory instances are installed on one host.

You have other options such as:

  • Distributed System (In a distributed system, every instance can run on a separate host)
  • High Availability (In a high-availability system, every instance run on a separate host with redundancy.)

5 - Hardware and Software Requirements

5.1 - Prerequisite Checker

To check the hardware and software requirements, you use the Prerequisite Checker in one of two modes:

  • Standalone mode (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 25].

  • Integrated in SAPinst (mandatory) during the installation process

When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the hardware and software requirements in the background.

For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.

The paragraph “3.2.2 Hardware and Software Requirements Tables” (page 25 of the installation guide) gives a table with all checks that are perform by the tool.

Advertising

5.2 - Product Availability Matrix

Check the Product Availability Matrix for supported:

Test the network connection to the database server with the following command:

ping -c 10 <db_server_name>

5.3 - Network

For smaller SAP Systems, the SAP server uses only one network adapter for communicating with the SAPgui frontends. Since the network load is very low through SAPgui frontends, you do not need to connect the SAP server using several, physically separate subnets (network adapters). Dividing up the rest of your network into subnets is possible and also useful. High data traffic only occurs locally on the SAP server between the database and the central instance

5.3.1 - SAP Host Name

The host name must be assigned before you install the SAP System. SAP does not support a name change after installation.

If you use only one network card, the host name must match the IP name that is assigned to this network card.

611361. The naming of hosts running SAP software has to be done according to general standards (RFCs see http://ietf.org/rfc) and some SAP specific restrictions.

  • Alphanumerical string of alpha characters [A-Z] and [a-z] and digits [0-9] and the hyphen (or minus) character “-”.
  • Recommend hostnames to begin with an alpha character.
  • The period character “.” is only allowed to delimit components of domain names like (sapc11.sap.com).
  • Maximum length of the hostname up to 13 characters
  • must not begin with S-[0-9] (e.g. hostname S-12345 is not allowed. 998631
  • Hostnames must be considered “case sensitive”
  • On multihomed hosts the hostname must be assigned to the IP address of the primary network interface. 21151
Advertising

5.3.2 - Multiple network adapters

The hostname of an SAP Application Server (i.e. the output of the command “hostname”) must be assigned to the IP address of the network interface in item 1).

5.4 - Linux Installation

5.4.1 - Linux Kernel Parameters

For more information about the Linux kernel versions certified by SAP, see SAP Note 171356. .

To check the Linux kernel parameters for your Linux distribution see one of the following SAP Notes:

Distribution SAP Note
RHEL5 1048303
RHEL6 1496410
SLES10 958253
SLES11 1310037

If you are using a Linux kernel version certified by SAP, you do not need to modify the Linux kernel.

5.4.2 - LDAP

If you want to use LDAP, you need the LDAP libraries that are usually installed with the openldap RPM. To check this, enter the following command:

rpm -qa | grep openldap 

Make sure that the output of this command contains at least one of the following RPM packages: * Red Hat Linux: openldap2 * SUSE LINUX: openldap2 or openldap2–client

5.4.3 - National Language Support

Make sure that National Language Support (NLS) and corresponding saplocales are installed. To display available locales, enter the following command:

locale -a

Check the output for locales such as the following:

de_DE, en_US

SAP blended Code Pages are available as an attachment of SAP Note 171356.

For more information about NLS on Linux, see SAP Note 187864.

5.4.4 - Operating system language

For the installation, you must choose English as the operating system language on all Linux hosts that run SAP software.

5.4.5 - Routing information

To check routing information, enter the following command:

netstat -r

5.4.6 - Shared Memory File System

To check the size of the shared memory file system, enter the following command:

df –k /dev/shm

5.4.7 - Activated Hardware Drivers

To check the activated hardware drivers, enter the following command:

lsmod

5.4.8 - Login shell

SAPinst only prompts you for this parameter if you use a login shell other than the recommended C shell (csh). For more information, see SAP Note 202227.

5.4.9 - Compiler

To check that the C compiler gcc is installed, enter the following command:

rpm -qa | grep gcc 

Make sure that the output of this command contains a gcc RPM package.

5.4.10 - Operating System Users and Groups

During the installation, SAPinst checks all required accounts (users, groups) and services on the local machine. SAPinst checks whether the required users and groups already exist. If not, it creates new users and groups as necessary. If you do not want SAPinst to create operating systems users, groups, and services automatically, you can optionally create them before the installation. This might be the case if you use central user management such as Network Information System (NIS).

5.4.11 - Swap Space

While the Linux distribution is being installed, create partitions of the type “Swap” when you organize the hard disk(s).

Recommended total size: Twice the main memory structure (2 x RAM). According to Note 153641, a swap space of 20 GB is generally sufficient on 64-bit Linux for operating an SAP system (including the database).

For earlier 32-bit Linux versions, the maximum size of a swap partition is 2 GB, but if you require more space, distribute the swap space over multiple swap partitions.

The Linux kernel does not usually require much swap space, since other limits have already been reached before the swap space has reached full capacity (“late swap allocation”).

However, if you discover that more swap space is required when using SAP software, you can use the distribution-specific tools to increase your swap space at any time.

Swap Space:

  • Twice the main memory structure (2 x RAM) with a maximum of 20 GB per SAP application server instance.
  • In addition, for the database instance, you need
    • Recommended: 3*RAM + 500 MB, at least 20 GB
    • Minimum: 2*RAM

5.5 - Hardware

  • CPU. at least one dual core CPU or two single core CPUs.
  • Hard Disk Space:
    • 4.3 GB of temporary disk space for every required installation DVD that you have to copy to a local hard disk.
    • 1.2 GB of temporary disk space for the installation.
    • Instance-specific Requirements:
      • Central services instance for Java (SCS). 2 GB
      • Enqueue replication server instance for the SCS (high-availability only). 2 GB
      • Database Instance: Minimum 150 GB
      • Central instance: 12 GB
      • Dialog instance: 12 GB
      • Host agent: 1 GB
      • Diagnostics agent: 1.5 GB
  • RAM. If you install several instances on one host, you have to add up the requirements accordingly.
    • Central services instance for Java (SCS) Minimum 1 GB
    • Enqueue replication server instance for the SCS (high-availability only) Minimum 1 GB
    • Database Instance: Minimum 2 GB (The default value used by SAPinst is 50 percent of the entire RAM)
    • Central instance: Minimum 4 GB
    • Dialog instance: Minimum 4 GB
    • Host agent: 0.5 GB
    • Diagnostics agent: 1 GB

To display RAM size in KB, enter the following linux command free.

5.5.1 - Quick Sizer

If you want to install a production system, the values provided by the Prerequisite Checker and the hardware and software requirements check-lists are not sufficient. In addition, you can use the Quick Sizer tool.

For more information about the Quick Sizer and available sizing guides, see the Master Guide SAP NetWeaver 7.0 at Planning.

The sizing depends on:

  • The set of applications to be deployed
  • How intensively the applications are to be used
  • The number of users

6 - Media

6.1 - How to get them ?

You normally obtain the installation media as part of the installation package from SAP. However, you can also download installation media from the software distribution center on SAP Service Marketplace using this path: SAP Service Marketplace > A–Z Index > Installations and Upgrades > Letter E > Sap ERP > SAP ERP ENHANCE PACKAGE“ EHP4 FOR SAP ERP 6.0 / NW7.01 > IDES Version > Linux > Oracle.

To download software, use Download Manager to download multiple files at once or to schedule downloads for a later time.

  1. Collect files in your Download Basket first;

As an alternative to downloading software from the SAP Software Distribution Center, you can also order software on CD or DVD from the SAP Software Shop in the SAP Service Marketplace. For more information, see the SAP Software Distribution Center at Ordering SAP Software or http://service.sap.com/softwarecatalog. If you experience problems or have questions relating to purchasing software, you can create a customer message for component XX-SER-SWFL- SHIP.

6.2 - Identification of the media

All download objects can be identify that belong to one installation DVD according to one or both of the following:

  • Material number

All download objects that are part of an installation DVD have the same material number and an individual sequence number:

<material_number>_<sequence_number>

Example:

51031387_1
51031387_2
...
  • Title

All objects that are part of an DVD have the same title, such as <solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.

6.3 - Required Media

Installation media needed are:

  • The SAP Installer (Installation Master),
    • 51034992_8 - ERP 6.0 SR3 IDES Installation Master Linux on X86_64 64bit
  • The Export DVDs (The IDES data),
    • 51034985 - IDES SAP ERP 6.0 SR3 Inst. Export
  • The Java Component,
    • 51033513 - NW 7.0 SR3 SP14 Java based SW Comp.
    • 51033526 - BS 2005 SR3 Java Components (BS Java components)
  • The Kernel,
    • 51033508_1 - NW 7.0 SR3 Kernel 7.00 Linux on x86_64 64bit
  • The SAP GUI
    • 50102369 - NW 7.0 Presentation - 7.20 Compilation 2 Present.
  • The Database
    • 51031676_1 to 4 - DVD ORACLE RDBMS 10.2 LINUX_X86_64
    • 51036968_3 - ORACLE RDBMS Patch 10.2.0.4 Linux on X86_64 64bit
SAP Instance Installation Required DVD
SCS instance Installation Master DVD
Kernel DVD
Central instance, dialog Instance Installation Master DVD
Kernel DVD
SAP NetWeaver Java DVD
RDBMS Client DVD
Java Components for SAP ERP, SAP CRM, SAP SCM, SAP SRM DVD
Database instance Installation Master DVD
Kernel DVD
SAP NetWeaver Java DVD
Java Components for SAP ERP, SAP CRM, SAP SCM, SAP SRM DVD
RDBMS DVD
RDBMS Patch DVD (if available)

7 - SAP Directory

SAP Directories page 48

8 - Basic SAP System Installation Parameters

SAPinst prompts for input parameters during the Define Parameters phase of the installation. You can install your SAP system either in:

  • Typical. If you choose Typical, you perform the installation with default settings. This means that you only have to respond to a small selection of prompts.
  • or Custom mode. If you choose Custom, you are prompted for all parameters.

At the end, you can still change any of the parameters on the Parameter Summary screen.

The basic system parameters that you need to specify before installing your SAP system are classified in three categories:

  • SAP System Parameters
  • SAP System Database Parameters
  • Diagnostics Agent Parameters

To have more information on all installation parameters, use the F1 help in the SAPinst screens or go to the documentation section “3.4 Basic SAP System Installation Parameters”

8.1 - SAP System Parameters

8.1.1 - SAP System ID <SAPSID>

The SAP System ID <SAPSID> identifies the whole SAP system. Choose your SAP system ID carefully. You cannot change the SAP system ID after the installation..

Make sure that your SAP system ID:

  • Is unique throughout your organization. Do not use an existing <SAPSID> when installing a new SAP system. EXAMPLE: If you have already installed an ABAP system and you want to install a new Java system on the same host, make sure that you enter a <SAPSID> that is different from the <SAPSID> of the existing ABAP system.
  • Consists of exactly three alphanumeric characters
  • Contains only uppercase letters
  • Has a letter for the first character
  • Does not include any of the following, which are reserved IDs:
ADD ALL AMD AND ANY ARE ASC AUX AVG BIT CDC COM CON DBA END EPS FOR GET GID 
IBM INT KEY LOG LPT MAP MAX MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW 
REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP UID USE USR VAR
  • If you want to install a dialog instance, make sure that no gateway instance with the same SAP system ID (SAPSID) exists in your SAP system landscape.

8.1.2 - SAP System Instance Numbers

Technical identifier for internal processes:

  • It consists of a two-digit number from 00 to 97.
  • The instance number must be unique on a host.

That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers. If you do not enter a specific value, the instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system to be installed or to SAP systems that already exist on the installation host.

To find out instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with <nn> of local (not mounted) /usr/sap/<SAPSID> directories.

The value <nn> is the number assigned to the instance.

8.1.3 - Master Password

Common password for all users created during the installation:

  • Operating system users (for example <sapsid>adm)

If you did not create the operating system users manually before the installation, SAPinst creates them with the common master password. In this case, make sure that the master password meets the requirements of your operating system and of your database.

  • Java users (for example Administrator)
  • Database users (for example ora<dbsid>
  • Secure Store key phrase For more information, see Key Phrase for Secure Store Settings.

Password policy: The master password:

  • Must be 8 to 14 characters long
  • Must contain at least one letter (a-z, A-Z)
  • Must contain at least one digit (0-9)
  • Must not contain \ (backslash) and ” (double quote)

Depending on the installation option, additional restrictions might apply (for example, the master password must not contain the name of a Java user created during the installation).

8.1.4 - Message Server Port

The message server port number must be unique for the SAP system on all hosts. If there are several message port numbers on one host, all must be unique.

Port number of the SAP Message Server: If you do not specify a value, the default port number is used.

The SCS instance profile contains the configuration for the Java message server. The Java message server port uses the parameter rdisp/msserv_internal with default value 39<nn>, where <nn> is the instance number of the SCS message server instance. For more information about the parameters used for message server ports, see SAP Note 821875.

8.1.5 - Java Development Kit (JDK)

A valid JDK 1.4.2 is required for the Java application server. For more information about JDK versions supported by SAP and about how to install them, see Installing the Java Development Kit [page 59].

8.1.6 - Java(TM) Cryptography Extension (JCE)

You have to download the JCE Unlimited Strength Jurisdiction Policy Files 1.4.2 archive for the SAP system. For more information, see Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive [page 60].

8.1.7 - Key Phrase for Secure Store Settings

This is a random word or phrase that is used to encrypt the secure store.

The Java EE engine uses this phrase to generate the key that is used to encrypt the data. The uniqueness of the phrase you use contributes to the uniqueness of the resulting key.

If you choose Typical mode, SAPinst sets the master password for the key phrase. In this case, make sure that you replace the master password with the required unique key phrase either in the Parameter Summary screen or after the installation has finished.

8.1.8 - DNS Domain Name for SAP System

If you want to use HTTP-based URL frameworks such as Web Dynpro applications, you have to specify the DNS domain name for the SAP system.

The DNS Domain Name is used to calculate the Fully Qualified Domain Name (FQDN), which is configured in profile parameter SAPLOCALHOSTFULL.

The DNS Domain Name is needed to define the URLs for the ABAP and Java application servers. It is appended to the server name to calculate the FQDN. For more information, see SAP Note 654982.

8.1.9 - User and Management (UME)

Before you add a newly installed SAP system to your system landscape, you must decide which kind of user management you want to use:

  • Use the database of AS Java.
  • Use an external ABAP system as the data source for user data.
  • Use an LDAP directory as the data source for user data.

During the installation, the SAP system is automatically configured to use the Java database as data source for the UME.

You are prompted for how to configure the UME during the input phase of the installation. You can choose between the following options:

  • Use Java database (default).
    • If you choose this option, administrators can manage users and groups with the UME Web admin tool and SAP NetWeaver Administrator only.
    • For LDAP, use this configuration for the installation and change the configuration to LDAP after the installation.
  • Use ABAP
    • If you choose this option, administrators can manage users with the transaction SU01 on the external ABAP system, and, depending on the permissions of the communication user, also with the UME Web admin tool and SAP NetWeaver Administrator.
    • Make sure that you have created the required users manually on the external ABAP system before you choose this option.

Select the Custom parameter mode. When you do this, you are prompted to select the appropriate option and to enter the required parameters. If you do not choose the Custom parameter mode, you have to change the required parameters on the Parameter Summary screen.

For more information about supported UME data sources and change options, see SAP Note 718383.

8.1.10 - SAP Solution Manager key

To install your SAP system, you need to generate an SAP Solution Manager key, which the installation requires to continue. For more information, see SAP Note 805390. You have already generated an SAP Solution Manager Key for the central instance, so you do not have to do this for the dialog instance.

8.2 - SAP System Database Parameters

8.2.1 - Database ID <DBSID>

The <DBSID> identifies the database instance. SAPinst prompts you for the <DBSID> when you are installing the database instance.

The <DBSID>:

  • can be the same as the <SAPSID>.
  • must follow the same restriction than the SAPSID.

Choose your database ID carefully. Renaming is difficult and requires that you reinstall the SAP system.

8.2.2 - Database schema, Passwords

The Java database schema is named SAP<SCHEMA_ID>DB. Default name is SAPSR3DB.

Choose a <SCHEMAID> that is different from your <SAPSID>.

It might cause problems when you copy a system where <SCHEMAID> is the same as <SAPSID>, and the database- specific method used for the copy does not allow you to rename the database schemas. In certain situations, you might create a system copy with a new <SAPSID>, but where the database schema has the old <SAPSID>. This is not a technical problem, but might confuse the system administrator

8.3 - Diagnostics Agent Parameters

The diagnostics agent is installed automatically with the SAP system.

8.3.1 - DASID

The System ID of the Diagnostics Agent (DASID)

SAPinst sets the system ID of the diagnostics agent, <DASID>, to DAA by default. If DAA is already used, SAPinst assigns another default system ID. You can overwrite the default system ID as required.

<DASID> must follow the same restriction than the SAPSID.

9 - Installation

Do not install the Oracle database software before you run SAPinst. SAPinst stops and prompts you to install the Oracle database [page 85] while the installation of the database instance is running.

10 - After Installation

10.1 - Missing table entries in the database

After you install an SAP system under Linux, a few entries are missing in the tables TSLE2 and TSLE3. The procedure described in Note 836992 corrects this.

11 - Starting and Stopping SAP System Instances

page 157: You can start or stop SAP system instances in one of the following ways:

  • Using the SAP Management Console (SAP MC)
  • Using commands

12 - Documentation / Reference

sap/installation.txt · Last modified: 2018/09/16 12:42 by gerardnico