Store and Forward routes

Routes between systems are primarily defined in the StoreAndForward table; however, the data delivered over these routes is defined through doas_dataset and doas_privilege records which must be configured prior to StoreAndForward records.

The image above shows a system that has a total of six routes. For data that is owned by ES; a Store and Forward route replicates the data to Main, which is then responsible for forwarding the data to Backup and DSS. Each established route also needs to be capable of going backwards. That way, if data modifications are made at Backup or DSS, there is a route back to Main which can forward it back to ES.

For any system that shares data between multiple connected computers; you can define two types of routes in the Route Type field on the StoreAndForward Row Details dialog boxl: direct and store and forward. You will use a store and forward route type whenever you expect data to be forwarded to multiple locations in a defined route. When you want to eliminate some, but not all of the routes that a star-configuration would have, a direct route can be used to get information from an owning system delivered straight to another system that subscribes to its data.

Note: To mimic the example above where Main is chosen as a Store and Forward system, all established routes would be configured as store and forward using the System Name field to define where the route starts and the Destination System field to define where the route goes to.