SuSE Linux Enterprise Server for SAP - subscription - unlimited virtual machines

Optimized for fast and easy deployment

An installation wizard in SUSE Linux Enterprise Server for SAP Applications installs both SAP software solutions and their underlying Linux infrastructures, unattended. This process seamlessly integrates and simplifies the installation of SAP applications. You can also easily integrate third-party components that weren't part of the original SAP solution stack. The installation is quality assured and requires almost no interaction once the workflow begins.

Optimized for performance

SAP and SUSE validated and certified the SUSE Linux Enterprise Server for SAP applications jointly to eliminate potential software incompatibilities, and they continue to test and validate the software stack. This partnership tightly integrates the application workload with the operating system and eliminates the possibility of incompatibilities when patches are applied to either the applications or the operating system.

Optimized for business continuity

SUSE Linux Enterprise Server for SAP Applications includes high-availability components. These provide an integrated clustering solution for physical and virtual Linux deployments, enabling the implementation of highly available Linux clusters and eliminating single points of failure. This solution supports NFS as the standard network file system to provide file access to all nodes in the cluster. For workloads that require parallel read/write access to all nodes, SUSE offers the OCFS2 cluster file system as an option.

Support for large in-memory workloads

Page cache limit is a kernel parameter that has been introduced to SUSE Linux Enterprise Server for SAP Applications like BWA and HANA to allow SAP administrators to optimize the kernel's paging behavior. Some SAP solutions use systems with very large amounts of memory to keep business data in memory. Parts of this memory are very seldom accessed. When faced with file system load such as backup jobs, the Linux kernel decides that it's better to use memory as file system cache (page cache) to speed up the file system operations, and pages out the seldom accessed memory from the application.