Two BPC .NET servers for one backend BW system..

[Former Member]

Hi Experts,

Can we use two BPC .NET servers for one backend BW system for load balancing incase of one BPC .NET server failure? if yes, are there any depencies between two BPC .NET servers? please suggest.

thanks

Venkata

[Former Member]

Hello All,

The document linked below has some details and explanations on how to set NLB.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0c04afc-e4f3-2d10-448a-cb2bcf4b7d04

Best Regards,

Carlos

[sorin_radulescu]

NLB = Network Load Balancing

This can be software or hardware and basically is balance the connection when you have multiple webservers.

Afinity is a typical setting into NLB where yuo specified if a client is connected from an IP to NLB it will be redirect to one of nodes from NLB. If afinity is ON that's means every time when a client will be connected from that specific IP will be always redirect to the same node from NLB.

I hope this it will help.

For more info about NLB you can go into Microsoft side or you can search on google.

Regards

Sorin Radulescu

[Former Member]

Hello Venkata,

Adding additional .NET servers to the same BW system is a valid solution for providing redundancy / fail over at the .NET tier (as Sorin mentioned) but it is important to note that this likely will not increase your overall capacity.

The primary logical capacity constraint for a BPC NetWeaver installation in the number of available dialog and batch worker processes configured on the ABAP server (see T-Code RZ10, parameters rdisp/wp_no_dia and rdisp/wp_no_btc for your current configured values). Synchronous operations (reporting, input schedules, etc) use Dialog worker processes. Asynchronous operations (data manager packages, some admin tasks) use background worker processes. Both of these parameters have a maximum configured value of 100. This means that at any time you can only process a maximum of 100 synchronous and 100 asynchronous operations executing at one point in time per NetWeaver instance regardless of the number of .NET servers configured. If you wish to increase capacity, you should install a dialog BW instance and direct one of the .NET servers there.

Thank you,

Daniel

[Former Member]

Hi Sorin Radulescu,

Thank you for info. What is the NLB and NLB afinity? can you educate me on this?

thanks

Venkata

[sorin_radulescu]

You can use two .NEt server with NLB for fail over capabilities.

Installation of second .NET server is the same with first one (notthing special).

If you will use NLB then you have to pay attention to NLB settings or installation of MSMQ.

If you can use for NLB afinity set to single, or for other NLB is called perssistency or or stickness on then you can have MSMQ installed local in each of .NET server.

But if you don't set this afinity to single for NLB then you have to use remote MSMQ and both .NET server must use this queue otherwise you can have erros because the system can use two different queues.

Regards

Sorin Radulescu

[Former Member]

Hi VIjay,

thank you very much for reply. Do you get any suggetions from SAP when you setup? if you have any document, please share with us. help us if there are any specific settings needs to take care.

thanks

Venkata

[Former Member]

Hi,

Am sure that we can use two .Net Servers to one back end Servers for load balancing. We have implemented the same.

Regards,

G.Vijaya Kumar