Slide 1. System Landscape Recommendations for SAP NetWeaver 7.3 Process Centric Capabilities. Dirk Anthony, SAP AG June 2011

Transcription

1 Slide 1 System Landscape Recommendations for SAP NetWeaver 7.3 Process Centric Capabilities Dirk Anthony, SAP AG June 2011

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 Process Integration and Business Process Management Deployments Enhanced Landscape Setups Additional Aspects for SAP NetWeaver Process Integration Based System Landscapes Related Building Blocks Recommendations for Deployment of System Landscape Directory 2011 SAP AG. All rights reserved. 3

4 Slide 4 Introduction Methodology & Scope of Landscape Recommendations

5 SolMan Content Solution Mng Component Additional SAP BS Instance Portal Content SEM Central BI Content BICS ESR Content Slide 5 SAP Business Suite Reference Landscape Baseline For Governance Measures Landscape Standards SAP s internal Development & Test Landscape Architectural Guidelines ERP Components SAP SRM SRM Components SRM SAP Components SAP CRM CRM Components CRM Ease Landscape Planning AS AS AS AS SAP Solution Manager SAP Business Suite Systems Improve Product Capabilities Manage Exceptions SLD Dual Stack Portal ADOBE EP Core SAP NetWeaver Hubs Business Warehouse BW AS BEx Web BI JAVA EP Process Integration 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 2011 SAP AG. All rights reserved. 5

6 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: Portal Process Integration BW incl. BEx Web 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 and 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 2011 SAP AG. All rights reserved. 6 Definition for Dual Stack: SAP system that contains installations of both and 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)

7 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 system* SAP NetWeaver Portal deployed as a central hub shared by an and an SAP SRM system Portal SRM Content HCM XSS XSS EP Core EP Core * only to support existing setups SAP NetWeaver Portal deployed as a local sidecar to an system HCM ERP Portal XSS SAP SRM SRM EP Core 2011 SAP AG. All rights reserved. 7

8 Slide 8 Deployment Of SAP Products Within A Solution Landscape Architectural Decisions Distribution of deployable product components Integrated Technology Stacks Combined usage of duties by multi stack system Deploy product components Centrally Shared Reuse of platform capabilities within a central system Separated Technology Stacks Separation of duties by separated technology stacks 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 2011 SAP AG. All rights reserved. 8

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

10 Slide 10 Scope of Landscape Recommendations (1/2) Building Blocks in System Landscapes for Process Centric Capabilities Process Integration - PI Content ccbpm Engine Advanced Integration Adapt. Engine Engine SLD Considered main building blocks SAP NetWeaver Process Integration (dual stack) Advanced Adapter Engine Extended (JAVA only) Enterprise Services Repository & Services Registry System Landscape Directory PI Dual Stack Process Integration - AEX Content JAVA Decentral Advanc. Adapter Engine Advanced Adapt. Engine Considered main usage scenarios A2A connectivity: Integration of internal systems B2B connectivity: Integration of systems across company boundaries Advanced Adapt. Engine SLD JAVA AEX SAP system with own database Role main role of this system available platform technology 2011 SAP AG. All rights reserved. 10 Considered main building blocks SAP NetWeaver Process Integration (PI - dual stack) Advanced Adapter Engine Extended (AEX - JAVA only) Enterprise Services Repository & Services Registry () System Landscape Directory Considered main usage scenarios A2A connectivity: Integration of internal systems to connect business activities and exchange information B2B connectivity: Integration of systems across company boundaries based on common standards

11 Slide 11 Scope of Landscape Recommendations (2/2) Building Blocks in System Landscapes for Process Composition Business Process Management Composite App. BPM Java-based incl. BRM SAP Instance COMP-ENV Additional SAP NetWeaver CE-APPS instance Considered main building blocks Business Process Management (BPM) Including Business Rules Management (BRM) Based on Composition Environment Platform and Composition Framework Considered main usage scenarios Business Process Composition Compose new innovative business process extensions BPM 7.30 focuses on human centric integration processes UI and Service Composition Develop, run, and manage composite applications Mainly used as part of Business Process Composition Role main role of this system SAP system with own database available platform technology 2011 SAP AG. All rights reserved. 11 Considered main building blocks Business Process Management (BPM) Including Business Rules Management (BRM) Based on Composition Environment Platform (COMP-ENV incl. Visual Composer, Enterprise Content Management, Enterprise Portal-baseline) Based on Composition Framework (CE-APPS) Considered main usage scenarios Business Process Composition: Compose new innovative business process extensions Integrate, adapt and extend core business processes BPM 7.30 focuses on human centric integration processes UI and Service Composition: Mainly used as part of Business Process Composition Develop, run, and manage composite applications Build new UIs on top of services of connected application systems Define, implement, adapt and govern services in a SOA landscape

12 Slide 12 Basic Landscape Setups Recommendations for SAP NetWeaver Process Integration and Business Process Management Deployments

13 Slide 13 Deployment of SAP NetWeaver Process Integration PI dual stack system General Recommendation Shared usage of SAP NetWeaver PI system Deployed as a central, separate system Avoid embedded deployment within the application backend system Example SAP Process Integration PI PI Dual Stack Integrating applications of different backend systems Less complexity of system landscape Central governance for meta data Less effort for maintaining data for routing, mapping, connectivity Central responsibility for monitoring of services and processes Different update cycles of PI and application backend systems Support of high volume scenarios, simplified modeling and configuration 2011 SAP AG. All rights reserved. 13 General Recommendation Central PI Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios SAP NetWeaver Process Integration is deployed as a central, separate system to support different innovation speed and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Process Integration within the application backend system Typical Technical Use Cases: Integration of internal systems to connect business activities and exchange information (A2A) Integration of systems across company boundaries based on common standards (B2B) Less complexity of system landscape Central governance for meta data Less effort by central maintaining of data for routing, mapping, connectivity, etc. Central responsibility for monitoring of services and processes Support of high volume scenarios, simplified modeling and configuration, enhanced standard support started with SAP NetWeaver PI 7.1

14 Slide 14 Deployment of SAP NetWeaver Process Integration PI dual stack system Possible Exception Separation of local Business or IT units by multiple PI domains Avoid embedded deployment within the application backend systems Example Process Integration PI PI Dual Stack Manual synchronization of PI content Process Integration Separation of PI systems due to organizational responsibilities Local development and service design Business Unit 1 (PI domain 1) SAP PI PI Dual Stack Business Unit 2 (PI domain 2) Governance for meta data more complicated No automatic federation across different PI systems Each application system can only be connected to one single PI More complex landscape 2011 SAP AG. All rights reserved. 14 Possible Exception Multiple PI systems within one system landscape Separation of local Business or IT units by multiple PI domains SAP NetWeaver Process Integration is deployed separately to the application systems for different innovation speed Avoid embedded deployment of SAP NetWeaver Process Integration within the application system Typical Technical Use Cases Integration of internal systems to connect business activities and exchange information (A2A) Integration of systems across company boundaries based on common standards (B2B) Separation of PI systems due to organizational responsibilities Local development and service design Governance for meta data becomes more complicated No automatic federation between different PI systems (content has to be synchronized manually by transports) Each application system can only be connected to one single PI More complex landscape

15 Slide 15 Deployment of SAP NetWeaver Process Integration Advanced Adapter Engine Extended (AEX) Landscape Setups for AEX Lean JAVA-based integration broker without business process management capabilities included within AEX deployment Same landscape recommendations like for SAP NetWeaver PI dual stack setup AEX will be closer integrated with SAP NetWeaver BPM in the future Example Advanced Adapter Engine Extended ESR Content Lean pure JAVA based deployment of middleware Less complex system architecture Central governance, monitoring and administration SAP AEX Integrating applications of different backend systems Subset of functionality compared to PI dual stack AEX closer integrated with SAP NetWeaver BPM in the future to support business process composition for system centric integration scenarios No joint deployment of BPM and AEX possible with SAP NetWeaver 7.30 Connecting non-central AAEs with a central AEX planned to be supported with 7.30 SP SAP AG. All rights reserved. * Current planning state, subject to change 15 Landscape Setups for AEX AEX is a lean JAVA-based integration broker without business process management capabilities included within AEX deployment Same landscape recommendations like for the SAP NetWeaver PI dual stack setup For future versions AEX will be closer integrated with SAP NetWeaver BPM to support business process composition for system centric integration scenarios Typical Technical use cases Integration of A2A or B2B processes between SAP and Non-SAP systems where pure mediation capabilities are required (no ccbpm functionality required) Usage of AEX for SAP Business Suite see SAP note Lean pure JAVA based deployment of middleware Less complex system architecture Central governance, monitoring and administration Subset of functionality compared to PI dual stack No joint deployment of BPM and AEX possible with SAP NetWeaver 7.30 Connecting non-central AAEs with a central AEX planned to be supported with 7.30 SP2

16 Slide 16 Deployment of Business Process Management Human Centric Integration Scenarios General Recommendation Central system for human centric integration scenarios If no SAP Portal part of the system landscape, locally contained basic portal capabilities within BPM can be used; does not substitute application portal usage No embedded deployment of BPM within PI dual stack or application backend Example Busines Process Management Composite Apps. Additional SAP NetWeaver BPM instance (optional) SAP Consuming application services within human centric scenarios Less complex system landscape Centrally governed and administrated composition of business processes Less operations effort Single system must fit to overall availability and scalability needs Connection to external LDAP or central identity management might be required for workflow driven scenarios 2011 SAP AG. All rights reserved. 16 General Recommendation Use BPM as a central system for business process composition for human centric integration scenarios across different connected application systems If no SAP Portal is part of the system landscape, locally contained basic portal capabilities within BPM can be used as runtime for composite applications However, BPM deployment does not substitute a comprehensive application portal No joint deployment of BPM within PI dual stack system possible Avoid embedded deployment within application backed system Joint deployment of BPM with other components will be considered within the next slides Typical Technical Use Cases Business Process Composition for human centric integr. scen. Build simplified UIs on top of services of application systems Less complex system landscape Centrally governed and administrated composition of business processes Less operations effort by avoiding multiple local BPM or CE systems Single system must fit to overall availability and scalability needs Connection to external LDAP or central identity management might be required for workflow driven scenarios (e.g. creating tasks for certain user or user groups)

17 Slide 17 Deployment of Business Process Management Human Centric Integration Scenarios General Recommendation If SAP NetWeaver Portal used as central Portal, central BPM jointly deployed with the portal system for human centric integration scenarios Joint deployment of BPM and AEX for system centric integration scenarios planned to be supported for EhP1 for SAP NetWeaver 7.3* * Current planning state, subject to change Example Portal Composite Apps. XSS Composite Apps. Portal Content BPM EP-Core SAP Consuming application services within human centric scenarios Reduced landscape complexity Less administration effort Joint usage of central Universal Worklist Direct access to user, group or role metadata of Portal No redundant portal capabilities Check landscape recomm. for SAP NetWeaver Portal Innovation speed of BPM and Portal to be synchronized Sizing to consider combined BPM and Portal usage Impact of licensing models to be considered Portal and BPM at least at SAP NetWeaver SAP AG. All rights reserved. 17 General Recommendation central BPM jointly deployed with central application portal If SAP NetWeaver Portal is used as central Portal within the system landscape, central BPM is jointly deployed with the portal system for human centric integration scenarios Deployment of ESR depends on main focused landscape scenario (see following slides) Joint deployment of BPM with AEX for system centric integration scenarios planned to be supported for EhP1 for SAP NetWeaver 7.3* Typical Technical Use Cases Business Process Composition for human centric integration scenarios Build simplified UIs on top of services of application systems Reduced landscape complexity Less administration effort by avoiding additional BPM system Joint usage of central Universal Worklist for BPM scenarios Direct access to user, group or role metadata within Portal for BPM workflow scenarios; role information can be uploaded from all connected SAP application backend systems into Portal via PFCG upload No redundant deployment of portal capabilities due to shared use in one system Consider definition and assumptions for application portal in the related landscape recommendations for SAP NetWeaver Portal Innovation speed of BPM and Portal has to be synchronized Sizing has to consider combined BPM and Portal usage Impact of licensing models have to be considered Portal and BPM needs to be at least at SAP NetWeaver 7.3

18 Slide 18 Deployment of Business Process Management Human Centric Integration Scenarios Reasonable Alternative Central BPM deployed as a separate system Remotely integrated with central SAP NetWeaver Portal Joint deployment of BPM and AEX for system centric integration scenarios planned to be supported for EhP1 for SAP NetWeaver 7.3* * Current planning state, subject to change Example Portal EPC Integrating BPM with central Portal Busines Process Management Composite App. BPM Easier scalability for high volume usage BPM usage does not impact portal performance BPM can run in faster innovation cycles than Portal SAP Consuming application services within human centric scenarios Higher landscape complexity Higher administration effort BPM to be integrated with Portal Redundantly deployed portal capabilities 2011 SAP AG. All rights reserved. 18 Reasonable Alternative central separate BPM system, remotely integrated with SAP Portal Central BPM deployed as a separate system BPM system neesd to be remotely integrated with central SAP NetWeaver Portal Deployment of ESR depends on main focused landscape scenario (see next slides) Joint deployment of BPM with AEX for system centric integration scenarios planned to be supported for EhP1 for SAP NetWeaver 7.3* Typical Technical Use Cases Business Process Composition for human centric integration scenarios Build simplified UIs on top of services of connected application systems Easier scalability for high volume BPM and Portal usage BPM usage does not impact portal performance BPM can run in faster innovation cycles than Portal Higher landscape complexity Higher administration effort for additional system BPM needs to be integrated with Portal Redundantly deployed portal capabilities within BPM and Portal system

19 Slide 19 Pure Process Integration Centric System Landscapes Typical Characteristics of this Landscape Setup Main use case to run A2A or B2B integration scenarios Process Integration ESR Content PI SLD PI Dual Stack Adv. Adapt. Engine Ext. ESR Content AEX SLD SAP NetWeaver PI used as integration broker Business process management based on PI ccbpm capabilities used optionally If no ccbpm usage required AEX used alternatively Business critical applications typically covered, including high availability needs Business process composition not in focus Improved version interoperability allowing decoupled software updates (starting with SAP Business Suite 7 and SAP NetWeaver 7.0) Main required SAP NetWeaver building blocks PI (dual stack), AEX (JAVA only) alternatively for certain use cases, SLD 2011 SAP AG. All rights reserved. 19 Landscape Characteristics: Main use case is to run process integration scenarios across different systems A2A: Integr. of internal systems to connect business activities and exchange information B2B: Integration of systems across company boundaries based on common standards SAP NetWeaver PI is used as integration broker to connect SAP and NON-SAP application systems Business process management based on ccbpm capabilities within PI used optionally If no ccbpm usage is required a JAVA-only based PI (Advanced Adapter Engine Extended AEX) could be used alternatively starting with SAP NetWeaver 7.3 System integration scenarios typically cover business critical applications High availability needs for SAP NetWeaver PI/AEX Business process composition not in focus Improved version interoperability to allow decoupled software updates starting with SAP Business Suite 7 and SAP NetWeaver 7.0 SAP Note (Version interoperability between SAP Business Suite and SAP NetWeaver) SAP Note (SAP Business Suite enablement of SAP NetWeaver 7.3) Main required SAP NetWeaver building blocks PI (dual stack), AEX (JAVA only) alternatively for certain use cases, SLD

20 Slide 20 Deployment of Enterprise Services Repository Process Integration Centric System Landscapes General Recommendation Shared usage of central Enterprise Services Repository & Services Registry within SAP NetWeaver PI Avoid setup of additional ESR systems in same solution landscape Example deployment of SAP Business Suite content to central ESR Process Integration ESR Content PI PI Dual Stack Central governance for service design & definition and central overview of published services Reduced landscape complexity Automated deployment of with PI Latest features of ESR directly leveraged by PI SAP Innovation speed of and PI to be synchronized 2011 SAP AG. All rights reserved. 20 General Recommendation single ESR used by central PI Shared usage of a central Enterprise Services Repository & Services Registry within the application solution landscape When focusing on A2A integration, connection to B2B networks or service provisioning and mediated message based communication use ESR & SR as part of SAP NetWeaver PI Avoid setup of additional ESR systems in the same solution landscape Typical Technical Use Cases A2A integration or connection to B2B networks by packaged integration (shipped ESR content) Design governance and service provisioning and mediated message based communications Central governance for service design & definition and central overview of published services Reduced landscape complexity Automated deployment of ESR & SR within PI Latest features of the Enterprise services repository can directly be leveraged by PI (same release) Requires SAP NetWeaver PI 7.1 and higher to get complete functionality Innovation speed of and PI have to be synchronized

21 Slide 21 Deployment of Enterprise Services Repository Process Integration Centric System Landscapes Possible Exception as part of SAP NetWeaver PI Multiple ESR systems triggered by multiple PI systems, one leading PI/ESR to be determined One central SR within the leading PI system Example PI PI Dual Stack SAP Business Unit 1 (PI domain 1) Leading ESR Process Integration ESR Content Manual content transports from leading ESR to local ESR for global content Process Integration ESR Content ESR PI PI Dual Stack Business Unit 2 (PI domain 2) Separation of PI systems due to organizational responsibilities Local development and service design Design governance more complicated One central SR within leading PI (should also contain the runtime SLD) ESR can not be connected to multiple PI systems No automatic federation between different ESRs Each application system only be connected to one single PI/ESR 2011 SAP AG. All rights reserved. 21 Possible Exception multiple ESR deployments with leading ESR When focusing on A2A integration, connection to B2B networks or service provisioning and mediated message based communication use ESR & SR as part of SAP NetWeaver PI Multiple ESR systems triggered by multiple PI systems, one leading ESR to be determined Use only one central SR within the leading PI system Typical Technical Use Case Integration centric scenarios with multiple PI systems for local Business or IT units Separation of PI systems due to organizational responsibilities Local development and service design Design governance becomes more complicated (should be mitigated by determining one organizational leading ESR for creating global content) Use one central SR within the leading PI (should also contain the runtime SLD) ESR can not be connected to multiple PI systems (only one PI connection can be maintained within ESR) No automatic federation between different ESRs, content has to be synchronized manually by transports; no back transports from PI 7.1/7.3 to PI 7.0 supported Each application system can only be connected to one single PI/ESR

22 Slide 22 Combined System Landscapes (PI and BPM) Typical Characteristics of this Landscape Setup Busines Process Management Composite Apps. Additional SAP NetWeaver BPM instance Adv. Adapt. Engine Ext. Process Integration ESR Content ESR Content AEX PI SLD SLD PI Dual Stack Process integration scenarios are dominating use case, Business Process Composition added for human centric integration scenarios SAP NetWeaver PI or AEX used as integration broker Business critical applications typically covered, including high availability needs for SAP NetWeaver PI/AEX Innovative business process extensions composed additionally Improved version interoperability allowing decoupled software updates (starting with SAP Business Suite 7 and SAP NetWeaver 7.0) Main required SAP NetWeaver building blocks PI (dual stack), AEX (JAVA only) alternatively, SLD BPM/CE 2011 SAP AG. All rights reserved. 22 Typical Characteristics of this Landscape Setup Process integration scenarios are the dominating use case (A2A and B2B connectivity) Business Process Composition will be added for human centric integration scenarios SAP NetWeaver PI or AEX used as integration broker to connect SAP and NON-SAP application systems System integration scenarios typically cover business critical applications High availability needs for SAP NetWeaver PI/AEX In addition new innovative business process extensions are composed Improved version interoperability to allow decoupled software updates starting with SAP Business Suite 7 and SAP NetWeaver 7.0 SAP Note (Version interoperability between SAP Business Suite and SAP NetWeaver) SAP Note (SAP Business Suite enablement of SAP NetWeaver 7.3) Main required SAP NetWeaver building blocks PI (dual stack), AEX (JAVA only) alternatively, SLD BPM/CE

23 Slide 23 Deployment of Enterprise Services Repository Combined System Landscapes General Recommendation Shared usage of central within SAP NetWeaver PI Central BPM/CE system using ESR within PI system Avoid setup of additional ESR systems in same solution landscape Example Central BPM in Portal XSS Composite Apps. Portal Content BPM EP Core central BPM system remotely connected to central PI Process Integration ESR Content Reduced risk for PI-based scenarios PI scenarios not to be reconfigured Integration of non-webservice based legacy systems via PI system SAP PI PI Dual Stack Innovation speed of ESR and PI to be synchronized Use central SR jointly deployed with ESR in PI system 2011 SAP AG. All rights reserved. 23 General Recommendation single PI ESR used by central PI and central BPM Shared usage of a central Enterprise Services Repository & Services Registry within the application solution landscape Use as part of SAP NetWeaver PI since BPM and ESR are only loosely coupled Configure central BPM/CE system for using ESR within PI system Avoid setup of additional ESR and SR systems in the same solution landscape Typical Technical Use Cases A2A integration or connection to B2B networks Central service definition & mediation and business process composition Reduced risk for PI-based scenarios since existing close architectural coupling of PI and ESR is not touched PI scenarios do not need to be reconfigured Integration of non-webservice based NON-SAP legacy systems via PI system possible Requires SAP NetWeaver PI 7.1 or higher to get complete ESR functionality Innovation speed of ESR and PI have to be aligned Avoid using SR in BPM system, use central SR jointly deployed with ESR within PI system

24 Slide 24 Deployment of Enterprise Services Repository Combined System Landscapes Reasonable Alternative Shared usage of central within SAP NetWeaver PI Multiple BPM/CE systems remotely connected against single ESR Avoid setup of additional ESR systems in same solution landscape Busines Process Management Composite App. BPM SAP Business Unit 1 Example Local BPM/CE systems remotely connected to central PI Process Integration ESR Content PI PI Dual Stack Leading ESR UI/Service Composition Composite App. CE Local composition based on different business units Central service design and governance Central overview of published services Central A2A or B2B integration and mediated communication systems only connected to one ESR and publish service to one SR Automatic federation of local SRs in the BPM/CE systems to central SR not supported Business Unit SAP AG. All rights reserved. 24 Reasonable Alternative single PI ESR used by central PI and local BPM/CE systems Shared usage of a central Enterprise Services Repository & Services Registry within the application solution landscape Use as part of SAP NetWeaver PI since BPM and ESR are only loosely coupled Multiple BPM/CE systems can be remotely connected against single ESR within PI system Avoid setup of additional ESR and SR systems in the same solution landscape Typical Technical Use Cases A2A integration or connection to B2B networks Central service definition & mediation within local consumption environments Separation of local composition based on different business units Central service design and governance Central overview of published services Central A2A or B2B integration and mediated communication systems can only be connected to one ESR and publish service to one SR Automatic federation of local SRs in the BPM/CE systems to a central SR not supported

25 Slide 25 Deployment of Enterprise Services Repository Combined System Landscapes Possible Exception Shared usage of within central BPM system Central PI system reconfigured to use remote BPM ESR ESR content only maintained within central BPM ESR Busines Process Management Composite App. BPM Example central PI system remotely connected to central BPM Newest ESR tools consumed by BPM without need to touch PI system Integration of non-webservice based legacy systems via PI system SAP Process Integration PI PI Dual Stack locally deployed, but not used PI system still contains (unused) technically deployed ESR PI need to be reconfigured for remote usage of ESR Existing ESR content needs to be moved to new ESR Potential version dependencies between PI and ESR to be checked Use central SR jointly deployed with ESR in BPM system BPM ESR >= SAP NetWeaver SAP AG. All rights reserved. 25 Possible Exception single BPM ESR used by central PI and BPM Shared usage of a central within the application solution landscape as part of central BPM system used, if high innovation speed for ESR required Central PI system reconfigured to use remote BPM ESR ESR content only maintained within central BPM ESR Typical Technical Use Cases: A2A integration or connection to B2B networks Central service definition & mediation and business process composition Newest ESR tools can be consumed by BPM without need to touch PI system Integration of non-webservice based legacy systems via PI system PI system still contains (unused) technically deployed ESR PI need to be reconfigured for remote usage of ESR Existing PI ESR content needs to be moved to new BPM ESR Potential version dependencies between PI and ESR need to be checked Avoid using SR in PI system, use central SR jointly deployed with ESR within BPM system Remote ESR configuration for PI requires SAP NetWeaver BPM ESR to be at least SAP NetWeaver 7.2

26 Slide 26 Business Process Composition Centric System Landscapes Typical Characteristics of this Landscape Setup Business Process Composition is dominating use case Busines Process Management Composite Apps. BPM Additional SAP NetWeaver instance Existing business processes extended for end-user Innovative business process extensions composed Process integration scenarios managed by point-to-point connections or NON-SAP integration broker Main required SAP NetWeaver building blocks BPM/CE 2011 SAP AG. All rights reserved. 26 Typical Characteristics of this Landscape Setup Business Process Composition is the dominating use case Existing business processes shall be extended for end-user New innovative business process extensions are composed Process integration scenarios across different application systems are managed by point-topoint connections or NON-SAP integration broker (meaning no SAP NetWeaver PI system part of system landscape) Main required SAP NetWeaver building blocks BPM/CE

27 Slide 27 Deployment of Enterprise Services Repository Business Process Composition Centric Landscapes General Recommendation Shared usage of central jointly deployed with central BPM/CE Avoid setup of additional ESR systems in same solution landscape Example Central BPM in Portal Portal Content EP Core services of application backend systems defined within central ESR Composite Apps. Composite Apps. BPM Central governance for service design & definition and central overview of published services Reduced landscape complexity Easy deployment of within BPM/CE Latest ESR tool features directly leveraged by BPM/CE SAP Innovation speed of ESR and BPM/CE to be synchronized ESR only required for BPM design time environment, SR also required for production environment 2011 SAP AG. All rights reserved. 27 General Recommendation Single ESR jointly deployed with central BPM) Shared usage of a central Enterprise Services Repository & Services Registry within the application solution landscape Use jointly deployed with central BPM/CE Avoid setup of additional ESR systems in the same solution landscape Typical Technical Use Case Central service definition for human centric integration scenarios Central governance for service design & definition and central overview of published services Reduced landscape complexity Easy deployment of within BPM/CE Latest ESR tool features can directly be leveraged by BPM/CE Innovation speed of ESR and BPM/CE have to be aligned ESR only required for BPM design time environment, SR also required for production environment

28 Slide 28 Deployment of Enterprise Services Repository Business Process Composition Centric Landscapes Reasonable Alternative Shared usage of central jointly deployed with single BPM Additional BPM/CE systems remotely connected against central ESR Only one central SR used Example Busines Process Management Composite App. BPM Local CE system remotely connected to central BPM UI/Service Composition Composite App. Local composition for different business units Central service design and governance Central overview of published services Services consumed across business units CE SAP Business Unit 1 Business Unit 2 systems only publish services to one SR systems only connected to one ESR ESR only required for BPM design time environment, SR also required for production environment 2011 SAP AG. All rights reserved. 28 Reasonable Alternative Single ESR, used by multiple BPM/CE systems Shared usage of a central Enterprise Services Repository & Services Registry within the application solution landscape Use jointly deployed with single BPM system Additional BPM/CE systems can be remotely connected against central ESR Only one central SR used Typical Technical Use Cases Consumption of SAP or NON-SAP services within local business units Central service governance Local composition for different business units Central service design and governance Central overview of published services Services can be consumed across business units systems can only publish services to one SR systems can only be connected to one ESR ESR only required for BPM design time environment, SR also required for production environment

29 Slide 29 Enhanced Landscape Setups Additional Aspects for SAP NetWeaver Process Integration Based System Landscapes

30 Slide 30 Distributed Advanced Adapter Engines Central PI with distributed Advanced Adapter Engines Central SAP NetWeaver PI approach across distributed regions Centralized governance and local message processing Central Integration can be bypassed Example Remote access to central PI ESR Local Advanced Adapter Engine AAE Process Integration ESR Content PI PI Dual Stack Remote access to central PI ESR Local Advanced Adapter Engine AAE Centralized governance, maintenance and monitoring De-coupled runtimes and distributed load Significant performance advantage Reduced message travel time and reduced network load in global networks Increased availability Local AAEs serve local business needs SAP Business Location 1 Business Location 2 Check supported adapters in adapter engine ccbpm scenarios require central PI runtime Aligning software versions of AAEs and central PI 2011 SAP AG. All rights reserved. 30 Central PI with distributed local Advanced Adapter Engines Supporting central SAP NetWeaver PI approach across geographically distributed regions Combining centralized governance with local message processing Central Integration can be bypassed (starting with SAP NetWever PI 7.1) Typical Technical Use Cases Local processing of messages Manual switch-over scenarios between different AAEs during software maintenance activities Centralized governance, maintenance and monitoring De-coupled runtimes and distributed load Significant performance advantage Reduced message travel time and reduced network load in global networks Increased availability Local AAEs can serve local business needs Scenarios limited to supported adapters in adapter engine ccbpm scenarios require central PI runtime Aligning software versions of AAEs and central PI Local AAEs could be on a lower software version than central PI to avoid lock situations However SAP recommends to keep local AAEs and central PI on the same version

31 Slide 31 Related Building Blocks Recommendations for Deployment of System Landscape Directory

32 Slide 32 Deployment of System Landscape Directory (SLD) Solution Manager 7.0 General Recommendation Central runtime SLD in addition to Solution Manager SLD Runtime SLD ensures ongoing availability for accessing SLD data, required by certain scenarios Runtime SLD deployed within a central high available SAP Netweaver system Example for Solution Manager 7.0 Central Solution Manager SLD SAP Solution Manager Solution Manager SLD synchronization between central runtime SLD and central Solution Manager SLD Portal EPC h Central Runtime SLD Process Integration PI Increased availability for critical use cases at low expense for additional operation effort + cost Clear separation between management system and managed systems SLD Dual Stack Solution Manager 7.0 or lower SLD PI Dual Stack SLD data suppliers of all SAP systems register against central runtime SLD SAP Data consistency has to be ensured Details in SLD planning guide 2011 SAP AG. All rights reserved. 32 General Recommendation Setup of central runtime SLD in addition to Solution Manager SLD to improve availability of SLD access for productive system landscape If customer uses SAP NetWeaver PI or Web Dynpro Java, a runtime SLD is required to ensure ongoing availability for accessing SLD data Runtime SLD is deployed within a central high available SAP Netweaver system (e.g. PI) Typical Technical Use Cases Central storage of information about all systems belonging to the solution landscape Setup of dedicated runtime SLD to compensate SLD high availability needs (triggered by certain scenarios like Web Dynpro Java applications based on arfc or SAP NetWeaver PI) Increased availability for critical use case at low expense for additional operation effort + cost Clear separation between management system + managed systems possible with central SLD in SAP Solution Manager and additional central runtime SLD Data consistency has to be ensured (data synchronization between different SLDs have to be configured) Details described in SLD planning guide

33 Slide 33 Deployment of System Landscape Directory Solution Manager 7.1 General Recommendation Central runtime SLD to improve availability of SLD access Runtime SLD deployed within central SAP Netweaver PI or SAP NetWeaver Portal system Starting with Solution Manager 7.1 local SLD can be replaced by LMDB Example for Solution Manager 7.1 SAP Solution Manager Solution Manager Central SLD provides content to Solution Manager LMDB Portal EPC h Central SLD Process Integration PI Increased availability for critical use case at low expense for additional operation effort + cost New LMDB in Solution Manager 7.1 can replace local SLD LMDB Dual Stack Solution Manager 7.1 SLD data suppliers of all SAP systems register against central runtime SLD SAP SLD PI Dual Stack Data synchronization between SLD and SAP Solution Manager LMDB to be configured Details in SLD planning guide and SAP Solution Manager setup guide 2011 SAP AG. All rights reserved. 33 General Recommendation Setup of central runtime SLD to improve availability of SLD access for prod. system landscape Runtime SLD can be deployed within the central SAP Netweaver PI or SAP NetWeaver Portal system Starting with Solution Manager 7.1 the Solution Manager SLD can be replaced by local -based LMDB Typical Technical Use Cases: Central storage of information about all systems belonging to the solution landscape Setup of dedicated runtime SLD to compensate SLD high availability needs (triggered by certain scenarios like Web Dynpro Java applications based on arfc or SAP NetWeaver PI) Increased availability for critical use case at low expense for additional operation effort + cost By using new Solution Manager LMDB the SLD within Solution Manager can be replaced Data synchronization between SLD and SAP Solution Manager LMDB has to be configured Details described in SLD planning guide and SAP Solution Manager setup guide

34 Slide 34 Deployment of System Landscape Directory Reasonable Alternative Central standalone SLD in addition to Solution Manager SLD Runtime SLD ensures ongoing availability for accessing SLD data, required by certain scenarios Standalone SLD can also serve as central master if multiple SLDs in use Example SLD synchronization between central SLD and local SLD/LMDB SAP Solution Manager Solution Manager SLD/LMDB Dual Stack Solution Manager with local SLD/LMDB Central SLD Standalone SLD SLD 7.3 SLD data suppliers of all SAP systems register against central SLD SAP Portal EPC h Process Integration PI h Increased availability for critical use case Independent innovation speed for SLD due to latest SLD version based on SAP NetWeaver 7.1 or 7.3 Additional system just for SLD capabilities Complex landscapes with multiple SLDs and large numbers of managed systems 2011 SAP AG. All rights reserved. 34 Reasonable Alternative Setup of central standalone SLD in addition to Solution Manager SLD to improve availability of SLD access for productive system landscape If customer uses SAP NetWeaver PI or Web Dynpro Java, a runtime SLD is required to ensure ongoing availability for accessing SLD data Standalone SLD can also serve as central master if multiple SLDs are in use Typical Technical Use Case Central storage of information about all systems within a complex solution landscape Increased availability for critical use case Independent innovation speed for SLD due to latest SLD version based on SAP NetWeaver 7.1 or 7.3 SLD content synchronization with other SLDs in landscape Continuous availability during maintenance events possible SLD instance cache can be used in a cluster to improve access performance Notification of changes between SLD and SolMan LMDB (other variant: delay of max 10 min due to polling) Additional system just for SLD capabilities More complex landscape with multiple SLDs and large numbers of managed systems

35 Slide 35 Deployment of System Landscape Directory Plain System Landscapes Solution Manager 7.0 General Recommendation Shared usage of SLD to provide a central access for all SLD clients Data suppliers ( and JAVA based systems) report to central SLD SLD deployed in central SAP Solution Manager system Central SLD SAP Solution Manager Solution Manager Example for Solution Manager 7.0 BEx Web Easy setup Low administration effort No redundancy Consistent storage for all systems SLD Dual Stack SLD data suppliers of all SAP systems register against central SLD SAP BI JAVA Data Warehouse System BW Later scale-out to additional runtime SLD requires redirecting of all SLD clients Not applicable, if runtime dependencies to SLD for certain scenarios exist Data of all systems visible/accessible within SLD 2011 SAP AG. All rights reserved. 35 General Recommendation (plain system landscapes) Shared usage of System Landscape Directory (SLD) to provide a central access for all SLD clients Data suppliers ( and JAVA based systems) report to central SLD SLD is deployed in the central SAP Solution Manager system to simplify landscape setups, if high availability of SLD access is not required Typical Technical Use Case Central storage of information about all systems belonging to the solution landscape scenarios with high availability needs for SLD access as described before are not in use Easy setup (one SLD for complete system landscape) Low administration effort No redundancy Consistent storage of landscape data for all systems belonging to the landscape Later scale-out to additional runtime SLD requires redirecting of all SLD clients Not applicable, if runtime dependencies to SLD for certain scenarios exist (e.g. SAP NetWeaver PI, Adaptive RFC based scenarios like ESS) Data of all systems visible/accessible within SLD

36 Slide 36 Deployment of System Landscape Directory Plain System Landscapes Solution Manager 7.1 General Recommendation Shared usage of SLD to provide a central access for all SLD clients Data suppliers ( and JAVA based systems) report to central SLD SLD deployed in the central SAP Solution Manager system in addition to LMDB Central SLD & Solution Manager LMDB SAP Solution Manager Solution Manager LMDB SLD Dual Stack Solution Manager 7.1 Example for Solution Manager 7.1 Central SLD provides content to Solution Manager LMDB SLD data suppliers of all SAP systems register against central SLD SAP BEx Web BI JAVA Data Warehouse System BW Easy setup Low administration effort Consistent storage of landscape data Later scale-out to additional runtime SLD requires redirecting of all SLD clients Not applicable, if runtime dependencies to SLD for certain scenarios exist Data of all systems visible/accessible within SLD Local SLD required in addition to LMDB providing content for LMDB 2011 SAP AG. All rights reserved. 36 General Recommendation (plain system landscapes) Shared usage of System Landscape Directory (SLD) to provide a central access for all SLD clients Data suppliers ( and JAVA based systems) report to central SLD SLD is deployed in the central SAP Solution Manager system in addition to LMDB to simplify landscape setups, if high availability of SLD access is not required Typical Technical Use Case Central storage of information about all systems belonging to the solution landscape Easy setup (one SLD for complete system landscape) Low administration effort No redundancy Consistent storage of landscape data for all systems belonging to the landscape Later scale-out to additional runtime SLD requires redirecting of all SLD clients Not applicable, if runtime dependencies to SLD for certain applications exist (e.g. SAP NetWeaver PI, Adaptive RFC based scenarios like ESS) Data of all systems visible/accessible within SLD Local SLD required in addition to LMDB providing content for LMDB

37 Slide 37 Additional Information Using Advanced Adapter Engine Extended: SLD planning guide Blog: Blog: SAP AG. All rights reserved. 37

38 Slide 38 Thank You! Dirk Anthony TIP Governance Architecture Excellence SAP System Landscape Governance Board SAP AG Dietmar-Hopp-Allee Walldorf Germany Phone +49/6227/ Fax +49/6227/