Installation Guide SAP JVM Switch Tool

SAP Systems Based on SAP NetWeaver 04 (SAP Web AS 6.40) and SAP NetWeaver 7.0 on UNIX
Target Audience ■ Technology consultants ■ System administrators

PUBLIC Document version: 1.10 – 2011-07-07

Document History

CAUTION

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

1.10 1.0

2011-07-07 2011-05-25

Updated Version Initial Version

2/36

PUBLIC

2011-07-07

Table of Contents

Chapter 1 1.1 1.2 Chapter 2 Chapter 3 3.1 3.2 Chapter 4 4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 Chapter 5 5.1 5.2 5.3 Chapter 6 6.1 Chapter 7 7.1 7.1.1 7.2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 How to Perform the Switch to SAP JVM Step by Step . . . . . . . . . . . . . . . . . 7 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Replacing the IBM i Native JDBC Driver with the IBM i Toolbox Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Downloading the Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Running the SAP JVM Switch Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing the Switch to SAP JVM 4 for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing SAP JVM 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacing the Vendor Java Cryptography Extension Policy Files . . . . . . . . . . . Adapting SAP System Instance Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 14 14 16 17 19

21 21 22 23

Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Making Changes to JAVA_HOME Effective . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Undoing the Changes Applied by the SAP JVM Switch Tool . . . . . . . . . . . . . . 27 27 27 27

2011-07-07

PUBLIC

3/36

. 29 4/36 PUBLIC 2011-07-07 . . . . . .1 What Does SAP JVM Switch Tool Do in Detail? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . 28 Reference . . . . . . . . 29 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . .3 Chapter A A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

40) and SAP NetWeaver 7.4.1 1.SAR to download the required software SAP JVM 4.1 parameters when Describes two sets of SAP JVM switching from a partner JDK parameters: One set for the server nodes and one for dispatcher nodes of an SAP NetWeaver Application Server Java. It is fully compliant to the Java Standard Edition 1.1 About This Document SAP introduced SAP JVM (SAP Java Virtual Machine) 4 for SAP systems based on SAP NetWeaver 04 (SAP Web AS 6. SAP JVM 4 is a Java Development Kit (JDK) provided and supported by SAP.2 of existing SAP systems based on SAP NetWeaver 7. 1.2 supported platforms and about the end of SAP's support for vendor JDKs Downloading SAP JVM Switch Tool Contains information about where and SAPJVM4. This document is about how to run SAP JVM Switch Tool to accomplish this replacement.0.2. The server node parameter set distinguishes parameters for 64 bit. SAP enables you to replace the vendor JVM 1.1 Introduction About This Document 1 Introduction 1. With the SAP JVM Switch Tool.0 with SAP JVM 4. 32 bit and parameters independent thereof.4. 2011-07-07 PUBLIC 5/36 .2 SAP Notes Make sure that you have read the following SAP Notes before you run the SAP JVM Switch Tool: SAP Note Number Title Description 1495160 1555341 1522200 SAP JVM as replacement for Partner Contains information about JDKs 1.4.

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

see the Java installation guides for SAP NetWeaver including EHP2 (SAP ERP 6.0 EHP5. SAP SRM 7. SAP CRM 7. 2011-07-07 PUBLIC 7/36 .4.0 SR3 (SAP ERP 6. You run the SAP JVM Switch Tool [page 11].com/instguides.0 EHP1) at http://service.2 How to Perform the Switch to SAP JVM Step by Step 2 How to Perform the Switch to SAP JVM Step by Step Procedure You have to perform the following steps on every application server instance host.0 including EHP1 (SAP ERP 6.0 SR3.0. 2.0 EHP1.2 (not with SAP JVM 6). You perform the switch to SAP JVM 4 for the diagnostics agent [page 21]. SAP CRM 5.0 EHP5. Performing the Switch to the SAP JVM 1. For more information about the choice between vendor JDK 1. SAP SRM 7. SAP SCM 5.0 EHP4.0 EHP1. ■ Your SAP Java system is based on SAP NetWeaver including EHP2 (SAP ERP 6.0.0 SR3) or SAP NetWeaver 7.0 SR3. SAP CRM 7. that is on the central instance host and on all dialog instance hosts: Preparation You download the required software [page 9].0).0 EHP1) and the diagnostics agent is running with vendor JVM 1. SAP CRM 7.4. SAP SRM 7. SAP SCM 7.0 SR3. SAP SRM 5. NOTE These steps are only required if one of the following applies: ■ Your SAP Java system is based on SAP NetWeaver 7.2 and SAP JVM 6 for the diagnostics agent. Follow-Up Activities You perform follow-up activities.sap.

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

Procedure 1.com/swdc. Extract SAPJVMSWITCH<version>.1 Preparation Replacing the IBM i Native JDBC Driver with the IBM i Toolbox Driver 3 Preparation 3. 2.SAR and SAPJVM<version>.SAR files for your operating system to the local file system of the host of the SAP system instance on which you want to perform the switch to SAP JVM. 3.SAR file. 3.3 3.SAR into a directory on the local file system. ■ SAPJVM 4 SAP JVM 4 is delivered as a SAPJVM<version>. If required. 2011-07-07 PUBLIC 9/36 . Prerequisites Make sure that at least SAPCAR 7.SAR file.2 Downloading the Required Software You have to make the following software available on every application server instance host of the SAP system: ■ SAP JVM 4 Switch Tool The SAP JVM 4 Switch Tool is delivered as a SAPJVMSWITCH<version>. you must replace it with the IBM i Toolbox Driver. Log on as user <sapsid>adm.00 is available.1 Replacing the IBM i Native JDBC Driver with the IBM i Toolbox Driver If your system uses the IBM i Native JDBC Driver. CAUTION You must not unpack SAPJVM<version>.sap. You have to download it but you must not extract it. download SAPCAR from http://service. You can find the current download path in SAP Note 1555341.SAR. We recommend that you use the latest SAPCAR version. Procedure Proceed as described in SAP Note 826449. You have to download and extract it using SAPCAR to be able to use it. Download the SAPJVMSWITCH<version>.

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

and GUI server are running on the same host. SAPinst includes a GUI client and a GUI server. SAPinst creates the installation directory sapinst_instdir directly below the /tmp directory by default. see SAP Note 1170809. Useful Information About SAPinst ■ When you start SAPinst. This section describes how to run the installation tool SAPinst. SAPinst finds the temporary directory by checking the value of the following environment variables in the following sequence: TEMP. set the environment variable TEMP to this directory before you start SAPinst. 2011-07-07 PUBLIC 11/36 . In the following. Alternatively. TMP. or TMPDIR. where the SAPinst GUI is running on a separate host from SAPinst.xxxxxx. we recommend that you perform a remote installation with SAPinst [page 16]. If you want SAPinst to create the installation directory sapinst_instdir in another directory. If you need to see the installation on a remote display. and TMPDIR. Shell Used Command TEMP=<directory> export TEMP Bourne shell (sh) C shell (csh) Korn shell (ksh) setenv TEMP <directory> export TEMP=<directory> ■ SAPinst creates a subdirectory for each installation option called sapinst_instdir/ <installation_option_directory>. GUI client. You can safely delete it. GUI client and GUI server are addressed as “SAPinst GUI”. ■ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.1 Running the SAP JVM Switch Tool Running SAPinst 4 Running the SAP JVM Switch Tool 4. This section describes an installation where SAPinst. which is located in the environment variables TEMP. If no value is set for these variables. The temporary directory sapinst_exe. For more information. you can use an X server for Microsoft Windows or other remote desktop tools like vncviewer or nxserver/nxclient – offered by various vendors or open source – for remote access to the GUI on Windows workstations. TMP. These files are deleted after SAPinst has stopped running. We recommend you use the Hummingbird Exceed X Server.1 Running SAPinst SAPJVM Switch Tool uses the functions of the installation tool SAPinst.xxxx.xxxxxx. which both use Java. it automatically starts the SAPinst GUI.xxxx sometimes remains undeleted. ■ SAPinst extracts itself to a temporary directory called sapinst_exe. which we use to validate installations with SAPinst.4 4.

GUI. CAUTION If SAPinst cannot find a temporary directory. and the shell of this user is not csh.out from the extraction process.1 Running the SAP JVM Switch Tool Running SAPinst The temporary directory also contains the log file dev_selfex. SAPinst exits. make sure that you have read SAP Note 202227. and HTTP server. SAPinst uses csh scripts during the installation to obtain the environment for user <sapsid>adm. ● 4239 is the port of the HTTP server. start SAPinst as described above with command line parameter -p: ./sapinst -p. TMP. If the ports for SAPinst and the GUI server are already in use. you can do this by pressing Prerequisites Ctrl + C . the default ports 21200. which is part of the GUI server. 21212. ■ We recommend that you use the csh shell for the installation with SAPinst. or TMPDIR: Shell Used Command TEMP=<directory> export TEMP Bourne shell (sh) 12/36 PUBLIC 2011-07-07 . NOTE If you need to terminate SAPinst. ■ If you need to run SAPinst in accessibility mode. GUI server. If the search fails. If you want to use another shell. proceed as described in Running SAPinst in Accessibility Mode [page 19]. which might be useful if an error occurs. as follows: ● SAPinst uses port 21200 to communicate with the GUI server.4 4. the installation terminates with the error FCO-00058. you can assign them by executing the sapinst executable with the following command line parameters: ● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server> ● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client> ● GUISERVER_HTTP_PORT=<port_number_http_server> ■ To see a list of all available SAPinst properties.env" ■ Check the value of the environment variable TEMP. execute the following command as user <sapsid>adm to make sure that the csh scripts are up-to-date: /bin/csh -c "source /<home>/<sapsid>adm/. ● The GUI server uses port 21212 to communicate with the GUI client. ■ If required. SAPinst automatically searches for free port numbers. Before you start SAPinst. In this case or if you want SAPinst to use specific ports. and 4239 are used for communication between SAPinst. you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu. ■ During the installation. This is also true if user <sapsid>adm already exists from an earlier SAP system installation.cshrc.

0 export DISPLAY Bourne shell (sh) C shell (csh) Korn shell (ksh) Procedure setenv DISPLAY <host_name>:0. Shell Used Command DISPLAY=<host_name>:0./sapinst from the following path: /<directory into which you extracted SAPJVMSWITCH<version>. If you want to perform the switch as user <sapsid>adm and the switch was started before by another user. In addition. or TMPDIR to another directory with 200 MB free space for the SAPinst executables.0 1. Start SAPinst by executing .1 Running the SAP JVM Switch Tool Running SAPinst Shell Used Command setenv TEMP <directory> export TEMP=<directory> C shell (csh) Korn shell (ksh) ● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variable TEMP. Sometimes these remain in the temporary directory. you can set one of the environment variables TEMP. For more information about the input parameters. position the cursor on the parameter and press F1 . you must delete the old NW70 directory and all its subdirectories in /<path to temporary directory>/ sapinst_instdir or move it to another location. TMP.SAR> Follow the instructions in the SAPinst dialogs and enter the required parameters. TMP. by using a crontab entry. 6. To start the switch operation. Log on to the installation host as user <sapsid>adm or root. CAUTION 2. choose Start If required.0.4 4. 4. ■ Make sure that your DISPLAY environment variable is set to <host_name>:0.xxxxxx. you need 200 MB free space for the SAPinst executables. ● Make sure that the temporary directory has the permissions 777. If you cannot provide 200 MB free space in the temporary directory. 2011-07-07 PUBLIC 13/36 .0 export DISPLAY=<host_name>:0. Make the required software available as described in Downloading the Required Software [page 9]. delete directories with the name sapinst_exe. ● Make sure that you have at least 60 MB of free space in the installation directory for each installation option. where <host_name> is the host on which you want to display the GUI.xxxx after SAPinst has finished. 3. for example by the <sapsid>adm of another system. NOTE 5. or TMPDIR points – for example.

If there are errors with the SAPinst extraction process. This is possible because SAPinst records the installation progress in the keydb.sdtgui/. The following table describes the options in the dialog box: Option Definition Retry SAPinst retries the installation from the point of failure without repeating any of the previous steps. ■ You interrupted the installation by choosing Cancel in the SAPinst menu. you can find the log file dev_selfex.2 Running the SAP JVM Switch Tool Additional Information About SAPinst NOTE 7. More Information ■ ■ ■ ■ ■ Interrupted Installation with SAPinst [page 14] Performing a Remote Installation with SAPinst [page 16] Starting SAPinst GUI Separately [page 17] Running SAPinst in Accessibility Mode [page 19] Troubleshooting with SAPinst [page 27] 4. 14/36 PUBLIC 2011-07-07 . any system or component installed by this option is incomplete and not ready to be used. We recommend that you delete the directory <user_home>/. CAUTION If you stop an option in the Execute phase.out in the temporary directory.xml file.1 Interrupted Installation with SAPinst The SAP system installation might be interrupted for one of the following reasons: ■ An error occurred during the Define Parameters or Execute phase: SAPinst does not abort the installation in error situations.2. the installation pauses and a dialog box appears.2 Additional Information About SAPinst The following sections provide additional information about SAPinst: ■ Interrupted Installation with SAPinst [page 14] ■ Performing a Remote Installation with SAPinst [page 16] ■ Starting SAPinst GUI Separately [page 17] ■ Running SAPinst with Accessibility Mode [page 19] 4. Any system or component uninstalled by this option is not completely uninstalled. If an error occurs.4 4. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

In the What do you want to do? screen. 1. closing the dialog box. select the installation option that you want to continue and choose Next.2 Option Running the SAP JVM Switch Tool Additional Information About SAPinst Definition Stop Continue View Log NOTE We recommend that you view the entries in the log files. you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below).4 4.SAR> 4. If you want to perform the switch as user <sapsid>adm and the switch was started before by another user. which you stopped by choosing Stop.xml file. From the tree structure in the Welcome screen. or to continue an interrupted installation after an error situation. 3. If the same or a different error occurs. SAPinst stops the installation. 6. try to solve the problem. and then choose Retry. SAPinst records the installation progress in the keydb. For more information about how to start SAPinst. decide between the following alternatives and continue with Next: 2011-07-07 PUBLIC 15/36 . the SAPinst GUI. Access installation log files. Make the required software available as described in Downloading the Required Software [page 9]. SAPinst continues the installation from the current point. Start SAPinst by executing the following command: . Therefore. and the GUI server. CAUTION 2. The What do you want to do? screen appears. Procedure This procedure describes the steps to restart an installation. because this kills the process immediately. we do not recommend that you use Ctrl + C . SAPinst displays the same dialog box again. Change to the directory with the sapinst executable for your operating system by entering the following command: cd <directory into which you extracted SAPJVMSWITCH<version>. You can also terminate SAPinst by choosing Ctrl + C . see Running SAPinst [page 11] or Performing a Remote Installation with SAPinst [page 16] and Starting SAPinst GUI Separately [page 17]. you must delete the old NW70 directory and all its subdirectories in /<path to temporary directory>/ sapinst_instdir or move it to another location. Log on to the installation host as user <sapsid>adm or root. for example by the <sapsid>adm of another system. However./sapinst NOTE 5.

Afterwards. you can no longer continue the old installation option. it moves the content of the old installation directory and all installationspecific files to a backup directory. 4. and the SAPinst GUI runs on the local host. As an alternative to remote installation you can use an X server for Microsoft Windows or other remote desktop tools such as VNC Viewer or NX Server / NX Client – offered by various vendors or open source – for remote access to SAPinst GUI on Windows workstations. The SAPinst GUI connects using a secure SSL connection to SAPinst. the following naming convention is used: <log_day_month_year_hours_minutes_seconds> EXAMPLE log_01_Oct_2008_13_47_56 CAUTION Continue with the old option SAPinst moves all the files and folders to a new log directory. Instead. For more information. The local host is the host from which you control the installation with the SAPinst GUI. 16/36 PUBLIC 2011-07-07 .2 Performing a Remote Installation with SAPinst You use this procedure to install your SAP system on a remote host. which we use to validate installations with SAPinst. For more information. even if these files and folders are owned by other users. SAPinst continues the interrupted installation option from the point of failure. see SAP Note 1170809. If there are any processes currently running on these files and folders. End of: Linux. Only valid for: Linux.2. see Starting SAPinst GUI Separately [page 17].4 4. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. SAPinst runs on the remote host. If your security policy requires that the person performing the installation by running the SAPinst GUI on the local host is not allowed to know root credentials on the remote host.Windows | You can run the SAPinst GUI on a PC with 32-bit while SAPinst is running on a 64-bit installation host. they might no longer function properly. In this case.Windows | Prerequisites ■ The remote host meets the prerequisites for starting SAPinst as described in Running SAPinst [page 11].2 Running the SAP JVM Switch Tool Additional Information About SAPinst Behavior Alternative Run a new option SAPinst does not continue the interrupted installation option. We recommend that you use the Hummingbird Exceed X Server. For the backup directory. you can specify another operating system user for authentication purposes.

you must delete the old NW70 directory and all its subdirectories in /<path to temporary directory>/ sapinst_instdir or move it to another location.4 4. Log on to the installation host as user <sapsid>adm or root./sapinst -nogui NOTE If you need to specify another operating system user for authentication purposes. You need to start the SAPinst GUI separately in the following cases: ■ You closed the SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still running. Change to the directory of the sapinst executable by entering the following command: cd <directory into which you extracted SAPJVMSWITCH<version>. 4. To test this: ■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter. for example by the <sapsid>adm of another system.2. Make the required software available as described in Downloading the Required Software [page 9]. port <port_number> to continue with the installation 5. 2011-07-07 PUBLIC 17/36 . Procedure 1. For more information. ■ You want to perform a remote installation.2 Running the SAP JVM Switch Tool Additional Information About SAPinst ■ Both computers are in the same network and can ping each other. make sure that this user exists on the remote host.SAR> Start SAPinst by executing the following command: ./sapinst -nogui SAPINST_REMOTE_ACCESS_USER=<specified OS user> SAPinst now starts and waits for the connection to the SAPinst GUI. waiting for a connection on host <host_name>. CAUTION 2. enter the following command: . Start the SAPinst GUI on your local host as described in Starting the SAPinst GUI Separately [page 17]. If you want to perform the switch as user <sapsid>adm and the switch was started before by another user. 3. where the SAPinst GUI runs on a different host from SAPinst.3 Starting SAPinst GUI Separately You use this procedure to start the SAPinst GUI separately. see Performing a Remote Installation with SAPinst [page 16]. You see the following at the command prompt: guiengine: no GUI connected. 4.

3. 2.exe with the relevant command line parameters: ■ If you want to perform a remote installation. The SAPinst GUI starts and connects to SAPinst. proceed as follows: ● If you are performing a local installation with SAPinst and SAPinst GUI running on the same host. Starting SAPinst GUI on UNIX 1. Procedure Starting SAPinst GUI on Windows 1. execute the following command: sapinstgui. execute the following command: sapinstgui.2 Running the SAP JVM Switch Tool Additional Information About SAPinst ■ You want to run SAPinst in accessibility mode. ● If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts. For more information.4 4. see Running SAPinst in Accessibility Mode [page 19]. and <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default). Make the required software available as described in Downloading the Required Software [page 9]. execute the following command: sapinstgui.SAR> Start the SAPinst GUI from a command prompt by executing sapinstgui. and <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default).exe -port <port_number_gui_server_to_gui_client> – where <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default). Make the required software available as described in Downloading the Required Software [page 9].exe -host <remote_host> -port <port_number_gui_server_to_gui_client> – where <remote_host> is the name of the remote host. Prerequisites The host on which you want to start the SAPinst GUI meets the prerequisites for starting SAPinst as described in Running SAPinst [page 11]. Change to the directory of the sapinstgui executable: <Drive>:\<directory into which you extracted SAPJVMSWITCH<version>. ■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst. In this case.exe -host <remote_host> -port <port_number_gui_server_to_gui_client> – where <remote_host> is the name of the remote host. 18/36 PUBLIC 2011-07-07 . you have to start the SAPinst GUI separately on a Windows host as described below with the additional command line parameter – accessible.

execute the following command: . ■ Custom font setting: This feature is derived from the Windows display properties. to enable this feature. and <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default).IBM i5/OS.HP-UX. Therefore. you must perform a remote installation with the SAPinst GUI running on a Windows host.Solaris. ● If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts.Solaris. proceed as follows: ● If you are performing a local installation with SAPinst and SAPinst GUI running on the same host. execute the following command: sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client> – where <remote_host> is the name of the remote host. 2011-07-07 PUBLIC 19/36 . ■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst.4 Running SAPinst in Accessibility Mode You can also run SAPinst in accessibility mode. and <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default).IBM i5/OS. 3.HP-UX. Therefore.4 4. The SAPinst GUI starts and connects to SAPinst.Windows | 4./sapinstgui -host <remote_host> -port <port_number_gui_server_to_gui_client> – where <remote_host> is the name of the remote host.Linux./sapinstgui with the relevant command line parameters: ■ If you want to perform a remote installation.2.Windows | Start the SAPinst GUI by executing . ■ High-contrast color: This feature is derived from the Windows display properties. you must perform a remote installation with the SAPinst GUI running on a Windows host.Linux. execute the following command: sapinstgui -port <port_number_gui_server_to_gui_client> – where <port_number_gui_server_to_gui_client> is the port the GUI server uses to communicate with the GUI client (21212 by default). End of: AIX. The following features are available: ■ Keyboard access: This feature is generally available for all operating systems. to enable this feature.SAR> Only valid for: AIX. Change to the directory of the sapinstgui executable by entering the following command: cd <directory into which you extracted SAPJVMSWITCH<version>.2 Running the SAP JVM Switch Tool Additional Information About SAPinst 2.

choose Advanced. To define your own color schemes.exe -accessible –host <remote_host> -port <port_number_gui_server_to_gui_client> 20/36 PUBLIC 2011-07-07 . Start SAPinst on the remote host by executing the following command from the command line as described in Performing a Remote Installation with SAPinst [page 16]: .2 Running the SAP JVM Switch Tool Additional Information About SAPinst Procedure Activating and Adjusting Accessibility Settings on Windows You first have to activate and adjust the relevant settings for the font size and color schemes before you start SAPinst or the SAPinst GUI.4 4. 3. Select a color scheme from the Color scheme drop-down box. Select Adjust font size (DPI) and choose Larger scale (120 DPI). NOTE The following procedure applies for Windows Server 2008 and might be different when using another Windows operating system. To define other font size schemes. In the right-hand pane. 2./sapinst –nogui 2. select Window Color and Appearance. Right click on your Windows desktop and choose Personalize. choose Custom DPI. 1. Start SAPinst GUI on a local Windows host by executing the following command from the command line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 17]: sapinstgui. Running SAPinst in Accessibility Mode You perform a remote installation as follows: 1.

SAP SCM 7. enter the following commands: 2011-07-07 PUBLIC 21/36 . Prerequisites You have downloaded the SAP JVM 4 Archive as described in Downloading the Required Software. You replace the Vendor Java Cryptography Extension policy files [page 22]. SAP SRM 7. SAP SRM 7.0 SR3 (SAP ERP 6. You install SAP JVM 4 [page 21]. SAP SRM 5.0 including EHP1 (SAP ERP 6. ■ Your SAP Java system is based on SAP NetWeaver including EHP2 (SAP ERP 6.sap. You adapt SAP system instance profiles [page 23]. enter the following commands: SAPCAR -xf <path to copied archive file>/SAPJVM4.0 SR3.0 SR3. For more information about the choice between vendor JDK 1. 3. Open a command shell and extract the archive as follows: ■ For SAP systems based on SAP NetWeaver 7.0 EHP1) and the diagnostics agent is running with vendor JVM 1.0.0 EHP4.com/instguides.1 Performing the Switch to SAP JVM 4 for the Diagnostics Agent Installing SAP JVM 4 5 Performing the Switch to SAP JVM 4 for the Diagnostics Agent You have to perform the following steps to perform the switch to SAP JVM 4 for the diagnostics agent running on the application server instances of your SAP Java system: 1.0 EHP1.2 (not with SAP JVM 6).0 EHP1) at http:// service.0 SR3) or SAP NetWeaver 7. 2.4.2 and SAP JVM 6 for the diagnostics agent.0 EHP5.0).0 EHP1.SAR -R /usr/sap/<SAPSID>/exe ■ For SAP systems based on SAP NetWeaver 7. Log on as user <sapsid>adm.1 Installing SAP JVM 4 If diagnostics agents are available in the application server instances of your SAP system.0 SR3.2 of the diagnostics agent with SAP JVM 4. you have to replace the vendor JVM 1.4.0 SR3 or 7.0. see the Java installation guides for SAP NetWeaver including EHP2 (SAP ERP 6. NOTE These steps are only required if one of the following applies: ■ Your SAP Java system is based on SAP NetWeaver 7. SAP CRM 7. Procedure 1.0 EHP1. 2.4. SAP CRM 7.0 EHP5.0 EHP2.5 5. SAP CRM 7. SAP CRM 5. SAP SRM 7. SAP SCM 5. 5.

■ AIX. you must replace the vendor JCE policy files with the JCE policy files required for the SAP JVM.jar default_local.4. permission javax. unlimited encryption is provided by your vendor JDK: EXAMPLE grant { // There is no restriction to any algorithms.2 Performing the Switch to SAP JVM 4 for the Diagnostics Agent Replacing the Vendor Java Cryptography Extension Policy Files SAPCAR -xf <path to copied archive file>/SAPJVM4.policy 2.jar and US_export_policy.crypto. 2 partner JDKs.5 5. These capabilities are controlled by two Java Cryptography Extension (JCE) policy files. Check the output of the commands.2>/ jre/lib/security to /usr/sap/<SID>/SYS/exe/run/sapjvm_4/jre/lib/security. namely local_policy. If you are using unlimited encryption with your vendor JDK.jar and US_export_policy. Overwrite already existing equally named files. the unlimited encryption policy files of your partner JDK can be reused for SAP JVM. Linux on Z architecture: 22/36 PUBLIC 2011-07-07 . HP-UX. which are located in the jre/lib/security folder of a vendor JDK. Applying Unlimited Encryption to the SAP JVM For Sun/Oracle and HP 1. Former IBM JDK users can download unlimited encryption policy files from Oracle's website.jar.CryptoAllPermission. but limited encryption capabilities by default. Linux on POWER processors. Linux on x86_64. Open a command shell and enter the following command: <path to vendor JDK>/bin/jar xf <path to vendor JDK>/jre/lib/security/ local_policy.jar from <path to Sun or HP JDK 1. Procedure Checking the Vendor JDK for Unlimited Encryption Proceed as follows to check whether unlimited encryption is provided by your vendor JDK: 1.policy cat default_local.4. If the output is similar to the following. }. Linux/x86 (32 bit): Copy local_policy. Proceed as follows to replace the vendor JCE policy files with the JCE policy files required for the SAP JVM: ■ Solaris.2 Replacing the Vendor Java Cryptography Extension Policy Files The SAP JVM has strong.SAR -R /usr/sap/<SAPSID>/SYS/ exe/uc/platform 5.

lst so that it looks as follows: _CPARG0 = list:$(DIR_CT_RUN)/j2eeinst. Unpack jce_policy_1_4_2. Download jce_policy_1_4_2. This step is only required for SAP systems based on SAP NetWeaver 7.3 Performing the Switch to SAP JVM 4 for the Diagnostics Agent Adapting SAP System Instance Profiles 1. Restart the sapstart service of each SAP system instance to make sure that the instance loads the changed profiles. ■ Using the SAP MMC or the SAP MC: Select your instances in the left tree view and choose All tasks Restart Service in the context menu. 3. Set the following parameter: jstartup/vm/home=/usr/sap/<SID>/SYS/exe/run/sapjvm_4 3. We recommend that you make a backup of the profiles before modifying them. This file is named <DASID>_<Instance>_<Hostname> 2.0 EHP 2: Set up the SAPCPE program to copy the executables from the central directory to the local instance directories as follows: 1.jar to /usr/sap/<SID>/SYS/exe/run/ sapjvm_4/jre/lib/security 5.2-oth-JPR@CDS-CDS_Developer. 2. Edit the instance profiles found at /usr/sap/<SID>/SYS/profile/ <SID>_<Instance>_<Hostname>.sun. or the SAP MC. proceed as follows: 1. You have to set the profile parameter jstartup/vm/home to the path of the SAP JVM executable to be able to run the diagnostics agent with SAP JVM.4.lst NOTE 2. Edit the <sapsid> profile.zip.zip from Oracle's website at https://cds. 2. Change line _CPARG0 = list:$(DIR_CT_RUN)/j2eeinst. To do so. Add the following parameter: SAPJVM_VERSION = <version of the SAPJVM4> 4. Save the modified instance profiles. 3. ■ Using sapcontrol: Enter the following command: 2011-07-07 PUBLIC 23/36 .lst list:$(DIR_CT_RUN)/sapjvm_4. you first have to apply further changes to the profiles.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetailStart?ProductRef=7503-jce-1. Before you can do this. not by a new-line character.com/is-bin/ INTERSHOP. Procedure 1.jar and US_export_policy. or the sapcontrol command line tool. Copy local_policy.5 5. The two list expressions must be separated by a space. You can either use the SAP MMC.3 Adapting SAP System Instance Profiles You have to restart the sapstart service in order to activate the changed <sapsid> profile.

5 5.3 Performing the Switch to SAP JVM 4 for the Diagnostics Agent Adapting SAP System Instance Profiles /usr/sap/<SAPSID>/SYS/exe/run/sapcontrol -nr <Instance number> -function RestartService 24/36 PUBLIC 2011-07-07 .

6 6.1 Follow-Up Activities Making Changes to JAVA_HOME Effective 6 Follow-Up Activities 6.1 Making Changes to JAVA_HOME Effective Procedure You have to log off and log on again as user <sapsid>adm on the host where you performed the switch to SAP JVM so that the changes to JAVA_HOME become effective. 2011-07-07 PUBLIC 25/36 .

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

■ If the SAPinst GUI does not start. create a customer message using component BC-INS. check the file sdtstart. choose View Logs. 7. Procedure 1. see Interrupted Installation with SAPinst [page 14]. ■ Displays a dialog informing you about the error. SAPinst: ■ Stops the installation.1 Troubleshooting with SAPinst This section tells you how to proceed when errors occur during the installation with SAPinst. ■ After resolving the problem.2 Undoing the Changes Applied by the SAP JVM Switch Tool If required.sdtgui/ for errors. 5. To view the log file. do either of the following: ■ Try to solve the problem ■ Stop the installation by choosing Cancel in the SAPinst menu. If you cannot resolve the problem.err in the current <user_home> directory. Go to directory /<path to temporary directory>/sapinst_instdir/NW70/SWITCH_JDK. Check the log and trace files of the GUI server and SAPinst GUI in the directory <user_home>/. you can undo the changes applied by the SAPJVM Switch Tool retroactively. contact your X Server vendor. Check SAP Note 1548438 for known SAPinst issues. For more information.7 7. 2.1.1 Troubleshooting 7. ■ If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote Access of SAPinst GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes. 2011-07-07 PUBLIC 27/36 . If an error occurs. you can continue the installation by choosing Retry. See also SAP Note 1170809.1 Additional Information Troubleshooting 7 Additional Information 7. If an error occurs during the Define Parameters or Execute phase. 4. Procedure 1. The vendor can give you information about whether this X Server supports Java Swing-based GUIs and also tell you about further requirements and restrictions. 3.

5. Updating (if already set) or setting (if not yet set) the JAVA_HOME environment variable to the path of the SAP JVM location for user <sapsid>adm.3 What Does SAP JVM Switch Tool Do in Detail? The SAP JVM Switch Tool replaces the vendor JVM 1.2 of your SAP system with SAP JVM 4. Creating a link /usr/sap/<SAPSID>/SYS/exe/jvm that points to /<sapmnt>/<SAPSID>/exe/jvm. To acccomplish this. SAP JVM Switch Tool performs the following steps: Process 1. Installing JCE policy files. if the vendor JVM uses unlimited encryption. 7.4.txt file. Unpacking the SAPJVM4.SAR archive to /<sapmnt>/<SAPSID>/exe/jvm/<arch>/ sapjvm_<version>. 28/36 PUBLIC 2011-07-07 . Updating the configuration of the Software Deployment Manager (SDM) in the central instance and restarting the instance service and instance agent. 3. 6.3 Additional Information What Does SAP JVM Switch Tool Do in Detail? 2. Modifying SAP system instance and start profiles by invoking sapcpe to replicate SAP JVM 4 to the exe directory of every SAP system instance directory /usr/sap/<SAPSID>/<INSTANCE_NAME>/ exe. Follow the instructions in the switchJDK.7 7. where <arch> is the name of the unpacked archive folder. 4. 2.

■ Target group: ● System administrators ● Technology consultants ● Solution consultants ■ Current version: ● On SAP Service Marketplace at http://service. It contains SAP-specific vocabulary in over 30 languages.A A. 2011-07-07 PUBLIC 29/36 .1 The Main SAP Documentation Types The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software. A collective security guide is available for SAP NetWeaver.sap. ■ Target group: ● Relevant for all target groups ■ Current version: ● On SAP Help Portal at http://help. SAP applications have a security guide of their own. This document contains general guidelines and suggestions. It provides scenario-specific descriptions of preparation.sap. as well as many glossary entries in English and German. It lists the required installable units for each business or IT scenario.com (also available as documentation DVD) The security guide describes the settings for a medium security level and offers suggestions for raising security levels.com Glossary ● In the SAP system in transaction STERM SAP Library is a collection of documentation for SAP software covering functions and processes.1 Reference The Main SAP Documentation Types A Reference A.sap. ■ Target group: ● Consultants ● System administrators ● Project teams for implementations or upgrades ■ Current version: ● On SAP Help Portal at http://help. Cross-Phase Documentation SAPterm is SAP’s terminology database.com/securityguide Implementation The master guide is the starting point for implementing an SAP solution.

the technical infrastructure guide and SAP Notes. such as installation guides. and precedes the application operations guides of SAP Business Suite. The manual refers 30/36 PUBLIC 2011-07-07 .sap. ■ Target group: ● Technology consultants ● Project teams for implementations ■ Current version: ● On SAP Service Marketplace at http://service. It contains Customizing activities. The Customizing activities and their documentation are structured from a functional perspective.) ■ Target group: ● Solution consultants ● Project teams for implementations or upgrades ■ Current version: ● In the SAP menu of the SAP system under Tools Customizing IMG Production Operation The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver. transactions.sap.com/instguides Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle platform. business processes.1 Reference The Main SAP Documentation Types execution.com/instguides The installation guide describes the technical implementation of an installable unit. (In order to configure a whole system landscape from a process-oriented perspective. which refers to the relevant Customizing activities in the individual SAP systems. ■ Target group: ● Technology consultants ● Project teams for implementations ■ Current version: ● On SAP Service Marketplace at http://service. and so on. It also provides references to other documents. SAP Solution Manager. taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. is used.A A. and follow-up of an implementation. One of its main functions is the configuration of business scenarios. and implementable steps. as well as documentation. ■ Target group: ● Technology consultants ● Solution consultants ● Project teams for implementations ■ Current version: ● In SAP Solution Manager The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system.

It does not describe any business-related configuration. execution. such as monitoring.sap.com/instguides The upgrade guide describes the technical upgrade of an installable unit. transports.com/instguides Release notes are documents that contain short descriptions of new features in a particular release or changes to existing features since the previous release. ■ Target group: ● System administrators ● Technology consultants ● Solution consultants ■ Current version: ● On SAP Service Marketplace at http://service. It provides scenario-specific descriptions of preparation. such as upgrade guides and SAP Notes.com/instguides Upgrade The upgrade master guide is the starting point for upgrading the business scenarios and processes of an SAP solution. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG). ■ Target group: ● Technology consultants ● Project teams for upgrades ■ Current version: ● On SAP Service Marketplace at http://service.1 Reference The Main SAP Documentation Types users to the tools and documentation that are needed to carry out various tasks. master data maintenance.A A. ■ Target group: ● System administrators ■ Current version: ● On SAP Service Marketplace at http://service. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks. and tests.sap.sap. and follow-up of an upgrade. ■ Target group: 2011-07-07 PUBLIC 31/36 . taking into account the combinations of operating systems and databases. ■ Target group: ● Technology consultants ● Project teams for upgrades ■ Current version: ● On SAP Service Marketplace at http://service.sap. backup/restore.com/instguides The application operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It also refers to other documents.

1 Reference The Main SAP Documentation Types ● Consultants ● Project teams for upgrades ■ Current version: ● On SAP Service Marketplace at http://service.sap.A A.com/releasenotes ● In the SAP menu of the SAP system under Help Release Notes (only ABAP developments) 32/36 PUBLIC 2011-07-07 .

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

Inc. WebSphere. Parallel Sysplex. DB2. OS/2. Duet. DB2 Connect. XHTML and W3C are trademarks or registered trademarks of W3C®. Data contained in this document serves informational purposes only. Sybase 365. OS/400. National product specifications may vary. R/3. z/VM. Netfinity. and Motif are registered trademarks of the Open Group. RACF. Sybase and Adaptive Server. and SAP Group shall not be liable for errors or omissions with respect to the materials. System z9. and other countries. Redbooks. eServer. Program Neighborhood. OS/390. POWER5+. System z. Citrix. RETAIN. POWER. PowerVM. without representation or warranty of any kind. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way. S/390 Parallel Enterprise Server. and PowerPoint are registered trademarks of Microsoft Corporation. AIX. BatchPipes. iAnywhere. Intelligent Miner. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. Sybase is an SAP company. S/390. Adobe.sap. 34/36 PUBLIC 2011-07-07 . SQL Anywhere. Outlook. zSeries. z9. i5/OS. pSeries. SAP BusinessObjects Explorer. DB2 Universal Database. System i. Excel. as is any decompilation of these components. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited. SAP NetWeaver. Massachusetts Institute of Technology. MetaFrame. PowerPC. used under license for technology invented and implemented by Netscape. MVS/ESA. Acrobat. System x. PostScript. BusinessObjects. Inc. HACMP. Inc.S. Crystal Reports. GPFS. xSeries. BladeCenter. Nothing herein should be construed as constituting an additional warranty. OSF/1. Disclaimer Some components of this product are based on Java™. if any. Inc. the Adobe logo. All other product and service names mentioned are the trademarks of their respective companies. PartnerEdge. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. OpenPower.com © Copyright 2011 SAP AG. WinFrame. System i5. The information contained herein may be changed without prior notice. VideoFrame. POWER5. UNIX. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. JavaScript is a registered trademark of Sun Microsystems. ICA. System z10. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only. All rights reserved. World Wide Web Consortium. Windows. iSeries. in the United States and in other countries. XML. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. z10. X/Open. and MultiWin are trademarks or registered trademarks of Citrix Systems. z/OS. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. Microsoft. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Business Objects and the Business Objects logo. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. POWER6.. These materials are subject to change without notice. System Storage. System p5. AS/400. ByDesign. IBM. HTML. POWER6+. SAP. Web Intelligence. System p. Crystal Decisions. Linux is the registered trademark of Linus Torvalds in the U. Xcelsius. Java is a registered trademark of Sun Microsystems. Power Architecture.

Documentation in the SAP Service Marketplace You can find this document at the following address: http://service.sap.com/instguides 2011-07-07 PUBLIC 35/36 .

. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.com © Copyright 2011 SAP AG.sap. All rights reserved.SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www. The information contained herein may be changed without prior notice.