Skip to Content

In this blog, I will explain the benefits and step by step guidance of using SAP Cloud Platform, API Management Hybrid Deployment.

Challenges Were:

1.How to manage APIs Securely from one Unified Cockpit while deploying the APIs from cloud or on premise private data centers

2.How to manage APIs without an impact on performance if API provider’s backend and the API consumers are within the customer firewall.

Solution is SAP Cloud Platform, API Management Hybrid Deployment which can connect to your SAP API Management on premise and help you manage your APIs from one place

Benefits

1.Performance: for ground-to-ground scenarios where API providers backend and the API consumers are within the customer firewall, it would make sense to have the API Gateway co-deployed closer to the on-premise systems for improved performance

2.Security: enterprise customers have internal API ecosystems (e.g. engineering/R&D departments) with high security requirements and want to have on-premise API gateways to manage the API traffic.

Now Lets set up our landscape

Pre-Requisite

  • Hana Cloud Connector set up refer
  • On-boarding a New account refer
  • Run time details like ORG_ADMIN, USER_PWD,port,Management Runtime url should be saved as it will be used while creating destination. In this blog I will take an example of Management Runtime URL as http://runtime.servername.com/v1, port as 443

 

Lets Add our SubAccount created as part of On-boarding to cloud connector

1.Logon to the Cloud connector administrator page (https://localhost:8443)

 

2.Click on Add Account to add sub account.

3.Enter the details like Landscape host, Account Name etc and Save it.

4.Account gets added.

5.Navigate to the Cloud To On-Premise tab.

6.Then click + to add the mapping for the API Gateway Management server

7.In the Add System Mapping wizard, select the drop down, and select the back-end type of on- premise as Non-SAP, and  then click Next.

8.Select the protocol as HTTP/HTTPS based on the API Gateway on premise system. During the on boarding HTTP was selected.

9.Provide the internal host and port to the API Gateway Management server.

The example we have taken is mentioned in pre-requisites and hence the same is used

10.Provide the external host and port to the API Gateway Management server. The value provided in this step should be those used during the creation of the HTTP Destinations of the API Portal.

11.Follow the Default settings and Select Finish.

12.Click + in the Resources Accessible section to whitelist the Management Server resources

13.In the Add Resource dialog, provide the value of path as /, and then select the radio option, Path and all the sub-paths and click on Save.

Configuring HTTP Destinations to the API Gateway on Premise Management Server

14.In the newly created SAP Cloud Platform Account, under the Connectivity tab, navigate to the Destinations tab.

15.For this blog I am attaching the screen shot of  HTTP Destinations files,you can import it by choosing the Import Destinations button.

 

Note: During API Management set up,a destination file for corresponding subscriber would be created under API Portal Providers context.This configuration file  would be supplied to you via support ticket.

16.From the imported file make the following changes: –

  • Edit the Name and replace accountname text with Account Name value of the newly created SAP Cloud Platform Account
  • Edit the URL and provide the Management server based on step (http://{ servername}:{port}/v1)
  • Provide the user/password for the org admin user configured in On premise Runtime System.

Note:During API Management Onboarding, the below listed configurations will be carried out for the on premise customer by SAP Cloud Ops Team.

  • Configuration for the subscriber under Environment service on Provider level context
  • Configuration for the subscriber under Virtual Host service on Subscriber level context

17.To get these Configurations done for you, raise a service request.

18.Once the configurations are done open API Portal URL

19.Navigate to Develop

20.Create an API Proxy,by clicking on create,Host Alias for the configured runtime should be shown

21.Click on Save and Deploy.

Note:To manage lifecycle of APIs from one unified cockpit, you need to disable your on premise UI which gets installed as part of the standard APIM installation. refer(Section 2)

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply