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 have a process flow that runs process flows that run data flows. It's a big process that moves hundreds of tables.
Is there a way to get a consolidated text file of all of the logs of all of the units that run? Data Migrator seems to do me the favor of breaking each into an individual piece and I don't want to have to consolidate all of them.This message has been edited. Last edited by: Tamra,
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007
This can be done by setting the individual property of the data flow to be 'Run as a Stored Procedure'.
This is dangerous however as it has an affect on variables if used in the data flow(s) as well as the 'State' of the data flow. It also makes debugging quite difficult since all the logs are in one log. As well, this cannot be done when flows are being called as part of a parallel process.
One alternative to this is to look at the DM log file on the file system. If the DM log was re-created each time this process is executed, then you would have a single text file that contained the log information from the process flow.
I would definitely go this route, given the reasons given above.
At the moment I've written a table file request against the ETLLOG to pull what I need, based on the timestamps of the run. It isn't perfect, but it's sufficient.
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007