System Landscape Recommendations for SAP NetWeaver Business Warehouse 7.3 - Additional Notes

Slide 1

System Landscape Recommendations for SAP

NetWeaver 7.3 – Information 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


Agenda

Introduction

Methodology & Scope of Landscape Recommendations

Basic Landscape Setups

Recommendations for SAP NetWeaver Business Warehouse Deployments

Enhanced Landscape Setups

Additional Aspects for SAP NetWeaver BW Based System Landscapes

Related Building Blocks

Recommendations for SAP Business Objects BI Platform in

SAP NetWeaver BW Landscapes

Slide 4

IntroductionMethodology & Scope of Landscape Recommendations

Slide 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


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


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


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


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


Scope of Landscape RecommendationsBuilding Blocks in System Landscapes for Information Centric Capabilities

Considered main building blocks SAP NetWeaver Business Warehouse (BW)

SAP NetWeaver BI JAVA (BEx Web)

Additional components or Add-Ons deployed with BW or BI JAVA like Strategic Enterprise Management or Adobe Document Services

Considered main usage scenarios Central Data Warehouse system

BW reporting on local operational data

Enhanced planning scenarios

JEE

SAP system with

own database

available platform

technology

Rolemain role of this

systemmandatory

component

optional

component

ECC Server

AS ABAP

SAP ERP

ABAP

BW

Web

Templates

Local BI

Content

BW

AS ABAP

Business Warehouse

Add On

Central BI

Content

ABAP

Web

TemplatesEP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

...BEx Web Apps.

Considered main building blocks SAP NetWeaver usage type Business Warehouse (BW) SAP NetWeaver usage type BI JAVA (BEx Web) Additional SAP NetWeaver usage types or Add-Ons deployed together with BW or BI

JAVA like Strategic Enterprise Management (SEM) or Adobe Document Services (ADOBE)

Considered main usage scenarios Usage of SAP NetWeaver BW as central data warehouse system Usage of SAP NetWeaver BW capabilities to access local operational data Usage of SAP NetWeaver BW and additional Add-Ons for enhanced planning scenarios

Slide 11


Scope of Landscape RecommendationsAdditional Building Blocks for Analytical Capabilities

SAP Business Objects BI Clients Different rich and thin clients

Supporting different scenarios and business needs

Different user roles

SAP Business Objects BI Web Applications Runtime for BI platform web applications

Different Web Application Server supported

BI content accessed via BI Launch Pad; improved integration into SAP NetWeaver Portal

SAP Business Objects BI Platform Services Based on SAP BO platform

Servers offering services for BI clients and mgmt. tasks

Additional capabilities like semantic layer

SAP Business Objects BI Clients

Dashboard

(Xcelsius)

Analysis

(Office)

Analysis

(OLAP)

Crystal

ReportWebI

Explorer

Web Applic. Server

BI Web Applications

BI Launch Pad

BI Platform

Web Applications

BI Platform

BI Platform Services

Management

Servers

Semantic Layer

Processing

Servers

BO

SAP Business Objects BI Clients different rich and thin clients available supporting different scenarios and business needs typically different user roles targeted (e.g. IT experts, data analysts, business users,

casual users)

SAP Business Objects BI Web Applications runtime for BI platform web applications

like BI Launch pad, Central Management Console, etc. different Web Application Server supported

Details see http://service.sap.com/bosap-support all BI content can be accessed from one location via BI Launch Pad (single entry point to

BI) can be integrated with any portal with Open Document API improved integration into SAP NetWeaver Portal via navigation iview

SAP Business Objects BI Platform Services based on SAP BO platform infrastructure containing different process servers supporting individual BI clients and management

tasks like Central Management Server, Event Server, Adaptive Processing Server,

Dashboard Server, Crystal Reports Processing Server, Web Intelligence Processing Server, etc.

providing additional capabilities like semantic layer (universe)

Slide 12


BI Web Applications for SAP NetWeaver BWAlternative BEx Web Deployments

(1) BEx Web Apps based on SAP NetWeaver Requires SAP NetWeaver BI JAVA including EP, EP Core,

and AS JAVA as runtime

Accessing web templates and additional scenarios

BEx Web Templates stored in one BW Master System

Future functional enhancements based on SAP Business Objects BI platform, not BI JAVA

(2) BEx Web Apps based on SAP BO BI platform Requires BI platform and supported Web Application

Server

Accessing web templates but limitations compared to existing BI JAVA functionality

Information Broadcasting, Document Integration with KM, Report-to-Report interface, and Portal Themes not supported

BEx Web Templates stored in one BW Master System

SAP Note 1541365 for BEx Web integration details

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

...BEx Web Apps.

Web Applic. Server

BI Web Applications

BI Launch Pad

BI Platform

Web Applications

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

BI Platform


Management

Servers

Processing

Servers

BO

Semantic Layer

(1) BEx Web Apps based on SAP NetWeaver requires BI JAVA and locally deployed SAP NetWeaver usage types EP, EP Core, and

AS JAVA as runtime consists of different components like

BI BASE Services containing BI Consuming Services (BICS) API BEx Web Applications (BEx Web access) Further components for specific scenarios like Information Broadcasting

BEx Web Templates need to be stored in one BW Master System future functional enhancements will be based on SAP Business Objects BI platform

(2) BEx Web Apps based on SAP Business Objects BI platform (SAP BI 4.0) BEx Web and BICS functionality require

BI platform containing BICS library and BEx Web Application Service started within Adaptive Processing Server

web application layer deployed on any of the supported Web Application Server (including SAP NetWeaver AS JAVA 7.3)

limitations compared to existing BI JAVA functionality Information Broadcasting, Document Integration with KM, Report-to-Report

interface, and Portal Themes not supported BEx Web Templates need to be stored in one BW Master System see SAP Note 1541365 for BEx Web integration details

Slide 13

Basic Landscape SetupsRecommendations for SAP NetWeaver Business Warehouse Deployments

Slide 14


Deployment of SAP NetWeaver Business Warehouse Technology Stack Deployment (ABAP and JAVA)

Separated Single Stacks Integrated Dual Stack

Benefits

High scalability

ABAP and Java independently scaled

Different innovation speeds for ABAP and JAVA, starting with SAP NetWeaver 7.02

Potential for reduced database admin. effort via MCOD

Best supporting SAP’s technology & BI strategy

Benefits Automatic config. of user mgmnt. during

installation Reduced number of systems (SIDs)

Considerations Not in line with SAP’s techn. stack strategy No new installations, only to support

existing BW dual stack setups Limited flexibility

General Recommendation Possible Exception

System 1 System 2 System 1

ABAP

BW Dual Stack

BW and BEx Web

ABAP

JAVAJEE

BW

Central BI

Content

EP

BI JAVA

BW

AS ABAP

Business Warehouse

Central BI

Content

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

Separated Single Stacks: Benefits •High scalability (server itself can scale or easy split to two servers possible) •ABAP and Java could be scaled independently •Different innovation speeds for ABAP and JAVA possible, version dependencies removed with SAP NetWeaver 7.02 •Reduced database administration effort via MCOD possible •Best supporting SAP’s technology & BI strategy Integrated Dual Stack: Benefit •Automatic configuration of user management during installation •Reduced number of systems (SIDs) Considerations •Not in line with SAP’s technology stack strategy •No new installations, only to support existing BW dual stack setups (SAP Note 1181025 for details) •Limited flexibility

Slide 15


Deployment of SAP NetWeaver Business Warehouse


Manage company data from multiple data sources in a central separate

data warehouse system

Central definition of all queries & web templates

Implement Business Explorer Web capabilities as separate system

Benefits Consolidated view of company wide reporting data

Comprehensive warehouse capabilities

Reduced TCO by shared system

Highly scalable

Interoperability between Business Warehouse and application backend systems ensured

Considerations Release & SP stack dependency between BW and

BEx Web removed

Example

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

Central BEx Web system accesses

web templates stored within central BW system

analytical data from different sources consolidated

within central Data Warehouse system

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

General Recommendation • central data warehouse •Integrate, store, and manage company data from multiple connected data sources in a central separate 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 Typical Technical 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 removed starting with EhP2 for SAP NetWeaver 7.0

Slide 16


SRM

Server

SAP SRM

Backend

ABAP

Application

Backend

NON SAP

Application

ECC

Server

SAP ERP

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

AS ABAP

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

Business Unit 1

Business Unit 2

Analytical data for

Unit Reporting Analytical data for

Unit Reporting

Analytical data for

Group Reporting

Corporate Company View

BW

AS ABAP

Business

WarehouseWeb

Templates

ABAP

BI Content

BW

Business

WarehouseWeb

Templates

ABAP

BI Content

BW

AS ABAP

Business

WarehouseWeb

Templates

ABAP

BI Content


Reasonable Alternative

Separate reporting for different business units

Consolidation of local reporting data into corporate data warehouse system

Individual usage of queries and web templates on local and corporate level

Benefits Reporting reflecting hierarchical setups of

company organizations

Data-mart specific web templates for local business units

Local and central view of reporting data

Considerations More complex landscape setup

Data-mart specific web templates require additional BEx Web systems

Release & SP stack dependency between BW and BEx Web removed

Example

Reasonable Alternative •local data warehouse systems and corporate reporting •Separate reporting data of different business units by local, separated BW systems •Consolidation of local reporting data into the corporate data warehouse system •Individual usage of queries and web templates for local data warehouse systems and on corporate level Typical Technical Use Cases •Local reporting data of different business units will be consolidated on corporate 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 business 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 Business Warehouse and BEx Web removed starting with EhP2 for SAP NetWeaver 7.0

Slide 17




SAP NetWeaver BW functionality embedded deployed within application

backend systems to access only local application data

Application specific design of web templates via local BEx Web system

Benefits Easy use of reporting scenarios for operational data

Simplified configuration

Smooth scale-out of use cases

Highest flexibility for web templates

Considerations Access only local application data, no consolidation of

data from remote systems

Potential restrictions for multi-client backend systems

Additional BEx Web system for each application system

Example

EP

AS JAVA

Local BEx Web

JEE

BI JAVA

BICS

EP

AS JAVA

Local BEx Web

JEE

BI JAVA

BICS

accessing individual

application system

specific web templates

(*) embedded deployed

BW functionality only used for

local application data

ECC Server

AS ABAP

SAP ERP

ABAP

BW (*)

Web

Templates

Local BI

Content

SRM Server

AS ABAP

SAP SRM

ABAP

BW (*)

Web

Templates

Local BI

Content

Reasonable Alternative •local application data, individual BEx Web •Using SAP NetWeaver Business Warehouse functionality embedded deployed in the application backend systems to access only 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 Typical Technical Use Cases Pure 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 business 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

Slide 18





ECC Server

AS ABAP

SAP ERP

ABAP

BW (*)

Local BI

Content

SRM Server

AS ABAP

SAP SRM

ABAP

BW (*)

Local BI

Content

EP

AS JAVA

Local BEx Web

JEE

BI JAVA

BICS

accessing individual

application system

specific web templates out

of one master system

Web

TemplatesWeb

Templates

using individual

application system

specific web templates via

URL reconfiguration to

access SRM backend

ERP system serves as

master system for all

application specific

web templates


Possible Exception

SAP NetWeaver BW functionality embedded deployed within application

backend systems to access only local application data

Application specific design of web templates via a shared BEx Web system


Smooth scale-out of use cases

Individual use of web templates with reduced landscape complexity

Considerations Access only local application data, no consolidation of

data from remote systems


All web templates stored in one backend system

Manual complex config. of web template access

Release & SP stack dependency between BW and BEx Web removed

Example

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 Typical Technical Use Cases Pure 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 between Business Warehouse and BEx Web removed

starting with EhP2 for SAP NetWeaver 7.0

Slide 19




Combined reporting approach of accessing local application data and

consolidating data into a central data warehouse

Central definition of all web templates in central BW master system


Applic. system specific web templates

Smooth scale-out to combined usage of local & central reporting

Less complex system landscape

Considerations


All web templates stored in central BW system

Manual complex config. of web template access for application backend systems

Release & SP stack dependency between BW and BExWeb removed

BW

AS ABAP

Business Warehouse

ABAP

Central BI

Content

Central BEx Web system accesses

web templates stored within central BW system

EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

Application

Backend

NON SAP

Application

ECC Server

AS ABAP

SAP ERP

ABAP

BW (*)

Local BI

Content

SRM Server

AS ABAP

SAP SRM

ABAP

BW (*)

Local BI

Content

Web

TemplatesWeb

Templates

Central BW system

serves as master

system for all

web templates

in addition certain analytical data from

different sources consolidated within

central Data Warehouse system




Example

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 all web templates in the central master system Typical Technical 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 (details see note 1358744) •All application specific web templates have to be created and stored in the central data warehouse system serving as a central store •URL reconfiguration for application specific web templates in the BEx Web system required to access data in the application backend systems •Release & SP stack dependency between Business Warehouse and BEx Web removed

starting with EhP2 for SAP NetWeaver 7.0

Slide 20

Enhanced Landscape SetupsAdditional Aspects for SAP NetWeaver BW Based System Landscapes

Slide 21


Add-Ons based on SAP NetWeaver Business Warehouse

Central BI Content BW Content Add-On developed by SAP Business Suite

Deployed within SAP NetWeaver BW system

Release strategy for BW Content described in SAP note 153967

Strategic Enterprise Management (SEM) Enrich data reporting scenarios by analytical capabilities

Mainly used within SAP Business Suite scenarios

Shipped as part of product SAP ERP 6.0, but tight connection with SAP NetWeaver Business Warehouse

Technically deployed on top of SAP NetWeaver BW components Typically on top of a central Data Warehouse system

Sometimes within SAP ERP system for embedded deployed BW

Example:

Business Warehouse with

enhanced analytic &

planning scenarios

BW

AS ABAP

Business Warehouse

SEM

Central BI

Content

ABAP

Web

Templates

Slide 22


Version Interoperability Matrix for SAP NetWeaver BW

Content Add-On

BI Content AddOn by SAP Business Suite

BI Content

Packages

SAP

NetWeaver BW

Supported

Release Range

(a)

First version of

new content for

SAP BS7

(b)

(e.g. for SAP ERP 6.04)

First version of

new content for

SAP BS7i2010

(b)


First version of

new content for

SAP BS7i2011

(b)


SAP NetWeaver BW 7.00BI Cont

7.02 – 7.06BI Cont 7.04 BI Cont 7.05 BI Cont 7.06






7.35 – 7.36*- BI Cont 7.35* BI Cont 7.36*

SAP NetWeaver BW

7.03/7.31BI Cont

7.46*- - BI Cont 7.46*

(a) consider independent maintenance

schedule for BI Content AddOns;

details see SAP note 153967

* functional equivalence:

BI Cont 7.05 = BI Cont 7.35

BI Cont 7.06 = BI Cont 7.36 = BI Cont 7.46

(b) BI content version also run against lower

or higher SAP Business Suite version

Slide 23


Deployment of SAP Strategic Enterprise Management


Deployed on top of central SAP NetWeaver Business Warehouse system

Running analytical scenarios for consolidated data

Benefits Reporting & planning enriched by further analytic

capabilities

Analytical scenarios executed on existing business warehouse data

Reduced landscape complexity

Considerations New SEM functionality deployed as part of SAP ERP

Enhancement Packages

Mutual SEM and SAP NetWeaver BW version dependency, but version independency to connected backend systems

Limitations for supported SAP ERP SEM 6.05 version(SAP note 1531022 for details)

Example

BW

AS ABAP

Business Warehouse

with SEM

ABAP

Central BI

Content

SEM

EP

AS JAVA

Local BEx Web

JEE

BI JAVA

BICS

Central Business Warehouse

with enhanced

analytic scenarios

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

analytical data from different sources consolidated

within central Data Warehouse system

General Recommendation •analytical scenarios on consolidated business data •SEM deployed on top of central SAP NetWeaver Business Warehouse system •SEM capabilities used for running analytical scenarios for consolidated data within central business warehouse system Typical Technical Use Case: Central strategic analysis for consolidated business data from different SAP sources Benefits •Reporting & planning capabilities within central business warehouse enriched by further analytic capabilities •Analytical scenarios can be executed on existing business warehouse data •Reduced landscape complexity since additional separate SEM system is avoided Considerations •New SEM functionality is deployed as part of SAP ERP Enhancement Packages •Mutual SEM and SAP NetWeaver BW version dependency, but version independency to connected backend systems •Limitations for supported SAP ERP SEM 6.05 version (details see next slides and SAP note 1531022)

Slide 24


Deployment of SAP Strategic Enterprise Management


Deployed on top of BW components, embedded installed within ERP system

Analyzing business data via local BW cubes

Useful if only local data is of interest and no central SAP NetWeaver BW

system in place

Benefits Reduced landscape complexity

Local BW functionality easily enhanced by further analytic capabilities

Close integration of SEM capabilities with SAP ERP innovation cycle

Considerations

SEM only to access local application data, no consolidation of data from remote systems

Consider performance impact of SEM scenarios for ERP system

New SEM functionality deployed as part of SAP ERP Enhancement Packages


SEM and BW functionality within

ERP only used for accessing local

application data

ECC Server

AS ABAP

SAP ERP

ABAP

BW (*)

SEM (*)

EP

AS JAVA

Local BEx Web

JEE

BI JAVA

BICSweb reporting &

analysis for local

application data

Example

Reasonable Alternative •analytical business scenarios on local application data •SEM installed on top of BW components, embedded deployed within ERP system •SEM capabilities for analyzing business data via local BI cubes •Useful if only local data is of interest and no central SAP NetWeaver BW system is in place Typical Technical Use Case: Pure focus on local application data, no analysis of data consolidated from different info sources Benefits •Reduced landscape complexity •Local BW functionality can easily be enhanced by further analytic capabilities •Close integration of SEM capabilities within SAP ERP innovation cycle Considerations •SEM functionality only used to access local application data, no consolidation of application data from remote systems •Consider performance impact of SEM scenarios for ERP system •New SEM functionality is deployed as part of SAP ERP Enhancement Packages

Slide 25


Version Interoperability Matrix for

SAP NetWeaver BW Add-Ons

BW Add-On

Add-On

SAP

NetWeaver BW

SAP SEM

(a)

(shipped as part of product SAP ERP)

SAP NetWeaver BW 7.00SAP SEM 6.0

(separate product)

SAP NetWeaver BW 7.01SEM 6.04

(Part of SAP ERP 6.04)

SAP NetWeaver BW 7.02SEM 6.05


SAP NetWeaver BW 7.30SEM 6.34*


SAP NetWeaver BW 7.03/7.31SEM 7.36*


*functional equivalence:

SEM 6.04 = SEM 6.34;

No SEM 6.05 functionality available on SAP NW 7.30;

ERP 6.06 and SEM 7.36 plannig state, subject to change

(a) SEM version depends on underlying SAP NetWeaver

BW version, but can be run independently from version of

SAP BS backend system

Slide 26

Related Building BlocksRecommendations for SAP Business Objects BI Platform in SAP NetWeaver BW

Landscapes

Slide 27


Deployment of Business Explorer Web Application BI platform in use, BI JAVA capabilities not required


Preferred setup, if scenarios do not require BI JAVA capabilities

BI launch pad to access BEx Web templates

SAP NetWeaver AS JAVA 7.3 as separate runtime for SAP BO BI 4.0 web appl.

Benefits No need for SAP NetWeaver BI JAVA system,

only SAP NetWeaver AS JAVA runtime required

Known SAP NetWeaver AS JAVA infrastructure

High scalability & proven robustness

Considerations Communication between Web App Server and

BW backend always via BI platform

At least SAP NetWeaver AS JAVA 7.3 andSAP Business Objects BI 4.0 SP2

Check PAM support for SAP BO BI 4.0

AS JAVA installed separately before BI platform installation

BI Web applications manually deployed on AS JAVA via BI platform tool (Wdeploy)

Example

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

Accessing web

templates stored

in central BW

master system

Interacting with BEx Web

App Service and BICS

provided by BI platform JEEAS JAVA

BI Web Applications

BI Launch Pad

BI Platform

Web Applications

BI Platform


Mngmt. Server

Adaptive

Process. Server

BO

Semantic Layer

BI Client

Process. Server

General Recommendation •Preferred setup, if targeted scenarios do not require BI JAVA capabilities •BI launch pad also used to access BEx Web templates •SAP NetWeaver AS JAVA 7.3 used as separate runtime for SAP Business Objects BI 4.0 web applications Typical Technical Use Case SAP Business Objects BI use cases without need of SAP NetWeaver BI JAVA based scenarios (e.g. no need to run information broadcasting scenarios) Benefits •No need to implement complete SAP NetWeaver BI JAVA system, only SAP NetWeaver AS JAVA runtime required •Known SAP NetWeaver AS JAVA infrastructure in use •High scalability & proven robustness of SAP NetWeaver AS JAVA runtime Considerations •Communication between Web App Server and BW backend always via BI platform •At least SAP NetWeaver AS JAVA 7.3 and SAP Business Objects BI 4.0 SP2 or higher •Check PAM support for SAP Business Objects BI •Need to be installed separately before BI platform installation •BI Web applications needs to be deployed manually on AS JAVA via BI platformtool (Wdeploy); details see installation guide

Slide 28




Useful setup, if scenarios do not require BI JAVA capabilities and existing

SAP Business Objects BI infrastructure in use

BI launch pad used to access BEx Web templates

Non-SAP Web Application Server as separate runtime for SAP BO BI 4.0 web appl.

Benefits Lean Web Application Server (Tomcat)

automatically installed during installation of BI platform

Existing NON-SAP Web Application Server used, if no SAP NetWeaver AS JAVA in place

Considerations Communication between Web App Server and

BW backend always via BI platform

NON-SAP Web Applic. Server needs to fulfill expected performance, scalability and robustness behavior

Additional NON-SAP infrastructure

Example

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

Web Applic. Server

BI Web Applications

BI Launch Pad

BI Platform

Web Applications

BI Platform


Mngmt. Server

Adaptive

Process. Server

BO

Semantic Layer

BI Client

Process. Server

Interacting with BEx Web

App Service and BICS

provided by BI platform

Accessing web

templates stored

in central BW

master system

Reasonable Alternative •SAP Business Objects BI Web Applications on NON-SAP Web Server •Useful setup, if targeted scenarios do not require BI JAVA capabilities and already existing SAP Business Objects BI infrastructure in use (reuse of existing BI web server) •SAP Business Objects BI 4.0 web applications also used to access BEx Web templates •Non-SAP Web Application Server used as separate runtime for SAP BO BI 4.0 web applications Typical Technical Use Case SAP Business Objects BI use cases without need of SAP NetWeaver BI JAVA based scenarios Benefits •Lean shipped Web Application Server (Tomcat) could be used for quick implementations; can be automatically installed during installation of BI platform; (productive usage needs to be checked for high load) •Already existing NON-SAP Web Application Server could be used, if no SAP NetWeaver AS JAVA infrastructure in place at responsible customer organization Considerations •Communication between Web App Server and BW backend always via BI platform •NON-SAP Web Server infrastructure needs to fulfill expected performance, scalability and robustness behavior •Additional NON-SAP JAVA Web Application Server infrastructure to be maintained by system administration

Slide 29




BI entry point via BI Launch Pad integrated into portal based user access

SAP BO BI Web Application system separately deployed and remotely

integrated with central SAP NetWeaver Portal

Avoid embedded deploym. of BI Web appl. within SAP NetWeaver Portal system

Benefits No need for SAP NetWeaver BI JAVA system,

only SAP NetWeaver AS JAVA runtime required

Known SAP NetWeaver AS JAVA infrastructure


Individual scalability of BI Web applic. and central Portal usage

Independent update cycles of SBOP BI Web Applic. and SAP NetWeaver Portal

Considerations SAP NetWeaver AS JAVA at least 7.3

Example

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

EP/

EP Core

AS JAVA

Central Portal

JEE

SAP BO BI

Business Pack.

BI launch pad remotely

integrated into central Portal

JEEAS JAVA

BI Web Applications

BI Launch Pad

BI Platform

Web Applications

BI Platform


Mngmt. Server

Adaptive

Process. Server

BO

Semantic Layer

BI Client

Process. Server

General Recommendation • Single BI entry point via BI Launch Pad integrated into portal based user access • SBOP BI Web Application system separately deployed and remotely integrated into existing central SAP NetWeaver Portal • Avoid embedded deployment of BI Web application within SAP NetWeaver Portal system Typical Technical Use Case SAP Business Objects BI use cases without need of SAP NetWeaver BI JAVA based scenarios Benefits •No need to implement complete SAP NetWeaver BI JAVA system, only SAP NetWeaver AS JAVA runtime required •Known SAP NetWeaver AS JAVA infrastructure in use •High scalability & proven robustness •Individual scalability of BI Web applications and central SAP NetWeaver Portal usage •Independent update cycles of SBOP BI Web Applic. and SAP NetWeaver Portal possible Considerations SAP NetWeaver AS JAVA needs to be 7.3

Slide 30


Deployment of Business Explorer Web Application BI platform in use, BI JAVA capabilities required


Preferred setup, if BI JAVA based scenarios required

BEx Web system (BI JAVA) to access BEx Web templates

Separate SAP NetWeaver AS JAVA as runtime for SAP BO BI 4.0 web appl.

Benefits No need to upgrade BI JAVA to 7.3

Homogeneous SAP NetWeaver AS JAVA infrastructure


Implementation of new SAP BO BI platform features independent from BI JAVA usage

BEx Web system based on BI JAVA easily to be disabled, if becoming obsolete in the future

Considerations Additional system required

Higher administration effort

Parallel usage of BI Web Apps. and BI JAVA by dedicated port configuration

Example

SRM

Server

SAP SRM

Backend

ABAP

ECC

Server

SAP ERP

Backend

ABAP

Application

Backend

NON SAP

Application

BW

AS ABAP

Business Warehouse

Web

Templates

ABAP

Central BI

Content

Accessing web templates stored

in central BW master system

Accessing BI platform services for

other BI client support

BI Platform


Management

Server

BI Client

Process. Server

BO

Semantic Layer

JEEAS JAVA

BI Web Applications

BI Launch Pad

BI Platform

Web Applications EP

AS JAVA

BEx Web

JEE

BI JAVA

BICS

...BEx Web Apps.

General Recommendation • SAP NW BEx Web and BI Web Server separately deployed •Preferred setup, if BI JAVA based scenarios required (e.g. Information broadcasting) •BEx Web system (BI JAVA) used to access BEx Web templates •SAP NetWeaver AS JAVA system used as separate runtime for SAP Business Objects BI 4.0 web applications (e.g. BI launchpad) Typical Technical Use Case: SAP NetWeaver BI JAVA based scenarios in combination with SAP Business Objects BI 4.0 Benefits •No need to upgrade BI JAVA to 7.3 (needs to be at least at 7.01 SP6 to support SAP NetWeaver BW 7.3) •Homogeneous SAP NetWeaver AS JAVA infrastructure in use •High scalability & proven robustness •Implementation of new SAP BO BI platform features independent from existing BI JAVA usage •BEx Web system based on BI JAVA can easily be disabled, if becoming obsolete in the future Considerations •Additional system required •Higher administration effort •Parallel usage of BI Web Apps. and BI JAVA by dedicated port configuration

Slide 31


Additional Information

Details about SAP Business Objects BI Platform Architecture

Integrating BEx Web Applications:

How to integrate BEx Web Applications into BI 4.x

Business Intelligence Platform Administrator Guide:

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

Slide 32

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 33


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 34


© 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.

Documents

System Landscape Recommendations for SAP NetWeaver Business Warehouse 7.3 - Additional Notes