Saiku BI server

Usage

Setting up a parallel BI server will provide users with a drag-and-drop OLAP tool.

Positives

• Very nice and intuitive UI
• Can reuse existing OLAP scheme from the builtin OLAP mavigator

Negatives

• User authentication must be handled seperately
• Currently no support for dimension properties

Preparations

1. Install the Saku client
2. Install the Saku backend

Using the Tempus Serva OLAP cube schemas

Scenario 1: Installed at SAME server

1. Create a new file tempusserva in <Saiku backend server>\WEB-INF\classes\tempusserva\saiku-datasources\ with the following contents

 type=OLAP
 name=tempusserva
 driver=mondrian.olap4j.MondrianOlap4jDriver
 location=jdbc:mondrian:Jdbc=jdbc:mysql://localhost/tslive;Catalog=<Path to tsCubeDefinitions.xml>;JdbcDrivers=com.mysql.jdbc.Driver;
 username=root
 password=TempusServa

Scenario 1: Installed at OTHER server

1. Create a new remote user in the MySQL database
2. Create a new folde named tempusserva in: <Saiku backend server>\WEB-INF\classes
3. Copy the file <Tempus Serva application>\WEB-INF\queries\tsCubeDefinitions.xml to <Saiku backend server>\WEB-INF\classes\tempusserva\
4. Create a new file tempusserva in <Saiku backend server>\WEB-INF\classes\tempusserva\saiku-datasources\ with the following contents

 type=OLAP
 name=tempusserva
 driver=mondrian.olap4j.MondrianOlap4jDriver
 location=jdbc:mondrian:Jdbc=jdbc:mysql://<dbHostname>/tslive;Catalog=<Path to tsCubeDefinitions.xml>;JdbcDrivers=com.mysql.jdbc.Driver;
 username=<newRemoteUsername>
 password=<newRemotePassword>

Note: A service for remote HTTP retrieval of the schema will be implemented late 2014, so the OLAP schema can be retrieved on the fly from the remote Saiku server