Adding an instance of the CDC Replication Engine for Sybase databases (UNIX and Linux®)

You must add an instance of the CDC Replication Engine for Sybase databases before you can start replication.

Procedure

  1. If you are configuring the first instance of CDC Replication 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 2 and press Enter to add a new instance of CDC Replication.
  5. Enter the name of the instance that you want to add and press Enter.

    The instance name must be unique.

  6. 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 10301. 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.

  7. Enter the maximum amount of disk space that will be utilized by the CDC Replication staging store on your source system. The default value is 100 GB.

    Specify 1 GB if you are creating an instance that will be used as a target of replication. This reduces the disk resources that CDC Replication requires on your target system.

  8. 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.

  9. 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.
  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 fully qualified path to your Sybase installation directory and press Enter.
    The configuration tool reads the SYBASE environment variable to provide a default value. For more information, see your Sybase documentation.
  12. Enter the number of the SYBASE_OCS environment variable and press Enter.
    The configuration tool lists the server names. If the number of detected server names is large, the system offers the option to enter the schema name directly, or you can press Enter to view the pages of schema names.
  13. Enter the number of the Sybase Adaptive Server and press Enter.
  14. If you want to specify extra JDBC parameters, perform the following steps. Otherwise, enter n and press Enter.
    1. Enter y and press Enter.
    2. Enter the extra JDBC parameters in a semicolon-delimited list and press Enter. If your database is configured to require encrypted passwords, add the following value and press Enter.
      AuthenticationMethod=encryptPassword
  15. For user authentication, choose one of the following options:
    Option Steps
    External secret store with Java™ user exit To use an external secret through Java user exit authentication, enter Y and press Enter.

    You are prompted to enter the Java class name of the external secret store user exit, for example com.datamirror.ts.external.keystore.VaultExternalSecretStoreTest.

    1. Enter the case-sensitive database user key from the external secret store for the specified database and press Enter.
    2. Enter the case-sensitive database password key from the external secret store for the specified database and press Enter.

    For more information, see Creating an instance by using database credentials stored in an external secret store.
    User name and password
    1. Enter N and press Enter.
    2. Enter the username for the specified database and press Enter.
    3. Enter the password for the specified database and press Enter. The configuration tool searches the database for schemas.
  16. Enter the number of the database that you want to replicate data to or from and contains all of the tables for replication and press Enter.
    You can set up or decide on this database before you install the CDC Replication Engine for Sybase databases.
    Note: You cannot select a Sybase system database.
  17. 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 database.
  18. Enter the path to the directory that will be used for your Sybase archive logs and press Enter.
    The CDC Replication Engine for Sybase databases uses the archive logs to replicate your database changes.
    Note:
    • All archive logs must be located in one directory and the CDC Replication Engine for Sybase databases must have read permissions for this directory.
    • You must not specify the directory that is being used for your online logs.
  19. If CDC Replication detects an unsupported encoding, an error message is displayed and you are asked to choose an alternative encoding.
  20. 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.