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.

Configuring <strong>Reports</strong> Server<br />

in your database. Using <strong>Oracle</strong>AS <strong>Reports</strong> Services's event-driven publishing API, you<br />

identify <strong>the</strong> event as a specific job type. When <strong>the</strong> event occurs, <strong>the</strong> job type<br />

information is sent <strong>to</strong> <strong>Reports</strong> Server, which looks up <strong>the</strong> job type under <strong>the</strong> job<br />

element in its configuration file, and follows <strong>the</strong> direction provided in <strong>the</strong> element's<br />

attributes <strong>to</strong> <strong>the</strong> engine (and, if applicable, security implementation) specified for that<br />

type of job.<br />

Attributes of <strong>the</strong> job element are listed and described in Table 3–7.<br />

Table 3–7 Attributes of <strong>the</strong> job element<br />

Attribute Valid values Description<br />

jobType string Default: report<br />

Describes <strong>the</strong> type of job <strong>to</strong> be processed by <strong>the</strong><br />

server. You can enter any type of job, as long as<br />

<strong>Reports</strong> Server has an engine <strong>to</strong> process it.<br />

engineId ID reference References <strong>the</strong> ID entered for <strong>the</strong> engine that will<br />

process this job type. Available IDs are specified<br />

under <strong>the</strong> engine element in <strong>the</strong> server<br />

configuration file using <strong>the</strong> id attribute. The id is<br />

a unique keyword (that you devise) within a given<br />

configuration XML file that identifies a particular<br />

engine.<br />

securityId ID reference References <strong>the</strong> ID entered for <strong>the</strong> security<br />

mechanism that will be applied <strong>to</strong> this job type.<br />

Available IDs are specified under <strong>the</strong> security<br />

element in <strong>the</strong> server configuration file.<br />

3.2.1.8 notification<br />

Example<br />

<br />

Required/Optional<br />

Optional. If you do not enter a notification element in <strong>the</strong> configuration file, <strong>the</strong><br />

notification function is disabled. You can have from zero <strong>to</strong> multiple notification<br />

elements in your configuration file.<br />

Description<br />

Use <strong>the</strong> notification element <strong>to</strong> specify a Java class that defines <strong>the</strong> type of<br />

notification that should be sent when a job succeeds or fails. You can use <strong>the</strong> default<br />

notification class, which provides for notification via e-mail, or design your own with<br />

<strong>the</strong> <strong>Oracle</strong> <strong>Reports</strong> Notification API.<br />

Note: The RSDK contains <strong>the</strong> latest APIs that you can use with<br />

<strong>Oracle</strong> <strong>Reports</strong>.<br />

Attributes of <strong>the</strong> notification element are listed and described in Table 3–8.<br />

3-16 <strong>Oracle</strong> Application Server <strong>Reports</strong> Services <strong>Publishing</strong> <strong>Reports</strong> <strong>to</strong> <strong>the</strong> <strong>Web</strong>

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

Saved successfully!

Ooh no, something went wrong!