Running Reports Through a Web Service

Running Report Requests 18-15 Oracle Reports Services cache results are persistent. If the Reports Server is shut down, once it is up again all the previous cache results are recovered and ready to use again.

18.12.1 Usage Note

You can set the cache size through Reports Queue Manager rwrqm on Windows, or rwrqv.sh on Solaris or through the cache element in the server configuration file rwserver.conf. Reports Server attempts to keep the total size of cache files below the set limit, deleting the oldest cache files. In addition, you can empty the cache through Reports Queue Manager. For more information on setting the cache, refer to the Reports Queue Manager online Help, and see Chapter 8, Configuring Oracle Reports Services .

18.13 Using a Key Map File

If you choose to provide users with a URL or add a hyperlink to a Web site, then you can use a key map file to simplify or hide parameters in your URL requests. This section provides the following information: ■ Understanding Key Mapping ■ Enabling Key Mapping ■ Adding Key Mapping Entries to a Key Map File ■ Using a Key with Non-JSP Reports ■ Using a Key with a Report Run as a JSP

18.13.1 Understanding Key Mapping

The key map file contains command strings for running reports, each headed by a unique key identifier. Except when you run a report as a JSP, you reference only this key in the runtime URL. Oracle Reports Servlet rwservlet sends the key value to the key map file cgicmd.dat, which in turn returns the command associated with the specified key to rwservlet for processing. By using key mapping, the command line options are all hidden from the user. Key mapping is useful for: ■ Shortening the URL, making it more convenient to use. ■ Remapping the runtime commands without having to change the original URL. ■ Standardizing several typical run configurations for your company. ■ Hiding certain parameters from users for example, the database connect string. ■ Restricting the parameters users can use to run a report. When you specify a key name from the key map file cgicmd.dat, it must always be at the beginning of the query string after the question mark in a report request URL. An exception to this is if you use the CMDKEY command line keyword, and express the key name as its value: CMDKEY=keyname. In this case, you can place the key name anywhere in the query string within the report request URL. The CMDKEY keyword can be used with jobs run as JSPs and with the rwservlet command. Note: Refer to Section A.8.22, TOLERANCE for more information.