Re: [Apiman-user] Changing gateway endpoints

Thanks Eric. I am using Wildfly 10, and I followed your instructions accordingly. It works great for an API that I created after the change, but a pre-existing published API doesn't get proxied correctly anymore. Instead, I get a 500 "API not found." In that case the managed endpoint is shown correctly through the manager UI - it just doesn't serve up properly. Generally this is the sort of config that would be done before anybody starts publishing APIs, and it's not likely to change, but just for my understanding, do you know why the pre-existing one would be broken? In any event thank you for you help - I'm enjoying exploring this cool product! ________________________________________ From: Eric Wittmann <eric.wittmann(a)redhat.com&gt; Sent: Tuesday, April 19, 2016 10:32:26 AM To: Christopher Stolte; apiman-user(a)lists.jboss.org Subject: Re: [Apiman-user] Changing gateway endpoints Assuming you are running apiman in WildFly or EAP (typical use) here is what you need to do to change the apiman endpoint: 1) Modify the "jboss-web.xml" file inside the apiman-gateway.war file (you can find it in WEB-INF). 2) Change the <context-root> to whatever you want it to be 3) Deploy the changed WAR to EAP/WildFly 4) Profit! Here is the file in question within the apiman source code: https://github.com/apiman/apiman/blob/master/gateway/platforms/war/wildfl... If you are running apiman on tomcat or jetty, you'll need to do something different - so let me know. :) -Eric On 4/18/2016 3:33 PM, Christopher Stolte wrote: