; Example cgicmd.dat Mapping file for Oracle Reports 6i Web Interface Component (rwcgi60.exe/rwcgim60) ; ; Key mapping file (CGICMD.DAT) ; ; CGICMD.DAT Syntax: Each key entry is defined as ; ; KEY : VALUE ; ; Where: ; ; KEY - the first argument of the RWCGI60 URL request (case insensitive); ; ; VALUE - command line parameters or special parameters combination. ; ; Extra spaces are ignored. Multi-line entries allowed. ; Multiple keys separated by an extra empty line. ; ; Line started with ";" character is treated as a comment and ignored. ; ; Comments inside a key or key value are NOT allowed. I.e., comments are only can be used between key definitions. ; Note: extra empty line is always required to separate different keys. ; ; NLS language support is provided and can be used (encoding should match the one used in HTML request - no language conversion ; of any kind is attempted. ; ; In addition to Reports Server command line parameters, VALUE can include special parameters, represented as "%X", where ; X identifies the parameter. ; ; Currently recognized special parameters: ; ; %0 - %9 - 0..9 arguments from original RWCGI60 URL request. Note that %0 refers to the key itself. ; %* - entire contents (all arguments) of original RWCGI60 URL request. ; %P - request for report parameter form in HTML format. It generates the PARAMFORM=HTML construction on the first submission ; of the URL and PARAMFORM=NO on the parameter form submission. ; %PT - request for report parameter form in HTMLTABLE format. It generates the PARAMFORM=HTMLTABLE construction on the ; first submission of the URL and PARAMFORM=NO on the parameter form submission. ; %PC - request for report parameter form in HTMLCSS format. It generates the PARAMFORM=HTMLCSS construction on the first ; submission of the URL and PARAMFORM=NO on the parameter form submission. ; %D - request users to input database userid everytime they run the report. ; ; Notes; ; ; 1.The HTML format is by default, mapped to the HTMLTABLE format in this release. The HTML format in the future may be ; mapped to the HTMLCSS format. ; ; 2.The HTMLCSS format is supported only by some browsers, including Internet Explorer 3.0.1 or later, ; and Netscape 4.x or later. It is not supported by Netscape 3.0.x. ; ; History ; ; PNARTH 11-Dec-98 Removed Reports 3 references, and added comments for the dummy entry ; JITANG 27-Jun-99 Removed dummy entry and associated comments. Dummy report is no longer used in ; Reports 6i ; Example 1: Run a simple breakb report and output to HTML ; A corresponding URL to this might look like: http://appserver.com/ows-bin/rwcgi60.exe?breakb orqa: report=breakb.rdf destype=cache desformat=html server=repserver ; Example 2: use %D to require user authentication every time report_secure: report=breakb.rdf destype=cache desformat=html server=repserver %D ; Example 3: use dababase userid stored in the cookie report_defaultid: report=breakb.rdf destype=cache desformat=html server=repserver ; Example 4: Take all arguments from URL request and send it to the reports server (servername specified in the URL) run: %* ; Example 5: Run breakb report with HTML parameter form. breakbparam : report=breakb.rdf destype=cache desformat=html server=repserver userid=scott/tiger@OR72 %P ; Example 6: take all URL arguments, and also generate a HTML parameter form runp=: %* %P ; Example 7: Run an Express Report. Replace with the name of the machine running the Express server. The ; builder on-line help explains the rest of the parameters (the /sl, st etc. etc.) express: report=my_expr_rep server=repserver express_server="server=ncacn_ip_tcp:/sl=1/st=1/ct=0/sv=1/" desformat=htmlcss userid=scott/tiger@mydb destype=cache