Publishing Reports to the Web - Downloads - Oracle

Configuring the Reports Servlet
If the default Reports Server is a member of a server cluster, use the cluster name:
SERVER=server_name.cluster_name
If you use a combination of the server name and cluster name in your URL, requests
sent to the default server will go to this specific machine. If this machine is down, an
error message will be returned and the report will not be run. By specifying just the
cluster name in the URL, requests will be sent to a random cluster member, and
fowarded to another if the target machine doesn't have an idle engine.
If you don’t specify a SERVER parameter in rwservlet.properties, the default
server name is rep_machine_name.
3.3.12 Pointing to Dynamically Generated Images
Optionally, you can use the IMAGE_URL parameter to specify where the reports’
dynamically generated images can be accessed.
For example:
IMAGE_URL=http://server_or_web_server_name.domain_name:port/reports/rwservlet
This parameter is in place for JSPs that do not run via the Reports Servlet. It ensures
that dynamically generated images, such as charts, will be viewable only by the person
who runs the report. JSPs, and other report types, that run through the Reports Servlet
have this protection automatically.
3.3.13 Setting Expiration for Database and System Authentication Cookies
Use the COOKIEEXPIRE parameter to set the lifetime (in minutes) of the database and
system authentication cookie. For example:
COOKIEEXPIRE=20
The default is 30.
Cookies save encrypted user names and passwords on the client-side when users first
authenticate themselves. When the server receives a cookie from the client, the server
compares the time saved in the cookie with the current system time. If the time is
longer than the number of minutes defined in COOKIEEXPIRE, the server rejects the
cookie and returns to the client the authentication form along with an error message.
Users must re-authenticate to run the report.
3.3.14 Setting an Encryption Key for the Database and System Authentication Cookies
Use ENCRYPTIONKEY to specify the encryption key to be used to encrypt the user
name and password of the database and system authentication cookies. The
encryption key can be any character string. For example:
ENCRYPTIONKEY=egbdf
3.3.15 Adding Formatting to Diagnostic/Debugging Output
The DIAGBODYTAGS and DIAGHEADTAGS parameters are available for including
additional HTML encoding in the and tags in the output files
associated with diagnostic and debugging output.
DIAGBODYTAGS defines the entire tag; while DIAGHEADTAGS defines tags to
appear between the open and close / tags.
3-38 Oracle Application Server Reports Services Publishing Reports to the Web