Saiku BI server - Revision history

Tvi: 28 revisions imported

2021-12-10T10:55:25Z

28 revisions imported

← Older revision	Revision as of 12:55, 10 December 2021
(No difference)

2016-07-08T15:12:36Z

Automatic installation

← Older revision		Revision as of 17:12, 8 July 2016
Line 14:		Line 14:
	The TS commandline tools can automate the installation		The TS commandline tools can automate the installation

	# Run 'tsinstallsaiku <instance name>'		# Run '''tsinstallsaiku <instance name>'''
	# Enable bcrypt passwords for users		# Enable bcrypt passwords for users

2016-07-08T15:12:25Z

Automatic installation

← Older revision		Revision as of 17:12, 8 July 2016
Line 14:		Line 14:
	The TS commandline tools can automate the installation		The TS commandline tools can automate the installation

	# Run ''tsinstallsaiku <instance name>''		# Run 'tsinstallsaiku <instance name>'
	# Enable bcrypt passwords for users		# Enable bcrypt passwords for users

2016-07-08T15:12:14Z

Automatic installation

← Older revision		Revision as of 17:12, 8 July 2016
Line 14:		Line 14:
	The TS commandline tools can automate the installation		The TS commandline tools can automate the installation

	# Run tsinstallsaiku <instance name>		# Run ''tsinstallsaiku <instance name>''
	# Enable bcrypt passwords for users		# Enable bcrypt passwords for users

2016-07-08T15:12:00Z

Automatic installation

← Older revision		Revision as of 17:12, 8 July 2016
Line 12:		Line 12:

	== Automatic installation ==		== Automatic installation ==
			The TS commandline tools can automate the installation

	# Run tsinstallsaiku <instance name>		# Run tsinstallsaiku <instance name>

2016-07-08T15:11:25Z

Usage

← Older revision		Revision as of 17:11, 8 July 2016
Line 10:		Line 10:
	* User authentication must be handled seperately		* User authentication must be handled seperately
	* Currently no support for dimension properties		* Currently no support for dimension properties

			== Automatic installation ==

			# Run tsinstallsaiku <instance name>
			# Enable bcrypt passwords for users

			Note: The users wont be able to login to Saiku before their password have been updated to bcrypt

			== Manual installation ==

	=== Preparations ===		=== Preparations ===

2014-03-09T05:14:35Z

Using the Tempus Serva OLAP cube schemas

← Older revision		Revision as of 07:14, 9 March 2014
Line 27:		Line 27:
	#* Verify that new credentials ARE working		#* Verify that new credentials ARE working

	=== Using the Tempus Serva OLAP ~~cube schemas~~ ===		=== Using the Tempus Serva OLAP cubes ===
			In order to expose the cubes Saiku needs a connection string to the database. The connection includes a reference to the OLAP schema used in Tempus Serva.

	==== Scenario 1: Installed at SAME server ====		==== Scenario 1: Installed at SAME server ====

2014-03-09T05:12:13Z

Preparations

← Older revision		Revision as of 07:12, 9 March 2014
Line 15:		Line 15:
	#* http://meteorite.bi/saiku/download		#* http://meteorite.bi/saiku/download
	# Install the Saku client ("Saiku UI WAR 2.5")		# Install the Saku client ("Saiku UI WAR 2.5")
	#* Option 1: Unpack the files to webapps\ROOT		#* The client is a single html file with a lot of built in JavaScript functionality
	#* Option 2: Create new folder in webapps and unpack the files		#** Option 1: Unpack the files to webapps\ROOT
	#* Option 3: Unpack and merge into the TempusServa folder		#** Option 2: Create new folder in webapps and unpack the files
			#** Option 3: Unpack and merge into the TempusServa folder
	# Install the Saku backend ("Saiku Backend WAR 2.5")		# Install the Saku backend ("Saiku Backend WAR 2.5")
	#* Rename the war file to '''saiku.war''' and place in webapps		#* Rename the war file to '''saiku.war''' and place in webapps

2014-03-09T05:07:34Z

Usage

← Older revision		Revision as of 07:07, 9 March 2014
Line 4:		Line 4:

	Positives		Positives
	* ~~Very nice~~ and intuitive UI		* Beautiful and intuitive UI
	* Can reuse existing OLAP scheme from the builtin OLAP mavigator		* Can reuse existing OLAP scheme from the builtin OLAP mavigator

2014-03-09T05:05:52Z

Scenario 1: Installed at SAME server

← Older revision		Revision as of 07:05, 9 March 2014
Line 39:		Line 39:
	username=root		username=root
	password=TempusServa		password=TempusServa

			Note: For safety reasons you should consider letting Saiku having its own database user. In that way you can later restrict access to certain data, and replace table access with views

	==== Scenario 1: Installed at OTHER server ====		==== Scenario 1: Installed at OTHER server ====