Sapjvm switch win

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

Target Audience ■ Technology consultants ■ System administrators

CUSTOMERDocument version: 1.90 – 2013-08-06

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.90 2013-08-06 Updated Version

1.80 2012-11-02 Chapter Importing Profiles [page 27] is added to the guide.








1.0 2011-05-25 Initial Version

2/32 CUSTOMER 2013-08-06

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

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

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

3.3 Required User Authorization for Running SAPinst . . . . . . . . . . . . . . . . . . . . . 10

3.4 Additional Preparation Steps for Heterogeneous Systems . . . . . . . . . . . . . . . . 11

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

4.1 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

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

4.2.1 How to Avoid Automatic Logoff by SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.2.2 Interrupted Installation with SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

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

4.2.4 Starting SAPinst GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.2.5 Running SAPinst in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4.2.6 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

6.2 Importing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2013-08-06 CUSTOMER 3/32

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

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

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

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

4/32 CUSTOMER 2013-08-06

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

2013-08-06 CUSTOMER 5/32

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 11].

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 13].

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

Follow-Up Activities

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

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

2 How to Perform the Switch to SAP JVM Step by Step

2013-08-06 CUSTOMER 7/32


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

2013-08-06 CUSTOMER 9/32


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 Required User Authorization for Running SAPinst

Although SAPinst automatically grants the required rights to the user account used for the installation,

you have to check whether this account has the required authorization to perform the installation.

The authorization required depends on whether you intend to perform a domain or local installation.

If necessary, you have to ask the system administrator to grant the account the necessary authorization

before you start the installation. If you attempt the installation with an account that has not the

required authorization, the installation aborts.

This section informs you about the authorization required for a domain and a local installation.

Procedure

Domain Installation

For a domain installation the account used for the installation needs to be a member of the local

Administrators and the domain Admins group of the domain involved. All machines in the system

must belong to the same domain. In a domain installation, the user information is stored centrally on

the domain controller and is accessible to all hosts in the system.

If the SAP system is to be distributed across more than one machine, SAP strongly recommends you

to perform a domain installation to avoid authorization problems.

For a domain installation, you need to:

1. Check that the account used for the installation is a member of the domain Admins group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the domain Admins group.

Local Installation

For a local installation the account used for the installation needs to be a member of the local

Administrators group of the machine involved. In a local installation, all Windows account

information is stored locally on one host and is not visible to any other hosts in the system.

CAUTION

Do not use the Windows built-in account Administrator or the renamed built-in account to

install your SAP system with SAPinst. The built-in account only has restricted network access

3 Preparation

3.3 Required User Authorization for Running SAPinst

10/32 CUSTOMER 2013-08-06


rights that are required by SAPinst. If you renamed the built-in account Administrator, do not

create a new account named Administrator.

For a local installation, you need to:

1. Check that the account used for the installation is a member of the local Administrators group.

2. If required, obtain these rights by asking the system administrator to enter the account as a member

of the local Administrators group.

3.4 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.4 Additional Preparation Steps for Heterogeneous Systems

2013-08-06 CUSTOMER 11/32


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

Useful Information About SAPinst

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

■ SAPinst creates the installation directory sapinst_instdir, which is located directly in the %

ProgramFiles% directory. If SAPinst is not able to create sapinst_instdir there, it tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.

RECOMMENDATION

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

correctly installed.

■ SAPinst creates a subdirectory for each installation option called sapinst_instdir

\<installation_option_directory>, which is located in %ProgramFiles%.

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

in %TEMP%, %TMP%, %TMPDIR%, or %SystemRoot%. 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 port 21212 is used for communication between the installer

GUI server and the installer GUI client. If this port is already in use, you see an error message.

In this case or if you want the installer to use a specific port, open a command prompt and change

to the required directory to which you unpacked the 70SWPM10SP<support package

number>_<version number>.SAR file


4.1 Running SAPinst

2013-08-06 CUSTOMER 13/32

Execute sapinst.exe with the following command line parameter:

GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>

■ To see a list of all available SAPinst properties, open a command prompt and start SAPinst with

command line parameter -p:

sapinst.exe -p

■ If you need to run SAPinst in accessibility mode, make sure that you have activated and adjusted

accessibility settings 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 choosing File Exit in the menu of

the Program Starter window.

Prerequisites

■ Make sure that you use an account with the required user authorization to run SAPinst [page 10].

Procedure

1. Log on as a user that is a member of the local administrators group.

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

3. Start SAPinst by double-clicking sapinst.exe from the following path:

<Drive>:\<directory into which you extracted SAPJVMSWITCH<version>.SAR>

NOTE

If you need to perform the installation in accessibility mode, open a command prompt, change

to the <Drive>:\<directory into which you extracted SAPJVMSWITCH<version>.SAR>

directory, and execute sapinst.exe –accessible.

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

4. If SAPinst prompts you to log off from your system, log off and log on again.

SAPinst restarts automatically.

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

6. 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/32 CUSTOMER 2013-08-06

7. We recommend that you delete the directory %userprofile%\.sdtgui\.

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

has successfully completed.

More Information

■ How to Avoid Automatic Logoff by SAPinst [page 15]

■ Interrupted Installation with SAPinst [page 16]

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

■ How to Avoid Automatic Logoff by SAPinst [page 15]

■ Interrupted Installation with SAPinst [page 16]

■ 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 How to Avoid Automatic Logoff by SAPinst

When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user

account used for the installation has the required privileges and authorization.

For a domain installation, the account needs to be both a member of the local Administrators group

and the domain Admins group. For a local installation, the account needs to be a member of the local

group Administrators group.

In both cases, the user account must be authorized to do the following:

■ Act as part of the operating system

■ Adjust memory quotas for a process

■ Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automatically logs

the account off to activate them. To avoid SAPinst logging the account off, you can set these rights

manually before you start the installation.

Procedure

You perform the following steps to assign these rights to the user account used for the installation.



2013-08-06 CUSTOMER 15/32

CAUTION

Be aware that domain policies override locally defined policies. This means that if you want to

grant domain administrator rights to a user who belongs to the local Administrators group,

make sure that you have also defined domain administrator rights for this user on domain level.

1. Choose Start Settings Control Panel Administrative Tools Local Security Policy .

2. In the Local Security Settings window, choose Local Policies User Rights Assignment. .

3. Double-click the required right under Policy and choose Add User or Group.

4. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.

5. Confirm your entry and then repeat the steps for each remaining policy that the user requires for

the installation.

6. Log off and log on again to apply the changes.

More Information

Required User Authorization for Running SAPinst [page 10]

4.2.2 Interrupted Installation with SAPinst

The SAP system installation might be interrupted for one of the following reasons:

■ An error occurred during the dialog or processing phase:

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 about 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 Exit in the SAPinst menu.

The following table describes the options in the dialog box:

Option Definition

Retry The installer retries the installation from the point of failure without repeating any of the previous steps.This is possible because the installer 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, the installer displays the same dialog box again.

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.The installer 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 The installer continues the installation from the current point.

View Log Access installation log files.



16/32 CUSTOMER 2013-08-06

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 remote host as a user who is a member of the local administrators group.

2. Insert the Installation Master DVD in your DVD drive.

3. Enter the following commands at the Windows command prompt:

cd <DVD drive>:\IM_WINDOWS<platform>

sapinst.exe

4. From the tree structure in the Welcome screen, select the installation service that you want to

continue and choose Next.

NOTE

If there is only one component to install, the Welcome screen does not appear.

The What do you want to do? screen appears.

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

OK.

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



2013-08-06 CUSTOMER 17/32

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

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host

have exactly the same version. You can check this by using the option –sfxver 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. You have to confirm

that the user is a trusted one. For more information, see SAP Note 1745524.

Procedure

1. Log on to your remote host as a user that is a member of the local administrators group.

2. Make the Installation Master medium available on your remote host.

3. Open a command prompt and change to the required directory by entering the following

command:

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

sapinst –sfxver

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. Execute sapinst.exe -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 SAPinst GUI Separately [page 18].

4.2.4 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:

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



18/32 CUSTOMER 2013-08-06


Prerequisites

■ Make sure that the sapinst.exe on the remote host and the sapinstgui.exe 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>

– 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







2013-08-06 CUSTOMER 19/32

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


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



20/32 CUSTOMER 2013-08-06

4.2.5 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. You can use it either for a local

installation or for a remote installation.

■ Custom font setting:

This feature is derived from the Windows display properties. You can use it either for a local

installation or for a remote installation.

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 can either perform a local installation, where SAPinst and SAPinst GUI are running on the same

host, or a remote installation, where SAPinst and SAPinst GUI are running on different hosts.

■ Local installation:

sapinst.exe –accessible

■ Remote installation:

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.exe –nogui

2. Start SAPinst GUI on the local host by executing the following command from the command

line as described in Starting the SAPinst GUI Separately for a Remote Installation [page 18]:



2013-08-06 CUSTOMER 21/32

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


4.2.6 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 16].

■ 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 %userprofile%

\.sdtgui\ for errors.

■ If the SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile

% directory.

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/32 CUSTOMER 2013-08-06



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

To perform the switch to SAP JVM 4 for the diagnostics agent running on the application server

instances of your SAP Java system, proceed as follows:

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 7.0 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 7.0 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 older diagnostics agents that are still running on a vendor JVM 1.4.2 are available on the application

server instance host of your SAP system, you have to replace the vendor JVM 1.4.2 of those diagnostics

agents 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:


5.1 Installing SAP JVM 4

2013-08-06 CUSTOMER 23/32



SAPCAR -xf <path to copied archive file>\SAPJVM4.SAR -R <drive>:\usr\sap

\<SAPSID>\exe

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

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:

cd <drive:>\<path to partner JDK>\bin\jar xf <drive:><path to partner JDK>\jre\lib

\security\local_policy.jar default_local.policy type 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:

Copy local_policy.jar and US_export_policy.jar from <drive:><path to Sun/Oracle JDK

1.4.2>\jre\lib\security to <drive>:\usr\sap\<SID>\SYS\exe\uc\<Windows platform>

\sapjvm_4\jre\lib\security. Overwrite already existing equally named files.


5.2 Replacing the Vendor Java Cryptography Extension Policy Files

24/32 CUSTOMER 2013-08-06

5.3 Adapting SAP System Instance Profiles

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

do this, you first have to apply the changes to the profiles described below.

Procedure

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

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 <drive>:\usr\sap\<SID>\SYS\profile

\<SAPSID>_<Instance>_<Hostname>.

2. Set the following parameter: jstartup/vm/home=<drive>:\usr\sap\<SAPSID>\<Instance>

\exe\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:

<drive>:\usr\sap\<SAPSID>\SYS\exe\run\sapcontrol -nr <Instance number> -

function RestartService


5.3 Adapting SAP System Instance Profiles

2013-08-06 CUSTOMER 25/32


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 11], 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 Importing Profiles

Procedure

After the JVM switch of a dual-stack system, you have to import the instance profiles using transaction

RZ10.

For more information, see the SAP Library for your release at:

Release Link Navigation Path

SAP Netweaver 7.0

http://

help.sap.com/nw70

Application Help Function-Oriented View Solution Life Cycle Management by Key Capability System Management Configuration What to do After Installing an SAP Instance Importing Profiles

SAP Netweaver 7.0 including enhancement package 1

http://

help.sap.com/nw701

Application Help Function-Oriented View Solution Life Cycle Management by Key Capability System Management Configuration Profiles What to do After Installing an SAP Instance Importing Profiles


http://

help.sap.com/nw702

Application Help Function-Oriented View Solution Life Cycle Management by Key Capability System Management Configuration Profiles What to do After Installing an SAP Instance Importing Profiles


6.1 Additional Follow-Up Steps for Heterogeneous Systems

2013-08-06 CUSTOMER 27/32

http://help.sap.com/nw70






Release Link Navigation Path


http://

help.sap.com/nw703

Application Help Function-Oriented View Solution Life Cycle Management by Key Capability Configuring SAP NetWeaver Configuring the CCMS

Profiles Saving and Importing Profiles After Installation


6.2 Importing Profiles

28/32 CUSTOMER 2013-08-06



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 16].

■ 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 %userprofile%

\.sdtgui\ for errors.

■ If the SAPinst GUI does not start, check the file sdtstart.err in the current %userprofile

% directory.

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.

Procedure

1. Go to directory %ProgramFiles%\sapinst_instdir\NW70\SWITCH_JDK.

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

7 Additional Information

7.1 Troubleshooting

2013-08-06 CUSTOMER 29/32



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

30/32 CUSTOMER 2013-08-06

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

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. National product specifications may vary.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.SAP 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.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

DisclaimerPlease see http://www.sap.com/corporate-en/legal/copyright/index.epx for disclaimer information and notices.

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

2013-08-06 CUSTOMER 31/32

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx


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

© Copyright 2013 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 win