Shaker Cockpit

From PlcWiki

On some routes selected cockpits enter the line twice. Each with a different sequence number, with the same product ID. A special dataflow is created to capture this. E.g. GOL460.

Dupcheck determines the target service according to the criteria. In GOL460, this is one of the headers. If it is a shaker cockpit, it sends the cockpit to a specially configured dupcheck shakertestwrite .

This dupcheck has no "duplicates target" (DuplicatesDir = ""), it only stores all through cockpits in a "check dir" and has the MaxAgeDays parameter set to keep the cockpits only for a given time interval. For naming, it uses only the cockpit ID to duplicate the cockpit with the same ID regardless of the sequence number. The goal is 'dispatcherdirq' , which sends data to target services. Kernel, etc.

On the second pass, the cockpit no longer bears the "SHAKER" flag, so it will pass from dupcheck to shakercheck service.

This is a specially configured Dupcheck. Shared check dir with 'shakertestwrite' dupcheck. It does not write to it (WriteToCheckDir = false). If a through cockpit is found to be a duplicate, it is not stored in the directory duplicate, but forwarded to another service (DuplicateTargetService = shakerdeliveryconvertor).

The shakerdeliveryconvertor 'sets the second pass flag on the cockpit and sends it to the dispatcherdirq' .