Connect one BO instance with several BW

[Former Member]

Hi experts,

I'm new to BO and I have a very newbi arquitectural question to ask, and I thought to start with the experts.

Do you advise having one BO instance connected to several BW sources?

The plan is to have one BO connected to a sandbox, dev and qas BW systems.

However I don't know if it's even possible, and if it is, then the configuration work to have such a landscape is probably more than having several BO instances.

On BO side only WebI will be used.

Any suggestions or comments?

Best regards,

João Pinto

[IngoH · Accepted solution]

Hi,

technically it is possible but that would mean you have a single point of failure for your DEV, QA and PROD BI system.

I don't think you would want that. At least I would have the PROD environment decoupled from the QA and DEV>

Ingo

[Former Member · Accepted solution]

Hi guys,

thanks for your answers.

I think my main doubt is now partially answered (technically it's possible to connect BO to several BW sources), however I would like a best practice approach regarding the effort involved since I've never been in a BO project like this.

The Prod will be isolated for sure and QAS probably too. No need to worry about the full landscape.

My main doubt is the effort required to connect the same BO to 2 BW backends (dev and sandbox) versus the effort to create a sandbox BO and connect it to the BW sandbox. The effort I'm measuring only technical (installation and connections) but other factors would also be in mind.

Some details:

-Dev and sanbox BW already exist.

-Dev BO is almost completed (installation, not the connection)

On one hand, for a new BO sandbox we will require additional hardware and several technical man days (not much but takes time to provision it). Using the same BO we have a lower number of technical mandays and no need for additional hardware.

For this argument I think using the same BO is the best approach.

On the other hand In the future the sandbox BO and sandbox BW (used for prototype) will disapear, so, if we have only 1 BO instance the effort to delete the prototype environment is also determinant because of the risk of leaving garbage information on the dev system. Deleting this environment has also the cost in mandays.

For this argument I think using separate BO is the best approach. Is it a clean process to delete the protorype environment from a mixed BO instance?

Thanks for your help,

João Pinto

[former_member136842 · Accepted solution]

Hello,

well if you want to minimize HW costs you could run DEV and Q&A on VM Machines. SAPBO recommends running PROD on physically HW.

If you mean uninstall BO with deleting it would be some kind of clean. But as we all know on Windows there will be always a rest piece of the un- installed Software

Regards

-Seb.

[former_member136842]

Hello,

well...technially you can connect one BO Server to multiple BW instances for Authorization and Query purpose.

But i would suggest also a 3-tier deployment loke DEV, Q&A, PROD

Regards

-Seb.