System landscape for API Management

[Mattias]

Hi,

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?

[divyamary · Accepted solution]

Hi Mattias,

For the dev/test/production environments you could create separate sub accounts and enable SAP Cloud Platform API Management in them individually. You can have the same API Providers ( with the same name) created in each of the SAP Cloud Platform API Management account. The advantage of the API Providers would be that in case your target endpoint is different for dev/test/product you can just link the API Proxy to the API Provider and can configure the API Provider to different target system ( dev/test/prod) accordingly. For transport of the content, the following options exists :-

• You can manually export and import the API Proxies which are linked to the API Providers.
• You would have to re-create key value maps , certificates etc if used in each of the sub-account.
• You can use the Client SDK which is part of the SAP Cloud Platform API Management to automate this transport. Details available in help documentation.
• You can use the Platform APIs to import / export the API Proxies. API details available in SAP API Business Hub.

Thanks and Best Regards,

Divya

[Mattias]

Great divya.mary , exactly the answer I was looking for. Thank you