Dundas BI config file

Contents[Hide]

1. Overview

This article describes the dbi.config file used to define pieces of information needed to start the application. This is initially configured when deploying the application.

The file created is located within your installation folder at:

[Instance Folder]\www\BIWebsite\App_Data\dbi.config

2. Application database connection string

The connection string used by Dundas BI or Managed Dashboards & Reports to connect to its application database is defined in the connectionStrings element:

  <connectionStrings>
    <add 
    name="AppConnectionString" 
    connectionString="Data Source=localhost;Initial Catalog=&quot;Dundas BI Instance1&quot;;User ID=DundasUser;Password=1234"
   />
  </connectionStrings>

If this section is encrypted, it can be decrypted using the dt command line tool. For more information, see Using the dt command line tool.

This can be either a Microsoft SQL Server database or a PostgreSQL database, and connection strings are defined differently for each. For syntax details including available parameters/keywords, see Microsoft Docs for SQL Server or Npgsql for PostgreSQL.

Tip

The warehouse database connection string can be changed from the configuration settings while logged in as an administrator. Its connection string uses the same syntax.

2.1. Application storage type

The ApplicationStorage key should be set to the type of database you are using. Below is an example of how this would look for SQL Server:

<!-- The type of database server hosting the Application database. 
Can be "SqlServer" or "Postgres". -->
<add key="ApplicationStorage" value="SqlServer" />

3. Setting the temp data path

The temp data path is the path where any temporary application data is saved. If it is not set or set to empty string, the App_Data path is used. The following folders would exist under the folder defined by this setting:

BLOBFiles
Logs
TempLib
ViewThumbnails
FileDelivery
DownloadStaging

<!-- The path where any temporary application data is saved. 
If not set or set to empty string, the App_Data path is used.". -->
<add key="TempDataPath" value="" />

4. Recycle the application pool

For changes to this file to take effect, you need to recycle the application pool in IIS or the website service on Linux.

5. Complete example

The following is a complete example of a dbi.config file's contents, including some example keys provided as comments for reference:

<?xml version="1.0"?>
<configuration>
  <connectionStrings>
    <!-- SQL SERVER -->
    <add name="AppConnectionString" connectionString="Data Source=localhost; Initial Catalog=&quot;Dundas BI Instance1&quot;;User ID=DundasUser;Password=1234" />

    <!-- PostgreSQL -->
    <!--<add name="AppConnectionString" connectionString="Host=localhost;Port=5432;Database=&quot;Dundas BI Instance1&quot;;User ID=DundasBIUser;Password=1234;" />-->
  </connectionStrings>
  <appSettings>
    <!-- The type of database server hosting the Application database. Can be "SqlServer" or "Postgres". -->
    <add key="ApplicationStorage" value="SqlServer" />
    
    <!-- The path where any temporary application data is saved. If not set or set to empty string, the App_Data path is used.". -->
    <!--<add key="TempDataPath" value="" />-->
  </appSettings>
</configuration>

Dundas BI, Managed Dashboards & Reports Support