file Examples Distribution XML File Examples

Creating Advanced Distributions 20-27 destinations

20.5.5.2 FTP Destination

This example shows the generic tag structure for sending report output to the FTP destination. destinations foreach destype id=ftp1 name=ftp instance=this format=pdf property name=desname value=ftp:username:passwdftpServerdirmyreport_amp;lt; DEPARTMENT_NAMEgt;.pdf include src=mainSection destype foreach destinations

20.5.5.3 WebDAV Destination

This example shows the generic tag structure for sending report output to the WebDAV destination. destinations foreach destype id=webdav1 name=webdav instance=this format=pdf property name=desname value=http:user:passwdWebDAVServerdirmyreport_amp;lt; DEPARTMENT_NAMEgt;.pdf include src=mainSection destype foreach destinations

20.5.5.4 Fax Destination

This example shows the generic tag structure for sending report output to the fax destination. destype id=faxdest name=fax property name=number value=123456789 include src=report destype Alternatively, for ease of use, you can specify a custom, more specific tag structure: fax id=faxdest number=123456789 include src=report fax

20.6 Using a Distribution XML File at Runtime

The method for using a distribution XML file at runtime is essentially the same whether you use it in a URL or a command line. Include the options: Note: All you must do after you modify the distribution.xsl file is, save it back to the same location under the same file name. Oracle Reports will automatically look for this file when resolving distributions. 20-28 Publishing Reports to the Web with Oracle Reports Services destination=filename.xml distribute=yes where filename is the name of the distribution XML file. You are required to specify either the relative or absolute path of the XML file. For example, for Windows, you might specify: destination=c:\ORACLE_HOME\reports\distribution\filename.xml distribute=yes For UNIX, you might specify: destination=ORACLE_HOMEreportsdistributionfilename.xml distribute=yes For example, the full command in a URL would be similar to: http:your_server:portreportsrwservlet?report=rep.jspuserid=db_credentials destination=ORACLE_HOMEreportsdistributiondistribution.xmldistribute=yes The paths in these examples are used for illustrative purposes only. There is no requirement for where you store your distribution XML files. You can store them wherever you like. For detailed information on running reports from command lines and URLs and using the cgicmd.dat file, see Chapter 18, Running Report Requests .

20.7 Limitations with Using Distribution

This section outlines the limitations with using distribution in Oracle Reports: ■ Delimited Output ■ Dynamic Format Values

20.7.1 Delimited Output

■ Report bursting and distribution does not support Delimited output format. You cannot specify DELIMITED as an output format in a distribution XML file or in the Distribution dialog box. Note: In some cases, Microsoft Internet Explorer ignores the mimetype of a URLs return stream and instead sets the type by looking at the URL. This can be a problem when you are using the distribution feature of Oracle Reports Services because your URL might end with the destination parameter; for example: ...distribute=yes destination=c:\oracle\reports\distribution\mydist. xml In this scenario, your URL ends with the extension .xml and Internet Explorer treats the return stream as XML, when in fact it is HTML. As a result, you will receive a browser error. To work around this issue, you should never use recognized file extensions at the end of a URL. In the preceding example, you could switch the positions of the distribute and destination parameters in your URL.