Publishing Reports to the Web - Downloads - Oracle

Using a Key Map File
The key mapping file might contain:
KEY: REPORT=myreport DEPTNO=%1 MYPARAM=%2 %*
This would generate the equivalent of the following command line request:
rwclient REPORT=myreport DEPTNO=par1 MYPARAM=par2 parN
Usage Notes
■ In rwcgi URLs, the first option (that is the first information after the question
mark) is treated as a key if it is not otherwise a part of a name/value pair. If the
first option is not a name/value pair (i.e., keyword=value), then the whole
command line is used in lieu of a cgicmd.dat key entry.
13.11.4 Using a Key with a Report Run as a JSP
When you run a report as a JSP and want to call a command key in the cgicmd.dat
file, you must use the cmdkey keyword in your URL. For example, your JSP URL
might look like this:
http://…/myreport.jsp?cmdkey=key
When you use cmdkey with a JSP or rwservlet, you can place it anywhere within
the query string. For example:
http://…/example.jsp?parameter1=value1&cmdkey=keyname
http://…/rwservlet?parameter1=value1&cmdkey=keyname
Usage Notes
Note: You can also use cmdkey with the rwservlet command.
■ When using key mapping, the order in which the parameters are substituted from
the URL into the key is determined by the placement of CMDKEY in the URL. For
example, suppose you have a key such as the following one in the cgicmd.dat
file:
mykeys: DEPTNO=%1 MYPARAM=%2
Now, you execute a JSP report that references this key as follows:
http://neptune.world.com:80/jsp/myreport.jsp?userid=scott/tiger@hrdb
&cmdkey=mykeys&10&test
Because of the placement of CMDKEY in this URL, the 10 corresponds to %1 and
test corresponds to %2. Even though they are not the first and second parameters
in the URL, 10 and test are the first and second parameters to follow CMDKEY in
the URL.
13-20 Oracle Application Server Reports Services Publishing Reports to the Web