Installation Guide SAP NetWeaver 7.0 Java including Enhancement Package 1 SR1 on Windows: MS SQL ServerUsing SAPinstIncluding: R SAP NetWeaver Application Server Java (AS Java) R SAP NetWeaver Business Intelligence Java Components (BI Java) R SAP NetWeaver Development Infrastructure (DI) R SAP NetWeaver EP Core (EPC) R SAP NetWeaver Enterprise Portal (EP) R Application Sharing Server (Optional Standalone Unit) Target Audience R System Administrators R Technical Consultants

PUBLIC R.MtW5U`0UcflhM>3V-'MVzlOw(u

About this Installation Guide

SAP System Installation

SAP system installations should only be performed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installingSAP Installation Tool

You must only use the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed.Downward Compatibility of Databases

For downward-compatible releases of DB/OS platforms for SAP products, SAP plans to regularly release the newest database (DB) and operating-system (OS) versions of SAP products. These releases are downward-compatible with earlier SAP system releases. Note that for already shipped SAP components, we only support the installation for database versions proposed by the installation tool. Therefore, you must install an SAP component or perform a system copy using a downwardcompatible database. That is, you either install the component with the old proposed database version or you upgrade the old database version to the downward-compatible new version.

2/212

PUBLIC

2009-05-04

Typographic Conventions

Example

Description

Example Example ExampleExample

Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, Enter your . Arrows separating the parts of a navigation path, for example, menu options Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 ; Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. ; Cross-references to other documentation or published works ; Output on the screen following a user action, for example, messages ; Source code or syntax quoted directly from a program ; File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard

http://www.sap.com /example

123456 Example

Example

EXAMPLE

EXAMPLE

2009-05-04

PUBLIC

3/212

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace http://service.sap.com/ instguides. The following table provides an overview on the most important document changes:Version Date Description

1.00

2009-05-04

Initial Version

4/212

PUBLIC

2009-05-04

Table of Contents

]zHO*8J"* 1.1 1.2 ]zHO*8J"* 2.1 2.2 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.4 2.5 2.6 2.7 2.8 ]zHO*8J"* 3.1 3.2 3.3 3.4 3.5 3.6

Introduction ........................................................................................................... New Features ............................................................................................................. SAP Notes for the Installation .................................................................................. Planning ................................................................................................................... Planning Checklist .................................................................................................... Installation Options Covered by this Guide ........................................................... Central System .......................................................................................................... Distributed System .................................................................................................... High Availability System .......................................................................................... Dialog Instance .......................................................................................................... Installation of Additional Usage Types in an Existing SAP System ....................... Hardware and Software Requirements ................................................................... Running the Prerequisite Checker in Standalone Mode (Optional) .................... Requirements for a Central System ........................................................................ Requirements for a Distributed System .................................................................. Requirements for a High-Availability System ........................................................ Requirements for the Dialog Instance .................................................................... Domain or Local Installation ................................................................................... Distribution of SAP System Components to Disks ................................................ SAP System Transport Host ..................................................................................... Planning User and Access Management ................................................................. Basic SAP System Parameters ................................................................................... Preparation .............................................................................................................. Preparation Checklist ............................................................................................... Disabling the Windows Server 2008 Firewall Temporarily .................................... Performing Basic Windows Preparation Steps ........................................................ Required User Authorization for Running SAPinst .............................................. Using Virtual Host Names ........................................................................................ Preparing the SAP System Transport Host .............................................................

11 12 14 17 17 17 18 18 19 19 21 21 22 23 25 28 32 32 33 36 36 37 49 49 49 50 52 53 54

2009-05-04

PUBLIC

5/212

3.7 3.8 3.9 3.10 /zs5wK4 [1 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.3 4.4 /zs5wK4 [0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17 5.18 5.19 5.20

Generating the SAP Solution Manager Key ............................................................ Installing the Java Development Kit ....................................................................... Downloading the JCE Unlimited Strength Jurisdiction Policy Files Archive ...... Preparing the Installation DVDs .............................................................................. Installation .............................................................................................................. Installation Checklist ................................................................................................ Installing the SQL Server Database Software .......................................................... Installing the SQL Server Database Software with SQL4SAP ................................. Installing the SQL Server 2005 Database Server Software Manually ..................... Installing the SQL Server 2005 Native Client Software Manually ......................... Installing the SQL Server 2008 Database Server Software Manually ..................... Installing the SQL Server 2008 Native Client Software Manually ......................... Running SAPinst ....................................................................................................... SAPinst Installation Options .................................................................................... Post-Installation ..................................................................................................... Post-Installation Checklist ....................................................................................... Configuring the Windows Server 2008 Firewall ..................................................... Logging On to the Application Server .................................................................... Logging On to the Portal .......................................................................................... Logging On to the SAP NetWeaver Development Infrastructure (NWDI) .......... Configuring User Management ............................................................................... Ensuring User Security ............................................................................................. Installing the SAP License ......................................................................................... High Availability: Setting Up Licenses ..................................................................... Applying the Latest Kernel and Support Package Stacks ...................................... Creating Symbolic Links on Windows Server 2008 for Application Servers ........ Configuring Remote Connection to SAP Support ................................................ Performing Initial Java Configuration ..................................................................... Setting the SQL Server Agent Configuration ......................................................... Performing a Full System Backup ........................................................................... Performing Post-Installation Steps for Adobe Document Services ...................... Setting Environment Variable CPIC_MAX_CONV .............................................. Configuring the Connection to a Central System Landscape Directory ............. Updating Component Repository Content in the System Landscape Directory .................................................................................................................... Configuring the Application Sharing Server ..........................................................

54 55 56 56 61 61 62 62 63 67 67 70 70 73 79 79 80 82 83 84 85 86 90 90 91 92 93 93 95 95 95 96 97 97 98

6/212

PUBLIC

2009-05-04

5.21 5.22 5.23 F?wf::]_6|vv_0.PR\B1P?G^_v^/*yx^Icyt:*(Ua,8 |hZ"2Jo6

5.19 Updating Component Repository Content in the System Landscape Directoryn\~f>wf::]_6|vv_0.PR\B1P?G^_v^/*yx^Icy

You have to update Component Repository Content in the System Landscape Directory (SLD) if the following conditions are true: sKs You have installed usage type Development Infrastructure (DI). sKs You have chosen option Register in existing central SLD for SLD destination during the Define Parameters phase of the installation.n\v?qwfa;]\5|kv9_2kuS\]cl?U^_v/y%

For more information about option Register in existing central SLD, see table Connectivity to System Landscape Directory (SLD) in Basic SAP System Parameters [page 37].Procedure

Update the CR content in the central SLD as described in SAP Note 669669.

2009-05-04

PUBLIC

97/212

5 5.20

Post-Installation Configuring the Application Sharing Server

Result

You can now run the Configuration Wizard to perform wizard-based basic configuration steps. For more information, see Running the Configuration Wizard [page 98].1e4nNC"[28j|bxl%T)T2}ipO*

5.20 Configuring the Application Sharing ServerNOTE

These steps are valid if you installed usage type EP and if you are using the default server installed on the portal machine. If you do not intend to use Application Sharing Server, you can disable it as described in the SAP Library at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaver by Key Capability People Integration by Key Capability Collaboration Administration Guide Real-Time Collaboration Configuring Real-Time Collaboration Configuring the Application Sharing Server (RTC) Enabling / Disabling the Application Sharing Server (RTC) The installation of Application Sharing Server as an optional standalone unit is described in the documentation Installation Guide Application Sharing Server on : 1e4fN2[i8j|b\l%T.T.}{?f*r\3y:[r#67e(T^SI2Uj=c&&9V!IrkD+>qRw!;r/#,Irjg-9-jz;1cg&M;'~~XP)tjHV{f:8o=sqdUv

5.22 Post-Installation Steps for the Diagnostics AgentTo implement the E2E Root Cause Analysis scenario, you have to configure the Diagnostics Agent.Prerequisites

You have installed an AS Java central instance or dialog instance.

2009-05-04

PUBLIC

99/212

5 5.23

Post-Installation Accessing Configuration Documentation in SAP Solution Manager

Procedure

Plan the implementation of the SAP Solution Manager Diagnostics Agent as described in the Root Cause Analysis Installation and Upgrade Guide, which you can find at: http://service.sap.com/diagnostics End-to-End Root Cause Analysis Media Library

5.23 Accessing Configuration Documentation in SAP Solution ManagerTo access configuration documentation in SAP Solution Manager, you have to connect your newly installed SAP system to SAP Solution Manager.NOTE

For SAP NetWeaver 7.0 usage types you can also find configuration documentation in the Technology Consultant's Guide at: http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English SAP NetWeaver Library Technology Consultant's GuidePrerequisites

* You have installed an SAP Solution Manager system as described in the documentation Installation Guide SAP Solution Manager on : . * You have connected your SAP system to SAP Solution Manager as described in the documentation Configuration Guide SAP Solution Manager as of . You can find this documentation at: http://service.sap.com/instguides SAP Components SAP Solution Manager Procedure

1. 2.

3. 4.

Log on to your SAP Solution Manager system. To be able to access configuration documentation, create a project as follows: 1. Create your project with transaction SOLAR_PROJECT_ADMIN for project administration. 2. Connect your SAP system to SAP Solution Manager with transaction SMSY for the SAP Solution Manager system landscape. 3. Create a project structure and add the required scenarios for your SAP system to your project structure with the Business Blueprint transaction SOLAR01, 4. Add your SAP system configuration structures to your project structure with the configuration transaction SOLAR02. Go to the project structure folder using transaction SOLAR02. Access configuration documentation for SAP NetWeaver usage types at Configuration Structure SAP NetWeaver 7.0 .

100/212

PUBLIC

2009-05-04

5 5.23

Post-Installation Accessing Configuration Documentation in SAP Solution Manager

Result

You can now configure your SAP system according to the configuration documentation in SAP Solution Manager.More Information

http://service.sap.com/solutionmanager

Media Library Technical Papers How to Create a

Configuration Guide using SAP Solution Manager http://help.sap.com SAP Solutions SAP Solution Manager Documentation for SAP Solution Manager SAP Solution Manager Implementing and Upgrading SAP Solutions Projects Configuration

2009-05-04

PUBLIC

101/212

This page is left blank for documents that are printed on both sides.

6 6.1

Additional Information SAP Directories

6 Additional Information

The following sections provide additional information about optional preparation, installation, and post-installation tasks. There is also a section describing how to delete an SAP system.Planning

SAP Directories [page 103]Preparation

U U U U U U

Performing a Domain Installation Without Being a Domain Administrator [page 107] Database Installation for Multiple Components with MS SQL Server [page 110] Installation of Multiple Components in One Database [page 112] Integration of LDAP Directory Services [page 113] Preparing User Management with an External ABAP system [page 117] Dialog Instance Installation for an Upgraded System: Updating Instance Profiles [page 120]

Installation

U Additional Information about SAPinst [page 121] U Installation of Additional Software Units or Usage Types in an Existing SAP System [page 129]Post-Installation

U U U U U U

Starting and stopping the SAP system [page 133] Accessing the SAP Java documentation [page 134] Usage Type-Specific Initial Technical Configuration [page 136] SAP System Security on Windows [page 143] Automatic Creation of Accounts and Groups [page 145] Troubleshooting [page 146]

Deleting an SAP System or SAP Instance

U Deleting an SAP System [page 149] U Deleting a Diagnostics Agent [page 150]

6.1 SAP DirectoriesThis section describes the directories that are available in an SAP system.

2009-05-04

PUBLIC

103/212

6 6.1

Additional Information SAP Directories

a,|vXF(Oz!Vvcf:%W

If you want to install an MSCS system, see also Directories in an MSCS Configuration [page 167].a,%vV(=Oz*

SAPinst automatically creates the following directories during the installation: `i\usr\sap

This directory is created on the: ` Global host and shared with the network share sapmnta,|vXF(Oz!x8c:

The global host is the host where the SCS instance is installed.a,%vV(Oz. a,|vXF(Oz!Vvcf:%W

The global host is the host where the SCS instance is installed.a,%vV(=Oz*

On global hosts, the \usr\sap directory contains general SAP software, global and local (instance-specific) data. For this, SAPinst creates the global directory usr\sap\ \SYS, which physically exists only once for each SAP system. It consists of the following subdirectories: ` global contains globally shared data ` profile contains the profiles for all instances ` exe contains executable replication directory for all instances and platforms ` Local host and shared with the name saploc. On local hosts, the \usr\sap\\ directory contains copies of the SAP software and local (instance-specific) data. During the installation of the central instance or dialog instance, and if not yet available SAPinst also creates the \usr\sap\\SYS\global and \usr\sap\ \ directories for the Diagnostics Agent on the installation host.NOTE

Since SAP traces for the instance are created in \usr\sap, make sure there is sufficient space available in this directory. Changes in SAP profiles can also affect the disk space.NOTE

The executables on the local host are replicated from those on the global host every time the local instance is started. The SAP copy program sapcpe compares the binaries in the directory on the global host and the binaries in the exe directory on the application server. If the binaries in the exe directory are elder than those in the directory, sapcpe replaces them with the newer version of the global host. Other application servers access the global data using the Universal Naming Convention (UNC) path \\\sapmnt. The SAP programs access their instance-specific data with the

104/212

PUBLIC

2009-05-04

6 6.1

Additional Information SAP Directories

UNC path \\\saploc. If the UNC path points to a local directory, the local path (and not the UNC path) is used to access the directory. The parameters SAPGLOBALHOST and SAPLOCALHOST have the same values on the global host.3\bCav!HMf}z]Yp2N?PVx

NOTE

Windows Server 2008 only: In a high-availability system, file shares pointing to directories on shared disks are only visible or accessible with the virtual host name of the cluster group the shared disks belong to. This lets you have several shares with the same name pointing to different disks (multi-SID).3\b.v1H)MC}[f]c

3y#

\usr\sap\trans

The transport directory contains SAP software for the transport of objects between SAP systems. SAPinst by default creates it on the SAPGLOBALHOST. If you want to have it created on another host or if you want to use an existing transport host from your SAP system landscape, you can specify another host during the installation. In this case, you have to prepare that host for the new SAP system to use it. For more information, see Preparing the SAP System Transport Host [page 54].Directory Structure

The following figures show how the physical directory \usr\sap is shared on the global host in a central and in a distributed system. In both cases, the UNC paths are used as follows: 3y# \\\sapmnt to access global directories 3y# \\\saploc to access local instance-specific data There is also a figure showing the directory structure of the Diagnostics Agent.NOTE

There are the following instance names available in an SAP system: Central services instance: SCS Central instance: JC Dialog instance: J. Diagnostics Agent instance: J3\bCav!HMf}z]Yp2N?PVx

Enqueue Replication Server instance: ERS3\b.v1H)MC}[f]c

NOTE

Every new installation of an SAP system is Unicode.

2009-05-04

PUBLIC

105/212

6 6.1

Additional Information SAP Directories

4N#Uv{X+R&Ko6Directory Structure on the Global Host in a Central Java System

4N#Uv{X+R&Kn6Directory Structure in a Distributed Java System

106/212

PUBLIC

2009-05-04

6 6.2

Additional Information Performing a Domain Installation Without Being a Domain Administrator

C+_DXzVRpI|gYZ5q:q05*c: