RKT Live Expert Session - PDF Free Download

RKT Live Expert Session Federated PI and Deployment Options Alexander Bundschuh SAP Product Management SAP NetWeaver Process Integration December 2010

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. 2010 SAP AG. All rights reserved. / Page 2

Background Information Scaling PI What will be covered in this presentation? Horizontal Additional PI Instances (Federation) Additional PI De-Central Adapter Engines (Distribution) Vertical Increasing hardware specification. Memory etc. Additional Java Server nodes Additional ABAP dialogue instances 2010 SAP AG. All rights reserved. / Page 4

SAP NetWeaver Process Integration 7.3 Installation and Connectivity Options ES Repository, Registry & Integration Directory System Landscape Directory Integration Server Business Process Engine Integration Engine SAP Solution Manager ES Repository SR, ID, SLD Adapter Engine (Java SE) Adapter IDoc, WS, http Central Advanced Adapter Engine Mediation Connectivity Security Non-Central Advanced Adapter Engine (opt.) Mediation Connectivity Security Advanced Adapter Engine Extended (optional) Mediation Connectivity Security File DB JMS SOAP Service Provider Service Consumer Application Techn. System File/DB/JMS Apps of Business Partners SAP System 2010 SAP AG. All rights reserved. / Page 5

Installation Options 7.0 XI / PI Domain IS Monitoring ESR Configuration IE ABAP AE JEE AE JEE AE JEE Double-Stack PI De-Central Adapter Engines (optional) Message Flow 2010 SAP AG. All rights reserved. / Page 6

Installation Options 7.1 / 7.11 & 7.30 Introduction of AAE PI Domain IS Monitoring ESR Configuration IE ABAP AAE JEE AAE JEE AAE JEE Double-Stack PI De-Central Advanced Adapter Engines (optional) Message Flow 2010 SAP AG. All rights reserved. / Page 7

New Installation Option planned for 7.30 SP2 AEX with De-Central AAEs PI Domain AEX Monitoring ESR Configuration AAE JEE AAE JEE AAE JEE JEE-based PI De-Central Advanced Adapter Engines (optional) Message Flow 2010 SAP AG. All rights reserved. / Page 9

What is PI Federation Architectural Models Central A single integration server communicating with all business systems. Distributed A single integration server with one or more de-central adapter engines communicating with relevant business systems. Federated Two or more integration servers within a single landscape tier communicating with relevant business systems 2010 SAP AG. All rights reserved. / Page 12

What is PI Federation Architectural Progression Sample geographical progression.. Central Central PI Integration Server supporting global requirements Distributed Central PI Integration Server with de-central adaptor engines located regionally Central PI Integration Server with de-central adaptor engines close to business systems Expansion Federated Region PI Integration Servers Regional PI Integration Servers with de-central adaptor engines close to business systems Global PI Integration Server with regional PI integration servers Localized PI Integration Servers Shadow PI Integration Servers in production for business continuity in patching or upgrade scenarios. (Not specifically in this progression) Consolidation 2010 SAP AG. All rights reserved. / Page 13

Architectural Models Central - Reasons Simplicity and great TCO benefits High level of governance. High re-use of development objects. It should be considered as a starting point for all organizations before further distribution or federation is implemented. Global requirements can be met via security and role based authorizations. 2010 SAP AG. All rights reserved. / Page 16

Architectural Models Central - Characteristics TCO Administration Effort Availability Monitoring Complexity Low Low Med Low Minimum hardware & application servers. Software Logistics simplified. Due to the single instance all in one solution. Upgrades, patches and software logistics are at their simplest. For larger organizations with a global footprint this may be restrictive due to downtime and patching synchronization. Single PI domain equals simplified monitoring Performance Internal Network Efficiency Common BP Delivery Global & Local Low Low High Low In a global organization this may be seen as low due to every message forced through central IS. In a global organization network efficiency is minimized due to lack of local processing. Development object re-use is maximized leading to common business process delivery. Single design time. In a global organization local autonomy may be restricted. Security & Profile usage may avoid this issue. 2010 SAP AG. All rights reserved. / Page 17

Architectural Models Central - Recommendations Governance Central Software Logistics & Synchronization ESR Integration Directory SLD Service Registry Proxy Development Normal transports with CTS+ integration across each tier. No additional synchronization required due to central governance model. Normal transports with CTS+ integration across each tier. No additional synchronization required due to central governance model. Strategy will determine complexity of software logistics. Production/Non Production or an SLD per tier is recommended. Strategy is independent of PI implementation however a single SR per tier is recommended across all SAP solutions. i.e. Single SR for all of Dev. Ensure transportation of ESR content and SWCV is consistent with backend proxy definitions and associated runtime. General Recommendation Central model offers great TCO benefits and should be the starting point where possible. 2010 SAP AG. All rights reserved. / Page 18

Architectural Models Distributed - Overview Single Integration Server with De-Central AEs. De-Central Adapter Engines* Central Design De-Central Execution * AAE or J2SE adapter engines 2010 SAP AG. All rights reserved. / Page 20

Architectural Models Distributed - Reasons Higher degree of distribution Localization Local processing of messages reducing network load, improving performance and reliability. Business Continuity Business continuity such as downtime minimization Technical Abstraction from upgrades & downtime Security Placement within a De-Militarized Zone for external and internal zone abstraction 2010 SAP AG. All rights reserved. / Page 21

Architectural Models Distributed Examples Single Integration Server with De-Central AEs. How close to your business system? Switch over scenarios using: Web Dispatcher Directory API Type Localization Business Continuity Security Description Central PI Integration Server with de-central adaptor engines located regionally. Central PI Integration Server with de-central adaptor engines located near business systems. Central PI integration Server with redundant Adapter Engines to be used in controlled switch over scenarios when upgrading or patching. Central PI Integration Server with an additional Adapter Engine in a De-Militarized Zone (DMZ). 2010 SAP AG. All rights reserved. / Page 22

Architectural Models Distributed - Characteristics TCO Administration Effort Availability Monitoring Complexity Performance Internal Network Efficiency Common BP Delivery Global & Local Med Med Med Med Med Med High Med Higher than central but still viable given additional application servers are still part of single domain. Higher effort than central given additional application servers. Central administration still an advantage. Better than central model due to de-central processing of messages and associated de-coupling. Higher than central but still manageable given single domain. Increased performance due to de-central message processing and associate load balancing benefits Improved efficiencies due to reduction of redundant message communications across network Development object re-use is maximized leading to common business process delivery. Single design time. Improved localization and globalization given distribution of runtime. Design time still centralized requiring security. 2010 SAP AG. All rights reserved. / Page 23

Architectural Models Federated - Reasons Highest flexibility at the expense of TCO Segmentation Geographical Organization and divisional autonomy due to legal or operational reasons. Able to remove division or sub-org quickly if sold. Separation of A2A and B2B integration scenarios for security reasons. Separation by process types such as transactional versus master data. Quality of Service obligations Billing requirements based on volume Prioritization of messages Security issues around personal data Business Continuity Business continuity such as downtime minimization Technical Abstraction from upgrades & downtime 2010 SAP AG. All rights reserved. / Page 26

Architectural Models Federated Examples Multiple PI instances per Tier What type of Segmentation? E.g. Political Level of segmentation? E.g. Regional Business Continuity for upgrades etc? 2010 SAP AG. All rights reserved. / Page 27

Architectural Models Federated - Characteristics TCO Administration Effort Availability Monitoring Complexity Performance Internal Network Efficiency Common BP Delivery Global & Local High High Med High High High Low High Highest TCO due to level of federation and additional PI instances. Large effort required to manage the solution and synchronize objects across landscapes. Best given local autonomy of design time and runtime message processing. De-coupling level is high. Domains monitored separately from central location however no holistic monitoring. You have to look at each domain. High level of performance given local processing. Additional hops with hub-2-hub may offset this. High level of efficiency due to minimization of network load. Again in hub-2-hub messaging an offset may be evident. Low level of re-use and resulting lack of common business process delivery. Multiple design times and runtimes. Allows for complete autonomy of local requirements which may offset global vision as per previous point. 2010 SAP AG. All rights reserved. / Page 28

Architectural Models Federated - Recommendations Governance Central Local or Mixed Software Logistics & Synchronization ESR Integration Directory Choose you governance model. Either do everything centrally in one ESR and then transport 1:1 or selectively author based on object type. MD / TX. Local configuration is required to configure local scenarios and end points. SLD Service Registry Proxy Development Strategy will determine complexity of software logistics. Production/Non Production or an SLD per tier is recommended. Strategy is independent of PI implementation however a single SR per tier is recommended across all SAP solutions. i.e. Single SR for all of Dev. Ensure transportation of ESR content and SWCV is consistent with backend proxy definitions and associated runtime. General Recommendation Federation offer flexibility and abstraction but significantly impacts TCO. Implement wisely! 2010 SAP AG. All rights reserved. / Page 29

Architectural Models Federated - Recommendations Business System Communications Hub to Hub Clean demarcation of messaging Hub to Business System Connections to each business system Restrictions on sender proxy scenarios Higher level of complexity 2010 SAP AG. All rights reserved. / Page 30

General Recommendations Governance Model Selection Where should my ESR objects be created and by whom? Centrally Allows for high level of object re-use Common process delivery Security and profiles should be leveraged Local No object re-use achieved Complete autonomy May provide flexibility from isolation Mixed Some object re-use achieved Benefits from both models Requires co-ordination 2010 SAP AG. All rights reserved. / Page 32

General Recommendations Final Thoughts Keep it simple Expansion - Start with central and justify outwards. Consolidation Less is more. Emphasize governance. There is a trade off between TCO and flexibility. Security Leverage security across components. ESR & Integration Directory provides flexible security model to restrict access. This may be enough to mitigate concerns with central architectural mode. Justify Architectural Change Enforce governance. Don t jump to federation without understanding considerations. Justify changes to architecture carefully. 2010 SAP AG. All rights reserved. / Page 33

Appendix Characteristic Descriptions TCO Administration Effort Availability Monitoring Complexity Performance Internal Network Efficiency Common BP Delivery Global & Local Total Cost of Ownership defines just how much it costs to implement, operate and support a given IT solution Administration defines how difficult the overall landscape is to operate and maintain with respect to downtime and planned upgrades etc. Relates to how available the Process Integration system for message processing This criterion defines the complexity and coverage of the monitoring solution in a given deployment model. This criterion covers the internal performance of the SAP application software, database and operating system when processing a message in SAP PI. Network looks at the impact or utilization on the physical communication network The ability to enforce a common business processes across the Process Integration landscape. The ability to meet local and global requirements both technically and business related. 2010 SAP AG. All rights reserved. / Page 34

SAP NetWeaver PI 7.3 Live Expert Sessions Times: 10:00 11:00 am (CET), 5:00 6:00 pm (CET) each What s new in SAP NetWeaver PI 7.3? Oct. 26 What s new in ESR 7.3? Oct. 28 What are the new service bus-based capabilities for SAP NetWeaver PI 7.3? Oct. 29 Central monitoring of SAP NetWeaver PI 7.3 landscapes with the new PI Work Center in SAP Solution Manager 7.1 Nov. 9 Improved fault tolerance with SAP NetWeaver PI 7.3 Dec. 9 Upgrade to SAP NetWeaver PI 7.3 Dec. 10 Available adapters for SAP NetWeaver PI 7.3 Dec. 13 Advanced Adapter Engine Extended - a new Java only installation option for SAP NetWeaver PI 7.3 Dec. 14 Local monitoring enhancements within SAP NetWeaver PI 7.3 Dec. 15 Federated PI and deployment options Dec. 16 Register at: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/21582 2010 SAP AG. All rights reserved. / Page 35

Registration for Ramp-up of SAP NetWeaver PI 7.3 Interested in joining the ramp-up for SAP NetWeaver PI 7.3? Registration at Customers: http://service.sap.com/rampup Partners: https://service.sap.com/partnerportal/rampup 2010 SAP AG. All rights reserved. / Page 36

2010 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 BusinessObjects Explorer 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. in the United States and in other countries. 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. 2010 SAP AG. All rights reserved. / Page 37