Reprocess Configuration
  • 02 Sep 2022
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Reprocess Configuration

  • Dark
    Light
  • PDF

Introduction

When a message from a downstream system is invalid or has data problems, functional support teams have two options. They can either request the message to be resent from the source system, or they can reprocess it by resubmitting the inbound message.

The first option takes more time because it requires communication between the source system support team and the integration functional support team. The second option is far more convenient and time-saving, especially when dealing with real-time mission-critical issues.

Serverless360 Business Activity Monitoring enables message correction and reprocessing by submitting to the following endpoints:

1. HTTP Web Endpoints.
2. Azure Service Bus Queue.
3. Azure Service Bus Topic.
4. Azure Event Grid.
5. SFTP Endpoint.

The Business Activity Monitoring environment keeps track of the count of reprocessed transaction instances.

reprocessed.png

Configure Reprocessing

  • The transaction/transaction stage can be reprocessed to any of the various endpoints to increase the dynamic nature of the reprocessing.

  • Business Activity Monitoring makes it simple to reprocess failed transactions. This is accomplished by right-clicking the desired stage and selecting Configure reprocess.

  • Select any of the available Endpoint types from the dropdown.

  • Enter the necessary information and click the Update button to save the reprocess configuration for the respective stage. Finally, press the Save button to apply the configuration to that stage.

HTTP Endpoint

  • After selecting the HTTP Endpoint as Endpoint Type, it will prompt the user to enter the Uri and to select the respective method type as either PUT or POST. Users can also Add or Remove headers.

HTTP endpoint.png

Azure Service Bus Queue

  • After selecting Azure Service Bus Queue as Endpoint Type, it will prompt the user to enter the Service Bus Connection string and Queue name. Users can also specify the User Properties and System Properties.

Service bus que.png

Azure Service Bus Topic

  • After selecting Azure Service Bus Topic as Endpoint Type, it will prompt the user to enter the Service Bus Connection string and Topic name. Users can also specify the User Properties and System Properties.

Service bus topic.png

Azure Event Grid

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

Event grid.png

Hide sensitive HTTP headers

  • When the Reprocess settings of a transaction are configured with an HTTP endpoint, highly secure information such as tokens or passwords may be sent in the headers to that HTTP endpoint. These secured pieces of information must not be displayed to users who reprocess the appropriate transactions.

  • This can be achieved by marking the required HTTP headers as Sensitive.

Sensitive headers.png

  • The header values marked as Sensitive will be masked to the users who reprocess the transaction and they cannot be deleted or updated.

SFTP Endpoint

When SFTP is chosen, users will have to provide valid details for Host(Server IP/Domain name), Port number(SSH port number), file Path along with User name and Password.

sttp.png

Masking Vital Information

  • While tracking real-time data for a transaction, it is necessary to conceal critical information from customers.

  • Serverless360 hides the details of the Service Bus connection string for the Service Bus Queue/Topic endpoints while tracking instances for a transaction.

img.png

  • The Service Bus connection string details will be available to the user while performing reprocess configuration for a stage in a transaction.

Visible.png

  • The URI value for the HTTP endpoint is also hidden while tracking instances for the relevant transaction.

  • The Topic endpoint value is hidden from customers when it comes to the Event Grid endpoint.


Was this article helpful?