Manage Replication Data Connections

Use data connections to access both data source and target systems. Connections configured to access Apache Kafka are only valid for these targets and cannot be used to connect to data sources.

Disclaimer: Due to the evolving nature, certain parts of this video may or may not be current with your version of the product.

Create Data Connections

Create a new replication data connection.

Replication Data Connection for Oracle

Configure a new connection. The Catalog tab is only enabled once the required information is displayed for the new connection type.
Note: This connection type needs a metabase.
  1. On the Data Connections page, click Add Data Connection.
  2. Enter the required information:
    OptionDescription
    Connection

    Name of data connection.

    Description

    Additional information about this Data Connection.
    Connection type

    Select a connection from the dropdown list.

    Runtime Engine
    • Engine - retrieves database information when configured.
      Note: Only Replication servers will be displayed for JDBC.
    • Add Engine - opens the Add Runtime Engine dialog box.
    Database server hostname or IP address

    Fully qualified hostname (FQDN) or IP address of the Oracle database server. The values are: hostname, IPv6 or IPv4 address.
    Instance name

    Name of an Oracle SID or service name. This is a required field.
    Port number

    Any port number from lower to upper possible port values. This is a required field.

    User name

    User ID credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    Password

    Password credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    JDBC driver version

    Select a version of the JDBC driver from the dropdown list. This version will be used on the database server and it is a required field.

    Enable JDBC encryption

    Option to enable JDBC encryption. Displayed when a JDBC driver version is selected. It is unchecked by default.
    Pluggable database

    Indicates if the database is a pluggable database. Displayed only if Oracle 12c is selected as the JDBC driver version.
    Root container user ID

    User ID for the root container of the database instance. Displayed only if pluggable database is checked. Required if Pluggable database is selected.
    Password

    Password for the root container of the database instance. Displayed only if pluggable database is checked. Required if Pluggable database is selected.
  3. Click Test.
  4. Click Save.

Replication Data Connection for Db2 for IBM i

Configure a new connection. The Catalog tab is only enabled once the required information is displayed for the new connection type.
Note: This connection type needs a metabase.
  1. On the Data Connections page, click Add Connection.
  2. Enter the required information:
    OptionDescription
    Connection

    Name of data connection.

    Description

    Additional information about this Data Connection.
    Connection type

    Select a connection from the dropdown list. When creating a new connection from a project, only connection types that can be used in that project type are present.
    Runtime Engine
    • Engine - retrieves database information when configured.
      Note: Only Replication servers will be displayed for JDBC.
    • Add Engine - opens the Add Runtime Engine dialog box.
    Database location

    Specify the server where the database is located. The values are: remote serveror runtime server.
    Database

    Name of the database. If runtime server is selected as your database location, enter the IP address associated with the runtime server.
    Installation library

    Name of installation library. This is a required field. The default value is the version number for the release. For example, ShareV50.
    User name

    User ID credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    Password

    Password credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    Enable IASP

    To enable Independent Auxiliary Storage Pool (IASP), click the drop-down list and select Yes. By default No is selected. An IASP is a collection of disk units which contains a set of user objects and the necessary system data (for example, storage management directories, object ownership, and authorization information) so that the IASP can be taken offline or brought online independently from system activity on other ASPs.

    IASP name
    • IASP name. The name of the IASP. Do not enter *SYSBAS for the IASP name.
    • RDB name. The name of the relational database. This field is automatically populated with the name you entered for the IASP. Accept this name or enter a different name. Do not enter *SYSBAS for the RDB name.
    Note: When you enter the value in the IASP name field, the value in the RDB name field gets automatically updated with the same values as the IASP name field. If necessary, you can change the value of the RDB name field.
    RDB name
    Specify the relational database name.
    Note: When the value is entered in the IASP name field, the value of RDB name field gets automatically updated with the same values as the IASP name field. You are allowed to change the value of the RDB name field.
    DBMS version

    Indicates the version of the DBMS. The default value is - (dash).
    JDBC driver version

    Indicates the version of the JDBC driver to use on the database server. The default value is - (dash).
    GMT offset

    Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). The default value is - (dash).
  3. Click Test.
  4. Click Save.

Replication Data Connection for Db2 for Linux, Unix, or Windows

Configure a new connection. The Catalog tab is only enabled once the required information is displayed for the new connection type.
Note: This connection type needs a metabase.
  1. On the Data Connections page, click Add Connection.
  2. Enter the required information:
    OptionDescription
    Connection

    Name of data connection.
    Description

    Additional information about this Data Connection.
    Connection type

    Select a connection from the dropdown list. When creating a new connection from a project, only connection types that can be used in that project type are present.

    Runtime Engine
    • Engine - retrieves database information when configured.
      Note: Only Replication servers will be displayed for JDBC.
    • Add Engine - opens the Add Runtime Engine dialog box.
    Database

    Specific database for data connection.
    Port number

    Any port number from lower to upper possible port values. This is a required field. The default value is 50000.

    User name

    User ID credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    Password

    Password credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    DBMS version

    Indicates the version of the DBMS. The default value is - (dash).
    JDBC driver version

    Indicates the version of the JDBC driver to use on the database server. The default value is - (dash).
    GMT offset

    Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). The default value is - (dash).
  3. Click Test.
  4. Click Save.

Replication Data Connection for Db2 for z/OS

Configure a new connection. The Catalog tab is only enabled once the required information is displayed for the new connection type.
  1. On the Data Connections page, click Add Connection.
  2. Enter the required information:
    OptionDescription
    Connection

    Name of data connection.
    Description

    Additional information about this Data Connection.
    Connection type

    Select a connection from the dropdown list. When creating a new connection from a project, only connection types that can be used in that project type are present.

    Runtime Engine
    • Engine - retrieves database information when configured.
      Note: Only Replication servers will be displayed for JDBC.
    • Add Engine - opens the Add Runtime Engine dialog box.
    Database server hostname or IP address

    Host name or IP address of the Db2 for z/OS database server.
    Database

    Name of the database. This is a required field.
    Port number

    Any port number from lower to upper possible port values. This is a required field. The default value is 448.

    User name

    User ID credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    Password

    Password credentials to allow access to test the connection to the database server and data source instance.

    This field is required to test the connection and the input will not be stored.
    DBMS version

    Indicates the version of the DBMS. The default value is - (dash).
    JDBC driver version

    Indicates the version of the JDBC driver to use on the database server. The default value is - (dash).
    GMT offset

    Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). The default value is - (dash).
    Server

    Specify the server for the z/OS server name.
    Port number

    Any port number from lower to upper possible port values for the capture server. The default value is 2626.
    Private key path

    Specify the location of the private key.

    Agent

    This version of the drop-down menu is displayed before the list of agents is retrieved from the server.

    Specify agent

    Specify name of an agent. This is a required field.

    Job card

    Gives the identity of the job to the Operating System (OS), in the spool and in the scheduler. The parameters in the JOB statement help the operating systems in allocating the right scheduler, required CPU time and issuing notifications to the user.

    Job library

    The JCL DD statement identifying the LOADLIB path where DMXDC is installed on the z/OS system required to run the JCL job. z/OS only searches public libraries if none are set.

    ISPF library

    The path where DMXCDC ISPF libraries are installed.
  3. Click Test.
  4. Click Save.

Replication Data Connection for Kafka

Configure a new connection. The Catalog tab is only enabled once the required information is displayed for the new connection type.
  1. On the Data Connections page, click Add Connection.
  2. Enter the required information:
    OptionDescription
    Connection

    Name of data connection.
    Description

    Additional information about this Data Connection.
    Connection type

    Select a connection from the dropdown list. When creating a new connection from a project, only connection types that can be used in that project type are present.

    Runtime Engine
    • Engine - retrieves database information when configured.
      Note: Only Replication servers will be displayed for JDBC.
    • Add Engine - opens the Add Runtime Engine dialog box.
    • Use Kerberos - Selects to use Kerberos protocol for connection security.
    • Principal - Kerberos service user ID.
    • Keytab location - Kerberos credential certificate file location.

    Kafka producer configuration

    Path to a Kafka producer configuration file on the runtime server, if no file is specified the configuration is set to the Kafka defaults.

    Enable asynchronous apply Select the checkbox to enable asynchronous apply.
    Cache size limit

    Specify the cache size limit. The default value is 1000.
    Enable Avro message formatting

    Enabled Avro message formatting to use in schema registry.
    Schema registry connection

    Displays a list of schema registry connections.

    Only those schema registry connections are listed that are made using the same runtime engine used during configuration of the kafka connection.
    Add Connection

    Add a new schema registry data connection.
    Add Broker

    Adds an additional group of hostname or IP address.

    Broker hostname or IP address

    Hostname or IP address for a Kafka broker.

    Port number

    Port number to access Kafka broker.
  3. Click Test.
  4. Click Save.

View Replication Data Connections Details

You can view the replication data connection details for information on the current statuses and time interval between when data changed on the source and when it was captured. For example, not all details are valid for copy replication data connection.
  1. Click () next to the data connections and select Details from the menu.
    The Data Connection Details page opens.
  2. Click Refresh to see the latest statistics, details, and statuses.
  3. Click Close.

Edit Replication Data Connections

Edit an existing replication data connections.
  1. Click () next to the data connections and select Edit from the menu.
    The Edit Data Connection dialog opens.
  2. (Optional) For Description, enter a brief description of the data connection.
  3. Edit properties, depending on your connection type.
  4. Click Test to verify that your credentials are valid for the properties you entered.
  5. Click Save to update the connection

Delete Replication Data Connections

Delete an existing replication data connections.
  1. Click () next to the data connections and select Delete from the menu.
    The Delete Data Connection dialog opens.
  2. Locate the connection(s) you want to delete.
    Note: If a connection is used in a replication pipeline, remove the association before you delete the connection.
  3. Edit properties, depending on your connection type.
  4. Click Delete the message closes, the connections are successfully deleted, and their names are removed and are no longer available for use.