Java Reporting Component

When creating a Java Reporting Component report source, the report's path can be specified in several different ways:

• File path

  This is an absolute path that specifies a report located on the machine running the Java Reporting Component.

  For example, C:\reports\sample.rpt.

• UNC address

  This specifies a report file that is accessible through a network resource.

  For example, \\hostname\sample.rpt.

• Relative file path

  For example, reports\sample.rpt refers to a directory called reports in the same directory as the Java Reporting Component.

• Relative URL

  This is a URL that is specified relative to the location of the Java Reporting Component.

  For example, ../reports/sample.rpt resolves to /WEB-INF/reports/sample.rpt where the Java Reporting Component JAR file is in /WEB-INF/lib.

Java Reporting Component configuration

The behavior of relative paths can be modified by specifying the value of the reportlocation tag in the CrystalReportEngine-config.xml, which is located in your WEB-INF directory. The value of reportlocation must specify a location as an absolute path or as a path relative to the location of the Java Reporting Component, which is by default WEB-INF/lib. The value of the reportlocation tag becomes the new root directory that is used to determine the location of a report.

The CrystalReportEngine-config.xml file also allows you to configure the time out interval that determines when inactive report sources are freed up. This is necessary as inactive report sources still consume system resources such as database connections, server memory, and disk space used by temporary files. The time-out interval can be specified by setting the value of the timeout tag in the CrystalReportEngine-config.xml file. By default, the timeout interval is 10 minutes. The timeout interval only applies to inactive reports—reports that are being processed are not timed out as a result of exceeding this value. Each time a report source request is successfully completed, the timeout timer is reset. If a report source is not used within the timeout interval, it is freed up and its resources are made available to other processes.