Hi, If I use a loadbalancer (= F5) exposing a physical IP address (= routed on internet) and calling one of our endpoints (REST, ...) running into different integration servers (Fuse + Camel), can we design such topology ? We setup an Apiman Manager (Front + ElasticSearch Database) to define the plans, services, roles, policies of all the endpoints which are running into different Fuse Servers. As the mapping between the incoming request and the endpoint is managed by the Apiman Gateway, I'm thinking to install one Apiman Gateway / Fuse Server. Is it doable ? Client --> 192.168.1.1 (IP Address of the Server replying to a REST Service) "Loadbalancer F5" --> NAT --> address of the gateway (= 10.0.2.1) managing the mapping between the request and the physical endpoint --> Camel REST Endpoint (10.0.1.1). The Apiman Manager could run internally on this addess (10.0.2.100). To support high availability or workload distribution, it will be required that at least each Camel REST / Web Service runs into multiple instances of Fuse Servers. That means that their IP address will be different (A REST service will be deployed on 10.0.1.1, 10.0.1.2, 10.0.1.3, ...). Question : As the GUI interface of the Apiman Manager to encode the address of the endpoint to map proposes one field (and no more if we would like to distribute the requests to different servers), is there a possibility to define a 1 to many relation into ApiMan Server (maybe if we develop such a feature) or do I have also to install an Apiman Manager / Gateway per Fuse Server and to encode the same info (plans, services, ...) excepted the IP address of the server which is different ? Regards, Charles