Далее хочу установить клиента. Запускаю:
SAP_NetWeaver_702e_Installation_Master\IM_WINDOWS_I386\sapinstgui.exe

какого "клиента"?

Summary

Symptom

SAP did not deliver any JCE policy archives within some SAP JVM versions used by the installation, the upgrade, or the EHP installer. Those are java version 1.5.0_09 (build 5.1.000) up to and including java version 1.6.0_07 (build 6.1.005).

SAPinst:
If you perform a "remote installation" SSL communication is used between GUI server and GUI, which requires policy files within the used JVM.
This means that the remote scenario is not activated by default.
"Remote installation" means that SAPinst and the GUI server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control the installation with SAPinst GUI.

SAP Upgrade Program and SAP Enhancement Package Installer:
The policy files are required in any case to start the upgrade program and the SAP Enhancement Package Installer.




Reason and Prerequisites

===================================================================

Differences between the old and new behaviour of SAPinst and SAPinst GUI

===================================================================
Before the policy files were removed, in a standard scenario where you double-click the sapinst executable on the Installation Master DVD, SAPinst started the SAPinst GUI in client-server mode. When the SAPinst GUI was closed, the GUI server was still active and it was possible to connect a separate SAPinst GUI to the GUI server to control the running installation.
If you now start SAPinst in the same way and close SAPinst GUI, no GUI server is available to handle another SAPinst GUI connection. The GUI fails with an error messages. See in the Troubleshooting section below for a solution.



Solution

===================================================================

The following information applies to SAPinst 701_1 and 712 (as of August 19, 2008)

===================================================================
To activate the remote scenario proceed as follows:

1. Download the JCE policy file from SAP (see note 1240081) or SUN on both the local and the remote host.
2. UNIX: Execute the following command: chmod +x <jce policy zip file>
3. Specify the location of the policy zip file by setting the user environment variable JCE_POLICY_ZIP=<jce policy zip file> on both the local and the remote host.
Note: On Windows when setting the environment variable JCE_POLICY_ZIP in a command line window, please make sure to start it as administrator, otherwise the setting will not be taken into account.
4. Start SAPinst on the remote host: sapinst -nogui
5. Start SAPinst GUI on the local host: sapinstgui -host <remote host name>

Then the zip files are unpacked and the jar archives are copied to the right location within the JVM that is used by SAPinst or the SAPinst GUI.


===============================================================

Troubleshooting for SAPinst


Symptom:
You have done the following:
You first started SAPinst. Then you closed SAPinst GUI. SAPinst is still running. Then you started a separate SAPinst GUI that displays the following error:
Error while connecting to communication partner - see preceeding messages.
Could not connect to host <hostname> on port <port number>.
java.net.ConnectException: Connection refused: connect

Cause:
After you closed SAPinst GUI, no GUI server is available to handle another SAPinst GUI connection.

Solution:
First start the GUI server and then the GUI as follows:

1. Download the JCE policy file from SAP (see note 1240081) or SUN on both the local and the remote host.
2. UNIX: Execute the following command: chmod +x <jce policy zip file>
3. Specify the location of the policy zip file by setting the user environment variable JCE_POLICY_ZIP=<jce policy zip file> on both the local and the remote host.
Note: On Windows when setting the environment variable JCE_POLICY_ZIP in a command line window, please make sure to start it as administrator, otherwise the setting will not be taken into account.
4. Start the GUI server on the remote host: sapinstgui -server -nogui
5. Start SAPinst GUI on the local host: sapinstgui -host <remote host name>


====================================================================

The following information applies to upgrade master and EHP installer

====================================================================

1. Download the JCE policy file from SAP (see note 1240081) or SUN.
2. UNIX: Execute the following command: chmod +x <jce policy zip file>
3. Start the tool: STARTUP "jce_policy_zip=<jce policy zip file>"



Header Data


Release Status:
Released on: 08.03.2012 13:48:16
Master Language: °ЭУЫШЩбЪШЩ
Priority:
Category:
Primary Component: BC-INS
Secondary Components: BC-UPG

Affected Releases

Software
Component Release From
Release To
Release And
subsequent
SAPJVM 5.1 5.1 5.1
SAPJVM 6.1 6.1 6.1


Related Notes



1261688 - Installation of SAP NW CE 7.1 on IBM i

1240081 - "Java Cryptography Extension Jurisdiction Policy" files

950619 - Installation of SAP Systems with Unattended Mode
Print Selected Notes (PDF)

Summary

Symptom

SAP does not deliver the so-called "Java Cryptography Extension (JCE) Jurisdiction Policy" files as part of the SAP JVM. Without these files the cryptography functionality inside the SAP JVM is blocked. Therefore typical usage scenarios requiring cryptography, e.g. communication via HTTPS or storage of information in Secure Storages will not work anymore.

Other terms

SAP JVM Patch Collection 17
SAP JVM Build 5.1.023
SAPinst
EHP Installer
Software Update Manager

Reason and Prerequisites

The JCE Jurisdiction Policy files are not shipped with SAP JVM 5.1 patches between patch level 23 (see note 1238379) and patch level 45. Patch level 46 contains them again (see note 1407902).
The SAP JVM is shipped and used with the SAP NetWeaver 7.0 installation tools (up to Enhancement Package 2). The policy files are missing there too (see also note 1238121).

Solution

The JCE Jurisdiction Policy files are provided as a separate download package, which needs to be downloaded prior installing a SAP JVM based SAP product. These files, namely (N = "4" or "5" or "6")

sapjvm_N/jre/lib/security/local_policy.jar
sapjvm_N/jre/lib/security/US_export_policy.jar


are available in two versions:

1. "Strong but limited" JCE Jurisdiction Policy files. This version limits the key length of most encryption algorithms to 128 bit. The files can be obtained from SAP's Service Marketplace at:
http://service.sap.com/swdc > Installations and Upgrades > Browse our Download Catalog > SAP Cryptographic Software

(Please download the package "SAP Java Cryptography Extension Jurisdiction Policy".)


2. "Unlimited" JCE Jurisdiction Policy files. This version allows key lenghts larger than 128 bit for most encryption algorithms. The files can be obtained from Sun Microsystems at:
For SAP JVM 4.1:
http://www.oracle. com/technetwork/java/archive-139210.html > Java Platform Technologies > Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2

For SAP JVM 5.1: http://www.oracle.com/technetwork/java/ ... 39210.html > Java Platform Technologies > Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0.

For SAP JVM 6.1:
http://www.oracle. com/technetwork/java/javase/downloads/index.html. Under Downloads goto to section: Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6. Click on Download Button


If you are currently using unlimited encryption, it is necessary to replace the delivered "Strong but limited" JCE Jurisdiction Policy files in sapjvm_N/jre/lib/security/ by unpacking the downloaded zip archive.

If not otherwise stated in the installation manuals for your SAP product, the "strong but limited" version of the JCE Jurisdiction Policy files is sufficient. However, a product which works with the "strong but limited" version, could also utilize the "unlimited" version (but not the other way around).

The handling of the JCE Jurisdiction Policy files in case of a SAP JVM patch is described in note 1133020.


Header Data

тогда вам нужен SAP GUI, он же Frontend, текущая версия 7.20

Очевидно, нужно читать указанну. ноту. У вас есть к ним доступ?

А что в батнике?