P. 1
BPC Technical Architecture and Data Integration

BPC Technical Architecture and Data Integration

|Views: 24|Likes:

More info:

Published by: Muhammad Siddique Ansari on Feb 23, 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

01/01/2014

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.

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

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 .

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

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

g.Why a Multi Server When the number of concurrent users is high Corporate policies dictate separating certain components – (e. 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 .

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

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 .

File Share.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. Application Server and Webserver Web Centric separates SQL relational database from web services .

separates all database services from web/file/app services File Share. RS Database and Analysis Services Server Database Centric . Application Server and Webserver . Reporting Services.Multi Server Configuration – Database Centric SQL Services Analysis Services EE Reporting Services Application Server File Share Web Server DB Server.

Multi Server Configuration – Database Centric SQL Services Analysis Services EE Reporting Services Application Server File Share Web Server DB Server.separates all database services from web/file/app services File Share. Application Server and Webserver . RS Database and Web Part and Analysis Services Server Database Centric .

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 .Configuration Options nnn Several other effective multi server configurations are possible.

Kerberos) authentication 3. & File Services). NTLM.Tier Authentication 1. Analysis services. Kerberos) authentication 2. Application Server BPC System Resources (SQL services. Client Application Server Currently supported using windows (BASIC. Application Server uses service-level accounts to access resources . NTLM. Client Web Server Currently supported using windows (BASIC.

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 .

Requires proper Kerberos setup . 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 .servers all in same domain & trusted for delegation.Authentication Matrix Authentication Mode: Security features: Windows Integrated Kerberos LDAP Basic Relative security Alternate userid High Yes. Users must be trusted.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. 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.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 .4 GHz >) x86 (1.

Vista not yet supported Internet Explorer 6.Client Software Requirements Window XP SP1 (or later).0 SP1 (or later) Microsoft Office Office XP SP2 (or later) Office 2003 SP3 (or later) Office 2007 Microsoft XML 3.NET Framework 1.0 SP1 (or later) Microsoft .1 PDF Reader (optional) .

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*** . Analysis Services.Why a Development Environment A development environment is an integral part of a successful implementation. SQL. It provides an environment for: Testing third party software updates: Windows.

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 .

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 . Includes the recovery of data. hardware.Disaster Recovery vs High Availability Disaster Recovery is the ability to restore the system back to working order in a timely manner.

SQL Services Analysis Services EE Reporting Application Services Services File Services Web Server .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.

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. 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 . Can be 64 bit when separate from web/application tier Minimum of 2 node cluster.

Can be 64 bit when separate from web/application tier Minimum of 2 node cluster.High Availability for Microsoft Analysis Services 2005 Microsoft Analysis Services 2005 Clustering SQL Server 2005 Failover Clustering. 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 .

for example: Microsoft Network Load Balancing F5 Big IP Cisco Load balancing device Reporting Services Reporting Services .High Availability for Microsoft Reporting Services 2005 Microsoft Reporting Services 2005 Load balancing – all nodes active Support many third party load balancing solutions.

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 .

for example: Microsoft Network Load Balancing F5 Big IP Cisco Load balancing device Web Server Web Server .High Availability for BPC Web Services BPC Web Services Load balancing – all nodes active Support many third party load balancing solutions.

Reporting Service and Web Tiers .HA MultiServer Environment Example Database Tiers SAN Load balancing device Application Server.

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

WebUI (ASP. OLAP Admin DB Connection Factory R Local File Store Insight Scheduling Logging Utilities ZIP.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 ..) Star Schema R MD Store Stored Procedures .. Chart. Store (meta data. etc.NET Web Services R Admin BPF WorkStatus Configuration . etc.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. XML. Write Back Shared Query Engine User Mgmt. 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.

R Application Services BPF Insight Comments Email Metadata R Platform Services Content Journal User Mgmt..NET) Web Services Admin BPF BPC App Services WorkStatus Configuration . etc.. Data Mgmt. XML. 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..SAP BPC 7. Reporting (ASP. R WebUI icl. 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 . Write Back Data Mgmt.NET) R R Application Services Proxies WorkStatus Configuration Audit Utilities ZIP.. Chart. Email Metadata Write Back Admin Publish Journal Logic Script Logic Logic Modules Data Mgmt. .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 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 .SAP Strategy Management 2007 Technical Architecture Browser interface thin client Excel interface via Wininet.NET Browser Excel Diagram Manager R R R HTTP R R TCP/IP MS IIS Jakarta ISAPI Filter PilotWorks Static Content R MS Usermgmt.Net) PIP Listener R SQLite PAS (.dll Diagram strategy manager via .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 . 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 (.

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 (.SAP Strategy Management 7.NET and Linux/UNIX) PAS Listener MDX over RFC/ OLAP BAPI R Stored procedures Work DB OLAP DB SAP BI Database .NET and Linux/UNIX) PIP Listener TCP/IP R Pilot Application Server •KPI data store •OLAP engine •Data warehouse interface •Netweaver BI integration PAS (.

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

graphics. SAP does not warrant the accuracy or completeness of the information. indirect. Windows. Java is a registered trademark of Sun Microsystems. and MultiWin are trademarks or registered trademarks of Citrix Systems. Intelligent Miner. System i. developments. and PowerPoint are registered trademarks of Microsoft Corporation. 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. System z9.Copyright 2007 SAP AG. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Data contained in this document serves informational purposes only. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. fitness for a particular purpose. DB2. System i5. UNIX. This document contains only intended strategies. OSF/1. All other product and service names mentioned are the trademarks of their respective companies. AFP. Microsoft. links. zSeries. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. pSeries. Program Neighborhood. mySAP. DB2 Universal Database. WinFrame. This document is provided without a warranty of any kind. S/390. the Adobe logo. Inc. OS/390. special. xApps. X/Open. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This limitation shall not apply in cases of intent or gross negligence. Please note that this document is subject to change and may be changed by SAP at any time without notice. xSeries. OS/2. IBM. used under license for technology invented and implemented by Netscape. mySAP. Oracle is a registered trademark of Oracle Corporation. Adobe. System x. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. SAP. iSeries. JavaScript is a registered trademark of Sun Microsystems. or other items contained within this material. ICA. Citrix. System p5. MetaFrame. R/3. 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. Massachusetts Institute of Technology. product strategy. copied. The statutory liability for personal injury and defective products is not affected. POWER5+. XML. including but not limited to the implied warranties of merchantability. National product specifications may vary. Tivoli. Netfinity. AS/400. Informix. text. SAP assumes no responsibility for errors or omissions in this document. System z. either express or implied. WebSphere. and Motif are registered trademarks of the Open Group. SAP shall have no liability for damages of any kind including without limitation direct. 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. . OS/400. Sweden. XHTML and W3C are trademarks or registered trademarks of W3C®. Outlook. i5/OS. Inc. OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Excel. No part of this document may be reproduced. Acrobat. or consequential damages that may result from the use of these materials. The information contained herein may be changed without prior notice. World Wide Web Consortium.com. or noninfringement.. MaxDB is a trademark of MySQL AB. xApp. Parallel Sysplex. HTML. VideoFrame. POWER5. SAP NetWeaver. POWER. AIX. and/or development. z/OS. Inc. MVS/ESA. System p. PostScript. The information in this document is proprietary to SAP.

bereitgestellt. World Wide Web Consortium. VideoFrame®. das Adobe Logo. unterliegen nicht dem Einfluss von SAP. xSeries. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. S/390. mySAP. AFP. Schweden. das Citrix-Logo. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind.oder Produktstrategie und/oder bestimmten Entwicklungen. die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. JAVA® ist eine eingetragene Marke der Sun Microsystems. i5/OS. besondere und mittelbare Schäden oder Folgeschäden. Citrix®. HTML. OS/2. auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen. POWER5. Netfinity. PowerPoint® und SQL Server® sind eingetragene Marken der Microsoft Corporation. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. UNIX®. MetaFrame®. WebSphere. OSF/1® und Motif® sind eingetragene Marken der Open Group. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen. Links und sonstigen in dieser Publikation enthaltenen Elementen. mySAP. z/OS. Texte. Informix. AIX. Dies gilt u. MultiWin® und andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems. Entwicklungen und Funktionen des SAP®-Produkts. SAP haftet nicht für entstandene Schäden.com. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. Word®. PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. SAP. System p5. pSeries. Grafiken. WINDOWS®. Intelligent Miner. Adobe.Copyright 2007 SAP AG. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts. Dies gilt u. . ICA®. Tivoli. DB2. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. AS/400. und uneingeschränkt für konkrete. xApp. Acrobat. POWER5+. OS/390. R/3. zSeries. EXCEL®. Parallel Sysplex. POWER.. nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. NT®. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Bei dieser Publikation handelt es sich um eine vorläufige Version. System z9. System i. IBM. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Inc. weder ausdrücklich noch stillschweigend. DB2 Universal Database. und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. Inc. a. a. 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. OS/400.. Diese Publikation enthält nur vorgesehene Strategien. ORACLE® ist eine eingetragene Marke der ORACLE Corporation. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation. System z. xApps. Massachusetts Institute of Technology. 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. JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. System x. zu welchem Zweck und in welcher Form auch immer. XML. XHTML sind Marken oder eingetragene Marken des W3C®. MaxDB ist eine Marke von MySQL AB. Inc. aber nicht ausschließlich. X/Open®. Die Informationen. iSeries. Program Neighborhood®. SAP NetWeaver. die aus der Nutzung dieser Materialien entstehen können. DHTML. Microsoft®. zu welchem Zweck und in welcher Form auch immer. MVS/ESA. Diese Publikation wird ohne jegliche Gewähr. in den USA und/oder anderen Ländern. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Produkte können länderspezifische Unterschiede aufweisen. WinFrame®. System i5. System p.

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)//-->