JDBC Connection with PostgreSQL

Metadata JDBC Connection

Starting in MicroStrategy ONE (June 2024), Platform Analytics Warehouse supports JDBC connections with PostgreSQL.

Starting in MicroStrategy 2021 Update 5, metadata and History List repositories support JDBC connections with PostgreSQL.

A feature flag and metadata upgrade are not required. This feature is available upon a successful Intelligence Server upgrade.

Only the PostgreSQL database has been certified for the metadata, History List, and Platform Analytics Warehouse repositories with a JDBC connection.

Only silent mode via the Configuration wizard is supported for the configuration.

You must manually update response.ini in a text editor.

Create a Response File

See Configuring MicroStrategy with a Response File to create a response file. Then, refer to the following sections to see the available parameters for establishing a JDBC connection with PostgreSQL.

Create the Metadata, History List, and Statistics Repositories

The response file parameters within the [Repository] section define how the metadata, History List, and statistics repositories are created. The table below lists the available parameters and the functionality of available options for each parameter.

Options	Description
[Repository]	This section creates metadata, History List, and statistics repositories. You can have more than one `[Repository]` section. Additional repository sections can be included as `[Repository1]`, `[Repository2]`, and so on.
ConnectionType=	The connection type for the metadata repository. JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
JDBCConnString=	The JDBC connection string for the metadata repository. Only the PostgresSQL database is supported. For example: Copy `JDBC;DRIVER={com.microstrategy.jdbc.postgresql.PostgreSQLDriver};URL={jdbc:microstrategy:postgresql://DataBase_Server:5432;DATABASENAME=Database_Name;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;};MathedJarFile=mypostgresql.jar;` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.
ConnectionTypeHist=	The connection type for the History List repository. JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
JDBCConnStringHist=	The JDBC connection string for the History List repository. Only the PostgresSQL database is supported. For example: Copy `JDBC;DRIVER={com.microstrategy.jdbc.postgresql.PostgreSQLDriver};URL={jdbc:microstrategy:postgresql://DataBase_Server:5432;DATABASENAME=Database_Name;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;};MathedJarFile=mypostgresql.jar;` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.

Set Up the MicroStrategy Intelligence Server

The response file parameters within the [Server] section configures an Intelligence server definition. The table below lists the available parameters and the functionality of available options for each parameter.

Options	Description
[Server]	In this section you can configure the Intelligence Server. You can have more than one `[Server]` section. Additional server sections can be included as `[Server1]`, `[Server2]`, and so on.
ConnectionType=	The connection type for the metadata repository. JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
JDBCConnString=	The JDBC connection string for the metadata repository. Only the PostgresSQL database is supported. For example: Copy `JDBC;DRIVER={com.microstrategy.jdbc.postgresql.PostgreSQLDriver};URL={jdbc:microstrategy:postgresql://DataBase_Server:5432;DATABASENAME=Database_Name;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;};MathedJarFile=mypostgresql.jar;` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.

Upgrade the Intelligence Server Components

The response file parameters within the [Server] section upgrades the Intelligence Server components. The table below lists the available parameters and the functionality of available options for each parameter.

Options	Description
[UpgradeServer]	In this section you can upgrade the Intelligence Server. You can have more than one `[UpgradeServer]` section. Additional server sections can be included as `[UpgradeServer1]`, `[UpgradeServer2]`, and so on.
UpgradeServer=	Defines whether the MicroStrategy Intelligence Server is upgraded, as determined by the following values: `1`: Upgrade MicroStrategy Intelligence Server `0`: Does not Upgrade MicroStrategy Intelligence Server
UpgradeMD=	Defines whether the metadata is upgraded, as determined by the following values: `1`: Upgrade metadata `0`: Does not Upgrade metadata
MigrateHL=	Defines whether to migrate the History List, as determined by the following values: `1`: migrate the history list `0`: Does not migrate the history list
UpgradeProjects=	Defines projects to be updated when the Intelligence Server is updated. You can update multiple projects by separating projects by the "`\`" character. For example, `UpgradeProjects=Project1\Project2`.
MDPwd	Defines the password to log into the metadata repository.
HLConnectionType=	The connection type for the History List repository. JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
DSNUser=	Defines the username to log into the metadata repository.
DSNPwd=	Defines the password to log into the metadata repository.
EncryptPassword=	Defines whether the password is encrypted in the response file, as determined by the following values: `0`: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. `1`: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior.
HLJDBCConnString=	The JDBC connection string for the metadata repository. Only the PostgresSQL database is supported. For example: Copy `JDBC;DRIVER={com.microstrategy.jdbc.postgresql.PostgreSQLDriver};URL={jdbc:microstrategy:postgresql://DataBase_Server:5432;DATABASENAME=Database_Name;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;};MathedJarFile=mypostgresql.jar;` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.
HLDBInstanceName=	The database instance name of the History List to create.
HLUserName=	Defines the username to log into the metadata repository.
HLUserPwd=	Defines the password to log into the metadata repository.

Upgrading the History List repository

The response file parameters within the [UpgradeHistoryList] section upgrades the History List repository. The table below lists the available parameters and the functionality of available options for each parameter.

Options	Description
[UpgradeHistoryList]	In this section you can upgrade the Intelligence Server definition. You can have more than one `[UpgradeHistoryList]` section. Additional server sections can be included as `[UpgradeHistoryList1]`, `[UpgradeHistoryList2]`, and so on.
HLConnectionType=	The connection type for the History List repository . JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
HLDBCConnString=	The JDBC connection string for the History List repository. Only the PostgresSQL database is supported. For example: Copy `JDBC;DRIVER={com.microstrategy.jdbc.postgresql.PostgreSQLDriver};URL={jdbc:microstrategy:postgresql://DataBase_Server:5432;DATABASENAME=Database_Name;ValidateServerCertificate=false;fetchTWFSasTime=TRUE;};MathedJarFile=mypostgresql.jar;` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.
HLDSN=	Defines the data source name for the History List repository. This is the data source that stores the History List.
HLUser=	Defines the username to log into the History List repository.
HLPwd	Defines the password to log into the History List repository.
HLPrefix=	Defines a prefix for the History List repository tables.
EncryptPassword=	Defines whether the password is encrypted in the response file, as determined by the following values: `0`: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it. `1`: Encrypts the password in the response file, which ensures that your password is secure. This is the default behavior.
CopyContent=	Defines whether to copy the content when upgrading, as determined by the following values: `1`: Copy content `0`: Does not copy content
CompressData=	Defines whether to compress data when upgrading, as determined by the following values: `1`: Compress Data `0`: Does not Compress Data
UpgradeHLPath=	Locates the SQL scripts to upgrade the History List repository, as listed below: Windows (64-bit): `C:\Program Files (x86)\Common Files\MicroStrategy\content_server_db_PostgreSQL.sql` Linux: `/INTELLIGENCE_SERVER_INSTALL_PATH/content_server_db_PostgreSQL.sql`

Creating and Upgrading the Platform Analytics Project

The response file parameters within the [PAProjectHeader] section defines how the Platform Analytics project is created or upgraded. The table below lists the available parameters and the functionality of available options for each parameter.

Options	Description
[PAProjectHeader]	In this section you can create or upgrade the Platform Analytics project.
PAProject=	Defines whether to upgrade the Platform Analytics project, as determined by the following values: `1`: Upgrade the Platform Analytics project `0`: Does not upgrade the Platform Analytics project
PAProjectEncryptPwd=	Defines whether the password is encrypted in the response file, as determined by the following values: `1`: Encrypts the password in the response file, which ensure that you password is secure. This is the default behavior. `0`: The password is not encrypted in the response file, which enables you to modify the password in the response file later using a text editor. You can then distribute the response file to multiple users with various login and password credentials. However, be aware that this can compromise your database security if you do not remove the password from the response file before distributing it.
PAProjectDSSUser=	Defines the username to log into the Intelligence Server.
PAProjectDSSPwd=	Defines the password to log into the Intelligence Server.
PAProjectDSNName=	Defines the data source name for the Platform Analytics Warehouse.
PAProjectDSNUserName=	Defines the username to log into the Platform Analytics Warehouse.
PAProjectDSNUserPwd=	Defines the password to log into the Platform Analytics Warehouse.
PAProjectDSNPrefix=	Defines a prefix for the Platform Analytics Warehouse.
PAProjectConnectionType=	The connection type for the Platform Analytics Warehouse: JDBC or jdbc: represents a JDBC connection Other Value: represents an ODBC connection
PAProjectConnString=	The JDBC connection string for the Platform Analytics Warehouse. Only the PostgreSQL database is supported. For example: Copy `JDBC;DRIVER={org.postgresql.Driver};URL={jdbc:postgresql://localhost:5432/platform_analytics_wh};` Use ‘`}}`’ for '`}`' if the database name or database server name includes the "`}`" special character.