SpagoBI Architectural Design

SpagoBI Architectural Design
Author Grazia Cazzin

SpagoBI Architectural Design ver 0.5 August, 5th 2005 – pag. 1 of 25
Engineering Ingegneria Informatica S.p.A., 2005. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/2.0/

SpagoBI Architectural Design

Index

VERSION ...........................................................................................................................................4 DOCUMENT GOAL .........................................................................................................................4 REFERENCES...................................................................................................................................4 1 2 FUNCTIONAL LEVEL ARCHITECTURE............................................................................5 APPLICATION LEVEL ARCHITECTURE...........................................................................7 2.1 DELIVERY LAYER ....................................................................................................................7 2.1.1 BIPortlet...........................................................................................................................8 2.1.2 BIService ..........................................................................................................................9 2.1.3 BIXCube ...........................................................................................................................9 2.1.4 BIMessage........................................................................................................................9 2.2 ANALYTICAL LAYER ................................................................................................................9 2.2.1 Service Components.........................................................................................................9 2.2.1.1 BIParameter ...........................................................................................................10 2.2.1.2 BIProfiling .............................................................................................................10 2.2.1.3 BIFunctionality ......................................................................................................11 2.2.1.4 BISearch.................................................................................................................11 2.2.1.5 BIQbE ....................................................................................................................11 2.2.1.6 BINotify .................................................................................................................11 2.2.2 Core Components...........................................................................................................12 2.2.2.1 BIObjController .....................................................................................................14 2.2.2.2 BIObjLogic ............................................................................................................14 2.2.2.3 BIObjDAO .............................................................................................................15 2.2.2.4 BIDriver .................................................................................................................15 2.2.3 BIContextController.......................................................................................................15 2.2.4 BIObjFactory .................................................................................................................17 2.3 DATA AND METADATA LAYER ..............................................................................................18 2.3.1 Service Repository..........................................................................................................19 2.3.2 Metadata repository.......................................................................................................19 2.3.2.1 CWMI, MDI Hub and MDI Bridge .......................................................................20 2.3.3 Data Warehouse.............................................................................................................20 2.3.3.1 Events Define and Alerts Configuration................................................................20 2.3.3.2 Events Store and Alerts Registry ...........................................................................20 2.3.3.3 Rule engine ............................................................................................................20 2.3.4 Specific Semantic Layer .................................................................................................21 2.3.5 Generic Semantic Layer.................................................................................................21 2.3.6 ETL – Staging Area........................................................................................................21 2.4 ADMINISTRATION ..................................................................................................................22 SpagoBI Architectural Design ver 0.5 August, 5th 2005 – pag. 2 of 25
Engineering Ingegneria Informatica S.p.A., 2005. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/2.0/

..............2.........................................................................................2 Content repository: Jackrabbit .............24 3................................25 3...........................24 3....................................................................................5 OLAP client/engine: Jpivot/Mondrian.........24 3........................................................4....A...........2........................................................................2.............4 Report Engine: JasperReport...2.......................22 Logging / Auditing ....................................23 3.p..9 ETL support: OCTOPUS .........2...............23 3..........22 Workflow ................................1 INTEGRATION STRATEGY .......................23 3.........1 Application Framework: Spago .................4..........0/ ..................2..............24 3....................................... 5th 2005 – pag..25 3..................5 August..........23 3.............................org/licenses/by-nc-sa/2...........................................................................................3 2... 2005..............................................................2 FIRST TOOLS SELECTION ......................................................2...............6 Data Mining engine: Weka .....................................................................7 QbE support: Hibernate............................................................................2..........2........................................25 SpagoBI Architectural Design ver 0...................10 Administration – scheduler: Quartz.....................................................................................................................................8 ETL support: BIE ............22 EXECUTIVE LEVEL ARCHITECTURE ...........SpagoBI Architectural Design 2............23 3...24 3.........2 2...................... To view a copy of this license..2.......1 2......4.............. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License....................... visit http://creativecommons................................................22 Metadata Management Interface ............4 3 Scheduler..............................4.........................................................3 Search Engine: Lucene ...........25 3........ 3 of 25 Engineering Ingegneria Informatica S..........................................................................................................11 Portal environment – eXo Platform ..................2....

SMITH. visit http://creativecommons. New York 20002. [4] KIMBALL. Data Mining Techniques: For Marketing. ROSS. Cleaning... [10] SILVERSTON. M. A. R.. The Data Warehouse Lifecycle Toolkit: Expert Methods for Designing.. KING. Manning Pubblications. [3] HALPIN. [6] KIMBALL. The sections “in progress” are pointed out. J. L.. Morgan Kauffman Publisher. [11] WITTEN. and Customer 2 Relationship Management. 2000. Ross. and Delivering Data. A. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. Conforming..0/ ..it).A.SpagoBI Architectural Design Version Version/Release n° : Update description: 0. I.. [9] RICHARDSON. New York 2004.... This document is a work-in-progress: it's likely to have further and deep reviews. M. New York 2001. Information about the Spago framework are available in the Spago Project site (http://spago-info. J. K. BERRY. D. Wiley Publishing. R. Wiley Publishing. W. 4 of 25 Engineering Ingegneria Informatica S. Wrox. THORNTHWAITE. San Francisco 2001. E. and Deploying Data Warehouses. Greenwich 2004.T.. the description of all its components and their responsibilities. Wiley. LINOFF... D.. Information Modeling and Relational Databases. Hibernate in Action. J. New York 2000. 5th 2005 – pag. W. VITALE. Wiley Publishing. R.. Wiley Publishing. CASERTA. Indianapolis 2004. Wiley Publishing.. Merz. Developing. References Some of the concepts of this document refer to the following documentation: BAUER. New York 2000. It draws the SpagoBI development guidelines. L.C. The Data WarehouseETL Toolkit: Practical Techniques for Extracting. The data warehouse toolkit. R. R.. The Data Model Resource Book. 5 th 2005 Draft – This is the first version released in the project’s site. T. G. REEVES..org/licenses/by-nc-sa/2. M.. The Data Webhouse Toolkit: Building the Web-Enabled Data Warehouse. AVONDOLIO. Document goal This document provides the architectural design of SpagoBI platform. [7] KIMBALL. Wiley Publishing. [1] [2] SpagoBI Architectural Design ver 0. C. To view a copy of this license.p. LEN.. [5] KIMBALL. Data Mining: Practical Machine Learning Tools and Techniques with Java Implementations. Sales.H.5 Data Version/Release : August. Building and Managing the Meta Data Repository: A Full Lifecycle Guide. FRANK. New York 2004 . USA 1998. Morgan Kauffman Publisher.5 August.. Form conceptual analysis to logical design. [8] MARCO. 2005.. G.eng... P. Professional Development With Open Source Tools.

2005. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. SpagoBI Architectural Design ver 0. organization and navigation across the different documents. they can be specific BI portals or generic enterprise portal services. Every kind of document maintains its features.5 August. To view a copy of this license. 5th 2005 – pag. but everyone integrates itself in a common infrastructure which provides the right application level and execution environment. It allows SpagoBI to manage usable Business Intelligence services. Enterprise Application Integration Administration BI Applications Analytics BI Engines Data sources and tools integration Dev Tools Picture 1 – Functional SpagoBI architecture The Enterprise Application Integration is related to the integration with generic portals. the activation and interaction modality. the versioning and storage. visit http://creativecommons.0/ .A. The functional SpagoBI architecture follows.. The Data sources and tools integration are related to the integration with source systems and to the all platform’s aspects and used tools. analysis models. in order to achieve data and metadata integration. The BI Application supports the analytical core of the platform.SpagoBI Architectural Design 1 Functional level architecture A Business Intelligence platform provides all the necessary tools in order to manage and deliver documents. It manages in a similar way the production of the results validation cycles. the navigation. The BI Engines are the interfaces for the engines which realizes the analytical documents. control and forecast systems.org/licenses/by-nc-sa/2. the visibility and authorizations policies and rules. although every BI object maintains its distinctive feautures. the parametric activation. It supports a common strategy for the parameters management. 5 of 25 Engineering Ingegneria Informatica S.p.

2005. To view a copy of this license. 5th 2005 – pag.p. SpagoBI hasn’t a prefixed set of development tools.). 6 of 25 Engineering Ingegneria Informatica S. HR. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.A. a layered functional architecture view is the following: o Delivery layer realizing Enterprise Application Integration (output integration). o Analytical layer realizing BI Applications and BI Enginees interfaces (the platform core). the user can choose his favourite ones. as well as development tools. visit http://creativecommons. apart from Development Tools and Analytics.SpagoBI Architectural Design The Administration provides support for the management functionalities of the whole platform. The Development tools are the specific products used for designing Business Intelligence documents. They will be the result of single projects which can evolve to general models. users profiling interface and so on..0/ . o Data and metadata layer solving all Data Source and tools integration responsibilities (the input and integration core). workflow design.org/licenses/by-nc-sa/2. Budget. So. logging and auditing services. etc.5 August. The Analytics. like scheduling. are out of the project scope. Sales. Delivery layer Enterprise Application Integration Administration Analytical layer BI Applications Analytics BI Engines Data & Metadata layer Dev Tools Data sources and tools integration Picture 2 – SpagoBI’s layers SpagoBI Architectural Design ver 0. as a thematic model (like CRM.

1 D E L I V E R Y L A Y E R The Delivery Layer main goals are both to make the Business Intelligence services usable in different ways and to give to the external application the capability to interact with SpagoBI. 5th 2005 – pag. 2005.0/ .org/licenses/by-nc-sa/2.5 August. Delivery layer BIPortlet BIService BIXCube BIMessage BIContextController ADMINISTRATIVE TOOLS / SCHEDULING Analytical layer BIParameter BIProfiling BIFunctionality BINotify BISearch BIReport BIOlap BIData Mining BIDashboard BIQbE Service Components Specific semantic layer BI Core Components (BIObj) Generic semantic layer Native access Data & Metadata layer Service Repository ETL Source Systems METADATA Staging Area DWH Picture 3 – SpagoBI application level architecture 2. 7 of 25 Engineering Ingegneria Informatica S. exposing Business Intelligence services managed by SpagoBI o Web Services (over SOAP/HTTP protocol) for Business Intelligences services invocation from enterprise portal and applications SpagoBI Architectural Design ver 0. It supports different channel/protocols: o Portlet (HTTP to portlet container).SpagoBI Architectural Design 2 Application level architecture Every layer of functional architecture is composed by means of different application modules. To view a copy of this license. visit http://creativecommons. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. as shown in the detailed picture and explained in this chapter..p.A.

A. You can either navigate through the documents or shift from a document to another inheriting its settings. In progress. visit http://creativecommons. In progress. AdapterSOAP. according to the JSR 168 specification.p.1. either a Report. for the end-users.0/ . 8 of 25 Engineering Ingegneria Informatica S. 2. In the next chapters the allowed channel/service and channel/interaction combinations will be outlined. a OLAP. It provides for the engines configuration. Here you can execute it. the document can be released for the end-user. see to the section related to the services exposed by this portlet. the functional tree management and the extraordinary maintenance of the documents configuration and state. the category locations and the documents profiling). o BIObjSearch. o SBIDevelopmentContext: it enables the services for BI Objects configuration to be used in a portal setting. o BIQbE. you can navigate through the category tree. by including the necessary portlets. This portlet works in two different ways: for the test users. The first available portlets. o SBIFunctionality: it offers the functional view of the documents registered in SpagoBI platform and allows their parametric activation. It's responsible for setting the execution context of the BI services (ex: the parameters definition and the use mode.. It makes available the core of a BI solution in a portal setting. are: o SBISettings: it offers the necessary services to manage the technological platform configuration to a portal administrator. If the test is successful. or as a part of an existing one. These implementations are based on Spago’s adapters (AdapterPortlet. 2005. the portlet filters the document in RELEASE state and according to his functional roles.SpagoBI Architectural Design o JMS for platform interaction by JMS messages.org/licenses/by-nc-sa/2. It’s possible to build your custom interface in a new Business Intelligence Portal. SpagoBI’s services and interactions are useful only with some of the available channels/protocols. up to reach the documents which realize a specific functionality. SpagoBI Architectural Design ver 0. AdapterJMS). For further information. everyone deployed in the same WebApplication. it only filters the document in TEST state and can activate them simulating all the expected final users' roles.5 August. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. a Data Mining model or a Dashboard view. To view a copy of this license. the control rules.1 BIPORTLET All main BI services are exposed via portlet. In this case. 5th 2005 – pag.

4 In progress.1. Some service components support the core effectiveness preparing the working environment in its collateral aspects: parameters unified management.org/licenses/by-nc-sa/2. BIMESSAGE JMS messages enables the analytical process. 2005.p.1. BIXCUBE A simple transmission of the information and the results is made easier by means of XML structures and models.3 BISERVICE You can use Web Services to interact with other enterprise applications or portals. 5th 2005 – pag. documents storage and search. 2..1.SpagoBI Architectural Design 2. Data Mining. but they support and make easier the process. the service components don’t correspond to an analytical task (unlike OLAP or Data Mining).A. The controller takes the responsibility for a successful coordination of the core components interaction and of their interaction with the service components. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. approval and management workflow.5 August. query by example capabilities. 2. engines and object profiling systems. They are described in the following. Its main components are Report.2 A N A L YT I C AL LAYER The Analytical Layer is the platform core which coordinates all the analytical activities supplying their supporting tools. To view a copy of this license.1 SERVICE COMPONENTS In the analytical layer. Dashboard and Scorecards modules: each of them corresponds to a specific functionality of the same architectural setting: this layer allows an easy learning and a modular use.2 In progress. it also highlight the critical conditions. structuring of categories for documents classification. 2. In progress. 9 of 25 Engineering Ingegneria Informatica S.0/ . visit http://creativecommons. 2.2. filters and domains. SpagoBI Architectural Design ver 0. OLAP.

1.2. predefined list of values.. visit http://creativecommons.org/licenses/by-nc-sa/2.see at the corresponding section for details -) 2. Data Mining.2 BIProfiling BIProfiling is responsible for the analytical documents registration. o validation rules to check the inserted value. 10 of 25 Engineering Ingegneria Informatica S. o parameter’s behaviour definition (its presentation form and value checks modality) in relation with user’s roles. BIParameter component enables: o input modality definition (manual input. 5th 2005 – pag. it also regulates the data visibility according to users’ roles. the BIProfiling component enables: o engines registration with standardized information set. SpagoBI Architectural Design ver 0. values from lookup tables or view. it can interact with any analytical one’s (report. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. OLAP. Dashboard and scorecard .2.A. default value and so on). you can have some reports running on JasperReport (FOSS product) together with others reports working on CrystalReport (proprietary product). To view a copy of this license.SpagoBI Architectural Design Picture 4 – Service Components 2. For example.1 BIParameter BIParameter takes the responsibility to manage the input values for the analytical modules startup and navigation. Every analytical module can be realized with different tools and it can use different engines to run.1.p. BIParameter is an independent component. 2005.5 August.0/ . So. useful for its execution. So.

p. BIFunctionality manages the structuring of a functional tree providing for: o the tree creation and maintenance. Otherwise.1. the services offered are clear: for example. ’sales deviation from plan’ and so on.6 BINotify BINotify is an alerting and events notification component.org/licenses/by-nc-sa/2.5 August. o the visibility and autority regulation on the users roles base.2. o the production of a generic analytical documents’ keeping.2.3 BIFunctionality BIFunctionality takes the responsibility to define and to manage the Business Intelligence services realized on the SpagoBI platform. Moreover they can be organized in other sub-functionalities. Each of them collects many detailed documents like 'sale trend forecast for product industry'. 2.SpagoBI Architectural Design o analytical document registration. To view a copy of this license. In a enterprise portal. It enables the saving of a template structure for subsequent reports development. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. ‘Simulation area’.2.1.2. usually in a Business Intelligence portal the functionalities aren’t so defined.0/ . In progress. SpagoBI Architectural Design ver 0. BIFunctionality depends from the BIProfiling component for analytical documents’ interface. under the tree lowest level (of every type. For every document (that is already developed) some standardized information are kept. o the approval and certification procedure for the documents’ production. a banking portal will have functionalities such as 'transfer management'. You can define services such as ‘Sales analysis’.. also Data Mining models too).4 BISearch BISearch is a documental search engine component. 2. o the maintenance of the historical versions for the relevant documents. 2005. in cooperation with the workflow supplied by the administration tools (looks later for additional information). 'trading'. visit http://creativecommons.5 BIQbE BIQbE is a component for inquiring of data in a semantic form.1. 2.A. ‘annual sales reporting’. It offers a visual mode for data inquiring. 11 of 25 Engineering Ingegneria Informatica S. In progress. 5th 2005 – pag. XML).1. ‘accounting operations list’. BIProfiling depends on BIParameter component for the parameters’ interface. 2. ‘Marketing models’. including the specific engine to use and the parameter input to receive. ‘Budget’. or the results’ exporting for external elaborations (ex: cvs.

SpagoBI Architectural Design In progress. OLAP Analysis. They have an interface layer and a common architecture. The analysis axis and the observation measures are structured. Decision Trees.) will enable the data analysis. o In the Management Performance context. o The multidimensional structures for the OLAP analysis add a higher degree of freedom and variability. SpagoBI enables the navigation capability between different reports. 2005.html. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.p. etc). etc. SpagoBI doesn’t provide the specific tool but it’s able to manage their different configuration and execution phase. drill-across. Data Mining. SpagoBI supports Data Mining models’ implementations and their results’ analysis trough the other Business Intelligence objects. . The common architecture for all the core components (generically called BIObj in the sequel) is the following: SpagoBI Architectural Design ver 0.. SpagoBI provides many widgets for the dashboards structuring and the parametric evaluation of performance scores.2. they manage their own application level context in a specific way. The architecture aims don’t concern the analytical objects development’s instruments.org/licenses/by-nc-sa/2. Dashboards and Scorecards are the BI core components of SpagoBI.5 August. by means of drill-down. slice and dice operations.pdf.A. visit http://creativecommons. o Data Mining algorithms and processes (Neural Networks. To view a copy of this license. 12 of 25 Engineering Ingegneria Informatica S.xls.csv. 2. inheriting the settings. In more details: o Reports realize the structured information views. This enables the obtaining of data examination at various detail levels and from various perspectives. . they have a greater diffusion level according to a static structure (. . You can draw a report using a tool for JasperReport or by means of the CrystalReport designer. 5th 2005 – pag.0/ . Reporting. with the aim to find out the hidden information.2 CORE COMPONENTS The SpagoBI platform’s heart and its analytical center are the modules directly faced to the datawarehouse inquiring and to its stored information analysing.

5 August.A. 2005.0/ .SpagoBI Architectural Design BIContextController Report Olap Data Mining Dash & Score Controller Driver 1 Engine 1 Engine 2 Engine 3 Logic Driver 2 Driver 3 Alternative drivers/engines Dao Data & Metadata Layer Picture 5 – Core Components interaction According to the classes. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. 5th 2005 – pag. visit http://creativecommons. 13 of 25 Engineering Ingegneria Informatica S.p..org/licenses/by-nc-sa/2. To view a copy of this license. the picture is: Picture 6 – Core Component classes SpagoBI Architectural Design ver 0.

2.org/licenses/by-nc-sa/2.2. o by directly implementing the analytical logic. 5th 2005 – pag. o it manages the BIObj’s state according to the approval and certification workflow. o it translates the general setting received from the BIContextController into specific ones that are understandable from the specific component. o by keeping the control logic of the execution and by driving the engine interaction (SUPERVISED mode).1 BIObjController The BIObjController is the abstract definition of a delegated structure which maintains the control on a specific analytical area related to the general context. then.e.2. the BIObjController takes the following responsibility: o it gives a unique interface to the BIContextController (i. the different implementations specialize their own work logics.SpagoBI Architectural Design An abstract definition of the components generalizes the common behaviours and the interactions with the other architectural layers. A BIObj can work in three different ways: o by totally delegating the execution and the management of the interaction to the specify engine (DELEGATED mode). Cooperating with the BIContextController (look after for its description).A.5 August. Façade pattern). BIObjController depends on BIContextController component for the general context interface (in a bi-directional relationship) and from BIObjLogic class for the analytical logic execution. in the SUPERVISED and PROPRIETARY execution way. o it manages a specific interface toward the BiObjLogic.0/ . it must: o supervise the specific logic of the analytical components. this object turns the generic parameters into specific ones that are suitable for their managed analytical area. o register and give back the new settings to the BIContextController when final user changes it. It also returns some additional data or new settings to the BIContextController. without using outside engines (PROPRIETARY mode). Independently from the BIObj execution mode. Furthermore. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. it only turns the BIObjController request to the specific driver. visit http://creativecommons. SpagoBI Architectural Design ver 0. 2.p. o manage the user interaction in its analytical area. According to the chosen working mode. It works in a different way according to the BIObj behaviour mode: o in DELEGATED mode.2.2 BIObjLogic The BIObjLogic class realizes the specific logics of an analytical area. 2005. 14 of 25 Engineering Ingegneria Informatica S.. To view a copy of this license. the component’s classes have a different weight and are composed by different tasks.2.

2. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. 5th 2005 – pag. BIObjLogic depends on BIDriver for the general engine’s interface and on BIDao for generic Data Layer interface. It works like this: o it translates the parameters’ values in a QueryString format.A..2.org/licenses/by-nc-sa/2.0/ . o it invokes the engine. without the drivers support.4 BIDriver The BIDriver class takes the responsibility for the engine’s interfacing. 2. o it creates the engine execution context.2. it access the data warehouse using the rdbms analytical features directly (if there are) or through the generic semantic layer. the specific engine directly manages the data layer access through the specific semantic layer. because: o in DELEGATED and SUPERVISED mode. It manages the parameters exchange between the objects ensuring the values’ heredity during the user driven navigation.p.3 BICONTEXTCONTROLLER The BIContextController acts as a focal point for the coordinating operations across the whole platform. 2. SpagoBI Architectural Design ver 0. 15 of 25 Engineering Ingegneria Informatica S. 2005.SpagoBI Architectural Design o in SUPERVISED mode. o it extents the QueryString with the specific engines’ parameters. 2.3 BIObjDAO The BIObjDao class takes the responsibility to interact with the data layer. BIObjDao interfaces the chosen rdbms by means of the generic semantic layer.2.2. it directly implements the analytical functions of its competence. it interacts with the specific engine through its driver. o in PROPRIETARY mode. providing the translation of the general analytical method into a specific engine invocation.5 August. It has a relevant role only in the proprietary mode of BI component execution. To view a copy of this license. BIDriver depends on the particular engine which it works with. o in PROPRIETARY mode. in order to realize the analytical functions of its competence. visit http://creativecommons.

o the caching of frequently used data. o managing the objects instances and their time life according to their scope and level.5 August. To view a copy of this license. o keeping a limit to the BIObjs instances number. 16 of 25 Engineering Ingegneria Informatica S. o the parameters’ inheritance in documents navigation. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. o interacting with the session at the right level. 5th 2005 – pag. in order to regulate the workload. visit http://creativecommons.p. o the management of a pool of BIObj instances. o the navigation management through the different BIObjs..SpagoBI Architectural Design BIPortlet BIService BIXCube BIMessage BIContextController ADMINISTRATIVE TOOLS / SCHEDULING BIParameter BIProfiling Controller Driver 1 1 Engine BIFunctionality Logic BINotify BIQbE Service Components BISearch Driver 2 2 Engine Driver 3 3 Engine Dao BI Core Component Data & Metadata Layer Picture 7 – BIContextController interaction The BIContextController component enables: o the interaction management between Service Components and BIObjs. o the factory implementation for the BIObjs instance.0/ . 2005. o the management of a policy for the BIObjs releases. o the interaction management between Administrative Components and BIObjs.A. in order to improve the performances and the memory allocation strategies. SpagoBI Architectural Design ver 0.org/licenses/by-nc-sa/2.

Then. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.5 August. dashboard and scorecard widget) and to the execution way it supports (delegated. Moreover.org/licenses/by-nc-sa/2. it works like this: o it takes a generic instance of the right BIObj from a pool. o it returns the BIObjController ’s handle to the BIContextController.0/ . when the BIObjFactory has to allocate a BIObj which works in a stateless mode. On the other way. For the BIObjs factory implementation. in order to guarantee the user’s functionalities as much as the platform performances. when the BIObjFactory has to allocate a BIObj which works in a statefull mode.. 17 of 25 Engineering Ingegneria Informatica S.SpagoBI Architectural Design The BIContextController depends on the BIParameter.4 BIOBJFACTORY A BIObj characterizes itself according to the document type it represents (report.A.p. To view a copy of this license. each different BIObj is implemented as a statefull and/or stateless component. OLAP. the component schema follows. data mining model. 5th 2005 – pag. BIProfiling.2. BIObjController components for their relative interface. Picture 8 – BIObj factory component schema 2. it works like this: SpagoBI Architectural Design ver 0. supervised or proprietary mode). o it sets a specific data retrieve from the BIContextController. 2005. visit http://creativecommons.

2.p. Some service repositories support specific tools or platform aspects such as the document management. and to success in recovering them at a later time. The metadata exchange is implemented according to the CWMI standard and with an hub for the external metadata collected by a bridge. On the contrary. transformation and loading. because many tools already have their own semantic layer.0/ . SpagoBI provides a meta-description for its technical aspects. supervised or proprietary) o it returns the BIObjController ’s handle to the BIContextController. A Data flows acceptance area. data mining model. The relation with the source systems is organized by an ETL module. a stateless BIObj needs to interact with the BIContextController a lot. for the business meanings of the data and for the processing information. For the event-driven strategy.. The interaction with the core business components works in a native way or through a semantic interface layer. SpagoBI provides a formal description of event to be monitored and alerts to notify. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. In general. You can see in the following picture how these aspects get one’s act together: SpagoBI Architectural Design ver 0.SpagoBI Architectural Design o it instances the right BIObj type (report.3 D A T A AND M E T A D AT A L A Y E R The Data and Metadata Layer locates itself at the data warehouse level. is implemented too. OLAP. also not having specific data in the DWH.5 August.org/licenses/by-nc-sa/2. dashboard and scorecard widget) o it instances the BIObj type according to its running mode (delegated. which can be generic (for example with Hibernate interface) or specific. that provides some features for data extraction. the private repositories and so on. so SpagoBI refers only to the metadata level. To view a copy of this license. 5th 2005 – pag. where many formal checks are applied.A. a statefull BIObj keeps its settings and the BIContextController is only be able to recover its right handle. visit http://creativecommons. The data warehouse design is out of the SpagoBI scope because a DWH necessary refers to a specific customer's world. 2005. 18 of 25 Engineering Ingegneria Informatica S. in order to register all its state changes.

2005. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license. visit http://creativecommons. SpagoBI Architectural Design ver 0.5 August.p. so.org/licenses/by-nc-sa/2. 2. 19 of 25 Engineering Ingegneria Informatica S.A. the formal validations’ rules. the metadata repository contains information related to: o the technical characteristics of the data stored in the data warehouse.3. like their formats’ description.1 SERVICE REPOSITORY The service repository contains private data structures which support some particular tools usage.0/ .SpagoBI Architectural Design BIParameter BIProfiling BIFunctionality BINotify BISearch BIReport BIOlap BIData Mining BIDashboard BIQbE Service Components Specific semantic layer BI Core Components (BIObj) Generic semantic layer Native access MDI Bridge MDI HUB CWMI METADATA Tecnical Business MD Process MD MD Even define Alert config DWH Alerts registry Rule Engine Event store DWH Service Repository ETL Source Systems Staging Area Picture 9 – Data & Metadata Layer 2. usage preconditions. o the data business meanings..3. the mapping with the source systems and so on. 5th 2005 – pag. derivation and aggregation methods and so on.2 METADATA REPOSITORY Metadata are data about data. The first one is the CMS repository. in the term of semantic validation rules and description. until it will migrate as an integrated metadata structure.

20 of 25 Engineering Ingegneria Informatica S..1 Events Define and Alerts Configuration At the metadata level you can provide a formal definition about the events to be monitored and about the alerts’ strategy to notify them.3. In progress. according to their formal description’s set up on the metadata level. however some structures can be realized in order to guide the event-driven behaviour of the platform.5 August.2. A bridge (the MDI Bridge) allows SpagoBI to communicate with other CWM-compliant systems. the rule engine is able to fill Event Store and Alerts Registry tables according to the metadata level set-up rules (Event Define and Alerts Configuration tables). This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. visit http://creativecommons. MDI Hub and MDI Bridge SpagoBI adopts the CWMI standard (Common Warehouse Metadata Interchange) for the metadata exchange with others platforms and products. 2005. In this case the metadata interaction gains a strong importance. starting from the rough data value up to its semantic meaning building. To view a copy of this license.3. 2.3.A.3. In progress. SpagoBI Architectural Design ver 0.3 Rule engine When a specific data warehouse is available. In progress.3. 2.0/ . Setting up an operating strategy without a specific data warehouse is possible.3.3.SpagoBI Architectural Design o the data process describing all the actions carried out on the information. In progress.3 DATA WAREHOUSE The data warehouse design is out of the SpagoBI scope.2 Events Store and Alerts Registry At the data warehouse level you can find the implementation of the structures on which both the real events are stored and the notification requests are written.1 CWMI.3. 2. The Metadata Integration Hub (MDI Hub) is the first collection point of the metadata coming from other platforms and products that are able to interact via the CWMI standard.p. 2.org/licenses/by-nc-sa/2. 5th 2005 – pag. 2.

To view a copy of this license.p. 5th 2005 – pag. 2.5 GENERIC SEMANTIC LAYER The Generic Semantic Layer makes the data layer independent from the data representation. In progress..3. 2. In progress. structured as follows: File System Listner LISTNER config FTP Listner LISTNER File System Valid Valid data Valid data data Data Data Store Data Store Store config Listner LISTNER config Listner LISTNER config Listner LISTNER config Listner LISTNER config Web Service … … HTTP Validation Engine Rejected Rejected data Rejected data data Staging loader Rejects Rejects Store Rejects Store Store E T L Rules Repository Metadati Metadati Data capture – sincronization -validation Staging Area SpagoBI Architectural Design ver 0. The first level is an acceptance area for the data flows. it provides some features for data extraction.6 ETL – STAGING AREA An ETL module organizes the relation with the source systems.5 August. that are often implemented in the specific products.0/ .SpagoBI Architectural Design 2.3. In progress. 21 of 25 Engineering Ingegneria Informatica S.org/licenses/by-nc-sa/2.3. transformation and loading. visit http://creativecommons.A. in a standardized way. 2005. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.4 SPECIFIC SEMANTIC LAYER The Specific Semantic Layer includes every private way of access to the data.

which are described below. that sets up the management strategies for both of them. 5th 2005 – pag.1 SCHEDULER The scheduler is the administration component for the back-ground activation of the relevant processes.4 A DM I N I S T R AT I O N Administration users are supported by many tools for the whole platform configuration and control. It interacts with the BIObjs and the BIParameters through the BIContextController. producing the discards flow. the following operations are carried out: o the formal controls are executed on the whole flow. In progress. In general. 2005. in terms of a set up on the metadata. 2.org/licenses/by-nc-sa/2. 22 of 25 Engineering Ingegneria Informatica S.4. o the formal controls are executed on all the data in the flow.4. it allows the planning of any platform management process.0/ . enabling the deferred production of the documents. o the flow is synchronized with the expetected ones. o the right and wrong data are provided in input to the ETL process. o the right data are separated from the wrong ones. in terms of a set up on the metadata.p. METADATA MANAGEMENT INTERFACE WORKFLOW LOGGING / AUDITING SpagoBI Architectural Design ver 0.2 In progress.4 In progress. To view a copy of this license.4. 2. visit http://creativecommons. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.5 August. 2.4. 2.A.3 In progress.SpagoBI Architectural Design Picture 10 – Acceptance data flows area Many listeners check the possible channels and when a flow comes on. 2..

5th 2005 – pag.p. CrystalReport). BIDriver). the integration of existing infrastructures and the publishing of the services on different channels. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license.2 F I R S T TOOLS SELECTION The following is a list of Free Open Source Software solution used by SpagoBI. 3. refer to : o http://spago-info.org/projects/jackrabbit. SpagoBI integrates the reports developed for JasperReport engine. 23 of 25 Engineering Ingegneria Informatica S. refer to : o http://incubator. for every additional engine there is a specific driver which is developed and managed as a SpagoBI plug-in. but it keeps its platform core clearly separate from the objects which realizes the integration (i.0/ . 2005.it 3.. visit http://creativecommons.org/licenses/by-nc-sa/2. it allows any substitution with another JSR 170 solution with no modification.2.2.html SpagoBI Architectural Design ver 0.1 APPLICATION FRAMEWORK: SPAGO Spago is a J2EE framework that enables the development of multichannel applications and integration services. In this way. 3.A.1 I N T E G R A T I O N S T RA T E G Y SpagoBI can integrate different FOSS tools using them for the services’ realization and execution. The same methods can be extended integrating proprietary products too (i.SpagoBI Architectural Design 3 Executive level architecture This chapter outline the platform integration strategy and a first selection of the tools used by SpagoBI is provided. o Integration.eng. For further information.2 CONTENT REPOSITORY: JACKRABBIT JackRabbit is a content repository API based on JSR-170. The relation modes will support: o Simple use. It allows the development of web applications.e.apache.e.5 August. For further information. 3. SpagoBI uses a CMS solution according to the JSR 170 specification.

For further information.ac. It uses Mondrian and XMLA as its OLAP engines. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License. To view a copy of this license.2. HTML.waikato.net/ 3. to the printer or into PDF. refer to : o http://jasperreports.nz/~ml/weka/ QBE SUPPORT: HIBERNATE Hibernate is an object/relational persistence and query service for Java.net/ o http://mondrian.sourceforge. users can perform typical OLAP navigations like drill down.6 DATA MINING ENGINE: WEKA Weka is a collection of machine learning algorithms for data mining tasks. For further information.org/ 3.4 REPORT ENGINE: JASPERREPORT JasperReports is an open source Java reporting tool that allows the delivery of rich contents onto the screen.. 2005.cs.SpagoBI Architectural Design 3.org/licenses/by-nc-sa/2.7 http://www. By means of it. refer to : o http://www. refer to : o http://jpivot. 24 of 25 Engineering Ingegneria Informatica S.2. CSV and XML files.5 OLAP CLIENT/ENGINE: JPIVOT/MONDRIAN JPivot is a JSP custom tag library that renders an OLAP table and chart.sourceforge.sourceforge.2.org/ SpagoBI Architectural Design ver 0. For further information.2.hibernate.apache. refer to : o http://lucene.5 August.net/ 3. For further information.3 SEARCH ENGINE: LUCENE Lucene is a Java text search engine library. It enables you to interactively analyze very large datasets stored in SQL databases without writing SQL code. refer to : o 3. slice and dice. visit http://creativecommons.2.0/ . For further information. Mondrian is an OLAP server written in Java.A. XLS. 5th 2005 – pag.p.

8 ETL SUPPORT: BIE The Business Integration Engine (BIE) is designed to help organizations to exchange data created in different applications in order to streamline the processes and to improve efficiency.objectweb. eXo Platform is not a SpagoBI’s component.opensymphony.brunswickwdi. refer to : o http://www. but it is the first portal environment that has been verified by SpagoBI Platform..11 PORTAL ENVIRONMENT – EXO PLATFORM eXo Platform is an application suite providing the more common services for building web based information portals. 25 of 25 Engineering Ingegneria Informatica S.org/licenses/by-nc-sa/2.objectweb. 2005. Loading) connecting to JDBC data sources and performing XML-defined transformations. Transformation. Furthermore.2.org/projects/octopus/ 3.SpagoBI Architectural Design 3. To view a copy of this license.0/ . SpagoBI implements the interface for the recovery of the users’ roles stored in eXo portal settings.A. This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.9 ETL SUPPORT: OCTOPUS Octopus is an ETL tool (Extraction.2.com/quartz/ 3. For further information. More information about eXo Platform are available starting from : o http://exoplatform.5 August. For further information.2.10 ADMINISTRATION – SCHEDULER: QUARTZ Quartz is a job scheduler for executing jobs whose tasks are defined as standard Java components or EJBs. refer to : o http://www. 5th 2005 – pag. refer to : o http://forge. It implements the JSR 168 portlet API specification.org SpagoBI Architectural Design ver 0.2. For further information.p.com/bie 3. visit http://creativecommons.

Sign up to vote on this title
UsefulNot useful