Reports Server includes a URL engine that can take the contents of any URL and distribute them. The URL engine enables 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, Oracle 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:
Add an engine element for the URL engine to the server configuration file. For example, your engine element might be as follows:
<engine id="rwURLEng" class="oracle.reports.engine.URLEngineImpl" initEngine="1" maxEngine="1" minEngine="0" engLife="50" maxIdle="30" callbackTimeOut="60000" />
Add a job element that associates the appropriate job types with the URL engine to the server configuration file. For example, your
job element might be as follows:
<job jobType="rwurl" engineId="rwURLEng"/>
Stop and restart Reports Server.
Note:When you restart your Reports Server with these new elements, you should see the number of engines increase accordingly in the Reports Server status message box. In the preceding example, the number of engines would increase by one (the value of
initEngine) when you restart Reports Server.
To learn about sending requests to the URL engine, refer to Chapter 17, "Running Report Requests".