15 Creating Advanced Distributions

15.2.1 The distribution.dtd File

When you create a distribution XML file, you follow the syntax defined in the distribution.dtd file located in the following directory on both Windows and UNIX:

ORACLE_HOME\reports\dtd

As you look through the following sections, it may be useful to you to print the distribution.dtd file and refer to it as various elements and attributes are described.

The distribution.dtd file lists all elements that are valid within a distribution XML file. Each of these elements have attributes. Attributes that come with default values need not be specified, unless you wish to override the default.

You can create a dynamic distribution by introducing variable values into many different attributes. Variable values reference columns that are present in the report that is using the distribution XML file.

15.2.2 Using Variables Within Attributes

You can use variables within attributes by entering &column_name or &<column_name> in the place of a static value.

<mail id="a1" to="&<manager>@mycompany.com" …

<mail id="a1" to="&amp;&lt;manager&gt;@mycompany.com" …>

The variable syntax you use depends on whether the value is expressed by itself or in combination with other values or strings. For example, a value for a to attribute in a mail element might be expressed as either:

<mail id="a2" to="&amp;email" …>

or

<mail id="a3" to="&amp;&lt;first_name&gt;.&amp;&lt;last_name&gt;@myco.com …>

In the first example (id="a2"), the variable's referenced column (email) contains a full e-mail address and does not require additional information. The second example (id="a3") uses a combination of variable values (first_name and last_name) and static text to construct an e-mail address (static text is the period after first_name and @myco.com). In both cases, you will get dynamic e-mail addressing. The example you use will depend on whether the variable contains all the information you need or requires additional information in order to be complete.

For more complex layouts, you can also reference report columns you created with PL/SQL formulas. For example, in your report you may define the PL/SQL column:

PL/SQL formula CF_MAILID: return(:first_name||'.'||:last_name)

You'd reference this column in the distribution XML file as:

to="&<CF_MAILID>@mycompany.com"

15.3.1 destinations

Example

<destinations>

  one or more distribution specifications

</destinations>

Required/Optional

Required. You must have no more or less than one destinations element in your distribution XML file.

Description

The destinations element opens and closes the content area of the distribution XML file. In terms of the distribution XML file's tagging hierarchy, all the other elements are subordinate to the destinations element.

15.3.2 foreach

Example

<foreach>
  <mail id="a1" to="my_addressee@mycompany.com" subject="Fourth Quarter Results">
    <attach format="pdf" name="dept_&amp;&lt;department_ID&gt;.pdf' 
        srcType="report" instance="this">
      <include src="mainSection"/>
    </attach>
  </mail>
</foreach>

or

<mail id="a4" to="recipient@mycompany.com" subject="Regional Results">
  <foreach>
    <attach format="pdf" name="report.pdf" srcType="report" instance="all">
      <include src="mainSection"/>
    </attach>
  </foreach>
</mail>

Required/Optional

Optional. You can have as many foreach elements as you require.

Description

Use the foreach element to burst your distribution against a repeating group. You can use foreach only when the associated report definition file (either RDF, JSP, or XML) has its Repeat On property for the section that will be burst set to an appropriate group. The foreach element specifies that the distribution defined between its open and close tags should be performed for each repeating group.

The Repeat On property can be set for a report section (Header, Main, and Trailer) to associate a data model break group to a section. By setting the Repeat On property for a section, you can generate multiple instances of a section, or a repeating section.

When you implement bursting and distribution in a report, you can generate section-level distribution by setting the Repeat On property for a section to a data model break group, which generates an instance of the section for each column record of that break group. Then, you can distribute each instance of the section as appropriate (for example, to individual managers in the MANAGER group).

If you set the Repeat On property for more than one of the Header, Main, and Trailer sections of a report, all Repeat On property values must be set to the same data model break group. If the Repeat On property for any one of the Header, Main, and Trailer sections is set to a different data model break group, Oracle Reports raises the following messages:

REP-177: Error while running in remote server
REP-34320: Report sections used in destination '<destination id>' do not repeat on the same group

You can also use the foreach element as a sub-element of the mail element, as depicted in the second example provided at the start of this section. (In this example, assuming that mainSection repeats on G_DEPARTMENT_ID, the example will produce a single attachment with all the instances of the report's mainSection in a single file.)

The foreach element works closely with the instance attribute of the attach and file elements. While foreach specifies that the distribution should be performed according to record groups, instance specifies whether the burst groups should be distributed in one file (instance="all") or distributed as separate files: one file for each group instance (instance="this").

When used with the mail element, foreach can mean different things according to its position relative to the mail element:

• When foreach precedes the mail element and instance="this", each group instance is dispatched as a separate mail. For example:

  <foreach>
    <mail id="a1" to="managers@mycompany.com" subject="results">
      <attach name="department_&amp;&lt;department_id&gt;.pdf" instance="this">
        <include src="mainSection" />
      </attach>
    </mail>
  </foreach>
  
  

  If the report is grouped according to department_id, and there are four departments, then there are four group instances. This means four e-mails per recipient, each e-mail with its own group instance attached: one e-mail has department 10's report attached; another e-mail has department 20's report attached; and so on. Each recipient receives all four e-mails.

• When foreach follows the mail element and instance="this", each group instance is attached to one e-mail going to each recipient. For example:

  <mail id="a1" to="managers@mycompany.com" subject="results">
    <foreach>
      <attach name="department_&amp;&lt;department_id&gt;.pdf" instance="this">
        <include src="mainSection" />
      </attach>
    </foreach>
  </mail>
  

15.3.3 mail

Example

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="text">
    Attached are quarterly results.
  </body>
  <attach srcType="report">
    <include src="headerSection"/>
    <include src="mainSection"/>
  </attach>
</mail>

or

<mail id="a4" to="recipient@mycompany.com" subject="Regional Results">
  <foreach>
    <attach format="pdf" name="report.pdf" srcType="report" instance="this">
      <include src="mainSection"/>
    </attach>
  </foreach>
</mail>

Required/Optional

Optional. You can have as many mail elements as you require.

Description

Use the mail element to specify distributions through an outgoing SMTP-based mail server. Use it to specify the recipients, the subject, and the priority of the e-mail.

Between an open and close tag of the mail element, there can be only one body sub-element and anywhere from zero to multiple attach and foreach sub-elements.

The mail element also has a set of related attributes. These are expressed within the mail tag. For example, the id, to, and subject attributes are expressed:

<mail id="a1" to="jsmith@foo.com" subject="Recent Hires">

Table 15-1 lists and describes the attributes of the mail element.

<pluginParam name=mailServer>smtp01.mycorp.com</pluginParam>

15.3.4 body

Example

On Windows 

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="file">
    <include src="c:\mail\body.html"/>
  </body>
</mail>

On UNIX 

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="file">
    <include src="/mail/body.html"/>
  </body>
</mail>

Required/Optional

Optional. You can have a maximum of one body element associated with a given mail element.

Description

The body element acts as a sub-element to the mail element. It specifies the content (or body) of the e-mail. With body, you can type a text string between the open and close tags of the body element or use an include sub-element to specify either an external file, a report, or a section of a report. For example:

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="text">
    Attached are quarterly results.
  </body>
…

or

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="file">
    <include src="d:/reports/admin/results.html"/>
  </body>
…

or

<mail id="a1" to="&amp;&lt;first_name&gt;.&amp;&lt;last_name&gt;@myco.com"   
    subject="Quarterly Results">
  <body srcType="report" format="html">
    <include src="headerSection"/>
  </body>
…

The body element has three attributes: srcType, format, and instance, described in Table 15-2.

15.3.5 attach

Example

<mail id="a1" to="jsmith@foo.com" subject="Results">
  <body srcType="text">

    Attached are quarterly results.

  </body>
  <foreach>

    <attach format="html" name="contacts.htm" srcType="report" instance="all">

      <include src="headerSection"/>
      <include src="mainSection"/>

    </attach>

  </foreach>

</mail>

Required/Optional

Optional. You can have as many attach elements as you require with a mail element. Note that attach is also a sub-element of foreach, and foreach requires that at least one of its sub-elements be used (out of mail,file,printer,destype,and attach).

Description

The attach element specifies attachments to the e-mail. Additionally, attach must have at least one include sub-element, and can have more than one if srcType="report".

Table 15-3 lists and describes the attributes of the attach element.

Using these attributes in conjunction with the foreach element, you can design a destination that will repeat on a group instance and generate an e-mail for each group attachment. For example:

<foreach>

  <mail id="a2" to="first.name@myco.com,second.name@myco.com, third.name@myco.com, 
      fourth.name@myco.com" subject="Department Summaries">

    <body srcType="text">

      Attached is the breakdown of department summaries for the last quarter.

    </body>
    <attach format="htmlcss" name="deptsum.html" srcType="report" instance="this">

      <include src="report"/>

    </attach>    

  </mail>

</foreach>

By moving the location of the foreach element, you can generate one e-mail with multiple attachments: a separate one for each group instance.

<mail id="a2" to="first.name@myco.com,second.name@myco.com, third.name@myco.com, 
    fourth.name@myco.com" subject="Department Summaries">

  <body srcType="text">

    Attached is the breakdown of department summaries for the last quarter.

  </body>
  <foreach>

    <attach format="htmlcss" name="deptsum.html" srcType="report" instance="this">

       <include src="report"/>

    </attach>

  </foreach>

</mail>

15.3.6 include

Example

<mail id="a1" to="jsmith@foo.com" subject="Q4">

  <body srcType="text">

    Attached are quarterly results.

  </body>
  <attach srcType="report" format="pdf">

    <include src="report"/>

  </attach>

</mail>

or

<mail id="a1" to="jsmith@foo.com" subject="Q4">

  <body srcType="text">

    Attached are quarterly results.

  </body>
  <attach srcType="report" format="htmlcss">

    <include src="headerSection"/>

  </attach>

</mail>

or

<mail id="a1" to="jsmith@foo.com" subject="Q4">

  <body srcType="text">

    Attached are quarterly results.

  </body>
  <attach srcType="file">

    <include src="d:/management/reports/current/Q4.htm"/>

  </attach>

</mail>

Required/Optional

Required when used with body and attach when srcType is report or file, but not when srcType is text. Also required for file, printer, and destype. In the instances where it is required, you must have one and can have more than one include.

Description

The include element is available for use with the body, attach, file, printer, and destype elements. It specifies the file, report, or report section to be included in the body of an e-mail, as an attachment to an e-mail, in the content of a file, in the printer output, or in the content of a custom destination type.

If you want to specify more than one section, but not the entire report, enter an include for each required section. For example:

<mail id="a1" to="jsmith@foo.com" subject="Results">

  <body srcType="text">

    Attached are quarterly results.

  </body>
  <attach srcType="report" format="htmlcss">

    <include src="headerSection"/>
    <include src="mainSection"/>

  </attach>

</mail>

If the preceding body or attach element has srcType of file, the subsequent include can specify the file either with a directory path and filename or with just the filename, provided the file is located in a directory listed in the REPORTS_PATH environment variable. For example:

<mail id="a1" to="jsmith@foo.com">

  <body srcType="file">

    <include src="q4sales.pdf"/>

  </body>

</mail>

If you do specify a path, use the appropriate standard for your platform. For example:

On Windows: 

<include src="c:\management\reports\current\Q4.htm"/>

On UNIX: 

<include src="/management/reports/current/Q4.htm"/>

No other XML elements are placed between an include element's open and close tag.

Table 15-4 describes the src attribute of the include element.

15.3.7 file

Example

On Windows 

<file id="a7" name="c:\management\reports\report.pdf" format="pdf">

  <include src="report"/>

</file>

On UNIX 

<file id="a7" name="/management/reports/report.pdf" format="pdf">

  <include src="report"/>

</file>

or

<foreach>

  <file id="a7" name="section&amp;&lt;department_id&gt;.pdf" format="pdf" 
      instance="this">

    <include src="mainSection"/>

  </file>

</foreach>

Required/Optional

Optional. You can have as many file elements as you require.

Description

Use the file element to specify distributions to a file. The file element has one sub-element: include. There must be at least one include sub-element and there may be more between an open and close tag of the file element.

When used with the foreach element and the instance="this" attribute, the file element can distribute each group instance of a grouped report to separate files. For example, if you group a report on department_id, and there are four departments, you can use the foreach/file/instance="this" combination to generate four files, each with a separate department's report. In this case, the file entry in the distribution XML file might look like this:

<foreach>

  <file id="a3" name="dept_&amp;&lt;department_id&gt;.pdf" format="pdf" 
      instance="this">
    <include src="report"/>

  </file>

</foreach>

In this example, all report sections (header, main, and trailer) must repeat on the same group instance (for example, department_id).

Table 15-5 lists and describes the attributes of the file element.

15.3.8 printer

Example

On Windows 

<printer id="a1" name="\\server_name\printer_name" copies="5">

  <include src="report"/>

</printer>

On UNIX 

<printer id="a1" name="alias_to_registered_printer" copies="5" instance="all">

  <include src="report"/>

</printer>

Required/Optional

Optional. You can have as many printer elements as you require.

Description

Use the printer element to specify distributions to a printer. The printer element has one sub-element: include. There must be at least one include sub-element and there may be more between the open and close tags of the printer element.

When used with the foreach element and the instance="this" attribute, the printer element can distribute each group instance of a grouped report to a separate print job. For example, if you group a report on department_id, and there are four departments, you can use the foreach/printer/instance="this" combination to generate four printed reports, each containing a separate department's report. In this case, the printer entry in the distribution XML file might look like this:

<foreach>

  <printer id="a7" name="\\server_name\printer_name" instance="this">

    <include src="report"/>

  </printer>

</foreach>

In this example, all report sections (header, main, and trailer) must repeat on the same group instance (for example, department_id).

Table 15-6 lists and describes the attributes of the printer element.

15.3.9 destype

Example

<destype id="acustom1" name="fax">

  <include src="headerSection"/>
  <property name="number" value="914925551212"/>
</destype>

See Section 15.4, "Distribution XML File Examples" for examples of using the destype element in a distribution.xml file to specify distribution to the following destinations: OracleAS Portal, FTP, WebDAV, and fax.

Required/Optional

Optional. You can have as many destype elements as you require.

Description

Use the destype element to specify distribution to a custom destination, such as a fax machine or an FTP site. You also use destype to specify distribution to a portal created with OracleAS Portal. The destype element allows for the use of two sub-elements: property and include. At least one include is required.

When used with the foreach element and the instance="this" attribute, the destype element can distribute each group instance of a grouped report to a separate destype instance (for example, a separate fax). For example, if you group a report on department_id, and there are four departments, you can generate four destype instances, each containing a separate department's report. In this case, the destype entry in the distribution XML file might look like this:

<foreach>

  <destype id="a9" name="fax" instance="this">

    <include src="report"/>
    <property name="number" value="&amp;&lt;fax_number&gt;"/>

  </destype>

</foreach>

In this example, all report sections (header, main, and trailer) must repeat on the same group instance (for example, fax_number).

Custom destination types also have a set of related attributes. These are expressed within the destype tag. For example, the id, name, and instance attributes are expressed:

<foreach>

  <destype id="a1" name="name_of_destination_type" instance="all">
    <include src='report'/>
  </destype>

</foreach>

Table 15-7 lists and describes the attributes of the destype element.

15.3.10 property

Example

<foreach>

  <destype id="custom1" name="fax" instance="all">

    <include src="headerSection"/>
    <property name="number" value="914925551212"/>

  </destype>

</foreach>

Required/Optional

Optional. You can have as many properties as you require under a destype element.

Description

The property element allows for the inclusion of name/value pairs expressed in terms recognized by a custom destination type (destype). Properties are merely passed along to the destination handler. They serve no function within OracleAS Reports Services. How you specify properties is entirely dependent on the requirements of your custom destination.

15.4.1 foreach Examples

The examples in this section include:

• Single E-Mail with Report Groups as Separate Attachments

• Separate E-Mail for Each Group Instance

• Separate E-Mails with Separate Sections as Attachments

• Separate File for Each Section

• Separate Print Run for Each Report

<mail id="a1" to="managers@mycompany.com" subject="New Hires">

  <foreach>

    <attach format="html" srcType="report" instance="this">

      <include src="report"/>

    </attach>

  </foreach>

</mail>

<foreach>

  <mail id="weeklies" to="managers@mycompany.com">

    <attach format="htmlcss" srcType="report" instance="this">

      <include src="mainSection"/>

    </attach>

  </mail>

</foreach>

<foreach>

  <mail id="a6" to="managers@mycompany.com" subject="Personnel Reports">

    <attach format="pdf" name="attach.pdf" srcType="report" instance="this">

      <include src="mainSection"/>

    </attach>
    <attach format="rtf" name="attach.rtf" srcType="report" instance="this">

      <include src="trailerSection"/>

    </attach>

  </mail>

</foreach>

<foreach>

  <file id="a10" name="department_&amp;&lt;department_id&gt;.pdf" instance="this">

    <include src="mainSection"/>

  </file>

</foreach>

<foreach>

  <printer id="a7" name="\\server_name\printer_name" instance="this">

    <include src="report"/>

  </printer>

</foreach>

<foreach>

  <printer id="a7" name="printer_alias" instance="this">

    <include src="report"/>

  </printer>

</foreach>

15.4.2 mail Examples

The examples in this section include:

• E-Mail with a Whole Report as the Body

• E-Mail with a Section of a Report as the Body

• E-Mail with Two Report Sections as the Body

• E-Mail with External File as Body and Report as Attachment

• E-Mail with Whole Report and Grouped Sections Attached

• E-Mail to Relevant Manager and Department

<mail id="a5" to="managers@mycompany.com" subject="Quarterly Report">

<body srcType="report" format="html">

<include src="report"/>

</body>

</mail>

<mail id="a6" to="employees@mycompany.com">

<body srcType="report" format="html">

<include src="mainSection"/>

</body>

</mail>

<mail id="emp_addresses" to="employees@mycompany.com" subject="Employee Address List">

<body srcType="report" format="html">

<include src="headerSection"/>
<include src="mainSection"/>

</body>

</mail>

<mail id="XQRSN" to="accounting@mycompany.com" subject="Salaries"

<body srcType="file">

<include src="c:\mail\body.html"/>

</body>
<attach format="pdf" name="salaries.pdf" srcType="report">

<include src="report"/>

</attach>

</mail>

<mail id="XQRSN" to="accounting@mycompany.com" subject="Salaries"

<body srcType="file">

<include src="/mail/body.html"/>

</body>
<attach format="pdf" name="salaries.pdf" srcType="report">

<include src="report"/>

</attach>

</mail>

<mail id="grx90" to="sales@mycompany.com">

<body srcType="text">
Attached you will find the summary report and breakdown by department of weekly totals.
</body>
<attach format="rtf" name="myAttach.rtf" srcType="report">

<include src="report"/>

</attach>
<foreach>

<attach format="pdf" name="myattach.pdf" srcType="report" instance="this">

<include src="mainSection"/>

</attach>

</foreach>

</mail>

<foreach>

<mail id="mgr1090" to="&amp;&lt;manager&gt;@mycompany.com">

<attach format="pdf" name="attach.pdf" srcType="report" instance="this">

<include src="mainSection"/>

</attach>

</mail>

</foreach>

15.4.3 file Examples

Whenever you burst and distribute grouped reports to files, be sure to specify filenames with variable values based on the repeating group or some other variable information. Otherwise, you run the risk of having each successive file that is created overwrite the previously created file. For example, if you specify an output filename of department.pdf, and you output separate instances of each department's report, the second department.pdf file will overwrite the first department.pdf file; the third will overwrite the second; an so on. You will end up with only one report, that of the final department to be output. Instead, with grouped reports that you want to output separately according to each group instance, use variable values to specify filenames, for example: name="department_&<department_id>.pdf".

The examples in this section include:

• File for Whole Report

• File for Combined Report Sections

• File for Each Group of Combined Sections

• File for Each Report Group Instance

<file id="a1" name="c:\reports\report.pdf" format="pdf">

<include src="report"/>

</file>

<file id="a1" name="/reports/report.pdf" format="pdf">

<include src="report"/>

</file>

<file id="a2" name="sections.pdf" format="pdf">

<include src="headerSection"/>
<include scr="mainSection"/>

</file>

<foreach>

<file id="file9" name="department_&amp;&lt;department_id&gt;.pdf" instance="this">

<include src="mainSection"/>
<include src="trailerSection"/>

</file>

</foreach>

<foreach>

<file id="a20" name="department_&amp;&lt;department_id&gt;.pdf" instance="this">

<include src="report"/>

</file>

</foreach>

15.4.4 printer Examples

The examples in this section include:

• Print Whole Report

• Print Two Sections of a Report

• Print Grouped Report

• Print Combined Sections for Each Group Instance

• Print Relevant Instance of a Report to Its Relevant Printer

The way printer names are specified, differs between Windows and UNIX. Each example demonstrates both ways.

<printer id="a80" name="\\neptune\prtr20">

<include src="report"/>

</printer>

<printer id="a80" name="10th_floor_printer">

<include src="report"/>

</printer>

<printer id="a1" name="\\neptune\prtr20">

<include src="headerSection"/>
<include src="mainSection"/>

</printer>

<printer id="a1" name="10th_floor_printer">

<include src="headerSection"/>
<include src="mainSection"/>

</printer>

<foreach>

<printer id="prt20" name="\\neptune\prtr20" instance="all">

<include src="report"/>

</printer>

</foreach>

<foreach>

<printer id="prt20" name="10th_floor_printer" instance="all">

<include src="report"/>

</printer>

</foreach>

<foreach>

<printer id="prt20" name="\\neptune\prtr20" instance="this">

<include src="mainSection"/>
<include src="trailerSection"/>

</printer>

</foreach>

<foreach>

<printer id="prt20" name="10th_floor_printer" instance="this">

<include src="mainSection"/>
<include src="trailerSection"/>

</printer>

</foreach>

<foreach>

<printer id="a60" name="&amp;printer_name" instance="this">

<include src="mainSection"/>

</printer>

</foreach>

15.4.5 destype Examples

You can use destype to define a custom destination or pluggable destination that can be used by Oracle Reports during distribution. For more information, see Section 15.3.9, "destype". The examples in this section include the following destinations:

• OracleAS Portal Destination

• FTP Destination

• WebDAV Destination

• Fax Destination

<destinations> 
  <destype id="customforPortal" name="oraclePortal"> 
    <property name="outputpage" value="sample_report"/> 
    <property name="statuspage" value="Reports_Status"/> 
    <property name="desformat" value="pdf"/> 
    <property name="pagegroup" value="REPORTS_OUTPUT"/> 
    <property name="itemtitle" value="MyReport"/> 
    <include src="report"/> 
  </destype> 
</destinations>

<destinations>
  	<foreach>
    	<destype id="ftp1" name="ftp" instance="this" format="pdf">
      <property name="desname"
      		  value="ftp://username:passwd@ftpServer/dir/myreport_&amp;&lt;
      		   DEPARTMENT_NAME&gt;.pdf"/>
      		<include src="mainSection"/>
    	</destype>
  	</foreach>
</destinations>

<destinations>
  	<foreach>
    	<destype id="webdav1" name="webdav" instance="this" format="pdf">
      <property name="desname" 
        value="http://user:passwd@WebDAVServer/dir/myreport_&amp;&lt;
         DEPARTMENT_NAME&gt;.pdf"/>
      		<include src="mainSection"/>
    	</destype>
  	</foreach>
</destinations>

<destype id="faxdest" name="fax">
  <property name="number" value="123456789"/>
  <include src="report"/>
</destype>

<fax id="faxdest" number="123456789">
  <include src="report"/>
</fax>

15.6.1 OracleAS Portal Destination

Beginning with Oracle9i Reports Release 2 (9.0.2), Oracle Reports supports OracleAS Portal as a destination. By using DESTYPE=ORACLEPORTAL, you can push a report to an output page specified in OracleAS Portal.

However, there are a few limitations in using this destination:

• The ORACLEPORTAL destination cannot be used with distribution. Instead, you can use DESTYPE=WEBDAV for advanced XML-based distribution to OracleAS Portal.

  
  

  Note: Ensure that the OracleAS Portal instance is WebDAV-enabled. Refer to the OracleAS Portal online Help for more information on how to enable WebDAV. For more information on how to use WebDAV for distribution to OracleAS Portal, refer to Note 241821.1 on Oracle MetaLink at http://metalink.oracle.com: How to Send and Distribute Reports 9i Output to Oracle Portal?

  
  

• The DESTYPE=ORACLEPORTAL destination cannot be used with the rwrun executable as it causes Reports Server to stop responding. Use this destination only with rwservlet, rwclient, or rwcgi.

15.6.2 XML Output

Using reference parameters for report bursting (that is, by specifying instance=this) is not supported for XML output. If used, it results in the following error message:

REP-34310 "Reference parameter not allowed in distribution list for XML destination files" 

You can use the XML format in distribution without the reference parameter.

15.6.3 Delimited and DelimitedData Output

Distribution and bursting are not supported in delimited output. You cannot specify a DELIMITED or DELIMITEDDATA output format in a distribution.xml file.

15.6.4 Spreadsheet Output

Distribution and bursting are not supported in spreadsheet output. You cannot specify a SPREADSHEET output format in a distribution.xml file. Thus, the current mode of generating paginated default output in a distribution module will not work for spreadsheet output.

15.6.5 Dynamic Format Values

XML distribution supports only static values for the format attribute (as seen in distribution.dtd). Thus, you cannot specify lexical parameters (to be resolved at runtime) for the format attribute. Hence the format cannot be dynamically determined either for the entire report or for a specific section.