Professional Documents
Culture Documents
Installation Guide
n Technology consultants
n System administrators
Document version: 1.0 12/04/2006
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
2/166
PUBLIC
12/04/2006
12/04/2006
PUBLIC
3/166
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
4/166
PUBLIC
12/04/2006
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
Example
Words or characters that you enter in the system exactly as they appear in the
documentation
Example
/example
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
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
12/04/2006
PUBLIC
5/166
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.0
12/4/2006
Initial Version
6/166
PUBLIC
12/04/2006
Table of Contents
Chapter 1
1.1
1.2
1.3
1.4
Introduction . . . . . . . . . . . . .
New Features . . . . . . . . . . . . . .
SAP Notes for the Installation . . . . . . . .
Information Available on SAP Service Marketplace
Naming Conventions . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
11
12
15
16
18
Chapter 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
Planning . . . . . . . . . . . . . . . . . . . . .
Basic System Variants . . . . . . . . . . . . . . . . .
How to Distribute Instances to Hosts . . . . . . . . . . .
Production Client Considerations . . . . . . . . . . . .
Basic SAP System Parameters . . . . . . . . . . . . . .
Multi-Language and Unicode Support . . . . . . . . . . .
Running Adobe Document Services on Non-Supported Platforms
Application Sharing Server as an Optional Standalone Unit . . .
High Availability: Planning the Switchover Cluster . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
21
21
24
26
27
33
34
35
36
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
Preparation . . . . . . . . . . . . . . . . . . . .
High Availability: Switchover Preparations . . . . . . . . .
Preparing for Switchover . . . . . . . . . . . . . . . .
Setting Up File Systems . . . . . . . . . . . . . . . .
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 . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
41
42
42
44
45
47
48
49
51
52
52
53
53
55
55
57
57
57
58
12/04/2006
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7/166
3.3.3
3.4
3.4.1
3.4.2
3.4.3
3.5
3.6
3.7
3.8
3.9
3.10
3.10.1
3.10.2
3.10.3
.
.
.
.
.
.
.
.
.
.
.
.
.
.
59
60
61
66
68
69
70
71
72
72
74
74
76
77
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.3.7
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 . . . . . . . . . . . . . . . .
Installing the Java Add-In for an Existing ABAP System (Optional) .
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
90
92
92
94
95
97
97
98
98
99
100
101
101
Chapter 5
5.1
5.2
5.3
5.4
Post-Installation . . . . . . .
Starting and Stopping the SAP System
Logging On to the SAP System . .
Logging on to the Portal . . . . .
Installing the SAP License . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
103
105
108
110
111
8/166
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
12/04/2006
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.12.1
5.12.2
5.13
5.15
5.16
5.16.1
5.17
5.18
5.18.1
5.18.2
5.19
5.20
5.21
5.22
124
125
125
125
125
126
126
127
127
130
133
135
Chapter 6
6.1
6.2
6.3
6.4
6.5
6.6
6.6.1
6.6.1.1
6.6.1.2
6.6.1.3
6.6.2
6.6.3
6.6.3.1
6.6.3.2
6.6.3.3
Additional Information . . . . . . . . . . . . . . . . . . .
Installation of Multiple Components in One Database (Optional) . . . . .
Integration of LDAP Directory Services (Optional) . . . . . . . . . .
Preparing User Management for an External ABAP System . . . . . . .
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 Application Server . . . . . . . . .
Initial Technical Configuration for Adobe Document Services . . . . . .
Initial Technical Configuration for Composite Application Framework Core
Configuring the Connection for System Landscape Directory . . . . . .
Initial Technical Configuration for the Portal . . . . . . . . . . . .
Initial Technical Configuration for Process Integration (PI) . . . . . . .
Importing the SAP Exchange Profile . . . . . . . . . . . . . . .
Assigning SAP_ALL Rights to User PISUPER . . . . . . . . . . . .
Activating the ICF Services . . . . . . . . . . . . . . . . . . .
137
137
139
142
145
145
145
146
146
147
147
148
149
149
150
150
5.14
12/04/2006
PUBLIC
112
112
113
115
116
117
118
120
120
120
122
9/166
6.6.3.4
6.6.4
6.6.4.1
6.6.4.2
6.6.4.3
6.7
6.8
6.8.1
6.8.1.1
6.8.1.2
6.8.2
6.8.2.1
6.8.2.2
6.8.2.3
6.8.2.4
6.8.2.5
6.9
6.9.1
6.9.2
10/166
PUBLIC
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
151
151
152
152
153
153
154
154
155
156
157
157
158
159
161
162
164
164
165
12/04/2006
Introduction
1 Introduction
This document explains how to install SAP NetWeaver 2004s SR2 ABAP+Java.
It also explains how to install the Java Add-In for an existing SAP NetWeaver 2004s SR2 ABAP
system.
For more information about SAP NetWeaver technology, see SAP Service Marketplace at
https://service.sap.com/netweaver.
You can install SAP NetWeaver 2004s SR2 ABAP+Java and the Java Add-In with the following
usage types in a single installation run using SAPinst:
Only valid for: Application Server (AS)
12/04/2006
PUBLIC
11/166
1
1.1
Introduction
New Features
You also have to install NetWeaver Application Server Java (AS Java), EP Core (EPC) and NetWeaver
Portal (EP).
End of: BI Java Components (BI-Java)
Only valid for: Mobile Infrastructure (MI)
Note
If you want to add additional usage types to an existing SAP system, follow SAP Note 883948.
For more information about the usage types of SAP NetWeaver and their interdependencies, see the
document Master Guide SAP NetWeaver 2004s on SAP Service Marketplace [page 16]. For restrictions,
see SAP Note 855534.
Constraints
You need to consider the following constraints before you start your installation:
n You can install your SAP system with Oracle 10.2 only.
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 who are
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 a 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.
12/166
PUBLIC
12/04/2006
1
1.1
Introduction
New Features
Area
Description
SAPinst
You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP
system. Instead, you have to install an 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 58].
n You can install SAP NetWeaver as a high-availability (HA) system.
n You can change the default names of the Java users J2EE_ADMIN, J2EE_GUEST and
SAPJSF during the input phase of the installation.
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 61].
Installation DVDs
12/04/2006
PUBLIC
13/166
1
1.1
Introduction
New Features
Area
Description
Usage type EP Core As of SAP NetWeaver 2004s SR2, usage type Enterprise Portal (EP) is now divided into
(EPC)
two different usage types, EP Core (EPC) and Enterprise Portal (EP).
n EP Core (EPC)
This usage type contains the core portal capabilities that were available in the former
usage type EP. This new usage type provides more flexibility when implementing a
portal where the full enterprise portal capabilities, such as knowledge management
and collaboration, are not needed.
n Enterprise Portal (EP)
This usage type includes Knowledge management, Collaboration, CAF-Core, Visual
Composer, Web Dynpro extension, and .NET PDK, while EPC contains the portal,
GP, and UWL.
Usage type EPC is a prerequisite for usage type EP. If you want to obtain the full
capabilities of the former usage type EP, you need both EP Core and EP.
The configuration of EPC comprises only portal configuration steps.
Note
Currently EPC is not supported as a standalone usage type. You must install both
EPC and EP usage types.
SAP Solution
Manager Key
You require a key to install your SAP system. You generate this key with your SAP Solution
Manager [page 72].
Oracle Database
New functions in
Oracle Database 10g
n As of the installation of SAP NetWeaver 2004s 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
Operating Systems
Area
Description
Support of Operating
Systems
Documentation
Area
Description
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 windows opens and the SAP Note is displayed.
14/166
PUBLIC
12/04/2006
1
1.2
Introduction
SAP Notes for the Installation
Area
Description
Standalone Gateway
Installation
You can use the new links in the PDF files of the guides as follows:
n Click on the section headings such as New Features to jump back to the
table of contents at the beginning of the guide.
n Click on an internet link such as https://service.sap.com to jump to
the corresponding internet page.
You can directly access the SAP Notes that are related to the SAP NetWeaver installation at
https://service.sap.com/sapnotesnw2004s.
SAP Notes for the Installation
Title
Description
972262
852008
12/04/2006
PUBLIC
15/166
1
1.3
Introduction
Information Available on SAP Service Marketplace
Title
Description
737368
972263
828268
98252
855498
937693
Description
Internet Address
Title
https://service.sap.com/installNW2004s
Technical Infrastructure
Guide for SAP NetWeaver
2004s
https://service.sap.com/installNW2004s
https://service.sap.com/installNW2004s
Installation of SAP
Solution Manager
https://service.sap.com
/solutionmanager
Installation Guides
https://service.sap.com
/solutionmanager
Installation Guides
16/166
PUBLIC
12/04/2006
1
1.3
Introduction
Information Available on SAP Service Marketplace
Description
Internet Address
Title
Patching of SAP
NetWeaver 2004s scenarios
https://service.sap.com
Upgrade to SAP
NetWeaver 2004s
https://service.sap.com/upgradeNW2004s
Installation of SAP
NetWeaver Developer
Workplace
https://service.sap.com/installNW2004s
Installation of SAP
NetWeaver Developer
Studio
https://service.sap.com/installNW2004s
/maintenanceNW2004s
/installNW2004s
Installation of a standalone
gateway
/installNW2004s
https://service.sap.com
Configuration
https://service.sap.com
Installation - Standalone
https://service.sap.com
/installNW2004s
Installation - Standalone
https://service.sap.com/installNW2004s
Homogeneous and
heterogeneous system
copy for SAP systems based
on NetWeaver 2004s
https://service.sap.com/installNW2004s
https://help.sap.com/nw2004s
SAP
NetWeaver Library SAP NetWeaver by Key
Capability Solution Life Cycle Management by Key
Capability SAP NetWeaver Problem Analysis Guide
(PAG)
Description
Internet Address
https://help.sap.com
https://help.sap.com/nw2004s
SAP Notes
https://service.sap.com/notes
12/04/2006
PUBLIC
17/166
1
1.4
Introduction
Naming Conventions
Description
Internet Address
https://service.sap.com/sapnotesnw2004s
https://service.sap.com/platforms
https://service.sap.com/unicode
https://service.sap.com/sizing
High availability
https://service.sap.com/ha
Security
https://service.sap.com/security
https://service.sap.com/sp-stacks
https://service.sap.com/solutionmanager
Variables
Description
<SAPSID>
<sapsid>
<DBSID>
<dbsid>
<host_name>
<user_home>
<INSTDIR>
<DVD_DIR>
<OS>
<SCHEMA_ID>
Database schema ID
18/166
PUBLIC
12/04/2006
1
1.4
Introduction
Naming Conventions
12/04/2006
PUBLIC
19/166
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.
2. You choose your basic system variant [page 21].
3. You plan how to distribute the instances to hosts [page 24].
4. You decide on your production client [page 26].
5. You identify basic SAP system parameters [page 27].
6. You decide whether you want to use Unicode and multi-language support [page 33].
7. 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 34].
Only valid for: Enterprise Portal (EP)
8. You decide if you want to install Application Sharing Server as a standalone unit on a dedicated host [page 35].
End of: Enterprise Portal (EP)
Only valid for: HA (UNIX)
9. You plan the switchover cluster [page 36] for a high-availability (HA) system.
End of: HA (UNIX)
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
12/04/2006
PUBLIC
21/166
2
2.1
Planning
Basic System Variants
Note
22/166
PUBLIC
12/04/2006
2
2.1
Planning
Basic System Variants
Figure 2:
Figure 3:
12/04/2006
PUBLIC
23/166
2
2.2
Planning
How to Distribute Instances to Hosts
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 will be
created during the installation of the primary application server instance (see below).
2. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).
24/166
PUBLIC
12/04/2006
2
2.2
Planning
How to Distribute Instances to Hosts
Only valid for: HA (UNIX)
3. On the SAP global host, you run SAPinst and install the ABAP and Java central services
instances (ASCS and SCS).
End of: HA (UNIX)
4. On the SAP global host, you export the required file systems to the database and central
instance host.
5. On the database host, you mount the exported file systems from the SAP global host and
SAP transport host.
6. On the database host, you run SAPinst and install the database instance.
7. On the central instance host, you mount the exported file systems from the SAP global host
and SAP transport host.
8. On the central instance host, you run SAPinst and install the central instance.
9. 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).
Java Add-In for an Existing ABAP System
If you want to install the Java Add-In for an existing ABAP system, you proceed as follows on the
instance host(s) of the ABAP system:
n Central system on a single host
You run SAPinst and install the Java Add-In on one host.
n Distributed system on several hosts
The following figure shows how to distribute your instances on several hosts:
Figure 5:
12/04/2006
PUBLIC
25/166
2
2.3
Planning
Production Client Considerations
1. On the SAP global host, you run SAPinst and install the Java central services instance (SCS).
2. On the database host, you run SAPinst and install the Java Add-In for the database instance.
3. On the central instance host, you run SAPinst and install the Java Add-In for the central
instance.
4. If required, you run SAPinst install one to <n> ABAP+Java dialog instances.
Caution
You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system.
Instead, you have to install new ABAP+Java dialog instance(s).
1. You install the ABAP system as described in the documentation Installation Guide <your SAP system
application> ABAP on <your OS>: <database>.
2. You perform the client copy [page 117].
3. You install the Java Add-In for ABAP as described in this installation guide.
You can specify the production client to which you want to connect the Java Add-In during
the input phase of the installation.
Installing an ABAP+Java System and Reconnecting the Java Part
If you need the Java users in your ABAP production client, you have to manually configure the
connection of the Java part to the ABAP part.
For more information about Java users, see the table User Management Engine (UME) in Basic SAP
System Parameters [page 27].
1. You install the ABAP+Java system as described in this documentation.
2. You perform the client copy [page 117].
3. You reconnect the Java part to the production client as described in SAP Note 937323.
26/166
PUBLIC
12/04/2006
2
2.4
Planning
Basic SAP System Parameters
If you do not need the Java users in your ABAP production client, you do not have to manually
configure the connection of the Java part to the ABAP part.
For more information about Java users, see the table User Management Engine (UME) in Basic SAP
System Parameters [page 27].
1. You install the ABAP+Java system as described in this documentation.
2. You perform the client copy [page 117].
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
SAP System ID
...
<SAPSID>
Caution
Database ID <DBSID>
12/04/2006
PUBLIC
...
27/166
2
2.4
Planning
Basic SAP System Parameters
Parameters
Description
Instance Number
Instance Number:
...
Technical identifier for internal processes, consisting of a
two-digit number from 00 to 97.
The instance number must be unique on a host. That is, if
more than one SAP instance is running on the same host, these
instances must be assigned different numbers.
If you want to install an additional application server
instance, you must use exactly the same instance number as the
existing primary application server instance.
To find out this number, look under the SAP directory
/usr/sap/<SAPSID>/DVEBMGS<nn> on the host of the primary
application server instance.
The value <nn> is the number assigned to the primary application
server instance.
Name of Instance
Host
Instance Host:
Host name of the specific instance.
To find out the host name, open a command prompt and enter
hostname.
For more information about the allowed host name length and
characters, see SAP Note 611361.
Messaging Service
Port
...
...
Caution
Make sure that all messaging service port numbers on the same
host are unique.
Port number of the SAP Messaging Service:
If you do not specify a value, the default port number is used.
The messaging service port number must be unique for the SAP
system on all hosts.
ABAP Messaging Service Port
There is an external messaging service port using the parameter
rdisp/msserv and an internal messaging service port using the
parameter rdisp/msserv_internal.
The ABAP messaging service uses both the internal and the
external messaging service ports. Both messaging service ports
are configured in the default profile.
The external messaging service port uses the parameter
rdisp/msserv with default value 36<nn>, where <nn> is the
instance number of the ABAP messaging service instance.
The internal messaging service port uses the parameter
rdisp/msserv_internal with default value 39<nn>, where <nn>
is the instance number of the ABAP messaging service instance.
Java Messaging Service Port
The Java messaging service only uses the internal messaging
service port. The Java messaging service is configured in the SCS
instance profile.
28/166
PUBLIC
12/04/2006
2
2.4
Planning
Basic SAP System Parameters
Parameters
Description
Parameters
Description
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
Parameters
Description
Parameter
Description
ABAP Client
...
Caution
12/04/2006
PUBLIC
29/166
2
2.4
Planning
Basic SAP System Parameters
Parameter
Description
DDIC Password
...
Caution
Communication User
...
Parameter
Description
Password of webadm
30/166
PUBLIC
12/04/2006
2
2.4
Planning
Basic SAP System Parameters
Parameters
Description
SAP Solution Manager To install your SAP system, you need to generate a SAP Solution
...
key
Manager key [page 72], which the installation requires to continue.
For more information, see SAP Note 805390.
Parameters Relevant for the Connectivity to System Landscape Directory
Parameters
Description
...
...
Example
...
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
...
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
12/04/2006
PUBLIC
31/166
2
2.4
Planning
Basic SAP System Parameters
Parameters
Description
...
...
...
Parameters
Description
Your Values
/home/<username>
...
...
...
Parameters
Description
Code page
...
32/166
PUBLIC
12/04/2006
2
2.5
Planning
Multi-Language and Unicode Support
Parameters
Description
Database schemata,
Passwords
...
Database OS User, Groups Oracle User Ora<dbsid> , Oracle Group oper, dba
...
Database User
...
...
12/04/2006
PUBLIC
33/166
2
2.6
Planning
Running Adobe Document Services on Non-Supported Platforms
u SAP ABAP systems that communicate with Java components (for example via the SAP
Java Connector)
Only valid for: Process Integration (PI)
Note
For information about restrictions in non-Unicode system installations refer to SAP Note
838402.
For information about code page support of SAP JAVA Connector refer to SAP Note 794411.
n Non-Unicode systems
SAP supports more than 30 languages in non-Unicode systems, but due to the technical limitations
of non-Unicode code pages, only certain combinations of languages can be used without
restrictions.
Integration
34/166
PUBLIC
12/04/2006
2
2.7
Planning
Application Sharing Server as an Optional Standalone Unit
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 125].
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.
12/04/2006
PUBLIC
35/166
2
2.8
Planning
High Availability: Planning the Switchover Cluster
Installation
1. Run SAPinst to install Application Sharing Server as an optional standalone unit [page 101].
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.
6.
Start and stop the Application Sharing Server system [page 105].
Check the SAP Java documentation [page 133].
Apply the latest kernel and support packages [page 116].
Perform post-installation steps for Adobe Document Services [page 120].
Perform post-installation steps for Application Sharing Server [page 125].
Ensure the security of Java standalone users stored in the database [page 127].
36/166
PUBLIC
12/04/2006
2
2.8
Planning
High Availability: Planning the Switchover Cluster
If you want install the Java Add-In to an existing ABAP High-Availability system, we recommend
that you install the Java central services instance (SCS) in the switchover cluster of the ABAP central
services instance (ASCS).
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 SAP High Availability at:
https://service.sap.com/ha Media Library Documentation HA Documentation .
This covers HA for SAP systems based on SAP NW 2004s and is part of the standard SAP
documentation delivered with SAP NW 2004s.
n Technical Infrastructure Guide: SAP NetWeaver 2004s at:
https://service.sap.com/installNW2004s
12/04/2006
PUBLIC
37/166
2
2.8
Planning
High Availability: Planning the Switchover Cluster
Figure 6:
Note
This figure and the figures in this section are only examples. You need to discuss your individual HA
setup with your HA partner.
The following figure shows an example of a switchover cluster in more detail:
38/166
PUBLIC
12/04/2006
2
2.8
Planning
High Availability: Planning the Switchover Cluster
Figure 7:
Constraints
This documentation concentrates on the switchover solution for the central services instance.
For more information on 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.
More Information
12/04/2006
PUBLIC
39/166
Preparation
3 Preparation
1. You perform the switchover preparations [page 42] for a high-availability (HA) system.
End of: HA (UNIX)
2.
3.
4.
5.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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 install the SAP front-end software [page 71].
Caution
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
7. You generate the SAP Solution Manager Key [page 72].
Caution
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
12/04/2006
PUBLIC
41/166
3
3.1
Preparation
High Availability: Switchover Preparations
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 36].
Procedure
1. You check that your system meets the hardware and software requirements [page 47] 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 node A (before the installation of the SCS instance with SAPinst) and node B (after the
installation of the SCS instance with SAPinst):
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 often 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.
42/166
PUBLIC
12/04/2006
3
3.1
Preparation
High Availability: Switchover Preparations
a) You set up the required file systems [page 44] using mount points or NFS
b) If required, you configure NFS [page 45], 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 8:
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
4. You assign the virtual IP addresses and host names for SCS instance, and (if required) NFS to
appropriate cluster packages.
12/04/2006
PUBLIC
43/166
3
3.1
Preparation
High Availability: Switchover Preparations
Caution
This step does not apply to the installation of a Java Add-In to an existing ABAP system.
Note
For more information on how to assign resources to cluster packages, ask your HA partner.
End of: HA (UNIX)
Only valid for: HA (UNIX)
This section does not apply to the installation of a Java Add-In to an existing ABAP 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 [page 61].
Note
The file systems /sapmnt/<SID> and /usr/sap/trans are Network File Systems (NFS), whereas
/usr/sap>SID> is a file system 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 /usr/sap/<SID> file system.
The file system contains two subdirectories:
n SYS contains links to the central directory /sapmnt/<SID>
n <INSTTYPE><NR> (where the name is defined by the type of services and the application server
number, for example DVEBMSG00), which contains data for the local AS instance.
Only the latter directory needs to be migrated with the AS instance during the switchover.
As 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/<SID>, create a file system
/usr/sap/<SID>/<INSTTYPE><NR> with the usual <> substitutions. The file name for the CI is
normally DVEBMGS00. This avoids mount conflicts when switching over to a node on which an AS
44/166
PUBLIC
12/04/2006
3
3.1
Preparation
High Availability: Switchover Preparations
instance is already running. The DVEBMGS00 directory can join the /usr/sap/<SID> tree instead
of mounting on top of it.
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 (in order
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)
Only valid for: HA (UNIX)
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.
12/04/2006
PUBLIC
45/166
3
3.1
Preparation
High Availability: Switchover Preparations
2. Since you can protect NFS by a switchover product, it makes sense to install it on a cluster node.
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>
46/166
PUBLIC
12/04/2006
3
3.2
Preparation
Hardware and Software Requirements
/sapmnt/<SID>
n The values that are checked by the Prerequisite Checker apply to the installation of development
systems or quality assurance systems.
n For the most recent updates to the Prerequisite Checker, always check SAP Note 855498.
You can run the Prerequisite Checker as follows:
n Standalone (optional):
To check the hardware and software requirements of the host on which you want to later install
an SAP system, you can run the Prerequisite Checker standalone [page 48].
n Integrated in SAPinst (mandatory):
SAPinst automatically runs the Prerequisite Checker when you install your SAP system.
We also recommend that you consult the requirements checklists tables, which provide values for the
installation of development systems or quality assurance systems. Depending on the amount of
data involved, the requirements might change. In addition, consider the following information:
n To get precise sizing values for production systems, you have to do one of the following:
l You use the SAP Quick Sizer tool that is available on SAP Service Marketplace at
https://service.sap.com/sizing. You enter information about your planned system and
the tool calculates the requirements.
For more information, see Planning your System Landscape in the Master Guide SAP NetWeaver 2004s,
which is available on SAP Service Marketplace [page 16].
l You contact your hardware vendor, who can analyze the load and calculate suitable hardware
sizing.
n For supported operating system and Java (JDK/JRE) releases, see the Product Availability Matrix on
SAP Service Marketplace at https://service.sap.com/pam.
n Contact your OS vendor for the latest OS patches.
n Make sure that the host name meets the requirements listed in SAP Note 611361.
n Check your keyboard definitions.
12/04/2006
PUBLIC
47/166
3
3.2
Preparation
Hardware and Software Requirements
n 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. If required, you run the Prerequisite Checker standalone [page 48] to check the hardware and software
requirements.
Caution
If you do not fully meet the requirements, you might experience problems when working with
the SAP system.
2. In addition, we recommend that you check the hardware and software requirements for your
operating system and for the system variant that you want to install:
n AIX [page 49]
n Central system [page 51]
n Distributed or high availability system [page 52]
3. If you want to install additional dialog instances, check the requirements for a Dialog instance
[page 55].
We recommend that you use both the Prerequisite Checker and the requirements tables for reference.
Note
When installing your SAP system, SAPinst automatically starts the Prerequisite Checker and checks the
hardware and software requirements in the background.
Procedure
48/166
PUBLIC
12/04/2006
3
3.2
Preparation
Hardware and Software Requirements
Note
For more information about each parameter, position the cursor on the parameter field and
choose F1 in SAPinst.
When you have finished, the Start Execution screen appears summarizing all parameters you have
entered. To change a parameter, choose Back and enter a new value.
4. To start the Prerequisite Checker choose Start.
Result
After the check has successfully completed, the Prerequisite Check Results screen appears displaying
the results found.
If required, you can also check the results in file prerequisite_checker_results.html, which you
can find in the installation directory.
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 ).
Requirement Type Requirement
Hardware
n 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
n CD / DVD drive
l ISO 9660 compatible
l 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 77].
n 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
12/04/2006
PUBLIC
49/166
3
3.2
Preparation
Hardware and Software Requirements
n Swap Space
3 to 4 * RAM
n CPU
The recommended minimum hardware is either two physical single core processors
or one physical dual core processor.
Software
n Additional software
Make sure that the following additional file sets are installed:
l bos.adt Base Application Development
l bos.perf performance and diagnostics tools
l perfagent.tools performance monitoring tools
l bos.perf.libperfstat Performance Statistics Library
For an overview of the installed file sets, enter this 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 this command:
smitty mle_add_lang
to install:
50/166
PUBLIC
12/04/2006
3
3.2
Preparation
Hardware and Software Requirements
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
n 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
n 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.
n Network
Test the network connection to the database server with this command:
/etc/ping <db_server_name> 100 10
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central instance
For more information, see Setting Up File Systems [page 61] SAP File Systems .
n Hard disk drives with sufficient space for swap: 3 to 4 * RAM
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 74].
n 1.2 GB of temporary disk space for the installation.
n RAM:
3 GB (minimum), 8 GB (recommended)
Java Add-In (ABAP system already exists): 1.5 GB (minimum), 4 GB
(recommended)
Only valid for: BI Java Components (BI-Java)
12/04/2006
PUBLIC
51/166
3
3.2
Preparation
Hardware and Software Requirements
Requirement
Type
Requirement
Software
n If application servers are installed decentralized, Network File System (NFS) must be
installed.
n Make sure that the required fonts and code pages are installed.
n Make sure that National Language Support (NLS) and corresponding saplocales are
installed.
If you install multiple SAP system instances on one host, you need to add up the requirements.
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central services instance
For more information, see Setting up File Systems [page 61].
n Hard disk drives with sufficient space for swap: 3 to 4 * RAM
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 74].
n 1.2 GB of temporary disk space for the installation.
n RAM:
0.5 GB (minimum), 1 GB (recommended)
52/166
PUBLIC
12/04/2006
3
3.2
Preparation
Hardware and Software Requirements
Requirement Type
Requirement
Only valid for: HA (UNIX)
1 GB (minimum), 3 GB (recommended)
End of: HA (UNIX)
Software
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the central instance.
For more information, see Setting Up File Systems [page 61] SAP File Systems .
n Hard disk drives with sufficient space for swap: 3 to 4 * RAM
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 74].
n 1.2 GB of temporary disk space for the installation.
n RAM:
1.5 GB (minimum), 5 GB (recommended)
Java Add-In (ABAP system already exists): 0.5 GB (minimum), 2 GB
(recommended)
Software
n If application servers are installed decentralized, Network File System (NFS) must be
installed.
n Make sure that the required fonts and code pages are installed.
n Make sure that National Language Support (NLS) and corresponding saplocales are
installed.
12/04/2006
PUBLIC
53/166
3
3.2
Preparation
Hardware and Software Requirements
Note
You can access the complete Oracle documentation as a member of the Oracle Technology Network
(OTN) at:
http://www.oracle.com/documentation
Recommendation
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1.
This document provides information on 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
You can install SAP NetWeaver 2004s SR2 with Oracle 10.2 only.
Requirement Type
Requirement
Hardware
n DVD drive
n We recommend distribution over three disks (RAID5) for data security
reasons.
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
https://help.sap.com/nw2004s
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 .
n Hard disk drives with sufficient space for the database instance. For
more information, see Setting Up File Systems and Raw Devices Oracle File
Systems [page 66].
n Hard disk drives with sufficient space for swap: 3 to 4 * RAM
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 74]
n 1.2 GB of temporary disk space for the installation.
n RAM:
1 GB (minimum), 3 GB (recommended)
Java Add-In (ABAP system already exists): 500 MB (minimum), 2
GB (recommended)
Software
54/166
PUBLIC
12/04/2006
3
3.2
Preparation
Hardware and Software Requirements
Requirement Type
Requirement
Requirement
Hardware
n DVD drive
n Hard disk drives with sufficient space for the dialog instance.
For more information, see Setting up File Systems [page 61].
n Hard disk drives with sufficient space for swap: 3 * RAM + 500 MB
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 74].
n 1.2 GB of temporary disk space for the installation.
n RAM:
1 GB minimum, 3 GB recommended
Software
We recommend that all UNIX kernel modifications be performed by your UNIX system
administrator.
12/04/2006
PUBLIC
55/166
3
3.2
Preparation
Hardware and Software Requirements
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
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.
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
56/166
PUBLIC
12/04/2006
3
3.3
Preparation
Creating Operating System Users
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 57].
12/04/2006
PUBLIC
57/166
3
3.3
Preparation
Creating Operating System Users
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.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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 which 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.
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.
Users and Their Primary Groups
User
Primary Group
<sapsid>adm
ora<dbsid>
58/166
PUBLIC
12/04/2006
3
3.3
Preparation
Creating Operating System Users
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
oper
<sapsid>adm, ora<dbsid>
dba
<sapsid>adm, ora<dbsid>
sapinst
<sapsid>adm, ora<dbsid>
More Information
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
12/04/2006
PUBLIC
59/166
3
3.4
1.
2.
3.
4.
Preparation
Setting Up File Systems and Raw Devices
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.
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.
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 58].
60/166
PUBLIC
12/04/2006
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Note
For more information on how to set up your file systems if you are performing an HA installation,
see High Availability: Setting Up File Systems [page 44].
End of: HA (UNIX)
Caution
The ABAP part of an ABAP+Java System can be Unicode or Non-Unicode, whereas the Java part is
always Unicode.
12/04/2006
PUBLIC
61/166
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Figure 9:
Figure 10:
62/166
SAP File Systems for an ABAP + Java System (ABAP Non-Unicode, Java Unicode)
PUBLIC
12/04/2006
3
3.4
Preparation
Setting Up File Systems and Raw Devices
The instance name (instance ID) of the ABAP+Java central instance is DVEBMGS<Instance_Number>,
the instance name of an ABAP+Java dialog instance is D<Instance_Number> and the instance name
of the Java central services instance is SCS<No>.
Only valid for: HA (UNIX)
If you are performing an HA installation of your ABAP+Java system, there is also an ABAP central
services instance called ASCS<Instance_Number>.
End of: HA (UNIX)
Example
Note
Space Required
n Central Instance:
3.0 GB
Java Add-In (ABAP system
already exists): 1.5 GB
n Central Services Instance:
1.0 GB
n Dialog instance:
no file system required
Note
12/04/2006
PUBLIC
63/166
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Space Required
<SAPSID>/exe/uc/<platform>
global
profile
/<sapmnt>/<SAPSID>/profile
/usr/sap/<SAPSID>/SYS/global is
/<sapmnt>/<SAPSID>/global
/usr/sap/<SAPSID>/SYS/exe/run is linked to
n Central instance
l AS ABAP:
1.5 GB (Non-Unicode), 2.0 GB
(Unicode)
l AS Java:
1.5 GB (Non-Unicode), 2.0 GB
(Unicode)
Java Add-In (ABAP system
already exists): 1.0 GB
l For BI add 2.0 GB.
l For EPC add 1.5 GB.
l For EP add 1.0 GB.
l For PI add 1.0 GB.
l For MI add 0.5 GB.
Dialog
instance:
n
See the space requirements
above for the central instance
minus one third of the space
requirements for Java software
units or usage types.
n Central Services Instance:
1.0 GB
linked to
which is
linked to /<sapmnt>/<SAPSID>/exe
/usr/sap/<SAPSID>/SYS/exe/dbg
Note
64/166
PUBLIC
12/04/2006
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Space Required
Executables located
in/usr/sap/<SAPSID>/SYS/exe/run are
replicated by sapcpe to the exe directory of
instances of the type <INSTANCE_NAME>, SCS<No>,
ASCS<No>.
Note
Note
12/04/2006
PUBLIC
65/166
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Set up the file systems required for the database as described in Oracle File Systems [page 66].
Unicode systems require additional hardware resources. You can find more information about
Unicode SAP systems on SAP Service Marketplace at https://service.sap.com/unicode.
Set up the required file system for the Oracle database before the installation.
Figure 11:
Description
Space Required
/oracle
/oracle/client
100 MB
/oracle/client/102_32/instantclient
or
is
created by SAPinst during the installation.
/oracle/client/102_64/instantclient
66/166
PUBLIC
12/04/2006
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Description
Space Required
/oracle/stage/102_32
5.5 GB
/oracle/<DBSID>
/oracle/<DBSID>/102_32
/oracle/<DBSID>/origlogA
200 MB
/oracle/<DBSID>/origlogB
200 MB
/oracle/<DBSID>/mirrlogA
200 MB
/oracle/<DBSID>/mirrlogB
200 MB
/oracle/<DBSID>/oraarch
or
/oracle/stage/102_64
or
/oracle/<DBSID>/102_64
12/04/2006
PUBLIC
/oracle/<DBSID>/oraarch
67/166
3
3.4
Preparation
Setting Up File Systems and Raw Devices
Description
Space Required
/oracle/<DBSID>/sapreorg
1.5 GB
/oracle/<DBSID>/sapdata1
SAP data
/oracle/<DBSID>/sapdata2
SAP data
/oracle/<DBSID>/sapdata3
SAP data
/oracle/<DBSID>/sapdata4
SAP data
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 .
68/166
PUBLIC
12/04/2006
3
3.5
Preparation
Exporting and Mounting the Global Transport Directory
of raw log.vol>.
Example
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
In your SAP system landscape, a global transport directory for all SAP systems is required.
12/04/2006
PUBLIC
69/166
3
3.6
Preparation
Exporting and Mounting Directories via NFS for AIX (Optional)
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.
2. Create the mount point /usr/sap/trans.
3. Mount /usr/sap/trans using Network File System (NFS) from the exporting host.
More Information
To mount directories via NFS from the host on which the directory to be mounted resides:
1. Log on as user root.
2. To start NFS services at the host on which the directory to be mounted resides, use SMIT as follows:
a) Enter the command smitty.
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.
70/166
PUBLIC
12/04/2006
3
3.7
Preparation
Installing the SAP Front-End Software
d) Choose ENTER .
3. Export the directory (for example <sapmnt>/<SAPSID>/exe) with read or read-write access for the
host on which the additional instance runs:
a) Enter the command smitty.
b) Choose Communications Applications and Services NFS Network File System (NFS) Add a Directory
to Exports List .
c) Enter the path of the directory which 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 on which 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 on which the additional instance runs: /usr/bin/mkdir
<sapmnt>/<SAPSID>/exe
5. Mount the directory on the host on which the additional instance runs.
a) Enter the command smitty.
b) Choose Communications Applications and Services NFS Network File System (NFS) Add a File System
for Mounting .
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 on which the future
additional instance will 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)
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
12/04/2006
PUBLIC
71/166
3
3.8
Preparation
Generating the SAP Solution Manager Key
For the installation, make sure that the front-end software is installed on at least one host machine in
your system environment. To simplify the administration of your SAP system, we recommend you
install the software on the central instance host.
With the SAP front-end installation software, SAPSetup, you can optimize the deployment of SAP
GUI to thousands of clients. You can easily tailor installation packages to match your requirements,
distribute patches, and set up automatic update processes for your clients.
For more information on installing the front-end software, see the documentation on SAP Service
Marketplace at https://service.sap.com/installNW2004s :
n SAP Front End Installation Guide (English version)
n SAP Frontend-Installationsleitfaden (German version)
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
You need to generate the Solution Manager key because SAPinst prompts for it during the input
phase of the installation. Without this key, the installation process cannot continue.
You can generate all needed keys for your entire system landscape on one SAP Solution Manager
system. For more information, see SAP Note 805390.
Prerequisites
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 <release> on <OS> : <Database> on SAP Service Marketplace at:
https://service.sap.com/solutionmanager SAP Solution Manager Installation Guides
Release <3.2 or 4.0>
2. Generate the SAP Solution Manager key as described in SAP Note 811923.
Result
The system displays the key, which you need to enter during the input phase of the installation.
72/166
PUBLIC
12/04/2006
3
3.9
Preparation
Installing the Java Development Kit
As of SAP NetWeaver 2004s you must install the J2EE Engine with strong encryption.
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 21] 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 https://service.sap.com/pam.
b) On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 2004s JSE Platforms .
c) Choose tab strip JSE Platforms.
For additional information on the recommended JDK version and about how to obtain it, see
SAP Note 709140.
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 JDK is not already installed
Since JDK is not part of the SAP shipment, you need to download and install it.
n If JDK is already installed
Check the installed version of 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 2004s 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.
12/04/2006
PUBLIC
73/166
3
Preparation
3.10 Preparing and Mounting the Installation Media
If you copy the installation DVDs to disk, make sure that the paths to the location of the copied
DVDs do not contain any blanks.
Procedure
1. Identify the required DVDs for your installation as listed below and keep them separate from the
remaining DVDs. This helps you to avoid mixing up DVDs during the installation.
Caution
If you are installing on an existing system using Multiple Components in One Database (MCOD),
the required DVDs will differ .
The following table shows the required DVDs for the installation of an SAP system based on the
usage type AS ABAP and AS Java:
Note
You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaver
usage types on the NetWeaver Java DVD.
74/166
PUBLIC
12/04/2006
3
Preparation
3.10 Preparing and Mounting the Installation Media
Only valid for: BI Java Components (BI-Java)
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 152].
End of: BI Java Components (BI-Java)
Required DVDs
n
n
n
n
n
n
n
The following table shows the required DVDs for the installation of the Java Add-In for an
existing ABAP System:
SAP Instance Installation
Required DVD
n
n
n
n
12/04/2006
PUBLIC
75/166
3
Preparation
3.10 Preparing and Mounting the Installation Media
To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which you
can find on SAP Service Marketplace at https://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
...
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.
76/166
PUBLIC
12/04/2006
3
Preparation
3.10 Preparing and Mounting the Installation Media
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.
CDROM
Example
<medium-mountdir>
is /sapcd
e) Choose ENTER .
f) To exit smitty, choose F10 .
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.
a)
b)
c)
d)
e)
f)
-v
12/04/2006
PUBLIC
77/166
3
Preparation
3.10 Preparing and Mounting the Installation Media
g)
h)
i)
j)
k)
78/166
PUBLIC
F4 .
12/04/2006
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
Only valid for: 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.
Only valid for: Enterprise Portal (EP)
4. If required, you can install an Application Sharing Server as an optional standalone unit [page 101].
End of: Enterprise Portal (EP)
Only valid for: HA (UNIX)
n You have completed all preparations, including preparing the installation of switchover units [page 42].
12/04/2006
PUBLIC
79/166
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.
Caution
If you install the Java Add-In to an existing ABAP system, note the following:
l When you install the central services instance, SAPINST_USE_HOSTNAME must point to the
virtual host name under which the central services instance is to run.
l When you install the database instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the database is installed.
l When you install the central instance, SAPINST_USE_HOSTNAME must point to the virtual
host name under which the central instance is installed.
Procedure
1. Install the central services (SCS) instance with SAPinst [page 85] using the virtual host name on the primary
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 42].
3. Set up the user environment on the standby node, host B.
For more information, see Creating Operating System Users and Groups Manually [page 58]. 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. You enable remote logons as follows:
a) To run certain operating system commands as user root and <sid>adm you have to allow
remote logons from user root to user <sid>adm.
b) You have to create the file .rhosts in the home directory of <sid>adm on each host machine
as follows:
host1 root
host2 root
This allows the user root to perform a remote logon to the <sid>adm account from both
host1 and host2.
5. Configure the switchover software and test that switchover functions correctly.
6. Install the database instance on the primary node, host A.
7. 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 ABAP SCS, which
is protected by the cluster.
80/166
PUBLIC
12/04/2006
4
4.2
Installation
Prerequisites before Starting SAPinst
8. 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 126].
End of: HA (UNIX)
n Make sure that you have defined the most important SAP system parameters as described in Basic
SAP System Parameters [page 27] before you start the installation.
n Check that your installation host(s) meets the requirements for the installation service(s) that you
want to install. For more information, see Running the Prerequisite Checker [page 48].
Procedure
1. If you want to install a dialog instance for an SAP system upgraded to SAP NetWeaver 2004s SR2
or Business Suite 2005 SR2, do the following:
a) Edit DEFAULT.PFL.
b) Set rdisp/msserv_internal to a free port number.
Note
12/04/2006
PUBLIC
81/166
4
4.2
Installation
Prerequisites before Starting SAPinst
...
After the change:
...
rdisp/msserv = sapmsSID
rdisp/msserv_internal = <free port number>
...
n 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.
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 .
82/166
PUBLIC
12/04/2006
4
4.2
Installation
Prerequisites before Starting SAPinst
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.
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 137].
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 where the SAPinst GUI is displayed.
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 153].
Procedure
1. Log on to the central instance host as user root and export the following directories with root
access to the dialog instance host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
For more information, see Mounting Directories via NFS for AIX [page 70].
12/04/2006
PUBLIC
83/166
4
4.3
Installation
Installing an SAP System Using SAPinst
Caution
Make sure that the global transport directory is mounted on every host where you want to install
an SAP instance. For more information, see Exporting and Mounting the Global Transport Directory [page
69]. Otherwise, the installation fails.
2. Log on to the distributed instance host as user root.
3. Create the following mount points and mount them from the central instance host:
<sapmnt>/<SAPSID>/exe
<sapmnt>/<SAPSID>/profile
<sapmnt>/<SAPSID>/global
Only valid for: HA (UNIX)
Set SAPINST_USE_HOSTNAME to the virtual host name of the machine on which you are installing
an SAP instance.
End of: HA (UNIX)
84/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
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 77].
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
Only valid for: HA (UNIX)
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.
12/04/2006
PUBLIC
85/166
4
4.3
Installation
Installing an SAP System Using SAPinst
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
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_gui_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:
./sapinst -p.
4. In the Welcome screen, choose one of the following installation services:
n SAP Systems
n Additional Software Life-Cycle Tasks
The following tables provide more information about these installation services:
n SAP Systems
You use this service to install a SAP system with usage types or software units by choosing
<SAP system> SAP Systems <Database> <System Variant> Based on <technical stack> .
You can install the following system variants:
l Central System
l Distributed System
Only valid for: HA (UNIX)
86/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
The following tables provide an overview of the installation services available for these system
variants:
Note
l Choose the corresponding installation services 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 service Operating System Users and Groups before you start the installation
(see table Additional Software Life-Cycle Tasks below).
l If required, install a dialog instance for a central or distributed system by choosing the
installation service <SAP System> Additional Software Life-Cycle Tasks Application Server
Dialog Instance .
Installation Services for a Central System
Installation Service
Remarks
12/04/2006
PUBLIC
87/166
4
4.3
Installation
Installing an SAP System Using SAPinst
Installation Services for a Distributed System
Installation Services
Remarks
Database Instance
Central Instance
Installation Services
Remarks
Central Services Instance Installs a central services instance for ABAP (ASCS) and prepares the SAP
for ABAP (ASCS)
global host.
Central Services Instance Installs a central services instance (SCS).
(SCS)
Database Instance
Central Instance
Dialog Instance
Remarks
Perform this task before you start the installation of your SAP
system.
l Prerequisites Check
Checks your hardware and software requirements before you
start the installation.
88/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
Installation Service
Remarks
System Copy
Installa-
tion
Uninstall
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:
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.
12/04/2006
PUBLIC
89/166
4
4.3
Installation
Installing an SAP System Using SAPinst
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 164].
90/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
Installation Services for a Java Add-In for ABAP Central or Distributed System
Installation Services
Remarks
Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage
types or software units based on AS Java
Database Instance Java Add-In
Installation Services
Remarks
Central Services Instance (SCS) Java Add-In Installs a central services instance (SCS) and adds usage
types or software units based on AS Java
Database Instance Java Add-In
4. Follow the instructions in the SAPinst input dialogs and enter the required parameters.
Note
SAPinst prompts you for the production client of your ABAP system, which is where you install
the Java Add-In.
After you have entered all required input parameters, SAPinst starts the installation and displays
the progress of the installation.
Result
After running these installation services, your ABAP+Java system consists of the following instances:
n Java central services instance (SCS)
n ABAP+Java database instance
n ABAP+Java central instance
Caution
You cannot install the Java Add-In for the dialog instance(s) of the existing ABAP system. Instead,
you have to install new ABAP+Java dialog instances as follows:
On the Welcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Application
Server <database> Dialog Instance .
12/04/2006
PUBLIC
91/166
4
4.3
Installation
Installing an SAP System Using SAPinst
Description
F1
Exit
Log off
Stops the SAPinst GUI, but SAPinst and the GUI server
continue running.
Note
Stop
Continue
92/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
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
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
Make sure that the root user has not set any environment variables for a different SAP system or
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.
12/04/2006
PUBLIC
93/166
4
4.3
Installation
Installing an SAP System Using SAPinst
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
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
Make sure that the root user has not set any environment variables for a different SAP system or
database.
2. Mount the Installation Master DVD.
3. Enter the following commands:
cd <Installation_Master_DVD>/IM_<OS>
./sapinst -nogui
94/166
PUBLIC
12/04/2006
4
4.3
Installation
Installing an SAP System Using SAPinst
4. Start SAPinst GUI on your local host, as described in Starting SAPinst GUI Separately [page 95].
You have installed the Java Development Kit [page 72] on the host on which you want to start SAPinst
without SAPinst GUI.
Starting SAPinst GUI on a Windows Platform
12/04/2006
PUBLIC
95/166
4
4.3
Installation
Installing an SAP System Using SAPinst
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. As
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
Make sure that the root user has not set any environment variables for a different SAP system or
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:
cd <Installation_Master_DVD>/IM_<OS>
96/166
PUBLIC
12/04/2006
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. As
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.
If there is more than one entry for the same port number, this is not an error.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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 100]
You install required interim patches [page 101]
12/04/2006
PUBLIC
97/166
4
4.4
Installation
Oracle Database Software Installation
mv /oracle/stage/<102_32 or 102_64>/database/Disk1/SAP
/oracle/stage/<102_32 or 102_64>/database/Disk1/SAP_ORIG
2. Download the file RDBMS_SAP_32.zip (for 32-bit platforms) or RDBMS_SAP_64.zip (for 64-bit
platforms) 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_32 or 102_64>/database
unzip /tmp/RDBMS_SAP.zip
You should now see the directory SAP extracted with the updated version of SAP-specific files.
If several Oracle instances run on one computer, you must shut these down before adapting the
kernel.
Procedure
c) Make sure that the user root is assigned the environment of ora<dbsid>:
su root
rootpre.sh:
./rootpre.sh
98/166
PUBLIC
12/04/2006
4
4.4
Installation
Oracle Database Software Installation
2. Remove any currently unused modules in kernel and library memory by entering the following
command as user root:
# /usr/sbin/slibclean
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.
2. Respond to the OUI as follows:
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
12/04/2006
PUBLIC
99/166
4
4.4
Installation
Oracle Database Software Installation
Prompt or Condition
Action
Summary page
3. 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.
4. 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.
n For more information on the latest patch set available for Oracle 10.2 see SAP Note 871735.
n For more information on 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 patchset 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.
100/166
PUBLIC
12/04/2006
4
4.5
Installation
Installing Application Sharing Server as an Optional Standalone Unit
n You only have to install the latest (that is, the current) patch set.
Procedure
n Make sure you have already installed the current patch set [page 100].
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
This command lists all the patches that have been applied to the software installation.
Only valid for: Enterprise Portal (EP)
12/04/2006
PUBLIC
101/166
4
4.5
Installation
Installing Application Sharing Server as an Optional Standalone Unit
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 35].
n Your machine meets the hardware requirements for AS Java.
Procedure
102/166
PUBLIC
12/04/2006
Post-Installation
5 Post-Installation
Note
Before you perform post-installation steps, make sure that you have read the release notes for the
software components that you have installed and that you want to use for your IT scenario. You can
find these release notes on SAP Service Marketplace at:
https://service.sap.com/releasenotes.
You perform the following post-installation steps:
1. You start and stop the SAP system [page 105].
2. You log on to the SAP system [page 108].
Only valid for: Enterprise Portal (EP);EP Core (EPC)
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
5. You install the SAP Online Documentation [page 112].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
6. You configure the remote connection to SAP support [page 112].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
7. You perform initial ABAP configuration [page 113].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
8. You complete and check the Oracle Installation [page 115]
12/04/2006
PUBLIC
103/166
Post-Installation
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
9. You apply the latest kernel and Support Packages [page 116].
10. You perform the client copy [page 117]
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
11. You perform a full backup of the installation [page 118].
12. You perform post-installation steps for Adobe Document Services [page 120].
13. You perform post-installation steps for Composite Application Framework [page 122].
14. If required, you configure access to SAP Knowledge Warehouse content from the SAP Internet Knowledge Servlet
[page 124].
Only valid for: BI Java Components (BI-Java);Process Integration (PI)
16. You perform the post-installation steps for usage type Process Integration (PI) [page 125].
End of: Process Integration (PI)
Only valid for: Enterprise Portal (EP)
17. You perform the post-installation steps required for Application Sharing Server [page 125].
End of: Enterprise Portal (EP)
Only valid for: HA (UNIX)
18. You perform the required post-installation steps for high availability [page 126].
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
End of: HA (UNIX)
20. To perform basic configuration steps, you run the Template Installer [page 130].
104/166
PUBLIC
12/04/2006
5
5.1
Post-Installation
Starting and Stopping the SAP System
Caution
This step does not apply to the installation of a Java Add-In for an existing ABAP system.
End of: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure (MI);Process
Integration (PI)
21. You check the Java documentation [page 133] for information that is relevant for running your Java system.
22. You may now start with the manual configuration of your IT scenarios for which you find the
appropriate documentation in the SAP Solution Manager [page 135].
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>
12/04/2006
PUBLIC
105/166
5
5.1
Post-Installation
Starting and Stopping the SAP System
Note
The instance name (instance ID) of the central instance is DVEBMGS<Instance_Number>, the
instance name of the central services instance is SCS<Instance_Number>, and the instance name
of a dialog instance is D<Instance_Number>.
Only valid for: HA (UNIX)
Procedure
Starting the SAP system
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
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.
106/166
PUBLIC
12/04/2006
5
5.1
Post-Installation
Starting and Stopping the SAP System
Note
When you use stopsap in a Multiple Components in One Database (MCOD) system with two central
instances, only one central instance and the database are 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 137].
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
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.
12/04/2006
PUBLIC
107/166
5
5.2
Post-Installation
Logging On to the SAP System
User
User Name
Client
SAP*
DDIC
000, 001
ABAP+Java User
User
Administrator
J2EE_ADMIN (default) or the name you gave this user during the
installation process.
Prerequisites
1. Start SAP Logon on the host where you have installed the front end as follows:
n SAP GUI for Windows:
Choose Start Programs SAP Front End SAP Logon .
n SAP GUI for Java:
Choose Start Programs SAP Clients SAP GUI for Java<Release> .
Note
You can also enter the command guilogon in the SAP GUI installation directory to start
SAP GUI for Java.
The SAP Logon appears.
2. Create a logon entry for the newly installed system in the SAP Logon.
For more information about creating new logon entries, press F1 .
3. When you have created the entry, log on as user SAP* or DDIC.
Logging On to the J2EE Engine
You access the J2EE Engine with a URL using a Web browser from your client machines. To log on to
the J2EE engine for the first time, proceed as follows:
1. Establish the default J2EE Engine URL.
2. Log on to the J2EE Engine.
108/166
PUBLIC
12/04/2006
5
5.2
Post-Installation
Logging On to the SAP System
The default URL consists of the installation host name and the port on which the J2EE Engine is
listening. You can use the HTTP or HTTPS protocol; HTTPS is relevant if you are using Secure
Sockets Layer (SSL) communication. To correctly establish the URL, you first have to calculate
the port number as follows:
Protocol
Formula
HTTP
The HTTP port number is based on the number of the J2EE instance on which you
have installed the J2EE Engine, and is calculated according to the following formula:
HTTP Port = 50000 + (100*<instance number>)
Example
If the J2EE Engine is installed on J2EE instance number 01, the port number is:
J2EE Engine HTTP Port = 50000 + (100 * 1) = 50100
HTTPS
Example
The default J2EE Engine URL looks as follows, depending on the protocol that you are using:
<protocol>://<fully qualified j2ee engine host name>:<protocol_port_number>
Example
If you installed the J2EE Engine on host saphost06 and the instance number of your J2EE Engine is 15,
enter the following URL: http://saphost06:51500
Logging on to the J2EE Engine
1. Open your Web browser, enter the J2EE Engine URL as described above and choose Enter.
The start page of the J2EE Engine appears in the Web browser.
2. Log on by choosing EXAMPLES in the upper right corner of the Web page.
3. In the Welcome screen, enter the following information:
n User ID: <J2EE Administrator name>
n Password: <J2EE Administrator password>
12/04/2006
PUBLIC
109/166
5
5.3
Post-Installation
Logging on to the Portal
Note
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. To correctly establish the URL, you first have to calculate the port number
as follows:
Protocol
Formula
HTTP
The HTTP port number is based on the number of the SAP J2EE instance on which
you have installed the portal, and is calculated according to the following formula:
HTTP Port = 50000 + (100*<instance number>)
Example
If the portal is installed on J2EE instance number 01, the port number is:
Portal HTTP Port = 50000 + (100 * 1) = 50100
HTTPS
Example
The default portal URL looks as follows, depending on the protocol that you are using:
<protocol>://<portal host name>:<protocol_port_number>/irj
110/166
PUBLIC
12/04/2006
5
5.4
Post-Installation
Installing the SAP License
Example
If the portal is installed on a computer identified on the network as PORTAL01, and the J2EE instance
number is 16, enter the following address:
<protocol>://Portal01.sap.corp:51600/irj
User names and passwords are registered in a directory server or a user list. When you log on to the
portal for the first time, there is no directory server or user list associated with the portal. To connect
to a user list, you have to create a user management configuration. Until you establish a connection
with a user list, you log on to the portal using a default user. The default user is the J2EE system
administrator. You provided the user name and password for this user during the SAP system installation.
Note
The default user logon provides you with access to the portal as administrator (super user). After
you have logged on, you can work as a portal administrator using your own name and password.
To do so, make sure that you are registered in the directory server or user list to which your
security configuration points and that you are associated with the portal administrative role. After
the first logon, you access the portal with your own name and password.
Procedure
1. Open your Web browser, enter the portal URL as described above and choose Enter.
2. In the Welcome screen, enter the following information:
n User ID: <J2EE Administrator name>
n Password: <J2EE Administrator password>
Once you have logged on to the portal, the installation phase is complete. The portal is now ready
to be configured for your chosen IT scenario.
3. Configure the portal as described in SAP Library at:
https://help.sap.com/nw2004s SAP NetWeaver Library
Technology Consultants Guide Running an
Enterprise Portal <your scenario variant>
Troubleshooting
If the iViews are not displayed correctly, or if the portal does not launch, see Troubleshooting for Usage Type
Enterprise Portal (EP) [page 165].
End of: Enterprise Portal (EP);EP Core (EPC)
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
12/04/2006
PUBLIC
111/166
5
5.5
Post-Installation
Installing the SAP Online Documentation
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 information about the installation procedure for the SAP license, see:
https://help.sap.com/nw2004s SAP NetWeaver SAP NetWeaver Library
Guide Cross-NetWeaver Configurations SAP License Key
Technology Consultant's
More Information
For more information about SAP license keys, see SAP Service Marketplace at
https://service.sap.com/licensekey.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
SAP currently provides an HTML-based solution for the online documentation, including the
Application Help, Glossary, Implementation Guide (IMG), and Release Notes. You can display the
documentation with a Java-compatible Web browser on all front-end platforms supported by SAP.
You can always find the up-to-date SAP online documentation at https://help.sap.com/nw2004s.
Process
Install the SAP online documentation in your SAP system as described in the README.TXT file
contained in the root directory of the online documentation DVD, delivered as part of the installation
package.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
112/166
PUBLIC
12/04/2006
5
5.7
Post-Installation
Performing Initial ABAP Configuration
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 https://service.sap.com/remoteconnection.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
Here you find information about how to perform initial ABAP system configuration.
Procedure
Configuration
Operation Modes
Configuration
Set up administrators
Background Processing
Background Processing
Install a printer
SAP Logon
System log
12/04/2006
PUBLIC
113/166
5
5.7
Post-Installation
Performing Initial ABAP Configuration
Note
SAPinst installs SAP systems with a minimum number of work processes. This is only an
initial configuration to get you started after the installation. It is not detailed enough for a
production system because the optimal number of each type of work process depends on the
system resources and on the number of users working in each SAP system application. For a
detailed configuration contact SAP Technical Consulting.
n Installing languages and performing language transport
l Installing languages using transaction I18N:
u If you want to use English only, you must activate the default language settings once.
u If you want to use languages other than English, you must install them and activate the
language settings.
For more information on configuring the language settings, see the online documentation
in transaction I18N I18N Menue I18N Customizing .
l Performing language transport using transation SMLT:
For more information on performing the language transport using transaction SMLT.
see Solution Life Cycle Management by Key Capability Software Life Cycle Management Software
Logistics Change and Transport System Language Transport. .
Activating
and configuring the integrated Internet Transaction Server (ITS)
n
l For more information on activating and configuring the ITS, which is installed
automatically with the SAP kernel, see Application Platform by Key Capability ABAP Technology
UI Technology ITS / SAP@Web Studio (BC-FES-ITS) .
For
more information about ITS, see SAP Note 742048, where you can find the necessary
l
information if you do not want to use the ITS.
n Maintaining address data
For more information on maintaining the company address in your SAP system using
transaction SU01, see Application Platform by Key Capability Business Services Business Address
Services (BC-SRV-ADR) Addresses in User Administration Maintenance of Address Data .
Note
You must maintain your company address to create ABAP system users.
n Configuring business applications
For more information about how to prepare the SAP system for using business applications,
which includes customizing the ABAP system and the business components, see Solution Life
Cycle Management by Key Capability Customizing .
114/166
PUBLIC
12/04/2006
5
5.8
Post-Installation
Completing and Checking the Oracle Database Installation
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
The following tasks need to be executed to ensure the availability of important database tools and
to complete the Oracle database installation.
Caution
An Oracle SAP database has to be run in archive log mode. Only this mode guarantees recovery after
system failure. The database archive logs are written to the directory /oracle/<DBSID>/oraarch.
If the file system containing the archive directory is full, all database transactions are stopped
(archiver stuck). Use the tool brarchive to save the archives on tape. For more information, see
the documentation SAP Database Administration: Oracle that is part of the Online Documentation.
Checking Database Utilities brbackup and brarchive
Execute the following steps in order to check whether the database utilities brbackup and brarchive
are installed correctly:
1. Log on as UNIX user ora<dbsid>
2. Verify that the database is running.
3. Start an online backup of a single database file (control
file) to disk:
processing
If brarchive or brbackup did not terminate successfully, refer to the documentation SAP Database
Administration: Oracle (supplied on the Online Documentation CD / DVD) to analyze error messages and to
obtain information on how to solve the problems.
Restricting DB Access to Specific Hosts
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.
12/04/2006
PUBLIC
115/166
5
5.9
Post-Installation
Applying the Latest Kernel and Support Packages
Apply parameter settings as described in SAP Note 830576 to improve the performance of the database.
More Information
n For information on Oracle database configuration, see the documentation SAP Database Guide:
Oracle (BC-DB-ORA-DBA) in the SAP Library at https://help.sap.com/nw2004s 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)
n For information on Oracle database administration using Computing Center
Management System (CCMS), see the documentation CCMS: Oracle in the SAP Library at
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability
Application Platform by Key Capability Platform-Wide Services Database Support Oracle CCMS: Oracle
Before you apply support packages, make sure that you have read the release notes for SAP
NetWeaver, available on SAP Service Marketplace at https://service.sap.com/releasenotes.
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 61].
Caution
You must have applied all ABAP Support Packages, before you run CTC online configuration.
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 2004s. 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 it, see https://help.sap.com/nw2004s 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
116/166
PUBLIC
12/04/2006
5
Post-Installation
5.10 Performing the Client Copy
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 https://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
For up-to-date release information on Support Package Stacks, see the documentation SAP
NetWeaver 2004s Support Package Stack Guide <current version> on SAP Service Marketplace at
https://service.sap.com/MaintenanceNW2004s.
b) Alternatively, you can download Support Packages from SAP Service Marketplace at:
https://service.sap.com/patches
c) Apply the ABAP Support Packages to your SAP system with the help of the Support Package
Manager (formerly called SAP Patch Manager, transaction SPAM).
d) 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:
https://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:
https://service.sap.com/noteassistant
PUBLIC
117/166
5
Post-Installation
5.11 Performing a Full Installation Backup
Caution
For client copy considerations for usage type Process Integration (PI), see SAP Note 940309.
End of: Process Integration (PI)
Procedure
Make sure that you fully back up your database so that you can recover it later if necessary.
118/166
PUBLIC
12/04/2006
5
Post-Installation
5.11 Performing a Full Installation Backup
n If required, you have completed client maintenance, such as the client copy [page 117].
n You have logged on [page 108] as user <sapsid>adm and stopped the SAP system and database [page 105].
n This procedure works on all hardware platforms. For more information on operating
system-specific backup procedures, see your operating system documentation.
Backing Up the Installation
Check for modifications in the existing parameter files before you overwrite them when restoring
the backup.
1. Log on as user root.
2. Restore the data that you previously backed up:
n Restoring the data from tape:
cat <tape_device> | compress cd | tar xf
12/04/2006
PUBLIC
119/166
5
Post-Installation
5.12 Post-Installation Steps for Adobe Document Services
1.
2.
3.
4.
5.
1.
2.
3.
4.
5.
6.
120/166
PUBLIC
12/04/2006
5
Post-Installation
5.12 Post-Installation Steps for Adobe Document Services
Note
This procedure contains only minimal configuration steps to check if the ADS installation with
SAPinst was successful.
For detailed configuration documentation, see the configuration guide for Adobe Document
Services:
n On SAP Service Marketplace at:
SAP Interactive Forms by Adobe Media Library Documentation
Adobe Document Services - Configuration Guide NW 2004s
n In the SAP Library at:
https://help.sap.com/nw2004s SAP NetWeaver Library
Technology Consultant's Guide
Cross-NetWeaver Configurations Adobe Document Services - Configuration .
https://service.sap.com/adobe
Note
stream:
If the setup is not correct, the page does not change and Submit remains on the screen.
Checking the ABAP Connection
1.
2.
3.
4.
12/04/2006
PUBLIC
121/166
5
Post-Installation
5.13 Performing Post-Installation Steps for Composite Application Framework Core (CAF Core)
Troubleshooting
If the tests are not successful, you might have to make some adjustments to the initial technical
configuration for ADS [page 146].
BI-MMR
CAF-KM
EPBC2
SAP_JTECHS
BI_UDI
CAF-UM
EP-PSERV
SAP_PRT
BI-REPPLAN
EC-JSTARTUP
KMC-CM
SAP-EU
BI-WDALV
EP_BUILDT
LM-TOOLS
SAP-JEE
CAF
EPBC
SAP_BUILDT
UWLJWF
Note
Only create SCs if they are missing from the project. These will be used when importing into
Change Management Service (CMS).
4. Define the build plug-in dependencies created in step 3 above.
5. Define the SC dependencies created in step 2 above.
Note
When importing SLD content downloaded from SAP Service Marketplace into your NWDI
landscape, you also import necessary dependencies. There you can skip step 5.
The SLD content can be downloaded from the SMP at: https://service.sap.com/patches
Entry by Application Group Support Packages and Patches Additional Components SAP Master Data for
SLD SAP Master Data for SLD 2.0 .
122/166
PUBLIC
12/04/2006
5
Post-Installation
5.13 Performing Post-Installation Steps for Composite Application Framework Core (CAF Core)
In CMS
Note
For all documents referenced in this section, see the administration chapter of the SAP NetWeaver Java
Development Infrastructure. You can find this documentation at https://help.sap.com/nw2004s
SAP NetWeaver Library Administrator's Guide Technical Operations Manual for SAP NetWeaver Administration
of SAP NetWeaver Systems Development Infrastructure .
1. In CMS, identify or create a domain.
See Change Management Service Configuring Domains .
2. Identify an existing track or create a new track for composite application development in
Landscape Configurator Creating a Development Track .
3. Add the SC created in step 2 in the section above to the track.
4. Add the runtime system of the track.
See Landscape Configurator Creating a Development Track Configuring Runtime Systems .
5. Check in the archives listed in the table below.
Archive Names
BI-MMR
CAF-KM
EPBC2
SAP_JTECHS
BI_UDI
CAF-UM
EP-PSERV
SAP_PRT
BI-REPPLAN
EC-JSTARTUP
KMC-CM
SAP-EU
BI-WDALV
EP_BUILDT
LM-TOOLS
SAP-JEE
CAF
EPBC
SAP_BUILDT
UWLJWF
The Composite Application Framework (CAF) Core Configuration Guide contains additional details
about setting up your CAF environment. You can find it at: https://help.sap.com/nw2004s SAP
NetWeaver Library Technology Consultant's Guide Developing, Configuring and Adapting Applications Creating
Composite Applications Composite Application Framework Core Configuration Guide
12/04/2006
PUBLIC
123/166
5
Post-Installation
5.14 Configuring Access to Knowledge Warehouse Content from the SAP Internet Knowledge Servlet
You have completed the installation of AS ABAP and AS Java as described in this documentation.
Procedure
1. Create a user of type system in your ABAP system using transaction SU01 and assign this user to
the role SAP_KM_KW_RFC_CPIC_USER.
This user is needed for the connection between the SAP IKS and the ABAP system.
2. Make sure that the Administrator user of the J2EE Engine has the required authorizations to
perform the configuration:
a) Log on to the User Management Engine (UME) using the URL
http://<J2EE_host>:<J2EE_port>/useradmin/index.jsp.
b) Assign either the role SAP_J2EE_ADMIN or KW_ADMINISTRATOR to the Administrator user.
c) If none of these roles exists, you need to create one of them. You do not need to perform
further configuration of the newly created role.
d) Log off from the UME.
3. Open a browser window and enter the following URL:
http://<J2EE_host>:<J2EE_port>/SAPIKS2
124/166
PUBLIC
12/04/2006
5
Post-Installation
5.16 Post-Installation Steps for Usage Type Process Integration (PI)
Only valid for: BI Java Components (BI-Java);Process Integration (PI)
Since CR_Content.zip contains all available SAP components, the content of this file grows with time.
The extensions contain information about new components (new releases and Support Packages, for
example). This content in the SLD has to be updated from time to time.
You can download the most up-to-date files from the SAP Service Marketplace.
For more information, see SAP Note 669669.
More Information
For more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAP
NetWeaver 2004s at https://service.sap.com/sld Media Library .
End of: Process Integration (PI)
Only valid for: Enterprise Portal (EP)
12/04/2006
PUBLIC
125/166
5
Post-Installation
5.18 High Availability: Post-Installation Steps
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
If your high-availability (HA) installation is running a two-node switchover cluster, you need to
order two SAP licenses [page 111]. When we receive confirmation from your vendor that you are
implementing a switchover environment, we provide two 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 (SCS) instance runs. There
is no license problem when only the database is switched over.
A switchover involving the central services (SCS) instance affects the licensing mechanism, so for
this case you must have two licenses, which you can install in parallel. There is no license problem
when only the database is switched over.
Procedure
1. Execute the following as user <sid>adm on the primary and secondary node where the ABAP SCS
instance runs for every license key you obtain from SAP:
saplicense -install
126/166
PUBLIC
12/04/2006
5
Post-Installation
5.19 Ensuring User Security
7. Open the Visual Administrator on the node where the SCS instance is running and choose CI
Host License Adapter and import the file containing the two licenses.
Result
The license is no longer a problem during switchover. This means you do not need to call saplicense
in your switchover scripts.
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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
12/04/2006
PUBLIC
127/166
5
Post-Installation
5.19 Ensuring User Security
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.
For more information, see:
https://help.sap.com/nw2004s SAP NetWeaver Library SAP 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 https://service.sap.com/securityguide:
Operating System and Database Users
User
User Name
Comment
<sapsid>adm
ora<dbsid>
SAP<SCHEMA_ID>
SYSTEM
SYS
OUTLN
DBSNMP
128/166
PUBLIC
12/04/2006
5
Post-Installation
5.19 Ensuring User Security
ABAP+Java Users
User
User Name
Comment
SAP*
DDIC
EARLYWATCH
SAPCPIC
Administrator
Guest
ADSUSER
ADS_AGENT
12/04/2006
PUBLIC
129/166
5
Post-Installation
5.20 Running the Template Installer
Java Add-In Users for Users Stored in the ABAP System
User
Comment
Administrator
Guest
ADSUSER
ADS_AGENT
Only valid for: Application Server (AS);BI Java Components (BI-Java);Development Infrastructure (DI);Mobile Infrastructure
(MI);Process Integration (PI)
130/166
PUBLIC
12/04/2006
5
Post-Installation
5.20 Running the Template Installer
Note
You can run the Template Installer only once and only directly after the installation.
You cannot use the configuration template after:
n Upgrade
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.
For more information , see Accessing Configuration Documentation in the SAP Solution Manager [page 135].
You can also find configuration documentation in the Technology Consultant's Guide in the
SAP Library at:
https://help.sap.com/nw2004s SAP NetWeaver Technology Consultant's Guide
For more information about how to start the Template Installer, see the SAP Library at:
https://help.sap.com/nw2004s SAP NetWeaver Library Technology Consultant's Guide Developing,
Configuring, and Adapting Applications Creating Java Applications Using Web Dynpro J2EE Engine Configuration
Template Installer
Note
For more information on the Template Installer and its limitations, see SAP Note 923359.
Only valid for: Application Server (AS)
After SAPinst has finished, you need to run the following configuration templates using the Template
Installer to automatically configure the SAP NetWeaver Administrator (NWA):
1.
2.
3.
4.
5.
6.
7.
12/04/2006
PUBLIC
131/166
5
Post-Installation
5.20 Running the Template Installer
Note
After SAPinst has finished and you have performed the necessary post-installation steps for usage
type PI, you need to run the configuration template PIPostInstallProcess using the Template
Installer. To select the template, change the scenario on the right of the page to PI.
Caution
If you are using a central SLD, you also have to perform the steps for SLD configuration manually
as described in SAP Note 939592.
Note
After the Template Installer has finished, you need to restart your SAP system.
End of: Process Integration (PI)
Only valid for: BI Java Components (BI-Java)
After SAPinst has finished, you need to run the configuration template BIPostInstallProcess
using the Template Installer.
End of: BI Java Components (BI-Java)
Only valid for: Development Infrastructure (DI)
After SAPinst has finished, you need to run the configuration template for usage typeDI using the
Template Installer.
1. Under Scenario choose DI.
2. Decide whether you want to install and run the entire NWDI on this system or configure the
services individually:
Recommendation
We recommend that use the first option shown below, to install and run the entire NWDI on
this system.
132/166
PUBLIC
12/04/2006
5
Post-Installation
5.21 Checking the SAP Java Documentation
n To install and run the entire NWDI on this system, perform the following steps:
a) Choose the Scenario DI
b) Choose All-in-one Complete Configuration of DTR, CBS, and CMS
c) Fill the open fields in the section Data Entry according to their label.
d) To run the template choose Execute Template.
n To configure the services individually (DTR, CBS, CMS) for example, because you have
distributed the usage type DI to different servers perform the following steps:
a) Choose the Scenario DI
b) Choose the service you want to configure, Design Time Repository, Component Build Service, or
Change Management Service.
c) Fill the open fields in the section Data Entry according to their label.
d) To run the template, choose Execute Template.
e) Choose the items that you need from Design Time Repository Configuration, Component Build Service,
and Change Management Service.
Note
Before performing any database settings make sure that you have read SAP Note 889038.
3. If you are using a new Oracle database installation, perform the step Set Oracle Parameters for DI.
Caution
Do not use this for an already configured database because it overwrites previous settings.
4. After the Template Installer has finished, you might have to restart the engine as described
in SAP Note 919942.
End of: Development Infrastructure (DI)
Only valid for: Mobile Infrastructure (MI)
After SAPinst has finished, you need to run the configuration template MI
Process using the Template Installer.
Post Installation
12/04/2006
PUBLIC
133/166
5
Post-Installation
5.21 Checking the SAP Java Documentation
Procedure
Contents
Architecture 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
134/166
PUBLIC
12/04/2006
5
Post-Installation
5.22 Accessing Configuration Documentation in the SAP Solution Manager
Manual
Contents
Migration Manual
More Information
For troubleshooting the J2EE Engine, see the J2EE Engine Problem Analysis Guide at:
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability
Solution Life Cycle Management by Key Capability SAP NetWeaver Problem Analysis Guide (PAG) J2EE Engine
Problem Analysis Scenarios
For SAP NetWeaver 2004s usage types you can also find configuration documentation in the
Technology Consultant's Guide at: https://help.sap.com/nw2004s SAP NetWeaver Library Technology
Consultant's Guide
Prerequisites
n You have installed an SAP Solution Manager system as described in the documentation Installation
Guide SAP Solution Manager <3.2 or 4.0> on <OS>: <Database>.
n You have connected your SAP system to the SAP Solution Manager as described in the
documentation Configuration Guide SAP Solution Manager <3.2 or 4.0>.
For more information, see SAP Service Marketplace at https://service.sap.com/instguides
SAP Components SAP Solution Manager Release <3.2 or 4.0> .
Procedure
12/04/2006
PUBLIC
135/166
5
Post-Installation
5.22 Accessing Configuration Documentation in the SAP Solution Manager
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:
https://help.sap.com/nw2004s SAP NetWeaver Library SAP 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 2004s .
Result
You can now configure your SAP system according to the configuration documentation in the
SAP Solution Manager.
136/166
PUBLIC
12/04/2006
Additional Information
6 Additional Information
The following sections provide additional information about optional preparation and
post-installation tasks:
Preparation
n If you decided to use a generic LDAP directory, you have to create a user for LDAP directory access
[page 145].
n Configuring User Management to Use an LDAP Directory [page 145].
n Usage Type-Specific Initial Technical Configuration [page 145]
n Heterogeneous SAP System Installation [page 153]
n Deleting an SAP System [page 154]
n Troubleshooting [page 164]
This section does not apply to the installation of a Java Add-In to an existing ABAP system.
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.
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.
12/04/2006
PUBLIC
137/166
6
6.1
Additional Information
Installation of Multiple Components in One Database (Optional)
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 on MCOD and its availability on different platforms, see the SAP Service
Marketplace at https://service.sap.com/mcod.
n MCOD is released 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. The same applies to 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 on the SAP
Quick Sizer, see the SAP Service Marketplace at https://service.sap.com/sizing.
Features
Special MCOD considerations and differences from the standard procedure are listed where relevant
in the installation documentation.
Constraints
Recommendation
PUBLIC
12/04/2006
6
6.2
Additional Information
Integration of LDAP Directory Services (Optional)
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 https://service.sap.com/remoteconnection.
n When you use stopsap in an MCOD system with two central instances, only one central instance
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 first SAP system, the database system ID can be different from the SAP system ID.
n For the second SAP system, make sure that you use the same DBSID as for the first SAP system.
n If you install a system into an existing database (MCOD), make sure that the SYSTEM tablespace
contains at least 350 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 database logging during the database load phase of the installation, you
need to plan downtime for all MCOD systems sharing the database.
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.
12/04/2006
PUBLIC
139/166
6
6.2
Additional Information
Integration of LDAP Directory Services (Optional)
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 Microsoft Management Console (MMC)
For more information on the automatic registration of SAP components in LDAP directories and
the benefits of using it in SAP Logon and MMC, see the documentation SAP System Information in
Directory Services on SAP Service Marketplace at https://service.sap.com/msplatforms Microsoft
Windows Server
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=
140/166
PUBLIC
12/04/2006
6
6.2
Additional Information
Integration of LDAP Directory Services (Optional)
MMC
The MMC 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 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 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 MMC.
If you need to administer distributed systems, we especially recommend that you use the MMC
together with Active Directory services. For example, you can simplify administration by using the
MMC in a distributed environment that implements the mySAP Business Suite components. You can
keep track of significant events in all of the systems from a single MMC interface. You do not need
to manually register changes in the system configuration. Instead, such changes are automatically
updated in the directory and subsequently reflected in the MMC.
Configuration Tasks for Active Directory
To enable an SAP system to make use of the features offered by the Active Directory, you must
configure the Active Directory so that it can store SAP data.
This involves extending the schema for the SAP data types, creating a root container for the storage
of SAP-specific information, and defining accounts that allow directory access. You perform all these
tasks using SAPinst with the option Active Directory Configuration.
For more information, see section Setting Up the Active Directory Services (Optional) in the Windows
installation guide for your SAP system solution and database.
Configuration Tasks for Generic LDAP Directories
To prepare the SAP system to use generic LDAP services, you must perform the following steps:
1. You configure the LDAP directory to store SAP data.
This involves extending the directory schema and creating a container for the SAP data.
2. You set up a user with a password on the server where the SAP system is running to permit the
system to access and modify the LDAP directory.
You do this by running the script ldappasswd.
For more information on how to enable interaction between a generic LDAP directory and the SAP
system, see the documentation SAP System Information in Directory Services in the SAP Service Marketplace
at: https://service.sap.com/msplatforms Microsoft Windows Server
12/04/2006
PUBLIC
141/166
6
6.3
Additional Information
Preparing User Management for an External ABAP System
Advantages
Disadvantages
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
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, see:
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability
Security Identity Management User Management Engine
142/166
PUBLIC
12/04/2006
6
6.3
Additional Information
Preparing User Management for an External ABAP System
Note
For more information about role maintenance, see the SAP Library at
https://help.sap.com/nw2004s SAP NetWeaver Library SAP NetWeaver by Key Capability
Security Identity Management Users and Roles (BC-SEC-USR) SAP Authorization Concept Organizing
Authorization Administration Organization if You Are Using the Profile Generator Role Maintenance Role
Maintenance Functions Changing Standard Roles
Administration of the ABAP system
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.
Caution
Log on to the SAP system once with this user to change its initial password. Because 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.
12/04/2006
PUBLIC
143/166
6
6.3
Additional Information
Preparing User Management for an External ABAP System
Recommendation
We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use any
password.
As 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 127] 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
For more information on SLD users and security roles, see the Post-Installation Guide - SLD of SAP
NetWeaver 2004s at https://service.sap.com/sld Media Library .
Activities for the Java System
144/166
PUBLIC
12/04/2006
6
6.4
Additional Information
Creating a User for LDAP Directory Access (Optional)
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.
During the SAP instance installation you chose to configure the SAP system to integrate LDAP services.
Procedure
PUBLIC
145/166
6
6.6
Additional Information
Usage Type-Specific Initial Technical Configuration
finished, depending on your installation scenario. The following usage type-specific sections provide
the required information:
n Application Server Java (AS Java) [page 146]
Only valid for: Enterprise Portal (EP);EP Core (EPC)
Depending on your installation scenario, you might have to perform one ore more of the following
steps:
146/166
PUBLIC
12/04/2006
6
6.6
n
n
n
n
n
Additional Information
Usage Type-Specific Initial Technical Configuration
You can find a detailed description of the manual procedure for these steps in section Configuring the
Web Service in the Adobe Document Services Configuration Guide, which you can find:
n On SAP Service Marketplace at:
SAP Interactive Forms by Adobe Media Library Documentation
Adobe Document Services - Configuration Guide NW 2004s
n In the SAP Library at:
https://help.sap.com/nw2004s SAP NetWeaver Library
Technology Consultant's Guide
Cross-NetWeaver Configurations Adobe Document Services - Configuration .
https://service.sap.com/adobe
12/04/2006
PUBLIC
147/166
6
6.6
Additional Information
Usage Type-Specific Initial Technical Configuration
n As an SLD client
For more information, see:
Configuration of Data Suppliers in the documentation Post Installation Guide System Landscape Directory SAP
NetWeaver 2004s on SAP Service Marketplace at https://service.sap.com/installNW2004s
Configuration .
Only valid for: Enterprise Portal (EP);EP Core (EPC)
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
/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/
servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl
148/166
PUBLIC
12/04/2006
6
6.6
Additional Information
Usage Type-Specific Initial Technical Configuration
Renaming initialPermissionsKMC.xml.template
1. Go to directory
/usr/sap/<sapsid>/<instance_name>/j2ee/cluster/server<x>/apps/sap.com/irj/
servlet_jsp/irj/root/WEB-INF/portal/system/xml/acl
If SAPinst has finished successfully, the exchange_profile.xml file does not exist on your system.
In this case, you can skip this step.
Procedure
12/04/2006
PUBLIC
149/166
6
6.6
3.
4.
5.
6.
7.
Additional Information
Usage Type-Specific Initial Technical Configuration
Password: <pisuper_password>
The Exchange Profile page appears
Choose Connection.
The Server Settings page appears.
Enter the required information for the PI host.
Use the logon information of user PILDUSER.
Choose Save.
The Exchange Profile page appears.
Choose Import.
The Import Profile page appears.
Choose Browse and select the following file:
/usr/sap/<SAPSID>/SYS/global/exchange_profile.xml
Caution
If you cannot run a Web Browser on your PI host, you need to copy the file exchange_profile.xml
from the PI host to a host were a Web browser runs.
8. Choose Import Data.
The profile will be imported.
Caution
Log on to your SAP NetWeaver AS ABAP host as user with SAP_ALL rights (use DDIC or SAP*).
Call transaction SU01.
Select user PISUPER.
Navigate to the Profiles tab and switch to edit mode.
In the row Profile, add SAP_ALL.
Save your settings.
150/166
PUBLIC
12/04/2006
6
6.6
Additional Information
Usage Type-Specific Initial Technical Configuration
Procedure
To activate the ICF services, call transaction SE38 and execute the report
RSXMB_ACTIVATE_ICF_SERVICES. For more information, see SAP Note 736312.
1.
2.
3.
4.
5.
6.
PUBLIC
151/166
6
6.6
n
n
n
n
Additional Information
Usage Type-Specific Initial Technical Configuration
For the installation of SAP NetWeaver 2004s BI Content Add-On 2 or higher on the AS ABAP
system, see SAP Note 847019.
152/166
PUBLIC
12/04/2006
6
6.7
Additional Information
Heterogeneous SAP System Installation
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
This section does not apply to installations of SAP instances in a mixed UNIX and Microsoft
Windows environment.
If you want to install an application server on Windows in a heterogeneous (UNIX) SAP system
environment, you need to follow the instructions in SAP Note 680617.
Procedure
Install the central instance and the database as described in the installation documentation.
Log on as user root on the dialog instance host.
Create <sapmnt>/<SAPSID>/exe as a local directory on the dialog instance.
On the central instance host, export the directories <sapmnt>/<SAPSID>/global and
<sapmnt>/<SAPSID>/profile via NFS and mount them on each dialog instance host as described
in Preparing and Mounting the Installation Media [page 74].
5. Mount the CD or DVD drive using NFS and insert the CD / DVD with the SAP executables on the
dialog instance host.
6. Install the dialog instance.
12/04/2006
PUBLIC
153/166
6
6.8
Additional Information
Deleting an SAP System
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 154]. However, you still have to delete the database
manually.
n You delete the SAP system manually [page 157].
154/166
PUBLIC
12/04/2006
6
6.8
Additional Information
Deleting an SAP System
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 157] or run SAPinst on the NFS server.
Uninstall
Note
With this SAPinst service 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.
Make sure that you delete the SAP instances in the correct order, as described in Deleting an SAP
System Using SAPinst [page 154].
12/04/2006
PUBLIC
155/166
6
6.8
Additional Information
Deleting 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.
3. Delete the database software manually [page 156].
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.
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 162].
Procedure
cd /oracle/stage/102_64/database/SAP
./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_32 or <DBSID>_102_64.
Mark the Oracle 10G database within the selected product.
Choose Remove.
Confirm your selection with Yes.
Choose EXIT.
156/166
PUBLIC
12/04/2006
6
6.8
Additional Information
Deleting an SAP System
1. You delete the SAP instances [page 157] 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 158].
3. You delete the Oracle database instance [page 162].
Note
The Java database schema is automatically deleted together with the database instance.
Deleting the Java Part of an SAP System
1.
2.
3.
4.
You delete the Java parts of all dialog instances [page 159], if there are any.
You delete the Java part of an SAP system [page 159].
You delete the central services instance [page 157].
You delete the Java database schema of your Oracle installation [page 161].
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
12/04/2006
PUBLIC
157/166
6
6.8
Additional Information
Deleting an SAP System
Example
6. Change to the directory /usr/sap, edit the file sapservices and delete the line that refers to
the instance to be deleted.
If you are not deleting the entire SAP system (on all hosts), make sure that you do not delete files or
directories that are used by other SAP instances by means of NFS mounts.
Prerequisites
You must have deleted your SAP instance(s) as described in Deleting an SAP Instance [page 157].
Procedure
158/166
PUBLIC
12/04/2006
6
6.8
Additional Information
Deleting an SAP System
3. Delete the local user <sapsid>adm, its home directory, and all subdirectories of the home directory.
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
If you delete a Java part, the ABAP part of the SAP system is not deleted.
12/04/2006
PUBLIC
159/166
6
6.8
Additional Information
Deleting an SAP System
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>
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 =
rdisp/j2ee_start_control =
160/166
PUBLIC
12/04/2006
6
6.8
Additional Information
Deleting an SAP System
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 =
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.
1. Log on as user ora<dbsid>.
2. Start sqlplus and connect to the database. Enter:
sqlplus /nolog
SQLPLUS>connect / as sysdba
12/04/2006
PUBLIC
161/166
6
6.8
Additional Information
Deleting an SAP System
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
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
PUBLIC
12/04/2006
6
6.8
Additional Information
Deleting an SAP System
cd /oracle/stage/102_32/database/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.
b) Choose Installed Products or Deinstall Products.
c) Select the database schema you want to uninstall, <DBSID>_102_32 or <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.
6. Log on as user root.
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
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 sub-directories
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:
n 32-bit Oracle 10G: rm -rf /oracle/stage/102_32
n 64-bit Oracle 10G: 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:
12/04/2006
PUBLIC
163/166
6
6.9
Additional Information
Troubleshooting
-rf /oracle/client/102_32
-rf /oracle/client/102_64
6.9 Troubleshooting
The following section(s) describe the steps that you need to perform manually if SAPinst fails:
n Troubleshooting with SAPinst [page 164]
Only valid for: Enterprise Portal (EP);EP Core (EPC)
<SCA name>:
<SCA name> :
system
164/166
PUBLIC
12/04/2006
6
6.9
Additional Information
Troubleshooting
/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcd
/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/pcdContent
/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/cluster/server0/
apps/sap.com/irj/servlet_jsp/irj/root/WEB-INF/deployment/
pcdContent/no_overwrite
12/04/2006
PUBLIC
165/166
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