2024 May 23 2:38 AM - edited 2024 May 23 7:50 AM
Dear All,
I am working on exposing an Integration Flow Endpoint as an API using API Management. I've followed several blogs and the tutorial "Expose Integration Flow Endpoint as API." However, I am struggling to get my iFlow endpoint to work with certain policies. Could you please advise if you have a good resource or knowledge base that we can follow step-by-step to achieve this?
Here is what I have done so far:
My questions are:
I feel lost amidst multiple blogs and help links, and I haven't been able to find a single place that clearly explains how to expose this endpoint with basic policies like OAuth, Allowed IPs, Exception Handling etc.
Thank you for your help and guidance.
Screenshots:
Your http path seems to be wrong. I did setup an API to CPI (Neo) a few weeks ago as well. However, I didn't configure an API Provider but linked it directly via HTTP.
Let's say, your iFlow has the following endpoint:
- https:// <host> -iflmap.hcisbp.eu2.hana.ondemand.com/http/Status
Meaning, you configured "/Status" as path in the iFlow.
Now, in the API Management, you need to configure it as following:
API Base-Path: https:// <your api path >/Status
Target-URL: https:// < your host > -iflmap.hcisbp.eu2.hana.ondemand.com/http
Hints:
All URL appendices after the api path, here "/Status", will be sent to the iFlow. Therefore, at the iFlow URL, I left out the "/Status".
Further, I used URL as a target provider but API Provider should work as well. I just didn't have the licence. If you found the iFlow via discovery, this should be already fine.
For your case, change the following:
- iFlow trigger path from "/permit/status" to "/v1/permitstatus"
- Target-End-Point url from "/http/permit/status" to "/http"
Debugging:
The whole setup can be tested via postman.
For the CPI, just call the oAuth URL with credentials to get a token. Then find the correct path for the iFlow.
For API Management, activate debugging in the API Portal and send a request from Postman. Within the debugging, you should be able to see what is the CPI URL that is called.
I hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you. It helped me a bit. I was able to call the API through Postman without any authentication as I didn't put any policies.
But I couldn't debug although I swithed it on in the API portal but there is nothing found upon refreshing or stopping debug session. How this works in general? I want to see end to end what data and paramters are going to CI and client?
The payload is hidden due to security. You can see only url, header and properties. In the last step, bottom left, you can see the target host and path. This should point to your iFlow. As I can see from your screenshot, your API Management seems fine as all of the steps are green. Do you see any call in the CPI?
Here, I forced an error in API Management by using a wrong path. The last step, "blue", shows the path:
I can't post any screenshots in the comment section directy. Only when I edit. Is it the same for you?
User | Count |
---|---|
62 | |
12 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.