using the microgateway I need to create an API proxy and it needs a public URL, what can I do in that case?
Hmmm, yes, I think what you are saying is... the design of the microgateway requires that there be an API Proxy, but you don't want the external gateway to ever handle requests on that API proxy endpoint.
I always thought the design of the microgateway was a little unfortunate. The concept of an API proxy was well established. We all knew what that meant. Then with the launch of the microgateway, we established some magic naming conventions (edgemicro_*) on API proxies... and the proxies themselves aren't really used. Adding regular policies has no effect. Tracing won't work. The vhost is irrelevant. And there are other differences. The plugins are ... not managed in the central admin repository. Really all of this points to a need for using a different entity to manage these things used by the microgateway.
I'm describing all this to say "I feel your pain." But that is all decided now.
I think your question is , how do I configure an Edgemicro proxy that will never receive inbound calls on the Enterprise Gateway.
If that is the problem, then there's an easy solution. Create a new, secure vhost with a bogus alias. And reference that vhost in the edgemicro_ proxy. When you deploy it, the deployment will succeed, but no call will ever reach the API Proxy endpoint on the Enterprise Gateway.
Arghya described the approach here.
LinkedIn
Twitter
