Hi All
Really appreciate some advice from BO gurus on a SAP BO architecture issue.
I have a requirement where we have 2 reporting database server (one in UK and another in Netherlands).We have one SAP BO reporting system in Netherlands in the same data center as the reporting database (in Netherlands)
My client wants to use the same BO reporting environment currently in Netherlands to report from the database in UK. Unfortunately the connectivity between the datacentre in Netherlands and UK is not good. It is difficult to refresh report (specially for adhoc large report). Fortunately the user groups in NL and UK are completely independent.
Is there any architecture i can follow where i can have a clustered BO environment with one machine in Netherlands and one in UK and 'somehow' compel the NL user group to use the Netherlands BO server to run the reports from the Netherlands DB and UK user group to use the UK BO server to run the reports from the UK DB. The only problem is CMC database will be in NL so there may be some access time lag for people logging in from UK.
Appreciate if someone can share some idea for such a scenario which we can test in a POC.
You can try with multiple option something like Security profile at universe data foundation level (Forcing users to select the connection according to their region) and Server groups (Server group for each region).
I would suggest you to come up with different components that you want to avail in both the regions and we can recommend you accordingly.
Thanks
Mani
Twitter : @meetmanie
Only possible solution is have multiple connections to Universe, one is UK and another one is Netherlands. You can have multiple universes with different connections and save them in different folders. Setup security for those user groups based on the location.
Since CMS DB , and Filestore in UK, you will have some lag in login and retrieving the reports. But the refresh will be much faster, since DB connections pointing to the location where the User base is.
But maintaining 2 universes will be nightmare. Whenever there is an update to the universe, you need to update the universe in other location as well.
if only schedule based reporting is allowed - it'll be possible, as you can isolate/assign all schedules to server groups - make all schedules for UK people to run on UK nodes of your cluster.
It's impossible to do so for Ad-hoc reporting (unless you create special set of reports/universes) for the UK users.
But then you might as well have 2 environments separately.
Hi Sanjit,
you can have BO nodes in UK and NL but required somewhat good network because CMS will check all available services for every one or two minutes and update the repository.
as mani mentioned, server group is the best option and you can have the app server also in UK and NL so that you easily mange the users and control.
as you mentioned, login will take time. processing the report will not take time because your reporting database in located on the same data center but all the status/updates will go to the CMS in another region :-)
we had a setup like this but network is good. we will use BO even one region is completely down. we did this for one of the bank. it's running very well.
we did POC for BO cluster with Linux and widows, it's also working very well. you can not have CMS on two different OS but processing servers fine. hope this helps!
Add a comment