on 12-27-2009 5:32 AM
Hi,
We have a Xcelsius dashboard based on a QaaWS query. It works in the development server. We are now moving it to procuction which is a clustered system. Two servers (server1 & server 2)and a load balancer. The URL of the QaaWS now has the development server which is fine.
Now after deploying the queries to production as we have more than one servers, on which server should the QaaWS be based on.
http://server1:8080/dswsbobje/qaawsservices/biws?
or
http://server2:8080/dswsbobje/qaawsservices/biws?
Please help me on this.
With my basic knowledge about a clustered setup, in a well deployed clustered setup you will not have 2 urls. I believe you will have to specify the url to the load balance server which will in turn choose the server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The load balancer will not have the BO installed on it. I will explain the problem again.
Two BO servers BO1 and BO2 are there with a load balancer. The Query as Web Service URL is based on BO1.
I hope a query can't be pointed to more than one server.
Scenario: BO1 server is down; BO2 server is up.
The Load balancer will route the request to BO2 where the user can see the dashboard. But he can not run it as the query used by the dashboard is based on BO1 server which is down.
What to do in this kind of model. Please help.
Hi,
The load balancer will not have the BO installed on it. I will explain the problem again.
Two BO servers BO1 and BO2 are there with a load balancer. The Query as Web Service URL is based on BO1.
I hope a query can't be pointed to more than one server.
Scenario: BO1 server is down; BO2 server is up.
The Load balancer will route the request to BO2 where the user can see the dashboard. But he can not run it as the query used by the dashboard is based on BO1 server which is down.
What to do in this kind of model. Please help.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.