Publishing Reports to the Web - Downloads - Oracle

Configuring Reports Server
Description
The log element is available for backward compatibility. It invokes the generation and
population of a reports log file. The log file is automatically generated and stored in
the following path (the path is the same for Windows and UNIX):
ORACLE_HOME\reports\server_name\rwserver.log
The log element has one attribute: option, described in Table 3–9.
Table 3–9 Attributes of the log element
Attribute Valid values Description
option allJobs
succeededJobs
failedJobs
noJob
3.2.1.10 jobStatusRepository
Example
Required/Optional
Optional. You can have a maximum of one jobStatusRepository element in your
server configuration file.
Description
The jobStatusRepository element specifies the Java class that implements a job
status repository. It provides an additional means (over the persistFile element) of
storing job status information.
The persistFile is a binary file and, therefore, cannot be used to publish job status
information within your application. The jobStatusRepository provides a means
of including status information in your application by providing additional ways of
storing it.
The default class, oracle.reports.server.JobRepositoryDB, stores
information in a database. Use the Oracle Reports APIs to create your own
implementation of the Reports Server Job Repository interface
(oracle.reports.server.JobRepository) that stores information wherever you
wish.
3-18 Oracle Application Server Reports Services Publishing Reports to the Web
Default: noJob
Describes the type of jobs to be included in the
log, in addition to default server activities that are
logged. Choose from:
allJobs: all jobs will be logged
succeededJobs: only jobs that ran successfully
will be logged
failedJobs: only jobs that failed will be logged
noJob: no jobs will be logged
Note: Look for information about OracleAS Reports Services APIs
on the Oracle Technology Network, (http://otn.oracle.com).