Use SAP Cloud Platform, API Management to Expose OData interfaces from SAP Process Orchestration as Open APIs
This blog is the part 2 of the 5-part blog-series. In this blog, we will introduce OData Interfaces which are exposed from SAP Process Orchestration (from 7.40 onwards) (SAP PO) can be exposed as Open APIs and managed through SAP API Management. Here with this blog you will be able to connect SAP API Management to your backend (SAP PO System) using cloud connector and will be able to manage OData Endpoints exposed in SAP PO.
Process Orchestration Overview
.Process Orchestration provides a tool infrastructure to model and design business processes from the overall process flow and the sequence of activities up to the interfaces and data types that are needed to integrate SAP systems and external systems.
SAP customers can now leverage SAP Process Orchestration to get the most out of their SAP and non-SAP investments. SAP Process Orchestration enables customers to adapt, simplify, accelerate and integrate business processes, as well as introduce flexible business rules to drive agility.
Equipped with solid B2B capabilities your organization will secure and at the same time extend SAP investments beyond the SAP domain.
To know more about Process Orchestration refer
Cloud Connector Overview
The SAP Cloud Platform cloud connector (cloud connector) serves as the link between on-demand applications in SAP Cloud Platform and existing on-premise systems. The cloud connector runs as on premise agent in a secured network and acts as a reverse invoke proxy between the on-premise network and SAP Cloud Platform. Due to its reverse invoke support, you don’t need to configure the on-premise firewall to allow external access from the cloud to internal systems
To know more on SAP API Management, refer
In this blog I have taken an example of my(*******)hanatrial account for SAP API Management and N75 as a backend(PO) system.
- You have access to N75 or any of the PO system
- OData Service should be available in PO system
Let’s get started!
For Downloading and configuring cloud connector refer
Type https://localhost:****/ on your browser following screen should come up
Enter User name and password to login as Admin
Click on Add Account to add an account
Fill in the appropriate details as shown below for your account
Here for SAP API Management I have taken example of my hanatrial account
Under Account Dashboard; Account should be added
As I have added my hanatrial account as host so my hanatrial account should be added as shown below
Now we will be adding the On Prem system for eg N75 (PO system)
Click on Cloud To On-Premise
Add Back end System as SAP Process Integration and Click Next
Select Protocol as HTTP and click Next
Add host and port of Back end System and click Next
In Virtual Host and port don’t put the same name and port as above
Select Principle Type as None and Click Next
Check the summary, select internal host checkbox and select Finish
System should get added
Click on Add button under Resources Accessible to add url path as”/” this is to consider all the resources after “/”
With this we have configured our back end system and now we will check in SAP API Management whether we can access OData services from PO system
Open SAP Cloud Platform Cockpit from where I can see under Connectivity – Cloud Connectors the successful connection to the on-premise system.
That’s All you need now let’s go to API Portal ->Services->click on API Management Tile->click on Access API Portal.
Click on Develop and Navigate to API Providers
Create API Provider and fill in the following details
Navigate to Authentication and give back-end system details
In my case I am connecting to N75 PO system and catalog service settings look like this
To test the new connectivity, just create a new API Proxy. Give API Provider as “PISYS” and give URL as /igwj/odata/SAP/ZMKA_EMP_DATETIMEOFFSET_KEY_SRV;v=1 and Save it.
Once you save, all the available Resources should come in Resources Tab
And Created API should get saved.
You can manage this OData endpoint by applying different policies
Great blog! Thanks for walking us through it!
Great blog with helpful hints and screenshots!
combining PI/PO with API Management offers a lot of possibilities to open up interfaces in a secure and performant manner for partners and B2B thorough APIs.
Thanks for walking through us for exposing OData service registered in SAP PI/PO gateway Hub.
Awaits for your next blog on exposing the Rest/SOAP based Interfaces of SAP PI/PO.
Also If I have interace available in SAP PI/PO can that be exposed as OData Service through API's ?
Thanks for you feedback.
Q:"Also If I have interface available in SAP PI/PO can that be exposed as OData Service through API’s ?"
A:Can you please elaborate which interface you are talking about?
If we have ODATA services defined the in ERP system via SEGW, then is the idea to have the PI/PO system act as the Gateway hub system?
We have older interfaces going out of the ERP system through PI and newer ones going through Gateway, and 3rd party systems going through PI, and it would be nice to treat all of these in a unified manner.