You are on page 1of 6

spagobi_server - SpagoBI JPXMLA Engine

Page - last modified by Alessandra Toninelli on 2013/11/08 16:04

SpagoBI JPXMLA Engine

Alessandra Toninelli
2013/11/08 16:04

Table of Contents
SpagoBIXMLAEngine is based on the popular JPivot Olap client . It can be used to query an external
XMLA compliant server like MSAS or ESBASE .
In order to use the SpagoBIXMLAEngine you need to have already installed a working instance of an
olap server capable of expose its API through an XMLA interface like MSAS , ESBASE or Mondrian
Olap server . In order to install and configure your target Olap server please refer directly to the
documentation provided by your server vendor. Here after is briefly explained how to configure Mondrian
server over tomcat in order to make it work as an XMLA compliant olap server that can be queried by
Download the latest binary release from SourceForge , and unzip it
From the unzipped binary release, explode lib/mondrian.war to
TOMCAT_HOME/webapps/mondrian of your tomcat server (version 5.0.25 or later)
Create or open the file in TOMCAT_HOME/webapps/mondrian and
customize the mondrian.jdbcDrivers properties for your target database
Open the web.xml file in TOMCAT_HOME/webapps/mondrian/WEB-INF and customize the two
connect strings there to the same database parameters for the FoodMart database you installed
following the instructions above . That is,


Create a mondrian schema that maps your phisycal relational schema to the dimensional one used
by mondrian. You can do it by hand, starting from an existing schema and than modifying it
properly, or using some graphical design tool.
Add your mondrian schemas under TOMCAT_HOME/webapps/mondrian/WEB-INF/queries
TOMCAT_HOME/webapps/mondrian/WEB-INF create a file called datasources.xml, with
content like this:

<?xml version=
<DataSourceDescription>FoodMart 2000 Data Warehouse From MS Analysis Services
<DataSourceInfo>Provider=mondrian; Jdbc=jdbc:odbc:MondrianFoodMart;
<Catalog name=

<Catalog name=

<DataSourceInfo>Provider=mondrian; Jdbc=jdbc:odbc:MarketingDB;


<DataSourceDescription>Test Data Warehouse On PostgreSQL
<DataSourceInfo>Provider=mondrian; Jdbc=jdbc:postgresql://localhost/olap;
JdbcDrivers=org.postgresql.Driver; JdbcUser=pgsql; JdbcPassword=pgsql
<Catalog name=



ProviderType and AuthenticationMode are ignored because the XML/A implementation provided by
Mondrian server currently only supports 'MDP' and 'Unauthenticated'.
The name of each catalogs defined in datasources.xml must match the name attribute in the respective
schema file and must be unique
add or un-comment the following block into web.xml

Copy the following files:

If needed, copy your JDBC driver JAR to TOMCAT_HOME/common/endorsed
Copy xalan.jar to TOMCAT_HOME/common/endorsed
Start your database, if needed.
Start Tomcat.
Hit http://localhost:8080/mondrian
Download the SpagoBIJPXMLAEngine-bin-latest from here and unzip it
Copy the file SpagoBIJPXMLAEngine.war under TOMCAT_HOME/webapps
Add the SpagoBIXmlaEngine context in file TOMCAT_HOME/conf/server.xml

<Context docBase=
"SpagoBIJPXMLAEngine" path=
"/SpagoBIJPXMLAEngine" reloadable=
"true" source=

<ResourceLink global=
"spagobi_resource_path" name=
"spagobi_resource_path" type=

<ResourceLink global=
"spagobi_sso_class" name=
"spagobi_sso_class" type=

<ResourceLink global=
"spagobi_service_url" name=
"spagobi_service_url" type=


Add to file TOMCAT_HOME/webapps/SpagoBIXmlaEngine/WEBINF/classes/engine-config.xml

file the newly created schema in the SCHEMAS configuration block as shown down here

<SCHEMA catalogUri=
"/WEB-INF/queries/YourSchemaFileName.xml" name=
"YourSchemaName" />

and add also the connection to the mondrian engine:



"FoodmartXMLA" type=
"xmla" xmlaServerUrl=

Restart the server an create a new OLAP document by choosing the SpagoBIXmlaEngine
In the document detail page use the template builder to automatically create the template for the
given document

In olap engine the template specifies the target schema to use, the selected cube inside the target schema
and the starting MDX query to exucute on the selected cube;
here it is an example of the template generated by the wizard

Execute the newly created olap document