Response AMQP

Alias

Selection of an AMQP 1.0 alias (see AMQP 1.0 connections). Required field.

Type

Defines whether a Queue or a Topic is used as the destination.

RPC

If the checkbox is checked, the call is made synchronously (Request/Response). Otherwise, it is sent asynchronously. When RPC is enabled, additional fields appear (see section Settings when RPC is enabled).

Queue/Topic

Name of the queue or topic to which the message is sent. Required field. Some brokers require an additional prefix, e.g., queue: or topic: for SAP Event Mesh.

Persistent/Durable

Marks the message as "durable"; the broker then stores it permanently if possible. Whether the message is actually persisted depends on the broker and its settings. Does not apply to RPC.

Mark whole job as failed if this response fails

Normally, a job is not necessarily considered failed if a single response path fails (see section Error behavior). This option enforces that the entire job is considered failed if this response path fails.

Additional text on error

Optional, additional log text for the error case.

RPC Timeout

Specifies (in seconds) how long the sending profile waits for the RPC response message provided by the AMQP broker on the temporary reply queue. If this timer expires, the RPC call itself is considered failed. Example of an error message: "Got no response from AMQP 1.0 RPC call within 20000ms".

Following profile

The specified profile must be active and have an input agent of type Message.

Max. execution/life

Specifies the maximum total time (in seconds) for executing the response, including sending, processing, and any retry attempts. The specific behavior depends on the message type (see Message types). The minimum lifetime of the message is 12 hours (regardless of the configured value). With the retry mechanism, this value also controls the retry behavior from the connection settings (permitted execution time across all retry attempts).

Message-Type

Type of message. Possible values: Synchronous, Asynchronous, Persistent (see section Message types).

Synchronous

The profile sends the message and does not continue until the response has been received. It waits until the target profile has finished its processing (successfully or with an error). If the time set under Max. execution/life is exceeded, the response aborts with an error, even though the target profile might succeed later.

Asynchronous

The profile sends the message and continues immediately; the response is irrelevant for further profile execution. The profile does not wait for the target profile; instead, the response ends successfully after the data has been transferred. The time set under Max. execution/life is the maximum lifetime of the message; if it could not be received by the target profile within this time, it is deleted.

Persistent

Works similarly to Asynchronous. In addition, if the destination is unavailable, the message is stored, and an attempt is made to send it every 50 ms. If no success is achieved within the time set under Max. execution/life, the message is lost.