Adding an instance of the CDC Replication Engine for Teradata (UNIX)

Before you can start replication, you must add and configure an instance.

Procedure

  1. If you are configuring the first instance of the CDC Replication Engine for Teradata after installation, you can proceed to Step 3 of this procedure.
  2. At the command prompt, launch the configuration tool by issuing the following command in the specified directory: 
    \CDC_installation_directory\bin\dmconfigurets
  3. At the welcome message, press Enter to continue.
  4. Enter the name of the instance that you want to add and press Enter.
  5. Enter the port number which CDC Replication uses for communication with client workstations running Management Console and other servers. CDC Replication displays a default port of 10701. Press Enter.

    This port number is not applicable for other applications installed on the same server. You will use this port number when specifying access parameters for your datastore in the Access Manager perspective in Management Console.

  6. Enter the amount of physically available RAM that you want to allocate for this instance of CDC Replication and press Enter. By default, the configuration tool allocates 1024 MB of RAM for each instance.

    Using values other than the defaults or allocating more RAM than is physically available on your server should only be undertaken after considering the impacts on product performance.

  7. Select the encryption profile from the list.
    If you would like to enable TLS for communication between source and target, you must select an encryption profile with encryption enabled. Click Manage to view and manage the available encryption profiles. Encryption profiles can be shared between multiple instances of CDC Replication.
  8. If you need to add new Teradata drivers, press 2.

    Enter the path of the new Teradata driver and press Enter. Repeat this process until all necessary drivers have been added. Ensure that you have also added the .jar files necessary for the drivers

  9. When all drivers have been added, press 4 to continue with the configuration.
  10. If you want to use TCP/IP as the exclusive method of communication between datastores, enter n and press Enter. If you want to have the option to use either a JMS provider or TCP/IP as the communications protocol, perform the following steps:

    A JMS provider should be used when characteristics of your network prevent the existence of a long-term, stable TCP/IP connection.

    1. Ensure that a queue has been created by your system administrator and is named correctly. Each CDC Replication instance that is to use a JMS message provider must have a queue named in the format CDC_<port>, where <port> is the five digit TCP listening port number of the instance. You can left-pad the number with zeroes if necessary to ensure five digits (example, CDC_00123).
    2. Enter y and press Enter.
    3. Enter 2 to add a JMS provider.
    4. Enter the fully qualified path to your JMS provider .jar file and press Enter.
    5. Enter 4 and press Enter to complete the configuration of the JMS providers.
    6. Enter 1 to add a JMS connection.
    7. Enter a JMS remote connection factory name and press Enter. For example, jms/ConnectionFactory. A connection factory encapsulates a set of connection configuration parameters that has been defined by an administrator. CDC Replication uses this to create a connection with your JMS provider.
    8. Enter the user name and press Enter.
    9. Enter the password to authenticate to the JMS server and press Enter.
    10. Enter the password a second time to confirm and press Enter.
    11. Enter the JNDI initial context and press Enter.
    12. Enter the URL that is relative to the JNDI Initial Context and press Enter.
    13. Enter the user name for the JNDI Principal and press Enter.
    14. Enter the JNDI credentials password and press Enter.
    15. Enter the password a second time to confirm and press Enter.
    16. Press Enter again to return to the Engine Communication Connection menu.
    17. Press 5 if you want to verify the connection and then press Enter to return to the Engine Communication Connection menu.

      If the JMS Provider is not configured correctly, CDC Replication will use TCP/IP as the communication protocol between datastores.

    18. Enter 7 to complete the configuration of the engine communication connection.
  11. Enter the name or IP address of the Teradata server that contains the database for replication and press Enter.
  12. Enter extra JDBC parameters if required. Multiple options are separated by semicolons.

    If you are using the Teradata JDBC driver version 17.10.00.07 or higher and the Teradata database supports SSL/TLS but these security features are not enabled, add the following parameter to avoid TLS connection errors: SSLMODE=DISABLE

    See this technote for more information: https://www.ibm.com/support/pages/node/6485893.

    Note: Do not select y and enter values unless you are directed to do so by an IBM representative.
  13. Enter the user name for the specified database and press Enter.
  14. Enter the password for the specified database and press Enter.

    The configuration tool will now search the database for schemas.

  15. Enter the number that corresponds to the database schema used by CDC Replication for metadata tables and press Enter. You can specify any schema except those in use by other installed instances of CDC Replication for the given database.
  16. Enter the absolute path for the refresh loader and press Enter.
  17. If CDC Replication detects an unsupported encoding, an error message will be displayed and you will be asked to choose an alternate encoding.
    1. Enter y to proceed.

      If you enter n and press Enter to cancel, the instance will not be created.

    2. Enter a value to choose how the alternate encodings will be displayed:
      1
      Displays the available alternate encodings that are the closest match to the database.
      2
      Displays the available alternate encodings in order of byte length.
      3
      Displays all available alternate encodings.
    3. Enter the number for the encoding to be used and press Enter.
  18. The configuration tool creates the CDC Replication instance and prompts you to start the instance. Enter y to start the instance.

    The configuration tool will prompt you if your configuration is about to overwrite the metadata for an existing instance.