During an upgrade from IFS Applications 10 UPD22 to IFS Cloud 24R1, Application Messages were previously used to monitor and reprocess both inbound and outbound BizAPI integration traffic. When a message failed (for example because basic data such as a currency was missing), the data could be corrected and the failed Application Message re-run. Is there an IFS Cloud capability to monitor and reprocess inbound REST API integration requests in a similar way, without relying only on logs?
Technical details
Upgrade path: IFS 10 UPD22 to IFS Cloud 24R1. Prior pattern used Application Messages for inbound and outbound BizAPI traffic, including reprocessing after basic-data fixes. Target pattern is inbound REST API (extend on the outside). Community also noted REST failures are not shown in the IFS Cloud GUI and appear in Kubernetes pod logs.
Any attachments are visible to signed-in members.
1 answer
0
✓ Accepted answer
Confirmed design guidance: inbound REST API integrations should not be treated as equivalent to IFS Connect / BizAPI Application Message flows. When a REST call fails, the platform returns HTTP 400 with exception details to the caller; the sending system is expected to handle retries and reprocessing. For BizAPI-style inbound replacements in IFS Cloud, use integration projections and PL/SQL methods, and configure routing-rule addresses so incoming requests are processed as Application Messages, or implement a custom projection / PL/SQL method. Choosing REST-direct versus Connect/Application Message routing is an integration design decision. Community suggestion (not a product reprocessing feature): one partner built a custom page that their integration platform updates with REST errors for administrator visibility; that page does not support reprocessing.
Prerequisites and limitations
Applies to IFS Cloud REST inbound versus Connect/BizAPI patterns. Direct REST errors are caller-handled and not reprocessable from Application Messages unless you deliberately route through Connect/Application Message designs. Custom error pages are partner-built and do not restore failed REST calls.