1. API reference
  2. Welcome
    1. Component overview
    2. Quick start
    3. System requirements
    4. Troubleshooting
    5. Managing license keys
  3. Connecting to Data Source
    1. JSON
      1. Connecting to JSON
      2. Connecting to JSON using the Data Compressor
      3. Data types in JSON
    2. CSV
      1. Connecting to CSV
      2. Connecting to CSV using the Data Compressor
      3. Data types in CSV
    3. Database
      1. Connecting to SQL databases
      2. Connecting to other databases
      3. Connecting to a database with Node.js
      4. Connecting to a database with .NET
      5. Connecting to a database with .NET Core
      6. Connecting to a database with Java
      7. Connecting to a database with PHP
    4. Microsoft Analysis Services
      1. Connecting to Microsoft Analysis Services
      2. Getting started with the Accelerator
      3. Installing the Accelerator as a Windows service
      4. Referring the Accelerator as a DLL
      5. Configuring the authentication process
      6. Configuring a secure HTTPS connection
      7. Troubleshooting
    5. Pentaho Mondrian
      1. Connecting to Pentaho Mondrian
      2. Getting started with the Accelerator
      3. Configuring Mondrian roles
      4. Configuring username/password protection
      5. Сonfiguring a secure HTTPS connection
      6. Troubleshooting
    6. Connecting to Elasticsearch
  4. Security
    1. Security in Flexmonster
    2. Security aspects when connecting to an OLAP cube
      1. The data transfer process
      2. Data security
      3. Data access management
    3. Security aspects when connecting to a database
      1. The data transfer process
      2. Data access management
  5. Configuring report
    1. What is a report
    2. Data source
    3. Slice
    4. Options
    5. Number formatting
    6. Conditional formatting
    7. Set report to the component
    8. Get report from the component
    9. Date and time formatting
    10. Configuring global options
    11. Export and print
    12. Calculated values
    13. Custom sorting
  6. Integration with frameworks
    1. Available tutorials
    2. Integration with AngularJS (v1.x)
    3. Integration with Angular
    4. Integration with React
    5. Integration with Webpack
    6. Integration with ASP.NET
    7. Integration with jQuery
    8. Integration with JSP
    9. Integration with TypeScript
    10. Integration with RequireJS
    11. Integration with PhoneGap
  7. Integration with charts
    1. Integration with Highcharts
    2. Integration with Google Charts
    3. Integration with FusionCharts
    4. Integration with any charting library
  8. Customizing
    1. Customizing toolbar
    2. Customizing appearance
    3. Customizing context menu
    4. Localizing component
  9. Updating to the latest version
    1. Updating to the latest version
    2. Release notes
    3. Migration guide from 2.6 to 2.7
    4. Migration guide from 2.5 to 2.6
    5. Migration guide from 2.4 to 2.5
    6. Migration guide from 2.3 to 2.4
    7. Migration guide from 2.2 to 2.3
    8. Documentation for older versions
Table of contents

The data transfer process

One of the most popular questions we get is how can the data from the OLAP cube be transferred to Flexmonster Pivot? Flexmonster Accelerator serves as an additional server-side layer that helps to restrict external access to the database. When connecting to the data source inside the pivot table, the URL to the Accelerator is used instead of the SSAS server URL. Flexmonster Pivot sends the requests to the Accelerator, then Flexmonster Accelerator communicates with the SSAS server and gets the necessary data. This data is sent back to the client from the Accelerator. The flowchart below shows the process:

Accelerator

Data transferring security

To ensure server-side data security, the Accelerator doesn’t accept requests from any other web applications, only from Flexmonster Pivot. Is it not possible to send an HTTP request directly to Flexmonster Accelerator without using Flexmonster Pivot. The Accelerator also doesn’t accept a response/request that was changed during the communication process. Each response/request contains a checksum for the package to ensure that it was not changed.

The only requirement is the necessity to open an additional port on the server for the Accelerator. This is not a specific requirement for our component but a strong restriction imposed by the browser’s security. It is absolutely necessary to use CORS and an extra port and there is no workaround. Otherwise, the clients’ browsers will not allow communication with the server.