01.02.2013 Views

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

7.2.3 Example Destination<br />

Registering Destination Types with <strong>the</strong> Server<br />

<br />

This example defines <strong>the</strong> values <strong>to</strong> be associated with a portal user ID. It includes <strong>the</strong><br />

attributes confidential and encrypted:confidential="yes", which indicate<br />

that <strong>the</strong> values within this element should be encrypted; encrypted="no", which<br />

indicates that <strong>the</strong> values are not yet encrypted. The next time <strong>the</strong> <strong>Reports</strong> Server starts,<br />

it will au<strong>to</strong>matically encrypt <strong>the</strong> values and reset encrypted <strong>to</strong> yes.<br />

Note: Elements and attributes allowable in server configuration<br />

file are determined by <strong>the</strong> syntax defined in <strong>the</strong><br />

rwserverconf.dtd file (ORACLE_<br />

HOME\reports\dtd\rwserverconf.dtd). This is discussed in<br />

detail in Chapter 3, "Configuring <strong>Oracle</strong>AS <strong>Reports</strong> Services".<br />

What is valid for a destination type's properties depends entirely on <strong>the</strong> destination<br />

type. These values do not come from <strong>Oracle</strong> <strong>Reports</strong> and are not put <strong>to</strong> use by <strong>the</strong><br />

<strong>Reports</strong> Server. They come from <strong>the</strong> destination type itself and use terms <strong>the</strong><br />

destination recognizes. It is up <strong>to</strong> <strong>the</strong> developer <strong>to</strong> understand <strong>the</strong> requirements of a<br />

cus<strong>to</strong>m destination and <strong>to</strong> know what properties <strong>to</strong> associate with a given cus<strong>to</strong>m<br />

output type.<br />

When we begin <strong>to</strong> discuss distribution, you may note that within <strong>the</strong> distribution XML<br />

file, <strong>the</strong> destype element also allows for <strong>the</strong> use of property name/value pairs. It's<br />

important <strong>to</strong> make a distinction between properties entered for a destination<br />

element in <strong>the</strong> server configuration file and those entered for a destype element in<br />

<strong>the</strong> distribution XML file:<br />

■ Properties entered for a destination element in <strong>the</strong> server configuration file<br />

should deal only with configuring an output type, for example setting an<br />

allowable number of retries for a destination fax.<br />

■ Properties entered for a destype element in <strong>the</strong> distribution XML file should deal<br />

only with specifying a runtime parameter, for example <strong>the</strong> identity of <strong>the</strong> fax's<br />

intended recipient.<br />

The following example illustrate a destination element for pushing content in<strong>to</strong><br />

<strong>Oracle</strong>AS Portal:<br />

<br />

<br />

<br />

Configuring Destinations for <strong>Oracle</strong>AS <strong>Reports</strong> Services 7-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!