Adding an instance of the CDC Replication Engine for Iceberg (UNIX)
Before you can start replication, you must add and configure an instance.
Procedure
- If you are configuring the first instance of the CDC Replication Engine for Iceberg 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.
- Enter the name of the instance that you want to add and press Enter.
-
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 12401. 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 want to use TCP/IP as the exclusive method of communication between
datastores, enter
nand 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.
- 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).
- Enter
yand press Enter. - Enter
2to add a JMS provider. - Enter the fully qualified path to your JMS provider .jar file and press Enter.
- Enter
4and press Enter to complete the configuration of the JMS providers. - Enter
1to add a JMS connection. - 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.
- Enter the user name and press Enter.
- Enter the password to authenticate to the JMS server and press Enter.
- Enter the password a second time to confirm and press Enter.
- Enter the JNDI initial context and press Enter.
- Enter the URL that is relative to the JNDI Initial Context and press Enter.
- Enter the user name for the JNDI Principal and press Enter.
- Enter the JNDI credentials password and press Enter.
- Enter the password a second time to confirm and press Enter.
- Press Enter again to return to the Engine Communication Connection menu.
- Press
5if 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.
- Enter
7to complete the configuration of the engine communication connection.
- A user name of
tsuseris displayed. This name is used for authentication when you create 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.
-
The configuration tool creates the CDC Replication instance and prompts you to start the
instance. Enter
yto start the instance.The configuration tool will prompt you if your configuration is about to overwrite the metadata for an existing instance.