B
Reports Server Configuration Parameters

CACHEDIR 

CACHEDIR is the cache for the Reports Server. CACHEDIR can be set to any directory or logical drive on the machine. If it is not specified, the default is ORACLE_HOME\ REPORT60\SERVER\CACHE.

Example CACHEDIR="c:\ORACLE_HOME\Report60\cache" 

CACHESIZE 

CACHESIZE is the size of the cache in megabytes. If you expect to store the output of many of your reports in the Reports Server cache, you may want to increase this setting. If you do not expect to store a lot of output in the cache and have limited system resources, you may want to reduce it. Once the cache grows beyond the set size, the Reports Server cleans up the cached files on a first in, first out basis.

Default value=50

Note: You can set this parameter from the Queue Manager. Open the Queue Manager and log on as the administrator. Choose Queue->Properties, and then change the Cache size (MB) setting. 

CLUSTERCONFIG

CLUSTERCONFIG is the configuration of slave servers to the master server. Clustering allows you to run reports on multiple Reports Servers. The master server can identify available slave servers and start their engines as needed. You can set up many servers as slaves to the master server. Use the following syntax in the master server configuration file:

Clusterconfig="(server=<servername> 
minengine=<minimum number of master engines> 
maxengine=<maximum number of master engines> 
initengine=<initial number of master engines> 
cachedir=<directory of central cache>)"

Note: Each slave definition must be enclosed in parentheses.

See Chapter 6, "Configuring Reports Server clusters" for detailed instructions. 

ENGLIFE 

ENGLIFE is the maximum number of reports that an engine will run before shutting itself down. The Reports Server will then bring up fresh engines for new requests.

Default value=50 

FAILNOTEFILE 

FAILNOTEFILE is path and file name of the notification message template that is sent to specified email addresses for jobs that fail to run.

Example

FAILNOTEFILE="c:\ORACLE_HOME\Report60\failnote.dat" 

IDENTIFIER 

IDENTIFIER is an internal setting that contains the encrypted queue administrator user ID and password. You should not attempt to modify it. If IDENTIFIER is not specified or is deleted, or the configuration file is not present, anyone can supply any user ID and password from the Reports Queue Manager to log on as the queue administrator. Once someone has logged on in this way, the user ID and password they specified becomes the queue administrator user ID and password until it is changed from the Queue Manager. 

INITENGINE 

INITENGINE is the initial number of runtime engines started by the Reports Server. The server process will spawn this many engines when it is started. It will wait two minutes for these engines to connect to it and will shut itself down if they fail to do so. If the engines cannot connect in this amount of time, there is usually some setup problem.

Default value=1 

LOGOPTION 

LOGOPTION is the type of log information you want inserted into the log file. The options are alljob, failedjob, and succeededjob.

Example

LOGOPTION="alljob" 

MAILPROFILE 

(Windows NT only) MAILPROFILE specifies the mail profile and password to be used when mailing reports.

Example

MAILPROFILE="mailprofileid/password" 

MAXCONNECT 

MAXCONNECT is the maximum number of processes that can communicate with the server process at any one time. This setting is the sum of the number of engines and clients, and must be greater than two (at least one engine and one client).

Default value=20  

MAXENGINE 

MAXENGINE is the maximum number of runtime engines available to the Reports Server to run reports. The server process will attempt to keep no more than this many engines active. Ensure that you have sufficient memory and resources available to accommodate this number of engines.

Default value=1

Note: You can set this parameter from the Queue Manager. Open the Queue Manager and log on as the administrator. Choose Queue->Properties, and then change the Simultaneous running engines Max setting. 

MAXIDLE 

MAXIDLE is the maximum amount of time an engine is allowed to be idle before being shut down. Note that the Reports Server will not shut down the engine if doing so would reduce the number of available engines to less than those defined in the MINENGINE.

Default value=30

Note: You can set this parameter from the Queue Manager. Open the Queue Manager and log on as the administrator. Choose Queue->Properties, and then change the Max idle time (minutes) before engine shutdown setting. 

MINENGINE 

MINENGINE is the minimum number of runtime engines the Reports Server should have available to run reports. The server process will attempt to keep at least this many engines active. Ensure that you have sufficient memory and resources available to accommodate this many engines.

Default value=0

Note: You can set this parameter from the Queue Manager. Open the Queue Manager and log on as the administrator. Choose Queue->Properties, and then change the change the Simultaneous running engines Min setting. 

PERSISTFILE 

PERSISTFILE indicates the location of the Reports Server's .DAT file, which contains the details of scheduled jobs. If PERSISTFILE is not specified, the default is ORACLE_HOME\REPORT60\SERVER.

Example

PERSISTFILE="C:\ORACLE_HOME\Report60\repserver.dat" 

REPOSITORYCONN 

REPOSITORYCONN is the database connection string that connects the Reports Server to the database when the server starts up. The database takes a snapshot of Reports Server queue activity (i.e., scheduled jobs) whenever jobs are run.

To create a queue activity table in your database, you must run rw_server.sql script.

For Web CGI configurations, see Section 3.2.6, "Step 6. (Optional) Modify the Reports Server configuration".

Example

REPOSITORYCONN="repserver_schema/password@mydb" 

SECURITY 

SECURITY is the security level (0, 1, 2, or 3) for accessing cached output files through the Reports Queue Manager. 0 means that anyone can access a job's cached output. 1 means that only a user whose user ID is identical to that of the user who ran the job can access the job's cached output. 2 means that only the same process that sent the job can access the job's cached output. 3 means that the cached output cannot be accessed.

Default value=1 

SECURITYTNSNAME 

SECURITYTNSNAME is the TNS name of the Oracle WebDB database that is used for authenticating users to the Reports Server. The Reports Server uses Oracle WebDB to perform a security check and to ensure that users have access privileges to run the report to the restricted Reprts Server and, if requested, output to a restricted printer.

When the SECURITYTNSNAME parameter is set, you must add information about the Reports Server, printers, and reports in WebDB to process report requests via the Reports Server.

See Chapter 5, "Controlling User Access to Reports" for more information.

Example

SECURITYTNSNAME="sec_db" 

SOURCEDIR 

SOURCEDIR is a path to be searched before REPORTS60_PATH when searching for reports and other runtime files. This setting is useful when you have more than one Reports Server sharing the same ORACLE_HOME because each Reports Server can search different directories.

Example

SOURCEDIR="c:\my_reports" 

SUCCNOTEFILE 

SUCCNOTEFILE is the path and file name of the notification message template that is sent to specified email addresses for jobs that run successfully.

Example

SUCCNOTEFILE="c:\ORACLE_HOME\REPORT60\succnote.dat" 

TEMPDIR 

TEMPDIR is a directory that will be used instead of REPORTS60_TMP when creating temporary files. TEMPDIR can be set to any directory or logical drive on the machine.

Example

TEMPDIR="c:\ORACLE_HOME\Report60\temp"