Can IBI display reports on the real time data?
If the answer is Yes, can you please share the process of handling and maintaining real time data on the reports.

This message has been edited. Last edited by: FP Mod Chuck,

Create the report against the data. Add it to a Portal page. Set the refresh frequency of the Portal page to the number of seconds you'd like. As long as the table you're using is populated with the latest data, the report will show the updates as frequently as you want.

Payal

First of all welcome to Focal Point. It is a great place to get answers to your development quesitons.

What version of WebFOCUS are you using? When you develop your real time reports you do that the same as with any data source. You create metadata (synonyms) and create your report content. From the WebFOCUS portal you can deploy the reports and set them up to refresh at whatever interval you need.

I was writing this and didn't see Babak's response but we are consistent in the answer...

Thank you, Babak and Chuck for the helpful information.

I am in agreement with the comments from both Chuck and Babak. I've been-there-and-done-that, down to a refresh rate of 30 seconds.

Be sure that your frequency is LE to the frequency of the DB update.

Also, if this is a stand-alone report, it will always retrieve the most recent dresults as with and stand-alone report / source.

quote:

Be sure that your frequency is LE to the frequency of the DB update.

Doug,

For my own understanding (and curiosity) why would you refresh you portal/report more often (is LE to) than your DB is refreshed and consume resources more often ?

If your DB is refreshed every minutes, why refreshing portal/report every 30 seconds, as per sample, if half of the time a refresh occurs, nothing will have changed ?

I may not see why

Tks

@Martin: If you poll at the same frequency as your DB updates, your refresh can occur just moments before the DB update and you will need to wait an entire cycle to see the update of (almost) a cycle ago.
And we all know what happens when things can go wrong: Murphy will make sure it does.


Another option is to push changes as the DB updates (using a trigger, for example). I haven't played with that (yet), but in some environments that should be possible.

For example, using PostgreSQL, you can define a trigger that sends a NOTIFY message to a listener that is querying for such events. Each time the event gets sent by the DB, the query completes. The report can use that to "wait" while no NOTIFY events occur, then to query the relevant table for the changes and loop back to the LISTEN query.