Hi guys. Thanks so much for a great piece of software.
Question: How do you recommend setting up a slice and dice environment for multiple user groups, eg finance and operations. Financial data is privileged and should only be visible to users from finance. The cubes will not overlap, ie common data will be integrated at the database level, not the presentation level. Do I have to :
1: Install 2 independent instances of Saiku, but on a single Tomcat instance, and use the URL to distinguish the user's resources
2: Use a single Saiku instance but somehow segregate users within the domain of Saiku
Has anyone done something similar?
asked 28 Jul '11, 06:01
at the moment you need to separate it on the application level (2 different instances)
we are planning to integrate security + olap roles more tightly so you can define user roles that are associated with levels/dimensions/cubes as defined here: http://mondrian.pentaho.com/documentation/schema.php#Access_control
there exist already tickets for that in our issue tracker (http://projects.analytical-labs.com/projects/saiku/issues)
right now i cant really say in which version this will be available but its on of the higher priority items on our todo
answered 28 Jul '11, 09:50
Thanks so much
answered 28 Jul '11, 10:32
OK, so I've set up saiku-server with multiple instances, each with its own port so that each user group can access a completely independent collection of cubes. But for some bizarre reason it's not keeping things completely separate:
1/12 : choose port 55000 for a new instance 2/12 : Make a dir under saiku-server named tomcat55000 3/12 : make copies of start and stop scripts and rename as start-saiku55000.sh and stop-saiku55000.sh 4/12 : edit each script and add export CATALINA_BASE="$DIR/tomcat55000" export CATALINA_HOME="$DIR/tomcat" 5/12 : copy CATALINA_HOME/webapps/ to CATALINA_BASE/webapps/ 6/12 : copy CATALINA_HOME/conf/server.xml to CATALINA_BASE/conf/ 7/12 : copy CATALINA_HOME/conf/web.xml to CATALINA_BASE/conf/ 8/12 : edit CATALINA_BASE/conf/server.xml and change shutdown port to 55001 and HTTP connector port to 55000 9/12 : make work, temp and logs dirs in CATALINA_BASE 10/12 : copy datasource and mondrian catalog to CATALINA_BASE/webapps/saiku/WEB-INF/classes/saiku-datasources 11/12 invoke start-saiku55000.sh
12/12 Now for the strange behaviour: When I access localhost:55000, everything works fine up to when I want to select a cube, as no cubes are on display. However, if I also copy the datasource and mondrian schema to the default 8080 instance and access localhost:8080 first, then the second attempt on localhost:55000 works right. I've tried to see whether any files in the CATALINA_HOME are amended, but none other than log files. Duplicating all datasources and catalogs in the default 8080 instance is clearly not feasable.
Why is this the case? Should I try and create instances in a different manner?
answered 01 Oct '11, 09:48
usually i just copy the saiku-server folder (so i have two: saiku-server1 and saiku-server2) and edit the tomcat/conf/server.xml to use different ports
that always worked for me
theoretically your way works as well but i would personally prefer to really separate those two in two different folders, they are easy enough to update anyway.
would that work for you too?
answered 04 Oct '11, 10:24
Once you sign in you will be able to subscribe for any updates hereBy RSS:
Asked: 28 Jul '11, 06:01
Seen: 1,118 times
Last updated: 04 Oct '11, 10:24