System Landscape Planning and Deployment - BI in SAP NetWeaver 2004s

System Landscape Planning and Deployment:BI in SAP NetWeaver 2004s

SAP NetWeaver Regional Implementation Group

Server Configuration Options

BI / Portal Landscape and FPN

Introduction

System Landscape Overview

SAP AG 2006, SAP NetWeaver 2004s BEx Web – Migration of Web Templates/ 3

BI-Focused IT Scenarios and Their Variants

Enterprise Data Warehousing (EDW)

� Modeling the Enterprise Data Warehouse

� Running the Enterprise Data Warehouse

Enterprise Reporting, Query, and Analysis

� Enterprise Reporting, Query, and Analysis

� Excel Integration

� Ad Hoc Query

� Information Broadcasting

� Visual Composer

Business Planning and Analytical Services

� BI Integrated Planning

Concept Hierarchy: IT Practice

IT Scenario

IT Scenario Variant

IT Scenario Variant Process

Business Information Management


Frontend-related IT Scenarios

IT Scenario Enterprise Reporting, Query, and AnalysisIT Scenario Enterprise Reporting, Query, and AnalysisIT Scenario Enterprise Reporting, Query, and AnalysisIT Scenario Enterprise Reporting, Query, and Analysis

BI Suite: Business Explorer is split into four IT Scenario Variants:

� Enterprise Reporting, Query, and Analysis with BEx Query Designer, BEx Web Application Designer (incl. BEx Web), BEx Report Designer (new)

� Excel Integration with BEx Analyzer

� Ad Hoc Query with BEx Web Analyzer (incl. BEx Web)

� Information Broadcasting with BEx Broadcaster and Broadcaster Wizard

IT Scenario Business Planning and Analytical ServicesIT Scenario Business Planning and Analytical ServicesIT Scenario Business Planning and Analytical ServicesIT Scenario Business Planning and Analytical Services

� BI Integrated Planning with Planning Modeler (WebDynpro-based)

�Business Explorer and BI Integrated Planning require UsageType BI Java

�Using Usage Type BI Java impacts your system landscape



Introduction



System Landscape

This section is about System Landscape aspects:This section is about System Landscape aspects:This section is about System Landscape aspects:This section is about System Landscape aspects:

� Business Explorer and Usage Type BI Java

� Business Explorer and Portal Runtime

� One Portal or two Portals?

� One Server or two Servers?

� One Server (Standalone Installation with two Systems)

� Recommendation

� Configuration Tools

� Summary


Business Explorer and Usage Type BI Java

How does Business Explorer relate to Usage Type BI How does Business Explorer relate to Usage Type BI How does Business Explorer relate to Usage Type BI How does Business Explorer relate to Usage Type BI

Java? Java? Java? Java?

� BEx Web and BI Integrated Planning require Usage Type BI Java

� Usage Type BI Java is based on Usage Type EP and AS Java

How does BEx Web and BI Integrated Planning relate to How does BEx Web and BI Integrated Planning relate to How does BEx Web and BI Integrated Planning relate to How does BEx Web and BI Integrated Planning relate to

Portal and Java?Portal and Java?Portal and Java?Portal and Java?

� BEx Web runtime generates output for Web Browser

� BEx Web requires Java-based Portal runtime functionality (for rendering as iView, for System integration, etc.)

� BI Integrated Planning requires WebDynpro-based Planning Modeler

�Functionality: BEx Web is using Portal as infrastructure andplatform (visible if desired, hidden if not)

�Project considerations: BEx Web requires Java technology and not an Enterprise Portal project

�System Landscape: BEx Web requires Usage Type EP and AS Java


Business Explorer and Portal Runtime

Which features of Business Explorer in SAP NetWeaver Which features of Business Explorer in SAP NetWeaver Which features of Business Explorer in SAP NetWeaver Which features of Business Explorer in SAP NetWeaver

2004s require Portal runtime?2004s require Portal runtime?2004s require Portal runtime?2004s require Portal runtime? (*)

� New BEx Web Application Designer (Unicode, Command Wizard, ...)

� Exporting to PDF and Printing

� BI Integrated Planning

� Drag&Drop (Analysis Web Item)

� Web Items (Container Layout, Menu Bar, Tab Pages, Button Group, ...)

� Formatted Reporting with BEx Report Designer

� Document Integration with storage in Knowledge Management

� ...

(*) Please remember that all new features of IT scenario Enterprise Reporting, Query, and Analysis (incl. variant Excel Integration with BEx Analyzer) require Usage Type AS Java and EP (i.e. Portal runtime)


Overview: Usage Types, Standalone Engines, Clients

Optional Usage Type based on

AS-ABAP

Tool/Client

Usage Type based on AS-ABAP

Optional Usage Type based on AS-ABAP and AS-Java

Usage Type based on AS-ABAP and

AS-Java

Optional Usage Type based on

AS-Java

Usage Type based on AS-Java

Optional Tool/Client

Standalone Engine

Optional Standalone Engine

Third-Party Component

System

A+J

Physicalhost

Physical database with ABAP and/or Java schema

Key

BI

accelerator


Configuration Tools

TemplateTemplateTemplateTemplate----Based Basic ConfigurationBased Basic ConfigurationBased Basic ConfigurationBased Basic Configuration

� Portal-based Template Installer for automatic configuration

� Easy to execute

� Same steps as Implementation Guide

Integration into the PortalIntegration into the PortalIntegration into the PortalIntegration into the Portal

� ABAP-based Implementation Guide (IMG)for manual/semi-automatic configuration

� Report RSPOR_SETUP

� Step by step

� Useful for problem analysis (incl. checks)

See note 917950 for detailsSee note 917950 for detailsSee note 917950 for detailsSee note 917950 for details


System Landscape – Portal User Management

Type of Portal User Management?

� If LDAP exists, use LDAP as central user management

� If no LDAP exists, reuse of existing BI user with ABAP persistence

� Java database persistence is not recommended due double maintenance of users

If you install a Portal, always select the Java database persistence during setup. Because only Java database persistence ensures that you can switch to LDAP or ABAP persistence.

You can change the type of User Management just after the setup.

See Note 718383 for details.



Introduction



One Server or two Servers?

Installation optionsInstallation optionsInstallation optionsInstallation options

Usage Types AS ABAP (incl. BI) and AS Java (incl. EP and BI Java)…

� … as Add-In Installation on one server as one system (MCOS, one SAPSYSTEMNAME, one DB)

� … as Standalone Installation on one server as two different systems

� … as Standalone Installation on two servers as two different systems

�� Due the flexibility of SAP NetWeaver, you could move your systemfrom option 1 to 2, 1 to 3 or 2 to 3

� In case of 1 to 2 or 1 to 3, you have to rebuild your Java-Stack but you could transport your content


Standalone Installation on one server as two different systemsStandalone Installation on one server as two different systemsStandalone Installation on one server as two different systemsStandalone Installation on one server as two different systems

� Server itself can scale or split to two servers possible

� High scalability

� Dialog Instances could be mixed or separate

��AS ABAP and AS Java could be scaled independently

� Recommended System Landscape

One Server (Standalone Installation with two Systems)

Central Instance (two System IDs) Dialog Instances

Physical Server

System


Server Architectural Recommendation

Use existing BI serverUse existing BI serverUse existing BI serverUse existing BI server

� Based on load and performance tests, existing BI server should be sufficient even with Usage Types AS Java, EP and BI Java

Upgrade SAP BW 3.x to BI in SAP NetWeaver 2004sUpgrade SAP BW 3.x to BI in SAP NetWeaver 2004sUpgrade SAP BW 3.x to BI in SAP NetWeaver 2004sUpgrade SAP BW 3.x to BI in SAP NetWeaver 2004s

Perform standalone installation on one server with two Perform standalone installation on one server with two Perform standalone installation on one server with two Perform standalone installation on one server with two different systemsdifferent systemsdifferent systemsdifferent systems

� Best combination of lowest hardware requirements and highest flexibility due…

Scalability (dialog instances could be scaled independently)

Start/Stop (combined using SAPMMC)

System downtime (independent between AS ABAP and AS Java)

Choose ABAP as User Management Engine (UME) Choose ABAP as User Management Engine (UME) Choose ABAP as User Management Engine (UME) Choose ABAP as User Management Engine (UME) configurationconfigurationconfigurationconfiguration

� Reduce administrator effort by using combined user persistence

� Automatic configuration of UME is one advantage of Add-In Installation


Performance & Sizing Considerations

Moving Load from AS-ABAP to AS-Java

� In SAP NetWeaver 2004s, load is moved from AS-ABAP to AS-Java

� BEx Web (BI-Java) generates load on Portal (AS-Java)

� BI users generate more load on Portal than normal Enterprise Portal users

� Refer back to the One portal vs. two portal discussion earlier

Sizing your AS-ABAP and AS-Java systems

� Usage Types AS-Java and EP require additional CPU and memory (overhead)

� Minimum requirements for Usage Type AS-Java and EP is 2 CPUs and 4 GB of memory (*)

� BEx Web aspect of capacity planning analysis is re-focused to AS-Java


Performance & Sizing Considerations (cont.)

Sample Sizing

� Before upgrade 100% ABAP (about 25% BEx) (*)

� Upgrade requires about 25% more CPU and memory for Java (Portal) (125% in total) (**)

� After upgrade 75% ABAP (without 25% BEx) and 50% Java (25% BEx)

(*) BEx Web percentage share based on performance analysis in your system

(**) Sample BI system with 8 CPU and 16 GB memory would require additional 2 CPU and 4 GB memory for Java (Portal)

BeforeBefore After



Introduction



Standalone Engines

Clients

Web Browser SAP GUI

Search and Classification

(TREX)

Visual Composer

Systems with Usage Types

AS-Java

EP

BI-Java

AS-ABAP

BI

Internet Graphics Service

comprised

Adobe document services

comprised

Business Explorer (BI)

System Landscape: Focus on BI – Portal Architecture

Clients

IGS

BI

AS-ABAP

NW04s BI / / / / Portal System Landscape Architecture Key Points:

� There can only be a 1:1 relationship between a NW04s BI instance and a NW04s Portal instance

� Either an existing SAP portal must be used for BI query runtime, or a new portal must be dedicated to support the BI query (BEx) runtime (running together with an existing portal)

� Multiple production BI systems drives a more complex portal landscape (because of the 1:1 relationship)

New technical

architecture... NW04s

has a1:1 BI Instance to Portal instance relationship only!

EP

BI-JAVA

AS-JAVA

Usage Types


One Portal or two Portals?

Two PortalsTwo PortalsTwo PortalsTwo Portals…………

� Different user groups(in general, Enterprise Portal user group is larger than BI user group)

� Two Portals if one Portal is for BI only and one Enterprise Portal

One PortalOne PortalOne PortalOne Portal…………

� Common user group (identical users)

� One Portal for both use cases (BI Portal and Enterprise Portal)

�Two Portals could be integrated by Federated Portal Network(see Integration into Enterprise Portal)

�No Support Package synchronization between BI and Enterprise Portal

�Might require upgrade of Enterprise Portal

�Support Package synchronization between BI and Enterprise Portal


Content Federation - Concept

Only one portal installation functions as the portal serving users, the

remaining portal installations function as content producers.

Consumer

Producer

CRM

Producer Producer Producer

ApplicationApplication

ApplicationERP

Producer

BI 2004s

Non SAP WSRP compliant Producer


Designing Your Landscape – Federated Portal

A Federated Portal (Global Portal) provides application functionality for managing a system landscape, including multiple SAP NetWeaver 2004s Portals (*):

� The central enterprise portal is called the consumer portal, and provides a single access point for end users

� All other portals are called producer portals, and can be linked to the consumer portal

� The consumer portal can integrate complete portal roles of a producer portal

– Currently, cannot combine roles from several producer portals

– Use Remote URL iViews instead to create portal roles with content from several producer portals

� Information Broadcasting integrated with Producer Portal

� Broadcasting between different producer Portals is not possible

See http://service.sap.com/nw-fpn for more details on Federated Portal


Designing Your Landscape – Federated Portal

System Landscape with Federated Portal

Producer

EP PortalContent

BI

KMContent

Producer

EP PortalContent

BI

KMContent

SAP BW 3.x

Consumer

EP

PortalContent

KMContent

(1) Remote Role Assignment (*)(2) Information Broadcasting(3) Producer URL iView in Portal

Content Studio (**)(4) BW iView in Portal Content

Studio

(1) and (3) (4)(1) and (3)

(2)(2)


Designing Your Landscape – SAP EP 6.0 and NW04s BI

System Landscape with SAP EP 6.0 as Enterprise Portal (*)

(***) Producer URL iViews are supported with SAP NetWeaver 2004 SP 17

Producer Producer

EP PortalContent

BI

KMContent

EP PortalContent

BI

KMContent

SAP BW 3.x

Enterprise Portal

EP 6.0

PortalContent

KMContent

(3) (4)(3)

(2)(2)

(1) N/A(2) Information Broadcasting(3) Producer URL iView in Portal

Content Studio (***)(4) BW iView in Portal Content

Studio


Federated Portal: Content Sharing Techniques

The content is shared throughout the network using three content usage modes:

� Remote Role Assignment – enables the consumer administrator to

assign complete roles offered by an SAP producer.

– Technique Used by BI

� Producer URL iView – iView with execution based on producer is

visible from consumer portal

– Utilized for BI Information Broadcasting to Portal Content Directory

� Remote Content Copy - enables the consumer to localize and use

content offered by an SAP producer.

– Not recommended for BI, avoid resource utilization on consumer portal

� WSRP Content Sharing - enables the consumer to provide its users

with portlets offered by a WSRP-compliment SAP or Non-SAP producer.

– Most relevant for integrating with non-SAP portals


FPN – Some General Benefits

�Synchronization of content can be ensured by using the remote role assignment content usage mode.

�De-couple support package synchronization requirements

�Integrate non-SAP portals into the SAP NetWeaver platform and exchange WSRP-compliant applications with SAP NetWeaver Portal.

�Secure access to content applications spread worldwide.

�Reduce the total cost of ownership (TCO) by reusing content and applications worldwide and increasing the autonomy of business units.

�Increase return on investment (ROI) by optimizing the reuse of human capital and hardware resources within the company at a relatively low investment.


FPN: Multi Version Support

� Not all business packages provide multi version support.

� The FPN can be used to provide multi version support.

� FPN should not be implemented only to provide multi version support.

Consumer

CRM 3.1 CRM 3.5

Producer

BP for CRM 3.1

Producer

BP for CRM 3.5


FPN: Supporting Different Service Level Agreements

� Each producer can support a different level of SLA.

� The consumer should always be available.

Consumer

ERP

Producer

Critical applications should always be available

Producer

Web Content and information


Interoperability with non SAP Portals

� Provide access to Non SAP WSRP compliant producer applications.

� Enables the integration of these application within the consumer local content.

Consumer




FPN: Code Isolation

Producer

Home grown application

Consumer



� Home grown applications are not rendered on the portal server to which all users log in.

� Reduce the risk of consumer portal failover because of a home grown application.

Producer





Consolidating portal content after mergers and acquisitions

� After consolidating all users to the same portal the applications remain on the producers until full consolidation is completed.

Consumer

Producer of company acquired Producer of company acquired


FPN – Knowledge Management considerations

1. Remote KM Navigation iView (recommended if no combined storage is required)

� Documents are displayed with a KM Navigation iView of the Producer Portal accessed remotely from the Consumer Portal (like Remote Role Assignment)

� Storage of documents remains in Producer Portal

� All properties are accessible and usable

� Combined storage of documents from different Producer Portal notpossible



2. CM Repository Manager (recommended if combined storage is required)

� Documents are stored in file system (not in database)

� Both KM uses CM Repository Manager to access the documents (typefsdb; document in file system and properties in database)

� Only file system properties are supported (Creation date, Last Access, etc.)

� KM Properties are not supported (Creator, Modifier, Application properties [services like feedback, subscription, etc.])

� Services on Consumer Portal’s Subscription is possible

� Possible time lag due Synchronizer (default “per request”; this is not critical)

� Problem: concurrent creation/change of documents à Consumer Portal could be read only



3. WebDAV (not recommended)

� Usage of WebDAV to access documents is not recommended due low performance

� Change of documents is possible

� Not all properties are supported

� Manual user mapping could be required

� Combined storage of documents from different Producer Portal possible

� Documentation: http://help.sap.com/saphelp_nw2004s/helpdata/en/4a/217fb6c33c6748a1715a161ac942cd/frameset.htm



4. ICE (Information and Content Exchange, not recommended)

� Document are frequently copied from Producer Portal’s KM to Consumer Portal’s KM

� No delta copy possible, only complete copy of all files

� Not recommended due time lag of copy process and no support of delta copy

� Consumer Portal should not change documents (read only; changes could be overwritten)

� All properties are accessible and usable

� Combined storage of documents from different Producer Portal notpossible

� Documentation: http://help.sap.com/saphelp_nw2004s/helpdata/en/35/4cf72bfe18455e892fc53345f4f919/frameset.htm


FPN – Collaboration considerations

Collaboration

� Room Directory not support via FPN

� Individual Collaboration Rooms supported via Remote URL iView


System Landscape Summary

Yes, Business Explorer and BI Integrated Planning in SAP Yes, Business Explorer and BI Integrated Planning in SAP Yes, Business Explorer and BI Integrated Planning in SAP Yes, Business Explorer and BI Integrated Planning in SAP NetWeaver 2004s require Portal, butNetWeaver 2004s require Portal, butNetWeaver 2004s require Portal, butNetWeaver 2004s require Portal, but…………

More details about System Landscapes under https://service.sap.com/bifaq �� SAP NetWeaver 2004s �� Query, Reporting & Analysis Design

�� No Enterprise Portal project required (BI owns Portal content ofBI Portal)

�� No second Server is required

�� No Portal training for end users required

�� No double maintenance of user required

�� No assignment of Portal Roles required

�� No additional effort to integrate into Enterprise Portal (same orless effort)


Further Information & Links

�� FAQs SAP NetWeaver 2004shttps://service.sap.com/bifaq --> SAP NetWeaver 2004s

�� SAP NetWeaver

https://service.sap.com/NetWeaver

�� Upgrade / Installation Info

https://service.sap.com/instguidesNW2004s

�� IT Scenarios

https://service.sap.com/it-scenarios

�� New Release Strategy

https://service.sap.com/releasestrategy

��

��

Services from SAP Support and SAP Consulting

�� SDN forum “BI in SAP NetWeaver 2004s”https://forums.sdn.sap.com/forum.jspa?forumID=154&start=0

�� Platforms

https://service.sap.com/platforms

�� Product Availability Matrix

https://service.sap.com/pam

�� Safe Guarding Upgrade

https://service.sap.com/safeguardingupgr

ade

�� SAP NetWeaver BI

https://service.sap.com/bi

Upgr. / Migration Info in Docu (TOM)http://help.sap.com/saphelp_nw2004s/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htm

Support Package Stackshttps://websmp101.sap-

ag.de/~form/sapnet?_SHORTKEY=01100035870000668996&

SAP Plug In

http://service.sap.com/R3-Plug-In

�� Education / Courseshttps://pgwshop.sap-ag.de/scripts/wgate/yhwbus/!?user=SPUBLIC


� 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

� IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

� Oracle is a registered trademark of Oracle Corporation.

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

� Java is a registered trademark of Sun Microsystems, Inc.

� JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

� MaxDB is a trademark of MySQL AB, Sweden.

� SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.

� This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

� SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

� The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use

of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Copyright 2006 SAP AG. All Rights Reserved