Use target-initiated paths when the network security policies prevent Deployment A's
Distribution service from opening network connections to
Deployment B's Receiver service. If Deployment A's Distribution
server is unable to initiate connections to Deployment B's
Receiver service, but the Receiver service can initiate a
connection to Deployment A's Distribution service, then you can
create and run a target-initiated path on Deployment B to pull
Trail files from Deployment A.
The source deployment is the deployment where you create the
target initiated Path. The target deployment is the remote
deployment from which you are extracting data (where your
Extract runs and produces Trails).
Before you begin
Ensure that you create GoldenGate connections for each deployment you want
to connect to, and then assign them to the deployment from which the path originates. For
example, the deployment where you create the Distribution Path or target-initiated
Receiver Path.
Otherwise, in IAM-enabled deployments, you'll encounter the error:
The network connection could not be established: 'OGG-08654' - 'Invalid or missing OAuth
resource - audiencescope in Client application'.
Add a Credential that allows a source deployment (the deployment where you
create this Path) to connect to a target deployment:
In the target deployment console, log in, and then access the
Administrator (or User Administration in 23ai) page from the navigation
menu.
Click Add User, and then create a user that the source deployment
can use to connect to the target deployment. Assign this user the Operator
role.
Open the source deployment console, and then navigate to the
Configuration page.
Under the Database tab, click Add Credential, and then complete
the following:
Credential Domain: Enter a name for this connection
Credential Alias: Enter an alias
User ID: Enter the name of the user created in step 2.
Password and Verify Password: Enter the password
associated with this user from step 2.
Click Submit.
Create and run a Receiver
Path
To add a Receiver path:
In the OCI GoldenGate deployment console, click Receiver
Service.
On the Overview page, click Add Path (plus icon).
On the Add Path page, complete the fields as follows:
For Path Name, enter a name for the path.
(Optional) For Description, enter a brief description of
this path's purpose.
(Optional) Enable Reverse proxy enabled to connect to the
target using a reverse proxy.
For Source Authentication Method, select one of the
following:
OAuth: Select this option if the source and target
deployments are IAM with Identity Domains enabled. This option uses the client
credentials for authentication from the Distribution Service to Receiver
Service.
Note:
In IAM enabled
tenancies, select OAuth when connecting to another IAM-enabled
deployment.
UserID Alias: This option uses a UserID Alias that you can
create on the target Oracle GoldenGate to establish a connection.
Note:
Create
a credential using the IAM user when connecting to an IAM-enabled deployment
from a GoldenGate credential store deployment. Ensure that the user exists in
the IAM Identity Stripe.
For Source, select a data transfer protocol from the dropdown:
ws: If selected, Source Authentication Method is not
required.
wss: Web socket secure is the default option.
For Source Host, enter the host name of the source
deployment.
For Port Number, enter the source deployment port
number.
For Trail Name, enter the name of the source deployment's
Extract trail file.
Deployment Name is required if Reverse Proxy is enabled.
Enter the source deployment name.
URI Path is required if Reverse Proxy is enabled. Enter the
source deployment URI path.
For Domain, enter the source credential domain.
For Alias, enter the source credential alias.
Generated Source URI autopopulates based on the values
entered. Click Edit (pencil icon) to modify the URI, if needed.
For Target Trail Name, enter the name of the Trail file as
it's received by the target.
For Target Encryption Algorithm, select an encryption algorithm for the target
trail:
None
AES128
AES192
AES256
For Enable Network Compression, select this option to set
the Compression Threshhold.
For Sequence Length, enter the length of the trail sequence
number.
For Trail Size (MB), enter the maximum size fo a file in a
trail.
For Configure Trail Format, enable this option if you want
to configure the trail file format, and then complete the additional fields as
needed.
Under the Encryption Profile section, complete the following fields as needed:
Profile Name
Encryption Profile Type
Masterkey Name
For Begin, select where to log data:
Now
Custom Time
Position in Log (default)
For Source Sequence Number, select the sequence number of
the trail file source deployment Extract.
For Source RBA Offset, enter the Relative Byte Address (RBA)
in the trail file where you want the process to start.
For Critical, set this option to True if the distribution
path is critical to the deployment. The default is False.
For Auto Restart, set this option to True if you want the
distribution path to restart automatically if it's terminated.
For Auto Restart Options, indicate the number of retries to
retart the path process and the delay duration interval between retries.
Under Rule-set Configuration, complete the following fields as needed:
For Enable Filtering, if selected, click Add
Rule, and then complete the additional fields.
Under More Options, complete the following fields as needed:
EOF Delay: end of file delay before searching for source data
Checkpoint Frequency: frequency in seconds for routine checkpoints
App Options
TCP Flush Bytes: Flush size
TCP Flush Seconds: Flush interval
TCP Options
DSCP: network differentiated services
TOS term of service
TCP_NODELAY: disables use of Nagle's algorithm if enabled
Quick ACK: sends acknowledgement if enabled
TCP_CORK: enables use of Nagle's algorithm
System Send buffer Size
System Receive Buffer Size
Keep Alive: timeout for keep alive
Click Create and Run.
You return to the Overview page, where you can view the status of the path
process.