Setting Up Repositories and Autoupdate Using File

The setup up can be executed on installing Foresight Analytics Platform or on starting the Tuner.exe file:

where: tuner.xml is the name of the XML file, containing information about repository properties and autoupdate options.

XML File Structure

To create an XML file, open a standard text editor. An XML file must have the following structure (example):

The example provides settings for the SQLite driver. Depending on the selected driver type, setup for some sections will differ:

<?xml version="1.0" encoding="utf-8"?>

<Configuration><Metabases>
<Metabase Driver="ORCL8" Package="STANDARDSECURITYPACKAGE" DebugMode="1" Name="Oracle Repository" Ident="OracleRepository">
<LogonData Server="OracleServer" Scheme="OracleScheme" />
</Metabase>
</Metabases>
</Configuration>

<?xml version="1.0" encoding="utf-8"?>

<Configuration><Metabases>
<Metabase Driver="MSSQL2012" Package="STANDARDSECURITYPACKAGE" DebugMode="1" Name="MSSQL Repository" Ident="MSSQLRepository">
<LogonData Server="MSSQLSERVER" Database="MSSQLDB" />
</Metabase>
</Metabases>
</Configuration>

<?xml version="1.0" encoding="utf-8"?>

<Configuration><Metabases>
<Metabase Driver="TRDT" Package="STANDARDSECURITYPACKAGE" DebugMode="1" Name="Teradata Repository" Ident="TeradataRepository">
<LogonData Server="TRDTSERVER" Database="TRDTDB" />
</Metabase>
</Metabases>
</Configuration>

<?xml version="1.0" encoding="utf-8"?>

<Configuration><Metabases>
<Metabase Driver="POSTGRES" Package="STANDARDSECURITYPACKAGE" DebugMode="1" Name="POSTGRES Repository" Ident="POSTGRESRepository">
<LogonData Server="POSTGRES" Database="POSTGRES" />
</Metabase>
</Metabases>
</Configuration>

Parameter Values

Section

Attributes

Driver. Select driver identifier. The driver identifier depends on the DBMS type, where a repository is created.

The list of available DBMS and driver identifiers that can be used as a repository basis is given in the Supported DBMS subsection.

Package. Standard security package of Foresight Analytics Platform:

STANDARDSECURITYPACKAGE.

Authentication. Select authentication type:

1. Password.
2. Integrated domain.
3. Role.
4. Domain.

DebugMode. Select assembly caching type:

0. No caching.
1. Assembly caching.

Name. Enter the repository name.

Ident. Enter the repository identifier.

Scope. Select, which registry key is used to add repository connection settings:

LM. [HKEY_LOCAL_MACHINE] - repository is set up for all users.
CU. [HKEY_CURRENT_USER] - repository is set up for the current user.

NOTE. The Scope parameter is optional. The default value is CU.

Section

Attributes

Server. Server name. The attribute is relevant for Oracle, Microsoft SQL Server, MSSQL2012, MSSQL2012ODBC, PostgreSQL, Teradata DBMS.

FileName. Database file name. The attribute is relevant for SQLite DBMS.

Scheme. Repository schema name. The attribute is relevant for Oracle DBMS.

Database. Repository schema name. The attribute is relevant for Microsoft SQL Server, MSSQL2012, MSSQL2012ODBC, PostgreSQL, Teradata DBMS.

Metabase. Repository schema identifier. The attribute is relevant for WSF DBMS.

EndPoint. Security server or BI server address. The attribute is relevant for WSF DBMS.

The list of available DBMS that can be used as a repository basis is given in the Supported DBMS subsection.

Section

Attributes

Profile. It determines the profile for recording autoupdate settings. Profile path in the registry:

In 32-bit Windows OS: [HKEY_CURRENT_USER\SOFTWARE\Wow6432Node\Foresight\Foresight Analytics Platform\9.0\AutoUpdate\Profiles\<Profile name>].
In 64-bit Windows OS: [HKEY_CURRENT_USER\SOFTWARE\Foresight\Foresight Analytics Platform\9.0\AutoUpdate\Profiles\<Profile name>]
By default, profile name matches with to version number, for example 9.2.

SourceType. The update source:

Path. Disk folder.
Db. Database server.

Update. Autoupdate:

Ask. Request for permission before starting the update.
""(empty). Do not update.
Always. Update automatically (no request).

Db. Database server parameters with updates. It looks as follows:

DB:LABEL;SERVER@,

where:

Db. DBMS type: ORACLE or MSSQL.
LABEL. Update label.
SERVER. Database server.

Source. The path to the network update directory.

Section

Attributes

Visible:

0. Do not display a standard image in the login dialog box.
1. Display a standard image in the login dialog box.

NOTE. Image can be disabled in the login dialog box by determining appropriate settings in the registry. The image and icon in the login dialog box can also be changed.

Section

Attributes

Name. Variable name.

Args. Variable value.

Section

Attributes

<Login>

VisibleAdvanced:

0. Do not display the Settings button.
1. Display the Settings button.

NOTE. The Settings button can be hidden by determining appropriate settings in the registry.

To determine information settings for the About dialog box, use the <AboutWindow> section in the nested sections.

Section	Attributes
<App>	Name. Program name. Version. Program version.
<Info>	Address. Address. Phone. Telephone. Fax. Fax. Email. Email address. Website. Website URL. Title. Column header containing information about technical support.
<Copyright>	Value. Copyright.

NOTE. The license number cannot be changed or hidden.

To cancel specified settings and display standard information in the About dialog box, delete the About chapter in the registry:

In 32-bit Windows OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Foresight\Foresight Analytics Platform\9.0\About].
In 64-bit Windows OS: [HKEY_LOCAL_MACHINE\SOFTWARE\Foresight\Foresight Analytics Platform\9.0\About].

After setting up the system using the XML file given above, the About dialog box looks as follows:

Section	Attributes
<Exception>	EMail. Email address inserted into the recipient field on sending platform error messages.