Tirupathi Mangalarapu

Normally $P{REPORT_CONNECTION} parameter is used to pass the main report's database to the subreport for the same report connection. A subreport can use a different JDBC connection than the main report. There are several ways to accomplish this requirement: Why this approach: One of our customers did not want to expose connecting string or username password information in the .jrxml file nor they do not want to use the data adapter approach. In this approach, we need to create two parameters to create a new database connection. I will detail the steps below. For this wiki, I am using two different JDBC data sources for my report one is a sample database that comes with TIBCO Jaspersoft sample database “SugarCRM” it’s a PostgreSQL database and the other is an MSSQL database. Here are the steps I followed: Create a report in Jaspersoft Studio using “Sugarcrm” with the following query: SELECT id, date_entered, name, modified_user_id, date_modified FROM accounts Read fields, preview the report, and run the report. Create two parameters in this report: $P{DATA_SOURCE_PATH}Class: com.jaspersoft.jasperserver.api.metadata.jasperreports.domain.JdbcReportDataSource Default value expression: com.jaspersoft.jasperserver.api.engine.jasperreports.util.RepositoryUtil.getThreadRepositoryContext().getRepository().getResource(null,"/public/Samples/Data_Sources/DB_MSSQL") Here “/public/Samples/Data_Sources/DB_MSSQL” is the path to the JDBC data source that is created on the Jaspersoft Server. (Right click go to properties and copy the path of the JDBC data source from Jaspersoft server) Attached a screenshot for your reference below: Screenshot of the param below: $P{SUBREPORT_CONNECTION}class: java.sql.Connection default value expression: “java.sql.DriverManager.getConnection($P{DATA_SOURCE_PATH}.getConnectionUrl(),$P{DATA_SOURCE_PATH}.getUsername(),$P{DATA_SOURCE_PATH}.getPassword())” Either you can create a sub report separately or you can add use the drag and drop subreport element and start from a blank sub-report (it’s up to you). Just to keep it easier, I will create sub report separately with MSSQL data source and bring in some fields and add them to the detail band. Preview it and ensure that the report runs and brings in some data as shown below: Once the sub report is created, I will change my Data Adapter to not use any data source as shown below: The purpose of the above steps is to ensure that the metadata of the fields are read and the report has fields added to the report from your second data source i.e. MSSQL in this case. Now, go ahead and drag and drop sub report component from the palette into the summary section of the main report. Select an existing report and point to the report that you have created using the MSSQL in the above step (using workspace resource). click “subreport” section You should see something like this: Now go ahead and change the value of the connection expression. Change it to $P{SUBREPORT_CONNECTION} We are passing the connection string from the main report to the sub report using the parameters. Now, preview the main report in the Jaspersoft Studio. You may see errors like this: I did not research more on the error messages. If anyone has any input let us know in the comment section(We might need to add all the jars from the Jaspersoft server to be added to the classpath on this project in the studio) Go ahead and publish this report to the Jaspersoft Server, and test it on the server. You should see your report running without any errors. Here is the screenshot of the report from my instance. Note: I attached the jrxml files to this KBA so that you can take this as a reference if you run into any challenges during configuration on your end. This is tested in the latest version of the JRS 8.0 Hope this helps someone! diffdbtype-postgresql-mssql.jrxml diffdbtype-subreport.jrxml

Jaspersoft Server authentication is required to do the following: Identify the userAuthentication is applied to organizations, users, and roles in the JasperReports Server databasePasswords are encrypted by default After a user supplies the correct information and authenticates successfully, a session is created and the user is presented their home page. The password is stored encrypted in the database table called jiuser. Here is a screenshot for your reference: Default Internal Authentication: In step 1, an unauthenticated user requests any page in JasperReports Server. Often, users bookmark the login page and begin directly at step 3, but this step covers the general case and secures every possible access to JasperReports Server. For example, this step applies when a user clicks the page of an expired session, or when a user enters the direct URL to a report within JasperReports Server. At step 2, JasperReports Server detects that the user is not logged in and replies with a redirect to the login page. For convenience, JasperReports Server includes the original request in the login screen URL so that the user goes directly to the requested page after logging in. At step 3 the user enters a username, password, and possibly an organization ID. JasperReports Server compares these credentials with the matching user account in the internal database, and, if they are valid, creates a principal object. The user is now authenticated, and the principal object represents the user session, including any assigned roles found in the user database.

Jasperserver Sample Environment: Some firms want to provide environments in which software code modifications and report development can occur without affecting the live production environment. These environments often carry names like Development, Integration, Test, and Prod. The report development environments can use sample data, and the production tiers, of course, use actual production data. Reports can be developed on systems that use free or open-source applications and database servers, then moved into production where the commercial servers are running. This is approach is cost-effective. Here is table view that lists how customers setup their BI environments using Jaspersoft for all different tiers: DEVELOPMENT INTEGRATION TEST PRODUCTION Description Development Environment Integration Test Environment Quality Assurance Environment Actual Production System Location Developer’s Machine Server Server Server Database PostgreSQL PostgreSQL Oracle Oracle Application Server Apache Tomcat Apache Tomcat JBoss JBoss Administration Developer Both Admin Admin Developer Super User Super User Read Only None Admin - Sys Admin Sys Admin Sys Admin / None Development is a working environment for developers. Isolated from the other tiers, developers can try radical changes to the code without adversely affecting the development team. Integration is where all developers commit changes. The goal of this environment is to combine and validate the work of the entire team so it can be tested before being promoted to the Test environment. Test is as identical to the Production environment as possible to simulate as much of the Production environment as possible. It is also called Staging environment. The Production tier might include a single machine or a sizeable cluster composed of many machines. Notice that, as you move from left to right, the database and application servers might change from the less expensive names like PostgreSQL and Tomcat to commercial names like Oracle and JBoss. The administrator’s job duties are many and varied. They may be involved in pushing reports along the production path, from early development to the test or QA environment, and eventually to the live production machines. Best Practice recommendation: The folder structure has to be identical across environments, or the paths will break and the report will not execute. For the same reason, data sources and all other items common to reports should carry the same names and URLs in all the environments, or else reports will be unable to find them and will not execute properly.

When to use Jaspersoft studio:Creating a report when the layout of the elements is of utmost importance (pixel perfect). When you want to write complex expressions, Layout visual components like charts, maps, tables, crosstab, custom visual components, and much more. When you want to provide canned reports to end-users. Create complex reports such as creating scriptlets. Create drill-down reports using hyperlinks etc. SQL knowledge is required to build reports. End users can only consume the reports. For more information on what you can do with Jaspersoft Studio, please refer to the Jaspersoft Studio Community Project page. When to use Ad hoc reports:Creating reports where the layout of the report elements (non-pixel perfect) is not a strict business requirement. When you want to create simple reports from Domains, Domain Topics from the Jaspersoft Web Interface. When you want to provide end business users the ability to create their own reports from the Jaspersoft Web UI. Create basic reports from the Ad hoc editor. SQL expertise is not required for users to create Ad Hoc views reports. End users can explore data before a final report is created. For more information on what you can do with Ad Hoc Editor, please refer to the JasperReports Server User Guide Note:Please let us know if anything else needs to be added or updated in the comments section below.

Please use the attached CSS file to create a custom theme and add the overrides_custom.css file to the new themes folder and Set as the active theme. When you click Home. Video Tutorials and Popular Resources should be hidden from the UI for the end-users. Here are the contents of the file: overrides_custom_5.css