As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
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.
WF7.1.4 Prod/Test, MRE, self serve, DM
Posts: 176 | Location: Desplaines | Registered: August 05, 2004
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
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004
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
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007
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.
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
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
O. Julian Plys PMP WebFocus Admin jplys@sunocoinc.com
Posts: 5 | Location: Philadelphia | Registered: May 24, 2004