Tutorial

  1. Home
  2. Docs
  3. Tutorial
  4. 10. How to use message reprocessing?
  5. 10.3 How to use message reprocessing per integration

10.3 How to use message reprocessing per integration

Learning Objectives:-

This unit describes:-

  • Describe what is message reprocessing per integration?
  • Comfortably use message reprocessing per integration.

Introduction:-

Message reprocessing job reprocesses all messages from all integration. We can exclude or include an integration to be reprocessed or not. With the flag „Automatic Reprocessing“ on the integration detail, we can include (checked) or exclude (unchecked) the integration from the reprocessing.

Message reprocessing is the process to be used for reprocessing failed and pending message from the previous integration. It might be failed if the user does not edit or edit wrong business logic in IMessage Data.

There are two cases for MessageReprocess job to correct the message records. The different cases we support are:

– Pending Message

– Failed Message  

Pending Messages:-

Pending messages are showing in yellow color. The message is Pending because of a lot of reasons. They have been shown in Comment. It is one of many reasons that causes Pending, for example, „This message has not met a condition of all workflows“.

Failed Messages:-

Failed messages are showing in red color. The message is Failed because of a lot of reasons, they have been shown in the Comment. This is one of many reasons, such as it missed some fields and incompleted. For example, it is “After evaluating the data source (accountname), no data passed for the mapped external id field (Name) and After evaluating the data source (accountname), no data passed for the mapped external id field (Name).“

Purpose:-

With this scheduler, we have great flexibility to run different interface groups at different times. With the new scheduler to schedule similar like the Agent, we can also scheduler at different days and not only for every minute like we have today. The priority handling would be inside each group and not over different interface groups.

We still use the SKYVVA default group where all interface for each integration is kept. If we don’t have an additional interface group the integration scheduler would work on the default group. We should separate between inbound and outbound reprocessing scheduler because for outbound the reprocessing is different than for inbound messages. For the outbound message, we have a callout which for example don’t need the scope size and needs to run immediately one by one.

Pre-requisite:-

Step1: We have to create one integration. Please refer our tutorial to create integration()

Step2: We have to create ten interfaces in one integration. In which six interfaces are inbound interfaces and the remaining four interfaces are an outbound interface.

Step3: To reprocess all the interface automatically, we have to check the Automatic Reprocessing flag at the integration level.

How to reprocess messages per Integration?

We can reprocess messages as:

  1. MessageReprocessPerIntegration scheduler with every min Time Interval
  2. MessageReprocessPerIntegration scheduler with Run At (IntegrationOnDemand)
  3. MessageReprocessPerIntegration scheduler with Run At Every Hour (IntegrationOnDemand)

Case 1: MessageReprocessPerIntegration scheduler with every min Time Interval:

Testing MessageReprocessPerIntegration scheduler with every min Time Interval (IntegrationOnDemand) with using Automatic Reprocessing flag. We have to follow the given step to reprocess messages per integration.

Step4:  Go to scheduler tab and Set scheduler 2 min in MessageReprocessPerIntegration.

Case 2: MessageReprocessPerIntegration scheduler with Run At (IntegrationOnDemand)

Testing MessageReprocessPerIntegration scheduler with Run At (IntegrationOnDemand) with using Automatic Reprocessing flag.

Set time Run At 5:00 PM

Case 3: MessageReprocessPerIntegration scheduler with Run At Every Hour (IntegrationOnDemand)

Testing MessageReprocessPerIntegration scheduler with Run At Every Hour (IntegrationOnDemand) with using Automatic Reprocessing flag.

–Set time Run At Every Hour = 6->8:00 AM

It will run at 6-8:00 AM every day and running all Interfaces stays in this integration.

Was this article helpful to you? Yes No

How can we help?