Use the GUI Installer to install Connect CDC - Connect_CDC - connect_cdc_mimix_share

Start the GUI Installer.

When the originating host is UNIX, run the GUI installer with the command:

sh ginstaller.sh

When the originating host is Windows, run the command:

ginstaller.cmd

The Welcome window has the fields in which you set constants for the operating system. The operating system that you select affects what options are included on subsequent windows.

Field	Description
Host	Enter a host name. Enter the name of the local machine on which you are installing. For remote install, enter the name or IP address of the remote host.
Operating System	Defaults to the operating system on the local machine. Select the operating system type that matches the installing host machine.
Root Password	(Linux and UNIX recipient hosts only--this option is not available for other operating systems.) Enter the root password if you want the Connect CDC Listener automatically started when the host reboots. The start and stop scripts are installed. Leave the password blank when you do not want the startup scripts installed on a Linux or UNIX host. Note: If the scripts to start Connect CDC Listener are not installed during installation, for example if the install is interrupted, they may be manually copied from their location in the kernel directory.
User ID	(Remote installs only) Enter the userid for logging on to the remote host.
User Password	(Remote installs only) Enter the password for logging on to the remote hosts.

Click Next.

The License Agreement screen displays.

Read and accept the license agreement:

The Java Path screen displays.

Enter the path where the Java program is located.

Notes:

For the Java installer, all paths specified during the install should use the forward slash (for example, /usr/java11.0/bin/).
The Java path you specify should also be part of the user ID PATH environment setting.

Click Next.

The Installation Target Directory screen displays.

Identify the directory where Connect CDC is to be installed. If installing remotely, the directory must be accessible to the remote host.

Note: When reconfiguring, the destination folder fills in with whatever was set during the previous install or reconfiguration.

Click Next to display the AS400 Offbox install and Translate Binary Data Values Option window displays.

Click Next to treat the binary FOR BIT data binary values as characters (if selected) on AS400 hosts.

The Installation Components Selection window displays.

Select the Connect CDC components to be installed. A target-only install is for IBM i, UDB, or Teradata databases. In this case, the change selector is not installed on the target. The option to install Jetty is grayed out if you are installing on IBM i.

Click Next to display the Database Selection window.

For UNIX, the following window is displayed:

For Linux, the following window is displayed:

Note: Sybase is not supported on Linux and MySQL and SQL Server are not supported on UNIX.

Select the database types that will participate in data movement.

Note: When reconfiguring, the selected database types are set according to those chosen in the previous install.

If you select Oracle, the Oracle JDBC Driver Information window displays. In this window, Provide Oracle JDBC driver information based on the version number.

Note: If you select Oracle and wish to create a new remote server for Oracle, you must install the appropriate JDBC drivers. The JDBC driver is required to access the remote instance of Oracle. This must be done even if Oracle is not installed on the remote host. For Windows you can use the Connect CDC Install Wizard to install the appropriate JDBC drivers. For Linux and Unix you must manually download the JDBC drivers. For more information, refer to the section, “Create a New Remote Oracle Server” in Chapter 2, Defining a Model, of the Getting Started Guide.

Specify the path for the JDBC driver directory for the appropriate Oracle versions, for example for Oracle

12c:/export/home/app/oracle/product/12.2.0/dbhome_1/jdbc

Click Next.

If you select UDB, the UDB JDBC Driver Information window displays. Use this window to set the UDB JDBC driver information based on the version number. You can use this information to validate the appropriate driver based on Db2 and Java version.

Note: The JDBC driver directory should have been installed and the path set up and the DB2 instance name defined before the install. If you have not set these up, cancel and see the setup requirements for UDB Db2.

Specify the following information:

Location for the JDBC driver directory, for example
```
:/common/users/dvtim/js23-32/v540/jdbc
```
Path for the DB2 library, for example:
```
/jdbx/UDB95/db2inst/sqllib/lib64
```
DB2 instance name, for example: db2instl

Click Next.

If you select Target-only installation from step 8, use the following window to enter the JDBC driver directory for remote hosting.

If you select SQL Server, the SQL Server JDBC Driver Information window displays. (Linux only.) Specify the full path to where the SQL Server JDBC driver is located.

If you intend to create a new remote Microsoft SQL server, do the following:

Ensure you have the latest SQL Server JDBC drivers installed. The drivers are required to access the remote instance of SQL Server. This must be done even if SQL Server is not installed on the remote host. For Linux installs, drivers are not installed with the CDC software. Therefore, you must manually download and install the latest JDBC drivers for Microsoft SQL Server on Linux.
Download and install the SQL Server command-line mssql-tools for Linux.
- mssql-tools include the sqlcmd command-line query utility and the bulk copy program (BCP) utility for remote loading to the target.
- The mssql-tools must be installed on the remote host machine that is applying the data to the remote SQL Server instance.
- After you install the utilities, append the BCP location to the PATH environment setting of the user running the kernel.
- This software is not provided by the Connect CDC install program. To download the utilities, see the “Install SQL Server tools” webpage of the “SQL Server on Linux” Microsoft online documentation.

Note: For information about creating a remote server, see the section, “Create a New MS SQL Server” in Connect CDC Getting Started Guide.

For other selections, set the path for the JDBC driver in the displayed windows. The JDBC drivers depend on:

The operating system chosen in the initial Welcome window

Database types selected for participation in data movement

The Browse button appears only if you are installing locally. Select the directory where the driver is installed. If installing remotely, the directory must be accessible to the remote host.

Note: When reconfiguring, the driver path contains the value provided in the previous install or reconfiguration.

DatabaseType	What to do...
Informix	Specify the full path to where the JDBC driver file is located, and click Next. You will see this window only if you selected Informix as a database type installed on this recipient.
MySQL (Linux only)	Specify the full path to where the MySQL Connector/JDBC driver is located, and click Next. You will see this window only if you selected MySQL as a database type installed on this recipient host.
PostgreSQL	Specify the full path to where the PostgreSQL JDBC driver was installed, then click Next. You will see this window only if you selected PostgreSQL as the database type installed on this recipient host.
Sybase (UNIX only)	Specify the full path to where the `jconn4.jar` file is located. Click Next. You will see this window only if you selected Sybase as a database type installed on this recipient host.
Teradata	Specify the full path to where the Teradata JDBC driver was installed, then click Next. You will see this window only if you selected Teradata as the database type installed on this recipient host.

Click Next to display the Listener Port window.

Specify an available TCP/IP port number for use by Connect CDC Listener. The install verifies the port is available by checking the /etc/services file on UNIX and attempting to open a socket connection on the specified port number.

If the port number is not found in the /etc/services file, it listens on the port to determine if it is currently in use. The installer assumes the port is free if the port is not active.

Note: When reconfiguring, the port number contains the value specified in the previous install or reconfiguration. When reconfiguring an install, Connect CDC Listener must be shut down prior to installing or the Installer assumes the port is in use by another service (see Stop Connect CDC Listener).

Click Next to display the JVM Memory Specifications window.

Specify the minimum and maximum amounts of memory, in megabytes, to use for data movement. We recommend that the maximum allocation be equal to the minimum allocation for performance efficiency. 1024MB is the default minimum and maximum value. You can change these values, but lower values may impact performance and higher values are subject to the memory limit on the machine where Connect CDC runs.

If reconfiguring, the memory minimum and maximum parameters contain the values specified in the previous install or reconfiguration.

Click Next to display the Encryption options window.

Select the Use encrypted communications option to use encryption in all communications with the recipient host.

When reconfiguring, the Use encrypted communications option is selected since it was chosen in the previous install or reconfiguration.

Click Next to display the Summary of Selections window which lists the selected install parameters.

Use the GUI Installer to install Connect CDC - Connect_CDC - connect_cdc_mimix_share - 5.8

Connect CDC Installation Guide