Publishing Reports to the Web - Downloads - Oracle

Invoking a Report From a Database Event
One way you can display this information is by setting SERVEROUT to ON in
SQL*PLUS before you run your script.
In addition to this method of debugging, the API has a set of pre-defined exceptions to
be used for error handling. You'll find examples of these exceptions in the srw_test.sql
script provided with your OracleAS Reports Services installation. Additionally, see the
Oracle Reports API reference documentation for a detailed explanation of these
exceptions.
Note: Look for upcoming information about Reports APIs on the
Oracle Technology Network, (http://otn.oracle.com).
17.3 Invoking a Report From a Database Event
Database triggers are the primary mechanism for invoking reports using the
Event-Driven Publishing API. The Oracle database allows you to define various scopes
of triggers that fire in response to various events. To submit a database-driven job, you
use the code described in the previous sections within a database trigger.
There are many ways to use event-driven publishing. One way is to create security
protocols using a trigger that fires whenever a grant is done or a user logs on or off.
Another way is to create automated processes that respond to certain types of changes
to data in a table. For example, a database trigger could fire when the status of an
expense report changes to DONE; in turn, a report could automatically be sent to an
employee's manager.
For example:
CREATE TRIGGER EXP_REP_TRG
AFTER INSERT OR UPDATE on EXP_REP FOR EACH ROW
myPlist SRW_PARAMLIST;
myIdent SRW.JOB_IDENT;
BEGIN
IF (:new.ExpStat = 'DONE') THEN
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
SRW.ADD_PARAMETER(myPlist,'GATEWAY','http://…');
SRW.ADD_PARAMETER(myPlist,'SERVER','fooSVR');
SRW.ADD_PARAMETER(myPlist,'REPORT','foo.RDF');
SRW.ADD_PARAMETER(myPlist,'USERID','foo/bar');
SRW.ADD_PARAMETER(myPlist,'ExpenseID',:new.ExpID);
myIdent := SRW.RUN_REPORT(myPlist);
END IF;
END;
This trigger will fire after each update on the EXP_REP table. In the event the status
changes to DONE, the report request is run.
If you want your request to run against a key specified in the cgicmd.dat file, specify
the CMDKEY parameter in lieu of the REPORT parameter. If the key contains user ID
information, you can omit the USERID parameter as well. For example:
CREATE TRIGGER EXP_REP_TRG
AFTER INSERT OR UPDATE on EXP_REP FOR EACH ROW
myPlist SRW_PARAMLIST;
myIdent SRW.JOB_IDENT;
BEGIN
IF (:new.ExpStat = 'DONE') THEN
myPlist := SRW_PARAMLIST(SRW_PARAMETER('',''));
SRW.ADD_PARAMETER(myPlist,'GATEWAY','http://…');
17-6 Oracle Application Server Reports Services Publishing Reports to the Web