For establishing a connection to Classic Architecture, the Distribution Server in Oracle GoldenGate Microservices Architecture must know where to place the remote trail file for reading.
To connect Oracle GoldenGate Microservices Architecture and Classic Architecture follow these steps:
Note:
For this procedure to work, an existing Extract must be running in Microservices Architecture.From the Service Manager, click Distribution Server.
Click the plus (+) sign next to Path. The Add Path page is displayed.
Enter the details:
Options | Description |
---|---|
Path Name |
Select a name for the path. |
Description |
Provide a description. For example, the name of the Extract and Replicat names. |
Source: Trail Name |
Select the Extract name from the drop-down list, which populates the trail name automatically. If it doesn’t, enter the trail name that you provided while adding the Extract. |
Generated Source URI: |
A URI is automatically generated for the trail based on the Extract information you provided. You can edit this URI by clicking the pencil, then modifying the source. Typically, you will need to edit the URI if you want to use reverse proxy. |
Reverse proxy enabled? |
Select to use reverse proxy. To know more about configuring you reverser proxy servers, see Reverse Proxy Support in Securing the Oracle GoldenGate Environment |
Target |
Enter the target endpoint of the path. From the drop-down list, select your data transfer protocol. The default option is You also need to enter the URL of the target host, for example, localhost, if the target is on the same system. You may enter the port number of the Receiver Server and the trail name of the Replicat you created earlier. However, it’s not mandatory. The port is the Manager port number for Classic Architecture. Path takes the source trail and sends the date to a target trail given here, which can be consumed by any Replicats created later. |
Use Basic Authentication |
Select to add a credential to the target URI creating basic MA authentication. |
Generated Target URI |
A source URI is automatically generated for the trail based on the Extract information you provided. You can edit this URI by clicking the pencil, then modifying the source. |
Configure Trail Format |
You can optionally toggle this switch to select one of these types |
Begin |
Select the point from where you need to log data. You can select the following options from the drop-down list:
|
Source Sequence Number |
Select the sequence number of the trail from source deployment Extract. |
Source RBA Offset |
This setting provides the RBA of the record for the source deployment. |
Critical |
The default value is false. If set to true, this indicates that the distribution path is critical to the deployment. |
Auto Restart |
The default value is false. If set to true, the distribution path is restarted automatically when killed. |
Rule Configuration | Description |
---|---|
Enable filtering |
If you enable filtering by selecting it from the toggle button and click the
You can also see the JSON script for the rule by clicking the JSON tab. |
Additional Options | Description |
---|---|
Eof Delay (cent sec) |
You can specify the Eof Delay in centiseconds. |
TCP Flush Bytes |
Enter the TCP flush size in bytes. |
TCP Flush Seconds |
Enter the TCP flush interval in seconds. |
DSCP |
Select the Differentiated Services Code Point (DSCP) value from the drop-down list, or search for it from the list. |
TOS |
Select the Type of service (TOS) value from the drop-down list. |
Nodelay |
Enable this option to prevent delay when using the Nagle’s option. |
Quick ack |
Enable this option to send quick acknowledgment after receiving data. |
Cork |
Enable this option to allow using the Nagle’s algorithm cork option. |
System Send Buffer Size |
You can set the value for the send buffer size for flow control. |
System Receiver Buffer Size |
You can set the value for the receive buffer size for flow control. |
Click Create Path
or Create and Run
, as required. Select Cancel
if you need to get out of the Add Path page without adding a path.
Once the path is created, you’ll be able to see the new path in the Overview page of the Distribution Server.
Log in to GGSCI.
Use the command:
START MANAGER
For more information, see START MANAGER
in Reference for Oracle GoldenGate.
ADD REPLICAT group_name
group_name
is the name of the Replicat group. For more information, see Creating an Online Replicat Group in Administering Oracle GoldenGate and GGSCI Command Interface Help. in Reference for Oracle GoldenGate.