<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.infra-repository.org/oiar-2013/index.php?action=history&amp;feed=atom&amp;title=EL.NetWeaver_kernel</id>
	<title>EL.NetWeaver kernel - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.infra-repository.org/oiar-2013/index.php?action=history&amp;feed=atom&amp;title=EL.NetWeaver_kernel"/>
	<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar-2013/index.php?title=EL.NetWeaver_kernel&amp;action=history"/>
	<updated>2026-05-06T13:18:59Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>https://www.infra-repository.org/oiar-2013/index.php?title=EL.NetWeaver_kernel&amp;diff=421&amp;oldid=prev</id>
		<title>Jan Schoonderbeek: start</title>
		<link rel="alternate" type="text/html" href="https://www.infra-repository.org/oiar-2013/index.php?title=EL.NetWeaver_kernel&amp;diff=421&amp;oldid=prev"/>
		<updated>2012-11-11T23:22:21Z</updated>

		<summary type="html">&lt;p&gt;start&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{Maturity|3}}&lt;br /&gt;
{{Pageheaderbox4Element&lt;br /&gt;
|name=SAP NetWeaver Kernel&lt;br /&gt;
|version=0.6&lt;br /&gt;
|owner=J.A.H. Schoonderbeek&lt;br /&gt;
|elementtype=Element type software&lt;br /&gt;
}}&lt;br /&gt;
{{Description Area&lt;br /&gt;
|description=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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* 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 DB-dependent 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.&lt;br /&gt;
* Unicode vs. Non-Unicode: Depending on users&amp;#039; 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.&lt;br /&gt;
* 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. &lt;br /&gt;
Before 2004, SAP applications had their own version of the kernel. As of 2004, all SAP application use the same kernel.&lt;br /&gt;
|annotate=yes&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Elementfooter&lt;br /&gt;
}}&lt;/div&gt;</summary>
		<author><name>Jan Schoonderbeek</name></author>
	</entry>
</feed>