Publishing Reports to the Web - Downloads - Oracle

Configuring the URL Engine
You can use these to include formatting options to make diagnostic and debugging
output easier to read. For example:
DIAGBODYTAGS= [additional HTML encoding]
DIAGHEADTAGS=[additional HTML encoding]
3.3.16 Defining the rwservlet Help File
A HELP keyword is available with the rwservlet command for bringing up a
servlet-related help topic. The help file is invoked when you specify the following
URL:
http://your_web_server/your_servlet_path/rwservlet/help
We provide a default help file for the servlet, ORACLE_
HOME\reports\templates\help.htm, which will be displayed if you leave this
parameter undefined. You may want to supply a help file of your own. To do this,
specify the name and location URL of your servlet help file with the HELPURL
parameter in the servlet configuration file. For example:
HELPURL=http://your_web_server/your_help_file_path/helpfile.htm
3.3.17 Specifying the Use of OracleAS Single Sign-On
If you plan to take advantage of OracleAS Reports Services’ Single Sign-On capability,
you must ensure the SINGLESIGNON parameter is set to YES in the servlet
configuration file. SINGLESIGNON is set to YES by default upon installation.
For more information, refer to Enabling and Disabling OracleAS Single Sign-On.
3.4 Configuring the URL Engine
Note: For more about the HELP keyword, see Appendix A,
"Command Line Options".
Reports Server includes a URL engine that can take the contents of any URL and
distribute them. The URL engine allows you to leverage the powerful scheduling and
distribution capabilities of Reports Server to distribute content from any publicly
available URL to various destinations such as e-mail, OracleAS Portal, and WebDav.
Since Reports Server’s destinations are pluggable, you can also add your own custom
destinations for the URL content.
Furthermore, if you use the URL engine in conjunction with Reports Server’s
event-based APIs, database events can trigger the content distribution. For example,
suppose you have created a JSP report for high fidelity Web publishing of data stored
in a table containing employee expense data. You could then use the URL engine and
the event-based API to e-mail that JSP whenever the expense application stores new or
updated employee expense data in the table.
If the URL engine is not activated, you can activate it by doing the following:
1. Add an engine element for the URL engine to the server configuration file. For
example, your engine element might be as follows: