P. 1
BPC ARCHITECTURE

BPC ARCHITECTURE

|Views: 29|Likes:
Published by Mohd Habib
BPC ARCHITECTURE
BPC ARCHITECTURE

More info:

Published by: Mohd Habib on Oct 30, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

10/30/2013

pdf

text

original

Technical Architecture Overview – SAP BPC

Agenda – Presentation Purpose

Provide an overview of the technology components that comprise the BPC platform Today. Explain how components can be mixed to design an effective infrastructure of a BPC deployment with Version 5. Discuss the factors that influence configuration decisions Identify the hardware and software requirements for the most common configurations Explain the BPC security components List the types of BPC users and the client components required for each Highlight the importance of a development environment High Availability and Disaster Recovery The Next Generations

BPC High Level Architecture Version 5

Presentation Purpose
Presentation Purpose
Web-based platform with centralized database.

Designed for scalability to thousands.

Zero-footprint, Web-based application leveraging cutting-edge technologies

Next generation Service-Oriented Architecture (SOA) providing easy integration.

Patented, enterprise-scale Microsoft Office integration.

Server Technology Stack

SQL Services

Analysis Services

Reporting Services

Application Services

File Services

Web Server

•Microsoft SQL Server – Enterprise Edition 2005 relational database component •Supports data management activities •100% Open Standard • Can be 64 bit when separate from Application/web services

•Microsoft SQL Server – Enterprise Edition 2005 multidimensional database component •Provides detailed analysis & drill down •Can be 64 bit when separate from Application/web services

•Microsoft SQL 2005 Reporting Services •Powerful relational report generator •Supports Journal, Audit and other reporting capabilities •Can be 64 bit when separate from Application/web services or IIS installed

•Microsoft IIS •Supports all SOA (Service Oriented Architecture) •Collection of BPC Services •Where BPC Application Business Logic Resides •Performs user authentication

•Storage location for all application files, UNC or local drive. •Book Repository •Templates •Unstructured Data •Conversion & Transformation Files

•Microsoft IIS •Uses SOAP (Service Oriented Application Protocol) calls for communication using XML between web and application server. •Host for ZFP (Zero footprint) Pages •Performs user authentication

Factors Affecting Installation

SQL Services

Analysis Services EE
SQL

Reporting Services

Application Services

File Services

Web Server

SQL

SQL

IIS

IIS

IIS

SQL Licensing Requirements … Where IIS is Located …

SQL IIS

BPC Application Tiers

Web Tier User Interface for BPC Web, Insight Application Tier XML services, Business Logic, Shared Query Language Database Tier Relational and multi-dimensional data store

Why Single Server

When the number of concurrent users is low If you are setting up a development environment If there are no requirements for separating the MS IIS component from the SQL Database component If the server is in a Workgroup not a Domain No requirements for High Availability (clustering)

Why a Multi Server

When the number of concurrent users is high Corporate policies dictate separating certain components – (e.g. IIS and SQL must not share the same server) Need to separate functional components according to corporate departmental structure Web Services must be hosted in a DMZ Database Services must be hosted internally

Single Server Configuration

SQL Services

Analysis Services EE

Reporting Services

Application Services

File Services

Web Server

SQL Services

Analysis Services EE

Reporting Application Services Services

File Services

Web Server

Sample Single Server Guidelines
Development Environment Minimum CPU’s RAM GB Disk GB 2 2 GB 36 GB Recommended 4 4 GB 72 GB Production Environment Minimum 4 4 GB 72 GB Recommended 4 Dual Core 8 GB 144 GB

RAID Level

RAID 5

OS–RAID 1 Data–RAID 1+0

RAID 5

OS–RAID 1 Data–RAID 1+0

OS

Windows 2003 Standard and Enterprise Edition SP2/R2 (32 bit only) SQL Server 2005 Enterprise Edition or Developer’s Edition 32 bit only, Runtime icensing supported

Windows 2003 Enterprise Edition SP2/R2 (32 bit only) SQL Server 2005 Standard/Enterprise Edition or Developer’s Edition, Runtime Licensing Supported

Contact an BPC Certified Technical Consultant for more information

Multi Server Configuration

SQL Services

Analysis Services EE

Reporting Services

Application Services

File Services

Web Server

Web Services & Reporting Services

Web Tier

Application Services & File Share

Application Tier

SQL Services & Analysis Services

Database Tier

Sample Tier Centric Server Guidelines
Minimum
Web Tier App Tier DB Tier Can be 64 bit CPU’s 2 2 2 Dual Core 2 Dual Core 2 Dual Core Web Tier

Recommended
App Tier DB Tier Can be 64 bit 4 Dual Core

RAM GB

2

2

2

2

4

8

Disk GB

36

36

72

36

72

144

RAID Level

1

1

5

1

1

OS – 1 Data 1+0

OS

Windows 2003 Standard and Enterprise Edition SP2/R2

Windows 2003 Enterprise Edition SP2/R2

Multi Server Configuration – Web Centric
SQL Services Analysis Services EE Reporting Services Application Server File Share Web Server

Database Server and Analysis Services and Reporting Services Database

Reporting Services, File Share, Application Server and Webserver

Web Centric separates SQL relational database from web services

Multi Server Configuration – Database Centric
SQL Services Analysis Services EE Reporting Services Application Server File Share Web Server

DB Server, RS Database and Analysis Services Server

Database Centric - separates all database services from web/file/app services

File Share, Reporting Services, Application Server and Webserver

Multi Server Configuration – Database Centric
SQL Services Analysis Services EE Reporting Services Application Server File Share Web Server

DB Server, RS Database and Web Part and Analysis Services Server

Database Centric - separates all database services from web/file/app services

File Share, Application Server and Webserver

Configuration Options nnn

Several other effective multi server configurations are possible.

Use Technical Consulting to help you determine the optimal configuration for the client.

SQL Services

Analysis Services EE

Reporting Services

Application Services

File Services

Web Server

Tier Authentication

1. Client

Web Server Currently supported using windows (BASIC, NTLM, Kerberos) authentication

2. Client

Application Server Currently supported using windows (BASIC, NTLM, Kerberos) authentication

3. Application Server

BPC System Resources

(SQL services, Analysis services, & File Services). Application Server uses service-level accounts to access resources

Types of Authentication

Domain Users
Do you support Active Directory? Do you have external users not part of your domain? Are all your users in one domain or many Do users log into their local machines with a Domain ID? Will users log into BPC with their Domain ID? Is Transparent Authentication or SSO a requirement?

BPC Users

Authentication Matrix
Authentication Mode:

Security features:

Windows Integrated

Kerberos

LDAP

Basic

Relative security Alternate userid

High Yes, if use BASIC

Higher Only if switch to another authentication mode

Med Yes

Low Yes

Password sent in clear text

No

No

Yes unless use https for login page

Yes unless use https for all pages

Requires Windows ID Works over internet (non-VPN) Works in multi-server environment Requires 1-3 windows service-like accounts (Windows UserIDs for COM+ Components - sysadmin/admin/user)

Yes Must use Basic Yes Yes

Yes No Yes Yes

No Yes Yes Yes

Yes Yes Yes Yes

Prerequisites

Windows ids for each user

Windows ids for each user. Requires proper Kerberos setup - servers all in same domain & trusted for delegation. Users must be trusted, BPC web sites trusted

Existing LDAP server we can read

Windows ids for each user

Client Hardware Requirements
Standard User Power User Admin User

CPU

x86 (600 MHz >)

x86 (1.4 GHz >)

x86 (1.6 GHz >)

RAM

256 MB >

512 MB >

512 MB >

Hard Drive

150 MB

500 MB

1 GB

Other

NIC 100 MBit SVGA 800 x 600

Client Software Requirements

Window XP SP1 (or later), Vista not yet supported Internet Explorer 6.0 SP1 (or later) Microsoft Office
Office XP SP2 (or later) Office 2003 SP3 (or later) Office 2007 Microsoft XML 3.0 SP1 (or later)

Microsoft .NET Framework 1.1 PDF Reader (optional)

Why a Development Environment

A development environment is an integral part of a successful implementation. It provides an environment for:

Testing third party software updates: Windows, SQL, Analysis Services, Reporting Services Can be used as a staging area for new BPC releases that require conversions Testing BPC application set design changes Environment to develop future BPC applications/ application sets Provides Fail Over and/or Disaster Recovery hardware Reduces potential impact on production users resulting from any of the above activities ***Production and Development environments do not have to be identical in hardware or configuration***

Common Client Scenarios

3 Environments Test / Dev UAT (User Acceptance Testing Environment) Production

Common Client Scenarios

3 Environments Test / Dev Single server or partner hosted Can be virtualized UAT (User Acceptance Testing Environment) Mirrors production Production Should run only production appsets Highly recommended to be physical servers

Common Client Scenarios

3 Environments Test / Dev UAT (User Acceptance Testing Environment) Production

Disaster Recovery vs High Availability

Disaster Recovery is the ability to restore the system back to working order in a timely manner.

Includes the recovery of data, hardware, and software Includes a DR plan with a time specified for maximum acceptable recovery time

High availability is the automatic failover of the system.

Includes identical replicas of complete database and application servers with continuous real-time failover Should a server fail or have to be shut down for maintenance a synchronized replica will instantaneously and automatically take its place to ensure continuous application availability and business continuity

Disaster Recovery Possibilities

Use Development Environment as a DR Environment

Your decision is then based on sizing – an exact replica or less performance and access for the time it takes to recover.

Use Backups
You need to see how often you need to backup based on the time frame you need to meet.

SQL Services

Analysis Services EE

Reporting Application Services Services

File Services

Web Server

High Availability Possibilities

Complete Redundancy for each component in the BPC 5 Technology Stack
Microsoft SQL Server 2005 Microsoft Analysis Services 2005 Microsoft Reporting Services 2005 BPC Application Services BPC File Share BPC Web Services

High Availability for Microsoft SQL Server

Microsoft SQL Server 2005 Clustering
SQL Server 2005 Failover Clustering. Can be 64 bit when separate from web/application tier Minimum of 2 node cluster, maximum number of nodes dependent on operating system (Windows 2003 STD vs. ENT) Microsoft Recommends Clustering for data protection and high availability

SQL Services

SQL Services

SAN

High Availability for Microsoft Analysis Services 2005
Microsoft Analysis Services 2005 Clustering
SQL Server 2005 Failover Clustering. Can be 64 bit when separate from web/application tier Minimum of 2 node cluster, maximum number of nodes dependent on operating system (Windows 2003 STD vs. ENT) Microsoft Recommends Clustering for data protection and high availability

Analysis Services

Analysis Services

SAN

High Availability for Microsoft Reporting Services 2005
Microsoft Reporting Services 2005 Load balancing – all nodes active
Support many third party load balancing solutions, for example:

Microsoft Network Load Balancing F5 Big IP Cisco

Load balancing device

Reporting Services

Reporting Services

High Availability for BPC Application Services

BPC Application Services Load balancing – all nodes active
Support many third party load balancing solutions, for example:

Microsoft Network Load Balancing F5 Big IP Cisco

Load balancing device

Application Services

Application Services

High Availability for BPC Web Services

BPC Web Services Load balancing – all nodes active

Support many third party load balancing solutions, for example:

Microsoft Network Load Balancing F5 Big IP Cisco

Load balancing device

Web Server

Web Server

HA MultiServer Environment Example
Database Tiers

SAN

Load balancing device Application Server, Reporting Service and Web Tiers

Requirements for Next-Generation CPM Solutions Architecture Roadmap of Next-Generation CPM Solutions
What’s Next?

SAP BPC 5 Technical Architecture
Rich Clients Admin ActionPane BPC for Excel ActionPane BPC for Word ActionPane BPC for PP ActionPane Browser Thin Client

R

HTTP/SOAP

R

R

HTTP

.NET Web Services R Admin BPF WorkStatus Configuration ... WebUI (ASP.NET) MS Reporting Services

R Application Services WorkStatus LiveReport Content Comments LiveUpdate R Publish Email Audit Session Journal Platform Services BPF Logic Script Logic Admin Configuration R Metadata Data Mgmt. Write Back Shared Query Engine User Mgmt. OLAP Admin DB Connection Factory R Local File Store Insight Scheduling Logging Utilities ZIP, XML, Chart, etc. R R

File Service

R

Send Govenor

R

DB Access DTS/SSIS ADODB ADOMD

R R R

SQL

R

MDX

Persistency MOLAP (Analysis Server) File Server

Source Systems RDBMS (SQL Server) Logic Rel. Store (meta data, etc.) Star Schema

R MD Store

Stored Procedures

SAP BPC 7.0 Technical Architecture
Rich Clients Admin ActionPane BPC for Excel ActionPane BPC for Word ActionPane BPC for PP ActionPane Browser Thin Client

R

HTTP/SOAP

R

HTTP

SAP BPC (.NET) Web Services Admin BPF BPC App Services WorkStatus Configuration ...
R

WebUI icl. Reporting (ASP.NET) R

R Application Services Proxies WorkStatus Configuration Audit Utilities ZIP, XML, Chart, etc. R Application Services BPF Insight

Comments

Email

Metadata

R Platform Services

Content

Journal

User Mgmt.

Write Back

Data Mgmt.

Scheduling Proxy File Service Proxy

Logging

LiveReport

LiveUpdate

Admin

Logic Proxies Parameterdriven Logic Script Logic

Local File Store

R

Session R

Publish

Shared Query Engine

DAO Proxies

R

HTTP/RFC

R

HTTP/RFC

R

ABAP BPC ABAP Function Modules WorkStatus Configuration Audit Comments File Service BPC Data Access Objects Session Insight

User Mgmt.

Email

Metadata

Write Back

Admin

Publish

Journal

Logic Script Logic Logic Modules

Data Mgmt. Data Mgmt. Process Components R R R ABAP Basis RSDRI IF Process Chains ABAP Batch Scheduler SAP Connect (Email) Shared Query Engine

Content

LiveUpdate

BPF

LiveReport

SAP BI (ABAP) BI BAPIs

R

BI ETL

MDX IF

R Database Source Systems InfoProvider BI Metadata BI Masterdata Unstructured Docs BPC Customizing BPC Audit ...

SAP Strategy Management 2007 Technical Architecture
Browser interface thin client Excel interface via Wininet.dll Diagram strategy manager via .net MS IIS •static pages •authentication •redirection of dynamic contents JBoss •application business logic •common services •authorization •interface with data tier
R R R R Pilot Administrator .NET

Browser

Excel

Diagram Manager

R

R

R

HTTP
R

R

TCP/IP

MS IIS
Jakarta ISAPI Filter PilotWorks Static Content
R

MS Usermgmt.
MS Store (pipadmin)

TCP/IP

Java (JBoss) Web PilotWorks Web PilotWorks Console PilotWorks Ext EJB PilotWorks Srv PilotWorks Core R AUTH JPIP Users TCP/IP R PIP (.Net) PIP Listener R SQLite PAS (.NET and Linux/UNIX) TCP/IP R LDAP Server PilotWorks Config

Pilot Interactive Publisher •relational connection pooling •PAS connection pooling •result caching

Pilot Application Server •KPI data store •OLAP engine •Data warehouse interface

Pilot DB

PAS Listener

ODBC /ODBO R Data Warehouse

Stored procedures

Work DB

OLAP DB

MDDB

SAP Strategy Management 7.0 Technical Architecture
R R R
R

Browser

Excel with plug-in HTTP

Diagram Manager

Pilot Administrator .NET
R

R

R

R

TCP/IP

Netweaver CE •application business logic •common services •authorization •interface with data tier •authentication •static content •configuration •database connection pooling •clustering

NW AS Java

Web Server
PilotWorks Static Content PilotWorks Web PilotWorks Core PilotWorks Srv

HTTP / XML IGS

NW AS Database PilotWorks Static Content PilotWorks Config Pilot DB

PIP Config

Users R JPIP UME

PIP Config WS

LDAP Server

Users

HTTP
R

TCP/IP

R

Pilot Interactive Publisher •PAS connection pooling •result caching

PIP (.NET and Linux/UNIX) PIP Listener TCP/IP
R

Pilot Application Server •KPI data store •OLAP engine •Data warehouse interface •Netweaver BI integration

PAS (.NET and Linux/UNIX) PAS Listener MDX over RFC/ OLAP BAPI
R

Stored procedures

Work DB

OLAP DB

SAP BI

Database

Multi-dimensional data access

Data Write Back

Logic Models

Modeling of NW BI Objects in BPC

Configurations

Changes and Flexibility for the Future

?

Thank You for Attending.

Copyright 2007 SAP AG. All Rights Reserved

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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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 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 noninfringement. 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 2007 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®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der 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, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation. Adobe, das Adobe Logo, Acrobat, PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern. ORACLE® ist eine eingetragene Marke der ORACLE Corporation. UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group. Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc. HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 weltweit. 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. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte, Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts. SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialien entstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->