2.4.4 Target Initiated Distribution Path

This topic provides information on target distribution path.

The target receiver server must establish a connection path to the source distribution server. This setup enables the OCI GoldenGate deployment to pull trail files from the source to the target OCI GoldenGate environment.

To create a Target-Initiated Distribution Path, follow the steps below:

  1. In the OCI GoldenGate self-service console, go to the Receiver Service section.
  2. Under the Receiver Service page, locate and select the Target-Initiated Path option.
  3. Click on the “+” symbol to create a new Target-Initiated Path.
  4. Enter the Path Details as shown in the images below, and then click Create Path to complete the configuration.
    1. Path Name – Enter a unique name for the path.
    2. Source Host / Endpoint – Specify the source distribution server hostname or IP.
    3. Port – Enter the listener port of the source distribution service.
    4. Authentication Details – Provide the Operator username and password from the source deployment.
    5. Encryption Profile – Select the required encryption profile (OCI Vault or Local Wallet).

User should note the following configuration settings while creating the Target-Initiated Distribution Path:

  • Reverse Proxy Enabled? → Off
  • Source Authentication Method → UserID Alias
  • Sourcewss
  • Source Host → <host:port> (provided by the OBCS SaaS team via Service Request)
  • Source Trail Name → <trail name> (same as the trail name used in Extract)
  • Source Aliasdt1np_ggnet alias created in the Credentials step above
  • Target Trail Name → np (can be any two-letter name)
  • Auto Restart → On

Note:

Adding the OBCS App unique URI path in the source breaks the Generated Source URI.

Hence, make sure the Generated Source URI is edited as shown below: wss://obcspresales.obcs.ocs.oc-test.com/nonprod/ggs:443/services/v2/sources?trail=np

Change to

wss://obcspresales.obcs.ocs.oc-test.com:443/non-prod/ggs/services/v2/sources?trail=np

After successfully creating the Distribution Path, the newly created path will be displayed on the Target-Initiated Distribution Path page.

Figure 2-54 Receiver current State



  • To validate the Target-Initiated Path, navigate to the Target-Initiated Path menu on the left, click on the started path, and then select Path Statistics.
  • You should now be able to view the Path statistics, displaying details such as DDL changes, table updates, and other relevant replication metrics.

Figure 2-55 Receiver current Details



  • Navigate back to Target Initiated Path and from the Action list for the Path, select Start.

    Figure 2-56 Start Receiver Service



  • Once the path is up and running, navigate to Target-Initiated Path from the left-hand menu and click on the created path to view its details.

    Figure 2-57 Target-Initiated Path



  • To validate the Target-Initiated Path, navigate to the Target-Initiated Path menu on the left, click on the started path, and then select Path Statistics.
  • You should now be able to view the Path statistics, displaying details such as DDL changes, table updates, and other relevant replication metrics.
  • This confirms that the SaaS-to-PaaS Data Replication has been successfully established and that the target is actively pulling trail files from the SaaS environment.