User manual BUSINESS OBJECTS EXTENDED ANALYSTICS 4.1 ARCHITECTURE AND RECOMMENDATIONS

[. . . ] BusinessObjects Extended Analytics Architecture and recommendations BusinessObjects Extended Analytics 4. 1 Copyright Copyright © 2007 Business Objects. 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. [. . . ] The different software components are physically separated on different computers: Architecture and recommendations 21 3 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture Warning: Reporter Server and SSRS MUST be installed on the same server. This server must have Windows Server 2003 and IIS. 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 Finance servers. 22 Architecture and recommendations Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture 3 Protocols Used in the BusinessObjects Extended Analytics Software Architecture OleDB 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 ADO. NET is an extended version of OLE DB for . NET applications. Architecture and recommendations 23 3 Technical architecture Detailed software components in the BusinessObjects Extended Analytics architecture DCOM 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: · · SOAP 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. XMLA XML for Analysis Services is the Microsoft standard protocol for accessing SSAS. 24 Architecture and recommendations Technical architecture Security implementation in BusinessObjects Extended Analytics 3 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 Finance via Web services deployed on the BusinessObjects Finance platform. All authentication mechanisms supported by BusinessObjects Finance are therefore automatically supported by BusinessObjects Extended Analytics. Designer This component is only used with BusinessObjects Finance. BusinessObjects Extended Analytics Designer uses the BusinessObjects Finance DCOM API; when a user tries to connect, BusinessObjects Finance authenticates the user. The BusinessObjects Finance 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 Finance database and to the Star Schema database. Architecture and recommendations 25 3 Technical architecture Security implementation in BusinessObjects Extended Analytics Reporter client Two authentication models can be used to connect to Reporter: · · BusinessObjects Finance login and password (corresponds to the BusinessObjects Finance integrated security or LDAP authentication). All Windows users must be declared in BusinessObjects Finance or BusinessObjects Planning applications. [. . . ] There are 2 authentication modes in BusinessObjects Finance (and only one for BusinessObjects Planning): · BusinessObjects Finance native mode: the connection string sent to SSAS contains the BusinessObjects Finance credentials in the CustomData field. Analyzer uses this CustomData field when BusinessObjects Finance 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 Finance application for a BusinessObjects Finance user name that matches the Windows ID user name. [. . . ]