You can configure the path behavior and time out interval for the Java Reporting Component by modifying the CRConfig.xml
file located in the WEB
directory of your web project.
When creating a report source using the Java Reporting Component, the report's path can be specified by using either a relative or absolute path.
When using relative paths, the path is specified relative to the location of the Java Reporting Component on the web server. For example, ../reports/sample.rpt
resolves to /WEB
where the Java Reporting Component JAR file is in /WEB
. The behavior of relative paths can be modified by specifying the value of the reportlocation
tag in the CRConfig.xml
file. The value of reportlocation must specify a location as a path relative to the location of the Java Reporting Component, which is by default WEB
. The value of the reportlocation tag becomes the new root directory that is used to determine the location of a report. If the reportlocation tag is not present, the Java Reporting Component uses absolute paths.
Note: When using absolute paths, the Java Reporting Component will also look in the location of your web application's resources. For example, you can place your report into the classes folder and then specify the name of the report directly in your JSP file (with no path). In this case, the Java Reporting Component will find the report.
To use absolute paths, ensure that the CRConfig.xml
file does not contain a reportlocation tag.
The CRConfig.xml
file allows you to configure the time out interval that determines (in minutes) when inactive report sources are disposed. 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 timetimeout
tag in the CRConfig.xml
file. By default, the timeout interval is 10 minutes. You can configure the Java Reporting Component to have no timeout by setting the value to 0.
The timeout interval only applies to inactive reportsreports 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 disposed and its resources are made available to other processes.
Business Objects http://www.businessobjects.com/ Support services http://www.businessobjects.com/services/support/ |