We are trying to implement the below task in our datapower servers.
1)There are 3 datapower servers and there is a service in domain-A, per box, with FSH as one ethernetinterface ip and port as 678
2)In the datapower servers we want to call the service(as a backend to another service), such a way that, always it should call the service from the same box. In case the service is down(example is disabling the service), it should call the service in the other two servers, loadbalanced; again should check if the service is up or not, in the other servers.
Could anyone give some idea on how to implement this.
Tried configuring a LBG, with the ethernetinterface as members, then gave the lbg name in the backend url. However I do not think LBG is able to find if the service is in up status or not. Also it is not exaclty a loadbalanced logic. The service in the same box should be called always, except if the service is down, it should be loadbalanced among the other two servers.
This topic has been locked.
3 replies Latest Post - 2012-06-26T00:54:33Z by irazabal
Pinned topic Services logic
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-06-26T00:54:33Z at 2012-06-26T00:54:33Z by irazabal
HermannSW 2700006U544230 PostsACCEPTED ANSWER
Re: Services logic2012-06-25T13:26:21Z in response to JaangoHi.
> Tried configuring a LBG, with the ethernetinterface as members, then gave the lbg name in the backend url. However I do not think LBG is able to find if the service is in up status or not.
> Also it is not exaclty a loadbalanced logic. The service in the same box should be called always, except if the service is down, it should be loadbalanced among the other two servers.
Sounds like "First Alive" algorithm to me ...
swlinn 100000E7QE1344 PostsACCEPTED ANSWER
Re: Services logic2012-06-25T13:28:49Z in response to JaangoSo if I understand your use case, you want a Datapower service to load balance to another Datapower service with session affinity? The LBG object has the capability of session affinity on the backside of a service, but it is only available with the Application Optimization feature which is a separate add on to the DataPower appliance firmware.