Publishing Reports to the Web - Downloads - Oracle

Defining Custom/Pluggable Destinations
Fax destination
You can specify the destination as per the generic tag structure in the distribution XML
file as follows:
Example 15–1 Generic Fax Destination
oraclePortal Destination
You can specify the destination as per the generic tag structure in the distribution XML
file as outlined in Example 15–2.
Example 15–2 illustrates a sample structure for DESTYPE=ORACLEPORTAL. When you
push a report output to Portal using DESTYPE=ORACLEPORTAL, the report output
will be created in the PAGEGROUP folder.
See Also: Command Line Options
For more information on the properties outlined in the examples.
Example 15–2 Simple Portal Destination
You can specify the custom destination in accordance with the generic destype tag
structure for a pluggable destination. Alternatively, for ease of use, you can specify a
custom, more specific tag structure.
Example 15–3 Custom Fax Destination
These tags are unknown to the distribution.dtd, therefore, they need to be
mapped to the generic destype tag structure specified in the distribution.dtd.
Reports runtime cannot process the tag structure as illustrated here because the
tag is not a standard destination specified in the distribution.dtd file. The
custom tag structure must therefore be converted to the generic format as shown in
Example 15–1.
Use the distribution.xsl file to transform user-defined custom tags in the
distribution XML file to a format required by Reports runtime. Reports can understand
only the generic destype tag structure for any pluggable destination.
The distribution.xsl file is an XML style sheet, located on both Windows and UNIX at
ORACLE_HOME\reports\conf\distribution.xsl. You can modify this file by
15-26 Oracle Application Server Reports Services Publishing Reports to the Web