Sap Nw7.0 Sr3 Java On Aix - Oracle

PUBLIC
Installation Guide
SAP NetWeaver 7.0

SR3 Java on AIX :
Oracle
Including the following:
SAP NetWeaver Java Application Server (AS Java)

SAP NetWeaver Business Intelligence Java Components (BI Java)
SAP NetWeaver Development Infrastructure (DI)
SAP NetWeaver EP Core (EPC)
SAP NetWeaver Enterprise Portal (EP)
Application Sharing Server (Optional Standalone Unit)
Target Audience
n Technology consultants
n System administrators
Document version: 1.00 03/28/2008
Document History
Caution
Before you start the implementation, make sure you have the latest version of this document. You
can find the latest version on SAP Service Marketplace http://service.sap.com/instguides.
The following table provides an overview on the most important document changes:
Version
Date
Description
1.00
3/28/2008
Initial Version
2/178
PUBLIC
03/28/2008
Table of Contents
Chapter 1
1.1
1.2
1.3
1.4
Introduction . . . . .
New Features . . . . . .
SAP Notes for the Installation
Online Information from SAP
Naming Conventions . . .
Chapter 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Planning . . . . . . . . . . . . . . . . . . . .
Basic System Variants . . . . . . . . . . . . . . . .
How to Distribute Instances to Hosts . . . . . . . . . .
SAP System Transport Host . . . . . . . . . . . . . .
Basic SAP System Parameters . . . . . . . . . . . . .
Running Adobe Document Services on Nonsupported Platforms
Application Sharing Server as an Optional Standalone Unit . .
High Availability: Planning the Switchover Cluster . . . . .
Chapter 3
3.1
3.1.1
3.1.2
3.1.3
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.4.1
3.2.4.2
3.2.4.3
3.2.5
3.2.6
3.2.7
3.3
3.3.1
3.3.2
3.3.3
03/28/2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7
8
11
12
15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
17
17
19
20
20
31
31
33
Preparation . . . . . . . . . . . . . . . . . . . .
High Availability: Switchover Preparations . . . . . . . . .
Preparing for Switchover . . . . . . . . . . . . . . . .
Setting Up File Systems for a High-Availability System . . . . .
Configuring Network File System . . . . . . . . . . . .
Hardware and Software Requirements . . . . . . . . . . .
Running the Prerequisite Checker in Standalone Mode (Optional)
Requirements for AIX . . . . . . . . . . . . . . . .
Requirements for a Central System . . . . . . . . . . . .
Requirements for a Distributed or a High Availability System . .
Requirements for the Central Services Instance . . . . . . .
Requirements for the Central Instance . . . . . . . . . .
Requirements for the Database Instance . . . . . . . . . .
Requirements for a Dialog Instance . . . . . . . . . . . .
Checking and Modifying the AIX Kernel . . . . . . . . . .
Setting up Swap Space for AIX . . . . . . . . . . . . . .
Creating Operating System Users . . . . . . . . . . . .
Network Information Service . . . . . . . . . . . . . .
Creating Operating System Users and Groups . . . . . . . .
Creating AIX Groups and Users (Optional) . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
37
38
38
40
41
43
44
45
47
49
49
50
51
53
54
55
56
56
56
58
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3/178
3.4
3.4.1
3.4.2
3.4.3
3.5
3.6
3.7
3.8
3.9
3.9.1
3.9.2
3.9.3
Setting Up File Systems and Raw Devices . . . . . . . . . . . . .

SAP Directories . . . . . . . . . . . . . . . . . . . . . .
Oracle Directories . . . . . . . . . . . . . . . . . . . . .
Setting Up File Systems and Raw Devices for AIX . . . . . . . . . .
Exporting and Mounting the Global Transport Directory . . . . . . .
Exporting and Mounting Directories via NFS for AIX (Optional) . . . .
Generating the SAP Solution Manager Key . . . . . . . . . . . .
Installing the Java Development Kit . . . . . . . . . . . . . . .
Preparing and Mounting the Installation Media . . . . . . . . . .
Preparing the Installation DVDs . . . . . . . . . . . . . . . .
Downloading Installation DVDs from SAP Service Marketplace (Optional)
Mounting a CD / DVD for AIX . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
59
59
65
68
69
70
71
71
73
73
75
76
Chapter 4
4.1
4.2
4.2.1
4.2.2
4.2.3
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.5
Installation . . . . . . . . . . . . . . . . . . . . .
Performing a High-Availability Installation . . . . . . . . . .
Prerequisites before Starting SAPinst . . . . . . . . . . . .
Prerequisites before Starting SAPinst: All Instances . . . . . . .
Prerequisites before Starting SAPinst: Distributed Instances . . . .
Prerequisites Before Starting SAPinst: High Availability . . . . . .
Installing an SAP System Using SAPinst . . . . . . . . . . .
Running SAPinst on UNIX . . . . . . . . . . . . . . . .
Using SAPinst GUI . . . . . . . . . . . . . . . . . . .
Interrupted Installation with SAPinst . . . . . . . . . . . .
Performing a Remote Installation with SAPinst (Optional) . . . .
Starting SAPinst GUI Separately (Optional) . . . . . . . . . .
Entries in the Services File Created by SAPinst . . . . . . . . .
Oracle Database Software Installation . . . . . . . . . . . .
Updating SAP-Specific Files in the Oracle Staging Area . . . . . .
Performing Steps for the AIX Operating System . . . . . . . .
Running the Oracle Universal Installer . . . . . . . . . . .
Installing the Current Patch Set . . . . . . . . . . . . . .
Installing Required Interim Patches . . . . . . . . . . . . .
Installing Application Sharing Server as an Optional Standalone Unit
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
79
79
81
81
83
84
84
85
91
92
94
95
97
97
98
98
99
101
101
102
Chapter 5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
Post-Installation . . . . . . . . . . . . . . . . . .
Updating Database Statistics . . . . . . . . . . . . . .
Logging On to the Application Server . . . . . . . . . . .
Logging on to the Portal . . . . . . . . . . . . . . . .
Logging on to SAP NetWeaver Development Infrastructure (NWDI)
Installing the SAP License . . . . . . . . . . . . . . .
Configuring Remote Connection to SAP Support . . . . . .
Applying the Latest Kernel and Support Packages . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
103
104
105
106
107
108
108
109
4/178
PUBLIC
.
.
.
.
.
.
.
.
03/28/2008
5.8
5.9
5.10
5.10.1
5.10.2
5.10.3
5.11
5.12
5.13
5.13.1
5.13.2
5.14
5.15
5.16
5.17
5.18
Performing Oracle-Specific Post-Installation Steps . . . . . .

Performing a Full Installation Backup . . . . . . . . . . .
Post-Installation Steps for Adobe Document Services . . . . .
Assigning Roles to Users ADSUSER and ADS_AGENT . . . . .
Checking the IIOP Service and the Startup Properties . . . . .
Installation Check and Quick Tests for Adobe Document Services
Setting Environment Variable CPIC_MAX_CONV . . . . . .
Post-Installation Steps for the Application Sharing Server . . . .
High Availability: Post-Installation Steps . . . . . . . . . .
Setting Up Licenses . . . . . . . . . . . . . . . . . .
Taking Precautions for Transport . . . . . . . . . . . .
Ensuring User Security . . . . . . . . . . . . . . . .
Running the Configuration Wizard . . . . . . . . . . . .
Checking the SAP Java Documentation . . . . . . . . . .
Accessing Configuration Documentation in SAP Solution Manager
Post-Installation Steps for the Diagnostics Agent . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
110
111
113
113
114
114
115
116
116
116
117
118
122
124
125
127
Chapter 6
6.1
6.2
6.3
6.4
Additional Information . . . . . . . . . . . . . . . . . . .
Installation of Multiple Components in One Database (Optional) . . . . .
Integration of LDAP Directory Services (Optional) . . . . . . . . . .
Preparing User Management for an External ABAP System . . . . . . .
Installation of Additional Software Units or Usage Types in an Existing SAP
System . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping SAP System Instances . . . . . . . . . . . .
Starting and Stopping SAP System Instances Using the SAP Management
Console . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting and Stopping SAP System Instances Using Scripts . . . . . . .
Starting and Stopping the Diagnostics Agent Using Scripts . . . . . . .
Creating a User for LDAP Directory Access (Optional) . . . . . . . . .
Configuring User Management to Use an LDAP Directory (Optional) . . .
Usage Type-Specific Initial Technical Configuration . . . . . . . . . .
Initial Technical Configuration for the Application Server Java (AS Java) . .
Initial Technical Configuration for Adobe Document Services . . . . . .
Initial Technical Configuration for Composite Application Framework Core
(CAF) . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial Technical Configuration for the System Landscape Directory (SLD) .
Initial Technical Configuration for Development Infrastructure (DI) . . .
Initial Technical Configuration for the Portal (Usage Types EPC and EP) . .
Initial Technical Configuration for BI Java . . . . . . . . . . . . .
Configuring BI Java Information Broadcasting . . . . . . . . . . . .
Process Chains: Transporting Texts for the Alert Category . . . . . . .
Renaming initialPermissionsBI.xml.template . . . . . . . . . . . .
129
129
131
135
6.5
6.5.1
6.5.2
6.5.3
6.6
6.7
6.8
6.8.1
6.8.1.1
6.8.1.2
6.8.1.3
6.8.2
6.8.3
6.8.4
6.8.4.1
6.8.4.2
6.8.4.3
03/28/2008
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
138
143
144
147
150
151
152
152
153
153
154
155
155
157
158
158
159
159
5/178
6.9
6.10
6.10.1
6.10.2
6.11
6.11.1
6.11.1.1
6.11.1.2
6.11.2
6.11.2.1
6.11.2.2
6.11.2.3
6.11.2.4
6.11.2.5
6/178
Heterogeneous SAP System Installation . . . . . . .

Troubleshooting . . . . . . . . . . . . . . . .
Troubleshooting with SAPinst . . . . . . . . . . .
Troubleshooting for Portal Installation . . . . . . .
Deleting an SAP System . . . . . . . . . . . . .
Deleting an SAP System Using SAPinst . . . . . . . .
Running SAPinst to Delete an SAP System . . . . . .
Deleting the Oracle Database Software . . . . . . .
Deleting an SAP System Manually . . . . . . . . .
Deleting an SAP Instance . . . . . . . . . . . .
Deleting Installation Files, Directories, and Users on a Host
Deleting the Java Part of an SAP System . . . . . . .
Deleting the Oracle Database Java Schema . . . . . .
Deleting an Oracle Database Instance . . . . . . . .
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
160
160
160
161
162
162
163
164
165
165
166
167
169
170
03/28/2008
Introduction
1 Introduction
This document explains how to install SAP NetWeaver 7.0 Support Release 3 (SR3) Java.
SAP NetWeaver 7.0 Support Release 3 corresponds to SAP NetWeaver 7.0 Support Package Stack
(SPS) 14.
For more information about the SAP NetWeaver technology, see
http://sdn.sap.com/irj/sdn/netweaver.
You can install SAP NetWeaver 7.0 SR3 Java with the following usage types in a single installation
run of SAPinst:
n SAP NetWeaver Application Server Java (AS Java)
Only valid for: Development Infrastructure (DI)
n SAP NetWeaver Development Infrastructure (DI)

End of: Development Infrastructure (DI)
Only valid for: EP Core (EPC)
n SAP NetWeaver EP Core (EPC)

End of: EP Core (EPC)
Only valid for: Enterprise Portal (EP)
n SAP NetWeaver Enterprise Portal (EP)

If you install usage type EP, note the following:
l You must install SAP NetWeaver Application Server Java (AS Java) and EP Core (EPC).
l The Application Sharing Server is installed automatically with usage type EP. For production
use, we recommend that you install the server as an optional standalone unit on a dedicated
host as described in this document.
End of: Enterprise Portal (EP)
Only valid for: BI Java
n SAP NetWeaver Business Intelligence Java Components (BI Java)

You also have to install SAP NetWeaver Application Server Java (AS Java), EP Core (EPC) and
SAP NetWeaver Portal (EP).
End of: BI Java
For more information about the usage types of SAP NetWeaver and their interdependencies, see
the document Master Guide SAP NetWeaver 7.0 at http://service.sap.com/instguidesNW70. For
restrictions, see SAP Note 852008.
03/28/2008
PUBLIC
7/178
1
1.1
Introduction
New Features
Installation of Additional Software Units or Usage Types in an Existing SAP System
If you want to install additional Java software units or usage types in an existing SAP system based on
SAP NetWeaver 7.0 SR3 (Support Package Stack (SPS) 14), you have to use the Java Support Package
Manager (JSPM). You cannot use SAPinst to install additional software units or usage types in an
existing SAP system. Existing SAP system means that it has at least AS Java.
As of SAP NetWeaver 7.0 SPS 12, you can use Install Additional Usage Types in JSPM to install and activate
additional software units or usage types.
For more information, see Installation of Additional Software Units or Usage Types in an Existing SAP System
[page 138].
Constraints
You need to consider the following constraints before you start your installation:
n Your operating system platform must be 64-bit.
n The database must be Oracle 10.2.0.2 or higher.
n You must only use the SAP installation tools according to the instructions and for the purposes
described in the SAP installation document. Improper use of the SAP installation tools can damage
files and systems already installed.
n SAP system installations should only be performed by SAP Technical Consultants certified for
your operating system, your database, and the SAP system that you are installing.
n For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly
release the newest database (DB) and operating-system (OS) versions of SAP products. These
releases are downward-compatible with earlier SAP system releases.
Note that for already shipped SAP components, we only support the installation for database
versions proposed by the installation tool. Therefore, you must install an SAP component or
perform a system copy using a downward-compatible database as follows:
l Install the component with the old proposed database version.
l Upgrade the old database version to the downward-compatible new version.
1.1 New Features

The following tables provide an overview of the new features related to the installation of this release:
Caution
Make sure that you read the release notes for your SAP system. You can find these at
http://service.sap.com/releasenotes.
8/178
PUBLIC
03/28/2008
1
1.1
Introduction
New Features
SAP System Installation
Area
Description
SAPinst
As of SAP NetWeaver 7.0, SAPinst has the following new features:

n You can check the prerequisites for your SAP system installation with the
Prerequisite Checker [page 44].
n You can install a central system in one of two modes:
l Typical Mode
If you choose Typical, your SAP system is installed with default settings. As
a result, you only have to respond to a small selection of prompts. If you
want to change any of the default settings, you can do so on the parameter
summary screen at the end of the installation.
l Custom Mode
If you choose Custom, you must manually enter all installation parameters.
You can change your values on the parameter summary screen at the end of
the installation.
n You can uninstall an SAP system or an SAP component with the SAPinst service
Uninstall System / Standalone Engines / Optional Standalone Unit.
n You can install the Java Add-In for an existing ABAP system. This means that you
run SAPinst to execute the following:
l Install the central services instance (SCS)
l Add the Java database schema to the existing ABAP database instance
l Add the Java central instance with usage types to the existing ABAP central
instance
The installation of the Java Add-In for an existing ABAP system is described in the
documentation Installation Guide <your product> ABAP+Java on <OS>: <Database>
available at http://service.sap.com/instguides.
Note
You cannot install the Java Add-In for existing ABAP dialog instance(s). Instead,
you have to install new ABAP+Java dialog instance(s).
n The sapinst group ID must be the secondary group of the users root and
<sapsid>adm. For more information, see Creating Operating System Users and Groups
Manually [page 56].
n You can install SAP NetWeaver as a high-availability (HA) system.
n You assign one master password to all users created by SAPinst. This password is
used for all user accounts and for the secure store key phrase.
n SAPinst fills in most of the input parameter fields with default values.
If required, you can change the default values on the Parameter Summary screen
before you start the actual installation.
n You no longer have to manually activate sapcpe.
The kernel is replicated automatically from
/usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to
/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each
SAP system instance.
For more information, see Setting Up File Systems [page 59].
Installation DVDs
03/28/2008
You start the installation from a single Installation Master DVD.
PUBLIC
9/178
1
1.1
Introduction
New Features
Area
Description
SAP Solution Manager

Key
You require a key to install your SAP system. You generate this key with your SAP Solution
Manager [page 71].
SAP NetWeaver
Administrator
SAP NetWeaver Administrator is a brand new solution for monitoring and

administering Java systems and their applications.
For more information, see the SAP NetWeaver Master Guide and the following:
http://www.sdn.sap.com/irj/sdn/netweaver Lifecycle Management Operations
Knowledge Center Administration

Diagnostics Agent
A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone

Java program that runs on each of the systems managed by SAP Solution Manager
Diagnostics. It gathers information and reports to the SAP Solution Manager system.
For more information about the Diagnostics Agent, see
http://service.sap.com/diagnostics .
The installation of the Diagnostics Agent is now part of the Installation Master DVD.
That is, you can choose between the following options:
n If there is no Diagnostics Agent already installed on this physical or virtual host,
it is installed automatically with an AS Java central instance and dialog instance.
n You can install it as a standalone engine.
64-bit support for all

instances except dialog
instances
If you want to use 32-bit SAP NetWeaver components, first check whether these
components can run on 64-bit operating systems. If so, we recommend that you
use 64-bit systems.
If not, you can install an SAP dialog instance on 32-bit operating systems to run
these components. For all other SAP instances, you must use 64-bit systems
Only Unicode support

for new installations
Every newly installed SAP system is a Unicode system.

However, non-Unicode is still supported for copied and upgraded systems.
Maintenance
Optimizer
All downloadable software components based on SAP NetWeaver 7.0 and subsequent
versions released after April 2, 2007 are available exclusively through the
Maintenance Optimizer in SAP Solution Manager. This comprises:
n Support Package Stacks, Support Packages, and patches for Java instances, except
for kernel patches
n Legal changes
n SAP applications and versions that are:
l Mandatory for SAP NetWeaver 7.0 (and subsequent versions) and all
applications based on this software, including SAP Business Suite 2005 (and
subsequent versions)
l Optional for all SAP applications
For more information, see http://service.sap.com/solman-mopz.
10/178
PUBLIC
03/28/2008
1
1.2
Introduction
Operating Systems and Platforms
Area
Description
Support of Operating
Systems and Platforms
n For supported operating system and database releases, see the Product Availability
Matrix at http://service.sap.com/pam.
n For forums, blogs, content, and community related to all of the supported
databases and operating systems, see the Database and Operating Systems area at
http://sdn.sap.com/irj/sdn/dbos.
Oracle Database
New functions in
Oracle Database 10g
n As of the installation of SAP NetWeaver 7.0 and SAP Business Suite 2005, new
functions of the Oracle Database 10g release are used.
For more information about the integration of Oracle 10g in the SAP
environment, see SAP Note 720886.
n For the complete list of new features, see further documentation from Oracle,
which you can find at:
http://www.oracle.com/technology/products/database/oracle10g
Documentation
Area
Description
Installation of Additional
The documentation on how to install additional software units or usage
Software Units or Usage Types types to an existing SAP system is now included in the installation guides. Up
to now this documentation was only available in SAP Note 883948.
Application Sharing Server
Installation
The installation of Application Sharing Server is part of the Java installation

guide for your product, available at http://service.sap.com/instguides
<choose your product>
SAP Notes
You can now access SAP Notes directly in SAP Service Marketplace from
your PDF. Place the cursor on the SAP Note <number> and double-click. A
separate browser window opens to display the SAP Note.
Links in PDF files
You can use the new links in the PDF files of the guides as follows:
n Click the section headings such as New Features to jump back to the table of
contents at the beginning of the guide.
n Click an internet link such as http://service.sap.com to jump to the
corresponding internet page.
1.2 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the
most recent information on the installation, as well as corrections to the installation documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find at
http://service.sap.com/notes.
03/28/2008
PUBLIC
11/178
1
1.3
Introduction
SAP Note Number
Title
Description
1052298
SAP NetWeaver 7.0 SR3 / Business UNIX-specific information about the SAP system
and corrections to this documentation.
Suite 2005 SR3 UNIX
852008
Release Restrictions for SAP

NetWeaver 7.0
1094599
SAP NetWeaver 7.0 SR3 / Business Oracle-specific information about the SAP
system installation and corrections to this
Suite 2005 SR3 UNIX: Oracle
documentation.
828268
Oracle 10g: New functions
Information about new Oracle features released

for the SAP system.
98252
Installing two Oracle databases

on a host
This SAP Note is only required if you plan to

install more than one Oracle database on the
same host.
855498
Installation Prerequisite Checker SAP Software on UNIX, Windows and System i:

Checking OS Dependencies
73606
Supported Languages and Code

Pages
Information on possible languages and language

combinations in SAP systems
737368
Hardware requirements of Java

Development Infrastructure
Information on the hardware requirements for

usage type Development Infrastructure (DI),
which depends on the size of your development
team.
1067221
Central Note for Heterogeneous

Installation
Heterogeneous ABAP system landscapes on

different operating systems have been released
for some time. Heterogeneous Java system
landscapes on different operating systems have
now also been released. However, not every
combination of operating system and database
system is released. This SAP Note and its related
SAP Notes describe the released operating system
and database combinations.
1152408
Installing SAP Systems into an

Independent ASP (iASP)
Information on features and limitations for

installations into independent ASP.
Customer information on restrictions in the

production use of certain functions.
1.3 Online Information from SAP

More information is available online as follows.
12/178
PUBLIC
03/28/2008
1
1.3
Introduction
Documentation
Description
Internet Address
Title
Master Guide for SAP

NetWeaver 7.0
http://service.sap.com/installNW70
Master Guide SAP NetWeaver 7.0
Technical Infrastructure
Guide for SAP NetWeaver
7.0
Technical Infrastructure Guide SAP

NetWeaver 7.0
Master Guide SAP

Solution Manager 4.0
http://service.sap.com/instguides SAP
Components SAP Solution Manager Release 4.0
Master Guide SAP Solution

Manager 4.0
List of media for

installation or upgrade
for SAP NetWeaver 7.0
Media List SAP NetWeaver 7.0
Installation of SAP
Installation Guide SAP Solution

Manager 4.0 on <OS>: <Database>
Configuration of SAP
Configuration Guide SAP Solution

Manager 4.0 as of <current stack>
http://service.sap.com/maintenanceNW70
Support Package Stack Guide SAP

NetWeaver 7.0 SPS <current stack>
Patching of SAP
NetWeaver 7.0 scenarios
Upgrade to SAP
NetWeaver 7.0
SPS <current stack>

SPS <current stack>
Support Package Stack Guide
http://service.sap.com/upgradenw70
Installation Upgrade to SAP NetWeaver Systems

Upgrade Documentation - SAP NetWeaver 7.0 <SR>
Installation of SAP
NetWeaver Developer
Workplace
Installation Installation Clients

SAP Developer Workplace
Installation of SAP
NetWeaver Developer
Studio
Installation Installation Clients

SAP NetWeaver Developer Studio
Installation
Installation
Component Upgrade Guide SAP

NetWeaver 7.0 Application Server
ABAP
Installation Guide Developer
Workplace for SAP NetWeaver
SAP NetWeaver Developer Studio
Standalone Installation Guide
Installation of the System

Landscape Directory (SLD) Configuration Post-Installation Guide SLD of SAP
NetWeaver 7.0
Post-Installation Guide System

Landscape Directory of SAP
NetWeaver 7.0
Installation of Web
Dispatcher
Installation Guide Web Dispatcher

on <platform> For SAP Systems
Based on SAP NetWeaver 7.0 (2004s)
Front End installation
Installation Standalone Engines Installation Web

Dispatcher on <platform>
Installation Clients
<Release>
03/28/2008
Installation SAP Front End
PUBLIC
SAP Front End Installation Guide

This guide is also available on
the Presentation DVD.
13/178
1
1.3
Introduction
Description
Internet Address
Title
Homogeneous and
heterogeneous system
Installation SAP NetWeaver Systems System Copy
copy for SAP systems based for SAP Systems Based on <Release> <Technology>
on NetWeaver 7.0
SAP NetWeaver Problem
Analysis Guide
System Copy Guide System Copy for

SAP Systems based on SAP NetWeaver
<Release> <Technology>
SAP NetWeaver Problem Analysis

http://help.sap.com/nw70 SAP NetWeaver
7.0 Library English SAP NetWeaver Library SAP Guide (PAG)
NetWeaver by Key Capability Solution Life Cycle
Management by Key Capability SAP NetWeaver
Problem Analysis Guide (PAG)
General Quick Links
Description
Internet Address
SAP Help Portal
http://help.sap.com
SAP NetWeaver Library in SAP

Help Portal
http://help.sap.com/nw70
SAP Notes
http://service.sap.com/notes
SAP Notes for SAP NetWeaver 7.0

installation
http://service.sap.com/sapnotesnw70
Forums, blogs, and general

information related to all of
the supported databases and
operating system platforms
http://sdn.sap.com/irj/sdn/dbos
Product Availability Matrix (PAM)

for supported operating system
releases
http://service.sap.com/pam
Release notes
http://service.sap.com/releasenotes
Unicode SAP systems and their

availability
http://service.sap.com/unicode
System sizing (Quick Sizer tool)
http://service.sap.com/sizing
SAP NetWeaver capabilities
http://sdn.sap.com/irj/sdn/netweaver
Life-cycle management for SAP

NetWeaver
http://sdn.sap.com/irj/sdn/lcm
Landscape design for SAP

NetWeaver
http://sdn.sap.com/irj/sdn/landscapedesign
Application management for SAP

NetWeaver
http://sdn.sap.com/irj/sdn/applicationmanagement
High Availability
http://sdn.sap.com/irj/sdn/ha
System Landscape Directory
http://sdn.sap.com/irj/sdn/nw-sld
14/178
PUBLIC
03/28/2008
1
1.4
Introduction
Naming Conventions
Description
Internet Address
Software logistics for SAP

NetWeaver
http://sdn.sap.com/irj/sdn/softwarelogistics
SAP NetWeaver operations
http://sdn.sap.com/irj/sdn/operations
SAP NetWeaver Development

Infrastructure
http://sdn.sap.com/irj/sdn/nw-di
Security for SAP NetWeaver
http://sdn.sap.com/irj/sdn/security
Information on SAP Support

Package Stacks
http://service.sap.com/sp-stacks
http://service.sap.com/solutionmanager
Maintenance Optimizer
http://service.sap.com/solman-mopz
End-to-End Root Cause Analysis
http://service.sap.com/diagnostics
1.4 Naming Conventions

In this documentation, the following naming conventions apply:
Terminology
n SAP system refers to SAP NetWeaver 7.0 SR3.

n Java system refers to SAP NetWeaver 7.0 SR3 Java.
n Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent.
Variables
Variables
Description
<SAPSID>
SAP system ID in uppercase letters
<sapsid>
SAP system ID in lowercase letters
<DBSID>
Database ID in uppercase letters
<dbsid>
Database ID in lowercase letters
<host_name>
Name of the corresponding host
<user_home>
Home directory of the user performing the installation.
<INSTDIR>
Installation directory for the SAP system
<DVD_DIR>
Directory on which a DVD is mounted
<OS>
Operating system name within a path
<SCHEMA_ID>
Database schema ID
03/28/2008
PUBLIC
15/178
1
1.4
Introduction
Naming Conventions
The following example shows how the variables are used:

Example
Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.

If your SAP system ID is C11, log on as user c11adm and change to the directory
/usr/sap/C11.
16/178
PUBLIC
03/28/2008
Planning
2 Planning
This section tells you how to plan the installation of your SAP system.
You have to complete the following planning activities:
1. You plan your SAP system landscape according to the Master Guide and the Technical Infrastructure
Guide available for your product.
2. You choose your basic system variant [page 17].
3. You plan how to distribute the instances to hosts [page 19].
4. You decide on the transport host to use [page 20].
5. You identify basic SAP system parameters [page 20].
6. If you want to use Adobe Document Services (ADS), you check what you have to do in case your platform is
not supported for ADS [page 31].
7. You decide if you want to install Application Sharing Server as a standalone unit on a dedicated host [page 31].
Only valid for: HA (UNIX)
8. You plan the switchover cluster [page 33] for a high-availability (HA) system.
End of: HA (UNIX)
The following planning activity is optional:

n Installation of Multiple Components in One Database (MCOD) [page 129]
n Preparing User Management for an External ABAP System [page 135]
2.1 Basic System Variants

The following section provides information about the basic system variants for a Java system and
about how to distribute SAP instances within them.
Note
If you want to use 32-bit SAP NetWeaver components, first check whether these components can run
on 64-bit operating systems. If so, we recommend you to use 64-bit systems. If not, you can install
an SAP dialog instance on 32-bit operating systems to run these components. For all other SAP
instances, you must use 64-bit systems.
03/28/2008
PUBLIC
17/178
2
2.1
Planning
Basic System Variants
Mandatory instances of a Java system are the central instance, the central services instance, and
the database instance.
Note
The Java central services instance is named SCS instance.

Optionally, you can install one or more dialog instances.
Note
Each instance can reside on a separate host.

Figure 1:
Figure 2:
18/178
Minimum System Distribution (Central System)
Maximum Distribution for a Distributed System or for a High-Availability System
PUBLIC
03/28/2008
2
2.2
Planning
How to Distribute Instances to Hosts
For a maximum system distribution, each instance resides on a separate host.
2.2 How to Distribute Instances to Hosts

The following provides information on how you can distribute the SAP instances for the different SAP
system variants. You use SAPinst to install the SAP instances as a:
n Central system on a single host
You run SAPinst and install all instances on one host.
n A distributed system on several hosts
The following figure shows how to distribute your instances on several hosts:
Figure 3:
Distribution of Instances in a Java System
Note
You can use the SAP transport host or the SAP global host as your central instance host.
You perform the following steps:
1. If you want to share the transport directory trans from another system, you have to mount it
from this system. Otherwise we recommend that you share the trans directory that is created
during the installation of the central instance (see below).
2. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).
03/28/2008
PUBLIC
19/178
2
2.3
Planning
SAP System Transport Host
3. On the SAP global host, you export the required file systems to the database and central
instance host.
4. On the database host, you mount the exported file systems from the SAP global host.
5. On the database host, you run SAPinst and install the database instance.
6. On the central instance host, you mount the exported file systems from the SAP global host
and SAP transport host.
7. On the central instance host, you run SAPinst and install the central instance.
8. If required, you can now install one to <n> dialog instances. The procedure is the same as
installing a central instance (replace central instance with dialog instance in the procedure).
2.3 SAP System Transport Host

The transport host contains the transport directory that is used by the SAP transport system to store
transport data and change information of SAP systems, such as software programs, data dictionary
data, or customization data. If you have several SAP systems they are usually organized in transport
domains. In most cases, all SAP systems in a transport domain have a common transport directory.
For more information, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver
by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle Management Software
Logistics Change and Transport System Change and Transport System Overview (BC-CTS) Basics of the Change
and Transport System Transport Management System Concept
When you install an SAP system, SAPinst by default creates the transport directory on the central
instance host in /usr/sap/trans.
You have to prepare this host for use by the new SAP system if one of the following applies to you:
n You want to locate the transport directory on another host.
n You want to use an existing transport host and directory in your SAP system landscape.
For more information, see Exporting and Mounting the Global Transport Directory [page 69].
More Information
Setting Up File Systems and Raw Devices [page 59]
2.4 Basic SAP System Parameters

The tables below list the basic system parameters that you need to determine before installing your
SAP system. For all other SAP system parameters, use the F1 help in the SAPinst dialogs.
20/178
PUBLIC
03/28/2008
2
2.4
Planning
Basic SAP System Parameters
Note
In the column Enter Your Values, you write down the values that you plan to use, for example,
the Message Port Number.
SAP System ID and Database ID
Parameters
Description
Enter Your Values
SAP System ID
The SAP System ID <SAPSID> identifies the whole SAP

system.
...
<SAPSID>
Caution
Choose your SAP system ID carefully. You cannot change

the SAP system ID after the installation.
Make sure that your SAP system ID:
n Is unique throughout your organization
n Consists of exactly three alphanumeric characters
n Contains only uppercase letters
n Has a letter for the first character
n Does not include any of the following, which are reserved
IDs:
ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR
GID IBM INT KEY LOG LPT MON NIX NOT NUL OFF OMS
PRN RAW ROW SAP SET SGA SHG SID SQL SYS TMP UID
USR VAR
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>.
...
Caution
Choose your database ID carefully. Renaming is difficult

and requires you to reinstall the SAP system.
n If you want to install a new database:
Make sure that your database ID:
l Is unique throughout your organization
l Consists of exactly three alphanumeric characters
l Contains only uppercase letters
l Has a letter for the first character
l Does not include any of the following, which are
reserved IDs:
ADD ALL AND ANY ASC AUX COM CON DBA END EPS
FOR GID IBM INT KEY LOG LPT MON NIX NOT NUL
OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL
SYS TMP UID USR VAR
n If you want to use an existing database system:
03/28/2008
PUBLIC
21/178
2
2.4
Planning
Parameters
Description
Enter Your Values
Enter exactly the database ID of the existing database to

which you want to add the system.
System ID <SMDSID> of SAPinst sets <SMDSID> to SMD by default.
SAP Solution Manager If SMD is already used by another SAP system that is not
Diagnostics Agent
a Diagnostics Agent system, <SMDSID> is set to DA<x>,
where <x> can be any letter from A to Z, and DA stands for
DiagnosticsAgent).
If required, you can change <SMDSID> to a value of your
choice on the Parameter Summary screen. If you do so, the
same naming conventions as for <SAPSID> apply. For more
information, see entry SAP System ID <SAPSID> in this
table above.
...
SAP System Instances, Hosts and Ports
Parameters
Description
Enter
Your
Values
Instance Number of
the SAP system
Technical identifier for internal processes. It consists of a two-digit

number from 00 to 98.
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.
To find out this number, look under the SAP directory
/usr/sap/<SAPSID>/JC<nn> on the host of the central instance.
The value <nn> is the number assigned to the central instance.
...
Instance Number for Technical identifier for internal processes for the Diagnostics Agent,
the Diagnostics Agent consisting of a two-digit number from 00 to 98.
The instance number is set automatically to the next free and valid
instance number that has not yet been assigned to the SAP system.
The same restrictions apply as in Instance Number of the SAP system
(see above).
...
Name of Instance
Host
Message Server Port
Instance Host:
...
Host name of the specific instance.
To find out the host name, open a command prompt and enter hostname.
The host name must not exceed 12 characters. For more information
about the allowed host name length and characters, see SAP Note 611361.
...
Caution
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.
22/178
PUBLIC
03/28/2008
2
2.4
Planning
Parameters
Description
Enter
Your
Values
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.
Master Password
Parameters
Description
Enter Your Values
Master Password
This password is used for all user accounts SAPinst creates and
for the secure store key phrase. The length has to be 8 to 14
characters.
Depending on your installation scenario there might be more
restrictions.
...
Caution
If you do not create the operating system users manually,

SAPinst creates them with the common master password (see
Operating System Users). In this case, make sure that the
master password meets the requirements of your operating
system and of your database.
Operating System Users
Parameters
Description
Enter Your Values
Password of Operating SAPinst processes the passwords of operating system users as

...
System Users
follows:
n If the operating system users do not exist, SAPinst creates the
following users:
l <sapsid>adm
This user is the SAP system administrator user.
l <smdsid>adm
This user is dedicated to the Diagnostics Agent installation
with sufficient authorization to manage the agent.
It is created on the central instance host and on every
dialog instance host.
SAPinst sets the master password for these users by default.
You can overwrite and change the passwords either by using
the parameter mode Custom or by changing them on the
parameter summary screen.
03/28/2008
PUBLIC
23/178
2
2.4
Planning
Parameters
Description
Enter Your Values
n If the operating system users already exist, SAPinst prompts

you for the existing password, except if the password of these
users is the same as the master password.
n Make sure that the user ID and group ID of these operating
system users are unique and the same on each relevant
application server instance host.
For more information, see Creating Operating System Users [page 56].
User Management Engine (UME)
Parameter
Description
Enter Your Values
UME Configuration
You are prompted for how to configure the UME during the
...
input phase of the installation.
You can choose between the following options:
n 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.
n Use an external ABAP system.
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.
You must have created the required users manually on the
external ABAP system.
For more information, see Preparing User Management for an
External ABAP System [page 135].
For more information about supported UME data sources and
change options, see SAP Note 718383.
Using the Java Database:

Java Administrator
User
SAPinst sets the user name Administrator and the master

password by default.
If required, you can choose another user name and password
according to your requirements.
...
Java Guest User
SAPinst sets the user name Guest and the master password by
default.
The Guest user is for employees who do not belong to a
company or who have registered as company users with
pending approval. Guest users belong to the default group
Authenticated Users and have read access only.
..
Using an External ABAP System Parameters for the ABAP Connection:
24/178
PUBLIC
03/28/2008
2
2.4
Planning
Parameter
Description
Enter Your Values
Application Server
Number
This is the instance number on the application server of

the central ABAP system to which you want to connect the
Application Server Java.
To find out the number on the host of the primary
application server instance, look under the SAP directory
usr/sap/<SAPSID>/DVEBMGS<nn>. The value <nn> is the number
assigned to the SAP system.
...
Application Server
Host
This is the host name of the relevant application server instance. ...
To find out the host name, enter hostname at the command
prompt of the host running the primary application server
instance.
Communication User
This is the name and password of the existing ABAP

communication user. You must have created this user
manually on the external ABAP system.
...
Using an External ABAP System Parameters for the Application Server Java Connection:
Administrator User
This is the name and password of the administrator user that

you created on the external ABAP system.
...
Administrator Role
The role SAP_J2EE_ADMIN must exist on the external ABAP

system.
...
Guest User
This is the name and password of the guest user that you
created on the external ABAP system.
The guest user is for employees who do not belong to a
company or who have registered as company users with
pending approval. Guest users belong to the default group
Authenticated Users and have read access only.
..
Guest Role
The role SAP_J2EE_GUEST must exist on the external ABAP

system.
...
Key Phrase for Secure Store Settings
Parameters
Description
Enter Your Values
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.
...
Recommendation
Use a long key phrase that cannot be guessed easily. Use both
uppercase and lowercase letters in the phrase and include
special characters.
03/28/2008
PUBLIC
25/178
2
2.4
Planning
Internet Communication Manager (ICM) User Management
Parameter
Description
Enter Your Values
Password of webadm
The administration user webadm is created to use the web

...
administration interface for Internet Communication Manager
(ICM) and Web Dispatcher.
SAPinst sets the master password by default. If required, you
can choose another password. The length of the password must
be between 5 and 128 characters.
Solution Manager Key
Parameters
Description
Enter Your Values
SAP Solution Manager To install your SAP system, you need to generate an SAP Solution
...
key
Manager key [page 71], which the installation requires to continue.
For more information, see SAP Note 805390.
Parameters Relevant for the Connectivity to System Landscape Directory (SLD)
Parameters
Description
Enter Your Values
SLD Destination
The System Landscape Directory (SLD) is

designed for registering the systems (along
with the installed software) of your whole
system landscape.
The usual case is to configure one SLD for
your complete system landscape.
For more information, see Configuring System
Landscape Directory [page 155].
...
SLD HTTP Host
The host name of the System Landscape

Directory (SLD)
...
SLD HTTP Port
The HTTP port of the Java system where

the SLD is installed. The following naming
convention applies: 5<instance_number>00.
...
Example
If the instance number of your Java system is

01, the SLD HTTP Port is 50100.
26/178
PUBLIC
03/28/2008
2
2.4
Planning
Parameters
Description
Enter Your Values
SLD Data Supplier User

and password
n If you want to install a local SLD, SAPinst ...

creates this user during the installation.
n If you want to connect your system to an
existing central SLD, you have to enter
the existing SLD Data Supplier User and
password of the central SLD during the
installation.
Recommendation
We recommend that you name this user

SLDDSUSER
SLD ABAP API User and

password
n If you want to install a local SLD, SAPinst ...

creates this user during the installation.
n If you want to connect your system to an
existing central SLD, you have to enter
the existing SLD Data Supplier User and
password of the central SLD during the
installation.
Recommendation
We recommend that you name this user

SLDAPIUSER
RFC User, Password
The ABAP RFC user of the SLD
...
SLD Gateway Host
The host on which the gateway instance of

the SLD is running
...
SLD Gateway Instance

Number
The instance number of the gateway instance ...

of the SLD
SAP System Client
The client in which the ABAP RFC user exists ...
Parameters Relevant for Adobe Document Services (ADS)
Parameters
Description
User for basic

authentication
SAPinst sets the user name ADSUSER and the master

...
If required, you can choose another password according
to your requirements.
User for processing forms

between an ABAP and a
Java environment
SAPinst sets the user name ADSAGENT and the master

...
03/28/2008
Enter Your Values
PUBLIC
27/178
2
2.4
Planning
Parameters Relevant for SAP NetWeaver Development Infrastructure (NWDI)
Parameters
Description
Enter Your Values
Administrator of the SAP

NetWeaver Development
Infrastructure (NWDI)
and Password
SAPinst sets the user name NWDI_ADM and the master

...
Developer in the SAP

and Password
SAPinst sets the user name NWDI_DEV and the master

...
Landscape Directory
Service User in the SAP
and Password
SAPinst sets the user name NWDI_CMSADM and the master ...
Parameters Relevant for the File System
Parameters
Description
Your Values
File system for the home directory

user
/home/<username>
...
SAP system mount directory
/<sapmnt> is the base directory for
...
the SAP system.

For /<sapmnt> you can use a
directory of your choice.
Do not add <SAPSID> as
subdirectory because the system
adds this directory automatically.
Example
If you enter /<sapmnt>, the

system creates the directory
/<sapmnt>/<SAPSID>.
Oracle database file systems
28/178
n Oracle home
n sapdata home
n Client destination
n sapdata directory
PUBLIC
...
03/28/2008
2
2.4
Planning
Parameters Relevant for the Database
Parameters
Description
Enter Your Values
Database schema,
Passwords
The Java database schema is namedSAP<SCHEMA_ID>DB.

Default name is SAPSR3DB.
...
Recommendation
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.
Password of User
ora<dbsid>
User ora<dbsid> is the database administrator user.

This user is only required on the host on which the
database instance runs.
n If you created user ora<dbsid> manually before the
installation, SAPinst prompts you for the existing
password of this user.
...
Note
If you chose parameter mode Typical, SAPinst only

prompts you for the existing password of this user if
the password is not the same as the Master Password.
n If you did not create user ora<dbsid> manually before
the installation, SAPinst creates it automatically during
the installation. SAPinst then prompts you to enter and
confirm a password for this user. In this case, SAPinst
sets the Master Password by default. You can overwrite
it.
Note
If you chose parameter mode Typical, SAPinst does

not prompt you for the existing password of this user
but creates this user and assigns the Master Password
automatically.
Make sure that the user ID and group ID of this operating
system user are unique and the same on each application
instance host.
For more information, see Creating Operating System Users
[page 56].
03/28/2008
PUBLIC
29/178
2
2.4
Planning
Parameters
Description
User ID of User
If you chose parameter mode Typical and you did not create ...
ora<dbsid> manually before the installation, SAPinst
automatically creates this user with the appropriate user
ID. In this case, SAPinst does not prompt you for the user
ID of ora<dbsid>.
Make sure that the user ID of user ora<dbsid> is unique
and the same on each application instance host.
[page 56].
ora<dbsid>
Enter Your Values
Group IDs of sys, dba and If you chose parameter mode Typical and you did not create ...
oper
ora<dbsid> manually before the installation, SAPinst
automatically creates this user and assigns it to groups sys,
dba and oper. In this case, SAPinst does not prompt you for
the user ID of ora<dbsid>.
Make sure that the group IDs of dba and oper are unique
and the same on each application instance host.
[page 56].
Database User
Oracle User System
Oracle Listener Name,

Oracle Listener Port
n If you install the database instance on a host where no ...

other Oracle database is installed, you normally do not
have to change the default values for Listener Name
and Listener Port.
n If there is already an Oracle database installed on your
installation host, you can either use one listener for
both databases or you have to specify an unused Listener
Name and an unused Listener Port for the new listener.
For more information if you use one listener for both
databases, see SAP Note 98252.
n All dialog instances of an SAP system must use the same
Listener Port than the database instance.
Tablespaces, Datafiles
An Oracle database consists of one or more logical storage ...

units called tablespaces, which collectively store all of the
databases data.
Each tablespace in an Oracle database consists of one or
more files called datafiles, which are physical structures
that conform to the operating system in which Oracle is
running.
MaxDatafileSize is the initial size of the tablespace
datafile and its mapping to the new tablespace layout while
importing the external file DBSIZE.XML.
SAPinst prompts you to enter MaxDatafileSize in MB:
n 0: Datafile size defined in DBSIZE.XML is not changed.
30/178
...
PUBLIC
03/28/2008
2
2.5
Planning
Running Adobe Document Services on Nonsupported Platforms
Parameters
Description
Enter Your Values
n 2000: Default datafile size.

n 10000: Maximum datafile size.
For more information about space requirements of the SAP
datafiles (sapdata 1 - 4), see Requirements for the Database
Instance [page 51].
Database Instance RAM
The RAM that is required for the database instance

...
installation.
The default value used by SAPinst is 50 percent of the entire
RAM.
For more information about minimum RAM, see
Requirements for the Database Instance [page 51].
Login Shell
SAPinst only prompts you for this parameter if you use a

login shell other than the recommended C shell (csh).
...
2.5 Running Adobe Document Services on Nonsupported

Platforms
Adobe document services (ADS) are currently supported on a limited set of 64-bit platforms for
SAP NetWeaver.
Procedure
To use ADS in SAP landscapes on nonsupported platforms, you have to install an additional
standalone SAP system with AS Java on a platform supported by ADS.
2.6 Application Sharing Server as an Optional Standalone Unit

Application Sharing Server for real-time collaboration provides data streaming services that enable
application sharing capabilities provided by SAP NetWeaver collaboration. The server handles the
flow of data between portal users collaborating through the real-time application sharing feature.
Application Sharing Server lets users share their Windows desktop or individual applications with
other portal users in real time. Remote users can interact directly with the shared desktop or
application as if they were sitting at the host machine.
The server is installed automatically with usage type Enterprise Portal (EP) on the portal host. In
a cluster environment, the load generated by the Application Sharing Server is replicated to all
instances of the cluster. This generates load on all dialog instance hosts.
03/28/2008
PUBLIC
31/178
2
2.6
Planning
Application Sharing Server as an Optional Standalone Unit
Note
You can only use Application Sharing Server with SAP NetWeaver systems with usage type EP.
Planning
For test or demo purposes, you can run the Application Sharing Server on the portal machine.
Recommendation
For production use, we recommend that you install the server as an optional standalone unit on a
dedicated host. To do this, you perform a separate installation as described in this documentation.
By removing Application Sharing Server traffic from the portal host, you reduce the networking and
J2EE Engine demands on that machine, which improves the overall performance of the portal.
When you install usage type EP, the Application Sharing Server is installed automatically. If you do
not intend to use the Application Sharing Server, you can disable it. For more information, see
Post-Installation Tasks for Application Sharing Server [page 116].
You can install Application Sharing Server on a dedicated host before or after installing the usage type
EP. However, you can only complete the post-installation steps after you have installed usage type EP.
Preparation
Prepare the Application Sharing Server installation host for an AS Java central system installation:
1.
2.
3.
4.
Check hardware and software requirements [page 43].

Set up file systems [page 59].
Install the Java Development Kit [page 71].
Prepare the installation DVDs [page 73].
Installation
1. Run SAPinst to install Application Sharing Server as an optional standalone unit [page 102].
2. During the installation of the Oracle database instance, SAPinst stops the installation and prompts
you to install the Oracle database software [page 97].
Post-Installation
Perform the post-installation steps for an AS Java central system installation on the Application
Sharing Server installation host:
1.
2.
3.
4.
5.
Apply the latest kernel and support packages [page 109].

Perform post-installation steps for Adobe Document Services [page 113].
Perform post-installation steps for Application Sharing Server [page 116].
Ensure the security of Java standalone users stored in the database [page 118].
Check the SAP Java documentation [page 124].
32/178
PUBLIC
03/28/2008
2
2.7
Planning
High Availability: Planning the Switchover Cluster
6. Access configuration documentation in the SAP Solution Manager [page 125].

2.7 High Availability: Planning the Switchover Cluster

You can reduce unplanned downtime for your high-availability (HA) SAP system by setting up a
switchover cluster. This setup replicates critical software units known as single points of failure
(SPOFs) across multiple host machines in the cluster. In the event of a failure on the primary node,
proprietary switchover software automatically switches the failed software unit to another hardware
node in the cluster. Manual intervention is not required. Applications accessing the failed software
unit experience a short delay but can then resume processing as normal.
Switchover clusters also have the advantage that you can deliberately initiate switchover to free up a
particular node for planned system maintenance. Switchover solutions can protect against hardware
failure and operating system failure but not against human error, such as operator errors or faulty
application software.
Without a switchover cluster, the SAP system SPOFs central services instance, the database instance,
and the central file share are vulnerable to failure because they cannot be replicated. All of these
can only exist once in a normal SAP system.
You can protect software units that are not SPOFs against failure by simply replicating them. For
example, you can add additional dialog instances (that is, additional application servers). This
complements the switchover solution and is an essential part of building HA into your SAP system.
Recommendation
We recommend switchover clusters to ensure HA for your SAP system.

A switchover cluster consists of:
n A hardware cluster of two or more physically separate host machines to run multiple copies of the
critical software units, in an SAP system the SPOFs referred to above
n Switchover software to detect failure in a node and switch the affected software unit to the standby
node, where it can continue operating
n A mechanism to enable application software to seamlessly continue working with the switched
software unit normally this is achieved by virtual addressing (although identity switchover
is also possible)
03/28/2008
PUBLIC
33/178
2
2.7
Planning
Prerequisites
You must first discuss switchover clusters with your hardware partner because this is a complex
technical area. In particular, you need to choose a proprietary switchover product that works with
your operating system.
We recommend that you read the following documentation before you start:
n Check the informations and the installation guides that are available at
http://sdn.sap.com/irj/sdn/ha.
n The standalone replicated enqueue server is a major contribution to an HA installation and is
essential for a Java system. We strongly recommend you to use it for an ABAP system.
For more information about how to install the standalone replicated enqueue server, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP
NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology Client/Server
Technology The SAP Lock Concept Standalone Enqueue Server Installing the Standalone Enqueue Server
Features
The following figure shows the essential features of a switchover setup:

Figure 4:
Note
This figure and the figures in this section are only examples. You need to discuss your individual HA
setup with your HA partner.
34/178
PUBLIC
03/28/2008
2
2.7
Planning
The following figure shows an example of a switchover cluster in more detail:

Figure 5:
Constraints
This documentation concentrates on the switchover solution for the central services instance. For
more information about how to protect the NFS File System and the database instance by using
switchover software or (for of the database) replicated database servers, contact your HA partner.
You need to make sure that your hardware is powerful enough to handle the increased workload after
a switchover. Some reduction in performance might be acceptable after an emergency. However, it is
not acceptable if the system comes to a standstill because it is overloaded after switchover.
End of: HA (UNIX)
03/28/2008
PUBLIC
35/178
This page is intentionally left blank.
Preparation
3 Preparation
You have to complete the following preparations:

1. You perform the switchover preparations [page 38] for a high-availability (HA) system.
End of: HA (UNIX)
2.
3.
4.
5.
You check the hardware and software requirements [page 43].

If required, you create operating system users manually [page 56].
You set up file systems and raw devices [page 59].
If you want to perform a distributed installation, you export and mount global directories:
a) On the SAP trans host, you export the trans directory to SAP global host, central instance host,
database instance host, and if required to the dialog instance host(s).
b) On the SAP global host, you export subdirectories exe, global, profile of /sapmnt/<SAPSID>
to central instance host, database instance host, and if required to the dialog instance
host(s).
c) You mount subdirectories exe, global, profile of /sapmnt/<SAPSID> and directory trans on
the database instance host and on the central instance host. If you want to install one or more
dialog instance(s), you also have to mount these directories on the dialog instance host.
For more information about exporting and mounting directories, see:
n Exporting and Mounting the Global Transport Directory [page 69]
n Exporting and Mounting Directories via NFS for AIX [page 70]
6. You generate the SAP Solution Manager Key [page 71].
7. You install the Java Development Kit [page 71].
8. You prepare and mount the installation media [page 73].
If required, you can optionally prepare user management for an external ABAP system [page 135].
03/28/2008
PUBLIC
37/178
3
3.1
Preparation
High Availability: Switchover Preparations
3.1 High Availability: Switchover Preparations

3.1.1 Preparing for Switchover

This section describes the extra preparations you need to make for a high availability (HA) installation.
For more information, consult your HA partner.
You need to perform the preparations listed below on host A and after you have installed the central
services (SCS) instance on host B.
Prerequisites
You have already installed the hardware that is, hosts, disks, and network and decided how
to distribute the database, SAP instances, and (if required) Network File System (NFS) server over
the cluster nodes (that is, over the host machines). For more information, see Planning the Switchover
Cluster [page 33].
Procedure
1. You check that your system meets the hardware and software requirements [page 43] for an HA setup,
including the switchover software.
2. You set up file systems (that is, disk partitions), mount points, and (if required) NFS for your
HA system on:
a) Node A before the installation of the SCS instance with SAPinst
b) Node B after the installation of the SCS instance with SAPinst
To do this proceed as follows:
Caution
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
Recommendation
If possible, use journaled file systems (JFS), which allows much quicker recovery after a host
machine crash. With JFS, you can reduce the switchover time because the hard disk maintains
data integrity in the event of a system crash or if the system is otherwise halted abnormally.
a) You set up the required file systems [page 40] using mount points or NFS
38/178
PUBLIC
03/28/2008
3
3.1
Preparation
b) If required, you configure NFS [page 41], making sure you are using the virtual host name for NFS
to enable NFS switchover..
c) You assign the local file systems to mount points.
d) You assign the shared file systems to mount points in appropriate cluster packages.
Example
The figure below shows an example of the file systems and disks in an HA setup
Note that this is only an example. For more information on a setup that meets your needs,
consult your HA partner.
Figure 6:
3. You set up Domain Name System (DNS) on the virtual host.

Caution
4. You assign the virtual IP addresses and host names for SCS instance, and (if required) NFS to
appropriate cluster packages.
Caution
03/28/2008
PUBLIC
39/178
3
3.1
Preparation
Note
For more information on how to assign resources to cluster packages, ask your HA partner.
End of: HA (UNIX)
3.1.2 Setting Up File Systems for a High-Availability System

When you prepare a high-availability (HA) installation, you need to set up your file systems as
described here. For more information, consult your HA partner.
Procedure
1. Create the file systems or raw partitions for the central services (SCS) instance on shared disks. For
more information, see Setting Up File Systems and Raw Devices [page 59].
Note
The directories /<sapmnt>/<SAPSID> and /usr/sap/trans have to be mounted from a Network

File System (NFS), whereas /usr/sap/<SAPSID> is a directory of the AS instance that is always
mounted on the instance (not with NFS).
Therefore, if the central instance host is not the NFS server host, you might have to mount at
least the first two file systems on different physical disks from the third file system.
2. If the node that takes over the central instance also runs an AS instance during normal operation,
we recommend that you use a different approach for the file system for the /usr/sap/<SAPSID>
directory.
/usr/sap/<SAPSID> contains two subdirectories:
n SYS contains links to the central directory /<sapmnt>/<SAPSID>
n <INSTTYPE><NR> contains data for the local AS instance
The name <INSTTYPE><NR> is defined by the type of services and the application server number,
for example DVEBMSG00.
Only the directory <INSTTYPE><NR> needs to be migrated with the AS instance during the
switchover. Since the SYS subdirectory contains only links that do not require any space, it can
be created locally on each cluster node. Therefore, instead of /usr/sap/<SAPSID>, create a file
system for /usr/sap/<SAPSID>/<INSTTYPE><NR> with the usual <> substitutions. The file name
for the central instance is usually DVEBMGS00. This avoids mount conflicts when switching over to
a node on which an AS instance is already running. The DVEBMGS00 directory can join the tree
/usr/sap/<SAPSID> instead of mounting on top of it.
40/178
PUBLIC
03/28/2008
3
3.1
Preparation
Note
This approach becomes increasingly important when you want to cluster central services while
other instances run on the cluster hosts outside the control of the switchover software, so as to
use the resources efficiently. You must use this approach for integrated installations of the AS
with ABAP and Java stacks.
End of: HA (UNIX)
3.1.3 Configuring Network File System

If required, you configure Network File System (NFS), which is a system-wide Single Point-of-Failure
(SPOF), for a high-availability (HA) installation. For more information, consult your HA partner.
We regard NFS as an extension to the operating system. The switchover product protects NFS and
makes it transparently available to the SAP system in switchover situations.
You need to decide:
n How to protect NFS
n Which switchover cluster nodes NFS is to run on
The NFS configuration might depend on your database system. The directories need to be available
for the SAP system before and after a switchover.
Procedure
1. Check the NFS directories, several of which need to be shared between all instances of a system.
These directories are:
n /sapmnt/<SID>/profile
Contains the different profiles to simplify maintenance
n /sapmnt/<SID>/global
Contains log files of batch jobs and central SysLog
n /usr/sap/trans
Contains data and log files for objects transported between different SAP Web AS systems (for
example, development integration). This transport directory ought to be accessible by at least
one AS instance of each system, but preferably by all.
n /sapmnt/<SID>/exe
Contains the kernel executables. These executables ought to be accessible on all AS instances
locally without having to use NFS. The best solution is to store them locally on all AS instance
hosts.
2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.
03/28/2008
PUBLIC
41/178
3
3.1
Preparation
The requirements of your database system might dictate how NFS has to be set up. If required, you
can configure the NFS server on the cluster node of the CI or the DB.
In both cases the NFS clients use the virtual IP address to mount NFS. If the second node is used as
an additional SAP instance during normal operation (for example, as a dialog instance), it also
needs to mount the directories listed above from the primary node.
When exporting the directories with their original names, you might encounter the problem of
a busy NFS mount on the standby node. You can use the following workaround to solve this
problem:
a) On the primary server, mount the disks containing the directories:
/export/usr/sap/trans
/export/sapmnt/<SID>
b) The primary server creates soft links to the directories with the original SAP names:
/usr/sap/trans > /export/usr/sap/trans
/sapmnt/<SID> > /export/sapmnt/<SID>
Alternatively the primary server can also mount the directories:

/export/usr/sap/trans > /usr/sap/trans
/export/sapmnt/SID > /sapmnt/<SID>
c) The primary server exports:

d) The standby NFS mounts:

from virt.IP:/export/usr/sap/trans to /usr/sap/trans
from virt.IP:/export/sapmnt/<SID> to /sapmnt/<SID>
If the primary node goes down and a switchover occurs, the following happens:
n These directories on the standby node become busy:
/usr/sap/trans
/sapmnt/<SID>
n The standby node mounts disks to:

n The standby node configures the virtual IP address virt.IP

n The standby node exports:
n These directories on the standby node are accessible again:

/usr/sap/trans
/sapmnt/<SID>
End of: HA (UNIX)
End of: HA (UNIX)
42/178
PUBLIC
03/28/2008
3
3.2
Preparation
Hardware and Software Requirements
3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating system
and the SAP instances.
Caution
If your hosts do not fully meet the requirements, you might experience problems when working
with the SAP system.
Prerequisites
n
n
n
n
Contact your OS vendor for the latest OS patches.

Make sure that the host name meets the requirements listed in SAP Note 611361.
Check your keyboard definitions.
If you want to install a printer on a host other than the central instance host (for example, on a
separate database instance host), make sure that the printer can be accessed under UNIX.
Process Flow
1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operating

system releases.
2. Check the hardware and software requirements using:
n The Prerequisite Checker:
l Standalone (optional) before the installation process
For more information, see Running the Prerequisite Checker Standalone [page 44].
l Integrated in SAPinst (mandatory) as part of the installation process
For more information, see Running SAPinst on UNIX [page 85]
Note
For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
n The hardware and software requirements checklists for:
l AIX [page 45]
l Central system [page 47]
l Distributed or high availability system [page 49]
l If you want to install dialog instance(s), check the requirements for a dialog instance [page 53].
Note
If you want to use 32-bit SAP NetWeaver components, first check whether these
components can run on 64-bit operating systems. If so, we recommend you to use 64-bit
systems. If not, you can install an SAP dialog instance on 32-bit operating systems to run
these components. For all other SAP instances, you must use 64-bit systems.
03/28/2008
PUBLIC
43/178
3
3.2
Preparation
3. If you are installing a production system, the values provided by the Prerequisite Checker and the
hardware and software requirements checklists are not sufficient. In addition, do the following:
n You use the SAP Quick Sizer tool available at http://service.sap.com/sizing.
For more information about the SAP Quick Sizer and available sizing guides, see the Master Guide
SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .
Note
If you want to install usage type Development Infrastructure (DI), also check SAP Note
737368 for system requirements and sizing.
n You contact your hardware vendor, who can analyze the load and calculate suitable hardware
sizing depending on:
l The set of applications to be deployed
l How intensively the applications are to be used
l The number of users
3.2.1 Running the Prerequisite Checker in Standalone Mode

(Optional)
Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check the
hardware and software requirements for your operating system (OS) and the SAP instances.
Note
When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the
hardware and software requirements in the background.
Prerequisites
n You have installed the correct Java Development Kit (JDK) [page 71].
n You have prepared the installation master DVD on the required installation host [page 73].
n You make sure that the required prerequisites are met before starting SAPinst [page 81].
Procedure
1. You start SAPinst [page 85].

2. On the Welcome screen, choose <SAP System> Software Life-Cycle Options Additional Preparation
Options Prerequisites Check .
3. Follow the instructions in the SAPinst dialogs and enter the required parameters.
44/178
PUBLIC
03/28/2008
3
3.2
Preparation
Note
For more information about each parameter, position the cursor on the parameter field and
choose F1 in SAPinst.
When you have finished, the Parameter Summary screen appears summarizing all parameters you have
entered. If you want to make a change, select the relevant parameters and choose Revise.
4. To start the Prerequisite Checker, choose Start.
Result
The Prerequisite Check Results screen displays the results found. If required, you may also check the
results in file prerequisite_checker_results.html, which you find in the installation directory.
3.2.2 Requirements for AIX

The host machine must meet the following requirements:
Note
The information here is not intended to replace the documentation of the AIX operating system.
You can perform AIX-specific steps as follows:
n Manually by entering AIX commands with the appropriate options
n Using System Management Interface Tool (SMIT), a menu-driven system administration tool
If you have problems with the function keys, you can also use ESC and the corresponding number
to simulate the function key (for example, F4 is equivalent to ESC and 4 ).
Hardware Requirements
Requirement
Values and Activities
Tape drive
High-capacity tape drive with hardware compression is recommended.

You can test the drive /dev/rmt0 with this command:
tar -cvf /dev/<tape_device> <test_file>
The device name is always rmt0 unless more than one tape drive exists
DVD drive
03/28/2008
n ISO 9660 compatible

n You can configure multiple CD / DVD drives, but you cannot mount all of them. For
more information, see Mounting a CD / DVD for AIX [page 76].
PUBLIC
45/178
3
3.2
Preparation
Requirement
Required disks
For data security reasons, distribution over three disks is required. We recommend
you to distribute over five disks.
To display available disks, enter this command:
lspv
Disks marked none in the 3rd column are unused.

To display free space on a disk, enter this command:
lspv -p <disk_name>
Areas marked free in the 2nd column are unused.

If an advanced disk array is available (for example, RAID), contact your hardware vendor
to make sure that the data security requirements are covered by this technology.
RAM
To display RAM size in KB, enter the following command:

lsattr -El sys0 -a realmem
CPU
The recommended minimum hardware is either two physical single core processors or
one physical dual core processor.
Software Requirements
Requirement
C++ runtime level
Check the C++ runtime level with the following commands:

n AIX 6.x:
l #lslpp L xlC.aix61.rte
The output must be at least 9.0.0.1.
l #lslpp L xlC.rte
AIX
5.x:
n
#lslpp
L xlC.aix50.rte
l
l #lslpp L xlC.rte
Operating system
version
Check the operating system version with the following command:

lslpp -l bos.rte
The output must include the following or a larger version number:

bos.rte 5.2.0.50
AIX Maintenance
Level (ML) and
Technology Level
(TL)
46/178
n AIX 6.x: The output of the command oslevel -s should be at least 6100-00-01.
n AIX 5.3: The output of the command oslevel -s should be at least 5300-05-01
(TL 5 SP 1).
n AIX 5.2: The output of the command oslevel -r should be at least 5200-04 (ML 4).
PUBLIC
03/28/2008
3
3.2
Preparation
Requirement
LDAP (Lightweight
Directory Access
Protocol)
If you want to use LDAP, you require the following LDAP library:
libldap.a
Additional software Make sure that the following additional file sets are installed:
n bos.adt Base Application Development
n bos.perf performance and diagnostics tools
n perfagent.tools performance monitoring tools
n bos.perf.libperfstat Performance Statistics Library
For an overview of the installed file sets, enter the following command:
lslpp L | more
Install the necessary local code set by adding an additional language environment
as follows:
1. Start the System Management Interface Tool (SMIT) with the following command:
smitty mle_add_lang
2. Select the following:

n Cultural Conventions
n
to install:
ISO8859-1 German (Germany) [de_DE]

Language Translation to install:
ISO8859-1 German [de_DE]
This step installs the required bos.loc and bos.iconv file sets.
3. Additionally, check that all file sets are in a consistent state with this command:
lppchk v
Other Requirements
Requirement
Printer
Check whether a file can be printed with this command:

lp -d<printer_name> <test_file>
Check the status of your spool and the printers with this command:
lpstat -t
Keyboard
You can set the keyboard by typing this command on the directly connected console:
smitty chkbd
You can select your keyboard under Motif by setting a language environment (LANG),
for which a National Language Support (NLS) component is installed. The settings
take effect after reboot.
Network
Test the network connection to the database server with this command:
/etc/ping <db_server_name> 100 10
3.2.3 Requirements for a Central System

If you want to install a central system that is, all instances reside on one host the host must meet
the following requirements:
03/28/2008
PUBLIC
47/178
3
3.2
Preparation
The table below also lists the most relevant requirements for the Oracle database.
You get the full list of hardware and software requirements from the relevant
Oracle database installation guide for your operating system, which you can find at:
http://www.oracle.com/technology/documentation.
Recommendation
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. This
document provides information about all operating system prerequisites and is regularly updated.
Caution
If your database resides on Network Attached Storage (NAS) you need to review and implement the
Oracle NAS guidelines. You need to mount network file systems with specific mount options, which
you can find in the Oracle installation guide.
Caution
The database must be Oracle 10.2 or higher.

Requirement
Distribution of the
Oracle Database
We recommend distribution of the Oracle database over three disks (RAID5) for
data security reasons.
To decide how many hard disks are required for your Oracle database, see the
section Database System Configuration in SAP Database Guide: Oracle (BC-DB-ORA-DBA) in
the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English
SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key
Capability Platform-Wide Services Database Support Oracle SAP Database Guide: Oracle
(BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System .
Hard disk space
n Hard disk drives with sufficient space for the SAP system and the database
For more information, see Setting Up File Systems [page 59].
n 4.3 GB of temporary disk space for every required installation DVD that
you have to copy to a local hard disk. For more information, see Preparing the
Installation DVDs [page 73].
n 1.2 GB of temporary disk space for the installation.
RAM
1.5 GB (minimum), 4 GB (recommended)

4 GB (minimum), 5 GB (recommended)
End of: BI Java

End of: BI Java
Swap Space
48/178
Hard disk drives with sufficient space for swap: 3 to 4 * RAM
PUBLIC
03/28/2008
3
3.2
Preparation
Requirement
Network File System

(NFS)
If application servers are installed decentralized, Network File System (NFS) must
be installed.
Fonts and code pages
Make sure that the required fonts and code pages are installed.
National Language
Support (NLS)
Make sure that National Language Support (NLS) and corresponding saplocales
are installed.
GUI for Oracle Database On the database host, a graphical user interface (GUI), for example X11, is required
Installation
for the Oracle database software installation with runInstaller. For more
information, see the documentation of your operating system.
Oracle Interim Patches
Check SAP Note 839182 whether you require an interim patch for the Oracle
database installation. In this case, make sure you have the corresponding Perl
version as stated in that SAP Note.
Oracle Kernel
Parameters
Review the Oracle-recommended kernel parameters and shell limits for your
operating system with Oracle Database 10g Release 2 (10.2).
These are only recommendations from Oracle for optimizing the system
performance in production environments. If the recommended settings are not
suitable for your system you must tune the kernel parameters accordingly.
You can get the recommended shell limits and kernel parameters from the relevant
Oracle database installation guide for your operating system at:
http://www.oracle.com/technology/documentation
3.2.4 Requirements for a Distributed or a High Availability

System
The following sections provide information about the hardware and software requirements in a
distributed system, where the following SAP instances can reside on different hosts:
n Central services instance [page 49]
n Central instance [page 50]
n Database Instance [page 51]
Note
If you install multiple SAP system instances on one host, you need to add up the requirements.
3.2.4.1 Requirements for the Central Services Instance

The central services instance host must meet the following requirements:
03/28/2008
PUBLIC
49/178
3
3.2
Preparation
Requirement
Hard disk space
n Hard disk drives with sufficient space for the central services instance
For more information, see Setting up File Systems [page 59].
you have to copy to a local hard disk. For more information, see Preparing
the Installation DVDs [page 73].
RAM
Swap Space
Requirement
Network File System

(NFS)
Network File System (NFS) must be installed.
3.2.4.2 Requirements for the Central Instance

The central instance host must meet the following requirements:
Requirement
Hard disk space
n Hard disk drives with sufficient space for the central instance.
For more information, see Setting Up File Systems [page 59] SAP File Systems .
RAM
Swap Space
Requirement
Network File System

(NFS)
If application servers are installed decentralized, Network File System (NFS) must
be installed.
50/178
PUBLIC
03/28/2008
3
3.2
Preparation
Requirement
Required fonts and code

pages
National Language
Support (NLS)
Make sure that National Language Support (NLS) and corresponding saplocales
are installed.
3.2.4.3 Requirements for the Database Instance

The database host must meet the following requirements:
The table below lists the most relevant requirements for the Oracle database instance host.
You get the full list of hardware and software requirements from the relevant
Oracle database installation guide for your operating system, which you can find at:
Recommendation
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. This
document provides information about all operating system prerequisites and is regularly updated.
Caution
If your database resides on Network Attached Storage (NAS) you need to review and implement the
Oracle NAS guidelines. You need to mount network file systems with specific mount options, which
you can find in the Oracle installation guide.
Caution
The database must be Oracle 10.2 or higher.

Requirement
Distribution of the Oracle We recommend distribution over three disks (RAID5) for data security reasons.
Database
To decide how many hard disks are required for your Oracle database, see the
Database System Configuration guide in SAP Database Guide: Oracle (BC-DB-ORA-DBA)
in the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library
English SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform
by Key Capability Platform-Wide Services Database Support Oracle SAP Database
Guide: Oracle (BC-DB-ORA-DBA) Getting Started with Oracle and the SAP System .
03/28/2008
PUBLIC
51/178
3
3.2
Preparation
Requirement
Hard disk space
n 20 GB plus space for the SAP data file systems

For space requirements of the SAP data file systems (sapdata
following file:
<Export_DVD>/EXP1/DB/ORA/DBSIZE.XML.
1 - 4), see the
Note
The values listed in DBSIZE.XML are only guiding values. Each sapdata<n>
file can grow up to 10 GB maximum.
For more information about the required disk space per file system, see Setting
Up File Systems and Raw Devices Oracle File Systems [page 65]
n 4.3 GB of temporary disk space for every required installation DVD you have
to copy to a local hard disk.
For more information, see Preparing the Installation DVDs [page 73]
RAM
500 MB (minimum), 2 GB (recommended)

1 GB
The default value used by SAPinst is 50 percent of the entire RAM.
Depending on the amount of data involved, the requirements might change.
You can do one of the following to get a more precise sizing definition that
reflects your particular system load:
n Contact a hardware vendor. The vendor analyzes the load and calculates
suitable hardware sizing.
n Contact the person in charge of installation or your Oracle Competence
Center.
Swap Space
Requirement
Network File System (NFS)
If application servers are installed decentralized, Network File System (NFS)

must be installed.
Required fonts and code

pages
National Language Support

(NLS)
Make sure that National Language Support (NLS) and corresponding

saplocales are installed.
GUI for Oracle Database

Installation
On the database host, a graphical user interface (GUI), for example X11, is
required for the Oracle database software installation with runInstaller. For
more information, see the documentation of your operating system.
52/178
PUBLIC
03/28/2008
3
3.2
Preparation
Requirement
Oracle Interim Patches
Check SAP Note 839182 whether you require an interim patch for the Oracle
database installation. In this case, make sure you have the corresponding Perl
version as stated in that SAP Note.
Oracle Kernel Parameters
Review the Oracle-recommended kernel parameters and shell limits for your
operating system with Oracle Database 10g Release 2 (10.2).
These are only recommendations from Oracle for optimizing the system
performance in production environments. If the recommended settings are
not suitable for your system you must tune the kernel parameters accordingly.
You can get the recommended shell limits and kernel parameters from the
relevant Oracle database installation guide for your operating system, which
you can find at:
3.2.5 Requirements for a Dialog Instance

The dialog instance host must meet the following requirements:
Requirement
Hard disk space
n Hard disk drives with sufficient space for the dialog instance.
For more information, see Setting up File Systems [page 59].
RAM
500 MB minimum, 1 GB recommended
Swap Space
Requirement
SAP kernel
Make sure that the SAP kernel of the central instance has at least the patch level
of the SAP kernel on the SAP Kernel DVD that is used for the installation of the
dialog instance.
We recommend that you apply the most current SAP kernel from the SAP Service
Marketplace at http://service.sap.com/swdc.
Network File System

(NFS)
Network File System (NFS) must be installed.
03/28/2008
PUBLIC
53/178
3
3.2
Preparation
3.2.6 Checking and Modifying the AIX Kernel

To run an SAP system on AIX with an Oracle database, you must check and if necessary modify
the UNIX operating system kernel.
Recommendation
We recommend that all UNIX kernel modifications be performed by your UNIX system
administrator.
Procedure
1. Asynchronous I/O: If the database is installed using file systems, the settings for asynchronous I/O
(aio) should be as follows:
maxservers = minservers = 1.2 * number of data files used for the database.
Set these values as follows:
a) Enter:
smitty aio or
smit aio
b) Select Change / Show Characteristics of Asynchronous I/O.

c) Enter the appropriate numbers for MINIMUM and MAXIMUM number of servers.
Note
If maxserver is greater than minserver, the surplus asynchronous I/O processes are charged
against the database system rather than root, and have a lower scheduling priority. Experience
shows that all processes become active very quickly and, once active, the asynchronous I/O
servers are never stopped. Therefore it is simpler and more efficient to set them to the same
value at startup.
2. The setting for Maximum number of processes allowed per user may need to be increased on the database
server. If you have increased the number of maxservers, then you should check this setting to
make sure that the Maximum number of processes allowed per user is at least greater than the maximum
number of aioservers. This is not an issue if the values set as recommended above. Actually,
it must be greater than the sum of the maximum number of aioservers plus all of the other
processes of the ora<dbsid> user.
a) As a rule of thumb, set maxprocs to the following:
n Small system: 512
n Medium system: 2048
n Large system: 4096
If you are not sure which value is applicable, choose the higher value.
54/178
PUBLIC
03/28/2008
3
3.2
Preparation
Note
Setting maxprocs to a higher value than the number of processes that are actually used
does not cause any extra overhead.
b) Set the Maximum number of Processes allowed per user to be greater than maxservers plus the result
from step a.:
A) Enter:
smitty or
smit
B) Select System Environments.

C) Select Change / Show Characteristics of Operating System.
D) Enter the appropriate number for Maximum number of processes allowed per user, and choose Enter.
3. Adjust the minperm and maxperm settings according to SAP Note 973227.
3.2.7 Setting up Swap Space for AIX

1. Check the allocated swap space:
a) To start the System Management Interface Tool (SMIT), enter the following command:
smitty.
b) Perform one of the following steps:
n Choose Physical & Logical Storage Logical Volume Manager Paging Space List All Paging Spaces
n Enter this command:
lsps a
2. Check if there is sufficient swap space: 3 to 4 * RAM is recommended.

3. If required, add another paging space using smitty:
a) Choose Physical & Logical Storage Logical Volume Manager Paging Space Add Another Paging Space
A list of volume group names is displayed.
b) Select a volume group.
c) Enter the size of paging space in logical partitions.
d) Set Start using this paging space NOW ? to YES.
e) Set Use this paging space each time the system is RESTARTED to YES.
f) To exit smitty, choose F10 .
g) To check the results, follow the procedure described above in step 1.
03/28/2008
PUBLIC
55/178
3
3.3
Preparation
Creating Operating System Users
3.3 Creating Operating System Users
3.3.1 Network Information Service

If you use Network Information Service (NIS), you need to distribute users over the network.
Caution
If you do not create users manually, SAPinst creates them automatically during the installation
All users must have identical environment settings. If you change the environment delivered by
SAP, such as variables, paths, and so on, SAP does not assume responsibility.
SAPinst checks all required users, groups, and services on the local machine. If you manage users,
groups or services network-wide in your company, we recommend that you create the user and
group NIS entries before running SAPinst as described in Creating Operating System Users and Groups
Manually (Optional) [page 56].
SAPinst checks if the required services are available on the host and creates them if necessary. See the
log messages about the service entries and adapt the network-wide (NIS) entries accordingly.
SAPinst checks the NIS users, groups and services using NIS commands. However, SAPinst does not
change NIS configurations.
3.3.2 Creating Operating System Users and Groups

If you do not want SAPinst to create operating systems users, groups and services, you can optionally
create them manually before the installation.
If you want to use global accounts that are configured on a separate host, you start SAPinst and
choose Life Cycle Management Preparation Operating System Users and Groups . For more information,
see Running SAPinst on UNIX [page 85].
Users and Groups
SAPinst checks whether the required users and groups already exist. If not, it creates new users and
groups as necessary.
SAPinst chooses available user IDs and group IDs unless you are installing a dialog instance. On a
dialog instance you have to enter the same IDs as on the central instance host.
As a general requirement, the user IDs and the group IDs must be the same on all hosts.
56/178
PUBLIC
03/28/2008
3
3.3
Preparation
Caution
If you use NFS-V4 file system, then you have to create the ora<dbsid> user on the NFS server. You
can do this either manually or by running Operating System Users and Groups. This user must have the
same user ID as the ora<dbsid> user on the database server.
Otherwise, you get the error message FSL-02098 Could not change owner of ... during the
installation of the database instance.
Caution
The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers
belonging to the same SAP system.
This does not mean that all users and groups have to be installed on all SAP servers.
Caution
Do not delete any shell initialization scripts in the home directory of the OS users. This applies even
if you do not intend to use the shells that these scripts are for.
Users and Groups
User
Primary Group
Additional Group(s)
Comment
<sapsid>adm
sapsys
oper, dba, sapinst
SAP system administrator
<smdsid>adm
sapsys
sapinst
Diagnostics Agent
administrator
ora<dbsid>
dba
oper, sapinst
Database administrator
Caution
If these operating system users already exist, make sure that they are assigned to group sapinst.
Caution
If you install a distributed system and you do not use central user management (for example, NIS),
and you use local operating system user accounts instead, user <sapsid>adm and the database
operating system user must have the same password on all hosts.
Groups and Members
Groups
Members
sapsys
<sapsid>adm, <smdsid>adm
oper
<sapsid>adm, ora<dbsid>
dba
<sapsid>adm, ora<dbsid>
sapinst
<sapsid>adm, <smdsid>adm, ora<dbsid>
03/28/2008
PUBLIC
57/178
3
3.3
Preparation
The user ora<dbsid> is only required on the host where the database instance runs.
More Information
Creating AIX Groups and Users (Optional) [page 58]
3.3.3 Creating AIX Groups and Users (Optional)

Creating AIX Groups and Users
To create AIX groups and users, use the System Management Interface Tool (SMIT) :
1. Create groups as follows:
a) Enter the command smitty.
b) Choose Security and Users Groups Add a group .
c) Enter a group name for example, sapsys and set administration group to true.
d) Press F3 until the Security & Users menu appears.
2. To create users, proceed as follows:
a) Enter a user name, for example <sapsid>adm.
b) Enter all required values.
3. Set the initial password using the following command:
passwd <user>
Example
passwd <sapsid>adm
Checking Created Users
As user root check all existing users as follows:

1.
2.
3.
4.
Enter the command smitty.

Choose Security & Users Users Change/Show Characteristics of a User .
To get a list of users, choose F4 .
For user root and each created user <user> perform the following steps:
a) Select <user>.
b) Change field Soft CPU time to -1 (this is the default value).
c) Change field Soft CORE file size to 2097151 (this is the default value).
d) Change field Soft FILE size to 4194302.
Note
If you are using large file enabled file systems, set the field Soft FILE size to -1 (unlimited).
e) Change field Soft DATA segment to -1.
58/178
PUBLIC
03/28/2008
3
3.4
Preparation
Setting Up File Systems and Raw Devices
f) Change field Soft STACK size to -1.

You must make sure that the system-wide default HARD values are not explicitly defined to be
lower than the values given above. Check the file /etc/security/limits under the default:
stanza. If they are not explicitly set, then the values are as shown in the table at the top of the file.
Checking the Operating System
1.
2.
3.
4.

Choose System Environments Change/Show Characteristics of Operating System .
Change Maximum number of PROCESSES allowed per user to 500.
To exit SMIT, choose F10 .
More Information
For more information about the users and groups that are created either by SAPinst or manually, see
Creating Operating System Users and Groups Manually (Optional) [page 56].
3.4 Setting Up File Systems and Raw Devices

The following section(s) describe the directories that are required for the instances of an SAP system,
how to set up file systems and if required raw devices on operating system level:
n SAP Directories [page 59]
n Oracle Directories [page 65]
n Setting Up File Systems and Raw Devices for AIX [page 68]
3.4.1 SAP Directories

Depending on the installation option you have chosen, SAPinst automatically creates the directories
listed in the following figures and tables.
Before running the installation, you have to set up the required file systems manually. In addition,
you have to make sure that the required disk space for the directories to be installed is available
on the relevant hard disks.
The figure below assumes that you have set up one file system for the SAP system mount directory
<sapmnt> and one file system for the /usr/sap directory. However, you have to decide for which
directories you want to set up separate file systems. If you do not set up any file system on your
installation host, SAPinst creates all directories in the root directory /.
SAPinst prompts you only for the <sapmnt> directory during the installation. See also table Parameters
Relevant for the File System in Basic SAP System Parameters [page 20].
03/28/2008
PUBLIC
59/178
3
3.4
Preparation
Note
For more information about how to set up your file systems if you are performing an HA installation,
see High Availability: Setting Up File Systems [page 40].
End of: HA (UNIX)
Caution
SAPinst uses sapcpe to replicate the kernel automatically

from /usr/sap/<SAPSID>/SYS/exe/run/DIR_CT_RUN to
/usr/sap/<SAPSID>/<INSTANCE>/exe/DIR_EXECUTABLE for each SAP system instance.
The following entry in the start profile is responsible for this:
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF),
where $(_PF) points to the instance profile.
Do not delete DIR_CT_RUN from the instance profile. Otherwise, you cannot restart the system after
patches have been applied.
For more information, see Applying the Latest Kernel and Support Packages [page 109].
SAP Directories for a Java System (Unicode)
A Java standalone system is always a Unicode system.

Figure 7:
60/178
PUBLIC
03/28/2008
3
3.4
Preparation
The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance name
of a Java dialog instance is J<Instance_Number>, and the instance name of the Java central services
instance is SCS01.
Example
For example, the file system structure might look as follows:

On a central instance with SAP system ID C11 and instance name JC00, the J2EE Engine is installed to
/usr/sap/C11/JC00/j2ee, and the corresponding SDM is installed to /usr/sap/C11/JC00/SDM.
On a dialog instance with instance name J01, the J2EE Engine is installed to /usr/sap/C11/J01/j2ee.
No SDM is installed.
SAP Directories for the Diagnostics Agent
The installation creates the following SAP directories for the Diagnostics Agent.
Figure 8:
SAPinst extracts the Diagnostics Agent to the directory

/usr/sap/SMD/J<instance_number>/SMDAgent.
Example
/usr/sap/SMD/J98/SMDAgent
03/28/2008
PUBLIC
61/178
3
3.4
Preparation
SAP Directories in Detail

Note
The listed space requirements are initial SAP requirements.

Depending on your operating system, you might also have to add space for administrative purposes.
The following directories are global, that is, they are accessed by all hosts in the SAP system.
SAP Directories
Directory
Description
<sapmnt>/<SAPSID>
Software and data for one SAP system

n Central instance:
1.5 GB
This directory is physically located on the SAP global host.
In homogeneous systems, you need to mount it via NFS n Central services instance:
1.0 GB
(Network File System) for all hosts belonging to the same
n Dialog instance:
SAP system. It contains the following subdirectories:
This directory is
n exe
mounted from the
This directory contains executable kernel programs.
global host.
If you install an SAP system with distributed instances,
you have to share this directory for all hosts with
the same operating system. For more information,
see Prerequisites Before Starting SAPinst: Distributed Instances
[page 83].
n global
This directory contains log files.
you have to share this directory for all hosts. For
more information, see Prerequisites Before Starting SAPinst:
Distributed Instances [page 83].
n profile
This directory contains the start and operations
profiles of all instances.
you have to share this directory for all hosts. For
more information, see Prerequisites Before Starting SAPinst:
Distributed Instances [page 83].
/usr/sap/<SAPSID>
Instance-specific data, symbolic links to the data for one n Central instance
system
l AS Java:
1.5 GB
This directory contains files for the operation of a local
instance.
l For BI, add 2.0 GB.
There is a subdirectory <INSTANCE_NAME> for each instance
l For EP, add 2.0 GB.
installed on the local instance host. The directory SYS
n Dialog instance:
See the space
contains only soft links to appropriate directories in
requirements above
/<sapmnt>/<SAPSID>/ for storing data used by several
for the central instance
instances.
minus one third of the
space requirements for
Note
Java software units or
SAPinst creates the subfolder
usage types.
62/178
Space Required
PUBLIC
03/28/2008
3
3.4
Preparation
Directory
Description
Space Required
/usr/sap/<SAPSID>/<INSTANCE_NAME>/SDM
only for the central instance of ABAP+Java or Java

systems.
For more information about SDM, see Checking the Java
Documentation [page 124].
n Central services instance:

1.0 GB
There are subdirectories of /usr/sap/<SAPSID>/SYS with

symbolic links to subdirectories of /<sapmnt>/<SAPSID>:
n /usr/sap/<SAPSID>/SYS/profile is linked to
n
/<sapmnt>/<SAPSID>/profile
/usr/sap/<SAPSID>/SYS/global
/<sapmnt>/<SAPSID>/global
/usr/sap/<SAPSID>/SYS/exe/run
is linked to
/usr/sap/<SAPSID>/SYS/exe/dbg,
is linked to
which is linked to
/<sapmnt>/<SAPSID>/exe
Note
SAP system ABAP (Non-Unicode) + Java only:

/usr/sap/<SAPSID>/SYS/exe/run is linked to
<sapmnt>/<SAPSID>/exe/uc
SAPinst sets up these directory structures during the

installation.
Executables located in/usr/sap/<SAPSID>/SYS/exe/run
are replicated by sapcpe to the exe directory of instances
of the type <INSTANCE_NAME> and SCS<No>.
Note
Make sure that sufficient space is available in directory

/usr/sap/<SAPSID>/<INSTANCE_NAME>, since this stores
SAP traces for the instance. Changes in SAP system
profiles can also affect the disk space.
/usr/sap/trans
03/28/2008
Global transport directory for all SAP systems

For more information about exporting and mounting
the global transport directory, see Exporting and Mounting the
Global Transport Directory [page 69]
The global transport directory is used by the Change
Management Service (CMS). The CMS helps you to
organize development projects in the ABAP Workbench
and in Customizing, and then transport the changes
between the SAP systems in your system landscape.
If you select the checkbox Prepare SAP System for NWDI
Integration on the screen SAP System > NWDI Landscape
during the Define Parameters phase of the installation,
SAPinst copies all SCAs belonging to the usage types
PUBLIC
n For the installation of

all instances: 500 MB
n For the use of all
instances: 2 GB
63/178
3
3.4
Preparation
Directory
Description
Space Required
or software units you install to the global transport

directory.
For more information, see http://help.sap.com/nw70
SAP NetWeaver 7.0 Library English SAP NetWeaver Library
SAP NetWeaver by Key Capability Solution Life Cycle
Management by Key Capability Software Life Cycle Management
Software Logistics Working with the Development Infrastructure
Administration of the Development Infrastructure Setting Up the
Development Landscape: Landscape Configurator
For more information about the directories required for the database instance, see Oracle Directories
[page 65].
SAP Directories for the Diagnostics Agent in Detail
Note
The listed space requirements are initial SAP requirements.

Depending on your operating system, you might also have to add space for administrative purposes.
Space
Required
Directory
Description
/usr/sap/<SMDSID>/J<instance_number>
Instance-specific data of the Diagnostics Agent

500 MB
Contains the following subdirectories:
n sapinst
Contains log files of the installation
n SMD Agent
Contains the Diagnostics Agent software and
properties files.
n script
Contains the following local scripts:
l smdstart.sh
This script is used to start the local
Diagnostics Agent.
l smdstop.sh
This script is used to stop the local Diagnostics
Agent.
l smdadmin.sh
This script is used to manage the local
Diagnostics Agent.
work
n
This is the work directory of the Diagnostics
Agent
64/178
PUBLIC
03/28/2008
3
3.4
Preparation
Directory
Description
/usr/sap/<SMDSID>/SYS/profile
Contains the profiles of the Diagnostics Agent

instance
/usr/sap/<SMDSID>/exe
Contains the following global scripts:

n smdstart.sh
This script is used to start one or more
Diagnostics Agent(s) available in the system
landscape.
n smdstop.sh
This script is used to stop one or more
landscape.
n smdadmin.sh
This script is used to manage one or more
landscape.
Space
Required
3.4.2 Oracle Directories

The figure below assumes that you have set up one file system for the oracle directory. However, you
have to decide yourself for which directories you want to set up separate file systems. If you do not set
up any file system on your installation host, SAPinst creates all directories in the root directory /.
Note
Unicode systems require additional hardware resources. You can find more information about
Unicode SAP systems at http://service.sap.com/unicode.
Set up the required file system nodes for the Oracle database before the installation.
03/28/2008
PUBLIC
65/178
3
3.4
Preparation
Figure 9:
Oracle Directories
Oracle Directories
Directory
Description
Space Required
/oracle
Oracle base directory
50 MB for Oracle software
/oracle/client
File system for Oracle client software

SAPinst creates the directory
100 MB
/oracle/client/102_64/instantclient
during the installation.

/oracle/stage/102_64
Installation and upgrade directory for

database software (staging area)
This directory is also used for Oracle
upgrades. We recommend that you do not
delete it after the installation.
5.5 GB
/oracle/<DBSID>
Home directory of user ora<dbsid>

We recommend that /oracle/<DBSID> does
not reside in the root directory. It must
reside in a file system with support for large
files.
For more information about how to create
file systems larger than 2 GB on your
operating system, see:
Setting Up File Systems and Raw Devices for AIX
[page 68]
Therefore, either create /oracle/<DBSID>
as a separate file system with support for
large files or create /oracle as a file system
100 MB for files of user

ora<dbsid> (for example,
log files)
66/178
PUBLIC
03/28/2008
3
3.4
Preparation
Directory
Description
Space Required
with support for large files and create

/oracle/<DBSID> as a directory in /oracle.
/oracle/<DBSID>/102_64
Home directory for Oracle instance <DBSID>

(<ORACLE_HOME>).
<ORACLE_HOME> must reside on a local disk. It
cannot be a softlink.
n Database instance: 4.0

GB
n All other instances:
200 MB
Make sure that this file
system has permissions
777.
/oracle/<DBSID>/origlogA
Original set A of redo logs
200 MB
/oracle/<DBSID>/origlogB
Original set B of redo logs
200 MB
/oracle/<DBSID>/mirrlogA
Mirrored set A of redo logs
200 MB
/oracle/<DBSID>/mirrlogB
Mirrored set B of redo logs
200 MB
/oracle/<DBSID>/oraarch
New standard backup file system for Oracle

offline redo logs
Use a separate disk for the file system
/oracle/<DBSID>/oraarch.
The file system /oracle/<SAPSID>/saparch
still remains but now only contains brbackup
log files. /oracle/<SAPSID>/saparch is
automatically created by SAPinst.
For the installation,

the archive directory
/oracle/<DBSID>/sapreorg
Working directory for database

administration
1.5 GB
/oracle/<DBSID>/sapdata1
SAP data
SAP data
SAP data
SAP data
For space requirements

of the SAP data file
systems required for
the installation, see the
following file:
/oracle/<DBSID>/oraarch
requires at least 400 MB

free disk space. For the
operation of your SAP
system, we recommend
that the archive directory
provides enough space
for archives between two
backups. In a production
system, the amount
archived each day is
between 300 MB and 1 GB.
<Export_DVD>/EXP1/
DB/ORA/DBSIZE.XML.
See also SAP Note 972263

Pre-Installation File
requirements of Oracle sapdata
file systems
03/28/2008
PUBLIC
67/178
3
3.4
Preparation
3.4.3 Setting Up File Systems and Raw Devices for AIX

Setting up File Systems
Note
If you want to create file systems larger than 2 GB, see SAP Note 129439.
Note that large files can lead to performance degradation due to access synchronization over the
nodes. For performance reasons, smaller files are recommended for very active data.
1. Create one logical volume for each file system listed in the appropriate SAP profile:
a) Using SMIT, choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a
Logical Volume .
b) Enter a volume group name, for example, sapr3vg.
c) Enter a logical volume name, for example, lvsap01.
d) Enter the number of logical partitions.
e) Press F3 until the Physical & Logical Storage menu appears.
2. Create the file systems.
a) Using SMIT, choose Physical & Logical Storage File Systems Add/Change/Show/Delete File Systems
Journaled File Systems Add a Journaled File System on a previously defined Logical Volume Add a Standard
Journaled File System .
If you want to use large enabled file systems for files larger than 2 GB, you have to choose Add a
Large File Enabled Journaled File System instead of Add a Standard Journaled File System.
If you want to use JFS2 file systems, you have to choose Enhanced Journaled File System instead
of Journaled File System.
b) To get a list of logical volumes, choose F4 .
c) Select one logical volume.
Caution
Select the logical volume with the desired size.

d) Enter mount point as given in the file system list files.
Example
e) Set mount automatically to yes.

Setting up Raw Devices
1. Create volume group.

2. Create logical volume:
68/178
PUBLIC
03/28/2008
3
3.5
Preparation
Exporting and Mounting the Global Transport Directory
a)
b)
c)
d)
e)
f)
g)

Choose Physical & Logical Storage Logical Volume Manager Logical Volumes Add a Logical Volume .
Enter volume group name.
Enter logical volume name (for example: lvsap02).
Enter the number of logical partitions.
Set the logical volume TYPE to r3data and press ENTER.
To exit SMIT, choose F10 .
Note
The logical volume can be accessed through /dev/r<name
of raw log.vol>.
Example
A logical volume called lvsap02 points to the device name /dev/rlvsap02.

3. Accessing raw devices:
It is not necessary to create a link to access the volume.
3.5 Exporting and Mounting the Global Transport Directory

In your SAP system landscape, a global transport directory for all SAP systems is required.
n If this global transport directory already exists, make sure that it is exported on the global transport
directory host and mount it on the SAP instance installation host.
n If this global transport directory does not exist, proceed as follows:
l Create the transport directory (either on the central instance host or on a file server).
l Export it on the global transport directory host.
l If you did not create the transport directory on your SAP instance installation host, mount it
there.
Exporting the Transport Directory
1. Log on as user root to the host where the global transport directory /usr/sap/trans resides.
2. Make sure that /usr/sap/trans belongs to the group sapsys and to the user root.
3. If not already done, export the directory using Network File System (NFS).
Mounting the Transport Directory
Note
If the transport directory resides on your local SAP instance installation host, you do not need to
mount it.
1. Log on as user root to the central or dialog instance host where /usr/sap/trans is to be mounted.
03/28/2008
PUBLIC
69/178
3
3.6
Preparation
Exporting and Mounting Directories via NFS for AIX (Optional)
2. Create the mount point /usr/sap/trans.

3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.
More Information
Mounting Directories via NFS for AIX (Optional) [page 70]
3.6 Exporting and Mounting Directories via NFS for AIX

(Optional)
There are two ways of mounting directories via NFS:
n Manually
n Using the System Management Interface Tool (SMIT)
Procedure
To mount directories via NFS from the host where the directory to be mounted resides:
1. Log on as user root.
2. To start NFS services at the host where the directory to be mounted resides, use SMIT as follows:
b) Choose Communications Applications and Services NFS Network File System (NFS) Configure NFS
on this System Start NFS .
c) In the line Start NFS now, on system restart or both, enter: both.
d) Choose ENTER .
3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for
the host where the additional instance runs:
b) Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory
to Exports List .
c) Enter the path of the directory that you want to export (for example, <sapmnt>/<SAPSID>/exe).
d) Choose export mode (use read-write or read-only as required by SAP). In the line HOSTS allowed
root access, enter the name of the host where the additional instance runs. For security reasons,
this root access should be disabled after the installation.
e) In the line Export directory now, system restart or both, enter: both
f) Choose ENTER .
4. Create the mount point at the host where the additional instance runs: /usr/bin/mkdir
<sapmnt>/<SAPSID>/exe
5. Mount the directory on the host where the additional instance runs.
b) Choose Communications Applications and Services NFS Network File System (NFS) Add a File System
for Mounting .
70/178
PUBLIC
03/28/2008
3
3.7
Preparation
Generating the SAP Solution Manager Key
c) Enter the path name of the mount point.

d) Enter the path name of the remote directory (the directory of the central instance).
e) Enter the host where the remote directory resides.
f) Set Mount now, add entry to /etc/filesystems or both to both.
g) Set /etc/filesystems entry will mount the directory on system RESTART to yes.
h) Change Mount file system soft or hard to soft and press ENTER.
6. If you exported the directory with read-write access, check if the host where the future additional
instance is to run has write access to directory <sapmnt>/<SAPSID>/exe using the following
commands:
cd <sapmnt>/<SAPSID>/exe
touch test (create a file called test)
ls -l test (check if file test is created)
rm test (remove the file test)
3.7 Generating the SAP Solution Manager Key

You need to generate the Solution Manager key because the installation tool prompts for it during
the installation. Without this key, the installation process cannot continue.
Procedure
1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:
a) Order SAP Solution Manager as described in SAP Note 628901.
b) Install SAP Solution Manager as described in the documentation Installation Guide SAP Solution
Manager <Current Release> on <OS>: <Database> which is available at:
http://service.sap.com/instguides SAP Components SAP Solution Manager <Current
Release>
2. Generate the SAP Solution Manager key as described in SAP Note 811923.
Result
The SAP Solution Manager system displays the key for which you are prompted during the
installation of your SAP system.
3.8 Installing the Java Development Kit

You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK).
As of SAP NetWeaver 7.0 you must install the J2EE Engine with strong encryption.
03/28/2008
PUBLIC
71/178
3
3.8
Preparation
Installing the Java Development Kit
The J2EE Engine requires a Java Development Kit (Java 2 SDK, Standard Edition = JDK) on every
host where the J2EE Engine is to be installed. You need this for the system variants [page 17] with Java.
The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst and
the SAPinst GUI.
Note
If required, you can perform a remote installation using a standalone SAPinst GUI on a separate
Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with
the SAPinst GUI from a local host.
If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 94]. In
this case, you need at least a JRE on the local host to start the SAPinst GUI there.
Procedure
1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):
a) Go to http://service.sap.com/pam.
b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S) .
c) Choose tabstrip JSE Platforms.
Note
For more information about the recommended JDK version for your operating system and
about how to download it, see SAP Note 723909.
2. Make sure a valid JDK version is installed on every host on which you want to install an SAP
instance with the J2EE Engine, as follows:
n If the JDK is not already installed, you need to download and install it.
n If the JDK is already installed
Check the installed version of the JDK by entering the following command:
java -version
Note
SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.
If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.
3. As of SAP NetWeaver 7.0 strong encryption is mandatory for the J2EE Engine and for all usage types
that are deployed on it. You need to obtain the JCE policy files beforehand so that they can be
installed by SAPinst:
a) Download the JCE policy files for your platform at
http://www6.software.ibm.com/dl/jcesdk/jcesdk-p.
b) SAPinst installs the JCE policy files during the installation process.
c) Copy the JCE policy files to directory /usr/java14_64/jre/lib/security.
72/178
PUBLIC
03/28/2008
3
3.9
Preparation
Preparing and Mounting the Installation Media
3.9 Preparing and Mounting the Installation Media
3.9.1 Preparing the Installation DVDs

This section describes how to prepare the installation DVDs, which are available as follows:
n You obtain the installation DVDs as part of the installation package.
n You can also download the installation DVDs from SAP Service Marketplace [page 75].
Procedure
1. Identify the required DVDs for your installation as listed below.

Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs during
the installation.
Caution
The media names listed below are abbreviated.

You can find the full names of all media shipped with SAP NetWeaver 7.0 SR3 in the appropriate
Media List for SAP NetWeaver 7.0 SR3 at:
http://service.sap.com/installNW70 Installation Installation SAP NetWeaver Systems
Media List SAP NetWeaver 7.0 SR3 .
Note
If you are installing on an existing system using Multiple Components in One Database (MCOD),
the required DVDs differ.
Note
The Software Component Archives (SCAs) for the installation of Java-based SAP NetWeaver usage
types are on the SAP NetWeaver Java DVD.
Note
Do not use the Business Intelligence Content Add-On DVD for the installation of BI with
SAPinst. You have to install the BI Content Add-On later. For more information, see Configuring BI
Java Information Broadcasting [page 158].
End of: BI Java
The following table shows the required DVDs for the installation of an SAP system based on the
usage type AS Java:
03/28/2008
PUBLIC
73/178
3
3.9
Preparation
Note
For a central system, where all mandatory instances reside on one host, you need the installation
DVDs that are required for the central instance, central services instance, and database instance.
SAP Instance Installation
Required DVDs
Central services instance, central instance, n Installation Master DVD

dialog instance
n Kernel DVD
n NetWeaver Java SP14 DVD
n RDBMS Client DVD
Database instance
n
n
n
n
n
Installation Master DVD

Kernel DVD
NetWeaver Java SP14 DVD
RDBMS DVD
RDBMS Patch DVD (if available)
Note
For an MCOD system you require the RDBMS Client

DVD instead of the RDBMS DVD and the RDBMS Patch
DVD (if available).
n RDBMS Client DVD
2. Make the required installation media available on each installation host.

If you need information about how to mount DVDs on AIX, see Mounting a CD / DVD for AIX
[page 76].
Note
Depending on your installation type, one or more instances can reside on the same host. You
need to keep this in mind when you make the required installation media available on each
installation host.
For a central system, you need to make all required installation media available on the single
installation host.
Use one of the following methods to make DVDs available:
n Before the installation, copy DVDs manually to local hard disks.
n During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to the
path you entered in the Copy Package To column.
74/178
PUBLIC
03/28/2008
3
3.9
Preparation
Caution
n Mount the DVDs locally. We do not recommend you to use Network File System (NFS),
because reading from DVDs mounted with NFS might fail.
n If you copy the DVDs to disk, make sure that the paths to the destination location of the copied
DVDs do not contain any blanks.
n If you perform a local installation and there is only one DVD drive available on your
installation host, you must copy at least the Installation Master DVD to the local file system.
3.9.2 Downloading Installation DVDs from SAP Service

Marketplace (Optional)
You normally obtain the installation DVDs as part of the installation package from SAP.
However, you can also download installation DVDs from SAP Service Marketplace at:
http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group <SAP
solution> <SAP product> <SAP release> Installation and Upgrade <operating system> <database> .
If you download installation DVDs, note that DVDs might be split into several files. In this case, you
have to reassemble the required files after the download.
Prerequisites
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR
700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer
unpack current SAR files. For more information, see SAP Note 212876.
Procedure
1. Create a download directory on the host on which you want to run SAPinst.
2. Identify all download objects that belong to one installation DVD according to one or both of the
following:
n 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
...
03/28/2008
PUBLIC
75/178
3
3.9
Preparation
n Title
All objects that are part of an installation DVD have the same title, such as
<solution><DVD_name><OS> or <database>RDBMS<OS> for RDBMS DVDs.
3. Download the objects to the download directory.
4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number
for example 51031387_1, then 51031387_2, and so on.
During the download SAPCAR sets up the structure of the installation DVD.
Note
SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always accept
with Yes.
3.9.3 Mounting a CD / DVD for AIX

Note
<medium-mountdir> refers to either <cd-mountdir> or <dvd-mountdir>.
Use the following procedure to mount a CD / DVD:

Procedure

2. Add a CD / DVD file system.
b) Choose Physical & Logical Storage File Systems Add / Change / Show / Delete File Systems CDROM
File Systems Add a CDROM File System .
c) To get a list of device names, choose F4 .
Select a device name.
d) Enter the mount point <medium-mountdir>.
Example
<medium-mountdir>
is /sapcd
e) Choose ENTER .
3. Mount the CD / DVD as follows:
Note
Alternatively, you can mount the CD / DVD manually with the following command: mount
cdrfs -r /dev/cd0 /sapcd.
76/178
PUBLIC
-v
03/28/2008
3
3.9
Preparation
a)
b)
c)
d)
e)
f)
g)
h)
i)
j)
k)

Choose Physical & Logical Storage File Systems Mount a File System .
Place the cursor on File System Name and choose F4 .
Select the CD / DVD device /dev/cd0.
Place the cursor on field Directory over which to mount and choose F4 .
Select /sapcd.
Place the cursor on field Type of File System and choose F4 .
Select cdrfs.
Change Mount as Read Only system to YES
Choose ENTER .
To exit smitty, choose F10 .
03/28/2008
PUBLIC
77/178
Installation
4 Installation
Note
Make sure that you have completed the planning and preparation activities before you start the
installation.
This section provides information about the steps that you have to perform to install your SAP system
Process Flow
1. If required, you perform a high-availability installation [page 79].

End of: HA (UNIX)
2. You check the prerequisites for the instances that you want to install before starting SAPinst [page 81].
3. You install your SAP system using SAPinst [page 84].
Note
This note does not apply to the installation of a Java Add-In to an existing ABAP system:
Do not install the Oracle database software before you run SAPinst.
SAPinst stops and prompts you to install the Oracle database [page 97] while the installation of the
database instance is running.
If you install a system into an existing database (MCOD), this action is not required.
4. If required, you can install an Application Sharing Server as an optional standalone unit [page 102].
4.1 Performing a High-Availability Installation

This section describes how to perform a high-availability (HA) installation. For more information,
consult your HA partner.
Prerequisites
n You have completed all preparations, including preparing the installation of switchover units [page 38].
03/28/2008
PUBLIC
79/178
4
4.1
Installation
Performing a High-Availability Installation
n You have set the environment variable SAPINST_USE_HOSTNAME [page 84] to specify the virtual host
name for the installation. Alternatively you can specify the virtual host name in the command
to start SAPinst.
Procedure
1. Run SAPinst [page 85] to install the central services instance (SCS) using the virtual host name on
the primary cluster node, host A.
2. Prepare the standby node, host B, making sure that it meets the hardware and software
requirements and it has all the necessary file systems, mount points, and (if required) Network
File System (NFS), as described in Preparing for Switchover [page 38].
3. Set up the user environment on the standby node, host B.
For more information, see Creating Operating System Users and Groups Manually [page 56]. Make sure that
you use the same user and group IDs as on the primary node. Create the home directories of users
and copy all files from the home directory of the primary node.
4. Configure the switchover software and test that switchover functions correctly.
5. Install the database instance on the primary node, host A.
6. Install the central instance with SAPinst [page 85] on the primary node, host A.
Note
In a high-availability installation, the central instance does not need to be part of the cluster
because it is no longer a single point of failure (SPOF). The SPOF is now in the central services
instance (SCS), which is protected by the cluster.
instance (ASCS), which is protected by the cluster.
instances (SCS and ASCS), which are protected by the cluster.
7. If required, install additional dialog instances with SAPinst [page 85] to replicate the SAP system services
that are not a SPOF. These nodes do not need to be part of the cluster.
Note
Make sure that you complete the activities described in High Availability: Post-Installation Steps [page 116].
End of: HA (UNIX)
80/178
PUBLIC
03/28/2008
4
4.2
Installation
Prerequisites before Starting SAPinst
4.2 Prerequisites before Starting SAPinst
4.2.1 Prerequisites before Starting SAPinst: All Instances

This section provides information about running SAPinst that is valid for the installation of all
instances (central, central services, database, and dialog instance).
Prerequisites
n Make sure that you have defined the most important SAP system parameters as described in Basic
SAP System Parameters [page 20] before you start the installation.
n Check that your installation hosts meets the requirements for the installation services that you
want to install. For more information, see Running the Prerequisite Checker [page 44].
Procedure
1. If you want to install a dialog instance for an upgraded SAP system:

a) Edit the instance profile of the central services instance.
b) Set the parameter rdisp/msserv to 0.
c) Insert a line with the parameter rdisp/msserv_internal and set it to the port number that was
assigned before to rdisp/msserv.
d) Restart the central services instance.
Example
This shows the required change to the instance profile of the central services instance:
Before the change:
...
rdisp/msserv = 4711
...
After the change:
...
rdisp/msserv = 0
rdisp/msserv_internal = 4711
...
2. Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.
03/28/2008
PUBLIC
81/178
4
4.2
Installation
Note
SAPinst normally creates the installation directory sapinst_instdir directly below the
temporary directory. SAPinst finds the temporary directory by checking the value of the
environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses
/tmp as default installation directory.
Make sure that the temporary directory has the permissions 777.
The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These
executables are deleted again after SAPinst has stopped running.
If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C .
Caution
If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.
3. Make sure that you have at least 60 MB of free space in the installation directory for each installation
service. In addition, you need 200 MB free space for the SAPinst executables. If you cannot provide
200 MB free space in the temporary directory, you can set one of the environment variables TEMP,
TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables.
Shell Used
Command
Bourne shell (sh)
TEMP=<directory>
export TEMP
C shell (csh)
setenv TEMP <directory>
Korn shell (ksh)
export TEMP=<directory>
4. If you are installing a second or subsequent SAP system into an existing database, make sure
that the database is up and running before starting the installation. For more information, see
Installation of Multiple Components in One Database [page 129].
5. Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime
Environment (JRE).
6. If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for
AIX 64-bit.
7. Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>
is the host on which you want to display the SAPinst GUI.
Shell Used
Command
Bourne shell (sh)
DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh)
setenv DISPLAY <host_name>:0.0
Korn shell (ksh)
export DISPLAY=<host_name>:0.0
82/178
PUBLIC
03/28/2008
4
4.2
Installation
8. Check the following values for user root:

n In csh execute limit
Output
Properties
cputime
unlimited
filesize
unlimited
datasize
2097148 KB
stacksize
8192 KB
coredumpsize
unlimited
descriptors
8192
memorysize
unlimited
n In sh or ksh execute ulimit
-a
Output
Properties
time(seconds)
unlimited
file(blocks)
unlimited
data(kbytes)
2097148
stack(kbytes)
8192
coredump(blocks)
unlimited
nofiles(descriptors)
8192
memory(KBytes)
unlimited
If your parameter settings differ from the settings above, change these values accordingly.
Example
If you have to change the value for descriptors to 8192, proceed as follows:
l In csh execute:
limit descriptors 8192
l In sh or ksh execute:
ulimit -n 8192
4.2.2 Prerequisites before Starting SAPinst: Distributed

Instances
If you install a database or a dialog instance on a host other than the SAP Global host, you must
mount directories from the SAP Global host.
03/28/2008
PUBLIC
83/178
4
4.3
Installation
Installing an SAP System Using SAPinst
Prerequisites
n If you want to install the executables locally instead of sharing them, do not mount the exe
directory with Network File System (NFS). Instead, create <sapmnt>/<SAPSID>/exe as a local
directory (not a link) with a minimum of 1100 MB free space.
n If you are installing a heterogeneous SAP system (that is, the instances are installed on different
operating-system platforms), do not mount the exe directory. For more information, see
Heterogeneous SAP System Installations [page 160].
Procedure
1. Log on to the SAP Global host as user root and export the following directories with root access to
the host on which you want to install the new instance:
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
For more information, see Mounting Directories via NFS for AIX [page 70].
2. Log on to the host of the new instance as user root.
3. Create the following mount points and mount them from the SAP Global host:
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
4.2.3 Prerequisites Before Starting SAPinst: High Availability

For a high-availability (HA) SAP system you can set the environment variable SAPINST_USE_HOSTNAME
to specify the virtual host name before you start SAPinst.
If you do not set this environment variable now, you can specify an equivalent parameter for the
virtual host name when you run SAPinst [page 85].
Procedure
Set SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installing
an SAP instance.
End of: HA (UNIX)
4.3 Installing an SAP System Using SAPinst

The following sections tell you how to install the various instances of an SAP system, or a standalone
engine:
84/178
PUBLIC
03/28/2008
4
4.3
n
n
n
n
n
n
Installation
Running SAPinst on UNIX [page 85]

Using SAPinst GUI [page 91]
Interrupted Installation with SAPinst [page 92]
Performing a Remote Installation with SAPinst (Optional) [page 94]
Starting SAPinst GUI Separately (Optional) [page 95].
Entries in the Services File Created by SAPinst [page 97]
4.3.1 Running SAPinst on UNIX

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUI
and a GUI server, which both use Java.
This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running
on the same host. If required, you can instead perform a remote installation with SAPinst [page 94], where
SAPinst GUI is running on a separate host from SAPinst and the GUI server.
When you start SAPinst, SAPinst GUI and the GUI server also start. SAPinst GUI connects via a secure
SSL connection to the GUI server and the GUI server connects to SAPinst.
Procedure
1. Log on to your host as user root.

Caution
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. If you want to install a central instance, a central services instance, a database instance, or a dialog
instance, mount the Installation Master DVD
Mount the DVDs locally. We do not recommend that you use Network File System (NFS),
because reading from DVDs mounted with NFS might fail.
For more information about mounting DVDs, see Mounting a CD / DVD for AIX [page 76].
3. Start SAPinst from the Installation Master DVD in one of the following ways:
n Using the default installation directory (recommended)
Enter the following commands:
cd <Installation Master_DVD>/IM_<OS>
./sapinst
03/28/2008
PUBLIC
85/178
4
4.3
Installation
Note
If you are installing a high-availability system and you have not already set the environment parameter
SAPINST_USE_HOSTNAME [page 84] to specify the virtual host name, you can start SAPinst
as follows:
./sapinst SAPINST_USE_HOSTNAME=<virtual host name>
End of: HA (UNIX)
Caution
Make sure that your operating system does not delete the contents of the temporary directory
/tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for
example by using a crontab entry.
Caution
Make sure that your current working directory is not an IM_<OS> directory belonging to
another operating system.
For example, the following commands are incorrect and cause an error:
$ cd /sapcd2/IM_HPUX_IA64
$ /sapcd2/IM_HPUX_PARISC/sapinst
The following commands are correct:

$ cd /sapcd2/IM_HPUX_PARISC
$ /sapcd2/IM_HPUX_PARISC/sapinst
n Using an alternative installation directory

If you want to use an alternative installation directory, set the environment variable TEMP,
TMP, or TMPDIR.
For more information, see Prerequisites before Starting SAPinst: All Instances [page 81].
Note
n During the installation, the default ports 21200 and 21212 are used for communication between
SAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUI
server. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an error
message if one of these ports is already in use by another service.
In this case, you must execute sapinst using the following parameters:
SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>
GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>.
n To get a list of all available SAPinst properties, start SAPinst as described above with the option
-p:
86/178
PUBLIC
03/28/2008
4
4.3
Installation
./sapinst -p.
4. In the Welcome screen, choose one of the following installation options:
n SAP Systems
n Software Life-Cycle Options
The following tables provide more information about these installation options:
n SAP Systems
You use this option to install an SAP system with usage types or software units by choosing:
l Central system:
<SAP system> SAP Systems <Database> Central System
l All other system variants:
<SAP system> SAP Systems <Database> <System Variant> Based on <technical stack>
You can install the following system variants:
l Central System
l Distributed System
l High Availability System

End of: HA (UNIX)
The following tables provide an overview of the installation options available for these system
variants:
Note
l Choose the corresponding installation options from the tree structure exactly in the
order they appear for each system variant.
l To use global accounts that are configured on a separate host, you have to run the
installation option Operating System Users and Groups before you start the installation
l If required, to install a dialog instance for a central or distributed system, choose:
Software Life-Cycle Options Application Server Dialog Instance
See table Software Life-Cycle Options below.
l On the SAPinst screens, the term software unit generally applies to both SAP NetWeaver
usage types and SAP Business Suite software units.
Installation Services for a Central System
Installation Service
Remarks
Central System
Installs a complete SAP system including the following instances on one

host:
l Central services instance (SCS)
l Database instance
l Central instance
You can install a central system in the following parameter modes:
l Typical Mode
03/28/2008
PUBLIC
87/178
4
4.3
Installation
Remarks
If you choose Typical, the installation automatically uses default

settings. You only have to respond to a small selection of prompts.
However, you can change any of the default settings on the parameter
summary screen.
l Custom Mode
If you choose Custom, the installation prompts you for all parameters.
At the end, you can change any parameter on the parameter summary
screen.
Note
You require at least usage type AS Java. You can choose the usage types or
software units on the screen SAP System > Software Units.
Installation Services for a Distributed System
Installation Services
Remarks
Central Services Instance (SCS)
Mandatory step in installing a distributed SAP system with

usage types or software units based on AS Java.
Installs a central services instance (SCS) and prepares the
SAP global host.
Database Instance
Mandatory step in installing a distributed SAP system.

Installs a database instance.
You must have finished the Central Services Instance (SCS)
installation, before you can choose this installation service.
Central Instance
Mandatory step in installing a distributed SAP system on

several hosts.
Installs a central instance and enables additional usage
types or software units.
Note
You require at least usage type AS Java or AS ABAP. You

can choose the usage types or software units on the
screen SAP System > Software Units.
You must have finished the database instance installation.
Installation Services for a High Availability System
Remarks
Central Services Instance Installs a central services instance (SCS)

(SCS)
Database Instance
88/178
Installs a database instance
PUBLIC
03/28/2008
4
4.3
Installation
Remarks
Central Instance
Installs a central instance and enables additional usage types or software

units
Note
You require at least usage type AS Java. You can choose the usage types or
software units on the screen SAP System > Software Units.
Dialog Instance
Installs a dialog instance

Note
If you want to use 32-bit SAP NetWeaver components, first check

whether these components can run on 64-bit operating systems. If so, we
recommend you to use 64-bit systems. If not, you can install an SAP dialog
instance on 32-bit operating systems to run these components. For all
other SAP instances, you must use 64-bit systems.
n Software Life-Cycle Options

You use this option to perform the following tasks or to install the following components:
Remarks
Additional Preparation
Options
These preparation tasks comprise:

l Operating System Users and Groups
Allows you to use global accounts that are configured on a separate
host.
Caution
Perform this SAPinst option before you start the installation of

your SAP system.
l Prerequisites Check
Checks your hardware and software requirements before you
start the installation.
Otherwise, SAPinst automatically checks the hardware and
software requirements during the installation with the Prerequisite
Checker. If any changes are necessary to the SAP system or operating
system settings, SAPinst automatically prompts you. For more
information, see Running the Prerequisites Checker in Standalone Mode [page
44].
03/28/2008
PUBLIC
89/178
4
4.3
Installation
Remarks
Application Server
Choose Application Server <Database> Dialog Instance to install

one or more dialog instance(s) in an already installed SAP system,
if required.
Note
If you want to use 32-bit SAP NetWeaver components, first check

whether these components can run on 64-bit operating systems. If
so, we recommend you to use 64-bit systems. If not, you can install
an SAP dialog instance on 32-bit operating systems to run these
components. For all other SAP instances, you must use 64-bit systems.
LDAP Registration
LDAP Support
Sets up LDAP support for an application server instance.
Choose this option once per SAP system and after you have:
a) Configured the Active Directory on a Windows host by choosing
LDAP Registration Active Directory Configuration .
You have to configure the directory server only once. Afterwards
all SAP systems that should register in this directory server can
use this setup.
Note
The option Active Directory Configuration is only available for

Windows.
b) Installed an application server instance.
For more information about LDAP and Active Directory, see Integration
of LDAP Directory Services [page 131].
System Copy
Choose this service to perform a system copy.

For more information, see the system copy guide, which is available at:
http://service.sap.com/instguidesnw70 Installation Installation
SAP NetWeaver Systems
Uninstall
Choose this service to uninstall your SAP system, standalone engines,

or optional standalone units.
For more information, see Deleting an SAP System Using SAPinst [page 162]
5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
Note
To find more information on each parameter during the input phase of the installation, position
the cursor on the field of the respective parameter and press F1 .
After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.
This screen shows both the parameters that you entered and those that SAPinst set by default.
6. If required, change the displayed parameters as follows:
90/178
PUBLIC
03/28/2008
4
4.3
Installation
a) Select the parameters you want to change.

b) Choose Revise.
SAPinst displays input screens for the selected parameters.
c) Enter the new values for the parameters.
7. To start the installation, choose Start.
SAPinst starts the installation and displays the progress of the installation.
When the installation has successfully completed, SAPinst displays the screen Finished successfully.
Note
During the installation of the Oracle database instance, SAPinst stops the installation and prompts
you to install the Oracle database software [page 97].
This action is not required if you install a system into an existing database (MCOD).
After you have finished the installation of the Oracle database, you continue the database instance
installation by choosing OK in the SAPinst GUI of the database instance installation.
8. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.
Sometimes these remain in the temporary directory.
Note
If there are errors with SAPinst Self-Extractor, you can find the Self-Extractor log file
dev_selfex.out in the temporary directory.
Recommendation
We recommend that you keep all installation directories until you are sure that the system is
completely and correctly installed.
9. We recommend you to delete all files in the directory <user_home>/.sdtgui/.
10. If you have copied installation DVDs to your hard disk, you can delete these files when the
installation has successfully completed.
More Information
If you have problems during the installation, see Troubleshooting with SAPinst [page 160].
4.3.2 Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:
03/28/2008
PUBLIC
91/178
4
4.3
Installation
SAPinst GUI Functions
Input Type
Label
Description
Function key
F1
Displays detailed information about each input parameter.
Menu option
File Log off
Stops the SAPinst GUI, but SAPinst and the GUI server continue
running.
Note
If for some reason you need to log off during the installation
from the host where you control the installation with SAPinst
GUI, the installation continues while you are logged off. You can
later reconnect to the same SAPinst installation from the same or
another host. For more information, see Starting SAPinst GUI Separately
[page 95].
Menu option
File View Log
Displays the installation log (sapinst_dev.log)
Menu option
File
Cancels the installation with the following options:

n Stop
For more information, see the description of the message button
below.
n Continue
For more information, see the description of the message button
below.
Exit
Message button
Retry
Performs the installation step again (if an error has occurred).
Message button
View Log
Displays the installation log (sapinst_dev.log)
Message button
Stop
Stops the installation (SAPinst GUI, SAPinst and the GUI server)
without further changing the installation files. You can continue the
installation later from this point.
Message button
Continue
Continues with the option you have chosen before.
4.3.3 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:
n An error occurred during the dialog or processing phase:
SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses
and a dialog box appears. The dialog box contains a short description about the choices listed in
the table below as well as a path to a log file that contains detailed information about the error.
n You interrupted the installation by choosing Exit in the SAPinst menu.
The following table describes the options in the dialog box:
92/178
PUBLIC
03/28/2008
4
4.3
Installation
Option
Definition
Retry
SAPinst retries the installation from the point of failure without repeating
any of the previous steps.
This is possible because SAPinst records the installation progress in the
keydb.xml file.
We recommend that you view the entries in the log files, try to solve the
problem and then choose Retry.
If the same or a different error occurs again, SAPinst displays the same
dialog box again.
Stop
SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and
the GUI server.
SAPinst records the installation progress in the keydb.xml file. Therefore,
you can continue the installation from the point of failure without
repeating any of the previous steps. See the procedure below.
Continue
SAPinst continues the installation from the current point.
Note
You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that you
use Ctrl + C , because this kills the process immediately.
Procedure
This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or
to continue an interrupted installation after an error situation.
1. Log on to your local UNIX host as user root.
Caution
database.
2. Mount your Installation Master DVD.
Note
Mount the DVD locally. We do not recommend using Network File System (NFS).
3. Enter the following commands:
cd <Installation_Master_DVD>/IM_<OS>
./sapinst
4. From the tree structure in the Welcome screen, select the installation service that you want to
continue and choose Next.
03/28/2008
PUBLIC
93/178
4
4.3
Installation
Note
If there is only one component to install, the Welcome screen does not appear.
The What do you want to do? screen appears.
5. In the What do you want to do? screen, decide between the following alternatives and confirm with OK.
Alternative
Behavior
Run a new Installation
SAPinst does not continue the interrupted installation. Instead, it moves

the content of the old installation directory and all installation-specific
files to the backup directory. Afterwards, you can no longer continue
the old installation.
For the backup directory, the following naming convention is used:
<log_day_month_year_hours_minutes_seconds> (for example,
log_01_Oct_2003_13_47_56).
Continue old installation
SAPinst continues the interrupted installation from the point of failure.
4.3.4 Performing a Remote Installation with SAPinst

(Optional)
You use this procedure to install your SAP system on a remote host. In this case, SAPinst and the
GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the
host from which you control the installation with SAPinst GUI.
Prerequisites
n The remote host meets the prerequisites before Starting SAPinst [page 81].
n Both computers are in the same network and can ping each other.
To test this:
l Log on to your remote host and enter the command ping <local host>.
l Log on to the local host and enter the command ping <remote host>.
Procedure
1. Log on to your remote host as user root.

Caution
database.
2. Mount the Installation Master DVD.
3. Enter the following commands:
94/178
PUBLIC
03/28/2008
4
4.3
Installation
./sapinst -nogui
For more information, see Running SAPinst on UNIX [page 85].

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at
the command prompt:
guiengine:
no GUI connected; waiting for a connection on host <host_name>, port
<port_number> to continue with the installation.
4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 95].
4.3.5 Starting SAPinst GUI Separately (Optional)

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUI
separately in the following cases:
n You have logged off from SAPinst.
If you logged off during the installation and you later want to reconnect to the installation while it
is still running, you can start SAPinst GUI separately.
n You want to perform a remote installation [page 94].
If you want to run SAPinst GUI on a different host from SAPinst and the GUI server, you have to
start SAPinst GUI separately.
Prerequisites
You have installed the Java Development Kit [page 71] on the host on which you want to start SAPinst
without SAPinst GUI.
Starting SAPinst GUI on a Windows Platform
1. Log on as a member of the local administrators group.

2. Insert the SAP Installation Master DVD into your DVD drive.
3. Open a command prompt and change to the relevant directory:
<DVD drive>:\IM_WINDOWS_<platform>
4. Start SAPinst GUI in one of the following ways:

n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command:
startinstgui.bat
SAPinst GUI uses the local host as default.

n If SAPinst and the GUI server runs on a different host from SAPinst GUI (remote installation),
enter the following command:
startinstgui.bat -host <host_name>
<host_name> is the host name of the installation host.
03/28/2008
PUBLIC
95/178
4
4.3
Installation
Note
l If you enter the command without additional parameters, SAPinst GUI uses the local host
as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since
SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and
the SAP Installation GUI Connection dialog appears.
In this case, enter the name of the host on which SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command startinstgui.bat -h.
Starting SAPinst GUI on a UNIX Platform

Caution
database.
2. Mount your installation DVD.
Note
Mount the DVD locally. We do not recommend that you use Network File System (NFS).
3. To change to the mount directory enter the following command:
4. Start the SAPinst GUI in one of the following ways:

n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following
command without additional parameters:
./startInstGui.sh
SAPinst GUI uses as default the local host.

n If SAPinst and the GUI server run on a different host from SAPinst GUI (remote installation),
enter the following command with additional parameters:
./startInstGui.sh -host <host_name>
<host_name> is the host name of the installation host.
96/178
PUBLIC
03/28/2008
4
4.4
Installation
Oracle Database Software Installation
Note
l If you enter the command without additional parameters, SAPinst GUI uses the local host
as default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. Since
SAPinst and GUI server are running on another host, SAPinst GUI cannot connect and the
SAP Installation GUI Connection dialog appears.
In this case, enter the name of host on which SAPinst is running and choose Log on.
The first dialog of the installation appears and you can perform the remote installation
from your local host.
l For a list of options to start SAPinst GUI, change to the same directory as your SAPinst
executable and enter the command ./startInstGui.sh -h.
4.3.6 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries in
/etc/services:
sapdpXX = 32XX/tcp
sapdbXXs = 47XX/tcp
sapgwXX = 33XX/tcp
sapgwXXs = 48XX/tcp
where XX is set from 00 to 99.

Note
If there is more than one entry for the same port number, this is not an error.
4.4 Oracle Database Software Installation

SAPinst prompts you to install the Oracle database.
Proceed as follows to install the Oracle database software:
Process Flow
1.
2.
3.
4.
5.
You update SAP-specific files in the Oracle stage area [page 98].
You perform steps for the AIX operating system [page 98]
You run the Oracle Universal Installer [page 99]
You install the current patch set [page 101]
You install required interim patches [page 101]
03/28/2008
PUBLIC
97/178
4
4.4
Installation
4.4.1 Updating SAP-Specific Files in the Oracle Staging Area

SAPinst extracts the Oracle RDBMS software to the staging area, usually
/oracle/stage/102_64/database.
The SAP folder located in /oracle/stage/102_64/database contains SAP-specific scripts as well
as the response files.
Before starting the Oracle software installation, you need to update this SAP folder so that the newest
versions of the scripts or response files are used.
Procedure
1. Rename the original SAP folder by performing one of the following:

n mv /oracle/stage/102_64/database/Disk1/SAP
/oracle/stage/102_64/database/Disk1/SAP_ORIG
mv /oracle/stage/102_64/database/SAP
/oracle/stage/102_64/database/SAP_ORIG
2. Download the file RDBMS_SAP_64.zip attached to SAP Note 819830 and copy it to a temporary
location such as /tmp.
3. Extract the zip file by performing one of the following:
n cd /oracle/stage/102_64/database
unzip /tmp/RDBMS_SAP.zip
cd /oracle/stage/102_64/database/Disk1
unzip /tmp/RDBMS_SAP.zip
You should now see the directory SAP extracted with the updated version of SAP-specific files.
4.4.2 Performing Steps for the AIX Operating System

To install the Oracle database software on the AIX operating system, you need to run the rootpre.sh
script to adapt the AIX kernel and also execute a command as the root user.
Prerequisites
If several Oracle instances run on one computer, you must shut these down before adapting the
kernel.
Procedure
1. Run the rootpre.sh script as follows:

a) Log on to the system with user ora<dbsid> if you are not already logged on.
b) Change to the directory /oracle/stage/102_64/database/Disk1/rootpre using the following
command:
cd /oracle/stage/102_64/database/Disk1/rootpre
98/178
PUBLIC
03/28/2008
4
4.4
Installation
c) Make sure that the user root is assigned the environment of ora<dbsid>:
su root
d) Call the script
rootpre.sh:
./rootpre.sh
e) Log off with the user root:

exit
2. Remove any currently unused modules in kernel and library memory by entering the following
command as user root:
# /usr/sbin/slibclean
4.4.3 Running the Oracle Universal Installer

To install the Oracle database software you run the Oracle Universal Installer (OUI).
Procedure
1. Log on as user ora<dbsid>.

Since you are already logged on as user root, you can switch to user ora<dbsid> by entering the
following command:
su ora<dbsid>.
2. If you install Oracle database software with Release 10.2.0.1 or 10.2.0.x on a new operating system or
a new operating system version, the Oracle Universal Installer might not yet recognize or support
this operating system. Follow the instructions in SAP Note 980426.
3. Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name>
is the host on which you want to display the GUI of the Oracle Universal Installer (OUI).
Shell Used
Command
Bourne shell (sh)
DISPLAY=<host_name>:0.0
export DISPLAY
C shell (csh)
setenv DISPLAY <host_name>:0.0
Korn shell (ksh)
export DISPLAY=<host_name>:0.0
4. Start the OUI by entering one of the following:

n cd /oracle/stage/102_64/database/Disk1/SAP
./RUNINSTALLER
cd /oracle/stage/102_64/database/SAP
./RUNINSTALLER
You see a message that a response file is being generated. It might take several minutes before you
see the OUI screen.
5. Respond to the OUI as follows:
03/28/2008
PUBLIC
99/178
4
4.4
Installation
Prompt or Condition
Action
When you run the OUI for the first time on this host, Accept the OUI proposal and continue by choosing
a dialog box, Specify File Locations Destination..., appears. Next.
This dialog box proposes the inventory location as
/oracle/oraInventory and the installation group
as dba.
Available Product Components
Confirm the default selections by choosing Next.
Product-Specific Prerequisite Checks

This phase checks if all necessary requirements for
installing and running the database have been met.
For items that are flagged as warnings or failed,

review the cause for the warning or failure on screen
and fix the problem if possible.
Alternatively you can verify the items manually
and confirm them by clicking the checkbox. You
can find details about each check by clicking on the
relevant item.
Summary page
Check the information on this page and then start

the installation.
When the Install step has completed, a dialog box

appears.
Execute the file $ORACLE_HOME/root.sh with the user

root, and confirm the dialog box by choosing OK.
If this is the first time that the Oracle software
has been installed on this host, the OUI
also asks you to execute a second script,
/oracle/oraInventory/orainstRoot.sh, as the root
user. Execute this script as well.
Continue by choosing Next.
6. At the end of the installation, in case there are any Configuration Assistants that have been started
automatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant.
You can ignore messages that some of the config assistants failed to complete successfully.
The Installer finishes, reporting that the Oracle installation was successful. It also informs
you about the services that it started. You can find the port numbers for these services in the
$ORACLE_HOME/install/portlist.ini file.
7. To exit the OUI, choose Exit and confirm the dialog box that appears.
Note
You can now access the Oracle 10.2 online documentation, which was installed during
the last step. You can find the entry point to the Oracle online documentation at
$ORACLE_BASE/doc/index.htm.
100/178
PUBLIC
03/28/2008
4
4.4
Installation
4.4.4 Installing the Current Patch Set

After the Oracle database software installation, you need to install the current Oracle Database
10g Release 2 (10.2) patch set.
Prerequisites
n For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735.
n For more information about how to install the patch set, see the patch set README file.
Caution
Do not perform any of the post-installation steps mentioned in the patch set README file. The
post-installation steps are to be performed only on an existing Oracle 10.2 database.
At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle
10.2. Therefore, make sure that you do not perform the post-installation steps mentioned in
the README file.
n You only have to install the latest (that is, the current) patch set.
Procedure
1. Log on at the operating system level with the ora<dbsid> user.

2. Download and extract the patch set as described in SAP Note 932251.
3. Install the patch set as described on the patch set README file.
4.4.5 Installing Required Interim Patches

After the Oracle database software installation, you need to install required interim patches, using the
Oracle tool OPatch. You need these interim patches in addition to the current patch set.
Prerequisites
n Make sure you have already installed the current patch set [page 101].
n Check SAP Note 871096 to find the list of required patches to be installed.
n Check SAP Note 839182 for instructions on how to use OPatch.
Procedure
1. Log on at the operating system level as the ora<dbsid> user.

2. Install the patches, following the instructions in SAP Note 839182.
03/28/2008
PUBLIC
101/178
4
4.5
Installation
Installing Application Sharing Server as an Optional Standalone Unit
Note
You can apply the patches in any order.

We recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME.
3. After all the patches have been successfully applied, you can query the status with the following
command:
$ORACLE_HOME/OPatch/opatch lsinventory
This command lists all the patches that have been applied to the software installation.
4.5 Installing Application Sharing Server as an Optional

Standalone Unit
When you install Application Sharing Server as a standalone engine on a dedicated machine, the
NetWeaver Java Application Server (AS Java) is also installed. In SAPinst, there are no specific input
screens for Application Sharing Server; all input screens are related to the installation of the new
AS Java.
Note
If you install Application Sharing Server on a machine that already has an AS Java installed, an
additional Java system is installed on that machine. You then have two engines running on the
machine. Typically, this is not recommended as Application Sharing Server requires a dedicated
machine.
Prerequisites
n Make sure that you have read Application Sharing Server as an Optional Standalone Unit [page 31].
n Your machine meets the hardware and software requirements [page 43] for a standard AS Java system.
Procedure
1. Start SAPinst [page 84] on the dedicated machine.

2. In the Welcome screen, choose <SAP System> Optional Standalone Units Application Sharing Server
<Database> Application Sharing Server Installation .
3. To start the installation, choose Next.
4. Follow the instructions in the SAPinst dialogs and enter the required parameters.
More Information
Post-Installation Steps for Application Sharing Server [page 116]

102/178
PUBLIC
03/28/2008
Post-Installation
5 Post-Installation
Note
In a central system, all mandatory instances are installed on one host. Therefore, if you are installing
a central system, you can ignore references to other hosts.
You perform the following post-installation steps:
1. If you have installed software units or usage types based on AS Java, you update database statistics
[page 104].
2. You check whether you can log on to the application server [page 105].
Note
In a distributed or high-availability system you check whether your can log on to every instance
of the SAP system that you installed.
Only valid for: Enterprise Portal (EP);EP Core (EPC)
3. You check whether you can log on to the portal [page 106].
Note
In a distributed or high-availability system you check whether your can log on to the portal from
every instance of the SAP system that you installed.
End of: Enterprise Portal (EP);EP Core (EPC)
4. You check whether you can log on to SAP NetWeaver Development Infrastructure [page 107].
5.
6.
7.
8.
You install the SAP license [page 108].

You configure the remote connection to SAP support [page 108].
On the central instance host, you apply the latest kernel and Support Packages [page 109].
On the database instance host, you perform the Oracle-specific post-installation steps [page 110].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
9. You perform a full backup of the installation [page 111].
03/28/2008
PUBLIC
103/178
5
5.1
Post-Installation
Updating Database Statistics
10. You perform post-installation steps for Adobe Document Services [page 113].
Only valid for: BI Java;Process Integration (PI)
11. You set the environment variable CPIC_MAX_CONV [page 115].

End of: BI Java;Process Integration (PI)
12. You perform the post-installation steps required for Application Sharing Server [page 116].
13. You perform the required post-installation steps for high availability [page 116].
End of: HA (UNIX)
14. You ensure user security [page 118].

Only valid for: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI)
15. To perform basic configuration steps, on the central instance host, you run the Configuration Wizard
[page 122].
End of: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI)
16. You check the Java documentation [page 124] for information that is relevant for running your Java system.
17. You can now start with the manual configuration of your IT scenarios for which you can find the
appropriate documentation in the SAP Solution Manager [page 125].
18. If you want or need to implement the E2E Root Cause Analysis scenario, you have to perform
post-installation steps for the Diagnostics Agent [page 127] on your central instance and/or dialog instance(s).
5.1 Updating Database Statistics

You have to update database statistics if you have installed software units or usage types based
on AS Java.
Prerequisites
The database is up and running.

Procedure
1. Log on as user ora<dbsid> to the host where the database instance is running.
2. Open a command prompt and execute the following command:
brconnect -u / -c -f stats -t all -o SAP<SCHEMA_ID>
Example
brconnect -u / -c -f stats -t all -o SAPQO1DB
104/178
PUBLIC
03/28/2008
5
5.2
Post-Installation
Logging On to the Application Server
5.2 Logging On to the Application Server

You need to check that you can log on to the SAP system using the following standard users.
Java Standalone Users
User
User Name Storage:

Database
User Name Storage:

External ABAP System
Administrator
Administrator
The user
J2EE_ADM_<SAPSID_Java_System>
that you must have created manually

before you started the installation
process.
For more information, see Preparing
User Management for an External ABAP
System [page 135].
Prerequisites
n The SAP system is up and running.

Logging On to the Java Application Server
You access AS Java with a URL using a Web browser from your client machines. To log on to the Java
application server, proceed as follows:
1. Start a Web browser and enter the following URL:
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00
Note
You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1
but instead enter 01.
Example
If you installed the SAP NetWeaver Application Server Java on host saphost06 and the instance
number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
http://saphost06:50400
The start page of the SAP NetWeaver Application Server Java appears in the Web browser.
2. Log on by pressing the link of any of the provided applications, for example the SAP NetWeaver
Administrator or the System Information.
03/28/2008
PUBLIC
105/178
5
5.3
Post-Installation
Logging on to the Portal
5.3 Logging on to the Portal

You need to check that you can log on to the application server using the following standard users.
This procedure applies when you install usage type EPC only and when you install it together with
usage type EP:
Java Standalone Users
User
User Name Storage:

Database
User Name Storage:

Administrator
Administrator
The user
that you must have created manually

before you started the installation
process.
For more information, see Preparing
User Management for an External ABAP
System [page 135].
Prerequisites
The SAP system is up and running.

Procedure
You access the portal with a URL using a Web browser from your client machines.
The default URL consists of the installation host name and the port on which the portal is listening.
You can use the HTTP or HTTPS protocol. HTTPS is relevant if you are using Secure Sockets Layer
(SSL) communication.
http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00/irj
Note
You must always enter a two digit number for <Instance_Number>. For example, do not enter 1
Example
If you installed the portal on host saphost06 and the instance number of your SAP NetWeaver
Application Server Java is 04, enter the following URL:
106/178
PUBLIC
03/28/2008
5
5.4
Post-Installation
Logging on to SAP NetWeaver Development Infrastructure (NWDI)
2. Log on by entering the required user and password.

5.4 Logging on to SAP NetWeaver Development Infrastructure

(NWDI)
You have to log on to the services of SAP NetWeaver Development Infrastructure (NWDI) to check
whether the installation of the usage type DI was successful.
Procedure

http://<hostname_of_J2EE_Engine_Server>:5<Instance_Number>00/devinf
Note
You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1
Example
If you installed the SAP NetWeaver Application Server Java with DI on host saphost06 and the
instance number of your SAP NetWeaver Application Server Java is 04, enter the following URL:
2. Log on with the user NWDI_ADMIN.

The start page SAP NetWeaver Development Infrastructure appears in the Web browser.
You should see the following links:
n Design Time Repository
n Component Build Service
n Change Management Service
n System Landscape Directory
3. Log on to these services one after another by clicking the appropriate link:
a) When you click Design Time Repository, you should see the Design Time Repository page with the
Repository Browser overview.
b) When you click Component Build Service, you should see the Component Build Service page with the CBS
Buildspace Information.
c) When you click Change Management Service, you should see the Change Management Service page
with the CBS Buildspace Information.
d) When you click System Landscape Directory, you should see the System Landscape Directory start page.
03/28/2008
PUBLIC
107/178
5
5.5
Post-Installation
Installing the SAP License
Note
The tables displayed on the pages may be empty. They are filled when you configure the
development infrastructure either by running the Configuration Wizard [page 122] or by configuring
your system manually.
5.5 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary license
is automatically installed. This temporary license allows you to use the system for only four weeks
from the date of installation.
Caution
Before the temporary license expires, you must apply for a permanent license key from SAP.
We recommend that you apply for a permanent license key as soon as possible after installing your
system.
Procedure
For more information about the installation procedure for the SAP license, see:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library Technology
Consultants Guide Cross-NetWeaver Configurations SAP License Key
If you have installed a high-availability system, proceed as described in High Availability: Setting Up
Licenses [page 116].
End of: HA (UNIX)
More Information
For more information about SAP license keys, see http://service.sap.com/licensekey.
5.6 Configuring Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the EarlyWatch
Service or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP.
For more information, see SAP Service Marketplace at http://service.sap.com/remoteconnection.
108/178
PUBLIC
03/28/2008
5
5.7
Post-Installation
Applying the Latest Kernel and Support Packages
5.7 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAP
Service Marketplace.
Note
The following are available exclusively through the Maintenance Optimizer in SAP Solution
Manager:
n All corrective software packages, including Support Packages (Stacks) for SAP NetWeaver 7.0 and
subsequent versions
n All applications based on this software (including SAP Business Suite 2005), released after April
2, 2007
For more information about the Maintenance Optimizer, see
http://service.sap.com/solutionmanager
SAP Solution Manager in Detail
Change Request Management Maintenance Optimizer .
Caution
Before you apply support packages, make sure that you read the release notes for your SAP system.
You can find these on SAP Service Marketplace at http://service.sap.com/releasenotes. The
release notes might include information about steps you have to perform after you have applied
the support packages.
Caution
Make sure that the entry DIR_CT_RUN exists in the instance profile. Otherwise you cannot restart the
system after patches have been applied.
See also Setting Up File Systems [page 59].
You can use Java Support Package Manager (JSPM) to apply both the latest ABAP+Java or Java kernel
and Java support packages.
JSPM is a Java standalone tool that you can use with SAP NetWeaver 7.0. JSPM uses the Software
Deployment Manager (SDM) to apply support packages and patches and to deploy software
components.
For more information about JSPM and how to use this tool, see http://help.sap.com/nw70
SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life
Cycle Management by Key Capability Software Life Cycle Management Software Maintenance Java Support
Package Manager
03/28/2008
PUBLIC
109/178
5
5.8
Post-Installation
Performing Oracle-Specific Post-Installation Steps
Prerequisites
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR
700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longer
unpack current SAR files. For more information, see SAP Note 212876.
Procedure
1. Apply the latest kernel.

You must always replace the installed kernel with the latest kernel from SAP Service Marketplace.
In particular, you must replace the installed kernel if:
n You installed the kernel executables locally on every host.
n Your central instance host runs on a different operating system than your dialog instance host.
For more information about how to download a kernel, see SAP Note 19466.
To exchange the ABAP+Java kernel, you can use Java Support Package Manager (JSPM).
2. Apply Support Packages.
a) For up-to-date information about recommended combinations of Support Packages and
patches, see SAP Service Marketplace at:
http://service.sap.com/sp-stacks
For up-to-date release information on Support Package Stacks and about how to apply them,
see the documentation SAP NetWeaver 7.0 Support Package Stack Guide <current version> on SAP
Service Marketplace at http://service.sap.com/MaintenanceNW70.
b) Alternatively, you can download Support Packages from SAP Service Marketplace at:
http://service.sap.com/patches
c) Apply the Java Support Packages to your SAP system with the help of the Java Support Package
Manager (JSPM).
For more information about the availability of Support Packages, see the SAP Service Marketplace
at:
http://service.sap.com/ocs-schedules
Note
The SAP Note Assistant lets you load, implement, and organize individual SAP Notes efficiently. It
also recognizes dependencies between SAP Notes, Support Packages, and modifications.
For more information, see the SAP Service Marketplace at:
http://service.sap.com/noteassistant
5.8 Performing Oracle-Specific Post-Installation Steps

You have to perform the following Oracle-specific post-installation steps:
110/178
PUBLIC
03/28/2008
5
5.9
Post-Installation
Performing a Full Installation Backup
Security Setup for the Oracle Listener
If the Oracle security setup defined by the standard installation is not restrictive enough for your
purposes, see SAP Note 186119 to configure the Oracle listener to accept only connections from
specific hosts.
Checking the Recommended Oracle Database Parameters
When installing the Oracle database, a standard database parameter set is used. To take into account
the size and configuration of your SAP system, and to enable new Oracle features, check and apply the
parameter settings as described in SAP Note 830576.
Configuring and Operating the Oracle Database
You have to configure your Oracle database before you start operating it with the SAP system.
For information on Oracle database configuration and administration, see the documentation in
the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver
Library SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services
Database Support Oracle .
5.9 Performing a Full Installation Backup

You must perform a full offline backup at the end of the installation. This procedure also describes
how to use the back-up data for a restore.
Caution
Make sure that you fully back up your database so that you can recover it later if necessary.
Prerequisites
n You have logged on [page 105] as user <sapsid>adm and stopped the SAP system and database [page 147].
Procedure
The Unix commands used in this procedure work on all hardware platforms. For more information
about operating system-specific backup tools, see your operating system documentation.
Backing Up the Installation
Note
The following only applies to a standard installation.

1. Back up the following file systems:
03/28/2008
PUBLIC
111/178
5
5.9
Post-Installation
Performing a Full Installation Backup
n /usr/sap/<SAPSID>
n /usr/sap/trans
n <sapmnt>/<SAPSID>
n Home directory of the user <sapsid>adm
n All database-specific directories
Proceed as follows:
a) Log on as user root.
b) Manually create a compressed tar archive that contains all installed files:
n Saving to tape:
tar cf <file_system> | compress c > <tape_device>
n Saving to the file system:

tar cf <file_system> | compress c > ARCHIVENAME.tar.Z
2. Back up the operating system using operating system means.

This saves the structure of the system and all configuration files, such as file system size, logical
volume manager configuration and database configuration data.
Restoring Your Backup
If required, you can restore the data that you previously backed up.
Caution
Check for modifications in the existing parameter files before you overwrite them when restoring
the backup.
2. Go to the location in your file system where you want to restore the backup image.
3. Execute the following commands to
n restore the data from tape:
cat <tape_device> | compress cd | tar xf
n restore the data from the file system:

cat ARCHIVENAME.tar.Z | compress cd | tar xf
Performing a Full Database Backup
1. Configure your third-party backup tool, if used.

2. Perform a full database backup (preferably offline).
If you use BR*TOOLS for the backup, refer to BR*Tools for Oracle DBA in the SAP Database Guide: Oracle
(BC-DB-ORA-DBA). This documentation is available in the SAP Library at:
NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services Database
Support Oracle SAP Database Guide: Oracle (BC-DB-ORA-DBA)
112/178
PUBLIC
03/28/2008
5
Post-Installation
5.10 Post-Installation Steps for Adobe Document Services

If you want to use Adobe document services (ADS) in your SAP system landscape, you have to
perform the following post-installation steps:
Note
Adobe document services (ADS) are only supported on a limited set of 64-bit platforms for SAP
NetWeaver. For more information, see Running Adobe Document Services on Non-Supported Platforms [page 31].
n You assign the required roles to users ADSUSER and ADS_AGENT [page 113].
n You check the IIOP service and the startup properties [page 114].
n You perform quick tests for Adobe Document Services (ADS) [page 114].
5.10.1 Assigning Roles to Users ADSUSER and ADS_AGENT

During the installation SAPinst created the users ADSUSER for basic authentication and ADS_AGENT
for processing forms between an ABAP and a Java environment.
After the installation you have to assign the required authorization roles manually to these users in
the ABAP system, as described below.
Assigning Role SAP_BC_FP_ICF to ADS_AGENT
1.
2.
3.
4.
5.
Log on to the ABAP system with user DDIC or SAP*.

Call transaction SU01.
Enter ADS_AGENT in the User field.
Choose User Names Change .
Choose the Roles tab and assign the role SAP_BC_FP_ICF to the user ADS_AGENT.
Creating Role ADSCallers and Assigning it to ADSUSER
1.
2.
3.
4.
5.
6.
Log on to the ABAP system [page 105].

Call transaction PFCG.
Enter ADSCallers in the Role field.
Choose Role Create .
On the Create Roles screen, choose Role Save .
Choose the User tab and assign the user ADSUSER in the User ID field.
03/28/2008
PUBLIC
113/178
5
Post-Installation
5.10.2 Checking the IIOP Service and the Startup Properties

After the installation of the Adobe document services and before performing any other configuration
steps you need to check special settings on the central instance host. If necessary, you need to adapt
these settings manually.
Procedure
1. Start the conguration tool of the AS Java by running

/usr/sap/<SAPSID>/<instance_name>/j2ee/configtool.sh.
The Config Tool screen appears.

2. Check if the startup mode of the service iiop is set to always:
a) In the left frame, open the tree Cluster data Cluster data Global dispatcher configuration Services .
b) Choose service iiop.
c) The field Startup mode in the right frame must be set to always. If it is not true, apply the value
always.
d) Choose Apply changes.
e) Repeat the steps b. to d. for the following path: Cluster data Cluster data Global server
configuration Services .
3. Check if the Java startup property for Adobe document services is set as follows:
a) Select Cluster data Cluster data instance_<IDxxxx> server_<IDxxxx> .
b) In the right frame, check if the following line exists in the Java Parameters area of the tab General:
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.
PortableInterceptor.JTSInitializer
If the line does not exist, add the line to this section.
Caution
Due to layout restrictions, this documentation cannot display the whole parameter in one
line. We had to insert a line break in front of PortableInterceptor.JTSInitializer.
In reality, this parameter must not contain any blank and must be entered in one line.
4. Exit the configuration tool.
5. If you have applied new values during the procedure above, you need to restart the AS Java
to adapt the new settings.
5.10.3 Installation Check and Quick Tests for Adobe

Document Services
Adobe document services (ADS) can run in different IT scenarios, infrastructures and usage types
in a new or in an upgraded installation. In some cases the installation process cannot perform all
114/178
PUBLIC
03/28/2008
5
Post-Installation
5.11 Setting Environment Variable CPIC_MAX_CONV
configuration settings that are necessary for the use of Adobe document services, for example, if ABAP
and Java are not installed on the same server. Use this process to check whether all configuration steps
are complete and to verify, which ones you still need to perform manually.
Prerequisites
Adobe document services are installed on your system.

Procedure
Check the ADS configuration as described in http://help.sap.com/nw70 SAP NetWeaver 7.0 Library
English SAP NetWeaver Library Technology Consultants Guide Business Task Management Adobe Document
Services (Configuration) Adobe Document Services Configuration Guide Configuring the Web Service Securing Access
to the Web Service Configuration Check .
If the tests are not successful, you might have to make some adjustments to the initial technical
configuration for ADS [page 153].
More Information
The Adobe Document Services Configuration Guide is also available in PDF form at
http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms Installation and
Configuration Guides Adobe Document Services - Configuration Guide NW 7.0 .
Only valid for: BI Java;Process Integration (PI)
5.11 Setting Environment Variable CPIC_MAX_CONV

To set the CPIC_MAX_CONV variable, proceed as follows:
1. Set the system variable CPIC_MAX_CONV:
env variable CPIC_MAX_CONV <maximum number of simultaneous RFCs to the SAP System>
Note
We recommend that you set the value to at least 200.

2. Restart the system.
3. Increase the profile value gw/max_conn and gw/max_sys on the SAP gateway to support more
parallel connections. If you run into memory bottlenecks, also increase gw/max_overflow_size
and gw/max_shm_req. Refer to report RSMONGWY_CHANGE_PARAMETER started from transaction SA38.
End of: BI Java;Process Integration (PI)
03/28/2008
PUBLIC
115/178
5
Post-Installation
5.13 High Availability: Post-Installation Steps
5.12 Post-Installation Steps for the Application Sharing

Server
After you have installed the necessary software, you must complete a number of configuration steps
in the portal to fully implement application sharing functions in the portal. These steps are valid
if you installed the Application Sharing Server as a standalone engine or you are using the default
server installed on the portal machine.
by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-Time
Collaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) .
This documentation includes information on how you define which Application Sharing Server
the portal must use.
by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-Time
Collaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) Enabling
/ Disabling the Application Sharing Server (RTC) .
5.13.1 Setting Up Licenses

Every SAP system needs a central license, which is determined by the environment of the message
server. Since SAPs high-availability (HA) solution stipulates two or more cluster nodes (host
machines) where the message server is enabled to run, you have to order as many license keys [page 108]
as you have cluster nodes.
When we receive confirmation from your vendor that you are implementing a switchover
environment, we provide the required license keys for your system, one key for each machine.
SAP has implemented a license mechanism for transparent and easy use with switchover solutions
and clustered environments. Your customer key is calculated on the basis of local information on the
message server host. This is the host machine where the central services instance (SCS) runs. There
is no license problem when only the database is switched over.
116/178
PUBLIC
03/28/2008
5
Post-Installation
Prerequisites
The SAP system is up and running.

Procedure
1. Make sure that the SCS instance on the primary host, node A, is running.
2. To find the hardware ID of the primary host, run the Visual Administrator on node A and choose
CI Host License Adapter .
The hardware ID is displayed in the Visual Administrator.
3. Perform a switchover of the central services instance (SCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:
http://service.sap.com/licensekey
5. To import the files containing the two licenses, run the Visual Administrator on the node where
the SCS instance is running and choose CI Host License Adapter .
6. Perform a switchover of the central services instance (SCS) to another node in the cluster and
repeat the previous step.
Repeat this for all remaining nodes in the cluster.
Result
The license is no longer a problem during switchover. This means you do not need to call saplicense
in your switchover scripts.
5.13.2 Taking Precautions for Transport

With a high-availability (HA) installation you need to take precautions before you perform a transport.
TPPARAM contains parameter settings for the transport control program tp, which is used for exports
and imports. It also includes the parameter <SID>/dbhost, which is used to address the database host.
Procedure
Set <SID>/dbhost to the virtual host name of the DB instance.

This lets you use the transport system for the normal maintenance of ABAP programs, but still allows
transparent operation in the event of a switchover.
End of: HA (UNIX)
03/28/2008
PUBLIC
117/178
5
Post-Installation
5.14 Ensuring User Security

You need to ensure the security of the users that SAPinst creates during the installation. For security
reasons, you also need to copy the installation directory to a separate, secure location such as a
DVD and then delete the installation directory.
Recommendation
In all cases, the user ID and password are only encoded when transported across the network.
Therefore, we recommend using encryption at the network layer, either by using the Secure Sockets
Layer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAP
protocols dialog and RFC.
NetWeaver by Key Capability Security Network and Transport Layer Security
Caution
Make sure that you perform this procedure before the newly installed SAP system goes into
production.
Prerequisites
If you change user passwords, be aware that SAP system users might exist in multiple SAP system
clients (for example, if a user was copied as part of the client copy). Therefore, you need to change the
passwords in all the relevant SAP system clients.
Procedure
For the users listed below, take the precautions described in the relevant SAP security guide, which
you can find on SAP Service Marketplace at http://service.sap.com/securityguide:
Operating System and Database Users
User
User Name
Comment
Operating system user
<sapsid>adm
SAP system administrator
<smdsid>adm
Administrator for the Diagnostics

Agent
ora<dbsid>
Oracle database administrator (that

is, the owner of the database files)
118/178
PUBLIC
03/28/2008
5
Post-Installation
User
User Name
Comment
Oracle database user
SAP<SCHEMA_ID>
Oracle database owner (that is, the

owner of the database tables)
SYSTEM
SYS
OUTLN
DBSNMP
Note
You can set up Java standalone users with the SAP User Management Engine (UME) in one of the
following ways:
n With the users stored in an external ABAP system see the first table below
n With the users stored in the database see the second table below
The next two tables show these ways of managing the users.
Java Standalone Users for Users Stored in an External ABAP System
User
User Name Storage: External ABAP System
Comment
Administrator
You create this user manually in the external ABAP system

during the installation process.
This users password

is stored in secure
storage.
Therefore, whenever
you change the
administrators
password, you must
also change the
password in secure
storage with the J2EE
Engine Config Tool.
For more
information, see
Checking the SAP Java
Documentation [page
124].
Recommendation
We recommend that you call the user

The maximum length is 12 characters.
Guest

Lock this user for

interactive logon.
Recommendation

J2EE_GST_<SAPSID_Java_System>
03/28/2008
PUBLIC
119/178
5
Post-Installation
User
Comment
Communication
user for the J2EE
Engine

Specify this user as

a Communications user
and not as a dialog
user.
This user exists at
least in the SAP
system client that
you specified during
the installation.
Recommendation

SAPJSF_<SAPSID_Java_System>

Users for Adobe
Document Services
(ADS)
120/178
ADSUSER
User exists at least in

the clients 000 and
001 of the external
ABAP system.
You must have
created this user
manually in the
external ABAP
system before
you started the
installation.
For more
information,
see Preparing User
Management for an
[page 135].
ADS_AGENT

the clients 000 and
001 of the external
ABAP system.
You must have
created this user
manually in the
external ABAP
system before
you started the
installation.
For more
information,
see Preparing User
Management for an
[page 135].
PUBLIC
03/28/2008
5
Post-Installation
User
Comment
Data supplier
user for System
Landscape
Directory (SLD)
(optional)
The name that you gave this user when you created it manually
[page 135].
The recommended name is SLDDSUSER.

the clients 000 and
001 of the external
ABAP system
ABAP API user for

System Landscape
Directory (SLD)
(optional)
The name that you gave this user when you created it manually
[page 135].
The recommended name is SLDAPIUSER.

the clients 000 and
001 of the external
ABAP system
Java Standalone Users for Users Stored in the Database
User
User Name Storage: Database
Administrator
The name that you gave this user This users password is stored in secure
during the installation or the
storage. Therefore, whenever you change
default name Administrator
the administrators password, you must also
change the password in secure storage with the
J2EE Engine Config Tool.
For more information, see Checking the SAP Java
Guest
The name that you gave this user Lock this user for interactive logon.
during the installation or the
default name Guest
Users for Adobe

Document Services
(ADS)
ADSUSER
This users password is stored in secure

ADS_AGENT
This users password is stored in secure

Data supplier user for

System Landscape
Directory (SLD)
(optional)
03/28/2008
The name that you gave this user

during the installation.
The recommended name is
SLDDSUSER.
PUBLIC
Comment
Note
SAPinst created this user automatically if you

chose Configure local SLD during the installation.
121/178
5
Post-Installation
5.15 Running the Configuration Wizard
Users in the SAP NetWeaver Development Infrastructure (NWDI)
User
User Name
Comment
Administrator of the SAP

Infrastructure (NWDI) and
password
NWDI_ADM
Administrator of the NWDI
Developer in the SAP NetWeaver

(NWDI) and password
NWDI_DEV
Developer in the NWDI
Landscape Directory Service

User in the SAP NetWeaver
(NWDI) and password
NWDI_CMSADM
Administrator of the NWDI

Change Management System
(CMS)
Caution
This user has extensive

authorizations. Make sure
that you assign a secure password.
Caution
Do not log on with this user. It

is used by the system for internal
communication.

Only valid for: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI)

This section provides information about how to run the Configuration Wizard for the SAP NetWeaver
usage types.
You can run the Configuration Wizard only once and only directly after you installed and patched
the system.
Note
You can run the configuration task for BI Java several times and after all use cases.
End of: BI Java
You cannot use the configuration wizard after:

n Upgrade
122/178
PUBLIC
03/28/2008
5
Post-Installation
n Add-In installation
n Enablement of additional usage types
In these cases, you need to perform the corresponding configuration steps as described in the
configuration documentation; see Accessing Configuration Documentation in the SAP Solution Manager [page 125].
You can also find configuration documentation in the Technology Consultants Guide in the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library
English SAP NetWeaver Library Technology
Consultants Guide .
For more information about the Configuration Wizard itself, see the SAP Library at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library
English SAP NetWeaver Library Technology
Consultants Guide Developing, Configuring, and Adapting Applications Creating Java Applications Using Web
Dynpro J2EE Engine Configuration Configuration Wizard .
Note
For more information about the Configuration Wizard and its limitations, see SAP Note 923359.
Prerequisites
You have applied the latest kernel and support packages [page 109] to your system.
You can find the latest LMTOOLS patch at http://service.sap.com/swdc Support Packages and
Patches Search for Support Packages and Patches . Search for LMTOOLS*P. Download and save the sca file.
Apply the patch using the SDM.
1. Open the URL http://<host>:<httpport>/nwa in a browser, and logon to the SAP NetWeaver
Administrator with the user Administrator.
2. In the SAP NetWeaver Administrator, navigate to the Deploy and Change tab. The system displays the
configuration wizard and its configuration tasks.
3. Depending on your installed system select a task from the list as described below and choose Start.
4. After the Configuration Wizard has finished, you need to restart your SAP system.
Only valid for: Application Server (AS)
Usage Type: Application Server
To configure the SAP NetWeaver Administrator, you need to run the configuration tasks NWA_
<0107> using the Configuration Wizard.
End of: Application Server (AS)
Usage Type: BI Java
After SAPinst has finished, you need to run the configuration task BIPostInstallProcess using the
Configuration Wizard.
03/28/2008
PUBLIC
123/178
5
Post-Installation
5.16 Checking the SAP Java Documentation
Recommendation
We recommend that you check the configuration of BI Java using SAP Note 937697.
End of: BI Java
Usage Type: Development Infrastructure
After SAPinst has finished, you need to run the configuration task for usage type Initial setup of functional
unit Development Infrastructure (DI all-in-one) using the Configuration Wizard.
After the Configuration Wizard has finished, you have to restart the engine as described in SAP
Note 919942.
End of: Application Server (AS);BI Java;Development Infrastructure (DI);Mobile Infrastructure (MI);Process Integration (PI)
5.16 Checking the SAP Java Documentation

Here you can find information about the configuration and administration of the J2EE Engine and
about SAP Java technology in the SAP Library.
Procedure
1. Go to http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library

SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology .
2. Check the following documentation for information relevant to running your Java system:
Manual
Contents
Architecture Manual
This manual describes the architecture of a Java or ABAP+Java system. It

contains information on:
n Java cluster architecture including central services, load balancing,
and high availability.
n J2EE Engine system architecture
n SAP NetWeaver Java development infrastructure, including SAP
NetWeaver Developer Studio
Note
The SAP NetWeaver Developer Studio is the SAP development

infrastructure for Java. The Architecture Manual describes the
integration of the SAP NetWeaver Developer Studio into the SAP
development infrastructure.
124/178
PUBLIC
03/28/2008
5
Post-Installation
5.17 Accessing Configuration Documentation in SAP Solution Manager
Manual
Contents
Administration Manual
This manual describes how to administer the SAP system, focusing on the
J2EE Engine. It contains information on:
n System landscape administration
n Software life-cycle management
Note
This part of the manual contains important information about:

l Installation information
l System Landscape Directory (SLD)
l Software Lifecycle Manager (SLM)
l Java Support Package Manager
l Administration of SAP NetWeaver Java Development
Infrastructure (JDI)
n J2EE Engine and J2EE Engine security
n Supportability and performance management
n Administration and configuration of Web Dynpro runtime
environment
n Administration of the XML Data Archiving Service (XML DAS)
Caution
Make sure that you check the mandatory post-installation procedures

listed in the Administration Manual under J2EE Engine Installation
Information Post-Installation Procedures .
Java Development Manual
This manual describes the technologies for developing Java-based business

applications. It explains how to use the SAP NetWeaver Developer Studio,
which is the SAP Java development environment.
Migration Manual
This manual contains all the information you need to migrate an

application created in J2EE Engine 6.20.
More Information
For more information about troubleshooting for the J2EE Engine, see the J2EE Engine Problem Analysis
Guide at:
by Key Capability Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide
(PAG) Usage Type Application Server Java J2EE Engine Problem Analysis Scenarios
5.17 Accessing Configuration Documentation in SAP Solution

Manager
To access configuration documentation in SAP Solution Manager, you have to connect your
newly-installed SAP system to SAP Solution Manager.
03/28/2008
PUBLIC
125/178
5
Post-Installation
5.17 Accessing Configuration Documentation in SAP Solution Manager
Note
For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the Technology
Consultants Guide at:
http://help.sap.com/nw70 SAP NetWeaver 7.0 Library English SAP NetWeaver Library
Technology
Consultants Guide
Prerequisites
n You have installed an SAP Solution Manager system as described in the documentation Installation
Guide SAP Solution Manager 4.0 <current support release> on <OS>: <Database>.
n You have connected your SAP system to SAP Solution Manager as described in the documentation
Configuration Guide SAP Solution Manager <Current Release> as of <Current SP Level>.
You can find this documentation at:
http://service.sap.com/instguides
SAP Components SAP Solution Manager Release 4.0
Procedure
1. Log on to your SAP Solution Manager system.

2. To be able to access configuration documentation, create a project as follows:
a) Create your project with transaction SOLAR_PROJECT_ADMIN for project administration.
b) Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution
Manager system landscape.
c) Create a project structure and add the required scenarios for your SAP system to your project
structure with the Business Blueprint transaction SOLAR01,
d) Add your SAP system configuration structures to your project structure with the configuration
transaction SOLAR02.
For more information about creating projects, assigning scenarios to projects, and creating
configuration structures, see:
NetWeaver by Key Capability Solution Life Cycle Management by Key Capability SAP Solution Manager
Using the SAP Solution Manager in Projects
3. Go to the project structure folder <project name> using transaction SOLAR02.
4. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure
SAP NetWeaver 7.0 .
Result
You can now configure your SAP system according to the configuration documentation in SAP
Solution Manager.
126/178
PUBLIC
03/28/2008
5
Post-Installation
5.18 Post-Installation Steps for the Diagnostics Agent
5.18 Post-Installation Steps for the Diagnostics Agent

To implement the E2E Root Cause Analysis scenario, you have to perform the following
post-installation steps.
Prerequisites
You have installed an AS Java central instance or dialog instance.

Procedure
1. Upgrade the JDK on AIX and Linux x86_64 operating systems as described in SAP Note 1093831.
This avoids connection problems between the Diagnostics Agent and the Diagnostics Managing
system, as well as out-of-memory errors and class-loader problems.
2. Plan the implementation of the SAP Solution Manager Diagnostics Agent as described in the Root
Cause Analysis Installation and Upgrade Guide, which you can find at one of the following:
n http://service.sap.com/diagnostics
n http://service.sap.com/instguides SAP Components SAP Solution Manager <Current
Release>
03/28/2008
PUBLIC
127/178
Additional Information
6 Additional Information
The following sections provide additional information about optional preparation, installation
and post-installation tasks.
There is also a section describing how to delete an SAP system.
Preparation
n Installation of Multiple Components in One Database [page 129]

n Integration of LDAP Directory Services [page 131]
n Preparing User Management with an External ABAP system [page 135]
Installation
n Installation of Additional Software Units or Usage Types in an Existing SAP System [page 138]
Post-Installation
n Starting and stopping the SAP system [page 143].

n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access
[page 151].
n Configuring User Management to Use an LDAP Directory [page 152].
n Usage Type-Specific Initial Technical Configuration [page 152]
n Troubleshooting [page 160]
Deleting an SAP System
n Deleting an SAP System [page 162]
6.1 Installation of Multiple Components in One Database

(Optional)
You can install multiple SAP systems in a single database. This is called Multiple Components
in One Database (MCOD).
Example
You install an SAP NetWeaver central system and an SAP CRM central system in a single database.
03/28/2008
PUBLIC
129/178
6
6.1
Installation of Multiple Components in One Database (Optional)
MCOD is available with all SAP components. We are releasing this technology on all the major
databases for the SAP system, in line with our commitment to deliver platform-independent
solutions.
Using this technology is as easy as installing a separate component. No extra effort is required because
the MCOD installation is fully integrated into the standard installation procedure. MCOD is not an
additional installation service. Instead, it is an option of the database instance installation.
With MCOD we distinguish two scenarios:
n The installation of an SAP system in a new database
n The installation of an additional SAP system in an existing database
Prerequisites
n For more information about MCOD and its availability on different platforms, see
http://service.sap.com/mcod.
n We have released MCOD for Unicode installations. A prerequisite is that the MCOD system
contains Unicode instances only. SAP does not support mixed solutions.
n Improved sizing required
In general, you calculate the CPU usage for an MCOD database by adding up the CPU usage for
each individual SAP system. You can do the same for memory resources and disk space.
You can size multiple components in one database by sizing each individual component using the
SAP Quick Sizer and then adding the requirements together. For more information about the SAP
Quick Sizer, see http://service.sap.com/sizing.
Features
n Reduced administration effort

n Consistent system landscape for backup, system copy, administration, and recovery
n Increased security and reduced database failure for multiple SAP systems due to monitoring and
administration of only one database
n Independent upgrade
In an MCOD landscape, you can upgrade a single component independently from the other
components running in the same database, assuming that the upgraded component runs on
the same database version. However, if you need to restore a backup, be aware that all other
components are also affected.
Note
Special MCOD considerations and differences from the standard procedure are listed where relevant
in the installation documentation.
130/178
PUBLIC
03/28/2008
6
6.2
Integration of LDAP Directory Services (Optional)
Constraints
Recommendation
We strongly recommend that you test MCOD in a test or development system.

We recommend that you run MCOD systems in the same context. We do not recommend that you
mix test, development, and production systems in the same MCOD.
n In the event of database failure, all SAP systems running on the single database are affected.
n Automated support in an MCOD landscape for the following administrative tasks depends on
your operating system and database:
l Copying a single component from an MCOD landscape to another database at database level.
l De-installing a single component from an MCOD landscape requires some additional steps.
You can use a remote connection to SAP support to request help with these tasks. For more
information, see http://service.sap.com/remoteconnection.
When
you use stopsap in an MCOD system with two central instances, only one central instance
n
is stopped. Therefore, you must first stop the other SAP system with stopsap R3 to make sure that
the database is also stopped.
n You cannot install a Unicode SAP system with a non-Unicode SAP system in one database.
n For the second SAP system, you must use the same DBSID as for the first SAP system.
n If you install a system into an existing database (MCOD), the SYSTEM tablespace must contain
at least 400 MB of free space. If there is not enough space left, increase the size of this tablespace
with BRSPACE or BRTOOLS.
n If you decide to turn off archive log mode during the database load phase of the installation, you
need to plan downtime for all MCOD systems sharing the database.
6.2 Integration of LDAP Directory Services (Optional)

This section explains the benefits of using the SAP system with the Lightweight Directory Access
Protocol (LDAP) directory and gives an overview of the configuration steps required to use an SAP
system with the directory.
LDAP defines a standard protocol for accessing directory services, which is supported by various
directory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory services
enables important information in a corporate network to be stored centrally on a server. The
advantage of storing information centrally for the entire network is that you only have to maintain
data once, which avoids redundancy and inconsistency.
If an LDAP directory is available in your corporate network, you can configure the SAP system to use
this feature. For example, a correctly configured SAP system can read information from the directory
and also store information there.
03/28/2008
PUBLIC
131/178
6
6.2
Note
The SAP system can interact with the Active Directory using the LDAP protocol, which defines:
n The communication protocol between the SAP system and the directory
n How data in the directory is structured, accessed, or modified
If a directory other than the Active Directory also supports the LDAP protocol, the SAP system can
take advantage of the information stored there. For example, if there is an LDAP directory on a UNIX
or Windows server, you can configure the SAP system to use the information available there. In the
following text, directories other than the Active Directory that implement the LDAP protocol are
called generic LDAP directories.
Caution
This section does not provide information about the use of LDAP directories with the LDAP
Connector. For more information about using and configuring the LDAP Connector for an ABAP
system, see the SAP Library at:
NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server
ABAP Configuration of Identity Management Directory Services LDAP Connector
Prerequisites
You can only configure the SAP system for Active Directory services or other LDAP directories if
these are already available on the network. As of Windows 2000 or higher, the Active Directory
is automatically available on all domain controllers. A generic LDAP directory is an additional
component that you must install separately on a UNIX or Windows server.
Features
In the SAP environment, you can exploit the information stored in an Active Directory or generic
LDAP directory by using:
n SAP Logon
n The SAP Microsoft Management Console (SAP MMC)
n The SAP Management Console (SAP MC)
For more information about the automatic registration of SAP components in LDAP directories and
the benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information in
Directory Services on SAP Service Marketplace at:
http://service.sap.com/msplatforms Microsoft Windows Server
For more information about the SAP MC and about how to configure it to access LDAP Directories,
see the documentation SAP Management Console at:
132/178
PUBLIC
03/28/2008
6
6.2
SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by
Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE Engine
J2EE Engine Administration Tools SAP Management Console
http://help.sap.com
SAP Logon
Instead of using a fixed list of systems and message servers, you can configure the SAP Logon in the
sapmsg.ini configuration file to find SAP systems and their message servers from the directory. If
you configure SAP logon to use the LDAP directory, it queries the directory each time Server or Group
selection is chosen to fetch up-to-date information on available SAP systems.
To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:
[Address]
Mode=LDAPdirectory
LDAPserver=
LDAPnode=
LDAPoptions=
Distinguish the following cases:

n If you use an Active Directory, you must set LDAPoptions=DirType=NT5ADS. For more
information, see the SAP system profile parameter ldap/options.
n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either of
the following is true:
l The client is not located in the same domain forest as the Active Directory
l The operating system does not have a directory service client (Windows NT and Windows 9X
without installed dsclient).
For more information, see the SAP system profile parameter ldap/servers.
n For other directory services, you can use LDAPnode to specify the distinguished name of the SAP
root node. For more information, see the SAP system profile parameter ldap/saproot.
SAP MMC
The SAP MMC is a graphical user interface (GUI) for administering and monitoring SAP systems from
a central location. It is automatically set up when you install an SAP system on Windows. If the SAP
system has been prepared correctly, the SAP MMC presents and analyzes system information that
it gathers from various sources, including the Active Directory.
Integrating the Active Directory as a source of information has advantages for the SAP MMC. It can
read system information straight from the directory that automatically registers changes to the
system landscape. As a result, up-to-date information about all SAP application servers, their status,
and parameter settings is always available in the SAP MMC.
If you need to administer distributed systems, we especially recommend that you use the SAP MMC
together with Active Directory services. You can keep track of significant events in all of the systems
from a single SAP MMC interface. You do not need to manually register changes in the system
03/28/2008
PUBLIC
133/178
6
6.2
configuration. Instead, such changes are automatically updated in the directory and subsequently
reflected in the SAP MMC.
If your SAP system is part of a heterogeneous SAP system landscape that comprises systems or
instances both on UNIX and Windows platforms, you can also use the SAP MMC for operating and
monitoring the instances running on UNIX.
SAP MC
The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems from a
central location. If the SAP system has been prepared correctly, the SAP MC presents and analyzes
system information that it gathers from various sources, including generic LDAP Directory.
Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. It
can read system information straight from the directory that automatically registers changes to the
system landscape. As a result, up-to-date information about all SAP application servers, their status,
and parameter settings is always available in the SAP MC.
Configuration Tasks for LDAP Directories
This section describes the configuration tasks you have to perform for the Active Directory or other
(generic) LDAP directories.
Configuration Tasks for Active Directory
To enable an SAP system to use the features offered by the Active Directory, you must configure the
Active Directory so that it can store SAP system data.
To prepare the directory, you use SAPinst to automatically:
n Extend the Active Directory schema to include the SAP-specific data types
n Create the domain accounts required to enable the SAP system to access and modify the Active
Directory. These are the group SAP_LDAP and the user sapldap.
n Create the root container where information related to SAP is stored
n Control access to the container for SAP data by giving members of the SAP_LDAP group permission
to read and write to the directory
You do this by running SAPinst on the Windows server on which you want to use Active Directory
Services and choosing <SAP System> Software Life-Cycle Options LDAP Registration Active Directory
Configuration . For more information about running SAPinst on Windows, see the documentation
Installation Guide <your product> on Windows: <Database>.
Note
You have to perform the directory server configuration only once. Then all SAP systems that need
to register in this directory server can use this setup.
Configuration Tasks for Generic LDAP Directories
To configure other LDAP directories, refer to the documentation of your directory vendor.
134/178
PUBLIC
03/28/2008
6
6.3
Preparing User Management for an External ABAP System
Enabling the SAP System LDAP Registration
Once you have correctly configured your directory server, you can enable the LDAP registration of
the SAP system by setting some profile parameters in the default profile.
To do this, run SAPinst once for your system and choose:
<SAP System> Software Life-Cycle Options LDAP Registration LDAP Support
If you use a directory server other than Microsoft Active Directory and/or non-Windows application
servers, you have to store the directory user and password information by using ldappasswd
pf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and is
therefore valid for all application servers. After restarting all application servers and start services,
the system is registered in your directory server. The registration protocols of the components are
dev_ldap*. The registration is updated every time a component starts.
6.3 Preparing User Management for an External ABAP System

For a Java system, you can also deploy user management for an external ABAP system. In this case,
you configure the User Management Engine (UME) of the J2EE Engine for the user management
of a separate ABAP system.
If you want to connect more than one Java system to the same ABAP system, you need to work out a
concept for the communication, administrator, and guest users for each engine.
You can take one of the following approaches:
Approach
Advantages
Disadvantages
Each Java system uses different

users
No interdependencies between the Initially more administration to

connected engines
create the users in the ABAP system
All Java systems use the same

configuration
You create the users only once and Interdependencies between the
enter the same information for
connected engines:
every Java system that you install. n If you change the password of
any of the users on the ABAP
system, this change affects all
connected engines.
n If you change the administrator
users password, you must also
change the password in secure
storage on all of the connected
J2EE Engines
Recommendation
For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.
03/28/2008
PUBLIC
135/178
6
6.3
Prerequisites
n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.
n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION and
SAP_BC_JSF_COMMUNICATION_RO exist and make sure that their profiles are generated.
n In transaction PFCG, check that the roles SAP_J2EE_ADMIN, SAP_J2EE_GUEST and SAP_BC_FP_ICF
exist. Neither role contains any ABAP permissions, so you do not need to generate any profiles.
n In transaction PFCG, create a role named ADSCallers. You do not need to maintain authorization
data or generate any profiles for that role.
n For more information about UME, see
Java User Management Engine
n For more information about role maintenance, see
ABAP Configuration of Identity Management Role Administration Role Administration Functions Changing
Standard Roles
Administration of the ABAP system
Perform the following administration steps in the ABAP system:

1. In transaction SU01, create a new communication user and assign it to the role
SAP_BC_JSF_COMMUNICATION_RO.
Recommendation
We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only
(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,
create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATION
instead.
We recommend that you name the user SAPJSF_<SAPSID_Java_System>.
You can use any password.
In addition, to make sure that this user can only be used for communication connections between
systems and not as a dialog user, assign it the type Communications under Logon data.
2. In transaction SU01, create a new dialog user and assign it to role SAP_J2EE_ADMIN. This is your
administrator user in the J2EE Engine.
Recommendation
We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use any
password.
136/178
PUBLIC
03/28/2008
6
6.3
Caution
Log on to the SAP system once with this user to change its initial password. Since the installer of
the J2EE Engine verifies this password, the installation fails if this password is initial
3. In transaction SU01, create a new dialog user and assign it to role SAP_J2EE_GUEST. This is your
guest user in the J2EE Engine.
Recommendation
We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use any
password.
Since this user is only used for anonymous access to the system, we recommend you to deactivate
the password and, if required, lock it after installation to prevent anyone from using it for explicit
named logons.
4. In transaction SU01, create the following dialog users:
Caution
You must have changed the initial passwords [page 118] of these users before you start the installation of
the Java system.
n Users for Adobe Document Services (ADS) (optional):
l ADSUSER:
In transaction PFCG, assign the role ADSCallers to this user.
l ADS_AGENT:
In transaction PFCG, assign the role SAP_BC_FP_ICF to this user.
n SLD Data supplier user (optional):
You only have to create this user if you want to install System Landscape Directory (SLD).
The SLD data supplier user name that you enter later on during the Java system installation
must be identical to this user.
Recommendation
We recommend that you name this user SLDDSUSER

n SLD ABAP API user (optional):
You only have to create this user if you want to install System Landscape Directory (SLD). The
SLD ABAP API user name that you enter later on during the Java system installation must be
identical to this user.
Recommendation
We recommend that you name this user SLDAPIUSER
03/28/2008
PUBLIC
137/178
6
6.4
Note
For more information about SLD users and security roles, see the Post-Installation Guide - System
Landscape Directory of SAP NetWeaver 7.0 at http://sdn.sap.com/irj/sdn/nw-sld.
Activities for the Java System
Perform the following steps in the Java system:

1. Before the installation of the Java system, make sure that you have the correct user names and
passwords of the users listed above for the separate ABAP system.
2. During the installation of the Java system, make sure that you enter the correct users and
passwords in the corresponding SAPinst dialogs.
6.4 Installation of Additional Software Units or Usage Types

in an Existing SAP System
To install additional Java software units or usage types in an existing SAP system based on SAP
NetWeaver 7.0 SR3 (Support Package Stack (SPS) 14), you cannot use SAPinst. Instead, you have
to use the Java Support Package Manager (JSPM). Existing SAP system means that this SAP
system has at least AS Java.
Restrictions
You can use the option Install Additional Usage Type only if the corresponding product is installed on the
host where you start JSPM. For more information, see section Installation.
Prerequisites
n The existing SAP system must have at least software unit or usage type Application Server Java
(AS Java).
n You have planned your SAP system landscape according to the Master Guide and the Technical
Infrastructure Guide [page 12] available for your product.
Preparation
1. Make sure that the following documentation is available:

Note
You do not need to read the whole documentation. However, make sure that you read those
parts of it referred to below in this procedure.
n For handling JSPM, use the documentation Java Support Package Manager at:
138/178
PUBLIC
03/28/2008
6
6.4
SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP

NetWeaver by Key Capability Solution Life-Cycle Management by Key Capability Software Life-Cycle
Management Software Maintenance Java Support Package Manager
n Check the Master Guide [page 12] for your SAP system application for supported/recommended
combinations of UT that can be run in one system. Check the appropriate installation guide for
your SAP system application for space requirements for the additional software units or usage
types you want to install.
2. Check which software units or usage types are already installed on your system.
You can do this in one of the following ways:
n Start JSPM and choose the Deployed Components tab.
n Check the usage type system information page of your system using the URL
http://<host>:<http_port>/utl/UsageTypesInfo
For more information, see the SAP Library:

NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle
Management Software Maintenance Java Support Package Manager Viewing the Deployed Components
3. Check the dependencies for the software units or usage types you want to install:
Usage Types of SAP NetWeaver 7.0
Usage Type Name (Technical

Name)
Long Text
Depends on
BI
SAP NetWeaver Business

Intelligence Java
AS Java
DI
SAP NetWeaver Development

Infrastructure
AS Java
EPC
SAP NetWeaver Enterprise Portal

Core Component
AS Java
EP
SAP NetWeaver Enterprise Portal
AS Java, EPC
MI
SAP NetWeaver Mobile

Infrastructure
AS ABAP, AS Java
4. Check hardware and software requirements for the software units or usage types you want
to install.
Note
You cannot use the Prerequisite Checker [page 44] to check the requirements of additional software
units or usage types.
a) Check space requirements for the additional software units or usage types that you want
to install.
03/28/2008
PUBLIC
139/178
6
6.4
To do this, check the table SAP Directories in SAP Directories [page 59].
b) Check Java virtual memory settings according to SAP Note 723909.
c) Check requirements for the Java Support Package Manager as described in:
Management Software Maintenance Java Support Package Manager Requirements for Free Disk Space
5. Download the required Software Component Archives (SCAs) and the appropriate stack
definition file using the Maintenance Optimizer in SAP Solution Manager.
http://help.sap.com SAP Solution Manager <Current Release> SAP Solution Manager Change
Management Maintenance Optimizer Planning and Monitoring Product Maintenance
Recommendation
We recommend that you also download the most current Support Package Stack for AS Java to
update the JSPM to the most current SPS level.
Usage Types of SAP NetWeaver 7.0
n Components of Business Intelligence Java (UT_NAME = BI):

Name of SCA
Description
BIIBC**_*.SCA
BI INFORM. BROADCASTING 7.00
BIWEBAPP**_*.SCA
BI WEB APPLICATIONS 7.00 (SP XX)
BIBASES**_*.SCA
BI BASE SERVICES 7.00 (SP XX)
BIREPPLAN**_*.SCA
BI REPORTING AND PLANNING 7.00
BIWDALV**_*.SCA
VCKITBI
VCKITBI**_*.SCA
BI WEBDYNPRO ALV 7.00
End of: BI Java

n Components of Development Infrastructure (UT_NAME = DI):

Name of SCA
Description
DICBS**_*.SCA
DI COMPONENT BUILD SERVER 7.00
DICMS**_*.SCA
DI CHANGE MGMT SERVER 7.00
DIDTR**_*.SCA
DI DESIGN TIME REPOSITORY 7.00
140/178
PUBLIC
03/28/2008
6
6.4
Only valid for: EP Core (EPC)
n Components of Enterprise Portal Core Component(UT_NAME = EPC):

Name of SCA
Description
EPBC**_*.SCA
PORTAL CORE SERVICES 7.00
EPBC2**_*.SCA
PORTAL FRAMEWORK 7.00
EPPSERV**_*.SCA
PORTAL 7.00
EPWDC**_*.SCA
PORTAL WEB DYNPRO 7.00
SAPEU**_*.SCA
CAF EU 7.00
UWLJWF**_*.SCA
UWL AND COLL PROCESS ENGINE 7.00
End of: EP Core (EPC)

n Components of Enterprise Portal (UT_NAME = EP):

Name of SCA
Description
NETPDK**_*.SCA
PDK PORTAL SERVICES 7.00
LMPORTAL**_*.SCA
LIFECYCLE MGMT PORTAL 7.00
CAFKM**_*.SCA
SAP CAF-KM 7.00
KMCCOLL**_*.SCA
KMC COLLABORATION 7.00
KMCCM**_*.SCA
KMC CONTENT MANAGEMENT 7.00
RTC**_*.SCA
RTC 7.00
RTCSTREAM**_*.SCA
STREAMING SERVER 7.00
KMCBC**_*.SCA
KMC BASE COMPONENTS 7.00
VCBASE**_*.SCA
VCBASE
VCFLEX**_*.SCA
VCFLEX
VCKITGP**_*.SCA
VCKITGP
VCKITXX**_*.SCA
VCKITXX
WDEXTENSIONS**_*.SCA
WDEXTENSIONS
VCFRAMEWORK**_*.SCA
VCFRAMEWORK
6. Copy the downloaded SCAs and the appropriate stack definition file to the JSPM inbox directory.
03/28/2008
PUBLIC
141/178
6
6.4
Management Software Maintenance Java Support Package Manager Detecting and Changing the JSPM Inbox
Directory
7. You must check in the SDM RemoteGui whether the following two substitution variables of
type String are created properly:
n com.sap.portal.deploy.pcd =
<com.sap.engine.installdir>/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deploym
com.sap.portal.deploy.pcdcontent =
<com.sap.engine.installdir>/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deploym
Note
<com.sap.engine.installdir> is the current value of SDM variable com.sap.engine.installdir
If these substitution variables do not exist or have wrong values, you must create them manually
as a prerequisite for the deployment of usage types EPC and EP.
For more information, see Software Deployment Manager at:
NetWeaver Developers Guide Fundamentals Using Java Core Development Tasks Deployment: Putting It All
Together Software Deployment Manager Deployment Substitution Variables Management
Installation
1. Start JSPM as described in:

Management Software Maintenance Java Support Package Manager Starting JSPM
2. We strongly recommend that you update JSPM to the most recent Support Package stack level
as described in:
Management Software Maintenance Java Support Package Manager Applying Single Support Packages
3. Depending on your SAP system landscape, you have to run different JSPM options:
n Run the option Install Additional Usage Type if the corresponding product is installed in the same
system in which you start JSPM, as described in:
Management Software Maintenance Java Support Package Manager Installing an Additional Usage Type
n Run the option Deploying New Software Components if the corresponding product is not installed
in the same system in which you start JSPM, as described in:
142/178
PUBLIC
03/28/2008
6
6.5
Starting and Stopping SAP System Instances

Management Software Maintenance Java Support Package Manager Deploying New Software Components
Example
You want to install BI Java as an additional usage type in an existing SAP NetWeaver system
landscape with software units AS ABAP, AS Java, EPC, and EP.:
n If AS ABAP, AS Java, EPC, and EP in the same system, you can choose the option Install Additional
Usage Type to install BI Java.
n However, if AS ABAP is in one system and AS Java, EPC, and EP are in another system, you
have to choose the option New Software Components. In addition you have to activate the newly
installed software unit BI Java manually using the scripts attached to SAP Note 883948.
Post-Installation
After you have finished the deployment with JSPM, you need to perform initial configuration to
complete the installation of additional software units or usage types before you perform the actual
configuration.
Caution
You must not run the Configuration Wizard for the added software unit(s) or usage type(s). Instead,
you have to configure them manually.
1. For initial configuration, perform the steps listed in Usage Type-Specific Initial Configuration [page 152].
Note
SAPinst performs these steps during the installation of an SAP system with usage types. JSPM
does not perform these steps.
2. For complete configuration, use the configuration documentation for your product from the
help portal or from SAP Solution Manager. For more information, see Accessing Configuration
6.5 Starting and Stopping SAP System Instances

You can start and stop SAP system instances and the Diagnostics Agent by using the SAP Management
Console (SAP MC) [page 144].
Apart from using the SAP Management Console (SAP MC) you can also use scripts to:
n Start or stop SAP system instances [page 147]
n Start or stop the Diagnostics Agent [page 150].
03/28/2008
PUBLIC
143/178
6
6.5
6.5.1 Starting and Stopping SAP System Instances Using the

SAP Management Console
You can start and stop all SAP system instances (except the database instance) and the Diagnostics
Agent using the SAP Management Console (MC). You have to start and stop the database instance
as described in Starting and Stopping the SAP System Using startsap and stopsap [page 147].
Note
If your newly installed SAP system is part of a heterogeneous SAP system landscape comprising
systems or instances on Windows platforms, you can also start and stop it from a Windows system or
instance using the Microsoft Management Console (MMC).
For more information about handling the MMC, see:
NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Solution Monitoring Monitoring
in the CCMS SAP Microsoft Management Console: Windows
Prerequisites
n Make sure that the host where you want to start SAP MC meets the following requirements:
l Java Runtime Environment (JRE) 5.0 is installed.
l The browser supports Java.
l The browsers Java plug-in is installed and activated.
n You have logged on to the host as user <sapsid>adm.
Starting the Web-Based SAP Management Console

http://<hostname>:5<instance_number>13
Example
If the instance number is 53 and the host name is saphost06, you enter the following URL:
This starts the SAP MC Java applet.

Note
If your browser displays a security warning message, choose the option that indicates that you
trust the applet.
2. Choose Start.
The SAP Management Console appears.
144/178
PUBLIC
03/28/2008
6
6.5
By default, the instances installed on the host you have connected to are already added in the
SAP Management Console.
Note
If the instances have not been added or if you want to change the configuration to display systems
and instances on other hosts, you have to register your system manually as described in Registering
Systems and Instances in the SAP Management Console below.
Starting SAP Systems or Instances
1. In the navigation pane, open the tree structure and navigate to the system node that you want to
start.
2. Select the system or instance and choose Start from the context menu.
3. In the Start SAP System(s) dialog box, choose the required options.
4. Choose OK.
The SAP MC starts the specified system or system instances.
Note
The system might prompt you for the credentials of the SAP system administrator. To complete
the operation, you must have administration permissions. Log in as user <sapsid>adm.
Starting the Instances of a Distributed SAP System Separately
If you need to start the instances of an SAP system separately for example when you want to start
a distributed or a high-availability system proceed as follows:
1.
2.
3.
4.
Start the database instance.

Start the central services instance SCS<Instance_Number>.
Start the central instance JC<Instance_Number>.
Start dialog instance(s) J<Instance_Number>, if there are any.
Stopping SAP Systems or Instances
1. Select the system or instance you want to stop and choose Stop from the context menu.
2. In the Stop SAP System(s) dialog box, choose the required options.
3. Choose OK.
The SAP MC stops the specified system or system instances.
Note
The system might prompt you for the SAP system administrator credentials. To complete the
operation, you must have administration permissions. Log in as user <sapsid>adm.
03/28/2008
PUBLIC
145/178
6
6.5
Similarly, you can start, stop, or restart all SAP systems and individual instances registered in the
SAP MC.
Stopping the Instances of a Distributed SAP System Separately
If you need to stop the instances of an SAP system separately for example when you want to start
a distributed or a high-availability system proceed as follows:
1.
2.
3.
4.
Stop dialog instance(s) J<Instance_Number>, if there are any.

Stop the central instance JC<Instance_Number>.
Stop the central services instance SCS<Instance_Number>.
Stop the database instance.
Registering Systems and Instances in the SAP Management Console
You can extend the list of systems and instances displayed in the SAP MC, so that you can monitor and
administer all systems and instances from a single console. You can configure the SAP MC startup
view to display the set of systems and instances you want to manage.
Prerequisites
The SAP MC is started.

Registering SAP Systems or Instances
1. In the SAP MC, choose File New .

2. In the New System dialog box, enter the required data.
Note
If you have already registered systems in the SAP MC, they are stored in the history. To open the
Systems History dialog box, choose the browsing button next to the Instance Nr. field. Select an
instance of the system that you want to add and choose OK.
3. Choose Finish.
Registering the Instances of a Distributed SAP System Separately
1. In the SAP MC, choose File New .

2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.
3. The SAP MC displays the SAP system node, the instance node and the relevant database node in
a tree view in the navigation pane.
Note
To view all instances of the respective SAP system, select the relevant system node and choose
Add Application Server from the context menu.
146/178
PUBLIC
03/28/2008
6
6.5
Configuring the SAP MC View
n You can choose the instances that the SAP MC displays automatically on startup:
1. In the Settings dialog box, select History.
2. In the right-hand pane, choose the instance you want the SAP MC to display on startup.
3. Choose the << button.
4. Choose Apply and then OK.
Similarly, you can remove instances from the startup configuration.
n You can save the current configuration in a file:
1. Choose File Save Landscape .
2. In the Save dialog box, enter the required data.
3. Choose Save.
n You can load a configuration from a file:
1. Choose File Load Landscape .
2. In the Open dialog box, select the configuration you want to load.
3. Choose Open.
More Information
For more information about the SAP Management Console, see:

by Key Capability Application Platform by Key Capability Java Technology Administration Manual J2EE
Engine J2EE Engine Administration Tools SAP Management Console
6.5.2 Starting and Stopping SAP System Instances Using

Scripts
You can start and stop SAP system instances by running the startsap and stopsap scripts.
You can also use the SAP Management Console (SAP MC) [page 144] to start or stop the instances of
the SAP system.
Prerequisites
n You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameter

login/system client and set the value to the correct production system client. For example, the
entry must be login/system_client = 001 if your production client is 001.
n You have checked the settings for Java Virtual Machine parameters as described in SAP Note
723909.
n You have logged on to the SAP system hosts as user <sapsid>adm.
n For more information about how to start or stop database-specific tools, see the database-specific
information in this documentation and the documentation from the database manufacturer.
03/28/2008
PUBLIC
147/178
6
6.5
n If you want to use startsap or stopsap (for example, in a script) and require the fully qualified
name of these SAP scripts, create a link to startsap or stopsap in the home directory of the
corresponding user.
Caution
If there are multiple SAP instances on one host for example, a central instance and a dialog
instance you must add an extra parameter to the scripts:
startsap <instanceID>
stopsap <instanceID>
For example, enter:

startsap JC00
Note
The instance name (instance ID) of the central instance is JC<Instance_Number>, the instance
name of the central services instance is SCS<Instance_Number>, and the instance name of a
Java dialog instance is J<Instance_Number>.
Procedure
Starting SAP System Instances
n To start all instances on the central system host, enter the following command:
startsap
This checks if the database is already running. If not, it starts the database first.
Note
You can start the database and SAP system separately by entering the following commands:
startsap DB
startsap R3 <instance ID of central services instance>
startsap R3 <instance ID of central instance>
startsap R3 <instance ID of dialog instance>
Make sure that you always start the database first because otherwise the other instances cannot
start.
Note
You can also use the parameter J2EE, which is a synonym for the parameter R3.
For ABAP+Java systems, you can enter either the command startsap R3 or startsap
start the SAP instance comprising both ABAP and Java.
J2EE to
n In a distributed system, proceed as follows:

1. On the database host, enter:
148/178
PUBLIC
03/28/2008
6
6.5
startdb
2. On the central services and on the central instance host, enter:

startsap
3. For dialog instances, enter the following on the relevant host:

startsap R3 <instance ID of dialog instance>
Note
Make sure that the SAP system and associated J2EE Engines are up and running before you start or
restart dialog instances and their J2EE Engines.
Stopping SAP System Instances
Note
When you use stopsap in a system with Multiple Components in One Database (MCOD) that has
two central instances, only one central instance and the database shut down. Therefore, you must
first stop the other SAP system with stopsap R3 or make sure that it has already been stopped.
For more information, see Installation of Multiple Components in one Database [page 129].
n If you have a central system, enter the following to stop all instances on the central system host:
stopsap
This stops the central instance, central services instance, and database.
Note
You can stop the database and SAP system separately by entering the following commands:
stopsap R3 <instance ID of dialog instance>
stopsap R3 <instance ID of central instance>
stopsap R3 <instance ID of central services instance>
stopsap DB
Make sure that you always stop the central instance first and the central services instance second
because otherwise the database cannot be stopped.
Note
You can also use the parameter J2EE, which is a synonym for the parameter R3.
For ABAP+Java systems, you can enter either the command stopsap R3 or stopsap
the SAP instance comprising both ABAP and J2EE.
J2EE to stop
n In a distributed system, proceed as follows:

1. On the dialog instance host, enter the following command:
stopsap <instance ID of dialog instance>
03/28/2008
PUBLIC
149/178
6
6.5
2. To stop the central services instance on the central services and on the central instance host,
enter the following command:
stopsap
3. To stop the database, enter the following command on the database host:
stopdb
Caution
Make sure that no SAP instance is running before you enter stopdb on a standalone database server.
No automatic check is made.
6.5.3 Starting and Stopping the Diagnostics Agent Using

Scripts
You can start and stop the Diagnostics Agent by running the smdstart and smdstop scripts.
The local versions of these scripts are located in /usr/sap/<SMDSID>/J<instance_number>/script.
The global versions of these scripts are located in /usr/sap/<SMDSID>/exe.
Note
You can only start or stop the Diagnostics Agent separately. It is not started or stopped automatically
with the SAP system.
You can also use the SAP Management Console (SAP MC) [page 144] to start or stop the Diagnostics Agent.
Prerequisites
You have logged on to the central instance or dialog host as user <smdsid>adm.
Procedure
Starting a Diagnostics Agent Locally
1. Change to the following directory:

/usr/sap/<SMDSID>/J<Instance_Number>/script
2. To start the Diagnostics Agent locally, enter this command:

./smdstart.sh
Starting Diagnostics Agent(s) Globally
To start Diagnostics Agent(s) globally, enter this command:

smdstart <SMDSID> <Instance_Number>
150/178
PUBLIC
03/28/2008
6
6.6
Creating a User for LDAP Directory Access (Optional)
Example
smdstart SMD 98
Note
You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this host.
Stopping a Diagnostics Agent Locally
1. Change to the following directory:

/usr/sap/<SMDSID>/J<instance_number>/script
2. To stop the Diagnostics Agent locally, enter this command:

./smdstop.sh
Stopping Diagnostics Agent(s) Globally
To stop Diagnostics Agent(s) globally, enter this command:

smdstop <SMDSID> <Instance_Number>
Example
smdstop SMD 98
Note
You do not have to specify the <SMDSID> if there is only one Diagnostics Agent system on this host.
6.6 Creating a User for LDAP Directory Access (Optional)

If you use LDAP directory services, you have to set up a user with a password on the host where the
SAP system is running. This permits the SAP system to access and modify the LDAP directory.
For more information, see section Preparing the Active Directory (Optional) in the Windows installation
guide for your SAP system solution and database.
Prerequisites
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure
1. Log on as user <sapsid>adm.

2. Enter:
ldappasswd pf=<path_and_name_of_instance_profile>
3. Enter the required data.
03/28/2008
PUBLIC
151/178
6
6.7
Configuring User Management to Use an LDAP Directory (Optional)
Example
The following is an example of an entry to create an LDAP Directory User:

CN=sapldap,CN=Users,DC=nt5,DC=sap-ag,DC=de
6.7 Configuring User Management to Use an LDAP Directory

(Optional)
If your user data source is an LDAP directory, you need to configure the connection to the LDAP
directory after installation.
For more information, see SAP Note 718383 and SAP Library at
NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server Java
Configuring Identity Management UME Data Sources LDAP Directory as Data Source Configuring UME to
Use an LDAP Directory as Data Source
6.8 Usage Type-Specific Initial Technical Configuration

SAPinst performs initial technical configuration steps for the usage types shown below during the
installation.
However, you might have to perform these steps manually if
n you have installed an additional usage type to an existing SAP system as described in SAP Note
883948
Note
This currently applies to the following usage types:

l Development Infrastructure (DI)
l EP Core (EPC)
l Enterprise Portal (EP)
l Business Intelligence (BI Java)
n you want to change existing parameters or if you want to set additional parameters.
The following usage type-specific sections provide the required information:
n Application Server Java (AS Java) [page 153]
n Development Infrastructure (DI) [page 155]

152/178
PUBLIC
03/28/2008
6
6.8
Usage Type-Specific Initial Technical Configuration
n EP Core (EPC) and Enterprise Portal (EP) [page 157]

n Business Intelligence (BI Java) [page 158]

End of: BI Java
6.8.1 Initial Technical Configuration for the Application

Server Java (AS Java)
SAPinst performs initial technical configuration steps for the AS Java components listed below during
the installation.
However, you might have to perform some of these steps manually after SAPinst has finished,
depending on your installation scenario.
For more information, see the following:
n Adobe Document Services (ADS) [page 153]
n Composite Application Framework (CAF) [page 154]
n System Landscape Directory (SLD) [page 155]
6.8.1.1 Initial Technical Configuration for Adobe Document

Services
SAPinst automatically performs some initial technical configuration steps for Adobe Document
Services (ADS) during the installation.
However, you might have to perform these steps manually if you want to change existing parameters
or if you want to set additional parameters.
SAPinst performs the following steps:
n Creates user ADSUser in AS Java for basic authentication and assigns it to group ADSCallers
For more information about this user, see Ensuring User Security [page 118].
n Sets up basic authentication in the Java environment
For more information about how to perform these steps manually, see:
Technology
Consultants Guide Business Task Management Adobe Document Services (Configuration) Adobe Document Services
Configuration Guide Configuring the Web Service Securing Access to the Web Service Configuration of the Web
Service for Basic Authentication
03/28/2008
PUBLIC
153/178
6
6.8
More Information
The Adobe Document Services Configuration Guide is also available in PDF form at:
http://sdn.sap.com/irj/sdn/adobe Installation & Configuration SAP Interactive Forms Configuration
Guides
6.8.1.2 Initial Technical Configuration for Composite

Application Framework Core (CAF)
SAPinst automatically performs some initial technical configuration steps for Composite Application
Framework Core (CAF) during the installation.
n Creates the following roles with the required User Management Engine (UME) actions:
l CAFAdmin
l CAFUIAdmin
For more information about how to perform these steps manually, see the SAP Library at:
Consultants Guide Developing, Configuring, and Adapting Applications Creating Composite Applications
Composite Application Framework Core Configuration Guide Setting Up Roles
n Configures CAF runtime properties for Business Warehouse (BW) integration
Composite Application Framework Core Configuration Guide Configuring CAF Core for BW Integration Configuring
CAF Runtime Properties for BW Integration
n Configures CAF runtime properties for knowledge management integration.
Composite Application Framework Core Configuration Guide Configuring CAF Core for Knowledge Management
Integration Configuring CAF Repository Managers Configuring CAF Runtime Properties
n SAPinst creates data sources to extract custom enumeration types.
NetWeaver Developers Guide Fundamentals Creating Composite Applications Developing Composite Applications
with CAF Core Integration CAF Core and SAP Business Information Warehouse Integration DataSource Use in
CAF and SAP BW Integration DataSources to Extract Custom Enumeration Types
154/178
PUBLIC
03/28/2008
6
6.8
6.8.1.3 Initial Technical Configuration for the System

Landscape Directory (SLD)
SAPinst automatically performs some initial technical configuration steps for the System Landscape
Directory (SLD) during the installation:
n If you chose the option Register in existing central SLD, SAPinst automatically configures the
connection of the system being installed to an existing central SLD.
n If you chose the option Configure a local SLD, SAPinst automatically sets up and configures a local
SLD during the installation.
n
n
n
n
Configures SLD security roles

Configures server and persistence parameters
Performs the initial data import
Configures the SLD bridge
For more information about how to perform these steps manually, see the documentation Post
Installation Guide System Landscape Directory of SAP NetWeaver 7.0 at:
http://service.sap.com/installNW70 Installation Configuration
More Information
n For more information about working with and configuring the SLD, see the SAP Library at:
SAP
NetWeaver by Key Capability Solution Life Cycle Management by Key Capability Software Life Cycle
Management System Landscape Directory
n For more information about SLD, see http://www.sdn.sap.com/irj/sdn/nw-sld.
n For more information about security and the role concept in the SLD, see:
Administrators Guide SAP NetWeaver Security Guide Security Aspects for System Management Security Guide
for the SAP System Landscape Directory
6.8.2 Initial Technical Configuration for Development

Infrastructure (DI)
SAPinst automatically performs some initial technical configuration steps for usage type Development
Infrastructure (DI) during the installation.
03/28/2008
PUBLIC
155/178
6
6.8
However, you might have to perform these steps manually if:

n You have installed usage type DI as an additional usage type to an existing SAP system as described
in SAP Note 883948
n You want to change existing parameters or if you want to set additional parameters.
n SAPinst creates the following NWDI users:
l NWDI_ADM
l NWDI_DEV
l NWDI_CMSADM
For more information about these NWDI users, see the table NWDI Users in Ensuring User Security
[page 118].
n SAPinst creates the following roles:
l NWDI.Administrator
l NWDI.Developer
n SAPinst adds the following actions to the role NWDI.Administrator:
l CBS.Administrator
l sap.com_com.sap.lcr.LcrInstanceWriterAll
n SAPinst adds the following actions to the role NWDI.DEVELOPER:
l CBS.Developer
l CMS.Display
l CMS.ExportOwn
l sap.com_com.sap.lcr.LcrInstanceWriterNR
n SAPinst creates the following groups:
l NWDI.Administrators
l NWDI.Developers
n SAPinst assigns the security role LcrInstanceWriterAll of the component
sap.com/com.sap.lcr*sld to the group NWDI.Administrators.
n SAPinst assigns the security role LcrInstanceWriterNR of the component
sap.com/com.sap.lcr*sld to the group NWDI.Developers.
n SAPinst assigns the role NWDI.Administrator to the group NWDI.Administrators.
n SAPinst assigns the role NWDI.Developer to the group NWDI.Developers.
n SAPinst assigns the group NWDI.Administrators to the user NWDI_ADM.
n SAPinst assigns the group NWDI.Developers to the user NWDI_DEV.
n SAPinst assigns the group NWDI.Administrators to the user NWDI_CMSADM.
Consultants Guide Developing, Configuring, and Adapting Applications Post Installation Steps of Usage Type DI
Setting Up Privileges, Roles and Groups
For more information about how to create and assign users, groups and roles, see the SAP Library at:
156/178
PUBLIC
03/28/2008
6
6.8

NetWeaver by Key Capability Security Identity Management Identity Management of the Application Server Java
Administration of Users and Roles Managing Users, Groups, and Roles

6.8.3 Initial Technical Configuration for the Portal (Usage

Types EPC and EP)
This section applies when you install usage type EPC only and when you install it together with
usage type EP.
SAPinst automatically performs some initial technical configuration steps for the usage types EPC and
EP during the installation.
However, you might have to perform these steps manually if:
n You have installed usage type EPC or EPC and EP as an additional usage type to an existing SAP
system as described in SAP Note 883948.
n You want to change existing parameters or if you want to set additional parameters.
n SAPinst copies the CMS_MAPPING Properties file.
n SAPinst renames the InitialPermissions.xml.template file to initialPermissions.xml.
n SAPinst renames the initialPermissionsKMC.xml.template file to initialPermissionsKMC.xml.
Copying CMS_MAPPING Properties
1. Change to the following source directory

/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/
servlet_jsp/irj/root/WEB-INF/portal/system/pcd/Migration/mapping/
2. Copy filecms_mapping.properties from the source directory to the following target directory:
/usr/sap/<sapsid>/SYS/global/pcd/Migration/mapping/.
Note
If the target directory does not exist, you have to create it as well.
Renaming InitialPermissions.xml.template
1. Go to directory
servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl.
2. Rename file initialPermissions.xml.template to initialPermissions.xml.
03/28/2008
PUBLIC
157/178
6
6.8
Renaming initialPermissionsKMC.xml.template
1. Go to directory
servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl
2. Rename file initialPermissionsKMC.xml.template to initialPermissionsKMC.xml.

6.8.4 Initial Technical Configuration for BI Java

SAPinst automatically performs BI Java-specific initial technical configuration steps during the
installation.
However, you might have to perform some of these steps manually if:
n You upgraded your SAP system to the current release.
n You have installed usage type BI Java as an additional usage type to an existing SAP system as
described in SAP Note 883948.
The following steps might be affected:
n
n
n
n
Configure BI Java Information Broadcasting [page 158]

Process Chains: Transport texts for alert category [page 159]
Rename initialPermissionsBI.xml.template [page 159]
Run the configuration template installer for usage type BI Java [page 122]
6.8.4.1 Configuring BI Java Information Broadcasting

For the configuration of the BI Information Broadcasting you need to perform the following steps
in your ABAP system:
1. Call transaction SPRO and perform the following steps:
a) Settings for Information Broadcasting:
Go to SAP NetWeaver Business Intelligence Reporting-relevant Settings Settings for Information
Broadcasting
b) Destinations for Web Dynpro ALV:
Go to SAP NetWeaver Application Server Web Dynpro for ABAP Set-Up Printing for Web Dynpro
ABAP ALV
n Create RFC destination in the SAP NetWeaver Portal
n Create RFC destination to the SAP NetWeaver Portal
n Set-Up Web Service destination for the Adobe Document Services
158/178
PUBLIC
03/28/2008
6
6.8
2. Installation of BI Content:
Call transaction RSTCO_ADMIN to check whether the installation has been carried out successfully.
If the installation status is red, restart the installation by calling transaction RSTCO_ADMIN again.
Check the installation log if you need further assistance or information.
Note
For the installation of SAP NetWeaver 7.0 BI Content Add-On 2 or higher on the AS ABAP system,
see SAP Note 847019.
6.8.4.2 Process Chains: Transporting Texts for the Alert

Category
Alerts can be triggered and sent for BI process chains that contain errors. Defining the alert categories
is necessary for this purpose. Alert category BWAC_PROCESS_CHAIN_FRAMEWORK is returned for errors
in background processing of process chains. This category has set texts that are not transported
when the alert category is transported.
Procedure
To manually transport the texts, see SAP Note 601619.
6.8.4.3 Renaming initialPermissionsBI.xml.template

If SAPinst does not rename the initialPermissionsBI.xml.template file automatically, you need
to rename it yourself.
Procedure
1. Go to directory
/usr/sap/<sapsid>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/
servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl
2. Rename file initialPermissionsBI.xml.template to initialPermissionsBI.xml.

End of: BI Java
03/28/2008
PUBLIC
159/178
6
6.9
Heterogeneous SAP System Installation
6.9 Heterogeneous SAP System Installation

This section provides information on the installation of an SAP system in a heterogeneous system
landscape. Heterogeneous system landscape means that application servers run on different
operating systems.
Procedure
See SAP Note 1067221 for information on

n supported combinations of operating systems and database systems,
n how to install an application server on Windows in a heterogeneous (UNIX) SAP system
environment,
n heterogeneous SAP system landscapes with different UNIX operating systems.
6.10 Troubleshooting
The following section(s) describe the steps that you need to perform manually if SAPinst fails:
n Troubleshooting with SAPinst [page 160]
n Troubleshooting for Portal Installation [page 161]

6.10.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.
If an error occurs, SAPinst:
n Stops the installation
n Displays a dialog informing you about the error
Procedure
1. To view the log file, choose View Logs.

2. If an error occurs during the dialog or processing phase, do either of the following:
n Try to solve the problem
n Abort the installation with Exit
For more information, see Interrupted Installation with SAPinst [page 92].
n Continue the installation by choosing Retry.
3. Check the log and trace files of the GUI server and SAPinst GUI in the directory
<user_home>/.sdtgui/ for errors.
160/178
PUBLIC
03/28/2008
6
6.10 Troubleshooting
4. If SAPinst GUI does not start, check the file sdtstart.err in the current <user_home> directory.
5. If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as
described in Starting SAPinst GUI Separately.
6. Ignore error messages such as the following in the SDM logs:
Error:
<SCA name>:
Location of software component <SCA name> / <SCA vendor> /
<SCA location> / <SCA counter> unknown./ Error:
<SCA name>:
system component
version store not updated.

6.10.2 Troubleshooting for Portal Installation

This section applies both when you install usage type EPC only and when you install it together
with usage type EP.
If the iViews are not displayed correctly, or if the portal does not launch, the reason might be that the
portal was not deployed completely.
To check the deployment of the portal, proceed as follows:
Procedure
1. Open a new console with the user <sapsid>adm.

2. Go to the directories deployment, pcd, and pcdContent, in the following paths:
n /usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment
/usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/
pcdContent/no_overwrite
3. Look for files with the extension *.err.

4. Do one of the following:
n If error and log files do not appear, the portal installation has been completed successfully
and you can continue.
n Rename the *.err files:
a) Remove the err extension; so the extensions of the files become *.ept or *.par.
03/28/2008
PUBLIC
161/178
6
6.11 Deleting an SAP System
b) Restart the J2EE Engine, using the commands stopsap and startsap, to change the files
to *.bak.

The following sections describe how to delete an SAP system.
Note
This description assumes that the installation of your SAP system has been performed using SAP
standard tools according to the installation documentation.
You can choose one of the following options:
n You delete the SAP system using SAPinst [page 162]. However, you still have to delete the database
manually.
n You delete the SAP system manually [page 165].
6.11.1 Deleting an SAP System Using SAPinst

You can use SAPinst to delete an SAP system.
Caution
SAPinst only stops local instances automatically.

Before you delete the database instance of a distributed system make sure that you stop all remaining
instances. You must stop the instance with the message server only after having entered all SAPinst
parameters for the deletion of the database instance.
n If you want to delete a central system (all instances reside on the same host), you can do this
in one SAPinst run.
1. Run SAPinst to delete the SAP system.
2. Delete the Oracle database software [page 164] manually.
n If you want to delete a distributed system, you have to run SAPinst to delete the required
instances locally on each of the hosts belonging to the SAP system in the following sequence:
1. Dialog instance(s), if there are any
2. Database instance
SAPinst deletes the database instance but you have to delete the Oracle database software [page 164]
manually.
3. Central instance
4. Central services instance
162/178
PUBLIC
03/28/2008
6
Caution
You cannot delete an SAP system remotely.

Caution
If you delete network-wide users, groups, or service entries in an environment with Network
Information System (NIS), other SAP installations might also be affected. Before you delete users,
groups, or service entries, make sure that they are no longer required.
Caution
When you delete an SAP system using SAPinst, system directories mounted from an NFS server
are not deleted.
You must either delete them manually [page 165] or run SAPinst on the NFS server.
6.11.1.1 Running SAPinst to Delete an SAP System

This procedure tells you how to run the Uninstall option of SAPinst.
Prerequisites
n You are logged on as user root.

n If the saposcol process on the host you are working on has been started from the SAP system you
want to delete, stop it using the command saposcol -k.
If there are other SAP systems on the host, log on as user <sid>adm of the other SAP system and
start saposcol from there using the command saposcol -l.
Procedure
1. Start SAPinst and on the Welcome screen, choose:

Software Life-Cycle Options Uninstall Uninstall System / Standalone Engine / Optional Standalone Unit
Note
With this SAPinst option you do not delete the database software.
2. Follow the instructions in the SAPinst input dialogs.
Note
For more information about the input parameters, place the cursor on the relevant field and
press F1 in SAPinst.
SAPinst first asks you which SAP instances you want to delete.
03/28/2008
PUBLIC
163/178
6
Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAP
System Using SAPinst [page 162].
Caution
SAPinst only stops local instances automatically. Before you delete the database instance of a
distributed system make sure that you stop all remaining instances. You must stop the instance
with the message server only after having entered all SAPinst parameters for the deletion of
the database instance.
3. Delete the database software manually [page 164].
4. If required, you can delete the directory /usr/sap/trans and its content manually.
SAPinst does not delete /usr/sap/trans because it might be shared.
6.11.1.2 Deleting the Oracle Database Software

You use the Uninstall functionality of the Oracle Universal Installer (OUI) to complete the deletion
of the Oracle database software.
Note
This section only applies if you have deleted your SAP system using the Uninstall service of SAPinst.
If you delete your SAP system manually, you delete the Oracle database instance as described in
Deleting an Oracle Database Instance [page 170].
Procedure
1. Start the OUI with the user ora<dbsid> by entering one of the following:
./runInstaller
./runInstaller
2.
3.
4.
5.
6.
7.
You see a message that a response file is being generated. It might take several minutes before you
see the OUI screen.
Choose Installed Products or Uninstall Products.
Select the database schema you want to uninstall: <DBSID>_102_64.
Mark the Oracle 10G database within the selected product.
Choose Remove.
Confirm your selection with Yes.
Choose EXIT.
164/178
PUBLIC
03/28/2008
6
6.11.2 Deleting an SAP System Manually

Deleting a Complete SAP System Manually
1. You delete the SAP instances [page 165] in the following sequence:
a) Dialog instances, if there are any
b) Central instance
Note
The Java part of an SAP system is deleted automatically when you delete the central instance
of the ABAP system.
c) Central services instance, if there is one
2. You delete the remaining installation files and directories on the host(s) where you deleted your SAP instance(s) [page 166].
3. You delete the Oracle database instance [page 170].
Deleting the Java Part of an SAP System
1.
2.
3.
4.
You delete the Java parts of all dialog instances [page 167], if there are any.
You delete the Java part of an SAP system [page 167].
You delete the central services instance [page 165].
You delete the Java database schema of your Oracle installation [page 169].
6.11.2.1 Deleting an SAP Instance

You use this procedure if you want to delete a single SAP instance or all instances of an SAP system.
Note
Make sure that you delete the instances in the following order:
1. Dialog instance if there are any
2. Central instance
3. Central services instance if there is one
Procedure
1. Stop the SAP instance that you want to delete as follows:

a) Log on as user <sapsid>adm.
b) Execute this command:
stopsap r3 <InstanceName>
2. Stop the sapstart service with the following command:

sapcontrol -nr <InstanceNumber> -prot NI_HTTP -function StopService
03/28/2008
PUBLIC
165/178
6
3. Stop the saposcol process with the following command:

saposcol -k
4. Remove the instance profiles as follows:

rm /usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<InstanceName>_<host_name>
rm /usr/sap/<SAPSID>/SYS/profile/START_<InstanceName>_<host_name>
Example
For example, enter the following commands:

rm /usr/sap/C11/SYS/profile/START_D00_h0001
rm /usr/sap/C11/SYS/profile/C11_D00_h0001
5. Log on as user root and delete the local instance directory:

rm -rf /usr/sap/<SAPSID>/<InstanceName>
6. Change to the directory /usr/sap. Edit the file sapservices and delete the line that refers to
the instance to be deleted.
6.11.2.2 Deleting Installation Files, Directories, and Users

on a Host
After you have deleted all SAP instances on a host, you still have to delete the remaining installation
files, directories, and users on this particular host. You have to repeat this procedure for any host
where you previously deleted an SAP instance.
Caution
Only delete files or directories that are used by other SAP instances by means of NFS mounts if you
are deleting the entire SAP system (on all hosts).
Prerequisites
You must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 165].
Procedure
1. If the following directories are mounted with NFS, unmount them:

/<sapmnt>/<SAPSID>/exe
/<sapmnt>/<SAPSID>/global
/<sapmnt>/<SAPSID>/profile
2. To delete directories, execute the following commands:

rm -rf /usr/sap/<SAPSID>
rm -rf /<sapmnt>/<SAPSID>
3. Delete the local user <sapsid>adm, its home directory, and all subdirectories of the home directory.
166/178
PUBLIC
03/28/2008
6
Caution
Do not delete user <sapsid>adm if this is a Network Information System (NIS) user and you do
not want to delete the SAP system on all hosts.
Recommendation
To delete users, use the administration tools of your operating system if possible.
a) Delete user <sapsid>adm as described in your operating system documentation.
b) If the home directory of the user was not deleted automatically in the previous step, execute
the following command to delete the directory:
rm -rf <sapsid_adm_home>
Example
rm -rf /home/c11adm
4. Delete the user <sapsid>adm from the groups sapsys, oper, and dba, if this was not done
automatically in the previous step. If one of these groups is now empty, delete the complete group
as described in your operating system documentation.
5. Check whether you need to delete entries from the file /etc/services:
a) Search for entries starting with sap
b) Check whether these entries are still required by other instances with the same or a different
<SAPSID> on any server.
c) If not, start by generating a backup copy of the services file by entering the following command:
cp /etc/services /etc/services.sap
d) Delete superfluous entries from /etc/services.

If you use NIS for the services file, see your operating system documentation for more
information on how to delete entries from network-wide service entries.
6. If there are no other SAP instances running on this host, delete the file /etc/sapconf if it exists.
7. If there are no other SAP instances running on this host, delete the file /usr/sap/sapservices.
6.11.2.3 Deleting the Java Part of an SAP System

This section describes how to delete the Java part of an SAP system.
Note
If you delete a Java part, the ABAP part of the SAP system is not deleted.
03/28/2008
PUBLIC
167/178
6
Caution
This description assumes that you installed the SAP system using SAP standard tools according
to the installation documentation.
Process
Caution
If you delete network-wide users, groups, or service entries in an environment with Network
Information System (NIS), other SAP installations might also be affected. Make sure that the users,
groups, and service entries to be deleted are no longer required.
1. Stop the central services instance and all dialog instances of your SAP system:
a) Log on to the corresponding instance host as user <sapsid>adm.
b) Execute the following commands:
n To stop the central services instance:
stopsap r3 <SCSinstanceName>
n To stop a dialog instance:

stopsap r3 <DialogInstanceName>
2. Stop the J2EE Engine of the central instance:

a) Log on to your SAP system.
b) Call transaction SMICM.
c) Choose Administration J2EE Instance (local) Send Hard Shutdown .
Note
You do not need to stop the central instance.

3. If lines beginning with the following parameters appear, delete these lines from the default profile,
/usr/sap/<SAPSID>/SYS/profile/DEFAULT.PFL:
j2ee/dbname =
j2ee/dbtype =
j2ee/dbhost =
j2ee/dbadminurl =
j2ee/scs/host =
j2ee/scs/system =
j2ee/ms/port =
4. If lines beginning with the following parameters appear, delete these lines
from the central instance prole and from all dialog instance proles,
/usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<INSTANCE_NAME>_<host_name>:
exe/j2ee =
exe/jlaunch =
168/178
PUBLIC
03/28/2008
6
rdisp/j2ee_start_control =
rdisp/j2ee_start =
rdisp/j2ee_timeout =
rdisp/j2ee_libpath =
rdisp/frfc_fallback =
jstartup/trimming_properties =
jstartup/instance_properties =
jstartup/protocol =
jstartup/vm/home =
jstartup/max_caches =
jstartup/release =
j2ee/dbdriver =
5. Delete the central services instance [page 165].

6. Delete the Oracle Java database schema [page 169].
7. Delete the following directories (<xx> is the central instance number):
n /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM
n /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee
6.11.2.4 Deleting the Oracle Database Java Schema

For the ABAP+Java installation, this section describes how to delete the Java database schema for an
Oracle database installed in the existing database of the ABAP system.
Caution
If you have multiple components installed in one database (MCOD), delete the database only if
you also want to delete all components. Otherwise, delete components selectively. For more
information, see SAP Note 399910.
Prerequisites
n Before deleting the Java database schema, stop all SAP instances belonging to this Java database
schema.
n We recommend you to delete the SAP instances before deleting the Java database schema.
Procedure
Caution
Before deleting the Java database schema, make sure that you have a recent offline database backup.
03/28/2008
PUBLIC
169/178
6
2. Start sqlplus and connect to the database. Enter:

sqlplus /nolog
SQLPLUS>connect / as sysdba
3. Enter the following command to delete the database objects of the database schema:
SQLPLUS> drop user SAP<SCHEMA_ID>DB cascade;
4. Enter the following command to get the file name of the corresponding data file in the file system:
SQLPLUS> select file_name from dba_data_files where \
tablespace_name = PSAP<SCHEMA_ID>DB;
5. Enter the following command to delete the tablespace of the database schema:
SQLPLUS> drop tablespace PSAP<SCHEMA_ID>DB including contents;
6. Exit sqlplus:
SQLPLUS> exit
7. Delete the data file of tablespace PSAP<SCHEMA_ID>DB from the file system
6.11.2.5 Deleting an Oracle Database Instance

This section describes how to delete an Oracle database that you have installed.
Caution
If you have multiple components installed in one database (MCOD), delete the database only if
you also want to delete all components. Otherwise, delete components selectively. For more
information, see SAP Note 399910.
Prerequisites
n Before deleting the database, stop all SAP instances belonging to this database or to this Java
database schema.
n We recommend that you delete the SAP instances before deleting the database instance.
Procedure

2. Start sqlplus and shutdown the database. Enter:
sqlplus /nolog
SQLPLUS> connect / as sysdba
SQLPLUS> shutdown immediate
SQLPLUS> exit
3. Kill the orasrv process if it is running:

ps -ef | grep orasrv (note the process ID <PID>)
kill 9 <PID>
170/178
PUBLIC
03/28/2008
6
4. Stop the listener process:

lsnrctl stop
5. Use the uninstall functionality of the Oracle Universal Installer (OUI):

a) Start the OUI with the user ora<dbsid> by entering one of the following:
./runInstaller
./runInstaller
You see a message that a response file is being generated. It might take several minutes before
you see the OUI screen.
b) Choose Installed Products or Deinstall Products.
c) Select the database schema you want to uninstall: <DBSID>_102_64.
d) Mark the Oracle 10G database within the selected product.
e) Choose Remove.
f) Confirm your selection with Yes.
g) Choose EXIT.
7. Delete user ora<dbsid> along with its home directory and all subdirectories of this directory:
a) Delete UNIX user ora<dbsid> using the steps appropriate for your operating system.
b) If the home directory of the user was not deleted automatically in the previous step, delete
this directory:
rm -rf <sapsid_adm_home>
Example
For example, enter:

rm -rf /home/orac11
8. Delete user ora<dbsid> from group dba, if this was not done automatically in the previous step.
If the group dba is now empty, delete the complete group using the steps appropriate for your
operating system.
9. Remove the directory /oracle/<DBSID> and subdirectories
rm -rf /oracle/<DBSID>
10. If there are no other database instances with the same Oracle release installed on this host, remove
the staging area directory, using the following command:
rm -rf /oracle/stage/102_64
11. If there are no other Oracle instances on this host, remove the Oracle client software directory
with one of the following commands:
rm -rf /oracle/client/102_64
03/28/2008
PUBLIC
171/178
Typographic Conventions
Example
Description
< >
Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your <User Name>.
Arrows separating the parts of a navigation path, for example, menu options
Example
Emphasized words or expressions
Example
Words or characters that you enter in the system exactly as they appear in the
documentation
Example
Textual cross-references to an internet address, for example, http://www.sap.com
/example
Quicklinks added to the internet address of a homepage to enable quick access to

specific content on the Web
123456
Hyperlink to an SAP Note, for example, SAP Note 123456
Example
n Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
n Cross-references to other documentation or published works
Example
n Output on the screen following a user action, for example, messages

n Source code or syntax quoted directly from a program
n File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools
EXAMPLE
Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE
EXAMPLE
Keys on the keyboard
172/178
PUBLIC
03/28/2008
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented
by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products
and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in
Germany and in several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies
("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not
be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are
those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.
This document was created using stylesheet 2006-12-31 (V5.1beta [= 6.0 for E3]) and XSLT processor SAXON 6.5.2 from
Michael Kay (http://saxon.sf.net/), XSLT version 1.
03/28/2008
PUBLIC
173/178
Disclaimer
Some components of this product are based on Java. Any code change in these components may cause unpredictable and
severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.
Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or
altered in any way.
Legal Software Terms
Terms for Included Open Source Software
This SAP software contains also the third party open source software products listed below. Note that for these third party
products the following special terms and conditions shall apply.
1. This software was developed using ANTLR.
2. SAP License Agreement for STLport
SAP License Agreement for STLPort between
SAP Aktiengesellschaft
Systems, Applications, Products in Data Processing
69190 Walldorf, Germany
(hereinafter: SAP)
and
you
(hereinafter: Customer)
a) Subject Matter of the Agreement
A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library
(STLport) and its documentation without fee.
B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual
property laws, and to all of the terms and conditions of this Agreement.
C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any
royalties or restrictions.
D) Customer shall maintain the following copyright and permissions notices on STLport sources and its
documentation unchanged: Copyright 2001 SAP AG
E) The Customer may distribute original or modified STLport sources, provided that:
n The conditions indicated in the above permissions notice are met;
n The following copyright notices are retained when present, and conditions provided in accompanying
permission notices are met:
Copyright 1994 Hewlett-Packard Company
Copyright 1996,97 Silicon Graphics Computer Systems Inc.
Copyright 1997 Moscow Center for SPARC Technology.
Copyright 1999,2000 Boris Fomitchev
Copyright 2001 SAP AG
Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is
hereby granted without fee, provided that the above copyright notice appear in all copies and that both that
copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is
174/178
PUBLIC
03/28/2008
copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no
representations about the suitability of this software for any purpose. It is provided as is without express or
implied warranty.
copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC
makes no representations about the suitability of this software for any purpose. It is provided as is without
express or implied warranty.
Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is
provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use
or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all
copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are
retained, and a notice that the code was modified is included with the above copyright notice.
copyright notice and this permission notice appear in supporting documentation. SAP makes no representations
about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set
forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only
towards its customers and only referring to its modifications.
b) Support and Maintenance
SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore
shall be not included.
All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions
and shall be subject to a separate contract.
c) Exclusion of warranty
As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the
STLport is error-free, without material defects or suitable for a specific application under third-party rights.
Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any
assurance of particular attributes.
d) Limited Liability
A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i)
can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or
(iii) if based on the failure of a guaranteed attribute.
B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial
employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall
depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract,
due to the circumstances known to it at that point in time representing a typical transfer of the software.
C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a
defect or lost profit.
D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed
EUR 5,000.
E) The Customer shall take adequate measures for the protection of data and programs, in particular by making
backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and
its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by
observing this obligation.
F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees
or agents of SAP.
3. Adobe Document Services
03/28/2008
PUBLIC
175/178
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems
Incorporated in the United States and / or other countries. For information on Third Party software delivered with
Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.
Documentation in the SAP Service Marketplace
You can find this document at the following address: https://service.sap.com/instguides
176/178
PUBLIC
03/28/2008
SAP AG
69190 Walldorf
Germany
T +49/18 05/34 34 34
F +49/18 05/34 34 20
www.sap.com
Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.

Sap Nw7.0 Sr3 Java On Aix - Oracle

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Nw7.0 Sr3 Java On Aix - Oracle

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP NetWeaver 7.0

SAP NetWeaver Java Application Server (AS Java)

Setting Up File Systems and Raw Devices . . . . . . . . . . . . .

Performing Oracle-Specific Post-Installation Steps . . . . . .

Heterogeneous SAP System Installation . . . . . . .

n SAP NetWeaver Development Infrastructure (DI)

n SAP NetWeaver EP Core (EPC)

n SAP NetWeaver Enterprise Portal (EP)

n SAP NetWeaver Business Intelligence Java Components (BI Java)

Installation of Additional Software Units or Usage Types in an Existing SAP System

1.1 New Features

SAP System Installation

As of SAP NetWeaver 7.0, SAPinst has the following new features:

You start the installation from a single Installation Master DVD.

SAP Solution Manager

SAP NetWeaver Administrator is a brand new solution for monitoring and

SAP Solution Manager

A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standalone

64-bit support for all

Only Unicode support

Every newly installed SAP system is a Unicode system.

Operating Systems and Platforms

The installation of Application Sharing Server is part of the Java installation

Links in PDF files

1.2 SAP Notes for the Installation

SAP Notes for the Installation

SAP Note Number

Release Restrictions for SAP

Oracle 10g: New functions

Information about new Oracle features released

Installing two Oracle databases

This SAP Note is only required if you plan to

Installation Prerequisite Checker SAP Software on UNIX, Windows and System i:

Supported Languages and Code

Information on possible languages and language

Hardware requirements of Java

Information on the hardware requirements for

Central Note for Heterogeneous

Heterogeneous ABAP system landscapes on

Installing SAP Systems into an

Information on features and limitations for

Customer information on restrictions in the

1.3 Online Information from SAP

Master Guide for SAP

Master Guide SAP NetWeaver 7.0

Technical Infrastructure Guide SAP

Master Guide SAP

Master Guide SAP Solution

List of media for

Media List SAP NetWeaver 7.0

Installation Guide SAP Solution

Configuration Guide SAP Solution

Support Package Stack Guide SAP

SPS <current stack>

Support Package Stack Guide

Installation Upgrade to SAP NetWeaver Systems

Installation Installation Clients

Installation Installation Clients

Component Upgrade Guide SAP

Installation of the System

Post-Installation Guide System