I'm running several ETL processes, in some cases I get an Email that tells me to do run a report.
I would like to run that report with reportcaster automatic, driven by the ETL event that now sends me the mail.
How can that be done?

Frank,

I have never used it, but I suspect that you should be able to use ReportCaster API function calls to achieve this.

If you haven't already considered this, look into ReportCaster API.

Best of luck!
Sean

We are able to do this by updating the next rime time of the report in report caster repository. IBI does not recommend modifying the report caster repository. You are on your own on this.

Hi Frank,

Just checked with one of our ETL experts and here is what I hear back:

The best way to accomplish this would be to add a post-extract stored procedure (written in FOCUS) to execute the report caster job. As far as I know, DM cannot execute stored procedures as part of the email object.

The flow would look like this

Dataflow Tab:
Source -> Transformations -> target

Process flow Tab:
Start -> dataflow -> RPC (kicks off the RC job via focus code) -> Email Object

Hope this helps.

Cheers,

Kerry

thanks Kerry

but would it then better to use the RC schedule to start the process in total?

so

RC -> start -> execute the ETL job
            -> if there is a reason to do so
            -> start the report   

Frank,
Good to finally meet you at Summit. I usually hang out in the WF forum instead of iWay, but just noticed this. Did you come up with a solution for this? Check out the DSTRUN routine that can be coded in a post-procedure. I also used it in the"Triggering WF Reporting" technique shown in the Tips & tecniques Contest session at Summit2007

Darin

I learned a lot during this summit and one of the interesting things I learned was the lab on "BI-driven processes" I'm looking forward (and planning) the upgrade to 7.6.1 and that will bring the whole solution I hope.

I missed the last sessions so I do not know where the next summit will be held but I hope we will meet again and find more time to talk.

Here is a suggestion for what you want to do:

Set up the ReportCaster job like an "alert" and have it polling every 5 minutes or so.

At the end of your ETL process write some sort of a "trigger" to a log table.

Do a TABLE FILE that tests the existence of the trigger and set &&KILL_RPC if the trigger is NOT there, if it exists, set the trigger to N in other words to NOT kill the report
-SET &&KILL_RPC = IF &LINES EQ 0 THEN 'Y' ELSE 'N';

Let the report run and in the POST Process, use some sort of SQL pass through to delete the trigger, EG:

SQL SQLMSS SET SERVER TriggerLocation
SQL SQLMSS
DELETE FROM TRIGGER
WHERE LOG_JOB = 'ALERTREPORT'
;
END

This will return you to the state where the trigger does not exist and will be written by the next pass of the ETL process