In SAP Cloud Integration, a Groovy script step operates on the current message being processed in the integration flow. The scripting environment provides a predefined variable named message, which is an instance of the com.sap.gateway.ip.core.customdev.util.Message class. This Message object encapsulates the payload (body) and headers. To access the payload within the script, you must invoke the getBody() method on this message object. This method returns the body of the message, which can then be manipulated as needed.

A. camelcontext: The CamelContext represents the Apache Camel runtime environment; it manages routes and components, but does not directly hold the message payload for scripting access.

B. property: A property is metadata stored on the exchange (not the message) and is accessed using methods like getProperty(), not getBody().

C. header: A header is metadata associated with the message and is accessed using methods like getHeader(). The getBody() method is not called on a header.

1. SAP Help Portal

SAP Cloud Integration: Groovy Scripting API

com.sap.gateway.ip.core.customdev.util.Message class documentation. This official source details the Message class provided in the scripting context and explicitly lists the getBody() method

stating it "Returns the message body."

Reference: SAP Help Portal -> SAP Cloud Integration -> Develop Integration Content -> Use the Cloud Integration Design Tools -> Define Script -> Groovy Scripting API.

2. SAP Help Portal

SAP Cloud Integration: Define Script for Groovy. This document explains the function of the Script step and the variables available to the script developer. It specifies that the processData function receives a message object as an argument.

Reference: SAP Help Portal -> SAP Cloud Integration -> Develop Integration Content -> Use the Cloud Integration Design Tools -> Define Script. The section on "Script Execution" clarifies the processData(Message message) method signature.