Adding an instance of the CDC Replication Engine for InfoSphere DataStage (UNIX and Linux®)

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

Procedure

If you are configuring the first instance of IBM® Data Replication after installation, you can proceed to Step 3 of this procedure.
At the command prompt, launch the configuration tool by issuing the following command in the specified directory:
```
\CDC_installation_directory\bin\dmconfigurets
```
At the welcome message, press Enter to continue.
At the Confirm dsjob path message, the installer auto-detects the current path of dsjob.exe used to automatically start jobs when using the Direct Connect connection method. Enter y to continue or n to quit installation and change the path variable.

Note: The Confirm dsjob path message does not appear if you have not installed InfoSphere® Information Server and set up the dsjob path on the same system as you're installing CDC Replication.
Enter 2 and press Enter to add a new instance of CDC Replication.
Enter the name of the instance that you want to add and press Enter.

The instance name must be unique.
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 10401. 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.
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.
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.
Would you like to include third party libraries in instance classpath? (y/n) [y]:
- Enter 1 to List Current Drivers.
- Enter 2 to Add Driver.
- Enter 3 to Delete added Driver.
- Enter 4 and press Enter to complete the process.
Note: To support S3 and ADLS with parquet, users need to include absolute path to the jars in the third party libraries.
A username of tsuser is displayed; this is used for authentication when creating a datastore in Management Console. You cannot modify this value.
Enter the password that is used to authenticate the user tsuser.
Confirm the password by typing it again.
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.
At the prompt, would you like to retrieve database login credentials from an external secret store through a Java user exit? (y/n)
1. Select whether to use an external secret through Java credentials retriever user exit authentication (y) or not (n).
2. Enter y and subsequently press Enter.
You are prompted to enter the Java class name of the external secret store user exit, for instance com.datamirror.ts.external.keystore.VaultExternalSecretStoreTest.

Note: Only S3 and ADLS can be authenticated via Userexit.