Monthly Archives: April 2015

This is a brief overview of how you can use the MDXGENERATE() function. All the examples below work with the SteelWheelsSales Cube, which ships with the Pentaho BA Server. Try the examples listed below either with Pentaho Analyzer, the Saiku CE plugin, Pivot4J or Roland Bouman’s Pentaho Analysis Shell (Pash) (The last 3 ones are plugins, which you can download via the Pentaho Marketplace).

The GENERATE() function has two different applications:

If the second parameter is a set, it will return the members that exist in both sets ( a UNION() of the sets). You can think of it as a kind of for-each function which checks if members in the first set exist in the second one. ALL can be used as a third parameter to keep any duplicates.

If the second parameter is a string expression then the members will be concatenated.

We have a Postgres instance running on our server and are good with Tomcat as application server so Archive mode of installation is suitable for us. Pentaho installation requires two things be installed before starting with Pentaho installation.

Unzip the archive file and you can see the installation files inside extracted directory.

1

2

3

$ unzip biserver-ee-5.x-dist.zip

$ cdbiserver-ee-5.x;ls

install.bat installer.jar install.sh license.txt README.txt

In remote servers Pentaho can be installed on console mode with ‘-console’. Accept the license and provide the installation path to install Pentaho BI server.

1

$ java -jar installer.jar -console

Find biserver-ee directory under the installation path and set sh files to executable mode.

1

2

$ cdbiserver-ee;

$ find. -typef -iname '*.sh'-execchmoda+x {} \;

Let’s create repository databases by running queries in SQL files located at biserver-ee/data/postgresql.
quartz, hibernate and jackrabbit databases will be created by executing these SQL files. Database names, usernames and password can be changed by modifying in SQL files if required.

1

2

3

4

5

$ cdbiserver-ee/data/postgresql

$ psql -U postgres -p 5432 -a -f create_jcr_postgresql.sql

$ psql -U postgres -p 5432 -a -f create_quartz_postgresql.sql

$ psql -U postgres -p 5432 -a -f create_repository_postgresql.sql

$ psql -U postgres -p 5432 -a -f pentaho_mart_postgresql.sql

Pentaho uses postgresql as default database and files are configured to use postgresql. So just verify the database_name, username and password to work with installed postgresql and databases created.

There are more occurrences in this file. Carefully do the necessary changes in all the places.
– biserver-ee/pentaho-solutions/system/jackrabbit/repository.xml
– biserver-ee/pentaho-solutions/system/jackrabbit/repository/workspaces/default/workspace.xml

A license needs to be installed to use Pentaho. Navigate to the license-installer directory in installation path. Feed license file to install_license.sh, separating more than one license file with spaces.

Install plugins
Archive mode of installation installs only BI Server. Necessary plugins can to be installed manually. Here install the plugins for reporting, analyzer and dashboard. Plugins are available at the same place where download BI server. Download these three files and place at any path on server
Reporting – pir-plugin-ee-5.x-dist.zip
Analyzer – pdd-plugin-ee-5.0.0.1-dist.zip
Dashboard – paz-plugin-ee-5.0.0.1-dist.zip

All the plugins installed through same procedure
– Unzip the plugins and navigate to extracted directory
– run installer on console, accept the license and provide $INSTALLTION_PATH/biserver-ee/pentaho-solutions/system as location to install plugins

1

$ java -jar installer.jar -console

Lets start the BI server

1

biserver-ee$ ./start-pentaho.sh

Install the licenses for the plugins by login as admin user (default – Admin:password) or install through the command line
Administration -> License -> install licenses for plugin by click +

Troubleshooting:

1

2

biserver-ee$ tail-f tomcat/logs/catalina.out

biserver-ee$ tail-f tomcat/logs/pentaho.log

If the pentaho.xml is present at tomcat/conf/Catalina directory, delete it. It will be generated again when you start the BA Server.