Skip to main content
Solved

Monitor inbound REST API integration requests

  • February 25, 2025
  • 4 replies
  • 60 views
V
Sidekick (Customer)
Forum|alt.badge.img+7

Hi,

We are currently working on upgrading IFS 10 UPD 22 Application to IFS Cloud 24R1 version.

In IFS 10, Application Message(s) is heavily utilized to monitor  both inbound and outbound bizAPI integration messages. The failed messages can be reprocessed if required.

Eg: If an integration message has failed due to missing basic data in IFS (Eg: Currency), we usually set up the basic data and rerun the failed messages in Application messages window.

 

Is there any feature in IFS Cloud to monitor and reprocess the inbound Rest API integration requests other than referring logs?

 

Thanks

Thilochana

Best answer by dsj

Hi ​@VPPEKANATHI 

 

Hope everything is good with you and nice to see in the community after some time :)

 

In my opinion, Rest API integrations (extend on the outside) should not be compared with IFS Connect based integrations.

Any error resulting from a Rest request will be return to the sender with the http 400 status code and the exception details so it’s senders responsibility to handle the errors and reprocess if needed. You may think its similar to integration using a SDK.

Regarding the IFS Connect and replacement for BizApi based integrations in Apps 10,  There are some integration projections and PLSQL methods as replacements for inbound integration BizApis and you can setup the routing rules addresses to process the incoming requests as application messages, or build your own projection/plsql method for processing the requests.

In that sense, the observability using the application messages still exists but it’s more of an integration design question to decide which path to take.

This might not be the answer you are looking for but hope it gives some idea to distinguish the rest api integrations from IFS Connect :)

 

Cheers and see you around!

Damith

View original
Thilochana Ekanayake
Did this topic help you find an answer to your question?

4 replies

AveTonitM
Sidekick (Partner)
Forum|alt.badge.img+9
  • AveTonitM
  • Sidekick (Partner)
  • 136 replies
  • February 25, 2025

If a IFS cloud Rest API call would end in a error, the error is not visible from IFS Cloud GUI. IFS Kubernetes POD logs have that error information, but the logs are very cumbersome for a monitoring purpose as they would need to be generated and viewed locally from the servers.

Hence we’ve developed a custom page for the purpose of storing integration errors and making them visible for IFS users. This page is updated by the integration platform that execute the Rest API calls, whenever a error occur, so that IFS administrators can view the errors. This solution does not provide any help in reprocessing the erroneous Rest API calls.

-Toni-
V
Sidekick (Customer)
Forum|alt.badge.img+7
  • VPPEKANATHI
  • Author
  • Sidekick (Customer)
  • 33 replies
  • February 25, 2025

Hi Toni,

 

Thanks for your input.

It appears that monitoring inbound requests will be a challenging task in IFS Cloud

 

Thilochana Ekanayake
dsj
Superhero (Partner)
Forum|alt.badge.img+22
  • dsj
  • Superhero (Partner)
  • 828 replies
  • Answer
  • February 27, 2025

Hi ​@VPPEKANATHI 

 

Hope everything is good with you and nice to see in the community after some time :)

 

In my opinion, Rest API integrations (extend on the outside) should not be compared with IFS Connect based integrations.

Any error resulting from a Rest request will be return to the sender with the http 400 status code and the exception details so it’s senders responsibility to handle the errors and reprocess if needed. You may think its similar to integration using a SDK.

Regarding the IFS Connect and replacement for BizApi based integrations in Apps 10,  There are some integration projections and PLSQL methods as replacements for inbound integration BizApis and you can setup the routing rules addresses to process the incoming requests as application messages, or build your own projection/plsql method for processing the requests.

In that sense, the observability using the application messages still exists but it’s more of an integration design question to decide which path to take.

This might not be the answer you are looking for but hope it gives some idea to distinguish the rest api integrations from IFS Connect :)

 

Cheers and see you around!

Damith

DSJ - https://dsj23.me
V
Sidekick (Customer)
Forum|alt.badge.img+7
  • VPPEKANATHI
  • Author
  • Sidekick (Customer)
  • 33 replies
  • March 3, 2025

Hi ​@dsj 

Everything’s great, Thanks. Hope you’re doing well as well.

 

In our scenario, we cannot wait till third party reprocess/attend to the failed integration messages. 

We have to make sure that IFS data/transactions are synced with the master, SAP :)

 

Managed to direct the REST API requests through the IFS SOAP gateway for better control.

Your input has been incredibly helpful in resolving my issue.

Thank you so much!

 

Cheers!

Thilochana

 

 

 

 

Thilochana Ekanayake

Reply


Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings