Instance Management in BusinessObjects is the topic of discussion for this blog. Let us see more in detail about reports and program objects Instance management further.
Instance is an entity which is created whenever a report or a program objects is scheduled to run. Up on creation these instances are stored in Output File Repository. To get the right information as on when required, it is always important managing and backup those reports and instances as they contain organizational data.
Instance management plan enables us to
– Identify scheduled reports and their frequency of schedule
– Retention period till which instances need to be maintained
– Size of each report instance and the amount of disk space required
– Necessity to keep organizational sensitive data (Instance cleanup)
– Schedule destinations
We can manage instances by setting instance limits at below levels
- Global limits (If it is required to set the limit throughout all the public folders and sub folders, we need set it at global level. We need to turn on inheritance to cascade the settings to sub folders and the objects.
- Folder limits (This will help us to set the limits for all the objects contained within the folder)
- Object limits (Applying limits to specific object then we need to set it at object level. This will override the limit set at folder level.
And based on below criteria’s
- Number of Instances
This will enable us delete excess instances when there are more than N instances of the object.
- User/User group
This will help us to set the limits per user/user group on a particular object.
- Number of Days
This will enable us delete excess instances when the age of the instance exceeds N days.
– Reduced File Repository Store backup size. This is a huge benefit as this backup is taken on daily basis.
– User need not search for a huge list of instances.
– By controlling the number of instances we can minimize the amount of space required in Output File Store
Hope this blog is informative. Thanks for reading!