Slide 1
System Landscape Recommendations for SAP
NetWeaver 7.3 – Process Centric Capabilities
Dirk Anthony, SAP AG
June 2011
Slide 2
© 2011 SAP AG. All rights reserved. 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in
making a purchase decision. This presentation is not subject to your license agreement
or any other agreement with SAP. SAP has no obligation to pursue any course of
business outlined in this presentation or to develop or release any functionality
mentioned in this presentation. This presentation and SAP's strategy and possible future
developments are subject to change and may be changed by SAP at any time for any
reason without notice. This document is provided without a warranty of any kind, either
express or implied, including but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no
responsibility for errors or omissions in this document, except if such damages were
caused by SAP intentionally or grossly negligent.
Slide 3
© 2011 SAP AG. All rights reserved. 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
Slide 4
IntroductionMethodology & Scope of Landscape Recommendations
Slide 5
© 2011 SAP AG. All rights reserved. 5
SAP Business Suite Reference LandscapeBaseline For Governance Measures
Architectural
Guidelines
Ease
Landscape
Management
Improve
Product
Capabilities
Landscape
Standards
Ease
Landscape
Planning
Manage
Exceptions
SAP‘s internal
Development &
Test Landscape
SAP System Landscape Governance Board:
Central unit within SAP to trigger and monitor concrete landscape
related improvements across SAP products
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution Mng
Component
AS ABAP
ECC
Server
SAP ERP
ABAP
ERP
Components
AS ABAP
SRM
Server
SAP SRM
ABAP
SRM
Components
AS ABAP
SCM
Server
SAP SCM
ABAP
SCM
Components
AS ABAP
CRM
Server
SAP CRM
ABAP
CRM
Components
BW
AS ABAP
Business Warehouse
SEM
Central BI
Content
ABAP
EP
AS JAVA
BEx Web
JEE
BI JAVA
BICS
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
SolMan Content
SAP NetWeaver Hubs
SAP Business Suite
Backend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
Portal
Content
ADOBE
Slide 6
© 2011 SAP AG. All rights reserved. 6
Technical Deployment of SAP NetWeaverFoundation Capabilities
Definition for Dual Stack:
SAP system containing Application Server ABAP and Application Server Java
A dual-stack system has the following characteristics:
• Common SID for all application servers and the database
• Common startup framework
• Common database (with different schemas for ABAP and Java)
Options for implementing the technology foundation of SAP NetWeaver
• ABAP single stack system
• JAVA single stack system
• Dual stack system (not recommended any longer, where not technically required)
Legend
SAP system with
own database
used platform
technology
Rolemain role of this
system
ABAP
Examples:
BW incl. BEx Web
ABAP
BWABAP JEE
BI JAVAJEE
Optional Dual stack
(technically not req.)
ABAP
single stack
ECC
Server
SAP ERP
Backend
ABAP
JAVA
single stack
EP Core
Application
Portal
JEE
Mandatory
Dual stack
(technically req.)
PI
Process
Integration
ABAP
JEE
Definition for Dual Stack: SAP system that contains installations of both Application Server ABAP and Application Server Java A dual-stack system has the following characteristics: • Common SID for all application servers and the database • Common startup framework • Common database (with different schemas for ABAP and Java)
Slide 7
© 2011 SAP AG. All rights reserved. 7
Technical Deployment of SAP NetWeaverIntegration Capabilities
Examples:
Options for implementing integration capabilities of SAP NetWeaver
• Embedded deployment within an SAP Business Suite system
• Deployed as a local “sidecar” system to an SAP Business Suite system
• Deployed as a central hub system shared by different SAP Business Suite systems
SAP NetWeaver Portal deployed as a
central hub shared by an
SAP ERP and an SAP SRM system
* only to support
existing setups
SAP ERP
ABAP
ECCABAP JEE
EP CoreJEE
XSSHCM
SAP NetWeaver Portal
technically deployed within
the SAP ERP system*
SAP NetWeaver Portal deployed as a
local sidecar to an SAP ERP system
EP Core
ERP Portal
JEE
XSS
ECC
SAP ERP
Backend
ABAP
HCMSRM
SAP SRM
Backend
ABAP
ECC
SAP ERP
Backend
ABAP
EP Core
JEE
XSS
SRM
Content
Application
Portal
Slide 8
© 2011 SAP AG. All rights reserved. 8
Deployment Of SAP Products Within A Solution LandscapeArchitectural Decisions
Centrally Shared
• Reuse of platform capabilities within a central system
Local Redundant Use
• Individual usage by multiple local systems
Jointly Deployed
• Less landscape complexity by using different capabilities in the same system
Separately Deployed
• Higher flexibility by separating systems
Integrated Technology
Stacks
• Combined usage of duties by multi stack system
Separated Technology Stacks
• Separation of duties by separated technology stacks
Distribution of deployable product components
Deploy product
components
Slide 9
© 2011 SAP AG. All rights reserved. 9
Ease Landscape Setups By Stronger Guidance Used Methodology
Option IOption II
Option
III
Clear recommendations by categorization of deployment options
General Recommendation
Best choice for majority of typical
landscape use cases
Recommended by SAP’s strategy
Accepted by a wide base of
customersReasonable Alternative
Useful choice for certain use
cases or customer scenarios
Supported and confirmed by
SAP’s strategy
Possible Exception
Only useful for specific use cases
Supported by SAP, but limitations
might occur
Outlining main important aspects
Optimal trade-off between flexibility and simplicity
Applied to main building blocks of SAP products
Alternative deployment options might have different benefits
Customer individual assessment not be compensated
Goal
Consider
Slide 10
© 2011 SAP AG. All rights reserved. 10
Scope of Landscape Recommendations (1/2)Building Blocks in System Landscapes for Process Centric Capabilities
Considered main building blocks SAP NetWeaver Process Integration (dual stack)
Advanced Adapter Engine Extended (JAVA only)
Enterprise Services Repository & Services Registry
System Landscape Directory
Considered main usage scenarios A2A connectivity:
Integration of internal systems
B2B connectivity: Integration of systems across company boundaries
JEE
SAP system with
own database
available platform
technology
Rolemain role of this
system
AS JAVA
Decentral Advanc.
Adapter Engine
JEE
Advanced
Adapt. Engine
JAVA
AEX
Process Integration -
AEX
JEE
ESR&SR
Advanced
Adapt. Engine
SLD
Content
ABAP
PI Dual Stack
Process Integration - PI
Integration
Engine
ABAPJAVA
JEE
Advanced
Adapt. Engine
ccBPM
Engine
SLD
ESR&SR
Content
Considered main building blocks SAP NetWeaver Process Integration (PI - dual stack) Advanced Adapter Engine Extended (AEX - JAVA only) Enterprise Services Repository & Services Registry (ESR&SR) 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
Slide 11
© 2011 SAP AG. All rights reserved. 11
Scope of Landscape Recommendations (2/2)Building Blocks in System Landscapes for Process Composition
Considered main building blocks Business Process Management (BPM)
Including Business Rules Management (BRM)
Based on Composition Environment Platform and Composition Application 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
JEE
SAP system with
own database
available platform
technology
Rolemain role of this
system
BPM
incl. BRM
AS JAVA
Business Process Management
COMP-ENV
CE-APPS
JEE
Composite App.
Additional
SAP NetWeaver
instance
Java-based
SAP Instance
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 Application 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
Slide 12
Basic Landscape SetupsRecommendations for SAP NetWeaver Process Integration and Business Process
Management Deployments
Slide 13
© 2011 SAP AG. All rights reserved. 13
Deployment of SAP NetWeaver Process IntegrationPI 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
Benefits 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
Example
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEE
Integrating
applications of
different backend
systems
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) Benefits •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
Slide 14
© 2011 SAP AG. All rights reserved. 14
Deployment of SAP NetWeaver Process IntegrationPI dual stack system
Possible Exception
Separation of local Business or IT units by multiple PI domains
Avoid embedded deployment within the application backend systems
Benefits Separation of PI systems due to
organizational responsibilities
Local development and service design
Considerations 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
Example
Application
Backend
NON SAP
Application
SCM
Server
SAP SCM
Backend
ABAP
ECC
Server
SAP ERP
Backend
ABAP
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Manual
synchronization
of PI content
Business Unit 1
(PI domain 1)
Business Unit 2
(PI domain 2)
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEE
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEE
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) Benefits •Separation of PI systems due to organizational responsibilities •Local development and service design Considerations •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
Slide 15
© 2011 SAP AG. All rights reserved. 15
Deployment of SAP NetWeaver Process IntegrationAdvanced Adapter Engine Extended (AEX)
Landscape Setups for AEX
Lean JAVA-based integration broker without business process management capabilities
ESR&SR 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
Benefits Lean pure JAVA based deployment of middleware
Less complex system architecture
Central governance, monitoring and administration
Considerations 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 SP2
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
Integrating
applications of
different backend
systems
AEX
AS JAVA
ESR&SR
ESR Content
JEE
Advanced Adapter
Engine Extended
Example
* Current planning state, subject to change
Landscape Setups for AEX •AEX is a lean JAVA-based integration broker without business process management capabilities •ESR&SR 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 1573180 Benefits •Lean pure JAVA based deployment of middleware •Less complex system architecture •Central governance, monitoring and administration Considerations •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
Slide 16
© 2011 SAP AG. All rights reserved. 16
Deployment of Business Process ManagementHuman Centric Integration Scenarios
General Recommendation
Central system for human centric integration scenarios
If no SAP Application 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
Benefits Less complex system landscape
Centrally governed and administrated composition of business processes
Less operations effort
Considerations 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
Example
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
AS JAVAJEE
BPM
Composite Apps.
Busines Process Management
Additional
SAP NetWeaver
instance
(optional)
Consuming application
services within human
centric scenarios
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 Application 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 Benefits •Less complex system landscape •Centrally governed and administrated composition of business processes •Less operations effort by avoiding multiple local BPM or CE systems Considerations •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)
Slide 17
© 2011 SAP AG. All rights reserved. 17
Deployment of Business Process ManagementHuman Centric Integration Scenarios
General Recommendation
If SAP NetWeaver Portal used as central Application 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*
Benefits 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
Considerations 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 7.3
* Current planning state, subject to change
Example
EP-Core
AS JAVA
Application Portal
JEE
Portal ContentBPM
Composite Apps.
Composite Apps.
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Consuming application
services within human
centric scenarios
XSS
SCM
Server
SAP SCM
Backend
ABAP
General Recommendation central BPM jointly deployed with central application portal If SAP NetWeaver Portal is used as central Application 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 Benefits 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 Considerations 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
Slide 18
© 2011 SAP AG. All rights reserved. 18
AS JAVA
Busines Process
Management
JEE
BPM
Composite App.
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
Consuming application
services within human
centric scenarios
Integrating BPM with
central Application Portal
EPC
Application
Portal
JEE
Deployment of Business Process ManagementHuman 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*
Benefits Easier scalability for high volume usage
BPM usage does not impact portal performance
BPM can run in faster innovation cycles than Portal
Considerations Higher landscape complexity
Higher administration effort
BPM to be integrated with Application Portal
Redundantly deployed portal capabilities
* Current planning state, subject to change
Example
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 Benefits •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 Considerations •Higher landscape complexity •Higher administration effort for additional system •BPM needs to be integrated with Application Portal •Redundantly deployed portal capabilities within BPM and Portal system
Slide 19
© 2011 SAP AG. All rights reserved. 19
Pure Process Integration Centric System LandscapesTypical Characteristics of this Landscape Setup
Main use case to run A2A or B2B integration scenarios
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
ESR&SR, SLD
AEX
AS JAVA
Adv. Adapt. Engine Ext.
JEE
ESR&SR
ESR Content
SLD
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
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 1388258 (Version interoperability between SAP Business Suite and SAP NetWeaver)
• SAP Note 1468349 (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 • ESR&SR, SLD
Slide 20
© 2011 SAP AG. All rights reserved. 20
Deployment of Enterprise Services RepositoryProcess Integration Centric System Landscapes
General Recommendation
Shared usage of central Enterprise Services Repository & Services Registry
ESR&SR within SAP NetWeaver PI
Avoid setup of additional ESR systems in same solution landscape
Benefits Central governance for service design &
definition and central overview of published services
Reduced landscape complexity
Automated deployment of ESR&SR with PI
Latest features of ESR directly leveraged by PI
Considerations Innovation speed of ESR&SR and PI to be
synchronized
Example
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
deployment of SAP
Business Suite
content to
central ESRPI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
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 Benefits •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) Considerations •Requires SAP NetWeaver PI 7.1 and higher to get complete ESR&SR functionality •Innovation speed of ESR&SR and PI have to be synchronized
Slide 21
© 2011 SAP AG. All rights reserved. 21
Deployment of Enterprise Services RepositoryProcess Integration Centric System Landscapes
Possible Exception
ESR&SR 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
Benefits Separation of PI systems due to organizational
responsibilities
Local development and service design
Considerations 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
Example
Application
Backend
NON SAP
Application
SCM
Server
SAP SCM
Backend
ABAP
ECC
Server
SAP ERP
Backend
ABAP
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Manual content
transports from
leading ESR to
local ESR for
global content
Business Unit 1
(PI domain 1)
Business Unit 2
(PI domain 2)
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR
ESR Content
Leading ESR
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 Benefits •Separation of PI systems due to organizational responsibilities •Local development and service design Considerations •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
Slide 22
© 2011 SAP AG. All rights reserved. 22
Combined System Landscapes (PI and BPM)Typical Characteristics of this Landscape Setup
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
ESR&SR, SLD
BPM/CE
AS JAVAJEE
BPM
Composite Apps.
Busines Process Management
Additional
SAP NetWeaver
instance
AEX
AS JAVA
Adv. Adapt. Engine Ext.
JEE
ESR&SR
ESR Content
SLDPI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
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 1388258 (Version interoperability between SAP Business Suite and SAP NetWeaver)
• SAP Note 1468349 (SAP Business Suite enablement of SAP NetWeaver 7.3) Main required SAP NetWeaver building blocks •PI (dual stack), AEX (JAVA only) alternatively •ESR&SR, SLD •BPM/CE
Slide 23
© 2011 SAP AG. All rights reserved. 23
Deployment of Enterprise Services RepositoryCombined System Landscapes
General Recommendation
Shared usage of central ESR&SR within SAP NetWeaver PI
Central BPM/CE system using ESR within PI system
Avoid setup of additional ESR systems in same solution landscape
Benefits Reduced risk for PI-based scenarios
PI scenarios not to be reconfigured
Integration of non-WebService based legacy systems via PI system
Considerations Innovation speed of ESR and PI to be
synchronized
Use central SR jointly deployed with ESR in PI system
Example
Application
Backend
NON SAP
Application
central BPM system
remotely connected to
central PI ESR&SR
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
EP Core
AS JAVA
Central BPM in Application Portal
JEE
Portal ContentBPM
Composite Apps.XSS
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 ESR&SR 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 Benefits •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 Considerations •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
Slide 24
© 2011 SAP AG. All rights reserved. 24
Deployment of Enterprise Services RepositoryCombined System Landscapes
Reasonable Alternative
Shared usage of central ESR&SR within SAP NetWeaver PI
Multiple BPM/CE systems remotely connected against single ESR
Avoid setup of additional ESR systems in same solution landscape
Benefits 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
Considerations Application 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
Example
AS JAVA
UI/Service
Composition
JEE
CE
Composite App.
AS JAVA
Busines Process
Management
JEE
BPM
Composite App.
Application
Backend
NON SAP
Application
SCM
Server
SAP SCM
Backend
ABAP
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Business Unit 1
Business Unit 2
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
Leading ESR
Local BPM/CE systems
remotely connected to
central PI ESR&SR
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 ESR&SR 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 Benefits •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 Considerations •Application 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
Slide 25
© 2011 SAP AG. All rights reserved. 25
Deployment of Enterprise Services RepositoryCombined System Landscapes
Possible Exception
Shared usage of ESR&SR within central BPM system
Central PI system reconfigured to use remote BPM ESR
ESR content only maintained within central BPM ESR
Benefits Newest ESR tools consumed by BPM without need
to touch PI system
Integration of non-WebService based legacy systems via PI system
Considerations
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 7.2
Example
Application
Backend
NON SAP
Application
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEE
ESR&SRlocally deployed,
but not used
AS JAVA
Busines Process
Management
JEE
BPM
Composite App.
ESR&SR
central PI system
remotely connected to
central BPM ESR&SR
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
Possible Exception •single BPM ESR used by central PI and BPM •Shared usage of a central ESR&SR within the application solution landscape •ESR&SR 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 Benefits •Newest ESR tools can be consumed by BPM without need to touch PI system •Integration of non-WebService based legacy systems via PI system Considerations •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
Slide 26
© 2011 SAP AG. All rights reserved. 26
Business Process Composition Centric System LandscapesTypical Characteristics of this Landscape Setup
Business Process Composition is dominating use case
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
ESR&SR
AS JAVAJEE
Composite Apps.
Busines Process Management
Additional
SAP NetWeaver
instance
BPM
ESR&SR
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-to-point connections or NON-SAP integration broker (meaning no SAP NetWeaver PI system part of system landscape) Main required SAP NetWeaver building blocks •BPM/CE •ESR&SR
Slide 27
© 2011 SAP AG. All rights reserved. 27
Deployment of Enterprise Services RepositoryBusiness Process Composition Centric Landscapes
General Recommendation
Shared usage of central ESR&SR jointly deployed with central BPM/CE
Avoid setup of additional ESR systems in same solution landscape
Benefits Central governance for service design & definition
and central overview of published services
Reduced landscape complexity
Easy deployment of ESR&SR within BPM/CE
Latest ESR tool features directly leveraged by BPM/CE
Considerations Innovation speed of ESR and BPM/CE to be
synchronized
ESR only required for BPM design time environment, SR also required for production environment
Example
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
services of application
backend systems defined
within central ESR
EP Core
AS JAVA
Central BPM in Application Portal
JEE
Portal Content
Composite Apps.Composite Apps.
BPM
ESR&SR
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 ESR&SR 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 Benefits •Central governance for service design & definition and central overview of published services •Reduced landscape complexity •Easy deployment of ESR&SR within BPM/CE •Latest ESR tool features can directly be leveraged by BPM/CE Considerations •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
Slide 28
© 2011 SAP AG. All rights reserved. 28
Deployment of Enterprise Services RepositoryBusiness Process Composition Centric Landscapes
Reasonable Alternative
Shared usage of central ESR&SR jointly deployed with single BPM
Additional BPM/CE systems remotely connected against central ESR
Only one central SR used
Benefits Local composition for different business units
Central service design and governance
Central overview of published services
Services consumed across business units
Considerations Application systems only publish services to
one SR
Application systems only connected to one ESR
ESR only required for BPM design time environment, SR also required for production environment
Example
Application
Backend
NON SAP
Application
Business Unit 1
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Business Unit 2
AS JAVA
Busines Process
Management
JEE
BPM
Composite App.
ESR&SR
SCM
Server
SAP SCM
Backend
ABAP
Local CE system
remotely connected to
central BPM ESR&SR
AS JAVA
UI/Service
Composition
JEE
CE
Composite App.
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 ESR&SR 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 Benefits •Local composition for different business units •Central service design and governance •Central overview of published services •Services can be consumed across business units Considerations •Application systems can only publish services to one SR •Application systems can only be connected to one ESR •ESR only required for BPM design time environment, SR also required for production environment
Slide 29
Enhanced Landscape SetupsAdditional Aspects for SAP NetWeaver Process Integration Based System
Landscapes
Slide 30
© 2011 SAP AG. All rights reserved. 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 Server can be bypassed
Benefits 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
Considerations Check supported adapters in adapter engine
ccBPM scenarios require central PI runtime
Aligning software versions of AAEs and central PI
Application
Backend
NON SAP
Application
Business Location 1
Application
Backend
NON SAP
Application
ECC
Server
SAP ERP
Backend
ABAP
Business Location 2
SCM
Server
SAP SCM
Backend
ABAP
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
AS JAVA
Local Advanced
Adapter Engine
JEE
AAE
AS JAVA
Local Advanced
Adapter Engine
JEE
AAE
Remote access to
central PI ESR
Remote access to
central PI ESR
Example
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 Server 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 Benefits •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 Considerations •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
Slide 31
Related Building BlocksRecommendations for Deployment of System Landscape Directory
Slide 32
© 2011 SAP AG. All rights reserved. 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
Benefits Increased availability for critical use cases at
low expense for additional operation effort + cost
Clear separation between management system and managed systems
Considerations Data consistency has to be ensured
Details in SLD planning guide
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
Application
Backend
NON SAP
Application
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEESLDSLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution
Manager
Central Solution
Manager SLD Central Runtime SLD
SLD data suppliers of all
SAP systems register against
central runtime SLD
SLD synchronization between central
runtime SLD and central Solution
Manager SLD
h
EPC
Application
Portal
JEE
Solution Manager 7.0
or lower
Example for
Solution Manager 7.0
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) Benefits •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 Considerations •Data consistency has to be ensured (data synchronization between different SLDs have to be configured) •Details described in SLD planning guide
Slide 33
© 2011 SAP AG. All rights reserved. 33
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
Application
Backend
NON SAP
Application
PI
PI Dual Stack
Process Integration
ESR&SR
ABAP
JEESLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution
Manager
Central SLD
SLD data suppliers of all
SAP systems register against
central runtime SLD
Central SLD provides content to
Solution Manager LMDB
h
EPC
Application
Portal
JEE
Solution Manager 7.1
LMDB
Deployment of System Landscape DirectorySolution 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
Benefits 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
Considerations Data synchronization between SLD and SAP
Solution Manager LMDB to be configured
Details in SLD planning guide and SAP Solution Manager setup guide
Example for
Solution Manager 7.1
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 ABAP-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) Benefits •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 Considerations •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
Slide 34
© 2011 SAP AG. All rights reserved. 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
Benefits Increased availability for critical use case
Independent innovation speed for SLD
Benefits due to latest SLD version based onSAP NetWeaver 7.1 or 7.3
Considerations Additional system just for SLD capabilities
Complex landscapes with multiple SLDs and large numbers of managed systems
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
SLD/LMDB
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution
Manager
Solution Manager
with local SLD/LMDB
SLD data suppliers of all
SAP systems register
against central SLD
SLD synchronization
between central SLD
and local SLD/LMDB
h
EPC
Application
Portal
JEE
Central SLD
SLD
AS JAVA 7.3
Standalone SLD
JEE
h
PI
Process
Integration
ABAP
JEE
Example
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 Benefits •Increased availability for critical use case •Independent innovation speed for SLD •Benefits 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) Considerations •Additional system just for SLD capabilities •More complex landscape with multiple SLDs and large numbers of managed systems
Slide 35
© 2011 SAP AG. All rights reserved. 35
Deployment of System Landscape DirectoryPlain System Landscapes – Solution Manager 7.0
General Recommendation
Shared usage of SLD to provide a central access for all SLD clients
Data suppliers (ABAP and JAVA based systems) report to central SLD
SLD deployed in central SAP Solution Manager system
Benefits Easy setup
Low administration effort
No redundancy
Consistent storage for all systems
Considerations 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
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
BI JAVA
BEx Web
JEE
BW
Data Warehouse
System
ABAP
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution
Manager
SLD data suppliers of all SAP
systems register against central SLD
Central SLD
Example for
Solution Manager 7.0
General Recommendation (plain system landscapes) •Shared usage of System Landscape Directory (SLD) to provide a central access for all SLD clients •Data suppliers (ABAP 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 Benefits •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 Considerations •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
Slide 36
© 2011 SAP AG. All rights reserved. 36
Deployment of System Landscape DirectoryPlain System Landscapes – Solution Manager 7.1
General Recommendation
Shared usage of SLD to provide a central access for all SLD clients
Data suppliers (ABAP and JAVA based systems) report to central SLD
SLD deployed in the central SAP Solution Manager system in addition to LMDB
Benefits Easy setup
Low administration effort
Consistent storage of landscape data
Considerations 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
Example for
Solution Manager 7.1
ECC
Server
SAP ERP
Backend
ABAP
SCM
Server
SAP SCM
Backend
ABAP
BI JAVA
BEx Web
JEE
BW
Data Warehouse
System
ABAP
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution
Manager
SLD data suppliers of all SAP
systems register against central SLD
Central SLD &
Solution Manager LMDB
Solution Manager 7.1
LMDBCentral SLD provides content to
Solution Manager LMDB
General Recommendation (plain system landscapes) •Shared usage of System Landscape Directory (SLD) to provide a central access for all SLD clients •Data suppliers (ABAP 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 Benefits •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 Considerations •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
Slide 37
© 2011 SAP AG. All rights reserved. 37
Additional Information
Using Advanced Adapter Engine Extended:
http://help.sap.com/saphelp_nw73/helpdata/en/a5/f6e04bdc1d4cdbbb32fa52ccdcc419/frameset.htm
SLD planning guide
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0a1a8fb-0527-2a10-f781-
8b67eab16582?QuickLink=index&overridelayout=true
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17579
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17779
Slide 38
Thank You!
Dirk Anthony
TIP Governance Architecture Excellence
SAP System Landscape Governance Board
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
Phone +49/6227/765224
Fax +49/6227/78-19164
E-Mail [email protected]
Slide 39
© 2011 SAP AG. All rights reserved. 39
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 and Java are registered trademarks of Oracle and/or 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.
© 2011 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork, 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 Server, 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.
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.
Slide 40
© 2011 SAP AG. All rights reserved. 40
© 2011 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, 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 und Informix 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.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork 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 Server, 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.
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.