Version 2021

Preview Features

Preview features are early versions of features. They are not ready for full release, but are functional enough for you to try out and experiment with. The official versions of preview features are included in subsequent releases.

Metadata JDBC Connection

Starting in MicroStrategy 2021 Update 5, the metadata, Distribution Services, 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, Distribution Service, and History List repositories with a JDBC connection.

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

You must manually update the response.ini file 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 metadata 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, and Enterprise Manager repositories are created. The table below lists the available parameters and the functionality of available options for each parameter.

Options

Description

[Repository]

This section configures the metadata repository and statistics tables. 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:

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:

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 szerver 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 definition. 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:

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 upgradethe Intelligence server definition. 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 select to update multiple projects by separating projects by the "\" character.

For example, UpgradeProjects=Project1\Project2.

MDPwd Defines the password to log into the metadata database.
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 database.

DSNPwd= Defines the password to log into the metadata database.

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:

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 database.

HLUserPwd=

Defines the password to log into the metadata database.

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 upgradethe 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 metadata repository. Only the PostgresSQL database is supported.

For example:

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 History List repository. This is the data source that stores the History List.

HLUser= Defines the username to log into the History List database.
HLPwd

Defines the password to log into the History List database.

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 for upgrade the History List reopository, 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