Like what you see? Have a play with our trial version.

Yellowfin OLAP Cube Connectivity

Yellowfin can connect and report from pre-built cubes exposed via an XMLA connection. Yellowfin views can be based on a cube, enabling reports to be written using a similar process to Yellowfin reports based on a standard RDBMS. Yellowfin does not have the capability to generate cubes, however.

XML for Analysis (XMLA) is a standard protocol for accessing data from OLAP data sources. It is built on existing standards including XML, SOAP and HTTP.

This guide will briefly cover the connection process for XMLA data sources. The connection method is largely independent of the data source you are connecting to, but examples are provided for connecting to Microsoft Analysis Services, Mondrian and PALO sources.


OLAP connectivity is provided to give access to existing cube infrastructure that may exist at an organization. When starting a new BI project with Yellowfin, it is recommended to use a RDBMS with a data warehouse, as this has several advantages over using a cube, with similar drill-down capabilities.


Using OLAP cubes has several restrictions compared to the functionality provided by Yellowfin for relational data sources.

  • Yellowfin inherits the hierarchies and data-types from the cube, and these cannot be changed in Yellowfin. 
  • Grouped Columns is not supported on Cubes. 

XMLA Data Source

Interface to an XMLA data source is via a HTTP URL. All data access is performed via HTTP requests to the data source. As such, the only connection parameters required are the XMLA URL, and an optional username and password if the data source requires them.

The method for enabling the XMLA interface depends on the data source you are connecting to, and therefore is not covered by this guide. 

Depending on the data source, the XMLA interface may be a built-in feature or require external software and configuration – for example, Microsoft Analysis Services requires IIS to be installed and a virtual directory configured to handle XMLA requests.

  1. Click on the Create button and select Data Source.
  2. Select Cube as the data source type in the "Add a Data Source" popup.
  3. Fill in all the required fields in the Cube Settings.
  4. Click on “Test Connection” to ensure a successful connection. Then, click Save.
  5. Continue creating views for this cube connection.

Examples of Connections

Microsoft Analysis Services

Microsoft Analysis Services requires an initial step of mounting the cube as an XMLA service. This requires configuring a redirection filter on an IIS server. This process differs depending on the version of Microsoft Analysis Services and the version of IIS installed. This process is not covered in this guide. The following links may assist in this process:

Configure HTTP Access to Analysis Services on Internet Information Services (IIS) 8.0:

The XMLA URL will depend on how IIS is configured. A common configuration is to have a virtual directory called “olap” which contains the connection pump dll file. In this case the URL would look like:


NB. Microsoft Analysis Services 2000 is not supported.


Mondrian is an open-source XMLA interface to an underlying RDBMS. We recommend the use of Mondrian only if existing Mondrian infrastructure is available, as Yellowfin can replicate the functionality of Mondrian directly from a relational database itself. 

It is assumed that Mondrian has been configured to interface with the database where report data is to be sourced. 

Mondrian runs as a web application on Tomcat (by default) and must be configured to enable XMLA. This process is outlined in the Mondrian documentation but basically requires the addition of the  MondrianXmlaServlet to the web.xml file for the Mondrian web application:


The XMLA URL is the address to the MondrianXmlaServlet, for example:



The Premium Edition of PALO OLAP server supports XMLA connections by installing the optional XMLA provider.

The default connection URL for the PALO XMLA provider is: 

XMLA URL: http://localhost:4242/xmla 

Username: admin

Password: admin

  • No labels