Setting Up Repository Connection

To set up repository connection and to work with it, use the Set Up Repository Connection dialog box or determine platform settings from file in the desktop application.

To open the dialog box

Set the parameters:

Set additional DBMS parameters depending on the selected driver type:

NOTE. When setting up repository connection, make sure that server IP address or DNS server name matches with the server specified on creating a service user on each client computer.

In the desktop application, additional connection parameters to SQLite and WEB Service are available:

NOTE. To use the Integrated Domain or Domain authentication type, first, add domain users or domain groups in the security manager.

The parameter is available for all DMS types, except for SQLite.

NOTE. After the checkbox is selected, database objects will be available only if their exact physical names are specified.

If the checkbox is deselected, the repository name, object identifiers and their fields in DBMS are converted to lower case while the platform addresses the server.

In the desktop application this parameters is contained in the Additional Parameters dialog box.

NOTE. The default repository can be only one. If another default repository is already used, after the checkbox is selected, the default repository will be changed for the current connected repository.

If the default repository is not set, on starting Foresight Analytics Platform, the login dialog box will display the latest connected repository. If web application cache was cleared, the login dialog box will display the repository specified in the PP.xml file in the <metabase> section.

In the desktop application a default repository is selected in the Parameters dialog box.

After executing the operations the repository connection is set up.

To save settings, click the Apply button in the web application or the OK button in the desktop application.

Additional Parameters in the Desktop Application

The desktop application contains additional parameters to set up repository connection:

If the checkbox is selected, the assemblies created on forms and units compilation are compiled on the local drive and not changed on the server.

If the checkbox is deselected, on starting the assemblies created on forms and units compilation, the system checks if assemblies on database server and local drive match If versions match, Foresight Analytics Platform continues working with assemblies on the local drive. If versions mismatch or there are no assemblies on the local drive, the database server compiles new assemblies and copies them to a local drive. Then Foresight Analytics Platform continues working with the assemblies on the local drive.

IMPORTANT. Caching of system metadata tables is allowed only in the production version. When caching is used, data in system metadata tables must not be changed.

Each startup of BI server process is accompanied with creating a cache corresponding to a specific process. Cache is reset only when this process finishes. Cache is local for BI server and is global for active sessions within the running BI server process.

If a BI server cluster is used, cache is created for each work node of cluster and is not synchronized with each other.

NOTE. To set up system metadata table caching, see to the technical support by sending an email at support@fsight.ru or via technical support services that are available after registration at the website.

Features of Lazy Loading of Repository Object Descriptors

If the user has limited access permissions on Foresight Analytics Platform, and the Only for Me checkbox is selected, new repository settings are not saved. If the Anyone Who Uses This Computer checkbox is selected, the user will be denied access.

Clicking the Advanced button opens the Additional Parameters dialog box. Parameters depend on the selected driver type used for connection:

Set the parameters:

IMPORTANT. Note that format should be the same as the substitution case.

For example:

$User@$Domain.COM

In this format, user name looks as follows: IVANOV@EXAMPLE.COM.

$Domain@$User

In this format, user name looks as follows: EXAMPLE@IVANOV.

$User@$FullDomain

In this format, user name looks as follows: IVANOV@EXAMPLE.WORLD.COM.

$FullDomainUser

In this format, user name looks as follows: IVANOV@EXAMPLE.WORLD.COM.

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

Set the parameters:

  • DBMS is Case Sensitive. If required, select the checkbox to work with the repository, objects and their fields in DBMS having different character case in their physical names.

NOTE. After the checkbox is selected, database objects will be available only if their exact physical names are specified.

If the checkbox is deselected, the repository name, object identifiers and their fields in DBMS are converted to lower case while the platform addresses the server.

Connection parameters specified for ODBC driver are stored in the system global variable that is automatically added to connection string when creating a database and another repository connection attribute.

When the Scheduler.xml configuration file is automatically created for task scheduler the specified connection parameters will be written in the ODBCPARAMS.

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

Set the parameters:

  • DBMS is Case Sensitive. If required, select the checkbox to work with the repository, objects and their fields in DBMS having different character case in their physical names.

NOTE. After the checkbox is selected, database objects will be available only if their exact physical names are specified.

If the checkbox is deselected, the repository name, object identifiers and their fields in DBMS are converted to lower case while the platform addresses the server.

When the Scheduler.xml configuration file is automatically created for task scheduler the specified connection parameters will be written in the ODBCPARAMS.

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

Set the parameters:

IMPORTANT. Note that format case should be the same as the substitution case.

For example:

$User@$Domain.COM

In this format, user name looks as follows: IVANOV@EXAMPLE.COM.

$Domain@$User

In this format, user name looks as follows: EXAMPLE@IVANOV.

$User@$FullDomain

In this format, user name looks as follows: IVANOV@EXAMPLE.WORLD.COM.

$FullDomainUser

In this format, user name looks as follows: IVANOV@EXAMPLE.WORLD.COM.

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

Set the parameters:

  • DBMS is Case Sensitive. If required, select the checkbox to work with the repository, objects and their fields in DBMS having different character case in their physical names.

NOTE. After the checkbox is selected, database objects will be available only if their exact physical names are specified.

If the checkbox is deselected, the repository name, object identifiers and their fields in DBMS are converted to lower case while the platform addresses the server.

NOTE. Parameters in the Authentication group can be set only if the Domain or Integrated Domain authentication type is selected on the Set Up Repository Connection page.

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

Set the parameters:

One can select one of the radio buttons:

NOTE. If language settings are not determined for specified objects and names, default repository language is used.

See also:

Setting Up Repository Access | Setting Up Repositories List | Foresight Analytics Platform Authentication