jasperreports_developer_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
jasperreports_developer_guide [2022/02/21 20:01] – [Helical Notes] ghachey | jasperreports_developer_guide [2024/06/18 01:28] (current) – ghachey | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== JasperReports | + | ====== JasperReports |
While the system can potentially support JasperReports, | While the system can potentially support JasperReports, | ||
Line 21: | Line 21: | ||
* Provide appropriate security for JasperReports Server (i.e. change default username and password at minimum) at least for production development. | * Provide appropriate security for JasperReports Server (i.e. change default username and password at minimum) at least for production development. | ||
- | ===== Jasper Technologies Configuration | + | ===== Download the Pacific EMIS Source Code ===== |
- | Assuming you have already cloned | + | You should first create a clone of the [[https:// |
+ | |||
+ | ===== Jaspersoft Workspace ===== | ||
+ | |||
+ | Set your Jaspersoft Studio Workspace to point to the location where all the reports for this project are located. For example, you may have cloned | ||
{{ : | {{ : | ||
- | Second thing, since we are using the MS SQL Server database we will need to install | + | ===== Jaspersoft Set Java Build Path ===== |
+ | |||
+ | There are a few things to add to the Java build path for things | ||
+ | |||
+ | * Install | ||
+ | * Font extension (Jar file can be found in the Pacific EMIS Report source code repository) | ||
+ | * Chart customizer | ||
{{ : | {{ : | ||
- | Furthermore, | + | ===== Jaspersoft |
- | < | + | Setup data adaptors for all databases you will be developing for. Example shown below. |
- | security.validation.sql.on=false | + | |
- | </ | + | {{ : |
+ | |||
+ | |||
+ | ===== Jaspersoft Setup Servers ===== | ||
+ | |||
+ | Setup serversconnections for all databases you will be developing for. Example shown below. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ===== Jaspersoft Publishing Strategy to JasperServer ===== | ||
+ | |||
+ | The adopted publishing strategy for all Pacific EMIS reports is to always override all resources when reports modifications such as improvements or fixes are made. Use local resources for any subreport and link resources for the following which are on the JasperServer in a single place for better re-usability. | ||
+ | |||
+ | * Images | ||
+ | * Templates | ||
+ | * Input controls (parameters) | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | To make this mostly automatic you can change the following setting. | ||
+ | {{ :: | ||
===== Reports Structure ===== | ===== Reports Structure ===== | ||
Line 120: | Line 151: | ||
===== Integration with Pacific EMIS ===== | ===== Integration with Pacific EMIS ===== | ||
- | To effectively integrate the JasperReport server with the Pacific EMIS you need to make sure the relevant part of the Web.Config is edited accordingly (i.e. jasperUrl, jasperUser, jasperPass). This would likely be different whether you are working in development or deploying to production. | + | Refer to the [[JasperReports Systems Administrator Guide]] |
- | + | ||
- | <code xml> | + | |
- | < | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | <add key=" | + | |
- | </ | + | |
- | </ | + | |
- | + |
jasperreports_developer_guide.1645473666.txt.gz · Last modified: 2022/02/21 20:01 by ghachey