Re: [Apiman-user] Apiman & Loadbalancer F5 !

Hi Charles. I'm not 100% certain I understand all aspects of your question - perhaps a diagram would help me, in case my answer doesn't make sense (and if you have the time). :) You are right that there is no 1..N mapping of an apiman service/api to a back-end endpoint URL. That is a feature we are contemplating for the future but it's certainly not available yet. Here are some thoughts that might be useful/relevant to this use case. First is that you could of course implement a custom policy that changed the back-end endpoint URL based on whatever criteria you see fit. The custom policy would simply have to change the value of the ApiRequest->Api:endpoint field. Doing that should be considered unsafe and a temporary workaround, as the Api object is globally scoped, and really should be either cloned (if we want to suppor this use-case) or immutable (if we don't). Another thing to note is that as of 1.2.0.Final we support system property and environment variable replacements in the API endpoint, endpoint properties, and all policy configurations. This means that you could install *identical* gateways on all the per fuse server, configured using the same shared registry. Then, when you configure the Service/API endpoint, you could set the value to something like: ${external_url} Then you could set a system property, which could be different for each gateway node, like so: (on gateway server 1) -Dexternal_url=http://fuse_server_1:port/ (on gateway server 2) -Dexternal_url=http://fuse_server_2:port/ That way your configuration is shared but certain aspects/properties of the configuration are *externalized*. This feature was originally meant to support more easily migrating data between dev/test/prod environments, but it would work fine for this as well. Did any of that help? -Eric On 1/19/2016 5:30 AM, Charles Moulliard wrote: