Publishing Reports to the Web - Downloads - Oracle

Command Line Keywords
Description Use USERID only if you're not using Single Sign-On. Use USERID to
specify your Oracle user name and password, with an optional database name for
accessing a remote database. If the password is omitted, then a database logon form
opens automatically before the user is allowed to run the report.
If you want users to log on to the database, then omit the password portion of the
USERID keyword from the report request. If you want users to log on every time they
run report requests, then use the Oracle Reports key mapping file, cgicmd.dat, to
specify the runtime command, and include the %D option in the relevant key mapping
entry.
Syntax userid=username[/password][@database]
Values
username Username assigned by the database administrator.
password Password for the username.
database The name of the database you are accessing.
Default None
Usage Notes
■ The logon definition cannot exceed 512 bytes in length.
■ USERID can be used when running JSP-based Web reports from the command
line.
A.4.117 WEBSERVER_DEBUG
Table A–129 indicates which commands can use the WEBSERVER_DEBUG keyword.
Description Use WEBSERVER_DEBUG for JSP debugging. It creates the stderr.log
and stdout.log files under the docroot/port# directory, and leaves temporary
JSP files under docroot/port#/default and log files under docroot/port#/log
for your inspection.
Syntax WEBSERVER_DEBUG={YES|NO}
Values
YES Create debugging files.
NO Do not create debugging files.
Default NO
Usage Notes
Note: For information on using the cgicmd.dat file, see
Running Report Requests.
Table A–129 Commands that can use WEBSERVER_DEBUG
rwclient rwrun rwbuilder rwconverter rwservlet rwcgi rwserver
no no yes no no no no
Command Line Options A-85