How to Deploy SAP NetWeaver

Deployment Recommendations for SAP NetWeaver 7.0

- SAP NetWeaver Business Warehouse -

Dirk Anthony, SAP NetWeaver Solution Management

August 2009

Approved by SAP System Landscape Governance Board

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 / Deployment Recommendations for Business Warehouse / Page 2

Document History

The following table provides an overview on the most important document changes

Version Date Description

1.00 2009-02-27 Initial Version

1.10 2009-08-26 Add details for embedded

deployed BW

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 3

1. Baseline

2. Deployment of SAP NetWeaver Business Warehouse

2.1. Enterprise Data Warehouse and Business Explorer Web Application

2.2 Combined Usages of Business Warehouse

Agenda

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 4

Introduction:

Evolution Of SAP Architecture

Technolo

gy

Applic

ation

SAP R/3

up to 4.6C

Industry Sol.

SAP Basis

Application

SAP R/3

Enterprise

Industry Solutions

SAP Web Application

Server 6.20

SAP R/3 Enterprise 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

ITSCom

posite A

pplic

atio

n F

ram

ew

ork

APPLICATION SERVER (6.40)

Life

Cycle

Mgm

t

PEOPLE INTEGRATION

Multi Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

PROCESS INTEGRATION

Business

Process Mgmt

ABAP

DB and OS Abstraction

Integration

Broker

J2EE

SAP NetWeaver 2004

SAP ERP 6.0

Composite Applications

Strategic Enterprise Management

Self-Services

Internet Sales

Supplier Relationship Management

EHP 2 EHP 3

and more …

SAP NetWeaver 7.0

Com

posite A

pplic

ation F

ram

ew

ork

APPLICATION SERVER (7.00)

Life

Cycle

Mgm

t

PEOPLE INTEGRATION

Multi Channel Access

Portal Collaboration

INFORMATION INTEGRATION

Master Data Mgmt

Bus. Intelligence Knowledge Mgmt

PROCESS INTEGRATION

Business

Process Mgmt

DB and OS Abstraction

Integration

Broker

J2EE ABAP ITS

SAP ECC Core (6.0)

Industry ExtensionsEnterprise Extensions

Switch Framework

..

SAP NetWeaver 7.0(foundation for the SAP Business Suite)

EhP EhPEhP

SAP Business Suite

Continuous Innovation

ERPCRM SCM

PLMSRM

EhP EhPEhP

Non

-SA

PThe Big Picture:

SAP Business Suite 7 and SAP NetWeaver

EhP EhP

Composite Applications

SAP NetWeaver

Accelerated Innovation

PI 7.1 …

How to deploy

SAP NetWeaver and

SAP Business Suite within

the system landscape?

How can different

innovation cycles be reflected?

…?

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 6

How To Design the Best Landscape

Layout – How SAP Will Support

Landscape Guides for

SAP Business Suite and

SAP NetWeaver

Configuration

Guide

For CTS+

…

Determine the strategic direction

Consider general recommendations

Assess the

individual situation

Derive the appropriate

landscape layout

Communication of product roadmaps

Categorization of deployment options

Landscape papers in certain areas for detailed aspects

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 7

Customer SAP

Ease Landscape Setups By Stronger Guidance

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

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 8

Dual Stack – Single Stack Systems

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)

Examples:

Process

Integration

PI

Mandatory

Dual stack

JAVA

single stack

Portal

Java

EP

EP-C

ABAP

single stack

Portal 7.0*

ABAP

ECC

ERP

Business

Warehouse

ABAP

BI

BEx Web

Java

BI Java

EP

Optional Dual stack

capability based on ABAP

capability based on JAVA

capability based on

ABAP & JAVA

Legende

Single system (SID)

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 9

Example: General Recommendation

Dual Stack vs. Separated Stacks

* Starting with SAP NetWeaver Mobile 7.1 a

dual stack is no longer required

General Recommendation Reasonable Alternative Possible Exception

Generic Use Case ABAP and JAVA based capabilities are

deployed on single stack systems

Approach In general install ABAP + Java stacks in

separate systems (where offered by SAP)

Benefit Separation of duties

Independent scalability & performance

Optimal resource consumption

Maintenance downtime only for used stack

Considerations Additional technical system to be

administrated

Additional appears in the landscape

Generic Use Cases

SAP NetWeaver capabilities require explicitly a dual stack installation (like PI today)

SAP Solution Manager

Approach

Install a dual stack where this is required by the application or related capability

Benefits

Direct support by the installation procedure

Automated connectivity

Considerations Deployment layout might be changed to

single stack by SAP with the next release

Generic Use Case

In individual cases only, dual stack systems might still be a valid solution (e.g. BI and Bex Web scenario)

Approach

Install ABAP and JAVA stack in the same system

Benefit

Setup and configuration effort only for one system

Administration and software maintenance effort only for one system

Considerations No need to change existing systems

today, dual stack systems will still be supported

Installation options will be limited

Separated

Single Stack Systems

Mandatory

Dual Stack System

Optional

Dual Stack System

Process

Integration

PI

Mobile*

MI*

ABAP Java

Solution Manager

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 10

System Landscape Governance By SAP

Consistent Deployment Recommendations:

One central activity of the SAP System Landscape

Governance Board to reduce complexity for customers

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 11

Scope of Deployment Recommendations

Assumptions

High-level deployment recommendation to provide an easy and quick overview

Consistent recommendations for the complete reference landscape approved by SAP System

Landscape Governance Board

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

No detailed description of concrete configuration steps

Customer individual assessment will not be compensated, especially individual data volume and

sizing still have to be evaluated

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 12

Provide Recommendations and Further Details

at One Central Place

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 / Deployment Recommendations for Business Warehouse / Page 13

1. Baseline

2. Deployment of SAP NetWeaver Business Warehouse

2.1. Enterprise Data Warehouse and Business Explorer Web Application

2.2 Combined Usages of Business Warehouse

Agenda

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 14

General Deployment of SAP NetWeaver Business

Warehouse (ABAP and JAVA)

Separated Single Stacks

Business

Warehouse

ABAP

BI

BEx Web

Java

BI Java

EP & EP-C

Integrated Dual Stack

Generic Use Case Execute web-template based BW queries within a

highly flexible and scalable infrastructure

Approach Deployment of BI and BI JAVA on separated systems

Benefit High scalability (server itself can scale or easy split to

two servers possible)

ABAP and Java could be scaled independently

Reduced database administration effort by MCOD possible

Generic Use case

Execute web-template based BW queries within a

simple infrastructure

Approach

Deployment of BI and BI JAVA on the same system*

Benefit Automatic configuration of user management during

installation

Combined maintenance and Start/Stop

Reduced number of systems

*SAP Note 1181025 describes how to install a BW dual stack system to stick to an existing landscape layout

General Recommendation Possible Exception

Business Warehouse & BEx Web

Java

BI Java

EP & EP-C

ABAP

BI

System 1 System 2 System 1

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 15

General Deployment of SAP NetWeaver Business

Warehouse – Standalone Usage

General Recommendation

(central data warehouse)

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

Comprehensive set of planning and simulation capabilities with a simplified landscape setup

Implement Business Warehouse and Business Explorer Web capabilities on separated systems

Use Cases 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 analytical data based on web templates

Benefits Consolidated view of company wide reporting data

Comprehensive Business Warehouse capabilities for planning and simulation

Reduced TCO by shared services and infrastructure

Highly scalable by separated technology stacks

Interoperability between Business Warehouse and application backend systems ensured

Considerations Release & SP stack dependency between Business Warehouse

and BEx Web²

Business

Warehouse

ABAP

BI

BEx Web

Java

BI Java

EP & EP-C

² dependencies are removed starting with SAP NetWeaver 7.0 EhP2

Central

Data Warehouse

Central BEx WebPortal 7.0*

ABAP

ERP

Portal 7.0*

ABAP

SRM

Portal 7.0*

ABAP

SCM

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 16

General Deployment of SAP NetWeaver Business

Warehouse - Standalone Usage

Reasonable Alternative

(local data warehouse systems and group reporting)

Separate reporting data of different business units by local, separated BW systems

Consolidation of local reporting data into the group data warehouse system

Individual usage of queries and web templates for local data warehouse systems and

on group level

Avoid embedded deployment of centralized BW capabilities into the application backend system

Use Cases Local reporting data of different business units will be

consolidated on group level

Design and execute queries to analyze business information

Access analytic data based on web templates

Benefits Independent collection and storage of local reporting data,

reflecting hierarchical setups of company organizations

Full flexibility to create data-mart specific web templates for the local units

Consolidated view of company wide reporting data

Local and central view of reporting data

Considerations More complex landscape setup

Usage of local data-mart specific web templates require additional BEx Web systems

Release & SP stack dependency between BW and BEx Web²

Group

Reporting

Portal 7.0*

ABAP

ERP

Portal 7.0*

ABAP

SRM

BEx Web

Java

BI Java

EP & EP-C

Portal 7.0*

ABAP

ERP

Portal 7.0*

ABAP

SCM

Business

Warehouse

ABAP

BI

BEx Web

Java

BI Java

EP & EP-C

BEx Web

Java

BI Java

EP & EP-C

Business

Warehouse

ABAP

BI

Business

Warehouse

ABAP

BI

Unit

Reporting

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 17

² dependencies are removed starting with SAP NetWeaver 7.0 EhP2

General Deployment of SAP NetWeaver Business

Warehouse - Embedded Deployment

Reasonable Alternative

(local application data, individual BEx Web)

Using SAP NetWeaver Business Warehouse functionality embedded deployed in the

application backend systems to access local application data

Easy & application specific design of web templates (in addition to queries and query views)

requires an individual BEx Web system for each application backend

Use CasesPure focus on local application data, no remote consolidation

Step 1: reporting & analysis with direct access to application data in the local backend system based on queries

Step 2: additional replication of application data by using embedded deployed data warehouse capabilities

Step 3: Enhanced reporting based on individual web templates

Benefits Easy usage of reporting scenarios for operational data

Easy configuration

Smooth scale-out of different use case steps

Highest flexibility to create individual application system specific web templates

Considerations BW functionality only used to access local application data,

no consolidation of application data from remote systems

Embedded deployed BW functionality might have restrictions for multi-client backend systems (details see note 1358744)

Additional BEx Web system for each application system that requires enhanced web reporting capabilities

BEx Web

Java

BI Java

EP & EP-C

* Embedded deployed

BW functionality only used

for local application data

Portal 7.0*

ABAP

SRM

BI*

BEx Web

Java

BI Java

EP & EP-C

Portal 7.0*

ABAP

ERP

BI*

Individual BEx Web

systems

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 18

²

²

² Version dependencies are

removed starting with SAP

NetWeaver 7.0 EhP2

General Deployment of SAP NetWeaver Business

Warehouse - Embedded Deployment

Possible Exception

(local application data, shared BEx Web)

Using SAP NetWeaver Business Warehouse functionality embedded deployed in the

application backend systems to access local application data

Application specific design of web templates (in addition to queries and query views)

using a shared BEx Web system for multiple application backends

Use CasesPure focus on local application data, no remote consolidation

Step 1: reporting & analysis with direct access to application data in the local backend system based on queries

Step 2: additional replication of application data by using embedded deployed data warehouse capabilities

Step 3: Enhanced reporting based on individual web templates

Benefits Easy usage of reporting scenarios for operational data

Smooth scale-out of different use case steps

Flexibility to create application system specific web templates with reduced landscape complexity (but centralized storage of all web templates)

Considerations BW functionality only used to access local application data, no

consolidation of application data from remote systems

Embedded deployed BW functionality might have restrictions for multi-client backend systems (details see note 1358744)

All application specific web templates have to be created and stored in one of the application backend systems, serving as a central store; URL reconfiguration in the BEx Web system required

Release & SP stack dependency to BEx Web to be removed for all systems (done with SAP NetWeaver 7.0 EhP 2 or higher)

BEx Web

Java

BI Java

EP & EP-C

* Embedded deployed

BW functionality only used

for local application data

Portal 7.0*

ABAP

SRM

BI *

Portal 7.0*

ABAP

ERP

BI *

Central BEx Web

systems

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 19

~ one application system serves as

master system for all application

specific web templates;

requires removal of version

dependencies to BEx Web (done

with SAP NetWeaver 7.0 EhP2 or

higher)

~

General Deployment of SAP NetWeaver Business

Warehouse – Combined Usage

General Recommendation

(local & central usage combined)

Using SAP NetWeaver Business Warehouse functionality embedded deployed in the

application backend systems to access local application data combined with consolidating

data from multiple backends into a central data warehouse

Combined usage of local and central queries possible

Central definition of web templates in the central master system

Use Cases Step 1: local reporting & analysis within the individual application systems

with central creation of web templates

Step 2: scale-out to combining local reporting with consolidating data from multiple sources into a central data warehouse

Benefits Easy usage of reporting scenarios for operational data

Flexibility to create application system specific web templates with reduced landscape complexity (but centralized storage of all web templates)

Smooth scale-out to combined usage of reporting & analysis for local application data and central data warehouse reporting

Less complex system landscape

Considerations Embedded deployed BW functionality might have restrictions for multi-

client backend systems

All application specific web templates have to be created and stored in the central data warehouse system serving as a central store; URL reconfiguration in the BEx Web system required

Release & SP stack dependency to BEx Web to be removed for all systems (SAP NetWeaver 7.0 EhP 2 or higher)

Business

Warehouse

ABAP

BI

BEx Web

Java

BI Java

EP & EP-C

Portal 7.0*

ABAP

ERP

BI*

Central BEx Web

Central

Data Warehouse

and master system

for web templates

* Embedded deployed

BW functionality only used

for local application data

Portal 7.0*

ABAP

SRM

BI*

Portal 7.0*

ABAP

SCM

BI*

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 20

1. Baseline

2. Deployment of SAP NetWeaver Business Warehouse

2.1. Enterprise Data Warehouse and Business Explorer Web Application

2.2 Combined Usages of Business Warehouse

Agenda

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 21

Possible Exception

(portal with integrated BW usage)

SAP NetWeaver Portal to provide a role-based user access to different application systems

Reuse of portal infrastructure for locally deployed BW reporting capabilities (BEx Web)

Avoid deployment of further portal applications on the integrated portal system

Avoid embedded deployment of SAP NetWeaver Portal within the application backend system

General Deployment of SAP NetWeaver Portal –

Integrated Portal

Use cases Using web reporting capabilities for operational reporting is the

main use case Personalized and role-based access to an application backend

system

Benefits Reuse of portal infrastructure for BW reporting and application

portal scenarios to simplify landscape setup Centrally administrated user access

Considerations No usage of the Bex Web system as a corporate intranet portal

supported Separation of BI JAVA to scale-out portal usage in the future is

not supported by automatic tools Existing dependencies within Business Warehouse impact

maintenance cycle of the application portal ² BW web reporting impacts usage of the integrated portal, so

deployment of further portal applications should be avoided Interoperability to connected application systems have to be

checked

Integrated Portal

Portal incl.

BEx Web

Java

EP & EP-C

BI Java

version

dependencies²

BP

Portal 7.0*

ABAP

ERP

BI*

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 22

² SP&EhP dependencies removed starting with SAP

NetWeaver 7.0 EhP2

* Only specific subset of BW functionality

(operational reporting), provided by SAP

NetWeaver Application Server ABAP, no

embedded enterprise data warehouse

General Deployment of

Adobe Document Services (ADS)

Reasonable Alternative (within BExWeb)

Shared usage of Adobe Document Services provides a central service to use interactive

forms by business applications or for printing Adobe forms

Adobe Document Services is deployed together with SAP NetWeaver Business Warehouse

to simplify the landscape setup

Avoid embedded deployment of ADS within the SAP Business Suite application system

Portal 7.0*

ABAP

ERPUse Cases Provide PDF based templates to be dynamically

enhanced with business data (interactive forms) Printing Adobe forms (non high volume print)

Benefits Simple landscape setup Shared usage of ADS by multiple application systems Re-use of existing BEx Web infrastructure, if

application portal is not available in the landscape Lean deployment for using interactive forms in BW

reporting driven scenarios

Considerations Interoperability to connected application systems

have to be checked Innovation cycle for ADS and BW(BExWeb) have to

be synchronized Restricted platform availability for ADS

Portal 7.0*

ABAP

SRM

Central

Business Warehouse

BEx Web

Java

EP & EP-C

Business

Warehouse

ABAP

BI

ADS

BI Java

© SAP 2008 / Deployment Recommendations for Business Warehouse / Page 23

Feedback

Dirk Anthony

Product Strategist

SAP NetWeaver Solution Management

SAP AG

Dietmar-Hopp-Allee 16

69190 Walldorf

Germany

Phone +49/6227/765224

Fax +49/6227/78-19164

E-Mail dirk.anthony@sap.com

mailto:christian.oehler@sap.com