The module mod_osso, used by the Oracle HTTP Server to connect to Single

2-6 Publishing Reports to the Web with Oracle Reports Services ■ The in-process Reports Server, which reduces the maintenance and administration of the Reports Server by providing a means for starting the server automatically, whenever it receives the first request from the client through rwservlet or a Reports JSP.

5. The Custom Tag Handler, which processes custom Oracle Reports tags included

in a JSP file. In a JSP file, Oracle Reports-related custom tags are identified by the prefix rw:; other custom tags using other prefixes may also be present.

6. The Reports Server rwserver, which processes client requests, including

ushering them through its various services, such as security authentication and authorization, job scheduling, caching, publishing, and bursting and distribution including distribution to custom—or pluggable—output destinations. The security service offers authentication based on the following methods: ■ Oracle Internet Directory ■ Java Platform Security JPS Oracle Internet Directory ■ Any LDAP-based ID Store using Java Platform Security JPS The security service offers authorization based on the following methods: ■ Java Platform Security JPS Oracle Internet Directory ■ XML file-based ■ Portal-based The bursting and distribution service enables the distribution of reports to multiple destinations, such as wireless, printer, FTP server, Portal, WebDAV, browser, and e-mail. The publishing service publishes Reports into multiple output formats, such as PDF, HTML, XML, and spreadsheet. The Reports Server also spawns runtime engines for generating requested reports, fetches completed reports from the Reports Server cache, and notifies the client that the job is ready. Reports output can be stored in the Reports cache or on a physical disk.

7. The Reports Server Cache, which securely stores completed job outputs.

8. The Reports Engine, which includes components for running SQL-based and

pluggable data source-based reports. It fetches requested data from the data source, formats the report, sends the output to cache, and notifies the Reports Server that the job is complete. The Reports engine also includes pluggable data sources, which are custom data sources like text, database, JDBC, OLAP, XML, and web services.

9. The pluggable data sources, a set of design-time and runtime Java APIs that

provide openness to Reports by enabling data input from numerous sources through the implementation of the PDS Java Interface. The PDS feature enables developers to leverage Reports’ aggregation, summarization, formatting, and scheduling capabilities not only on data that is accessed through SQL, but also on data that is available elsewhere.

10. The pluggable engines, which are custom engines that use Java APIs to pass jobs

to the Reports Server, as well as leverage the servers other features, such as scheduling, distribution, notification, and caching. Oracle Reports Services provides an out-of-the-box pluggable engine called the URL engine. The URL engine enables you to distribute content from any publicly available URL to destinations such as e-mail, Oracle Portal, and WebDAV. In addition to the Reports Services components, Figure 2–1 depicts the following: