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.
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.
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.
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.
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
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>
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>
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.
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.
2. Solution
There is an empty cube in SSAS, and you and delete the empty cube.