Deploying Runtime components
When you only use JReport Runtime instead of JReport Designer, you should deploy the Engine Bean Runtime components, which include the following files:
- JREngine.jar
JReport Engine Bean.
- JRResultViewer.jar
Result Viewer Bean.
- log4j-1.2.8.jar
Jar file used for the JReport Engine logging system.
- chart.jar
Jar file used when exporting to HTML with images that are to be embedded as a chart applet in the HTML file.
- udo12.jar
Registers user defined objects.
- report.ini
Configuration file.
- activation.jar
Jar file used when exporting to mail.
- mail.jar
Jar file used when exporting to mail.
- poiHSSF_151.jar
Jar file used when exporting to Excel.
- Itext.zip
Jar file used when exporting to PDF.
- LogConfig.properties
Used to configure log mechanism.
- sac.jar
Used to parse xml files.
Notes:
- In your code, if you set the reporthome as
c:\\jreport\\designer, the file report.ini will be read in the directory c:\jreport\designer\bin. You will find in this file the configuration information, including the temporary path, template path and the help path. JReport Engine Bean will use the temporary path to export temporary files. You should therefore ensure that the temporary folder specified in the file report.ini exists.
- If you only want to generate a report, you will only need JReport Engine Bean. While if you want to view a report result file, you will also need JReport Result Viewer Bean.