Concept Behind Report Scheduling

[ankan_priya]

Hi All,

I've been creating cognos reports for last 1 year on Cognos 10 and recently have started to use "scheduling" feature as well.

I'm a bit confused as when we run a report normally, it runs in a browser (a container to hold HTML data). However, when we schedule a report, it executes in the background. How does the HTML data (the report) actually gets generated when there is no browser to run the report.

My question might be phrased a little bit off, but can someone please explain to me the cocept underneath the scheduling feature of Cognos BI.

Thanks a lot
Ankan

[MFGF]

Hi All,

I've been creating cognos reports for last 1 year on Cognos 10 and recently have started to use "scheduling" feature as well.

I'm a bit confused as when we run a report normally, it runs in a browser (a container to hold HTML data). However, when we schedule a report, it executes in the background. How does the HTML data (the report) actually gets generated when there is no browser to run the report.

My question might be phrased a little bit off, but can someone please explain to me the cocept underneath the scheduling feature of Cognos BI.

Thanks a lot
Ankan

Hi,

The Cognos server is getting the data required for your report by running one ore more queries, then it is rendering the designed report output in your preferred format (HTML, PDV, Excel, CSV, XML). Your browser doesn't create the HTML pages for your report interactively, the Cognos Report Service does this. Your browser just displays the rendered HTML pages. When running a report in batch, the batch report service does the rendering rather than the report service, but it's exactly the same concept. Instead of the rendered HTML pages being sent to your browser, they are saved into the Content Store database as a saved output.

Cheers!

MF.