Slide 1. System Landscape Recommendations for SAP NetWeaver Gateway. Dirk Anthony, Jürgen Kremer, Matthias Tebbe SAP AG May 2012

Transcription

1 Slide 1 System Landscape Recommendations for SAP NetWeaver Dirk Anthony, Jürgen Kremer, Matthias Tebbe SAP AG May 2012

2 Slide 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 SAP AG. All rights reserved. 2

3 Slide 3 Agenda Introduction Methodology & Scope of Landscape Recommendations Basic Landscape Setups Recommendations for SAP NetWeaver 2012 SAP AG. All rights reserved. 3

4 Slide 4 Introduction Methodology & Scope of Landscape Recommendations

5 SolMan Content Solution Mng Component JEE Additional SAP BS Instance Portal Content JEE SEM Central BI Content BICS JEE ESR Content JEE Slide 5 SAP Business Suite Reference Landscape Baseline For Governance Measures Landscape Standards SAP s internal Development & Test Landscape Architectural Guidelines SAP ERP ERP Components ECC SAP SRM SRM Components SRM SAP SCM SCM Components SCM SAP CRM CRM Components CRM Ease Landscape Planning AS AS AS AS SAP Solution Manager SAP Business Suite Backend Systems Improve Product Capabilities Manage Exceptions SLD Dual Stack Application Portal ADOBE EP Core AS JAVA SAP NetWeaver Hubs Business Warehouse BW AS BEx Web BI JAVA EP AS JAVA Process Integration ESR&SR PI SLD PI Dual Stack Ease Landscape Management SAP System Landscape Governance Board: Central unit within SAP to trigger and monitor concrete landscape related improvements across SAP products 2012 SAP AG. All rights reserved. 5

6 JEE JEE JEE Slide 6 Technical Deployment of SAP NetWeaver Foundation Capabilities Options for implementing the technology foundation of SAP NetWeaver single stack system JAVA single stack system Dual stack system (not recommended any longer, where not technically required) Examples: SAP ERP Backend Application Portal Process Integration BW incl. BEx Web ECC EP Core PI BW BI JAVA single stack JAVA single stack Mandatory Dual stack (technically req.) Optional Dual stack (technically not req.) Definition for Dual Stack: Legend SAP system containing Application and Application 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 and Java) SAP system with own database Role main role of this system used platform technology 2012 SAP AG. All rights reserved. 6

7 JEE JEE JEE Slide 7 Technical Deployment of SAP NetWeaver Integration Capabilities 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 Examples: SAP NetWeaver Portal technically deployed within the SAP ERP system* SAP ERP SAP NetWeaver Portal deployed as a central hub shared by an SAP ERP and an SAP SRM system Application Portal SRM Content HCM XSS XSS ECC EP Core EP Core * only to support existing setups SAP NetWeaver Portal deployed as a local sidecar to an SAP ERP system SAP ERP Backend HCM ERP Portal XSS SAP ERP Backend ECC SAP SRM Backend SRM ECC EP Core 2012 SAP AG. All rights reserved. 7

8 Slide 8 Ease Landscape Setups By Stronger Guidance Used Methodology Clear recommendations by categorization of deployment options Possible Exception Only useful for specific use cases Supported by SAP, but limitations might occur Reasonable Alternative Useful choice for certain use cases or customer scenarios Supported and confirmed by SAP s strategy Option III Option II Option I General Recommendation Best choice for majority of typical landscape use cases Recommended by SAP s strategy Accepted by a wide base of customers Goal Consider 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 2012 SAP AG. All rights reserved. 8

9 Slide 9 Scope of Landscape Recommendations Overview SAP NetWeaver 2.0 Architecure of different deployment options SAP NetWeaver Central Content Enabl. AS Dedicated SAP NetWeaver system SAP Business Suite Application System Local Applic. Content* Enabl. SAP Business Suite Application AS * e.g. Mobile Add-On, HCM Renewal SAP Business Suite Application System Local Applic. Content* Enabl. SAP Business Suite Application AS * e.g. Mobile Add-On, HCM Renewal SAP NetWeaver within application system Legend: see next slide Considered main usage scenarios Enables UI-centric applications to consume SAP Business Suite data in an easy and standards-based way Enables online scenarios on mobile devices Enables a new light-weight consumption across different kind of application backend systems based on OData Considered main building blocks SAP NetWeaver containing Add-On to provide complete gateway infrastructure Optional Content Add-On for centrally produced and provided content Optional Enablement Add-On to provide infrastructure services that are required by local application content Local Application Content Optional content Add-On to consume applications via e.g. Mobile Add-On for SAP Business Suite, HCM Renewal Requires locally deployed Enablement Add-On 2012 SAP AG. All rights reserved. 9

10 Slide 10 Legend SAP NetWeaver Central Content Enabl. AS SAP Business Suite Application System Local Applic. Content* SAP system with own database Role JEE main role of this system available platform technology mandatory component optional component Enabl. SAP Business Suite Application AS Overview main Installation Add-Ons for SAP NW IW_FND GW_CORE Central Content IW_CNT IW_CBS Enablement IW_BEP 2012 SAP AG. All rights reserved. 10

11 Slide 11 Basic Landscape Setups Recommendations for SAP NetWeaver Dependent of aimed main use cases

12 Slide 12 Landscape Use Case I: OData Enablement of SAP Applications Typical Characteristics of this Landscape Setup SAP ERP ERP specific content* Enabl. ECC AS Example: OData enablement of SAP ERP system Main use cases online mobile scenarios as provided by SAP Business Suite Add-Ons for mobile applications support HTML5 based UI access to SAP Business Suite systems Main required SAP NetWeaver components and Enablement as SAP NetWeaver AS Add-Ons SAP NetWeaver used to enable OData based access to SAP Business Suite applications to reduce development costs by using local business logic and dictionary objects Local OData content delivered for dedicated SAP applications User/access management for mobile user could be managed via Sybase Unwired Platform 2012 SAP AG. All rights reserved. 12

13 Slide 13 Deployment of SAP NetWeaver Embedded deployment within application system General Recommendation SAP NetWeaver & Enablement Add-Ons deployed in each application backend system that shall be enabled for light-weight consumption Avoid deployment of central SAP NetWeaver Content in application system Example SAP ERP ERP specific content* Enabl. ECC AS consumer~ App... App Point-to-point connectivity with single application system SAP ERP HCM HCM specific content* Enabl. ECC AS * e.g. Mobile Add-On, HCM Renewal ~ e.g. desktops or mobile clients, SUP platform SAP CRM CRM specific content* Enabl. CRM AS Benefits Direct local access to metadata and business data Simplified deployment when using mobile applications provided by SAP No additional SAP NetWeaver system Considerations Lifecycle of SAP NetWeaver content determined by update frequency of backend Backend system must be based on SAP NetWeaver 7.0 SP25, 7.01 SP10, 7.02 or higher Point-to-point integration of consuming application with application system No usage of central SAP NetWeaver content, only local application-specific content used 2012 SAP AG. All rights reserved. 13 General Recommendation (embedded deployed with local application backend system) SAP NetWeaver & Enablement Add-Ons deployed in each application backend system that shall be enabled for light-weight consumption Simplified enablement of SAP NetWeaver consumer with single application systems Avoid deployment of central SAP NetWeaver Content in application system (only local application content to be deployed in backend systems) Benefits Direct local access to metadata and business data Simplified deployment when using mobile applications provided by SAP No content merge for different applications required No additional separate SAP NetWeaver system required Considerations Lifecycle of SAP NetWeaver content is determined by the update frequency of the backend system Backend system must be based on SAP NetWeaver 7.0 SP25, 7.01 SP10, 7.02 or higher

14 Consuming app or consuming infrastructure need to be integrated with application system on a point-to-point base Central SAP NetWeaver content not available, only application-specific content locally used

15 Slide 14 Deployment of SAP NetWeaver Central single hub deployment Reasonable Alternative & optional central content deployed as central hub provides OData based or HTML5 based access for multiple application backend systems Example SAP Netweaver Enabl. AS consumer App... App Benefits Central management of connectivity deployed only once SAP NetWeaver system could be implemented in DMZ to serve specific security needs Software update frequency of SAP NetWeaver decoupled from application backend system Central OData & HTML5 enablement for multiple SAP Business Suite backend systems SAP ERP 6.0 ERP content* ERP content* enabl. ECC SAP ERP 6.05 ERP content* enabl. ECC * e.g. Mobile Add-On, HCM Renewal SAP SRM SRM content* enabl. SRM Considerations Additional SAP NetWeaver system SAP Web Dispatcher mandatatorily req. for HTML5 based scenarios enabl. component additionally to be installed in each application system that requires local OData content Limited version interoperability until SAP Netweaver 2.0 SP4: version must be >= version of enabl. (planned to be removed with SP5) 2012 SAP AG. All rights reserved. 14 Reasonable Alternative (central SAP NetWeaver Hub) & optional central content deployed as central hub provides OData based or HTML5 based access for multiple application backend systems Benefits Central management of connectivity with application systems component deployed only once within the landscape SAP NetWeaver system could be implemented in DMZ for external access to serve specific security needs Software update frequency of SAP NetWeaver is decoupled from the application backend system Considerations Additional separate SAP NetWeaver system required HTML5 based scenarios mandatorily require a reverse proxy (e.g. SAP Web Dispatcher) in addition to route access to SAP NetWeaver server and application backend system Only few solutions require dedicated central SAP NetWeaver content today

16 enabl. component additionally to be installed in each application system, if OData content within backend system required Limitation of version interoperability until SAP Netweaver 2.0 SP4: version must be >= version of enabl.; limitaiton planned to be removed with SP5

17 Slide 15 Deployment of SAP NetWeaver Sidecar deployment Possible Exception SAP NetWeaver deployed as redundant separate systems for local usage only Application specific content is deployed within application backend system Example SAP NetWeaver Consumer specific Content Enabl. AS SAP R/3 Enterprise R/3 SAP NetWeaver AS application specific prepackaged systems locally linked to single backend system SAP ERP ERP content* enabl. ECC SAP NetWeaver AS SAP SRM SRM content* enabl. SRM Benefits Update of SAP NetWeaver system does not impact application backend system Support of application systems based on a lower version than SAP NetWeaver 7.0 SP25 or 7.01 SP10 Considerations Landscape complexity increases significantly with increasing number of application systems Highest administration effort SAP Web Dispatcher mandatatorily req. for HTML5 based scenarios * e.g. Mobile Add-On, Consumer Grade UI 2012 SAP AG. All rights reserved. 15 Possible Exception (multiple local separate SAP NetWeaver systems) SAP NetWeaver deployed as redundant separate systems for local usage only Application specific content is deployed within application backend system Benefits Update of SAP NetWeaver system does not impact application backend system Support of application systems with a version that do not support a codeployment (based on a lower version than SAP NetWeaver 7.0 SP25 or 7.01 SP10) Support of individual application systems on a NON- platform Considerations Landscape complexity increases significantly with increasing number of application systems that need to be enabled for consumer Highest administration effort HTML5 based scenarios mandatorily require a reverse proxy (e.g. SAP Web Dispatcher) in addition to route access to SAP NetWeaver server and application backend system

18

19 Slide 16 Change Deployment of SAP NetWeaver Later move to embedded deployment Scale-in Option Temporarily more complex landscape at the beginning of the product lifecycle of SAP NetWeaver to reduce impact on SAP Business Suite application system Move at a later state to the embedded deployment setup Example SAP NetWeaver Consumer specific Content Enabl. Content AS SAP R/3 Enterprise R/3 SAP NetWeaver AS application specific prepackaged systems locally linked to single backend system SAP NetWeaver AS SAP ERP SAP SRM ERP specific SRM content* content* Enabl. enabl. SRM ECC Benefits Customer can start with separate SAP NetWeaver system to reduce impact on SAP Business Suite application system Reduce landscape complexity after piloting phase Considerations component needs to be moved to the SAP Business Suite application system (additional Add-On deployment) Configuration data of all involved components need to be changed manually AS 2012 SAP AG. All rights reserved. 16 Scale-in Option Accept temporarily more complex landscape at the beginning of the product lifecycle of SAP NetWeaver to reduce impact on SAP Business Suite application system Move at a later state to the embedded deployment setup Benefits Customer can start with separate SAP NetWeaver system to reduce impact on SAP Business Suite application system Reduce landscape complexity after piloting phase Considerations component needs to be moved to the SAP Business Suite application system (additional Add-On deployment) Configuration data of all involved components need to be changed manually

20 Slide 17 Change Deployment of SAP NetWeaver Central hub deployment combined with local deployment Scale-out Option & central content deployed as central hub & enablement for individual SAP Business Suite systems Central hub enables central consumption across different applications Local used for individual OData enablement Example NON SAP Infrastructure SAP Netweaver Central Duet Enterprise or Alloy connectivity with partner infrastructure Consumer specific content Enabl. Central Content AS Central routing and connectivity of Duet/Alloy scenarios against multiple backend systems SAP ERP ERP content* SAP R/3 Enterprise enabl. ECC R/3 App consumer connectivity with single application system via central consumer infrastructure SAP ERP HCM HCM content* enabl. ECC... App Benefits Customer can start with simple landscape setup and scale out later Central management of routing & connectivity Central and local content can be separated due to aimed use cases Redundant deployment of metadata could be avoided Considerations component deployed multiple times (local and central usage combined) Separation of local and central usage need to be configured 2012 SAP AG. All rights reserved. 17 Scale-out Option & central content deployed as central hub & enablement for individual SAP Business Suite systems Central hub enables central consumption across different applications (see landscape use case II) Local used for individual OData enablement Benefits Customer can start with simple landscape setup (embedded deployment) and scale out later Central management of routing & connectivity with application systems (e.g. SAP NetWeaver enables routing for Alloy or Duet Enterprise scenarios against multiple backend systems) Central and local content can be separated due to the aimed use cases Redundant deployment of metadata could be avoided Considerations component deployed multiple times within the landscape (local and central usage combined) Separation of local and central usage need to be configured

21

22 Slide 18 Landscape Use Case II: Enable Central Consumption For Multiple Backends Typical Characteristics of this Landscape Setup SAP Netweaver Consumer specific content Enabl. Central Content AS Example: dedicated SAP NetWeaver hub with central content Main use cases enable a central light-weight consumption across different kind of application backend systems Main required SAP NetWeaver building blocks based on SAP NetWeaver AS [mandatory] Enablement, Central Content [optional] SAP NetWeaver used as a development framework to enable people centric applications for consuming business data out of different kind of application systems based on OData standard Consuming business data without disruptive changes in the application system Central SAP NetWeaver hub can be additionally used for OData enablement of SAP Business Suite systems (might require deployment of Enablement Add-On in SAP Business Suite system for local application content) 2012 SAP AG. All rights reserved. 18

23 Slide 19 Deployment of SAP NetWeaver Central single hub deployment General Recommendation deployed as central hub Additional central or consumer specific content could be exposed by the SAP NetWeaver Hub as well Example SAP Netweaver Consumer specific content Enabl. Central Content AS Central Duet Enterprise or Alloy connectivity with partner infrastructure NON SAP Infrastructure Benefits Decoupled lifecycle of consumer apps from applications Central management of routing & connectivity deployed only once SAP NetWeaver system could be implemented in DMZ to serve specific security needs Lifecycle of SAP NetWeaver system decoupled from lifecycle of application system SAP NetWeaver Business Warehouse BW Content BW Central routing and connectivity of Duet/Alloy scenarios against multiple application systems SAP ERP ERP content* enabl. ECC * e.g. Mobile Add-On, Consumer Grade UI SAP SRM SRM content* enabl. SRM Considerations Central SAP NetWeaver content available, but limited scope today Redundant deployment of metadata or Data Dictionary structures Optional deployment of enablement in application system to simplify local OData content development 2012 SAP AG. All rights reserved. 19 General Recommendation (central individual SAP NetWeaver Hub) deployed as central hub Additional consumer specific content could be exposed by the SAP NetWeaver Hub as well Benefits Decoupled lifecycle of consumer apps from applications (via dedicated central content) Central management of routing & connectivity against application systems (e.g. enables routing for Alloy or Duet Enterprise scenarios against multiple backend systems) component deployed only once within the landscape SAP NetWeaver system could be implemented in DMZ for external access to serve specific security needs Lifecycle of SAP NetWeaver system decoupled from lifecycle of application system Considerations Central SAP NetWeaver content available, but limited scope today Potentially redundant deployment of metadata or Data Dictionary structures within SAP NetWeaver hub

24 Optional deployment of enablement in application system to simplify local OData content development (by directly using local business logic and dictionary objects)

25 Slide 20 Thank you

26 Slide 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, PowerPoint, Silverlight, and Visual Studio 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, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Oracle and Java are registered trademarks of Oracle and its affiliates. 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. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. IOS is a registered trademark of Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc. INTERMEC is a registered trademark of Intermec Technologies Corporation. Wi-Fi is a registered trademark of Wi-Fi Alliance. Bluetooth is a registered trademark of Bluetooth SIG Inc. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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 Software Ltd. Business Objects is an SAP company. Sybase and Adaptive, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG SAP AG. All rights reserved. 21

27 Slide SAP AG. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/vm, z/os, OS/390, zenterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, purescale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix und Smarter Planet sind Marken oder eingetragene Marken der IBM Corporation. Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Ländern. Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Incorporated in den USA und/oder anderen Ländern. Oracle und Java sind eingetragene Marken von Oracle und/oder ihrer Tochtergesellschaften. UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Apple, App Store, ibooks, ipad, iphone, iphoto, ipod, itunes, Multi-Touch, Objective-C, Retina, Safari, Siri und Xcode sind Marken oder eingetragene Marken der Apple Inc. IOS ist eine eingetragene Marke von Cisco Systems Inc. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook und BlackBerry App World sind Marken oder eingetragene Marken von Research in Motion Limited. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik und Android sind Marken oder eingetragene Marken von Google Inc. INTERMEC ist eine eingetragene Marke der Intermec Technologies Corporation. Wi-Fi ist eine eingetragene Marke der Wi-Fi Alliance. Bluetooth ist eine eingetragene Marke von Bluetooth SIG Inc. Motorola ist eine eingetragene Marke von Motorola Trademark Holdings, LLC. Computop ist eine eingetragene Marke der Computop Wirtschaftsinformatik GmbH. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA und weitere im Text erwähnte SAP-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern. Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius und andere im Text erwähnte Business- Objects-Produkte und Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der Business Objects Software Ltd. Business Objects ist ein Unternehmen der SAP AG. Sybase und Adaptive, ianywhere, Sybase 365, SQL Anywhere und weitere im Text erwähnte Sybase-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der Sybase Inc. Sybase ist ein Unternehmen der SAP AG. Crossgate, EDDY, B2B 360, B2B 360 Services sind eingetragene Marken der Crossgate AG in Deutschland und anderen Ländern. Crossgate ist ein Unternehmen der SAP AG. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet SAP AG. All rights reserved. 22