1. INSTALLATION & SETUP OF R/3 SYSTEM
Installing Hardware
Network connections to Systems
Operating System Installation
Database Installation
Partition as per SAP Recommendation
R/3 Installation & Setup
2. Requirements
Hardware Software Network Frontends
Supported
Certified TCP/IP
OS version
hardware OS patches
configuration
Number of Hostname
C compiler
processors Network file
Memory
make utilities
Kernel
system (NFS)
Disk space Network
High
configuration
Additional
information
availability system (NIS)
software
Ensure the requirements in the installation checklist are met
Consult hardware partners for sizing
3. Technically Correct Installation:
Requirements
Oracle database Database version
Database name
Directory names
Mirrored redo log files
Disk layout
4. Oracle Directory Structure
Server site
SAPDATA_HOME
sapdata1 sapdata<n>
ORACLE_HOME
origlogA origlogB
dbs bin network/admin
mirrlogA mirrlogB
saparch sapbackup
sapcheck sapreorg
Client site saptrace ...
ORACLE_HOME Unix environment variables:
<sid>adm
network/admin ORA_NLS: $ORACLE_HOME/ocommon/NLS_723/admin/data
ORA_NLS32: $ORACLE_HOME/ocommon/NLS_733/admin/data
ORA_NLS33: $ORACLE_HOME/ocommon/NLS_805/admin/data
ora<sid> (ORA_NLS and ORA_NLS32 see above)
ORA_NLS33: $ORACLE_HOME/ocommon/nls/admin/data
5. R/3 Directory Structure
usr
Global directories sap Instance directories
trans <SID> tmp put
SYS <Instance_name>
exe profile global work data log
<sapmnt>
run dbg opt
<SID>
exe profile global
= Symbolic link
6. Post Installation Steps
Configuring Transport Management Systems
Importing Required Profiles
To use your SAP software legally and in
accordance with the contractual stipulations, SAP
Systems can only be operated with a license key
(license key) granted by SAP.
7. Post Installation Steps
Configuring Transport Management Systems
Importing Required Profiles
To use your SAP software legally and in
accordance with the contractual stipulations, SAP
Systems can only be operated with a license key
(license key) granted by SAP.
Editor's Notes
When you plan an installation, you must ensure that the minimum requirements in the installation checklist provided by SAP are met. This installation checklist is contained in every installation package and can be ordered through SAPNet. Installation requirements for frontends are contained in a separate installation checklist. For detailed network information, refer to the manual Integration of R/3 Servers in TCP/IP Networks and to installation checklists for supported and required network products. For detailed R/3 release information, log on to SAPNet - R/3 Frontend and look in the component XX-SER-SWREL. The task of sizing is usually performed by SAP hardware partners, who must consider both the SAP recommendations and their own hardware specifications.
The Oracle database version must be released for the current version of the operating system. For release information, go to SAPNet - R/3 Frontend and look under component XX-SER-SWREL Release planning. This installation check list also specifies which versions of the operating system and database can be used together. The database name must be identical to the R/3 System identification (SID). The name assigned to the database at installation cannot easily be changed. The naming convention for the Oracle database also cannot be changed. Database programs and R/3 programs refer to this fixed naming convention for file directories. The redo log files (online log files) must be mirrored. Certain restrictions apply to the physical location of the Oracle file directories. For example, redo log files, archive files, and data files should not be located together on the same physical disk.
The Oracle database file tree structure on the database server site has 2 main branches: The Oracle binaries are located in the subdirectory bin in the ORACLE_HOME directory. The ORACLE_HOME directory is also required on each server with a database client The environment variables SAPDATA_HOME point to the directories containing database-specific files, such as data files, online redo log files, and offline redo log files. In addition, the operating system user <sid>adm requires the following environment variables: ORACLE_SID = <SID> DBS_ORA_TNSNAME: set to the database identifier <SID> from tnsnames.ora In a UNIX environment, the following environment variables are set by R/3 configuration tools: ORA_NLS: $ORACLE_HOME/ocommon/NLS_723/admin/data ORA_NLS32 $ORACLE_HOME/ocommon/NLS_733/admin/data ORA_NLS33: $ORACLE_HOME/ocommon/nls/admin/data (user ora<sid>) TNS_ADMIN: $ORACLE_HOME/network/admin
This graphic displays the global and instance specific R/3 file system view of a homogenous R/3 System. Global files can be managed centrally on the central instance host, using the network file system (NFS) <sapmnt>/<SID>. <sapmnt>/<SID> must be physically stored on the central instance host. It must also be exported explicitly as NFS in read/write mode to all dialog instance hosts and in read-only mode to all UNIX presentation servers. To run dialog instances with executables stored locally on the dialog instance host, activate program SAPCPE. The global transport directory /usr/sap/trans must be accessible by every R/3 instance belonging to one system landscape. This access is achieved through a soft link that points to the transport directory or through mounting the file system /usr/sap/trans using NFS. Installing a heterogeneous R/3 System requires a different file system, which is described in the installation and OS dependencies guide.
