Oracle® Retail Bulk Data Integration Implementation Guide Release 16.0.027 E94818-01 |
|
Previous |
Next |
The BDI infrastructure applications move data from one application to another. So there is data producing applications and data consuming applications. Depending on the customer needs, the data produced by an application may be used by one or more consuming applications. This leads to different deployment architectures for various needs.
In all of the topologies presented, regardless of the examples presented, in practice, the sender and receiver locations can be on-premise, cloud, or hybrid deployments. BDI is designed to be location transparent.
In this deployment topology, there is only one consumer for an interface module (An interface module may have one or more interfaces).
Note: In the case of where there are multiple receivers for the data, this topology is not the most efficient. |
A detailed diagram of a point to point topology usage in Oracle Retail is shown below.
In the case of Sender Side Split (SSS), the data is extracted once from the source system. The extracted data is transmitted to each destination separately. Since, unlike point to point topology, the extraction done only once regardless of the number of destinations.
A detailed diagram of sender side split topology usage in Oracle Retail is shown below.
The Receiver Side Split (RSS) topology is used for multi destination data transfer such as Sender Side Split. In this topology data is extracted and transmitted to the destination only once regardless of the number of destinations. This topology differs from the sender side split in the number of times the data is transmitted.
Receiver side split can only be used if all the destinations have a shared network drive access. This is the most optimal multi destination data transfer topology.
A detailed diagram of receiver side split topology usage in Oracle Retail is shown below.