Sapjvm Switch Unix

Installation GuideSAP JVM Switch ToolSAP Systems Based on SAP NetWeaver 04 (SAP Web AS 6.40) and SAP NetWeaver 7.0 on UNIX

Target Audience ■ Technology consultants ■ System administrators

PUBLICDocument version: 1.40 – 2012-04-11

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.60 2012-04-11 Updated Version






1.0 2011-05-25 Initial Version

2/34 PUBLIC 2012-04-11

http://service.sap.com/instguides

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2 How to Perform the Switch to SAP JVM Step by Step . . . . . . . . . . . . . . . . . 7

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Checking SAP JVM Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Downloading the Required Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.3 Additional Preparation Steps for Heterogeneous Systems . . . . . . . . . . . . . . . . 10

Chapter 4 Running the SAP JVM Switch Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.2 Additional Information About SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.1 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.2 Performing a Remote Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2.3 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2.4 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.2.5 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 5 Performing the Switch to SAP JVM 4 for the Diagnostics

Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1 Installing SAP JVM 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2 Replacing the Vendor Java Cryptography Extension Policy Files . . . . . . . . . . . 24

5.3 Adapting SAP System Instance Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.1 Additional Follow-Up Steps for Heterogeneous Systems . . . . . . . . . . . . . . . . . 27

6.2 Making Changes to JAVA_HOME Effective . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2012-04-11 PUBLIC 3/34

7.1.1 Troubleshooting with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

7.2 Undoing the Changes Applied by the SAP JVM Switch Tool . . . . . . . . . . . . . . 29

4/34 PUBLIC 2012-04-11

1 Introduction

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.40) Java and SAP NetWeaver 7.0 Java or dual stack (ABAP+Java). SAP JVM 4 is a Java

Development Kit (JDK) provided and supported by SAP. It is fully compliant to the Java Standard Edition

1.4.2. With the SAP JVM switch tool, SAP enables you to replace the vendor JVM 1.4.2 of existing SAP

systems based on SAP NetWeaver 0.4 or 7.0 with SAP JVM 4. This document is about how to run SAP

JVM switch tool to accomplish this replacement.

1.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

1665953 SAP JVM Switch Tool Composite Note

Contains supplementary information to the SAP JVM switch tool guide and to the SAP JVM switch tool as such.

1 Introduction

1.1 About This Document

2012-04-11 PUBLIC 5/34

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

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

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, that is on the

central instance host and on all dialog instance hosts:

Preparation

1. You check the installation prerequisites for the SAP JVM [page 9].

2. You download the required software [page 9]

3. If you have a heterogeneous system on UNIX and Windows, you perform additional preparation steps

for heterogeneous systems [page 10].

You only have to perform this step if you want to run the SAP JVM switch tool for the central

instance or a dialog instance of a heterogeneous system landscape on UNIX and Windows for which

the following is true: the central instance or the dialog instance runs on Windows hosts, whereas

the SCS instance runs separately on a UNIX host.

Performing the Switch to the SAP JVM

1. You run the SAP JVM switch tool [page 11].

2. You perform the switch to SAP JVM 4 for the diagnostics agent [page 23].

NOTE

These steps are only required if one of the following applies:

■ Your SAP Java system is based on SAP NetWeaver 7.0 SR3 (SAP ERP 6.0 SR3, SAP CRM

5.0 SR3, SAP SRM 5.0 SR3, SAP SCM 5.0 SR3), or SAP NetWeaver 7.0 including EHP1 (SAP

ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0).

■ Your SAP Java system is based on SAP NetWeaver including EHP2 (SAP ERP 6.0 EHP5,

SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1) and the diagnostics agent is running with vendor

JVM 1.4.2 (not with SAP JVM 6). For more information about the choice between vendor

JDK 1.4.2 and SAP JVM 6 for the diagnostics agent, see the Java installation guides for SAP

NetWeaver including EHP2 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1)

at http://service.sap.com/instguides.

Follow-Up Activities

1. If you did not perform the preparation steps described in Additional Preparation Steps for Heterogeneous

Systems [page 10], you have to perform additional follow-up steps for heterogeneous systems [page 27].


2012-04-11 PUBLIC 7/34


2. You make changes to JAVA_HOME effective [page 27].


8/34 PUBLIC 2012-04-11

3 Preparation

3.1 Checking SAP JVM Installation Prerequisites

The SAP JVM requires specific operating system versions, additional libraries and library patches.

Procedure

Check the requirements for your operating system as listed in SAP Note 1367498.

3.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 Switch Tool

The SAP JVM switch tool is delivered as a SAPJVMSWITCH<version>.SAR file. You have to download

and extract it using SAPCAR to be able to use it.

NOTE

If you want to perform a remote installation, and your remote and your local host are running

on different operating systems, you also have to download the required software for your

local host separately. For example:

● If your local host is Windows 32 bit, you have to download the file

SAPJVMSWITCH<version>.SAR of the platform Windows Server on IA32 32 bit on the local

host.

● If your local host is Linux 32 bit, you have to download the file

SAPJVMSWITCH<version>.SAR of the platform Linux on IA32 32 bit on the local host.

For more information, see Performing a Remote Installation with SAPinst [page 17].

■ SAPJVM 4

SAP JVM 4 is delivered as a SAPJVM<version>.SAR file. You have to download it but you must

not extract it.

Prerequisites

Make sure that at least SAPCAR 7.00 is available. We recommend that you use the latest SAPCAR

version. If required, download SAPCAR from http://service.sap.com/swdc.

Procedure

1. Log on as user <sapsid>adm.

3 Preparation

3.1 Checking SAP JVM Installation Prerequisites

2012-04-11 PUBLIC 9/34


http://service.sap.com/swdc

2. Download the SAPJVMSWITCH<version>.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.

You can find the current download path in SAP Note 1555341.

3. Extract SAPJVMSWITCH<version>.SAR into a directory on the local file system.

CAUTION

You must not unpack SAPJVM<version>.SAR.

3.3 Additional Preparation Steps for Heterogeneous Systems

You only have to perform this step if you want to run the SAP JVM switch tool for the central instance

or a dialog instance of a heterogeneous system landscape on UNIX and Windows for which the following

is true: the central instance or the dialog instance runs on Windows hosts, whereas the SCS instance

runs separately on a UNIX host.

NOTE

If the central instance or a dialog instance runs on the same host as the SCS instance, you only

have to run the SAP JVM switch tool on this host.

Procedure

1. Log on to the SCS instance host as user <sapsid>adm.

2. Execute the following commands:

1. mkdir /<sapmnt>/<SAPSID>/exe/jvm

2. cd /usr/sap/<SAPSID>/SYS/exe

3. ln -s /<sapmnt>/<SAPSID>/exe/jvm jvm

3 Preparation

3.3 Additional Preparation Steps for Heterogeneous Systems

10/34 PUBLIC 2012-04-11


4 Running the SAP JVM Switch Tool

4.1 Running SAPinst

SAP JVM switch tool uses the functions of the installation tool SAPinst.

This section describes how to run the installation tool SAPinst. SAPinst includes a GUI client and a GUI

server, which both use Java.

The procedure describes an installation where SAPinst, GUI client, and GUI server are running on the

same host. In the following, GUI client and GUI server are addressed as “SAPinst GUI”.

If you need to see the installation on a remote display, we recommend that you perform a remote installation

with SAPinst [page 17], where the SAPinst GUI is running on a separate host from SAPinst.

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote

access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.

Useful Information About SAPinst

■ When you start SAPinst, it automatically starts the SAPinst GUI.

■ SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.

SAPinst finds the temporary directory by checking the value of the following environment variables

in the following sequence: TEMP, TMP, and TMPDIR. If no value is set for these variables, SAPinst

creates the installation directory sapinst_instdir directly below the /tmp directory by default.

If you want SAPinst to create the installation directory sapinst_instdir in another directory, set

the environment variable TEMP to this directory before you start SAPinst.

Shell Used Command

Bourne shell (sh) TEMP=<directory>

export TEMP

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

CAUTION

Make sure that the installation directory is not mounted with NFS, or there might be problems

when the Java Virtual Machine is started.

RECOMMENDATION

We recommend that you keep all installation directories until the system is completely and

correctly installed.

■ SAPinst creates a subdirectory for each installation option called sapinst_instdir/

<installation_option_directory>.


4.1 Running SAPinst

2012-04-11 PUBLIC 11/34


■ SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located

in the environment variables TEMP, TMP, or TMPDIR. These files are deleted after SAPinst has stopped

running.

The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely

delete it.

The temporary directory also contains the log file dev_selfex.out from the extraction process,

which might be useful if an error occurs.

CAUTION

If SAPinst cannot find a temporary directory, the installation terminates with the error

FCO-00058.

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between SAPinst, GUI server, GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with the GUI client.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for

free port numbers. If the search fails, SAPinst exits.

In this case or if you want SAPinst to use specific ports, 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, start SAPinst as described above with command line

parameter -p:

./sapinst -p.

■ If you need to run SAPinst in accessibility mode, proceed as described in Running SAPinst in Accessibility

Mode [page 21].

■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.

NOTE

If you need to terminate SAPinst, you can do this by pressing Ctrl + C .

Prerequisites

■ We recommend that you use the csh shell for the installation with SAPinst. If you want to use

another shell, make sure that you have read SAP Note 202227.

SAPinst uses csh scripts during the installation to obtain the environment for user <sapsid>adm.

This is also true if user <sapsid>adm already exists from an earlier SAP system installation, and the

shell of this user is not csh. Before you start SAPinst, execute the following command as user

<sapsid>adm to make sure that the csh scripts are up-to-date:


4.1 Running SAPinst

12/34 PUBLIC 2012-04-11


/bin/csh -c "source /<home>/<sapsid>adm/.cshrc;env"

■ Check the value of the environment variable TEMP, TMP, or TMPDIR:

Shell Used Command

Bourne shell (sh) TEMP=<directory>

export TEMP

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

● 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, TMP, or TMPDIR

points – for example, by using a crontab entry.

● Make sure that you have at least 60 MB of free space in the installation directory for each

installation option. In addition, you need 200 MB free space for the SAPinst executables. If you

cannot provide 200 MB free space in the temporary directory, you can set one of the

environment variables TEMP, TMP, or TMPDIR to another directory with 200 MB free space for

the SAPinst executables.

● Make sure that the temporary directory has the permissions 777.

■ Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where

<host_name> is the host on which you want to display the GUI.

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0

■ Make sure that umask is set to 022 for user root.

As user root, enter the following command: umask 022

■ Check the following values for user root:

● In csh, execute limit

Output Properties

cputime unlimited

filesize unlimited

datasize unlimited

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

● In sh or ksh, execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited


4.1 Running SAPinst

2012-04-11 PUBLIC 13/34

Output Properties

data(kbytes) unlimited

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

If your parameter settings differ from the settings above, change these values accordingly.

EXAMPLE

If you have to change the value for descriptors to 8192, proceed as follows:

◆ In csh, execute:

limit descriptors 8192

◆ In sh or ksh execute:

ulimit -n 8192

Procedure

1. Log on to the installation host as user root.

CAUTION

If you want to perform the switch as user <sapsid>adm and the switch was started before by

another user, for example by the <sapsid>adm of another system, you must delete the old

NW70 directory and all its subdirectories in /<path to temporary directory>/

sapinst_instdir or move it to another location.

2. Make the required software available as described in Downloading the Required Software [page 9].

3. Start SAPinst by executing command ./sapinst from the following path:

/<directory into which you extracted SAPJVMSWITCH<version>.SAR>

CAUTION

Make sure that the installation directory is not mounted with NFS, or there might be problems

when the Java Virtual Machine is started.

4. Follow the instructions in the SAPinst input screens and enter the required parameters.

NOTE

For more information about the input parameters, position the cursor on the parameter and

press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.

This screen shows both the parameters that you entered and those that SAPinst set by default. If

required, you can revise the parameters before starting the installation.

5. To start the installation, choose Start.

SAPinst starts the installation and displays the progress of the installation.

When the installation option has finished successfully, SAPinst displays the message Execution of

<Option_Name> has completed.


4.1 Running SAPinst

14/34 PUBLIC 2012-04-11

6. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after SAPinst has finished.

Sometimes these remain in the temporary directory.

NOTE

If there are errors with the SAPinst extraction process, you can find the log file

dev_selfex.out in the temporary directory.

RECOMMENDATION

Keep all installation directories until you are sure that the system, including all instances, is

completely and correctly installed. Once the system is completely and correctly installed,

make a copy of the installation directories with all their contents. Save the copy to a physically

separate medium, such as a medium or an USB drive that is separate from your installation

hosts.

This might be useful for analyzing issues occurring later when you use the system. For security

reasons, do not keep installation directories on installation hosts, but make sure that you

delete them after saving them separately.

7. We recommend that you delete the directory <user_home>/.sdtgui/.

8. If you copied installation media to your hard disk, you can delete these files when the installation

has successfully completed.

More Information

■ Interrupted Installation with SAPinst [page 15]

■ Performing a Remote Installation with SAPinst [page 17]

■ Starting SAPinst GUI Separately [page 18]

■ Running SAPinst in Accessibility Mode [page 21]

■ Troubleshooting with SAPinst [page 22]

4.2 Additional Information About SAPinst

The following sections provide additional information about SAPinst:

■ Interrupted Installation with SAPinst [page 15]

■ Performing a Remote Installation with SAPinst [page 17]

■ Starting SAPinst GUI Separately [page 18]

■ Running SAPinst with Accessibility Mode [page 21]

■ Troubleshooting with SAPinst [page 22]

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



2012-04-11 PUBLIC 15/34

SAPinst does not abort the installation in error situations. If an error occurs, the installation pauses

and a dialog box appears. 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.

■ You interrupted the installation by choosing Cancel in the SAPinst menu.

CAUTION

If you stop an option in the Execute phase, any system or component installed by this option

is incomplete and not ready to be used. Any system or component uninstalled by this option

is not completely uninstalled.

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.This is possible because SAPinst records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, SAPinst displays the same dialog box again.

Stop SAPinst stops the installation, closing the dialog box, the SAPinst GUI, and the GUI server.SAPinst records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps (see the procedure below).

Continue SAPinst continues the installation from the current point.

View Log Access installation log files.

NOTE

You can also terminate SAPinst by choosing Ctrl + C . However, we do not recommend that

you use Ctrl + C , because this kills the process immediately.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to

continue an interrupted installation after an error situation.

1. Log on to your local UNIX host as user root.

CAUTION

Make sure that the root user has not set any environment variables for a different SAP system

or database.

2. Make the medium for the installation master available on the installation host.

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.



16/34 PUBLIC 2012-04-11

3.

4. Start SAPinst using the following command:

./sapinst

NOTE

5. From the tree structure in the Welcome screen, select the installation option that you want

to continue and choose Next.

The What do you want to do? screen appears.

6. In the What do you want to do? screen, decide between the following alternatives and continue with

Next:

Alternative Behavior

Run a new option SAPinst does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a backup directory. Afterwards, you can no longer continue the old installation option.For the backup directory, the following naming convention is used:<log_day_month_year_hours_minutes_seconds>

EXAMPLE

log_01_Oct_2008_13_47_56

CAUTION

SAPinst moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

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

4.2.2 Performing a Remote Installation with SAPinst

You use this procedure to install your SAP system on a remote host. In this case, SAPinst runs on the

remote host, and the SAPinst GUI runs on the local host. The local host is the host from which you

control the installation with the SAPinst GUI. The SAPinst GUI connects using a secure SSL connection

to SAPinst.

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote

access to SAPinst GUI on Windows workstations. For more information, see SAP Note 1170809.

Prerequisites

■ Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command ping <local host>.

2. Log on to the local host and enter the command ping <remote host>.



2012-04-11 PUBLIC 17/34


■ Make sure that the sapinst executable on the remote host and the sapinstgui executable on the

local host have exactly the same version. You can check this by using the option –version as

described in the procedure below and in the procedure in Starting SAPinst GUI Separately [page 18].

■ If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER

command line parameter, make sure that this user exists on the remote host.

Procedure

1. Log on to your remote host as user root.

CAUTION

Make sure that the root user has not set any environment variables for a different SAP system

or database.

2. Make the medium for the installation master available on the remote host.

RECOMMENDATION

Make installation media locally available. For example, reading from media mounted with

Network File System (NFS) might fail.

Only valid for: Solaris |

NOTE

If you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |

3. Change to the directory of the sapinst executable by entering the following command:

4. Check the version of the sapinst executable by entering the following command:

./sapinst –version

The version of the sapinst executable must be exactly the same as the version of the

sapinstgui executable on the local host (see also Starting SAPinst GUI Separately [page 18]).

5. Start SAPinst by executing the following command:

./sapinst -nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the

command prompt:

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

6. Start the SAPinst GUI on your local host as described in Starting the SAPinst GUI Separately [page

18].

4.2.3 Starting SAPinst GUI Separately

You use this procedure to start the SAPinst GUI separately. You need to start the SAPinst GUI separately

in the following cases:



18/34 PUBLIC 2012-04-11

■ You closed the SAPinst GUI using File Exit from the SAPinst menu while SAPinst is still

running.

■ You want to perform a remote installation, where the SAPinst GUI runs on a different host from

SAPinst. For more information, see Performing a Remote Installation with SAPinst [page 17].

■ You want to run SAPinst in accessibility mode. In this case, you have to start the SAPinst GUI

separately on a Windows host as described below with the additional command line parameter –

accessible. For more information, see Running SAPinst in Accessibility Mode [page 21].

Prerequisites

■ Make sure that the sapinst executable on the remote host and the sapinstgui executable on the

local host have exactly the same version. You can check this by using the option –version as

described in the procedure below and in the procedure in Performing a Remote Installation with SAPinst

[page 17].

Procedure

Starting SAPinst GUI on Windows

1. Make the Installation Master medium available on the host on which you want to start the SAPinst

GUI.

2. Change to the directory of the sapinstgui executable using the following command:

3. Start the SAPinst GUI from a command prompt by executing sapinstgui.exe with the relevant

command line parameters:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:

sapinstgui.exe –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst

[page 17]).

2. Start the SAPinst GUI by entering the following command:

sapinstgui.exe -host <remote_host> -port

<port_number_gui_server_to_gui_client>

– where <remote_host> is the name of the remote host, and

<port_number_gui_server_to_gui_client> is the port the GUI server uses to

communicate with the GUI client (21212 by default).

■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, 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.exe -port <port_number_gui_server_to_gui_client>



2012-04-11 PUBLIC 19/34

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to


● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui.exe -host <remote_host> -port





The SAPinst GUI starts and connects to SAPinst.

Starting SAPinst GUI on UNIX

1. Make the Installation Master medium available on the installation host.

RECOMMENDATION

Make installation media locally available. For example, if you use Network File System (NFS),

reading from media mounted with NFS might fail.

2. Change to the directory of the sapinstgui executable using the following command:

3. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Start the SAPinst GUI by executing ./sapinstgui with the relevant command line parameters:

■ If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:

./sapinstgui –version

The version of the sapinstgui executable must be exactly the same as the version of the

sapinst executable on the remote host (see also Performing a Remote Installation with SAPinst

[page 17]).

2. Start the SAPinst GUI by entering the following command:

./sapinstgui -host <remote_host> -port





■ If you closed the SAPinst GUI using File Exit and want to reconnect to SAPinst, 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 -port <port_number_gui_server_to_gui_client>

– where <port_number_gui_server_to_gui_client> is the port the GUI server uses to




20/34 PUBLIC 2012-04-11

● If you are performing a remote installation with SAPinst and SAPinst GUI running on

different hosts, execute the following command:

sapinstgui -host <remote_host> -port





The SAPinst GUI starts and connects to SAPinst.End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

4.2.4 Running SAPinst in Accessibility Mode

You can also run SAPinst in accessibility mode. The following features are available:

■ Keyboard access:

This feature is generally available for all operating systems.

■ High-contrast color:

This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.

■ Custom font setting:

This feature is derived from the Windows display properties. Therefore, to enable this feature, you

must perform a remote installation with the SAPinst GUI running on a Windows host.

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.

NOTE

The following procedure applies for Windows Server 2008 and might be different when using

another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.

2. Select Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.

3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme drop-down box.

To define your own color schemes, choose Advanced.

Running SAPinst in Accessibility Mode

You perform a remote installation as follows:



2012-04-11 PUBLIC 21/34

1. 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 17]:

./sapinst –nogui

2. 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 18]:

sapinstgui.exe -accessible –host <remote_host> -port


4.2.5 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

■ Stops the installation

■ Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known SAPinst issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the Define Parameters or Execute phase, do either of the following:

■ Try to solve the problem

■ Stop the installation by choosing Cancel in the SAPinst menu.

For more information, see Interrupted Installation with SAPinst [page 15].

■ After resolving the problem, you can continue the installation by choosing Retry.

4. Check the log and trace files of the GUI server and SAPinst GUI in the directory

<user_home>/.sdtgui/ for errors.

■ If the SAPinst GUI does not start, check the file sdtstart.err in the current <user_home>

directory.

■ 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, contact your X Server vendor. 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. See also SAP Note 1170809.

5. If you cannot resolve the problem, create a customer message using component BC-INS.

For more information about using subcomponents of BC-INS, see SAP Note 1669327.



22/34 PUBLIC 2012-04-11




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. You install SAP JVM 4 [page 23].

2. You replace the Vendor Java Cryptography Extension policy files [page 24].

3. You adapt SAP system instance profiles [page 25].

NOTE

These steps are only required if one of the following applies:

■ Your SAP Java system is based on SAP NetWeaver 7.0 SR3 (SAP ERP 6.0 SR3, SAP CRM 5.0

SR3, SAP SRM 5.0 SR3, SAP SCM 5.0 SR3) or SAP NetWeaver 7.0 including EHP1 (SAP ERP 6.0

EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0).

■ Your SAP Java system is based on SAP NetWeaver including EHP2 (SAP ERP 6.0 EHP5, SAP

CRM 7.0 EHP1, SAP SRM 7.0 EHP1) and the diagnostics agent is running with vendor JVM

1.4.2 (not with SAP JVM 6). For more information about the choice between vendor JDK 1.4.2

and SAP JVM 6 for the diagnostics agent, see the Java installation guides for SAP NetWeaver

including EHP2 (SAP ERP 6.0 EHP5, SAP CRM 7.0 EHP1, SAP SRM 7.0 EHP1) at http://

service.sap.com/instguides.

5.1 Installing SAP JVM 4

If diagnostics agents are available in the application server instances of your SAP system, you have to

replace the vendor JVM 1.4.2 of the diagnostics agent with SAP JVM 4.

Prerequisites

You have downloaded the SAP JVM 4 Archive as described in Downloading the Required Software.

Procedure

1. Log on as user <sapsid>adm.

2. Open a command shell and extract the archive as follows:

■ For SAP systems based on SAP NetWeaver 7.0 SR3 or 7.0 EHP1, enter the following commands:

SAPCAR -xf <path to copied archive file>/SAPJVM4.SAR -R /usr/sap/<SAPSID>/exe

■ For SAP systems based on SAP NetWeaver 7.0 EHP2, enter the following commands:


5.1 Installing SAP JVM 4

2012-04-11 PUBLIC 23/34



SAPCAR -xf <path to copied archive file>/SAPJVM4.SAR -R /usr/sap/<SAPSID>/SYS/

exe/uc/platform

5.2 Replacing the Vendor Java Cryptography Extension Policy Files

The SAP JVM has strong, but limited encryption capabilities by default. These capabilities are controlled

by two Java Cryptography Extension (JCE) policy files, namely local_policy.jar and

US_export_policy.jar, which are located in the jre/lib/security folder of a vendor JDK. If you are

using unlimited encryption with your vendor JDK, you must replace the vendor JCE policy files with

the JCE policy files required for the SAP JVM.

Procedure

Checking the Vendor JDK for Unlimited Encryption

Proceed as follows to check whether unlimited encryption is provided by your vendor JDK:

1. 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 default_local.policy

cat default_local.policy

2. Check the output of the commands.

If the output is similar to the following, unlimited encryption is provided by your vendor JDK:

EXAMPLE

grant {

// There is no restriction to any algorithms.

permission javax.crypto.CryptoAllPermission;

};

Applying Unlimited Encryption to the SAP JVM

For Sun/Oracle and HP 1.4. 2 partner JDKs, the unlimited encryption policy files of your partner JDK

can be reused for SAP JVM. Former IBM JDK users can download unlimited encryption policy files

from Oracle's website.

Proceed as follows to replace the vendor JCE policy files with the JCE policy files required for the SAP

JVM:

■ Solaris, HP-UX, Linux/x86 (32 bit):

Copy local_policy.jar and US_export_policy.jar from <path to Sun or HP JDK 1.4.2>/

jre/lib/security to /usr/sap/<SID>/SYS/exe/run/sapjvm_4/jre/lib/security. Overwrite

already existing equally named files.

■ AIX, Linux on POWER processors, Linux on x86_64, Linux on Z architecture:


5.2 Replacing the Vendor Java Cryptography Extension Policy Files

24/34 PUBLIC 2012-04-11

1. Download jce_policy_1_4_2.zip from Oracle's website at https://cds.sun.com/is-bin/

INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-

Start?ProductRef=7503-jce-1.4.2-oth-JPR@CDS-CDS_Developer.

2. Unpack jce_policy_1_4_2.zip.

3. Copy local_policy.jar and US_export_policy.jar to /usr/sap/<SID>/SYS/exe/run/

sapjvm_4/jre/lib/security

5.3 Adapting SAP System Instance Profiles

You have to restart the sapstart service in order to activate the changed <sapsid> profile. Before you

can do this, you first have to apply further changes to the profiles.

Procedure

1. This step is only required for SAP systems based on SAP NetWeaver 7.0 EHP 2:

Set up the SAPCPE program to copy the executables from the central directory to the local instance

directories as follows:

1. Edit the <sapsid> profile. This file is named <DASID>_<Instance>_<Hostname>

2. Change line _CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst so that it looks as follows:

_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst list:$(DIR_CT_RUN)/sapjvm_4.lst

NOTE

The two list expressions must be separated by a space, not by a new-line character.

2. 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. We recommend that you make a backup of

the profiles before modifying them.

To do so, proceed as follows:

1. Edit the instance profiles found at /usr/sap/<SID>/SYS/profile/

<SID>_<Instance>_<Hostname>.

2. Set the following parameter: jstartup/vm/home=/usr/sap/<SID>/SYS/exe/run/sapjvm_4

3. Add the following parameter: SAPJVM_VERSION = <version of the SAPJVM4>

4. Save the modified instance profiles.

3. Restart the sapstart service of each SAP system instance to make sure that the instance loads the

changed profiles.

You can either use the SAP MMC, or the SAP MC, or the sapcontrol command line tool.

■ 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.

■ Using sapcontrol:

Enter the following command:



2012-04-11 PUBLIC 25/34

https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=7503-jce-1.4.2-oth-JPR@CDS-CDS_Developer



/usr/sap/<SAPSID>/SYS/exe/run/sapcontrol -nr <Instance number> -function

RestartService



26/34 PUBLIC 2012-04-11

6 Follow-Up Activities

6.1 Additional Follow-Up Steps for Heterogeneous Systems

If you did not perform the preparation steps described in Additional Preparation Steps for Heterogeneous

Systems [page 10], you have to perform the following steps on the SCS instance host after the SAP JVM

switch tool has finished.

NOTE

You have to perform this step only once on the SCS instance host.

Procedure

1. Log on to the SCS instance host as user <sapsid>adm.

2. Execute the following commands:

1. mkdir /<sapmnt>/<SAPSID>/exe/jvm (if /<sapmnt>/<SAPSID>/exe/jvm does not yet exist)

2. mv /usr/sap/<SID>/SYS/exe/jvm/<Windows OS> /<sapmnt>/<SID>/exe/jvm/

3. rmdir /usr/sap/<SAPSID>/SYS/exe/jvm

4. cd /usr/sap/<SAPSID>/SYS/exe

5. ln -s /<sapmnt>/<SAPSID>/exe/jvm jvm

6.2 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.

6 Follow-Up Activities

6.1 Additional Follow-Up Steps for Heterogeneous Systems

2012-04-11 PUBLIC 27/34

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

7 Additional Information

7.1 Troubleshooting

7.1.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

■ Stops the installation

■ Displays a dialog informing you about the error

Procedure

1. Check SAP Note 1548438 for known SAPinst issues.

2. To view the log file, choose View Logs.

3. If an error occurs during the Define Parameters or Execute phase, do either of the following:

■ Try to solve the problem

■ Stop the installation by choosing Cancel in the SAPinst menu.

For more information, see Interrupted Installation with SAPinst [page 15].

■ After resolving the problem, you can continue the installation by choosing Retry.

4. Check the log and trace files of the GUI server and SAPinst GUI in the directory

<user_home>/.sdtgui/ for errors.

■ If the SAPinst GUI does not start, check the file sdtstart.err in the current <user_home>

directory.

■ 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, contact your X Server vendor. 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. See also SAP Note 1170809.

5. If you cannot resolve the problem, create a customer message using component BC-INS.

For more information about using subcomponents of BC-INS, see SAP Note 1669327.

7.2 Undoing the Changes Applied by the SAP JVM Switch Tool

If required, you can undo the changes applied by the SAPJVM Switch Tool retroactively.


7.1 Troubleshooting

2012-04-11 PUBLIC 29/34




Procedure

1. Go to directory /<path to temporary directory>/sapinst_instdir/NW70/SWITCH_JDK.

2. Follow the instructions in the switchJDK.txt file.


7.2 Undoing the Changes Applied by the SAP JVM Switch Tool

30/34 PUBLIC 2012-04-11

Typographic Conventions

Example Description

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

ExampleExample

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

Example Emphasized words or expressions

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

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

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

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

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

■ Cross-references to other documentation or published works

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

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

2012-04-11 PUBLIC 31/34

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the United States and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.Oracle and Java are registered trademarks of Oracle and its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.IOS is a registered trademark of Cisco Systems Inc.RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.INTERMEC is a registered trademark of Intermec Technologies Corporation.Wi-Fi is a registered trademark of Wi-Fi Alliance.Bluetooth is a registered trademark of Bluetooth SIG Inc.Motorola is a registered trademark of Motorola Trademark Holdings LLC.Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, 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. Business Objects is an SAP company.Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

32/34 PUBLIC 2012-04-11

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. 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, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

2012-04-11 PUBLIC 33/34


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2012 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Documents

Sapjvm Switch Unix