The installation and configuration of Fabric's BI includes the following steps:
Installation Recommendations
Have 3 separate BI installations - one each for Dev, QA and Production environments.
The recommended Storage Management DB type is PostgreSQL.
Due to performance considerations, it is recommended to install the PostgreSQL on a different from BI server host.
PostgreSQL version 12 and below must be installed because the recommended driver (DB provider) is Devart.Data.PostgreSql which is not supported by PostgreSQL 13 and higher versions.
The BI solution uses the Fabric config.ini to retrieve information about the BI host and port and the Storage Management DB connection details.
Update the [bi] section parameters of the Fabric config.ini as follows:
Important: the Admin module of BI has a Storage Management page which displays the default settings. These settings are not applicable in the BI solution, since Fabric retrieves the Storage Management connection details from the config.ini!
[bi]
## BI server host
#BI_HOST=
## BI Storage Management host, empty for SQLite
#STORAGE_MGMT_HOST=
## BI Storage Management Listener port
#BI_PORT=5432
## BI Storage Management name, default = StorageMgmt for both SQLite and PostgreSQL
#STORAGE_MGMT_DB_NAME=StorageMgmt
## BI Storage Management type, the values are SQLite, PostgreSQL
#STORAGE_MGMT_DB_TYPE=SQLite
## BI Storage Management provider, the values are SQLite (for SQLite), Devart.Data.PostgreSql (for PostgreSQL)
#STORAGE_MGMT_DB_PROVIDER=SQLite
## BI Storage Management user, empty for SQLite
#STORAGE_MGMT_DB_USER=
## BI Storage Management password, empty for SQLite
#STORAGE_MGMT_DB_PASSWORD=
## BI Storage Management table prefix
#TABLE_PREFIX=
## BI REST key
#BI_REST_KEY=~encs0~lH54NQEhYq/LCeBX+jQYCw==
Upon the completion of installation and configuration setup, deploy the Fabric project.
Note that Full Deploy must be performed rather than Soft Deploy. To deactivate Soft Deploy if it was activated in the Fabric Studio, go to the User Preferences > Server Configuration window and uncheck the Soft Deploy checkbox.
Now any user accessing this project has the default read-only access to the project's reports within the Designer. To setup different access permissions per Fabric role, refer to the Access Permissions Setup article which explains how to do this.
It is possible to use the same BI host and the same Storage Management DB (even the same table prefix) by different Fabric Projects. Meaning both Fabric Projects have the same settings in the [bi] section of config.ini. In this case, upon deploying each project a folder is created in the Storage Management DB metadata and it gives the default read-only access to the users defined under each project. When logging into the Web Framework > BI, the project's users will see only the current project's folder and not the other one.
For example, two projects are deployed on the same Storage Management DB and use the same table prefix: Customer360 and TDM.
The installation and configuration of Fabric's BI includes the following steps:
Installation Recommendations
Have 3 separate BI installations - one each for Dev, QA and Production environments.
The recommended Storage Management DB type is PostgreSQL.
Due to performance considerations, it is recommended to install the PostgreSQL on a different from BI server host.
PostgreSQL version 12 and below must be installed because the recommended driver (DB provider) is Devart.Data.PostgreSql which is not supported by PostgreSQL 13 and higher versions.
The BI solution uses the Fabric config.ini to retrieve information about the BI host and port and the Storage Management DB connection details.
Update the [bi] section parameters of the Fabric config.ini as follows:
Important: the Admin module of BI has a Storage Management page which displays the default settings. These settings are not applicable in the BI solution, since Fabric retrieves the Storage Management connection details from the config.ini!
[bi]
## BI server host
#BI_HOST=
## BI Storage Management host, empty for SQLite
#STORAGE_MGMT_HOST=
## BI Storage Management Listener port
#BI_PORT=5432
## BI Storage Management name, default = StorageMgmt for both SQLite and PostgreSQL
#STORAGE_MGMT_DB_NAME=StorageMgmt
## BI Storage Management type, the values are SQLite, PostgreSQL
#STORAGE_MGMT_DB_TYPE=SQLite
## BI Storage Management provider, the values are SQLite (for SQLite), Devart.Data.PostgreSql (for PostgreSQL)
#STORAGE_MGMT_DB_PROVIDER=SQLite
## BI Storage Management user, empty for SQLite
#STORAGE_MGMT_DB_USER=
## BI Storage Management password, empty for SQLite
#STORAGE_MGMT_DB_PASSWORD=
## BI Storage Management table prefix
#TABLE_PREFIX=
## BI REST key
#BI_REST_KEY=~encs0~lH54NQEhYq/LCeBX+jQYCw==
Upon the completion of installation and configuration setup, deploy the Fabric project.
Note that Full Deploy must be performed rather than Soft Deploy. To deactivate Soft Deploy if it was activated in the Fabric Studio, go to the User Preferences > Server Configuration window and uncheck the Soft Deploy checkbox.
Now any user accessing this project has the default read-only access to the project's reports within the Designer. To setup different access permissions per Fabric role, refer to the Access Permissions Setup article which explains how to do this.
It is possible to use the same BI host and the same Storage Management DB (even the same table prefix) by different Fabric Projects. Meaning both Fabric Projects have the same settings in the [bi] section of config.ini. In this case, upon deploying each project a folder is created in the Storage Management DB metadata and it gives the default read-only access to the users defined under each project. When logging into the Web Framework > BI, the project's users will see only the current project's folder and not the other one.
For example, two projects are deployed on the same Storage Management DB and use the same table prefix: Customer360 and TDM.