1. Oracle GoldenGate Microservices Documentation
  2. Quickstarts
  3. Connecting Two Deployments Using a Common RootCA Certificate
  4. Connect the Two Deployments through the Distribution Path

Connect the Two Deployments through the Distribution Path

This part of the quickstart describes the tasks that you need to perform if you need to use server, client, and trusted chain certificates when connecting two different deployments over a secure network.

After applying certificates, do the following:

  1. Set up the distribution path on source deployment.

  2. Create a user with the Operator role on target deployment, which would be used by the source when the DISTPATH establishes connection with the target deployment.

    1. From the Administration Service, navigate to the Administrator menu.

    2. Click the plus sign next to Users.

    3. Specify the details for target deployment Operator user, as shown in the following image:Add a user with the Operator role and the Type as Password

    4. Specify a password and click Submit.

Configure the Distribution Path for Connecting Source to Target

  1. On the target side, add a user with the Operator role (dist_user) that is used by the source deployment when the DISTPATH connects to the target deployment.

  2. On the source side, create a credential alias to store the Operator user credential that was created on the target side (dist_user).


    Adding credentials for dist_user on the source deployment with credential alias as ggeast.

  3. Create a distribution path on the source side.

    Note:

    Make sure to use the following guidelines when creating the distribution path:

    • Select the wss protocol.

    • Use the Target Authentication Method as UserID Alias and specify the credential alias, ggeast, which was created for the Operator user.

    • Make sure that the target hostname matches the CN name or SAN name(s) in the target certificate. In this case, the value is east.oracle.com. If this value does not match the value specified in the target configuration file, then the connection will not work.

    See the following image to see the options to set up the configuration:
    Distribution Path configuration options when setting up the connection between two different deployments

    1: Target Authentication Method is selected as UserID Alias

    2: Target protocol is selected as wss

    3: Target name is the same as the CN name specified in the target.cfg file

    4: Credential alias for the Operator user created in the target deployment, is added as alias

  4. Click Create Path. The path is created successfully and is visible on the Distribution Service home page.

  5. To start the path, click Action and then click Start. This will start the distribution path as shown in the following image. You will be able to see the distribution path in running state. Distribution Path in running state.

  6. Navigate to the Receiver Service and you will see the distribution path in running state.Receiver Service showing the distribution path in running state.