There are many ways to use multiple data sources in reports designed via Jaspersoft Studio or JasperReports Server:
Multiple datasets, which is a standard feature in the product. You can associate a different dataset with each component added to a report, for example Tables, Crosstabs and Charts. If you require something more complex, another way to use multiple data sources is via Subreports. See this article for more details. And this blog post about using JNDI datasources in Subreports in particular (which would be recommended). Each of those components can be also nested into another one, if required. See also this article about conditionally using different SQL queries in the same report.
You can specify a data adapter for an individual data set by setting the net.sf.jasperreports.data.adapter property on each data set.
For JasperReports Server, you would deploy each data adapter as a file, and set up the Report Unit as per https://community.jaspersoft.com/wiki/how-deploy-and-use-data-adapter-jasperreports-server-v56 which still works in JasperReports Server 8.X.
Domains with a Virtual Data Source: see the Administrator Guide
Jaspersoft ETL to integrate data from multiple sources into the same data warehouse or reporting database. Likely the most performant solution, when done right
Using Profile Attributes in the Data Source definition allows to connect to a different database depending on the Profile Attributes defined at User, Tenant or Server level – as long as it's supported by the same JDBC driver
Instance of java.sql.DriverManager.getConnection to be passed as a connection expression to a dataset:
- Create parameterName: subConnClass: java.sql.ConnectionEXAMPLE Default Value Expression: java.sql.DriverManager.getConnection("jdbc:postgresql://localhost:5432/foodmart", "myusr", "mypwd")
- Component (e.g. Chart / Subreport) Sub Dataset
Connection/Data Source Expression: Use a Connection expression / Use another connection / Connection Expression (depending on which element in the Jaspersoft Studio UI)Expression content: $P{subConn}
Dynamic SQL table name in the same data source, e.g. via Parameter Contributors
Custom Data Sources or a data source that (potentially) provides access to multiple sources in its underlying implementation, e.g. the Webservice Data Source
And finally, a JRDataSource interface implementation if you need even more control, and use anything you can in Java to access multiple data sources and present them together via one interface. This option is probably the most complex to implement and maintain. See here for an example: How to cache data in a report for use in multiple datasets
Recommended Comments
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now