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
BPC High Level Architecture
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.
Server Technology Stack
•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
SQL
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
Reporting
Services
•Storage location for
all application files,
UNC or local drive.
•Book Repository
•Templates
•Unstructured Data
•Conversion &
Transformation Files
File
Services
•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
Web
Server
•Microsoft IIS
•Supports all SOA
(Service Oriented
Architecture)
•Collection of BPC
Services
•Where BPC
Application
Business Logic
Resides
•Performs user
authentication
Application
Services
•Microsoft SQL
Server –
Enterprise Edition
2005
multi-dimensional
database
component
•Provides detailed
analysis & drill
down
•Can be 64 bit
when separate
from
Application/web
services
Analysis
Services
Factors Affecting Installation
SQL Licensing Requirements …
SQL
SQL
SQL
SQL
SQL
Services
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
Where IIS is Located …
IIS
IIS
BPC Application Tiers
Web Tier
User Interface for BPC Web, Insight
Application Tier
XML services, Business Logic, Shared Query Language
Database Tier
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
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
Single Server Configuration
SQL
Services
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
SQL
Services
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
Sample Single Server Guidelines
OS–RAID 1
Data–RAID 1+0
OS–RAID 1
Data–RAID 1+0
RAID 5
RAID 5
RAID Level
Recommended
Recommended
Contact an BPC Certified Technical Consultant
for more information
Windows 2003 Enterprise Edition SP2/R2 (32 bit
only)
SQL Server 2005 Standard/Enterprise Edition or
Developer’s Edition, Runtime Licensing Supported
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
OS
Minimum
Minimum
144 GB
72 GB
72 GB
36 GB
Disk GB
8 GB
4 GB
4 GB
2 GB
RAM GB
4 Dual Core
4
4
2
CPU’s
Multi Server Configuration
SQL
Services
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
Web Tier
Web Services & Reporting Services
Application Services & File Share
SQL Services & Analysis Services
Application Tier
Sample Tier Centric Server Guidelines
Windows 2003 Enterprise Edition SP2/R2
Windows 2003 Standard and Enterprise Edition
SP2/R2
OS
OS – 1 Data
-1+0
1
1
5
1
1
RAID Level
144
72
36
72
36
36
Disk GB
8
4
2
2
2
2
RAM GB
4 Dual Core
2 Dual Core
2 Dual Core
2 Dual Core
2
2
CPU’s
DB Tier
Can be 64 bit
App Tier
Web Tier
DB Tier
Can be 64 bit
App Tier
Web Tier
Recommended
Minimum
Multi Server Configuration – Web Centric
Web Centric
-separates SQL
relational
database from
web services
Reporting Services, File Share,
Application Server and Webserver
Database Server and Analysis
Services and Reporting Services
Database
SQL
Services
Reporting
Services
File
Share
Web
Server
Application
Server
Analysis
Services
EE
Multi Server Configuration – Database Centric
Database Centric
- separates all
database services
from web/file/app
services
File Share, Reporting Services,
Application Server and Webserver
DB Server, RS Database and
Analysis Services Server
SQL
Services
Reporting
Services
File
Share
Web
Server
Application
Server
Analysis
Services
EE
Multi Server Configuration – Database Centric
Database Centric
- separates all
database services
from web/file/app
services
File Share, Application Server and
Webserver
DB Server, RS Database and Web
Part and Analysis Services Server
SQL
Services
Reporting
Services
File
Share
Web
Server
Application
Server
Analysis
Services
EE
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
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
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
Is Transparent Authentication or SSO a requirement?
Do you support Active Directory?
Will users log into BPC with their Domain ID?
Do users log into their local machines with a Domain ID?
Are all your users in one domain or many
Do you have external users not part of your domain?
BPC
Users
Authentication Matrix
Windows ids for each user Existing LDAP server we can read
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
Windows ids for each user Prerequisites
Yes Yes
Yes Yes
Requires 1-3 windows service-like accounts (Windows UserIDs for COM+ Components - sysadmin/admin/user)
Yes Yes
Yes Yes
Works in multi-server environment
Yes Yes
No Must use Basic
Works over internet (non-VPN)
Yes No
Yes Yes
Requires Windows ID
Yes unless use https for all pages Yes unless use https for login page
No No
Password sent in clear text
Yes Yes
Only if switch to another authentication mode Yes, if use BASIC
Alternate userid Low Med Higher High Relative security Basic LDAP Kerberos Windows Integrated Security features: Authentication Mode:
Client Hardware Requirements
NIC 100 MBit
SVGA 800 x 600
Other
1 GB
500 MB
150 MB
Hard Drive
512 MB >
512 MB >
256 MB >
RAM
x86 (1.6 GHz >)
x86 (1.4 GHz >)
x86 (600 MHz >)
CPU
Admin User
Power User
Standard User
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
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
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
Reporting
Services
File
Services
Web
Server
Application
Services
Analysis
Services
EE
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
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
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
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
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
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
Web
Server
Web
Server
HA MultiServer Environment
Example
Load balancing device
Application
Server, Reporting
Service and
Web Tiers
SAN
Database Tiers
Architecture Roadmap of Next-Generation
CPM Solutions
Requirements for Next-Generation CPM
Solutions
SAP BPC 5 Technical Architecture
.NET
DB Access
Thin Client
Persistency
Application Services Utilities
Platform Services RDBMS (SQL Server) MOLAP (Analysis Server) MD Store Star Schema DTS/SSIS File Server ADODB ADOMD R R OLAP Admin Scheduling File Service Rel. Store (meta data, etc.) SQL MDX ZIP, XML, Chart, etc. MS Reporting Services R Local File Store Logging Data Mgmt. Audit Configuration Admin Shared Query Engine Comments WorkStatus Metadata Email User Mgmt. Insight Journal LiveUpdate BPF Content LiveReport Session Publish Write Back Web Services DB Connection Factory Admin Configuration Send Govenor BPF WorkStatus ... Rich Clients Admin ActionPane Browser HTTP/SOAP WebUI (ASP.NET) R Logic Script Logic HTTP Source Systems R BPC for Excel ActionPane BPC for Word ActionPane BPC for PP ActionPane R R R R R R R Logic Stored Procedures R R R R R
ABAP
BPC ABAP Function Modules BPC Data Access Objects SAP BPC (.NET) Application Services Source Systems Database BPC Customizing InfoProvider BI Metadata MasterdataBI
BPC App Services
BPC Audit ... Thin Client
Web Services
Admin BPF WorkStatus Configuration ...
Browser HTTP/SOAP WebUI icl. Reporting (ASP.NET) R HTTP
Application Services Proxies Utilities
Platform Services Scheduling Proxy File Service ZIP, XML, Chart, etc. Local File Store Logging Data Mgmt. Audit Configuration Admin Shared Query Engine Comments WorkStatus Metadata Email User Mgmt. Insight Journal LiveUpdate BPF Content LiveReport Session Publish Write Back Logic Proxies Script Logic Parameter-driven Logic Unstructured Docs Audit Configuration Admin Shared Query Engine Comments WorkStatus Metadata Email User Mgmt. Insight Journal LiveUpdate BPF Content LiveReport Session Publish Write Back SAP BI (ABAP) MDX IF BI ETL
BI BAPIs RSDRI IF ProcessChains Logic
Script Logic ModulesLogic
ABAP Basis ABAP Batch Scheduler R DAO Proxies R File Service Proxy HTTP/RFC HTTP/RFC Data Mgmt.
Data Mgmt. ComponentsProcess
SAP Connect (Email) Rich Clients Admin ActionPane BPC for Excel ActionPane BPC for Word ActionPane BPC for PP ActionPane R R R R R R R R R R R R R R
SAP Strategy Management 2007 Technical
Architecture
Browser interface thin client
Excel interface via Wininet.dll
Diagram strategy manager via .net
MS IIS
PIP (.Net) Java (JBoss)
EJB Web
PAS (.NET and Linux/UNIX) Jakarta ISAPI Filter PilotWorks Web R Pilot Administrator .NET
HTTP
TCP/IP
TCP/IP
PAS Listener Pilot DB SQLite R Work DB OLAP DB MS Usermgmt. R PIP Listener Stored procedures JPIP AUTH PilotWorks Core PilotWorks Console PilotWorks Ext Excel PilotWorks Srv PilotWorks Static Content LDAP Server Users R MS Store (pipadmin) R R TCP/IP Data Warehouse MDDB R ODBC /ODBO R TCP/IP R R R Browser R PilotWorks Config R R Diagram Manager RMS IIS
•static pages
•authentication
•redirection of dynamic contents
JBoss
•application business logic
•common services
•authorization
•interface with data tier
Pilot Interactive Publisher
•relational connection pooling
•PAS connection pooling
•result caching
Pilot Application Server
•KPI data store
•OLAP engine
SAP Strategy Management 7.0 Technical
Architecture
NW AS Java
NW AS Database
PIP (.NET and Linux/UNIX)
PAS (.NET and Linux/UNIX)
PilotWorks Web R Pilot Administrator .NET HTTP TCP/IP PAS Listener Pilot DB Work DB OLAP DB PIP Listener Stored procedures JPIP UME PilotWorks Core Excel with plug-in PilotWorks Srv PilotWorks Static Content LDAP Server Users R TCP/IP SAP BI Database R MDX over RFC/ OLAP BAPI R TCP/IP R R R R Browser R PilotWorks Config Users R PIP Config WS PIP Config
Web Server
HTTP R PilotWorks Static Content R Diagram Manager R IGS HT TP / XM LNetweaver CE
•application business logic
•common services
•authorization
•interface with data tier
•authentication
•static content
•configuration
•database connection pooling
•clustering
Pilot Application Server
•KPI data store
•OLAP engine
•Data warehouse interface
•Netweaver BI integration
Pilot Interactive Publisher
•PAS connection pooling
•result caching
Changes and Flexibility for the Future
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 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 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.
