SAP Basis Tech Supports

Symptom
This note is valid for the following releases:
SAP NetWeaver 7.11 (i5/OS, Windows and Linux)
Other terms

install, SAPinst, AS/400, Java EE, iSeries,System i, homogeneous system copy, OS/400, Windows, NT, Linux, NW, IBM i
Reason and Prerequisites

Problems discovered after publication of the installation guide
Solution

This SAP Note is available in English only.
Topics Date changed
====== ============
1 General Information Jun/2008
2 Pre-Installation Feb/2009
3 Installation Mar/2009
4 Post-Installation Mar/2009
5 Troubleshooting Dec/2008
+===================================================================+
1: General Information

+===================================================================+
i5/OS
——————————————–
Independent ASPs (iASPs)
Full support for Independent ASP(iASP) installations and system copy services is available starting with SAP Netweaver 7.1 Ehp 1.
——————————————–
VNCVirtual Network Computing
Running SAPinst using VNC
The default mode to start SAPinst on IBM i is using SAPinst with
parameter ‘-nogui’ and a remote SAPinstGUI on a Windows PC as described
in the installation documentation.
An alternative way to start SAPinst is using VNC. For more information,
see http://www-03.ibm.com/servers/enable/site/porting/tools/vnc.html.
VNC offers a GUI by using IBM i tools. When VNC is prepared as described
on the IBM url the SAPinstGUI is directly started on your Windows PC
after starting SAPinst on IBM i.
The basic steps are:
1. Make sure the latest iSeries Tools For Developers product (5799PTL)
is installed in the IBM i host. The version needed to effectively run
VNC on an IBM i host is release V5R4M0, not V4R5M0.
2. Download and install the VNC viewer.
Go to www.RealVNC.com and follow links to download. (You can use the
Free Edition, and you need only install the VNC viewer, though it might
be packaged with the VNC server. Instead, you will use the VNC server
packaged with the Tools for Developers for i5/OS PRPQ, as explained
below.)
3. Create a vnc password file for your installation user (e.g. SAPIUSER)
You only need to do this the first time you want to use VNC and when you
want to change your VNC password. Create a passwd file containing your
encrypted password by running the following commands on your IBM i box:
mkdir ‘/home/youruserid/.vnc’
QAPTL/VNCPASSWD USEHOME(*NO) PWDFILE(’/home/youruserid/.vnc/passwd’)
4. Logon as installtion user and start the VNC server.
Run the following command on i5/OS to start your VNC Server environment:
STRPTL CLIENT(*VNC)
When the server starts you will see a message similar to the following:
New ‘X’ desktop is yoursystemname:1 (You will see that the variable
DISPLAY is set to ‘yoursystemname:1′ in your environment.)
(note that each time another vncserver is started, you will see a
different number in the place of :1 in the example above)
5. Next start the vncviewer (e.g. vnc-n_m_x-x86_win32_viewer.exe) you
downloaded to your pc earlier.
When the VNC Viewer is asking for Connection Details put into the Server
field: yoursystemname:n
Afterwards the VNC Viewer will ask for the Password you to put into the
password file in step 3..
Now VNC is running and you can start SAPinst by your installation user
(e.g. SAPIUSR) without the parameter ‘-nogui’. The SAPinstGUI will
appear in your VNC viewer on your Windows PC.
+===================================================================+
2: Pre-Installation

+===================================================================+
———————–————————–
ABAP+Java, Java: Make sure there is not an older version of the JCE
policy zip file for your platform on the installation host.
If there is an old JCE policy zip file, the Prerequisite Checker does
not recognize this fact. Because of this, SAPInst throws a
java.lang.SecurityException during the Create Secure Store step stating
the jurisdiction policy files are not signed by trusted signers.
For more information about how to handle the JCE Policy Zip File and how
to download it, seeSAP Note 1240081.
——————————————–
Convert the profile file DEFAULT.PFL of all old EBCDIC SAP systems
At the beginning of the installation SAPinst checks all existing SAP systems installed on your iSeries. At that time SAPinst tries to read the file DEFAULT.PFL of each system. Files in EBCDIC cannot be read and the SAPinst will end with a read error. To avoid this error convert all DEFAULT.PFL files written in EBCDIC into ASCII. The EBCDIC SAP system will still be able to handle the converted profile DEFAULT.PFL!
——————————————–
Installing additional double byte language locales
The kernel shipped with this release contains all needed single byte language locales. If you need additional double byte language locales, you have to install the missing locales using additional language DVDs. To determine which language DVD and which language library you have to install, see the IBM internet link:http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/pase_locales.htm or search for terms “pase locales” in the iSeries Information Center.
For example for the double byte locales ZH_TW you need the language DVD “Traditional Chinese” to install the language library QSYS2987.
Before you install an additional double byte language library to create additional double byte locales, make sure that PASE is installed and up-to-date.
After you have installed a new double byte language also all locales of this language are created. As a final step check if there are any PTFs to be installed using the INFOAPAR.
Linux
———————-< C5046158, Feb 2005 >————————-
Users and Permissions
Check that the following directories have an owner and group which is known to the Linux host, for example if you enter command ls -l on those directories, you should not see UIDs/GIDs, but real user names:
/sapmnt//profile
/sapmnt//global
all directories in /usr/sap/trans
For the /sapmnt subdirectories, you could do this by changing the owner to adm and the group to sapsys using qsh on System i:
chgrp sapsys /sapmnt//profile
chown adm /sapmnt//profile
For the /usr/sap/trans subdirectories, you could create artificial users and groups with those UIDs/GIDs on your Linux host.
———————-< C5046158, Feb 2005 >————————-
Format of DEFAULT.PFL
On your Linux host, convert the file /usr/sap//SYS/profile/DEFAULT.PFL to UNIX format.
+===================================================================+
3: Installation

+===================================================================+
————————————–
Changing “Custom” to “Typical” on the “Parameter Summary” screen does not work.
Symptom: You want to change from “Custom” to “Typical” parameter mode or from “Typical” to “Custom” parameter mode by using the “Revise” button on the “Parameter Summary” screen. However, this does not work.
Cause: In “Revise” mode, you can change all parameters that you can select fromthe “Parameter Summary” screen except for the parameter mode (”Typical” or “Custom”). Solution: Restart the installation with option “Run a new option”.

———————-————————–
ABAP+Java, Java: Do not uninstallallapplication server
instances
You must not uninstallallapplication server instances of an SAP
system if you want to continue using the database instance of the SAP
system.
————– ———————————
Additonal application server installation: gateway instance with same
must not exist
If you want to install the Java Add-In for an existing ABAP system or a
dialog instance, make sure that no gateway instance with the same SAP
System ID (SAPSID) exists in your SAP system landscape. If so, you must
reinstall the gateway with a different .

i5/OS
——————————————–
SAPCRYPTO.CAR
You do not have to mark the installation option of the security package SAPCRYPTO.CAR. All needed security files are part of the kernel.
But if you are asked to install the SAPCRYPTO.CAR you have to consider the following points:
System i uses the SAPCRYPTO.CAR of AIXthe SAPCRYPTO.CAR of AIX embodies different versions. Make sure to select the 64 bit version of AIX 5.1 when you are asked by SAPinst.

+===================================================================+
4: Post-Installation

+===================================================================+
———————–<24/FEB/09, D041479>————————–
Dealing safely with installation directories
Keep all installation directories until you are sure that the system, including all instances, is completely and correctly installed. Once thesystem is completely and correctly installed, make a copy of the installation directories with all their contents and save it to a physically separate medium, such as a DVD or a USB drive 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.
i5/OS
———————-< D031901, Dec 2008 >————————-
Configuration of SAP NetWeaver Process Integration 7.1 incl. EHP1
The Solution Manager Content for SAP NetWeaver PI 7.1 EHP1 is available
on SAP Service Marketplace at http://service.sap.com/maintenancenwpi71.
Prerequisites for the download: SAP Solution Manager 7.0 with STICO
150_700 Patch level 17. For information about downloading and importing
SAR-files into your SAP Solution Manager, see SAP Note 629829.
+===================================================================+
5: Troubleshooting

+===================================================================+
i5/OS
———————-< C5069979, May 2007 >————————-
During the phase ‘Unpack SAP archives’ of a distributed installation on System i, SAPinst fails with the following error:
WARNING珽 2007-04-18 15:53:50.345 琲axxbfile.cpp:644
CIaOsFile::chgrp_impl()
FSL-02003 Unable to set owner /qfilesvr.400//sapmnt//exe/uc/as400_pase_64/icmbnd for
Solution:
Log on to , where the file exists locallyChange icmbnd ownership to adm using the following command:
CHGOWN OBJ(’/sapmnt/ /exe/uc/as400_pase_64/icmbnd’) NEWOWN(ADM)Click retry or restart and continue the installation

Windows
———————-< C5038284, Dec 2008 >————————-
The Windows additional application server installation breaks in the
phase Execute/Install instance basics in step runSAPCpe.
Error message in sapinst_dev.log:
FSL-00009 System call failed. Error 2 (The system cannot find the file
in execution of system call ‘CreateProcessAsUser’ with parameter ( NULL, NULL, TRUE, 0x420, NULL, F:/usr/sap/PTZ/J00/work, &StartupInfo, &P
line (631) in file (synxcchapp.cpp), stack trace: iaxxejsctl.cpp: 272:
EJS_ControllerImpl::executeScript()
d:\depot\bas\710_rel\bc_710-2_rel\gen\optu\ntamd64\ins\sapinst\impl\src\
450: EJS_Base::dispatchFunctionCall()
iaxxejsexp.cpp: 178: EJS_Installer::invokeModuleCall()
synxcchapp.cpp: 228: CSyChildApplicationImpl::start(false)
synxcchapp.cpp: 252: CSyChildApplicationImpl::doStart()
To solve the problem press the Retry button.
If the installation still doesnot continue open a message against
component BC-INS-NT.
Linux
----------------------< C5046158, Feb 2005 >————————-
Error During sapstart
Make sure you have converted file /usr/sap//SYS/profile/DEFAULT.PFL to UNIX format.