Determining Report Bursting Status

[tensiodn]

Just wanted to see if anyone can assist me with a small issue.  We do alot of report bursting using ReportNet and sometimes the bursting fails. 

We have no way of proactively and quickly finding out which packages failed the bursting process.  Therefore, we're thinking of building a reportnet framework model to extra log data from the Content Store to enable us create reports that can tell us this at specified intervals.

Does anyone has any recommendations on how we can better do this - that is determine the status of report bursting activities?  Do anyone know the tables in Content Store that store this information?  Doe anyone has any suggestions on best practices how to get this done?

Any recommendations will be greatly appreciated.

Thanks.



Anthony.

[skylab]

hello anthony,

even we implement a lot of bursting and repeater stuff. can you explain to me in detail as to what you want to acheive. i had problems while bursting but managed to make them work and they are working fine.

i din't understand this part "We have no way of proactively and quickly finding out which packages failed the bursting process."

please let me know further and i might come up with simething for you.

regards,

sri.

[tensiodn]

Hi,

Thanks for looking into my post.

We would like to develop a reportnet report that tells us which reports burtings passed or failed.

We have hundreds of reports scheduled to burst at certain interval.  Right now the only way we know a report burst status is by logging into cognos connection and viewing it's history to see if it succeeded or failed.  We want to take that to another level - whereby we build a report scorecard (using report studio) that tells us which reports ran successfully or failed.

I hope this clarifies things - if not please let me know.

Thanks.


Anthony.

[Darek]

It might be easier with the SDK. Keep in mind that Cognos can change structure of Content Store between versions. Did you try Audit reports?

[skylab]

hello,

even we were stuck with it. the reports were bursting out properly but we did not had a way to know as to which were succesfull and which were not. there is an option  of "IsBursting()" function, but that wasn't helpfull either because it can be used only inside the report as a layout expression. but this function will tell you if the report is bursted to the reciepient or not. since it can be only used in the report layout, we can know if the report is bursted or not but, it can be only known if you open up the bursted report, which is not that helpfull. we had a case filed at the support for this enhancement. SDK probably has some extra functionality. you can ask the support if this can be acheived thru SDK.

Regards,

Skylab