SAP NetWeaver 2004s kernel updates explained -- Part I

Storm Archer III/SDN

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This Reprints

What is the kernel of an SAP system? An ABAP or Java-based SAP system runs on top of the SAP Web Application Server. This software serves as an abstraction layer between the underlying operating system and database system to the ABAP or Java applications. The applications then are coded and run in an OS and DB-independent manner. The execution environment of the applications is often referred to as a Runtime system. Thus, the kernel of an SAP system consists of all native programs and dynamic libraries that are required for launching the Runtime, executing ABAP or Java codes, communicating with the outside world of the application server like OS, DB and network. These native binaries can be categorized through different aspects: * DB-dependent vs. DB-independent: While all native binaries are OS-specific, they can be grouped in either database-dependent or independent manner. Mostly there are numerous database management systems available for a particular Operating System. The DBdependent part -- which is small in size -- presents the abstraction layer to the particular database system and the DB-independent part -- which makes up the vast majority of all native codes -- presents the abstraction layer to the rest of the outside world. *Unicode vs. Non-Unicode: Depending on users' requirement, an SAP system supports data encoding either as Unicode or as non-Unicode. Since the processing of Unicode data and non-Unicode data respectively are slightly different, the kernel binaries are compiled accordingly. * Primary vs. subsidiary: Some of the kernel binaries are permanently loaded in the memory when the system is running. We call them primary. In other words, without the primary codes, the system is not functioning. Contrary to the primary programs, the subsidiary programs provide tools and services which are used occasionally, no matter whether the system is running or not, in terms of OS and DB abstraction. How to get the kernel patches?

You can download the latest versions of the kernel patches from the SAP Service Marketplace (http://service.sap.com), either as part of an SP Stack or separately. However, you have to take following facts into account: * What operating systems is your system running on? In some (although rare) cases, you need multiple variants of the kernel patches, because it's possible to install a SAP system in a cluster with different operating systems. *Do you need a Unicode or non-Unicode kernel, or both of them? This question is especially relevant, if the system is ABAP-based. Java-based systems are always Unicode systems. A Double-Stack system runs both an ABAP and a Java engine, while the ABAP part runs with a non-Unicode kernel. Once these details have been determined, you can go on with selecting the appropriate packages on the SAP Service Marketplace. There are two packaged files for each OS-DBcombination, SAPEXE.SAR for the DB-independent part and SAPEXEDB.SAR for DBdependent part. As mentioned, the first file is much larger than the latter one. These two packages together consist of updates of all kernel binaries needed to patch the system kernel to level in required. .SAR files are an SAP-specific archive format. You can extract this format with the tool SAPCAR which in turn is one of the kernel programs. Normally, the existing SAPCAR tool should be able to open the newer kernel package .SAR files with the existing SAPCAR. Occasionally it happens that you cannot open the newer .SAR files with the older SAPCAR, because the format has been enhanced. In this case, you can download SAPCAR alone from the SAP Service Marketplace. Other standalone tools are also available; SAPCPE which we will deal with in more detail later. Read SAP NetWeaver 2004s kernel updates explained -- Part II

This content is reposted from the SAP Developer Network. Copyright 2006, SAP Developer Network SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free. Want to read more from this author? Click here to read Storm Archer III's Weblog. Click here to read more about Application Server on SDN.

SAP NetWeaver 2004s kernel updates explained -- Part II

Storm Archer III/SDN

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This RSS Reprints

SAP NetWeaver 2004s kernel updates explained -- Part I Now let's explore the update procedures in more detail. Binary distribution with SAPCPE Before we go on with the procedures of different system types, it makes sense to have a closer look at how the kernel updates is distributed to the different instances of a Web Application Server. The graphic below depicts the file system layout of a typical system installation on Unix (It's similar on other operating system like Windows).

SAP Netweaver 2004s Kernel Updates Explained Normally each system has a so-called SAPGLOBALHOST which is shared by all instances system-wide. The kernel files of all relevant platform combinations reside on this host under the directory /<sapmnt>/<SAPSID>/exe. Each host in the system cluster mounts this global directory to its file system beside the instance-individual directories which are depicted with

the left branch in the graphic. The system directory /usr/sap/<SAPSID>/SYS is shared by all instances on the host and maintain links to the global host so that all instances can access the global host via the links. Each instance on the host points to a subdirectory beneath the system directory with the instance-specific parameter DIR_CT_RUN. When an instance starts, a bootstrap program called SAPCPE which itself is a kernel program comes into play first. The job of SAPCPE is to compare the binaries in the local-instance executable directory with the DIR_CT_RUN. If new versions of the relevant files are available in DIR_CT_RUN, it copies them to instance's executable directory. In this way, new kernel updates are distributed to the instances. However, in a heterogeneous system landscape, where the instances run on hosts of different operating systems, it is possible, that the DIR_CT_RUN directory of some hosts are not linked to the global host because of file format compatibility. Thus SAPCPE cannot copy the new version of the kernel files from the global host to the local executable directory. We will discuss the update process for this case later. Standalone ABAP system Now let's discuss the update of the kernel update of a standalone ABAP system. For a homogeneous system with only the ABAP engine, it is rather straight forward. Logon as the <sid>adm user onto the central instance host. After you have stopped the system and all OS-level services of all instances, unpack the kernel patch files SAPEXE.SAR and SAPEXEDB.SAR to the DIR_CT_RUN of the central instance. Execute the command as follows: sapcar -xvf <file>-R <DIR_CT_RUN> Because DIR_CT_RUN of the central instance is linked to the corresponding directory on the global host which is accessible from all hosts in the cluster, the updates will be distributed by SAPCPE when the instances start as explained. In a heterogeneous system landscape, if there are instances whose DIR_CT_RUN directory does not point to the system's global host, you have to patch their DIR_CT_RUN separately like on the central instance host. You can find out the value of DIR_CT_RUN of a particular dialog instance using the transaction RZ11, if the instance is running. Another way is to use the kernel program SAPPFPAR which can be invoked for the Central Services Instances in a HA installation (ASCS) and idle dialog instances. The command spells as follows: sappfpar pf=<instance profile> The instance profiles are located in the /usr/sap/<SAPSID>/SYS next to the DIR_CT_RUN. For Unix platforms, there is one thing you have to perform before you restart the system. Due to the security implementation of Unix, you have to re-logon as a root user and execute the kernel script saproot.sh once in order to assign all necessary root permissions to the newly copied files. Java and double-stack systems

Applying kernel updates to a Java system is a little bit different. Unlike SPAM in ABAP, the counterpart for Java systems (JSPM) is able to apply kernel updates too. Although you can update the kernel of your system like in an ABAP system as discussed above, why not just use JSPM? In this way, you can combine the applications of the kernel update and Support Packages of standard Software Component in a single run. Nonetheless, JSPM does not take over all manual activities. Since you can perform JSPM (which is a central tool) only on the central instance host as the <sid>adm user, JSPM is not able to restart the OS-level services of all instances situated on different hosts. For kernel update to take effect to all instances, the OS-level services of the instances have to be restarted. Therefore, you also have to logon to the hosts of the system cluster and restart the instances manually once JSPM has finished the kernel update on the central host. It is fairly common to run a Java engine along with an ABAP engine in the same system. This type of system is called double-stack system. In the case that the ABAP engine works with a non-Unicode kernel, while the kernel of the Java engine is always Unicode, JSPM will apply both parts of kernel. It does not matter that the non-Unicode kernel actually belongs to the ABAP part. All that needs to be done is to put the non-Unicode kernel into the JSPM inbox. When using JSPM to update the kernel, JSPM consider all platforms (OS and Unicode vs. non-Unicode) of a heterogeneous system as a whole. Not only will it update all the kernels involved, it will also update the packages of all kernel parts available. The JSPM won't proceed with applying the updates, as long as some of the required update packages of the involved platforms are still missing. I hope you now have a good grasp of the subject around SAP system kernel update.

This content is reposted from the SAP Developer Network. Copyright 2006, SAP Developer Network SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free. Want to read more from this author? Click here to read Storm Archer III's Weblog. Click here to read more about SAP NetWeaver platform on SDN.

patch (fix)

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This RSS Reprints Enterprise Desktop Resources Programming

A patch (sometimes called a "fix") is a quick-repair job for a piece of programming. During a software product's beta test distribution or try-out period and later after the product is formally released, problems (called bug) will almost invariably be found. A patch is the immediate solution that is provided to users; it can sometimes be downloaded from the software maker's Web site. The patch is not necessarily the best solution for the problem and the product developers often find a better solution to provide when they package the product for its next release. A patch is usually developed and distributed as a replacement for or an insertion in compiled code (that is, in a binary file or object module). In larger operating systems, a special program is provided to manage and keep track of the installation of patches. Related glossary terms: Anna Kournikova virus VBS.SST, Windows Remote Desktop, desktop management, system tray, graphic equalizer, Internet Explorer Administration Kit (IEAK), remote desktop, CONFIG.SYS, Curl, authentication ticket or ticket-granting ticket (TGT)

kernel

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This RSS

Reprints Open source Web and application servers Operating systems

The kernel is the essential center of a computer operating system, the core that provides basic services for all other parts of the operating system. A synonym is nucleus. A kernel can be contrasted with a shell, the outermost part of an operating system that interacts with user commands. Kernel and shell are terms used more frequently in Unix operating systems than in IBM mainframe or Microsoft Windows systems. Typically, a kernel (or any comparable center of an operating system) includes an interrupt handler that handles all requests or completed I/O operations that compete for the kernel's services, a scheduler that determines which programs share the kernel's processing time in what order, and a supervisor that actually gives use of the computer to each process when it is scheduled. A kernel may also include a manager of the operating system's address spaces in memory or storage, sharing these among all components and other users of the kernel's services. A kernel's services are requested by other parts of the operating system or by application programs through a specified set of program interfaces sometimes known as system calls. Because the code that makes up the kernel is needed continuously, it is usually loaded into computer storage in an area that is protected so that it will not be overlaid with other less frequently used parts of the operating system. The kernel is not to be confused with the Basic Input/Output System (BIOS). Some kernels have been developed independently for use in any operating system that wants to use it. A well-known example is the Mach kernel, developed at Carnegie-Mellon University, and currently used in a version of the Linux operating system for Apple's PowerMac computers.

Related glossary terms: Linspire (Lindows) , Tux, GNOME (GNU Network Object Model Environment) , CRON script, POSIX (Portable Operating System Interface), LILO (LInux LOader) , bash (Bourne Again Shell) , Ingres, crontab, backward compatible (backward compatibility) Contributor(s): Elizabeth Holland Kern This was last updated in July 2006 Posted by: Margaret Rouse

Kernel patch upgrades on a three-tier system

Giovanni Davila

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This Reprints

We are upgrading R/3 4.6B to 4.6D on WINDOWS NT 4.0 with MS SQL 7.0. When we do a kernel and kernel patch upgrade on a three-tier system, do we do the same for the 2 application servers or should I say dialogue instances that are attached to the live PRD server? Yes. You also need to upgrade the Kernel on the application servers. Do them after upgrading the central instance. See page 283 on my new book "SAP Basis Administration

Downloading kernel executables vs. patches

Giovanni Davila

E-Mail Print A AA AAA LinkedIninShare0 Facebook Twitter Share This Reprints

When should you download all the kernel executables to have the latest R/3 kernel executables versus downloading kernel patches? We are on the 46d kernel.

You might get different answers to this question. If everything seems to be working fine you may just want to update the "tp" and "r3trans" executables only and not really the R/3 kernel. My rule of thumb is to stay behind one or two versions. I had an experience with R/3 kernel patch number 584 for 4.5b. It prevented me from changing the user master records and it also caused EDI IDocs to not be sent. SAP was not aware of this problem but fortunately they had

just released 590 so I upgraded my systems to it and everything worked again. There is nothing wrong staying behind as long as everything seems to be working well. A new kernel patch should be applied to one system first (DEV usually) for testing. Once you're satisfied with the test you can put it in the other servers. As you may know when you download the new kernel, you can execute disp+work -V and check out the corrections made. If you have anything there you need fixed then go for it.

Upgrading your SAP NetWeaver 2004s ABAP Edition

Tiest van Gool/SDN

E-Mail Print A AA AAA LinkedInin Share 0 Facebook Twitter Share This Reprints

This weblog is intended as a sequel on the infamous Blog Series of Craig Cmehil regarding the MiniWAS 620 and his travels. I recently installed the NetWeaver 2004s Sneak Preview with ABAP Stack in order to play around with WebDynpro for ABAP (WDA) and therefore had to say goodbye to my good old MiniWAS. This blog assumes you have successfully installed the WAS 700 as outlined in the installation guide. As a note on this installation I must say that the actual process is many, many times easier as its 620 counterpart. Craig, this installation looks like heaven compared to our MiniWas 620 endeavors ;-).

I also would recommend that you register your local installation as described in License Key Guide. In order to complete this process, ensure you log on to your machine as user nspadm in order to avoid any issues during registration.

As seen in the picture above this weblog will contain the steps for all you out there that would like to upgrade their NetWeaver 2004s installation from Service Pack (SP) 5 to the most recent version SP8 and/or further when available. This since every SP upgrade adds new functionalities to your local installation this enables you to gain exposure to SAP's most recent development efforts. During my previous experiences I had several more or less basic knowledge gaps regarding the actual upgrade process that I will try to fill in this blog. Also you might want to have a look at the blog Thomas Jung wrote on this subject: Apply Support Packages to the SDN ABAP-AS Sneak Preview . Step 1: Download SAP kernel patches -OPTIONALEven tough given the current SP requirements do not require a kernel upgrade; I will execute this upgrade to complete the information in this weblog. Kernel upgrades are divided into database independent and database dependent portions. The sneak preview of SAP NetWeaver 2004s ABAP edition comes packed with Kernel version 23 and at the moment of writing this blog patch level 58 is available. First step is to download the newest kernel version located at on the SAP Support Portal. Here you select the Kernel version for WAS 700 32 bit, select your operating system (Windows Server on IA32 bit) and download the database independent file as well as the database dependent file for MaxDB. Step 2: Download the latest SPAM/SAINT release Download the possible SPAM/SAINT (SAPKD700*) updates that are available. Use transaction SPAM to determine your current version (download comes with release 19). Similar as the regular support packages ensure no additional import conditions are mentioned. Step 3: Download the relevant support packages for BASIS and ABAP components Download the Basis (SAPKB700*) and ABAP (SAPKA700*) SP's that are available for WAS 700 higher then release 05 on the SAP Support Portal. Also check whether there are any additional conditions in place before applying the SP. Place the available SP's in your download basket and assume downloading. In the situation additional requirements are identified also download these components, e.g. Kernel, TP. Step 4: Unpack and installing the Kernel patch -OPTIONAL-

Locate your Kernal files and move them to a temporary directory. Unpack these files into this directory using the following command: sapcar.exe xvf ".CAR" r "". Ensure the sapcar application is not located in the since this will result in a partial unpacking process. After a successful unpacking stop the SAP NSP System and ensure all SAP related services, e.g. xserver, are stopped. Now make a back-up of your 'usr' directory just in case your need to return to the old kernel version. Execute the actual kernel upgrade by moving the content to the following directory: ':\usr\sap\\\exe\' and the non-unicode destination: ':\usr\sap\sys\exe\nuc\'. Restart your system and compare your extended status information to the picture below.

Note: SAP Note 19466 contains additional information regarding a Kernal upgrade, please consider this note before making any upgrades. Step 5: Determine available NSP disk space Before actually unpacking and importing our downloaded SP's we need to determine whether or not we have enough disk space available. In order to do so we need to install the DBGUI for Windows delivered with your sneak preview .rar archive, and located at <extract_drive>\SAPNW2004sSneakPreviewABAP\MaxDB_7.6.0_RDBMS_Installations_B uild_09__ID__MAXDB760\MAXDB_WINDOWS_I386\SETUPS. After installation of the Database Manager application establish a connection to your NSP database (superdba and password information required) and check the amount of data and log space available. I would recommend you have at least 30% (in case of 9 gigabyte MaxDB size) of database space available. If you do not have enough space available you can create another volume using this application. Step 6: Unpacking the .CAR files Manually unpacked the SP's downloaded in the previous steps using sapcar.exe. In order to do so locate your downloaded files and move them in the C:\usr\sap\trans directory. Locate the sapcar.exe application and place a copy in the same directory. Finally execute the following command in this directory: sapcar.exe xvf "KA70006.CAR" and the SP SAPKA70006 is being unpacked and placed in your EPS inbox. Repeat this step for all downloaded SP's. Step 7: Upgrade SPAM/SAINT version

Before we can apply our new SP's we have to upgrade our SPAM/SAINT version. In order to do so execute transaction SPAM and select Support Package -> Load packages -> From application server. After the import all our not imported SP's are visible to our NetWeaver Installation. Next step is to perform the actual SPAM/SAINT update by selecting Support Package ->. Upon execution of this import the actual SP is imported through the TP layer and its content is being applied to our local installation. Most possibly the import ends in a short dump, just rerun transaction SPAM and you will see your version has been upgraded successfully. If SPAM status still shows a red light simply continue by re-initiating the SPAM import as previously mentioned. Congratulations you just upgraded your SPAM/SAINT version! Note: SAP Note 822379 contains various known issues/requirements regarding the actual import process for the individual SP's. I recommened you review this note before continuation of the next step. Step 8: Upgrading your local NetWeaver 2004s installation Finally we have arrived by the actual SP imports. In order to start this import click the button 'Display/define' which shows you a pop-up window containing the components your NetWeaver application consists of. Select the SAP_BASIS component; remember these are required for a successful import of your SAP_ABA imports. Select the first package ensuring the imports are being imported one by one. Click the 'import queue' button and off you go. Similar as the previous import, a short dump can occur, also here simply re-start transaction SPAM. Congratulations again, you have completed the upgrading effort! Tiest van Gool has been working in the SAP area for 7 years+. He started is career as an ABAP developer. Using his programming knowledge he started to get more involved in customizing related activities. He is working as a solution architect for Accenture.

This content is reposted from the SAP Developer Network. Copyright 2006, SAP Developer Network SAP Developer Network (SDN) is an active online community where ABAP, Java, .NET, and other cutting-edge technologies converge to form a resource and collaboration channel for SAP developers, consultants, integrators, and business analysts. SDN hosts a technical library, expert blogs, exclusive downloads and code samples, an extensive eLearning catalog, and active, moderated discussion forums. SDN membership is free.

Want to read more from this author? Click here to read Tiest van Gool's weblog. Click here to read more about Application Servers on SDN.

More News and Tutorials

Articles o 4.6 C IDES installation procedure o ABAP jobs and more: Special report o Finding the latest SAP patches o Download and install the trial version of SAP NetWeaver 2004s ABAP o SAP ABAP for beginners
o o o o o

1. ABAP SAP NetWeaver 2004s kernel updates explained -- Part II Top 10 SAP tips of 2007 ABAP definition SAP ABAP development quiz

Related glossary terms

Terms for Whatis.com - the technology online dictionary

o

ASAP (AcceleratedSAP)

This was first published in September 2006

TSSJS Keynote speakers: Steve Harris & Adam Messinger of Oracle, James Gosling, Rod Johnson. Dont miss out register now!

Join the conversationComment Share Comments

1. There are currently no responses. Be the first to tell us what you think.
Results Contribute to the conversation All fields are required. Comments will appear at the bottom of the article.
190 23c26b2fb64b22

1. Comment: 2. Submit

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.