Skip to content
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

Jump to bottom

Update data-store-variables-and-jms-queues-when-to-use-which-option-6… #27

Merged
merged 1 commit into from
Dec 14, 2023
Merged

Update data-store-variables-and-jms-queues-when-to-use-which-option-6… #27

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
4 changes: 2 additions & 2 deletions ...lopment/data-store-variables-and-jms-queues-when-to-use-which-option-6bc21cb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@ JMS queue
</td>
<td valign="top">

You can use the JMS sender adapter to store messages in a JMS queue. One important key characteristic of the Java Message Service \(JMS\) feature is the support of high-speed messaging with high throughput. This is why it offers the optimal solution for reliable messaging using asynchronous decoupling. JMS is a Java-based standard application programming interface \(API\) for sending and receiving messages. It enables efficient asynchronous communication based on a JMS message broker between different components. The JMS message broker is a separate runtime component that ensures that messages in JMS queues in the JMS message broker are treated separately. The JMS adapter is used to store messages in the JMS queue and to consume messages from the JMS queue in the JMS message broker.
You can use the JMS receiver adapter to store messages in a JMS queue. One important key characteristic of the Java Message Service \(JMS\) feature is the support of high-speed messaging with high throughput. This is why it offers the optimal solution for reliable messaging using asynchronous decoupling. JMS is a Java-based standard application programming interface \(API\) for sending and receiving messages. It enables efficient asynchronous communication based on a JMS message broker between different components. The JMS message broker is a separate runtime component that ensures that messages in JMS queues in the JMS message broker are treated separately. The JMS adapter is used to store messages in the JMS queue and to consume messages from the JMS queue in the JMS message broker.

The processing sequence used by the JMS adapter is first-in, first-out \(FIFO\). However, because of parallel processing and retry handling this does not mean that messages are processed in a guaranteed order.

Expand Down Expand Up @@ -122,7 +122,7 @@ What is the frequency of consumption?
</td>
<td valign="top">

Whenever a message is initiated by a client's call or a timer \(scheduler\)
Whenever a message is initiated by a client's call or a timer \(scheduler\), or pushed to the integration flow automatically by the Data Store sender adapter.

</td>
<td valign="top">
Expand Down
Loading