5 DS Retry Route

This route saves data to a reserve Data Storage. If the route is not able to save a message at the first attempt, XEServer makes 3 more attempts to store the message (the number of attempts is controlled by the XEServer environment property ${RetryCountNum}), and if this fails, XEServer stores the message in an archive for further investigation. If XEServer is able to store the message successfully, the route sends the message to 3 Validate Error Route.

There are two ways to start the processing on this route: either manually or by a timer. To activate the route processing manually and to disable route activation by a timer, set the XEServer environment property ${TimerEnabled} to false and copy the file trigger.txt from the directory ${XESProfileConfig}/samples to the directory ${XESWorkspace}/test-data/Inbound/TriggerManual_DS.

Route Structure

Route Components Description

Component Name	Component Type	Description
ManualTrigger	FS Inbound	Picks up a sample file from the file system to initiate the route processing. To do this, drop the sample file ${XESProfileConfig}/samples/trigger.txt to ${XESWorkspace}/test-data/Inbound/TriggerManual_DS and set the XEServer environment property ${TimerEnabled} to false.
Timer Reporting	Timer Reporting	Emits a trigger signal every 4 seconds to initiate route processing.
TimerEnabled?	Router	Conducts timer signals if the XEServer property TimerEnabled is set to true.
StoreDSRetry	FS Inbound	Once the component receives a trigger signal (either manual or generated by a timer), the component picks up data from the 4 Error DS Check route. Note The component works in the By command activation mode, which means that the component waits for a signal to pick up data from the source folder.
CPDSRetry	Checkpoint	Creates a checkpoint in the processing flow. If there is an error further down the route, the component rolls back the processing to the checkpoint position and attempts a retry. If the number of attempts exceeds the component's Retry limit value, the component directs the message to the component's error output.
WithinRetryLimit	Router	Splits the data flow based on whether the current checkpoint retry attempt number is lower than the ${RetryCountNum} value. Tip The combination of the DS Secondary Good, DS Primary Bad and DS NO Error components emulates the work of a single DS component in the Error or No Errors mode based on the value of the XEServer environment property ${DS_Secondary--DS_Good_Enabled_and_DS_Bad_Disabled}
Secondary Good, Secondary Bad	Data Storage Outbound	Based on the WithinRetryLimit Router check, the components write data to the corresponding Data Storage. Note that the components use different XEServer Data Storage services.
Stored in DS	FS Outbound	Sends the messages that were stored in Data Storage to 2 Sample Route.