Then, we see agnostics documents represent a very huge part of the repository size and I can’t explain why this kind of files are stored in it while the publications who generates it in our company put it on a network drive !
It is like for each PDF or XLS generated outside BO, the BO system would keep a copy in the filestore !!!
Have you noticed such thing ? how did you manage it ? Do you know how if it is a bug, how to reduce it ? I have read in forum the ‘-prune’ stuff to delete empty folders in the filestore but I dare it would not be enough…
Thank you in advance for your inputs on this subject.
Yes HRS, thank you for your input but I am already able to estimate the size of the documents in the repository. Now, my question was, why all this agnostics files are stored in the FRS while I want them only to be generated otside, and how to purge it
in attachment some typical settings of such publication and you can seee than i only want to be saved in the drive and if we consult the history and query the CMS, we see that PDF are also stored inside the FRS BOXI_30_FRS_Grows.doc (79.0 KB)
My observation has been that no matter what you do in Business Objects, it creates an instance within Business Objects (i.e. the FileStore) unless you tell it not to.
There are a couple of ways you can handle this.
Set up limits on the number of instances that are retained. You can either do this by number of instances or by time. Which you choose depends on your data and how long it is valid. In your case, if all of the reports write a file out to your network and that is your official document retention area, you wouldnt need to keep any instances in Business Objects. Bernard, this is the limits feature you were asking about.
As Mak 1 points out, setting the clean up instances option may also work. This deletes the instance after it has been used to create the file on the network. This prevents the number of instances from accumulating. I don’t know exactly when this setting removes the instance but it shouldn’t retain the instance in the FileStore. I can’t remember if I have looked at this or not. It’s an option we don’t use.
The “delete instance after scheduled run” option is a bit flaky…or perhaps works only for certain parameters. I find that even if you check that option, the instances are still retained. As long as you can see/access the instance in the “history”, it is present somewhere on the filestore. Even when you schedule a report to an external drive, it still retains a copy on the filestore.
In the end we find a lot of users utlizing BO as their document archival system. We have set limits on the folders at root level, but users have option to override those. As a result some of them accumulate thousands of instances.
Apart from auditing such usage and sending alerts to errant users, there is not much we can do.
yes, I have been said that the delete instance after was a bit bugged in XI3.0. maybe it works better in XI 3.1 and after. if someone has testimonies regarding this…
(BOB member since 2003-05-26)
(BOB member since 2005-01-06)
(BOB member since 2005-05-25)