01.02.2013 Views

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Usage Notes<br />

Environment Variables<br />

■ The default value for <strong>the</strong> environment variable is required for <strong>Oracle</strong> <strong>Reports</strong><br />

executables <strong>to</strong> function correctly. Additional user classes may be appended, but<br />

<strong>the</strong> list must conform <strong>to</strong> <strong>the</strong> platform-specific Java CLASSPATH definition.<br />

Example<br />

REPORTS_CLASSPATH=%ORACLE_HOME%\reports\jlib\rwbuilder.jar;<br />

%ORACLE_HOME%\reports\jlib\rwrun.jar;%ORACLE_<br />

HOME%\jlib\zrclient.jar;%ORACLE_<br />

HOME%\j2ee\home\oc4j.jar;%ORACLE_HOME%\j2ee\home\lib\ojsp.jar<br />

■ <strong>Reports</strong> Builder will fail if <strong>the</strong> value of <strong>the</strong> REPORTS_CLASSPATH environment<br />

variable (registry) exceeds 511 characters. To workaround this issue, you can use<br />

<strong>the</strong> CLASSPATH environment variable (system) <strong>to</strong> specify a value in excess of 511<br />

characters.<br />

B.1.37 REPORTS_COOKIE_EXPIRE *<br />

Description This environment variable specifies <strong>the</strong> lifetime of a cookie within a<br />

given <strong>Reports</strong> Server session.<br />

If Single Sign-On is not being used, <strong>the</strong>n any user accessing a secured instance of <strong>the</strong><br />

<strong>Reports</strong> Server is challenged <strong>to</strong> identify <strong>the</strong>mselves by rwservlet via its own<br />

au<strong>the</strong>ntication mechanism (identical <strong>to</strong> <strong>the</strong> behavior of <strong>Oracle</strong> <strong>Reports</strong>6i). Because <strong>the</strong><br />

HTTP 1.0 pro<strong>to</strong>col is stateless (i.e., each call <strong>to</strong> <strong>the</strong> server is effectively independent of<br />

all o<strong>the</strong>rs), users might need <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves for each report request unless<br />

a cookie is maintained.<br />

To allow users <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves only once per session, rwservlet has its own<br />

client-side cookie, <strong>the</strong> authid cookie, in which it s<strong>to</strong>res <strong>the</strong> required au<strong>the</strong>ntication<br />

information for <strong>the</strong> current session. Once <strong>the</strong> user is au<strong>the</strong>nticated, an encrypted<br />

cookie is created in <strong>the</strong> browser <strong>to</strong> enable <strong>the</strong> user <strong>to</strong> submit multiple report jobs<br />

without re-au<strong>the</strong>nticating for each request. The authid cookies are terminated when<br />

<strong>the</strong> user closes <strong>the</strong>ir browser session, but you should not rely strictly on this method of<br />

terminating <strong>the</strong> cookie. You should limit <strong>the</strong> lifetime of <strong>the</strong> cookie within a given<br />

session using <strong>the</strong> REPORTS_COOKIE_EXPIRE environment variable. For example, a<br />

user might log on and <strong>the</strong>n go <strong>to</strong> lunch, leaving <strong>the</strong> browser session open. To minimize<br />

<strong>the</strong> potential for a security breach in this situation, <strong>the</strong> administra<strong>to</strong>r may define <strong>the</strong><br />

REPORTS_COOKIE_EXPIRE environment variable on <strong>the</strong> <strong>Reports</strong> Server. When<br />

rwservlet receives a job request, it compares <strong>the</strong> time saved in <strong>the</strong> cookie with <strong>the</strong><br />

current system time. If <strong>the</strong> time is longer than <strong>the</strong> number of minutes defined in <strong>the</strong><br />

environment variable (e.g., 30 minutes), <strong>the</strong> cookie is rejected and <strong>the</strong> user is<br />

challenged <strong>to</strong> provide au<strong>the</strong>ntication information.<br />

Valid Values Any number of minutes.<br />

Default 30<br />

Note: If you want <strong>to</strong> force users <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves for a<br />

specific report, you can use <strong>the</strong> SHOWAUTH command line keyword.<br />

Alternatively, you can include a %S in <strong>the</strong> corresponding report<br />

entry in <strong>the</strong> key map file. This file is usually called cgicmd.dat<br />

and is located in ORACLE_HOME\reports\conf. %S forces users<br />

<strong>to</strong> enter <strong>the</strong>ir user name and password each time <strong>the</strong> report is<br />

called.<br />

<strong>Reports</strong>-Related Environment Variables B-13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!