If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

10.2.2 Burst Reports to File System Best Practices

Started by gpollock, 27 Jan 2016 09:52:55 AM

Previous topic - Next topic

gpollock

Hi All, hopefully I have the right forum for this.  I'm summoning best practices gurus and link repositories.  I want to present a burst report strategy, and want to make sure I have the best practice and know which links I can use as resources.  Most of what I get on google points to 8.4 and I'm confused about the archive location in global settings vs the file location in administration vs cm.reportoutput.  I'm also looking for a good sample script.

We want to start bursting certain store reports as saved files (they're currently burst by active directory or email) to a shared drive.  We will be bursting by store, and for security reasons want to put the reports in separate folders--one folder for each store.  I don't know if removing the "-en-us" is a concern at this point, but we will need the files to have a timestamp to avoid overriding yesterday's report.  For example, if I run the daily sales report burst by store and save to location <share>\Stores\, I want to see Store 001's report saved to <share>\Stores\001.

As an added diffuculty, I want to leave the door open for other types of bursts and scripts, so I don't want to hard set any global settings.  Can you please see my plan below and let me know if I'm missing something or doing something the wrong way?


  • Create our root share <share> and subfolders Stores\<store names>
  • In configuration, set the Archive Location parameter to <share> and set the option to allow file system sharing.
  • In Cognos connection, add a file system for "Stores" folder
  • In my report, set it to burst by store, with label and data item set to store name, type Directory Entries
  • Schedule the report to run, with burst and save to the file system location "Stores"
  • Create a script that will sit in "Stores" folder, wake up every few minutes to process the files
  • Script will rename the report based on the time, move it to the store subfolder, and delete the .xml file that comes with the report

Is there a better way to do any of this?  I see there is an option for cm.reportoutputlocation and cm.outputscript that will go from a service to an on-demand run, but these look to be global, which I don't want.  What steps would you add/change?  Finally can someone link me to a sample script that I can modify?  I could work with either something that reads the xml file or parses the file name?

Thanks for your help!