Was looking for a bit of advice, i've got a WS-Proxy, with one endpoint defined. What I want to do is, if that endpoint is un-reachable (ie a specefic error is returned) then i'd want to route to an alternative endpoint. Is this possible from the WS-Proxy?
JBrennan 270003M2T277 Posts
Re: Routing to 2 endpoints2011-08-25T14:43:19ZThis is the accepted answer. This is the accepted answer.A load balancer group would work if the primary endpoint is truly unreachable. If you are looking for trying a secondary endpoint in the event of some HTTP response code or some other error, you would best implement this in a error rule.
Mike.L 110000KY0K15 Posts
Re: Routing to 2 endpoints2011-08-25T14:56:06ZThis is the accepted answer. This is the accepted answer.
- JBrennan 270003M2T2
Re: Routing to 2 endpoints2011-08-26T08:22:20ZThis is the accepted answer. This is the accepted answer.Thanks for that, I haven't done much work with the load balancer group - not sure of its capabilities, will do some reseach into that.
The requirement is to always send to the primary endpoint, after consecutive
errors (whic are recieved when the primary is unavalible), the endpoint should switch to the secondary one and then stay at
that until we receive further notice that the primary is back up.
Does the load balancer group work by just sending to which ever endpoint is avaliable? The problem is we don't know which endpoint is avalible until a request is sent and we receive a response.
SystemAdmin 110000D4XK6772 Posts
Re: Routing to 2 endpoints2011-08-26T09:55:21ZThis is the accepted answer. This is the accepted answer.
- rsb_113 270004H13C
If your webservice has a suitable operation, the Load Balancer can send that request periodically and apply a predefined XPATH to validate the response.
This is probably the easiest and safest way to prove that an endpoint works.
Using custom error rules you can implement any error-retry logic but I would avoid complexity if possible.
Be sure to clearly qualify the requirements with the customer.