Getting Started with the IBM PowerLinux Solution Edition for SAP Applications

1

Industry standard Linux, solutions tuned to the task

Getting Started with the IBM PowerLinux Solution Edition for SAP Applications

April 11, 2012

Authors:

Caecilie Hampel, SAP on PowerLinux Software Engineer, [email protected]

Susan Proietti Conti, PowerLinux Offering Manager, [email protected]

2

Table of Contents Table of Contents ...............................................................................................................................................2

Introduction .........................................................................................................................................................3

Scope of This Paper ...........................................................................................................................................3

Solution Elements of the IBM PowerLinux Solution Edition for SAP Applications .............................................3

POWER Systems............................................................................................................................................3

IBM PowerLinuxTM

7R2 Server .......................................................................................................................4

IBM Flex System p24L Compute Node...........................................................................................................5

IBM PowerVM .................................................................................................................................................5

Required SAP products for the SAP landscape setup....................................................................................7 SAP ERP .....................................................................................................................................................................7 SAP Solution Manager.................................................................................................................................................7

Getting Started....................................................................................................................................................7

IBM PowerLinux 7R2 Set Up ..........................................................................................................................7

Configuration Requirements for your hardware..............................................................................................9

Performance..................................................................................................................................................10

SAP landscape setup....................................................................................................................................10

DB2® UDB....................................................................................................................................................10 Migrating to DB2 ........................................................................................................................................................11

IBM Systems Storage ...................................................................................................................................11

Conclusion ........................................................................................................................................................12

Related Content................................................................................................................................................13

IBM Documentation.......................................................................................................................................13

SAP Documentation......................................................................................................................................13

Copyright ..........................................................................................................................................................15

3

Introduction

An Enterprise Resource Planning (ERP) system is the core business application for every company, covering a multitude of different business functions. This applies to both landscapes for large enterprise companies as well as for midsize companies with constrained IT resources.

For midsize companies in particular, finding a platform that offers good performance, reliability and maintainability while still offering the right price performance ratio can be a challenge.

To specifically address midsize business enterprise resource planning needs, IBM® offers a robust and affordable platform alternative based on Linux® and IBM POWER7® technology. IBM’s new IBM PowerLinux™ hardware line perfectly fits the needs of a small and integrated ERP setup.

Linux, the industry’s fastest growing server operating system, offers a flexible, easy to maintain and cost-optimized environment that is readily used by midsize companies. Coupled with IBM’s new Linux-optimized hardware, Linux and IBM PowerLinux servers provide an excellent price performance ratio compared to traditional Linux servers.

SAP has supported IBM Power systems running Linux since 2004. IBM Power has proven its reliability and performance leadership with SAP workloads repeatedly since then. Deploying SAP applications on the new IBM PowerLinux hardware offers midsize customers the advantages of an SAP ERP system with the openness of Linux on an enterprise proven hardware platform.

The IBM PowerLinuxTM

Solution Edition for SAP Applications enables midsize customers to run multiple SAP landscapes and their database on a single server, thus reducing floor space and other IT costs. The solution offers a robust virtualization solution by leveraging IBM’s advanced virtualization capabilities in PowerVM® technology. IBM has released a new PowerVM edition, PowerVM for IBM PowerLinux that is offered exclusively for IBM PowerLinux servers. The IBM PowerLinux edition provides enterprise level functionality with a new pricing structure, comparable to x86 virtualization solutions.

The net result is a highly robust, secure and pre-integrated solution that enables midsize businesses to deliver SAP applications faster, with higher quality and more affordably.

Scope of This Paper

This paper describes a set up and configuration example for an SAP ERP landscape on a single IBM PowerLinux server. Its primary focus is on the hardware set up requirements and configuration.

The scope is to provide a blueprint for a small, easy to maintain ERP landscape and to give an overview of the implementation process from bare metal set up to configuring the SAP system landscape.

The architecture in this paper consists of an IBM PowerLinux server with PowerVM virtualization and management tools, and the additional use of a storage extension using Storage Area Network (SAN) storage. On top of this virtualized environment, Linux and SAP products, SAP Solution Manager and SAP ERP with an IBM DB2® database are installed and configured.

Solution Elements of the IBM PowerLinux Solution Edition for SAP Applications

The IBM PowerLinux Solution Edition for SAP Applications is a comprehensive solution comprised of IBM Power Systems hardware, IBM PowerVM virtualization, the Linux operating system, SAP Solution Manager and SAP ERP with IBM DB2. The following section describes the required elements of the solution.

POWER Systems

For the past 10 years, through sustained investment in the Power Systems platform, IBM has gone head-to-head with competitors in the UNIX market segment, and has become the leader of the UNIX market

4

segment1. Power systems have supported Linux since 2002, and have developed strategic partnerships with

Red Hat and SUSE to optimize, distribute, and support their Linux enterprise server releases on Power systems.

SAP software has been available on PowerLinux servers since 2004, being the first virtualized Linux platform to run SAP workloads. Starting with Power4+ and up to the current Power7 generation, PowerLinux has proven its reliability and performance running SAP workloads over several years and hardware generations.

SAP solutions on IBM PowerLinux servers offer businesses the flexibility and economics of Linux on an enterprise proven hardware platform.

IBM PowerLinux 7R2 Server

The SAP on PowerLinux solution edition is based on IBM PowerLinux 7R2 hardware. The IBM PowerLinux

7R2 server is a 2U rack-mount server with two processor sockets. The processors are 64-bit POWER7 chips with 8-core modules. There are two processor frequencies available:

IBM PowerLinux 7R2 Rack Sever, Machine Type Model: 8246-L2C, or 8246-L2S for external drawer support Feature Code Sockets Processor Frequency Cores

EPL4 2 socket 3.3 GHz 16 cores

EPL5 2 socket 3.55 GHz 16 cores

The PowerLinux 7R2 server provides a maximum of 16 DDR3 DIMM slots and is available with a maximum of 256GB RDIMM DDR3 memory.

Both Linux distributions Red Hat Enterprise Linux and SUSE Linux Enterprise Server are supported, on the 7R2. The supported distribution versions are RHEL 5 and 6 as well as SUSE Linux Enterprise Server 10 and 11.

Several configuration options with disks or tape drive are possible. The maximum internal storage without RAID is 6 x 600 GB. Additional external storage and a Fibre Channel Adapter to connect to it can be added to the machine. Four PCI Express adapter slots can be equipped with required adapters.

The IBM PowerLinux 7R2 system is a small up to medium size server that is the ideal platform for an SAP solution for 250 with up to 1000 SAP users depending on the used memory from 64 GB to 256 GB and also the landscape setup. It combines the advantages of the Power platform with those of Linux as open operating system, and offers an excellent price performance ratio. The whole SAP landscape can run on one server, nevertheless if the landscape is growing, scale out to additional servers is possible.

5

IBM Flex System p24L

IBM PureFlex System is an expert integrated system that can support a hybrid environment of both POWER and x86 compute nodes to leverage the advantages of both hardware architectures within the same environment. Different compute nodes can be installed and managed in one IBM Flex System chassis along with integrated Storage, Flex System Manager and Networking.

IBM PureFlex systems can be built with your choice of two socket or four socket compute nodes:

• Two and four socket Power Systems compute nodes for AIX, IBM i and Linux applications (Flex System p260 and p460)

• Two socket PowerLinux compute node for Linux only applications (Flex System p24L)

• Two socket x86 compute node for Windows or Linux applications (Flex System x240)

The IBM Flex System V7000 Storage Enclosure is available inside or outside of the chassis. The Flex System Manager is an integrated management appliance that manages all of the physical and virtual resources within the Flex System chassis.

IBM Flex System p24L compute nodes are Linux only, half-wide, two socket POWER servers with 64-bit Power7 processor cores in three speeds. IBM Flex System p24L compute nodes have a maximum of 16 DDR3 DIMMs with up to 256GB memory.

IBM Flex System p24L compute nodes, Machine Type Model: 1457-7FL

Feature Code Sockets Processor Frequency Cores

EPR7 2 socket 3.7 GHz 12 cores



Both Linux distributions Red Hat Enterprise Linux and SUSE Linux Enterprise Server are supported, on the IBM PowerLinux compute nodes. The supported distribution versions are RHEL 5 and 6 as well as SUSE Linux Enterprise Server 11.

Companies that already use the IBM Flex System can expand its use by adding an IBM Flex System p24L Compute Node to run their ERP landscape in the IBM Flex system.

In this paper the set up and configuration example refers to either an IBM PowerLinux 7R2 rack server or an IBM Flex System p24L Compute Node.

IBM PowerVM

PowerVM, the virtualization technology of Power, is an intrinsic part of the IBM Power platform. It comprises several virtualization features that improve management, utilization and administration of the Power landscape and therefore significantly reduces the total cost of ownership.

6

PowerVM is also a proven technology with Linux, and has demonstrated its virtualized efficiency for years, long before other Linux virtualization technologies appeared. In SAP environments, PowerLinux was the first virtualized Linux platform, exploiting advanced virtualization features from the onset.

The PowerLinux 7R2 server comes with the PowerVM for IBM PowerLinux edition. It offers customers a comprehensive set of advanced PowerVM virtualization features, e.g. Multiple Shared Processor Pools; virtualized disk and optical devices (VIOS); Integrated Virtualization Manager (IVM); Shared Dedicated Capacity; Live Partition Mobility (LPM) and Active Memory Sharing (AMS).

Particularly important for SAP environments are the following virtualization features:

A vital application for the management and monitoring of Power hardware is the Integrated Virtualization Manager. It offers functionalities like creating or deleting logical partitions, adding or removing resources, and the ability to log on to the partitions via console. The Integrated Virtualization Manager is located on the Virtual I/O Server (VIOS), which provides virtual I/O resources to the logical partitions. A logical partition, or LPAR, is the equivalent term for a Virtual Machine (VM) used with x86-based virtualization. Only the VIOS owns dedicated physical I/O adapters while client partitions use virtual e.g. Ethernet or storage adapters. Using a virtual I/O server increases flexibility and leads to resource reductions, and therefore cost savings.

A major virtualization feature of PowerVM is micropartitioning which enables up to 10 partitions per processor sharing CPU cycles. This enables the 16 core 7R2 server or compute node to host as many as 160 Logical Partitions (LPARs). Dedicated CPU resources are never completely used, and free cycles are lost. By sharing the processor capacity across several partitions enables greater workload consolidation and better hardware utilization.

A slightly different approach is to reserve CPU for a partition but donate free cycles to the shared CPU pool which can then be used by other LPARS. In this manner the partition with dedicated resources can use all its dedicated resources without interrupts from other partitions. It all the dedicated resource is not required however, it can be shared with other LPARs. This configuration is called “shared dedicated capacity”.

For partitions using shared processor resources there is a priority assignment option to make sure a specific LPAR gets enough resources. According to the priority of the partition it will be assigned the appropriate amount of CPU cycles. This ensures a better balance of resources while still ensuring high priority partitions receive the required resources. The resource distribution for the sharing partitions is done by the Hypervisor. In the case of the SAP architecture solution, the SAP production system should be assigned a higher priority than SAP development system.

PowerVM Live Partition Mobility (LPM) allows relocation of LPARS between two Power servers without downtime. Running SAP systems on an LPAR do not have to be stopped as LPM supports the concurrent use SAP applications while the LPAR is being relocated. This means that the server does not have to brought down for system maintenance or other types of planned SW and HW outages. This feature has been supported for multiple Power processor generations and is one of Power’s key availability and cost reduction features. The ability to run workloads without interruption provides continued service for businesses.

For more information on PowerVM and SAP refer to the following resources:

• IBM Datasheet for the Virtual I/O Server

http://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/datasheet.html

• IBM Whitepaper “Live Migration of Power Partitions Running SAP Applications”

http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101471

• IBM Redbook "SAP Applications on IBM PowerVM"

http://www.redbooks.ibm.com/abstracts/sg247564.html

7

Required SAP products for the SAP landscape setup

SAP ERP

SAP Enterprise Resource Planning (ERP) is the core product of SAP AG. It is one of the most popular Enterprise Resource Planning tools and reflects the major business processes of a company, such as Financial Accounting, Controlling, Logistics, Sales and Distribution etc.

SAP ERP is the successor of SAP R/2 and R/3 and is based on the SAP NetWeaver platform, which provides SAP ERP with a comprehensive technology stack.

The ERP system is customized according to the needs of the customer and its business processes. The application can be extended with custom source code or other custom functionalities can be added. Not all modules of the systems must be configured and used; only the parts that will be customized.

SAP Solution Manager

Combining several supporting funtionalities in one tool, the SAP Solution Manager is an essential part of every SAP landscape. SAP requires its installation before other products can be added to the landscape.

Key application areas of the SAP Solution Manager are for example change management support, solution monitoring, implementation and upgrades of SAP products, service-level management and reporting.

It functions as SAPs entry point to the local landscape with early watch landscape monitoring, update notifications and support portal.

Getting Started

IBM PowerLinux 7R2 Set Up

The example configuration described in this paper is comprised of four workloads or LPARs. One of the LPARs will host the Virtual I/O Server (VIOS) with the Integrated Virtualization Manager (IVM) and the other three LPARs will host the SAP installations that form together the SAP landscape.

LPAR1

The first LPAR is reserved for the VIOS with the integrated IVM. It does not need a lot of resources but should be given the highest priority for resource sharing. Without the VIOS running, the attached LPARs will be out of control as their virtual adapters will not be configured. Therefore it is important to set up the VIOS configuration in order for the other paritions to run properly. In this configuration the VIOS shares ethernet and storage adapters with the attached LPARs. Every LPAR owns a virtual ethernet and storage adapter.

LPAR2

The second LPAR hosts the installation of the SAP Solution Manager which is a pre-requisite for all the other SAP product installations in the landscape and needs to be installed first. The SAP Solution Manager is based on a SAP dual stack and should therefore be equipped with sufficient memory resources, although it will not host of a lot of users and therefore does not need a high priority in cpu shares.

LPAR3

The SAP ERP development system is located on the third LPAR. SinceI it is a development system and used only for development and test purposes, the required resources are moderate, but need to fulfill a minumum for the ERP system to work. The priority of the resources could be lower compared to those of the production ERP system, which is located on the fourth LPAR on the PowerLinux 7R2 machine.

LPAR4

The production SAP ERP system is the core component of the SAP landscape and will have the highest user frequency. Therefore, it should get the most CPU and memory resources, and with higher CPU sharing

8

priority. If the partition should not in general share resources with the other LPARS, another possibility would be to set it up with shared dedicated capacity. It then only shares unused resources if they are not required.

The LPAR for the production system is the partition with the most assigned system resources and also has the highest resource priority after the partition running the VIOS. This ensures ongoing availability of the production system.

The following values are a sample configuration with 64 GB of memory. Please note that a separate sizing must be done for every landscape, that this sample configuration should not be used as blueprint.

Sample Memory Allocation by LPAR

LPAR1: VIOS 6 GB

LPAR2: SAP Solution Manager 14 GB

LPAR3: SAP ERP Development 10 GB

LPAR4: SAP ERP Production System 30 GB

Sample CPU Allocation by LPAR

For this small installation the LPARs can be part of one cpu pool and share their resources. A sample resource entitlement could be:

LPAR1: VIOS 0.2 (priority 255)

LPAR2: SAP Solution Manager 0.4. (priority 64)

LPAR3: SAP ERP Development 0.4. (priority 64)

LPAR4: SAP ERP Production System 2 (priority 128)

Additionally every LPAR gets two virtual adapters from the VIOS:

9

• ethernet adapter

• storage adapter

Disk space must be defined according to the required data in the system. A minimum requirement to install an SAP ERP system is at about 300 GB, but this does not provide sufficient storage for a lot of business data.

LPAR resource assignment for memory, CPU and adapters is done via the IVM where new LPARs are added. The IVM view shows the four LPARs with their memory and processors. In this case the LPARs are all in CPU sharing mode and are part of one CPU pool. The IVM can also be used to monitor the LPARs running during production.

For more detailed information on IVM with IBM PowerLinux 7R2 servers, consult the Architecture and Sizing Guide for IBM PowerLinux and the Implementation and Tuning Guide for IBM PowerLinux in the PowerLinux Community on DeveloperWorks.

• PowerLinux Community

https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32

Configuration Requirements for your hardware

The amount of the CPU and memory resources, as well as disk space described above is only an example for the architecture. Every SAP landscape has different requirements, thus the sizing for the landscape will vary significantly based on factors like the number SAP users, peak workload requirements, etc.

An important pre-requisite for any server’s successful deployment is planning its workload capacity, physical and virtual resource, and implementation steps. Take time to size the SAP landscape planned for the server. Sizing should also take into consideration if attached hardware will be needed to provide sufficient storage. Proper sizing will prevent running out of capacity, or conversely,wasting resources that will not be used. Be sure to consult resource guidelines in SAP documentation based on performance results from SAP benchmarks. The following site can provide useful information:

• IBM Sizing and Planning Questionnaire for SAP Solutions

http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/PRS261

10

You should also contact your IBM representative or SAP business partner to help plan and size SAP landscapes on Power Systems. IBM can provide assistance with the planning and deployment of your PowerLinux server, setting up your SAP landscape, and migrating data. For IBM Lab Services Assistance find contact information at: http://www.ibm.com/systems/services/labservices/

Performance

SAP Sales and Distribution (SD) Benchmarks prove the performance of Power Systems in combination with SAP workloads. SAP SD Benchmarks are a common vehicle to show the performance of a platform. The performance of a benchmark run is measured in the unit called SAPS that indicate the capacity of a server.

The performance measurements are then the basis for capacity sizings of production SAP systems and their hardware planning.

IBM PowerLinux benchmark runs with both 12 and 16 core hardware demonstrated market leading performance of Linux running on Power hardware.

For more information and current benchmark runs please visit the SAP SD Benchmark site.

• SAP SD Benchmark information

http://www.sap.com/solutions/benchmark/sd2tier.epx

SAP landscape setup

The described SAP landscape is a very basic setup to cover the major business processes of a company with a SAP ERP system. Additional products may be added to the described landscape.

The setup of the SAP landscape starts with the Solution Manager. Its installation is a prerequisite to run SAP and it offers some support tools for the landscape setup. It is required for every SAP landscape regardless of the number of SAP installations attached.

The major parts in the landscape are two ERP installations. One system is used as a development and test system, and the other one is used for production. Code changes or Service Pack installations are first performed on the development system and are also tested there. After successful testing, the changes are deployed into the production environment. This process ensures that the production system remains a stable environment, and is unaffected by possible issues caused by beta/pre-production code. The ERP landscape could even be enhanced to three systems, a development system, a separate test system and the production system. As this landscape requires setting up and maintaining three SAP systems, it is only required for large or extremely sensitive environments. For small and midsize installations, a two system ERP landscape is sufficient.

Both the development and the production ERP system are configured as two-tier systems that have the database and application logic on one server. This ensures an easy to maintain infrastructure that keeps setup and administration effort low. For bigger installations it is also possible to set up the database and application logic on separate LPARS or hardware.

To learn more information about SAP landscape setup options and to read more about SAP system configurations, please view the SAP on Power Linux reference architecture paper. It describes the PowerLinux architecture for use with an SAP landscape.

• SAP on PowerLinux reference architecture

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/904b62ee-a64d-2f10-9cae-93f1fe232b03?QuickLink=index&overridelayout=true&53953379192934

DB2® UDB

To leverage database optimization with SAP and POWER7, it is recommended to use the IBM DB2 database management system with the IBM PowerLinux Solution Edition for SAP Applications. IBM offers a

11

DB2 LUW version that was developed jointly with SAP and is optimized for SAP applications and the SAP NetWeaver platform running on Linux.

DB2 is performance-optimized for SAP workloads, and offers a simplified storage layout and automatic statistics collection. With the DBCockpit, DB2 offers multiple enhanced monitoring features that are unique to the SAP system. Recent SAP SD Benchmarks with a PowerLinux environment and DB2 demonstrate the optimal combination of operating system, hardware and database.

The DB2 database setup is embedded in the SAP install routine for SAP products, offering a quick and easy installation of the database. The database is shipped and fully integrated in SAP applications as one product.

This sample architecture uses a DB2 v9.7 database for SAP installations. Other versions of DB2, however, are also supported.

For more information on SAP and DB2 please visit

• DB2 and SAP information by IBM

http://www.ibm.com/solutions/sap/db2

• Features in DB2 v9.7 for SAP

http://scn.sap.com/docs/DOC-8062

Migrating to DB2

IBM offers standardized procedures to help you migrate your database to DB2 if you are already a SAP customer and want to leverage the advantages of DB2. Migrating to DB2 is simple and ensures you numerous benefits such as easy database compression and excellent performance.

The change to new hardware is also a perfect time to switch your database, so if you are planning to move to new PowerLinux hardware consider migrating to DB2 LUW.

For more information on database migration to DB2 please visit

• Redbook “DB2 Optimization Techniques for SAP Database Migration And Unicode Conversion”


or contact your IBM representative.

IBM Systems Storage

The example configuration in this paper uses internal hard drive disks. External storage is also an option, and often preferred since ERP is a mission critical workload for midsize and large enterprise companies. Use of external disks will increase data security and reliability. It is also likely that over time growing business needs, and hence storage requirements, will eventually exceed the maximum internal disk storage of an IBM PowerLinux server. Thus the recommendation for this SAP setup is to add external storage to the landscape in order to provide extra capacity for landscape growth in the future. This storage could also be used for other applications that may run in the PowerLinux landscape.

External storage can be added as Disk Storage, Network Attached Storage (NAS) or storage in a Storage Area Network (SAN). The advantage of external storage is that it can be easily extended and can offer additional administration tools for its management.

Using external storage also brings other advantages to the landscape, e.g. the flexibility to use live partition mobility if replacing a Power server or adding more Power servers to the landscape. Live partition mobility

allows you to move easily between PowerLinux servers while the data still stays on the same disk space.

A small and very cost efficient storage box that perfectly fits with IBM PowerLinux hardware and the described sample

12

architecture is the IBM DS3500 express storage, which is available with up to 12 or 24 disks.

It includes 6 Gbps SAS systems, a built-in storage management software, Fibre Channel access and data security with full disk encryption.

For further information on supported storage solutions that work in a virtualized Power environment with a Virtual I/O Server please visit

• Datasheet for the Virtual I/O Server with storage solutions section


Conclusion

The SAP landscape described in this paper gives you a starting point to configure a compact SAP ERP landscape on PowerLinux hardware. Depending on the requirements of your business your landscape may vary from the example. Regardless, PowerLinux hardware and PowerVM technology provide an ideal platform for SAP solutions. All major SAP products are available on PowerLinux and each landscape can be created according to your business needs. This applies for both new SAP setups as well as migrations to PowerLinux.

PowerLinux offers you the flexibility to start small, and to grow your SAP landscape and other workloads that you might want to add to your PowerLinux hardware.

For additional information on IBM PowerLinux servers with SAP workloads refer to the following URLs:

• IBM PowerLinux http://www.ibm.com/power/powerlinux

• SAP Community Network: SAP on IBM Power Linux http://scn.sap.com/docs/DOC-8438

13

Related Content

IBM Documentation

• IBM Whitepaper "IBM Integrated Virtualization Manager"

http://www-03.ibm.com/systems/power/hardware/whitepapers/ivm.html

• IBM Redbook "Hardware Management Console V7 Handbook"


• IBM Redbook "IBM PowerVM Virtualization Introduction and Configuration"

http://publib-b.boulder.ibm.com/abstracts/sg247940.html

• Architecture and Sizing Guide for IBM PowerLinux

Implementation and Tuning Guide for IBM PowerLinux

• DB2 and SAP information by IBM

http://www.ibm.com/solutions/sap/db2

• Features in DB2 v9.7 for SAP

http://scn.sap.com/docs/DOC-8062

• Redbook “DB2 Optimization Techniques for SAP Database Migration And Unicode Conversion”


• IBM Sizing and Planning Questionnaire for SAP Solutions

http://www.ibm.com/support/techdocs/atsmastr.nsf/PubAllNum/PRS261

• IBM Datasheet for the Virtual I/O Server


• IBM Whitepaper “Live Migration of Power Partitions Running SAP Applications

http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101471

• IBM Redbook "SAP Applications on IBM PowerVM"


• Architecture and Sizing Guide for IBM PowerLinux and the Implementation and Tuning Guide for IBM PowerLinux

https://www.ibm.com/developerworks/mydeveloperworks/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/?lang=en

• IBM PowerLinux

http://www.ibm.com/power/powerlinux

SAP Documentation

• SAP on PowerLinux reference architecture

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/904b62ee-a64d-2f10-9cae-93f1fe232b03?QuickLink=index&overridelayout=true&53953379192934

• SAP on PowerLinux servers

http://www.sdn.sap.com/irj/sdn/linux?rid=/webcontent/uuid/b29e49ae-0e01-0010-8a93-86294c7f35e1

14

• Virtualization on SAP

http://www.sdn.sap.com/irj/sdn/virtualization

• SAP on DB2 for Linux

http://www.sdn.sap.com/irj/sdn/db6

• SAP SD Benchmark information

http://www.sap.com/solutions/benchmark/sd2tier.epx

15

Copyright

© IBM Corporation 2012 IBM Corporation Marketing Communications Systems Group Route 100 Somers, New York 10589 Produced in the United States of America April 2012 All Rights Reserved This document was developed for products and/or services offered in the United States. IBM may not offer the products, features, or services discussed in this document in other countries. The information may be subject to change without notice. Consult your local IBM business contact for information on the products, features and services available in your area. All statements regarding IBM future directions and intent are subject to change or withdrawal without notice and represent goals and objectives only. IBM, the IBM logo, ibm.com, Power, PowerVM, POWER7, DB2,IBM PowerLinux, and IBM Flex System are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml Linux is a trademark of Linus Torvalds in the United States, other countries or both. PowerLinux™ uses the registered trademark Linux® pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds, owner of the Linux® mark on a world-wide basis. SAP and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Other company, product, and service names may be trademarks or service marks of others. IBM hardware products are manufactured from new parts, or new and used parts. In some cases, the hardware product may not be new and may have been previously installed. Regardless, our warranty terms apply. Photographs show engineering and design models. Changes may be incorporated in production models. This equipment is subject to FCC rules. It will comply with the appropriate FCC rules before final delivery to the buyer. Information concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions on the capabilities of the non-IBM products should be addressed with those suppliers. All performance information was determined in a controlled environment. Actual results may vary. Performance information is provided “AS IS” and no warranties or guarantees are expressed or implied by IBM. Buyers should consult other sources of information, including system benchmarks, to evaluate the performance of a system they are considering buying. When referring to storage capacity, 1 TB equals total GB divided by 1000; accessible capacity may be less. The IBM home page on the Internet can be found at: http://www.ibm.com. The IBM Power Systems home page on the Internet can be found at: http://www.ibm.com/systems/power/

1 IBM Captures Leadership Position in Worldwide Server Market in Fourth Quarter of 2011,

http://www.ibm.com/press/us/en/pressrelease/36998.wss

POW03080-USEN-00

Getting Started with the IBM PowerLinux Solution Edition for SAP Applications

Technology

Transcript of Getting Started with the IBM PowerLinux Solution Edition for SAP Applications