InstallationGuide SAPNetWeaverCompositionEnvironment7 ... · InstallationGuide SAPNetWeaverCompositionEnvironment7.1SR5oni5/OS: IBMDB2fori5/OS ProductionEdition TargetAudience nSystemAdministrators

Installation GuideSAP NetWeaver Composition Environment 7.1 SR5 on i5/OS:IBM DB2 for i5/OSProduction Edition

Target Audience

n System Administratorsn Technical Consultants

PUBLICDocument version: 1.2 ‒ 12/08/2008

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version at http://www.sdn.sap.com/irj/sdn/nw-ce.

The following table provides an overview of the most important document changes.

Version Date Description

1.2 12/8/2008 Added a new SAP Note in section SAP Notes for the Installation

1.1 5/16/2008 Initial Version

2/146 PUBLIC 12/08/2008

http://www.sdn.sap.com/irj/sdn/nw-ce

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 71.1 How to Use This Guide . . . . . . . . . . . . . . . . . . . . 71.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . 81.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . 121.4 Online Information from SAP . . . . . . . . . . . . . . . . . . 131.5 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . 141.6 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 172.1 Installation Options Covered by this Guide . . . . . . . . . . . . . 172.1.1 Standard System . . . . . . . . . . . . . . . . . . . . . . . 182.1.2 Distributed System . . . . . . . . . . . . . . . . . . . . . . 182.1.3 High-Availability System . . . . . . . . . . . . . . . . . . . . 192.1.4 Additional Application Server Instance . . . . . . . . . . . . . . 202.1.5 Standalone Host Agent . . . . . . . . . . . . . . . . . . . . 232.2 SAP System Transport Host . . . . . . . . . . . . . . . . . . . 242.3 Running Adobe Document Services on Nonsupported Platforms . . . . . 252.4 Integration of LDAP Directory Services . . . . . . . . . . . . . . 262.5 Multiple SAP Systems on a Single System i . . . . . . . . . . . . . 292.6 Planning the Switchover Cluster . . . . . . . . . . . . . . . . . 31

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 353.1 Basic SAP System Parameters . . . . . . . . . . . . . . . . . . 373.2 Hardware and Software Requirements . . . . . . . . . . . . . . . 433.2.1 Running the Prerequisite Checker in Standalone Mode (Optional) . . . . 453.2.2 Hardware and Software Requirements on System i . . . . . . . . . . 463.2.3 Requirements for a Standard System . . . . . . . . . . . . . . . 483.2.4 Requirements for a Distributed System . . . . . . . . . . . . . . 483.2.4.1 Requirements for a Central Services Instance . . . . . . . . . . . . 493.2.4.2 Requirements for the Database Instance . . . . . . . . . . . . . . 493.2.4.3 Requirements for the Primary Application Server Instance . . . . . . . 503.2.5 Requirements for a High Availability System . . . . . . . . . . . . 503.2.5.1 Requirements for a Central Services Instance . . . . . . . . . . . . 503.2.5.2 Requirements for an Enqueue Replication Server Instance . . . . . . . 513.2.5.3 Requirements for the Database Instance . . . . . . . . . . . . . . 52

12/08/2008 PUBLIC 3/146

3.2.5.4 Requirements for the Primary Application Server Instance . . . . . . . 523.2.6 Requirements for an Additional Application Server Instance . . . . . . 533.2.7 Requirements for a Standalone Host Agent . . . . . . . . . . . . . 543.3 Specifying Virtual Host Name(s) . . . . . . . . . . . . . . . . . 903.4 Performing Switchover Preparations for High Availability . . . . . . . . 543.5 Preparing User Management for an External ABAP System . . . . . . . 553.6 Setting Up File Systems . . . . . . . . . . . . . . . . . . . . 583.6.1 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . 583.6.2 Host Agent Directories . . . . . . . . . . . . . . . . . . . . 623.7 Installing the Toolbox JDBC Driver . . . . . . . . . . . . . . . . 623.8 Qp2Term, Qp2Shell and the i5/OS Portable Application Solution Environment 643.9 Installing the Qshell . . . . . . . . . . . . . . . . . . . . . 643.10 Checking and Adjusting i5/OS System Values . . . . . . . . . . . . 653.11 Adjusting Startup Program QSTRUP . . . . . . . . . . . . . . . 693.12 Distribution of Libraries on ASPs . . . . . . . . . . . . . . . . . 723.13 Adding a User ASP . . . . . . . . . . . . . . . . . . . . . . 733.14 Configuring TCP/IP . . . . . . . . . . . . . . . . . . . . . 743.15 Adjusting the Relational Database Name . . . . . . . . . . . . . . 793.16 Installing English as a Secondary Language . . . . . . . . . . . . . 793.17 Preparing a System i User Profile . . . . . . . . . . . . . . . . . 803.18 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 813.19 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 813.20 Copying the DVDs Manually Using the ROOTBIN Share . . . . . . . . 84

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . 874.1 Linking Global Directories . . . . . . . . . . . . . . . . . . . 904.2 Specifying Virtual Host Name(s) . . . . . . . . . . . . . . . . . 904.3 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . 904.4 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 1234.5 Performing a Remote Installation with SAPinst . . . . . . . . . . . 974.6 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . 994.7 SAPinst Installation Options . . . . . . . . . . . . . . . . . . 1004.8 Installing Additional Components (Optional) . . . . . . . . . . . . 1034.9 Installing SAP Memory Analyzer (Optional) . . . . . . . . . . . . 105

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . 1075.1 Logging On to the Application Server . . . . . . . . . . . . . . . 1085.2 Ensuring User Security . . . . . . . . . . . . . . . . . . . . 1095.3 Installing the SAP License . . . . . . . . . . . . . . . . . . . 1115.4 Configuring the Transport Management System . . . . . . . . . . . 1115.5 Configuring the Remote Connection to SAP Support . . . . . . . . . 1125.6 Granting Authorizations for Operating System Collector Programs . . . . 112

4/146 PUBLIC 12/08/2008

5.7 Setting Up the Transport Directory . . . . . . . . . . . . . . . . 1125.8 Applying the Latest Kernel and Support Packages . . . . . . . . . . . 1135.9 Performing a Full Backup . . . . . . . . . . . . . . . . . . . 1135.10 High Availability: Setting Up Licenses . . . . . . . . . . . . . . . 1145.11 Post-Installation Steps for the Host Agent . . . . . . . . . . . . . 1155.12 Checking the SAP Java Documentation . . . . . . . . . . . . . . 1165.13 CE-Specific Post-Installation Activities . . . . . . . . . . . . . . . 1175.14 Post-Installation Steps for the Diagnostics Agent . . . . . . . . . . . 120

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . 1216.1 Transporting Self-Developed Software Component Archives (SCA) into the

System . . . . . . . . . . . . . . . . . . . . . . . . . . 1216.2 Configuration Templates . . . . . . . . . . . . . . . . . . . 1226.3 Uninstalling SAP NetWeaver Composition Environment . . . . . . . . 1236.4 Additional Information About SAPinst . . . . . . . . . . . . . . 1236.4.1 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 1236.4.2 Entries in the Services File Created by SAPinst . . . . . . . . . . . . 1256.4.3 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 1256.5 Starting and Stopping SAP System Instances . . . . . . . . . . . . 1266.5.1 Starting and Stopping the SAP System Using the SAP Management Console . 1266.5.2 Starting and Stopping the SAP System Using Commands . . . . . . . . 1306.5.3 Starting and Stopping the Diagnostics Agent . . . . . . . . . . . . 1316.6 High Availability: Finalizing the Enqueue Replication Server . . . . . . 1326.7 System i Library Structure . . . . . . . . . . . . . . . . . . . 1336.8 System i Integrated File System . . . . . . . . . . . . . . . . . 1346.9 Restoring a Backup . . . . . . . . . . . . . . . . . . . . . . 1356.10 Editing Stream Files . . . . . . . . . . . . . . . . . . . . . 1366.11 Deleting an SAP System . . . . . . . . . . . . . . . . . . . . 1376.12 Deleting an SAP Instance on System i . . . . . . . . . . . . . . . 1386.13 Deleting an SAP System on System i . . . . . . . . . . . . . . . 1396.14 Deleting the Java Part of an SAP System . . . . . . . . . . . . . . 140

12/08/2008 PUBLIC 5/146

6/146 PUBLIC 12/08/2008

1 Introduction

1 Introduction

This document explains how to install an SAP NetWeaver Composition Environment system asproductive edition.For more information about SAP NetWeaver Composition Environment, seehttp://sdn.sap.com/irj/sdn/nw-ce.

Constraints

You need to consider the following constraints before you start your installation:

n Youmust only use the SAP installation tools according to the instructions and for the purposesdescribed in the SAP installation document. Improper use of the SAP installation tools can damagefiles and systems already installed.

n SAP system installations should only be performed by SAP Technical Consultants certified foryour 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 regularlyrelease the newest database (DB) and operating-system (OS) versions of SAP products. Thesereleases are downward-compatible with earlier SAP system releases.Note that for already shipped SAP components, we only support the installation for databaseversions proposed by the installation tool. Therefore, you must install an SAP component orperform a system copy using a downward-compatible database as follows:l Install the component with the old proposed database version.l Upgrade the old database version to the downward-compatible new version.

1.1 How to Use This Guide

At the beginning of each installation phase ‒ planning, preparation, installation, and post-installation‒ you can find a list of the steps that you have to perform in that phase, as well as additionalinformation. Detailed information about the steps for each phase is available in the relevant chapter.When you plan the installation, you have to decide what exactly you want to install, because the stepswithin each phase vary according to the installation option you choose.The following installation options are described in this document:

n Standard system (formerly known as central system)n Distributed systemn High-availability system

12/08/2008 PUBLIC 7/146

http://sdn.sap.com/irj/sdn/nw-ce

1 Introduction1.2 New Features

n One or more additional application server instance(s) for an existing standard, distributed, orhigh-availability system

n Standalone host agent

1.2 New Features

Here you can find the new features in this release.

Note

Many installation concepts have changed, so make sure that you read the installation guide carefully.

Caution

Make sure that you read the release notes for your SAP system. You can find these athttp://service.sap.com/releasenotes.

SAP System Installation

Area Description

SAPinst SAPinst has the following new features:n The technical terms used for the instances of an SAP system have changed as follows:l “Central instance” (CI) is now called “primary application server instance”.l “Dialog instance” (DI) is now called “additional application server instance”.

NoteThe technical terms “Database instance”, “Java central services instance” (SCS), and“ABAP central services instance” (ASCS) remain unchanged.

n “Central system” ‒ meaning an SAP system running on one single host ‒ is nowcalled “standard system”.

n Host agentThe host agent contains all of the required elements for centrally monitoringany host with the Alert Monitor or the SAP NetWeaver Administrator. It isautomatically installed during the installation of all SAP NetWeaver components,except TREX.The host agent is automatically installed with your SAP system.You can also install a standalone host agent with SAPinst. There is a new installationoption Host Agent available under Software Life-Cycle Options Additional Preparations .You only need to install a standalone host agent in the following cases:l You want to centrally monitor a host that does not have an SAP component.l You want to perform an upgrade to SAP NetWeaver.

n The locations of all installation DVDs can be entered on one screen.

8/146 PUBLIC 12/08/2008

http://service.sap.com/releasenotes




Area Description

SoftwareDeploymentManager (SDM)no longer availablein the ApplicationServer Java

The Software Deployment Manager (SDM) is no longer part of the primary applicationserver instance of a Java-only system. Therefore, there is no longer any technicaldifference between the primary application server instance and the additionalapplication server instance of a Java-only system.The SAP system directory of both instances is now called J<instance_number>.JC<instance_number> no longer exists.

Usage type EP Core(EPC)

The usage type Enterprise Portal (EP) is divided into the 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 formerusage type EP. This new usage type provides more flexibility when implementing aportal where the full enterprise portal capabilities, such as knowledge managementand collaboration, are not required. It contains the portal, GP, and UWL.

n Enterprise Portal (EP)This usage type includes Knowledge management, Collaboration, CAF-Core, VisualComposer, Web Dynpro extension, and .NET PDK.

Usage type EPC is a prerequisite for usage type EP. If you want to obtain the fullcapabilities of the former usage type EP, you need both EP Core and EP.The configuration of EPC comprises only portal configuration steps.

NoteThe standalone implementation of the new usage type EPC without usage type EP iscurrently limited to certain ERP scenarios, as described in the SAP ERP Master Guide.

Installation DVDs You start the installation from the Installation Master DVD for your database.

Java Library There is no longer a Java library for Java systems. Everything is now in the kernel. Youno longer need APYJ2EELIB and RMVJ2EELIB.

SAP Java VirtualMachine (SAP JVM)

You no longer have to download and install a Java Development Kit (JDK) from anothersoftware vendor as a prerequisite for the installation with SAPinst.The SAP JVM is a Java Development Kit (JDK) provided and supported by SAP. The SAPJVM is fully compliant to the Java Standard Edition 5. It is available on the InstallationMaster DVD and is installed automatically by SAPinst when you start the installation.

VisualAdministratortool integratedin SAP NetWeaverAdministrator

SAP NetWeaver Administrator is a brand new solution formonitoring and administeringJava systems and their applications. It is a web-based tool for administration,configuration, and monitoring.The Visual Administrator tool is no longer available as a separate tool. It has beenintegrated in the SAP NetWeaver Administrator.SAP NetWeaver Administrator offers you most of the functions previously available inVisual Administrator, but redesigned for the task-oriented approach of SAP NetWeaverAdministrator.For more information about SAP NetWeaver Administrator, see the SAP NetWeaverMaster Guide and the following:

12/08/2008 PUBLIC 9/146


Area Description

http://www.sdn.sap.com/irj/sdn/netweaver Lifecycle Management OperationsKnowledge Center Administration

SAP SolutionManagerDiagnostics Agent

A SAP Solution Manager Diagnostics Agent (Diagnostics Agent) is a standaloneJava program that runs on each of the systems managed by SAP Solution ManagerDiagnostics. It gathers information and reports to the SAP Solution Manager system.For more information about the Diagnostics Agent, seehttp://service.sap.com/diagnostics .

The installation of the Diagnostics Agent is now part of the Installation Master DVD.That is, you can choose between the following options:n If there is no Diagnostics Agent already installed on this physical or virtual host, it

is installed automatically with an AS Java primary application server instance andadditional application server instance.

n You can also install it as a standalone engine, for example if you want a non-SAPsystem to be managed by SAP Solution Manager Diagnostics.The installation of the Diagnostics Agent as a standalone engine is not described inthis installation guide, but in the Diagnostics Agent Setup Guide, which is available athttp://service.sap.com/diagnostics.

New Features for SAP on DB2 for i5/OS

New Feature Description

Starting and Running SAPinst SAPinst runs natively on the System i, but a secondhost with a GUI capable operating system is stillrequired for access with a remote GUI. During theinstallation, you should make sure that all referencesto resources such as file paths, commands andmemory are specific to the i5/OS where you install theSAP system. You no longer need to copy the contentsof the Installation DVD into the i5/OS Integrated FileSystem before starting the process. However, we stillrecommend copying the contents for performancereasons.

NoteMake sure you read the installation guide carefully.The procedure to start SAPinst on System i haschanged significantly from previous releases. Thenew SAPinst runs in PASE!

TMKSVR The TMKSVR is no longer required for theinstallation.

10/146 PUBLIC 12/08/2008

http://www.sdn.sap.com/irj/sdn/netweaver

http://service.sap.com/diagnostics




New Feature Description

New User Concept The SAP on System i user concept has been redesignedfor this release to be more in-line with the generalSAP concept. This change allows better interactionswith SAP systems running in other UNIX hosts, forexample Linux application servers. Starting with thisrelease, the user <SID>OFR will no longer be availableand <SID>ADM should be used for administration tasks.Also, the user <SID>nn does not exist anymore. TheSAP processes are started now by the user <SID>ADM.For more information, see SAP Note 1123501.

User SAPINST Starting with this release, you need to check if the userSAPINST exists. If this user already exists, you mustdelete it. We now use the user SAPIUSR.

Kernel Library Changes In previous releases, the full kernel was found in anILE library (kernel library). The kernel library of anexisting SAP system was copied and shared with otherSAP systems, but now this is not possible anymore asthe ILE kernel libraries contents and usage neededto be redesigned to accommodate the new SAP filesystem and kernel patching strategy. On System i, aSAP system kernel contains parts in the IntegratedFile System and the ILE libraries, and they are equallysetup and used according to the new SAP systemstructure. The names of these libraries are generatedbased on the SAP system release and instance numberand can not be modified as in previous releases.For more information, see SAP Note 1097751.

SAPinst Group In previous installation guides, we recommendedthat you create a user profile with the name SAPINSTfor the installation user. Following generic SAPconventions, the installation process requires a groupwith this same name. It is not possible to have a userand a group with the same name in i5/OS, if this useralready exists you need to delete it before startingany installation. The first time SAPinst runs, a groupSAPINST is created if it does not already exist. It isadded as a supplemental group to any user createdfor an SAP system.

12/08/2008 PUBLIC 11/146

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1123501&_NLANG=en&_NVERS=0


1 Introduction1.3 SAP Notes for the Installation

Operating Systems

Area Description

Support of OperatingSystems

n For supported operating system and database releases, see the Product AvailabilityMatrix at http://service.sap.com/pam.

n For forums, blogs, content, and community related to all of the supporteddatabases and operating systems, see the Database and Operating Systems area athttp://sdn.sap.com/irj/sdn/dbos.

Documentation

Area Description

SAP Notes You can now access SAP Notes directly in SAP Service Marketplace fromyour PDF. Place the cursor on the SAP Note <number> and double-click. Aseparate browser window opens to display the SAP Note.

Links to the Internet You can use the new links in the PDF files of the guides as follows:n Click the section headings such as New Features to jump back to the table of

contents at the beginning of the guide.n Click an internet link such as http://service.sap.com to jump to the

corresponding internet page.

1.3 SAP Notes for the Installation

Youmust read the following SAP Notes before you start the installation. These SAP Notes contain themost recent information on the installation, as well as corrections to the installation documentation.Make sure that you have the up-to-date version of each SAP Note, which you can find athttp://service.sap.com/notes.

SAP Notes for the Installation

SAP Note Number Title Description

966719 SAP NetWeaver Inst. Based on Kernel 7.10:IBM DB2 for i5/OS

Platform-specific information about the SAPsystem installation and corrections to thisdocumentation.

73606 Supported Languages and Code Pages Information on possible languages andlanguage combinations in SAP systems

953763 Installation of SAP NetWeaverComposition Environment 7.1

CE-specific information about theinstallation and corrections to thisdocumentation.

1261688 Installation of SAP NW CE 7.1 on IBM i Platform-specific information about the SAPNetWeaver Composition Environment 7.1system installation and corrections to thisdocumentation.

12/146 PUBLIC 12/08/2008

http://service.sap.com/pam

http://sdn.sap.com/irj/sdn/dbos

http://service.sap.com

http://service.sap.com/notes





1 Introduction1.4 Online Information from SAP

SAP Note Number Title Description

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows andSystem i: Checking OS Dependencies

73606 Supported Languages and Code Pages Information on possible languages andlanguage combinations in SAP systems

1067221 Central Note for HeterogeneousInstallation

Heterogeneous ABAP system landscapeson different operating systems have beenreleased for some time. Heterogeneous Javasystem landscapes on different operatingsystems have now also been released.However, not every combination ofoperating system and database system isreleased. This SAP Note and its related SAPNotes describe the released operating systemand database combinations.

1.4 Online Information from SAP

More information is available online as follows.

Documentation

Description Internet Address Title

Master Guide for SAPNetWeaver CompositionEnvironment 7.1

http://sdn.sap.com SAP NetWeaverComposition Environment

Master Guide ‒ SAP NetWeaverComposition Environment 7.1

Master Guide SAPSolution Manager 4.0

http://service.sap.com/instguides SAPComponents SAP Solution Manager Release 4.0

Master Guide ‒ SAP SolutionManager 4.0

General Quick Links

Description Internet Address

SAP Help Portal http://help.sap.com

SAP Notes http://service.sap.com/notes

Released platforms and operatingsystems


Product AvailabilityMatrix (PAM) http://service.sap.com/pam

Release notes http://service.sap.com/releasenotes

Unicode SAP systems and theiravailability

http://service.sap.com/unicode

System sizing (Quick Sizer tool) http://service.sap.com/sizing

12/08/2008 PUBLIC 13/146




http://sdn.sap.com

http://service.sap.com/instguides


http://help.sap.com










http://service.sap.com/sizing


1 Introduction1.5 Accessing the SAP Library

Description Internet Address

SAP NetWeaver capabilities http://sdn.sap.com/irj/sdn/netweaver

Life-cycle management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/lcm

Landscape design for SAPNetWeaver

http://sdn.sap.com/irj/sdn/landscapedesign

Application management for SAPNetWeaver

http://sdn.sap.com/irj/sdn/applicationmanagement

Software logistics for SAPNetWeaver

http://sdn.sap.com/irj/sdn/softwarelogistics

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

Security for SAP NetWeaver http://sdn.sap.com/irj/sdn/security

Information on SAP SupportPackage Stacks

http://service.sap.com/sp-stacks

SAP Solution Manager http://service.sap.com/solutionmanager

Maintenance Optimizer http://service.sap.com/solman-mopz

1.5 Accessing the SAP Library

For more information about SAP NetWeaver, access the SAP Library from the SAP Help Portal athttp://help.sap.com.The references to SAP NetWeaver Library documentation in this documentation always refer to thefollowing entry point on the SAP Help Portal:

1.6 Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

n SAP system refers to SAP NetWeaver CE 7.1.n Diagnostics Agent refers to SAP Solution Manager Diagnostics Agent.n SAP System ID

The SAP system ID is abbreviated to SID and SAPSID or sid and sapsid. For <sid> / <sapsid>,substitute your SAP system ID in lower case characters, for example, prd. For <SID> / <SAPSID>,substitute your SAP system ID in upper case characters, for example, PRD.IBM System i and Short Forms

14/146 PUBLIC 12/08/2008

http://sdn.sap.com/irj/sdn/netweaver

http://sdn.sap.com/irj/sdn/lcm

http://sdn.sap.com/irj/sdn/landscapedesign

http://sdn.sap.com/irj/sdn/applicationmanagement

http://sdn.sap.com/irj/sdn/softwarelogistics

http://sdn.sap.com/irj/sdn/operations

http://sdn.sap.com/irj/sdn/security



http://service.sap.com/solutionmanager


http://service.sap.com/solman-mopz

http://service.sap.com/solman-mopz

http://help.sap.com

1 Introduction1.6 Naming Conventions

In this document, the short form “System i” is used for “IBM System i”. In previous versions of thisdocument, “IBM System i” was referred to as “IBM eServer iSeries” or “IBM AS/400”.IBM DB2 for i5/OS and Short FormsIn this document, the short form “DB2 for i5/OS” is used for the database “IBMDB2 for i5/OS”, andin certain cases, the SAP ID “DB4” is used as well. In previous versions of this document, “IBMDB2 for i5/OS” was referred to as “IBM DB2 Universal Database for iSeries” or “IBM DB2 UniversalDatabase for AS/400” or “DB2/400”.IBM i5/OS and Short FormsIn this document, the short form “i5/OS” is used for the operating system “IBM i5/OS”. In previousversions of this document, “IBM i5/OS” was referred to as “IBM OS/400”.

Variables

Variables Description

<SID> and <SAPSID> SAP system ID in uppercase letters

<sid> and <sapsid> SAP system ID in lowercase letters

<host_name> Name of the corresponding host

<INSTDIR> Installation directory for the SAP system

<DVD_DIR> Directory on which a DVD is mounted

<OS> Operating system name within a path

<SAPLOCALHOST> Name of Windows application server

<SAPTRANSHOST> Name of transport directory (on System i)

<SAPGLOBALHOST> Name of primary application server instance host

The following example shows how the variables are used:

Example

Log on as user <sapsid>adm and change to the directory /usr/sap/<SAPSID>.If your SAP system ID is C11, log on as user c11adm and change to the directory /usr/sap/C11.

12/08/2008 PUBLIC 15/146

This page is intentionally left blank.

2 Planning

2 Planning

This section provides general planning information.You must first:

1. Plan your SAP system landscape according to theMaster Guide and the Technical Infrastructure Guideavailable for your product.

2. Decide on your installation option [page 17].

Now continue with the section for your chosen installation option below.

Standard, Distributed, or High-Availability System

1. If you want to use Adobe Document Services (ADS), you check what you have to do if your platform isnot supported for ADS [page 25].

2. You decide whether you want to install multiple SAP systems on a single System i [page 29].3. If you want to install a high-availability system, you read Planning the Switchover Cluster [page 31].4. You can now continue with Preparation [page 35].

Additional Application Server Instance

You do not have to perform any planning steps.You can immediately continue with Preparation [page 35].

Host Agent as a Standalone Installation

You do not have to perform any planning steps.You can immediately continue with Preparation [page 35].

2.1 Installation Options Covered by this Guide

This section shows the installation options covered by this installation guide.

n Standard system [page 18] (formerly known as central system)n Distributed system [page 18]n High-availability system [page 19]n You can install one or more additional application server instance(s) [page 20] to an existing standard,

distributed or high-availability system.n You can install a standalone host agent [page 23].

12/08/2008 PUBLIC 17/146

2 Planning2.1 Installation Options Covered by this Guide

2.1.1 Standard System

n Central services instance (SCS)n Database instance (DB)n Primary application server instance

Figure 1: Standard Java System

Optionally you can install one or more additional application server instances. For more information,see Additional Application Server Instance [page 20].

2.1.2 Distributed System

In a distributed system, every instance can run on a separate host:

n Central services instance (SCS)n Database instance (DB)n Primary application server instance

Note

You can also use the SAP transport host or the SAP global host as your primary applicationserver instance host.

Optionally you can install one or more additional application server instances. For more information,see Installation of an Additional Application Server Instance [page 20].

18/146 PUBLIC 12/08/2008


Figure 2: Distributed Java System

2.1.3 High-Availability System

In a high-availability system, every instance can run on a separate host:

n Java Central Services Instance (SCS)n Database instance

n Primary application server instance

We recommend that you run both the ASCS and the SCS in a switchover cluster infrastructure. Boththe ASCS and the SCS must each have their own Enqueue Replication Server (ERS) instance.Optionally you can install one to <n> additional application server instances. For more information,see Installation of an Additional Application Server Instance [page 20].The following figures show examples for the distribution of the SAP instances in a high-availabilitysystem.

12/08/2008 PUBLIC 19/146


Figure 3: High-Availability System

2.1.4 Additional Application Server Instance

You can install one or more additional application server instance(s) for an existing SAP system.An additional application server instance can run on:

n The host of any instance of the existing SAP system (exceptions see below)n On a dedicated host

Additional Application Server Instance for a Standard System

For example, the following figure shows each of the three additional application server instancesthat are running:

n On the main host of the SAP system, that is on the host on which the primary application serverinstance and the database instance run

20/146 PUBLIC 12/08/2008


n On dedicated hosts

Figure 4: Additional Application Server Instance for a Standard System

For additional information, see Standard System [page 18].

Additional Application Server Instance for a Distributed System

For example, the following figure shows each of the three additional application server instancesthat are running:

n On the main host of the SAP system, that is on the host on which the primary application serverinstance and the database instance run

n On dedicated hosts

It is not recommended to install additional application server instance(s) on the SAP global host.

12/08/2008 PUBLIC 21/146


Figure 5: Additional Application Server Instance for a Distributed System

For additional information, see Distributed System [page 18].

Additional Application Server Instance for a High-Availability System

For example, the following figure shows each of the three additional application server instancesthat are running on:

n The host of the primary application server instancen Dedicated hosts

It is not recommended to install additional application server instance(s) on the switchover clusterinfrastructure.

22/146 PUBLIC 12/08/2008


Figure 6: Additional Application Server Instance for a High-Availability System

For more information, see High-Availability System [page 19].

2.1.5 Standalone Host Agent

Using the host agent you can centrally monitor any host with the Alert Monitor or the SAPNetWeaver Administrator or the Adaptive Computing Controller (ACC). In addition, the host agentis used by the ACC for starting, stopping, and relocating SAP instances and databases.For more information on the ACC see http://sdn.sap.com/irj/sdn/adaptive.The host agent is automatically installed during the installation of all SAP NetWeaver instancesand components.You only need to install a standalone host agent in the following cases:

n You want to manage a host that does not have an SAP instance or component.n You have upgraded your SAP system to SAP NetWeaver 7.1 or higher and want to the instances of

the upgraded system to be managed by the ACC.

12/08/2008 PUBLIC 23/146

http://sdn.sap.com/irj/sdn/adaptive

2 Planning2.2 SAP System Transport Host

Figure 7:

The host agents contain the following elements:

n The control program saphostexec

n The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)n The sapacosprep executable of the Adaptive Computing Infrastructuren The operating system collector saposcol

Note

On System i, the installed programs are started by the auto-start job (ADDAJE) SAPINIT in subsystemQUSRWRK, which was created during the installation. The subsystem QUSRWRK is restarted after everyIPL automatically.

More Information

For more information about the host agent, see the SAP Library [page 14]:Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS Infrastructure of the NetWeaver Management Agents

2.2 SAP System Transport Host

The transport host contains the transport directory that is used by the SAP transport system to storetransport data and change information of SAP systems, such as software programs, data dictionary

24/146 PUBLIC 12/08/2008

2 Planning2.3 Running Adobe Document Services on Nonsupported Platforms

data, or customization data. If you have several SAP systems they are usually organized in transportdomains. In most cases, all SAP systems in a transport domain have a common transport directory.For more information, see the SAP Library [page 14]:Administrator’s Guide Technical Operations Manual General Administration Tasks Software Life Cycle

Management Software Logistics Change and Transport System Change and Transport System ‒ Overview(BC-CTS) Basics of the Change and Transport System Transport Management System ‒ ConceptWhen you install an SAP system, SAPinst by default creates the transport directory on the primaryapplication server instance host in /usr/sap/trans.You have to prepare this host for use by the new SAP system if one of the following applies to you:

n You want to locate the transport directory on another host.n You want to use an existing transport host and directory in your SAP system landscape.

More InformationSetting Up File Systems [page 58]

2.3 Running Adobe Document Services on NonsupportedPlatforms

Adobe document services (ADS) are currently not supported to run natively on all platformssupported by SAP systems based on SAP NetWeaver, in particular on 64-bit platforms.

ProcedureTo use ADS in SAP landscapes on nonsupported platforms, install an additional standalone ASJava on a platform supported by ADS.For more information, see SAP Note 925741.

Note

Currently, System i supports ADS only on double-stack systems. For Java systems such as CE, youmust install an additional AS Java on a platform supported by ADS.

More InformationFor more information about running ADS on SAP systems based on SAP NetWeaver, seehttp://sdn.sap.com/irj/sdn/adobe.

12/08/2008 PUBLIC 25/146


http://sdn.sap.com/irj/sdn/adobe

2 Planning2.4 Integration of LDAP Directory Services

2.4 Integration of LDAP Directory Services

This section explains the benefits of using the SAP system with the Lightweight Directory AccessProtocol (LDAP) directory and gives an overview of the configuration steps required to use an SAPsystem with the directory.LDAP defines a standard protocol for accessing directory services, which is supported by variousdirectory products such as Microsoft Active Directory, and OpenLDAP slapd. Using directory servicesenables important information in a corporate network to be stored centrally on a server. Theadvantage of storing information centrally for the entire network is that you only have to maintaindata once, which avoids redundancy and inconsistency.If an LDAP directory is available in your corporate network, you can configure the SAP system to usethis feature. For example, a correctly configured SAP system can read information from the directoryand also store information there.

Note

The SAP system can interact with the Active Directory using the LDAP protocol, which defines:

n The communication protocol between the SAP system and the directory

n How data in the directory is structured, accessed, or modified

If a directory other than the Active Directory also supports the LDAP protocol, the SAP system cantake advantage of the information stored there. For example, if there is an LDAP directory on a UNIXor Windows server, you can configure the SAP system to use the information available there. In thefollowing text, directories other than the Active Directory that implement the LDAP protocol arecalled generic LDAP directories.

Caution

This section does not provide information about the use of LDAP directories with the LDAPConnector. For more information about using and configuring the LDAP Connector for an ABAPsystem, see the SAP Library [page 14]:Function-Oriented View Security Identity Management Identity Management of the Application Server

ABAP Configuration of Identity Management Directory Services LDAP Connector

PrerequisitesYou can only configure the SAP system for Active Directory services or other LDAP directories ifthese are already available on the network. As of Windows 2000 or higher, the Active Directoryis automatically available on all domain controllers. A generic LDAP directory is an additionalcomponent that you must install separately on a UNIX or Windows server.

26/146 PUBLIC 12/08/2008


FeaturesIn the SAP environment, you can exploit the information stored in an Active Directory or genericLDAP directory by using:

n SAP Logonn The SAP Microsoft Management Console (SAP MMC)n The SAP Management Console (SAP MC)

For more information about the automatic registration of SAP components in LDAP directories andthe benefits of using it in SAP Logon and SAP MMC, see the documentation SAP System Information inDirectory Services on SAP Service Marketplace at:http://service.sap.com/msplatforms Microsoft Windows Server

For more information about the SAP MC and about how to configure it to access LDAP Directories,see the documentation SAP Management Console in the SAP Library [page 14]:Administrator’s Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems AS

Java (Application Server Java) Administration Administration Tools SAP Management Console

SAP Logon

Instead of using a fixed list of systems and message servers, you can configure SAP Logon in thesapmsg.ini configuration file to find SAP systems and their message servers from the directory. Ifyou configure SAP logon to use the LDAP directory, it queries the directory each time Server or Groupselection is chosen to fetch up-to-date information on available SAP systems.To use LDAP operation mode, make sure that the sapmsg.ini file contains the following:[Address]

Mode=LDAPdirectory

LDAPserver=

LDAPnode=

LDAPoptions=

Distinguish the following cases:

n If you use an Active Directory, you must set LDAPoptions=“DirType=NT5ADS”. For moreinformation, see the SAP system profile parameter ldap/options.

n You must specify the directory servers (for example, LDAPserver=pcintel6 p24709) if either ofthe following is true:l The client is not located in the same domain forest as the Active Directoryl The operating system does not have a directory service client (Windows NT and Windows 9X

without installed dsclient).For more information, see the SAP system profile parameter ldap/servers.

n For other directory services, you can use LDAPnode to specify the distinguished name of the SAProot node. For more information, see the SAP system profile parameter ldap/saproot.

12/08/2008 PUBLIC 27/146

http://service.sap.com/msplatforms




SAP MMC

The SAPMMC is a graphical user interface (GUI) for administering andmonitoring SAP systems froma central location. It is automatically set up when you install an SAP system on Windows. If the SAPsystem has been prepared correctly, the SAP MMC presents and analyzes system information thatit gathers from various sources, including the Active Directory.Integrating the Active Directory as a source of information has advantages for the SAP MMC. It canread system information straight from the directory that automatically registers changes to thesystem landscape. As a result, up-to-date information about all SAP application servers, their status,and parameter settings is always available in the SAP MMC.If you need to administer distributed systems, we especially recommend that you use the SAP MMCtogether with Active Directory services. You can keep track of significant events in all of the systemsfrom a single SAP MMC interface. You do not need to manually register changes in the systemconfiguration. Instead, such changes are automatically updated in the directory and subsequentlyreflected in the SAP MMC.If your SAP system is part of a heterogeneous SAP system landscape that comprises systems orinstances both on Unix and Windows operating systems, you can also use the SAP MMC for operatingand monitoring the instances running on Unix.

SAP MC

The SAP MC is a graphical user interface (GUI) for administering and monitoring SAP systems froma central location. The SAP MC is automatically set up when you install an SAP system on anyplatform. If the SAP system has been prepared correctly, the SAP MC presents and analyzes systeminformation that it gathers from various sources, including a generic LDAP Directory.Integrating a generic LDAP Directory as a source of information has advantages for the SAP MC. Itcan read system information straight from the directory that automatically registers changes to thesystem landscape. As a result, up-to-date information about all SAP application servers, their status,and parameter settings is always available in the SAP MC.

Configuration Tasks for LDAP Directories

This section describes the configuration tasks you have to perform for the Active Directory or other(generic) LDAP directories.

Configuration Tasks for Active Directory

To enable an SAP system to use the features offered by the Active Directory, you must configure theActive Directory so that it can store SAP system data.To prepare the directory, you use SAPinst to automatically:

n Extend the Active Directory schema to include the SAP-specific data typesn Create the domain accounts required to enable the SAP system to access and modify the Active

Directory. These are the group SAP_LDAP and the user sapldap.

28/146 PUBLIC 12/08/2008

2 Planning2.5 Multiple SAP Systems on a Single System i

n Create the root container where information related to SAP is stored

n Control access to the container for SAP data by giving members of the SAP_LDAP group permissionto read and write to the directory

You do this by running SAPinst on the Windows server on which you want to use Active DirectoryServices and choosing <SAP System> Software Life-Cycle Options LDAP Registration Active DirectoryConfiguration . For more information about running SAPinst on Windows, see documentationInstallation Guide — <your product> on Windows : <Database>.

Note

You have to perform the directory server configuration only once. Then all SAP systems that needto register in this directory server can use this setup.

Configuration Tasks for Generic LDAP Directories

To configure other LDAP directories, refer to the documentation of your directory vendor.

Enabling the SAP System LDAP Registration

Once you have correctly configured your directory server, you can enable the LDAP registration ofthe SAP system by setting some profile parameters in the default profile.To do this, run SAPinst [page 90] once for your system and choose:<SAP System> Software Life-Cycle Options LDAP Registration LDAP Support

If you use a directory server other than Microsoft Active Directory and/or non-Windows applicationservers, you have to store the directory user and password information by using ldappasswdpf=<any_instance_profile>. The information is encrypted for storage in DIR_GLOBAL and istherefore valid for all application servers. After restarting all application servers and start services,the system is registered in your directory server. The registration protocols of the components aredev_ldap*. The registration is updated every time a component starts.

2.5 Multiple SAP Systems on a Single System i

SAP on System i allows installation of multiple SAP systems on a single System i host (provided spaceexists). However, we recommend that you isolate your SAP production system as far as possible fromyour test and development systems. The degree of isolation you opt for can range from running eachSAP system on a separate System i to having all the environments on a single host.If you decide to implement multiple SAP systems on a single System i, you need to be aware of therisks involved.Running multiple SAP systems on a single System i is similar to MCOD. For more information,see SAP Note 443925.

12/08/2008 PUBLIC 29/146


2 Planning2.5 Multiple SAP Systems on a Single System i

Importance of an Independent Testing Environment

If you have both your production and development/test systems on the same machine, youcannot test PTFs (IBM program temporary fixes) and CUM packages (cumulative packages) in anindependent testing environment. The reason is that this immediately affects the production system.The same problem applies to operating system upgrades. If these initially take place in an independenttest environment, it allows you to identify any customer-specific problems (such as problemsresulting from any modifications you might have made to the standard system) away from the liveenvironment.If you have more than one SAP system on a single System i host, you can test SAP upgradesindependently. However, if you test an SAP upgrade on a separate System i host, it has the advantagethat a test SAP upgrade does not take away resources from the production system.

Possibilities for Resource Distribution

n LPAR: Logical Partitioning of the System iOn System i, you can divide your complete System i into several entirely independent servers. Thismeans that you install different copies of the operating system on each of the servers. You candecide on the CPU, memory and DASD splitting. Only the serial number is the same, and all theother elements are separate and cannot interfere with a system in another LPAR. This is the best(but most expensive) way to separate SAP systems.

n Memory: Running SAP Instances in Separate SubsystemsEach SAP system with its associated database can have multiple instances. Each instance runs in aseparate operating system subsystem. (A subsystem is an operating environment in which thesystem coordinates processing and resources.) The subsystem definition allows you to define andallocate individual memory pools to the subsystem. These memory pools cannot be accessed byusers from any other SAP instance.

n Disks: Separate ASPs for Each SAP SystemOn System i the installed disk capacity can be segmented to provide a separate auxiliary storage pool(ASP) for each SAP system. You can then allocate specific disk drives to each user ASP created. Thishelps to minimize the impact of disk activity of one SAP environment on other SAP environments.

n Processors: Long-Running Tasks Can Slow Down the Production EnvironmentRegardless of the number of processors involved, the System i manages them all as a single entity.It dispatches tasks to its processors and ensures that usage is balanced. A long-running program orother task encountered during development or testing can have an impact on production activityif these SAP systems are running on the same host. You can minimize the potential impact of thisby running development and test systems at a lower priority than the production system.

30/146 PUBLIC 12/08/2008

2 Planning2.6 Planning the Switchover Cluster

2.6 Planning the Switchover Cluster

You can reduce unplanned downtime for your SAP system by setting up a switchover cluster. Thissetup installs critical software units ‒ known as “single points of failure” (SPOFs) ‒ across multiplehost machines in the cluster. In the event of a failure on the primary node, proprietary switchoversoftware automatically switches the failed software unit to another hardware node in the cluster.Manual intervention is not required. Applications accessing the failed software unit might experiencea short delay but can then resume processing as normal.Switchover clusters also have the advantage that you can deliberately initiate switchover to freeup a particular node for planned system maintenance. Switchover solutions can protect againsthardware failure and operating system failure but not against human error, such as operator errors orfaulty application software. Additional downtime might be caused by upgrading your SAP system orapplying patches to it.Without a switchover cluster, the SAP system SPOFs ‒ central services instance, the database instance,and the central file share ‒ are vulnerable to failure because they cannot be replicated. All of thesecan only exist once in a normal SAP system.You can protect software units that are not SPOFs against failure by making them redundant, whichmeans simply installing multiple instances. For example, you can add additional application serverinstances. This complements the switchover solution and is an essential part of building HA intoyour SAP system.

Recommendation

We recommend switchover clusters to improve the availability of your SAP system.

A switchover cluster consists of:

n A hardware cluster of two or more physically separate host machines to run multiple copies of thecritical software units, in an SAP system the SPOFs referred to above

n Switchover software to detect failure in a node and switch the affected software unit to the standbynode, where it can continue operating

n Amechanism to enable application software to seamlessly continue working with the switchedsoftware unit ‒ normally this is achieved by virtual addressing (although identity switchoveris also possible)

PrerequisitesYou must first discuss switchover clusters with your hardware partner because this is a complextechnical area. In particular, you need to choose a proprietary switchover product that works withyour operating system.We recommend that you read the following documentation before you start:

n Check the informations and the installation guides that are available athttp://sdn.sap.com/irj/sdn/ha.

12/08/2008 PUBLIC 31/146

http://sdn.sap.com/irj/sdn/ha


n The enqueue replication server (ERS) is a major contribution to an HA setup and is essential for aJava system. We strongly recommend you to also use it for an ABAP system. You need one ERS foreach Java SCS and one ERS for each ABAP SCS (ASCS) installed in your system.

FeaturesThe following graphic shows the essential features of a switchover setup:

Figure 8: Switchover Setup

Note

This graphic and the graphics in this section are only examples. You need to discuss your individualHA setup with your HA partner.These graphics summarize the overall setup and do not show the exact constellation for aninstallation based on one of the available technologies (ABAP, ABAP+Java, or Java).

The following graphic shows an example of a switchover cluster in more detail:

32/146 PUBLIC 12/08/2008


Figure 9: Switchover Cluster

ConstraintsThis documentation concentrates on the switchover solution for the central services instance. Formore information about how to protect the central file share and the database instance by usingswitchover software or (for of the database) replicated database servers, contact your HA partner.You need to make sure that your hardware is powerful enough and your configuration is robustenough to handle the increased workload after a switchover. Some reduction in performance mightbe acceptable after an emergency. However, it is not acceptable if the system comes to a standstillbecause it is overloaded after switchover.

12/08/2008 PUBLIC 33/146


3 Preparation

3 Preparation

This section includes the preparation steps that you have to perform for the:

n Standard, distributed or high-availability systemn Additional application server instancen Standalone host agent

Preparation Steps for a Standard, Distributed, or High-Availability System

Note

In a standard system, all mandatory instances are installed on one host. Therefore, if you areinstalling a standard system, you can ignore references to other hosts.

1. You identify basic SAP system parameters [page 37].2. You check the hardware and software requirements [page 43] for every installation host of the HA system

landscape that you want to install.3. If you want to configure the User Management Engine (UME) of Application Server Java (AS Java)

for the user management of a separate ABAP system, you have toprepare user management for an external ABAP System [page 55].

4. You set up file systems [page 58] and make sure that the required disk space is available for thedirectories to be created during the installation.

5. You install the Toolbox JDBC driver [page 62].6. You check Qp2Term, Qp2Shell, and the i5/OS Portable Application Solution Environment [page 64].7. You install the Qshell [page 64].8. You check and adjust i5/OS system values [page 65].9. You adjust startup program QSTRUP [page 69].10. You check distribution of libraries on ASPs [page 72].11. You add a user ASP [page 73].12. You configure TCP/IP [page 74].13. You adjust the relational database name [page 79].14. You install English as a secondary language [page 79].15. You prepare a System i user profile [page 80].16. If you want to share the transport directory trans from another system, make available this

directory to your installation hosts.

12/08/2008 PUBLIC 35/146

3 Preparation

17. If you want to use virtual host names, you have to set the environment variableSAPINST_USE_HOSTNAME [page 90]. Alternatively you can specify the virtual host name in thecommand to start SAPinst.

18. If you want to install a high-availability system, you perform switchover preparations [page 54].19. You generate the SAP Solution Manager Key [page 81].20. You make sure that the required installation media [page 81] are available on every host on which you

want to install an instance of your SAP system.21. You can continue with Installation [page 87].

Preparation Steps for an Additional Application Server Instance

You have to perform the following preparations on the host where you install the additionalapplication server instance(s):

1. You identify basic SAP system parameters [page 37].2. You check the hardware and software requirements [page 43] for every installation host on which you want

to install one or more additional application server instances.3. You set up file systems [page 58] and make sure that the required disk space is available for the

directories to be created during the installation.4. You install the Toolbox JDBC driver [page 62].5. You check Qp2Term, Qp2Shell, and the i5/OS Portable Application Solution Environment [page 64].6. You install the Qshell [page 64].7. You check and adjust i5/OS system values [page 65].8. You adjust startup program QSTRUP [page 69].9. You configure TCP/IP [page 74].10. You adjust the relational database name [page 79].11. You install English as a secondary language [page 79].12. You prepare a System i user profile [page 80].13. If you want to share the transport directory trans from another system, make available this

directory to your installation hosts.14. If you want to use a virtual host name, you have to set the environment variable

SAPINST_USE_HOSTNAME [page 90]. Alternatively you can specify the virtual host name in thecommand to start SAPinst.

15. You make sure that the required installation media [page 81] are available on every host on which youwant to install one or more additional application server instances.

16. You can continue with Installation [page 87].

Preparation Steps for a Standalone Host Agent

You have to perform the following preparations on the host where you install a standalone host agent:

1. You identify basic SAP system parameters [page 37].You can find the parameters in the table Host Agent.

36/146 PUBLIC 12/08/2008

3 Preparation3.1 Basic SAP System Parameters

2. You check the hardware and software requirements [page 43] on the installation host.You can find the requirements for the Host Agent in section Requirements for a Standalone Host Agent.

3. You set up file systems [page 58] and make sure that the required disk space is available for thedirectories to be created during the installation.

4. You check Qp2Term, Qp2Shell, and the i5/OS Portable Application Solution Environment. [page 64]5. You install the Qshell [page 64].6. You check and adjust i5/OS system values [page 65].7. You configure TCP/IP [page 74].8. You adjust the relational database name [page 79].9. You install English as a secondary language [page 79].10. You prepare a System i user profile [page 80].11. You make sure that the required installation media [page 81] are available on the installation host.

You can find the installation media that are required for the installation of a standalone host agentin the row Host Agent (Standalone) of the media table.

12. You can continue with Installation [page 87].

3.1 Basic SAP System Parameters

SAPinst asks whether you want to run the installation in Typical or Custommode.If you choose Typical, SAPinst provides automatic default settings and you only have to respond toa minimum number of prompts. However, you can still change any of the default settings on theparameter summary screen.The tables below list the basic system parameters that you always need to specify before installing yourSAP system, both in typical and in custom mode.For all other SAP system parameters, use the F1 help in the SAPinst dialogs.

SAP System ID and Database ID

Parameters Description

SAP System ID <SAPSID> The SAP system ID <SAPSID> identifies the entire SAP system.SAPinst prompts your for the <SAPSID> when you execute the first installationoption to install a new SAP system.If there are further installation options to be executed, SAPinst prompts youfor the profile directory. For more information, see the description of theparameter SAP System Profile Directory.

ExampleThis prompt appears when you install the central services instance, which is the

12/08/2008 PUBLIC 37/146



first instance to be installed in a distributed system.

CautionChoose your SAP system ID carefully. Renaming is difficult and requires youto reinstall the SAP system.

Make sure that your SAP system ID:n Is unique throughout your organizationn Consists of exactly three alphanumeric charactersn Contains only uppercase lettersn Has a letter for the first charactern Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY LOG

LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID SQL SYS

TMP UID USR VAR

Database ID <DBSID> The <DBSID> identifies the database instance. SAPinst prompts you for the<DBSID> when you are installing the database instance.For System i, the <DBSID> is always the same as the <SAPSID>.

CautionChoose your database ID carefully. Renaming is difficult and requires youto reinstall the SAP system.

n If you want to install a new database:Make sure that your database ID:l Is unique throughout your organizationl Consists of exactly three alphanumeric charactersl Contains only uppercase lettersl Has a letter for the first characterl Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT KEY

LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA SHG SID

SQL SYS TMP UID USR VAR

n If you want to use an existing database system:Enter exactly the database ID of the existing database to which you want toadd the system.

System ID <SMDSID> ofSAP Solution ManagerDiagnostics Agent

SAPinst sets <SMDSID> to SMD by default.If SMD is already used by another SAP system that is not a Diagnostics Agentsystem, <SMDSID> is set to DA<x>, where <x> can be any letter from A to Z, and DA

stands for “DiagnosticsAgent”).If required, you can change <SMDSID> to a value of your choice on the ParameterSummary screen. If you do so, the same naming conventions as for <SAPSID> apply.For more information, see entry “SAP System ID <SAPSID>” in this table above.

38/146 PUBLIC 12/08/2008


SAP System Profile Directory


/<sapmnt>/<SAPSID>/profile or/usr/sap/<SAPSID>/SYS/profile

The installation retrieves the parameters entered earlier from the SAPsystem profile directory.SAPinst prompts you to enter the location of the profile directorywhen the installation option that you execute is not the first onebelonging to your SAP system installation. See also the description ofthe parameters SAP System ID and Database ID./usr/sap/<SAPSID>/SYS/profile is the soft link referring to/<sapmnt>/<SAPSID>/profile.

NoteIf you install an additional application server instance in an existingSAP system, SAPinst also prompts you for the profile directory ofthe existing SAP system.

SAP System Instances, Hosts, and Ports


Instance Number of theSAP system

Instance Number:Technical identifier that is required for every instance of an SAP system,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 SAPinstance is running on the same host, these instances must be assigned differentnumbers.The instance number is used to specify the names of the SAP system instancedirectories which are created automatically by SAPinst during the installation:n The directory both of the primary application server instance and of an

additional application server instance is called J<Instance_Number>.n The directory of the central services instance is called SCS<Instance_Number>.n The directory of the Enqueue Replication Server instance is called

ERS<Instance_Number>.For more information, see SAP Directories [page 58].

Instance Number for theDiagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent, consistingof a two-digit number from 00 to 98.The instance number is set automatically to the next free and valid instancenumber that has not yet been assigned to the SAP system.The instance number is used to specify the name of the Diagnostics Agentinstance directory which are created automatically by SAPinst during theinstallation:The directory of the Diagnostics Agent instance is called J<Instance_Number>.For more information, see SAP Directories [page 58].The same restrictions apply as in “Instance Number of the SAP system” (seeabove).

12/08/2008 PUBLIC 39/146



Virtual Host Name You can use one or more virtual TCP / IP host names for SAP servers within anSAP server landscape to order to conceal their physical network identities fromeach other. This may be useful when moving SAP servers or complete serverlandscapes to other new hardware within a short time frame without having tocarry out a reinstallation or complicated reconfiguration.If you want to use virtual host names for the installation, you have to specify thevirtual host name [page 90] before you start SAPinst.If you want to install a high-availability (HA) system [page 19], you need the virtualhost name when you install the SCS instance into a cluster.n For more information about the use of virtual TCP/IP host names, see SAP

Note 962955.n The host name must not exceed 12 characters. For more information about

the allowed host name length and characters, see SAP Note 611361.

Message Server PortCaution

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

Port Number of the SAP Message Server:If you do not specify a value, the default port number is used.The SCS instance profile contains the configuration for the Java message server.The Java message server port uses the parameter rdisp/msserv_internal withdefault value 39<nn>, where <nn> is the instance number of the SCS messageserver instance.For more information about the parameters used for message server ports, seeSAP Note 821875.

Master Password


Master Password This password is used for all new user accounts SAPinst creates and for thesecure store key phrase. The length has to be 8 to 14 characters.Depending on your installation scenario there might be more restrictions.

CautionIf you do not create the operating system users manually, SAPinst createsthem with the common master password. For more information, see thedescription of the parameter Operating System Users. In this case, make sure thatthe master password meets the requirements of your operating system andof your database.

40/146 PUBLIC 12/08/2008





Operating System Users of the SAP System


Operating System Users SAPinst creates the users <sapsid>adm and <sapsid>owner.SAPinst assigns these users to the group R3GROUP.SAPinst also creates the user sapadm to use central monitoring services.Make sure that the ID of this operating system user is unique and the same oneach application instance host.If you do not create operating system users manually before you start theinstallation, SAPinst creates them automatically during the installation.

User Management Engine (UME)

Parameter Description

UME Configuration SAPinst prompts you for how to configure the UME during the input phase ofthe installation.You can choose between the following options:n Use Java database (default).

If you choose this option, administrators can manage users and groups withthe UME Web admin tool and SAP NetWeaver Administrator only.

n Use an external ABAP system.If you choose this option, administrators can manage users with thetransaction SU01 on the external ABAP system, and, depending on thepermissions of the communication user, also with the UME Web admin tool

and SAP NetWeaver Administrator.You must have created the required users manually on the external ABAPsystem.For more information, see Preparing User Management for an External ABAPSystem [page 55].

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

Using the Java Database:

Java Administrator User SAPinst sets the user name Administrator and the master password by default.If required, you can choose another user name and password according toyour requirements.

Java Guest User SAPinst sets the user name Guest and the master password by default.The Guest user is for employees who do not belong to a company or who haveregistered as company users with pending approval. Guest users belong to thedefault group Authenticated Users and have read access only.

Using an External ABAP System ‒ Parameters for the ABAP Connection:

Application Server InstanceNumber

This is the instance number on the application server of the central ABAPsystem to which you want to connect the Application Server Java.To find out the number on the host of the primary application server instance,look under the SAP directory usr/sap/<SAPSID>/DVEBMGS<nn>. The value <nn>is the number assigned to the SAP system.

12/08/2008 PUBLIC 41/146




Application Server Host This is the host name of the relevant application server instance.To find out the host name, enter hostname at the command prompt of the hostrunning the primary application server instance.

Communication User This is the name and password of the existing ABAP communication user. Youmust have created this user manually on the external ABAP system.

Using an External ABAP System ‒ Parameters for the Application Server Java Connection:

Administrator User This is the name and password of the administrator user that you created onthe external ABAP system.

Administrator Role The role SAP_J2EE_ADMINmust exist on the external ABAP system.

Guest User This is the name and password of the guest user that you created on theexternal ABAP system.The guest user is for employees who do not belong to a company or who haveregistered as company users with pending approval. Guest users belong to thedefault group Authenticated Users and have read access only.

Guest Role The role SAP_J2EE_GUESTmust exist on the external ABAP system.

Key Phrase for Secure Store Settings


Key Phrase for SecureStore Settings

This is a random word or phrase that is used to encrypt the secure store.The Java EE engine uses this phrase to generate the key that is used to encryptthe data.The uniqueness of the phrase you use contributes to the uniqueness of theresulting key.

RecommendationUse a long key phrase that cannot be guessed easily. Use both uppercase andlowercase letters in the phrase and include special characters.

Internet Communication Manager (ICM) User Management


Password of webadm The administration user webadm is created to use the web administrationinterface for Internet Communication Manager (ICM) and Web Dispatcher.SAPinst sets themaster password by default. If required, you can choose anotherpassword. The length of the password must be between 5 and 128 characters.

42/146 PUBLIC 12/08/2008

3 Preparation3.2 Hardware and Software Requirements

Host Agent


Password of sapadm The administration user sapadm is created to use central monitoring services.If this user does not already exist, SAPinst automatically creates it.SAPinst prompts you to enter either the password of the existing user or a newpassword for the user to be created.

Parameters Relevant for the Database

Parameters Description Your Values

Database schema The database schema name isSAP<SAPSID>DB for Java systems.

...

Location of the Toolbox JDBCDriver

Enter the path where the ToolboxJDBC driver files are located.Make sure that the correct versionof the JDBC driver is used.For more information, see Hardwareand Software Requirements [page 46].

...

ASP of SAP<SID>DB and SAP<SID>JRN Auxiliary Storage Pool (ASP) for theJava Database Library SAP<SID>DB

and the Java Journal ReceiverLibrary SAP<SID>JRN. For moreinformation, seeDistribution of Librarieson ASPs [page 72].

...

ASP of SAP<SID>71 andSAP<SID>71<nn>

Auxiliary Storage Pool (ASP) for thekernel library SAP<SID>71. Formore information, see Distribution ofLibraries on ASPs. [page 72]

...

3.2 Hardware and Software Requirements

You check that your hosts meet the hardware and software requirements for your operating systemand the SAP instances.

Caution

If your hosts do not fully meet the requirements, you might experience problems when workingwith the SAP system.

The Java-based SAPinst graphical user interface (GUI) called SAPinst GUI requires a Java DevelopmentKit (Java™ 2 SDK, Standard Edition) with graphical capabilities (AWT, Swing). Since IBM DB2 fori5/OS does not provide a graphical user interface, you must install the JDK on a 32-bit Windowshost to perform the installation with SAPinst.

12/08/2008 PUBLIC 43/146


Note

Some Java VMs might not have essential libraries needed to run the SAPinst GUI: If you haveproblems starting the GUI, download the latest SUN JVM release.

Prerequisites

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.

Process Flow

1. Check the Product Availability Matrix at http://service.sap.com/pam for supported operatingsystem releases.

2. Check the hardware and software requirements using:n The Prerequisite Checker:l Standalone (optional) before the installation process

For more information, see Running the Prerequisite Checker Standalone [page 45].l Integrated in the installation tool (mandatory) as part of the installation process

For more information, see Running SAPinst [page 90].

Note

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

n The hardware and software requirements checklists for:l Standard system [page 48]

Note

These requirements also apply if you want to install the Application Sharing Server as anOptional Standalone Unit.

l Distributed system [page 48]l High availability system [page 50]l If you want to install additional application server instances, check the requirements for

an additional application server instance [page 53].l If you want to install the host agent on a host that does not have an SAP component, check

the requirements for the host agent as a separate installation [page 54].3. If you are installing a production system, the values provided by the Prerequisite Checker and the

hardware and software requirements checklists are not sufficient. In addition, do the following:n You use the SAP Quick Sizer tool available at http://service.sap.com/sizing.

For more information about the SAP Quick Sizer and available sizing guides, see theMaster Guide ‒SAP NetWeaver 7.0 at http://service.sap.com/installnw70 Planning .

44/146 PUBLIC 12/08/2008







http://service.sap.com/installnw70


n You contact your hardware vendor, who can analyze the load and calculate suitable hardwaresizing depending on:l The set of applications to be deployedl How intensively the applications are to be usedl The number of users

3.2.1 Running the Prerequisite Checker in Standalone Mode(Optional)

Before installing your SAP system, you can run the Prerequisite Checker in standalone mode to check thehardware and software requirements for your operating system (OS) and the SAP instances.

Recommendation

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 thehardware and software requirements in the background.

Prerequisites

n You have prepared the Installation Master DVD on the required installation host [page 81].

Procedure

1. You start SAPinst [page 90].2. On theWelcome screen, choose <SAP System> Software Life-Cycle Options Additional Preparation

Tasks Prerequisites Check .3. Follow the instructions in the SAPinst dialogs and enter the required parameters.

Note

For more information about each parameter, position the cursor on the parameter field andchoose F1 in SAPinst.

When you have finished, the Parameter Summary screen appears summarizing all parameters you haveentered. If you want to make a change, select the relevant parameters and choose Revise.

4. To start the Prerequisite Checker, choose Start.

ResultThe Prerequisite Check Results screen displays the results found. If required, you can also check the resultsin file prerequisite_checker_results.html, which you can find in the installation directory.

12/08/2008 PUBLIC 45/146


3.2.2 Hardware and Software Requirements on System i

Purpose

If you have any questions, contact the person in charge of the installation, your Competence Center,or your local IBM representative.You check the network requirements. For more information, see the documentationNetwork Integrationof SAP Servers on SAP Service Marketplace at http://service.sap.com/network.The following table lists the requirements for an SAP system installation on IBM DB2 for i5/OS:

Hardware and Software Requirements

Requirement How to check

HardwareRequirements

n DVD driven Before installing an SAP system on System i, you must obtain detailed sizing

information from your IBM representative.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 81].

Operating SystemRequirements

This product is released for i5/OS V5R4M0, V5R4M5 and V6R1M0.For information about which operating system versions have been released for SAP onIBM DB2 for i5/OS, see SAP Note 410783. For more information about V5R4, see SAPNote 853564. For more information about IBM i 6.1, see SAP Note 1148480.PTF and Information APARFor the latest information on cumulative PTF package (CUM package) release levelsand operating system corrections related to SAP products on IBM DB2 for i5/OS, referto IBM Information APAR II14126 (V5R4M0), APAR II14319 (V5R4M5) and APARII14362 (V6R1M0).To load an APAR onto your System i via the IBM ECS link, enter:SNDPTFORD PTFID((<Info APAR ID>))

ExampleTo load the IBM Info APAR, enter:SNDPTFORD PTFID(II14126) for V5R4

For information about the releases and PTFs for SAP on System i and the addresswhere you can find the Info APARs, see SAP Note 83292.

CautionMake sure that English is installed as the primary or secondary language. For moreinformation, see Installing English as a Secondary Language [page 79].

To be able to run an SAP system on System i with ASCII code pages, make sure thatyou have installed the following: 5722SS1 option 21‒ Extended NLS Support. Thisoption is delivered to you by IBM with the installation DVDs of the operating system.For more information about how to install the secondary language, see the IBMdocumentation AS/400 National Language Support (SC41-5101-01).Other Products

46/146 PUBLIC 12/08/2008

http://service.sap.com/network








Requirement How to check

The following products are required:

Notexx = 22 (V5R4) and xx = 61 (IBI i 6.1)

n 57xxTC1 option *BASE IBM TCP/IP Connectivity Utilities for iSeriesn 57xxSS1 option *BASE i5/OSn 57xxSS1 option 1 ‒ Extended Base Supportn 57xxSS1 option 2 ‒ Online Informationn 57xxSS1 option 3 ‒ Extended Base Directory Supportn 57xxSS1 option 12 ‒ Host Serversn 57xxSS1 option 13 ‒ System Openness Includesn 57xxSS1 option 21 ‒ Extended NLS Supportn 57xxSS1 option 30 ‒ Qshell Interpretern 57xxSS1 option 33 ‒ Portable Application Solutions Environment (PASE)n 57xxJC1 option *BASE IBM Toolbox for Javan 57xxJV1 option *BASE IBM Developer Kit for Javan 57xxJV1 option 7 Java Developer Kit 5.0n 57xxJV1 option 6 Java Developer Kit 1.4

Space Requirements The amount of space required for an SAP system on System i is dependent on manyvariables, such as:n Size of the databasen Number of work processesn Number of usersSizing recommendations are made by the IBM Competency Center. We recommendthat ASP (auxiliary storage pool) usage in SAP production systems should not exceed70%.

Installation HostRequirements

Windows 32-bit operating system or Linux 32-bit operating system.

Front EndRequirements

SAP systems on System i support the following front end products:n Windows NT/2000/2003/XPn Windows 95/98/Men Linuxn IBM Network Station with WinCenterTo connect front ends, you require an Ethernet LAN adapter.

Other Requirements Make sure the local relational database name (RDB name) of your system equals thehost’s TCP/IP. To do so, compare the following values:n On a WRKRDBDIRE screen, use the relational database name where remote

location equals *LOCAL.n On a CHGTCPDMN command prompt, look at the value of host name.For more information, see Adjusting the Relational Database Name (RDB name) [page 79].

12/08/2008 PUBLIC 47/146


DB2 for i5/OS

The DB2 for i5/OS is fully integrated into the operating system and is always available. No separateinstallation phase is required for the database code and database tools and there is no need to startor stop the RDBMS.

3.2.3 Requirements for a Standard System

Hardware Requirements

Requirement Values and Activities

Hard disk space n Hard disk drives with sufficient space for the SAP system and the databaseFor more information, see SAP Directories [page 58].

n 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk. For more information, see Preparing theInstallation DVDs [page 81].

n 1.2 GB of temporary disk space for the installation.

Minimum RAM 2 GB

Software Requirements


Network File System(NFS)

If application servers are installed decentralized, Network File System (NFS) mustbe installed.

Fonts and code pages Make sure that the required fonts and code pages are installed.

National LanguageSupport (NLS)

Make sure that National Language Support (NLS) and corresponding saplocalesare installed.

3.2.4 Requirements for a Distributed System

The following sections provide information about the hardware and software requirements for adistributed system, where the following SAP instances can reside on different hosts:

n Central services instance [page 49]n Database instance [page 49]n Primary application server instance [page 50]

Note

If you install multiple SAP system instances on one host, you need to add up the requirements.

48/146 PUBLIC 12/08/2008


3.2.4.1 Requirements for a Central Services Instance

The central services instance host must meet the following requirements for the central servicesinstance:



Hard disk space n Hard disk drives with sufficient space for the central services instanceFor more information, see SAP Directories [page 58].

n 4.3 GB of temporary disk space for every required installation DVD that youhave to copy to a local hard diskFor more information, see Preparing the Installation DVDs [page 81].


Minimum RAM 1 GB




Network File System (NFS) must be installed.

3.2.4.2 Requirements for the Database Instance

The database host must meet the following requirements:



Hard disk space n 4.5 GB of temporary disk space for every requiredinstallation DVD you have to copy to a local harddisk.

n 25 GB for the ABAP databasen 5 GB for the Java databasen 1.2 GB of temporary disk space for the installation.

NoteYou must take into account additional space forjournalling and the SQL packages.

Minimum RAM 2 GB

12/08/2008 PUBLIC 49/146


3.2.4.3 Requirements for the Primary Application ServerInstance

The host where the primary application server instance runs must meet the following requirements:



Hard disk space n Hard disk drives with sufficient space for the primary application serverinstance.For more information, see SAP Directories [page 58].

n 4.3 GB of temporary disk space for every required installation DVD thatyou have to copy to a local hard disk. For more information, see Preparingthe Installation DVDs [page 81].


Minimum RAM 1 GB





Required fonts and codepages

Make sure that the required fonts and code pages are installed.



3.2.5 Requirements for a High Availability System

The following sections provide information about the hardware and software requirements fora high-availability system, where the following SAP instances can reside on different hosts or on aswitchover cluster infrastucture:

n Enqueue replication server instances [page 51]n Database instance [page 52]n Primary application server instance [page 52]

3.2.5.1 Requirements for a Central Services Instance

The central services instance host must meet the following requirements for the central servicesinstance (SCS):

50/146 PUBLIC 12/08/2008







Minimum RAM 1 GB





3.2.5.2 Requirements for an Enqueue Replication ServerInstance

The host on which an enqueue replication server instance runs must meet the followingrequirements:

Note

The enqueue replication server instance is only required for high-availability systems.You need one ERS for each Java SCS and one ERS for each ABAP SCS (ASCS) installed in your system.






Minimum RAM 1 GB

12/08/2008 PUBLIC 51/146






3.2.5.3 Requirements for the Database Instance

The database host must meet the following requirements:



Hard disk space n 4.5 GB of temporary disk space for every requiredinstallation DVD you have to copy to a local harddisk.

n 25 GB for the ABAP databasen 5 GB for the Java databasen 1.2 GB of temporary disk space for the installation.

NoteYou must take into account additional space forjournalling and the SQL packages.

Minimum RAM 2 GB

3.2.5.4 Requirements for the Primary Application ServerInstance

The host where the primary application server instance runs must meet the following requirements:



Hard disk space n Hard disk drives with sufficient space for the primary application serverinstance.For more information, see SAP Directories [page 58].



Minimum RAM 1 GB

52/146 PUBLIC 12/08/2008






Required fonts and codepages

Make sure that the required fonts and code pages are installed.



3.2.6 Requirements for an Additional Application ServerInstance

The additional application server host must meet the following requirements:



Hard disk space n Hard disk drives with sufficient space for the additional application serverinstance.For more information, see SAP Directories [page 58].



Minimum RAM 1 GB



SAP kernel Make sure that the SAP kernel of the primary application server instance has atleast the patch level of the SAP kernel on the SAP Kernel DVD that is used for theinstallation of the additional application server instance.We recommend that you apply the most current SAP kernel from the SAP ServiceMarketplace at http://service.sap.com/swdc.



12/08/2008 PUBLIC 53/146

http://service.sap.com/swdc

3 Preparation3.3 Specifying Virtual Host Name(s)

3.2.7 Requirements for a Standalone Host Agent

If you want to install a standalone host agent, the installation host has to meet the followingrequirements:



Hard Disk Space n Minimum disk spaceFor information about the required disk space per file system, see Setting Up FileSystems [page 58]

n 4.3 GB of temporary disk space for every required installation DVD that you haveto copy to a local hard disk. For more information, see Preparing the Installation DVDs[page 81].


Minimum RAM 0.5 GB





3.3 Specifying Virtual Host Name(s)

You can use one or more virtual TCP / IP host names for SAP servers within an SAP server landscapeto conceal their physical network identities from each other. This can be useful when quickly movingSAP servers or complete server landscapes to alternative hardware without having to reinstallor reconfigure.If you want to use a virtual host name, you have to set the environment variableSAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst.If you do not set this environment variable now, you can specify an equivalent parameter for thevirtual host name when you run SAPinst (see Running SAPinst [page 90]).

Procedure

3.4 Performing Switchover Preparations for High Availability

Do the following to prepare the switchover cluster:

54/146 PUBLIC 12/08/2008

3 Preparation3.5 Preparing User Management for an External ABAP System

Procedure

1. Make sure that the virtual host name [page 90] can be correctly resolved in your Domain NameSystem (DNS) setup.

2. Assign the virtual IP addresses and host names for the SCS instance, and (if required) NFS toappropriate failover groups.

Note

For more information on virtual addresses and virtual host names and how to assign resources tofailover groups, ask your HA partner.

3.5 Preparing User Management for an External ABAP System

For a Java system, you can also deploy user management for an external ABAP system. In this case,you configure the User Management Engine (UME) of Application Server Java (AS Java) for theuser management of a separate ABAP system.If you want to connect more than one Java system to the same ABAP system, you need to work out aconcept for the communication, administrator, and guest users for each system.You can take one of the following approaches:

Approach Advantages Disadvantages

Each Java system uses differentusers

No interdependencies between theconnected engines

Initially more administration tocreate the users in the ABAP system

All Java systems use the sameconfiguration

You create the users only once andenter the same information forevery Java systems that you install.

Interdependencies between theconnected engines:n If you change the password of

any of the users on the ABAPsystem, this change affects allconnected engines.

n If you change the administratoruser’s password, you must alsochange the password in securestorage on all of the connectedJava systems

Recommendation

For security reasons, we recommend the first approach.

The procedures below assume that you are using the first approach.

Prerequisites

n The ABAP system is based on at least SAP Web AS ABAP release 6.20 SP25.

12/08/2008 PUBLIC 55/146


n In transaction PFCG, check that the roles SAP_BC_JSF_COMMUNICATION andSAP_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 For more information, see the SAP Library [page 14]:

Function-Oriented View Security Identity Management Identity Management of the Application Server JavaUser Management Engine .

Note

For more information about role maintenance, see the SAP Library [page 14] atFunction-Oriented View Security Identity Management Identity Management of the Application Server

ABAP AS ABAP Authorization Concept .

Administration of the ABAP systemPerform the following administration steps in the ABAP system:

1. In transaction SU01, create a new communication user and assign it to the roleSAP_BC_JSF_COMMUNICATION_RO.

Recommendation

We recommend that you assign this user the role SAP_BC_JSF_COMMUNICATION_RO for read-only(display) access to user data with Java tools. If you intend to maintain user data (that is, to change,create, or delete users) with Java tools, you need to assign the role SAP_BC_JSF_COMMUNICATIONinstead.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 betweensystems 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 youradministrator user in AS Java.

Recommendation

We recommend that you name the user J2EE_ADM_<SAPSID_Java_System>. You can use anypassword.

Caution

Log on to the SAP system once with this user to change its initial password. Since the installer ofAS Java verifies this password, the installation fails if this password is initial.

56/146 PUBLIC 12/08/2008


3. In transaction SU01, create a new dialog user and assign it to role SAP_J2EE_GUEST. This is yourguest user in AS Java.

Recommendation

We recommend that you name the user J2EE_GST_<SAPSID_Java_System>. You can use anypassword.Since this user is only used for anonymous access to the system, we recommend you to deactivatethe password and, if required, lock it after installation to prevent anyone from using it for explicitnamed logons.

4. In transaction SU01, create the following dialog users:

Caution

You must have changed the initial passwords of these users before you start the installation ofthe 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 installationmust be identical to this user.

Recommendation

We recommend that you name this user SLDDSUSER

n SLD ABAP API user (optional):You only have to create this user if you want to install System Landscape Directory (SLD). TheSLD ABAP API user name that you enter later on during the Java system installation must beidentical to this user.

Recommendation

We recommend that you name this user SLDAPIUSER

Note

For more information about SLD users and security roles, see the SAP Library [page 14] atAdministrator’s Guide Technical Operations for SAP NetWeaver Software Life-Cycle Management

Configuring, Working with and Administering System Landscape Directory Administrating the SLD .

12/08/2008 PUBLIC 57/146

3 Preparation3.6 Setting Up File Systems

Activities for the Java SystemPerform the following steps in the Java system:

1. Before the installation of the Java system, make sure that you have the correct user names andpasswords 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 andpasswords in the corresponding SAPinst dialogs.

3.6 Setting Up File Systems

The following section(s) describe how to set up SAP file systems for the SAP instances on operatingsystem level:

Note

The installation of any SAP system does not require a special file system setup or separate partitions.

n SAP Directories [page 58]n Host Agent Directories [page 62]

3.6.1 SAP Directories

Here we describe the directories of a typical SAP system.SAPinst creates the following types of directories:

n Physically shared directories, which reside on the global host and are shared by QFileSvr.400n Logically shared directories, which reside on the local host(s) with symbolic links to the global hostn Local directories, which reside on the local host(s)

FeaturesThe following figure shows the directory structure of the SAP system:

58/146 PUBLIC 12/08/2008


Figure 10: Directory Structure for a Java System

Figure 11: Directory Structure for the Diagnostics Agent

Physically Shared Directories

SAPinst creates the following directories:

12/08/2008 PUBLIC 59/146


n The directory /<sapmnt>/<SAPSID>, which contains SAP kernel and related files, is created on thefirst installation host. Normally, the first installation host is the host on which the central servicesinstance is to run, but you can also choose another host for /<sapmnt>/<SAPSID>.You need to manually share this directory with QFileSvr.400 and ‒ for a distributed system ‒ linkit from the other installation hosts.SAPinst creates the following shared directories during the SAP system installation:

l global

Contains globally shared data

l profile

Contains the profiles of all instances

l exe

Contains executable kernel programsFor Java:

l jdbc

Contains the JDBC driver to connect to the Java database on System il j2ee(deprecated)

Contains data to run the Java EE Server using IBM Classic JVMn The directory /usr/sap/trans, which is the global transport directory.

If you want to use an existing transport directory, you have to make it available with QFileSvr.400before you install the application server instance in question. Otherwise SAPinst creates/usr/sap/trans locally.For more information about the global transport directory, see Setting Up the Transport Directory[page 112].

Directory Required Disk Space

<sapmnt>/SAPSID> n Primary application server instance:1.5 GB

n Central services instance:1.0 GB

/usr/sap/trans This value heavily depends on the use of your SAP system.For production systems, we recommended to use as much free space as available (at least2.0 GB), because the space requirement normally grows dynamically.For the installation, it is sufficient to use 200 MB for each SAP system instance. You canenlarge the file system afterwards.

Logically Shared Directories

SAPinst creates the directory /usr/sap/<SAPSID>/SYS on each host. The subdirectories containsymbolic links to the corresponding subdirectories of /<sapmnt>/<SAPSID> on the first installationhost, as shown in the figure above.Whenever a local instance is started, the sapcpe program checks the executables against those in thelogically shared directories and, if necessary, replicates them to the local instance.

60/146 PUBLIC 12/08/2008


Local Directories (SAP System)

The directory /usr/sap/<SAPSID> contains files for the operation of a local instance as well assymbolic links to the data for one system.This directory is physically located on each host in the SAP system and contains the followingsubdirectories:

n SYS

Note

The subdirectories of /usr/sap/<SAPSID>/SYS have symbolic links to the correspondingsubdirectories of /<sapmnt>/<SAPSID>, as shown in the figure above.

n <INSTANCE> for each instance installed on the hostThe instance-specific directories have the following names:l The directory both of the primary application server instance and of an additional application

server instance is called J<Instance_Number>.l The directory of the central services instance is called SCS<Instance_Number>.l The directory of the Enqueue Replication Server instance is called ERS<Instance_Number>.


/usr/sap/<SAPSID> Primary application server instance or additional application server instance:2.5 GB

Local Directories (Diagnostics Agent)

The directory /usr/sap/<SMDSID> contains files for the operation of a local Diagnostics Agentinstance.This directory is physically located on each host in the SAP system and contains the followingsubdirectories:

n exe

Contains the following global scripts:

n <INSTANCE>

The directory of the Diagnostics Agent is called J<Instance_Number>

This directory contains the Instance-specific data of the Diagnostics Agent.Contains the following subdirectories:

l profile

Contains the smd.properties file

l sapinst

Contains log files of the installation

l SMDAgent

Contains the Diagnostics Agent software and properties files.

l work

This is the work directory of the Diagnostics Agent

12/08/2008 PUBLIC 61/146

3 Preparation3.7 Installing the Toolbox JDBC Driver

n SYS

l profile

Contains the profiles of the Diagnostics Agent instance


/usr/sap/<SMDSID>/J<instance_number>

/usr/sap/<SMDSID>/SYS/profile

/usr/sap/<SMDSID>/exe

500 MB

3.6.2 Host Agent Directories

For the host agent, the following directories are required:

Directories Description Required Disk Space

/usr/sap/hostctrl Contains the following directories:n exe

Contains the profilehost_profile

n work

Working directory of the hostagent

70 MB

3.7 Installing the Toolbox JDBC Driver

All database access from Java occurs through the JDBC API (Java Database Connectivity).Implementations of this are called JDBC driver. The JDBC driver typically runs on the applicationserver. SAP certifies one JDBC driver for access to System i:

n IBM Toolbox for Java JDBC Driver also referred to as Toolbox JDBC driver (part of license product5722JC1)Toolbox JDBC driver is a type 4 JDBC driver. That means that it is completely written in Java. It istherefore OS-independent. SAP certifies this driver for the following:l Local (two-tier) access from a System i to a System i databasel Remote (three-tier) access from any platform that was certified by SAP for SAP NetWeaver to

a System i database

Note

IBM Developer Kit for Java JDBC driver also referred to as the Native JDBC driver (part of licenseproduct 5722JV1) is not supported for SAP NetWeaver 7.1 running SAP JVM.

62/146 PUBLIC 12/08/2008

3 Preparation3.7 Installing the Toolbox JDBC Driver

Prerequisites

Toolbox JDBC Driver

n Make sure that the QUSER profile is enabled. To do so, log on as user QSECOFR and enter thefollowing command:CHGUSRPRF USRPRF(QUSER) STATUS(*ENABLED)

n You need to start the DDM TCP/IP server and host servers after each IPL. To do so, proceedas follows:l To start the DDM TCP/IP server, enter the following command:

STRTCPSVR SERVER(*DDM)

l To start host servers, enter the following command:STRHOSTSVR SERVER(*ALL)

Note

You might want to start server jobs automatically after each IPL. For more information, seeAdjusting Startup Program QSTRUP [page 69].

Procedure

Note

The Toolbox JDBC driver is installed with license product 5722JC1(V5R4) and 5761JC1(IBM i 6.1) . Youmust follow the patch strategy described in the respective IBM Information APAR (V5R4 or higher)to get the current correction level of the supported System i JDBC driver.

Since you use the Toolbox JDBC driver that is not supplied by a PTF but that has to be downloadedfrom an IBM web page, we recommend that you do not overwrite the Toolbox product. Instead,proceed as follows:

1. Log on to your database server as user <SID>ADM.2. Follow the download instructions in the respective Information APAR.3. Extract the patch into an arbitrary directory on your database server, for example:

/sapmnt/jdbc/toolbox/jt400.jar

4. During the installation process, choose Toolbox JDBC driver and specify the directory you havechosen above. In the above example, this is the following directory:/sapmnt/jdbc/toolbox

Note

The installation process copies the Toolbox JDBC driver into the directory\usr\sap\<SID>\SYS\jdbc\tbx. You have to maintain this JDBC driver for your SAP systemin this directory. If you have several SAP systems using the Toolbox JDBC driver you have tomaintain the driver individually for every SAP system.

12/08/2008 PUBLIC 63/146

3 Preparation3.8 Qp2Term, Qp2Shell and the i5/OS Portable Application Solution Environment

3.8 Qp2Term, Qp2Shell and the i5/OS Portable ApplicationSolution Environment

The i5/OS Portable Application Solution Environment (PASE) delivers similar UNIX command lineflexibility as the Qshell interpreter.i5/OS PASE is more than just a shell interpreter, it is an entire programming environment based onthe AIX Application Binary Interface.The Qp2Term program runs an interactive terminal application on the System i, similar to theQshell command line. The Qp2Shell programs allow you to execute a shell script or an i5/OS PASEapplication. Qshell accomplishes these features by a command wrapper which either starts the Qshellcommand line, or executes scripts non-interactively.You call the i5/OS Qp2Term and Qp2Shell programs by using the i5/OS CALL mechanism.

Recommendation

We recommend that you use i5/OS Qp2Term instead of QShell.

ProcedureIf not already installed, install option 33 of the license program 5722SS1(V5R4)and 5761221(IBM i 6.1), the i5/OS Portable Application Solution Environment. Formore information about Qp2Term, Qp2Shell and installing the i5/OS PASE, seehttp://www.ibm.com/servers/enable/site/porting/iseries/pase.

3.9 Installing the Qshell

You must install the Qshell on your System i. This gives you a greater flexibility in dealing withstream files because you can use a large set of utilities that are common on UNIX systems, forexample, grep, tail, or ls.In addition, Qshell is compatible with ksh scripts in UNIX.

Procedure

1. Install option 30 of the Qshell Interpreter (license program 5722SS1(V5R4) and 5761SS1(IBM i 6.1)).

For more information about Qshell and installing the Qshell Utilities and the Qshell Interpreter, seepublib.boulder.ibm.com/iseries. Choose a region and a language. Then search for Qshell.

64/146 PUBLIC 12/08/2008

http://www.ibm.com/servers/enable/site/porting/iseries/pase

3 Preparation3.10 Checking and Adjusting i5/OS System Values

3.10 Checking and Adjusting i5/OS System Values

To allow the SAP system to run optimally on System i, you have to adjust a number of i5/OS systemvalues.

Prerequisites

n You have entered the following command to switch on work control block compression:CHGIPLA CPRJOBTBL(*ALL)

This allows work control block space to be reused.n The recommendations given below for system values QACTJOB, QTOTJOB, QADLACTJ, and

QADLTOTJ assume that only the SAP system is running on the System i. If you are also runningother applications, you might need to preallocate more jobs. The values QACTJOB and QTOTJOB areused for initial space allocation at IPL (initial program load) time for the number of active jobsand the total number of jobs that are in the system at any one time. If the allocated number ofactive or total jobs is reached, the system values QADLACTJ and QADLTOTJ determine how manyadditional jobs are to have space allocated.

n Check and adapt your TCP/IP configuration on System i. For more information, see SAP Note92589.

Caution

Do not forget to perform an IPL after any change. Otherwise your changes do not work.

n You have applied all installed PTFs on your System i. To check this, enter the following command:DSPPTF

PTFs with the state Permanently applied, Temporarily applied or Superseded are integrated in the system orare superseded by a newer PTF. PTFs with another state such as Not applied, Save file only, Damaged,Cover letter only are not currently active. We recommend that you install all required PTFs. Theyshould be applied and active.

n To display all system values, enter the following command:WRKSYSVAL SYSVAL(*ALL) OUTPUT(*PRINT)

n To display or change individual system values, enter the following command:WRKSYSVAL SYSVAL(<system_value_name>)

and enter option 5 (Display) or option 2 (Change).After changing a system value, enter option 5 (Display) to check your changes.

Note

To avoid having to run an IPL (initial program load) several times, we recommend that you delaythe IPL until you have made all the necessary changes to the system values and, if necessary,have added a user ASP [page 73].

12/08/2008 PUBLIC 65/146



Checking and Adjusting i5/OS System Values

System Value RecommendedValue Description

QACTJOB 1000 Set system value QACTJOB to a value close tothe number of jobs usually on your system.(To find out the number of jobs, enter thecommand WRKACTJOB. For a two-tier system,this is about 1000).

QTOTJOB 2000 Set system value QTOTJOB to 2000. Whenyou have worked with the SAP system fora while, adjust this value to the value youusually see in the field Jobs in system on theWRKSYSSTS command.

QADLACTJ

andQADLTOTJ

5001000

Set system value QADLACTJ to 500 and systemvalue QADLTOTJ to 1000.

QSECURITY 30 or 40 System value QSECURITY controls the levelof security enforced on your system. SetQSECURITY to at least 30 to ensure objectsecurity for the SAP objects to be installed.Security levels 10 and 20 are theoreticallypossible. However, we do not recommendthat you use either of these values. Securitylevel 10 provides neither password norobject protection. Security level 20 providesno object protection.To activate this system value, you mustperform an IPL (initial program load).

QCTLSBSD QCTL When you start your System i, the programspecified in system value QSTRUPPGM(QSTRUP)is called. This startup program is responsiblefor starting the subsystems.When this startup program runs,system value QCTLSBSD is queried. Thespecifications made for this value decidewhether subsystem QBASE or subsystemsQCTL,QINTER,QBATCH,QSPL,QCMN, andQSERVER are started.Two settings are possible for system valueQCTLSBSD (controlling subsystem):n QBASE

The controlling subsystem is QBASE.Subsystem QBASE is started.

n QCTL

The controlling subsystemis QCTL. SubsystemsQCTL,QINTER,QBATCH,QSPL,QCMN,QSERVER

are started. Your change is activated thenext time the System i is started. To

66/146 PUBLIC 12/08/2008



activate the subsystems, you have torestart the System i.

QDATE Check the system date and adjust ifnecessary. (The date format is determinedby system value QDATFMT.)

QTIME Check the system time and adjust it ifnecessary.

QJOBMSGQFL *WRAP or *PRTWRAP System value QJOBMSGQFL allows you tospecify how you wish the job message queueto be handled if it overflows. The defaultvalue is *NOWRAP. If this value is set, theSystem i sends a message when the queueis full and ends the job that is currentlyrunning. When an SAP system is installed, alarge amount of information is sent to thejob message queue. For this reason, systemvalue QJOBMSGQFL is automatically changedto *WRAP during installation. If the queuebecomes full, the oldest entries are deletedand the current job is not interrupted.Once the installation is complete, thesystem value is automatically returned toits original value.

QPFRADJ 0 If you have adjusted the size of the System ipools as described in SAP Note 49201, youhave to set the system value QPFRADJ to 0.This deactivates automatic performanceadjustment and prevents your settings frombeing lost after an IPL.

QSTRUPPGM To cause your adjusted startup program tobe started after an IPL (initial program load),change Startup program to QSTRUP and Libraryto QGPL.

QAUTOCFG 1 Set system value QAUTOCFG to 1 to allowdevice descriptions to be configuredautomatically.

QBASACTLVL Use the following formulas:JavaJava server:(number of servers) * 700

QBASACTLVL is the activity level of the basestorage pool. This value indicates howmanysystem and user threads can compete at thesame time for storage in the base storagepool. This pool is specified in the subsystemdescriptions as *BASE. QBASACTLVL dependson the types of jobs run in this storage pool.The lower limit for QBASACTLVL is 1.Note: This value does not affect only SAPwork processes but also processes and

12/08/2008 PUBLIC 67/146




threads that belong to other applicationsrunning on your system.Since the Java processes contains morethan 100 threads we strongly recommendthat you adjust the Max Act (MaximumActive) value of the memory pool yourJava processes are running in. To do this,enter command WRKSYSSTS and edit theparameter Max Act or enter commandWRKSYSVAL with Option 2 to change systemvalue QBASACTLVL. The change becomesactive immediately. As a rule of thumb, youhave to add to your current Max Act valuea number of 700 for each SAP Java serverprocess you start on your System i.

ExampleWhen you install one Java only systemon your System i, this system has at thebeginning only one Java server (calledserver0). At that point you have to add 700to your current Max Act value. When youlater reconfigure your Java only system tohave two Java servers running in parallel(server0 and server1) you have to add onceagain 700 to your current Max Act value.Finally in total you have added 1400 to MaxAct value.

NoteIn the past the Max Act value had aninfluence on the database optimizer, butthis has changed.

Changing TCP Buffer Size:

1. To change the following values, enter the following command:CHGTCPA

Set value TCPRCVBUF to 1048576 or higherSet value TCPSNDBUF to 1048576 or higher

2. To activate the changes, restart TCP/IP by entering the following commands:ENDTCP

STRTCP

or perform an IPL.

For more information, see SAP Note 484548 and 92589.

68/146 PUBLIC 12/08/2008



3 Preparation3.11 Adjusting Startup Program QSTRUP

ResultYou have made the necessary adjustments to System i values to enable the SAP system to runcorrectly on System i.

Note

When a new SAP system is created a special entry is made automatically in the System Reply List.These entries make sure that changes of tables attributes work without problems. Do not change ordelete this entry after the installation!

System Reply List Entries

Sequence Number Message ID Reply

3201 CPA32B2 I

3.11 Adjusting Startup Program QSTRUP

Starting SAP Instances Automatically

The program SAPINIT parses the file /usr/sap/sapservices. The files contain entries for all instanceson the host whose sapstartsrv is started automatically after the SAPINIT call. The SAPINIT hasbeen moved to library R3SAP400 and is now part of the SAP Host Agent. The SAPINIT program isalso now automatically started when the QUSRWRK is initially started at IPL, so the additional entryQSTRUP is not needed.

Starting the Job QXDAEDRSQL Automatically

The job QXDAEDRSQL is a prerequisite for working with the SAP system. It is required for the followingtasks:

n Calling APIs from the ABAP Dictionary and from CCMS (Computing Center ManagementSystem)

n Transports between different System i systems

To start the job QXDAEDRSQL automatically after each IPL, enter the following code into programQSTRUP:

n STRTCPSVR SERVER(*EDRSQL)

n MONMSG MSGID(CPF0000)

Creating the Subdirectories of /QFileSvr.400 Automatically

All SAP instances of an SAP system share one JDBC driver file. The SAP instances get access to this filevia /QFileSvr.400. Every instance host needs subdirectories in /QFileSvr.400 for itself and everyother System i host that is part of the SAP system.

12/08/2008 PUBLIC 69/146


Example

Your system PRD consists of instances J00, J01. Your central instance host is AS0001, your databaseinstance host is AS0002 and you have the dialog instance J01 on host AS0003.

Note

All of the three hosts need directories:/QFileSvr.400/AS0001

/QFileSvr.400/AS0002

/QFileSvr.400/AS0003

To create the directories automatically after each IPL, enter the following code into program QSTRUP:

n MKDIR DIR(’/QFileSvr.400/<system host>’)

Example

MKDIR DIR(’/QFileSvr.400/AS0001’)


Starting the DDM TCP/IP Server and Host Servers Automatically

If you use the Toolbox JDBC Driver for your Java or ABAP+Java system, you need to start the DDMTCP/IP server and host servers after each IPL. To start the servers automatically after each IPL, enterthe following code into program QSTRUP:

n STRTCPSVR SERVER(*DDM)


n STRHOSTSVR SERVER(*ALL)


ProcedureSince no source statements are provided for startup program QSTRUP, you have to retrieve the CL(control language) source statements from CL program QSTRUP. This is possible as the parameterRTVCLSRC(*YES) was specified when the program was created.

1. To retrieve the CL source statements, enter the following command:RTVCLSRC PGM(QSYS/QSTRUP) SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP)

If the source statements are retrieved successfully, this message is displayed:CL source retrieved for program QSTRUP in QSYS.

2. To edit the program with EDTF, enter the following command:EDTF FILE(QGPL/QCLSRC) MBR(QSTRUP)

The following is an example of how the program modifications might look:

70/146 PUBLIC 12/08/2008


Example

/* */

/* START ADDITIONAL PROGRAM */

/* */

QSYS/STRSBS SBSD(QSERVER)

MONMSG MSGID(CPF0000)

/* START QXDAEDRSQL JOB */

STRTCPSVR SERVER(*EDRSQL) /* INSERT */

MONMSG MSGID(CPF0000) /* INSERT */

/* START DDM AND HOST SERVERS FOR TOOLBOX JDBC DRIVER */

STRTCPSVR SERVER(*DDM) /* INSERT */


STRHOSTSVR SERVER(*ALL) /* INSERT */


/* CREATE QFILESVR.400 SUBDIRECTORIES */

MKDIR DIR(’/QFileSvr.400/<system host>/’) /* INSERT */


/* */

To leave the editor, press F3 .3. After you have made your changes to the source statements in program QSTRUP, you have to

create the CL program from the source code.

Note

Do not change the original QSTRUP program supplied by IBM. Instead, create a modified versionof QSTRUP in library QGPL. If you do this, the program is not overwritten when an IBM systemupgrade is performed.

To do so, enter:CRTCLPGM PGM(QGPL/QSTRUP) SRCFILE(QGPL/QCLSRC) SRCMBR(QSTRUP)

If the program is created successfully, you receive this message:Program QSTRUP created in library QGPL.

To make sure that your adjusted startup program (and not the default startup program) is startedafter an IPL, adjust system value QSTRUPPGM.For more information, see Checking and Adjusting i5/OS System Values [page 65].

ResultThe programs and jobs you have included in your startup program are started automatically whenyou perform an IPL (initial program load) of your System i.

12/08/2008 PUBLIC 71/146

3 Preparation3.12 Distribution of Libraries on ASPs

To check if TCP/IP is running, enter WRKACTJOB. Look for subsystem QSYSWRK, job QTCPIP. If the job isrunning, the entry in the status column is normally DEQW.

3.12 Distribution of Libraries on ASPs

Disk units that are attached to a System i server are combined into one or multiple auxiliary storagepools (ASPs). You always have an ASP 1, also known as system ASP. Optionally, you can configure oneor multiple additional ASPs. These are called user ASPs.Before you run SAPinst to install your SAP system, you must decide on the following:

n Which ASP you want to use to install new libraries for ABAPn How you want to distribute the libraries that hold the SAP system data on ASPs

Depending on the installation type, you can find the following libraries on the system after theinstallation:

n SAP NetWeaver Java systems:

l SAP<SID>DB

This is the database library for SAP NetWeaver Java.

l SAP<SID>JRN

This is the journal receiver library that is associated with SAP<SID>DB.

You can keep the libraries that contain the database objects and their associated journal receivers indifferent ASPs. This enables data recovery after disk failures that result in a loss of the ASP that isholding the database libraries. This may be desirable for production systems that are not protectedby high availability or disaster recovery solutions based on two independent copies of the databaselibraries. For more information, see SAP Note 654801.The following figure is an example of how the above-mentioned libraries can be distributed:

Figure 12:

72/146 PUBLIC 12/08/2008


3 Preparation3.13 Adding a User ASP

3.13 Adding a User ASP

If you decide to store the database libraries and journal receiver libraries in separate ASPs, makesure that you follow these guidelines:

1. The disk units in the ASP that is holding the journal receiver libraries must be protected bymirrored protection or a different parity set than the disk units in the ASP that is holding thedatabase libraries.

2. For performance reasons, the ASP that is holding the journal receiver libraries should have aminimum of three disk arms.

3. The ASP that is holding the journal receivers should be large enough to hold all journal receiversthat are generated while your SAP system is running, until the receivers can be detached, saved,and deleted. If the journal receivers grow too quickly and the ASP is full, some data mightoverflow into the system ASP. In this state, you can no longer perform data recovery after diskfailures that result in the loss of the system ASP.

Before you can specify a different ASP during the SAP installation, you must configure the ASP ini5/OS and assign disk units to it. The procedure consists of two steps:

1. You check if user ASP has been set up and if it has been assigned sufficient space.2. You add or extend a user ASP if required.

Checking the User ASP

1. Enter STRSST (Start System Service Tools).2. Sign on with a valid service tools user ID and password.3. Enter option 3 (Work with disk units).4. Enter option 2 (Work with disk configuration).5. Enter option 1 (Display disk configuration).6. Enter option 2 (Display disk configuration capacity).

You can see whether a user ASP exists and if it contains enough disk units. On the Display diskconfiguration screen, you can also use option 5 (Display device parity status) to verify that your userASP is in a separate parity set.

Note

In early releases of OS/400, user ASPs could only contain objects of type journal receiver or savefile. The libraries to address these objects where kept in the system ASP. If an existing user ASPcontains journal receivers or save files, while the library that contains these objects is in thesystem ASP, you cannot create additional libraries in this user ASP and the installation fails. If youhave sufficient disk space, we recommend that you work around this problem by adding a seconduser ASP (for example, ASP 3). The alternative would be to remove the old journal receivers orsave files from the user ASP, or to create the SAP journal receivers in the system ASP. For more

12/08/2008 PUBLIC 73/146

3 Preparation3.14 Configuring TCP/IP

information, see the IBM documentation OS/400 Backup and Recovery (SC41-5304).Adding a User ASP

1. Perform a manual IPL (Initial Program Load) of your System i.n Set the mode to manual on the control paneln Enter the following command:

PWRDWNSYS *IMMED RESTART(*YES)

2. Enter option 3 (Use Dedicated Service Tools (DST)) from the menu that appears.3. Sign on by entering your DST user and password.4. Enter option 4 (Work with disk units).5. Enter option 1 (Work with disk configuration).6. Enter option 3 (Work with ASP configuration).7. Enter option 6 (Move units from one ASP to another).8. Specify the ASP to which you wish to move specific units by entering the number of the ASP next

to the relevant unit in the column New ASP.9. Choose ENTER .10. In the next screen, choose ENTER to confirm that you want to continue.

The Confirm Move of Units screen appears.11. To confirm your choices, choose ENTER .

Note

Moving units takes several minutes.

12. Continue the procedure and complete the IPL.13. Switch back to normal mode.

3.14 Configuring TCP/IP

This section describes how to integrate System i into your TCP/IP network.

PrerequisitesBefore configuring TCP/IP, you must do the following:

n Make sure that you have the following information:l The interface of your System i to which the Local Area Network is attachedl The IP addresses of your System i, subnet mask, and router or gatewayl The local domain name

l The System i host namen Decide on your System i host name. The host name cannot be longer than eight characters

although SAP allows thirteen characters starting with Release 4.6 and higher.For more information, see SAP Note 611361.

74/146 PUBLIC 12/08/2008

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=Note 611361&_NLANG=en&_NVERS=0


Note

The TCP/IP configuration on System i is case sensitive. Do not enter your host name once inuppercase and then in lowercase characters. It is important that you enclose your host nameentry in single quotation marks. Otherwise, the System i interprets the characters as uppercasecharacters.

Note

An IP address is a unique address in a TCP/IP network for a particular System i. A subnet mask is amask used to divide a single network address into multiple logical networks.

1. To change the name of the computer, enter the command chgneta and prompt F4 .You must then enter the following information and choose ENTER :n System namen Local network ID

n Default local location nameThe following screen appears:

Figure 13:

2. To setup the description line, enter the command go hardware and proceed as follows:a) On the Hardware Resources screen, enter option 1 (Work with communication resources) and choose

ENTER .b) On theWork with Communication Resources screen, enter option 5 (Work with configuration descriptions) for

the port and choose ENTER .

12/08/2008 PUBLIC 75/146


c) On theWork with Configurations Description screen, enter option 1 (Create) to enter the descriptiongigaline or ethline and choose ENTER . On the following screen, enter the line speed and duplexand then press F10 and page down two screens.

Figure 14:

On the Create Line Desc (Ethernet) (CRTLINETH) screen, make sure the autocreate controller isset to *yes.

Figure 15:

3. To call the TCP/IP configuration menu, enter the command CFGTCP and proceed as follows:a) To work with interfaces, enter option 1 (Work with TCP/IP interfaces).

The following screen appears:

76/146 PUBLIC 12/08/2008


Figure 16:

You need at least two entries: one for the loopback entry and one for the IP address of yourSystem i.The loopback address always takes the IP address 127.0.0.1, subnet mask 255.0.0.0 andline description *LOOPBACK.To add an entry, enter option 1 (ADD) and choose ENTER .Add entries for the first three fields and accept the default values for the other fields.

b) To work with routes, enter option 2 (Work with TCP/IP routes).The following screen appears:

Figure 17:

If the route to the remote host, in this case the PC workstation, is through a gateway or ifthe remote host resides in a different network or subnetwork to the local host, you need toconfigure a route.

c) To change the domain information, enter option 12 (Change TCP/IP domain information).The following screen appears:

12/08/2008 PUBLIC 77/146


Figure 18:

Note

It is important that you enclose your host name entry in single quotation marks. If you donot, the System i interprets the characters as uppercase characters.

If you have one or more remote name servers, you need to define the IP address here. Note thatthe Host name server prioritymust be set to *LOCAL.

Testing the TCP/IP ConnectionBefore proceeding with the SAP installation (that is, the installation of the executable programs),check that this TCP/IP connection has been set up correctly. To do so, enter the command ping

(Network Connection) specifying your own system as Remote system. Do this twice, once specifyingonly <host_name>, and once <host_name>.<domain_name>.

Example

In this example we assume that the host name is as0008 and the domain name is wdf.sap.corp. In thiscase, your entries are the following:

n ping ’as0008’

n ping ’as0008.wdf.sap.corp’

After installing the SAP system kernel, check the TCP/IP connection again with the command:WRKLNK ’/QFileSvr.400/<host_name>’

Your host name should be displayed under Object link, for example, as0008 for the host in the examplegiven above.For more information about TCP/IP configuration, see the IBM documentation TCP/IP Configuration andReference (SC41-5420).

78/146 PUBLIC 12/08/2008

3 Preparation3.15 Adjusting the Relational Database Name

ResultThe System i is integrated into your TCP/IP network.

3.15 Adjusting the Relational Database Name

You use the following procedure to adjust the local relational database name (RDB name) so it isthe same as the TCP/IP host name.

Note

The *LOCAL database name must match the TCP/IP host name for the SAP system to work properly.

Procedure

1. Log on to your database host as user QSECOFR.2. To display your TCP/IP host name, enter the command CHGTCPDMN, press F4 and then press F11 .3. Search for the contents of HOSTNAME. This is your TCP/IP host name.4. Before you can adjust the local RDB name, you have to check if the entry Remote Location equals

*LOCAL exists. To do this, enter the following command:WRKRDBDIRE

Depending on the outcome proceed as follows:n If an entry for RDB name exists and you want to adjust the name to the TCP/IP host name

<tcp_host_name>, enter the following command:CHGRDBDIRE RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)

RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)

RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)

n If there is no such RDB name, you have to add one with the correct name <tcp_host_name>.To do this, enter the following command:ADDRDBDIRE RDB(<tcp_host_name>)

RMTLOCNAME(*LOCAL *IP) PORT(*DRDA)

RMTAUTMTH(*ENCRYPTED *ALWLOWER) DEV(*LOC) LCLLOCNAME(*LOC)

RMTNETID(*LOC) MODE(*NETATR) TNSPGM(*DRDA)

3.16 Installing English as a Secondary Language

On every System i where English is not the primary language, you must install English as thesecondary language library. This is necessary for SAP to be able to provide support.

12/08/2008 PUBLIC 79/146

3 Preparation3.17 Preparing a System i User Profile

Note

To check if English is already installed on your System i as a secondary language, enterWRKLIB QSYS29* on the System i command line. If one of the following secondary languagelibraries is displayed, you have already installed English as a secondary language library:QSYS2924,QSYS2938,QSYS2959 or QSYS2984.

Procedure

1. On the System i command line, enter GO LICPGM

2. Enter option 21 (install secondary languages).3. Enter option 1 to select any of the following libraries QSYS2924,QSYS2938,QSYS2959 or QSYS2984.

3.17 Preparing a System i User Profile

For the installation you need to create a user account on the System i you want to install.The following requirement apply:

n The System i user profile must have user class *SECOFR and all special authorities that belongto user QSECOFR.

Note

The user name SAPINSTUSR and the password SAP are used in the procedures as examples.

System i:Execute the following command:CRTUSRPRF USRPRF(SAPIUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT(’Test User for SAP

Installation’) SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500)

Note

In previous releases, we recommended that you create the user SAPINST to install the SAP system. Inthe current release, a group SAPINST is created and used for the installation and SAP system. If a userSAPINST already exists on your system, you must delete this user.

Caution

You should not set the system variable QIBM_PASE_CCSID. You should leave this variable empty!

80/146 PUBLIC 12/08/2008

3 Preparation3.18 Generating the SAP Solution Manager Key

3.18 Generating the SAP Solution Manager Key

You need to generate the Solution Manager key because the installation tool prompts for it duringthe installation. Without this key, the installation process cannot continue.For more information, see SAP Note 805390.

Procedure

1. If SAP Solution Manager is not yet available in your system landscape, proceed as follows:a) Order SAP Solution Manager as described in SAP Note 628901.b) Install SAP Solution Manager as described in the documentation Installation Guide ‒ SAP Solution

Manager <release> on <OS>: <Database> which is available at:http://service.sap.com/solutionmanager SAP Solution Manager Installation Guides

Release 4.02. Generate the SAP Solution Manager key as described in SAP Note 811923.

ResultThe SAP Solution Manager system displays the key for which you are prompted during theinstallation of your SAP system.

3.19 Preparing the Installation DVDs

This section describes how to prepare the installation DVDs, which are available as follows:

n You normally obtain the installation DVDs as part of the installation package.n You can also download the installation DVDs from SAP Service Marketplace, as described at

the end of this section.

You need several DVDs during an SAP system installation. We recommend that you copy all relevantDVDs for an instance installation to the IFS of the System i host before you install the instance.Make sure you have configured your TCP/IP as described in SAP Note 92589. Do not forget afterwardsto perform an IPL to make the change effective. Otherwise, copy performance is poor from your localWindows DVD drive to the IFS on your System i.

1. Identify the required DVDs for your installation [page 17] as listed below.Keep them separate from the remaining DVDs as this helps you to avoid mixing up DVDs duringthe installation.

12/08/2008 PUBLIC 81/146








3 Preparation3.19 Preparing the Installation DVDs

Note

n The media names listed in the following table are abbreviated.n You can find the Software Component Archives (SCAs) for the installation of SAP NetWeaver

usage types on the NetWeaver Java DVD.

SAP Instance Installation Required DVDs

Central services instance (SCS) n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Database instance n Installation Master DVDn Kernel DVDn Export DVD

HA only:Enqueue Replication Server

n Installation Master DVDn Kernel DVD

Primary application server instance n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Additional application server instance n Installation Master DVDn NetWeaver Java DVDn Kernel DVD

Host Agent (Standalone) n Installation Master DVDn Kernel DVD

2. Make the required installation media available on each installation host.

Note

Depending on your installation type, one or more instances can reside on the same host. Youneed to keep this in mind when you make the required installation media available on eachinstallation host.For a standard system, you need to make all required installation media available on the singleinstallation host.

Use one of the following methods to make DVDs available:n Before the installation, copy DVDs manually to local hard disks.n During the installation, use the SAPinst Media Browser dialog and copy the entire DVDs to

the path you entered in the Copy To column.

82/146 PUBLIC 12/08/2008

3 Preparation3.19 Preparing the Installation DVDs

Caution

n If you copy the DVDs to disk, make sure that the paths to the destination location of the copiedDVDs do not contain any blanks.

n If you perform a local installation and there is only one DVD drive available on yourinstallation host, you must copy at least the Installation Master DVD to the local file system.However, we recommend that you copy all of the DVDs to your installation host as describedin this section.

3. You need to copy the DVDS manually using the ROOTBIN share [page 84].

Downloading Installation DVDs from SAP Service Marketplace (Optional)You normally obtain the installation DVDs as part of the installation package from SAP.However, you can also download installation DVDs from SAP Service Marketplace at:http://service.sap.com/swdc Download Installations and Upgrades Entry by Application Group

<SAP solution> <SAP product> <SAP release> Installation and Upgrade <operating system><database> .

Note

If you download installation DVDs, note that the DVDs might be split into several files. In this case,you have to reassemble the required files after the download.

Caution

To extract the downloaded SAR files make sure that you use the latest SAPCAR version, which youcan find on SAP Service Marketplace at http://service.sap.com/swdc. You need at least SAPCAR700 or SAPCAR 640 with patch level 4 or higher because older versions of SAPCAR can no longerunpack current SAR files. For more information, see SAP Note 212876.

1. Create a download directory on the host where 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 andan individual sequence number:<material_number>_<sequence_number>

Example

51031387_151031387_2...

12/08/2008 PUBLIC 83/146








3 Preparation3.20 Copying the DVDs Manually Using the ROOTBIN Share

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

3. Download the objects to the download directory.4. Extract the individual download objects using SAPCAR, starting with the lowest sequence number

‒ for example 51031387_1, then 51031387_2, and so on.During the download SAPCAR sets up the structure of the installation DVD.

Note

SAPCAR asks if you want to replace existing files, for example LABELIDX.ASC. Always acceptwith Yes.

3.20 Copying the DVDs Manually Using the ROOTBIN Share

Note

We use the user name SAPIUSR and the password SAP as examples.

Note

This is a secure way to copy DVDs manually into the IFS of your System i.

Note

When you make the DVDs available locally, make sure that the content is copied correctly. Forexample, the content might become corrupted by copying using a converting share or long filenames can be shortened.

1. If you do not already have a binary share ROOTBIN on your System i, you have to create this sharemanually using the iSeries Navigator (OpsNav).

Caution

This is normally done by a System i administrator!

a) Start the iSeries Navigator on your Windows PC.b) Connect to your System i usingMy Connections.c) To create or change the share ROOTBIN choose File Systems File Shares .d) Right-click File Systems Open iSeries Netserver .e) A new screen iSeries Netserver appears. Click the folder Shared Objects to see the shares.f) To check the already existing share ROOTBIN or create a new share ROOTBIN, right-click New

File .g) The share ROOTBIN should have the access permission Read/Write and the Path name should be /.

84/146 PUBLIC 12/08/2008

3 Preparation3.20 Copying the DVDs Manually Using the ROOTBIN Share

h) On the Text Conversion tab, do not select Allow file text conversion.i) To save the share ROOTBIN press OK.

Now you have created a share ROOTBIN on your System i.2. To open the MS DOS screen on Windows, choose Start Run .3. Enter cmd.exe.4. Press OK.

The MS DOS screen appears.5. In the command line of the MS DOS screen, enter net use.

All network connections to shared resources are displayed.6. Check if you have a connection to your System i.

If you find \\<System_i_Hostname>\ROOTBIN in the column Remote and a drive directory letter inthe column Local, you have already established the required connection to your System i.Otherwise, you have to establish this connection. To do this, enter:net use X: \\<System_i_Hostname>\ROOTBIN SAP /USER:SAPIUSR

X: is now your new network drive to share \\<System_i_Hostname>\ROOTBIN to your IFS on theSystem i. If X: is already in use, choose another drive letter that is free.For more information, see Preparing a System i User Profile [page 80].

7. To change to the new network drive, enter X: in the command line of your MS DOS screen.8. Create the subdirectories in your IFS where you want to copy the required DVDs.

For each DVD, enter:mkdir \tmp\<sid>\<DVD_name>

Note

You should avoid spaces in the DVD path name.

9. Copy the installation DVDs from your Windows drive (for example D:\) to the IFS of your Systemi host. Insert the required installation DVDs and enter the following command:For each DVD, enter:xcopy D:\<DVD> X:\tmp\<sid>\<DVD_name> /E

Note

You have to copy the root directory of the DVD and all required DVD subdirectories to theIFS of your System i.

10. For each required DVD, create a subdirectory and copy the required DVDs.

12/08/2008 PUBLIC 85/146


4 Installation

4 Installation

Note

SAPinst uses the UID and GID of the DEFAULT.PFL file in the SAPGLOBALHOST and assumes that theUID belongs to the user <SID>ADM and the GID to the group R3GROUP. To have a successful distributedlandscape installation, you must do the following:

1. Make sure the UID for the user<SID>ADM and the GID for the group R3Group are available acrossall of the system landscape. You can set these values from the SAPinst GUI.

2. After installing the SAPGLOBALHOST, you must check to make sure that the DEFAULT.PFL file isowned by the user <SID>ADM and the primary group is R3GROUP.

3. In every additional installation option on a host distinct to SAPGLOBALHOST, you must check thatSAPinst contains the right values for UID and GID for the users displayed in the summary screen.

Installation Steps for a Standard System

1. You run SAPinst [page 90] to install the SAP system.2. You continue with Post-Installation [page 107].

Installation Steps for a Distributed System

1. If you want to share the transport directory trans from another remote system, you have to makeit available on this system. Otherwise we recommend that you share the trans directory that iscreated during the installation of the primary application server instance. For more information,see Setting Up the Transport Directory [page 112].

2. On the SAP global host, you do the following:a) You run SAPinst [page 90] to install the central services instance.

3. On the database instance host, you do the following:a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the SAP global host and ‒

optionally ‒ the trans directory from the SAP transport host.b) You run SAPinst [page 90] to install the database instance.

4. On the primary application server instance host, you do the following:a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the SAP global host.b) You run SAPinst [page 90] to install the primary application server instance.

5. If required, you can now install one to n additional application server instance(s) [page 20].6. You continue with Post-Installation [page 107].

12/08/2008 PUBLIC 87/146

4 Installation

Installation Steps for a High-Availability System

1. If you want to share the transport directory trans from another remote system, you have to makeit available on this system. Otherwise we recommend that you share the trans directory that iscreated during the installation of the primary application server instance. For more information,see Setting Up the Transport Directory [page 112].

2. You set up the switchover cluster infrastructure as follows:a) You run SAPinst [page 90] to install the central services instance (SCS) using the virtual host name

[page 90] on the primary cluster node, host A.b) You prepare the standby cluster node, host B, making sure that it meets the hardware and software

requirements [page 43] and it has all the necessary file systems, mount points, and (if required)Network File System (NFS).

c) You configure the switchover software and test that switchover functions correctly to allstandby nodes in the cluster.

d) You perform the switchover to a node where you want to install the enqueue replicationserver (ERS).

e) You run SAPinst [page 90] to install the enqueue replication server (ERS).f) You repeat the previous two steps for all nodes in the cluster.

3. On the database instance host, you do the following:a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the switchover cluster

infrastructure and ‒ optionally ‒ from the SAP transport host.b) You run SAPinst [page 90] to install the database instance on the database instance host.

4. On the primary application server instance host, you do the following:

Note

In a high-availability installation, the primary application server instance does not need to bepart of the cluster because it is no longer a single point of failure (SPOF). The SPOF is now in thecentral services instance (SCS), which is protected by the cluster.

a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the switchover clusterinfrastructure.

b) You run SAPinst [page 90] to install the primary application server instance.5. We recommend that you install additional application server (AS) instances with SAPinst to

create redundancy.Since the AS instances are not a SPOF, you do not need to include these instances in the cluster.

6. You continue with Post-Installation [page 107].

Installation Steps for an Additional Application Server Instance

Installation Steps for Additional Application Server Instance(s) for a Standard System

1. On every additional application server instance host, you do the following:

88/146 PUBLIC 12/08/2008

4 Installation

a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the SAP global host.b) You run SAPinst [page 90] to install the additional application server instance.


Installation Steps for an Application Server Instance for a Distributed System

1. If you want to share the transport directory trans from another system, you have to make itavailable from this system. Otherwise we recommend that you share the trans directory that iscreated during the installation of the primary application server instance. For more information,see Setting Up the Transport Directory [page 112].

2. On every additional application server instance host, you do the following:a) You link the global directories [page 90] in <sapmnt>/<SAPSID> from the SAP global host.b) You run SAPinst [page 90] to install the additional application server instance.


Installation Steps for an Additional Application Server Instance for a High-Availability System

1. If you want to share the transport directory trans from another system, you have to make itavailable from this system. Otherwise we recommend that you share the trans directory that iscreated during the installation of the primary application server instance. For more information,see Setting Up the Transport Directory [page 112].

2. On every additional application server instance host, you do the following:a) You make available the global directories [page 90] in <sapmnt>/<SAPSID> from the SAP global host.b) You run SAPinst [page 90] to install the additional application server instance.


Installation Steps for Additional Components and Tools for SAP NetWeaver CE (Optional)

n You install additional components [page 103] for SAP NetWeaver Composition Environment, such asl Composition Toolsl Adobe Document Services

l Composite Voicel IDE Update Site

n You install SAP Memory Analyzer [page 105] for SAP NetWeaver Composition Environment.

Installation Steps for a Standalone Host Agent

1. You run SAPinst [page 90] to install the host agent.2. You continue with Post-Installation [page 107].

12/08/2008 PUBLIC 89/146

4 Installation4.1 Linking Global Directories

4.1 Linking Global Directories

If you install a database or an additional application server instance on a host other than the SAPglobal host, you must make global directories from the SAP global host available.

PrerequisitesYou make sure the /QFileSvr.400/<SAPGLOBALHOST> directory is always available after the IPL of theadditional host.

Procedure

1. Make sure that the global transport directory is also available on every host where you want toinstall an SAP instance. Otherwise, the installation fails. For more information, see Setting Up theTransport Directory [page 112].

2. Log on to the host of the new instance that you want to install as the user with user class *SECOFRthat will execute the installation. This user must exist in all systems in the distributed systemlandscape.For more information, see Adjusting Startup Program QSTRUP [page 69].

3. Create the following link to the SAP global host file system:ADDLNK OBJ(’/QFileSvr.400/<SAPGLOBALHOST>/sapmnt/<sapsid>’) NEWLNK(’/

sapmnt/<sapsid>’)

4.2 Specifying Virtual Host Name(s)

You can use one or more virtual TCP / IP host names for SAP servers within an SAP server landscapeto conceal their physical network identities from each other. This can be useful when quickly movingSAP servers or complete server landscapes to alternative hardware without having to reinstallor reconfigure.If you want to use a virtual host name, you have to set the environment variableSAPINST_USE_HOSTNAME to specify the required virtual host name before you start SAPinst.If you do not set this environment variable now, you can specify an equivalent parameter for thevirtual host name when you run SAPinst (see Running SAPinst [page 90]).

Procedure

4.3 Running SAPinst

This procedure tells you how to install an SAP system with SAPinst. SAPinst includes a SAPinst GUIand a GUI server, which both use Java.

90/146 PUBLIC 12/08/2008

4 Installation4.3 Running SAPinst

If you need to see the installation on a remote display, we recommend you perform a remoteinstallation with SAPinst, where SAPinst GUI is running on a separate host from SAPinst and theGUI server. Alternatively you can use an X Server for Microsoft Windows or other remote desktoptools like vncviewer or nxserver/nxclient offered by various vendors (or OpenSource) for the RemoteAccess of SAPinst GUI on Windows Workstations. We recommend you use the Hummingbird ExceedX Server which we use ourselves to validate installations with SAPinst.

Note

Since i5/OS does not have GUI capabilities, we recommend that you perform a remote installationwith SAPinst. However, the remote GUI display (using the DISPLAY environment variable) is possible,but it is considered an advanced user option.

Note the following information about SAPinst:

n SAPinst normally creates the installation directory sapinst_instdir directly below the temporarydirectory. SAPinst finds the temporary directory by checking the value of the TEMP, TMP, orTMPDIR environment variable. If no value is set for these variables, SAPinst uses /tmp as defaultinstallation directory.If you want to use an alternative installation directory, set the environment variable TEMP, TMP,or TMPDIR to the required directory before you start SAPinst.

Recommendation

We recommend that you keep all installation directories until the system is completely andcorrectly installed.

n SAPinst creates a subdirectory for each installation option called<sapinst_instdir>/<installation_option_directory>.

n The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. Theseexecutables are deleted again after SAPinst has stopped running.Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory.You can safely delete them.The temporary directory also contains the SAPinst Self-Extractor log file dev_selfex.out, whichmight be useful if an error occurs.

Caution

If SAPinst cannot find a temporary directory, the installation terminates with the error FCO-00058.

n During the installation, the default ports 21200, 21212, and 4239 are used for communicationbetween SAPinst, GUI server, SAPinst GUI and HTTP server. SAPinst uses port 21200 tocommunicate with the GUI server. The GUI server uses port 21212 to communicate with SAPinst

12/08/2008 PUBLIC 91/146


GUI. 4239 is the port of the HTTP server, which is part of the GUI server. You get an error messageif one of these ports is already in use by another service.In this case, you must execute sapinst using the following parameters:SAPINST_DIALOG_PORT=<free_port_number_sapinst_to_gui_server>

GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui>

GUISERVER_HTTP_PORT=<free_port_number_http_server>.n To get a list of all available SAPinst properties, enter the following command:

CALL PGM(QP2TERM) PARM(’./sapinst’ ’-p’)

Using SAPinst GUI

The following table shows the most important functions that are available in SAPinst GUI:

SAPinst GUI Functions

Input Type Label Description

Function key F1 Displays detailed information about each inputparameter

Menu option File Exit Stops the SAPinst GUI, but SAPinst and the GUIserver continue running

Menu option SAPinst Log Browser Displays the Log Viewer dialogThis dialog enables you to access the following logfiles directly:n Installation log (sapinst_dev.log)n Log files from the SAPinst GUI server

Menu option SAPinst Cancel Cancels the installation with the following options:n Stop

Stops the installation (SAPinst GUI, SAPinst andthe GUI server) without further changing theinstallation files.You can restart and continue the installationlater from this point.

n ContinueContinues the installation

Message button Retry Performs the installation step again (if an error hasoccurred)

Message button Stop Stops the installation without further changing theinstallation filesYou can continue the installation later from thispoint.

Message button Continue Continues with the option you have chosen before

92/146 PUBLIC 12/08/2008


Prerequisites

n 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, forexample by using a crontab entry.Make sure that the temporary directory has the permissions 777.

n Make sure that you have at least 300 MB of free space in the installation directory for eachinstallation option. In addition, you need 300 MB free space for the SAPinst executables. If youcannot provide 300 MB free space in the temporary directory, you can set one of the environmentvariables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the SAPinstexecutables.You can set values for the TEMP, TMP, or TMPDIR environment variable as follows:

Shell Used Command

i5/OS command prompt ADDENVVAR ENVVAR(TEMP) VALUE(’<directory>’)

REPLACE(*YES)

i5/OS Qp2Term export TEMP=<directory>

n

Note

This is optional for advanced users.

Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name>is the host on which you want to display the SAPinst GUI.You can set values for the DISPLAY environment variables as follows:

Shell Used Command

i5/OS command prompt ADDENVVAR ENVVAR(DISPLAY) VALUE(’<hostname>:0.0’)

REPLACE(*YES)

i5/OS Qp2Term export DISPLAY=<host_name>:0.0

Note

For advanced users only: PASE, which is similar to AIX, allows you to set the DISPLAY variable. Ifyour XWindows Server on Linux or Windows (for example Humming Bird) is already configuredand running, you can try to direct the graphical output of SAPinst to a XWindow by setting theDISPLAY variable. If this works, you do not have to use the remote SAPinst GUI separately. Wedo not recommend that you start the SAPinst using the DISPLAY variable as there is no supportavailable.

n Make sure that you have defined the most important SAP system parameters as described in BasicSAP System Parameters [page 37] before you start the installation.

n Check that your installation host(s) meets the requirements for the installation option(s) that youwant to install. For more information, see Running the Prerequisite Checker [page 45].

12/08/2008 PUBLIC 93/146


Procedure

1. Log on your host as a user with similar authorization rights as QSECOFR. For more information, seePreparing a System i User Profile [page 80].

Caution

Make sure that the installation user has not set any environment variables for a different SAPsystem or database.

2. If you want to install a primary application server instance, a central services instance, a databaseinstance, or an additional application server instance, make available the Installation Master DVDYou should make sure the DVDs are available locally. We do not recommend that you useNetwork File System (NFS), because reading from DVDs mounted with NFS might fail.

3. Start SAPinst from the Installation Master DVD by entering the following commands:cd ’<Installation Master_DVD>/DATA_UNITS/IM_OS400_PPC64_DB4’

CALL PGM(QP2TERM) PARM(’./sapinst’)

Note

If you are installing a high-availability system and you have not already set the environmentparameter SAPINST_USE_HOSTNAME to specify the virtual host name, start SAPinst as follows:CALL PGM(QP2TERM) PARM(’./sapinst’ ’SAPINST_USE_HOSTNAME=<virtual host name>’)

Note

As a default, there is no GUI on System i, so you do not see theWelcome screen for SAPinst. Youmust start the SAPinst GUI separately on a Windows 32-bit platform.

Caution

n Make sure that the installation directory is not mounted with NFS, or there might be problemswhen the Java Virtual Machine is started.

n Make sure that your current working directory is not an IM_<OS>_<DB> directory belonging toanother operating system.For example, the following commands are incorrect and cause an error:$ CD DIR (’/sapcd2/DATA_UNITS/IM_HPUX_IA64_ORA’)

$ CALL PGM(QP2TERM) PARM(’/sapcd2/DATA_UNITS/IM_HPUX_IA64_ORA/sapinst’)

The following commands are correct:$ CD DIR(’/sapcd2/DATA_UNITS/IM_OS400_PPC64_DB4’)

$ CALL PGM(QP2TERM) PARM(’./sapinst’)

4. In theWelcome screen, choose the required SAPinst installation option from the tree structure.For more information, see SAPinst Installation Options [page 100].

5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

94/146 PUBLIC 12/08/2008

4 Installation4.4 Interrupted Installation with SAPinst

Note

To find more information on each parameter during the input phase of the installation, positionthe cursor on the required parameter and press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summaryscreen. This screen shows both the parameters that you entered and those that SAPinst set bydefault. If required, you can revise the parameters before starting the installation.

6. To start the installation, choose Start.SAPinst starts the installation and displays the progress of the installation. When the installationhas successfully completed, SAPinst shows the dialog Execution of <option_name> has been completedsuccessfully.

7. We recommend you to delete all files in the directory <user_home>/.sdtgui/.8. If you have copied installation DVDs to your hard disk, you can delete these files when the

installation has successfully completed.

More Information

n Interrupted Installation with SAPinst [page 123]n Entries in the Services File Created by SAPinst [page 125]n Troubleshooting with SAPinst [page 125]

4.4 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

n An error occurred during the dialog or processing phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description about the choices listed inthe table below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Exit in the SAPinst menu.

The following table describes the options in the dialog box:

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem and then choose Retry.If the same or a different error occurs again, SAPinst displays the samedialog box again.

12/08/2008 PUBLIC 95/146

4 Installation4.4 Interrupted Installation with SAPinst

Option Definition

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

ProcedureThis procedure describes the steps to restart an installation, which you stopped by choosing Stop, orto continue an interrupted installation after an error situation.

1. Log on to your local System i host as a user with similar authorization rights as QSECOFR.2. Make available your Installation Master DVD.

Note

Make sure that the DVD is available locally. We do not recommend using Network File System(NFS).

3. Enter the following commands:cd ’<Installation_Master_DVD>/DATA_UNITS/IM_OS400_PPC64_DB4’


4. From the tree structure in theWelcome screen, select the installation option that you want tocontinue and choose Next.

Note

If there is only one component to install, theWelcome screen does not appear.

TheWhat do you want to do? screen appears.5. In theWhat do you want to do? screen, decide between the following alternatives and confirm with OK.

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it movesthe content of the old installation directory and all installation-specificfiles to the backup directory. Afterwards, you can no longer continuethe old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

96/146 PUBLIC 12/08/2008

4 Installation4.5 Performing a Remote Installation with SAPinst

4.5 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst and theGUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is thehost from which you control the installation with SAPinst GUI.

Prerequisites

n The remote host meets the prerequisites before starting SAPinst [page 90].n Both computers are in the same network and can “ping” each other.

To test this:l Log on to your remote host and enter the command ping <local host>.l Log on to the local host and enter the command ping <remote host>.

Procedure

1. Log on your host as a user with similar authorization rights as QSECOFR. For more information, seePreparing a System i User Profile [page 80].

Caution

Make sure that the installation user has not set any environment variables for a different SAPsystem or database.

2. If you want to install a primary application server instance, a central services instance, a databaseinstance, or an additional application server instance, make available the Installation Master DVDYou should make sure the DVDs are available locally. We do not recommend that you useNetwork File System (NFS), because reading from DVDs mounted with NFS might fail.

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>/DATA_UNITS/IM_OS400_PPC64_DB4’

CALL PGM(QP2TERM) PARM(’./sapinst’ ’-nogui’)

Note

There is no GUI on System i, so you do not see a SAPinstWelcome screen. As a default, youmuststart the SAPinst GUI separately on a Windows 32-bit platform. For more information, seeStarting SAPinst GUI Separately (Optional) [page ].

12/08/2008 PUBLIC 97/146

4 Installation4.5 Performing a Remote Installation with SAPinst

Note

If you are installing a high-availability system and you have not already set the environmentparameter SAPINST_USE_HOSTNAME to specify the virtual host name, you can start SAPinstas follows:CALL PGM(QP2TERM) PARM(’./sapinst’ ’SAPINST_USE_HOSTNAME=<virtual host name>’)

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.

Caution

Make sure that your current working directory is not an IM_<OS>_<DB> directory belonging toanother operating system.For example, the following commands are incorrect and cause an error:$ CD DIR (’/sapcd2/DATA_UNITS/IM_HPUX_IA64_ORA’)

$ CALL PGM(QP2TERM) PARM(’/sapcd2/DATA_UNITS/IM_HPUX_IA64_ORA/sapinst’)

The following commands are correct:$ CD DIR(’/sapcd2/DATA_UNITS/IM_OS400_PPC64_DB4’)

$ CALL PGM(QP2TERM) PARM(’./sapinst’)

n Using an alternative installation directoryIf you want to use an alternative installation directory, set the environment variable TEMP,TMP, or TMPDIR.

Note

n During the installation, the default ports 21200 and 21212 are used for communication betweenSAPinst, GUI server, and SAPinst GUI. SAPinst uses port 21200 to communicate with the GUIserver. The GUI server uses port 21212 to communicate with SAPinst GUI. You get an errormessage 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>

GUISERVER_HTTP_PORT=<free_port_number_http_server>.n To get a list of all available SAPinst properties, enter the following command:

CALL PGM(QP2TERM) PARM(’./sapinst -p’)

4. In theWelcome screen, choose the required SAPinst installation option from the tree structure.For more information, see SAPinst Installation Options [page 100].

5. Follow the instructions in the SAPinst input dialogs and enter the required parameters.

98/146 PUBLIC 12/08/2008

4 Installation4.6 Starting SAPinst GUI Separately

Note

To find more information on each parameter during the input phase of the installation, positionthe cursor on the field of the respective parameter and press F1 .

6. To start the installation, choose Start.SAPinst starts the installation and displays the progress of the installation. When the installationhas successfully completed, SAPinst displays the screen Execution of Service <Service_Name> has beencompleted successfully.

7. We recommend that you delete all files in the directory <user_home>/.sdtgui/.8. If you have copied installation DVDs to your hard disk, you can delete these files when the

installation has successfully completed.

4.6 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately. You might need to start SAPinst GUIseparately in the following cases:

n You are running System i and did not set a DISPLAY environment variable.n You have logged off from SAPinst.

If you logged off during the installation and you later want to reconnect to the installation while itis still running, you can start SAPinst GUI separately.

n You want to perform a remote installation.If SAPinst GUI runs on a different host from SAPinst and the GUI server, you have to start SAPinstGUI separately.

Caution

This is the default on System i. Since there is no GUI on System i, you must start the SAPinst GUIseparately.

Starting SAPinst GUI on Windows

1. Log on as a member of the local administrators group.2. Insert the SAP Installation Master DVD into your DVD drive.3. Change to the directory of the sapinst executables:

<Installation_Master_DVD>\DATA_UNITS\IM_0S400_PPC_DB4

12/08/2008 PUBLIC 99/146

4 Installation4.7 SAPinst Installation Options

Note

If you have a share ROOTBIN on your System i and you have mapped this share to the drive X, youcan start the SAPinst GUI using your copied Installation Master DVD:X:\tmp\<SID>\<Inst._Master_DVD>\DATA_UNITS\IM_OS400_PPC_64_DB4

For more information, see Copying the DVDs ManuallyUsing the ROOTBIN Share [page 84].

4. Start SAPinst GUI by double-clicking sapinstgui.exeSAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local hostas default.If SAPinst and the GUI server are running on another host, SAPinst GUI cannot connect and theSAP 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 fromyour local host.

Note

Optionally you can start sapinstgui.exe with the following parameters:n host=<host name>, where <host name> is the host name of the installation host

n port=<nr>, where <nr> is the port number for the connection to the GUI server

n -accessible enables the Accessibility modeExample:./sapinstgui.exe host=lsi1209 port=3000 -accessible

4.7 SAPinst Installation Options

This section provides information about the following in SAPinst:

n Installation Options

n Software Life-Cycle Options

Note

n Choose the required installation options from the tree structure exactly in the order they appearfor each system variant.

n If you want to use global accounts, which are configured on separate hosts, you must run theinstallation option Operating System Users and Groups before you start the installation of the SAPsystem (see table Software Life-Cycle Options below).

n If required, install an additional application server instance for a standard system (all instances onone host) or distributed system by choosing <SAP System> Software Life-Cycle Options Additional

100/146 PUBLIC 12/08/2008


Application Server Instance Additional Application Server Instance .n If required, install additional CE components by choosing <SAP System> Software Life-Cycle

Options Additional CE Components Additional CE components .n If required, install SAP Memory Analyzer by choosing <SAP System> Software Life-Cycle

Options SAP Memory Analyzer SAP Memory Analyzer .

Installation Options

You choose SAP Systems with <your database> to install a SAP system with usage types or software units.You can install the following system variants:

n Standard System

Installation Options for a Standard System

Installation Option Remarks

Standard System Installs a complete SAP system including the following instances on one host:l Central services instance (SCS)l Database instancel Primary application server instanceYou can install a standard system in the following modes:l Typical Mode

If you choose Typical, the installation automatically uses default settings. Youonly have to respond to a small selection of prompts. However, you can changeany of the default settings on the parameter summary screen.

l Custom ModeIf you choose Custom, the installation prompts you for all parameters. At the end,you can change any parameter on the parameter summary screen.

NoteYou require at least usage type AS Java or AS ABAP. You can choose the usage typesor software units on the next screen.

n Distributed System

Installation Options for a Distributed System

Installation Options Remarks

Central Services Instance(SCS)

Installs a central services instance (SCS) and prepares the SAP global hostMandatory step in installing a distributed SAP system with usage typesor software units based on AS Java

12/08/2008 PUBLIC 101/146



Database Instance Installs a database instanceMandatory step in installing a distributed SAP systemYou must have finished the Central Services Instance (SCS) installation beforeyou can choose this installation option.

Primary Application ServerInstance

Installs a primary application server instance and enables additionalsoftware unitsMandatory step in installing a distributed SAP system on several hostsYou must have finished the database instance installation.

n High-Availability System

Installation Options for a High Availability System


Central Services Instance(SCS)

Installs a central services instance (SCS)

Database Instance Installs a database instance

Primary ApplicationServer Instance

Installs a primary application server instance and enables additional usagetypes or software units

Additional ApplicationServer Instance

Installs an additional application server instance

Software Life-Cycle Options

You use the options located in this folder to perform the following tasks or to install the followingcomponents:


Additional Preparations n Host AgentChoose Additional Preparations Host Agent Host Agent to install the hostagent with the profiles SAPSystem=99 and SAPSystemName=SAP.The host agent contains all of the required elements for centrally monitoringany host.Normally you do not need to install a standalone host agent, because itis automatically installed during the installation of all SAP NetWeavercomponents, except TREX.You only need to install a standalone host agent when:l You want to centrally monitor a host that does not have an SAP

component.l You want to perform an upgrade to SAP NetWeaver.For more information, see Standalone Host Agent [page 23].

n Operating system users and groupsLets you use global accounts that are configured on a separate host

102/146 PUBLIC 12/08/2008

4 Installation4.8 Installing Additional Components (Optional)


CautionPerform this SAPinst option before you start the installation of your SAPsystem.

n Prerequisites checkChoose Additional Preparations Prerequisites Check if you want to check yourhardware and software requirements before you start the installation.

Additional ApplicationServer Instances

Choose Additional Application Server Instances Additional Application Server Instanceto install one or more additional application server instance(s) in an alreadyinstalled SAP system, if required.

Additional CEComponents

Choose this option to install additional CE components, such asn Composition Toolsn Adobe Document Services (if available for your platform)n Composite Voicen IDE Update Site

SAP Memory Analyzer Choose this option to install SAP Memory Analyzer.SAP Memory Analyzer helps you to analyze Java heap dumps, easily find bigchunks of memory or complex memory aggregation patterns in your datastructures and identify who is keeping this memory alive.

System Copy Choose this option to perform a system copy.For more information, see the system copy guide for your SAP system at:http://service.sap.com/instguides <SAP system> Installation .

Uninstall Choose this option to uninstall your SAP system, standalone engines, or optionalstandalone units.For more information, see Deleting an SAP System [page 137].

4.8 Installing Additional Components (Optional)

You can install the following additional components:

n Composition Toolsn Adobe Document Services (if available for your platform)n Composite Voicen IDE Update Site

PrerequisitesYou need to fulfill the same hardware and software requirements as for your already installedproduction system plus an additional 2 GB RAM.

12/08/2008 PUBLIC 103/146


4 Installation4.8 Installing Additional Components (Optional)

The Composition Tools and Composite Voice component make use of the Visual Composer. VisualComposer is a Web browser based tool to model user interfaces. To run Visual Composer, thefollowing programsmust be installed on the client computer fromwhich you access Visual Composer:

n Microsoft Internet Explorer 6.0 SP1 or highern Adobe SVG Viewer 3.0

n Microsoft XML Parser 4.0 or higher

Note

n Before installing additional components, you need to stop all application servers manually.

n Before installing additional components and in the case that you made changes to the defaulttemplate settings, see SAP Note 953763.

Procedure

Note

When installing from a network share make sure that everyone has read access to this share. Theinstallation routine creates users such as <sid>adm (for example, ce1adm). During the installationSAPinst does a user switch to this user. If the newly created user does not have permissions to thenetwork share where the installation is running from, the installation will fail.

1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally.2. Run SAPinst [page 90].3. In theWelcome screen, choose SAP NetWeaver CE Productive System Software Life-Cycle Options

Additional CE Components Install Additional Components .4. Choose whether you want to run the installation in Typicalmode or in Custommode.

If you select Typical, the installation wizard provides automatic default settings and you only haveto respond to a small selection of prompts. The rest is set by default. If you select Custom, you haveto respond to all prompts.

Note

If you want to install the offline documentation for SAP NetWeaver CE, you need to chooseCustommode.After the installation, you can access the offline documentation by choosing Start AllPrograms SAP NetWeaver Composition Environment <SAPSID> .

5. Follow the screens and enter the required parameters.

104/146 PUBLIC 12/08/2008


4 Installation4.9 Installing SAP Memory Analyzer (Optional)

Note

For more information about the input parameters and information about restrictions forpasswords, position the cursor on the required parameter and press F1 .


6. To start the installation, choose Start. SAPinst starts the installation and displays the progress ofthe installation. When the installation has successfully been completed, SAPinst shows the dialogExecution of <Option_Name> has been completed successfully.

Note

After installing additional components, you need to perform CE-specific post-installation activities [page117] to get the system up & running.

4.9 Installing SAP Memory Analyzer (Optional)

SAP Memory Analyzer helps you to analyze Java heap dumps, easily find big chunks of memory orcomplex memory aggregation patterns in your data structures and identify who is keeping thismemory alive. New and innovative analysis techniques support the user with a fast and powerfulfeature set.The tool (Eclipse RCP application) was developed to analyze real productive heap dumps, whichtend to get enormous in size with hundreds of millions of objects. Performance, low resourceconsumption and especially the newly developed innovative analysis techniques make it a helpfultool, even to small application heap dumps.You can install SAP Memory Analyzer as an additional tool.

Procedure

Note

When installing from a network share make sure that everyone has read access to this share. Theinstallation routine creates users such as <sid>adm (for example, ce1adm). During the installationSAPinst performs a user switch to this user. If the newly created user does not have permissions tothe network share where the installation is running from, the installation will fail.

1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally.2. Run SAPinst [page 90].3. In theWelcome screen, choose SAP NetWeaver CE Productive System Software Life-Cycle Options SAP

Memory Analyzer Install SAP Memory Analyzer .

12/08/2008 PUBLIC 105/146

4 Installation4.9 Installing SAP Memory Analyzer (Optional)

4. Choose whether you want to run the installation in Typicalmode or in Custommode.If you select Typical, the installation wizard provides automatic default settings and you only haveto respond to a small selection of prompts. The rest is set by default. If you select Custom, you haveto respond to all prompts.

Note

If you want to install the offline documentation for SAP NetWeaver CE, you need to chooseCustommode.After the installation, you can access the offline documentation by choosing Start AllPrograms SAP NetWeaver Composition Environment <SAPSID> .

5. Follow the screens and enter the required parameters.

Note

For more information about the input parameters and information about restrictions forpasswords, position the cursor on the required parameter and press F1 .


6. To start the installation, choose Start. SAPinst starts the installation and displays the progress ofthe installation. When the installation has successfully been completed, SAPinst shows the dialogExecution of <Option_Name> has been completed successfully.

106/146 PUBLIC 12/08/2008

5 Post-Installation

5 Post-Installation

This section includes the post-installation steps that you have to perform for the:

n Standard, distributed or high-availability systemn Additional application server instancen Standalone host agent

Standard, Distributed, or High-Availability System

1. If required, you perform a full backup [page 113] immediately after the installation has finished.2. You check whether you can log on to the SAP system [page 108].

Note

In a distributed or high-availability system you check whether your can log on to every instanceof the SAP system that you installed.

3. You ensure user security [page 109].4. You install the SAP license [page 111].5. You configure the remote connection to SAP support [page 112].6. You grant authorizations for operating system collections [page 112].7. You set up the transport directory [page 112].8. On the primary application server instance host, you apply the latest kernel and Support Packages [page 113].9. You check the Java manuals [page 116] for information that is relevant for running your Java system.10. You perform CE-specific post-installation steps [page 117].11. If you want or need to implement the E2E Root Cause Analysis scenario, you have to perform

post-installation steps for the Diagnostics Agent [page 120] on your central instance and/or dialog instance(s).

Additional Application Server Instance

1. You check whether you can log on to the additional application server instance [page 108].2. If you want or need to implement the E2E Root Cause Analysis scenario, you have to perform

post-installation steps for the Diagnostics Agent [page 120] on your central instance and/or dialog instance(s).

Standalone Host Agent

You perform the post-installation steps for the Host Agent [page 115].

12/08/2008 PUBLIC 107/146

5 Post-Installation5.1 Logging On to the Application Server

5.1 Logging On to the Application Server

You need to check that you can log on to the application server using the following standard users:

Java Standalone Users

User User Name Storage:Database

User Name Storage:External ABAP System

Administrator Administrator You create this user manuallyduring the installation process.

RecommendationWe recommend thatyou call the userJ2EE_ADM_<SAPSID_Java_System>

The maximum length is 12characters.

Prerequisites

n The SAP system is up and running.

Logging On to the Java Application ServerYou access AS Java with a URL using a Web browser from your client machines. To log on to the Javaapplication server, proceed as follows:

1. Start a Web browser and enter the following URL:http://<hostname_of_Java EE_Engine_Server>:5<Instance_Number>00

Note

You must always enter a two-digit number for <Instance_Number>. For example, do not enter 1but instead enter 01.

Example

If you installed the SAP NetWeaver Application Server Java on host saphost06 and the instancenumber of your SAP NetWeaver Application Server Java is 04, enter the following URL:http://saphost06:50400

The start page of the SAP NetWeaver Application Server Java appears in the Web browser.2. Log on by pressing the icon of any of the provided applications, for example the SAP NetWeaver

Administrator.

108/146 PUBLIC 12/08/2008

5 Post-Installation5.2 Ensuring User Security

5.2 Ensuring User Security

You need to ensure the security of the users that SAPinst creates during the installation. For securityreasons, you also need to copy the installation directory to a separate, secure location ‒ such as aDVD ‒ and then delete the installation directory.

Recommendation

In all cases, the user ID and password are only encoded when transported across the network.Therefore, we recommend using encryption at the network layer, either by using the Secure SocketsLayer (SSL) protocol for HTTP connections, or Secure Network Communications (SNC) for the SAPprotocols dialog and RFC.For more information, see the SAP Library [page 14]:Function-Oriented View Security Network and Transport Layer Security

Caution

Make sure that you perform this procedure before the newly installed SAP system goes intoproduction.

PrerequisitesIf you change user passwords, be aware that SAP system users might exist in multiple SAP systemclients (for example, if a user was copied as part of the client copy). Therefore, you need to change thepasswords in all the relevant SAP system clients.

ProcedureFor the users listed below, take the precautions described in the relevant SAP security guide, whichyou can find on SAP Service Marketplace at http://service.sap.com/securityguide:To change passwords at the operating system level, use the command CHGPWD or CHGUSRPRF.

Changing Passwords of Created System i Users

User Profile Initial Password

<SID>ADM ‒

<SID>OWNER ‒

Caution

In three-tier systems, these users must have the same password on all System i.

12/08/2008 PUBLIC 109/146

http://service.sap.com/securityguide



5 Post-Installation5.2 Ensuring User Security

Host Agent User

User User Name Comment

Operating system user sapadm SAP system administratorYou do not need to change thepassword of this user after theinstallation.This user is for administrationpurposes only.

Note

You can set up Java standalone users with the SAP User Management Engine (UME) in one of thefollowing ways:

n With the users stored in an external ABAP system ‒ see the first table below

n With the users stored in the database ‒ see the second table below

The next two tables show these ways of managing the users.

SAP System Users Stored in an External ABAP System

User User Name Storage: External ABAP System Comment

Administrator You create this user manually in the externalABAP system during the installation process.

RecommendationWe recommend that you call the userJ2EE_ADM_<SAPSID_Java_System>

The maximum length is 12 characters.

This user’s password is stored insecure storage.Therefore, whenever you change theadministrator’s password, you mustalso change the password in securestorage with the Config Tool .For more information, see Checking theSAP Java Documentation [page 116].

Guest You create this user manually in the externalABAP system during the installation process.

RecommendationWe recommend that you call the userJ2EE_GST_<SAPSID_Java_System>


Lock this user for interactive logon.

Communicationuser for ApplicationServer Java

You create this user manually in the externalABAP system during the installation process.

RecommendationWe recommend that you call the userSAPJSF_<SAPSID_Java_System>


Specify this user as a Communicationsuser and not as a dialog user.This user exists at least in the SAPsystem client that you specifiedduring the installation.

110/146 PUBLIC 12/08/2008

5 Post-Installation5.3 Installing the SAP License

SAP System Users Stored in the Database

User User Name Storage: Database Comment

Administrator The name that you gave this userduring the installation or thedefault name Administrator

This user’s password is stored in securestorage. Therefore, whenever you changethe administrator’s password, you must alsochange the password in secure storage with theAS Java Config Tool.For more information, see Checking the SAP JavaDocumentation [page 116].

Guest The name that you gave this userduring the installation or thedefault name Guest

Lock this user for interactive logon.

5.3 Installing the SAP License

You must install a permanent SAP license. When you install your SAP system, a temporary licenseis automatically installed. This temporary license allows you to use the system for only four weeksfrom 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 yoursystem.

ProcedureFor information about the installation procedure for the SAP license, see the SAP library [page 14]:SAP NetWeaver Process Integration Library Administrator’s Guide Technical Operations Manual for SAP

NetWeaver (TOM) General Administration Tasks License Administration

More InformationFor more information about SAP license keys and how to obtain them, see SAP Service Marketplace athttp://service.sap.com/licensekey.

5.4 Configuring the Transport Management System

You have to perform some steps to be able to use the Transport Management System.

Procedure

1. Perform post-installation steps for the transport organizer:

12/08/2008 PUBLIC 111/146

http://service.sap.com/licensekey



5 Post-Installation5.5 Configuring the Remote Connection to SAP Support

a) Call transaction SE06.b) Select Standard Installation.c) Choose Perform Post-Installation Actions.

2. Call transaction STMS in your SAP Solution Manager system to configure the domain controllerin the Transport Management System (TMS).

ResultYou can now perform Java transports in the TMS of your SAP Solution Manager system.

More InformationFor more information, see the SAP Library [page 14]:Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Change and

Transport System

5.5 Configuring the Remote Connection to SAP Support

SAP offers its customers access to support and a number of remote services such as the EarlyWatchService or the GoingLive Service. Therefore, you have to set up a remote network connection to SAP.For more information, see SAP Service Marketplace at http://service.sap.com/remoteconnection.

5.6 Granting Authorizations for Operating System CollectorPrograms

If your primary language is not English, you must enable SAP Support to activate the newly installedsecondary language. For more information, see Installing English as a Secondary Language [page 79].

ProcedureEnter the command:GRTOBJAUT OBJ(QSYS/CHGSYSLIBL) OBJTYPE(*CMD) USER(R3GROUP) AUT(*USE)

You also have the option of granting authorization to USER(*PUBLIC).

5.7 Setting Up the Transport Directory

You need to set up the transport directory for your SAP system.

PrerequisitesUsing a shared system transport directory /usr/sap/transmakes it easier to maintain your SAPsystem and instance configuration data. We recommend that you link /usr/sap/trans to the IFS

112/146 PUBLIC 12/08/2008

http://service.sap.com/remoteconnection



5 Post-Installation5.8 Applying the Latest Kernel and Support Packages

directory /sapmnt/trans on the primary application server instance host of an SAP system. If theprimary application server instance is on a different host, the directory should be linked usingQFileSvr.400.By default, the installation creates directory /sapmnt/trans and link /usr/sap/trans, which pointsto /sapmnt/trans, provided the directories do not exist on the host yet. It is possible to let the SAPinstinstallation change the /usr/sap/trans link to point to the primary application server instance hostof the newly installed SAP system. If you want that directory /usr/sap/trans points to any otherhost, you have to change it manually.

ProcedureTo change the /usr/sap/trans to /sapmnt/trans of any other host, proceed as follows:

1. Log on to the System i host as a user with administrator rights similar to QSECOFR.2. To link to another host, enter the following command:

CHGR3SHLOC NEWHOST(<hostname>)

For more information, see SAP Note 67213.

5.8 Applying the Latest Kernel and Support Packages

You use this procedure to apply the latest kernel and Support Packages for your SAP system from SAPService Marketplace.

PrerequisitesYou must have applied all ABAP Support Packages, before you perform CE-Specific Post-InstallationActivities [page 117].

ProcedureDownload and apply the latest Kernel and Support Packages as described in the SAP NetWeaverComposition Environment 7.1 ‒ Update Guide SP<xx> at http://www.sdn.sap.com/irj/sdn/nw-ce.

5.9 Performing a Full Backup

You can use this procedure to make a full backup of your SAP system.

Note

During the backup, your SAP system is unavailable to other users.

12/08/2008 PUBLIC 113/146


http://www.sdn.sap.com/irj/sdn/nw-ce

5 Post-Installation5.10 High Availability: Setting Up Licenses

Procedure

1. On the System i command line, enter GO SAVE.2. Enter option 21.

For more information, see the IBM documentation OS/400 Backup and Recovery (SC41-5304).

Figure 19: How to Back Up Your System

More InformationRestoring a Backup [page 135]

5.10 High Availability: Setting Up Licenses

Every SAP system needs a central license, which is determined by the environment of the messageserver. Since SAP’s high-availability (HA) solution stipulates two or more cluster nodes (hostmachines) where the message server is enabled to run, you have to order as many license keys [page 111]as you have cluster nodes.When we receive confirmation from your vendor that you are implementing a switchoverenvironment, we provide the required license keys for your system, one key for each machine.SAP has implemented a license mechanism for transparent and easy use with switchover solutionsand clustered environments. Your customer key is calculated on the basis of local information on themessage server host. This is the host machine where the central services instance (SCS) runs. Thereis no license problem when only the database is switched over.

114/146 PUBLIC 12/08/2008

5 Post-Installation5.11 Post-Installation Steps for the Host Agent

PrerequisitesThe SAP system is up and running.

Procedure

1. Make sure that the SCS instance on the primary host, node A, is running.2. To find the hardware key of the primary host, run the SAP NetWeaver Administrator (NWA) on

any application server instance and choose Configuration Management Infrastructure ManagementLicenses .The hardware key is displayed in the NWA.

3. Perform a switchover of the central services instance (SCS) to another node in the cluster andrepeat the previous step.Repeat this for all remaining nodes in the cluster.

4. To obtain the two license keys, enter the hardware IDs for the primary and backup hosts at:http://service.sap.com/licensekey

5. To import the files containing the two licenses to the primary cluster node, run the NWA onany application server instance and choose:Configuration Management Infrastructure Management Licenses

6. Perform a switchover of the central services instance (SCS) to another node in the cluster andrepeat the previous step.Repeat this for all remaining nodes in the cluster.

ResultThe license is no longer a problem during switchover. This means you do not need to call saplicensein your switchover scripts.

5.11 Post-Installation Steps for the Host Agent

You have to perform the following steps on each host where the host agent is installed. This applieswhether the host agent is installed on a host within the SAP system or standalone on another host.

Procedure

1. You check whether the installed services are available as follows:a) Log on as user sapadm.b) Check whether the following services are available:n The control program saphostexec

n The operating system collector saposcoln The SAP NetWeaver Management agent SAPHostControl (sapstartsrv in host mode)

12/08/2008 PUBLIC 115/146




5 Post-Installation5.12 Checking the SAP Java Documentation

Note

On System i, the installed programs are started by the auto-start job (ADDAJE) SAPINIT insubsystem QUSRWRK, which was created during the installation. The subsystem QUSRWRK isrestarted after every IPL automatically.

2. You configure the host agent according to your requirements.

More InformationFor more information, see the SAP Library [page 14]:Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS Infrastructure of the SAP NetWeaver Management Agents

5.12 Checking the SAP Java Documentation

Here you can find information in the SAP Library about the configuration of Application ServerJava (AS Java) and about SAP Java technology.

Procedure

1. Choose the following in the SAP library [page 14]:Function-Oriented View Application Server Java AS Java (Application Server Java)

2. Check the following documentation for information relevant to running your Java system:

Manual Contents

Application Server InfrastructureArchitecture of the SAPNetWeaver

Application Server Architectureof AS Java

This documentation provides an overview of the architecture of theApplication Server Java (AS Java). It contains information on:n Java cluster architecturen Application Server Java (AS Java) system architecturen Zero Administration (technical configuration within AS Java)

Application Server JavaAdministration

This documentation describes how to administer the SAP system,focusing on AS Java. It contains information on:n Administration Toolsl SAP Management Console

The SAP Management Console (SAP MC) provides a commonframework for centralized system management. It lets youmonitor and perform basic administration tasks on the SAPsystem centrally, thus simplifying system administration.

l SAP NetWeaver AdministratorSAP NetWeaver Administrator is a Web-based tool foradministration and monitoring that offers a single entry point toconfigure, administer, and monitor your SAP NetWeaver system,its components, and the applications running on it.

l Config Tool

116/146 PUBLIC 12/08/2008

5 Post-Installation5.13 CE-Specific Post-Installation Activities

Manual Contents

The Config Tool provides offline configuration of the SAPNetWeaver Application Server Java (AS Java) instances. It lets youmodify the properties of all services, managers, and applications.In addition, it enables you to manage log configurations offline,add filters, and edit the JVM parameters.

l Administration Using Telnetn SAP Java Virtual Machine (SAP JVM)n The Startup Framework for AS Javan Administration Functions for Information Lifecycle Management

Application Server Java IdentityManagement of the Application ServerJava

Identity Management of the SAP NetWeaver Application Server (AS) Javaenables you to manage users and roles for access to applications of the ASJava and the data, which the applications require. The user managementengine (UME) provides identity management as a service of the AS Java.This documentation contains information on:n User Management Enginen Authorization Concept of the AS Javan Configuring Identity Managementn Administration of Users and Roles

SAP High Availability This documentation contains information on:n Cluster and Load Balancing (AS-Java)n Single points of failure for SAP NetWeaver AS Java

Security System Security This documentation contains information on additional system securityfunctions for AS Java.

5.13 CE-Specific Post-Installation Activities

This section describes the steps that you have to perform after the installation has finished successfully.

Running the Configuration Wizard (Optional)

Note

You can run the configuration wizard only once and only directly after installing and patchingyour SAP system.

After SAPinst has finished, run the configuration wizard to apply automated configuration tasksto your system.For SAP NetWeaver CE, you need to run the following configuration tasks, depending on the installedcomponents:

n Configuration of Services Registry Webservice Destinations

n Configuration and Mirroring of local NWDS Update Site

n Initial setup ADS in CE (if ADS is available on your platform)

12/08/2008 PUBLIC 117/146


n Change Management Service (CMS): Create an Application Skeleton

n Change Management Service (CMS): Modify a Software Component

For more information about how to start the configuration wizard, see the configurationdocumentation in the SAP Solution Manager.

Enabling Adobe Document ServicesIf you have installed SAP NetWeaver Composition Environment with the Adobe Document Servicesadd-on aWindows platform, you must complete the following post-installation steps to enable theadd-on. In case you have installed an AS Java cluster, apply the procedure to the central host, as wellas to all hosts where additional application server instances are running.

1. Using the SAP Management Console, stop the AS Java system.For more information about starting and stopping SAP systems, seehttp://help.sap.com/nwce Administrator’s Guide Administration of SAP NetWeaver

CE General System Administration AS Java (Application Server Java) .2. From the Start menu, open Control Panel Administrative Tools Computer Management Services

and Applications Services .3. Select SAP<SID>_<Instance_Number> (for example, SAPCE1_00) and open Properties from the

context menu.4. On the Log On tab page, enable the Local System account indicator.5. Repeat the above steps for the second SAP<SID>_<Instance_Number> service that you see in the list.6. Start the AS Java system.

Adobe LiveCycle Designer

For more information about how to install and configure the Adobe LiveCycle Designer see SAPNote 962763.

Enabling Services RegistryYou must apply additional configuration steps to enable Services Registry after you have installed anSAP NetWeaver Composition Environment system containing the following components:

n Java Application Server and Composition Platformn Java Application Server and Adobe Document Services

To enable Services Registry, you must apply the following configuration template to your system:CE_Complete_Stack_production_full

118/146 PUBLIC 12/08/2008

http://help.sap.com/nwce





Note

For more information about what configuration templates are available, see Configuration Templates[page 122].For more information about applying configuration templates, see http://help.sap.com/nwce

SAP NetWeaver Composition Environment Library Administrator’s Guide Configuration of SAP NetWeaver CEInitial System Configuration AS Java Configuration Activating a Configuration Template .

See also

http://help.sap.com/nwce SAP NetWeaver Composition Environment Library Developer’s GuideDeveloping and Composing Applications Consuming Enterprise Services Searching for Services Services RegistryTasks Searching & Browsing Service Definitions Configuring the Services Registry

Configuring the Portal in SAP NetWeaver CEAfter installing the portal in SAP NetWeaver CE, a number of deactivated or irrelevant tools aredisplayed in the UI. To display the correct portals tools for CE, proceed as follows:

1. Open a browser and log on to your portal as an administrator.2. In the same browser session, enter the following URL:

http://<host>:<httpport>irj/servlet/prt/portal/prtroot/com.sap.portal.

content.layers.ContentLayersTool

where <host> is the host name of your server and <httpport> is the port number of your server.3. In the Portal Mode Configuration Tool, choose Activate Development Mode to restore the portal tools

and content that are assigned to the development mode.4. Restart or refresh your browser.5. In the SAP Management Console, restart the server.

You may then continue with the mandatory and optional configuration steps as described inhttp://help.sap.com/nwce SAP NetWeaver Composition Environment Library Administrator’s Guide

Configuration of SAP NetWeaver Composition Environment Configuration for CE Additional Components Configuringthe Portal .

Changing the Password for the Internet Communication Manager (ICM)You can monitor and manage the Internet Communication Manager (ICM) from the command lineprogram.After the installation of your SAP NetWeaver CE system has successfully finished, you need to changethe ICM password manually. To do so, proceed as follows:

1. Log on at operating system level to the computer where the ICM is running.2. Start the program icmon with icmon –a profile=<instance_profile> to maintain the

authentication file (default: authfile.txt).3. Choose a to add a user.4. Choose c to change the password of the existing user.

12/08/2008 PUBLIC 119/146










5 Post-Installation5.14 Post-Installation Steps for the Diagnostics Agent

5. Choose s to save your settings.

Further Configuration StepsAfter installing your SAP NetWeaver CE system and performing the post-installation steps to get thesystem up & running, you may need to perform further configuration steps.Refer to the following documentation to proceed with your tasks:

n If you are a system administrator, refer to http://help.sap.com/nwce Administrator’s Guide .It contains information about how to configure and administer your system.

n If you are a developer, refer to http://help.sap.com/nwce Developer’s Guide . It providesguidelines for developing applications using the SAP NetWeaver CE.

Note

The SAP NetWeaver CE documentation is also available offline as a part of your installation. To accessit, choose Start All Programs SAP NetWeaver Composition Environment 1.0 Documentation .

5.14 Post-Installation Steps for the Diagnostics Agent

To implement the E2E Root Cause Analysis scenario, you have to configure the Diagnostics Agent.

PrerequisitesYou have installed an AS Java central instance or dialog instance.

ProcedurePlan the implementation of the SAP SolutionManager Diagnostics Agent as described in the Root CauseAnalysis Installation and Upgrade Guide, which you can find at http://service.sap.com/diagnostics.

120/146 PUBLIC 12/08/2008








6 Additional Information

6 Additional Information

Here you find additional information about the installation of your SAP system.There is also information about how to delete an SAP system.

n Transporting Self-Developed Software Component Archives (SCA) into the System [page 121]n Configuration Templates [page 122]n Uninstalling SAP NetWeaver Composition Environment [page 123]n Starting and Stopping the SAP System [page 126]n High-Availability: Finalizing the enqueue replication server for high availability [page 132].

You have to perform this procedure only if you have installed the enqueue replication server(ERS) into an existing system.

n System i Library Structure [page 133]n System i Integrated File System [page 134]n Restoring a Backup [page 135]n Editing Stream Files [page 136]n Deleting an SAP System [page 137]n Deleting an SAP Instance on System i [page 138]n Deleting an the Java Part of an SAP System [page 140]

6.1 Transporting Self-Developed Software ComponentArchives (SCA) into the System

PrerequisitesYou have developed your own Software Component Archives (SCA) and want to transport theminto your SAP NetWeaver CE system.

ProcedureTo transport your SCAs to the SAP NetWeaver CE system, proceed as follows:

1. Download the update file from http://service.sap.com/swdc Download Support Packages andPatches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER CE7.1 Support Package Stacks Support Package Stacks .

2. Log on to your system as user QSECOFR and switch into PASE using the command call qp2term.From an empty directory, run the update toolupdate. When the update program is runningconnect to it using updategui.exe from Windows.

12/08/2008 PUBLIC 121/146




6 Additional Information6.2 Configuration Templates

Note

If the tool displays descriptions such as Applying Support Packages, you can ignore them.

3. In the dialog screens, specify the directory where your SCAs are located.4. Follow the on-screen instructions.

6.2 Configuration Templates

Configuration templates contain the predefined instance configuration for specific scenarios. Theyare automatically applied according to the installation option you have selected. The templatesare designed to optimize system performance by applying certain configuration to the Java VirtualMachine and the application server, as well as by applying startup filters to AS Java services andapplications to start only those relevant for the selected installation options.The following table provides information about the available templates with SAP NetWeaverComposition Environment. In the template name, replace the <system_mode> parameter bydevelopment (for the templates relevant to systems installed in developmentmode) or production (forthe templates relevant to systems installed in productivemode).

Configuration Template Selected Installation Options

CE_Java_EE_<system_mode>_full Java Application Server Installation

CE_Composition_Environment_<system_mode>_full Java Application Server Installation + CompositionPlatform Installation

CE_Adobe_Document_Service_<system_mode>_full Java Application Server Installation + AdobeDocument Services Add-on Installation

CE_Composite_Voice_<system_mode>_full Java Application Server Installation + Voice Add-onInstallation

CE_Complete_Stack_<system_mode>_full Java Application Server Installation + CompositionPlatform Installation + Adobe Document ServicesAdd-on Installation + Voice Add-on Installation

If your selection cannot be mapped to one of the combinations in the above table, the templateCE_Complete_Stack_<system_mode>_full is applied. It starts all applications and services neededto run the complete stack.You canmanually apply a different configuration template if youwant to switch to another installationoption. For example, by changing from template CE_Complete_Stack_<system_mode>_full toCE_Java_EE_<system_mode>_full, you achieve shorter startup times and less memory consumption,but also less functionality since not all applications and services are running.

122/146 PUBLIC 12/08/2008

6 Additional Information6.3 Uninstalling SAP NetWeaver Composition Environment

For more information about applying configuration templates, see http://help.sap.com/nwce

Administrator’s Guide Configuration of SAP NetWeaver CE Initial System Configuration AS Java ConfigurationActivating a Configuration Template .

Note

Make sure that you do not apply a development template to a productive system or vice versa.

6.3 Uninstalling SAP NetWeaver Composition Environment

You have to uninstall all components of the SAP NetWeaver Composition Environment separately.You can uninstall your SAP NetWeaver CE system in different ways.

Uninstalling SAP NetWeaver CE Using SAPinst

1. Insert the SAP Installation Master DVD into your DVD drive or mount it locally.2. Start SAPinst from the SAP Installation Master DVD as described in the section Installing SAP

NetWeaver Composition Environment.3. In theWelcome screen, choose Uninstall SAP System or Single Instances from the tree structure.4. Follow the on-screen instructions.

6.4 Additional Information About SAPinst

The following sections provide additional information about SAPinst [page 90]:

n Interrupted Installation with SAPinst [page 123]n Troubleshooting with SAPinst [page 125]

6.4.1 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

n An error occurred during the dialog or processing phase:SAPinst does not abort the installation in error situations. If an error occurs, the installation pausesand a dialog box appears. The dialog box contains a short description about the choices listed inthe table below as well as a path to a log file that contains detailed information about the error.

n You interrupted the installation by choosing Exit in the SAPinst menu.

The following table describes the options in the dialog box:

12/08/2008 PUBLIC 123/146




6 Additional Information6.4 Additional Information About SAPinst

Option Definition

Retry SAPinst retries the installation from the point of failure without repeatingany of the previous steps.This is possible because SAPinst records the installation progress in thekeydb.xml file.We recommend that you view the entries in the log files, try to solve theproblem and then choose Retry.If the same or a different error occurs again, SAPinst displays the samedialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, andthe GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore,you can continue the installation from the point of failure withoutrepeating any of the previous steps. See the procedure below.

Continue SAPinst continues the installation from the current point.

ProcedureThis procedure describes the steps to restart an installation, which you stopped by choosing Stop, orto continue an interrupted installation after an error situation.

1. Log on to your local System i host as a user with similar authorization rights as QSECOFR.2. Make available your Installation Master DVD.

Note

Make sure that the DVD is available locally. We do not recommend using Network File System(NFS).

3. Enter the following commands:cd ’<Installation_Master_DVD>/DATA_UNITS/IM_OS400_PPC64_DB4’


4. From the tree structure in theWelcome screen, select the installation option that you want tocontinue and choose Next.

Note

If there is only one component to install, theWelcome screen does not appear.

TheWhat do you want to do? screen appears.5. In theWhat do you want to do? screen, decide between the following alternatives and confirm with OK.

124/146 PUBLIC 12/08/2008

6 Additional Information6.4 Additional Information About SAPinst

Alternative Behavior

Run a new Installation SAPinst does not continue the interrupted installation. Instead, it movesthe content of the old installation directory and all installation-specificfiles to the backup directory. Afterwards, you can no longer continuethe old installation.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds> (for example,log_01_Oct_2003_13_47_56).

Continue old installation SAPinst continues the interrupted installation from the point of failure.

6.4.2 Entries in the Services File Created by SAPinst

After the installation has finished successfully, SAPinst has created the following entries in/etc/services:After the installation has finished successfully, SAPinst has created the following entries in the servicetable.To review the entries use the command WRKSRVTBLE.

Service Table

Service Port Protocol

sapdpXX 32XX tcp

sapdpXXs 47XX tcp

sapgwXX 33XX tcp

sapgwXXs 48XX tcp

Note

If there is more than one entry for the same port number, this is not an error.

6.4.3 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.If an error occurs, SAPinst:

n Stops the installationn Displays a dialog informing you about the error

Procedure

1. To view the log file, choose View Logs.

12/08/2008 PUBLIC 125/146

6 Additional Information6.5 Starting and Stopping SAP System Instances

2. If an error occurs during the dialog or processing phase, do one of the following:n Try to solve the problem.n Abort the installation with Exit.

For more information, see Interrupted Installation with SAPinst [page 123].n Continue the installation by choosing Retry.

3. Check the log and trace files of the GUI server and SAPinst GUI in the directory<user_home>/.sdtgui/ for errors.n If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

<user_home> directory.n If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately [page ].n If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote

Access of SAPinst GUI on Windows Workstations and you experience display problems such asmissing repaints or refreshes, contact the vendor of the X Server that you use for informationon whether this X Server support Java Swing-based GUIs and for further requirements andrestrictions. See also SAP Note 1170809.

6.5 Starting and Stopping SAP System Instances

You can start and stop SAP system instances and the Diagnostics Agent by using the SAP ManagementConsole (SAP MC) [page 126].Apart from using the SAP Management Console (SAP MC) you can also use commands to

n Start or stop SAP system instances [page 130]n Start or stop the Diagnostics Agent [page 131].

6.5.1 Starting and Stopping the SAP System Using the SAPManagement Console

You can start and stop all SAP system instances using the SAP Management Console (MC) exceptthe database instance.

Note

If your newly installed SAP system is part of a heterogeneous SAP system landscape comprisingsystems or instances on Windows platforms, you can also start and stop it from a Windows systemor instance using the Microsoft Management Console (MMC).For more information about handling the MMC, see the SAP Library [page 14]:Function-Oriented View Application Server ABAP Administration Tools for AS ABAP Monitoring in the

CCMS SAP Microsoft Management Console: Windows

126/146 PUBLIC 12/08/2008



Prerequisites

n Make sure that the host on which you start SAP MCmeets the following requirements:l Java Runtime Environment (JRE) 5.0 is installed.l The browser supports Java.l The browser’s Java plug-in is installed and activated.

n You have logged on to the host as user <sapsid>adm.

Starting the Web-Based SAP Management Console

1. Start a Web browser and enter the following URL:http://<hostname>:5<instance_number>13

Example

If the instance number is 53and the host name is saphost06, you enter the following URL:http://saphost06:55313

This starts the SAP MC Java applet.

Note

If your browser displays a security warning message, choose the option that indicates that youtrust the applet.

2. Choose Start.The SAP Management Console appears.

Note

When you start the SAP MC for the first time for a newly installed SAP system, you have toregister your system as described in Registering Systems and Instances below. Having done this , theinstances installed on the host you have connected to are already added in the SAP ManagementConsole when you start the SAP MC next time.

By default, the instances installed on the host you have connected to are already added in theSAP Management Console.If you want to change the configuration to display systems and instances on other hosts, seeRegistering Systems and Instances below.

Starting and Stopping Systems and Instances

Starting an SAP System or Instance

1. In the navigation pane, open the tree structure and navigate to the system node that you want tostart.

12/08/2008 PUBLIC 127/146


2. Select the system or instance and then, from the context menu, choose Start.3. In the Start SAP System(s) dialog box, choose the required options.4. Choose OK. The SAP MC starts the specified system or system instances.

Note

The system might prompt you for the SAP system administrator credentials. To complete theoperation, you must have administration permissions. Log in as user <sapsid>adm.

Starting Instances Separately

If you need to start the instances of an SAP system separately, for example when you want to start adistributed or a high-availability system, proceed in the following sequence:

1. Start the database instance.2. Start the central services instance SCS<Instance_Number>.3. Start application server instance(s) J<Instance_Number>.

Stopping an SAP System or Instance

1. Select the system or instance you want to stop and choose Stop from the context menu.2. In the Stop SAP System(s) dialog box, choose the required options.3. Choose OK. The SAP MC stops the specified system or system instances.

Note

The system might prompt you for the SAP system administrator credentials. To complete theoperation, you must have administration permissions. Log in as user <sapsid>adm.

Similarly, you can start, stop or restart all SAP systems and individual instances registered in theSAP MC.

Stopping Instances Separately

If you need to stop the instances of an SAP system separately, for example when you want to start adistributed or a high-availability system, proceed in the following sequence:

1. Stop application server instance(s) J<Instance_Number>.2. Stop the central services instance SCS<Instance_Number>.3. Stop the database instance.

Registering Systems and Instances in the SAP Management ConsoleYou can extend the list of systems and instances displayed in the SAPMC, so that you canmonitor andadminister all systems and instances from a single console. You can configure the SAP MC startupview to display the set of systems and instances you want to manage.

128/146 PUBLIC 12/08/2008


Prerequisites

The SAP MC is started.

Registering SAP Systems

1. In the SAP MC, choose File New .2. In the New System dialog box, enter the required data.

Note

If you have already registered systems in the SAP MC, they are stored in the history. To open theSystem’s History dialog box, choose the browsing button next to the Instance Nr. field. Select aninstance of the system that you want to add and choose OK.

3. Choose Finish.

Registering Individual Instances

1. In the SAP MC, choose File New .2. In the New System dialog box, enter the required data and deselect Always show all SAP Instances.3. The SAP MC displays the SAP system node, the instance node and the relevant database node in

a tree view in the navigation pane.

Note

To view all instances of the respective SAP system, select the relevant system node and chooseAdd Application Server from the context menu.

Configuring the SAP MC View

n You can choose the instances that the SAP MC displays automatically on startup:1. In the Settings dialog box, select History.2. In the right-hand side pane, choose the instance you want the SAP MC to display on startup.3. Choose the << button.4. Choose Apply and then choose OK.Similarly, you can remove instances from the startup configuration.

n You can save the current configuration in a file:1. Choose File Save Landscape .2. In the Save dialog box, enter the required data.3. Choose Save.

n You can load a configuration from a file:1. Choose File Load Landscape .2. In the Open dialog box, select the configuration you want to load.3. Choose Open.

12/08/2008 PUBLIC 129/146


More InformationFor more information about how to handle the SAP MC, see the SAP Library [page 14]:Administrator’s Guide Technical Operations for SAP NetWeaver Administration of SAP NetWeaver Systems

AS Java (Application Server Java) Administration Administration Tools SAP Management Console

6.5.2 Starting and Stopping the SAP System Using Commands

The procedures below explain how to start and stop the SAP system after the installation.

Note

The central services instance only exists if you install AS Java.

Prerequisites

n You have checked the default profile /<sapmnt>/<SAPSID>/profile/DEFAULT.PFL for parameterlogin/system_client and set the value to the correct productive system client. For example, theentry must be login/system_client = 001 if your productive client is 001.

n You have checked the settings for Java Virtual Machine parameters as described in SAP Note723909.

Note

The instancename (instance ID) of the primary application server instance is J<Instance_Number>.The instance name of the central services instance is SCS<Instance_Number>, and the instancename of a Java additional application server instance is J<Instance_Number>.

Starting the SAP System

1. Log on to your System i as user <SID>ADM.2. Check that there are no active jobs for the instance that you have just installed. To do this, proceed

as follows:a) For the central services instance, the primary application server instance and all additional

application server instances, enter the following command:WRKACTJOB SBS(R3_<instance_number>)

b) If a job is displayed, stop it by entering the following command:ENDSBS SBS(R3_<instance_number>) OPTION(*IMMED)

3. To start the SAP system, enter the following command and press F4 :STARTSAP

4. Enter the SAP system ID (for example, C11) and instance number (for example, 90). Repeat this foreach instance that you want to start.

130/146 PUBLIC 12/08/2008



Recommendation

We recommend that you retain the default value *ENV for the SAP system ID. *ENV is replacedby the correct value for the SAP system ID.

Note

Make sure that the SAP system and associated AS Javas are up and running before you start orrestart additional application server instances and their AS Javas.

5. To check whether your SAP system started successfully for every installed instance, enter thefollowing command:WRKACTJOB SBS(R3_<nn>)

Note

Every instance runs in its own subsystem R3_<nn>, where <nn> is the instance number.

Stopping the SAP System

1. Log on to your System i as <SID>ADM.2. To stop an SAP system, enter the following command and press F4 :

STOPSAP

3. Enter the SAP system ID (for example, C11) and instance number (for example, 90).Repeat this for each instance that you want to stop.

Recommendation

We recommend that you retain the default value *ENV for the SAP system ID. *ENV is replacedby the correct value for the SAP system ID.

For each stopped instance, the user you used to shut down the system receives a message from theoperating system.

6.5.3 Starting and Stopping the Diagnostics Agent

An installed Diagnostic Agent in IBM i, is managed as any other SAP system.You can start and stop the Diagnostics Agent using the commands STARTSAP and STOPSAP.

Note

You can only start or stop the Diagnostics Agent separately. It is not started or stopped automaticallywith the SAP system.

12/08/2008 PUBLIC 131/146

6 Additional Information6.6 High Availability: Finalizing the Enqueue Replication Server

You can also use the SAP Management Console (SAP MC) to start or stop the Diagnostics Agent (seeStarting and Stopping SAP System Instances Using the SAP Management Console [page 126]).

PrerequisitesYou have logged on to the central instance or dialog host as user <smdsid>adm.

Procedure

Starting a Diagnostics Agent(s)

To start the Diagnostics Agent, proceed as follows:

1. Log on to your system as user <smdsid>adm.2. To start the Diagnostics Agent(s), enter the following command and press F4 :

STARTSAP SID(<SMDSID>) INSTANCE(98)

Note

You can start all instances of the Diagnostic Agent at the same time by entering the followingcommand:STARTSAP SID(<SMDSID>) INSTANCE(*ALL)

Stopping Diagnostics Agent(s)

To stop the Diagnostics Agent(s), proceed as follows:

1. Log on to your system as user <smdsid>adm.2. To stop the Diagnostics Agent(s), enter the following command and press F4 :

STOPSAP SID(<SMDSID>) INSTANCE(98)

Note

You can stop all instances of the Diagnostic Agent at the same time by entering the followingcommand:STOPSAP SID(<SMDSID>) INSTANCE(*ALL)

6.6 High Availability: Finalizing the Enqueue ReplicationServer

You have to perform this procedure only if you have installed the enqueue replication server (ERS)into an existing system. This is necessary to ensure correct functioning of the ERS, which depends onthe switchover software you are using.

132/146 PUBLIC 12/08/2008

6 Additional Information6.7 System i Library Structure

Procedure

1. Restart the central services instance associated with the ERS.This requires you to restart the primary application server and additional application serverinstance.

2. Contact your hardware partner to configure and test the ERS.

More InformationSee the SAP Library [page 14]: Function-Oriented Overview Application Server Infrastructure StandaloneEnqueue Server Installing the Standalone Enqueue Server

6.7 System i Library Structure

Definition

Libraries form the primary native organizational structure on System i. A library is an object thatgroups together related objects.There are three different types of library:

n System libraries, such as library QSYS for objects supplied as part of the operating systemn User libraries, such as the various SAP libraries:

System i Library Structure

Library Description

SAP<SID>DB Java database library

SAP<SID>JRN Java journal receiver library

R3<SID>400 Library for work management objects

R3<SID><XXXXX> Liibrary for SQL packages

R3<REL>ARFC Library for RFC SDK (ASCII)

R3<REL>ACPIC Library for CPI-C SDK (ASCII)

R3WRK<nn> Internal SAP work library

R3* Reserved for SAP

Q* System libraries

Note

<SID> is the SAP system ID (for example PRD or TST)<REL> is the SAP release (for example, 710)<nn> is the instance number.

12/08/2008 PUBLIC 133/146

6 Additional Information6.8 System i Integrated File System

n Product libraries, such as library QPDA, which contains objects associated with the System iProgramming Development Manager (PDM)

Recommendation

Some of the SAP library names may vary if you assign your own library names.

Types of objects stored in libraries include, for example, files and programs.Files do not contain the actual data. The data is stored inmembers within each file. In SQL systems,such as SAP, each file contains exactly one member.

6.8 System i Integrated File System

Definition

The System i also provides a UNIX-style and PC-style integrated file system that provides enhancedcapabilities for managing new types of information processing including client/server, open systems,and multimedia.

Use

The integrated file system supports the use of stream files for storing and operating on data. Streamfiles are files containing a continuous stream of data. This data might take the form of text files orimages, for example. Stream files are system objects with object type *STMF.For information about displaying or editing stream files, see Editing Stream Files [page 136].

Structure

The System i integrated file system has a hierarchy comparable to that used by UNIX. The integratedfile system treats the different types of support for accessing the various object types as separatefile systems. These file systems are:

System i Integrated File System

File System Description

“/” This file system corresponds to the UNIX root directory. This PC-style filesystem is not case-sensitive.

QOpenSys The open systems file system. This UNIX-style file system is case-sensitive(not used by the SAP system).

QSYS.LIB The library file system allowing the user to access objects residing in nativeSystem i libraries using IFS commands.

QDLS The document library services file system (not used by the SAP system).

QLANSrv The LAN Server/400 file system (not used by the SAP system).

134/146 PUBLIC 12/08/2008

6 Additional Information6.9 Restoring a Backup

File System Description

QOPT The optical file system; this file system is mainly used during installation andcontains all DVDs that have been inserted so far.

QFileSvr.400 This file system provides access to other file systems on remote System isystems. It is used by several SAP functions, for example correction andtransport, to access remote stream files.

Caution

Take care with upper- and lowercase notation. The “/” file system is not case sensitive, but QOpenSysand the contents of SAP profiles are case sensitive..

IntegrationThe integrated file system distinguishes between two different types of link: hard links and softlinks. A link is a named connection between a directory and an object.

Hard and Soft Links

Type of Link Description

Hard link, also known as link, absolute link n Indicated by a separate directory entryn Cannot exist unless linked to an objectn Cannot cross file systems

Soft link, also known as symbolic link n Takes the form of a path name contained in a filen Can exist without pointing to an existing object.

(Is an object of type *SYMLNK.)n Can be removed without affecting the objectn Can cross file systemsn Only allowed in the IFS

Note

To see the contents of a symbolic link, use the command WRKLNK with Detail option *EXTENDED. (Thiscommand corresponds to the UNIX command ls -l.) Enter option 12 (Work with links).

Note

The SAP system uses soft links by default.

6.9 Restoring a Backup

You can restore a backup in the sequence given below.

12/08/2008 PUBLIC 135/146

6 Additional Information6.10 Editing Stream Files

PrerequisitesYou have a full backup.

Procedure

1. Control the panel function.2. Perform an IPL (initial program load) or Install System Menu.3. To restore a user profile or profiles saved with command

SAVSYS (Save System) or SAVSECDTA (Save Security Data), enter:RSTUSRPRF (Restore User Profile)

4. To restore to the system a configuration object saved with the SAVSYS (Save System) or SAVCFG(Save Configuration) command, enter:RSTCFG (Restore Configuration)

5. To restore libraries saved with the SAVLIB command with LIB(*NONSYS) specified, enter:RSTLIB (*NONSYS) (Restore Library)

6. To restore documents, folders, and distribution objects, enter:RSTDLO (Restore Document Library Object)

7. To restore a copy of an object or objects that can be used in the Integrated File System, enter:RST DEV(’/qsys.lib/tap01.devd’)

OBJ((’*’ *INCLUDE) (’\qsys.lib’ *OMIT) (’\qdls’ *OMIT))

8. To restore saved changes in libraries, documents, and directories, enter:RSTLIB, RSTOBJ, RSTDLO, RST

9. To apply journaled changes (for a particular database file member) to recover the file, enter:APYJRNCHG (Apply Journaled Changes)

10. To restore private authorities to user profiles, enter:RSTAUT (Restore Authority)

Figure 20: Methods for Restoring a Backup

6.10 Editing Stream Files

Stream files are files containing a continuous stream of data. Stream files are used, for example, tostore documents and images. On System i, SAP profiles are stored in stream files.

ProcedureYou can access System i stream files and directories in a number of different ways.

n Using the Command EDTF

136/146 PUBLIC 12/08/2008

6 Additional Information6.11 Deleting an SAP System

EDTF is an editor similar to SEU (Source Entry Unit). The prefix area of each record accepts theedit command. To display the edit commands available, press F1 .

n Using Netserver/400The Netserver/400 is included in the operating system since V4R2M0. This provides, similar toWindows, shares that can be mapped with every Windows client. You can configure these shareswith a free-of-charge option of the operation navigator on Client Access Express. Since V4R4M0you can configure a character-by-character conversion from ASCII to EBCDIC and vice-versa.

n Using Client AccessIf you have Client Access, you can also access stream files using this product. Using CA/400’sNetwork Drive feature and the capability of CA/400 to perform a character-by-characterconversion from ASCII to EBCDIC and vice-versa, you can work on the System i IFS in the sameway as on the PC file system. That is, you can create, edit, and delete files and directories with allthe restrictions that apply to CA/400.

6.11 Deleting an SAP System

This section describes how to delete a single instance, a standalone engine or a complete SAP systemwith the Uninstall option of SAPinst.

Caution

n You cannot delete an SAP system remotely.

Prerequisites

n This description assumes that you have installed your SAP system with standard SAP toolsaccording to the installation documentation.

n You should make sure that your SAP system is down and that you are not logged on as one of theSAP system users. A lock on one of the SAP system objects would break the uninstall!

Procedure

1. Start SAPinst [page 90] and on theWelcome screen, choose:2. Follow the instructions in the SAPinst input dialogs.

Note

For more information about the input parameters, place the cursor on the relevant field andpress F1 in SAPinst.

SAPinst first asks you which SAP instances you want to delete. Make sure that you delete the SAPinstances in the order as described hereinafter.

12/08/2008 PUBLIC 137/146

6 Additional Information6.12 Deleting an SAP Instance on System i

n You run SAPinst and delete the required instances or standalone engines.n If you want to delete a distributed system, you have to run SAPinst to delete the required

instances locally on each of the hosts belonging to the SAP system in the following sequence:a) Additional application server instance(s), if there are anyb) All SAP instances that are installed on System i.c) Primary application server instanced) Central services instance

Note

The uninstall only uses the SAP kernel tool DLTR3INST and DLTR3SYS. Whenever these toolsfail to delete an object on System i this object will be given to the user SAPGARBAGE. SAP systemobjects are also given to the user SAPGARBAGEwhen it is not clear if the object should be erased.Finally check after every uninstall all the objects of SAPGARBAGE using WRKOBJOWN and delete allobjects you do not need anymore. For more information, see SAP Note 936956.

6.12 Deleting an SAP Instance on System i

This section describes how to delete SAP instances that are installed on System i.

Note

If you want to delete an entire SAP system on one local host, you can use the command DLTR3SYS.For more information, see Deleting an SAP System on System i.

Caution

If you delete an entire SAP system, you have to delete the instances one by one.

Caution

This description assumes that the installation of your SAP system has been performed using SAPstandard tools according to the installation documentation.

ProcedureTo delete an instance, log on to the System i where the SAP instance you want to delete is installed. Todo this, log on as user QSECOFR or as a user that has the same authorizations as QSECOFR.

1. To add the kernel library to the library list, enter the following command:ADDLIBLE LIB(SAP<SID>71)

138/146 PUBLIC 12/08/2008


6 Additional Information6.13 Deleting an SAP System on System i

Caution

If you want to delete a complete ABAP+Java system but not the ABAP database instance, delete allinstances but do not delete the system at the end.

2. To delete an entire SAP instance, enter the following command:DLTR3INST SID(<system>) INST(<instance number>)

Note

When you encounter errors using DLTR3INST use DSPJOBLOG to correct the problem. Objects withlocks usually cause an error. After deleting an object lock using WRKOBJLCK, you can start DLTR3INSTagain to continue deleting you instance.

6.13 Deleting an SAP System on System i

This section describes how to delete an SAP system that is installed on System i.

Caution

This description assumes that the installation of your SAP system has been performed using SAPstandard tools according to the installation documentation.

Procedure

1. To add the kernel library to the library list enter the following command:ADDLIBLE LIB(SAP<SID>71)

Caution

If you want to delete a complete Java system but not the Java database instance, delete all instancesbut do not delete the system at the end.

2. To delete an SAP system, enter the following command:DLTR3SYS SID(<SAP SAP_System_ID>) DLTINST(*YES) DLTGLB(*YES) DLTHOME(*YES)

3. If the following directories and files exist, delete them by entering the following command:WRKLNKSAP

12/08/2008 PUBLIC 139/146

6 Additional Information6.14 Deleting the Java Part of an SAP System

n /usr/sap/trans/config/<SID>

n /usr/sap/trans/cofiles/*<SID>*

n /usr/sap/trans/data/*<SID>*

n /usr/sap/trans/log/*<SID>*

n /sapmnt/<SID>

Example

For example, for directory /sapmnt/<SID>/jdbc, enter the following command:WRKLNKSAP DIR(’/sapmnt/<SID>’)

Choose 4 (Delete) on directory jdbc.

Note

To limit the command WRKLNKSAP, choose Subset (in the upper right part on the screen).

4. In directory buffer /usr/sap/trans/buffer/*<SID>*, delete all files that contain <SID>.5. If the kernel library of the system you just deleted was only used by the deleted system, you can

remove it. To do this, enter the following command:DLTLIB LIB(<kernelname>)

Note

When you encounter errors using DLTR3INST use DSPJOBLOG to correct the problem. Objects withlocks usually cause errors. After deleting an object lock using WRKOBJLCK, you can start DLTR3SYSagain to continue deleting your system.

ResultThe SAP system is now deleted. If you want to reinstall an SAP system, you can use the same <SID> asthe one of the SAP system you deleted.

6.14 Deleting the Java Part of an SAP System

This section describes how to delete the Java Add-In, which is the Java part of an ABAP+Java system.

Note

If you delete a Java Add-In, the ABAP part of the SAP system is not deleted.

Process

1. Log on as <SID>OFR and stop all instances of your SAP system then log off.2. Log on as QSECOFR and add the kernel library of your system to your library list by entering the

command ADDLIBLE LIB(SAP<SID>71).

140/146 PUBLIC 12/08/2008


3. To delete the central services instance of Java (SCS<xx>), enter the following command:DLTR3INST SID(<sapsid>)INST(<xx>)

4. To delete the Java part of an ABAP+Java primary application server instance or additionalapplication server instance, enter the following command:DLTR3INST SID(<sapsid>) INST(<xx>) JAVAONLY(*YES)

To display the additional parameter JAVAONLY,press F10 . Set the value to JAVAONLY(*YES).5. Delete all other Java parts of the system, including library SAP<sapsid>DB. To do this, enter the

following command:DLTR3SYS SID(<sapsid>) JAVAONLY(*YES)

6. If lines beginning with the following parameters appear, delete these lines from the default profile,/usr/sap/<SAPSID>/SYS/profile/DEFAULT.PFL:

n j2ee/dbname =

n j2ee/dbtype =

n j2ee/dbhost =

n j2ee/dbadminurl =

7. If lines beginning with the following parameters appear, delete these lines from the primaryapplication serverl instance profile and from all additional application server instance profiles,/usr/sap/<SAPSID>/SYS/profile/<SAPSID>_<INSTANCE_NAME>_<host_name>:

n exe/j2ee =

n rdisp/j2ee_start_control =

n rdisp/j2ee_start =

n rdisp/j2ee_timeout =

n rdisp/frfc_fallback =

n jstartup/trimming_properties =

n jstartup/instance_properties =

n jstartup/protocol =

n exe/jlaunch =

12/08/2008 PUBLIC 141/146


SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of othersoftware vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP productsand services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and in several other countries all over the world. All other product and service names mentioned are thetrademarks of their respective companies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

142/146 PUBLIC 12/08/2008


DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

Legal Software Terms

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below. Note that for these third partyproducts the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. SAP License Agreement for STLportSAP License Agreement for STLPort betweenSAP AktiengesellschaftSystems, Applications, Products in Data ProcessingDietmar-Hopp-Allee 1669190 Walldorf, Germany(hereinafter: SAP)andyou(hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library(STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without anyroyalties or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged: Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:n The conditions indicated in the above permissions notice are met;n The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:Copyright 1994 Hewlett-Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose ishereby granted without fee, provided that the above copyright notice appear in all copies and that both that

12/08/2008 PUBLIC 143/146


copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations about the suitability of this software for any purpose. It is provided “as is” without express orimplied warranty.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARCmakes no representations about the suitability of this software for any purpose. It is provided “as is” withoutexpress or implied warranty.Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material isprovided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to useor copy this software for any purpose is hereby granted without fee, provided the above notices are retained on allcopies. Permission to modify the code and to distribute modified code is granted, provided the above notices areretained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. SAP makes no representationsabout the suitability of this software for any purpose. It is provided with a limited warranty and liability as setforth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations onlytowards its customers and only referring to its modifications.

b) Support and MaintenanceSAP does not provide software maintenance for the STLport. Software maintenance of the STLport thereforeshall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditionsand shall be subject to a separate contract.

c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that theSTLport 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 anyassurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i)can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or(iii) if based on the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shalldepend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract,due to the circumstances known to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by adefect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceedEUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data andits recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employeesor agents of SAP.

3. Adobe Document Services

144/146 PUBLIC 12/08/2008


Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe SystemsIncorporated in the United States and / or other countries. For information on Third Party software delivered withAdobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: https://service.sap.com/instguides

12/08/2008 PUBLIC 145/146


https://service.sap.com/instguides



SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2008 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Documents

InstallationGuide SAPNetWeaverCompositionEnvironment7 ... · InstallationGuide SAPNetWeaverCompositionEnvironment7.1SR5oni5/OS: IBMDB2fori5/OS ProductionEdition TargetAudience nSystemAdministrators