To access the payload in a Groovy script, you must use the message object and call the getBody() method on it. The message object represents the current message that is being processed in the integration flow. It has methods to get and set the message body, headers, properties, and attachments. The getBody() method returns the message body as an object of the specified type, such as java.lang.String, java.io.InputStream, or org.w3c.dom.Document. Reference: General Scripting Guidelines | SAP Help Portal, Message | SAP Help Portal

In the SAP Integration Suite, you can change the virtual host name in the Settings APIs. The Settings APIs allow you to configure various aspects of your API provider, such as the virtual host name, the base path, the authentication method, and the CORS settings. Reference: Integration Software | SAP Integration Suite, Modernize Integration with SAP Integration Suite | openSAP

The "Trace" log level expires after 10 minutes and the log files are removed after 1 hour. The "Trace" log level is the most detailed log level that can be set for an integration flow. It records all the information about the message processing, such as headers, properties, payloads, attachments, and exceptions. However, it also consumes more resources and storage space than other log levels. Therefore, it is recommended to use it only for troubleshooting purposes and for a short duration. The "Trace" log level can be activated from the Monitor Message Processing view or from the integration flow editor. Reference: Log Levels | SAP Help Portal, Activating Trace Log Level | SAP Help Portal

An API consumer is an application or system that invokes an interface provided by an API provider. An API consumer uses the interface to access or manipulate data or functionality exposed by the API provider. An API consumer can be a web browser, a mobile app, a cloud service, or any other client that can send requests and receive responses from an API provider. Reference: Integration Software | SAP Integration Suite, Modernize Integration with SAP Integration Suite | openSAP

You use exception-handling subprocesses in an integration flow to handle unexpected errors. Exception-handling subprocesses are special types of subprocesses that are triggered when an error occurs in the main process or another subprocess. You can define custom actions and logic to handle different types of errors using exception-handling subprocesses. Reference: Modernize Integration with SAP Integration Suite | openSAP