I have recently run into an issue where I'd like to segment report processing loads through use of server groups in a distributed environment (i.e. HR, Finance, Marketing server groups). Creating a server group for a new organization beginning use of the BOE platform is no problem, but by design all other pre-existing reports for other organizations will be able to use this org's services unless there is a server group assigned for them as well. (The environment was originally created with no server groups) Which brings me to my problem...
Since BOE cannot assign objects to server groups at the folder level, routing them at the report level is a time consuming (if not impossible) task, as there can easily be 1000's of report objects to be assigned.
I can create (and was advised by tech support that the solution is) a SDK bulk update tool, but first wanted to check to see if anyone else has run into this dilemma before I go any further.
It seems best practice when initially building out an environment should be to create and route all reports to a single "catchall" server group if there is ANY chance of using server groups to segment geographically, by organization, etc. in the future....
Thoughts?
Since BOE cannot assign objects to server groups at the folder level, routing them at the report level is a time consuming (if not impossible) task, as there can easily be 1000's of report objects to be assigned.
I can create (and was advised by tech support that the solution is) a SDK bulk update tool, but first wanted to check to see if anyone else has run into this dilemma before I go any further.
It seems best practice when initially building out an environment should be to create and route all reports to a single "catchall" server group if there is ANY chance of using server groups to segment geographically, by organization, etc. in the future....
Thoughts?