A Distribution Server is a process that functions as a networked data distribution agent (similar to Pump Extract in CA).
A Distribution Server replaces the classic multiple source-side data pumps with a single instance service.
It provides lightweight data and object filtering.
Unlike data pump processing, a Distribution Server cannot transform data.
It is responsible for conveying and processing data, and dispatching commands in a distributed networked deployment.
A Distribution Server can dispatch trail files to one or more Receiver Servers in a Multiservices deployment. It is also capable of interoperating with the Classic Architecture, delivering trail files to Classic Architecture collectors.
A Distribution Server is able to concurrently handle multiple commands and multiple data streams from multiple source trail files to target trail files, all at once.
A Distribution Server supports multiple communication protocols:
Oracle GoldenGate protocol (ogg) uses the traditional TCP/IP based protocol. Used for communication between the Distribution Server and the Collector in a non-service-based (CA) target. Supported for interoperability with OGG CA.
WebSocket for HTTP/HTTPS-based streaming (ws or wss). This protocol is supported over plain HTTP (ws) or HTTPS relying on SSL/TLS security (wss).
UDT: A UDP-based data transfer protocol for high-speed wide area networks.
Proxy support for cloud environments. CKS5 (SOCKS5) for any network protocol and TTP for HTTP-type protocols only, including WebSocket.
Distribution Server Functionality
You connect to a Distribution Server to:
* Create and Manage Paths
* Stop and Start Paths
* Reposition reading offsets in Trail Files.
* Assign content filters to Paths
A Patch, within an MA deployment, is a channel that connects source trail files to target trail files. In a fully MA context, a Path is established between a Distribution Server and a Receiver Server. In a mixed CA/MA environment, a Path can connect MA servers with CA processes, such as collectors.
The Distribution Server includes an embedded web application.
- You can use the embedded web application to connect directly from any web browsers.
- The embedded web application does not require any client software installation.
- You interact with the Distribution Server using your browser. The TCP/IP port used by the Distribution Server is set up during deployment configuration through the oggca.sh utility.
- Server Collector in CA functions somehow similarly as Receiver Server in MA.
- MA – Microservices Architecture only supports Oracle, whereas CA – Classic Architecture supports both Oracle and Non-Oracle DBs.
- TCP is more reliable but UDT (layer on-top of UDP) is more faster.
- TCP encryption does not work in a mixed environment of CA and MA.
- Further about UDT : https://www.myvirtualinstitute.org/old/oracle-goldengate-microservices-architecture-supports-udt