Message Reprocessing
  • Updated on 10 Jul 2019
  • 2 minutes to read
  • Contributors
  • Print
  • Share
  • Dark
    Light

Message Reprocessing

  • Print
  • Share
  • Dark
    Light

Overview

When a message from a downstream system is invalid or has issues with data, functional support teams will have two choices. Either they can request the source system to resend the message, or they can reprocess it by resubmitting the inbound message. The former option is time-consuming as it involves communication between the source system support teams and integration functional support teams. The latter option is much more convenient and time-saving, especially when addressing real-time mission-critical issues.

Serverless360 BAM brings the ability to correct and reprocess messages by submitting to following endpoints:

1. Http Web Endpoints
2. Azure Service Bus Queue
3. Azure Service Bus Topic
4. Azure Event Grid

Configure Reprocessing

In Serverless360, failed transactions can be reprocessed. This can be achieved by configuring Reprocess at a stage. The following steps must be followed to configure reprocess at stage level.

  1. Click the Configure Reprocess button which will be present at a respective stage

  2. Click Select to select the available Endpoint types

    • After selecting the Http Endpoint as Endpoint Type, will prompt you to enter the Uri and you have to select the respective method type as either PUT or POST. You can also able to Add or Remove headers.

image.png

  • After selecting Azure Service Bus Queue as Endpoint Type, will prompt you to enter Service Bus Connection string and Queue name. You can also specify the user properties and system properties.

image.png

  • After selecting Azure Service Bus Topic as Endpoint Type, will prompt you to enter Service Bus Connection string and Topic name. You can also specify the user properties and system properties.

image.png

  • After selecting Azure Event Grid as Endpoint Type, you need to mention Topic endpoint, Topic key, Subject and Data version of the respective configuration. You can also specify the event type if its necessary.

image.png

Enter the appropriate details, click Done and Save to save the reprocess configuration for that stage.

Reprocessing Failed Transaction

Once all the configuration is done, go to the BAM section and select a failed transaction as shown below.

image.png

On clicking the tracking data, you will see a graphical flow in a blade as shown below.

image.png

When you click the Reprocess button, you will be directed to a blade in which you will be allowed to edit the archived message or reprocess configuration and reprocess it to the respective configured Endpoint Type.
image.png

Bulk Reprocessing

For Bulk reprocessing of messages, you need to map a reprocess setting of a particular stage to that respective transaction.

image.png

After mapping the reprocess settings, you can reprocess multiple transactions from the BAM UI, by selecting the required transactions and click Reprocess.

image.png

This will reprocess the respective selected transactions and it will provides the respective reprocess results.

We'd love to hear your thoughts
Please visit our feedback system to suggest new Features or Enhancements. You can also take a look at our Roadmap
Was this article helpful?