Installation - SAP Developer Workplace (EHP1)

Installation GuideSAP Developer Workplace for SAP NetWeaver 7.0 IncludingEnhancement Package 1

Target Audience

n System administratorsn Technology consultants

PUBLICDocument version: 1.0 ‒ 09/25/2008

Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version on SAP Service Marketplace http://service.sap.com/instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.0 9/25/2008 Initial Version

2/48 PUBLIC 09/25/2008

http://service.sap.com/instguides



Table of Contents

Chapter 1 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Software Components Overview . . . . . . . . . . . . . . . . . 51.2 Installation Considerations . . . . . . . . . . . . . . . . . . . 61.3 Developer Workplace Installation - Step by Step . . . . . . . . . . . 6

Chapter 2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 92.1 Checking Hardware and Software Requirements . . . . . . . . . . . 92.2 Preparing the Installation DVDs . . . . . . . . . . . . . . . . . 102.3 Installing the Java Development Kit . . . . . . . . . . . . . . . . 11

Chapter 3 Installation Procedure . . . . . . . . . . . . . . . . . . . . 133.1 Using SAPinst GUI . . . . . . . . . . . . . . . . . . . . . . 133.2 Installing SAP Developer Workplace . . . . . . . . . . . . . . . 143.3 Installing SAP Developer Studio only . . . . . . . . . . . . . . . 15

Chapter 4 Post-Installation Steps . . . . . . . . . . . . . . . . . . . . 174.1 Starting and Stopping the SAP System . . . . . . . . . . . . . . . 174.2 Running Deployment Tests . . . . . . . . . . . . . . . . . . 184.3 Starting the Visual Administrator . . . . . . . . . . . . . . . . 184.4 Starting and Stopping the SAP Software Delivery Manager (SDM) . . . . 184.5 Installing a Permanent SAP License . . . . . . . . . . . . . . . . 19

Chapter 5 Additional Information . . . . . . . . . . . . . . . . . . . 215.1 Users Created During the Installation . . . . . . . . . . . . . . . 215.2 Installing the SQL Server Database Software . . . . . . . . . . . . . 215.2.1 Installing the SQL Server Database Software with SQL4SAP . . . . . . . 225.2.2 Installing the SQL Server Database Software Manually . . . . . . . . . 235.2.2.1 Installing the SQL Server 2000 Database Software on 32-Bit Manually . . . 235.2.2.2 Installing the Corrected MS SQL Server Collation for MS SQL Server 2000 . . 255.2.2.3 Installing the SQL Server 2005 Database Server Software Manually . . . . 275.2.2.4 Installing the SQL Server 2005 Native Client Software Manually . . . . . 305.3 Uninstalling the Developer Workplace . . . . . . . . . . . . . . . 305.4 Troubleshooting for Automated Basic Configuration Steps . . . . . . . 315.4.1 SLD: Post-Installation Steps . . . . . . . . . . . . . . . . . . . 325.4.2 Post-Installation Steps for Composite Application Framework (CAF) . . . 32

09/25/2008 PUBLIC 3/48

5.4.2.1 Setting Up Roles . . . . . . . . . . . . . . . . . . . . . . . 325.4.2.2 Setting Configuration Parameters . . . . . . . . . . . . . . . . 335.4.3 Post-Installation Steps for Adobe Document Services (ADS) . . . . . . . 335.4.3.1 Checking the IIOP Service . . . . . . . . . . . . . . . . . . . 335.4.3.2 Checking Java Startup Properties . . . . . . . . . . . . . . . . . 345.4.3.3 Entering Credentials . . . . . . . . . . . . . . . . . . . . . 345.4.3.4 Creating a User for Basic Authentication . . . . . . . . . . . . . . 345.4.3.5 Creating a Web Service Destination . . . . . . . . . . . . . . . . 365.4.3.6 Creating an HTTP Destination . . . . . . . . . . . . . . . . . 375.4.4 Post-Installation Steps for Enterprise Portal (EP) . . . . . . . . . . . 385.4.4.1 Copying CMS_MAPPING Properties . . . . . . . . . . . . . . . 385.4.4.2 Renaming InitialPermissions.xml.template . . . . . . . . . . . . . 385.4.4.3 Renaming initialPermissionsKMC.xml.template . . . . . . . . . . . 385.5 SAPinst-specific Information . . . . . . . . . . . . . . . . . . 395.5.1 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . 395.5.2 Starting SAPinst on the Remote Host (Optional) . . . . . . . . . . . 405.5.3 Starting SAPinst GUI Separately (Optional) . . . . . . . . . . . . . 415.5.4 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . 42

4/48 PUBLIC 09/25/2008

1 Planning

1 Planning

This document explains how to install the SAP Developer Workplace for SAP NetWeaver 7.0 includingEnhancement Package 1 (SAP NetWeaver 7.0 EHP 1).

Check Documentation

You must read SAP Note 924983 before you start the installation. This SAP Note contains the mostrecent information on the installation, as well as corrections to the installation documentation.Make sure that you have the up-to-date version of the SAP Note, which you can find athttp://service.sap.com/notes.

1.1 Software Components Overview

The following table defines the installation components. Each table cell corresponds to oneinstallation component.

Component Description

SAP NetWeaver Developer Studio The SAP NetWeaver Developer Studio introduces SAP’s ownenvironment for developing Java-based, multiple-layeredbusiness applications. The new development environment isbased on Eclipse; an open source product with an open plug-inarchitecture that provides a suitable platform for incorporatingspecific functions. For more information, see the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including

Enhancement Package 1) English SAP NetWeaver Library SAP NetWeaverby Key Capability Application Platform by Key Capability JavaTechnology Java Development Manual Getting Involved Concepts ofthe Developer Studio .

SAP MaxDB DB software, DB instance, J2EE schema

MS SQL Server DB software needs to be installed before

SAP J2EE Central Instance J2EE dispatcher, 1 J2EE server process, SDM

SAP J2EE Central Services Message Server, Enqueue Server

You can choose between two scenario variants for SAP NetWeaver Developer Workplace.Depending on which scenario you choose, the following components will be installed:

n Developing Composite Applications

09/25/2008 PUBLIC 5/48

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

http://service.sap.com/notes

http://help.sap.com/nw70

1 Planning1.2 Installation Considerations

l Composite Applications Framework (CAF)l Enterprise Portal (EP)

n Developing Web Dynpro Applicationsl System Landscape Directory (SLD)l Adobe Document Services (ADS) (optional, required for Adobe forms)l Enterprise Portal (EP)

Figure 1: The figure below provides an overview of the relevant components.

1.2 Installation Considerations

SAP Developer Workplace for SAP NetWeaver 7.0 EHP 1 is installed on a single host running on a Windows2003 Advanced Server or Windows XP Professional. All components are installed during one singleinstallation routine.The installation provides the new Default Mode installation. This means that you see all the defaultvalues in the first screens. You can change the default values if required.

1.3 Developer Workplace Installation - Step by Step

This section provides an overview of the complete installation procedure.

1. Checking hardware and software requirements [page 9].2. Preparing the required DVDs [page 10].3. Installing the SQL Server database software [page 21] (optional).

6/48 PUBLIC 09/25/2008

1 Planning1.3 Developer Workplace Installation - Step by Step

4. Installing SAP Developer Workplace [page 14].5. Installing SAP Developer Studio only [page 15] (optional).6. Starting and stopping the SAP system [page 17].7. Running deployment tests [page 18].8. Starting the Visual Administrator [page 18].9. Starting and stopping the SAP Software Delivery Manager (SDM) [page 18].10. Installing a permanent SAP license [page 19].

09/25/2008 PUBLIC 7/48

This page is intentionally left blank.

2 Preparation

2 Preparation

You have to perform the followings steps as preparation:

1. Check the hardware and software requirements [page 9].2. Prepare the installation DVDs [page 10].3. Install the Java Development Kit [page 11].

2.1 Checking Hardware and Software Requirements

Minimum Hardware Requirements

n RAM: 1 GB required, 2 GB recommendedn CPU: 1.5 GHz required, 2 GHz recommendedn Disk Space:l For SAP MaxDB: 8.6 GB (3.1 GB temporary)

u3.1 GB (temporary): extracted <installation DVD>

u5.59 GB: Installed SAP NetWeaver Developer Workplace:

t SAP J2EE Engine: 3 GB

t SAP MaxDB: 2 GB

t SAP NetWeaver Developer Studio: 500 MB

Note

t You can distribute the SAP J2EE engine, the SAP MaxDB software and the SAPNetWeaver Developer Studio on different drives.

t The SAP MaxDB software is installed automatically during the installation of SAPDeveloper Workplace.

l ForMS SQL Server: 9.1 GB (3.1 GB temporary)

u3.1 GB (temporary): extracted <installation DVD>

u6 GB: Installed SAP NetWeaver Developer Workplace:

t SAP J2EE Engine: 3 GB

t MS SQL Server: 2.5 GB

t MS SQL Software 150 MB

t SAP NetWeaver Developer Studio: 500 MB

09/25/2008 PUBLIC 9/48

2 Preparation2.2 Preparing the Installation DVDs

Caution

The database software forMS SQL Server has to be installed before you start the installationof the SAP NetWeaver Developer Workplace.For more information about how to install the MS SQL Server software, see Installing theSQL Server Database Software [page 21].

Software Requirements

Requirement How to Check

n Microsoft Windows 2000 Professionaln Microsoft Windows XP 2002

Professional 32-BITFor more information about supportedoperating system releases, see theProduct Availability Matrix athttp://service.sap.com/pam.

NoteEnglish (International) version withNTFS file system; FAT partition is notsupported.

Installed SP?

1. Choose Start Run and execute the command winver.

2. Use the About Windows dialog box to check if your operatingsystemmeets the software requirements. If not, use the linkson the left to install the missing Support Package.

FAT or NTFS File System?

1. Open theWindows Explorer.

2. Select the drive C:\.

3. Choose File Properties .

4. Switch to the General tab to see the type of file system that isin use.

5. Check each drive on which you intend to perform theinstallation.

Installed Software Components?Choose Start Settings Control Panel Add/RemovePrograms .The Add/Remove Programs dialog box appears and displaysthe installed components.

SUN J2SE SDK version 1.4.2_09Even if you already have another SDKversion on your host, you can install therequired 1.4.2_09 version alongside theexisting version.For more information, seehttp://service.sap.com/pam.

CautionTogethersoft Users onlyIf (and only if) you have installed Togethersoft, you need toread SAP Note 564195 because Togethersoft modifies the SDKinstallation.

Internet Explorer 5.5 or higher In Internet Explorer, choose Help About Internet Explorer .

2.2 Preparing the Installation DVDs

Make sure that you have the following installation DVDs for your SAP product:

10/48 PUBLIC 09/25/2008

http://service.sap.com/pam



2 Preparation2.3 Installing the Java Development Kit

n Installation Master DVD

n RDBMS DVD

n Kernel DVD

Note

Use one of the following methods to make the DVDs simultaneously accessible:

n Before the installation:l Use a sufficient number of DVD drives

l Copy the DVDs manually to local hard disks

n During the installation:Use the SAPinst DVD / CD Browser dialog. You can check the entered location and then copy theentire DVD to the path you entered in column Copy Package to.

Downloading the DVD from SAP Service Marketplace

You can also download and prepare the installation DVD as follows:Download the installation DVD from SAP Service Marketplace on your local disk into a temporaryfolder (devwp, for example):

1. Go to http://service.sap.com/swdc Download Installations and Upgrades Entry by ApplicationGroup .

2. In the right frame, choose SAP NetWeaver SAP NetWeaver SAP EHP 1 for SAP NetWeaver 7.0Installation Windows Server <Oracle> OR <SAP DB> .

2.3 Installing the Java Development Kit

You need to prepare the system for the J2EE Engine by installing the Java Development Kit (JDK).As of SAP NetWeaver 7.0, you must install the J2EE Engine with strong encryption.The J2EE Engine requires a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK) on everyhost where the J2EE Engine is to be installed.The JDK includes the Java Runtime Environment (JRE), which is required both for SAPinst andthe SAPinst GUI.

Note

If required, you can perform a remote installation using a standalone SAPinst GUI on a separateWindows or UNIX host. This lets you perform the installation on a remote host, controlling it withthe SAPinst GUI from a local host.If you want to perform a remote installation, see Starting SAPinst on the Remote Host [page 40]. In this case,you need at least a JRE on the local host to start the SAPinst GUI.

09/25/2008 PUBLIC 11/48

http://service.sap.com/swdc

2 Preparation2.3 Installing the Java Development Kit

Procedure

1. Check the JDK versions that are released for SAP systems in the Product Availability Matrix (PAM):a) Go to http://service.sap.com/pam.b) On the right-hand panel, choose SAP NetWeaver SAP EHP 1 for SAP NetWeaver 7.0 JSE

Platforms .c) Choose tab pageJSE Platforms.For more information about the recommended JDK version, see SAP Note 709140.

2. Make sure a valid JDK version is installed on every host on which you want to install an SAPinstance with the J2EE Engine:n If JDK is not already installed

Since JDK is not part of the SAP shipment, you need to download and install it.n If JDK is already installed

Check the installed version of JDK by entering the following command:java —version

Note

SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

3. As of SAP NetWeaver 7.0, strong encryption is mandatory for the J2EE Engine and for all usagetypes that are deployed on it. You need to obtain the JCE policy files beforehand so that theycan be installed by SAPinst:a) Download the JCE policy files for your platform. For more information, see www.java.sun.com.b) SAPinst installs the JCE policy files during the installation process.

12/48 PUBLIC 09/25/2008



http://www.java.sun.com

3 Installation Procedure

3 Installation Procedure

Note

Make sure that you have completed the planning and preparation activities before you start theinstallation.

This section provides information about the steps that you have to perform to install your SAPDeveloper Workplace.

Caution

The database software for MS SQL Server has to be installed before you start the installation of theSAP NetWeaver Developer Workplace.For more information about how to install the MS SQL Server software, see Installing the SQL ServerDatabase Software [page 21].

3.1 Using SAPinst GUI

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

SAPinst GUI Functions

Button / Function Key / Menu Entries Description

F1 Displays detailed information about each input parameter.

Exit Cancels the installation with the following options:n Stop

Stops the installation without making further changes tothe installation files. You can restart SAPinst later on, inorder to continue the installation from this point.

n ContinueContinues the installation.

09/25/2008 PUBLIC 13/48

3 Installation Procedure3.2 Installing SAP Developer Workplace

Button / Function Key / Menu Entries Description

Log off Stops the SAPinst GUI, but SAPinst and the GUI server continuerunning.

NoteIf you need to log off from the host where you control theinstallation with SAPinst GUI (during the installation), theinstallation continues while you are logged off. You can laterreconnect to the same SAPinst installation either from thesame host or a different host. For more information, see StartingSAPinst GUI Separately [page 41].

Retry Performs the installation step again (if an error has occurred).

Stop Stops the installation without making further changes to theinstallation files. You can continue the installation later onfrom this point.

Continue Continues with the option you chose before.

3.2 Installing SAP Developer Workplace

1. Insert the SAP Installation Master DVD into your DVD drive or install it locally.2. Start SAPinst by double-clicking sapinst.exe from the following path:

<DVD drive>:\IM_WINDOWS_I386

SAPinst GUI starts automatically by displaying theWelcome screen.

Note

n Normally, SAPinst creates the installation directory sapinst_instdir directly under thepath <drive>:\Program Files\.Exception:If <drive>:\Program Files\ is not accessible or write-protected, SAPinst tries to create thedirectory sapinst_instdir directly under the temporary directory ($TEMP). If SAPinst does notfind the temporary directory, the installation terminates with the error FCO-00057.

n SAPinst uses the port 21212 during the installation for communication with the SAPinst GUI. Ifone of these ports is already used by another service, you must start SAPinst as follows:sapinstSAPINST_DIALOG_PORT=<free_port_number>

3. In theWelcome screen, choose SAP NetWeaver 7.0 including Enhancement Package 1 Developer Workplace .4. Choose Developer Workplace with SAP MaxDB or Developer Workplace with MS SQL Server.

14/48 PUBLIC 09/25/2008

3 Installation Procedure3.3 Installing SAP Developer Studio only

Note

SAPinst creates the subdirectory workplace under sapinst_instdir.

5. Follow the instructions on the screen.6. Decide whether you need to change the default parameters (see also Installation Considerations [page 6]):n No changes necessary

If you do not need to change any of the parameters, choose Next.In the screen Selecting the Master Password, enter the password that you want to create for thedisplayed accounts. The password must have at least 8 characters.

n Changes neededIf you need to change one ore more parameter values, select the appropriate checkbox andchoose Next.Depending on the selected parameters, different screens appear where you can change thenew values.

Once you have entered all the required values, SAPinst displays a summary screen where youcan check your values.

7. Choose Next to start the installation. The screen Start Installation is displayed.8. Choose Start to start the installation.

ResultThe installation automatically starts the J2EE Engine (SCS / Dispatcher / Server) and the SDM server(see minimized command prompt in your taskbar).The following is created:

n SAP MaxDB with the given instance (DBSID) with directory <drive>:\sapdb\... and databaseschema (SAP<SAPSID>DB)

n SAP Java system directory structure:

l <drive>:\usr\sap\<SAPSID>\JC<Instance_Number>

l <drive>:\usr\sap\<SAPSID>\SCS<Instance_Number>

l <drive>:\usr\sap\<SAPSID> \SYS

n SAP Management ConsoleWith the SAP Management Console, you can start and stop the SAP J2EE Engine and the SAPMaxDB.

3.3 Installing SAP Developer Studio only

With this function, you can install the SAP Developer Studio (Integrated Development Environment - IDE) only.

PrerequisitesYou have access to an SAP NetWeaver system.

09/25/2008 PUBLIC 15/48

3 Installation Procedure3.3 Installing SAP Developer Studio only

Procedure

1. Insert the SAP Installation Master DVD into your DVD drive or install it locally.2. Start SAPinst by double-clicking sapinst.exe from the following path:


SAPinst GUI starts automatically by displaying theWelcome screen.

Note

n Normally, SAPinst creates the installation directory sapinst_instdir directly below thepath <drive>:\Program Files\.Exception:If <drive>:\Program Files\ is not accessible or write-protected, SAPinst tries to create thedirectory sapinst_instdir directly below the temporary directory ($TEMP). If SAPinst does notfind the temporary directory, the installation terminates with the error FCO-00057.

n SAPinst uses the port 21212 during the installation for communication with the SAPinst GUI. Ifone of these ports is already used by another service, you must start SAPinst as follows:sapinstSAPINST_DIALOG_PORT=<free_port_number>

3. In theWelcome screen, choose SAP NetWeaver 7.0 including Enhancement Package 1 Developer Studio .4. Follow the instructions on the SAPinst screens.5. Decide whether you need to change the default parameters (see also Installation Considerations [page 6]):n No changes necessary

If you do not need to change any of the parameters, choose Next.In the screen Selecting the Master Password, enter the password that should be created for thedisplayed accounts. The password must have at least 8 characters.

n Changes neededIf you need to change one or more parameter values, select the appropriate checkbox andchoose Next.Depending on the selected parameters, different screens appear where you can adapt thenew values.

When you have entered all the required values, SAPinst displays a summary screen where youcan check your values.

6. Choose Next to start the installation and the screen Start Installation is displayed.7. Choose Start to start the installation.

16/48 PUBLIC 09/25/2008

4 Post-Installation Steps

4 Post-Installation Steps

After SAPinst has finished, you need to perform the following post-installation steps and checks.

4.1 Starting and Stopping the SAP System

You use this procedure to check that you can start and stop the SAP system after the installation withthe SAP Microsoft Management Console (SAP MMC).With a newly installed MMC, you can start or stop installed SAP instances locally on the host that youare logged on to. If the MMC is configured for central system administration, you can start or stopthe entire system from a single host.

Note

For more information, see http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (includingEnhancement Package 1) English SAP NetWeaver by Key Capability Solution Life Cycle Management by KeyCapability Solution Monitoring Monitoring in the CCMS Microsoft Management Console: Windows .

Prerequisites

n You have logged on to the SAP system host as user <sapsid>adm.n You have checked the settings for VM parameters as described in SAP Note 723909.

Procedure

1. Start the SAP MMC on the SAP system host by choosing Start Programs SAP ManagementConsole .

2. Right-click the SAP system node and choose Start or Stop from the context menu.All instances listed under the system node will start or stop in the correct order.

3. If the SAP system is installed on multiple hosts (distributed system), you have the followingoptions to start or stop your system:n You start or stop the SAP instances using the MMC on each host.n You add the remote instances to the MMC configuration to start or stop all instances from

a single MMC.For more information, see Changing the Configuration of the MMC in the SAP MMC documentation.

09/25/2008 PUBLIC 17/48



4 Post-Installation Steps4.2 Running Deployment Tests

4.2 Running Deployment Tests

1. Make sure that the SAP System is up and running (see Starting and Stopping the SAP System [page 17]).2. Start the J2EE engine by entering the following URL in your browser:

http://<hostname>:5<J2EEinstance_number>00

The J2EE engine Start Page should appear.3. Select Examples and run at least the last exampleMessage Driven Bean Example to test the SAP J2EE

engine.

4.3 Starting the Visual Administrator

1. To start the Visual Administrator, run \usr\sap\<SAPSID>\JC<xx>\admin\go.bat.The SAP J2EE Engine ‒ Administration screen appears.

2. From the menu, choose Connect Login .Enter new login data.

Note

Port: P4PortThe following convention applies to the port: 5<J2EEinstance_number>04For example, if your J2EE instance number is 00, the P4port is 50004.

3. Choose Connect.4. Exit the tool.

4.4 Starting and Stopping the SAP Software Delivery Manager(SDM)

Starting the SDMThe installation automatically starts the SDM Server.You can connect to the SDM server via remote GUI by running the command RemoteGui.bat from\usr\sap\<SAPSID>\JC<xx>\SDM\program\.Login data:

n Password: sdm

n Port: 5<J2EEinstance_number>18

Stopping the SDMRun stopServer.bat / startServer.bat from directory\usr\sap\<SAPSID>\JC<xx>\SDM\program\

18/48 PUBLIC 09/25/2008

4 Post-Installation Steps4.5 Installing a Permanent SAP License

4.5 Installing a Permanent SAP License

When you install your SAP system, a temporary license is automatically installed. This temporarylicense allows you to use the system for four weeks from the date of installation.Before the temporary license expires, you can apply for a permanent license key from SAP.For more information, see the SAP Library at http://help.sap.com/nw70 SAP NetWeaver 7.0Library (including Enhancement Package 1) English SAP NetWeaver by Key Capability Solution Life CycleManagement by Key Capability SAP Licenses SAP License Key SAP License Key SAP Licensing Procedure .

09/25/2008 PUBLIC 19/48


This page is intentionally left blank.

5 Additional Information

5 Additional Information

The following sections provides:

n a list of users that are created during the installation [page 21]n information on how to install the SQL Server Database software [page 21]n information on how to uninstall the Developer Workplace [page 30]n SAPinst-specific information [page 39]

5.1 Users Created During the Installation

The following users are created during the installation:

User Type User Comment

Operating system user <sapsid>adm SAP system administrator

Operating system user SAPService<SAPSID> User to run the SAP system

Operating system user sqd<dbsid> SAP MaxDB database administrator (that is, theowner of the database files)

Administrator J2EE_ADMIN This user’s password is stored in secure storage.Therefore, whenever you change the administrator’spassword, you must also change the password insecure storage.For more information, see the SAP JavaDocumentation at http://help.sap.com/nw70

SAP NetWeaver 7.0 Library (including Enhancement Package1 ) English SAP NetWeaver by Key CapabilityApplication Platform by Key Capability Java Technology .

Guest J2EE_GUEST None

Only valid for: MS SQL Server

5.2 Installing the SQL Server Database Software

The following sections describe how to install the SQL Server database software. The SQL Serversoftware has to be installed on each host in the system where you intend to set up an SAP instance.

09/25/2008 PUBLIC 21/48


5 Additional Information5.2 Installing the SQL Server Database Software

Depending on the type of host involved, you either have to install the software for the databaseclient or server.To install the SQL Server database software, you have the following options:

n Install SQL Server automatically with SQL4SAP [page 22].n Install the SQL Server database software manually [page 23].

5.2.1 Installing the SQL Server Database Software withSQL4SAP

This section describes how to install the SQL Server 2000 or SQL Server 2005 database softwareautomatically.

Note

For more information about installing with SQL4SAP.VBS, see Customized Installation of SQL Server for anSAP System with SQL4SAP.VBS (SQL4SAP_docu.pdf) and the readme.txt, both of which are located inthe root directory of the SQL Server RDBMS DVD.

n For SQL Server 2000, you use the SQL4SAP.VBS script to automatically install the:l SQL Server 2000 Enterprise Edition on 32-bit or 64-bit systems.l Latest SQL Server 2000 service packl Latest SQL Server hotfix, if required.l SQL_Latin1_General_CP850_BIN or SQL_Latin1_General_CP850_BIN2 collation.

Note

For up-to-date information about installing SQL Server 2000 with SQL4SAP.VBS, read SAP Note377430, which also includes the material number of the DVD containing the VB script.

n For SQL Server 2005, you use the SQL4SAP.VBS script to automatically install:l 32-bit SQL Server 2005 Enterprise Edition on x86 systemsl Default Instances, Named Instances, or SQL Server Client Tools Only.

Note

For up-to-date information about installing SQL Server 2005with SQL4SAP, read SAPNote 896566.

Procedure

1. For SQL Server 2000, insert the SQL Server 2000 RDBMS SP4 DVD into your DVD drive orconfigure the network share locally.

2. For SQL Server 2005, insert the SQL Server 2005 RDBMS DVD in your DVD drive or configurethe network share locally.

22/48 PUBLIC 09/25/2008




3. Double-click SQL4SAP.VBS located in the root directory.4. Follow the instructions and enter the required information in the installation screens.

5.2.2 Installing the SQL Server Database Software Manually

The following section describes how to install the SQL Server 2000 or SQL Server 2005 databasesoftware manually.

Note

If you install SQL Server 2000, the installation procedure depends on whether you have a 32-bit or64-bit system. It may also be necessary to install the corrected collation for SQL Server 2000.

5.2.2.1 Installing the SQL Server 2000 Database Software on32-Bit Manually

The MS SQL Server software has to be installed on each host in the system where you intend to set upan SAP instance. Depending on the type of host involved, you either have to install the software forthe database client or server.

n The software for the servermust be installed on the database host. It provides all the functionsrequired to run a relational database management system.

n The software for the clientmust be installed on all hosts without the database. It enables thecommunication between a host and the database.

Procedure

1. Log on to the host as a local administrator.

Caution

Make sure that you have not applied NTFS compression to the disk where you install the MSSQL Server software.

2. Insert the MS SQL Server 2000 RDBMS SP4 DVD into your DVD drive.3. Start the installation program with autorun.exe located in the x86\SQL2000 directory of the

MS SQL Server 2000 RDBMS SP4 DVD.

Note

Ignore the compatibility warning and choose Continue.

Enter the required information as specified in the table below.

09/25/2008 PUBLIC 23/48


Note

When you mount the DVD from a remote server, it must be assigned a drive letter.The installation writes a log file sqlstp.log to the Windows directory %windir%

Input for MS SQL Server Installation on 32-Bit Systems

Window Server Input Client Input

Microsoft SQL Server 2000 EnterpriseEdition

Select SQL Server 2000 Components. Select SQL Server 2000 Components.

Install Components Microsoft SQL Server2000 Enterprise Edition

Select Install Database Server. Select Install Database Server.

Welcome Choose Next. Choose Next.

Computer Name Select Local Computer. Select Local Computer.

Installation Selection Select Create a new instance of SQLServer, or install Client Tools.

Select Create a new instance of SQLServer or install Client Tools.

User Information Enter your personal information. Enter your personal information.

Software License Agreement Choose Yes. Choose Yes.

CD-Key Enter the key specified in thefile SAPCDKEY.txt in the rootdirectory of the RDBMS DVD.

Enter the key specified in thefile SAPCDKEY.txt in the rootdirectory of the RDBMS DVD.

Installation Definition Select Server and Client Tools. Select Client Tools Only.

Instance Name Select Default.Do not specify an instance name.

Dialog box does not appear.

Setup Type Select Custom. Dialog box does not appear.

Select Components Select all components. Select all components.

Service Accounts Select Use the same account for eachservice. Auto start SQL Server Service.Select Use the Local Systemaccount.


Authentication mode Select the authentication mode.We recommend to useWindowsauthentication mode.

NoteFor a Java system,Mixed mode isrequired. SAPinst automaticallychanges the authenticationmode into Mixed mode wheninstalling a Java system.


24/48 PUBLIC 09/25/2008


Window Server Input Client Input

Collation settings Select SQL Collations.From the dropdown list selectBinary order, for use with the 850(Multilingual) Character Set.


Network Libraries Leave selection unchanged andchoose Next.


Start Copying Files Choose Next. Choose Next.

Choose Licensing Mode Select the mode you require. Dialog box does not appear.

4. When you have finished the installation, install the latest Service Pack, and the latest hotfix, ifavailable, for SQL Server 2000.For more information about the latest Service Pack, see SAP Note 62988.For more information about the latest hotfix, see SAP Note 608651.

5. If you have installed the server software, install the corrected MS SQL Server collation [page 25]. For moreinformation about the SQL Server collation, see SAP Note 600027.

Only valid for: MS SQL Server

5.2.2.2 Installing the Corrected MS SQL Server Collation forMS SQL Server 2000

When you install the MS SQL Server 2000 database for an SAP system, in the field Collation Settings youhave to select Binary order, for use with the 850 (Multilingual) Character Set.This means that all new databases and table columns are created with this collation setting.

Note

To view the default collation of MS SQL Server, use the query:select serverproperty(’collation’)

This query returns the default collation of the overall server. When you have selected Binary order, foruse with the 850 (Multilingual) Character Set, it returns: SQL_Latin1_General_CP850_BIN

Unfortunately this collation setting does not sort Unicode data as it is required by an SAP system. Tosolve this problem, Microsoft provides a corrected collation for SQL Server.For more information about installing the collation, see SAP Note 600027.

Prerequisites

n You have installed the MS SQL Server 2000 database software. In the field Collation Settings, youselected Binary order for use with the 850 (Multilingual) Character Set.

09/25/2008 PUBLIC 25/48

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





n You have installed the latest service pack and hotfix, if available. For more information, see SAPNotes 62988 and 608651.

Note

Besides applying the latest service and hotfix, if available, you do not have to make any changeson the client side (SAP application servers).

n To obtain a correct collation order with MS SQL Server, you have to use the new collation for allnew installations of a Unicode or non-Unicode SAP system with the MS SQL Server database. Newversions of the SAPinst installation tool check for the new collation.

n A new SAP system using the new collation and an existing SAP system that is using the oldcollation cannot run as two databases in the same MS SQL Server instance. If you want to installa new system on a database server with an existing system you have to apply the new collationwith INSTCOLL.EXE.

1. Download the INSTCOLL.EXE file for your platform, which is attached as zip file to SAP Note600027, and extract it to your server.

2. Open a command prompt and change to the directory where you extracted the INSTCOLL.EXE file.3. Enter the following:n For a default instance enter: INSTCOLL.EXE

n For a named instance enter: INSTCOLL.EXE -S<server>\<instance> (without any spacesafter --S)

The executable starts the SQL Server Service if it is not running already and runs several checks.When you are asked to apply the new collation to all databases confirm with Y (Yes).When the conversion has finished, it restarts the SQL Server Service.

4. To check whether the MS SQL Server is properly configured, run:select serverproperty(’collation’)

Caution

You have to run INSTCOLL.EXE only once to apply the new collation. To convert a single SAPdatabase to the new collation, see SAP Note 600027.

ResultYou can now continue with the standard SAP system installation and install any SAP instance onthis server.End of: MS SQL Server

26/48 PUBLIC 09/25/2008

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





5.2.2.3 Installing the SQL Server 2005 Database ServerSoftware Manually

This section describes how to install the SQL Server 2005 database server software manually.The SQL Server 2005 database server software must be installed on the database host.You can also use the SQL4SAP script [page 22] to install SQL Server 2005.

Note

If you want to install the database client software manually, see Installing the SQL Server 2005 NativeClient (SNAC) Software [page 30].

Prerequisites

n When installing SQL Server 2005, make sure that you have enough free disk space available onthe system drive for:l .Net Framework 2.0

l SQL Server Client Toolsl SQL Server instancel Temporary space during the installation

The required disk space depends on the type of SQL Server components already installed or tobe installed. It also depends on the system.

n Make sure that the Microsoft Distributed Transaction Coordinator (MSDTC) service is running beforeyou start the installation.

Procedure

1. Log on to the host as a local administrator2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose Enterprise Edition Servers .4. Start the installation program with setup.exe.5. Enter the required information as specified in the table below.

Note

The installation writes the log files to the directory %ProgramFiles%\Microsoft SQL

server\90\Setup Bootstrap\LOG. You find the summary of the setup log in summary.txt inthe same directory.

Window Server Input

End User License Agreement Accept the licensing terms and conditions andchoose Next.

Installing Prerequisites Choose Install and, if required, Next.

09/25/2008 PUBLIC 27/48


Window Server Input

Welcome to the Microsoft SQL Server Installation Wizard Choose Next.

System Configuration Check a) Check your system configuration and, ifrequired, set up the required configuration.

Noten For more information about the required

system configuration for a softwarecomponent, chooseMessages.

n IIS is not required for an SAP system.Therefore, you can ignore the warningabout the IIS Feature Requirement.

n If there is a warning in COM Plus CatalogRequirement, correct the configuration beforeyou proceed with the installation. Makesure that the Microsoft Distributed TransactionCoordinator (MSDTC) service is running.

b) Choose Next.

Registration Information (if available) a) If this screen appears, enter your personalinformation.

b) Choose Next.

Components to Install a) Select:n SQL Server Database Servicesn Workstation components, Books Online and development

tools.

b) Choose Advanced

Feature Selection a) Expand Database Services and deselect Replication.

b) Expand Client Components and if available, deselectBusiness Intelligence Development Studio.

NoteWe recommend that you deselect these featuresas they are not required for an SAP system.

c) Choose Next.

Instance Name Select the instance you want to install and chooseNext.

NoteWe recommend that you install a Default instance.

28/48 PUBLIC 09/25/2008


Window Server Input

Service Account a) Select one of the following options:n Use the built-in System account for each service and

choose Local System or Network Service.n Use a domain user account, and enter the user

name and password.

b) Under Start services at the end of setupmake sure thatSQL Server and SQL Server Agent are selected.

NoteIf you use a named instance, you must alsoselect SQL Browser.

c) Choose Next.

Authentication Mode a) SelectMixed Mode (Windows Authentication and SQLServer Authentication).This mode is required for a Java or ABAP+Javasystem.If you choose this mode, you have to set thepassword for the sa login.

NoteSAPinst automatically changes theauthentication mode into Mixed Modewhen installing a Java system.The password for the sa login must complywith the Windows password policy.

b) Choose Next.

Collation Settings a) Select SQL collations (used for compatibility with previousversions of SQL Server).

b) From the dropdown list select Binary order based oncode point comparison, for use with the 850 (Multilingual)Character Set.

c) Choose Next.

Error and Usage Report Settings Leave the selection unchanged and choose Next.

Ready to Install Choose Install.

Setup ProgressNote

To see the log files for the SQL Server components,choose Setup finished.

When the setup process has finished, choose Next.

Completing Microsoft SQL Server 2005 Setup Choose Finish.

09/25/2008 PUBLIC 29/48

5 Additional Information5.3 Uninstalling the Developer Workplace

6. When you have finished the installation, enable the Named Pipes and TCP/IP protocol in the SQLServer Configuration Manager as follows:n Choose Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server

Configuration Manager .n Expand SQL Server 2005 Network Configuration and select one of the following:n For a default instance, select Protocols for MSSQLServer

n For a named instance, select Protocols for <SAPSID>n In the right-hand pane, under Protocol Name, right-click Named Pipes and TCP/IP, and select Enable.

7. Restart SQL Server.8. Install the latest SQL Server service pack and hotfix, if available. For more information, see SAP

Note 62988.

5.2.2.4 Installing the SQL Server 2005 Native Client SoftwareManually

This section describes how to install the SQL Server 2005 Native Client (SNAC) software.The SQL Server 2005 client software must be installed on all SAP application servers. It enables thecommunication between an application server and the database.

Procedure

1. Log on as local administrator to the host where you want to install an application server.2. Insert the SQL Server 2005 RDBMS DVD in your DVD drive or mount it locally.3. Change to the platform-specific folder and choose sqlncli.msi

Note

With every SQL Server service pack a new sqlncli.msi file is available in the specified directoryon the RDMBS DVD. You can also use this file to upgrade the SQL Native Client software.

4. Follow the instructions in the SQL Server installation setup screens.

End of: MS SQL Server

5.3 Uninstalling the Developer Workplace

You can uninstall the entire Developer Workplace.

Uninstalling the SAP Developer Workplace with SAPinstWith this procedure, you can uninstall the SAP NetWeaver AS Java and the database software.

30/48 PUBLIC 09/25/2008


5 Additional Information5.4 Troubleshooting for Automated Basic Configuration Steps

Note

You cannot uninstall the SAP NetWeaver Developer Studio by using this procedure. To uninstall theDeveloper Studio separately, refer to the documentation Installation Guide - SAP NetWeaver DeveloperStudio at http://service.sap.com/installnw70 Installation .

Note

You need the original SAP Developer Workplace Installation Master DVD for SAP NetWeaver 7.0 includingEnhancement Package 1 because the downloaded stack version does not contain this feature.

1. Log on to your installation host as a user with administrator rights.2. Insert the SAP Installation Master DVD in your DVD drive or install it locally.3. Start SAPinst by double-clicking sapinst.exe from the following path:


SAPinst GUI starts automatically by displaying theWelcome screen.4. In theWelcome screen, choose Uninstall Uninstall ‒ Developer Workplace .5. Follow the instructions on the screen.6. Define the SAPSID and DBSID that should be uninstalled.

You can also choose to uninstall the SAP NetWeaver Developer Studio.7. If you chose to uninstall the DBSID, the following screens appear:n Uninstalling the SAP MaxDB database schema / database / software

If you select Drop the whole database, the selected DBSID and its database schema is deleted.If you only select Remove for the database schema, only the database schema is deleted andnot the DBSID.

n Uninstalling the SAP MaxDB database schema / database / softwareThis second dialog only appears, if you have selected Drop the whole database above.Here you can define to uninstall the whole SAP MaxDB software.

8. On the Start Installation screen, choose Start to uninstall the software.Note that during the SAP MaxDB uninstall process, several pop-ups must be confirmed with OK.If you have decided to uninstall the SAP NetWeaver Developer Studio, the SAP NetWeaver DeveloperStudio Uninstall Wizard appears.

Caution

Do not cancel the SAPinst GUI during the Developer Workplace uninstall process, as you willnot be able to continue uninstalling the software with SAPinst.

5.4 Troubleshooting for Automated Basic Configuration Steps

You have to perform the following steps manually if SAPinst fails or if you want to adjust existingparameters or set additional parameters.

09/25/2008 PUBLIC 31/48

http://service.sap.com/installnw70




5.4.1 SLD: Post-Installation Steps

You have to perform the following post-installation steps for the SLD:

n Maintaining SLD Connection Parametersn Maintaining Server Settings in SLDn Uploading SLD Contentn Configuring the SLD Gateway/Startup Bridgen Maintaining the ABAP Connectionn Configuring the SLD Data Supplier Service

For more information, see the Post-Installation Guide ‒ System Landscape Directory SAP NetWeaver 7.0 athttp://service.sap.com/sld sld .

5.4.2 Post-Installation Steps for Composite ApplicationFramework (CAF)

You need to perform the following post-installation steps for Composite Application Framework(CAF) after SAPinst has finished.

5.4.2.1 Setting Up Roles

First you have to create the roles CAFAdmin and CAFUIAdmin. After setting up the roles, you canassign the roles to the dedicated users.

Setting Up the Administrator Role

1. Launch the User Administrator tool within SAP NetWeaver:http://<host>:<port>/useradmin

2. From the left pane, choose Roles.3. To create the role CAFAdmin, select the Create New icon.4. Enter CAFAdmin and a description (optional).5. From Available Actions, select com.sap.caf.rt.caf.aut and choose Add. The action appears in

the Selected Actions window.6. Choose Save.

CAFAdmin appears in the Roles list. If this does not happen, enter the role name next to New Searchand select the icon to search.

Note

By configuring CAFAdmin, you can allow the configuration of data source assignments for entityservices, as well as the import of external services.

32/48 PUBLIC 09/25/2008

http://service.sap.com/sld




7. To create the role CAFUIAdmin, repeat steps 3-6 above.This allows the configuration of user interface (UI) components.

Assigning Users

1. Repeat steps 1-2 as described above.2. From Roles, select the role you want to assign.

Multiple selections are allowed.3. Select the icon Assign User To…

The Assign User(s) window appears.4. Select the "plus" icon to add a user.5. Enter the name of any piece of information about the user you want to select and choose Search.6. Select the user from the list and choose Select.7. Choose Continue.

The user is assigned the role.

5.4.2.2 Setting Configuration Parameters

You have to adjust general system configuration parameters for CAF.For more information about these steps, see the CAF-GP Configuration Guide in the SAP Library athttp://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

Technology Consultant’s Guide Developing, Configuring, and Adapting Applications Creating CompositeApplications .

5.4.3 Post-Installation Steps for Adobe Document Services(ADS)

You need to perform the following post-installation steps for Adobe Document Services (ADS) afterSAPinst has finished.

5.4.3.1 Checking the IIOP Service

The startup mode of the service iiopmust be set to always. To verify this, you have to check andif required modify special settings on the central instance host.

Procedure

1. Start the configuration tool of the J2EE engine:Run <Drive:>\usr\sap\<SAPSID>\<instance_name>\j2ee\configtool.bat

09/25/2008 PUBLIC 33/48



The J2EE Engine ‒ Config Tool screen appears.2. In the left frame, open the tree Cluster data Global dispatcher configuration Services .3. Choose service iiop.4. The field Startup mode in the right frame must be set to always.5. Choose Apply changes.6. Repeat the steps 2 to 5 for the following path: Cluster data Global server configuration Services .

5.4.3.2 Checking Java Startup Properties

You have to check if the Java startup property for Adobe document services is set. To do so, you haveto check and if required modify special settings on the central instance host.

Procedure

1. Start the configuration tool of the J2EE engine:Run \usr\sap\<SAPSID>\<instance_number>\j2ee\configtool.bat

The J2EE Engine ‒ Config Tool screen appears.2. Select cluster data instance_<IDxxxx> server_<IDxxxx> .3. In the right frame, check if the following line exists in the Java Parameters area of the tab General:

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.

services.ts.jts.ots.PortableInterceptor.JTSInitializer

If the line does not exist, add the line to this section.

5.4.3.3 Entering Credentials

Since the installation asks for an Adobe Credentials file during the installation, you need to have thisfile available during the installation.Obtain the Adobe Credential file as described in SAP Note 736902.

5.4.3.4 Creating a User for Basic Authentication

To ensure secure access, you must create a user and assign the security role ADSCaller to this user.The ADSCaller security role was created during the SAP system installation.

Caution

Do not assign this security role to users other than the system user that you will use to accessAdobe document services.

34/48 PUBLIC 09/25/2008



You can create this user in the J2EE Engine or in the SAP NetWeaver usage type AS ABAP dependingon the J2EE installation settings for the SAP User Management Engine (UME). You create this userin the usage type AS ABAP when the UME is configured against the SAP NetWeaver usage type ASABAP back-end. In this case you also have to create a role ADSCallers in the usage type AS ABAP andassign the user ADSUser to this role.

Procedure

Creating a User in AS Java

1. Log on to the Visual Administrator of the J2EE Engine as follows:.a) On your central instance host, change to the following directory:

\usr\sap\<SAPSID>\<instance_name>\j2ee\admin

b) Double-click go.bat.2. On the Cluster tab, choose Server <x> Services Security Provider .3. On the User Management tab, choose Create Group to create a group called ADSCallers, if the group

does not exist. In the dialog box that follows, enter the name and choose OK.4. Choose Create User.

The Create New User dialog box appears.5. In the User name, Password, and Confirm password fields, enter ADSUser for the user name and enter a

password.6. Choose Tree in the right panel.7. In the User Tree, choose ADSCallers and then OK.8. Choose Tree in the left panel.9. Select ADSCallers ADSUser .10. In the Authentication field, choose No password change required.11. On the Policy Congurations tab, in the Components area, choose

com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.12. On the Security Roles tab, choose ADSCaller from the Security Roles list.13. In theMappings field, choose Add, which is assigned to Users.

The Choose Users or Groups dialog box appears.14. Choose Tree.15. In the User Tree, under the ADSCallers group, select the ADSUser that you just created and choose

OK.The new user is assigned to the ADSCaller security role.

Creating a User in AS ABAP

1. Log on to the SAP system as a user with administrator rights, in the client that is used for theUME authentication.

2. Choose Tools Administration User Maintenance User (transaction SU01).3. Enter ADSUser as user name and choose Create.

09/25/2008 PUBLIC 35/48


4. Choose system user as type for ADSUser.5. Choose Tools Administration User Maintenance Role Administration Roles (transaction PFCG).6. Create a role ADSCallers (no authorizations required).7. Activate the role.8. Assign the user ADSUser to this role.9. Log on to the Visual Administrator of the J2EE Engine as follows:

a) On your central instance host, change to the following directory:\usr\sap\<SAPSID>\<instance_name>\j2ee\admin

b) Double-click go.bat.10. On the Cluster tab, choose Server <x> Services Security Provider .11. On the User Management tab, choose Tree in the left panel.12. In the User Tree, make sure that the user you created in ABAP appears under the ADSCallers group.13. On the Policy Congurations tab, in the Components area, select

com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.14. On the Security Roles tab, choose ADSCAller from the Security Roles list.15. In theMappings area, choose Add, which is assigned to Users.

The Choose Users or Groups box appears.16. Choose Tree.17. In the User Tree, under the ADSCallers group, select the ADSUser you just created and choose OK.

The new user is assigned to the ADSCaller security role.

5.4.3.5 Creating a Web Service Destination

1. Log on to the Visual Administrator of the J2EE engine as follows:a) On your central instance host, change to the following directory:


b) Double-click go.bat.2. On the Cluster tab, choose Server <x> Services Web Services Security .3. Choose Web Service Clients sap.com > tc~wd~pdfobject com.sap.tc.webdynpro.adsproxy.AdsProxy*Cong-

Port_Document .4. From the Authentication list, choose BASIC.5. In the User and Password fields, enter ADSUser as user name and a password.6. Choose Save.7. Activate the authentication data by navigating to Services Deploy .8. Choose Application.9. In the tree, choose sap.com/tc~wd~pdfobject .10. Choose Stop Application.11. To restart the application, choose Start Application.

36/48 PUBLIC 09/25/2008


Note

If the Adobe document services and the Web Dynpro runtime environment are not installed on thesame J2EE Engine, you have to configure a Custom URL. For more information, see:http://help.sap.com/nw70 SAP NetWeaver 7.0 Library (including Enhancement Package 1) English

SAP NetWeaver by Key Capability Application Platform by Key Capability Java Technology AdministrationManual Administration/Configuration of Web Dynpro Runtime Environment Web Dynpro-Specific URLParameters Configuring the Web Dynpro Runtime Environment.

5.4.3.6 Creating an HTTP Destination

You have to create an HTTP destination to the back-end where the Adobe document services areinstalled.

Procedure

1. Start the Visual Administrator of the J2EE Engine as follows:a) On your central instance host, change to the following directory:


b) Double-click go.bat.2. On the Cluster tab, choose Server <x> Services Destinations .3. Under Runtime, choose HTTP. The information that applies to a selected destination is displayed in

the right pane.4. In the navigation panel, choose New.5. In the dialog box that follows, enter the name FP_ICF_DATA_<SAPSID> ‒ where <SAPSID> specifies

the back-end where the Adobe document services are installed ‒ for the new destination andchoose OK.

6. As the target URL, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAPin the URL field:http://<J2EE_host>:<J2EE_port>

and for SSL:https://<J2EE_host>:<J2EE_port>

Note

To display the host name of your SAP NetWeaver AS ABAP, log on your ABAP system and calltransaction SICF. In the main menu, choose Go to Port Information . The HTTP_port is specifiedunder Services.

7. Select the authentication method to use for the connection, and enter the parameters for theauthentication method in the corresponding fields.n In the Username field, enter ADS_AGENT (must exist as service user in usage type AS ABAP).

09/25/2008 PUBLIC 37/48



n In the Password field, enter the same password as given for the AS ABAP service user ADS_AGENT.8. If the connection is to use HTTPS, specify how the connection should handle SSL server

authentication.9. Save your settings.

5.4.4 Post-Installation Steps for Enterprise Portal (EP)

You need to perform the following post-installation steps for Enterprise Portal (EP) after SAPinsthas finished.

5.4.4.1 Copying CMS_MAPPING Properties

Copy the cms_mapping.properties file from the source directory/usr/sap/<sid>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/servlet_jsp/irj/

root/WEB-INF/portal/system/pcd/Migration/mapping/

into the target directory/usr/sap/<sid>/SYS/global/pcd/Migration/mapping/.

Note

If the target directory does not exist, you have to create it.

5.4.4.2 Renaming InitialPermissions.xml.template

1. Go to the directory/usr/sap/<id>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/servlet_jsp/irj/

root/WEB-INF/portal/system/xml/acl

2. Rename the file initialPermissions.xml.template asinitialPermissions.xml.

5.4.4.3 Renaming initialPermissionsKMC.xml.template

1. Go to the directory/usr/sap/<sid>/JCxx/j2ee/cluster/server<x>/apps/sap.com/irj/servlet_jsp/irj/

root/WEB-INF/portal/system/xml/acl.2. Rename the file initialPermissionsKMC.xml.template as initialPermissionsKMC.xml.

38/48 PUBLIC 09/25/2008

5 Additional Information5.5 SAPinst-specific Information

5.5 SAPinst-specific Information

5.5.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:

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 as a user who is a member of the local administrators group.2. Insert the Installation Master DVD in your DVD drive.3. Change to the required directory

<DVD drive>:\IM_WINDOWS_<platform>

Double-click sapinst.exe

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

09/25/2008 PUBLIC 39/48


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.

5.5.2 Starting SAPinst on the Remote Host (Optional)

You can 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 the hostfrom which you want to control the installation with SAPinst GUI.

Prerequisites

n You have installed the Java Development Kit [page 11].n Both computers are in the same network and can ping each other.

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

Procedure

1. Log on to your remote host with a user that belongs to the local administrators group.2. Insert the Installation Master DVD in the DVD drive on your remote host.3. Open a command prompt, and enter the following commands:

cd <DVD drive>:\IM_WINDOWS_<platform>

sapinst.exe –nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following atthe command prompt:guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

4. Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 41].

40/48 PUBLIC 09/25/2008


5.5.3 Starting SAPinst GUI Separately (Optional)

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

n You have logged off from SAPinst.If you logged off during the installation and you want to reconnect to the installation (that is stillrunning) later on, you can start SAPinst GUI separately.

n You want to perform a remote installation.If SAPinst GUI runs on a different host than the host for SAPinst and the GUI server, you alsohave to start SAPinst GUI separately.

PrerequisitesYou have installed the Java Development Kit [page 11].

Procedure

1. Log on as a member of the local administrators group.2. Insert the SAP installation DVD into your DVD drive.3. To change to the relevant directory, enter the following command:

cd <DVD drive>:\IM_WINDOWS<platform>

4. Start SAPinst GUI in one of the following ways:n If SAPinst GUI runs on the same host as SAPinst and the GUI server, enter the following

command without additional parameters:startinstgui.bat

SAPinst GUI uses the local host as default.n If SAPinst and the GUI server runs on a different host than the host for SAPinst GUI (remote

installation), enter the following commandwith additional parameters:startinstgui.bat -host <host_name>

<host_name> is the host name of the installation host.

Note

l If you enter the command without additional parameters, SAPinst GUI uses the local hostas default. SAPinst GUI starts and tries to connect to the GUI server and SAPinst. SinceSAPinst and the GUI server are running on another host, SAPinst GUI cannot connect andthe SAP Installation GUI Connection dialog appears.In this case, enter the name of the host on which SAPinst is running and choose Log on.The first dialog of the installation appears and you can perform the remote installationfrom your local host.

l For a list of options to start SAPinst GUI, change to the same directory as your SAPinstexecutable and enter the command startinstgui.bat —h.

09/25/2008 PUBLIC 41/48


5.5.4 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.2. If an error occurs during the dialog or processing phase, do either of the following:n Try to solve the problemn Abort the installation with Exit

For more information, see Interrupted Installation with SAPinst [page 39].n Continue the installation by choosing Retry.

3. Check the log and trace files of the GUI server and SAPinst GUI in the directory%userprofile%\.sdtgui\ for errors.n If GUI server or SAPinst GUI do not start, check the file sdtstart.err in the current

%userprofile% directory.n If SAPinst GUI aborts during the installation without an error message, restart SAPinst GUI as

described in Starting SAPinst GUI Separately [page 41].4. Ignore error messages in the SDM logs that software components are not available. For more

information, see SAP Note 828978.

42/48 PUBLIC 09/25/2008


Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

09/25/2008 PUBLIC 43/48

http://www.sap.com



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.

44/48 PUBLIC 09/25/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

09/25/2008 PUBLIC 45/48

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

46/48 PUBLIC 09/25/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

09/25/2008 PUBLIC 47/48


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.

Installation - SAP Developer Workplace (EHP1)

Documents

Transcript of Installation - SAP Developer Workplace (EHP1)