Skip to Content

Changes for page Manage Message Redelivery

Last modified by Danniar Firdausy on 2024/09/18 21:26
From version 16.5
edited by Danniar Firdausy
on 2024/09/05 09:03
Change comment: There is no comment for this version
To version 16.7
edited by Danniar Firdausy
on 2024/09/18 21:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -5,7 +5,7 @@
5 5  Please note that this microlearning is for the new monitoring stack only.
6 6  {{/warning}}
7 7  
8 -In this microlearning, we will learn how you can view the messages that are currently waiting for message redelivery. On top of that, we will learn how you can perform actions on these messages. The primary step we will be focusing on is the redelivery of the message itself.
8 +In the previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Message Redelivery.intermediate-message-redelivery-configuration-gen3.WebHome||target="blank"]], we have learned how to configure Message Redelivery functionality for a specific flow towards a system. In this microlearning, we will learn how you can view the messages that are currently waiting for message redelivery. On top of that, we will learn how you can perform actions on these messages. The primary step we will be focusing on is the redelivery of the message itself.
9 9  
10 10  Should you have any questions, please get in touch with academy@emagiz.com.
11 11  
... ... @@ -32,8 +32,6 @@
32 32  
33 33  == 3. Manage Message Redelivery ==
34 34  
35 -In this microlearning, we will learn how you can view the messages that are currently waiting for message redelivery. On top of that, we will learn how you can perform actions on these messages. The primary step we will be focusing on is the redelivery of the message itself.
36 -
37 37  The message redelivery overview can be found in the Manage phase of eMagiz. Within Manage you can navigate to Explore -> Redelivery to access the overview. In this overview you can search on the queue name or on the original ID (as can be found in the error message under the header called jms_messageId).
38 38  
39 39  {{info}}Note that the overview is sorted ascending on date. This means that the oldest message is shown on top and the latest message is shown at the bottom of the list.{{/info}}