Connect Oracle GoldenGate Classic Architecture to Microservices Architecture

Oracle GoldenGate Classic Architecture uses the data pump Extract in Admin Client and GGSCI to connect to Microservices Architecture

Note:

Oracle GoldenGate Classic Architecture's pump Extract can only connect to an un-secured Microservice Architecture deployment, of which the receiver server's port is open for ingress traffic.

If the above requirement is a security concern, it is recommended to install Microservices Architecture on the same target, along with Classic Architecture, and use a reverse proxy server to allow wss distribution path between these two Microservices Architecture deployments. After this distribution path is established, the Classic Architecture deployment can pick up the trail from the same location on the target.

To connect Oracle GoldenGate Classic Architecture and Microservices follow these steps:

Note:

To establish a connection between Oracle GoldenGate Classic Architecture and Microservices, only non-secured MA deployments are supported. Secure Microservices Architecture deployments are not supported.

Create a data pump Extract

Note:

To perform this task, an existing data pump Extract must be running in Classic Architecture.

Log in to GGSCI.
Add a data pump Extract using the command:

ADD EXTRACT dp_name, EXTTRAILSOURCE ./dirdat/aa

This example uses, dp_name as the name of the data pump Extract.
Add the remote trail to the data pump Extract using the command:
```
ADD RMTTRAIL ab, EXTRACT dp_name, MEGABYTES 500
```

Edit the parameter file for the data pump Extract using the command:

EDIT PARAMS dp_name

Here is an example of the data pump Extract parameter file:

EXTRACT dp_name
RMTHOST hostname-or-IP-address, PORT receiver-service-port
RMTTRAIL ab
PASSTHRU
TABLE pdb.schema.table;

Start the data pump Extract

Use the following command to start the data pump Extract dp_name:

START EXTRACT dp_name

Once the data pump Extract has started, the Receiver Service establishes a path and begins reading the remote trail file. The remote trail file appears in the $OGG_VAR_HOME/lib/data of the associated deployment running the Receiver Service.