Layer 7 API Management

Expand all | Collapse all

Fail over Scenario b/w back ends

Jump to Best Answer
  • 1.  Fail over Scenario b/w back ends

    Posted 09-03-2019 07:41 PM
    Hi Team,
    I have 2 versions of Tibco back ends. BW5 and BW6 are the 2 versions.

    Currently we are migrating from BW5 to BW6.

    i would like to create a policy based on back ends availability. if BW6 is down or not accessible then need to send request to BW5 and vice versa.

    Can you please help me on how to achieve this.

    Thanks,
    Sri


  • 2.  RE: Fail over Scenario b/w back ends

    Posted 09-05-2019 02:34 AM
    Dear Sri,

    you can simply use route to JMS in order (BW6, BW5) with circuit breaker assertion inside at least statement ( like in pic ) or for production ready solution you can have a look at:
    https://docops.ca.com/ca-api-gateway/9-4/en/policy-assertions/assertion-palette/policy-logic-assertions/create-routing-strategy-assertion/working-with-dynamic-routing/


    Regards


  • 3.  RE: Fail over Scenario b/w back ends

    Posted 09-05-2019 08:55 AM
    Hi Ozan,
    Thanks for your response.

    here we are not dealing with JMS. we have just BW5 and BW6 back end urls like below. if BW5 is down,i just want to send traffic to BW6.

    BW6 endpoint:

     https://esbbw6.com:17996/customer/sapcleanse

    BW5 endpoint:

     https://esbbwt5.com:17996/customer/sapcleanse


    T
    hanks,
    Sri




  • 4.  RE: Fail over Scenario b/w back ends
    Best Answer

    Posted 09-05-2019 09:53 AM
    Then it is even more simpler:

    use multiple urls in connection tab with ordered sticky with failover option



  • 5.  RE: Fail over Scenario b/w back ends

    Posted 09-05-2019 11:35 AM
    Hi Ozan,
    Thank you, it is working.
    is there a way to capture 500 error and based on 500 error fail over to working back end.

    Thanks,
    Sri