Skip to Content

With the September 2018 release of SAP Cloud Platform Integration you would observe that SAP API Management and SAP Cloud Platform integration have been tightly coupled.

You can now directly explore API’s present in SAP API Business Hub and generate Integration Flows based on pre-provided templates. You can use this feature for the following use cases

Use Case 1: You would like to consume and API listed in SAP API Business Hub as is for one of your integration scenarios but would like it to be routed via SAP Cloud Platform Integration in order to centralize your Integration monitoring and operations.

Use Case 2: You know of an API that is required for your Integration scenario. You can use the generate Integration Flow option to create a bare bone Integration process that you can extend based on your integration needs.

So what does the new functionality have in its offer:

The Discover function on the CPI tenant is extended to additionally discover the APIs from API Business Hub.

You can also Search for API’s from SAP API Business Hub right from your Integration space as shown below. Example in this case I have searched for the Cloud Platform API.

 

You can select an API and a specific operation of the API like (GET/PUT/POST) and Generate Integration Flow for the operation.

 

 

On choosing Generate Integration flow you can choose a specific Package where the iFlow has to be generated. You can additionally choose the Resource and the target URL of the API.

After choosing the Package, iflow name, resource, operation and the target URL of the API you are taken to the screen to mention the Sender and Receiver Adapter Address for the generated iflow.

 

The Sender Address acts as the proxy resource URL that you can use to call the target API that you have selected for generation.

The Integration flow that is generated creates an equivalent Sender Address for every API that you choose for iflow generation. Example

  1. REST API with GET operation would have an HTTP Sender Adapter with GET operation.
  2. OData API with POST operation would have an OData Sender Adapter with POST operation.
  • SOAP API with a GET method would have an SOAP 1.x Sender Adapter with equivalent method.
  1. …. Similarly for rest of the operations for REST, OData and SOAP ….

The iflow that is generated exposes an end-point equivalent for the API that you have chosen. This end-point acts as a proxy to simply send the request to the target API. By generating this Integration flow and deploying it you have the option to redirect the call to the API via the newly exposed Sender URL.

Note: The Sender Address and Receiver Address cannot have the parameter placeholders. Depending on the API (mostly in REST API’s) it is possible that your pre-filled Receiver Address might have a placeholder like {placeholder value}. You can either substitute this with actual values OR simply remove the placeholder and the content after the placeholder as this is something that you can pass via the URI during your call to the proxy address that is exposed via the Sender Address.

With the September 2018 release the default iflow generation only offers prefilling with Basic Authentication. If you do not have a credential you can simply leave it empty. You always have the option to go to the Generated flow and changing the Sender and Receiver Address parameters including its Authentication types.

On finish of the wizard the Integartion flow is generated in the selected package. You may go to the package to Edit and change the iflow to your required needs and deploy it.

 

In this blog you have learnt how generating Integration Flows from API has been made simple in SAP Cloud Platform Integration.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply