The Apache Camel Exchange is the fundamental container for messages being processed within SAP Cloud Integration. Its standard structure includes an Exchange ID for unique identification, an InMessage which holds the input payload and headers, and a property to store an Exception if an error occurs during routing. Runtime node information, which pertains to the specific worker node executing the process, is environment-specific metadata and not a standard, built-in component of the platform-agnostic Camel Exchange message model itself.

A. InMessage: The InMessage is the mandatory input message within the Exchange, containing the body and headers at the start of a route.

B. Exception: The Exchange has a dedicated property to hold any java.lang.Exception object that is thrown during message processing.

C. Exchange ID: Every Exchange is assigned a unique ID, which is essential for message tracking, logging, and correlation.

1. Apache Camel Documentation (Official Vendor Documentation): The Javadoc for the org.apache.camel.Exchange interface

which is the foundation for SAP CPI's message processing

explicitly defines the core components. It includes methods like getExchangeId()

getIn()

and getException(). There is no standard method or property for runtime node information.

Source: Apache Camel 3.x Javadoc

org.apache.camel.Exchange interface.

2. SAP Help Portal (Official Vendor Documentation): The SAP Cloud Integration documentation describes the message processing model

which is based on the Camel Exchange. It details the structure containing the message (In/Out)

headers

properties

and the handling of exceptions.

Source: SAP Help Portal

Cloud Integration – "Understand the Message Processing Model". This section outlines the message structure

which aligns with the Camel Exchange model and does not include runtime node as a default component.