Often when a new system is brought into an existing integration the messages for the last few months or years are replayed to bring the system up to speed. Iguana X provides a solution for this in the form of log resubmission.
...
title | STEP 1 : Add a Custom component called Destination |
---|
From the previous parts, we have a component set up with 5 years of log data. In order to try this out, we will need another component.
From Iguana X’s dashboard, click + Component
In the Add Components dialog that pops up, select Custom, which should be the first option
It is recommended to change the name of the component. This guide proceeds assuming you renamed it
Destination
Then click Add in the bottom right of the dialog
You should see a new component appear on the dashboard
...
In order to reposition a component queue you need to have linked components (at minimum a source and destination component) with log data.
From the Component Card:
Here you can only trigger a queue reposition using the destination component - requires selection of a linked upstream component queue to reposition.
Expand | ||
---|---|---|
| ||
Now we will need to link the two components together so that messages can be pushed from one component to another . Assuming
| ||
| ||
Expand | ||
---|---|---|
| ||
Now that the components are linked, we can reposition the queue. From Iguana X’s dashboard, double click on In the Queue Position row click reposition Change the date to go back 5 years:
After clicking reposition the dialog will close itself and you will see the updated queue position in the component card: Then close the card and pay attention to fact that there should be a large number of days of logs in the QUE column on the dashboard. |
Expand | ||
---|---|---|
| ||
Going to the Logs tab and selecting Going back to the dashboard and running the |
Now that you have lots of Logs present in IguanaX, you may want to delete them as they take up some space, please continue to our next page on Log Management and Purging.
Next Log Management and Purging
...
From the Log Details:
Here you can only trigger a queue reposition using the upstream component - requires selection of a linked downstream component queue to reposition.
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
|
Expand | ||
---|---|---|
| ||
Click on the Last Log timestamp in the component card, you should see a log message showing that a new queue position was accepted: Going back to the dashboard and running the |