Hi Alan,
That is exactly what we were originally asked to do. Turns out it is an interim solution. When the full solution is deployed the three IP-addresses will be behind a DNS so the round-robin/load balance will be for someone else to work out.
We also learned that these three IP-addresses corresponded to three availability zones of a cloud provider.
So for the interim solution which should only be in effect a few months we can simply use one IP-address with manual reconfigurations to cover any long(-ish) outages. Nevertheless this type of cloud provider environment, albeit interim for us, is not unreasonable and I shall discuss the matter of an RFE with the client so it can possibly be part of a proper discussion within the z/OS Community.
Thank you,
Colin C
------------------------------
Colin Campbell
------------------------------
Original Message:
Sent: Wed October 27, 2021 12:48 PM
From: Alan Hollingshead
Subject: Multiple IP-addresses for apiRequester
Hello Colin,
Just to ensure I understand your requirement, are you asking for z/OS Connect EE to provide a round-robin / workload balancing option for requests going to (three) remote API endpoints? If so, this is currently not supported and would require the customer to raise an RFE against z/OS Connect EE for customers to vote on.
Best regards,
Alan.
------------------------------
Alan Hollingshead
------------------------------