Publishing Reports to the Web - Downloads - Oracle

13.8 Scheduling Reports to Run Automatically
Reusing Report Output from Cache
You can use the server to run reports automatically from Reports Queue Manager,
OracleAS Portal, or with the SCHEDULE command line option. The scheduling feature
enables you to specify a time and frequency for the report to run.
Refer to the Reports Queue Manager online help, for more information about scheduling
your reports.
If you publish a report as a portal component on an OracleAS Portal page, then you
can schedule the report request to run automatically and push the resulting reports to
specified pages. Refer to OracleAS Portal online help for more information.
The SCHEDULE keyword is available for use with the rwclient, rwservlet, and
rwcgi commands. See Command Line Options, SCHEDULE for more information.
13.9 Additional Parameters
See Also: Using the Oracle Reports Web Service
For more information on the Oracle Reports Web service and
installing and using the sample proxy and Java client.
When you send a request to the Reports Server, the following additional parameters,
the values of which you cannot change, are implicitly passed along with your request:
Table 13–5 Additional parameters passed with a report request
Name Description
ACCEPT_LANGUAGE The comma separated list of languages accepted by the
browser/user.
REMOTE_ADDR The remote IP address from which the user is making the
request.
REMOTE_HOST The remote host name from which the user is making the
request.
SCRIPT_NAME The virtual path of the script being executed.
SERVER_NAME The host name or IP address of the server on which the Reports
Servlet is running.
SERVER_PORT The port number of the server on which the Reports Servlet is
running.
SERVER_PROTOCOL The name and revision of the information protocol with which
the request was sent.
USER_AGENT The description of the remote client’s browser.
13.10 Reusing Report Output from Cache
When you run a report, a copy of the report output is saved in the OracleAS Reports
Services cache. Subsequently, if an identical report is run (that is, with the same cache
key), then the current request is recognized as a duplicate job.
There are several scenarios where reports caching takes effect:
■ When a new job request "A" comes to the Reports Server, and there is another job
"B" that has the same cache key in the Current Jobs Queue (where it is waiting for
an available engine or is in the middle of execution), then job "A" will use the
output from job "B".
Running Report Requests 13-17