I need help to find out the issue in configuring the fallback settings. Consider the below target end point settings with the fall back target server.
<HTTPTargetConnection>
<LoadBalancer>
<Server name="pp2url"/>
<Server name="callback1url">
<IsFallback>true</IsFallback>
</Server>
</LoadBalancer>
<Path>/XISOAPAdapter/MessageServlet?senderParty=&senderService=BS_Sender&receiverParty=&receiverService=&interface=SI_OS_Request_StoredProcedure&interfaceNamespace=http://lsco.com/rtc/API_StoredProcedure_POC</Path>
</HTTPTargetConnection>
The target is the soap based webservice and requires authentication.
Issue:
If the pp2url is not found or having issue, the apigee is invoking the callback1url - but giving error. Whereas if I used the callback1url in the place of pp2url, the flow returns success response. Can you please help us resolving this issue?
Solved! Go to Solution.
Hi @Paranitharan , 404 cannot be called as target unavailable by Load balancer and thats the reason why in your case , re-routing is not happening to fallback server .
Using health monitor you can one way handle all Http 4xx and 5xx too . Based on the error scenarios what you want to handle , you can design your target definition
pls check this link http://apigee.com/docs/api-services/content/load-balancing-across-backend-servers
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |