how to deploy sap net weaver

7/31/2019 How to Deploy Sap Net Weaver

1/24

How to Deploy SAP NetWeaver

SAP NetWeaver for SAP Business

Suite in 2008

Dirk Anthony, SAP NetWeaver Solution ManagementChristian Oehler, SAP Business Suite Solution Management

August 2008


2/24

Disclaimer

This presentation outlines our general product direction and should not berelied on in making a purchase decision. This presentation is not subject toyour license agreement or any other agreement with SAP. SAP has noobligation to pursue any course of business outlined in this presentation or todevelop or release any functionality mentioned in this presentation. Thispresentation and SAP's strategy and possible future developments are

subject to change and may be changed by SAP at any time for any reasonwithout notice. This document is provided without a warranty of any kind,either express or implied, including but not limited to, the implied warrantiesof merchantability, fitness for a particular purpose, or non-infringement. SAPassumes 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


3/24

1. Baseline

2. General Recommendations

Agenda



4/24

Introduction:

Evolution Of SAP Architecture

Technology

Application

SAP R/3up to 4.6C

Industry Sol.

SAP Basis

Application

SAP R/3

Enterprise

Industry Solutions

SAP Web Application

Server 6.20

SAP R/3Enterprise Core (4.70)

Enterprise Extension Set

mySAP ERP 2004

Composite Applications

Strategic Enterprise Management

Self-Services

Internet Sales

Industry Solutions

and more

SAP NetWeaver 2004

SAP ECC Core (5.0)

Enterprise Extensions

ITS

CompositeApplicationFramework

APPLICATION SERVER (6.40)

LifeCy

cleMgmt

PEOPLE INTEGRATION

Multi Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

PROCESS INTEGRATIONBusiness

Process Mgmt

ABAP

DB and OS Abstraction

IntegrationBroker

J2EE

SAP NetWeaver 2004

SAP ERP 6.0


Strategic Enterprise Management

Self-Services

Internet Sales

Supplier Relationship Management

EHP 2 EHP 3

and more

SAP NetWeaver 7.0

CompositeApplicationF

ramework

APPLICATION SERVER (7.00)

L

ifeCycleMgmt

PEOPLE INTEGRATION

Multi Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

PROCESS INTEGRATIONBusiness

Process Mgmt

DB and OS Abstraction

IntegrationBroker

J2EE ABAP ITS

SAP ECC Core (6.0)

Industry Extensions

Enterprise Extensions

Switch Framework

..


5/24

SAP NetWeaver 7.0(foundation for the SAP Business Suite)

EhP EhPEhP

SAP Business Suite

Continuous Innovation

ERPCRM SCM

PLMSRM

EhP EhPEhP

Non-S

AP

The Big Picture:

SAP Business Suite in 2008

EhP EhP


SAP NetWeaver

Accelerated Innovation

PI 7.1

How to deploySAP NetWeaver andSAP Business Suite within

the system landscape?

How can differentinnovation cycles be reflected?

?



6/24

SAP Business Suite in 2008:

Reference Landscape For Governance Measures

(Phase 1)

SAP Business

Suite in 2008SAP NetWeaver

Process Integration

ABAP + JAVA

SAP NetWeaver

Portal

Java

EP

SAP NetWeaver

Business Intelligence

ABAP

BI

SAPSolution Manager

ABAP + JAVA

Portal 7.0*

ECCServer

SAP ERP

ABAP

BEx Web

Java

EP

BI Java

Portal 7.0*

CRMServer

SAP CRM

ABAP

Portal 7.0*

SCMServer

SAP SCM

ABAP

Portal 7.0*

SRMServer

SAP SRM

ABAP

SLD

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 SAPNetweaver 7.0 EHP 1. SAP 2008 / SAP NetWeaver for SAP Business Suite in 2008/ Page 6


7/24

Clear separation of new functionality

in enhancement packages andcorrections in support packages

Reduced effort for testing and no end-user training required when applyingsupport packages

Adding new functionality predictableand controllable

Improvement Benefits

SAP NetWeaver 7.0

SAP ERP 6.0

BUSINESS SUITE - Stable Core

EHP EHPEHP

EHP EHP

System Landscape Impact of

SAP Enhancement Packages

EHP 4 components for SAP ECC 6.0always require SAP enhancementpackage 1 for SAP NetWeaver 7.0(AS ABAP)

Optional deployment of SAPenhancement package 1 for SAPNetWeaver 7.0 usage types, e.g. PI



8/24

Ease Landscape Setups By Stronger Guidance

Option I

Option II

OptionIII

Clear recommendations by categorization of deployment options

General Recommendation Best choice for majority of typical

landscape use cases Recommended by SAPs strategy

Accepted by a wide base ofcustomersReasonable Alternative

Useful choice for certain usecases or customer scenarios

Supported and confirmed bySAPs strategy

Possible Exception Only useful for specific use cases Supported by SAP, but limitations

might occur

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

Goal

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

Consider



9/24

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 of2008

Differentiation between development, test and production landscape so far not covered



10/24

1. Baseline


2.1. SAP Business Suite

2.2. SAP NetWeaver

Agenda



11/24

I: General Recommendation II: Reasonable Alternative

Recommendations For SAP SRM

SRM Server Deployment Single System Scenario

Use Case

Centrally governed SRM Server integrated to 1-n ERPsystems

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

Use Case

Single System Scenario with SRM 7.0 (with EHP4 andSRM_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 oneorganizational model

Master data distribution synchronously & bi-directional

Considerations

Functional Limitations, e.g. no extended classicscenario, no multi backend deployment

SAP SRM

SAPSRM

Server



12/24


Recommendations For SAP SCM SAP SCM

Use Case

Standalone, centrally governed SCM Server

Benefits Support different innovation cycles, individual availability




Full functionality available

Considerations

Higher TCO

Use Case

Single System Scenario with SCM 7.0 (with EHP3+ andSCM_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)

SCM Server Deployment Single System Scenario



13/24

Recommendations For SAP CRM SAP CRM

I: General Recommendation

CRM Server Deployment

Use Case

Standalone, centrally governed CRM Server

Benefits Support different innovation cycles, individual availability




Considerations

More complex system landscape

End-to-endScenarios

Self-service Interaction

Center

PartnerField

Multi-channel

Key Capability of CRM

Marketing, sales, service and allcustomer interaction channels



14/24

Recommendations for SAP PLM SAP PLM


Single System Scenario Layered PLM Deployment

Use Case

Single System Scenario with PLM 7.0 (PLMWUI andEHP 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

Use Case

Product development with partners using external("presentation only" mode) and internal ("data

persistency" mode) layers

Benefits

Increased network security through separation ofapplication servers

Intranet and extranet access controlled byauthorizations inside internal application server

Better scalability and load balancing capabilities

Considerations

Complex system landscape and higher TCO

internal

external



15/24

1. Baseline


2.1. SAP Business Suite

2.2. SAP NetWeaver

Agenda



16/24

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 Suiteapplication systems in the customer solution landscape

SAP NetWeaver Portal is deployed as a separate system to support different innovation speedand simplified landscape setups

Avoid embedded deployment of SAP NetWeaver Portal within the application system

Portal 7.0*

ABAP

ECC

ERPUse Cases

Central role-based access to different backendapplications

Sharing central portal infrastructure for portalbased applications

Benefits Centrally governed and administrated portal

Shared use of central SAP NetWeaver system to

reduce administration effort

Considerations Interoperability to connected application systems

have to be checked

Applications running in the portal might impact stability & performance

downtime for patching

Portal 7.0*

ABAP

SRM

Portal 7.0*

ABAP

SCM

Portal

Java

EP

EP-C

Central portal



17/24

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 andenterprise 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

Integrate, store, and manage company data frommultiple connected data sources in a central datawarehouse system

Design and execute queries to analyze businessinformation

Access analytic data based on web templates andenterprise reports

Benefits

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

Considerations Release & SP stack dependency between BI and BEx

Web

BusinessIntelligence

ABAP

BI

BEx Web

Java

BI Java

EP

Portal 7.0*

ABAP

ECC

ERP

Portal 7.0*

ABAP

SRM

Portal 7.0*

ABAP

SCM

current planning: remove SP stack dependency with SAP NetWeaver 7.0 EhP2

CentralData Warehouse

Central Bex Web



18/24

General Deployment of SAP NetWeaver Process

Integration and the SAP Business Suite


Shared usage of SAP NetWeaver Process Integration for A2A or B2B scenarios as well asservice enabling of the SAP Business Suite application systems

SAP NetWeaver Process Integration is deployed as a central, separate system to supportdifferent innovation speed and simplified landscape setups

Avoid embedded deployment of SAP NetWeaver Process Integration within the application system

Use Cases Integration of A2A or B2B processes between SAP

and Non-SAP systems

Service enablement of SAP and Non-SAP systems

Benefits 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 andprocesses

Support of high volume scenarios, simplifiedmodeling and configuration, enhanced standardsupport with SAP NetWeaver PI 7.1

Portal 7.0*

ABAP

SCM

Portal 7.0*NON-SAP

ProcessIntegration

ABAP +

JAVA

PI

Portal 7.0*

ABAP

ECC

ERP

Portal 7.0*

ABAP

ECC

ERP

Central PI



19/24

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 solutionlandscape

When focusing on A2A integration, connection to B2B networks or service provisioning andmediated message based communication use ESR as part of SAP NetWeaver PI 7.1

Avoid setup of additional ESR systems in the same solution landscape

Portal 7.0*

ABAP

ECC

ERP

Portal 7.0*

ABAP

SCM

Use Cases

A2A integration or connection to B2B networks bypackaged integration

Design governance and service provisioning andmediated message based communications

Benefits 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)

Considerations Requires SAP NetWeaver PI 7.1 to get complete ESR

functionality

Innovation speed of ESR and PI have to besynchronized

Portal 7.0*NON-SAP

ProcessIntegration

ABAP +JAVA

PI

Central ESR



20/24

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 solutionlandscape

When focusing on pure consumption of services provided by SAPs application system orNON-SAP services use ESR as part of SAP NetWeaver Composition Environment 7.1

Avoid setup of additional ESR systems in the same solution landscape

Portal 7.0*

ABAP

ECC

ERP

Portal 7.0*

ABAP

SRM

Use Case

Pure consumption of SAP or NON-SAP services

Benefits

Central governance for service design & definition

Reduced landscape complexity

Easy deployment of ESR within CE

Latest features of the Enterprise services repositorycan directly be leveraged by CE (same release)

Considerations Innovation speed of ESR and CE have to be

synchronized

Composition

Java

CE

Portal 7.0*NON-SAP Central ESR



21/24

General Deployment of System Landscape

Directory and the SAP Business Suite


Shared usage of System Landscape Directory (SLD) to provide a central access for allSLD 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

Use Cases Central storage of information about all systems

belonging to the solution landscape

Benefits Easy setup (one SLD setup for all systems)

Low operation effort

No redundancy

Consistent foundation for all systems belonging to the

landscape

Considerations Higher demand on SLD regarding availability and

stability

Not applicable, if runtime dependencies to SLD forcertain applications exist (e.g. SAP NetWeaver PI, ESSscenario)

Data of all systems visible/accessible

Portal 7.0*

ABAP

ECC

ERP

Portal 7.0*

ABAP

SRM

BusinessIntelligence

ABAP

BI

BEx Web

Java

BI Java

EP

SolutionManager

ABAP +JAVA

SLD

SLD

Central SLD



22/24

General Deployment of System Landscape

Directory and the SAP Business Suite

General Recommendation (addition)

Extension of generic approach setup of additional local SLDs to improve availabilityof SLD data for certain use cases

If customer uses SAP NetWeaver PI or Web Dynpro Java, a local runtime SLD is requiredin addition to the central SLD in SAP Solution Manager system

Use Cases 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 Javaapplications using aRFC or for 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 SAPSolution Manager

Considerations Data consistency has to be ensured (data

synchronization between different SLDs have to beconfigured)

Portal 7.0*

ABAP

ECC

ERP

SolutionManager

ABAP +JAVA

SLD

Portal 7.0*

ABAP

SRM

Process Integration

ABAP +JAVA

PI

SLD

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

SLD datasynchronization

SLD

Central SLD

Runtime SLD



23/24

Provide Recommendations and Further Details

at One Central Place

We are going to provide a central access to relevant information and recommendationsregarding 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

Roadmap for deploymentrecommendations The recommendations published in

this presentation provide just a

rough outline Further concrete deployment

recommendations for SAPNetWeaver will be published,starting in 2009


24/24

Feedback

Christian OehlerSuite Solution ArchitectureSolution Management SAP Business Suite

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

Mobile +49/160/3603621Fax +49/6227/78-31120E-Mail [email protected]

Dirk AnthonyProduct StrategistProduct Management SAP NetWeaver

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

Phone +49/6227/765224Fax +49/6227/78-19164E-Mail [email protected]
mailto:[email protected]:[email protected]:[email protected]:[email protected]

how to deploy sap net weaver

Documents