
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Note: These properties have no impact on scheduled reports: they always run on the
application server.
When reports are generated on the web server, web scalability can be used to scale
generation limit the impact of report generation on a core cluster of web servers. See the
Application Scalability Guide for more information.
Management of Report Files
During report generation, a number of files may be stored in the server’s file system. These include
data content XML, embedded images for HTML and the final reports. Oracle Transportation
Management must have full create/read/write/delete privileges to these files and their directories to
properly stage reports.
The following properties control the location of reporting files on each tier:
glog.bipreports.report.path
glog.bipreports.app.tempDir
data content files for the application
server
glog.bipreports.app.ImageDir
HTML embedded images for the
application server
glog.bipreports.web.tempDir
data content files for the web server
glog.bipreports.web.ImageDir
HTML embedded images for the web
server
Intermediate report files are typically removed once the final report is generated. Final report files are
managed with a Least Recently Used (LRU) algorithm. The default number of reports maintained by a
running server is 200. Use the following property to modify this value:
glog.cache.Reports.capacity=<report capacity>
If a server generating reports fails or is cycled, existing report files will no longer be managed by the
LRU algorithm. The following set of properties provides a backup to clean out old report and image
files.
glog.bipreports.cleanup.<type>.threshold
# of days to hold files of this type
9
This must be underneath the document root to properly server images to the browser.
Kommentare zu diesen Handbüchern