☝️Small business or a startup? See if you qualify for our special offer.
+
All documentation
  • Introduction
  • Connecting to data source
    1. Supported data sources
    2. Connecting to other data sources
  • Browser compatibility
  • Documentation for older versions
  • Installing the Accelerator as a Windows Service

    This guide describes how to install Flexmonster Accelerator as a Windows Service.

    The main benefits of running the Accelerator as a Windows service are:

    • It runs in the background and out of sight.
    • It starts automatically on Windows startup.
    • It’s hard for a user to inadvertently quit the application.

    Prerequisites

    • Microsoft Analysis Services installed and configured
    • Microsoft .NET Framework 4.7.2 or higher
    • Flexmonster CLI
      Install it with the following command:
      npm install -g flexmonster-cli

    Step 1. Install Flexmonster Accelerator

    Start the installation process with the following CLI command:

    flexmonster add accelerator -i

    The flexmonster add accelerator command does the following:

    • Downloads the .zip archive with Flexmonster Accelerator.
    • Automatically unpacks the files in the current folder — as a result, the flexmonster-accelerator/ folder will appear in your current directory.

    The -i option, which stands for --install, automatically starts the installation using the Flexmonster Accelerator.msi setup file. When the installation begins, just follow the wizard.

    The flexmonster-accelerator/ folder has the following structure:

    • Flexmonster Accelerator.msi – a server-side utility that handles the connection between Microsoft Analysis Services and Flexmonster Pivot.
    • flexmonster.config – a file that contains configuration parameters for the utility (connection string, port, etc.).

    You can check whether the Accelerator is up and running by navigating to its URL in the browser (http://localhost:50005 by default).

    Step 2. Configure Flexmonster Accelerator on the server

    After a successful installation, run Flexmonster Accelerator Manager:

    fm-accelerator-manager

    Click the Config button to open the flexmonster.config file, which contains configurations for the Accelerator. To learn more about them, see the configurations reference.

    When the configuration is finished, restart Flexmonster Accelerator using the Accelerator Manager: click the Stop button and then click Start. Then you can close Flexmonster Accelerator Manager — the service will continue working in the background.

    Step 3. Open a port for the Accelerator in the firewall

    If you plan to allow connections to the Accelerator from outside the server, open the appropriate port in the firewall. The default port number is 50005, but it can be changed using the PORT parameter in the flexmonster.config file.

    Step 4. Embed the component into your webpage

    If Flexmonster is not yet embedded, set up an empty component in your webpage:

    In pure JavaScript

    Complete the Integrating Flexmonster guide. Your code should look similar to the following example:

    const pivot = new Flexmonster({
      container: "pivotContainer",
     toolbar: true
    });

    In React

    Complete the Integration with React guide. Your code should look similar to the following example:

    <FlexmonsterReact.Pivot
     toolbar={true}
    />

    In Angular

    Complete the Integration with Angular guide. Your code should look similar to the following example:

    <fm-pivot
     [toolbar]="true">
    </fm-pivot>

    In Vue

    Complete the Integration with Vue guide. Your code should look similar to the following example:

    <Pivot
     toolbar
    />

    Step 5. Configure the component

    The report should be configured as follows (replace proxyUrl, catalog and cube parameters with your specific values):

    Connect to a multidimensional model

    const pivot = new Flexmonster({
    container: "pivotContainer",
    toolbar: true,
    report: {
    dataSource: {
    type: "microsoft analysis services",

    /* URL to Flexmonster Accelerator */
    proxyUrl: "http://localhost:50005",

    /* Catalog name */
    catalog: "Adventure Works DW Standard Edition",

    /* Cube name */
    cube: "Adventure Works",

    // Flag to use the Accelerator instead of XMLA protocol binary
    binary: true
    }
    }
    });

    Connect to a tabular model

    const pivot = new Flexmonster({
    container: "pivotContainer",
    toolbar: true,
    report: {
    dataSource: {
    type: "microsoft analysis services",

    /* URL to Flexmonster Accelerator */
    proxyUrl: "http://localhost:50005",

    /* Database name */
    catalog: "Adventure Works DW Standard Edition",

    /* Model name */
    cube: "Adventure Works",

    // Flag to use the Accelerator instead of XMLA protocol binary
    binary: true
    }
    }
    });

    Live example

    See the full list of Flexmonster properties used to configure the dataSource object.

    Now launch the webpage from a browser — there you go! A pivot table is embedded in your project.

    List of supported configuration parameters

    When connecting to data from Microsoft Analysis Services, you can use the following properties to configure the DataSourceObject:

    List of properties
    Property/TypeDescription
    type
    String
    The data source type. When connecting to data from Microsoft Analysis Services, set the type to "microsoft analysis services".
    catalog
    String
    The data source catalog name.
    cube
    String
    The catalog's cube's name.
    dataSourceInfo
    String
    optional The service info.
    proxyUrl
    String
    The URL to the Flexmonster Accelerator.
    binary
    Boolean
    optional Indicates whether to use Flexmonster Accelerator or the XMLA protocol. When set to true, Flexmonster will use Flexmonster Accelerator.
    Default value: false.
    effectiveUserName
    String
    optional Specify this property when an end-user identity must be impersonated on the server. Specify the account in the domain\user format.
    localeIdentifier
    Number
    optional The Microsoft locale ID value for your language.
    mapping
    MappingObject | String
    optional Defines how fields from the data source are treated and presented within the component. When using Microsoft Analysis Services, you can specify the field’s captions or hide the field from the dataset. Read more in the Mapping guide.
    It can be either an inline MappingObject or a URL to a JSON file with the mapping Live example.
    roles
    String
    optional A comma-delimited list of predefined roles to connect to a server or a database using the permissions defined by that role.
    If this property is omitted, all roles are used and the effective permissions are the combination of all roles. For example, to combine "admin" and "manager" roles, set the roles property like so: roles: "admin,manager".
    subquery
    String
    optional Sets a server-side filter to decrease the size of the response from the OLAP cube.
    For example, to show reports for only one specific year set the subquery like so: "subquery": "select {[Delivery Date].[Calendar].[Calendar Year].&[2008]} on columns from [Adventure Works]" Live example.
    requestHeaders
    Object
    optional Adds custom request headers. Consists of "key": "value" pairs, where "key" is a header name and "value" is its value Live example.
    Note The requestHeaders property is not saved when obtaining the report via save() and getReport() API calls.
    useGranularityNamesForDateFilters
    Boolean
    optional Adjusts date filters to the cube structure.
    When set to true, date filters use granularityNames. When set to false, date filters use the unique name of the hierarchy being filtered.
    Default value: true.
    withCredentials
    Boolean
    optional Indicates whether cross-site Access-Control requests should be made using credentials such as authorization headers (true) or not (false). For more details, refer to MDN web docs.
    Setting the withCredentials flag to true is recommended when using Windows authentication and other types of server authentication. When set to false, the browser does not ask for credentials and does not include them in outgoing requests.
    Default value: false.

    Cache control

    Usually, a cache can improve performance greatly. However, if the underlying database ever changes, the cache goes out of date. By default, caching is enabled and controlled by the Accelerator.

    It is also possible to disable the cache with the CACHE_ENABLED parameter in the flexmonster.config file:

    CACHE_ENABLED = false

    What’s next?

    You may be interested in the following articles: