Kernel Installation 720 based on OSS # 1636252 & 1553465

Prereqs
1.
2.
3.
4.
5.

Download Kernel 720 sapexe & sapexedb files.

Download all additional programs rfcsdk etc
Download saphostagent latest package
Download igsexe.sar & igshelper.sar for kernel720
Prerequisites for Windows per OSS # 1553465

The SAP installation and upgrade tools normally install the required Microsoft C
-runtime. This is not the case if you download an SAP kernel as SAPEXE.sar archi
ve from SAP Service Marketplace. In this case, you have to install the C-runtime
manually as follows:
1. Extract the SAPEXE.sar archive, which contains the installer package vcre
dist_XXX.msi.
XXX is a placeholder for the platform and has one of these values: x64, x86,
ia64.
2. Execute the vcredist_XXX.msi installer package for your platform.
After the installation has finished successfully, the operating system contains
the required C-runtime.
INSTALLATIONS STEPS
5.1 StopSAP
1. Stop the SAP system. (You do not need to stop the database.)
On UNIX or Windows:
Stop the SAP system as usual.

5.2. Stop saposcol.

If it exists, stop the Windows service SAPOsCol and delete it using the foll
owing commands:
net stop saposcol
sc delete saposcol
5.3
Stop and deactivate (Startup Type = Disabled) the services SAP<SID>_<INSTANC
E no.>.
5.4 If present, unregister all standalone CCMS agents (sapccmsr [-j2ee], sapccm4
x). On Unix you can see corresponding processes, on Windows you can see them run
ning as services <agent name>.<instance number>:
sapccm4x -u pf=<profile the agent started with>
sapccmsr -u pf=<profile the agent started with> [-j2ee]
5.5 Remove any IPC objects that still exist (this is required on UNIX only):
cleanipc <instance no> remove

5.6 Installing SAPHOSTAGENT

-- Download latest saphosagent.sar file and download to staging directory C:\M\
saphostagent\saphostagent.sar
-- cd C:\M\saphostagent
-- SAPCAR -xvf saphostagent.sar
-- saphostexec.exe -install
Once installed, check that saposcol saphostexec & sapcontrol services are runnin
g with command
-- C:\usr\sap\hostctrl\exe\saphostexec -status
To check version
-- C:\usr\sap\hostctrl\exe\saphostexec -version
5.7 Afterwards, you must delete the call of the program SAPOSCOL from all the st
art profiles. (not Windows)
5.8. Importing the new kernel
Import the 7.20 kernel from the directory <newkernel> on the host of the central
instance and then on all of the application servers with local executables.

8. If you use IGS, you must unpack the IGS archive using the following
command:
<newkernel>/SAPCAR -xvf <newkernel>/igsexe. sar
9. If there are files or directories that were saved in step 3, restore them
into the current directory
10. To deploy the optional IGSHELPER archive switch to the relevant local di
rectory /usr/sap/SPM/DVEBMGS00/ on every instance and execute the command:
<newkernel>/SAPCAR -xvf <newkernel>/IGSHELPER. SAR
11. Switch to the user root and run the shell script saproot.sh, which is av
ailable in the kernel directory.
su - root (or su <user with UID 0> on OS/390)
cd /usr/sap/<SAPSID>/SYS/exe/run
./saproot.sh <SAPSID>
exit
12. Delete all of the local executables on the individual instances. To do t
his, switch to the relevant local executable directory /usr/sap/<SAPSID>/<INSTAN
CE>/exe and execute
rm -rf *
13. Since executables from the local executable directories may already be e

xecuted for the start before sapcpe runs, start an initial copy of the executabl
es.
a) All application server instances (primary application server/central
instance, additional application servers/dialog instances):
For ABAP-only systems:
cd /usr/sap/<SAPSID>/<INSTANCE>/work
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>
For Dual-Stack systems:
cd /usr/sap/<SAPSID>/<INSTANCE>/work
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile>
If your system is running with the SAPJVM:
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> s
ource:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst
For Java-only systems:
cd /usr/sap/<SAPSID>/<INSTANCE>/work
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> list:/usr/sap/<SAPSID
>/SYS/exe/run/j2eeinst.lst
If your system is running with the SAPJVM:
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> s
ource:<sapjvm directory> list:<sapjvm directory>/sapjvm_<version>.lst
b) For additional instances such as ASCS, SCS and ERS (exist only in a c
luster):
cd /usr/sap/<SAPSID>/<INSTANCE>/work
sapcpe pf=/usr/sap/<SAPSID>/SYS/profile/<instance profile> list:/usr/sap/<SAPSID
>/SYS/exe/run/scs.lst
NB: the arguments ("pf", "list", "source") are separated by a white s
pace, not by a newline character. <sapjvm directory> means the location of the s
aved SAPJVM, see the step 9 above.
4.2 On Windows
1. Log on as user <sapsid>adm and switch to the global host in your kernel d
irectory, for example: <drive>:\usr\sap\<SAPSID>\sys\exe\<uc|nuc>
2. Rename the <platform> directory, for example <platform>.save.
3. Create a new directory <platform> and switch to this directory.
Unpack the new kernel from the directory <newkernel> of the downloaded a
rchive in the specified sequence.

Important: Do not call SAPCAR.EXE directly without specifying a path; in

stead, use the specified directory structure.

<newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXE.SAR

<newkernel>\SAPCAR.EXE -xvf <newkernel>\SAPEXEDB.SAR

4. Restore the following directories and files into the newly created direct
ory if they exist in the <platform>.save directory
a) the directory jvm or sapjvm* (e.g., sapjvm, sapjvm_4)
b) the file protect.lst
c) the files rfcexec.exe, rfcexec.sec
d) the icu libraries icu*30.dll or icu*34.dll if they exist
The directories jvm or sapjvm* and the file protect.lst only exist i
n the case of a Java or Dual-Stack implementation.
The files rfcexec and rfcexec.sec are only used in customer specific non-ALE sce
narios. It is mandatory to check if such scenarios exist. With the ALE scenario
the classic rfcexec needs to be replaced with the version delivered with NW RFC
SDK 720. Details are available in SAP note 1140031.
5.

<newkernel>\SAPCAR.EXE -xvf <newkernel>\DBATL720O10.SAR

6. If you use IGS, unpack the new IGS using the following command:

<newkernel>\SAPCAR.EXE -xvf <newkernel>\igsexe.sar

7. To deploy the optional IGSHELPER archive, still logged in as <sapsid>adm,
switch to the relevant local directory on every instance. For example:
primary application server instance:
<drive>:\usr\sap\<SAPSID>\DVEBMGS<No>
additional application server instance:
<drive>:\usr\sap\<SAPSID>\D<No>
and execute the command
< newkernel>\SAPCAR.EXE -xvf <newkernel>\IGSHELPER.SAR
8. On all instances in the directories <drive>:\usr\sap\<SAPSID>\<INSTANCE>\
exe, delete all of the files (including the subdirectories).
9. Install the current C runtime library as per note 1553465 by executing vc
redist_<platform>.msi in the command box (or by double-clicking this file in the
Windows Explorer). Before you start the system for the first time, and if you h
ave a distributed system environment, perform this step manually on each node wh
ere a component of the system is configured to run.

10. Since executables from the local executable directories may already be e
xecuted for the start before sapcpe runs, start an initial copy of the executabl
es.
a) For all application server instances (primary application server/cent
ral instance, additional application servers/dialog instances):
For ABAP-only systems:
< drive>:
cd \usr\sap\<SAPSID>\<INSTANCE>\work
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>
For Dual-Stack systems:
< drive>:
cd \usr\sap\<SAPSID>\<INSTANCE>\work
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile>
If your system is running with the SAPJVM:
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance pr
ofile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst
For Java-only systems:
< drive>:
cd \usr\sap\<SAPSID>\<INSTANCE>\work
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> list:<drive>:
\usr\sap\<SAPSID>\sys\exe\<uc|nuc>\<platform>\j2eeinst.lst
If your system is running with the SAPJVM:
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance pr
ofile> source:<sapjvm directory> list:<sapjvm directory>\sapjvm_<version>.lst
b) For additional instances such as ASCS, SCS and ERS (exist only in a c
luster):
< drive>:
cd \usr\sap\<SAPSID>\<INSTANCE>\work
sapcpe pf=<drive>:\usr\sap\<SAPSID>\sys\profile\<instance profile> list:<drive>:
\usr\sap\<SAPSID>\sys\exe\<uc|nuc>\<platform>\scs.lst
NB: the arguments ("pf", "list", "source") are separated by a white s
pace, not by a line break. <sapjvm directory> means the location of the saved SA
PJVM, see the step 4 above.
11. Activate (Startup Type = Automatic) and start the Windows Services SAP<S
ID>_<INSTANCE no.> of primary application server instance and of every additiona
l application server instance to active the new version of sapstartsrv.exe.

MSCS only:
1. Start and Stop the clustered (A)SCS instances and the appropriate SAP ser
vices using the cluster admin tool or the Powershell.
2. Also see SAP Note 1596496 on how to update the SAP Resource Type DLL.
3. You have to follow step 6-10 also for the ERS instances on your clust
er nodes.
Search for REPSRV.lst in all Start Profile of the ERS instances (line St

art_Program_00 =)and if it exists replace it with SCS.lst.

Be sure to check if your Enqueue Replication Service is replicating again af
ter starting the ERS instances
4. If you have standalone gateway instances installed on cluster nodes, thes
e also need to be updated with the corresponding files from the kernel staging d
irectory \\$(SAPGLOBALHOST)\sapmnt\<SAPSID>\sys\exe\<nuc|uc>\<platform>.
On Windows Server 2003 (see Note 657999) the standalone gateway is insta
lled in the <Windows>\SAPCLUSTER directory.
On Windows Server 2008 and higher (see Note 1764650 - How to install a s
tandalone gateway in a Microsoft Failover Cluster for Oracle) it is <oracle shar
ed disk>:\sap\<DB-SID>\dbtools.

5.2 Additional manual changes in Dual-Stack and Java-only systems

This step applies only to releases 7.00 and 7.01.
Only necessary in case of a Dual-Stack system: you must set the following pa
rameter in the default system profile DEFAULT.PFL:
system/type = DS
In all (Dnn, DVEBMGSnn, Jnn, JCnn, etc.) instance profiles, you must set the
following parameter:
FN_JSTART = jcontrol$(FT_EXE)
5.3 Reinstalling SAPCRYPTOLIB
Starting with the patch level 513, also in SP stack kernels 720 PL >=600, a new
CommonCryptoLib is delivered with the SAP Kernel. This library is fully compatib
le to the SAPCRYPTOLIB and replaces it, so the reinstallation of SAPCRYPTOLIB is
no longer necessary. See the Note 1848999 for more detail.
5.4 Reinstalling additional programs
If you had installed additional programs such as the RFC Library, you have to in
stall them again. To do this, proceed as follows:

On Windows:
Execute the following commands as user <SAPSID>ADM:
1. CD \USR\SAP\<SAPSID>\SYS\EXE\RUN
2. <newkernel>\SAPCAR.EXE -xvf <newkernel>\<additional package>.SAR
On IBM i:
On IBM i, you do not have to install any further programs.

5.4.1 Copying executable files from NetWeaver RFC SDK 720.

Due to security reasons the program rfcexec (UNIX and IBM i) or rfcexec.exe (Win
dows) is no longer shipped together with SAP kernel 720. For various reasons, it
is mandatory to move to a new version of these files, contained in the NW RFC S
DK 720. Please refer to SAP Notes 1581595 and 1025361for detailed instructions a
nd further information.
Remark: The new version of rfcexec might break some of your application scenario
s. Only in this case it is required to use the old version, which was saved in t
he previous preparation step (Unix, step 3 c, Windows 4 c).
5.5 Special features for the syslog (ABAP-only and Dual-Stack systems)
Due to the situation described in note 1517379, you have to set the profile para
meter
rslg/new_layout = 9.
If a syslog file already exists in the new format because this parameter has not
been set from the very beginning, the syslog will still be written in the new f
ormat even if the parameter has been set in the meantime. In that case, the exis
ting syslog files have to be deleted.
5.6 Dynamic work processes (NW 7.00 and NW 7.01 systems only)
The 7.20 kernel supports the dynamic increase of the number of work processes at
runtime. However, this function is not fully compatible with NW 7.00 and NW 7.0
1. To prevent errors from occurring, deactivate it by setting the following para
meters:
rdisp/wp_no_restricted = 0
rdisp/configurable_wp_no = 0
rdisp/dynamic_wp_check = FALSE
rdisp/wp_max_no = Sum of
( rdisp/wp_no_dia + rdisp/wp_no_btc + rdisp/wp_no_vb + rdisp/wp_no_vb2 + rdisp/w
p_no_spo +rdisp/wp_no_enq )
Mind that rdisp/wp_max_no has the default value DEFAULT, which will a
dd two unwanted dynamic processes if not set to the number of configured classic
al wp types.
5.7 Configuration of the CCMS central monitoring
Depending on the SAP kernel release of the monitored system you upgraded from an
d depending on the release of the central monitoring system (CEN), it is necessa
ry to check the following scenarios:
You upgraded the monitored system:
CEN system is based on SAP_BASIS 7.0 (7.00) and lower:
You have to disable the integrated CCMS agents in sapstartsrv of the upg
raded system and use standalone CCMS agents instead. sapccm4x for the central mo
nitoring of pure ABAP and Dual-Stack systems, sapccmsr -j2ee for the central mon
itoring of pure Java systems. Please proceed as outlined in note 1368389, sectio
n "Solution".
CEN system is based on SAP_BASIS 7.0 EhP 1 (7.01):

The registration of the integrated CCMS agents from the central system n
eeds to be repeated. Please follow the instructions given in SAP Help (http://he
lp.sap.com/saphelp_nwpi71/helpdata/EN/44/893e933dc912d3e10000000a422035/content.
htm).
You upgraded the central system:
No reconfiguration is necessary.
SAP note 1667336 contains a detailed description for every case.

6 System Start
Start the SAP system with the new kernel and check the poins below if relevant.
6.1 AS Java or Dual-Stack systems with release 7.00 or 7.01
If the Java instance or even the complete system does not start, check the follo
wing points:
The minimum support packages and patch levels have been installed as describ
ed in section "Attention" under "Reason and Prerequisites".
sapjvm: The directory jvm or sapjvm or the file protect.lst have been saved
and restored as described in
Section 4.1, "On Unix", steps 3 and 9
Section 4.2, "On Windows", step 4
6.2 DDIC_TYPELENG_INCONSISTENT short dumps
If you did not handle the DDIC_TYPELENG_INCONSISTENT issue, which is described i
n chapter "Reason and Prerequisites", section "Attention", while the original ke
rnel was still running, you should now install Note 1610716.
in instance profile, add parameter rslg/new_layout = 9
and delete /usr/sap/SPM/SYS/global/*.SLOG
6.3 Load format of ABAP programs
After you start the SAP system with the new kernel, the following message is dis
played in the system log: 'Load format of PROGRAM not valid.'
You can ignore this message because the load is automatically regenerated.
It is also possible to regenerate these ABAP loads directly using transaction SG
EN. For more information see Note 185745.
6.4 CCMS Monitoring issues
In case of any issues with the CCMS monitoring after the kernel upgrade, check n
ote 1667336, in particular the section "Local monitoring in the upgraded doublestack system".-

1347768 - ume browser support

869852 - webdynpro ume disable
pdf - sap* activate