All documentation
  • Introduction
  • Connecting to data source
    1. Supported data sources
    2. Connecting to other data sources
  • Browser compatibility
  • Documentation for older versions
  • Data sources guide

    This tutorial describes how to connect Flexmonster Data Server used as a Windows/Unix service to your data.

    Prerequisites

    To complete this walkthrough, you should have the Data Server as a service and Flexmonster Admin Panel installed on your machine. If they are not already installed, complete the following guide: Installing Flexmonster Data Server as a Windows/Unix service.

    You can now connect the Data Server to your data source. Server configurations vary depending on the data source type: database, JSON, or CSV.

    Connecting to databases

    Flexmonster Data Server supports the following databases: MySQL, MariaDB, Microsoft SQL Server, PostgreSQL, Oracle, and Microsoft Azure SQL.

    To connect to a database with Flexmonster Data Server, open Flexmonster Admin Panel and go to Indexes > Add New Index. Then fill in the Name, Type, Database type, Connection string, and Query fields:

    Sample configuration of a MySQL index

    "index-database" is a dataset identifier. It will be used to configure the data source on the client side.

    When the index configuration is complete, click Create. The index will be automatically added to your index pool.

    Learn more about connecting to a database with the Data Server in our detailed guides:

    To see how the connection with Flexmonster Data Server is configured in the component, refer to the Configuring the report section.

    Connecting to JSON

    To connect to JSON with Flexmonster Data Server, open Flexmonster Admin Panel and go to Indexes > Add New Index. Then fill in the Name, Type, and Path to file fields:

    Sample configuration of a JSON index

    "index-json" is a dataset identifier. It will be used to configure the data source on the client side.

    When the index configuration is complete, click Create. The index will be automatically added to your index pool.

    Learn more about connecting to JSON with the Data Server in our detailed guide: Connecting to JSON using Flexmonster Data Server.

    To see how the connection with Flexmonster Data Server is configured in the component, refer to the Configuring the report section.

    Connecting to CSV

    To connect to CSV with Flexmonster Data Server, open Flexmonster Admin Panel and go to Indexes > Add New Index. Then fill in the Name, Type, and Path to file fields:

    Sample configuration of a CSV index

    "index-csv" is a dataset identifier. It will be used to configure the data source on the client side.

    When the index configuration is complete, click Create. The index will be automatically added to your index pool.

    Learn more about connecting to CSV with the Data Server in our detailed guide: Connecting to CSV using Flexmonster Data Server.

    To see how the connection with Flexmonster Data Server is configured in the component, refer to the Configuring the report section.

    Configuring the report

    On the client side, the report should be configured as follows:

    new Flexmonster({
      container: "pivotContainer",
      componentFolder: "node_modules/flexmonster/",
      report: {
        dataSource: {
          type: "api",
          url: "http://localhost:9500",
          index: "index-json"
        }
      }
    }); 

    Note The index must match the name of the index defined when configuring Flexmonster Data Server (e.g., "index‑json").

    Display non-Latin characters correctly

    If your data contains non-Latin characters, ensure you have set UTF-8 encoding for your data and page so the data is displayed correctly in the component.

    About response caching

    When Flexmonster Pivot requests data, Flexmonster Data Server sends a response and then caches it. If the component sends the same request again, the server responds with the data from its cache.

    The Data Server’s cache has a limit. When the cache does not have enough space for a new response, the Data Server deletes one of the previously cached responses. You can manage the cache size via the Cache size limit configuration.

    The Data Server clears the cache when restarted.

    What’s next?