Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
shruthiarjun
Employee
Employee

Introduction


So, you are a Cloud Foundry developer developing microservices/APIs/applications on SAP Cloud Platform. If you are familiar with SAP API Management, you will already know that on the Neo stack of the SAP Cloud Platform it provides you the capability to manage your APIs for security, traffic and protocol transformations. If you are unfamiliar with the service, get to know more about it here

With our latest release, we extend this capability to the Cloud Foundry stack of the platform and enable you to manage your digital assets on Cloud Foundry using SAP API Management. We provide you a service broker in the Cloud Foundry marketplace that you can use to create an instance and connect to your existing Neo subscription. You can then bind your Cloud Foundry application to the created service instance which automatically creates an API Proxy in your API Portal. From now on, when your Cloud Foundry application is called, it is routed via the API Proxy. You are now free to add management Policies to the auto created API Proxy and enjoy the full benefits of API Management 🙂

Creating a API Management Service Instance


In your Cloud Foundry space look for API Management Service in the Service Market place.



 

Create an instance by providing the co-ordinates of your Neo subscription (the pre-requisite is to have the API Management set up ready on Neo)

Note: Leave the Application field empty



 



 

Binding your Cloud Foundry application


Login to your Cloud Foundry space via the Command Line Interface (CLI). Invoke the following route service binding command to create the API Proxy in your Neo subscription.
cf bind-route-service sap-cf-domain.com apim-service-instance-name --hostname my-cf-app -c '{"api_name" : ”custom_api_proxy_name”}'

The api_name is an optional parameter incase you want a custom name for your API Proxy. Else it is created with an auto-generated name.

Example:
cf bind-route-service cfapps.sap.hana.ondemand.com APIMServiceInstance --hostname eProductStore

With this, all calls to your application will be routed through API Management.

Managing in API Portal


You will find the API Proxy in your API Portal. You could go ahead and add Policies to bring in additional security or control traffic, quota etc.



 



 

Summary


In this blog we saw how you could reuse your API Management subscription in Neo and manage your Cloud Foundry assets. You can find detailed documentation of the feature in our help documentation here. The service is now available on Cloud Foundry Trial for new registrations. Very soon we will also make this available to our customers to use on their productive accounts.

Do give this a try and let us know what you think.

 

Update :

The service is also available now for existing Cloud Foundry Trial accounts. Details on how you could get started is described at the end of this blog.
18 Comments