Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel

MySQL

You can create a separate flexbi_private user and grant it access to all MySQL databases which start with the flexbi_private prefix:

 

Code Block
GRANT ALL PRIVILEGES ON `flexbi_private%`.* TO 'flexbi_private'@'%' IDENTIFIED BY 'secret';

 

(Replace "secret" with your chosen password). When you have specified the database connection parameters in flex.bi then a flexbi_private database will be created. Later when additional flex.bi accounts will be created then the data from each account will be stored in separate databases with names flexbi_jira_dwh_N (where N is account ID number).

In addition you should download the MySQL JDBC driver and copy the included mysql-connector-java-*.jar to flexbi_private/lib directory (MySQL JDBC driver is not included in Private flex.bi distribution due to GPL license restrictions).

Please also tune the MySQL memory settings to speed up both data import and data queries. The following my.cnf settings are recommended:

 

Code Block
innodb_buffer_pool_size = 1024M
innodb_log_file_size = 256M
query_cache_size= 16M
query_cache_type = 1
 

The parameter innodb_buffer_pool_size will specify how much database data MySQL can store in the memory - adjust it to your available server memory (the more data MySQL will store in the memory the less disk input/output operations will be performed). If you change innodb_log_file_size then it will require that you delete existing MySQL log files before starting the MySQL server.

Panel

PostgreSQL

You need to create a separate user flexbi_private with database creation rights for flex.bi:

...

Code Block
CREATE ROLE flexbi_private

...

 PASSWORD 'secret'

...

 LOGIN CREATEDB;

...

If you do not want to add the CREATEDB role to the flexbi_private user then manually create the flexbi_private database with flexbi_private user as the owner.

Each new flex.bi account will store data in a new flexbi_jira_dwh_N schema (where N is account ID number) in the same database.

Please tune PostgreSQL memory parameters. The following postgresql.conf settings are recommended:

 

...

Code Block
shared_buffers = 1024MB

...

 


wal_buffers = 32MB

 

The parameter shared_buffers will specify how much database data PostgreSQL can store in the memory - adjust it to your available server memory (the more data PostgreSQL will store in the memory the less disk input/output operations will be performed). The parameter wal_buffers affects the performance of writing transaction logs to disk.

 

 

Panel

Microsoft SQL Server

Create a MS SQL Server user flexbi_private – if you use SQL Server Management Studio then select SQL Server authentication and uncheck Enforce password policy. In addition from Server Roles select dbcreator (to allow the creation of new databases) or manually create the flexbi_private database with flexbi_private user as the owner.

Each new flex.bi account will store data in a new flexbi_jira_dwh_N schema (where N is account ID number) in the same database.

Oracle

Create an Oracle database user flexbi_private:

...

Code Block
CREATE USER flexbi_private IDENTIFIED BY secret DEFAULT TABLESPACE users;

...


GRANT CONNECT, RESOURCE TO flexbi_private;

...

In this configuration all flex.bi data will be stored in one flexbi_private schema.

Start application

On Mac OS X and Linux start the application with the bin/start.sh shell script. Please review the bin/start.sh script and if necessary customise it (e.g. increase Java memory parameters in the JAVA_OPTS environment variable).

...