Skip to Content
Dec 11, 2019 at 08:36 AM

System landscape for API Management



I'm sure this is documented somewhere, but I cannot find it.

We've setup API Management talking to our on-prem Gateway OData-service in our development environment. Currently it's running on Neo, but I'm also experimenting with Cloudfoundry to see what we can do.

My question is how should we think when it comes to our dev/test/production environments? Should I create different subaccounts and manually move the API management setup between these, or how do you manage this?