Skip to content

Add documentation for default headers #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+85 −1
Open

Add documentation for default headers #164

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
46 changes: 45 additions & 1 deletion docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,49 @@

# Configure the AMQP Sender Adapter

You use the Advanced Message Queuing Protocol \(AMQP\) sender adapter to consume messages in SAP Cloud Integration from queues or topic subscriptions in an external message broker.
You use the Advanced Message Queuing Protocol \(AMQP\) sender adapter to consume messages in SAP Cloud Integration from queues or topic subscriptions in an external message broker or from the SAP Event Mesh.

## Default Headers

Each time an Iflow is triggered via this Adapter the following Headers are present:

*Headers have to be listed in Allowed Header(s) for Iflow*
<table>
<tr>
<th valign="top">

Header

</th>
<th valign="top">

Description

</th></tr>
<tr>
<td valign="top">

*JMSRedelivered*

</td>
<td valign="top">

Indicates if the message is retried. Values: true/false

</td>
</tr>
<td valign="top">

*JMSXDeliveryCount*

</td>
<td valign="top">

The count of how often the Message is retried. First Read has Count 0.

</td>
</tr>
</table>


> ### Note:
Expand All @@ -24,6 +65,9 @@ You use the Advanced Message Queuing Protocol \(AMQP\) sender adapter to consume
> ### Note:
> This adapter exchanges data with a remote component that might be outside the scope of SAP. Make sure that the data exchange complies with your company’s policies.

> ### Note:
> There is no option to configure a delay in retry processing in the AMQP adapter because this is not supported by the AMQP protocol.



Once you have created a sender channel and selected the AMQP sender adapter \(TCP or WebSocket\), you can configure the following attributes. See [Overview of Integration Flow Editor](overview-of-integration-flow-editor-db10beb.md).
Expand Down
40 changes: 40 additions & 0 deletions docs/ci/Development/data-store-sender-adapter-4f5ef3f.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,45 @@ You can model the steps that write into the data store and those that consume me

If multiple worker nodes are set up, there's no parallel processing of the same data store entry by these multiple worker nodes.

## Default Headers
Each time an Iflow is triggered via this Adapter the following Headers are present:

*Headers have to be listed in Allowed Header(s) for Iflow*
<table>
<tr>
<th valign="top">

Header

</th>
<th valign="top">

Description

</th></tr>
<tr>
<td valign="top">

*SAP_DataStoreRetries*

</td>
<td valign="top">
The count of how often the Message is retried. First Read has Count 0.
</td>
</tr>
<td valign="top">

*SAP_MessageProcessingLogID*

</td>
<td valign="top">

The ID of the entry. Can be used for update or delete actions. See: [Define Data Store Operations](define-data-store-operations-79f63a4.md)

</td>
</tr>
</table>

> ### Tip:
> You can use this feature to implement scenarios with quality of service Exactly Once for cases when the sender hasn't any mechanism in place to retry messages.
>
Expand Down Expand Up @@ -201,3 +240,4 @@ Enter a value for the timeout of the in-progress repository. After this time, a
</tr>
</table>


Loading