Publishing Reports to the Web - Downloads - Oracle

orawin/reports/conf/filename.ext
3.3.1 Specifying the Location of the Key Map File
Configuring the Reports Servlet
Your report runtime command line may include information you do not want to
expose to your users. Additionally, it may be comprised of a long string of options that
is difficult to remember or makes for an ungainly URL.
You have the option of entering a report's command line options in a key map file
(cgicmd.dat), then limiting the exposed runtime command to the name of the
particular key section in this file that holds the required options.
The key map file is discussed in Chapter 13, "Running Report Requests". Use the
Reports Servlet configuration file to list the location of this file.
For example:
KeyMapFile=d:\\orawin\\reports\\conf\\cgicmd.dat
This example uses the default filename and location. An entry for the location and
filename of the key map file doesn't appear by default in the servlet configuration file
because the servlet already knows what to look for and where to look for it. If you use
a file with a different name and/or different location, you must include a
KeyMapFile parameter in your servlet configuration file that includes the directory
path and filename.
3.3.2 Reloading the Key Map File
Use the RELOAD_KEYMAP parameter to specify whether the key map file
(cgicmd.dat) should be reloaded each time the servlet receives a request.
For example:
RELOAD_KEYMAP=yes
This is useful if you frequently make changes to the map file and want the process of
loading your changes to be automatic. Runtime performance will be affected according
to how long it takes to reload the file.
Typically, this parameter is set to no in a production environment and yes in a testing
environment.
3.3.3 Hiding Web Command Output
You may want to provide an authentication mechanism for an unsecured Reports
Server so that only an administrator (based on the authid) can run a Web command,
like showenv, showjobs, etc. By setting DIAGNOSTIC=NO in the
rwserver.properties file, you can provide just such an authentication mechanism.
This authentication information is also used for administrative tasks, for example,
stopping the Reports Server from the command line.
Note: Setting DIAGNOSTIC=NO only works for non-secured
Reports Server. For secure Reports Server users, Reports Server
verifies the user’s privileges based on the entries in Oracle Internet
Directory.
To disable Web command display for an unsecured Reports Server
Configuring OracleAS Reports Services 3-33