Publishing Reports to the Web - Downloads - Oracle

7
Configuring Destinations for OracleAS
Reports Services
Two things to consider when you run a report are how the report should be output
(destination) and who should receive it (distribution). Distribution is discussed in
Chapter 15, "Creating Advanced Distributions". This chapter explores how OracleAS
Reports Services handles output processing to default and custom destinations. It
provides an overview of output processing and information on registering destination
types with the OracleAS Reports Services.
It includes the following sections:
■ Overview of Output Processing
■ Registering Destination Types with the Server
7.1 Overview of Output Processing
How the report should be output is controlled by the destype that you specify at
runtime, which, in turn, are determined by the destination output types you have
registered in your server configuration file (server_name.conf). You can register no
output types and simply use the default types provided by OracleAS Reports Services:
■ Cache (i.e., browser)
■ SMTP-compliant e-mail
■ File
■ Printer
■ OracleAS Portal (this is an exception in that, for access to the portal, it requires the
specification of a userid and password in the server configuration file)
You can also define custom output types, such as fax, Oracle's Internet File System
(iFS), or any type you define using the OracleAS Reports Services Destinations API.
This API enables you to define new destination types and build handlers to usher your
reports to custom destinations.
Note: Build a custom destination type via the OracleAS Reports
Services Destinations API. Look for upcoming information about
Oracle Reports APIs and destination types for download on the
Oracle Technology Network, (http://otn.oracle.com).
The OracleAS Reports Services architecture standardizes the way output is generated
and delivered. It takes responsibility for delivering report output to the appropriate
Configuring Destinations for OracleAS Reports Services 7-1