Oracle® Application Server Reports Services Publishing Reports to the Web
Part Number B13673-01
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:
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 (
conf). You can register no output types and simply use the default types provided by OracleAS Reports Services:
Cache (i.e., browser)
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, (
The OracleAS Reports Services architecture standardizes the way output is generated and delivered. It takes responsibility for delivering report output to the appropriate destination (via the Reports Server), yet generates output independent of its destination (via the Reports Engine). This provides a significant improvement in efficiency by allowing one run of a report to be used in a number of different ways. It also opens up the output processing architecture to allow for any number of destination types.
In the past, the Reports Runtime engine was totally responsible for delivering the output. Consequently, it had to know how to communicate with output destinations. This resulted in a tight coupling between the engine and the supported destinations.
OracleAS Reports Services eliminates this tight coupling and its attendant restrictions. The runtime engine now treats all destinations alike. It doesn't need to know the destination type for which the output is being produced. The server hands output off to destination handlers that prepare the material for delivery to their associated destination types. You can use predefined destination types (with predefined handlers) or create a handler for a custom destination type you intend to support. Almost any type of destination can be plugged into Oracle Reports.
Figure 7-1 illustrates the main components of the OracleAS Reports Services output processing architecture.
The user submits a request from a client or browser to the Reports Server.
The server passes it along to the runtime engine.
The runtime engine creates/processes the destination objects (which include file lists for specific destinations as well as any properties related to those destinations) and the report output; the runtime engine sends the destination objects to the Reports Server and the report output to cache.
The Reports Server sends the destination objects to the Reports Server's destination component.
The destination component of the Reports Server fetches the report output from cache.
Before OracleAS Reports Services can send a report to a particular destination type, the type must be a default type (printer, e-mail, cache, or file) or a type registered in the server's configuration file,
conf. The configuration file contains a
destination element for registering destination types that are valid for your reports. You can register anywhere from zero to any number of destination types.
These tasks are described in the following sections.
To set up a destination section in the
Open the server configuration file with your preferred text editor.
You'll find the server configuration file in the following directory (Windows and UNIX use the same path):
Note:The server configuration file follows the order of elements defined in the file's related document type definition file (
Use the following syntax to register all the destination types you will use for outputting reports:
<property name="valid_destype_property" value="valid_value"/ <property name="valid_destype_property" value="valid_value"/
</destination> <destination destype="output_type_2" class="java_class_2"
<property name="valid_destype_property" value="valid_value"/
The valid values for these tags are discussed in the following sections.
This section outlines the destinations supported by Oracle Reports.
class attributes are required for valid registration of a non-default output type. They specify the destination types and their associated Java classes. The predefined (default) destination types and classes that come with OracleAS Reports Services are listed in Table 7-1:
Table 7-1 Standard destination types and classes
|OracleAS Portal content area||
Contrary to the other default types, you must register an
oraclePortal destype. This is because the
oraclePortal destype requires the specification of a userid and password for accessing the portal.
See Also:Chapter A, " Command Line Options"
For examples on pushing a report using the
You are not limited to the predefined destypes and classes provided with the server. You can register custom destination types, such as a fax, once you have defined a custom handler (through the Destinations API).
Note:Look for upcoming information about Oracle Reports APIs on the Oracle Technology Network, (
The server configuration file allows the association of an unlimited number of properties with a registered destination. Destination properties consist of name/value pairs that define some aspect of an output type's configuration. They are expressed in terminology recognized by the destination type. For example, a destination with a destype of
oraclePortal would recognize the name/value pair:
<property name="portalUserid" value="portal_id/portal_password@portal_schema" confidential="yes" encrypted="no"/
This example defines the values to be associated with a portal user ID. It includes the attributes
confidential="yes", which indicate that the values within this element should be encrypted;
encrypted="no", which indicates that the values are not yet encrypted. The next time the Reports Server starts, it will automatically encrypt the values and reset
Note:Elements and attributes allowable in server configuration file are determined by the syntax defined in the
What is valid for a destination type's properties depends entirely on the destination type. These values do not come from Oracle Reports and are not put to use by the Reports Server. They come from the destination type itself and use terms the destination recognizes. It is up to the developer to understand the requirements of a custom destination and to know what properties to associate with a given custom output type.
When we begin to discuss distribution, you may note that within the distribution XML file, the
destype element also allows for the use of property name/value pairs. It's important to make a distinction between properties entered for a
destination element in the server configuration file and those entered for a
destype element in the distribution XML file:
Properties entered for a
destination element in the server configuration file should deal only with configuring an output type, for example setting an allowable number of retries for a destination fax.
Properties entered for a
destype element in the distribution XML file should deal only with specifying a runtime parameter, for example the identity of the fax's intended recipient.
The following example illustrate a
destination element for pushing content into OracleAS Portal:
<destination destype="oraclePortal" class="oracle.reports.server.DesOraclePortal" <property name="portalUserid" value="<the_username_password_tnsname_for_logon_to_portal>" encrypted="yes"/> </destination>