Dirk Anthony, SAP AG June 2011 -...

System Landscape Recommendations for SAP

NetWeaver 7.3 – Human Centric Capabilities

Dirk Anthony, SAP AG

June 2011

© 2011 SAP AG. All rights reserved. 2

Disclaimer

This presentation outlines our general product direction and should not be relied on in

making a purchase decision. This presentation is not subject to your license agreement

or any other agreement with SAP. SAP has no obligation to pursue any course of

business outlined in this presentation or to develop or release any functionality

mentioned in this presentation. This presentation and SAP's strategy and possible future

developments are subject to change and may be changed by SAP at any time for any

reason without notice. This document is provided without a warranty of any kind, either

express or implied, including but not limited to, the implied warranties of

merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no

responsibility for errors or omissions in this document, except if such damages were

caused by SAP intentionally or grossly negligent.


Agenda

Introduction

Methodology & Scope of Landscape Recommendations

Basic Landscape Setups

Recommendations for SAP NetWeaver Portal Deployments

Enhanced Landscape Setups

Additional Aspects for SAP NetWeaver Portal Based System Landscapes

Related Building Blocks

Recommendations for Adobe Document Services and SAP NetWeaver Business

Process Management in SAP NetWeaver Portal based System Landscapes

IntroductionMethodology & Scope of Landscape Recommendations


SAP Business Suite Reference LandscapeBaseline For Governance Measures

Architectural

Guidelines

Ease

Landscape

Management

Improve

Product

Capabilities

Landscape

Standards

Ease

Landscape

Planning

Manage

Exceptions

SAP„s internal

Development &

Test Landscape

SAP System Landscape Governance Board:

Central unit within SAP to trigger and monitor concrete landscape

related improvements across SAP products

SLD

Dual Stack

SAP

Solution Manager

ABAP

JEE

Solution Mng

Component

AS ABAP

ECC

Server

SAP ERP

ABAP

ERP

Components

AS ABAP

SRM

Server

SAP SRM

ABAP

SRM

Components

AS ABAP

SCM

Server

SAP SCM

ABAP

SCM

Components

AS ABAP

CRM

Server

SAP CRM

ABAP

CRM

Components

BW

AS ABAP

Business Warehouse

SEM

Central BI

Content

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

PI

PI Dual Stack

Process Integration

ABAP

JEE

ESR&SR

ESR Content

SLD

SolMan Content

SAP NetWeaver Hubs

SAP Business Suite

Backend Systems

EP Core

AS JAVA

Application Portal

JEE

Additional SAP BS Instance

Portal

Content

ADOBE


Technical Deployment of SAP NetWeaverFoundation Capabilities

Definition for Dual Stack:

SAP system containing Application Server ABAP and Application Server Java

A dual-stack system has the following characteristics:

• Common SID for all application servers and the database

• Common startup framework

• Common database (with different schemas for ABAP and Java)

Options for implementing the technology foundation of SAP NetWeaver

• ABAP single stack system

• JAVA single stack system

• Dual stack system (not recommended any longer, where not technically required)

Legend

SAP system with

own database

used platform

technology

Rolemain role of this

system

ABAP

Examples:

BW incl. BEx Web

ABAP

BWABAP JEE

BI JAVAJEE

Optional Dual stack

(technically not req.)

ABAP

single stack

ECC

Server

SAP ERP

Backend

ABAP

JAVA

single stack

EP Core

Application

Portal

JEE

Mandatory

Dual stack

(technically req.)

PI

Process

Integration

ABAP

JEE


Technical Deployment of SAP NetWeaverIntegration Capabilities

Examples:

Options for implementing integration capabilities of SAP NetWeaver

• Embedded deployment within an SAP Business Suite system

• Deployed as a local “sidecar” system to an SAP Business Suite system

• Deployed as a central hub system shared by different SAP Business Suite systems

SAP NetWeaver Portal deployed as a

central hub shared by an

SAP ERP and an SAP SRM system

* only to support

existing setups

SAP ERP

ABAP

ECCABAP JEE

EP CoreJEE

XSSHCM

SAP NetWeaver Portal

technically deployed within

the SAP ERP system*

SAP NetWeaver Portal deployed as a

local sidecar to an SAP ERP system

EP Core

ERP Portal

JEE

XSS

ECC

SAP ERP

Backend

ABAP

HCMSRM

SAP SRM

Backend

ABAP

ECC

SAP ERP

Backend

ABAP

EP Core

JEE

XSS

SRM

Content

Application

Portal


Deployment Of SAP Products Within A Solution LandscapeArchitectural Decisions

Centrally Shared

• Reuse of platform capabilities within a central system

Local Redundant Use

• Individual usage by multiple local systems

Jointly Deployed

• Less landscape complexity by using different capabilities in the same system

Separately Deployed

• Higher flexibility by separating systems

Integrated Technology

Stacks

• Combined usage of duties by multi stack system

Separated Technology Stacks

• Separation of duties by separated technology stacks

Distribution of deployable product components

Deploy product

components


Ease Landscape Setups By Stronger Guidance Used Methodology

Option IOption II

Option

III

Clear recommendations by categorization of deployment options

General Recommendation

Best choice for majority of typical

landscape use cases

Recommended by SAP’s strategy

Accepted by a wide base of

customersReasonable Alternative

Useful choice for certain use

cases or customer scenarios

Supported and confirmed by

SAP’s strategy

Possible Exception

Only useful for specific use cases

Supported by SAP, but limitations

might occur

Outlining main important aspects

Optimal trade-off between flexibility and simplicity

Applied to main building blocks of SAP products

Alternative deployment options might have different benefits

Customer individual assessment not be compensated

Goal

Consider


Scope of Landscape RecommendationsBuilding Blocks in System Landscapes for Human Centric Capabilities

Considered main building blocks SAP NetWeaver Enterprise Portal (EP)

SAP NetWeaver Enterprise Portal Core (EP Core)

Adobe Document Services (ADOBE), Business Process Management (BPM)

Java-based SAP Business Suite User Interfaces

Considered main usage scenarios Application Portal for SAP Business Suite

Corporate Intranet Portal in landscapes

Adobe Document Services for PDF-based printing

BPM for human centric integration

JEE

SAP system with

own database

available platform

technology

Rolemain role of this

system mandatory

component

optional

component

EP Core

Application Server JAVA

Application Portal

JEE

Portal

Content

Portal based

SAP Instance

Java-based

SAP Instance

Additional

SAP NetWeaver

instance

Enterprise

Portal


Corporate Intranet Portal

JEE

Portal Content

Additional

SAP NetWeaver

instanceEP Core

Java-based

SAP Instance

Portal Add-On

Basic Landscape SetupsRecommendations for SAP NetWeaver Portal Deployments


Basic Landscape SetupsTypical characteristics of usage as an Application Portal

Central, role-based, personalized and unified access

Mainly business application user

Dedicated portal content by the SAP Business Suite

Consolidation layer for Java-based UIs of SAP applications

Based on SAP NetWeaver Enterprise Portal Core

Improved version interoperability starting with SAP Business

Suite 7 and SAP NetWeaver 7.0

Increased simplicity for initial implementations with SAP

NetWeaver 7.3

EP Core


XSS

Application Portal

JEE

Business

Packages

Adobe Doc.

Services

Biller Direct

ALV-EXPORT

Example:

Application Portal with

additional

Java-based instances


Deployment of SAP NetWeaver PortalApplication Portal


Single SAP NetWeaver Portal for central user access and shared runtime

for SAP Business Suite JAVA UIs

Deployed as central & separate system

Avoid embedded deployment within the application backend system

Benefits Centrally governed and administrated user

access

Shared usage to simplify landscape setup and reduce TCO

Support independent innovation speeds

Considerations Version interoperability to connected application

backend systems to be checked

Applications/UIs running in the portal might impact stability & performance downtime for patching

Example

EP Core

AS JAVA

Application Portal

JEE

Biller Direct

XSS

ERP, SRM, BW

Business Pack.

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Content and Java-

based UIs of SAP

Business Suite

backend systems

deployed on central

SAP NetWeaver Portal



Benefits Central access and role-based navigation

Autonomous local UIs/applications

Local changes do not impact central application portal

Considerations

Workaround for Java-UIs/applications closely coupled to backend systems

More complex landscape setup

Higher TCO

Higher integration effort

Reasonable Alternative

Shared SAP NetWeaver Portal for central user access

Additional local sidecar systems as runtime for SAP Business Suite Java-UIs,

remotely integrated with central portal


* details regarding content sharing see slide „Additional Information“

Example

EP Core

AS JAVA

Application Portal

JEE

Business

Packages

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

AS JAVA

Local SRM

JAVA System

JEE

LAC

ECC

Server

SAP ERP

Backend

ABAP

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local BP

Content sharing with

Application Portal*


Possible Exception

Portal capabilities within BEx Web system configured

Provide a role-based user access to single application backend system

Avoid deployment of further portal applications on the portal system


Benefits Reuse of portal infrastructure for BW reporting and application

portal scenarios

Simplified landscape setup

Centrally administrated user access

Considerations BEx Web system as corporate intranet portal not supported

No automated separation of BI JAVA for later scale-out

Innovation speed of portal and BEx Web capabilities to be synchronized

BW web reporting impacts performance of portal usage

Interoperability to connected applic. systems to be checked

Example

SAP ERP

Backend

ECC

Server

BW

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

Portal content of SAP ERP

backend system deployed

within BEx Web system

ERP Bus. Pack.



Benefits Central access to content via consumer portal

Autonomous sub-portals for different business units

Independent content administration

Considerations Complex landscape setup

Configuration effort to setup FPN scenario

Higher administration & maintenance effort for additional producer portal

Same user basis required within consumer and producer portal

Only content administration can be distributed

Restrictions as defined in SAP note 880482

Possible Exception

Federated Portal Network (FPN) with a consumer portal for central end user

access to application systems of different business units

Local producer portal for independent content administration

* details regarding content sharing see slide „Additional Information“

EP-Core

AS JAVA

Producer Portal

JEE

Business

Packages

EP Core

AS JAVA

Producer Portal

JEE

Business

Packages

EP-Core

AS JAVA

Producer Portal

JEE

Business

Packages

EP Core

AS JAVA

Producer Portal

JEE

Business

Packages

EP Core

AS JAVA

Consumer Portal

JEE

Business

Packages

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

Federation between

multiple

autonomous

application portal*

Example


Basic Landscape SetupsTypical characteristics of usage as an Corporate Intranet Portal

Enterprise-wide integrated access to SAP and NON-SAP

applications, connecting heterogeneous information

sources, and enabling a central collaboration platform

Leveraging comprehensive portal capabilities

Mainly all employees or enterprise end-users

Typically not a consolidation runtime layer for Java-based

SAP application UIs

Typically based on SAP NetWeaver Enterprise Portal (EP)

extended by further capabilities or consumption of 3rd

party content

Intensive usage of enhanced portal functionality (e.g.

Wikis, Forums) and improved 3rd party interoperability

Example:

Corporate Intranet Portal with

additional Portal Add-Ons

Enterprise

Portal



JEE

Business

Packages

IDM UIsEP Core

Forums

Wikis


SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

Content sharing with

Corporate Intranet

Portal*

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local BP

AS JAVA

Local SRM

JAVA System

LAC

JEE

EP

AS JAVAJEE

Business

Packages

EWS

Forums

Wikis

Corporate Intranet

Portal

Deployment of SAP NetWeaver PortalCorporate Intranet Portal

Benefits Centrally governed and administrated

Single point of access to all corporate assets

Autonomous local UIs/applications

Higher scalability

Less effort to keep the Intranet portal stable

Considerations More complex landscape setup

Additional administration effort

Higher integration effort


Enterprise-wide intranet portal for central access to all applications

Deployed as separate system and central collaboration platform

Additional local systems as runtime for SAP Business Suite Java-UIs,

remotely integrated into central corporate intranet portal

* details regarding

content sharing see

slide „Additional

Information“

Example



Shared corporate portal for central access to all applications

Connecting heterogeneous information sources, enabling collaboration

In addition shared runtime for Java-UIs

Deployment of SAP NetWeaver PortalCorporate Intranet Portal

Benefits Centrally governed and administrated

Less complex landscape setup

Considerations Interoperability to connected application systems

to be checked, violations will impact the Corporate Portal

All Applications and UIs in Corporate Intranet Portal to be detailed analyzed for impact on stability & performance downtime for patching availability

Sizing more complex

Innovation cycles of all appl. within corporate intranet portal to be aligned

Example

EP

AS JAVA


JEE

EWS

Wikis

Business

Packages

Biller Direct

XSS

IDM UIs

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Server

NON SAP

Information Source

Content and Java-

based UIs of SAP

Business Suite

backend systems

deployed on Corporate

Intranet Portal

Enhanced Landscape SetupsAdditional Aspects for SAP NetWeaver Portal Based System Landscapes


Enhanced Landscape SetupsSupport Additional Portal Landscape Needs

• special needs regarding usability, network connections and security

• application layer adapted in addition to network infrastructure

Separation of internal and

external usage

• Locations distributed across the globe

• Connections with low bandwidth or high latency

Global systems across different

locations

• Integration based on industry standards and open interfaces

Interoperability with NON-SAP portal

SAP product capabilities serving those needs

External Facing Portal

Accelerated Application Delivery

Interoperability with 3rd party Portals



Landscape Option for External User

Implementing External Facing Portal

Emphasizes general recommendation of central portal approach

Re-use existing central portal for external users like vendors or suppliers

Web infrastruc. setup should balance security requirem., performance and hardware costs

Benefits Existing portal landscape re-used

Consider needs of internal and external users

Access performs well over Internet

Portal operates similar to standard, customizable web sites

Considerations Company security requirements may drive

separate external portal architecture

Not every scenario supported, check SAP note 853509 for known restrictions

Example

EP

SAP NetWeaver

Portal

JEE

ECC

Server

SAP ERP

Backend

ABAP

CRM

Server

SAP CRM

Backend

ABAP

Server

NON SAP

Information Source

EXTERNAL

USER

INTERNAL

USER

Firewall


capabilities used for

connecting external users


Accelerated Application Delivery (AccAD)SAP Product for Global Networks

AccAD infrastructure especially within

SAP NetWeaver Portal Scenario

Maximizes knowledge about applic. format to optimize network traffic

Reducing TCO: Reusing existing central portal system

for connecting globally distributed locations

Use smaller infrastructure components to avoid additional portal systems

Increased performance for accessing central portal across Wide Area Networks

Additional Information http://www.sdn.sap.com/irj/sdn/nw-

accad

http://www.sdn.sap.com/irj/sdn/nw-accad




Accelerated Application DeliveryLandscape Option for Global Networks

Setup of AccAD infrastructure

Emphasizes general recommendation of central portal approach

Re-use existing central portal for connecting globally distributed locations

Smaller infrastructure components to increase network performance

Benefits Connect remote users efficiently via WAN

connections

Existing portal landscape re-used without setting up additional portal systems

Increased performance across network connections with high latency or low bandwith

Considerations Additional hardware engines implemented

near data centers and remote offices

Check PAM for supported hardware and OS requirements

EP

SAP NetWeaver

Portal

JEE

ECC

Server

SAP ERP

Backend

ABAP

CRM

Server

SAP CRM

Backend

ABAP

Server

Front-End

AccAD Engine

Repository

AccAD

Engine

Client

Front-End

USER

USER

...

exchange compressed

content over WAN

Global Data

Center

Remote Office

Location

Example


Interoperability with 3rd Party Portals (1/2)Landscape Option for NON-SAP Portal

Integr. complement. 3rd party content into SAP NetWeaver Portal

SAP NetWeaver Portal serves as central Corporate Intranet Portal

Complementary 3rd party content and services integrated via open standards and APIs

Benefits Single point of access to all corporate assets

Open platform for 3rd party content integration

SAP NetWeaver Portal smoothly enhanced with existing NON-SAP content & capabilities

Considerations Custom coding or 3rd party integration

packages may need to be implemented

Look&Feel of different portals to be aligned

Example

SRM

Server

SAP SRM

Backend

ECC

Server

SAP ERP

Backend

ABAP

AS JAVA

Local SRM

JAVA System

LAC

AS JAVA

Local

HR Portal

JEE

XSS

EP Core

Local BP

Server

NON SAP

Information Source

NON SAP

Portal

3rd Party Content

Integrating

3rd party content

into SAP NetWeaver

Portal

ABAP

JEE

EP

AS JAVAJEE

Business

Packages

EWS

Forums

Wikis

Corporate Intranet

Portal


Interoperability with 3rd Party Portals (2/2)Landscape Option for NON-SAP Portal

Integrating SAP NetWeaver Portal into 3rd party portal

SAP NetWeaver Portal serves as central application portal for SAP applications

SAP applications integrated into 3rd party portal via interoperability capabilities of SAP

NetWeaver Portal

Benefits Re-use of existing non-SAP portal infrastructure

Smoother integration of SAP applications via SAP Portal into 3rd party portal(e.g. SSO, session management)

Considerations Additional SAP Portal required

Not all SAP portal functionality available to end user

Look&Feel of different portals to be aligned

Example

EP Core

AS JAVA

Application Portal

JEE

Biller Direct

XSS

ERP, SRM, BW

Business Pack.

SRM

Server

SAP SRM

Backend

ABAP

3rd Party

Portal

Company Portal

Server

NON SAP

Information Source

SAP NetWeaver Portal produces

content for central

NON-SAP Company Portal

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

Related Building BlocksRecommendations for Adobe Document Services and SAP NetWeaver Business

Process Management in SAP NetWeaver Portal based System Landscapes


Deployment of Adobe Document Services


Shared usage of Adobe Document Services (ADS) as central service

Deployed together with SAP NetWeaver Portal

Avoid embedded deployment within application backend system

Benefits Simple landscape setup

Shared usage of ADS

Reduced administration effort

Lean deployment when using interactive forms in portal based scenarios


to be checked

Innovation cycle for ADS and SAP NetWeaverPortal to be synchronized

Restricted platform availability for ADS

Example

EP Core

AS JAVA

Application Portal

JEE

Biller Direct

XSS

ERP, SRM, BW

Business Pack. ADOBE

BI JAVA

BEx Web

JEE

BW

Data Warehouse

System

ABAP

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

ADOBE provides central

PDF printing services for

backends




Shared usage of Adobe Document Services as central service

Deployed together with SAP NetWeaver BEx Web

Avoid embedded deployment within application backend system

Benefits Simple landscape setup

Shared usage of ADS

Re-use of BEx Web infrastructure, if application portal is not available in the landscape

Lean deployment when using interactive forms in BW reporting driven scenarios


to be checked

Innovation cycle for ADS and BExWeb to be synchronized

Restricted platform availability for ADS

Example

SRM

Server

SAP SRM

Backend

ABAP

BI JAVA

BEx Web

JEE

ADOBE

AS JAVA

BW

Data Warehouse

System

ABAPAS ABAP

ECC

Server

SAP ERP

Backend

ABAP



backends




Shared usage of Adobe Document Services as a central service

Deployed as a single separate system for high volume printing


Benefits Shared usage of ADS

High volume printing supported

ADS can have a faster innovation cycle without impact on other applications

ADS load does not impact other applications

Considerations Limited platform availability of ADS mitigated

by individual system

More complex system landscape

Higher administration effort

Example

ECC

Server

SAP ERP

Backend

ABAP

SRM

Server

SAP SRM

Backend

ABAP

CRM

Server

SAP CRM

Backend

ABAP

ADOBE

ADOBE Printing

AS JAVAJEE



backends


EP Core

AS JAVA

Application Portal

JEE

Biller Direct

XSS

ERP, SRM, BW

Business Pack. BPM

Composite Apps.

Composite Apps.

ECC

Server

SAP ERP

Backend

ABAP

SCM

Server

SAP SCM

Backend

ABAP

Application

Backend

NON SAP

Application

remote connection to

central ESR within

SAP NetWeaver PI

PI

PI Dual Stack

Process Integration

ABAP

JEE

ESR&SR

ESR Content

Deployment of Business Process ManagementHuman Centric Integration Scenarios

General Recommendation (Setup 1)

Central BPM deployed with central application portal for human centric

integration scenarios

ESR&SR used as part of SAP NetWeaver PI, remotely accessed by BPM

Benefits Reduced landscape complexity

Joint usage of central Universal Worklist

Less administration effort

No redundant deployment of portal capabilities

Considerations New ESR version requires update of PI system

Innovation speed of BPM and Portal to be synchronized

Sizing considers both BPM and Portal usage

Impact of licensing models to be considered

Portal and BPM at least at SAP NetWeaver 7.3

Example


Deployment of Business Process ManagementHuman Centric Integration Scenarios

General Recommendation (Setup 2)

Central BPM deployed with central application portal for human centric

integration scenarios

ESR deployed together with BPM and Portal, if SAP NetWeaver PI not in use

Benefits Reduced landscape complexity

Joint usage of central Universal Worklist

Less administration effort

No redundant deployment of portal capabilities

Considerations Innovation speed of BPM, ESR and Portal to be

synchronized

Sizing considers both BPM and Portal usage

Impact of licensing models to be considered

Portal, BPM and ESR at least at SAP NetWeaver 7.3

Example

ECC

Server

SAP ERP

Backend

ABAP

SCM

Server

SAP SCM

Backend

ABAP

Application

Backend

NON SAP

Application

EP Core

AS JAVA

Application Portal

JEE

Biller Direct

XSS

ERP, SRM, BW

Business Pack.BPM

Composite Apps.

Composite Apps.

ESR & SR


Additional Information

Details for integrating content and applications into SAP NetWeaver Portal:

Best Practice for Integrating SAP applications into the SAP NetWeaver Portal:

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17333

SAP NetWeaver Portal – Application Integration and Federated Portal Network, when should I use each

solution?


Integration of Applications into Portal:

http://www.sdn.sap.com/irj/sdn/nw-puca

Further details regarding BPM deployment:Landscape recommendations for process centric building blocks:

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

Impact of chosen deployment options to software update processesUsage of Landscape Pattern within the “Planning Guide – SAP Business Suite Landscape

Implementation”

https://websmp209.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000671158&

then move to SAP EhPs for SAP ERP 6.0 -> SAP EhP5 for SAP ERP 6.0 -> List of documents








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








Thank You!

Dirk Anthony

TIP Governance Architecture Excellence

SAP System Landscape Governance Board

SAP AG

Dietmar-Hopp-Allee 16

69190 Walldorf

Germany

Phone +49/6227/765224

Fax +49/6227/78-19164

E-Mail [email protected]

mailto:[email protected]

Copyright

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information

contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries,

xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+,

POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect,

RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks

of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States

and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business

Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the

United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational

purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only

warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if

any. Nothing herein should be construed as constituting an additional warranty.

Dirk Anthony, SAP AG June 2011 -...

Documents

Transcript of Dirk Anthony, SAP AG June 2011 -...