System Configurations and Their Working Principles

Foresight Analytics Platform can work in various configurations by using separate servers to focus on business logic core, security core or user interface.

See below basic configurations. In order to increase fault tolerance in each configuration can implement BI servers cluster.

Conventions

The configurations given below use the following legend:

Business logic core provides work logic of Foresight Analytics Platform, logic of interaction between objects, loads, processes, calculates and saves data.

Security core executes administration functions and information security functions.

User interface ensures interaction of the user with Foresight Analytics Platform.

Web service is used to interact between the web application and system servers via http/https requests.

Interaction between configuration elements on the level of Foresight Analytics Platform.

Interaction between configuration elements on user level in manual mode.

Standard Configuration

Standard configuration of Foresight Analytics Platform includes the use of the desktop and web applications:

On using the desktop application:

  1. A user interacts with desktop application interface.

  2. The desktop application sends requests to license server, as a result the desktop application determines access to the functionality.

  3. The desktop application interacts with database via the DBMS driver using business logic core.

If the web application is used, business logic and security functions are performed by BI server, the user interface is presented by the web application:

  1. The user interacts with web application interface.

  2. The web application interacts with web server and BI server via the PP.SOM.Som access point. The scheme shows general interaction, a detailed scheme is given in the Installing and Setting Up Web Application Back End section.

  3. BI server sends requests to license server, as a result BI server determines access to the functionality.

  4. The BI server interacts with database via the DBMS driver using business logic core.

When executing scheduled resource-intensive tasks:

  1. The user sets up scheduled tasks in the desktop application, sends the settings to the application server and starts theTask Scheduler tool.

  2. Application server sends requests to license server, as a result application server determines access to the functionality.

  3. The application server executes scheduled resource-intensive tasks and interacts with database via the DBMS driver using business logic core.

NOTE. Application server can be combined with BI server.

BI server and web application installation is described in the articles: Installing Web Application on Windows OS and Installing Web Application on Linux OS.

Configuration with Security Server

Security core functions can be moved to security server:

On using the desktop application:

  1. A user interacts with desktop application interface.

  2. The desktop application sends requests to license server, as a result the desktop application determines access to the functionality.

  3. Desktop application via the PP.SOM.SomSec access point interacts with security server.

  4. The security server sends a request via DBMS driver, gets data and returns it to the business logic core.

If the web application is used, business logic function is performed by BI server, the user interface is presented by the web application:

  1. A user interacts with web application interface.

  2. The web application interacts with web server and BI server via the PP.SOM.Som access point. The scheme shows general interaction, a detailed scheme is given in the Installing and Setting Up Web Application Back End section.

  3. BI server sends requests to license server, as a result BI server determines access to the functionality.

  4. BI server interacts with security server via the PP.SOM.SomSec access point.

  5. The security server interacts:

When executing scheduled resource-intensive tasks:

  1. The user sets up scheduled tasks in the desktop application, sends the settings to the application server and starts theTask Scheduler tool.

  2. Application server sends requests to license server, as a result application server determines access to the functionality.

  3. The application server via the access point PP.SOM.SomSec interacts with the security server.

  4. The security server sends a request via DBMS driver, gets data and returns it to the business logic core.

  5. The application server executes scheduled resource-intensive tasks.

NOTE. Application server can be combined with BI server.

BI server and web application installation is described in the articles: Installing Web Application on Windows OS and Installing Web Application on Linux OS.

NOTE. On working via the security server, the number of available operations is limited: operations are available for working with repository, working with object metadata and for working with SQL objects.