How to Deploy SAP NetWeaver

Dual Stack vs. Separated Stacks

Dirk Anthony, SAP NetWeaver Product Management

Boris Zarske, SAP NetWeaver Product Management

December 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 / Dual Stack vs. Separated Stacks/ Page 2

Document History

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

Version Date Description

1.00 2008-08-20 Initial Version

1.01 2008-12-15 Slide 22 added regarding

dual stack installation of

SAP Business Suite

application systems

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 3

1. Technical Comparison

2. General Recommendations

Agenda

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 4

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

Intelligence

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 / Dual Stack vs. Separated Stacks/ Page 5

Comparison Dual Stack vs. Separated Stacks:

Integration / Coupling

Pro Dual Stack

• Always one consistent version for ABAP and Java parts - this is an advantage for setups that require this consistency

Con Dual Stack

• Flexibility concerning SP Stacks/releases

• Tightly coupled versions of the ABAP and the Java stack have different technological innovation speed

• Coupling multiple capabilities with different roles in the system landscape can be detrimental

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 6

Comparison Dual Stack vs. Separated Stacks:

Lifecycle Management

Pro Dual Stack

• Integrated installation, update, upgrade, system copy procedures

• Common operations handbook (at least for basis operation)• One integrated view on the system in the SAP Management

Consoles – can be started and stopped consistently with one click

• Reuse of local ABAP-only based tools like database monitoring/management or CCMS

• Common and consistent backup/restore for ABAP and Java

Con Dual Stack

• Specialized administration skill set for ABAP and JAVA still required

• Compared to single stack systems• more resources are consumed• installation efforts and maintenance downtimes are

greater• ABAP and Java stacks cannot be isolated from each other

with respect to failures and resource consumption• No separate scale-out possible, if load characteristics are

different for ABAP and Java• It is not possible to stop/start ABAP independent from Java

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 7

Comparison Dual Stack vs. Separated Stacks:

User Management

Pro Dual Stack

• Integrated user management (however, this can be achieved also for separate systems)

Con Dual Stack

• The mapping between ABAP entities and Java entities is unintuitive (such as between ABAP roles and JEE groups)

• Limited flexibility, not all Java user management options can be used

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 8

Dual Stack – Separated Stacks:

Appraisal

Dual Stack System Single Stack System

• Advantages for the dual stack in some areas of life-cycle management, such as installation + configuration effort (one-time activities!)

• Benefits for database administration could also be achieved by MCOD

• In some other areas tools & procedures have to be provided on landscape level like central monitoring, change management or user management

• Altogether, only some goals reached on expense of other areas, such as flexibility or scalability

Conclusion

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 9

The Way Forward: Unified Life-Cycle

Management Spanning Multiple Systems

Example: Unified Software Logistics

For example, if you have a landscape with both ABAP and Java parts, you are looking for a

solution for unified software logistics

Using dual stack systems does not address this challenge at all

Proposed solution: Enhanced Change & Transport System (CTS)

Enhancement of existing ABAP CTS to transport also non-ABAP objects:

– Java objects (J2EE, Java EE)

– SAP-specific non-ABAP technologies (such as Web Dynpro Java, SAP NetWeaver Portal)

Combined transport requests for

mixed sets of objects (ABAP, Java, …)

Simplified transport management,

avoids inconsistent system states

Central administration of all transports

(ABAP, Java, …) in one UI

Synchronized updates of mixed

processes (ABAP/Java applications)

Available as of SAP NetWeaver 7.0 Support Package Stack (SPS) 12

Address challenges of mixed technologies by

improved tool support on system landscape level© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 10

Additional Deployment Option: MCOD

Administrative opportunity

Multiple independent and different applications

are located in one database

One logical and physical database instance

Point in time recovery of semantically related

systems, such as SAP ERP and SAP CRM possible

Migration of existing systems is possible

All systems use same DB release

Optionally installable on one physical host

SAP ERPSAP SCM

SAP CRM

SAP PLMSAP SRM

Multiple Components in One Database

(MCOD):

Multiple independent and different applications are

located in one database with separate schemas

One or multiple hosts,

one or multiple applications,

multiple systems,

one database,

multiple schemas“MCOD”

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 11

Example: How MCOD Could Be Used To

Compensate Dual Stack Systems

Example: Enterprise Data

Warehousing

Our general recommendation is to have

two systems, one for BI ABAP, one for BI

Java

Nevertheless, both systems could use

one database with MCOD

Reduced database administration effort

Possible without explicit dual stack deployment by

using the same database for separated systems

Even dual stack systems already use separate

database schemas for ABAP and JAVA like MCOD

MCOD

Database

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 12

1. Technical Comparison

2. General Recommendations

Agenda

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 13

Deployment Of SAP Systems Within A

Solution Landscape

1. Decision

Centrally Shared

• Reuse of platform capabilities within a central system

Local Redundant Use

• Individual usage by multiple local systems

2. Decision

Jointly Deployed

• Less landscape complexity by using different capabilities in the same system

Separately Deployed

• Higher flexibility by separating systems

3. Decision

Integrated Technology Stacks

• Combined usage of duties by dual stack system

Separated Technology Stacks

• Separation of duties by separated technology stacks (ABAP, JAVA)

Architectural decisions to be

taken

Distribution

Model

Deploy product

capabilities

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 14

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 / Dual Stack vs. Separated Stacks/ Page 15

General Recommendation (I):

Dual Stack vs. Separated Stacks

General RecommendationGeneric 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)

Benefits Separation of duties

Independent scalability & performance

Optimal resource consumption

Maintenance downtime only for used stack

Considerations Additional technical system to be administrated

Additional <SID> appears in the landscape

Separated

Single Stack Systems

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 16

General Recommendation (II):

Dual Stack vs. Separated Stacks

Reasonable AlternativeGeneric 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 SAP NetWeavercapability

Benefits Direct support by the installation procedure

Automated connectivity

Considerations Future deployment layout might be changed to

single stack by SAP with the next releaseMandatory

Dual Stack System

Process

Integration

PI

Mobile*

MI*

ABAP Java

Solution Manager

* Starting with SAP NetWeaver Mobile 7.1 a dual stack is no

longer required

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 17

General Recommendation (III):

Dual Stack vs. Separated Stacks

Possible ExceptionGeneric Use Case In individual cases only, dual stack systems

might still be a valid solution (e.g. BI and BExWeb 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 for dual stack will be limited

Optional

Dual Stack System

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 18

General Recommendation (Summary):

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 <SID> 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 / Dual Stack vs. Separated Stacks/ Page 19

Example:

General Deployment of BEx Web Application

Separated Single Stacks

Business

Intelligence

ABAP

BI

BEx Web

Java

BI Java

EP

Integrated Dual Stack

Generic Use Case Execute web-template based BI 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 BI 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

General Recommendation Possible Exception

Business Intelligence & BEx Web

Java

BI Java

EP

ABAP

BI

System 1 System 2 System 1

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 20

Consequence of Recommendation:

Installation Options Offered by SAP Installation Tools

SAP is going to provide clear recommendations for customers how to deploy

different SAP NetWeaver capabilities in a solution landscape

Based on SAP’s product strategy, considering experiences from existing customer landscape layouts

Example of Enterprise Data Warehousing mentioned before:

SAP’s general recommendation to deploy BI and BEx Web capabilities as provided by SAP NetWeaver

usage types BI and BI Java is to install two separate systems rather than installing one dual stack

system

Therefore, default installation option for BI as offered by SAP installer is to install BI ABAP and BI Java

on separate systems

Latest version of installation already reflects this recommendation:

Installation of SAP NetWeaver 7.0 Enhancement Package 1

(EHP1) offers the following options for SAP systems:

Dual stack installation options for SAP NetWeaver PI

and SAP NetWeaver Mobile only

Single stack installation options for AS ABAP systems

Single stack installation options for AS Java systems

Nevertheless, existing BI dual stack installations will still be supported

SAP Note 1181025 describes how to install a BI dual stack system to stick to an existing

landscape layout

Dual stack

Dual stack

ABAP only

Java only

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 21

SAP Business Suite in 2008

EHP4 for ECC

Server 6.0

SAP ERP

ABAP

CRM

Server 7.0

SAP CRM

ABAP

SCM

Server 7.0

SAP SCM

ABAP

SRM

Server 7.0

SAP SRM

ABAP

As of SAP Business Suite 7, you can no longer install

Dual Stack Application Systems (ABAP+Java).

If you want to use both SAP Business Suite ABAP and Java Components in your

system landscape, you have to proceed as follows:

1. Install a separate ABAP-based SAP Business Suite system.

2. Install the required Java components in a separate Java-based SAP system.

3. Configure the connection of the Java-based SAP system to the ABAP-based

SAP Business Suite back-end system

The SAP Business Suite 7 comprises:

EHP4 for SAP ERP 6.0, SAP CRM 7.0, SAP SCM 7.0, SAP PLM 7.0, SAP SRM 7.0

© SAP 2008 / Dual Stack vs. Separated Stacks/ Page 22

Feedback

Boris Zarske

Product Strategist

Product Management SAP NetWeaver

SAP AG

Dietmar-Hopp-Allee 16

69190 Walldorf

Germany

Phone +49/6227/745546

Fax +49/6227/78-29035

E-Mail boris.zarske@sap.com

Dirk Anthony

Product Strategist

Product Management SAP NetWeaver

SAP AG

Dietmar-Hopp-Allee 16

69190 Walldorf

Germany

Phone +49/6227/765224

Fax +49/6227/78-19164

E-Mail dirk.anthony@sap.com