SAP 720 Kernel

7/18/2019 SAP 720 Kernel

http://slidepdf.com/reader/full/sap-720-kernel 1/6

SAP Note

Header Data

Symptom

You want to use the SAP 7.20 EXT kernel in your SAP system environment as an alternative to the SAP 7.20 kernel.This SAP Note describes how to deploy the 7.20 EXT kernel in your SAP system that is currently using the standard 7.20 kernel by default.If you intend to use the 7.20 EXT kernel as a downward compatible kernel you can find more details in SAP note 1636252.

Other Terms

EXT, kernel, EXT kernel, 7.02, 7.20, 7.30, maintenance, 720_EXT, AKK, DCK, Downward Compatible Kernel

Reason and Prerequisites

For general information about the SAP 7.20 EXT kernel, see SAP Note 1553300.

The usage of the 7.20 EXT kernel as an alternative to the 7.20 kernel is supported for all SAP NetWeaver releases which are supported with the7.20 kernel. The following NetWeaver releases are supported with 7.20 and 7.20 EXT kernel:

l SAP NetWeaver 7.0

l SAP EhP1 for SAP NetWeaver 7.0


l SAP NetWeaver 7.1


l SAP NetWeaver CE 7.1

l SAP EhP1 for SAP NetWeaver CE 7.1

l SAP NetWeaver 7.2

l SAP NetWeaver 7.3

In addition the following NetWeaver releases are supported with the 7.20 EXT kernel:



You can find more information about the 7.20 downward compatible kernel in SAP note 1629598 and SAP note 1636252.

Attention

1553301 - 7.20 EXT Kernel - Usage

Version 15 Validity: 20.11.2013 - active Language English

Released On 20.11.2013 09:32:06

Release Status Released for Customer

Component BC-CST Client/Server Technology

BC-DB-DB2 DB2 for z/OS BC-DB-DB4 DB2 for AS/400

BC-DB-DB6 DB2 Universal Database for Unix / NT

BC-DB-MSS Microsoft SQL Server

BC-DB-ORA Oracle

BC-DB-SDB MaxDB

BC-DB-SYB Sybase ASE Database Platform

BC-OP-AIX IBM AIX

BC-OP-AS4 IBM AS/400

BC-OP-HPX HP-UX

BC-OP-LNX Linux

BC-OP-NT Windows

BC-OP-S390 IBM OS/390, z/OS BC-OP-SUN SUN Solaris

BC-OP-ZLNX Linux on IBM zSeries Hardware

Priority Recommendations / Additional Info

Category Release planning information

Other Components

7/18/2019 SAP 720 Kernel


l To use the 7.20 EXT kernel in your SAP systems, you might have to upgrade the operating system and/or the database release used for theoperation of your SAP system. To check if your operating system and/or database release is supported with the 7.20 EXT kernel, see theProduct Availability Matrix (PAM) on SAP Service Marketplace athttps://service.sap.com/pam.

l The 7.20 EXT kernel is only supported and available in a 64-bit version.

l If you are installing a new SAP system based on SAP NetWeaver 7.0 or higher or if you are creating a system copy of an existing SAP systemwhich is based on SAP NetWeaver 7.0 or higher you have to use the Software Provision Manager (SWPM). The SWPM supports the usage of the7.20 EXT kernel. For details please see SAP note 1680045.

l When you implement the 7.20 EXT kernel, you must replace the kernels of all application servers of the affected system.

l When you implement the 7.20 EXT kernel, you also have to exchange the Internet Graphics Server (IGS) by SAP IGS 7.20 EXT.

l After updating the system with the new 7.20 EXT kernel, you do not need to update SAP GUI. The installed SAP GUI also works with the 7.20EXT kernel.

l The 7.20 EXT kernel is a "binary only" release. This means that customers can implement the newer kernel without upgrading the SAP system.

l After installing the 7.20 EXT kernel, customers must continue to import the support packages for the installed SAP release when updatingor implementing corrections to the repository objects.

l After installing the 7.20 EXT kernel, customers must use only 7.20 EXT patches when implementing corrections to the kernel.

l The database Sybase ASE for Business Suite is only supported with the 7.20 EXT kernel. For the NetWeaver releases supported with SybaseASE in general check the product availability matrix (PAM).

Platform-Specific Information

l Microsoft WindowsThe 7.20 EXT kernel on Windows requires a specific C runtime that is included in the SAPEXE.SAR archive. SAP Note 1553465 describes how toapply the C runtime to your system.

l AIXPlease see SAP Note 1780629 for the minimal OS release and C/C++ runtime requirements.

l IBM iNo particular activities are required.

l LinuxBefore the installation of the 7.20 EXT kernel, see SAP Note 1563102.

l Oracle DatabaseOn IBM Power Linux and on Linux IA64 (Intel Itanium), only Oracle 10g is supported. For these two platforms you do not have to make anychanges to your database client.

On all other platforms, make sure that the following prerequisites are met before the installation of the 7.20 EXT kernel:

¡ The database server runs with Oracle 11.2.0.2 or higher. The latest SAP Bundle Patch needs to be applied on top of the existingpatchset release.

¡ Install the Oracle 11g Instant Client on all application servers and the database server as described in SAP Note 1431794: Oracle11.2.0 Instant Client.You can download the Oracle client software from SAP Service Marketplace at: https://service.sap.com/oracle-downloadIMPORTANT: After the installation of the Oracle 11g Instant Client, make sure that the library path for the <sid>adm user (LIBPATH,SHLIB_PATH, LD_LIBRARY_PATH) no longer contains any references to the old Oracle 10g Instant Client location.

l Other platformsNo specific information besides the Platform Availability Matrix (PAM) has to be taken into account.

Solution

Content 1. Manual Exchange of the 7.20 EXT Kernel in Existing SAP Systems 2. Applying the 7.20 EXT Kernel During Upgrade and Update of SAP Systems

3. Applying the 7.20 EXT Kernel Within SP Stacks 4. Updating SAP NetWeaver CE Using the Update Management Service

1. Manual Exchange of the 7.20 EXT Kernel in Existing SAP Systems

The 7.20 EXT kernel is supported only on recent versions of the database systems and the operating systems. Refer to the first part of thisNote and make sure that your computing environment fullfills all requirements.

Obtaining the 7.20 EXT Kernel

Download the latest 7.20 EXT kernel stack for your operating system and database from SAP Service Marketplace.For Windows and UNIX/Linux platforms and IBM i, the 7.20 EXT kernel stack consists of the database-independent SAPEXE.SAR and the database-dependent SAPEXEDB.SAR archives.

Download the latest support package for the IGS from the SAP IGS 7.20 EXT branch. The package constists of the IGSEXE.SAR and the IGSHELPER.SARarchives.

If you are using SAPCRYPTOLIB, download the EXT version of the corresponding archive in accordance with SAP Note 397175.

For Oracle, you also need the archive DBATOOLS.SAR.

Replacing the 7.20 Standard Kernel by the 7.20 EXT Kernel for an ABAP-Only Stack and for an ABAP/Java Dual Stack

If no explicit other statement is given, the following tasks have to be performed as user <SAPSID>adm. The kernel has to be exchanged in thes are rectory o t e rst nsta at on ost. T e program sapcpe automat ca y cop es a requ re es to t e oca rector es ur ng t enext start of the SAP system.

Preliminary Tasks

1. Stop the SAP system (there is no need to stop the database).

2. Terminate the SAProuter.<DVEBMGS00>/data/stat).

7/18/2019 SAP 720 Kernel


Deploying the Kernel A. On UNIX / Linux Platforms

1. Log on to your first installation host as user <SID>adm.

2. Copy the kernel archives SAPEXE.SAR and SAPEXEDB.SAR and the IGS archives IGSEXE.SAR and IGSHELPER.SAR to a temporary directory<TEMPDIR> of your choice (for example, /tmp).

3. If you are using the Oracle database, copy the archive DBATOOLS.SAR to a temporary directory <TEMPDIR> of your choice (forexample, /tmp).

4. Switch to one of the following kernel directories:

¡ /usr/sap/<SAPSID>/SYS/exe/runon systems based on EhP 2 for SAP NetWeaver 7.0

¡ /usr/sap/<SAPSID>/SYS/exe/<codepage>/<platform>on systems based on SAP NetWeaver 7.30

5. We recommend to save the old kernel before deploying the EXT kernel.

Save the old kernel by creating a tar archive of the complete kernel directory using the following command:

tar -cvf ../sapexe.tar

6. Save the SAPCAR program to a temporary directory <TEMPDIR> of your choice (for example, /tmp).

7. Switch to the user root and change the owner of all files to <SAPSID>adm using one of the following commands:

¡ su - rootchown <SAPSID>adm /usr/sap/<SAPSID>/exe/run/*exit

on systems based on EhP 2 for SAP NetWeaver 7.0

¡ su - rootchown <SAPSID>adm /usr/sap/<SAPSID>/SYS/exe/<codepage>/<platform>exiton systems based on SAP NetWeaver 7.30

Caution: With the OS/390 operating system, you have to use the command "su <user>" instead of "su - root", where <user> must havethe UID 0.

8. Unpack the new kernel using the following commands:

<TEMPDIR>/SAPCAR -xvf <TEMPDIR>/SAPEXE.SAR

<TEMPDIR>/SAPCAR -xvf <TEMPDIR>/SAPEXEDB.SAR

9. If you are using the Oracle database, unpack the archive DBATOOLS.SAR using the following command:

<TEMPDIR>/SAPCAR -xvf <TEMPDIR>/DBATOOLS.SAR

10. Unpack the new IGS using the following commands:

<TEMPDIR>/SAPCAR -xvf <TEMPDIR>/IGSEXE.SAR

<TEMPDIR>/SAPCAR -xvf <TEMPDIR>/IGSHELPER.SAR

11. Switch to the user root and run the shell script saproot.sh, which is available in the kernel directory.

In addition to the deployment of the IGSHELPER.SAR archive in the installation directory as described in the previous section, you have todeploy the IGSHELPER.SAR archive additionally in the instance directory of the primary application server instance and for every additional

application server instance.For the primary application server instance and every application server instance proceed as follows:

1. Logon to your host as user <SID>adm

2. Copy the IGS archive IGSHELPER.SAR to a temporary directory <TEMPDIR> of your choice (for example, /tmp).

3. Switch to one of the following instance directories:

¡ /usr/sap/<SAPSID>/DVEBMGSon the primary application server instance

¡ /usr/sap/<SAPSID>/Don the additional application server instance

4. Unpack the IGSHERLPER.SAR archive using the following command:

./exe/SAPCAR -xvf <TEMPDIR>/IGSHELPER.SAR

B. On Windows

1. Copy the kernel archives SAPEXE.SAR and SAPEXEDB.SAR and the IGS archives IGSEXE.SAR and IGSHELPER.SAR and the archive for the DBAtools DBATOOLS.SAR (Oracle only) to a temporary directory <TEMPDIR> of your choice (for example, c:\temp).

2. Determine the value of the SAP profile parameter DIR_CT_RUN according to SAP Note 997848.

7/18/2019 SAP 720 Kernel


3. On t e g o a ost, og on as <SAPSID>a m an open a comman prompt cm .exe as a m n strator. Set t e wor ng rectory to yourkernel staging directory DIR_CT_RUN, for example, <drive>:\usr\sap\<SAPSID>\sys\exe\[uc|nuc]\<platform>.

4. Copy sapcar.exe to the parent directory of DIR_CT_RUN

(copy sapcar.exe ..).

5. I you want to eep t e o erne executa es, you must use t e copy unct on to create a ac up an not t e rename unct on. For moreinformation, see SAP Note 142100, point 18.

6. Unpack the new kernel from the kernel archives stored in the temporary directory in the specified sequence.

IMPORTANT: Do not ca SAPCAR.EXE rect y w t out a pat spec cat on. Instea , use t e cop e vers on o SAPCAR.EXE n t e parentdirectory of the current kernel directory.

..\sapexe.car -xvf <TEMPDIR>\SAPEXE.SAR

..\sapexe.car -xvf <TEMPDIR>\SAPEXEDB.SAR

..\sapcar.exe -xvf <TEMPDIR>\DBATOOLS.SAR (Oracle only)

Note:

If your path to <TEMPDIR> contains blanks you need to put the path in double quotes and include a trailing comma:

Example:

..\sapcar.exe -xvf "c:\<directory_with_blanks>\dbatools.sar,"

7. Unpack the new IGS from the IGS archives stored in the temporary directory in the specified sequence.

..\sapexe.car -xvf <TEMPDIR>\IGSEXE.SAR

8. Deploy the IGSHELPER.SAR archive in the instance directory of the primary application server instance and for every additionalapplication server instance.

For the primary application server instance and every application server instance proceed as follows:

a) Log on to your host as user <SID>adm.

b) Copy the IGS archive IGSHELPER.SAR to a temporary directory <TEMPDIR> of your choice (for example, c:\temp).

c) Switch to one of the following instance directories:

¡ <drive>:\usr\<SAPSID>\DVEBMGS<No>on the primary application server instance

¡ <drive>:\usr\sap\<SAPSID>\D<No>on the additional application server instance

d) Unpack the IGSHERLPER.SAR archive using the following command:

sapcar.exe -xvf <TEMPDIR>\IGSHELPER.SAR

9. Install the current C runtime library by executing vcredist_<platform>.msi in the command box (or by double-clicking this file in theWindows Explorer). Before you start the system for the first time, and if you have a distributed system environment, perform this stepmanually on each node where a component of the system is configured to run.

10. MSCS only:

Update the files on all cluster nodes in the Windows\SAPCLUSTER directory with the corresponding files in the central kernel staging

directory.

C. On IBM i

1. Log on to your first installation host as user <SID>adm.

2. Copy the kernel archives SAPEXE.SAR and SAPEXEDB.SAR and the IGS archives IGSEXE.SAR and IGSHELPER.SAR to a temporary directory<TEMPDIR> of your choice (for example, /tmp).

3. Run the APYSIDKRN command as follows:

APYSIDKRN SID(<SAPSID>)

ARCHIVES('<TEMPDIR>/SAPEXE.SAR'

'<TEMPDIR> /SAPEXEDB.SAR'

'<TEMPDIR> /IGSEXE.SAR'

'<TEMPDIR>/IGSHELPER.SAR')

MODE(*FULLY) CARPATH(*BUILTIN)

D. On all platforms if you are using SAPCRYPTOLIB

Reinstall SAPCRYPTOLIB according to SAP Note 510007, step 1.

The installation procedure is also described in the SAP Help Portal, http://help.sap.com. Search Documentation for

7/18/2019 SAP 720 Kernel


l Insta ng t e SAP Cryptograp c L rary on t e AS ABAP

l "Installing the SAP Cryptographic Library on the AS Java"

(enter the search string with quotation marks), Product Type "SAPNetWeaver", Release "7.0 EHP2".

Replacing the 7.20 Standard Kernel by the 7.20 EXT Kernel for a Java-Only Stack

To replace the 7.20 standard kernel with the 7.20 EXT kernel in a Java-only stack, proceed as described in the SAP Knowledge Base article1505299. Be aware of choosing the correct 7.20 EXT kernel archives for your platform (correct DB/OS combination, 64 bit, Unicode).To replace the IGS archives IGSEXE.SAR and IGSHELPER.SAR, you have to follow the instructions provided in the section "Replacing the 7.20Standard Kernel by the 7.20 EXT Kernel for an ABAP-Only Stack and for an ABAP/Java Dual Stack".

2. Applying the 7.20 EXT Kernel During Upgrade and Update of SAP Systems

Be ore start ng t e upgra e or up ate o your SAP system, ma e sure t at t e ata ase an t e operat ng system u t e m n mum requ rementsas described in the first section of this Note and in the "Platform-Specific Information" section.

Defining the SP Stack for Upgrade or Update Using the SAP Maintenance Optimizer

While creating your SP stack definition, you have to select the appropriate SAP kernel for your SAP system. Instead of selecting the 7.20stan ar erne n t e SAP Ma ntenance Opt m zer MOPZ , you ave to se ect t e respect ve 7.20 EXT erne or your system an scape. Ma e surethat you select the correct 7.20 EXT kernel for your platform (correct DB/OS combination, 64 bit, Unicode/Non-Un co e . For IGS, c oose SAP IGS7.20 EXT.

Defining the SP Stack for Upgrade or Update on SAP Service Marketplace

While creating your SP stack definition, you have to select the appropriate SAP kernel for your SAP system. Instead of selecting the 7.20standard kernel on SAP Service Marketplace, you have to select the respective 7.20 EXT kernel for your system landscape. Make sure that youselect the correct 7.20 EXT kernel for your platform (correct DB/OS combination, 64 bit, Unicode/Non-Unicode). For IGS, choose SAP IGS 7.20EXT.

If you upgrade or update an SAP CE system, refer to section 4 of this Note: Updating SAP NetWeaver CE Using the Update ManagementService The update of SAP NetWeaver CE 7.0 to SAP NetWeaver CE 7.2 and EhP 1 for SAP NetWeaver CE 7.0 to SAP NetWeaver CE 7.2 requires to define the SPstack on SAP Service Marketplace as described above.

3. Applying the 7.20 EXT Kernel Within SP Stacks

Before starting the installation of the SAP stack on your SAP system, make sure that the database and the operating system fulfill the minimumrequirements as described in the first section of this Note and in the "Platform-Specific Information" section.While creating your SP stack definition, you have to select the appropriate SAP kernel for your SAP system. Instead of selecting the 7.20standard kernel, you have to select the correct 7.20 EXT kernel for your platform (correct DB/OS combination, 64 bit, Unicode/Non-Unicode).This automatically puts the right archives to your download basket. All other steps in the update procedure of your system do not change. ForIGS, choose SAP IGS 7.20 EXT.

4. Updating SAP NetWeaver CE Using the Update Management Service

The Update Management Service helps to automate the process of updating the SAP NetWeaver CE system. Using the Update Management Service, youcan update your CE system in one of the following ways:

l Using a locally downloaded Support Package Stack

l Using an SMP Automatic Update

I you nten to app y t e 7.20 EXT erne to your CE system on y, t e met o y us ng a oca y own oa e Support Pac age Stac s supporte .This applies to the following:

l System upgrade and system update

l Deployment of an SP stack

l Any other software lifecycle operation if you are already using the 7.20 EXT kernel in your system

While creating your SP stack definition, you have to select the appropriate SAP kernel for your SAP system. Instead of selecting the 7.20standard kernel, you have to select the correct 7.20 EXT kernel for your platform (correct DB/OS combination, 64 bit, Unicode). Thisautomatically puts the right archives to your download basket. All other steps in the update procedure of your system remain unchanged. ForIGS, choose SAP IGS 7.20 EXT.

The Update Management Service using an SMP Automatic Update is not supported with the 7.20 EXT kernel at all.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes 142100 Windows: Problems with new SAP service as of Rel. 4.5B

1431794 Oracle 11.2.0: Instant Client

1553300 7.20 EXT Kernel - Extended Kernel Maintenance

1553465 Prerequisites for 720/721 EXT and higher kernels on Windows

1563102 Linux Requirements for 7.20 EXT and higher kernel

1569874 Initial delivery of SAP IGS / SAP IGS Helper 7.20_EXT

1591607 SAP Kernel for SAP_BASIS releases 7.03 and 7.31

7/18/2019 SAP 720 Kernel


This document is referenced by:

SAP Notes (22)

1597627 SAP HANA connection

1609441 Add. info about the upgrade to SAP NetWeaver 7.3 EHP1

1629598 SAP Kernel 720 will replace older kernel versions

1636252 Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

1638356 Additional information about BR*Tools Version 7.20 EXT

1678024 Linux: NetWeaver 7.0 EhP 3 with SAP kernel 720

1680045 Release Note for Software Provisioning Manager 1.0

1687173 IBM i: Collection of notes about the 7.20 kernel

171356 SAP software on Linux: Essential information

1713986 Installation of kernel 721 (EXT)

1716826 Usage of the downward compatible kernel 721 (EXT)

1780629 AIX: Minimal OS Requirements for SAP Kernel 397175 SAP Cryptographic Software - Export control

510007 Setting up SSL on Web Application Server ABAP

142100 Windows: Problems with new SAP service as of Rel. 4.5B

397175 SAP Cryptographic Software - Export control

171356 SAP software on Linux: Essential information

1569874 Initial delivery of SAP IGS / SAP IGS Helper 7.20_EXT

1713986 Installation of kernel 721 (EXT)

1716826 Usage of the downward compatible kernel 721 (EXT)

1591607 SAP Kernel for SAP_BASIS releases 7.03 and 7.31 1629598 SAP Kernel 720 will replace older kernel versions

1636252 Installing a 7.20 kernel in SAP Web AS 7.00/7.01/7.10/7.11

1638356 Additional information about BR*Tools Version 7.20 EXT

1780629 AIX: Minimal OS Requirements for SAP Kernel

1926209 Questions on subjects of 7.20/7.21 EXT kernel and C/C++ runtime

510007 Setting up SSL on Web Application Server ABAP

1678024 Linux: NetWeaver 7.0 EhP 3 with SAP kernel 720

1553300 7.20 EXT Kernel - Extended Kernel Maintenance

1553465 Prerequisites for 720/721 EXT and higher kernels on Windows

1431794 Oracle 11.2.0: Instant Client

1680045 Release Note for Software Provisioning Manager 1.0

1687173 IBM i: Collection of notes about the 7.20 kernel

1563102 Linux Requirements for 7.20 EXT and higher kernel

1597627 SAP HANA connection

1609441 Add. info about the upgrade to SAP NetWeaver 7.3 EHP1

Documents

SAP 720 Kernel