THE BEST RUN. INSTALLATION GUIDE PUBLIC Software Provisioning Manager 1.0 SP24 Document Version:

Transcription

1 INSTALLATION GUIDE PUBLIC Software Provisioning Manager 1.0 SP24 Document Version: SAP SE or an SAP affiliate company. All rights reserved. Installation of SAP NetWeaver Developer Workplace Valid for SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Composition Environment 7.2, Systems Based on SAP NetWeaver 7.1 to SAP NetWeaver 7.3 Including Enhancement Package 1 THE BEST RUN

2 Content 1 About this Document Planning Preparation Installation Installation Installing SAP NetWeaver Developer Workplace SAP NetWeaver Developer Studio Installing SAP Memory Analyzer (Optional) Post-Installation Post-Installation Applying the Latest Kernel and Support Package Stacks Performing Automated Configuration Additional Information Additional Information Installation of Additional Usage Types to an Existing SAP System Performing a Developer Workplace Update with SUM Using the SL Common GUI Troubleshooting Repairing an Inconsistent SAP MaxDB Installation Restarting the SAP MaxDB Server Manually Restarting the MS SQL Server Manually Uninstalling the SAP NetWeaver System P U B L I C Content

3 Document History Before you start reading, make sure you have the latest version of this installation guide, which is available at System Provisioning Install a System using Software Provisioning Manager Installation Option of Software Provisioning Manager 1.0 SP <Current Number>. The following table provides an overview on the most important document changes: Version Date Description Updated version for Software Provisioning Manager 1.0 SP24 (SL Toolset 1.0 SP24) Updated version for software provisioning manager 1.0 SP23 (SL Toolset 1.0 SP23) Updated version for software provisioning manager 1.0 SP22 (SL Toolset 1.0 SP22) Updated version for Software Provisioning Manager 1.0 SP21 (SL Toolset 1.0 SP21) Updated version for Software Provisioning Manager 1.0 SP20 (SL Toolset 1.0 SP20) Updated version for Software Provisioning Manager 1.0 SP19 (SL Toolset 1.0 SP19) Updated version for Software Provisioning Manager 1.0 SP18 (SL Toolset 1.0 SP18) Updated version for Software Provisioning Manager 1.0 SP17 (SL Toolset 1.0 SP17) Updated version Updated version Document History P U BL IC 3

4 Version Date Description Updated version Updated version Initial version 4 P U B L I C Document History

5 1 About this Document This document explains how to install the following SAP NetWeaver releases as developer workplace: SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 SAP NetWeaver Composition Environment 7.2 SAP NetWeaver 7.3 SAP NetWeaver 7.3 including Enhancement Package 1 You perform the installation using the installation tool using the installation tool software provisioning manager 1.0 SP24 ( installer for short), which is part of SL Toolset 1.0 SP24. Software provisioning manager is the successor of the product- and release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation or system copy, we recommend that you always download the latest version of the software provisioning manager [page 12], which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note As a result, SAPinst has been renamed to software provisioning manager (installer for short) in this documentation. However, the term SAPinst is still used in: Texts and screen elements in the software provisioning manager GUI Naming of executables, for example sapinst Naming of Command line parameters, for example SAPINST_HTTP_PORT Operating system user groups, for example additional group sapinst Before you start with this installation guide, make sure you have read the corresponding Master Guide for you release, which you can find at: SAP NetWeaver Composition Environment 7.1: Installation and Upgrade SAP NetWeaver Composition Environment 7.1 including enhancement package 1: Installation and Upgrade SAP NetWeaver Composition Environment 7.2: SAP NetWeaver 7.3: Installation and Upgrade Installation and Upgrade SAP NetWeaver 7.3 including enhancement package 1: Installation and Upgrade About this Document P U B L I C 5

6 SAP Notes for the Installation Before you start the installation, make sure you have read the latest version of the following SAP Notes: SAP Note Release Note for Software Provisioning Manager 1.0 SAP Note This SAP Note contains the most recent information on the installation, as well as corrections to the installation documentation. Naming Conventions installer refers to software provisioning manager 1.0 SAP system refers to SAP NetWeaver Composition Environment 7.1, SAP NetWeaver Composition Environment 7.1 including enhancement package 1, SAP NetWeaver Composition Environment 7.2, SAP NetWeaver 7.3 or SAP NetWeaver 7.3 including enhancement package 1 MS SQL Server only: SQL Server Terminology In this document, SQL Server 2008 (R2) with (R2) written in parentheses means that the information applies to both SQL Server 2008 and SQL Server 2008 R2. 6 P U B L I C About this Document

7 2 Planning This section includes the planning steps for your installation. You must first: 1. Plan your SAP system landscape according to the Master Guide available for your product. 2. Decide on your installation option. SAP strongly recommends that you install SAP NetWeaver Developer Workplace on 64-bit only. If you insist on installing SAP NetWeaver Developer Workplace on 32-bit, report an incident on component BC-INS to get support from SAP. Installation Options This section provides information about the following in the installer: SAP NetWeaver <Release> Developer Edition <Database> Install SAP NetWeaver Release SAP NetWeaver 7.3 including enhancement package 1 or higher Installation Options SAP NetWeaver Developer Studio [page 20] Server Installation [page 16] The installation is performed with default settings. If you want to change any of the default settings, you can do so on the Parameter Summary screen. SAP NetWeaver 7.3 SAP NetWeaver Developer Studio [page 20] Server Installation [page 16] The installation is performed with default settings. If you want to change any of the default settings, you can do so on the Parameter Summary screen. SAP NetWeaver Composition Environment 7.2 SAP NetWeaver Developer Studio [page 20] Typical Server Installation The installation is performed with default settings. If you want to change any of the default settings, you can do so on the Parameter Summary screen. Planning P U B L I C 7

8 SAP NetWeaver Release SAP NetWeaver Composition Environment 7.1 including enhancement package 1 Installation Options SAP NetWeaver Developer Studio [page 20] Java EE Application Server [page 16] The installation is performed with default settings. If you want to change any of the default settings, you can do so on the Parameter Summary screen. Custom Server Installation [page 16] If you choose this option, you are prompted for all parameters. At the end, you can still change any of these parameters on the Parameter Summary screen. Add Server Capability [page 24] Installs additional components to an existing SAP NetWeaver developer workplace system SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Developer Studio [page 20] SAP CE Development System [page 16] Installs an SAP Composition Environment (CE) system as developer workplace. Add Server Capability [page 24] Installs additional components to an existing SAP NetWeaver developer workplace system Add ESR Capability Installs Enterprise Services Repository in an existing SAP Composition Environment (CE) 7.1 developer workplace system Memory Analyzer [page 20] SAP NetWeaver <Release> Developer Edition <Database> System Copy This option is not available for the following SAP NetWeaver Developer Workplace releases: SAP NetWeaver Composition Environment 7.1 including enhancement package 1 SAP NetWeaver Composition Environment 7.1 Choose this option to perform a system copy. For more information, see the system copy guide valid for SAP systems based on SAP NetWeaver 7.1 and higher, which you can find at: System Provisioning System Copy Option of Software Provisioning Manager System Copy Guides. Uninstall Uninstalls an SAP NetWeaver system. For more information, see Uninstalling Your System [page 28]. 8 P U B L I C Planning

9 Hardware and Software Requirements for Development Systems Before you start the installation, make sure you meet the hardware and software requirements for your operating system (OS) and the SAP NetWeaver system. Consider the following information: For supported operating system releases, see the Product Availability Matrix on SAP Service Marketplace at Contact your OS vendor for the latest OS patches. The host must meet the following requirements: Requirement Type Requirement Hardware 20 GB free disk space Min. 1 CPU with 3 GHz Minimum 6 GB RAM, recommended 8 GB RAM Paging file size: 2x RAM To check the paging file size: 1. Right-click My Computer and choose Properties. 2. Choose Advanced Performance Settings. 3. If required, in section Virtual Memory, choose Change. SAP strongly recommends that you install SAP NetWeaver Developer Workplace on 64-bit only. If you insist on installing SAP NetWeaver Developer Workplace on 32-bit, report an incident on component BC-INS to get support from SAP. Planning P U B L I C 9

10 Requirement Type Requirement Software Supported Operating Systems: WINDOWS SERVER 2008/IA64 64BIT WINDOWS SERVER 2008/X64 64BIT WINDOWS SERVER 2012/X64 64BIT WINDOWS SRV 2008 R2/IA64 64BIT WINDOWS SRV 2008 R2/X64 64BIT SAP strongly recommends that you install SAP NetWeaver Developer Workplace on 64-bit only. If you insist on installing SAP NetWeaver Developer Workplace on 32-bit, report an incident on component BC-INS to get support from SAP. Supported Databases: SAP MaxDB 7.9 The SAP MaxDB software is installed with the SAP NetWeaver system. MS SQL Server 2008 (R2) If you want to use the MS SQL Server database, you have to install it before installing SAP NetWeaver. JDK version: Caution SAP NetWeaver Developer Studio requires a 64-bit Java Development Kit (JDK). You must install it in the <installation_folder_of the_developer_studio>\eclipse\jre directory or in another location referred by the JAVA_HOME variable of your Windows OS. Make sure you use the JDK, and not the JRE, even though the location that the Developer Studio expects contains the jre\bin string. The following 64-bit JDKs are supported: SAP JVM 6.0 or higher Oracle Java SE Development Kit 1.6.0_7 or higher 10 P U B L I C Planning

11 If you want to install additional components (optional) [page 24], you need the same hardware and software requirements as stated above plus an additional 2 GB RAM. Planning P U BL IC 11

12 3 Preparation This section includes the preparation steps that you have to perform before you proceed with the installation. Downloading the Java Cryptography Extension Jurisdiction Policy Files Archive The SAP Java Virtual Machine (SAP JVM) is not delivered with Java Cryptography Extension (JCE) Jurisdiction Policy files. The delivery of these is subject to import restrictions in some countries. The JCE jurisdiction policy files must be available beforehand so that the installer can install them if required. Prerequisites Make sure there is not an older version of the JCE policy zip file for your platform on the installation host. Caution If there is an old JCE policy zip file, the Prerequisite Checker does not recognize this fact. For this reason, the installer issues the error message java.lang.securityexception during the Create Secure Store step, stating the jurisdiction policy files are not signed by trusted signers. If you want to install usage type or software unit Adobe Document Services, make sure that you download the unlimited version of the JCE Jurisdiction Policy files. Procedure Download the JCE jurisdiction policy files as described in SAP Note Preparing the Installation Media This section describes how to prepare the installation media, which are available as follows: The software provisioning manager 1.0 archive containing the installer as such. You always have to download the latest version of the software provisioning manager 1.0 archive. The media containing the software to be installed, which are available as follows: Prerequisites You normally obtain the physical installation media as part of the installation package. You can also download the installation media apart from the software provisioning manager 1.0 archive from SAP Service Marketplace, as described at the end of this section. Make sure the latest version of the SAPCAR archiving tool is available on each installation host. You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files) which is the format of software life-cycle media and tools that you can download from the SAP software distribution center. 12 P U B L I C Preparation

13 If required, you can download the latest version of SAPCAR from: Support Packages and Patches A Z Index S SAPCAR. For more information about SAPCAR, see SAP Note Procedure 1. Download the latest version of the software provisioning manager 1.0 archive SWPM10SP<support package number>_<version number>.sar from the following location: Support Packages and Patches A - Z Index S SL Toolset SL Toolset <release> Entry by Component Software Provisioning Manager Software Provisioning Manager 1.0 Windows 2. Unpack the software provisioning manager archive to a local directory using the following command: SAPCAR xvf <download directory>/<path>/<archive>.sar -R <unpack directory> 3. Make the media containing the software to be installed available. You can do this in one of the following ways: Copy the required media folders directly to the installation hosts. Mount media on a central media server that can be accessed from the installation hosts. Caution If you copy the media to disk, make sure that the paths to the destination location of the copied media do not contain any blanks. Downloading from SAP Service Marketplace the Installation Media Containing the Software to be Installed You normally obtain the installation media as part of the installation package from SAP. However, you can also download installation media from the software distribution center on SAP Service Marketplace using one of the following paths: You always have to download the software provisioning manager 1.0 archive (SWPM10SP<support package number>_<version number>.sar) from the software distribution center because you have to use the latest version (see above). Installations and Upgrades My companys application components <your product> <your product version> Installations and Upgrades A-Z index <first letter of your product> <your product version> If you download installation media, note that they might be split into several files. In this case, you have to reassemble the required files after the download. 1. Create a download directory on the host where you want to run the installer. Preparation P U BL IC 13

14 2. Identify all download objects that belong to one installation medium according to one or both of the following: Material number All download objects that are part of an installation medium have the same material number and an individual sequence number: <material_number>_<sequence_number> Example _ _2... Title All objects that are part of an installation medium have the same title, such as <solution><media_name><os> or <database>rdbms<os> for database media. 3. Download the objects to the download directory. 4. To correctly re-combine the media that are split into small parts, you must unpack all parts into the same directory. In the unpacking directory, the system creates a subdirectory with a short text describing the medium and copies the data into it. The data is now all in the correct directory, the same as on the medium that was physically produced. For more information, see SAP Note Only Valid for MS SQL Server: Preparations for the MS SQL Server Database Before starting the installation check the following: The default collation of your database server is SQL_Latin1_General_CP850_BIN2 1. Start the SQL Server Management Studio. 2. Connect to your server. 3. Right-click the server and in the context menu, choose Properties. 4. Check the server collation on the general page. 5. If the server collation differs from SQL_Latin1_General_CP850_BIN2, you have to reinstall it or use a different MS SQL Server instance. SQL Server logins are enabled. 1. Start the SQL Server Management Studio. 2. Connect to your server. 3. Right-click the server and in the context menu, choose Properties. 4. Switch to the security page. Under Server Authentication, make sure that the entry SQL Server and Windows Authentication mode is selected. If only Windows Authentication mode is selected, change it to SQL Server and Windows Authentication mode and restart the server for the changes to take effect. TCP/IP protocol is enabled and your server is able to communicate on the TCP port. 1. Start the SQL Server Configuration Manager from the following path: Start All Programs MS SQL Server 2008 Configuration Tools. 14 P U B L I C Preparation

15 2. Expand SQL Server Network Configuration and select your instance. 3. In the right-hand pane, make sure that protocol TCP/IP is set to enabled. For more information about how to configure the TCP/IP connection properly, see SQL Server Books Online. Preparation P U BL IC 15

16 4 Installation 4.1 Installation This section includes the installation steps that you have to perform for: Installing SAP NetWeaver Developer Workplace [page 16] Installing SAP NetWeaver Developer Studio [page 20] Installing SAP Memory Analyzer (Optional) [page 20] Detailed information about the steps is available in the relevant chapter. 4.2 Installing SAP NetWeaver Developer Workplace This section describes how to run the installation tool Software Provisioning Manager 1.0 (the installer for short). Software Provisioning Manager (the installer for short) offers two GUIs: The new web browser-based SL Common GUI of the Software Provisioning Manager - SL Common GUI for short The classic Java-based GUI with a CUI client and server - Java SDT GUI for short If the SL Common GUI does not meet your requirements you can still use the classic Java SDT GUI. You then have to start the sapinst executable with the command line option SAPINST_SLP_MODE=false. In cases where both GUIs behave the same way, we address them as installer GUI. This procedure describes an installation where you use one of the following GUI scenarios: You run the installer and use the SL Common GUI. Then you can control the processing of the installer in the browser running on any device. You run the installer and use the Java SDT GUI. Both are running on the same host. The installer includes an installer GUI and a GUI server, which both use Java. This section describes an installation where the installer, the installer GUI, and the GUI server are running on the same host. Note the following information about the installer: When you start the installer, the installer GUI and the GUI server also start. The installer GUI connects to the GUI server with a secure SSL connection, and the GUI server connects to the installer. The installer normally creates the installation directory sapinst_instdir, where it keeps its log files, and which is located directly in the Program Files directory. If the installer is not able to create 16 P U B L I C Installation

17 sapinst_instdir there, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP. Recommendation We recommend that you keep all installation directories until the system is completely and correctly installed. The installer creates a subdirectory for each installation option called <sapinst_instdir> \<installation_option_directory>, which is located in %ProgramFiles%\. The installer Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after the installer has stopped running. Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. The temporary directory also contains the installer Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. Caution If the installer cannot find a temporary directory, the installation terminates with the error FCO If you want to terminate the installer and the installer Self-Extractor, choose one of the following options: Right-click the icon for the installer output window located in the Windows tray and choose Exit. Click the icon for the installer output window located in the Windows tray and choose File Exit. How to Avoid Automatic Logoff by the Installer When you install the SAP system, the installation tool checks whether the user account used for the installation has the required privileges and authorization. For a domain installation, the account needs to be both a member of the local Administrators group and the domain Admins group. For a local installation, the account needs to be a member of the local Administrators group. In both cases, the user account must be authorized to do the following: Act as part of the operating system Adjust memory quotas for a process Replace a process level token If the user account does not have these rights assigned, the installer assigns them and automatically logs the account off to activate them. To avoid the installer logging the account off, you can set these rights manually before you start the installation. Procedure You perform the following steps to assign these rights to the user account used for the installation. Caution Be aware that domain policies override locally defined policies. This means that if you want to grant domain administrator rights to a user who belongs to the local Administrators group, make sure that you have also defined domain administrator rights for this user on domain level. 1. Choose Start Control Panel Administrative Tools Local Security Policy. Installation P U BL IC 17

18 2. In the Local Security Settings window, choose Local Policies User Rights Assignment. 3. Double-click the required right under Policy and choose Add User or Group. 4. In the Select Users and Groups window, choose the required user and choose Add. The selected user appears in the box below. 5. Confirm your entry and then repeat the steps for each remaining policy that the user requires for the installation. 6. Log off and log on again to apply the changes. Prerequisites You are logged on as a user with administration rights. If you want to use the SL Common GUI, make sure that the following web browser requirements are met: You have one of the following supported browsers on the device where you want to run the SL Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11. Always use the latest version of these web browsers. Recommendation We recommend using Google Chrome. If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI. Procedure 1. Make the installation media available on the installation host. For more information, see Preparation [page 12] 2. Start the installer by double-clicking sapinst.exe from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.sar file. By default, the SL Common GUI uses the default browser defined for the host where you run the installer. However, you can also specify another supported web browser available on the host where you start the installer. You can do this by starting the sapinst executable with command line option SAPINST_BROWSER=<Path to Browser Executable>, for example SAPINST_BROWSER=firefox.exe. 3. The installer is starting up Depending on the type of the installer GUI you want to use, do one of the following: If you use the SL Common GUI, the installer now starts and waits for the connection with the SL Common GUI. If you have a supported web browser (see Prerequisites) installed on the host where you run the installer, the SL Common GUI starts automatically by displaying the Welcome screen. If the SL Common GUI does not open automatically, you can find the URL you require to access the SL Common GUI at the bottom of the Program Starter window of the installer. You find the icon of the Program Starter window in the taskbar of your Windows host. Open a supported web browser and run the URL from there. 18 P U B L I C Installation

19 Sample Code... INFO :19: (MyUser) [D:/.../ins/SAPINST/ impl/src/guiengine/cslpcommunicationserver.cpp:157] CSLPCommunicationServer::doWork() Access URL for GUI is Logon users: [MyUser] INFO :19: (MyUser) [D:/.../ins/SAPINST/ impl/src/syslib/system/synxcsymgt.cpp:245] CSySystemMgtImpl::openUrlWithBrowser() Opening url ' The SL Common GUI opens in the browser by displaying the Welcome screen. Caution After opening the browser URL, make sure that the URL in the browser starts with to avoid security risks such as SSL stripping. Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst process on this computer could not be verified. Proceed as follows to avoid security risks such as a man-in-the-middle attack: 1. Click on the certificate area on the left hand side in the address bar of your browser, and view the certificate. 2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones displayed in the console output of the installer. Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate printed in the installer console: 1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the installer has extracted itself: %userprofile%\.sapinst\ 2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the command line option get_my_name -p. As a result, you get the server fingerprint or thumbprint from the server certificate. 3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not be verified. If you use the Java SDT GUI - that is you started the sapinst executable with command line option SAPINST_SLP_MODE=false, the Java SDT GUI starts automatically by displaying the Welcome screen. 4. In the Welcome screen, choose the required option. For more information about the different installation options, see Planning [page 7] If the installer prompts you to log off from your system, log off and log on again. The installer restarts automatically. Choose Continue Old Installation. Installation P U BL IC 19

20 5. Follow the instructions on the screens and enter the required parameters. To find more information on each parameter during the Define Parameters phase, position the cursor on the required parameter input field, and choose either F1 or the HELP tab. Then the available help text is displayed in the HELP tab. After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation. 6. To start the installation, choose Start. The installer starts the installation and displays the progress of the installation. When the installation has finished successfully, the installer shows the dialog Execution of <Option_Name> has been completed successfully. 4.3 SAP NetWeaver Developer Studio If you want to install SAP NetWeaver Developer Studio, proceed as described in the document Installation and Update Guide SAP NetWeaver Developer <Studio Release>, which you can find at support.sap.com/sltoolset System Provisioning Installation Option of Software Provisioning Manager Installation Guides - Standalone Engines and Clients 4.4 Installing SAP Memory Analyzer (Optional) Use You can install SAP Memory Analyzer as an additional tool. Together with the Developer Studio, you can optionally install the Memory Analyzer which helps you to analyze Java heap dumps, easily find large amount of memory or complex memory aggregation patterns in your data structures, and identify who is keeping this memory alive. The tool (Eclipse RCP application) has been developed to analyze real productive heap dumps, which tend to become enormous in size with hundreds of millions of objects. Performance, low resource consumption and especially the newly developed innovative analysis techniques make it a helpful tool, even to small application heap dumps. Procedure Installing SAP Memory Analyzer on SAP NetWeaver Composition Environment Make the installation media available on the installation host. For more information, see Preparation [page 12] 20 P U B L I C Installation

21 2. Start the installer by double-clicking sapinst.exe from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.sar file. The installer GUI starts automatically by displaying the Welcome screen. 3. In the Welcome screen, choose the following: SAP NetWeaver Composition Environment (CE) 7.1 Developer Edition <Your Database> Install Memory Analyzer 4. Choose Next. 5. Enter the location of the SAP Memory Analyzer, which is located in the Java IDE directory of the Java DVD. OR 1. Insert the Java DVD into your DVD drive or mount it locally. 2. Start the SAP Memory Analyzer by double-clicking the SAPMemoryAnalyzer.exe, which is located at: <DVD drive>:\data_units\<product>_java_ide Installing SAP Memory Analyzer on SAP NetWeaver Composition Environment 7.1 including enhancement package 1 and SAP NetWeaver Composition Environment Insert the Java DVD into your DVD drive or mount it locally. 2. Extract the files from MemoryAnalyzer.zip to your local system. MemoryAnalyzer.zip can be found at the following location: <DVD drive>:\data_units\<product>_java_ide 3. Start SAP Memory Analyzer from your newly created directory by double-clicking MemoryAnalyzer.exe. Installing SAP Memory Analyzer on SAP NetWeaver 7.3 and Higher For more information about installing and using the Memory Analyzer, see the SAP Library documentation for your release: SAP NetWeaver 7.3: Development Information Developer s Guides <Language> SAP NetWeaver Composition Environment Developing Composite Applications SAP NetWeaver Developer Studio Basics Administering the AS Java from the Developer Studio Working with the Memory Analyzer SAP NetWeaver 7.3 including enhancement package 1: Development Information Developer s Guides <Language> SAP NetWeaver Composition Environment Developing Composite Applications SAP NetWeaver Developer Studio Basics Administering the AS Java from the Developer Studio Working with the Memory Analyzer Installation P U BL IC 21

22 5 Post-Installation 5.1 Post-Installation This section describes the steps that you have to perform after the installation has finished successfully. 5.2 Applying the Latest Kernel and Support Package Stacks We strongly recommend that you apply the latest kernel and Support Package stacks before you start configuring your SAP system. Context If you have installed an SAP Solution Manager 7.2 system, you must apply at least Support Package Stack (SPS) 01. You cannot use SAP Solution Manager 7.2 with SPS 00. Procedure Download and apply the latest Kernel and Support Package stacks using the Software Update Manager (SUM) as described in the documentation Updating SAP Systems Using Software Update Manager <Release> available at System Maintenance Software Update Manager (SUM) scenarios Software Update/Upgrade with SUM <Release> If you want to update the kernel manually, proceed as described below: a. Log on as user <sapsid>adm to the hosts of the SAP system instances to be updated. b. Download the latest kernel for your operating system and database platform as described in SAP Note c. Back up the kernel directory that is specified by the profile parameter DIR_CT_RUN. d. Extract the SAR files of the kernel Support Packages of the target SP level to a temporary directory using the SAPCAR tool. e. Copy or move the extracted programs from the temporary directory to the local kernel directory. 22 P U B L I C Post-Installation

23 5.3 Performing Automated Configuration This section provides references to documentation about how to run automated configuration tasks for the initial configuration of SAP NetWeaver functional units. Caution Do not use the functional unit configuration tool to configure functional units that have already been enabled after: Upgrade Update System copy If you need to change the configuration of functional units that have already been enabled, then you must execute the configuration steps manually. If you want to use a functional unit that has not previously been enabled, you can either use the functional unit configuration tool or execute the steps manually. To initially configure an SAP NetWeaver functional unit, proceed as described in the SAP Library for the SAP NetWeaver release your application is based on: SAP Release and SAP Library Quick Link SAP Library Path (Continued) SAP NetWeaver SAP NetWeaver 7.3 including Enhancement Package 1 SAP NetWeaver SAP NetWeaver Application Help SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management SAP NetWeaver Configuration Configuration Wizard Post-Installation P U BL IC 23

24 6 Additional Information 6.1 Additional Information The following section provides additional information about the installation of your SAP NetWeaver Developer Workplace system. 6.2 Installation of Additional Usage Types to an Existing SAP System Use Valid only for the installation of additional usage types to SAP NetWeaver Composition Environment 7.1 and SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 32 bit Developer Workplace Systems. If you want to add Java software units or usage types to an existing SAP NetWeaver Developer Workplace system, proceed as described below for your release: Prerequisites The existing SAP system must have at least usage type SAP NetWeaver Application Server for Java (BASIC) and usage type SAP NetWeaver Product Description (CE-MODEL) You have planned your SAP system landscape according to the Master Guide available for your product. Prerequisites for SAP MaxDB During the installation of additional components, entries are written into the log area of the database. To avoid the log becoming full during the installation, make sure that your backup strategy is already active and an initial data backup was successful. When you want to establish your backup strategy after installing additional components, you can turn on the special log mode AutoOverwrite using the Database Manager GUI. This interrupts the existing backup history. You have to run a complete backup to start the history again. 24 P U B L I C Additional Information

25 Procedure 1. Make the installation media available on the installation host. For more information, see Preparation [page 12] 2. Start the installer by double-clicking sapinst.exe from the directory to which you unpacked the SWPM10SP<support package number>_<version number>.sar file. The installer GUI starts automatically by displaying the Welcome screen. 3. In the Welcome screen, choose one of the following releases: SAP NetWeaver Composition Environment 7.1 SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 Choose the following: <Database> Install Add Server Capability 4. Follow the screens and enter the required parameters. For more information about the input parameters and about restrictions for passwords, position the cursor on the required parameter and press F Performing a Developer Workplace Update with SUM Using the SL Common GUI Use To update a Developer Workplace system using the Software Update Manager (SUM) 1.0 SP13 and higher while using the browser-based SL Common GUI, you have to perform changes to several SUM startup parameters. Prerequisites You have completed all required planning and preparation steps required for your update and for starting the SL Common GUI, as described in chapters Planning and Preparation of the SUM user guide. You have not yet started the SL Common GUI. Procedure Proceed as follows: 1. Edit the startup.props file, which is located in the <Drive:>\usr\SAP\SUM\sdt\param folder. 2. Change the value of the DWLPSystem parameter to =true. Additional Information P U BL IC 25

26 3. Remove the hashtag symbol in front of the SID parameter. 4. Add the SID of the system where you are going to run the update process. 5. Save and close the file. 6. Open a command prompt, and run the startup command relevant for your operating system: For Windows-based systems: 'STARTUP confighostagent devwp_update SID=<SID> user=<username>' For UNIX-based systems: './STARTUP confighostagent devwp_update SID=<SID> user=<username>' Your user must have root privileges. In addition, be aware that the <SID> parameter in the command allows you to run multiple SUM instances on a host with multiple SIDs. Result The SL Common GUI back-end process is started and ready for use with your system. You can proceed with your SUM update as described in 6.4 Troubleshooting Repairing an Inconsistent SAP MaxDB Installation Prerequisites During the preinstallation phase, the installation tool checks the Microsoft Windows registry for already installed SAP MaxDB software. If the registry key is found but there is no software on the hard drive, you receive the following message: The existing MaxDB software is not consistent. Check the file system and registry. The most common reason for this inconsistency is the manual deletion of the software from the file system without using the specified tools. Procedure To repair this inconsistency, proceed as follows: 1. Choose Start Control Panel Administrative Tools Services. 2. Make sure the services SAPDBWWW, SAPDB: *, and XServer are stopped. 3. Choose Start Run and run the command regedit. 26 P U B L I C Additional Information

27 4. Open My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAP DBTech Key IndepPrograms. The key contains a path to a folder. 1. Check if this folder exists on the file system. 2. Note down the value of Key IndepPrograms for later usage in step 7. If the path does not exist in the file system, delete the key SAP DBTech. 5. Delete the following keys: My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAP DBTech-* My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPDBWWW My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\XServer 6. Choose Start Control Panel System Advanced Environment Variables System Variables Path. 7. Delete the following paths from the variable: <IndepPrograms>/bin <IndepPrograms>/pgm 8. Restart your computer. 6.5 Restarting the SAP MaxDB Server Manually Use If the database server does not start automatically after a system restart, you have to manually restart the SAP MaxDB server manually. Procedure Production Systems To manually restart the SAP MaxDB server, proceed as follows: 1. Do one of the following: Open a command prompt and enter the following command: net start sapdbwww Choose Start All Programs Administrative Tools Services. Double-click SAP DB WWW and choose Start. 2. Open the SAP Management Console and choose SAP Systems <SAPSID> <machine name>. 3. Enter the master password and choose Logon. 4. Choose Online. When the database server is online, you can restart the engine. Development Systems To manually restart the SAP MaxDB server, choose Start All Programs SAP NetWeaver Application Server <SAPSID> Start Application Server. Additional Information P U BL IC 27

28 6.6 Restarting the MS SQL Server Manually Use If the database server does not start automatically after a system restart, you have to restart the MS SQL Server manually. Procedure To restart the MS SQL Server manually, proceed as follows: 1. Choose Start All Programs Administrative Tools Services. 2. Find the service named SQL Server <name>, where <name> is MSSQLSERVER for the default instance or <instance name> for a named instance. 3. In the context menu of the SQL Server <name>, choose Start if the service is not started. 4. To make sure that the service is started automatically after each system restart, right-click it, choose Properties, and select the Automatic startup type. 6.7 Uninstalling the SAP NetWeaver System Use You have to uninstall all components of the SAP NetWeaver system separately. Procedure Uninstalling SAP NetWeaver Choose Start Control Panel Add / Remove programs SAP System<SAPSID>. OR Choose Start Programs SAP NetWeaver Composition Environment SAP System<SAPSID> Uninstall. Uninstalling SAP NetWeaver Using the Installer 1. Start the installer as described in section Installing SAP NetWeaver Developer Workplace [page 16]. 2. Choose Uninstall from the tree structure In the Welcome screen. 3. Follow the on-screen instructions. 28 P U B L I C Additional Information

29 Uninstalling SAP NetWeaver Developer Studio Prerequisites Before uninstalling SAP NetWeaver Developer Studio, consider the following: All additionally installed features and plug-ins that were installed to the same folder as Developer Studio, for example, by using the Eclipse Update Manager, are also removed. There may be other directories and files in the installation directory, especially <install_dir>/ eclipse/workspace/, <install_dir>/eclipse/links/, and <install_dir>/eclipse/ configuration/ that contain important data. The files and folder as well as the existing workspaces are retained when the product is uninstalled. Procedure To remove SAP NetWeaver Developer Studio, you have to delete the folder that contains the Developer Studio files. Uninstalling the SAP Management Console Since all SAP systems use the SAP Management Console, there is no uninstallation option for the SAP Management Console with the installer. If you are sure that you do not need the SAP Management Console any more, you can remove it using Start Control Panel Add / Remove programs. Additional Information P U BL IC 29

30 Important Disclaimers and Legal Information Hyperlinks Some links are classified by an icon and/or a mouseover text. These links provide additional information. About the icons: Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this: The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information. SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct. Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information. Beta and Other Experimental Features Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the experimental features in a live operating environment or with data that has not been sufficiently backed up. The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP. Example Code Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example code unless damages have been caused by SAP's gross negligence or willful misconduct. Gender-Related Language We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders. 30 P U B L I C Important Disclaimers and Legal Information

31 Important Disclaimers and Legal Information P U BL IC 31

32 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see for additional trademark information and notices. Material Number: ** THE BEST RUN