Multidimensional Dataset Plugin

  • Last update:April 19, 2024
  • Overview

    Version

    Report Server Version

    JAR Package Version

    Plugin Version

    10.0

    2020-04-27

    V3.3.11

    9.0

    2018-10-10

    V3.2.9

    8.0

    2018-10-10

    V3.2.9

    Plugin Introduction

    The multidimensional database (MDD) refers to storing data in multiple dimensions.

    In simple terms, MDDs involve storing data in an n-dimensional array instead of in the form of records as in a relational database. Hence, numerous sparse matrices exist in MDDs where data can be observed by multidimensional views.

    Besides, the addition of a time dimension in MDDs offers advantages over relational databases, primarily in terms of enhancing data processing speed, accelerating response time, and improving query efficiency.

    Procedure

    FineReport provides a way to connect to MDDs through XMLA data connection, converting data from the databases into two-dimensional tables for template creation and data analysis.

    Plugin Installation

    You can obtain the plugin at Multidimensional Dataset.

    For details about installing the plugin in the designer, see Designer Plugin Management.

    For details about installing the plugin on the server, see Server Plugin Management.

    After the plugin is installed, choose Server > Define Data Connection, and the XMLA data connection can be selected on the Define Data Connection setting page, as shown in the following figure.

    7152b375ea6c76eac93bcccb79023ee.png

    Configuring Parameters of the Data Connection

    Add an XMLA data connection. The XMLA data connection in FineReport supports the connection to mainstream types of databases in the market, including SQL Server Analysis Services, Oracle Essbase, and SAP HANA.

    ef1d7f137ddb3b81addc4704079196b.png

    The following content introduces the configuration methods of the database.

    1. SQL Server Analysis Services

    Set Database Type to SQL Server Analysis Services, enter the information of XMLA URL, Username and Password in order. Select the database from the drop-down list of Database and click Test Connection, as shown in the following figure.

    iconNote:
    The URL entered in XMLA URL is the site directly deployed via IIS.

    2. Oracle Essbase

    1. Set Database Type to Oracle Essbase, enter the site address (where the database is located) in XMLA URL, enter the username and password, and select the database from the drop-down list of Database.

    Click Test Connection to test if the connection is successful.

    终2.png

    Adding Datasets

    After the XMLA data connection is established, you can add XMLA datasets of the multidimensional database. For more details, see Multidimensional Database. The ways to retrieve data through the XMLA dataset query include Simple General Query and Custom MDX Query

    iconNote:
    1. When you perform the simple general query to filter on selected dimensions, the operators do not support Contain, Not Contain, and Begin with. When you perform the query to filter on non-selected dimensions, the operator only supports Equal to.
    2. For complex filtering forms, you can perform the custom MDX query.

    Note

    Error: HTTP-503

    1. Problem Description

    When you create an SSAS service, one of the configuration files used is msmdpump.ini.

    By default, msmdpump.ini allows a maximum of four connections per client when connected to SSAS through the IIS proxy. Exceeding four connections will result in an HTTP 503 error due to server restrictions on concurrent access.

    2. Solution

    Modify the msmdpump.ini configuration file.

    Before modification:

     <ConfigurationSettings>
        <ServerName>localhost</ServerName>     
        <SessionTimeout>3600</SessionTimeout>    
        <ConnectionPoolSize>100</ConnectionPoolSize>    
        <MinThreadPoolSize>0</MinThreadPoolSize><!--This line may not exist-->     
        <MaxThreadPoolSize>0</MaxThreadPoolSize><!--This line may not exist-->     
        <MaxThreadsPerClient>4</MaxThreadsPerClient><!--This line may not exist--> 
    </ConfigurationSettings&gt

    After modification:

     <ConfigurationSettings>     
        <ServerName>localhost</ServerName>    
        <SessionTimeout>3600</SessionTimeout>   
        <ConnectionPoolSize>100</ConnectionPoolSize>  
        <MinThreadPoolSize>200</MinThreadPoolSize><!--This line is added, 200 is the recommended value-->     
        <MaxThreadPoolSize>500</MaxThreadPoolSize><!--This line is added, 500 is the recommended value-->   
        <MaxThreadsPerClient>100</MaxThreadsPerClient><!--This line is added, 100 is the recommended value--> 
    </ConfigurationSettings&gt

    You can modify the data as needed by following the rules below.

    MaxThreadsPerClient < MinThreadPoolSize < MaxThreadPoolSize

    If accessing this service after the modification still doesn't resolve the data issue under multiple threads, you can simply stop, restart, and refresh the service to resolve the problem, as shown in the following figure.

    Screenshot 2024-04-16 152557.png

    Screenshot 2024-04-16 152805.png

    Error: Catalog Can not Be Null

    1. Problem Description

    SSAS connection failed with the error message "catalog can not be null!", as shown in the following figure.

    d0a136f2cb272570f219435889d74b5.png

    2. Solution

    There is an empty cube in SSAS, and you and delete the empty cube.

    Attachment List


    Theme: Data Preparation
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy