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.

Using a Key Map File<br />

13.10.1 Usage Notes<br />

The job cache key excludes <strong>the</strong> destype, desname, server, and <strong>to</strong>lerance<br />

parameters, and includes almost all o<strong>the</strong>r parameters.<br />

This level of cache happens au<strong>to</strong>matically. You don’t need <strong>to</strong> specify any o<strong>the</strong>r<br />

parameters in <strong>the</strong> command line for it <strong>to</strong> work.<br />

■ If <strong>the</strong> user specifies TOLERANCE=n (where n is a number in units of minutes) in<br />

<strong>the</strong> new job request "A", and it doesn’t happen, <strong>the</strong>n <strong>Reports</strong> Server will try <strong>to</strong> find<br />

a job in <strong>the</strong> Finished Jobs Queue which was successfully completed within n<br />

minutes. If <strong>Reports</strong> Server can find such a job, <strong>the</strong>n <strong>the</strong> new job request "A" will<br />

return <strong>the</strong> output of job "B".<br />

■ In a clustered environment, duplicate job checking (i.e., jobs with <strong>the</strong> same cache<br />

key) is executed across cluster members. If a duplicate job is found in ano<strong>the</strong>r<br />

server in <strong>the</strong> same cluster, <strong>the</strong> job request will be transferred <strong>to</strong> that server <strong>to</strong><br />

retrieve <strong>the</strong> cached result.<br />

<strong>Oracle</strong>AS <strong>Reports</strong> Services cache results are persistent. If <strong>the</strong> <strong>Reports</strong> Server is shut<br />

down, once it is up again all <strong>the</strong> previous cache results are recovered and ready <strong>to</strong><br />

use again.<br />

■ You can set <strong>the</strong> cache size through <strong>Reports</strong> Queue Manager or via <strong>the</strong> cache<br />

element in <strong>the</strong> server configuration file (server_name.conf). <strong>Reports</strong> Server<br />

attempts <strong>to</strong> keep <strong>the</strong> <strong>to</strong>tal size of cache files below <strong>the</strong> set limit, deleting <strong>the</strong> oldest<br />

cache files. In addition, you can empty <strong>the</strong> cache through <strong>Reports</strong> Queue Manager.<br />

For more information on setting <strong>the</strong> cache, refer <strong>to</strong> <strong>the</strong> <strong>Reports</strong> Queue Manager<br />

online help, and see Configuring <strong>Oracle</strong>AS <strong>Reports</strong> Services.<br />

13.11 Using a Key Map File<br />

Note: Refer <strong>to</strong> Command Line Options for more information<br />

about <strong>the</strong> TOLERANCE command line option.<br />

If you choose <strong>to</strong> provide users with a URL or add a hyperlink <strong>to</strong> a <strong>Web</strong> site, <strong>the</strong>n you<br />

can use a key map file <strong>to</strong> simplify or hide parameters in your URL requests.<br />

The key map file contains command strings for running reports, each headed by a<br />

unique key identifier. Except when you run a report as a JSP, you reference only this<br />

key in <strong>the</strong> runtime URL. The server or servlet sends <strong>the</strong> key value <strong>to</strong> <strong>the</strong> map file<br />

(cgicmd.dat), which in turn returns <strong>the</strong> command associated with <strong>the</strong> specified key<br />

<strong>to</strong> <strong>the</strong> server or servlet for processing. By using key mapping, <strong>the</strong> command line<br />

options are all hidden from <strong>the</strong> user.<br />

Key mapping is useful for:<br />

■ Shortening <strong>the</strong> URL, making it more convenient <strong>to</strong> use<br />

■ Remapping <strong>the</strong> runtime commands without having <strong>to</strong> change <strong>the</strong> original URL<br />

■ Standardizing several typical run configurations for your company<br />

■ Hiding certain parameters from users (for example, <strong>the</strong> database connect string)<br />

■ Restricting <strong>the</strong> parameters users can use <strong>to</strong> run a report<br />

When you specify a key name from <strong>the</strong> key map file (cgicmd.dat), it must always be<br />

at <strong>the</strong> beginning of <strong>the</strong> query string (after <strong>the</strong> question mark) in a report request URL.<br />

13-18 <strong>Oracle</strong> Application Server <strong>Reports</strong> Services <strong>Publishing</strong> <strong>Reports</strong> <strong>to</strong> <strong>the</strong> <strong>Web</strong>

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

Saved successfully!

Ooh no, something went wrong!