Technical Architecture Overview SAP BPC

Transcription

1 Technical Architecture Overview SAP BPC

2 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 ecovery The Next Generations

3 BPC High Level Architecture Version 5

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

5 Server Technology Stack SQL Analysis eporting Application File 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 eporting 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 Where BPC Application Business Logic esides Performs user authentication Storage location for all application files, UNC or local drive. Book epository 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

6 Factors Affecting Installation SQL Analysis EE eporting Application File Web Server SQL SQL SQL IIS IIS IIS SQL Licensing equirements SQL Where IIS is Located IIS

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

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

9 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 must be hosted in a DMZ Database must be hosted internally

10 Single Server Configuration SQL Analysis EE eporting Application File Web Server SQL Analysis EE eporting Application File Web Server

11 Sample Single Server Guidelines Development Environment Production Environment Minimum ecommended Minimum ecommended CPU s Dual Core AM GB 2 GB 4 GB 4 GB 8 GB Disk GB 36 GB 72 GB 72 GB 144 GB AID Level AID 5 OS AID 1 AID 5 OS AID 1 Data AID 1+0 Data AID 1+0 OS Windows 2003 Standard and Enterprise Edition SP2/2 (32 bit only) SQL Server 2005 Enterprise Edition or Developer s Edition 32 bit only, untime icensing supported Windows 2003 Enterprise Edition SP2/2 (32 bit only) SQL Server 2005 Standard/Enterprise Edition or Developer s Edition, untime Licensing Supported Contact an BPC Certified Technical Consultant for more information

12 Multi Server Configuration SQL Analysis EE eporting Application File Web Server Web & eporting Web Tier Application & File Share Application Tier SQL & Analysis Database Tier

13 Sample Tier Centric Server Guidelines Minimum ecommended Web Tier App Tier DB Tier Web Tier App Tier DB Tier Can be 64 bit Can be 64 bit CPU s Dual Core 2 Dual Core 2 Dual Core 4 Dual Core AM GB Disk GB AID Level OS 1 Data OS Windows 2003 Standard and Enterprise Edition SP2/2 Windows 2003 Enterprise Edition SP2/2

14 Multi Server Configuration Web Centric SQL Analysis EE eporting Application Server File Share Web Server Database Server and Analysis and eporting Database eporting, File Share, Application Server and Webserver Web Centric - separates SQL relational database from web services

15 Multi Server Configuration Database Centric SQL Analysis EE eporting Application Server File Share Web Server DB Server, S Database and Analysis Server File Share, eporting, Application Server and Webserver Database Centric - separates all database services from web/file/app services

16 Multi Server Configuration Database Centric SQL Analysis EE eporting Application Server File Share Web Server DB Server, S Database and Web Part and Analysis Server File Share, Application Server and Webserver Database Centric - separates all database services from web/file/app services

17 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 Analysis EE eporting Application File Web Server

18 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 esources (SQL services, Analysis services, & File ). Application Server uses service-level accounts to access resources

19 Types of Authentication Domain Users BPC 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?

20 Authentication Matrix Authentication Mode: Security features: Windows Integrated Kerberos LDAP Basic elative security High Higher Med Low Alternate userid Yes, if use BASIC Only if switch to another authentication mode Yes Yes Password sent in clear text No No Yes unless use https for login page Yes unless use https for all pages equires Windows ID Yes Yes No Yes Works over internet (non-vpn) Must use Basic No Yes Yes Works in multi-server environment Yes Yes Yes Yes equires 1-3 windows service-like accounts (Windows UserIDs for COM+ Components - sysadmin/admin/user) Yes Yes Yes Yes Prerequisites Windows ids for each user Windows ids for each user. equires 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

21 Client Hardware equirements Standard User Power User Admin User CPU x86 (600 MHz >) x86 (1.4 GHz >) x86 (1.6 GHz >) AM 256 MB > 512 MB > 512 MB > Hard Drive 150 MB 500 MB 1 GB Other NIC 100 MBit SVGA 800 x 600

22 Client Software equirements 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 eader (optional)

23 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, eporting 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 ecovery hardware educes 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***

24 Common Client Scenarios 3 Environments Test / Dev UAT (User Acceptance Testing Environment) Production

25 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

26 Common Client Scenarios 3 Environments Test / Dev UAT (User Acceptance Testing Environment) Production

27 Disaster ecovery vs High Availability Disaster ecovery 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 D 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

28 Disaster ecovery Possibilities Use Development Environment as a D 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 Analysis EE eporting Application File Web Server

29 High Availability Possibilities Complete edundancy for each component in the BPC 5 Technology Stack Microsoft SQL Server 2005 Microsoft Analysis 2005 Microsoft eporting 2005 BPC Application BPC File Share BPC Web

30 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 ecommends Clustering for data protection and high availability SQL SQL SAN

31 High Availability for Microsoft Analysis 2005 Microsoft Analysis 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 ecommends Clustering for data protection and high availability Analysis Analysis SAN

32 High Availability for Microsoft eporting 2005 Microsoft eporting 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 eporting eporting

33 High Availability for BPC Application BPC Application 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 Application

34 High Availability for BPC Web BPC Web 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

35 HA MultiServer Environment Example Database Tiers SAN Load balancing device Application Server, eporting Service and Web Tiers

36 equirements for Next-Generation CPM Solutions Architecture oadmap of Next-Generation CPM Solutions What s Next?

37 SAP BPC 5 Technical Architecture ich Clients Thin Client Admin ActionPane BPC for Excel ActionPane BPC for Word ActionPane BPC for PP ActionPane Browser HTTP/SOAP HTTP.NET Web Admin BPF WorkStatus Configuration... WebUI (ASP.NET) MS eporting Application Utilities WorkStatus Liveeport Content Comments LiveUpdate ZIP, XML, Chart, etc. Publish Audit Session Journal Platform BPF Logic Insight Scheduling Logging Script Logic Admin Configuration OLAP Admin Local File Store Metadata Data Mgmt. Write Back Shared Query Engine User Mgmt. DB Connection Factory File Service Send Govenor DB Access DTS/SSIS ADODB ADOMD SQL MDX Persistency MOLAP (Analysis Server) File Server Source Systems MD Store DBMS (SQL Server) el. Store (meta data, etc.) Star Schema Logic Stored Procedures

38 SAP BPC 7.0 Technical Architecture ich Clients Thin Client Admin BPC for Excel BPC for Word BPC for PP ActionPane ActionPane ActionPane ActionPane Browser HTTP/SOAP HTTP SAP BPC (.NET) Web Admin BPF BPC App WorkStatus Configuration... WebUI icl. eporting (ASP.NET) Application Proxies Utilities Application WorkStatus Configuration Audit ZIP, XML, Chart, etc. BPF Insight Comments Metadata Content Journal Platform User Mgmt. Write Back Data Mgmt. Scheduling Proxy Logging Liveeport LiveUpdate Admin Shared Query Engine Logic Proxies Parameterdriven Logic Script Logic File Service Proxy Local File Store Session Publish DAO Proxies HTTP/FC HTTP/FC ABAP BPC ABAP Function Modules BPC Data Access Objects WorkStatus Configuration Audit Comments File Service Session Insight User Mgmt. Metadata Write Back Admin Publish Journal Logic Script Logic Logic Modules Data Mgmt. Data Mgmt. Process Components Shared Query Engine Content LiveUpdate BPF Liveeport SAP BI (ABAP) ABAP Basis BI BAPIs SDI IF Process Chains ABAP Batch Scheduler BI ETL MDX IF SAP Connect ( ) Database Source Systems InfoProvider BI Metadata BI Masterdata Unstructured Docs BPC Customizing BPC Audit...

39 SAP Strategy Management 2007 Technical Architecture Browser interface thin client Excel interface via Wininet.dll Diagram strategy manager via.net Browser Excel Diagram Manager HTTP Pilot Administrator.NET TCP/IP MS IIS static pages authentication redirection of dynamic contents Jakarta ISAPI Filter MS IIS TCP/IP PilotWorks Static Content MS Usermgmt. MS Store (pipadmin) JBoss application business logic common services authorization interface with data tier Java (JBoss) Web PilotWorks Web PilotWorks Console PilotWorks Ext EJB PilotWorks Srv PilotWorks Core AUTH PilotWorks Config LDAP Server JPIP Pilot Interactive Publisher relational connection pooling PAS connection pooling result caching PIP (.Net) PIP Listener SQLite TCP/IP Users TCP/IP PAS (.NET and Linux/UNIX) Pilot Application Server KPI data store OLAP engine Data warehouse interface Pilot DB PAS Listener ODBC /ODBO Stored procedures Work DB OLAP DB Data Warehouse MDDB

40 SAP Strategy Management 7.0 Technical Architecture Browser Excel with plug-in Diagram Manager Pilot Administrator.NET HTTP 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 PilotWorks Static Content PilotWorks Web NW AS Database PilotWorks Static Content PIP Config PIP Config WS Web Server PilotWorks Core PilotWorks Config JPIP PilotWorks Srv Pilot DB Users UME HTTP / XML IGS LDAP Server Users HTTP TCP/IP Pilot Interactive Publisher PAS connection pooling result caching PIP (.NET and Linux/UNIX) PIP Listener TCP/IP Pilot Application Server KPI data store OLAP engine Data warehouse interface Netweaver BI integration PAS (.NET and Linux/UNIX) Stored procedures PAS Listener Work DB OLAP DB MDX over FC/ OLAP BAPI SAP BI Database

41 Multi-dimensional data access

42 Data Write Back

43 Logic Models

44 Modeling of NW BI Objects in BPC

45 Configurations

46 Changes and Flexibility for the Future?

47 Thank You for Attending.

48 Copyright 2007 SAP AG. All ights eserved 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, POWE, POWE5, POWE5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and eader 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, /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.

49 Copyright 2007 SAP AG. Alle echte 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, POWE, POWE5, POWE5+, OpenPower und PowerPC sind Marken oder eingetragene Marken der IBM Corporation. Adobe, das Adobe Logo, Acrobat, PostScript und eader sind Marken oder eingetragene Marken von Adobe Systems Inc. in den USA und/oder anderen Ländern. OACLE ist eine eingetragene Marke der OACLE 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. JAVASCIPT 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, /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 echts. 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.