Exploring SAP Salesforce Adapter - retry mechanism with JMS queue
Builds a retry design for Salesforce update failures in Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp on SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp: a Parent iFlow triggered by a Salesforce push topic calls a Child iFlow, whose Exception Subprocess routes specific Salesforce errors to a separate JMS Retry PD iFlow over a ProcessDirect target address. The retry iFlow stores the failed payload in a JMS queue (Enterprise Edition), retries up to five times with exponential backoff, moves exhausted messages to the dead-letter queue, and mails the Application Maintenance team; the author notes the queue's 10 GB size limit and that polling may pause under load.
Where it sits
Who is behind it
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP Community · integration-suite-tag.
For your agent
- Ref
content:exploring-sap-salesforce-adapter-retry-mechanism-with-jms-queue- JSON
- /content/exploring-sap-salesforce-adapter-retry-mechanism-with-jms-queue.json
- MCP
- Connecting an agent