BusinessObjects Extended Analytics Architecture and recommendations

Transcription

1 BusinessObjects Extended Analytics Architecture and recommendations BusinessObjects Extended Analytics FPM 7.0

2 Copyright Third-party contributors Copyright 2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,555,403; 6,247,008; 6,289,352; 6,490,593; 6,578,027; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 7,139,766; 7,181,435; 7,181,440 and 7,194,465. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Xcelsius, Crystal Decisions, Intelligent Question, Desktop Intelligence, Crystal Enterprise, Crystal Analysis, Web Intelligence, RapidMarts, and BusinessQuery are trademarks or registered trademarks of Business Objects in the United States and/or other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at:

3 Contents Chapter 1 Introduction 1 About this guide Typefaces What s new in this version? Chapter 2 Technical architecture 1 Key Concepts of the Software Architecture Detailed software components in the BusinessObjects Extended Analytics architecture Security implementation in BusinessObjects Extended Analytics Chapter 3 Hardware and software recommendations 1 General recommendations Analyzer client Designer client Deployer for Finance SSAS server BusinessObjects XI R3 platform Microsoft Data Pump Architecture and recommendations 1

4 Contents 2 Architecture and recommendations

5 Introduction chapter

6 1 Introduction About this guide About this guide Intended audience The BusinessObjects Extended Analytics architecture and hardware and software recommendations guide contains the following: The key concepts of the BusinessObjects Extended Analytics software architecture. The hardware and software recommendations for this version. This document is intended for architects in charge of the technical setup for BusinessObjects Extended Analytics. Architects should be experienced in systems and networks and be familiar with the technology used by this application. To find out more about how to use this product, please refer to the BusinessObjects Extended Analytics user guide. The user guide is available in PDF format on the installation CD or in HTML format in the Help menu after installation. Document conventions Typefaces The table below presents the different typefaces used in the guide: Typeface Meaning Example Bold Names of windows, dialog boxes, menus, menu commands and buttons The Installation Directory dialog box will appear. Menu > Command Menu command Select New > Data source. Code Command line C:\>iisreset /restart Code on gray background All or part of a configuration file to be checked or changed <add key="compressionlevel" value="normal" /> 2 Architecture and recommendations

7 Introduction About this guide 1 Typeface Meaning Example Numbered list Procedure or series of 1. Right-click to select New > Virtual steps to be performed Directory. 2. The following dialog box will appear: 3. Click on Next. 4. Open a Command Prompt dialog box. 5. Run the C:\>iisreset /restart command line. < > Value to be set <datasource_name> Compulsory space between settings " " To be inserted if spaces are used in a setting CtStartServer.vbe_<datasource_manager > <"datasource_password"> [ ] Optional setting <"datasource_password">_[<server>] Architecture and recommendations 3

8 1 Introduction What s new in this version? What s new in this version? BusinessObjects Extended Analytics version FPM 7.0 Platform evolution Due to major architectural evolutions, the following components are no longer provided: The Reporter server and client The Configuration Manager BusinessObjects Extended Analytics Web The following version of BusinessObjects Financial Consolidation is supported: BusinessObjects Financial Consolidation 10.5 SP1 Warning: only this version is supported. Now supported To support the integration into the BusinessObjects Enterprise XI R3 platform, BusinessObjects Enterprise XI R3 Fix Pack 01 is now required The former components have been replaced by: BusinessObjects Web Intelligence BusinessObjects InfoView BusinessObjectsVoyager Support of Windows Vista SP1 for client components 4 Architecture and recommendations

9 Technical architecture chapter

10 2 Technical architecture Key Concepts of the Software Architecture Key Concepts of the Software Architecture BusinessObjects Extended Analytics uses a multi-tier client/server architecture. The presentation layer, the functional layer and the data layer have been developed as independent modules for Windows Intel 32 bit in a Microsoft.NET 2.0 environment in C# and C++ languages. Its architecture relies on the Microsoft SSAS 2005 technology, on the BusinessObjects Financial Consolidation environment and on the BusinessObjects Enterprise XI R3 platform. All user interfaces are written in Windows Forms 2.0 and have a "look & feel" similar to Microsoft Office All server components use multi-thread mechanisms. The application can thus simultaneously and automatically use all of the processors available on the servers (scaling-in, i.e. increasing the number of processors on a single server). Architecture Overview with SSAS BusinessObjects Extended Analytics architecture consists of 6 main server components: The SSAS server, which hosts the cubes and the Microsoft SSAS 2005 engine The Data Pump server, which ensures the link between the SSAS server and Analyzer The BusinessObjects Financial Consolidation Web Services, which manages security and provides Finance metadata to Designer The BusinessObjects Financial Consolidation platform, which collects data The Deployer for Finance server, which handles cubes creation and deployments The BusinessObjects Enterprise XI R3 platform, which provides security, authentication and BI tools (Voyager and WebI) There are also 3 main client components: The Analyzer client, which uses Microsoft Excel to create reports and to browse data The Designer client running on a Windows client platform, which defines cubes 2 Architecture and recommendations

11 Technical architecture Key Concepts of the Software Architecture 2 The BusinessObjects platform BI tools: BusinessObjects Web Intelligence (WebI) BusinessObjects Voyager Architecture Overview with star schema BusinessObjects Extended Analytics architecture with BusinessObjects Financial Consolidation consists of 4 main components: The BusinessObjects Financial Consolidation platform, which collects data The Deployer for Finance component, which handles cubes creation and deployments The star schema database, which handles star schemas The BusinessObjects Enterprise XI R3 platform, which provides security and authentication There is also 1 main client component: The Designer client running on a Windows client platform, which defines cubes Architecture and recommendations 3

12 2 Technical architecture Key Concepts of the Software Architecture BusinessObjects Financial Consolidation database and star schemas database (SQL Server or Oracle databases) can be installed on separated servers. 4 Architecture and recommendations

13 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 2 Detailed software components in the BusinessObjects Extended Analytics architecture Server components BusinessObjects Enterprise XI R3 platform Requirements: BusinessObjects Enterprise XI R3 + Fix Pack 01 BusinessObjects Extended Analytics Plugin Microsoft SQL Server 2005 SP2 MSXML6 Parser The SQLServer2005 OLEDB provider Note: The BusinessObjects Enterprise XI R3 platform is mandatory. Function: BusinessObjects Enterprise XI R3 includes specialized services including Web Intelligence, Desktop Intelligence, InfoView and Crystal Reports components, and a set of Dashboard and Analytics services for metrics Architecture and recommendations 5

14 2 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture management, predictive analysis, and process analysis. It provides you with all authentication and security management tools that are needed with this version of BusinessObjects Extended Analytics. BusinessObjects Financial Consolidation platform Requirements: The BusinessObjects Financial Consolidation Web Services component must be deployed on the BusinessObjects Financial Consolidation platform. The Web Services are mandatory because BusinessObjects Extended Analytics uses it in order to interface with BusinessObjects Financial Consolidation. If these Web Services are not installed, Analytics will not function. To find out more about the installation procedure of the web services, see the BusinessObjects Financial Consolidation installation guide, Installing and configuring BusinessObjects Financial Consolidation Web Services. Note: BusinessObjects Financial Consolidation web is not mandatory. Supported BusinessObjects Financial Consolidation versions: BusinessObjects Financial Consolidation 10.5 SP1 BusinessObjects Enterprise XI R3 + Fix Pack 01 Function: BusinessObjects Extended Analytics connects directly to the web API for security purposes and to the database for data extraction. 6 Architecture and recommendations

15 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 2 Deployer for Finance server Required components: Microsoft components: Microsoft.NET Framework 2.0 Internet Information Services Business Objects components: BusinessObjects Extended Analytics Deployer (includes Microsoft SQL Server native client, SQL Server Management object, MSXML Parser 6.0) Function: Deployer with SSAS Solutions for cube deployment are defined and managed in the Designer client, and then processed by the Deployer server. The Deployer server sends the deployment descriptions to the SSAS server; which processes them. Deployer server does not process the cube deployment by itself. Deployer server connects to the BusinessObjects Financial Consolidation database and to SSAS. Deployer with Star Schema (for BusinessObjects Financial Consolidation) Deployer with Star Schema performs the same type of operations; but instead of directly sending deployment orders to SSAS, it directly generates a deployment inside the Star Schema database. The Deployer Server does not execute the deployment itself but sends the requests needed for the deployment. Those requests are sent to the Business Objects database and the Star Schema database. The Deployer server connects to the BusinessObjects Financial Consolidation database, to the Star Schema database. The Designer client connects to the Deployer server. Architecture and recommendations 7

16 2 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture SSAS Server & Datapump component SSAS Server Required components: Microsoft components: Microsoft SSAS 2005 Internet Information Services (only if the datapump is hosted on the SSAS server) Business Objects components: UDF for Security: this component enables BusinessObjects Financial Consolidation security to be used in SSAS Function: This server hosts the SSAS engine, which is the Microsoft OLAP engine. It also stores the cubes created in Designer which are consulted by Analyzer client that connects through the InfoView portal. The UDF for Security component must be installed in order to apply the Business Objects security to data instead of the standard Microsoft integrated security. The SSAS server is accessed by the Deployer server, by the Analyzer client connecting through the Data Pump component. 8 Architecture and recommendations

17 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 2 Client components Designer client Datapump component Warning: This applies only if this component is installed on a machine other than the SSAS server. Required components: Microsoft components: Internet Information Services Microsoft.NET Framework 2.0 MSXML Parser 6.0 Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider Data Pump for SSAS 2005 Function: This server hosts the Microsoft Data Pump for SSAS 2005 component. It must be deployed in order to allow the Analyzer client to connect directly to cubes using the XMLA over HTTP protocol instead of XMLA over TCP/IP (HTTP being more manageable than TCP/IP). Required components: Warning: The BusinessObjects Financial Consolidation Windows client must be installed before installing Designer. DBMS clients for the BusinessObjects Financial Consolidation database access (Microsoft SQL Server or Oracle) Microsoft components: Microsoft.NET Framework 2.0 Business Objects components: BusinessObjects Extended Analytics Designer (includes Microsoft SQL Server 2005 native client, SQL Server 2005 Management object, MSXML Parser 6.0) Architecture and recommendations 9

18 2 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture Function: Designer is a modeling tool that: allows the Designer to define how the BusinessObjects Financial Consolidation IDM (Integrated Data Model) will be represented in the OLAP server. stores these definitions consistently as BusinessObjects Financial Consolidation Model Definitions. creates the appropriate OLAP model in the SSAS server through the Deployer server from the Model Definition specified by the user. The Designer client connects to the BusinessObjects Financial Consolidation platform, the BusinessObjects Financial Consolidation database and the Deployer server. BusinessObjects Enterprise XI R3 clients Analyzer client Required components: Internet Explorer. Function: The BusinessObjects Enterprise XI R3 provides several BI applications, like: Web Intelligence and Voyager that can be used to consult Extended Anaytics cubes. InfoView is a web portal used to store extended analytics work books. The CMC is used to configure your Extended Analytics application. 10 Architecture and recommendations

19 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 2 Required components: Microsoft components: Windows Installer 3.1 Microsoft.NET Framework 2.0 MDAC 2.6 Internet Explorer Microsoft Excel Business Objects components: BusinessObjects Extended Analytics Analyzer (includes Analysis Services 9.0 OLE DB Provider and Visual Studio Tools for Office) Function: The Analyzer client: creates the reports that will be published on the InfoView portal. allows OLAP analysis of cubes (drill-down, pivot axis, etc.). The Analyzer client will connect to the InfoView portal and also to the SSAS server through the Data Pump server. Recommended Architecture Implementation The diagrams below provide an example of how the technical architecture in BusinessObjects Extended Analytics can be implemented. The different software components are physically separated on different computers: Architecture and recommendations 11

20 2 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture Recommended Architecture Implementation with Star Schema The diagram below provides an example of how the technical architecture in BusinessObjects Extended Analytics with Star Schema can be implemented. The different software components are physically separated on different computers. As the Deployer server does not require many resources, it can be installed on an existing server, for instance one of the BusinessObjects Financial Consolidation servers. 12 Architecture and recommendations

21 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 2 Protocols Used in the BusinessObjects Extended Analytics Software Architecture OleDB ADO.NET OleDB is the standard programming interface for data access between an application and a database server and is an ODBC object-oriented version. OleDB can be used to access all types of database and can therefore support several RDBMS s with the same product. OleDB is one of the software components in the MDAC (Microsoft Data Access Components) stack. ADO.NET is an extended version of OLE DB for.net applications. Architecture and recommendations 13

22 2 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture DCOM SOAP XMLA DCOM is a network-distributed object protocol. It defines the remote procedure call that enables (DLL) objects to be run remotely over the network, regardless of their location. These objects can be located on the same computer as the client program or on another computer in the network. DCOM enables you to develop an object-oriented application to provide access to objects regardless of their exact location. DCOM: is one of the components in Windows. uses the IP, IPX and Net BEUI network protocols. Simple Object Access Protocol is an XML-based protocol providing intraprocess communication and access to objects across machines. XML for Analysis Services is the Microsoft standard protocol for accessing SSAS. 14 Architecture and recommendations

23 Technical architecture Security implementation in BusinessObjects Extended Analytics 2 Security implementation in BusinessObjects Extended Analytics Security implementation overview BusinessObjects Extended Analytics does not implement its own specific user management or authentication mechanism. Security is handled by BusinessObjects Financial Consolidation and BusinessObjects Enterprise XI R3 via Web services deployed on the BusinessObjects Financial Consolidation platform. All authentication mechanisms supported by BusinessObjects Enterprise XI R3 are therefore automatically supported by BusinessObjects Extended Analytics. Designer This component is only used with BusinessObjects Financial Consolidation. BusinessObjects Financial Consolidation manages connections to the Designer module. BusinessObjects Extended Analytics Designer uses the BusinessObjects Financial Consolidation DCOM API; when a user tries to connect, BusinessObjects Financial Consolidation authenticates the user. The BusinessObjects Financial Consolidation user must be granted the "Administrator" BusinessObjects Extended Analytics functional right in order to create and deploy cubes. When a new deployment is performed with SSAS or Star Schema, Designer connects to the Deployer server. Warning: Currently it is not possible to connect to Designer with an integrated Windows authentication. This will be possible in future versions. Deployer server The Deployer server is an ASP.NET application that runs with a Windows account. This account must belong to the SSAS administrators in order to be able to create new databases and to install UDF for Security for the first deployment. When a deployment is performed with SSAS, Deployer connects to the SSAS instance. When a deployment is performed with Star Schema, Deployer connects to the BusinessObjects Financial Consolidation database and to the Star Schema database. Architecture and recommendations 15

24 2 Technical architecture Security implementation in BusinessObjects Extended Analytics Analyzer client The Analyzer module is started via InfoView. Authentication is carried out first in InfoView and user credentials are then sent to the Analyzer Excel add-in. Excel will then use these credentials to connect to the SSAS server and to deploy new reports in InfoView. For each dimension value requested by the Analyzer client, a request will be sent to BusinessObjects Financial Consolidation to check user rights. Analyzer can function in a standalone configuration. In this case, Excel is started without the InfoView credentials. If no datapump is used, Analyzer will connect directly to the SSAS instance. The Windows account used to start Excel must have access to the SSAS database, without administration rights. If a datapump is used, the Windows account is not relevant (the datapump Windows account will be used). Internal implementation SSAS Server SSAS uses role-based security. The BusinessObjects Extended Analytics Deployer module will create a new role named "DefaultRole" in SSAS when a new database is created. This role contains one member: "Everyone". Note: The content of this role can be customized using a configuration file. When a database is created with Deployer, a UDF (User-defined function) for Security assembly is deployed on the SSAS server associated with this role and database. Each BusinessObjects Financial Consolidation data source corresponds to one SSAS database. One cube corresponds to one deployment. This role has the following rights: Read only for all cubes of the database. Read only for the definition of all dimensions. When users connect to SSAS, they will first be authenticated by SSAS (where the role is Everyone); they will then be authenticated in BusinessObjects Financial Consolidation via the UDF for Security component. There are 2 authentication modes in BusinessObjects Financial Consolidation: 16 Architecture and recommendations

25 Technical architecture Security implementation in BusinessObjects Extended Analytics 2 BusinessObjects Financial Consolidation native mode: the connection string sent to SSAS contains the BusinessObjects Financial Consolidation credentials in the CustomData field. Analyzer uses this CustomData field when BusinessObjects Financial Consolidation uses the login / password authentication mode. Windows native mode: the connection string does not have a CustomData field. In this case, the UDF for Security component retrieves the Windows ID from a client and checks the BusinessObjects Financial Consolidation application for a BusinessObjects Financial Consolidation user name that matches the Windows ID user name. Warning: The only supported authentication mode in BusinessObjects Planning is the Windows native mode. Once it is authenticated by the BusinessObjects Enterprise XI R3 platform (the CMS), the UDF for Security component will then check BusinessObjects Financial Consolidation for user rights for all of the dimensions (ie. the Data Access Group of each BusinessObjects Financial Consolidation user defined for Data Analysis Access and the Default Category). As a result, Business Objects data security is applied to the data stored in the cube. Warning: UDF for Security is not applied to any Windows or SSAS login with Administrator rights. This is why the Windows user set to run the datapump and to establish the link between SSAS and other products cannot have Administrator rights. This is also why all Business Objects components must connect to SSAS through the datapump. If users are not recognized by BusinessObjects Financial Consolidation, they will not be able to see any data. It is possible however to create other roles manually; but in this case, Business Objects security for the dimensions will not be applied. These users will only be able to see the dimensions. Note: You can customize security for a database, but each time a cube is deployed or redeployed, all dimensions are deleted and recreated. This custom security must be reset after each cube deployment. The SSAS server will host the X509 certificate public key. The BusinessObjects Extended Analytics setup will install a default X509 certficate but it is highly recommended to replace it by a true certificate when working on a full production environment. This public certificate must match the private certificate deployed on the BusinessObjects Enterprise XI R3 platform. Architecture and recommendations 17

26 2 Technical architecture Security implementation in BusinessObjects Extended Analytics Datapump server The datapump handles connections between Anayzer clients and SSAS. The Windows account used to run the datapump component MUST be a user known and authenticated by the SSAS Server (in the same domain or a domain known). This user must NOT have the local administration rights on the SSAS Server, SSAS instance or SSAS database. Otherwise, the UDF For Security component will not function. 18 Architecture and recommendations

27 Hardware and software recommendations chapter

28 3 Hardware and software recommendations General recommendations General recommendations The software and hardware platform presented in this chapter is the reference platform supported by BusinessObjects Extended Analytics. This platform applies to the product version indicated on the cover page of this document. Unless otherwise mentioned, all operating systems and software components specified are supported in the following languages only: English French German Japanese Warning: We recommend that BusinessObjects Extended Analytics be installed on dedicated servers. Tip: You can use BusinessObjects Extended Analytics on other platforms. To find out more about other platforms, please contact Business Objects Software Support. 2 Architecture and recommendations

29 Hardware and software recommendations Analyzer client 3 Analyzer client Category Supported configuration Recommended configuration Processor Intel Pentium processor 600 MHz or Intel Pentium processor 1 GHz a Pentium compatible processor RAM At least 256 MB (depending on the 512 MB operating system) Disk space 1 GB available disk space for installing BusinessObjects Finance Screen resolution 1024 X 768 Operating system All the following OS Service Packs available as of July : Windows XP SP1, SP2 or SP3 Windows Vista SP1 Windows 2003 SP1, R2 or SP2 Terminal Services Windows XP SP2 Software components Only 32 bits editions are supported Internet Explorer 6 SP1 or SP2 Internet Explorer 7 Internet Explorer 7 Microsoft.NET Framework 2.0 Microsoft Office Excel XP, 2003, 2007 Microsoft Office Excel 2003 Network connection Windows Installer 3.1 MDAC Kbps connection or higher dedicated to daily operations By default, the HTTP flow is compressed An ADSL connection or equivalent can improve performance Warning: In the case of complex configurations, the client computer's performance (available RAM and processor performance) can have a significant impact on the application's performance. Architecture and recommendations 3

30 3 Hardware and software recommendations Designer client Designer client Category Supported configuration Recommended configuration Processor Intel Pentium processor 500 MHz or a Intel Pentium III 1 GHz or higher Pentium compatible processor RAM 256 MB or more (depending on the 512 MB operating system) Disk space 100 MB available disk space Operating system All the following OS Service Packs available as of July : Windows XP SP1, SP2 or SP3 Windows Vista SP1 Windows 2003 SP1, R2 or SP2 Terminal Services Windows XP SP2 Software components Network connection Only 32 bits editions are supported Internet Explorer 6 SP1 or SP2 Internet Explorer 7 Microsoft.NET Framework 2.0 DBMS clients: For the BusinessObjects Finance database access: - Oracle 10g Release 1 or release 2 client - Microsoft SQL Server 2005 SP2 client For the SSAS database access: - Microsoft SSAS 2005 SP2 client (installed by default with Cartesis Analytics Designer) Ethernet 10 Mbps or higher Internet Explorer 7 with the HTTP/ 1.1 protocol Ethernet 100 Mbps 4 Architecture and recommendations

31 Hardware and software recommendations Deployer for Finance 3 Deployer for Finance Category Supported configuration Recommended configuration Processor Intel Pentium processor 600 MHz or a Pentium compatible processor Intel Pentium Xeon 2 GHz (or higher) RAM 256 MB Disk space 10 GB Operating system All the following OS Service Packs available as of July : - Windows Server 2003 SP1 - Windows Server 2003 R2 - Windows Server 2003 SP2 Windows Server 2003 SP2 Software components 32 or 64 bits editions Microsoft.NET Framework 2.0 Internet Information Services (IIS) 6 MSXML Parser 6.0 Microsoft SQL Server 2005 SP2 Analysis Services 9.0 OLEDB Provider DBMS clients: For the Business Objects databases access: - Oracle 10g Release 1 or release 2 client - Microsoft SQL Server 2005 SP2 client Network connection For the SSAS database access: - Microsoft SSAS 2005 SP2 client Ethernet 10 Mbps or higher Ethernet 100 Mbps Architecture and recommendations 5

32 3 Hardware and software recommendations SSAS server SSAS server Category Supported configuration Recommended configuration Processor Intel Pentium processor 2 GHz or a Pentium compatible processor for every 50 users Intel Pentium Xeon 2.8 GHz (or higher) dual-processor server Multi-processors are supported RAM 1 GB 4 GB Disk space 50 GB Secured disks recommended Depends on the volume of data (RAID or other technologies) Operating system All the following OS Service Packs Windows Server 2003 SP2 available as of July : - Windows Server 2003 SP1 - Windows Server 2003 R2 - Windows Server 2003 SP2 32 or 64 bits editions Software components DBMS clients: For the BusinessObjects Finance database access: - Oracle 9i Release 2 client - Oracle 10g Release 1 or release 2 client Microsoft.NET Framework Microsoft SSAS 2005 SP2 Enterprise Edition, 32 or 64 bits Internet Information Services (IIS) 6 Only the Microsoft SSAS 2005 SP2 Enterprise Edition or higher is supported Network connection Ethernet 100 Mbps or higher Ethernet 1 Gbps Warning: Since BusinessObjects Extended Analytics uses functionality only available in the Enterprise Edition, only Microsoft SQL 2005 SP2 Enterprise Edition is supported on the SSAS Server. 6 Architecture and recommendations

33 Hardware and software recommendations BusinessObjects XI R3 platform 3 BusinessObjects XI R3 platform Category Supported configuration Recommended configuration Processor 2.0 GHz Pentium 4 class processor RAM 2 GB Disk space 4.9 GB hard disk space for BusinessObjects Enterprise Operating system All the following OS Service Packs available as of July : - Windows Server 2003 SP1 - Windows Server 2003 R2 - Windows Server 2003 SP2 32 or 64 bits editions Software components Internet Information Services (IIS) 6 Network connection Ethernet 100 Mbps or higher Ethernet 1 Gbps Warning: Only the Windows version of the BusinessObjects Enterprise XI R3 platform is supported with BusinessObjects Extended Analytics. Architecture and recommendations 7

34 3 Hardware and software recommendations Microsoft Data Pump Microsoft Data Pump Category Supported configuration Recommended configuration Processor Intel Pentium processor 600 MHz or a Intel Pentium Xeon 2.8 GHz (or Pentium compatible processor higher) dual-processor server RAM Disk space Operating system Multi-processors are supported 256 MB 10 GB All the following OS Service Packs available as of July : - Windows Server 2003 SP1 - Windows Server 2003 R2 - Windows Server 2003 SP2 Windows Server 2003 SP2 Software components 32 or 64 bits editions Microsoft.NET Framework 2.0 Internet Information Services (IIS) 6 MSXML Parser 6.0 Network connection Microsoft SQL Server 2005 SP2 Analysis Services 9.0 OLEDB Provider Ethernet 100 Mbps Ethernet 1 Gbps Note: The Business Objects recommendation is to install this component on the SSAS Server. Nethertheless, if you have a DMZ, you can install it on a separated machine. 8 Architecture and recommendations