How to Deploy SAP NetWeaver

SAP NetWeaver for SAP Business Suite in 2008

Dirk Anthony, SAP NetWeaver Solution Management Christian Oehler, SAP Business Suite Solution Management August 2008

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 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 2

Agenda

1. Baseline 2. General Recommendations

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 3

Introduction: Evolution Of SAP Architecture

EHP 2 EHP 3

mySAP ERP 2004

SAP ERP 6.0

Supplier Relationship Management Self-Services Internet Sales Composite Applications Strategic Enterprise Management and more
Switch Framework

..

Application

Self-Services Internet Sales Composite Applications

Strategic Enterprise Management and more

SAP R/3 Enterprise SAP R/3

up to 4.6C

Industry Solutions
Enterprise Extensions

Enterprise Extensions

Industry Extensions

Industry Solutions Enterprise Extension Set

Composite Application Framework

SAP ECC Core (5.0)

SAP NetWeaver 2004 SAP NetWeaver 2004
PEOPLE INTEGRATION

SAP ECC Core (6.0)

SAP NetWeaver 7.0 Composite Application Framework
PEOPLE INTEGRATION Multi Channel Access
Portal Collaboration

Industry Sol.

Application
SAP Basis

Multi Channel Access Portal Bus. Intelligence Collaboration Life Cycle Mgmt Knowledge Mgmt

SAP R/3 Enterprise Core (4.70)

SAP Web Application Server 6.20

INFORMATION INTEGRATION

Master Data Mgmt

PROCESS INTEGRATION

INFORMATION INTEGRATION Bus. Intelligence Knowledge Mgmt Master Data Mgmt PROCESS INTEGRATION Business Integration Process Mgmt Broker APPLICATION SERVER (7.00) J2EE ABAP DB and OS Abstraction

Life Cycle Mgmt

Technology

Integration Broker J2EE

Business Process Mgmt

ABAP
ITS

APPLICATION SERVER (6.40)

DB and OS Abstraction

ITS

The Big Picture: SAP Business Suite in 2008

Accelerated Innovation Composite Applications

How can different innovation cycles be reflected?

SAP NetWeaver

PI 7.1

? Continuous Innovation
EhP EhP EhP EhP CRM SRM SAP Business Suite EhP EhP SCM PLM EhP EhP

Non-SAP

ERP

How to deploy SAP NetWeaver and SAP Business Suite within the system landscape?

SAP NetWeaver 7.0

(foundation for the SAP Business Suite)

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 5

SAP Business Suite in 2008: Reference Landscape For Governance Measures (Phase 1)
SAP Business Suite in 2008
SAP NetWeaver Portal
EP Java

BEx Web
BI Java EP Java

SAP NetWeaver Business Intelligence

BI
ABAP

SAP NetWeaver Process Integration

ABAP + JAVA

SAP Solution Manager

ABAP + JAVA

SLD

SAP ERP Portal 7.0*

ECC Server ABAP

SAP SRM Portal 7.0*

SRM Server ABAP

SAP SCM Portal 7.0*

SCM Server ABAP

SAP CRM Portal 7.0*

CRM Server ABAP

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 6

If the customer has already SAP NetWeaver EP, PI or BI 7.00 in place the latest Business Suite innovation can be used without necessarily updating to SAP Netweaver 7.0 EHP 1.

System Landscape Impact of SAP Enhancement Packages

Improvement Benefits

EHP

EHP

EHP

SAP ERP 6.0

EHP EHP

SAP NetWeaver 7.0

BUSINESS SUITE - Stable Core

EHP 4 components for SAP ECC 6.0 always require SAP enhancement package 1 for SAP NetWeaver 7.0 (AS ABAP) Optional deployment of SAP enhancement package 1 for SAP NetWeaver 7.0 usage types, e.g. PI

Clear separation of new functionality in enhancement packages and corrections in support packages Reduced effort for testing and no enduser training required when applying support packages Adding new functionality predictable and controllable

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 7

Ease Landscape Setups By Stronger Guidance

Clear recommendations by categorization of deployment options
Possible Exception

Only useful for specific use cases Supported by SAP, but limitations might occur

Option III

General Recommendation

Option II

Reasonable Alternative

Option I

Best choice for majority of typical landscape use cases Recommended by SAPs strategy Accepted by a wide base of customers

Useful choice for certain use cases or customer scenarios Supported and confirmed by SAPs strategy

Goal

Outlining main important aspects to be considered Best considered trade-off between flexibility and simplicity Applied to main building blocks of SAP products

Consider

Alternative deployment options might have different benefits Customer individual assessment not be compensated

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 8

Landscape Recommendations: SAP Business Suite in 2008

Assumptions

Consistent deployment recommendations for the complete reference landscape Recommendations reflect the current planning status (final agreement by SAPs landscape governance board planned for end of 2008) Focus on general recommendations within the first phase Complete classification including alternative deployment options is planned to be delivered end of 2008 Differentiation between development, test and production landscape so far not covered

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 9

Agenda

1. Baseline 2. General Recommendations 2.1. SAP Business Suite 2.2. SAP NetWeaver

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 10

Recommendations For SAP SRM

SAP SRM

I: General Recommendation
SRM Server Deployment

II: Reasonable Alternative

Single System Scenario

SAP SRM Server

Use Case Centrally governed SRM Server integrated to 1-n ERP systems Centralized procurement

Benefits Support different innovation cycles, individual availability Separation of responsibilities (e.g. less alignment effort) Independent scalability & performance Flexibility to change landscape layout
Considerations Higher TCO
SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 11

Use Case Single System Scenario with SRM 7.0 (with EHP4 and SRM_SERVER and SRM_EXT as Add Ons) Self-Service Procurement (classic Scenario), Temp. Labor Service Procurement, Supplier Self Service
Benefits Reduced TCO by shared use of infrastructure and one organizational model Master data distribution synchronously & bi-directional Considerations Functional Limitations, e.g. no extended classic scenario, no multi backend deployment

Recommendations For SAP SCM

SAP SCM

I: General Recommendation
SCM Server Deployment

II: Reasonable Alternative

Single System Scenario

Use Case Standalone, centrally governed SCM Server Benefits Support different innovation cycles, individual availability Separation of responsibilities (e.g. less alignment effort) Independent scalability & performance Flexibility to change landscape layout Full functionality available Considerations Higher TCO
SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 12

Use Case Single System Scenario with SCM 7.0 (with EHP3+ and SCM_BASIS, SCMEWM , SCEMSRV as Add Ons) Event Management, Extended Warehouse Management, planned: Transportation Management (SAP TM 8.0) Benefits Reduced TCO by shared use of infrastructure Reduced administration and operation effort Considerations Functional Limitations, e.g. no Supply Network Collaboration (SAP SNC) or Advanced Planner & Optimizer (SAP APO)

Recommendations For SAP CRM

SAP CRM

Key Capability of CRM

Marketing, sales, service and all customer interaction channels

I: General Recommendation
CRM Server Deployment

Field

Multichannel

Self-service Interaction Center

Partner

Use Case Standalone, centrally governed CRM Server Benefits Support different innovation cycles, individual availability Separation of responsibilities (e.g. less alignment effort) Independent scalability & performance Flexibility to change landscape layout Considerations More complex system landscape

End-to-end Scenarios

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 13

Recommendations for SAP PLM

SAP PLM

I: General Recommendation
Single System Scenario

II: Reasonable Alternative

Layered PLM Deployment

external

internal

Use Case Single System Scenario with PLM 7.0 (PLMWUI and EHP 4) with PPM 5.0 (CPRXRPM) as Add On Project and portfolio management, Design collaboration Benefits Reduced TCO by shared use of infrastructure Reduced administration and operation effort Considerations PLM Scenarios running in ECC Server might impact: stability & performance downtime for patching security
SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 14

Use Case Product development with partners using external ("presentation only" mode) and internal ("data persistency" mode) layers Benefits Increased network security through separation of application servers Intranet and extranet access controlled by authorizations inside internal application server Better scalability and load balancing capabilities Considerations Complex system landscape and higher TCO

Agenda

1. Baseline 2. General Recommendations 2.1. SAP Business Suite 2.2. SAP NetWeaver

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 15

General Deployment of SAP NetWeaver Portal and the SAP Business Suite
General Recommendation

Shared usage of SAP NetWeaver Portal provides a central access to the SAP Business Suite application systems in the customer solution landscape SAP NetWeaver Portal is deployed as a separate system to support different innovation speed and simplified landscape setups Avoid embedded deployment of SAP NetWeaver Portal within the application system

ERP Portal 7.0*

ECC ABAP

Use Cases

Portal
EP EP-C Java

Central role-based access to different backend applications Sharing central portal infrastructure for portal based applications

Benefits

SRM Portal 7.0* Central portal

ABAP

Centrally governed and administrated portal Shared use of central SAP NetWeaver system to reduce administration effort

Considerations
SCM Portal 7.0*

ABAP

Interoperability to connected application systems have to be checked Applications running in the portal might impact

stability & performance downtime for patching

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 16

General Deployment of SAP NetWeaver Business Intelligence and the SAP Business Suite
General Recommendation

Integrate, store, and manage company data from multiple connected data sources in a central data warehouse system including central definition of all queries, web templates and enterprise reports Comprehensive set of planning and simulation capabilities with a simplified landscape setup Implement Business Intelligence and Business Explorer Web capabilities on separated systems

Use Cases
ERP Portal 7.0*
ECC ABAP BEx Web
BI Java
EP

Central Bex Web

SRM Portal 7.0*

Java

Integrate, store, and manage company data from multiple connected data sources in a central data warehouse system Design and execute queries to analyze business information Access analytic data based on web templates and enterprise reports

Benefits
ABAP Business Intelligence

SCM Portal 7.0*

BI ABAP

Consolidated view of company wide reporting data Comprehensive Business Intelligence capabilities for planning and simulation Reduced TCO by shared services and infrastructure Highly scalable by separated technology stacks

ABAP

Central Data Warehouse

Considerations

Release & SP stack dependency between BI and BEx Web

current planning: remove SP stack dependency with SAP NetWeaver 7.0 EhP2
SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 17

General Deployment of SAP NetWeaver Process Integration and the SAP Business Suite
General Recommendation

Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well as service enabling of the SAP Business Suite application systems 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 system
ERP Portal 7.0*
ECC

Use Cases

ERP Portal 7.0*

ECC ABAP

ABAP

Process Integration PI ABAP + JAVA

Integration of A2A or B2B processes between SAP and Non-SAP systems Service enablement of SAP and Non-SAP systems

Benefits

Central PI SCM Portal 7.0* NON-SAP Portal 7.0*

ABAP

Less complexity of system landscape Central governance for meta data Less effort by central maintaining of data for routing, mapping, connectivity, ccBPM, etc. Central responsibility for monitoring of services and processes Support of high volume scenarios, simplified modeling and configuration, enhanced standard support with SAP NetWeaver PI 7.1

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 18

General Deployment of Enterprise Services Repository and the SAP Business Suite
General Recommendation (Variant 1)

Shared usage of a central Enterprise Services Repository within the application solution landscape When focusing on A2A integration, connection to B2B networks or service provisioning and mediated message based communication use ESR as part of SAP NetWeaver PI 7.1 Avoid setup of additional ESR systems in the same solution landscape
ERP Portal 7.0*
ECC ABAP Process Integration

Use Cases

A2A integration or connection to B2B networks by packaged integration Design governance and service provisioning and mediated message based communications

SCM Portal 7.0*

PI ABAP + JAVA

Benefits

ABAP

Central governance for service design & definition Reduced landscape complexity Automated deployment of ESR within PI Latest features of the Enterprise services repository can directly be leveraged by PI (same release)

NON-SAP Portal 7.0*

Central ESR

Considerations

Requires SAP NetWeaver PI 7.1 to get complete ESR functionality Innovation speed of ESR and PI have to be synchronized

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 19

General Deployment of Enterprise Services Repository and the SAP Business Suite
General Recommendation (Variant 2)

Shared usage of a central Enterprise Services Repository within the application solution landscape When focusing on pure consumption of services provided by SAPs application system or NON-SAP services use ESR as part of SAP NetWeaver Composition Environment 7.1 Avoid setup of additional ESR systems in the same solution landscape
ERP Portal 7.0*
ECC ABAP Composition CE

Use Case

Pure consumption of SAP or NON-SAP services

Benefits

SRM Portal 7.0*

Java

ABAP

Central governance for service design & definition Reduced landscape complexity Easy deployment of ESR within CE Latest features of the Enterprise services repository can directly be leveraged by CE (same release)

NON-SAP Portal 7.0*

Central ESR

Considerations

Innovation speed of ESR and CE have to be synchronized

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 20

General Deployment of System Landscape Directory and the SAP Business Suite
General Recommendation

SLD

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

ERP Portal 7.0*

ECC ABAP

Use Cases

Solution Manager
ABAP + JAVA

Central storage of information about all systems belonging to the solution landscape

Benefits

SRM Portal 7.0*

SLD
ABAP

Easy setup (one SLD setup for all systems) Low operation effort No redundancy Consistent foundation for all systems belonging to the landscape

Central SLD

Considerations
Business Intelligence
BI

BEx Web
BI Java EP Java

ABAP

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 21

Higher demand on SLD regarding availability and stability Not applicable, if runtime dependencies to SLD for certain applications exist (e.g. SAP NetWeaver PI, ESS scenario) Data of all systems visible/accessible

General Deployment of System Landscape Directory and the SAP Business Suite
General Recommendation (addition)

SLD

Extension of generic approach setup of additional local SLDs to improve availability of SLD data for certain use cases If customer uses SAP NetWeaver PI or Web Dynpro Java, a local runtime SLD is required in addition to the central SLD in SAP Solution Manager system
ERP Portal 7.0*
ECC ABAP

Use Cases

Solution Manager
ABAP + JAVA

Central storage of information about all systems belonging to the solution landscape Setup of additional SLDs to compensate SLD runtime dependencies (such as for Web Dynpro Java applications using aRFC or for PI)

SRM Portal 7.0*

Benefits

ABAP

SLD Central SLD

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

Process Integration PI ABAP + JAVA SLD data synchronization

Considerations

SLD
Runtime SLD

Data consistency has to be ensured (data synchronization between different SLDs have to be configured)

SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 22

SLD runtime dependency for PI is planned to be removed with SAP NetWeaver 7.20 Web Dynpro dependency is planned to be removed after complete migration from aRFC to aRFC2

Provide Recommendations and Further Details at One Central Place

Roadmap for deployment recommendations

The recommendations published in this presentation provide just a rough outline Further concrete deployment recommendations for SAP NetWeaver will be published, starting in 2009

We are going to provide a central access to relevant information and recommendations regarding deployment options for SAP NetWeaver: https://www.sdn.sap.com/irj/sdn/landscapedesign section Distribution Models
SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 23

Feedback

Dirk Anthony Product Strategist Product Management SAP NetWeaver

Christian Oehler Suite Solution Architecture Solution Management SAP Business Suite

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Phone Fax E-Mail +49/6227/765224 +49/6227/78-19164 dirk.anthony@sap.com

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Mobile Fax E-Mail +49/160/3603621 +49/6227/78-31120 christian.oehler@sap.com